google-drive-to-sqlite initial release

Basic design:
google-drive-to-sqlite files google.db FOLDER_ID

Looks for auth.json with credentials in the current directory - it wants a refresh_token or an access_token of some sort.
Features for the initial release:

[x] #2
[x] #3
[x] #7
[x] #5

Released: https://pypi.org/project/google-drive-to-sqlite/


imod-wq time_discretization fails on single times within a package; time_discretization is also confusing

In GitLab by @T.Mulder on Sep 6, 2019, 17:16
E.g. model._use_cftime fails on scalar time values since they are not iterable.
This is pretty ugly:
    def time_discretization(self, endtime, starttime=None, *times):

In GitLab by @visr on Sep 7, 2019, 23:58
Fixed by 577c7a5f8f04e03396a1812b57c0a19d3a527d43


Mark concurrency-related tests as "expected to fail" on MacOS

Motivation
Some tests fail to run on MacOS. I think this is probably due the use of spawn rather than fork for multiprocessing. This means that the keys held in memory by moto are lost in the subprocesses. My reasoning started with this comment: https://github.com/spulec/moto/issues/2111#issuecomment-480000481
And then looking here: https://docs.python.org/3/library/multiprocessing.html#contexts-and-start-methods
I discovered that Windows and MacOS use spawn and Linux uses fork. It is quite possible (likely even?) that the spawn mechanism fails to identify the moto parts of the process memory as needed.

These test failures should be fixed by #633

Thanks.

It is quite possible (likely even?) that the spawn mechanism fails to identify the moto parts of the process memory as needed.

If that's the case, then that makes moto pretty useless. We don't want to run tests on Linux only, when smart_open works fine on any system (incl. Windows and Mac OSX).

Thanks.

It is quite possible (likely even?) that the spawn mechanism fails to identify the moto parts of the process memory as needed.

If that's the case, then that makes moto pretty useless. We don't want to run tests on Linux only, when smart_open works fine on any system (incl. Windows and Mac OSX).

Yup, I agree! It might be the case that it is safest to make all the tests which test the parallelisation require the moto_server like a few other tests do currently. This should avoid the issue if it is indeed an issue. Just makes the tests very slightly more painful to run locally.

If that's the case, then that makes moto pretty useless. We don't want to run tests on Linux only, when smart_open works fine on any system (incl. Windows and Mac OSX).

moto has it's quirks, like the problems with multiprocessing addressed in this PR, but it's still very useful for us, because it makes tests that don't touch multiprocessing (the vast majority of them) significantly easier. The alternative would be to run our own server (e.g. localstack) just for unit testing (like we do for some integration tests), which would be a huge PITA.
I think the general direction of this PR is correct: if we expect certain tests to fail on MacOS, then it's OK to disable them, or ignore their failure on that platform only. It would also be good to beef up the test suite with non-multiprocessing tests, but that's out of scope here.

Merged. Thank you for your work @judahrand !!


MODELIX-463 MODELIX-464 model-api-gen fixes

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


logging: serialize tests at compile-time

On slack, Ben R. found a problem ... some LTL programs fail to compile because of a marshalling error.
Here's an example program:
#lang forge
test expect {
    aTest : {
        always true
    } is sat
}

Running raco make .... gives an error like this one:
"ltl.rkt":
  making #<path:/Users/ben/code/racket/fork/extra-pkgs/Forge/issue-marshal/ltl.rkt>
  making #<path:/Users/ben/code/racket/fork/extra-pkgs/Forge/forge/main.rkt>
write: cannot marshal value that is embedded in compiled code
  value: (srcloc #<path:/Users/ben/code/racket/fork/extra-pkgs/Forge/issue-marshal/ltl.rkt> 5 8 78 11)
  context...:
   "/Applications/Racket-7.9-BC/collects/raco/raco.rkt": [running body]
   "/Applications/Racket-7.9-BC/collects/raco/main.rkt": [running body]

The problem is that we're trying to embed a compile-time struct, srcloc, into the run-time code.
I don't know why we're trying to do that, but I do know these srcloc appear in the AST to track source locations. The idea is that forge syntax gets parsed to a data structure that also holds srclocs.
PS calling build-source-location-list gives a serializable result instead of a srcloc struct

This PR avoids the serializing by turning tests into a string at compile-time instead of run-time.
I'm still not sure what else besides LTL can have this issue ... only that the "macro constructor" in define-node-op is making the srcloc struct in the example above. But either way, this PR should hide the problem.

Closing --- the example program works now on dev. Looks like the srcloc are gone.


Python 3.8 error with brew version - error while loading shared libraries: libpython3.8.so.1.0

The output of thefuck --version (something like The Fuck 3.1 using Python 3.5.0 and Bash 4.4.12(1)-release):
Unable to run thefuck command, but here's the output of brew info thefuck:
thefuck: stable 3.30 (bottled), HEAD
Programatically correct mistyped console commands
https://github.com/nvbn/thefuck
/home/linuxbrew/.linuxbrew/Cellar/thefuck/3.30_1 (850 files, 7.7MB) *
  Poured from bottle on 2020-07-06 at 11:22:47
From: https://github.com/Homebrew/linuxbrew-core/blob/HEAD/Formula/thefuck.rb
==> Dependencies
Required<EMAIL_ADDRESS>✔
==> Options
--HEAD
	Install HEAD version
==> Caveats
Add the following to your .bash_profile, .bashrc or .zshrc:

  eval $(thefuck --alias)

For other shells, check https://github.com/nvbn/thefuck/wiki/Shell-aliases
==> Analytics
install: 252 (30 days), 744 (90 days), 2,212 (365 days)
install-on-request: 252 (30 days), 744 (90 days), 2,209 (365 days)
build-error: 0 (30 days)

Your system (Debian 7, ArchLinux, Windows, etc.):
Ubuntu 18.04.4 LTS
zsh 5.4.2 (x86_64-ubuntu-linux-gnu)
Homebrew 2.4.3-91-gf72328d
Homebrew/linuxbrew-core (git revision ea4a0e; last commit 2020-07-05)
Homebrew/homebrew-cask (git revision 1f8cc; last commit 2020-07-06)
How to reproduce the bug:
After brew upgrade a number of brew-installed tools (including thefuck) errored with libpython3.8.so.1.0 errors, e.g.
/home/linuxbrew/.linuxbrew/Cellar/thefuck/3.30_1/libexec/bin/python3.8: error while loading shared libraries: libpython3.8.so.1.0: cannot open shared object file: No such file or directory

For other tools, a brew reinstall X fixed the issue, thefuck is the only one still showing the error.
The output of The Fuck with THEFUCK_DEBUG=true exported (typically execute export THEFUCK_DEBUG=true in your shell before The Fuck):
All thefuck commands error with the following
/home/linuxbrew/.linuxbrew/Cellar/thefuck/3.30_1/libexec/bin/python3.8: error while loading shared libraries: libpython3.8.so.1.0: cannot open shared object file: No such file or directory

If the bug only appears with a specific application, the output of that application and its version:
N/A
Anything else you think is relevant:
Reinstalled both<EMAIL_ADDRESS>and thefuck with brew reinstall X with no luck.

Please follow Homebrew/linuxbrew-core#20174.


[2.21.91 wpewebkit] build failure with VIDEO disabled

I was trying the branch with upgraded packages from this PR: https://github.com/Igalia/meta-webkit/pull/27
My build is failing due to no video in PACKAGECONFIG
Error message:
Source/WebCore/page/Page.cpp:1521:27: error: 'class WebCore::ChromeClient' has no member named 'setUpPlaybackControlsManager'

Error reason:
This member is not compiled when the VIDEO is not enabled (347 line in ./Source/WebCore/page/ChromeClient.h) :
#if ENABLE(VIDEO)
    virtual void enterVideoFullscreenForVideoElement(HTMLVideoElement&, HTMLMediaElementEnums::VideoFullscreenMode) { }
    virtual void setUpPlaybackControlsManager(HTMLMediaElement&) { }
    virtual void clearPlaybackControlsManager() { }
#endif

However, it is used unconditionally in the Page.cpp file.
By the way: is there any repo with the code of the WPEwebkit? Where do the releases of the https://wpewebkit.org/ come from?

Yeah @psaavedra recently contributed !VIDEO build fixes indeed. Feel free to close the issue if the new recipe builds for you!

The build with VIDEO disabled does not fail anymore


API documentation: group properties by meaning

Feature request type
Other
Component name
At least MudTable, but can be also for other components.
Is your feature request related to a problem?
List of MudTable<T> properties is long and hard to comprehend.
Describe the solution you'd like
It would be good to have an option to group properties by meaning, eg. put MultiSelection, SelectedItem, and SelectedItems properties in a group named Selection.
Have you seen this feature anywhere else?
Web Forms; Quasar library
Describe alternatives you've considered
No response
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

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

I have categorized properties for all components: http://consensualknowledge.net/temp/MudBlazor_grouping/. The categorization proposed by me is logical and consistent in my opinion, so you don't need to check everything. We can always recategorize few properties later.
Can I add [Category("some category")] to all properties of all components in the MudBlazor source code? There is more than thousand properties in total - it will take me about 5 hours, so I want to be sure I can do it.

Sorry for taking so long to respond, but we finally decided that we would love it if you do a PR!
We would prefer it if the constants are defined in a file and are referenced like this:
[Category(CategoryTypes.Table.MultiSelect)]
What's your take on this?

Do you mean the enum type defined below or something else?
using System;

namespace MudBlazor
{
    /// <summary>
    /// Specifies the name of the category in which to group the property of a MudBlazor component when displayed in the API documentation.
    /// </summary>
    /// <remarks>
    /// Use this attribute together with the <see cref="Microsoft.AspNetCore.Components.ParameterAttribute"/>. <br/>
    /// This attribute is similar to <see cref="System.ComponentModel.CategoryAttribute"/>.
    /// </remarks>
    [AttributeUsage(AttributeTargets.Property, AllowMultiple = false, Inherited = true)]
    public class CategoryAttribute : Attribute
    {
        protected CategoryTypes category;

        public CategoryAttribute(CategoryTypes category)
        {
            this.category = category;
        }
    }

    public enum CategoryTypes
    {
        Data, Validation,
        ValidatedData, ValidationResult,
        Header, Footer, Rows,

        Behavior,

        Filtering,
        Grouping,
        Expanding,
        Sorting,
        Pagination,

        Selecting,
        Editing,
        ClickAction,
        Appearance,

        PopupBehavior, PopupAppearance,
        ListBehavior, ListAppearance,
        PickerBehavior, PickerAppearance,
        Dot,

        Other,
        Common
    }
}

Or this:
using System;

namespace MudBlazor
{

    [AttributeUsage(AttributeTargets.Property, AllowMultiple = false, Inherited = true)]
    public class CategoryAttribute : Attribute {
        protected int category;

        public CategoryAttribute(int category) {
            this.category = category;
        }
    }

    public static class CategoryTypes {

        // used in MudButton, MudFab, MudIconButton, MudMenu, and MudToggleIconButton
        public static class Button
        {
            public const int Behavior = 1;
            public const int ClickAction = 2;
            public const int Appearance = 3;
        }

        // used in MudTextField/MudNumericField/MudSelect/MudAutocomplete, MudCheckBox/MudSwitch, and pickers
        public static class FormComponent
        {
            public const int Data = 1;
            public const int Validation = 2;
            public const int Behavior = 3;
            public const int Appearance = 4;
            public const int ListBehavior = 5;
            public const int ListAppearance = 6;
            public const int PickerBehavior = 7;
            public const int PickerAppearance = 8;
        }

        public static class Alert           { public const int Behavior = 1; public const int Appearance = 2; }
        public static class AppBar          { public const int Behavior = 1; public const int Appearance = 2; }
        public static class Avatar          { public const int Behavior = 1; public const int Appearance = 2; }
        public static class AvatarGroup     { public const int Behavior = 1; public const int Appearance = 2; }
        public static class Badge           { public const int Behavior = 1; public const int Appearance = 2; }
        public static class Breadcrumbs     { public const int Behavior = 1; public const int Appearance = 2; }
        public static class ButtonGroup     { public const int Behavior = 1; public const int Appearance = 2; }

        // used in MudCard, MudCardHeader, MudCardMedia, MudCardContent, and MudCardActions
        public static class Card            { public const int Behavior = 1; public const int Appearance = 2; }

        // used in MudCarousel, and MudCarouselItem
        public static class Carousel
        {
            public const int Data = 1;
            public const int Behavior = 2;
            public const int Appearance = 3;
        }

        // used in all charts
        public static class Chart           { public const int Behavior = 1; public const int Appearance = 2; }

        public static class Chip
        {
            public const int Behavior = 1;
            public const int ClickAction = 2;
            public const int Appearance = 3;
        }

        public static class ChipSet         { public const int Behavior = 1; public const int Appearance = 2; }
        public static class Container       { public const int Behavior = 1; public const int Appearance = 2; }

        // used in MudDialog, MudDialogInstance, and MudDialogProvider
        public static class Dialog          { public const int Behavior = 1; public const int Appearance = 2; }

        public static class Divider         { public const int Behavior = 1; public const int Appearance = 2; }

        // used in MudDrawerContainer, MudDrawer, and MudDrawerHeader
        public static class Drawer          { public const int Behavior = 1; public const int Appearance = 2; }

        // used in MudExpansionPanels, and MudExpansionPanel
        public static class ExpansionPanel  { public const int Behavior = 1; public const int Appearance = 2; }

        public static class Field
        {
            public const int Data = 1;
            public const int Validation = 2;
            public const int Behavior = 3;
            public const int Appearance = 4;
        }

        public static class FileUploader
        {
            public const int Behavior = 1;
            public const int ClickAction = 2;
            public const int Appearance = 3;
        }

        public static class FocusTrap { public const int Behavior = 1; public const int Appearance = 2; }

        public static class Form {
            public const int ValidatedData = 1;
            public const int ValidatedResult = 2;
            public const int Other = 3;
        }

        public static class Grid    { public const int Behavior = 1; public const int Appearance = 2; }
        public static class Item    { public const int Behavior = 1; public const int Appearance = 2; }
        public static class Hidden  { public const int Behavior = 1; public const int Appearance = 2; }
        public static class Icon    { public const int Behavior = 1; public const int Appearance = 2; }
        public static class Link    { public const int Behavior = 1; public const int Appearance = 2; }

        // used in MudList,  MudListItem, and MudListSubheader
        public static class List {
            public const int Behavior = 1;
            public const int Expanding = 2;
            public const int Selecting = 3;
            public const int ClickAction = 4;
            public const int Appearance = 5;
        }

        // used in MudMenu and MudMenuItem
        public static class Menu
        {
            public const int Behavior = 1;
            public const int ClickAction = 2;
            public const int Appearance = 3;
            public const int PopupBehavior = 4;
            public const int PopupAppearance = 5;
        }

        public static class MessageBox { public const int Behavior = 1; public const int Appearance = 2; }

        // used in MudNavMenu, MudNavGroup, MudNavLink
        public static class NavMenu {
            public const int Behavior = 1;
            public const int ClickAction = 2;
            public const int Appearance = 3;
        }

        public static class Overlay
        {
            public const int Behavior = 1;
            public const int ClickAction = 2;
        }

        public static class Pagination       { public const int Behavior = 1; public const int Appearance = 2; }
        public static class Paper            { public const int Behavior = 1; public const int Appearance = 2; }
        public static class Popover          { public const int Behavior = 1; public const int Appearance = 2; }
        public static class ProgressLinear   { public const int Behavior = 1; public const int Appearance = 2; }
        public static class ProgressCircular { public const int Behavior = 1; public const int Appearance = 2; }
        public static class Radio            { public const int Behavior = 1; public const int Appearance = 2; }

        public static class Rating
        {
            public const int Data = 1;
            public const int Behavior = 2;
            public const int Appearance = 3;
        }

        public static class ScrollToTop      { public const int Behavior = 1; public const int Appearance = 2; }
        public static class Skeleton         { public const int Behavior = 1; public const int Appearance = 2; }

        public static class Slider
        {
            public const int Data = 1;
            public const int Validation = 2;
            public const int Behavior = 3;
            public const int Appearance = 4;
        }

        public static class SwipeArea        { public const int Behavior = 1; public const int Appearance = 2; }

        public static class Table
        {
            public const int Data = 1;
            public const int Header = 2;
            public const int Footer = 3;
            public const int Rows = 4;
            public const int Behavior = 5;
            public const int Filtering = 6;
            public const int Grouping = 7;
            public const int Sorting = 8;
            public const int Pagination = 9;
            public const int Selecting = 10;
            public const int Editing = 11;
            public const int Appearance = 12;
        }

        public static class SimpleTable { public const int Behavior = 1; public const int Appearance = 2; }

        // used in MudTabs, MudDynamicTabs, and MudTabPanel
        public static class Tabs
        {
            public const int Behavior = 1;
            public const int Appearance = 2;
        }

        // used in MudTimeline and MudTimelineItem
        public static class Timeline
        {
            public const int Behavior = 1;
            public const int Appearance = 2;
            public const int Dot = 3;
        }

        public static class ToolBar { public const int Behavior = 1; public const int Appearance = 2; }
        public static class Tooltip { public const int Behavior = 1; public const int Appearance = 2; }

        // used in MudTreeView, MudTreeViewItem, and MudTreeViewItemToggleButton
        public static class TreeView
        {
            public const int Data = 1;
            public const int Behavior = 2;
            public const int Expanding = 3;
            public const int Selecting = 4;
            public const int ClickAction = 5;
            public const int Appearance = 6;
        }

        public static class Text { public const int Behavior = 1; public const int Appearance = 2; }
    }
}

Or this:
using System;

namespace MudBlazor
{

    [AttributeUsage(AttributeTargets.Property, AllowMultiple = false, Inherited = true)]
    public class CategoryAttribute : Attribute {
        protected int category;

        public CategoryAttribute(int category) {
            this.category = category;
        }
    }

    // Categories in the API documentation are displayed in the same order as below
    public static class CategoryTypes {

        // used in MudButton, MudFab, MudIconButton, MudMenu, MudToggleIconButton, and FileUploader
        public static class Button
        {
            public const int Behavior = 1;
            public const int ClickAction = 2;
            public const int Appearance = 3;
        }

        // used in MudTextField/MudNumericField/MudSelect/MudAutocomplete, MudCheckBox/MudSwitch, and pickers
        public static class FormComponent
        {
            public const int Data = 1;
            public const int Validation = 2;
            public const int Behavior = 3;
            public const int Appearance = 4;
            public const int ListBehavior = 5;
            public const int ListAppearance = 6;
            public const int PickerBehavior = 7;
            public const int PickerAppearance = 8;
        }

        public static class Alert           { public const int Behavior = 1; public const int Appearance = 2; }
        public static class AppBar          { public const int Behavior = 1; public const int Appearance = 2; }
        public static class Avatar          { public const int Behavior = 1; public const int Appearance = 2; }
        public static class AvatarGroup     { public const int Behavior = 1; public const int Appearance = 2; }
        public static class Badge           { public const int Behavior = 1; public const int Appearance = 2; }
        public static class Breadcrumbs     { public const int Behavior = 1; public const int Appearance = 2; }
        public static class ButtonGroup     { public const int Behavior = 1; public const int Appearance = 2; }

        // used in MudCard, MudCardHeader, MudCardMedia, MudCardContent, and MudCardActions
        public static class Card            { public const int Behavior = 1; public const int Appearance = 2; }

        // used in MudCarousel, and MudCarouselItem
        public static class Carousel
        {
            public const int Data = 1;
            public const int Behavior = 2;
            public const int Appearance = 3;
        }

        // used in all charts
        public static class Chart           { public const int Behavior = 1; public const int Appearance = 2; }

        public static class Chip
        {
            public const int Behavior = 1;
            public const int ClickAction = 2;
            public const int Appearance = 3;
        }

        public static class ChipSet         { public const int Behavior = 1; public const int Appearance = 2; }
        public static class Container       { public const int Behavior = 1; public const int Appearance = 2; }

        // used in MudDialog, MudDialogInstance, and MudDialogProvider
        public static class Dialog          { public const int Behavior = 1; public const int Appearance = 2; }

        public static class Divider         { public const int Behavior = 1; public const int Appearance = 2; }

        // used in MudDrawerContainer, MudDrawer, and MudDrawerHeader
        public static class Drawer          { public const int Behavior = 1; public const int Appearance = 2; }

        // used in MudExpansionPanels, and MudExpansionPanel
        public static class ExpansionPanel  { public const int Behavior = 1; public const int Appearance = 2; }

        public static class Field
        {
            public const int Data = 1;
            public const int Validation = 2;
            public const int Behavior = 3;
            public const int Appearance = 4;
        }

        public static class FocusTrap { public const int Behavior = 1; public const int Appearance = 2; }

        public static class Form {
            public const int ValidatedData = 1;
            public const int ValidatedResult = 2;
            public const int Other = 3;
        }

        public static class Grid    { public const int Behavior = 1; public const int Appearance = 2; }
        public static class Item    { public const int Behavior = 1; public const int Appearance = 2; }
        public static class Hidden  { public const int Behavior = 1; public const int Appearance = 2; }
        public static class Icon    { public const int Behavior = 1; public const int Appearance = 2; }
        public static class Link    { public const int Behavior = 1; public const int Appearance = 2; }

        // used in MudList,  MudListItem, and MudListSubheader
        public static class List {
            public const int Behavior = 1;
            public const int Expanding = 2;
            public const int Selecting = 3;
            public const int ClickAction = 4;
            public const int Appearance = 5;
        }

        // used in MudMenu and MudMenuItem
        public static class Menu
        {
            public const int Behavior = 1;
            public const int ClickAction = 2;
            public const int Appearance = 3;
            public const int PopupBehavior = 4;
            public const int PopupAppearance = 5;
        }

        public static class MessageBox { public const int Behavior = 1; public const int Appearance = 2; }

        // used in MudNavMenu, MudNavGroup, MudNavLink
        public static class NavMenu {
            public const int Behavior = 1;
            public const int ClickAction = 2;
            public const int Appearance = 3;
        }

        public static class Overlay
        {
            public const int Behavior = 1;
            public const int ClickAction = 2;
        }

        public static class Pagination       { public const int Behavior = 1; public const int Appearance = 2; }
        public static class Paper            { public const int Behavior = 1; public const int Appearance = 2; }
        public static class Popover          { public const int Behavior = 1; public const int Appearance = 2; }
        public static class ProgressLinear   { public const int Behavior = 1; public const int Appearance = 2; }
        public static class ProgressCircular { public const int Behavior = 1; public const int Appearance = 2; }
        public static class Radio            { public const int Behavior = 1; public const int Appearance = 2; }

        public static class Rating
        {
            public const int Data = 1;
            public const int Behavior = 2;
            public const int Appearance = 3;
        }

        public static class ScrollToTop      { public const int Behavior = 1; public const int Appearance = 2; }
        public static class Skeleton         { public const int Behavior = 1; public const int Appearance = 2; }

        public static class Slider
        {
            public const int Data = 1;
            public const int Validation = 2;
            public const int Behavior = 3;
            public const int Appearance = 4;
        }

        public static class SwipeArea        { public const int Behavior = 1; public const int Appearance = 2; }

        public static class Table
        {
            public const int Data = 1;
            public const int Header = 2;
            public const int Footer = 3;
            public const int Rows = 4;
            public const int Behavior = 5;
            public const int Filtering = 6;
            public const int Grouping = 7;
            public const int Sorting = 8;
            public const int Pagination = 9;
            public const int Selecting = 10;
            public const int Editing = 11;
            public const int Appearance = 12;
        }

        public static class SimpleTable { public const int Behavior = 1; public const int Appearance = 2; }

        // used in MudTabs, MudDynamicTabs, and MudTabPanel
        public static class Tabs        { public const int Behavior = 1; public const int Appearance = 2; }

        // used in MudTimeline and MudTimelineItem
        public static class Timeline
        {
            public const int Behavior = 1;
            public const int Appearance = 2;
            public const int Dot = 3;
        }

        public static class ToolBar { public const int Behavior = 1; public const int Appearance = 2; }
        public static class Tooltip { public const int Behavior = 1; public const int Appearance = 2; }

        // used in MudTreeView, MudTreeViewItem, and MudTreeViewItemToggleButton
        public static class TreeView
        {
            public const int Data = 1;
            public const int Behavior = 2;
            public const int Expanding = 3;
            public const int Selecting = 4;
            public const int ClickAction = 5;
            public const int Appearance = 6;
        }

        public static class Text { public const int Behavior = 1; public const int Appearance = 2; }
    }
}

Yes like this. I don't know if integers will work. Otherwise just use strings


Swift 4 Update

This PR is part of https://github.com/SlackKit/SlackKit/issues/117 and should be merged once all other repos are migrated.

Updates Package.swift to Package Manager Version 4 format
Recreates Xcode project with swift 4.0 toolchain
Fixes compile warnings in SKServer target
[ ] Add correct build schemes to xcodeproj?
[ ] Version bump
[ ] Update README.md
[ ] Update Swifter dependency

Done here: https://github.com/SlackKit/SKServer/releases/tag/4.1.0 - thanks!


SuperSlicer

Project description
SuperSlicer is a fork of PrusaSlicer, a slicer for 3d-printing, with advanced features.
Metadata

homepage URL: https://github.com/supermerill/SuperSlicer
source URL: https://github.com/supermerill/SuperSlicer
license: AGPL-3.0
platforms: linux, darwin

This is already packaged: https://search.nixos.org/packages?channel=22.05&show=super-slicer&from=0&size=50&sort=relevance&type=packages&query=super-slicer

Sorry, didn't see that.
Thanks


Queue basic operation in C

added my name on contributor section on README.md. please check it. thank you by the way! @atyant-yadav


The Illuminate\Database\Eloquent\Builder namespace for custom Unique Rule in validations is wrong.

Laravel Version: 10.2.0
PHP Version: 8.1.0
Database Driver & Version: SQL Server 2019 enterprise

Description:
I try to use the Unique Rule in validations:
use Illuminate\Validation\Rule;
use Illuminate\Validation\ValidationException;
use Illuminate\Database\Eloquent\Builder;

 public function update(Request $request, $id)
    {
        try {
                $rules = [
                    'email' => [
                        'required',
                         Rule::unique('email')
                            ->where(fn (Builder $query) => $query->where('customer_id, '<>', $id))
                     ]
                  ];

                $request->validate($rules);
            } catch (ValidationException $exception) {
                Log::channel('single')->info("validation_error", $exception->getMessage());
        }
    }

But i this exception is throw:
Argument #1 ($query) must be of type Illuminate\\Database\\Eloquent\\Builder, Illuminate\\Database\\Query\\Builder given, called in /var/www/html/vendor/laravel/framework/src/Illuminate/Validation/DatabasePresenceVerifier.php on line 85
But if you change to this:
use Illuminate\Validation\Rule;
use Illuminate\Validation\ValidationException;

 public function update(Request $request, $id)
    {
        try {
                $rules = [
                    'email' => [
                        'required',
                         Rule::unique('email')
                            ->where(fn (\Illuminate\Database\Query\Builder $query) => $query->where('customer_id, '<>', $id))
                     ]
                  ];

                $request->validate($rules);
            } catch (ValidationException $exception) {
                Log::channel('single')->info("validation_error", $exception->getMessage());
        }
    }

It's work!. The Illuminate\Database\Query\Builder namespace was shown like a wrong, but it's actually the correct one!
Steps To Reproduce:

Create array for rules;
Read the documentation about custom Unique Rules;
Write a custom unique rule with Rule::unique()->where() method;

I'm not entirely sure what the issue here is? You indeed need to reference the correct namespace.

Yes, need. But the namespace was shown like a correct... it's the wrong!

@matheusbrdev yes your right  "Illuminate\Database\Query\Builder" works fine.


Deterministic dataset loading

When calling:
import nlp
dataset = nlp.load_dataset("trivia_qa", split="validation[:1%]")

the resulting dataset is not deterministic over different google colabs.
After talking to @thomwolf, I suspect the reason to be the use of glob.glob in line:
https://github.com/huggingface/nlp/blob/2e0a8639a79b1abc848cff5c669094d40bba0f63/datasets/trivia_qa/trivia_qa.py#L180
which seems to return an ordering of files that depends on the filesystem:
https://stackoverflow.com/questions/6773584/how-is-pythons-glob-glob-ordered
I think we should go through all the dataset scripts and make sure to have deterministic behavior.
A simple solution for glob.glob() would be to just replace it with sorted(glob.glob()) to have everything sorted by name.
What do you think @lhoestq?

Yes good point !

I think using sorted(glob.glob()) would actually solve this problem. Can you think of other reasons why dataset loading might not be deterministic? @mariamabarham @yjernite @lhoestq @thomwolf .
I can do a sweep through the dataset scripts and fix the glob.glob() if you guys are ok with it

I'm pretty sure it would solve the problem too.
The only other dataset that is not deterministic right now is blog_authorship_corpus (see #215) but this is a problem related to string encodings.

I think we should do the same also for os.list_dir


[Bug] Swagger doc, response decorator, arguments possibly misaligned.

Describe the bug
It appears that when the doc.response decorator is used to document the possible responses, basically for the swagger documentation,
A clear and concise description of what the bug is. It there is error log, please provide it.
Screenshots
No screenshots are included as it will not actually help and is thus not necessary.
To Reproduce
Here follows a short script to quickly reproduce the issue:
A basic setup is all that is necessary, adding in a doc.response decorator with a description field following the status code will result in a IndexError.
`
from sanic import Sanic
from sanic.response import json
from sanic_openapi import swagger_blueprint, doc
app = Sanic()
app.blueprint(swagger_blueprint)
@app.route("/")
@doc.response(404, description="This is the description of the response code")
async def test(request):
return json({"hello": "world"})
if name == "main":
app.run(host="<IP_ADDRESS>", port=8000)    #  locathost
`
I am not completely sure what the intention was in the code highlighted by the below error, but is seems that the RouteField class is expecting an additional arg, namely the variable "field" - when looking into the sanic_openapi.doc code. If that variable was not intentionally assigned as such, it would probably make sense to assign a default value to it as well, and not pass in the args[1] to the RouteField class.
Traceback (most recent call last):   File "test_api.py", line 10, in <module>     @doc.response(404, description="This is the description of the response code")   File "/path/to/project/venv/lib/python3.7/site-packages/sanic_openapi/doc.py", line 324, in inner     routefield = RouteField(args[1], description=description) IndexError: tuple index out of range
Note: I just anonymized my file path.
Expected behavior
Expected a description field to have been added to the swagger.json under the response documentation. This obviously does not happen.
Current Workaround
This is just a code snippet, note the additional arg passed to the doc.response decorator.
`
from sanic import Sanic
from sanic.response import json
from sanic_openapi import swagger_blueprint, doc
app = Sanic()
app.blueprint(swagger_blueprint)
@app.route("/")
@doc.response(404, "", description="This is the description of the response code")
async def test(request):
return json({"hello": "world"})
if name == "main":
app.run(host="<IP_ADDRESS>", port=8000)   #  locathost
`
Environment

OS: macOS Catalina, 10.15.1
Browser : Chrome
Version: 0.6.0 (2019-08-02)
Virtual Environment with Python 3.7

Additional context
I found this slight issue setting up some "client" facing swagger documentation. Hilarious that dev's need documentation right? Either way this is by no means a large issue, and is easily circumvented by adding a dummy arg as a placeholder as shown above, but hey, every bit helps :).
This can probably be easily fixed. I will also probably submit a pull request for this issue.

nevermind - read the docs.


Makers of industry-grade MQTT-enabled sensor devices?

Hello,
this is a bit OT, sorry.
Can someone point to companies that offer boxed and ready-to-run sensor devices (specifically measuring lightness and motion)?
Thanks!
Karlo

Hi,
already with MQTT support or in general?
One project I use is this: https://github.com/arendst/Sonoff-Tasmota
Best regards
Christian

Thanks interesting!
Did you ever see a lightness sensor based on that hardware platform? I want to detect whether ceiling lights are switched on/off (mostly indoor).

Usually I use ESP8266 (NodeMcu dev kit) with several sensors. Or do you need some without soldering etc.?

Yes, something boxed and ready to use would be great. I' not an electronic guy :)

Sorry but I don't know much ready to use sensors.

Thanks!


Small font size in navbar

In dark theme font size of the navbar is too small and barely visible

Please assign me this issue under gssoc21

@garvitgupta13 Already an issue #284

@garvitgupta13 Already an issue #284

The PR attached with issue is concerned over changing fontsize of navbar elements in light theme only
I have raised issue specific to dark theme


Configure an NFS client for Azure NetApp Files

Page title is misleading.  Should be updated to reflect kerberos related setup instruction.

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

ID: 08a2c99a-9745-82bf-9821-840e2cee3fc7
Version Independent ID: d694e40e-27b7-957e-b990-1ff931abfeed
Content: Configure an NFS client for Azure NetApp Files
Content Source: articles/azure-netapp-files/configure-nfs-clients.md
Service: azure-netapp-files
GitHub Login: @b-juche
Microsoft Alias: b-juche

@ MrRitt  -- Thanks for the comment.
This article (Configure an NFS client for Azure NetApp Files) is indeed part of the kerberos configuration (as referenced in Configure NFSv4.1 Kerberos encryption for Azure NetApp Files).  However, its steps are also used for configuring dual protocol volumes (as referenced in Create a dual-protocol (NFSv3 and SMB) volume for Azure NetApp Files).  That's why we keep a generic title for this article.  Thanks.

@b-juche  - Thank you for providing your insights.
@@MrRitt - I hope @@b-juche has answered your question. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Update sv.json

Added translation for vacation mode, corrected spelling mistakes and rewrote some translations.

Thanks a lot for providing this 👍
Hope you can also check back every once in a while, if things change in Alarmo some translations may be affected.


Adding support for faer

This PR aims to add support for faer into diffsol.
To do this I created a Scale structure to be used as an interface between nalgebra and faer when working with scalar operations.
I replaced all the scalar operations to use Scale and implemented all the traits needed to have it to work with nalgebra.
All tests are passing.
The faer traits are still under development but the initial integration is already in place. All the faer integration code is commented to guarantee that the package compiles. My plan is to put the respective implementations behind their specific faer and nalgebra features.

I think I made al the changes requested.

I did rebase the branch to include the current changes on main


Fix blank side bar

closes #1195
Description

use RED.utils to get correctly resolved icon

NOTE: some icons from contrib nodes do not use transparency and cannot be faithfully represented. If we want to support that then the only reliable way would be to generate the tree entries like nodes (as they appear in the left hand palette.)
Demo

Related Issue(s)
#1195
Checklist

[x] I have read the contribution guidelines
[ ] Suitable unit/system level tests have been added and they pass
[ ] Documentation has been updated

[ ] Upgrade instructions
[ ] Configuration details
[ ] Concepts

[ ] Changes flowforge.yml?

[ ] Issue/PR raised on FlowFuse/helm to update ConfigMap Template
[ ] Issue/PR raised on FlowFuse/CloudProject to update values for Staging/Production

Labels

[ ] Includes a DB migration? -> add the area:migration label

Hi @Steve-Mcl,
Thanks for the PR!  Really appreciated!!
What a bummer that you had to spend your saturday on this one 😞
It looks like your implementation support a wide range of icon types.
The ´RED.utils.getNodeIcon´ was the one I was looking for last week.  The missing link...

some icons from contrib nodes do not use transparency and cannot be faithfully represented

Is that a real problem?  Currently there are only a few ui nodes for D2.  The developers or the users will quickly see that something is wrong with the icon and fix it.
Or am I mistaken?   Because from your screenshot it looks like you have also non-ui nodes in your sidebar tree?

Because from your screenshot it looks like you have also non-ui nodes in your sidebar tree?

They're subflows :)


Need additional detail regarding few-shot learning experiment

Can you explain the few-shot setting whose result are reported in
Table 7. Transfer learning from ImageNet to few-shot CIFAR-10
and CIFAR-100 with 1000 training labels with 3 networks: ResNet50 (R-50), ConvNext-B (C-B) and Swin-T (S-T)
How many shots in the training set as well as in the test set or query set.

CIFAR-100 has 100 classes, so with 1000 training labels we have 10 shots.
We used the code from our previous paper to run these fine-tuning experiments (https://github.com/facebookresearch/ppuda/blob/main/experiments/sgd/train_net.py), so we pass --n_shots 10 for CIFAR-100 experiments. The hyperparameters are based on our another paper Pretraining a Neural Network before Knowing Its Architecture (https://arxiv.org/abs/2207.10049), see Table 2 there. For CIFAR-100 the best hyperparameters are generally similar. We used --beta 3e-5 to add some noise to predicted parameters before their fine-tuning, but we didn't use orthogonal re-initialization (i.e. we use --init rand).
Let me know if there are further questions.


Make a script to run light curve functions at scale

Update sample_lc.py to, e.g., use sample_table. (This is a script version of the parallel section of the notebook, meant to be called from command line, but has not been kept up to date.) Alternately, consider making the modules directly callable from the command line and write a .sh script to execute them. This should speed up bulk runs because ZTF could use multiple workers.

Im renaming this issue to be more clear about what I think the goal of this issue is, but if I have misappropriated some other issue, please clarify.  I don't think we want to update an old script, I think we want a new functional script that runs the light curve notebook at scale.  For the time being, this should include ZTF, WISE, HEASARC, Icecube, and Gaia.  It should in the future be able to also run the MAST archive searches.


fix(search): Fix the unintentional rollback(#2028) of dataset index to search by field paths.

Fix the unintentional rollback(#2028) of dataset index to search by field paths. Fixes #2019
Context: Refer #2019.  Dataset Index mappings defined in #2001 got overriden later by #2028.
Checklist

[x] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[x] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable)

LGTM assuming checks pass

LGTM, thanks for the quick fix!


A let property cannot be reassigned after all fields have been initialized

:struct A
  :let field U8: 5

  :new (@field)

I'd assume that it is possible assign a value to a let field in a constructor and if not, the :let declarators default value is taken.

I agree this would be nice to have, but it will make the completeness analysis significantly more complicated, I think.

I see. So we should better raise an error at compile time in these situation. IIRC, there is already an open issue for that.

Sorry, mixing things up. Well, :let default values as of now are more or less constant as you cannot change them.

Right, I agree it would be more useful if default values for :let could be overridden by explicit values in a constructor, and right now, that is not possible.


add covid3dmaps

I built this site trying to provide an alternative for visualizing and interacting with latest COVID stats.

Provides latest global stats in percentages.
Countries statistics by geographic division (province) in form of bars representing number of cases.
Visually more engaging.

I really love the project!


Error

PaperSpigot build 137: https://pastebin.com/jiRNCpfw

That doesn't have anything to do with MyDog, but is from a plugin called Earrape.


chore: move lint_style executable to the scripts directory

Otherwise, importing Mathlib.Tactic makes defining own executables impossible, as the main function in Linter.TextBased would collide with any other main function. Move the code for the lint_style executable to scripts (which arguably might be a better place anyway); we leave the text-based linters in Tactic/Linter.

maintainer merge
LGTM, but let's get a second pair of eyes.

bors d+
Please fix the exit code issue, but otherwise LGTM!

Thanks for the review! Per my comment above, let me
bors r+


Metadata with Int Value isn't going thru

Hello.
When I send metadata with an integer value, instead of a string, isn't going thru mati.

Hello @dfmarulanda yes, it can be, let me check, 1) do you want to use Int for key or for value? 2) it is for iOS SDK right?

Int value. In Android works well

Hello @dfmarulanda got it, yes in iOS we have [String:String?] let me prepare an update to change into [String:Any?], i think we can provide update till this Friday

@dfmarulanda Hello, we have just published 3.3.3 please try it

If you will have new questions/issues, please open a new ticket


[CS2103T-F12-3] Track-O

Track-O provides a centralised digital platform for freelance tutors to manage the information of tutees. It helps to find and store relevant information easily, reducing cumbersome and inefficient physical methods of information management.

Codecov Report

Merging #52 (3e17ef2) into master (ba53b8c) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #52   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

Continue to review full report at Codecov.

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


Fixed Integer casting

Fixed the problem of integer casting, particularly casting unsigned to signed numbers, fixing #7184

Sorry I havent used git in a while and have managed to severly screw this up

@wizard7377 that CI failure looks significant, are you able to investigate?
     Summary [  98.658s] 962 tests run: 961 passed, 1 failed, 6 skipped
        FAIL [   0.068s] test_gen::test_gen gen_num::cast_signed_unsigned

Oh dear me
Yeah the test I added should probably be passing shouldn't it


Exporting without metadata

Since I started using Aves, I have been increasingly relying on metadata to organize my photo collection (with titles/captions, tags, ...).
However when I share pictures with other people I'd usually like to remove most metadata, either for privacy (e.g. in the case of GPS data) or simply because my "custom" metadata such as tags is only relevant in the context lf my own photo collection.
I think it would be useful to have an option to export pictures without metadata. I'm aware of the "convert" option, which lets the user choose whether to include metadata in the exported file, but I think it would be nice to have that option also for exporting the original image (i.e. without recompression or change of format).
Additionally I would also find it very useful if such a new "export without metadata" menu offered a choice of removing some metadata while keeping some other. For example in my personal workflow I'd often like to share a picture with most EXIF metadata, including in particular camera-related information (camera type, shutter speed, ISO, ...), GPS coordinates and any embedded color profile, but without stuff relating to my photo collection, such as tags, captions, star ratings, "face tags" (i.e. the names of people in the picture, which is not a feature of Aves but might be added to the metadata using other apps).
However, since as far as I know there is no unique standard on how to store e.g. tags in JPEG metadata, I don't know if there is a sensible way to implement this.
My current workaround relies on the existing "remove metadata" option: I create a copy of all of the pictures I want to export, I remove their metadata, I share them and then I delete the copies without metadata. However this workflow is rather cumbersome, and it is also relatively easy to mix things up and accidentally share the copy with metadata or keep the one without. Also there is no way to selectively delete unwanted metadata while keeping the rest.

Agreed. This is actually the kind of things i intend to do as part of this:

#10

Refining what kind of metadata to keep/remove is possible, but i'd like to keep a balance between being flexible and newbie friendly.


No such file or directory - /platform-tools/adb (Errno::ENOENT)

Why do I have the following error every time

but
➜  ~ source ~/.bash_profile
➜  ~ echo @ANDROID_HOME
@ANDROID_HOME
➜  ~ echo $ANDROID_HOME
/Users/***/Library/Android/sdk
?

What was the problem?

@cesarferreira I have also encountered this problem:
C:>dryrun -c
Searching for devices...
D:/Ruby23-x64/lib/ruby/2.3.0/open3.rb:199:in `spawn': No such file or directory

D:\path\to\my\sdk/platform-tools/adb.exe  devices  (Errno::ENOENT)
from D:/Ruby23-x64/lib/ruby/2.3.0/open3.rb:199:in popen_run'       from D:/Ruby23-x64/lib/ruby/2.3.0/open3.rb:95:in popen3'
from D:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/dryrun-0.9.0/lib/dryrun/dryr
un_utils.rb:54:in run'       from D:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/dryrun-0.9.0/lib/dryrun/dryr un_utils.rb:46:in run_adb'
from D:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/dryrun-0.9.0/lib/dryrun.rb:1
08:in pick_device'       from D:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/dryrun-0.9.0/lib/dryrun.rb:1 68:in call'
from D:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/dryrun-0.9.0/bin/dryrun:6:in
<top (required)>'       from D:/Ruby23-x64/bin/dryrun:22:in load'
from D:/Ruby23-x64/bin/dryrun:22:in `'

However, I have ANDROID_HOME set in my environment variables and when I type adb, I can see it's commands.

Can you create a separate issue @SuperMasterBlasterLaser please?

@ftc300 I have the same problem, what is the cause and what is the solution?

What is you ANDROID_HOME path @thushcapone ?

@luispereira I forgot to set it. The issue was related to it missing. Thank you


Add avcode.h to decoder example

Many avcodec struct and function prototypes are in avcodec.h which is not included in the decoder_user example, which causes compilation issue.

It doesn't need,because the avformat.h will include avcodec.h


Subprocesses cannot publish to topics

While the origin of the issue is unclear, the reason why publishing is not possible is because the subscriber is not added to the publisher's list, and thus no messages are received. The self.connections variable in topics.py of rospy is not updated in the subprocess.

[ ] check publisher code flow in rospy
[ ] check subscriber code flow in rospy
[ ] look at services, apparently they work

According to this comment, topics and services can be initialised before the node - does this affect anything?

Information about added publishers or subscribers is sent to the master node here.

subscriber_listener here is None when initialising the chatter topic in subprocess.

Might be able to use the subscriber_listener to trigger addition of the subscription topic to the connections list of the publisher?

tcpros_base is where checks are made to determine subscribers and publishers (?). This is run in a separate thread, with the run function, which runs until the node is shutdown.

tcpros_pubsub::topic_connection_handler is where connections for topics are created, both subscribers and publishers.

topics::TopicManager::acquire_impl creates the subscriber/publisher.
Line 1149 get_registration_listeners().notify_added(resolved_name, ps.type, reg_type)  seems to be important, appears to call reg_added function of registration::RegManager, which informs the master about the new topic or subscriber. publisher_update is then called, which modifies the updates list.

@asmodehn looks like there's nothing we can do about this. I suppose we can close this.

@heuristicus yes lets keep fixing the current design then.


Optional animations

This pull request adds an attribute animate that needs to be set to "true" in order for the animations to be activated.
This can be used as a work-around for issue #161.

I was thinking about something like this, but left that out, because I couldn't see a need to dynamically dis/enable animations. I suppose an application will either animate or not. To disable animation, just declare empty animate-{row,column} classes. But I guess there could be a use case for that.

I suppose it might be worth trying to turn the animation off on drag start and then turn it back on...

Awesome, this looks great!  Thanks for the tests.
I do think that it'd be better to have animations on by default instead of off - that way you can still disable and it's not a major change.

It occurred to me, that the purpose of the animations is really to animate the collapsing/toggling. So I would suggest that we add the classes before toggling a container and remove it afterwards. What do you think.

Hm, that'd be interesting to see, mind putting together that in a Plunkr?

@SomeKittens I'd like to do that later this week, if time permits. But will wait for @widmoser 's reaction since s/he seems to be very active at the moment.

@petrsimon, @SomeKittens  I will turn on animations by default in the PR and I will try to implement your idea regarding the toggling.

Ok, I will hold back :)

Something I was also thinking about is to have a look at whether it would be possible to simplify the collapse/toggle implementation and after that do everything related to it (persisting state, etc.), because right now I am not very confident in changing something in relation to it because I don't understand it fully. I'll probably have to examine the code in more detail :)

@SomeKittens is there something else that needs to be done before merging this PR?

@widmoser Hi, sorry.   Work got busy and then it got worse.  Trying to catch up now.

Things look good, squash the commits into one and I'll bring it in.

This PR has been pending for so long. Dear Dev team, could you please consider review the change and merge into upstream?

We need this, too. +1 vote for merging this!


Updated docs to use Graph SDK in UWP application

The sample active-directory-dotnet-native-uwp-v2 is updated to use Microsoft Graph SDK in the Pull Request. This PR is created to make corresponding changes in docs.
Updated uwp-results-screen-vs2019.png to display output in latest format.

Pull Request already merged.


chore: Remove deprecated deploy workflows/scripts

This cleans up some files that are no longer needed. Travis CI also doesn't need to run the "Deploy" step anymore.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 7.82%. Comparing base (2985560) to head (7dcc297).

Additional details and impacted files
@@          Coverage Diff           @@
##           master    #775   +/-   ##
======================================
  Coverage    7.82%   7.82%
======================================
  Files          68      68
  Lines        3949    3949
  Branches      863     863
======================================
  Hits          309     309
  Misses       3640    3640

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

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


lobby id for into bots

hello, im new to python and coding and was wondering how to switch to intro bots. i managed to figure out the intermediate bots lobby ID (850) but just used:
start_matchmaking(INTERMEDIATE_BOTS_GAME_LOBBY_ID)
though im unable to get it working with:
start_matchmaking(INTRO_BOTS_GAME_LOBBY_ID)

Intro bots lobby id i believe is 830. I am not sure that the bot works correctly in that mode but it might work. In either case, if you want to run it in intro bots, undo your current changes and simply change line 32 in constants.py to

GAME_LOBBY_ID = 830

yeah, ended up figuring it out, also what are the champion priorities for this script and why do does the script barely use any abilities?

Champion priorities come from line 36 in constants.py, you can find a list of champions and their numbers on google pretty easily. It will follow that order then try any free to play champs.. As for abilities, it doesn't use them becuz it is unnecessary as well as difficult to implement.


Add build() method to GCN and GAT classes

Description
This is a continuation of ticket #339, the aim is to add build() method to GCN and GAT classes.
User Story
As a: user of the library
I want: consistent interface to all model classes
so that: I can easily switch models with minimum code change
Done Checklist (Development)

[ ] build method added

[ ] GCN.build()
[ ] GAT.build()

[ ] tests updated
[ ] Demos updated
[ ] Branch and Pull Request build on CI
[ ] Branch and Pull Request pass unit tests on CI
[ ] Peer Code Review Performed
[ ] Code well commented
[ ] CHANGELOG updated

Duplicate of #410

Closing this duplicate issue.


Use i18n instead of PRODUCT_NAME in all the project

What happened?
Now that we have i18n we should be able to have product specific entries and avoid relying on PRODUCT_NAME

@johncowen I think you did this right?

Oh mostly, yeah, now we are just unfortunately left with the place where we started using env('KUMA_PRODUCT_NAME') previous to us having i18n. If you are ok with it, could we add this to the board? Then we can replace all the env('KUMA_PRODUCT_NAME')  with t usage and then we are done with it. It shouldn't take more than an hr or so.

This was done in https://github.com/kumahq/kuma-gui/pull/1383.


Main

Fix wrong parameter type of TrackSubscriptionPermissionChanged event

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Sorry, I wanted to open a different PR for my second contribution :sweat_smile: . Let me properly open two different PRs.


[improve] Handle PositionInfo that's too large to serialize as a single entry

Motivation
In some cases cursor position info can be too large to serialize as a single entry, e.g. in case of too many deleted ranges. Also the serialization can be too slow.
cherry-picks of changes by @eolivelli @nicoloboschi and I.
Modifications
Cursor PositionInfo serialization is reworked to produce less garbage/serialize faster; serialized data can be compressed.
In case the serialized data too large it is chunked and saved as a sequence of entries.
Verifying this change

[ ] Make sure that the change passes the CI checks.

This change added tests.
Does this pull request potentially affect one of the following parts:
NO
If the box was checked, please highlight the changes

[ ] Dependencies (add or upgrade a dependency)
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The threading model
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[ ] The metrics
[ ] Anything that affects deployment

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository: https://github.com/dlg99/pulsar/pull/17

I wonder if this is related to PIP-81 which doesn't seem to have an implementation: https://github.com/apache/pulsar/wiki/PIP-81%3A-Split-the-individual-acknowledgments-into-multiple-entries
There was a larger PR for PIP-81 that was closed: #10729
Some parts of it were split, such as #15425 and #15607.
@codelipenghui @315157973 any details about future PIP-81 plans to share?

Btw. I'm currently investigating a Key_Shared subscription type issue where ordinary consumption of message leads to a very large number of "ack holes". The WIP test app where this is reproduced is https://github.com/lhotari/pulsar-playground/blob/master/src/main/java/com/github/lhotari/pulsar/playground/TestScenarioIssueKeyShared.java .
The test class is not yet simplified to contain the relevant parts. I started with a very complex test case and it seems that the "ack hole" problem shows up in all possible cases.
No messages get lost. It's just that some messages don't get delivered until all other messages have been processed.

In the 1M message experiment, the number of ack holes goes down from about 150k ack holes to <500 with this experiment: https://github.com/lhotari/pulsar/commit/a3b06391fc63635e7a2b86ed51652cde4b51c117

It's possible that the root cause of this issue is #23200 and it is addressed with PRs #23231 and #23226. There's #23224 for observability. Large msgInReplay counts would confirm the root cause.

this is a real problem and it has been solved with a simple and fundamentally proven solution with perf numbers : https://github.com/apache/pulsar/pull/9292
But again I am not sure some folks blocked this PR without saying the reason even after asking multiple times and blocked the progress on this PR.

I wonder if this is related to PIP-81 which doesn't seem to have an implementation: https://github.com/apache/pulsar/wiki/PIP-81%3A-Split-the-individual-acknowledgments-into-multiple-entries
There was a larger PR for PIP-81 that was closed: #10729 Some parts of it were split, such as #15425 and #15607. @codelipenghui @315157973 any details about future PIP-81 plans to share?

Since a PR implemented the compression of PositionInfo, the size of PositionInfo can be greatly reduced, and the problem of Entry size exceeding the threshold will no longer occur, so this PIP was not further promoted.

I wonder if this is related to PIP-81 which doesn't seem to have an implementation: https://github.com/apache/pulsar/wiki/PIP-81%3A-Split-the-individual-acknowledgments-into-multiple-entries
There was a larger PR for PIP-81 that was closed: #10729 Some parts of it were split, such as #15425 and #15607. @codelipenghui @315157973 any details about future PIP-81 plans to share?

Since a PR implemented the compression of PositionInfo, the size of PositionInfo can be greatly reduced, and the problem of Entry size exceeding the threshold will no longer occur, so this PIP was not further promoted.

@315157973 Are you referring to PIP-146: ManagedCursorInfo compression
? What if the size exceeds the threshold after compression?

Codecov Report
Attention: Patch coverage is 38.98757% with 687 lines in your changes missing coverage. Please review.

Project coverage is 74.28%. Comparing base (bbc6224) to head (1397faf).
Report is 599 commits behind head on master.

Files with missing lines
Patch %
Lines

...che/bookkeeper/mledger/impl/PositionInfoUtils.java
26.32%
597 Missing and 16 partials :warning:

...che/bookkeeper/mledger/impl/ManagedCursorImpl.java
74.00%
56 Missing and 16 partials :warning:

...e/bookkeeper/mledger/impl/LedgerMetadataUtils.java
50.00%
1 Missing and 1 partial :warning:

Additional details and impacted files

@@             Coverage Diff              @@
##             master   #22799      +/-   ##
============================================
+ Coverage     73.57%   74.28%   +0.70%
- Complexity    32624    34457    +1833
============================================
  Files          1877     1935      +58
  Lines        139502   146033    +6531
  Branches      15299    15998     +699
============================================
+ Hits         102638   108477    +5839
- Misses        28908    29247     +339
- Partials       7956     8309     +353

Flag
Coverage Δ

inttests
27.56% <20.78%> (+2.98%)
:arrow_up:

systests
24.59% <19.53%> (+0.26%)
:arrow_up:

unittests
73.62% <38.98%> (+0.78%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines
Coverage Δ

.../apache/bookkeeper/mledger/impl/MetaStoreImpl.java
86.34% <100.00%> (+0.43%)
:arrow_up:

...e/bookkeeper/mledger/impl/LedgerMetadataUtils.java
91.66% <50.00%> (-8.34%)
:arrow_down:

...che/bookkeeper/mledger/impl/ManagedCursorImpl.java
79.05% <74.00%> (-0.25%)
:arrow_down:

...che/bookkeeper/mledger/impl/PositionInfoUtils.java
26.32% <26.32%> (ø)

... and 602 files with indirect coverage changes

@lhotari I got rid of byte[] usage and added a feature flag, per your comments

overall let us organize code more appropriately and I am not comfortable with such heavy implementation for a simple feature and it should go to separate interface implementation. I will not block this PR but let's not rush to merge PR and please do not merge this PR without addressing such fundamental separation to avoid creating a messy code base.


[NEW BONUS GUIDE] Sparrow Terminal

What
Additional way to run sparrow on your node using headless implementation for servers.
Why
More ways to run sparrow for users and mixing on your node
How
Adding necessary steps to install Sparrow Terminal and following them
Scope

[ ] reviews

Test & maintenance
Can be tested by following guide and reporting issues, improvements etc.

Thanks for review @VajraOfIndra, except the rest of the things, maybe we could expand the guide? Like "Sparrow Terminal in action", similiar to desktop version. Will demand some screenshots etc. wdyt? Or its something user will figure out himself? Its not that different from normal wallet after all...
Also will change the Fulcrum banner, I deleted Electrs on my node and cant test its connection. Or just can delete the banner and fake it as a "electrum"

Thanks for review @VajraOfIndra, except the rest of the things, maybe we could expand the guide? Like "Sparrow Terminal in action", similiar to desktop version. Will demand some screenshots etc. wdyt? Or its something user will figure out himself? Its not that different from normal wallet after all...

💯  Expanding it with a Sparrow ina ction section would be fantastic. Always better to provide a few pointers on how to use the app imho.

Also will change the Fulcrum banner, I deleted Electrs on my node and cant test its connection. Or just can delete the banner and fake it as a "Electrs"

I think having Electrs as the default option in the command is best. But maybe having the Fulcrum banner in the pic could make the user wonder about it and try it out... so up to you. If it was in the main guide it would have to be Electrs to avoid confusion but since it's a bonus guide, it's up to you but this pic is great as it is I think.

OK

Thanks for review @VajraOfIndra, except the rest of the things, maybe we could expand the guide? Like "Sparrow Terminal in action", similiar to desktop version. Will demand some screenshots etc. wdyt? Or its something user will figure out himself? Its not that different from normal wallet after all...

💯 Expanding it with a Sparrow ina ction section would be fantastic. Always better to provide a few pointers on how to use the app imho.

Also will change the Fulcrum banner, I deleted Electrs on my node and cant test its connection. Or just can delete the banner and fake it as a "Electrs"

I think having Electrs as the default option in the command is best. But maybe having the Fulcrum banner in the pic could make the user wonder about it and try it out... so up to you. If it was in the main guide it would have to be Electrs to avoid confusion but since it's a bonus guide, it's up to you but this pic is great as it is I think.

Cool! I had busy weekend but shoudl get into it today/tommorow

The new entry in the index looks great 🔥
A second review to update the guide to v1.7.1 + a couple of other ocmments
LGTM and tACK (with Raspberry Pi and Electrs + Tor proxy)

I like it too! Did the proposed changes to the latest version
Will we add then that "Sparrow in Action" improvement in another PR? It will take some work and time with screenshotting, so I am not sure If its better to merge this and then focus on that, or finish it? (I think this week I should have it done)

The new entry in the index looks great 🔥
A second review to update the guide to v1.7.1 + a couple of other ocmments
LGTM and tACK (with Raspberry Pi and Electrs + Tor proxy)

I like it too! Did the proposed changes to the latest version
Will we add then that "Sparrow in Action" improvement in another PR? It will take some work and time with screenshotting, so I am not sure If its better to merge this and then focus on that, or finish it?

Probably focus on that one first and then another PR for the "Sparrow in action", easier to reviewa and merge.

The new entry in the index looks great 🔥
A second review to update the guide to v1.7.1 + a couple of other ocmments
LGTM and tACK (with Raspberry Pi and Electrs + Tor proxy)

I like it too! Did the proposed changes to the latest version
Will we add then that "Sparrow in Action" improvement in another PR? It will take some work and time with screenshotting, so I am not sure If its better to merge this and then focus on that, or finish it?

Probably focus on that one first and then another PR for the "Sparrow in action", easier to reviewa and merge.

Cool, I agree. I have this week a bit busy, so I would be able to finish it off by the end of the week, so I agree with another PR!
I dont think I have anything more to add/improve


turn off by default, rather than on by default 2. buggy display in preview mode

I only want it to be active in certain files. My workaround is to use a strange delimeter, but that causes problems as well. It would be better if it were off by default and one could use frontmatter to turn on.
see the width of the key value pairs in this screenshot, which are inconsistent.

(yes, the last is false. this is a true false exam.)
Also, sometimes I intermittently get really short rows or anomalies that sort of go away if I click in each row...

I tried various css such as
kvl-value {
    width: 100%!important;
}

.kvl-key {
    width: 100%!important;
}

.kvl-row {
    width: 100%!important;
    display: inline-block;
}

.kvl-row-inner {
    width: 100%!important;
    display: inline-block;
}

This seems to work the best, but is not perfect.
.kvl-row {
    width: 100%;
    display: inline-block;
    min-width: 70vw!important;
}

I'm also experiencing this problem! The plugin seems to load in some CSS that is conflicting with obsidians own CSS. This makes the plugin unusable for me currently. I'm not in a position to look into this myself, but hope someone finds the issue! 🙏


chore: bdd-sbhg-1586825846 to 0.0.1

chore: Promote bdd-sbhg-1586825846 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Story: Add proper language support for DVC.yaml

We need to help users manage stages, metrics, models, params within the editor.

Updates:

Highlighting is working, but we'll need to adjust colors, so we can leave it for later.

Language support:

(Easy) We can link the file/folder references in the dvc yaml files so VSCode can open them in a new tab.
(Medium) We can register the parameters as symbols, so the user can jump to them on a Cmd+Click on their reference.
(Medium) We can register the metric fields as symbols for the same reasons.
(Hard, because of scoping issues) We can provide definitions for the symbols referenced in the variables, for the same reasons.

I'm posting this now because I believe I have a shot at a first iteration of the first three items in the language support list, and I would like to post a demo tomorrow.

From the DVC docs, the variables are scoped per stage/foreach block and can't be referenced outside of it. They can also be shadowed by using the same variable name in an inner scope.

@wolmir, I think you can ignore the inner scope unless someone asks for it (it's an arcane feature).
That said, I think it'd be easier to design it in a way that resolves each stage independently, considering the support for for-each, as the extension still needs to understand item/key (which is shadowed).

Thanks @skshetry !
While you're here, can you think of other ways VSCode can help with dvc.yaml?

:+1: to pretty much everything here.

We have an in-product prompt to install that extension. It was added in #903. Under this ticket we'll look at expanding support outside of the scope of that extension 👍🏻.

Can we call this out even more? Like @jorgeorpinel, I didn't realize it was for DVC and ignored it.

(Medium) We can register the parameters as symbols, so the user can jump to them on a Cmd+Click on their reference.

This would be nice. Even better would be to suggest individual parameters in IntelliSense by parsing params.yaml (or a custom params file if the key has been provided).

(Medium) We can register the metric fields as symbols for the same reasons.

Unlike params, there shouldn't be individual metrics fields in dvc.yaml. All metrics values should be path-level references. Maybe I'm misunderstanding this point.

(Hard, because of scoping issues) We can provide definitions for the symbols referenced in the variables, for the same reasons.

Not sure I follow what this would do.

I think a view of all stages in the sidebar would be nice which takes you to the individual definitions of the stages and maybe allows running each individually (just like the tests).

In addition, it would be nice if we could show in which other stages a path is referenced and in what context (what is the stage name and is the path a dep/out/etc.).

Other ideas that I think would be helpful (apologize if some are wildly unrealistic, but I'm excited for this as it could greatly improve the experience of creating pipelines):
Snippets
Suggest filled-out templates for sections of dvc.yaml:

Whole stages, or maybe have different stage templates (like dvc exp init --type).
A basic plot template or different templates for various plot types (examples in https://dvc.org/doc/dvclive/api-reference/live/log_plot?tab=roc#supported-plots, https://dvc.org/doc/command-reference/plots#example-smooth-plot).
Foreach stage template.
Vars template.

IntelliSense Suggestions

Suggest path values under sections like wdir, deps, outs, params, metrics, and plots. Even better would be to use file extensions to only suggest appropriate paths (for example, metrics support JSON/TOML/YAML).
Suggest params values from params.yaml. If a specific parameters file is specified, suggest values from that file.
When using vars or foreach and ${} syntax, suggest valid values based on vars/foreach items (and ideally put these at the top of suggestions).

Nice, thanks @dberenbaum !

WIP stuff:
https://user-images.githubusercontent.com/1231848/181832824-6ae3eec9-dbae-4aba-ae9e-8ac21c2d9865.mov
https://user-images.githubusercontent.com/1231848/181832852-2e4f224c-8c16-4b75-a2e4-a6bcc5c5b7f7.mov
https://user-images.githubusercontent.com/1231848/181832917-fd9f8e4b-0204-4ddb-8811-e7107aa37659.mov

@shcheklein ticket needs a checklist of items... please.

It would be nice to have a bash syntax highlighting for cmd. vscode-yaml does not seem to support it though (https://github.com/redhat-developer/vscode-yaml/issues/714).
Parametrization syntax is not very important.

We can link the file/folder references in the dvc yaml files so VSCode can open them in a new tab.

Wasn't this already done in #3175?


Support PHP 7

I like the idea, I use PHP's image The PHP7, Apache, Ubuntu version.
FROM php:7-apache

# installing required stuff
RUN apt-get update \
    && apt-get install -y unzip libaio-dev libmcrypt-dev git \
    && apt-get clean -y

# PHP extensions
RUN \
    docker-php-ext-configure pdo_mysql --with-pdo-mysql=mysqlnd \
    && docker-php-ext-configure mysqli --with-mysqli=mysqlnd \
    && docker-php-ext-install pdo_mysql \
    && docker-php-ext-install mbstring \
    && docker-php-ext-install mcrypt

# xdebug, if you want to debug
RUN pecl install xdebug

# PHP composer
RUN curl -sS https://getcomposer.org/installer | php -- --version=$(curl -s https://api.github.com/repos/composer/composer/releases/latest | grep -oP '"tag_name": "\K[^"]+')  --install-dir=/usr/bin --filename=composer

# apache configurations, mod rewrite
RUN ln -s /etc/apache2/mods-available/rewrite.load /etc/apache2/mods-enabled/rewrite.load

and maybe sharing the PHP configurations folder + MySQL in case geeks wanted to tune stuff.
Web:
  volumes:
    - ./conf/php:/usr/local/etc/php/
db:
  volumes:
    - ./conf/mysql:/etc/mysql/

@AminMkh that looks very good. However I prefer NGINX instead of Apache, and all the current images are based on phusion/baseimage. So I wish if you can contribute with PHP7 + NGINX on phusion/baseimage. Thanks.

Finally this feature is now available, check the release version 1.0.0
https://github.com/LaraDock/laradock/releases/tag/v1.0.0


azcopy copy - Huge diff between recursive folder copy with wildcard vs --list-of-files option

Hi azcopy team,
I'm trying to copy a local folder containing 200 files (size from 500 bytes to 2M) in various subdirectories (max depth 3) to a blob storage.
When, I use wildcard it takes around 20 seconds to proceed from init to end (15 seconds of execution) :
azcopy copy "tests_files/*" "https://region1store.blob.core.windows.net/extracted/test_WC/?sv=xxxxxxx" --recursive=true

...
Elapsed Time (Minutes): 0.2501
...

When I use --list-of-files it takes around 3 minutes to proceed from init to end (14 seconds of execution):
azcopy copy "tests_files" "https://region1store.blob.core.windows.net/extracted/test_FP/?sv=xxxxxxx" --list-of-files=filepath.txt
With the list-of-files, the longest waiting moment seems to be before the processing, explanation in the logs

INFO: Discarding incorrectly formatted input message
INFO: Scanning...
INFO: Any empty folders will not be processed, because source and/or destination doesn't have full folder support

<<WAITS HERE FOR a bit more than 2 minutes and a half>>

Job c877dd8f-79e5-3a46-4178-69e16c14f403 has started
Log file is located at: /root/.azcopy/c877dd8f-79e5-3a46-4178-69e16c14f403.log
100.0 %, 200 Done, 0 Failed, 0 Pending, 0 Skipped, 200 Total,
Job c877dd8f-79e5-3a46-4178-69e16c14f403 summary
Elapsed Time (Minutes): 0.2334
...

The Elapsed time shows that the total execution time is roughly the same (tiny advantage for list-of-files option)
Unfortunately my business scenario would rather use the list-of-files option as I don't need to copy all files in the folder.
The filepath.txt is generated right before the azcopy command, hence it has a valid list of files that does not need to be verified.
Is there anything I could do to minimize this waiting period ?

Hi @jrevault,
This the expected behavior, by design list-of-files option takes more time. This flag is hidden, and we encourage customers to not use it.

Hi @syeleti-msft ,
Thank you for the info, too bad for me :)
Cheers


[LAB2] 311555030

Description

[x] A clear title (name your PR "[LAB{lab_number}] {your_student_id}")
[x] A meaningful message for PR, as well as its commits
[x] From your specific branch (not main or other's branch) merging to your branch
[x] Excluding any irrelevant files, such as binaries, text files, or dot files
[x] Passing all CI (You should check it first to pass one of the validations in CI. However, you need to make sure your PR passes all CI after you submit it.)

It seems you accidentally modify validation script. You should re-sync or redo the operation to fix the workflow.


Add ci test report coverage and upload to codecov

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@98436a8). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             master    #282   +/-   ##
========================================
  Coverage          ?   9.75%
  Complexity        ?      47
========================================
  Files             ?      61
  Lines             ?    2296
  Branches          ?     183
========================================
  Hits              ?     224
  Misses            ?    2052
  Partials          ?      20

Continue to review full report at Codecov.

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

Can you show us the result ? e.g., how does this tool report test coverage (you post some screenshots or reports here)

Beisdes the robot(codecov-commenter) report the coverage of commit above, the detail can be viewed in codecov website.

@yaalsn Thanks a lot for your investigation. I think this is a nice job and we can add a badge (with the permissions of streamnative) in the future.

@timmyyuan
Could we need to merge this pr ?

@Technoboy- The PR failed to pass mop mvn build check. I think we can merge it after the check passes.

Test coverage tool mainly uses JVMTI Agent and It will increase the running time of every test case. We need to resolve the problem of test case timeout before merge the PR.


Confusion between 91_Train and 92_Trap Rust

92_Trap rust folder contains the code for 91_Train

oops, I'll fix that real quick.

turns out I pushed 91_train's implementation to 91_train and 92_trap, luckily I hadn't overwritten someone else's work when I made that mistake, but still.

I could've sworn I implemented 92 Trap for rust.. I guess not x)


Tab Completation is not blocked for players

tab-completion:
disabled = blocked; if it's true, the tab completion will be blocked. (dumb explanation)
disable: true
Player still can use the tabcompletation :3

Hello,
What version are you using which is not blocking the tab completion?
Thanks.

latest version im also getting this but i get kicked and an error in my bungee log

Fixed.

nope i have latest version still get kicked https://gyazo.com/45b3b8c43d20745068912086690d2e41
http://pastebin.com/MBmj92cK

@Twi5TeD this is not your issue. I'll check out yours, I honestly don't know what's causing it as I don't develop BungeeCord but I'll see what's wrong.


Matrix

A brief about your proposal -
So I can see there is no folder for matrix if you want I would like to add some topics in matrix like wave traversal and spiral traversal

@SarthakKeshari please give your review

okay sure


Automatically use configuration from prettierrc

Currently I need to define a custom configuration file for every project because they might all have a different codestyle (different framework for example). It would be nice if this extension could import the settings from a prettierrc file so I don't have to manually reconfigure everything.

Hi @qjnr, have you tried JS/TS Import/Export Sorter which does exactly what you want?


Set permissions to GITHUB_TOKEN

Hi, I'm Joyce, from the Google Open Source Security Team (GOSST). Setting the GITHUB_TOKEN permission is one of the OSSF Scorecard recommendation -- called Token-Permissions check.
The default permissions given to GITHUB_TOKEN is write all, which can be exploited by an attacker in case of a compromised action.
To mitigate this risk it is important to Use credentials that are minimally scoped.
I'll submit a PR together with the issue. Thanks.

Hi thank you for the PR. We will check It soon


Implementing a simple type of deposit for performance testing

Fixes DD-
Description of changes
How to test
Related PRs
(Add links)
*
Notify
@DANS-KNAW/core-systems

Already merged.


Add metrics to understand the  incidence rate of low, standard, and high fees

@beguene To understand the metric accurately,despite selecting low,standard, high and custom received the same metric:

Is this accurate?
analytics.track('use_fee_estimation_default_simulated', {
estimations: [
{
fee: 224,
fee_rate: 37.39330897956175
},
{
fee: 1671,
fee_rate:<PHONE_NUMBER>2979175
},
{
fee: 72159,
fee_rate: 12026.585281780368
}
],
maxValues: [
{
fee: 224,
fee_rate: 37.39330897956175
},
{
fee: 1671,
fee_rate:<PHONE_NUMBER>2979175
},
{
fee: 72159,
fee_rate: 12026.585281780368
}
],
network: 'testnet',
route: '/send',
usingDefaultHiroApi: true,
version: '<IP_ADDRESS>2'
});
Noticed that the fees were

but its listed as   {
fee: 72159,
fee_rate: 12026.585281780368
}
in the segment without decimal,is this the way we want the display of the fees in segment?
Also believe we are not adding the metrics for custom hence will leave the criteria out

If the above findings are accurate,we can move the ticket to merge.Thx

@Eshwari007 My bad, I changed the key name, can you please check again ?
The fee is in micro STX, this is what we use throughout (in our UX code, api, blockchain and documentation) and matches the fee_rate which is also in based on micro STX. I would prefer to stay consistent so we can communicate with the same units if there is an issue.
But if we really need it I can change it.

+1 for consistency!

@beguene the key name is reflecting to the changes

I also cross checked the values are acccurate as being displayed within the ww and segment using the micro STX system.
Will move the ticket to Merge as testing completed


Istio PDBs

This PR introduces Pod Disruption Budget (PDBs) for Istio components. This should increase HA and help in situations like node pool upgrades by ensuring that no more than 1 instance of the critical Istio control plane components is down at a time.
Initially, I wanted to implement this via native TF provider, but it does not support PDBs at this moment, and therefore the new Helm chart and necessity of a separate module.  This cannot co-exist in istio module due to Terraform's inability to handle dynamic provider configuration for import command (even though the provider is not used for the actual resource import, helm_release & helm provider use data source dependent config). See hashicorp/terraform#17847 for details.

LGTM.
Though it is a bit surprising to me that disruption budgets as well as autoscaling changes from #420 are not there on GKE  by default when Istio add-on is enabled.

Thanks for reviews @mrtyler @natarajaya! 👍

I would consider adding the rationale for this standalone chart from the description in this PR to the chart somewhere -- maybe the README?

I've added a comment to main.tf of the Terraform module - rationale - this issue has nothing to do with Helm or the chart, but only Terraform.


Bump cluster-standup-teardown to v1.27.4 to use lower lifecycle hooks heartbeat timeout to allow spot instances to terminate more quickly (CAPA)

What this PR does
Use https://github.com/giantswarm/cluster-standup-teardown/pull/173 to prevent test from timing out because EC2 spot instances can't terminate quickly.
Checklist

[x] Update changelog in CHANGELOG.md.

Trigger e2e tests
Chicken-egg problem, so I'll run these on the cluster-aws PR instead.

This worked for me in a locally-run test and used the correct, reduced lifecycle hook heart beat timeout.
E2E_RELEASE_VERSION=25.1.3 E2E_RELEASE_COMMIT=capa-25-1-3 ginkgo -v -r ./providers/capa/standard

Therefore I'm merging this.


[DEFECT] Auxiliary parameter in ramping constraints may be too large in some instances

Defect Description
Describe the defect
What did you expect to see happen?
This is something that could cause issues in the future. The ramp-up and ramp-down constraints in the Pyomo Dispatcher uses binary variables to track ramp-up, ramp-down, and non-ramp events (with values either 0 or 1).
In the ramping constraints, an auxiliary parameter is used to ensure that if the production variable is constant between time steps (i.e., steady production w/o ramping) that both the ramp-up and ramp-down binary variables must be 0. That parameter was chosen to be a small number, but depending on the capacities that the user specifies, that number may be too large and create artificial constraints on the ramping.
What did you see instead?
Do you have a suggested fix for the development team?
The auxiliary parameter should be either a smaller number, or it should scale with capacity.
Describe how to Reproduce
Steps to reproduce the behavior:
1.
2.
3.
4.
Screenshots and Input Files
Please attach the input file(s) that generate this error.  The simpler the input, the faster we can find the issue.
Platform (please complete the following information):

OS: [e.g. iOS]
Version: [e.g. 22]
Dependencies Installation: [CONDA or PIP]

For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.

[x] 1. Is it tagged with a type: defect or task?
[x] 2. Is it tagged with a priority: critical, normal or minor?
[x] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
[x] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
[x] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.

[x] 1. If the issue is a defect, is the defect fixed?
[x] 2. If the issue is a defect, is the defect tested for in the regression test system?  (If not explain why not.)
[x] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
[x] 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
[x] 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?

Approved to close with #358


Regex in zend-expressive-zendrouter

Hello,
we will migrate our ZF2 MVC Application to ZF3 Expressive. For some functions we use Regex to build the routes. When can I use Regex in zend-expressive-zendrouter?
For example:
'vcalendar' => [   'type' => 'regex',   'options' => [     'regex' => '/vcalendar/(?<room>[0-9]+)(\.(?<format>(html|ics)))?',     'defaults' => [       'action' => 'vcalendar',       'format' => 'ics'     ],     'spec' => '/vcalendar/%room%.%format%',   ], ],

You can't, at least not using the Expressive API for attaching routes to middleware, due to a need to keep the API compatible between all routing implementations. In particular, we found that HTTP method negotiation, while supported directly in other routing implementations, was something we had to "hack" around to make work with zend-router; we ended up injecting a method route as a child route on the primary route to make it happen.
We could potentially support this by allowing you to provide the route type via route options (which would be handled in the ZendRouter::injectRoute() method); if anybody would like to try their hand at this, I'd welcome a pull request.

This repository has been closed and moved to mezzio/mezzio-laminasrouter; a new issue has been opened at https://github.com/mezzio/mezzio-laminasrouter/issues/1.


Add additional conflicts

Fixes for #1344
when testing the previous change I was expecting to to prompt me to remove rtx with the following changes it did so.
I had rtx-bin installed and build the miso-bin package locally using DRY_RUN=1 ./scripts/scripts/release-aur-bin.sh and then running makepkg installing the artifact using yay.
malachi@pulsar aur-bin $ yay -U mise-bin-2024.1.3-1-x86_64.pkg.tar.zst
loading packages...
resolving dependencies...
looking for conflicting packages...
:: mise-bin and rtx-bin are in conflict. Remove rtx-bin? [y/N] y

Package (2)  Old Version  New Version  Net Change

rtx-bin      2024.0.0-1                -15.84 MiB
mise-bin                  2024.1.3-1    15.83 MiB

Total Installed Size:  15.83 MiB
Net Upgrade Size:      -0.01 MiB

:: Proceed with installation? [Y/n]

Feels a bit convuluted mentioning all varations of what it conlifcts with but I guess it's complete :)

unless we really do want to allow them to be installed side by side? :thinking:
in which case we can close this :)


[ServiceBus]: Api version 2023-01-01-preview to support data disaster recovery

Choose a PR Template
Switch to "Preview" on this description then select one of the choices below.
Click here to open a PR for a Data Plane API.
Click here to open a PR for a Control Plane (ARM) API.

/pr RequestMerge

/pr RequestMerge


Configure Azure Pipelines

This step does not merge any code. It tells others that you have changes that you are proposing be merged into master.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: pasmuther sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Added testing to the generated OpenAPI.

Description
This adds tests using dredd.

Builds the spec that only includes APIs with x-tested. This is a new feature of the merger than can be extended in the future to exclude deprecated APIs, or ones for a specified hosted target (AOS, AOSS, etc.), or version of OpenSearch.
Starts an OpenSearch docker container.
Runs dredd against it for the APIs present in the specs.

Issues Resolved
Resolves #277
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.

The spec is pretty far from passing dredd, but I'll keep chipping at it. @Xtansia @nhtruong LMK what you think about this approach?

This is ready to review @Xtansia @nhtruong. Leaving as draft so I can add at least some tests for HEAD/PUT/POST before adopting dredd.

@nhtruong I added POST and DELETE specs, which required correcting the response code from POST to be 201, but now the linter complains that the responses for all index should be the same.
$ npm run lint:spec

><EMAIL_ADDRESS>lint:spec
> ts-node tools/src/linter/lint.ts

Validating /Users/dblock/source/opensearch-project/opensearch-api-specification/dblock-opensearch-api-specification/spec ...
Errors found:

{
  file: 'namespaces/_core.yaml',
  location: 'Operation Group: index',
  message: "3 'index' operations must have an identical set of responses."
}

Total errors: 1

Help me correct this the right way?

Regarding: https://github.com/opensearch-project/opensearch-api-specification/pull/286#issuecomment-2108698322https://github.com/opensearch-project/opensearch-api-specification/pull/286#issuecomment-2108698322
We'll need to update the linter to accept a list of exceptions OR update this lint rule to consider 200 and 201 to be equal. We can't get rid of this lint because the client generators expect operations of the same group to share certain properties, and responses is an important one.

You can use 2XX as the key to just say it'll be some successful response code but not specific (https://swagger.io/specification/#responses-object), though that loses some fidelity

Closing in favor of #299


Cleaning classes

Removing GIS classes, adding instances and proxies: https://linear.app/speckle/issue/CNX-859/objects-alignment
Data objects, interfaces and their inheritance is ignored for now

lets hold off a bit on adding new classes, maybe even deleting.
We're probably going to do a similar v2-v3 fork we did in Objects for specklepy.


BERT Sentiment Service

create an sentiment microservice with an BERT Modell from huggungfaces

finished an BERT sentiment analyser with two models ... one is an standard finetuned model and the second one is an finetuned BERT model from news