Nvidia and other fixes

This PR fixes nvidia hwaccel compilation. nv-codec-headers need pkgconfig files installed the same place as other libs. Need --enable-nvdec and --enable-ffnvcodec to build all. (fixes #183, #187)
Works around the git ffmpeg version bug #197 and #104. https://github.com/FFmpeg/FFmpeg/blob/master/ffbuild/version.sh#L6
It
Adds --small option. This makes --enable-small ffmpeg config option not the default and disables building manpages. Including this option optimizes ffmpeg executable size rather than speed. It also removes certain metadata, like the descriptions of the codecs (ie, ffmpeg -codecs gives only the name with this option enabled). IMHO, this should not be the default, but this option makes it possible anyway.
Makes the install folder under linux ~/.local if it exists, /usr/local if it exists, and /usr only if neither does. The first two are preferred because they will not overwrite the system packages if installed, but will become the new default ffmpeg on a properly configured machine.
Installs the manpages (except if they are not built, with option --small). Consolidates the install code so it isn't written twice. Only uses sudo if installing to a system path.
Updates documentation for user-facing changes.
Tested in Linux Mint 21.1 (based on Ubuntu 20.04).

I updated the readme, in an effort to make clear the optional dependencies that are needed to install all the codecs and filters, and how to install them. In doing so it helped to re-organize somewhat, putting general build instructions before docker build instructions, and including the Usage before the general (common) build instructions.

Thx, for your work. I will check it asap.

I was just having issues building ffmpeg with nvenc, hopefully this works


Added missing artifacts

Add missing artefacts from graphql, health, open-api and added mutiny. Also bumped the open-api major version to 2.x
Signed-off-by:Phillip Kruger<EMAIL_ADDRESS>

Looks like it's missing reactive-utils ?
See https://github.com/smallrye/smallrye-bom/issues/103#issuecomment-661096431

A, I missed that. Hold on adding it now...

@gastaldi - please have a look again now, added all from reactive-utils.

Hold on - there seems to be a conflic.
@cescoffier - the smallrye-reactive-streams-operators/converters and the smallrye-reactive-utils/reactive-converters both have:
<groupId>io.smallrye.reactive</groupId>
<artifactId>smallrye-reactive-converter-rxjava2</artifactId>

and
<groupId>io.smallrye.reactive</groupId>
<artifactId>smallrye-reactive-converter-reactive-streams-operators</artifactId>

as far as I can see. Might be more. So the groupId/artifactId is not unique ? (Or I am missing something)

The smallrye reactive streams operators project is in maintenance mode. No
releases are planned. Even if a release is done it would not cover the
converters which have been migrated to reactive utils.
On Mon 20 Jul 2020 at 19:46, Phillip Krüger<EMAIL_ADDRESS>wrote:

Hold on - there seems to be a conflict.
@cescoffier https://github.com/cescoffier - the
smallrye-reactive-streams-operators/converters and the
smallrye-reactive-utils/reactive-converters both have:
io.smallrye.reactive
smallrye-reactive-converter-rxjava2
and
io.smallrye.reactive
smallrye-reactive-converter-reactive-streams-operators
as far as I can see. Might be more. So the groupId/artifactId is not
unique ? (Or I am missing something)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/smallrye/smallrye-bom/pull/104#issuecomment-661236444,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADCG7JP77S3B4DGFQBQPL3R4R7IHANCNFSM4PCNYGCQ
.

OK thanks @cescoffier - so we should remove the stream-operators from the bom ?

On Mon 20 Jul 2020 at 19:55, Phillip Krüger<EMAIL_ADDRESS>wrote:

OK thanks @cescoffier https://github.com/cescoffier - so we should
remove the stream-operators from the bom ?

Yes, only the mutiny based implementation should be listed.
—

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/smallrye/smallrye-bom/pull/104#issuecomment-661241992,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADCG7L5LS7OQHJEHKBINO3R4SAIHANCNFSM4PCNYGCQ
.

Thanks :)

Thanks!

It would be nice to squash these commits before merging to master, no?

See here:
https://github.com/smallrye/smallrye-bom/commit/e5952183d3ee290d968d49986e18d5fee06d8e5c

Thanks, I know that option exists but wasn't sure if it was used here (it is forbidden in the Quarkus repository for example) :wink:

🤣


Chrome Web Store users counter shield returns "not found"

Are you experiencing an issue with...
shields.io
🐞 Description
Reproducible example:

https://img.shields.io/chrome-web-store/users/ngbjjfmkdbnkobmnenaclacogdkalimn?style=for-the-badge&logo=chrome&label=Install%20for%20Chrome

However, the addon ID clearly exists: https://chrome.google.com/webstore/detail/dom-update-highlighter/ngbjjfmkdbnkobmnenaclacogdkalimn
🔗 Link to the badge
No response
💡 Possible Solution
No response

Interesting.
This plugin does work with other badges e.g:
https://img.shields.io/chrome-web-store/rating/ngbjjfmkdbnkobmnenaclacogdkalimn
https://img.shields.io/chrome-web-store/price/ngbjjfmkdbnkobmnenaclacogdkalimn
The reason we're showing not found on the users badge is because https://chrome.google.com/webstore/detail/dom-update-highlighter/ngbjjfmkdbnkobmnenaclacogdkalimn does not have an interactionCount so we are getting null back when we call .users() here https://github.com/badges/shields/blob/6e793f1159f7f9689003431b944cc0e6763014f5/services/chrome-web-store/chrome-web-store-users.service.js#L25
This doesn't appear to be broken for all badges. It does work for some e.g: https://img.shields.io/chrome-web-store/users/ogffaloegjglncjfehdfplabnoondfjo so it does appear to be something specific to this plugin.
Normally I'd suggest following up with the upstream service, but google are notorious for providing zero support so :shrug: Fundamentally though, there is no number available for us to report.


Few Ideas

Hey, I have a few ideas which would make this plugin even better!

/r  command - reply to the most recent user
allow us to re-format /msg command (for example I'd love to make it look like this: https://i.imgur.com/qQPt7WS.png)

Thanks!

Thank you, I will work on this when possible.

Reply command finished, language can be modified in language.yml. Please tell me if reply does not work.
I will close this when a stable build is ready for release.
btelnyy-nochatreport-1.0.4-REPLY_TEST.zip

Fixed in 1.1.0


Added mappings

Added mappings to tripper.

Codecov Report
Base: 73.10% // Head: 64.89% // Decreases project coverage by -8.21% :warning:

Coverage data is based on head (9203a41) compared to base (d75f7ac).
Patch coverage: 41.44% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #62      +/-   ##
==========================================
- Coverage   73.10%   64.89%   -8.22%
==========================================
  Files          12       14       +2
  Lines         751     1014     +263
==========================================
+ Hits          549      658     +109
- Misses        202      356     +154

Impacted Files
Coverage Δ

tripper/mappings/mappings.py
41.22% <41.22%> (ø)

tripper/mappings/__init__.py
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Outdated code samples, do not work anymore.

Code samples on this page as well as master branch in https://github.com/Azure-Samples/azure-cosmos-db-python-getting-started do not match the azure-cosmos api anymore. CosmosClient constructor definition seems to have changed. The sample app on Github already has branches with working code but master is outdated. This documentation should be updated to reflect changes.

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

ID: 995ff127-8028-8118-701e-53f07f3a7fc5
Version Independent ID: dff7d0b8-f677-99a9-64b3-89d9bb4fde0d
Content: Quickstart: Build a Python app using Azure Cosmos DB SQL API account
Content Source: articles/cosmos-db/create-sql-api-python.md
Service: cosmos-db
Sub-service: cosmosdb-sql
GitHub Login: @SnehaGunda
Microsoft Alias: sngun

@mkyrath  I just tested the sample and it works fine. Here is the output. The doc is also in sync with the sample. Can you share the specific section where you see it didn't match?

The branches in the sample repo are for testing purposes. The docs are linked to the master branch which has the latest code.

@mkyrath I don't see any doc update, so closing this issue. If you want to discuss further, please reopen.
#please-close


Unable to install

I get this:
$ composer require "cebe/js-search"
PHP Fatal error:  Class 'Phar' not found in /usr/bin/composer on line 23

quite sure this is not related to this package. which version of composer are you using and which PHP version?

You are missing the php phar extensions, see e.g. http://stackoverflow.com/questions/17633784/xampp-composer-php-fatal-error-class-phar-not-found or google the error message for more details.

thanks


Laravel Dusk is active in production

Laravel Dusk is included in the regular composer dependencies which causes it to load when the app environment is set to production. This is a major security risk and composer doesn't let you proceed with this configuration anyway and dumps the following error message:
[Exception]
It is unsafe to run Dusk in production.
My recommended fix for this is to add that dependency to the "require-dev" section of the composer.json instead of in the "require" section.

I also having the same issue when I try to push to Laravel Forge.
What you can temp. do is change your .env set APP_ENV=local or testing.
At least to allow you to run.

Changed composer.json in last commit. Thanks!

As seen in other Laravel issues lie https://github.com/laravel/dusk/issues/289 it seems a problem in other packages after upgrading from Laravel 5.4 to Laravel 5.5.
The best options seems to add composer.json:
"extra": {
        "laravel": {
            "dont-discover": [
                "laravel/dusk"
            ]
        }
    },

@dmitry-ivanov Done.release 5.0.5 created

The best options seems to add composer.json:
"extra": {
        "laravel": {
            "dont-discover": [
                "laravel/dusk"
            ]
        }
    },

In this way works but I cannot manage to test with Dusk on Travis CI.
Because TravisCI install all the composer packages every time, so if dusk is in "dont-discover" it cannot find it.

I've solved adding to the default deploy script on Laravel forge the string --no-dev
cd /home/forge/ciglobalcalendar.net
git pull origin master
composer install --no-dev --no-interaction --prefer-dist --optimize-autoloader
echo "" | sudo -S service php7.3-fpm reload

if [ -f artisan ]
then
    php artisan migrate --force
fi

test

cd /home/forge/..my domain..
git pull origin master
composer install --no-dev --no-interaction --prefer-dist --optimize-autoloader
echo "" | sudo -S service php7.3-fpm reload
if [ -f artisan ]
then
php artisan migrate --force
fi

composer install --no-dev --no-interaction --prefer-dist --optimize-autoloader

Thank you @suisun2015

Illuminate\Foundation\ComposerScripts::postAutoloadDump
@php artisan package:discover --ansi
Segmentation fault (core dumped)
Script @php artisan package:discover --ansi handling the post-autoload-dump event returned with error code 139

I'm getting above when i was install composer

use this command:
composer install --no-dev --no-interaction --prefer-dist --optimize-autoloader

use this command: composer install --no-dev --no-interaction --prefer-dist --optimize-autoloader

used this command but Same, error showing. please give solution for this problem


DD-PPO - RL BaseLine Visual Encoder Output Size

I have a question regarding the output dimension of the visual encoder. There seems to be a discrepancy in the paper.
In the paper (page 15, Appendix C) it says:
Given these modifications, each backbone produces a 1024x4x4 feature map. We then convert this to a 128x4x4 feature map with a 3x3-Conv.
But on the next page (page 16) it says:
Our navigation policy takes the 64x4x4 feature map from the visual encoder, flattens it, and then converts the 2048-d vector to the same size as the hidden size via a fully-connected layer.
Why was the number of channels halved from 128 to 64? I couldn't find an explanation in the code either. When I execute the code, it produces an output of 64x4x4, as was written on page 16.

This repository is associated with a number of papers. I can't tell which paper you are talking about. Please email the first author directly (this isn't quite a question for github).

Oh sorry, I should have mentioned the title of the paper.
My comment was in regards to "DD-PPO: Learning Near-Perfect PointGoal Navigators from 2.5 Billion Frames" (https://arxiv.org/abs/1911.00357), the source for the RL-baseline.
Since the author of the paper (Erik Wijmans) answered a question of mine here before and the question is in direct regard to a part of this repository, I felt it was appropriate to ask the question here.

The second one is a typo, it's 128x4x4

I see, thanks.


Live-input

Is it can handle live video input? With live predictions like
And also can I use weights which I train with VideoMAE from Hugging-Face pipeline? They have this list of files:

Is it can handle live video input? With live predictions like

Yes, I think it is possible to apply video-mae on live-video. Have you tried it? If you face any issue with this codebases, let me know. This sounds interesting, I might add it later.

And also can I use weights which I train with VideoMAE from Hugging-Face pipeline? They have this list of files:

I'm not sure, as the underline framework is different.


Add positioning and design options for the titles

I initially opted for just having them centered and properly scaled, but thinking about it now, they could use some config options (colour, position, font, size, etc.).

I'm bumping this back to 1.1.1 because I'll ultimately need this working to truly close #20.


Warnings while using Swashbuckle on AspNet.Core

I added Swashbuckle 6.0.0-beta902 and the following warnings are throwing at build time:
5>Startup.cs(86,17,86,31): warning CS1701: Assuming assembly reference 'Microsoft.AspNetCore.Http.Abstractions, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60' used by 'Swashbuckle.Swagger' matches identity 'Microsoft.AspNetCore.Http.Abstractions, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60' of 'Microsoft.AspNetCore.Http.Abstractions', you may need to supply runtime policy
5>Startup.cs(87,17,87,33): warning CS1701: Assuming assembly reference 'Microsoft.AspNetCore.Http.Abstractions, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60' used by 'Swashbuckle.SwaggerUi' matches identity 'Microsoft.AspNetCore.Http.Abstractions, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60' of 'Microsoft.AspNetCore.Http.Abstractions', you may need to supply runtime policy

I assume it is because the dependency on aspnet assemblies are old. Can it be updated?
Thanks

This package is obsolete, It has moved to Swashbuckle.AspNetCore https://www.nuget.org/packages/Swashbuckle.AspNetCore/1.0.0-rc1 .
I was wondering the same a few days ago. I guess this should be advertised in a more visible way on the homepage as I guess, a lot of early adopter might be wondering the same. Maybe the description of deprecated packages could be updated it as well to mention the new repo

@sandorfr Multiple people in CoreCLR community are mentioning the .AspNetCore package is going to be merged back to the main package :(
I don't know which one now is true :(

I don't know about maintainer plans about this, but I don't really see it working well.
They are really two different versions of swashbuckle targeting two very different stack sharing almost nothing but a base name (aspnet core and apsnet). I don't know how one would select the right assemblies if it was to be merged together. To me this would be unclear and tricky hence this is very unlikely.

See the announcement at the top of the readme.
Swashuckle.6.0.0-beta* packages are obsolete. The new name is Swashbuckle.AspNetCore.1.0.0-*. The plan is to maintain two separate projects, the original Swashbuckle for ASP.NET / WebApi and Swashbuckle.AspNetCore for ASP.NET Core, that can live on with their respective frameworks

@domaindrivendev ok, good. Now a clear statement from someone who did that :)
What about the annoying warnings?


Made Life Swell Skill working

One known limitation: It just has effect on the own player. Effects on the party is not yet implemented.
We need to extend the Skill or MagicEffectDefinition configuration by a flag, e.g. "AddEffectToPartyMembers", or similar. The configuration is probably missing some more stuff which will be required for other skills... I might have to analyze this first.


Tooltips are applied to all  tags, regardless of class

Hey!
So I noticed today that any  tag with a title attribute is triggering the jQuery UI tooltip. Ideally, it's only applied to  tags with the .osrstooltip class.

Had some time to look into this issue today. Unfortunately, it is not an easy fix. Since the tooltips library relies on the JQuery UI, there are aspects of that library that come with additional functionality (in this case, unwanted functionality). There are two options:

Change to JQuery code to remove adding the style to the .osrstooltip class
Write a new osrstooltip library that does not use JQuery
Both are big jobs. One potential solution is to remove title tags (probably not very desirable). Another option is to hide the title attribute on hover (see: https://spigotdesign.com/hide-title-attribute-hover-dont-remove/), this could be a decent option, but will break any other code that uses title attribute and hover events. Out of the two options, I am not sure how/where to change the JQuery code, and writing a new tooltip library is a massive job (my JS is not strong).
If you have any ideas, please feel free to let me know!

Hey @osrsbox, is this going to make it into the 1.0.3 release? I think it's my last blocker before I can roll the plugin out across my site and start tool-tippin' it up :)

Hey @jburleigh1. Yes, I will build a new release today with the new fix. It took a while as I was trying to update the project web page first to align with the flurry of updates we have had lately! But version 1.0.3 should be up in a couple hours!


nix: allow to define nix.extraConfig as a set

Motivation for this change
Not being able to define nix.extraConfig with Nix language seemed really odd, and it is inconvenient.
Since it is nothing more than a keyValue configuration, it is possible to add a way to declare extra config options using a set.
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

The commit should be prefixed with nixos/nix-daemon

https://github.com/NixOS/nixpkgs/pull/139075

This was done with the above-mentioned PR


documentation: typeMapping definition has no effect if type name and class name are the same

What are you missing in the docs
My config of the generateJava task looks like this since I only want code generation for GQL client and use my own API classes in fetchers:
generateJava {     schemaPaths = ["${projectDir}/src/main/resources/schema"]     packageName = 'my.company.package'      generateClient = true     generateDataTypes = false     typeMapping = [         "Foobar": "my.company.package.FoobarResult",         "FoobarInput": "my.company.package.FoobarInput"     ] }
This works - but I realized that the second type mapping has actually no effect because DGS somehow figures this out from the method signature in my DgsFetcher if the schema type and the java class have the same name . if they don't, the mapping definition for query result classes/types has actually no effect!
Would be nice to add a hint that we only need a type mapping if the names don't match

I'm not really understanding the issue you're describing. The type mapping is for codegen only, the framework doesn't have any knowledge about it.

I can image it is a bit confusing... I'm basically referring to this section:

When you have existing classes that you want to use instead of generating a class for a certain type, you can configure the plugin to do so using a typeMapping. The typeMapping configuration is a Map where each key is a GraphQL type and each value is a fully qualified Java/Kotlin type.

_https://netflix.github.io/dgs/generating-code-from-schema/#mapping-existing-types_
Applied to my example - the following is actually needed if my gql type/java type are not equally named:
typeMapping = [ "Foobar": "my.company.package.FoobarResult" ]
but the following actually is not needed, because it "magically" recognized the class name:
typeMapping = [ "FoobarInput": "my.company.package.FoobarInput" ]
We ran into an issue where changing the typeMapping had no effect and this was our realization.

I think this was a side effect of a bug fixed in: https://github.com/Netflix/dgs-codegen/pull/183


Friend list and BlockList content in getUser request

Friend list and BlockList content in getUser request are stored as Ideas whereas we should see their alias,
maybe more details,
depends if we want to rely on an other api to get more info, which seems liek a better option

done


Finish Project Scope Docs

Docs Link: https://docs.google.com/document/d/11l7Mb60JMRpdJpp9-B7VjWOF4FshBdjzY0FDOTq9sMk/edit?usp=sharing

Closing this! I think we're good here 👍


Remove FlyWheel screenshots for dxt

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


Simplify JSON_INT_MAX

Simplifies the JSON_INT_MAX expression.
Thanks to @LB--  for suggesting to use CHAR_INT instead of 8 (char type is defined as at least 8 bits).

Seems alright to me, though I wonder if the #include <stdint.h> stuff at the top of the file can be safely removed now? I don't see any other obvious places in the source where that header's content was needed.

I agree <stdint.h> should be removed from json.c, but it should be included by  json.h instead of <inttypes.h>:
#ifndef json_int_t
   #ifndef _MSC_VER
      #include <inttypes.h>
      #define json_int_t int64_t

Indeed, the int64_t type is defined in <stdint.h>. Actually,  <inttypes.h> includes <stdint.h> and simply defines additional printf-related macros for the types defined <stdint.h>, which are not needed here as far as I can see.

Header <limits.> is ANSI C, so this patch looks good and <stdint.h> will be removed by #109 anyway.

Thank you for this, unfortunately after further research and consideration I believe #115 offers a better solution for this, so I'm closing this for now.


Listings look odd when in dark mode

the previous and next buttons do not work properly
having fixed them, the ?page=NUMBER does not refresh; now I have handleSearch useEffect triggered when pageNumber changes too


update to 2.1.5

Changes:

Update to 2.1.5

https://github.com/aleaxit/gmpy/tree/gmpy2-2.1.5

Linter check found the following problems:
The following problems have been found:
WARNING: clone/recipe/meta.yaml:58: missing_description: The recipe is missing a description
Warnings were found


False positives when using validateAttributeSeparator

The following lines of Jade cause false positives when using validateAttributeSeparator:
a(style={color: 'red', background: 'green'})
a(class=['red', 'green', 'blue'])
a(class={active: currentUrl === '/'})

@benedfit another false positive
a(href='#') English (US)

Thanks @brunowego. Unfortunately this issue won't be solved until I've finished my work on returning the column number of tokens in jade-lexer, at which point the regex I currently have can be simplified as I won't need to parse the whole contents of each line of Jade to find pairs of opening and closing attribute brackets

Hi @benedfit
For extensively used mixins such like e.g.
+createItem(anItem)(class='aClass anotherClass')

it is also false positive. I hope you can fix it soon. (I understand it is due to the same as mentioned above.)
Thanks your efforts! Cheers.

Thanks, I'll make sure to include this in the test cases once I've finished the improvements to jade-lexer

I'm back on the case with the linter and will hopefully have an update on this soon

Hi both, these issues have been resolved in v2.0.0

Thanks @benedfit


Added sentinel per Target. Added test_next_round , test_same_round_di…

Use descriptive PR message


ciao-controller: Delete image metadata and data

When deleting a tenant delete both the image metadata and the image data
itself.
Signed-off-by: Rob Bradford<EMAIL_ADDRESS>

Coverage increased (+0.005%) to 65.395% when pulling 9891cb13afcc53fa6f20970582b1e6751738747f on rbradford:fix-image-tenant-deletion into 506e50f1cf93f1ca437294c9f8385334b2178323 on ciao-project:master.


Don't print extra info on -q + cargo run

If a process fails then it's probably printing out why and Cargo doesn't need to
do it all over again.
Closes #2735

r? @wycats
(rust_highfive has picked a reviewer for you, use r? to override)

r? @brson

@bors r+

:pushpin: Commit 860f38a has been approved by brson

:hourglass: Testing commit 860f38a with merge b5479d9...

:sunny: Test successful - cargo-cross-linux, cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32, cargo-win-msvc-64


Investigate alternative development paths.

One of our biggest problems, especially this year, has always been orienting new people. Teaching them the existing codebase takes a lot of time, and in that time we often lose people.
A few people expressed frustration at this, and I think there's definitely some value in it. Building a project from scratch definitely has its merits, and I think it's worthwhile to start thinking of alternatives now and assign them to new people.
Start compiling any ideas for alternatives that you have here, even if they're not fully fleshed out, just so that newer people have a starting point.
The first thing we have to do is identify what resources we already have.
Currently in the locker we have:

Pandaboard (Embedded Linux, maybe use to explore ROS? #419 )
AVR Dragon
Arexx (Came with the Dagu arm, repackaged Arduino Mega)

Alternate localization strategy using IR range finders, or ultrasonics.  Currently we have plenty of ultrasonics in the locker.
A possible starting point would be to reach a point of being able to follow the edge of the playing field.

I've been looking into using the ultrasonic with the BeagleBone without using the PRUs and this doesn't seem like a feasible option. We might have to resort to some of the PRU code that @PaladinEng wrote in the past as seen in issue #69 to get the ultrasonics to work.
Any advice on this would be much appreciated @PaladinEng

If we want to move to any of the new BBB modules like @AhmedSamara proposed over the winter break meetings, we could put new members on reimplementing old modules in the new language. Make a whole new bot repository.  Switching the existing backend for hardware communication will be a decent sized task that is easily split up because each of the components are modularized into their packages.  If we want to continue working with webcams, we could attempt to work on moving the robot with opencv visual detection directly. I saw a cool video about a drone being piloted by OpenCV.  If we make a system that can target certain things and drive to it with opencv that might be a useful generic movement tool.

Sean, VJ and I all messed around with alternate localization devices we tested Sonics using arduinos using code similar to this: http://www.theengineeringprojects.com/2015/02/interfacing-multiple-ultrasonic-sensor-arduino.html.
We also tried using a magnetometer(compass): http://www.funnyrobotics.com/2011/03/arduino-with-hmc6352-digital-compass.html.  Both worked but the sonics had limited range and were off by a centimeter. The magnetometer recording were similar to the value from our smartphone compasses


tests failing for getEffective* methods.

Many of the tests I wrote for these are failing, so either I don't understand fully how they are supposed to work or they are broken.

Also the queryAllEffectiveChildren method throws if you call it

https://github.com/Polymer/polymer/issues/2648

https://github.com/Polymer/polymer/issues/2649

fixed in next update


Knex is unable to locate migration files in Node

Environment
Knex version: 2.4.2
Database + version: pg 8.7.3
OS: Node 18.x
Select applicable template from below.
@lorefnon
Bug

Explain what kind of behavior you are getting and how you think it should do

Tried to use Knex to deploy migration scripts from an AWS Lambda function on Node 18 - but Knex is unable to locate migration files from /tmp.
I verified that files do exist in the tmp folder - and I was expecting Knex to be able to locate the files given proper configuration.  It is worth noting that the Lambda was packaged with Webpack with target="node" , and I am using Knex api to load config and call latest.

Error message
Sorry I lost my logs but it was quite clear that it could not locate the files

As a workaround, I was able to read files via third party lib and use a custom source as shown in the Knex documentation; however, this is not ideal.
So, in summary,  I don't know how Knex is reading the files under the hood - but fs can see them but unfortunately Knex is having trouble.

Can you provide a minimal reproduction environment for this ? Also, does it work if ran outside of an AWS lambda function ?

Not sure how to provide an environment - but an easier way to replicate would be to use a local docker image from node base. In the image copy a migration file in a /tmp folder, copy the main file in usr/src/main.js.
ex. main
...
knex.migrate.latest([{directory: "/tmp"}])
...

Then run container


Implement set_agg aggregate function

👋 hi all - first PR here. Excited to contribute to this project.
Which issue does this PR close?
This closes https://github.com/apache/arrow-datafusion/issues/1323.
Rationale for this change
This provides an efficient way to aggregate unique values into an array. This is beneficial for aggregating low cardinality fields where array_agg may require significantly more memory than set_agg.
I mainly implemented this as a way to get familiar the codebase. Though - I'm not 100% sure merging this actually makes sense if the goal of the project is to be as Postgres-like as possible. set_agg is supported by Presto (as linked in the issue above) and other DBMS, but Postgres neither supports set_agg nor array_distinct. The recommended approach to something like set_agg in Postgres is to use array_agg, unnest the values, select distinct, then use array_agg again on the output.
Edit - looks like this is the general approach for getting unique items from an array, but for everything set_agg would work for array_agg(distinct <expr>) would work as well.
What changes are included in this PR?
This includes the implementation of set_agg and a couple tests. It borrows heavily from the patch that implemented array_agg: https://github.com/apache/arrow-datafusion/pull/1300
Open questions
There's a couple specific points I could use feedback on:

Using hashbrown::HashSet for the accumulator instead of std::collections::HashSet - it seems this is preferred in the codebase.
Tests - this was actually the most difficult part of writing this as output ordering of set_agg is nondeterministic. I managed to hack it together but I'm sure there's an easier way (for both integration and unit tests).
Documentation - In general, what docs need to be updated? And given this is a divergence from Postgres, is there anywhere specific this should be called out?

Closing this for now as upon further review, array_agg(distinct <expr>) should work fine for this use case, but there are some bugs in how Datafusion handles non-column expressions in this syntax. Will open another issue when I figure out more.

Thanks for the contribution @james727  -- let us know if we can help out in some way 👍

Thanks for the contribution @james727  -- let us know if we can help out in some way 👍

Thanks @alamb - I think I have a solution for the strange behavior with complex expressions in distinct aggregations in https://github.com/apache/arrow-datafusion/pull/1519 - if you or someone else could have a look and let me know if this makes sense or is totally off base, it would be much appreciated.


[Bug Report] Reporting several bugs that will affect the vehicular control

Hello there. Many thanks for the effort on this project. I’ve been testing the control module of Apollo via this co-simulation bridge, and discovered several bugs that would affect the performance of vehicle in simulation.
—-----------------------------------------------------------------------------------------------------------------------
Bug 01: Vehicle physics are not properly set in simulation.
Currently, the bridge code spawns the ego vehicle but does not set the properties of the vehicle. Setting these properties can make the control performance better. Specifically, following code can be added after the ego vehicle is spawned, and before the control command is executed:
def modify_vehicle_physics(self, actor):
    try:
        actor.set_simulate_physics(True)
        physics_control = actor.get_physics_control()
        physics_control.use_sweep_wheel_collision = True
        physics_control.damping_rate_zero_throttle_clutch_engaged = 0.35
        actor.apply_physics_control(physics_control)
    except Exception:
        pass

This function (derived from another bridge project: https://github.com/MaisJamal/carla_apollo_bridge/blob/f6d803aae82c296a5bb9de6ef0a7f66908f16aba/examples/manual_control_13.py#L667C5-L682C17) will enable the physics feature of the vehicle, and adjust some parameters. However, this is just a temporal fix and I believe there are room for improvement on the car physics.
Reference about the Carla car physics: https://carla.readthedocs.io/en/latest/tuto_G_control_vehicle_physics/
—-----------------------------------------------------------------------------------------------------------------------
Bug 02: Buggy configuration of the control module.
The control module of Apollo will read the configuration file and load it to initialize the controller. Specifically, by default it will load this file:
https://github.com/ApolloAuto/apollo/blob/master/modules/control/conf/control_conf.pb.txt
However, this configuration is buggy from the following aspects:
(a). There are contradictions in tire mass. The default value provided in https://github.com/ApolloAuto/apollo/blob/master/modules/control/conf/control_conf.pb.txt is 520:

However, another file indicates that this value is 530 for the vehicle (Lincoln2017MKZ) to be simulated:

Further investigation is needed to determine which value is correct, and to get more accurate vehicle parameters for simulation.
—-----------------------------------------------------------------------------------------------------------------------
The “calibration_table” in the config file is essential in control module. It will translate the desired acceleration (output of the control calculation module) to the actual vehicle action on vehicle (throttle or brake). This table is consist of various triplets containing three values: speed, acceleration, and command:

For example, the above triplet indicate that, when the speed of the vehicle is 0 m/s, to produce a -1.43m2/s acceleration, a command of -35% on brake is given to the actuator.
There are the following bugs on this config file:
(b). It is obvious that the sign of the control command and acceleration should be the same (e.g., If I want acceleration, I will need to step on the throttle). However, some configurations do not follow this rule. For example, in the following config, a command of -17% on brake is given, when the vehicle needs an acceleration of 0.38 m/s:

Vice versa, some de-accelerations are translated into stepping on throttle:

(c). Another obvious fact is that under the same speed, if I want a greater acceleration, then I will surely need to give a more bigger control on throttle. However, the config file does not follow this correlation. For example, in the following part:

If I want an acceleration of 2.89 m2/s, a command of 70% on throttle is needed. However, If I want an acceleration of 2.9 m2/s (greater than 2.89 m2/s), I will only need 70% on throttle, which is obviously intuitive and incorrect. Many other similar cases are in this config file.
(d). I found that the acceleration commands given in this “calibration_table” are overall too low to produce a prompt acceleration. I raised the overall value of the command values, and the control performance gets better.
(e). There are Abrupt changes in the control signals for acceleration (throttle) and deceleration (brake), due to the very unsmooth transition of the control command in this table.
I tried to modify this config file to solve the above inconsistencies, and the control performance gets better. I will share my modified config file later. By the way, another bridge project has also provided the customized config file: https://github.com/MaisJamal/carla_apollo_bridge/blob/f6d803aae82c296a5bb9de6ef0a7f66908f16aba/apollo_control/control_conf.pb.txt
—-----------------------------------------------------------------------------------------------------------------------
Apollo provides two methods for controlling: PID+LQR, or the MPC control. These codes are under https://github.com/ApolloAuto/apollo/tree/master/modules/control/controller . The function of these controller code is to output the control command (i.e., acceleration and steering angle), based on the input trajectory (which is the output of the Planning module), and the current vehicle state.
Bug 03: Steering control is filtered twice.
In the MPC control code  (https://github.com/ApolloAuto/apollo/blob/master/modules/control/controller/mpc_controller.cc), the output steering command will be filtered twice when FLAGS_set_steer_limit == True:

As shown above, both line 450 and 454 are filtering the steer_angle signal. Line 450 should be deleted.
Bug 04: Filters for controller input error are initialized but not used.
In the MPC control code (https://github.com/ApolloAuto/apollo/blob/master/modules/control/controller/mpc_controller.cc), two filters for lateral and heading error is set, but never used (line 165 and line 167):

In comparison, these filters were set and used in lat_controller.cc (line 811):

I think such inconsistency on the implementation of the filtering process is a bug.
Bug 05: Regarding the trajectory point to follow, inconsistent points were chosen for the calculation of lateral and longitudinal error.
The logic of the control module is to first select a point on the planned trajectory, and then calculate the distance (i.e., error) between the current vehicle state and the state on this planned point. However, in the MPC control code (https://github.com/ApolloAuto/apollo/blob/master/modules/control/controller/mpc_controller.cc), there is an inconsistency problem on the selection of the trajectory point to follow. Specifically, when calculating the lateral error, the “nearest point by position” is selected:

However, when calculating the longitudinal error, the “nearest point by time” is selected:

Generally, the “nearest point by position” and “nearest point by time” are not the same point. Due to such inconsistent selection, the MPC controller will keep calculating the control output based on a NON-EXISTING trajectory point.
It would be recommended to unified the selected of the queried point (e.g., calculating the lateral and longitudinal error both based on the “nearest point by time”).
Bug 06: Inconsistency between the controller frequency (100hz) and the state update frequency (20hz).
By default, the control module (PID+LQR, and MPC) is running with the frequency around 100hz (update the control command every 0.01s). However, the state of the vehicle is updated with the frequency of only 20hz (update every 0.05s):

As a result, other modules will fail to provide timely state data for control module. In this case, the control module will keep calculating and output control commands based on the outdated state. Regarding the difference on frequency, there are about 80% control commands are the outdated control command that should not be implemented.
Possible fix is to modify the code to output the control command ONLY WHEN the state is updated, otherwise the controller will output the previous command.
This bug exists in both the PID+LQR controller and the MPC controller.
Bug 07: Trajectory point is queried based on in-program running time, instead of the state update time.
Taking MPC controller for example, the query point is selected based on the current running time (line 683):

However, this “current_control_time” is not the actual of the current vehicle state. Particularly, the vehicle state provider “injector_->vehicle_state()” contains the correct corresponding timestamp of the current state, and this timestamp should be used as the input of the line 685.
This bug exists in both the PID+LQR controller and the MPC controller.
Bug 08: The controller output is added with redundant feedback, which violates the MPC design (i.e., optimization process and predictive nature).
In the MPC control code, the acceleration is consist of two parts:

“acc_feedback” is the acceleration calculated by the MPC algorithm, and “debug->acceleration_reference()” is the expected acceleration that the controller aims to achieve.
In the closed-loop control like PID, it is correct to directly use “debug->acceleration_reference()” and then rely on the closed-loop mechanism to adjust the control process. However, such solution should not be implemented to the MPC control: In MPC control, the control command is a calculated value based on the finely-tuned MPC algorithm, with the predictive nature and optimization process. In this case, “debug->acceleration_reference()” is not needed, and “acc_feedback” should be the final result (of course this relies on a finely-tuned MPC, which could be a challenge).
Similar problem exists in the steering control command (solely using “steer_angle_feedback” should be sufficient):

Bug 09: Planned trajectory goes off-road.
Control module relies on the planning trajectory, so it is critical to ensure the correctness of the trajectory. However, it is found that the trajectory can often go-off road, making the vehicle hit the road curb:

I tried to tune the parameters of the planning module but it doesn’t work. Maybe some additional codes should be added to the planning module to prevent this situation.
Related issue: https://github.com/ApolloAuto/apollo/issues/15091
Bug 10: Unrealistic planning.
The planning trajectory, particularly the planned speed can be very unsmooth and the vehicle cannot follow the trajectory well. This issue will also affect the performance of the control module.
Details on this issue: https://github.com/ApolloAuto/apollo/issues/14985
Bug 11: Abrupt changes exist in the planned trajectory points.
I have plotted the following figures to present the actual trajectory (red dot line) and the planned trajectory (blue solid line) that was queried during the calculation process in the control module:

In another word, the blue line is the input to the control module. However, it is observed that sudden changes frequently appear in the process. This is because the output of the trajectory is constantly changing based on the current vehicle state, but it is not well smoothed and then fed to the control module.
Such sudden changes also appear in other states (i.e., heading angle, velocity and acceleration):

—-----------------------------------------------------------------------------------------------------------------------
Thanks for reading this report. I have personally tried to fix these bugs and have made some progress. However, the control module is still farm form perfect (or to say, farm from being adequate)...
I've noticed that very few previous ADAS + Simulator has good control performance. Particularly, Apollo + LGSVL simulation does not activate control module at all, and LGSVL is already abandoned. Autoware + Carla simulation also have similar control problems. Openpilot + Carla has flaw but it might have the best performance among all.
I hope this report will help this project. : )

Thank you so much for your work and this bug report.
We are still investing in the development and maintenance of this project, and your effort will help us a lot.
We'll analyze these problems one by one in the near future and try to solve them.
Each progress will be updated here, and thanks again!

Thank you so much for your work and this bug report. We are still investing in the development and maintenance of this project, and your effort will help us a lot. We'll analyze these problems one by one in the near future and try to solve them. Each progress will be updated here, and thanks again!

Hello. I saw that in a recent demo, the car can move smoothly. May I ask what fixes have been implemented? Many thanks!
I opened a new issue to discuss this question: https://github.com/guardstrikelab/carla_apollo_bridge/issues/172


Google FCM Server Key

I'm having trouble going through the steps in this article
Section "Create a Firebase project and enable Firebase Cloud Messaging"
Step 6 is obsolete as Google seems to have changed their model to obtain a Server Key, or the Server Key does not apply to FCM.

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

ID: 2a03ab5f-3dda-f469-33e0-9504c90d468c
Version Independent ID: 4f8e4309-cd06-f09f-00f0-d978b3d16777
Content: Send push notifications to Xamarin.Android apps using Azure Notification Hubs
Content Source: articles/notification-hubs/xamarin-notification-hubs-push-notifications-android-gcm.md
Service: notification-hubs
GitHub Login: @sethmanheim
Microsoft Alias: matthewp

@sethmanheim, Requesting your review on the ask, and help update the document as appropriate. #93552


Prevent logs

Fixes #230

I couldn't prevent logs but I did prevent Sandpack from crashing the site on load. The solution was to NOT use Vite and just use the vanilla environment. Also, I updated everything… like Astro is version 3.0 and Starlight is 0.9. I didn't need to make any changes.


Feature request: Open doors with door knobs is missing.

The integration works great.
But I'm missing the open door feature. Since my door is with a door knob and not with a handle on the outside I can't open the door from the outside. It will be great to add open functionality as a separate entity.
I really like that it allows me to unlock and lock the door without actually opening it. But there is need for open door button where the outside of the door is using a knob.

Hi shiSHARK,
This is already implemented with HA open service. See here: https://github.com/uriyacovy/ESPHome_nuki_lock/issues/1
Let me know if this doesn't work for you.

The issue here might be that HA's frontend doesn't show an open button (yet).
I filed this esphome issue #3495 and they confirmed it's an issue of HA, not ESPHome.
@shiSHARK try this in 🔨Developer Tools → Services:
service: lock.open
target:
  entity_id: lock.mynuki   (← or whatever your nuki's entity_id is in your HA)

It should open your nuki door.
If that works, you can use it in automations or scripts.
Or you could set up a button in ESPHome which you can then use in Lovelace:
esphome:
# ...
button:
  - platform: template
    name: "Nuki Open"
    on_press:
      - lock.open: mynuki

lock:
  - platform: nuki_lock
    id: mynuki
    # ...

Thanks @crixionz. Did you open an issue on HA?
@shiSHARK, waiting also for your feedback.

I did not (yet) @uriyacovy 😐 I want to open a different issue for your component first but am currently procrastinating 😬

Well, I'm on my summer vacation anyway, so take your time :smile:.

Close due to inactivity.


DIY methods of model struct?

Your Question

Is there a way to diy methods of model struct?

The document you expected this should be explained

Want to add some common custom methods, not sure how to implement it
example:
func (m *User) IsEmpty() bool {
    if m == nil {
        return true
    }

    return m.ID == 0
}

Expected answer

Maybe you can express it more clearly

user.gen.go:
// User mapped from table <user>
type User struct {
	ID         int64                 `gorm:"column:id;primaryKey;autoIncrement:true" json:"id"`        // 主键ID
}

// DIY method
func (m *User) IsEmpty() bool {
    if m == nil {
        return true
    }

    return m.ID == 0
}

emmm,  it seems like not a common feature

The example may not be clear, the main thing is to have a way to extend the model methods

do u think providing a method to accept a function template an acceptable solution?

Yes.

ok, we will discuss a most suitable implementation method, And more ideas from you are welcome👍

👌


Sidekick Bookmarklet RC

This PR has been auto-generated from https://github.com/adobe/helix-sidekick-extension/.

https://sidekick-rc-2348173--helix-website--adobe.hlx.page/tools/sidekick/

Changes in this release:

https://github.com/adobe/helix-sidekick-extension/pull/257
https://github.com/adobe/helix-sidekick-extension/pull/262


Add mentions.

This adds a feature to add comments to PRs that touch certain files to ping interested people or to give information to the author. This is intended to take over the responsibility from highfive.
One of the key changes compared to highfive is that this can handle subsequent pushes to a PR (fixing https://github.com/rust-lang/highfive/issues/223). To avoid duplicate mentions in that scenario, this PR introduces the concept of "issue data" which stores data about an issue in the Postgres database.

Thanks! I'm going to go ahead and merge this tomorrow, so I can be around to help resolve issues if something goes wrong. Not expecting any problems though.
Once this is ready we can post a PR adding/migrating high-five mentions to triagebot and after a short period of duplicate mentions remove the high-five configuration for rust-lang/rust (and other repositories eventually).


change the video with arrow keys.

hitting the arrow keys right now pauses the video and lets you move one frame at a time. if you hit space, it continues playing. This isn't really a needed functionality. if the arrow keys shuffled the screens, or just cycled through them, that'd be awesome.

+1

This seems related to Issue #67 – I imagine it’s the QuickTime player intercepting user input.

Fixed for a while, also fixed in the preview panel now in 1.4.1 ;)


youtube-dl Truck Factor

As part of my PhD research on code authorship, we calculated the Truck Factor (TF) of some popular GitHub repositories.
As you probably know, the Truck (or Bus) Factor designates the minimal number of developers that have to be hit by a truck (or quit) before a project is incapacitated. In our work, we consider that a system is in trouble if more than 50% of its files become orphan (i.e., without a main author).
More details on our work in this preprint: https://peerj.com/preprints/1233
We calculated the TF for youtube-dl and obtained a value of 3.
The developers responsible for this TF are:
Philipp Hagemeister - author of 59% of the files
Sergey M. - author of 20% of the files
Jaime Marquinez Ferrandiz - author of 19% of the files
To validate our results, we would like to ask youtube-dl developers the following three brief questions:
(a) Do you agree that the listed developers are the main developers of youtube-dl?
(b) Do you agree that youtube-dl will be in trouble if the listed developers leave the project (e.g., if they win in the lottery, to be less morbid)?
(c) Does youtube-dl have some characteristics that would attenuate the loss of the listed developers (e.g., detailed documentation)?
Thanks in advance for your collaboration,
Guilherme Avelino
PhD Student
Applied Software Engineering Group (ASERG)
UFMG, Brazil
http://aserg.labsoft.dcc.ufmg.br/

I don't think youtube-dl will ever be in trouble since it's public domain.
Closing as offtopic.


Add ability to pass additionnal models to Func for formatting

Add an optionnal 'additionnal_models' attribute to Func allowing to specify additionnal models to pass to formatting function. Useful for SQL queries that involve multiple tables.
Type: feature

Can I have a feedback here? I think this is ready for a merge.

Thanks for your suggestion. I'm thinking that this may be too specific of a context variable at the moment to go in the main library. There have been a few requests for extending Func, and I think I'd like to just support Django's template rendering system and either a) pass in all model metadata as a var or b) have a template tag.
In any case, for now you should still be able to subclass Func and use this change in your project. I will open a discussion about better template rendering and if this belongs in the library or in a third-party extension

Awesome!


New data table from AG

Data table added by AG at 2015-05-16T00_10_28.503565

Nice, looks like it works now!

yes! but we must update the  submodules to include .git after uploads in the config files


Version support and automatic CI build

Description
replaces #1785
Version of docs built using CI: https://intelkevinputnam.github.io/scikit-learn-intelex/
There are two major changes in this PR:

Version switching support
CI deployment to GitHub pages via GitHub action

Version Switching Support
All published versions must be tracked in doc/versions.json as this will allow all subsequent versions of the docs to automatically be able to switch to the latest without needing to rebuild the docs.
The version is supplied by the installed version of scikit-learn-intelex (latest by default in the CI script). This way building the docs is not dependent on the oneDAL environment with the goal of making it easier to contribute to and edit the docs. It should also make builds faster.
Since the move to the UXL Foundation, version switching is broken in the latest version of the docs because of there is a hard coded path to the versions.json that no longer exists (it was intel.github.com/scikit-learn-intelex). It also is now settable in the conf.py (html_context)
CI Deployment to GitHub Pages via GitHub Action
GitHub pages will be updated automatically.  A new directory will be added for each version of scikit-learn-intelex. When the same version is built twice, it is overwritten. See .github/workflows/publish.yml for the script. The branch will need to be changed to main before it will work on the main branch. I'm not sure it is necessary to have the docs built on every merge into main. Adding workflow_dispatch: to the list of conditions for running the action can provide a handy "deploy whenever you feel like it" option.
To build the docs locally, run ./build-docs.sh. Docs can be previewed locally by starting a web server (python3 -m http.server) in the _build directory and using localhost:8000/scikit-learn-intelex as the URL.

Checklist to comply with before moving PR from draft:
PR completeness and readability

[X] I have reviewed my changes thoroughly before submitting this pull request.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have updated the documentation to reflect the changes or created a separate PR with update and provided its number in the description, if necessary.
[X] Git commit message contains an appropriate signed-off-by string (see CONTRIBUTING.md for details).
[ ] I have added a respective label(s) to PR if I have a permission for that.
[X] I have resolved any merge conflicts that might occur with the base branch.

Perhaps this PR could be a good opportunity to address one topic around the version numbers: in open source projects, version "latest" or "dev" is typically meant for docs from "latest commit of the master branch", while the "last released version" is typically "stable".
This is the case for the docs of the scikit-learn package which this repository builds upon, and for most other machine-learning-related libraries such as gradient boosting frameworks and similar.
Could we make the switch here so that the freshest release would be "stable" and have "latest" as something built periodically from the main branch?


fix flush active memtables in batches

Proposed changes
Flush one by one is not fast enough when memtable size could be small (and stale).
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run clickbench

run buildall


Confusion about the setting of validation dataset

Thank you for your great work. I retrained the model according to the code in README. But I founded the default value of "--val_dataset" is "test" in line 12, utils/options.py. Will it affect the results?

This setting follows the prior works.

This setting follows the prior works.

Sorry, can you elaborate on this continuation of the 'piror works'? I also noticed this. Do you mean: when training, it is set to 'val'. When debugging the test.py file, I found that the ‘training’ and ‘val_dataset’ of args are defined to false and test. So the setting about 'val_dataset' is  ‘val’ during training process?


Bumping main to 2.2

Description

Cherry-picked 2.1 to 2.2 version bump commit.
Cherry-picked terser version bump commit to address dependabot alert.
Cherry-picked release notes commit.
Enabled unit and cypress test workflows on all PRs.
Adjusted OSD version used by unit and cypress tests to align with OSD branching strategy.
Updated a website link in the README file that was broken when ODFE was deprecated.
Adjusted path for a dependency used by unit tests to align with migration from EUI to OUI.
Will be closing https://github.com/opensearch-project/index-management-dashboards-plugin/pull/224 in favor of this PR.

Issues Resolved
[List any issues this PR will resolve]
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #227 (1cca570) into main (4821889) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #227   +/-   ##
=======================================
  Coverage   51.55%   51.55%
=======================================
  Files         183      183
  Lines        5804     5804
  Branches      888      888
=======================================
  Hits         2992     2992
  Misses       2591     2591
  Partials      221      221

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


feat(verify): support options.audience: Function

Signed-off-by: Robert Jefe Lindstaedt<EMAIL_ADDRESS>COC: check
Description
This PR adds support for the verify options to allow audience being a function.
Similar to secret callbacks etc. this allows for up- and downstream flexibility:

lib authors to support more complex audience schemes or options
developers to e.g. get audience state from DBs

References
Testing

[x] pass a function to verify(payload, { audience: () => (true) })
[x] see tests for usage patterns and coverage

Checklist

[x] I have added documentation for new/changed functionality in this PR or in auth0.com/docs
[x] All active GitHub checks for tests, formatting, and security are passing
[x] The correct base branch is being used, if not master

@ziluvatar sorry for ping. Could I get your opinion on that?


[Table] Button icon in custom toolbar has incorrect position

What package is this for?

[x] React
[ ] Angular

Describe the bug
If the table has custom toolbar, and there is a button with icon in the custom toolbar,  then the icon position is not correct on Safari.  All buttons with icons produce this invalid result .

Environment/versions:

Browser: [Safari Only]
carbon-addons-iot-react version: [e.g. v2.141.0]

Hi @zhaozhuo813. Do you happen to have the carbon-components-react' and/or carbon-componentspackage installed. If so there may be some styles being overwritten. I ask because I do not see this issue in our storybook when I add a custom button with icon to our table toolbar. If you are usingcarbon-addons-iot-react` package we ship the appropriate version of the carbon packages so it is unnecessary for your app to do so as well.

Hi @zhaozhuo813. Do you happen to have the carbon-components-react' and/or carbon-componentspackage installed. If so there may be some styles being overwritten. I ask because I do not see this issue in our storybook when I add a custom button with icon to our table toolbar. If you are usingcarbon-addons-iot-react` package we ship the appropriate version of the carbon packages so it is unnecessary for your app to do so as well.

closing this since I believe removing extraneous packages should provide the fix. Feel free to reopen if the issue persist.

closing this since I believe removing extraneous packages should provide the fix. Feel free to reopen if the issue persist.


[stable/metabase] interpolate liveness and readiness probes

Signed-off-by: Kash Law<EMAIL_ADDRESS>
What this PR does / why we need it:
Allows modification of the values of the liveness and readiness probe. In our case, we'd like to modify the liveness probe.
Which issue this PR fixes
Special notes for your reviewer:
Change is a no-op compared to the original template. I've also got another PR for this chart that has bumped up the same patch version (https://github.com/helm/charts/pull/20456). Let me know how you'd like me to handle this and I'll make the necessary change.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/ok-to-test

@kl4w Can you please bump the chart version again, due to current conflict

@pmint93 updated chart version and rebased

/ltgm

/approve
/lgtm
Thanks for your contribution ;)


Update list of devices using L4T 32.6.1

Adding jetson-xavier-nx-devkit-emmc to the list of devices that require BSP L4T 32.6.1 as a identified in this ticket https://jel.ly.fish/support-thread-balenaos-xavier-nx-emmc-47bc640

Thanks for your PR @rmorillo24 !


proposal of modification Step4

Step may need more explanation how to modify wrangler.toml.
Below is my idea.
Cloudflare uses a file called wrangler.toml to configure the development and publishing of a worker. More information about Cloudflare configuration can be found on their website. In the example directory, update the wrangler.toml file with the cache name and HTTP endpoint as they appeared in the Momento Console. And also, you need to wave # from blow 3 lines.
[vars]
MOMENTO_REST_ENDPOINT =
MOMENTO_CACHE_NAME =

Thanks for the feedback @MomentoBigFun !
@pratik151192 I think this might be similar to what you did in your recent PR, can you weigh in if you get a moment?

Hey @MomentoBigFun, thanks for calling this out! We have updated our README to be more explicit here https://github.com/momentohq/client-sdk-javascript/pull/944. Feel free to re-open this issue if you see something else missing! Thanks again!


Uncaught TypeError: Cannot read property 'startsWith' of undefined

[Enter steps to reproduce below:]

...
...

Atom Version: 1.8.0
System: Mac OS X 10.10.5
Thrown From: modular-snippets package, v0.1.2
Stack Trace
Uncaught TypeError: Cannot read property 'startsWith' of undefined
At /Applications/Atom.app/Contents/Resources/app.asar/src/pane.js:1002

TypeError: Cannot read property 'startsWith' of undefined
    at /Users/jankiewicz/.atom/packages/modular-snippets/index.coffee:49:22
    at Function.module.exports.Emitter.simpleDispatch (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/event-kit/lib/emitter.js:25:14)
    at Emitter.module.exports.Emitter.emit (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/event-kit/lib/emitter.js:125:28)
    at TextBuffer.module.exports.TextBuffer.saveAs (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/text-buffer/lib/text-buffer.js:1113:27)
    at TextEditor.module.exports.TextEditor.saveAs (/Applications/Atom.app/Contents/Resources/app.asar/src/text-editor.js:666:26)
    at Pane.module.exports.Pane.saveItemAs (/Applications/Atom.app/Contents/Resources/app.asar/src/pane.js:742:16)
    at Pane.module.exports.Pane.saveItem (/Applications/Atom.app/Contents/Resources/app.asar/src/pane.js:726:21)
    at Pane.module.exports.Pane.saveActiveItem (/Applications/Atom.app/Contents/Resources/app.asar/src/pane.js:701:19)
    at Workspace.module.exports.Workspace.saveActivePaneItem (/Applications/Atom.app/Contents/Resources/app.asar/src/workspace.js:684:35)
    at atom-workspace.commandRegistry.add.core:save (/Applications/Atom.app/Contents/Resources/app.asar/src/register-default-commands.js:214:32)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:260:29)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:61
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:580:16)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:388:22)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeyEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:98:36)
    at HTMLDocument.<anonymous> (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:3:61)

Commands
     -0:23.7.0 core:save (atom-text-editor.editor.is-focused)

Config
{
  "core": {
    "disabledPackages": [
      "linter-jshint"
    ]
  }
}

Installed Packages
# User
atom-beautify, v0.29.10
atom-bootstrap4, v1.4.0
emmet, v2.4.3
highlight-selected, v0.11.2
jade-beautify, v0.1.5
javascript-snippets, v1.2.1
language-ejs, v0.2.0
language-pug, v0.0.17
linter, v1.11.14
linter-eslint, v7.2.4
linter-htmlhint, v1.3.0
linter-scss-lint, v3.0.4
modular-snippets, v0.1.2
personal-snippets, vundefined
pigments, v0.31.2
pretty-json, v1.4.4
react, v0.15.0
standard-formatter, v2.0.1
terminal-plus, v0.14.5

# Dev
No dev packages

personal-snippets, vundefined
I wonder if this might have anything to do with

Thank you, I deleted the folder from packages. This was my attempting to load the snippets without your package.

So that was the cause or not? This package loads your snippets from ATOM_HOME/snippets so just move them into there…

Yes it appears to have been.

Okay, as soon as I said yes, it showed up again

Not sure if these help at all. Please let me know if there is anything else I can do to help resolve the bug.
Could it be two different packages conflicting?

Okay, as soon as I said yes, it showed up again, of course

Always the way… 😄
@Ankiewicz Just looking at this… Iv’e actually refactored the code a bit since the last update on my local copy so will push an update that should/might correct this (it makes heavier use of the ? existential operator…)

Could it be two different packages conflicting?

I don’t think so, but do you still have that personal-snippets package running?
The error is thrown from this line so it’s not picking up @project (which is just atom.project.getPaths()[0]), not sure why… Is it actually loading your snippets from ATOM_HOME/snippets and/or you local project snippets?

I don’t think so, but do you still have that personal-snippets package running?
No I deleted the folder. I am still using the snippets, but that attempt of creating my own package, I dropped it.

I created a folder "snippets" in the atom file and it's working from there.(attached image of folder structure)

also, wanted to note it only occurs when I save the file.

Same problem here, these are the steps I followed to reproduce the bug:

Open folder in Atom
Create new folder
Create new file using Application: New File command
Save it in the new folder I've created before

After the step number 4 the error shows up. It seems that path is undefined for files created using Application: New File and it produces that startsWith can be reached because path is undefined. A simple workaround could be check if path exists before execute that part of the code.

This is the best config.
https://gist.github.com/radiovisual/7c27e5a1d0f7aa56e0e3922c98e19ffc


installation issue: homebrew install fails

Brew install fails with the following message:
❯ brew install --HEAD \
>   https://raw.github.com/apiaryio/drafter/master/tools/homebrew/drafter.rb
######################################################################## 100.0%
==> Cloning https://github.com/apiaryio/drafter.git
Error: Failed to download resource "drafter"
Failure while executing: git clone --depth 1 --branch v0.1.2 https://github.com/apiaryio/drafter.git /Library/Caches/Homebrew/drafter--git

❯ brew --version
0.9.5

Then, when I manually tried:
git clone --recursive --depth 1 --branch v0.1.2 https://github.com/apiaryio/drafter.git
cd drafter;
make build

It seems to work fine.

Can you try using the brew command now?

@pksunkara got the same error:
❯ brew install --HEAD \
   https://raw.github.com/apiaryio/drafter/master/tools/homebrew/drafter.rb
######################################################################## 100.0%
==> Cloning https://github.com/apiaryio/drafter.git
Error: Failed to download resource "drafter"
Failure while executing: git clone --depth 1 --branch v0.1.2 https://github.com/apiaryio/drafter.git /Library/Caches/Homebrew/drafter--git

It's working for me. Can you give your homebrew version?

It's failing to execute the git command: git clone --depth 1 --branch v0.1.2 https://github.com/apiaryio/drafter.git /Library/Caches/Homebrew/drafter--git.
Sounds like it would either be caused by a permission error or internet problems.
Does brew doctor report any problems with your installation?
brew doctor

Will the git command run? Does it show any specific problems?
git clone --depth 1 --branch v0.1.2 https://github.com/apiaryio/drafter.git /Library/Caches/Homebrew/drafter--git

Will the git command run? Does it show any specific problems?

I tried git clone --depth 1 --branch v0.1.2 https://github.com/apiaryio/drafter.git /Library/Caches/Homebrew/drafter--git. It seems to work fine.

brew doctor

I do have warnings while running brew doctor listed below. But my normally running brew intsall x succeeds fine.
❯ brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry and just ignore them. Thanks!

Warning: A newer Command Line Tools release is available.
Update them from Software Update in the App Store.

Warning: Python is installed at /Library/Frameworks/Python.framework

Homebrew only supports building against the System-provided Python or a
brewed Python. In particular, Pythons installed to /Library can interfere
with other software installs.

Warning: Unbrewed dylibs were found in /usr/local/lib.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected dylibs:
    /usr/local/lib/libntfs-3g.76.dylib
    /usr/local/lib/libntfs.9.0.0.dylib
    /usr/local/lib/libublio.1.dylib

Warning: Unbrewed header files were found in /usr/local/include.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected header files:
    /usr/local/include/ntfs/attrib.h
    /usr/local/include/ntfs/attrlist.h
    /usr/local/include/ntfs/bitmap.h
    /usr/local/include/ntfs/bootsect.h
    /usr/local/include/ntfs/collate.h
    /usr/local/include/ntfs/compat.h
    /usr/local/include/ntfs/compress.h
    /usr/local/include/ntfs/debug.h
    /usr/local/include/ntfs/device.h
    /usr/local/include/ntfs/device_io.h
    /usr/local/include/ntfs/dir.h
    /usr/local/include/ntfs/endians.h
    /usr/local/include/ntfs/gnome-vfs-method.h
    /usr/local/include/ntfs/gnome-vfs-module.h
    /usr/local/include/ntfs/index.h
    /usr/local/include/ntfs/inode.h
    /usr/local/include/ntfs/layout.h
    /usr/local/include/ntfs/lcnalloc.h
    /usr/local/include/ntfs/list.h
    /usr/local/include/ntfs/logfile.h
    /usr/local/include/ntfs/logging.h
    /usr/local/include/ntfs/mft.h
    /usr/local/include/ntfs/mst.h
    /usr/local/include/ntfs/ntfstime.h
    /usr/local/include/ntfs/rich.h
    /usr/local/include/ntfs/runlist.h
    /usr/local/include/ntfs/security.h
    /usr/local/include/ntfs/support.h
    /usr/local/include/ntfs/tree.h
    /usr/local/include/ntfs/types.h
    /usr/local/include/ntfs/unistr.h
    /usr/local/include/ntfs/version.h
    /usr/local/include/ntfs/volume.h
    /usr/local/include/ntfs-3g/acls.h
    /usr/local/include/ntfs-3g/attrib.h
    /usr/local/include/ntfs-3g/attrlist.h
    /usr/local/include/ntfs-3g/bitmap.h
    /usr/local/include/ntfs-3g/bootsect.h
    /usr/local/include/ntfs-3g/cache.h
    /usr/local/include/ntfs-3g/collate.h
    /usr/local/include/ntfs-3g/compat.h
    /usr/local/include/ntfs-3g/compress.h
    /usr/local/include/ntfs-3g/debug.h
    /usr/local/include/ntfs-3g/device.h
    /usr/local/include/ntfs-3g/device_io.h
    /usr/local/include/ntfs-3g/dir.h
    /usr/local/include/ntfs-3g/efs.h
    /usr/local/include/ntfs-3g/endians.h
    /usr/local/include/ntfs-3g/index.h
    /usr/local/include/ntfs-3g/inode.h
    /usr/local/include/ntfs-3g/layout.h
    /usr/local/include/ntfs-3g/lcnalloc.h
    /usr/local/include/ntfs-3g/logfile.h
    /usr/local/include/ntfs-3g/logging.h
    /usr/local/include/ntfs-3g/mft.h
    /usr/local/include/ntfs-3g/misc.h
    /usr/local/include/ntfs-3g/mst.h
    /usr/local/include/ntfs-3g/ntfstime.h
    /usr/local/include/ntfs-3g/object_id.h
    /usr/local/include/ntfs-3g/param.h
    /usr/local/include/ntfs-3g/reparse.h
    /usr/local/include/ntfs-3g/runlist.h
    /usr/local/include/ntfs-3g/security.h
    /usr/local/include/ntfs-3g/support.h
    /usr/local/include/ntfs-3g/types.h
    /usr/local/include/ntfs-3g/unistr.h
    /usr/local/include/ntfs-3g/volume.h
    /usr/local/include/ublio.h

Warning: Unbrewed .la files were found in /usr/local/lib.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected .la files:
    /usr/local/lib/libntfs-3g.la
    /usr/local/lib/libntfs.la
    /usr/local/lib/libublio.la

Warning: Unbrewed .pc files were found in /usr/local/lib/pkgconfig.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected .pc files:
    /usr/local/lib/pkgconfig/libntfs-3g.pc
    /usr/local/lib/pkgconfig/libublio.pc

Warning: Unbrewed static libraries were found in /usr/local/lib.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected static libraries:
    /usr/local/lib/libntfs-3g.a
    /usr/local/lib/libntfs.a
    /usr/local/lib/libublio.a

Warning: Some directories in your path end in a slash.
Directories in your path should not end in a slash. This can break other
doctor checks. The following directories should be edited:
    /Applications/MAMP/Library/bin/    /usr/local/mysql/bin/

Warning: You have a curlrc file
If you have trouble downloading packages with Homebrew, then maybe this
is the problem? If the following command doesn't work, then try removing
your curlrc:
  curl http://github.com

Warning: Some keg-only formula are linked into the Cellar.
Linking a keg-only formula, such as gettext, into the cellar with
`brew link <formula>` will cause other formulae to detect them during
the `./configure` step. This may cause problems when compiling those
other formulae.

Binaries provided by keg-only formulae may override system binaries
with other strange results.

You may wish to `brew unlink` these brews:

    gettext

I guess, it's probably i could be an issue with brew
@pksunkara My brew version is 0.9.5
❯ brew --version
0.9.5

What's your git version?

❯ git --version
git version 2.3.3
hub version 2.2.0

Well, i've upgraded git to 2.3.5. The issue remains same:
❯ git --version
git version 2.3.5
hub version 2.2.0

Seems to be working for me.

==> Summary
🍺  /usr/local/Cellar/drafter/HEAD: 4 files, 828K, built in 38 seconds

Any updates from others?

@theskumar Can you try it after removing hub symlink as git? I am thinking maybe hub is doing something.

I'm going to close this ticket since we haven't heard back from you @theskumar, please let us know if you are still having problems.
Also note the following message from brew doctor:

Warning: You have a curlrc file
If you have trouble downloading packages with Homebrew, then maybe this
is the problem? If the following command doesn't work, then try removing
your curlrc:
curl http://github.com

Since git internally uses lib curl, this may be relevant and causing problems.


Ability to refresh python environments from notebook interpreter selection

If you create a new python environment via the console, then from a notebook try and select it as a kernel it doesn't appear in the list of python environments. This also occurs when running the Python: Select Interpreter command, however in the latter case a Refresh Interpreter List icon is shown at the top right of the list. The same should be added t the list of kernels.

Thanks for the suggestion.

Dupe of microsoft/vscode-python#17004


reloading source code in source code conflicts with the instructions in README

hi Carl
it is about the scheme version of j-bob
in j-bob.scm
I see you are using (load "j-bob-lang.scm")
and
in little-prover.scm
you are using (load "j-bob.scm")
and in README.md
you said
;; Load the J-Bob language:
(load "j-bob-lang.scm")
;; Load J-Bob, our little proof assistant:
(load "j-bob.scm")
;; Load the transcript of all proofs in the book:
(load "little-prover.scm")
;; Run every proof in the book, up to and including the proof of align/align:
(dethm.align/align)

note that
function redefinition is side effect
thus
this will redefine a lots of primitive functions multiple times
and use these multiple redefined functions to redefine other functions
this hurts performance
as a result
when I follow the instructions in README.md
my scheme interpreter will eat up all the memory of my machine [about 2G of memory]

you can fix this in many ways
my advice is to keep the README.md as it is
and do not use (load) in source code

Thanks for the report.  I'm aware that loading multiple of these files will redefine a lot of functions.  Our intention was that users only need to load one of these files, depending on what set of definitions they need, and each file pulls in whatever dependencies it needs.  Perhaps we should clarify that in the README.
I would not have expected you to get to 2G of memory, however.  I'd like to figure out how that is happening.  I would expect reloading one of these files to redefine the functions in the file, and then the old ones would be garbage collected, so there wouldn't be cumulative memory wasted over time, just a little time wasted once.  I would also expect the memory footprint of each file to be relatively small, so that it would take many, many copies of the whole thing to add up to 2G.  Somehow, my expectations do not correspond to reality.  Do you know what might cause the redefinitions to add up to so much memory usage?

what cause the redefinitions to add up to so much memory usage?

;; as instructed by README.md
;; (load "j-bob-lang.scm")

(define s.car car)

(define (car x) (if (pair? x) (s.car x) '()))

;; as instructed by README.md
;; (load "j-bob.scm")
;; in j-bob.scm
;; (load "j-bob-lang.scm") [again]

(define s.car car)
;; "s.car" should denotes "the primitive car of scheme"
;;   [forgive me to abuse double quote here]
;; but at this point
;; it is already not "the primitive car of scheme"
;; but is "the car of j-bob-lang"
;; note that
;;   "the car of j-bob-lang"
;;   runs slower then
;;   "the primitive car of scheme"

;; thus the following is "the car of j-bob-lang"
;; but runs slower then "the previous car of j-bob-lang"
(define (car x) (if (pair? x) (s.car x) '()))

;; and all the functions in j-bob.scm
;; are composed by the slower version of functions

;; as instructed by README.md
;; (load "little-prover.scm")
;; in little-prover.scm
;; (load "j-bob.scm") [again]

;; you see how things get even worse here

Our intention was that
users only need to load one of these files,
depending on what set of definitions they need,
and each file pulls in whatever dependencies it needs.

IMO
the feature you need here is the module system of a programming language
for example
a simple idea is
when
  (need "cicada.scm")

record the file "cicada.scm" as been loaded
and
when
  (need "cicada.scm") ;; again

just ignore it
note that
the calling to the function "need" can be nested
so recursive function should be used to implement it

Yep, I'm aware that R5RS Scheme lacks a module system.  It's unfortunate.  We used R5RS because the previous books in the series are compatible with it, and we didn't have to bring in details of a module system like Racket's or R6RS's or so on and so forth.  Module systems are fantastic, but beyond the scope of a little book like this one.  So we're making do with the semantics of load in Scheme.
You're right that I picked the wrong default.  I've switched the files to not load each other, so you can load them yourself in sequence and they won't interfere with each other.  Thanks again for bringing this to my attention, and sorry for the difficulties.

glad that I can help ^-^
I am a fans of the little books


Update for PureScript 0.14

Hi @garyb! This PR updates your Bower dependencies for PureScript 0.14. It also updates the repository url in your Bower file to match the PureScript registry.
If this looks good to you, you could cut a v4.0.0 release for codec and I can take care of updating it in package sets.

I missed the warnings! The latest commit takes care of the warnings by:

Adding a kind annotation to GCodec.
Removing the MonadZero instance for GCodec as it's deprecated.

...I've also removed the npm run -s test in CI, as there aren't any tests.


Do not use fixed db user in Exporter

Currently KubeDB uses fixed DB username for some databases in exporter.
For Example,
PostgreSQL:
https://github.com/kubedb/operator/blob/2550b7722fd317f6e275bd20ac301167a11e5a04/pkg/exporter/exporter_handler.go#L239
Elasticsearch:
https://github.com/kubedb/operator/blob/2550b7722fd317f6e275bd20ac301167a11e5a04/pkg/exporter/exporter_handler.go#L131
If user uses custom db user then exporter might not work.

https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/#use-configmap-defined-environment-variables-in-pod-commands

Postgres:
https://github.com/wrouesnel/postgres_exporter/blob/master/cmd/postgres_exporter/postgres_exporter.go#L1073


Update gradle/bt-execution ownership based on AC assignments

Your PR is queued. See the queue page for details.

I've triggered a build for you.


Adding contextual demo for Gemma 2B

Shows how to create a right click interface to bring smarts to any website.

Thanks for the comments. Have addressed them.


Refresh not showing all changes.

Hello I am having a issue with this plugin when I load in data from localStorage.
We allow the user to go ahead and typ in the form and the moment they leave it is saved in localStorage.
When they come back the whole form is being republished if they wish so.
Same goes for a candidate select selectbox.
I tried to solve this with the following js code :
if ($formData[$i].split("=")[0] === "contacts_id") {
    $("[name='" + $formData[$i].split("=")[0] + "'] option").each(function() {
        if ($formData[$i].split("=")[1] === $(this).val()) {

            console.log($(this).val(), $('[name=contacts_id]').selectpicker());

            $(this).attr('selected', true);
            $('[name="contacts_id"]').selectpicker('refresh');

            getContactInformation($formData[$i].split("=")[1]);
        }
    });
}

I gives me back the following : https://puu.sh/v19Jo/fa52ebc37f.png.
And this is the html : https://puu.sh/v1a03/73182f430c.png.
Is there any reason why I don't see 3 selected items.

You probably need to use $(this).prop('selected', true) instead of attr.


Trade order form Spot & Derivatives Updates

Task
-- update dex trade review form based off the notion doc provided by product owners: https://www.notion.so/injective/Trading-Form-UI-Enhancements-v1-11da8b0dc9b14a9fa397b661e4e98abd and figma https://www.figma.com/file/qJtXzfX9nzh0c7yA6G9iI3/Injective-DEX?node-id=0%3A1
-- Completed:

created a map of how I implemented the requested new quote amount input field and associated amount/price/quote amount calcs in https://www.notion.so/injective/Average-Price-Calcs-for-trade-vue-bf1117cded3943f3a6d7b81ff4b56b9c
created a tech spec before building: https://www.notion.so/injective/Dex-Trade-Order-Form-Changes-8c9fda16d5d048df93e852669673b746

This PR entails changes to the spot trade order review form for both market and limit buy/sell orders:

##Todo:

complete post only feature after updating the sdk-ts and sdk-ui-ts since an update for MsgCreateSpotLimitOrder is almost ready
recreate all the business logic and UI for derivatives, but with a twist

Codebase wise, ready for testing @Tofel


Add new entries to governance [UI Only]

Remove this layer, we move it to governance:

The next parts will go to the governance tab (above destroy):

Enable Plugins
Headline: Enable Plugins
Text: Connect your DAO to ink! - a smart contract layer that allows you to extend the functionality of your ink layer.
Flow:

This will be a two part flow, first will be a backend call (that will be authenticated by a DAO signer), second needs signing.
Create Vesting Wallet
Headline: Create a Vesting Wallet
Text: Create a wallet with full voting power, but tokens are locked for a given vesting time.

finished UI

This is now ready to wire with the backend:
Enable Plugins
Initiating all the contracts is a simple API call: https://service.genesis-dao.org/redoc/#operation/Initiate Contracts
Afterwards all the contracts are configured and ready to use. The contract addresses can be found in the DAO endpoint:
"ink_asset_contract": "string", -> A contract representing the asset on ink!
"ink_registry_contract": "string", -> The registry contract to wire the node with the smart contracts
"ink_vesting_wallet_contract": "string", -> A setup vesting wallet
"ink_vote_escrow_contract": "string" -> A setup vote escrow

For the second step (connect to your dao) you have to call an extrinsic (that may need to respect multisig). It's called Hookpoints and the extrinsic is called register_global_callback - it takes the ink_registry_contract as an argument.

Create Vesting Wallet
The contract address is ink_vesting_wallet_contract. The asset to approve is ink_asset_contract

there should be an error if a vesting wallet already exists, that is the get_total
this UI needs a two step process, first is approve the asset and the second is to create the vesting wallet.

Here are some examples on how to read from a contract:
https://polkadot.js.org/docs/api-contract/start/contract.read/
and here how to write
https://polkadot.js.org/docs/api-contract/start/contract.tx
Here is some sample code.
// Parameters for approval and creating a vesting wallet
const tokenContract = '...'; // Address of the token contract
const vestingContract = '...'; // Address of the vesting contract
const amount = 1000; // Total amount of tokens to be vested
const duration = 123456; // Total duration over which the tokens will be vested
const account = '...'; // AccountId for whom the vesting wallet will be created

// Approve the vesting contract to transfer tokens
await tokenContract.tx.approve({ value, gasLimit }, vestingContract, amount)
  .signAndSend(sender, async (result) => {
    if (result.status.isInBlock || result.status.isFinalized) {
      // Once approved, create the vesting wallet
      await contract.tx.createVestingWalletFor({ value, gasLimit }, account, amount, duration)
        .signAndSend(sender, (result) => {
          if (result.status.isInBlock) {
            console.log('Vesting wallet created in a block');
          } else if (result.status.isFinalized) {
            console.log('Vesting wallet creation finalized');
          }
        });
    }
  });

And to get_total:
// AccountId to check for total tokens
const account = '...'; // Replace with the actual AccountId

// Query total tokens
const totalTokens = await contract.query.getTotal(account, { gasLimit: -1 }, account);

if (totalTokens.result.isOk) {
  console.log(`Total tokens: ${totalTokens.output.toHuman()}`);
} else {
  console.error('Error fetching total tokens');
}

Didn't test the code but should give an idea.


A paragraph is all in bold font in "Asynchronous Workflows" article

https://msdn.microsoft.com/en-us/visualfsharpdocs/conceptual/asynchronous-workflows-[fsharp]

/cc @ReedCopsey

Fixed in #128


Use cryptographically signed cookies

In order to improve security and reach nowadays standards, it would be nice to have the session cookie cryptographically signed.

I also feel like this is important.  Would be willing to help if we had a path to adding this feature.

See https://github.com/pyx/sanic-cookiesession/blob/master/sanic_cookiesession/init.py#L14 for suggested implementation.

Since we don't store anything on the user side besides session id, which is just random UUID I don't think there is any reason to sign cookies. I'm sure that we pretty much protected for any type of attacks, except cookie stealing, but this is fixed by using TLS.
If you have any arguments I don't see feel free to comment on this issue I will open it again.


The director name should be exposed to Bosh jobs

We have received a request to differentiate between Bosh directors based on the director name. It would be ideal if that differentiation could take place without operators having to re-define it in every manifest that uses it. Ideally this would be taken from the 'spec' object is spec.director_name.

need to decide whether it's director name or director guid that we would want to use here. cc @emalm @coreyti

Any reason not to do both?

Is either value mutable for a given director?

@emalm director uuid isnt not changeable, but director name could be changed, though it has some downstream side effects (like renaming credhub entries, etc.)

This feature plus adoption by existing components that forward BOSH VM metrics could help operators distinguish between VM metrics when aggregated from several different directors (as happens in the Diego CI accounts), but for that we'd really just like the director UUID and/or name tagged on the metrics when they come out of the health monitor.
/cc @cloudfoundry/cf-diego

Closing and re-opening to make a tracker story

Seems related to: #2077

@mfine30 This isn't actually really related. If you have a field in various deployments for the director name, you're still required to enter it into multiple manifests. There IS a source of truth for the director name, but the bosh director is not giving releases or deployments access to this information without redundancy. As on demand service brokers become more and more relevant, this is even more necessary.


jarSearchableOptions task fails with search/jarSearchableOptions is a duplicate under Gradle 7.0

Plugin version: v1.0
v0.7.3 wasn't affected under Gradle 7.0.
I'm not sure if running under Gradle 6.x works around this error; I can check if needed.
I can also provide the entire offending state of the repository if needed 🕵🏻
> Task :buildSearchableOptions
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.intellij.ide.ui.laf.darcula.DarculaLaf to field javax.swing.text.html.HTMLEditorKit.DEFAULT_STYLES_KEY
WARNING: Please consider reporting this to the maintainers of com.intellij.ide.ui.laf.darcula.DarculaLaf
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
2021-05-27 16:29:32,208 [   3114]   WARN - j.internal.DebugAttachDetector - Unable to start DebugAttachDetector, please add `--add-exports java.base/jdk.internal.vm=ALL-UNNAMED` to VM options
Starting searchable options index builder
2021-05-27 16:29:40,681 [  11587]   WARN - #com.intellij.ui.jcef.JBCefApp - JCEF is manually disabled in headless env via 'ide.browser.jcef.headless.enabled=false'
Found 215 configurables
Searchable options index builder completed

> Task :jarSearchableOptions FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':jarSearchableOptions'.
> Entry search/jarSearchableOptions is a duplicate but no duplicate handling strategy has been set. Please refer to https://docs.gradle.org/7.0/dsl/org.gradle.api.file.CopySpec.html#org.gradle.api.file.CopySpec:duplicatesStrategy for details.

@PawelLipski, thanks for reporting – please provide sources to reproduce this issue.

Pls take a look at https://github.com/VirtusLab/git-machete-intellij-plugin, branch chore/212-eap (current tip at a297482bb40bd6e65a68d7441b1155080f4882fb).
Run ./gradlew buildPlugin (use Java 11).
Also, see a failed run in CI: https://app.circleci.com/pipelines/github/VirtusLab/git-machete-intellij-plugin/4065/workflows/f54a1d08-bbc6-4f80-8a93-4b6dc79d6b25/jobs/4276

Thanks, Paweł – I was able to track and finally fix the issue.


non-refreshed files cause issue in mirrorlist

See http://mirrors.kodi.tv/test-builds/test.txt?mirrorlist
I've added a test file because we were debugging another issue (excessive disk reads by mirorrbits child processes) and wanted to take a look at the mirrorlist for this file.
Obviously because the file is not yet refreshed from local disk, this doesn't work but should probably be handled better.
template: mirrorlist.html:78:89: executing "body" at <$v.FileInfo.Path>: nil pointer evaluating *main.FileInfo.Path
Has to do with last changed made in etix/mirrorbits#9

Thanks for fixing this, implemented and behaves beautifully.


InternalError

Receiving an "InternalError" on self-hosted N8N. Same for PowerShell and PowerShell Core
N8N Version 1.47.1

Hiya! It's working for me on 1.47.1 (installed with npm)
Can I confirm:

This is happening when you try to run a script? Or on trying to install?
You don't have any environment variables enabled that might interfere with running custom nodes or running scripts on your machine? Or any security stuff on your machine?
You have PowerShell installed on the same machine as your n8n instance?
Can you let me know your Node version?

Ah! I think I know what the issue will be: you need PowerShell installed with n8n. If you installed n8n's Docker image, it'll be looking for PowerShell within that environment, not on the host machine.
The PowerShell node is very similar to n8n's Execute Command node: https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.executecommand/

If you run n8n with Docker, your command will run in the n8n container and not the Docker host.

This thread in the community forum is one example: https://community.n8n.io/t/how-to-execute-command-outside-n8n-container/8984
So you either need to take n8n's Docker image and modify it to include PowerShell, or find a way to set up a connection from the Docker container to the host machine (probably using SSH). I'm afraid this isn't something I've ever done, and I'm not very familiar with Docker, so you might be better off on the forum for further support: https://community.n8n.io/


test enhancement

Changed log

add more tests.
add the different PHPUnit version for the different PHP to avoid the warning message.
Please consider the previous Travis build log.

Awesome :)


Trace middleware: replace exit.case attribute with error.type

Hey @NthPortal.
While the exit.case doesn't exist in the spec, we should fill error.type based on the following cases:

If the response was sent and the response code was within 4xx-5xx - the status code must be used
If the response cannot be generated due to an error - the error name must be used

@iRevive ready for merge?

Yep, it can be merged. Thanks for the review.


File Tree Background Color

Awesome Theme! I'm currently using nuclide that is a package on apm not a theme and for some reason it's file tree doesn't become "vibrant". Do you know why this may be?

Ahh.. yes, Nuclide uses their own file tree, you can add the styles below to
your styles.less file:
// Add vibrancy to Nuclide's file tree
.one-vibrancy {
  .nuclide-file-tree-toolbar-container,
  .tree-view {
    background-color: transparent;
  }
}