Allow shadowing module level symbols

Purpose

This PR aligns the shadowing behaviour with the scoping rules specified in the spec.

Fixes #13273
Fixes #15249
Fixes #12547
Samples

With this change, the following scenarios are now allowed.

boolean b = true;

type myRecord record {
    string a;
    int b;  // used to be a compile error
};

type myObject object {
    int b = 0; // used to be a compile error
};

function testLocalVarScope() returns string {
    string b = "name"; // used to be compile error

    if (true) {
        float b = 12.34; // still a compile error since it's attempting to shadow `b` in the enclosing scope of this block scope.
    }

    return b;
}

Check List

[x] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[x] Added necessary tests

[x] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #15526 into master will increase coverage by 0.88%.
The diff coverage is 0%.

@@             Coverage Diff              @@
##             master   #15526      +/-   ##
============================================
+ Coverage      8.33%    9.22%   +0.88%
- Complexity     2068     2323     +255
============================================
  Files          1378     1487     +109
  Lines         70440    75198    +4758
  Branches       9059     9820     +761
============================================
+ Hits           5874     6939    +1065
- Misses        64004    67542    +3538
- Partials        562      717     +155

Impacted Files
Coverage Δ
Complexity Δ

...ng/compiler/semantics/analyzer/SymbolResolver.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...alang/compiler/semantics/analyzer/SymbolEnter.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...erinalang/compiler/parser/BLangParserListener.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...erinalang/compiler/parser/BLangPackageBuilder.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...c/main/java/org/wso2/ballerinalang/util/Flags.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

.../ballerinalang/compiler/BIRPackageSymbolEnter.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

...lang/compiler/bir/writer/BIRInstructionWriter.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

...2/ballerinalang/compiler/bir/model/BIRVisitor.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

...rs/scopeproviders/BlockStatementScopeProvider.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

...wso2/ballerinalang/compiler/bir/model/BIRNode.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

... and 138 more

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 ca3a3f1...3dc0dfb. Read the comment docs.


Top-level string doesn't interpolate

"civet coffeeInterpolation"
"Hello #{name}!"

compiles to "Hello #{name}!" (incorrect)
"civet coffeeInterpolation"
console.log "Hello #{name}!"

compiles to console.log(`Hello ${name}`) (correct)

I think it has to do with caching. Since the "civet coffeeInterpolation" prologue directive changes the behavior of strings if it is followed by a string it may be parsed and cached. I'd prefer to not add strings to the non-cached list since that could affect parsing performance throughout the whole file.
Fine tuning the directive prologue parsing to only check for simple strings may fix this.

Oh, I forgot about JS prologues. This behavior makes sense then, I think.
It might make sense to just clear the cache after parsing the Civet directive, though I'm not sure whether this is ever an issue.

I probably need to add a comment in the parser since I forgot about it until reading the code :)


find_value: Add 'throw_if_not_present'

Required in order to be able to distinguish between keys which do not exist
and those which exist but point to null values.
If anyone has a better recommendation for which specific exception to throw here, or perhaps even a better way to do it, I'm all ears.

Changed to inherit from std::exception, also see https://github.com/bitcoin/bitcoin/pull/12435

Which methods present you with missing fields? I'm curious to know where you need this. In any event, I don't think this is right. In C++ try/catch blocks are cheap, but throwing an exception is very expensive, because it requires unwinding the stack. The way I would be something like this:
const UniValue& find_value(const UniValue& obj, const std::string& name, int *status=nullptr);

Then in the body if status is not null I'd set a flag if the value is missing (e.g. something like *status = MISSING).

It's in the pull request on the bitcoin repo. In the JSON-RPC 2.0 spec if the 'id' field is not present in a request, then the request should be treated as a 'notification' and not responded to.
The default-argument null pointer thing is clever. I'll change it over to use that instead.

Needs rebase.

PR title is misleading, please update. I think the status could just be a bool?

Closing this for now, as the downstream work is not continuing.


Result/Error improvements

We've been discussing a few ideas for improving the way Errors are structured within our new "Rust-like" results implementation. Some ideas:
1. Current way of handling errors
Base Error: struct Error { id, message, data? }
For each module, we define:
library LibFooError {
    bytes32 constant ERROR1_ID = ...;
    bytes32 constant ERROR2_ID = ...;

    function error1(...args) internal pure returns(FooResult memory) { }
    function error2(...args) internal pure returns(FooResult memory) { }
}

Usage:
// To return the error
return LibFooError.error1(...args);

// To handle the error
if (res.isError(LibFooError.ERROR1_ID)) {
    (...decodedArgs) = abi.decode(res.toError().data, (...argTypes));
}

Pros:

Simple

Cons:

Error id definitions are separate from the other stuff related to the error (getting ids and creating the error are not standardized)
No type safety, users have to manually decode
Encoding/decoding must be simple (abi.decode)

2. Errors as micro libraries
Base Error: struct Error { id, message, data? }
For each specific error, we define:
library FooError {
    bytes32 constant id = ...;
    function create(...args) internal pure returns(Result memory) { } // Alternatively this could return the specific result we want
    function decode(Error memory) internal pure returns(...decodedArgs) { } // Only if Error encodes data
}

Usage:
    library someModule {
        function returnErrors() internal returns (ModuleResult memory) {
            return ModuleResult(FooError.create(bytes32("Hello, World!")));
        }
    }

    function foo() external {
        ModuleResult memory result0 = someModule.returnErrors();

        if (result0.isOk()) {
            // Do something
        }

        if (result0.isError(FooError.id) {
             bytes32 payload = FooError.decode(result0.toError());

             expect(payload).toEqual(bytes32("Hello, World!")); // true
        }
    }

Pros:

Full type safety
The error id "is part" of the error library definition (standardized way of checking ids)
Internal encoding/decoding can be as complex as we need as long as we don't change the api

Cons:

We have to define a library for each error
The library functions are just a convention, as libs can't inherit (all methods are conventions anyways)
Add more

3. Using custom errors
Base Error: struct Error { message, data }
We modify the Error struct functions and we add
    function extract(Error memory self) internal pure returns (bytes4 selector, bytes memory payload) {
        (selector, payload) = extractSelector(self.data);
    }

Our module specific error library will look something like
library ModuleErrors {
    error Error0(bytes32);

    // `data` is the additional information we want to store on the error
    function error0(bytes32 data) internal pure returns (TestResult memory) {
        return TestResult(Error("error0", abi.encodeWithSelector(Error0.selector, data)).toResult());
    }
}

Usage:
    library someModule {
        function returnErrors() internal returns (ModuleResult memory) {
            return ModuleErrors.error0(bytes32("Hello, World!"));
        }
    }

    function foo() external {
        TestResult memory result0 = someModule.returnErrors();

        if (result0.isError()) {
            Error memory err = result0.toError();

            (bytes4 selector, bytes memory payload) = err.extract();

            if (selector == TestErrors.Error0.selector) {
                bytes32 payload = abi.decode(payload, (bytes32));

                expect(payload).toEqual(bytes32("Hello, World!")); // true
            }
        }
    }

Pros:

We don't need to maintain custom ids since we can use selectors.
Custom errors encapsulate and describes the additional data we want to transmit with the error.
There is less boilerplate since the extract function will return the selector and payload directly from the Error struct so we don't need to add special functions to the module libraries

Cons:

The payload needs to be decoded with the correct types so bugs can be added when decoding
There is no type safety when storing the custom error in the Error struct

4. Errors as functions
Base Error: type Error is bytes32
For each specific error we define a function:
    using LibError for *;

    function FooError(bytes32 value) internal pure returns (Error) {
        return FooError.encodeError("Foo error message", value);
    }

Usage:
    library someModule {
        function returnErrors() internal returns (ModuleResult memory) {
            return ModuleResult(FooError(bytes32("Hello, World!")).toResult());
        }
    }

    function foo() external {
        ModuleResult memory result0 = someModule.returnErrors();

        if (result0.isOk()) {
            // Do something
        }

        Error err = result0.toError();
        if (err.matches(FooError) {
             bytes32 payload = err.decodeAs(FooError);

             expect(payload).toEqual(bytes32("Hello, World!")); // true
        }
    }

Pros:

Full type safety
The error id "is part" of the error (it is just the encoded internal function)
Clean syntax as the error functions can be passed as arguments to other functions
Once we have the main setup ready for multiple function types, defining new error functions is extremely easy

Cons:

We have to define a large LibError library that defines matches, encodeError and decodeAs for each function type we want to support (this could be automated though).
internal function encoding is actually not documented and is considered an implementation detail, so it could change at some point. However, other projects use function pointers so we should probably be fine.

We decided to go for 4. implemented in #189


[WIP] fix(ngRoute): Attach resolved locals before controller instantiation

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Bug fix. Fixes #14134

What is the current behavior? (You can also link to an open issue here)
#14134

What is the new behavior (if this is a feature change)?
Add the $resolve property to the route scope prior to instantiating the controller

Does this PR introduce a breaking change?
no

Please check if the PR fulfills these requirements

[X] The commit message follows our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
[X] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

Other information:

Resolved locals are attached to route scope as $resolve or the
resolveAs string prior to instantiation of the routes controller
so the properties are available in the controller as $scope.$resolve.
Fixes #14134

[WIP] because I was unsure where to document this new behavior. If the team has any suggestions, I'd like to hear them. The current documentation for $resolve is in the components section, but that didn't seem to make sense for using the property within any generic route controller. Does it make sense to put it in the di doc?

I assume this is superseded by https://github.com/angular/angular.js/pull/14136

That's actually a standalone issue.


override find_bs with len in accumulate

fixes #638

@lgvaz what do you think? The failing tests are not from the things I touched


Pass is-large-runner to release-dev workflow

This change only affects CI on the main branch. Bypassing in order to validate CI on main.


Not able to get the element

Trying to get the value of  titlebar of the page :
var pageTitle = _driver.Current.FindElementByAccessibilityId("TitleBar").GetAttribute("Value.Value");
Also tried :  var pageTitle = _driver.Current.FindElementByTagName("TitleBar").GetAttribute("Value.Value");
In both the case it is throwing the following error:
error: The HTTP request to the remote WebDriver server for URL http://<IP_ADDRESS>:4723/session/ABC7DE2E-34C5-444B-A202-DD1B54E6774A/element timed out after 60 seconds. (62.8s)
Suprising thing is  : This code used to work before , suddenly stopped working where I have done no changes in the code.
Team please help me.

@anunay1 , I do  confirm from the respective Dev team nothing is changed in that particular section ... and i have not change anything in the framework....
If any more suggestion to me... it will be helpful

What do you get in page source?

Code is failing when trying to get the page source:
var PageSource= _driver.Current.PageSource;
error: The HTTP request to the remote WebDriver server for URL http://<IP_ADDRESS>:4723/session/7DBCF40E-97CC-41E4-A997-D0F2FFA1E932/source timed out after 60 seconds.

then there is some issue with the winappdriver server, what is shown in the console output of winappdriver. Also check before this line are you able to ping the server.

@anunay1 I am able to do everything except this line...
In the code I just need to get the title of the page, which really used to work but suddenly providing the following sort of error.
error: The HTTP request to the remote WebDriver server for URL http://<IP_ADDRESS>:4723/session/7DBCF40E-97CC-41E4-A997-D0F2FFA1E932/source timed out after 60 seconds.

the error says that it timed out, that means the client request is not able to reach the server.

Yes, but it is so wierd ... If I am trying to click any other element it is working, whenever I am trying to get the titlebar it is providing the server error.. any suggestion from your end

It is solved:
_driver.Current.Title


Service principal script fails

To use the service principal script, I first had to run the following PowerShell commands:

Install-Module -Name AzureAD -AllowClobber -Scope CurrentUser
Install-Module -Name Microsoft.Xrm.OnlineManagementAPI -AllowClobber - Scope CurrentUser

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

ID: fba2155b-98b3-64e0-29f5-79cf2b1a90f1
Version Independent ID: d2b30089-7cf3-563a-eb38-d112793beb9b
Content: Microsoft Power Platform Build Tools for Azure DevOps - Power Platform
Content Source: power-platform/alm/devops-build-tools.md
Service: powerapps
GitHub Login: @phecke
Microsoft Alias: pehecke

Even after following the steps above i still keep getting the following error.
\New-CrmServicePrincipal.ps1 : A parameter cannot be found that matches parameter name 'TenantId'.
At line:1 char:1
+ .\New-CrmServicePrincipal.ps1 -TenantLocation "Europe"
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [New-CrmServicePrincipal.ps1], ParameterBindingException
    + FullyQualifiedErrorId : NamedParameterNotFound,New-CrmServicePrincipal.ps1

The fix for this is to use version <IP_ADDRESS> of Microsoft.Xrm.OnlineManagementAPI:
Uninstall-Module -Name Microsoft.Xrm.OnlineManagementAPI
Install-Module -Name Microsoft.Xrm.OnlineManagementAPI -MaximumVersion <IP_ADDRESS>

The fix for this is to use version <IP_ADDRESS> of Microsoft.Xrm.OnlineManagementAPI:
Uninstall-Module -Name Microsoft.Xrm.OnlineManagementAPI
Install-Module -Name Microsoft.Xrm.OnlineManagementAPI -MaximumVersion <IP_ADDRESS>

@pierceboggan Thanks for your feedback. We are closing this issue because we are either unable to find relevant information or reproduce this. If you're still experiencing the issue described here, please reopen or create a new issue.


.withQueryParam() criteria not distinguishes 2 different values

Hi,
Working v2.17.0 of WireMock, I'm having trouble with 2 stubs on the same url but with two different parameter values. It seems that the url with the second param value does not match any stub.
...
get(urlPathEqualTo("/mock/api/rest/v1/locales")).withQueryParam("page", equalTo("1"))
...
get(urlPathEqualTo("/mock/api/rest/v1/locales")).withQueryParam("page", equalTo("2"))
...

Then I have the log reporting as below :
                                               Request was not matched
                                               =======================

-----------------------------------------------------------------------------------------------------------------------
| Closest stub                                             | Request                                                  |
-----------------------------------------------------------------------------------------------------------------------
                                                           |
GET                                                        | GET
/mock/api/rest/v1/locales                                  | /mock/api/rest/v1/locales?page=2&limit=100
                                                           |
Query: page = 1                                            | page: 2                                             <<<<< Query does not match
                                                           |
                                                           |
-----------------------------------------------------------------------------------------------------------------------

Am I doing anything wrong ?
Please advice,
Best regards

my bad I had a mistake in my code so it called another page but not on "locales"...
sorry


new devtools team members

https://www.ncameron.org/blog/dev-tools-in-2018/#devtools

Hm, it looks like diesel_cli isn't happy with the current version rfcbot is pinned to. @Centril bumped versions in https://github.com/anp/rfcbot-rs/pull/197 which are passing CI. Want to cherry-pick his version bumps here?

yolo


question regarding polygons

First let me thank you for your hard work and your efficient code!
I have a question regarding the use of your code. I need to get the voronoi tesselation exported as polygons. Your code (as far as I can see) only gives me a bunch of line strings which plotted look like polygons but in fact are not related to each other.. am I right?
Is there a way to get the information about which lines form a enclosed polygon?
So I know the number of polygons by providing the number of points but I don't know when to cut the output of lines to a complete polygon.
Can you help me here? You know your code probably better than me from just reading :)

you can get the "polygons" in the Cells
unsigned int index; //from 0 to amount of Vornoi Cells
unsigned int edge_index;
Diagram* diagram; //the Diagram you are working in
Cell* c = diagram->cells.at(index); // the Cell at index, order is random
c->halfEdges[edge_index];//you get the points with c->halfEdges[edge_index]-> startPoint(); or
c->halfEdges[edge_index]-> endPoint();
every Cell is a Convex Shape (NOT splitet in TRIAS it´s an NGon) so it is already in a useful form, you only have to convert it in your format.

Thanks, that works perfectly! :)
Currently I am using your provided Visual Studio Project file to work with your code. Everything is fine here and it compiles without errors. But when using the same code in another Editor I get errors like this:

undefined reference to `Point2::Point2()

Even though the includes are set correctly. I am not working with the OpenGL version, only console.
What am I doing wrong here?


Not possible to start PowerToys as user !

Microsoft PowerToys version
0.55.2
Running as admin

[ ] Yes

Area(s) with issue?
Installer
Steps to reproduce
On a machine on a domain in an user session with no admin rights, install PowerToys by executing as admin then at the end of installation you will have the error : Not possible to start PowerToys as user !
If you click on ok on this error message, it still continue to appear, i need to uninstall PowerToys to stop the error message to appear.
This issue happens since version 0.55.1
✔ Expected Behavior
No error message
❌ Actual Behavior
Error message which appear and when click stop it still appear : Not possible to start PowerToys as user !
Other Software
No response

@xillibit Thanks for reporting. This is a known issue and is already solved. Will be a part of the next PT release. In the meantime ,as workaround you can kill the PowerToys process manually from Task Manager, and then start PowerToys again. It should work that way

This is fixed with 0.561.  Please head over to https://aka.ms/installpowertoys


es: boost fields in search factory

Boost fields defined in boosted_fields attribute of a RecordsSearch class (if the attribute exists).

@KonstantinaStoikou thanks a lot for this PR! Would it be possible to add a test to show the boosting?
Or too hard? I am thinking to have a couple of demo records where we boost the title for example...
We also need to see this issue with the *.


Tracking issues of OpenDAL v0.47.2 Release

This issue is used to track tasks of the opendal v0.47.2 release.
Tasks
Blockers

Build Release
Relelase List

Name
Version
Next

core
0.47.1
0.47.2

integrations/cloudfilter
0.0.0
0.0.0

integrations/dav-server
0.0.3
0.0.4

integrations/fuse3
0.0.0
0.0.1

integrations/object_store
0.44.1
0.44.2

integrations/unftp-sbe
0.0.0
0.0.1

integrations/virtiofs
0.0.0
0.0.0

bin/oay
0.41.4
0.41.5

bin/ofs
0.0.5
0.0.6

bin/oli
0.41.4
0.41.5

bindings/c
0.44.6
0.44.7

bindings/cpp
0.45.4
0.45.5

bindings/dotnet
0.1.2
0.1.3

bindings/go
0.0.0
0.0.0

bindings/haskell
0.44.4
0.44.5

bindings/java
0.46.1
0.46.2

bindings/lua
0.1.2
0.1.3

bindings/nodejs
0.46.2
0.47.0

bindings/ocaml
0.0.0
0.0.0

bindings/php
0.1.2
0.1.3

bindings/python
0.45.4
0.45.5

bindings/ruby
0.1.2
0.1.3

bindings/swift
0.0.0
0.0.0

bindings/zig
0.0.0
0.0.0

Notes:

nodejs binding has breaking changes

GitHub Side

[x] Bump version in project

[x] rust
[x] cpp
[x] haskell
[x] java
[x] nodejs

[x] Update docs
[x] Generate dependencies list
[x] Push release candidate tag to GitHub

ASF Side

[x] Create an ASF Release
[x] Upload artifacts to the SVN dist repo
[x] Close the Nexus staging repo

Voting

[x] Start VOTE at opendal community

Official Release

[x] Push the release git tag
[x] Publish artifacts to SVN RELEASE branch
[x] Release Maven artifacts
[x] Send the announcement

For details of each step, please refer to: https://opendal.apache.org/community/release/

v0.47.2 released now, closing.


Build fails with linux

[fennectech@Aluminum ~/PqSave]$  xbuild PqSave.sln

xbuild tool is deprecated and will be removed in future updates, use msbuild instead <<<<

XBuild Engine Version 14.0
Mono, Version <IP_ADDRESS>
Copyright (C) 2005-2013 Various Mono authors
Build started 6/4/2018 5:09:48 PM.

/home/fennectech/PqSave/PqSave.sln:  warning : /home/fennectech/PqSave/PqSave/PqSave.csproj: The default XML namespace of the project must be the MSBuild XML namespace. If the project is authored in the MSBuild 2003 format, please add xmlns="http://schemas.microsoft.com/developer/msbuild/2003" to the  element. If the project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format.
/home/fennectech/PqSave/PqSave.sln:  warning : Don't know how to handle GlobalSection ExtensibilityGlobals, Ignoring.
Project "/home/fennectech/PqSave/PqSave.sln" (default target(s)):
Target ValidateSolutionConfiguration:
Building solution configuration "Debug|Any CPU".
Target Build:
/home/fennectech/PqSave/PqSave/PqSave.csproj: error : /home/fennectech/PqSave/PqSave/PqSave.csproj: The default XML namespace of the project must be the MSBuild XML namespace. If the project is authored in the MSBuild 2003 format, please add xmlns="http://schemas.microsoft.com/developer/msbuild/2003" to the  element. If the project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format.
Task "MSBuild" execution -- FAILED
Done building target "Build" in project "/home/fennectech/PqSave/PqSave.sln".-- FAILED
Done building project "/home/fennectech/PqSave/PqSave.sln".-- FAILED
Build FAILED.
Warnings:
/home/fennectech/PqSave/PqSave.sln:  warning : /home/fennectech/PqSave/PqSave/PqSave.csproj: The default XML namespace of the project must be the MSBuild XML namespace. If the project is authored in the MSBuild 2003 format, please add xmlns="http://schemas.microsoft.com/developer/msbuild/2003" to the  element. If the project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format.
/home/fennectech/PqSave/PqSave.sln:  warning : Don't know how to handle GlobalSection ExtensibilityGlobals, Ignoring.
Errors:
/home/fennectech/PqSave/PqSave.sln (default targets) ->
(Build target) ->
/home/fennectech/PqSave/PqSave/PqSave.csproj: error : /home/fennectech/PqSave/PqSave/PqSave.csproj: The default XML namespace of the project must be the MSBuild XML namespace. If the project is authored in the MSBuild 2003 format, please add xmlns="http://schemas.microsoft.com/developer/msbuild/2003" to the <Project> element. If the project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format.

 2 Warning(s)
 1 Error(s)

Time Elapsed 00:00:00.8125330
{17:09} Mon Jun 04
[fennectech@Aluminum ~/PqSave]$

Use Visual Studio or the .NET Core SDK to build the project

thanks    :D i did not know of the  .net core SDK    its effing cool


Added a first version of architecture documentation

Summary
Added an architecture documentation.
How to test
Any feedback is welcome. Also Is this the correct place for this or should it be in QuantMark repository?

Codecov Report

Merging #153 (95c6e14) into main (3a9e870) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #153   +/-   ##
=======================================
  Coverage   87.91%   87.91%
=======================================
  Files          33       33
  Lines        1051     1051
=======================================
  Hits          924      924
  Misses        127      127

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 3a9e870...95c6e14. Read the comment docs.


Add support for Carla 0.9.15

It seems that nothing in the API has changed so it should be enough to build a new version for Carla 0.9.15.

will take a look when having some time

Done in https://github.com/mjxu96/carlaviz/pull/70.


Folder Error

Hi bro, I have problem with your Plug-In - On settings I select my folder, but all time it write the same error :

Can you help me? :) Thank you.

I have the same problem with this.. I create the folder but there is no text for my plugin

Sorry, I completely forgot about this issue.
Once you select the desired folder in CurrentSong's options, does its path appear next to the "Browse ..." button like shown in this image?

If so, is the path still there after restarting Firefox?

If you are experiencing this problem, please contact me here and I will try to resolve it. Right now I'm missing information to know what is causing the problem.

I ve fix this with restart my PC... After that I set the folder without problem. Is there any chance that this plugin will support direct file to CLR Browser for OBS or Browser Plugin for OBS Studio ? My problem is with size of song name. When song name is large I can't keep it under text box..

CurrentSong does support CLR Browser and Browser plugin, that's why CurrentSong also saves a XML file. Of course the HTML page to show with the plugin is missing, I supposed users wanted to do that themselves.
I might do a simple HTML page so that users can use it as a template for their own pages.

@ceco22 check out this HTML page. It's very crude, but it should get you started to display the song info with the Browser plugin.

I'm going to close this issue.
@ceco22 if you still want to talk about the Browser plugin please open a new issue, as it is a different topic.


Add a license

I'd like to use your code, so if you'd allow this, please add a FLOSS license like MIT, BSD or GPL.

Apologies for not responding to this sooner, I've been away from FOSS for a while due to other commitments.
I'll try to get a license file added this week, it will be MIT, please feel free to do whatever you want with this code. If you make your millions from it, please send me some milk as I have run out and cannot be bothered walking to the shop even though I really want a cup of tea.

Sure, thanks!


nixos/knot-resolver: extraFeatures depends on listenDoH, awkward to workaround

Describe the bug
My kresd configuration invokes features that depend on cqueues, which is disabled by default
and can be enabled with .override { extraFeatures = true; }.
Since the kresd modules does not have a package option, the user can overlay this new package
and the module will use it. Until 20.03, where the module itself overrides the package again,
undoing my previous override if listenDoH == [].
https://github.com/NixOS/nixpkgs/blob/68df00b0ba61eb304549dd52154622fdcc4c806e/nixos/modules/services/networking/kresd.nix#L35-L37
This can be worked around with
  nixpkgs.overlays = [
    (self: super: rec {
      # this adds lua cqueues, required for watching the rpz file
      # prohibit further overrides, because the kresd module undoes this override
      knot-resolver = (super.knot-resolver.override {
        extraFeatures = true;
      }) // { override = _: knot-resolver; };
    })
  ];

but that's hacky, and there should be a better way.
Expected behavior
Either of these would be better, but I opened an issue instead of a PR, to discuss alternate solutions

Add an option to enable features
Add a package option
Conditionally override if listenDoH != [], but don't override if it's empty

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute: knot-resolver
# a list of nixos modules affected by the problem
module: services.kresd

cc @vcunat

:thinking: what configuration API would be best?
Off the top of my head, I'd suggest adding services.kresd.package that defaults to the current state:
pkgs.knot-resolver.override { extraFeatures = cfg.listenDoH != []; }

The .package options seem pretty standard in NixOS config.

Actually, I'd probably apply the third one or something similar, as that seems a pure bugfix approach.  That doesn't really prevent us also adding something else like the first or second bullet, but that would probably be later than for 20.03.


change my own password

As a user, I would like to change my own password.
This does not seem to be possible yet?

user need to be in group defined by "gidcanchgpass"

ohh, thanks for the explanation!


How do you style the buttons?

Is it possible to style the buttons?

The elements in the popover recieve class names. You can check this file for reference if the browser inspector does not suffice.
As seen in the demo, you can also give the popover additional custom class names in case you want to have multiple types of styles in different cases.


Phosphorus does not apply to item (fertilizer data)

My script:

In game:

Thanks for the report! This will be fixed in 1.0.3 which should be going out soon

Alright, curse is being a pain, but its up on Modrinth, so I'll go ahead and close both issues


Jassby

https://jassby.com/

Fixed in https://github.com/jplock/awesome-fintech/commit/8abc238bbf2378cde9a322dc6ad164f0d5cbea70


New Hacking Programs

With HSN3 there are a number of new hacking programs that need to be implemented.

Added new programs in bf3d8dc9c8e87c7417d30b68b4d3dcfd6d577658 and ae374f0e8450422701dd3b6c119e3de68e77b8ea
SWORD-2
*Redrum
*Skullbuster
*Trinity
UPGRADES
*Exile
*Maestro
*Lightning
*Icebreaker

Things that still need implementation:

KHDs ignore firewalls
Proper handling for units with multiple hacking devices (they will show one of them arbitrarily)
Kaleidoscope bonuses
Reboot bonuses


Padding

Hi. Is there anyway i could add a padding between the border and the circular image?
Thanks!

@klutchmeister have you figured out how to do this? I need to set that padding so badly!

Not yet. I kinda ended up accepting it. LOL. But please hit me up whenever you do. I'll do the same.


[Feature] Add typehint.

Motivation
Add typehint to the code and make it more readable.
Checklist

Pre-commit or other linting tools are used to fix the potential lint issues.
The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness.
If the modification has potential influence on downstream projects, this PR should be tested with downstream projects.
The documentation has been modified accordingly, like docstring or example tutorials.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: pd-michaelstanley:x: Lum1104You have signed the CLA already but the status is still pending? Let us recheck it.


Enhancement/jel 631 ip hostname and provisioning status

All things are good on the UX side, once #649 is addressed by updating the seed or alternatively a device is provisioned the changes will be realized

removed the debug, good call!

:+1:

Addressed by https://github.com/projectjellyfish/api/tree/feature/update-services


Update the repository for www.embulk.org site

We'll update the repository to provide the https://www.embulk.org website.
@sakama @kamatama41 Can you have a look?

Thanks! Let me merge this - and then I'll release Embulk v0.9.12.


Support geohash API(#14)

Support the redis geohash API(#14). The implementation is derived from the C code of Redis.

Will be merged after the next release.


rp: fix adc test flakiness

GP29 is connected to the cyw43 SCK pin. cyw43 is selected by default (due to rp2040 pins being input/pulldown by default), so the wifi chip is always selected and watches the SCK pin. this little bit of load on the SCK pin is enough to disturb the 300k voltage divider used for VSYS sensing, making the test flaky.

LGTM, can you fix CI?


Check for empty auth info as well as null.

@nickmbailey maybe squash and rebase?

This was purposely branched from 1.3.0 in case it can go into a 1.3.1 patch release, but I'm happy to rebase against master if thats needed. Also happy to squash to a new branch and create a new PR, but any reason not to just use the github squash+merge feature?

This has been merged in as 1.3.1-alpha3.

Hey @danielcompton the PR appears to not have been merged (I don't see it in master).

Sorry, I've pushed it now.

We've tested 1.3.1-alpha3 and is good for us.


Add esp_v2 gke deployment files

Signed-off-by: Wayne Zhang<EMAIL_ADDRESS>Add two GKE deployment files for ESPv2.

Could you be specific about how they are used or referenced?
I see there a README.md under k8s/. Updated it also?

They are used in public doc:
endpoints/docs/_shared/_enabling-ssl.md
endpoints/docs/openapi/get-started-kubernetes-engine.md

Hold on,  I will update README too


⚠ Aither has degraded performance

In bb29f6b, Aither ($AIH) experienced degraded performance:

HTTP code: 200
Response time: 5582 ms

Resolved: Aither performance has improved in 94c2a58 after 7 minutes.


Added config file for tox. Closes #31.

Checkout the branch, run pip install tox and then run tox. As a side-note, there is currently one failing test.

@richleland Yeah, I added that test to illustrate #75 and #74, which are still open.


How to integrate with api

is there any way to add the api builder / generator to the quickadmin

We have this function in online generator version at www.quickadminpanel.com - here's a short video: https://www.youtube.com/watch?v=hqSuBb_WQmE


License of hb

What is the license of hb?

I totally forgot, thanks for bringing this up! I added the MIT license 👍

Thank you for the reply.
I have understood the license now and would like to implement some of your creations to my next project.


Ldap integration for vsphere when tanzu is enabled

we are trying to integrate tanzu kubernetes cluster with ldap integration.
we have vsphere with tanzu enabled in the vcenter server .
We will be creating tanzu kubernetes cluster from the workload management in the vcenter.
How we can integrate our tanzu kubernetes cluster with ldap in vsphere with tanzu enabled?

https://github.com/vmware-tanzu/pinniped/issues/949#issuecomment-1014826334


docs: Create architecture overview.

[x] Create codemap
[ ] Document end-to-end process
[ ] Add cross-cutting concerns

Needs to be rewritten when v2 is complete.


Can't select text in textfield inputs within sortables

Hi
I create a list of choices of a question. I put a textfield inside each of my sortable item. When i select (dragging pointer) text in textfield, the textfield become moved. So.. all of elements inside become draggable. I need to know how to exclude textfield element from draggable?
Thank You :)

Solved!
Use class 'is-isolated' in any element that we need to exclude from draggable.
example:


Activate rotation of role for mtg facilitator

@damianavila it still needs debugging, the commit step isn't working and I'm not sure why 😢 There is a GitHub workflow with a manual trigger that will advance the role along. But yes, the intention was that this will be rolled out to the team now.

it still needs debugging, the commit step isn't working and I'm not sure why

If it takes time, it takes time... I am pretty sure you will succeed in the end! 😉
Thanks for the additional information, @sgibson91!


[incubator/elasticsearch/] - no persistent volumes available for this claim and no storage class is set

values.yaml
# Default values for elasticsearch.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.
appVersion: "5.4"

image:
  repository: "centerforopenscience/elasticsearch"
  tag: "5.4"
  pullPolicy: "IfNotPresent"

cluster:
  name: "elasticsearch"
  config:
  env:
    # IMPORTANT: https://www.elastic.co/guide/en/elasticsearch/reference/current/important-settings.html#minimum_master_nodes
    # To prevent data loss, it is vital to configure the discovery.zen.minimum_master_nodes setting so that each master-eligible
    # node knows the minimum number of master-eligible nodes that must be visible in order to form a cluster.
    MINIMUM_MASTER_NODES: "2"

client:
  name: client
  replicas: 2
  serviceType: ClusterIP

## (dict) If specified, apply these annotations to the client service
#  serviceAnnotations:
#    example: client-svc-foo

  heapSize: "512m"
  antiAffinity: "soft"
  resources:
    limits:
      cpu: "1"
      # memory: "1024Mi"
    requests:
      cpu: "25m"
      memory: "512Mi"

  ## (dict) If specified, apply these annotations to each client Pod
  # podAnnotations:
  #   example: client-foo

master:
  name: master
  exposeHttp: false
  replicas: 3
  heapSize: "512m"
  persistence:
    enabled: true
    accessMode: ReadWriteOnce
    name: data
    size: "4Gi"
    storageClass: "gluster-heketi"
  antiAffinity: "soft"
  resources:
    limits:
      cpu: "1"
      # memory: "1024Mi"
    requests:
      cpu: "25m"
      memory: "512Mi"

  ## (dict) If specified, apply these annotations to each master Pod
  # podAnnotations:
  #   example: master-foo

data:
  name: data
  exposeHttp: false
  replicas: 2
  heapSize: "1536m"
  persistence:
    enabled: true
    accessMode: ReadWriteOnce
    name: data
    size: "100Gi"
    storageClass: "gluster-heketi"
  terminationGracePeriodSeconds: 3600
  antiAffinity: "soft"
  resources:
    limits:
      cpu: "1"
      # memory: "2048Mi"
    requests:
      cpu: "25m"
      memory: "1536Mi"

  ## (dict) If specified, apply these annotations to each data Pod
  # podAnnotations:
  #   example: data-foo

## Install Default RBAC roles and bindings
rbac:
  create: false

kube@server2:/data/glusterfs/data/gluster_volume/helm/elasticsearch$ kubectl describe sc gluster-heketi
Name:                  gluster-heketi
IsDefaultClass:        No
Annotations:           <none>
Provisioner:           kubernetes.io/glusterfs
Parameters:            resturl=http://<IP_ADDRESS>:8080,restuser=joe,restuserkey=My Secret Life,volumetype=none
AllowVolumeExpansion:  <unset>
MountOptions:          <none>
ReclaimPolicy:         Delete
VolumeBindingMode:     Immediate
Events:                <none>

In other PVC work with StorageClass gluster-heketi
helm call
helm install --name elasticsearch1 -f values.yaml incubator/elasticsearch
Result
kube@server2:/data/glusterfs/data/gluster_volume/helm/elasticsearch$ kubectl describe pvc data-elasticsearch1-elasticsearch-master-0
Name:          data-elasticsearch1-elasticsearch-master-0
Namespace:     default
StorageClass:
Status:        Pending
Volume:
Labels:        app=elasticsearch
               component=master
               release=elasticsearch1
Annotations:   <none>
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
Events:
  Type    Reason         Age                 From                         Message
  ----    ------         ----                ----                         -------
  Normal  FailedBinding  50s (x423 over 1h)  persistentvolume-controller  no persistent volumes available for this claim and no storage class is set

Where I see the problem:
no persistent volumes available for this claim and no storage class is set

i get the same problem

Also getting this error

Add to values.yml like this:
master:
persistence:
storageClass: "managed-nfs-storage"
data:
persistence:
storageClass: "managed-nfs-storage"


update(driver,libsinsp): inode numbers in file events

What type of PR is this?
/kind feature
Any specific area of the project related to this PR?
/area driver-kmod
/area driver-ebpf
/area libsinsp

What this PR does / why we need it:
This adds inode number to information about returned file descriptors in relevant events: PPME_SYSCALL_OPEN_X , PPME_SYSCALL_CREAT_X , and PPME_SYSCALL_OPENAT_2_X . This involed:

kmod driver now extracts inode number while getting device number with minimal additional work
ebpf driver now uses inode number it already extracted
libsinsp now exposes inode number in sinsp_fdinfo and supports it in filters

Which issue(s) this PR fixes:

Fixes #304
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

Welcome @yo348! It looks like this is your first PR to falcosecurity/libs 🎉

Hi @yo348. Thanks for your PR.
I'm waiting for a falcosecurity member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: yo348
To complete the pull request process, please assign leogr after the PR has been reviewed.
You can assign the PR to them by writing /assign @leogr in a comment when ready.
The full list of commands accepted by this bot can be found 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

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

bcae6f8 update(driver,libsinsp): unify the method of getting inode numbers for pipes and files. Minor fixes.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: yo348
To complete the pull request process, please ask for approval from andreagit97 after the PR has been reviewed.
The full list of commands accepted by this bot can be found 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

On which kernel version (clang version) do you test it?

$ clang --version
clang version 10.0.0-4ubuntu1
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
$ uname -a
Linux yoliinyk-ubuntu 5.13.0-40-generic #45~20.04.1-Ubuntu SMP Mon Apr 4 09:38:31 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
I can tell the probe is being built just fine, but I do have trouble testing it. Attempting to load it with sysdig gives me this:
# sysdig --bpf=/root/.falco/probe.o
invalid filler name: sys_open_by_handle_at_x

This happens for both master branch and this branch, so not related to my change. I do not have experience testing falco's BPF probe, perhaps I would need to try on another supported system?

On which kernel version (clang version) do you test it?

$ clang --version clang version 10.0.0-4ubuntu1 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/bin $ uname -a Linux yoliinyk-ubuntu 5.13.0-40-generic #45~20.04.1-Ubuntu SMP Mon Apr 4 09:38:31 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
I can tell the probe is being built just fine, but I do have trouble testing it. Attempting to load it with sysdig gives me this:
# sysdig --bpf=/root/.falco/probe.o
invalid filler name: sys_open_by_handle_at_x

This happens for both master branch and this branch, so not related to my change. I do not have experience testing falco's BPF probe, perhaps I would need to try on another supported system?

The testing phase, especially for BPF, is often painful :disappointed:  I usually try on different kernels just to be sure that old BPF verifiers do not reject the probe. I think that the best way we have for doing this is the little scap-open example. You can find here some instructions on how to build and run it https://github.com/falcosecurity/libs#test-drivers, but if you have any problems don't hesitate to ask :smile: ! Note in this first phase, I just try to load the probe into the kernel without looking at the syscall parameters.
In a nutshell, this executable allows you to inject the bpf probe or the kernel module and see if it works correctly. If it is able to start without verifier issues we win :laughing:.  I usually test it on Vagrant machines with old kernels like 4.14 (the first supported) or 4.19. Don't worry, obviously we will also test the code in different environments but let's say the more testing we are able to do the better is...
After fighting and winning against BPF and the kernel module, we can finally test if the syscall parameters are correctly caught. You can test them with sysdig as you said, or directly with Falco. It is always a good thing to take a ride on both.
I haven't used sysdig in a while, thanks for pointing this out we'll take a look at it! Once these last changes have been made, we can begin the testing phase. Changing only one parameter shouldn't be too painful but never say never :disappointed_relieved:

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

eb459a6 update(bpf): clean up inode helper function for getting inode numbers

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

I did check with scap-open bpf test and all worked fine in my dev environment. At least this PR does not introduce a failure for 5.13.0-40-generic #45~20.04.1-Ubuntu SMP Mon Apr 4 09:38:31 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux, clang version 10
Tried also testing on another machine I have readily available and it rejected the probe even from the master branch 😢 with the usual verifier nonsense:

math between map_value pointer and register with unbounded min value is not allowed
in filler/sys_mmap_e after a wall of bpf listing. This was on:
Linux ubuntu 5.4.0-87-generic #98~18.04.1-Ubuntu SMP Wed Sep 22 10:45:04 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux, clang version 6.

So, hopefully there is no regression with my change...

I did check with scap-open bpf test and all worked fine in my dev environment. At least this PR does not introduce a failure for 5.13.0-40-generic #45~20.04.1-Ubuntu SMP Mon Apr 4 09:38:31 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux, clang version 10
Tried also testing on another machine I have readily available and it rejected the probe even from the master branch cry with the usual verifier nonsense:

math between map_value pointer and register with unbounded min value is not allowed
in filler/sys_mmap_e after a wall of bpf listing. This was on:
Linux ubuntu 5.4.0-87-generic #98~18.04.1-Ubuntu SMP Wed Sep 22 10:45:04 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux, clang version 6.

Wow, thank you very much! We are near the release and finding this is really important! I will investigate more in detail, but probably is another verifer+clang no sense as you said :rofl:

So, hopefully there is no regression with my change...

Thank you for having tested it! :rocket:

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

022a9f9 Merge branch 'master' into driver-inode-numbers

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yo348: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-libs-arm
e23512cc7304ef88fb481bbf1c9d058c2436102e
link
true
/test build-libs-arm

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yo348: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-libs-arm
e23512cc7304ef88fb481bbf1c9d058c2436102e
link
true
/test build-libs-arm

build-libs-with-chisels
e23512cc7304ef88fb481bbf1c9d058c2436102e
link
true
/test build-libs-with-chisels

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yo348: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-libs-arm
e23512cc7304ef88fb481bbf1c9d058c2436102e
link
true
/test build-libs-arm

build-libs-with-chisels
e23512cc7304ef88fb481bbf1c9d058c2436102e
link
true
/test build-libs-with-chisels

build-libs
e23512cc7304ef88fb481bbf1c9d058c2436102e
link
true
/test build-libs

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yo348: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-libs-arm
e23512cc7304ef88fb481bbf1c9d058c2436102e
link
true
/test build-libs-arm

build-libs-with-chisels
e23512cc7304ef88fb481bbf1c9d058c2436102e
link
true
/test build-libs-with-chisels

build-libs
e23512cc7304ef88fb481bbf1c9d058c2436102e
link
true
/test build-libs

build-libs-minimal
e23512cc7304ef88fb481bbf1c9d058c2436102e
link
true
/test build-libs-minimal

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yo348: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-libs-arm
e23512cc7304ef88fb481bbf1c9d058c2436102e
link
true
/test build-libs-arm

build-libs-with-chisels
e23512cc7304ef88fb481bbf1c9d058c2436102e
link
true
/test build-libs-with-chisels

build-libs
e23512cc7304ef88fb481bbf1c9d058c2436102e
link
true
/test build-libs

build-libs-minimal
e23512cc7304ef88fb481bbf1c9d058c2436102e
link
true
/test build-libs-minimal

build-libs-bundled-deps
e23512cc7304ef88fb481bbf1c9d058c2436102e
link
true
/test build-libs-bundled-deps

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Rebased, squashed commits and resolved conflicts

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, yo348
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 [Andreagit97]

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

/hold

Thanks for the thorough review, @Andreagit97 !

use case for which this inode information is particularly relevant

Without going into too much detail, inode number (combined with device number that was already present) is a good way to track and refer to a file on disk without doing costly string comparisons on filenames.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP, yo348
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 [Andreagit97,FedeDP]

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

/unhold

/test build-libs-bundled-deps


About the BO in action

I wanna know whether the authors release the codes for the animation of the "Bayesian Optimization in Action". This process is really impressive.

please see here:
https://github.com/fmfn/BayesianOptimization/issues/18


[BUG] chat-downloader: command not found

Basic information

Program version: chat-downloader
Python version: Python 3.10.9  - pip 22.3.1
Operating system: OSX 12.6.1

Describe the bug
I successfully installed chat-downloader via pip install chat-downloader, but when I launch it from prompt it shows:  chat-downloader: command not found

You must run it with chat_downloader ...  (_ not -)


entity details table now has word wrap

Description
Text Alignment Issues on Organization Details Page
!vibez
I should have solved this one faster, but tables and CSS are kinda gross sometimes... feeling meh about it
Related Issue/Ticket
https://jira.di2e.net/browse/UOT-134402
Types of changes

[ x ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Optimization (provides speedup with no functional changes)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Smoke testing instructions
Navigate to an Organization Details Page (example: White House) and view the Entity Details – text should be wrapped so that the user can see the full amount of text.
Checklist:

[ ] Documentation updated
[ ] Unit tests added/updated
[ ] Smoke testing relevant to authentication needed
[ ] Clones involved and accounted for
[ ] RDS migrations or other data manipulation necessary
[ ] Dev tools or other infrastructure changed

Need to pull dev into this to fix lint errors. If that doesnt do it then need to find the lint errors using "npm eslint --ext .js --quiet node_app" from inside the backend folder


Integrating a new project with GPUImage3 failed

Hello, I am new to GPUImage3, and I try to integrate GPUImage3 in a completely new Swift project, but it shows some error:

My environment is Xcode 10.1 (10B61).
I only followed the steps in Using GPUImage in a Mac or iOS application in a new created Swift project.
Maybe I should do some extra steps like add "MetalKit" or something?

Same problem in the current examples

I found it only works on real device, not simulator.

Yeah, unfortunately the Simulator does not currently support Metal in the way that this framework needs, so all testing needs to be done on-device and all builds need to target actual hardware. Sorry about that.


⚠ Bofrost.de has degraded performance

In aef23ed, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 829 ms

Resolved: Bofrost.de performance has improved in 78af4f3.


change layer type from MULTIPOLGON to POLYGON to allow inserts

GeoMoose inserts POLYGONs, not MULTIPOLYGONs.  GeoServer fails if the  insert type does not match the data store type.

@brentfraser is this ready for merge? LGTM.

@theduckylittle Yep, it works fine.


fix incorrect buffer size limiting in parquet async writer

Which issue does this PR close?

Closes #4477 .
Rationale for this change

What changes are included in this PR?

Are there any user-facing changes?

I took the liberty of fixing the formatting and removing the force parameter


Post/Put ratings, with some small style changes (sorry large single c…

Description
Implemented customer POST/PUT request for groomer rating and commenting (reviews)
Small style changes.

[ ] This is a bugfix.
[ ] This is a new feature.
[x ] This is part of a feature.

Whoops the API context function isn't running with auth so thats gonna have to be added. forgot


website: new sidebar

Implement new sidebar
https://github.com/chakra-ui/panda/assets/30869823/f886a506-7c5a-416d-a75b-ba7701dd7a49

Thanks for attempting this, @anubra266.
We'll use a subnav under the top bar instead of this sidebar UX. It's on me of course


home: fixes #109, word wrap summary section

This is not ready for merge yet.

@zachlatta Ready for merge.


network: Refactor mod structure and add types for StatusBlock,Network,Subnet,Leaserange

Following PR

Adds types for StatusBlock,Network,Subnet,Leaserange
Refactor network module structure into more generic one.

@Luap99 @mheon PTAL

Can we get some tests for this? We can get test data by writing a little Go program to serialize the Podman types, and then just include the test data - no need to include the Go code in the actual repo.

@mheon Sure could do this. Infact i was just about to start writing some early tests for this. Should tests be part of this PR or seperate PR is fine.

Separate PR is fine

@Luap99 @mheon final review and merge needed on this one.

LGTM


Change channel group of STS classic cluster to stable.

Change channel group of STS classic cluster to stable.

/retest

/retest

/test rosa-sts-advanced-critical-high-presubmit

/test rosa-sts-advanced-critical-high-presubmit

/lgtm

/approve


Adapt to updated spidev kernel 3.15+ API

New fields in spi_ioc_transfer struct: tx_nbits, rx_nbits
New IOCTLs: SPI_IOC_WR_MODE32, SPI_IOC_RD_MODE32 - we are checking for these to determine if the new fields are available in spi_ioc_transfer
see also https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=dc64d39b54c1e9db97a6fb1ca52598c981728157

I've compiled Py-spidev along with this pull request against spidev.h for kernel 3.18.4+ and can confirm that this change appears to not only work, but be essential for Py-spidev to work against this kernel.
The upshot of compiling the existing pypi package is this:
self.spi.xfer([self.instruction_set_template | instruction_set])
IOError: [Errno 22] Invalid argument

While the package, with this PR, works as expected.
I have yet to test this PR against an earlier kernel.


Add Schema.tuple5 - Schema.tuple22

There are implicit def tuple2 all the way up to implicit def tuple4 inside the companion object of Schema. The pattern can be continued all the way up to tuples of size 22.
e.g.:
implicit def tuple5[A, B, C, D, E](implicit a: Schema[A], b: Schema[B], c: Schema[C], d: Schema[D], e: Schema[E]): Schema[(A, B, C, D, E)] = ???

...

implicit def tuple22[A, B, C, ...](...): Schema[(A, B, C, D, ...)] = ???

I would like to work on this


Update TFLite concrete function conversion codes to have the associated

Description
Brief Description of the PR:
Providing trackable objects is now recommended for the users. This makes the
concrete function conversion API be based on the new SavedModel importer, which
will enable new TensorFlow Lite features including variable support, resources
and variant tensor, and signature concept.
Fixes # (issue)
Type of change

[ ] Bug fix
[ ] New Tutorial
[ ] Updated or additional documentation
[ ] Additional Testing
[ ] New Activation and the changes conform to the activation contribution guidelines
[ ] New Callback and the changes conform to the callback contribution guidelines
[ ] New Image addition and the changes conform to the image op contribution guidelines
[ ] New Layer and the changes conform to the layer contribution guidelines
[ ] New Loss and the changes conform to the loss contribution guidelines
[ ] New Metric and the changes conform to the metric contribution guidelines
[ ] New Optimizer and the changes conform to the optimizer contribution guidelines
[ ] New RNN Cell and the changes conform to the rnn contribution guidelines
[V] New Seq2seq addition and the changes conform to the seq2seq contribution guidelines
[ ] New Text addition and the changes conform to the text op contribution guidelines

Checklist:

[V ] I've properly formatted my code according to the guidelines

[ ] By running Black + Flake8
[ ] By running pre-commit hooks

[ ] This PR addresses an already submitted issue for TensorFlow Addons
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] This PR contains modifications to C++ custom-ops

How Has This Been Tested?
If you're adding a bugfix or new feature please describe the tests that you ran to verify your changes:
*

Please take another look :)

Checks are passing now.


test

@conda-grayskull test

Requirements for host
| Current Deps | Grayskull | |
| pip | pip | :heavy_check_mark: |
| python >=3.8 | python >=3.8 | :heavy_check_mark: |
| setuptools >=30.3.0 | setuptools >=30.3.0 | :heavy_check_mark: |
| setuptools-scm | setuptools-scm | :heavy_check_mark: |
Requirements for run
| Current Deps | Grayskull | |
| python >=3.8 | python >=3.8 | :heavy_check_mark: |
| ruamel.yaml >=0.15.3 | ruamel.yaml >=0.15.3 | :heavy_check_mark: |
| ruamel.yaml.jinja2 | ruamel.yaml.jinja2 | :heavy_check_mark: |

Requirements for host

Current Deps
Grayskull

pip
pip
:heavy_check_mark:

python >=3.8
python >=3.8
:heavy_check_mark:

setuptools >=30.3.0
setuptools >=30.3.0
:heavy_check_mark:

setuptools-scm
setuptools-scm
:heavy_check_mark:

Requirements for run

Current Deps
Grayskull

python >=3.8
python >=3.8
:heavy_check_mark:

ruamel.yaml >=0.15.3
ruamel.yaml >=0.15.3
:heavy_check_mark:

ruamel.yaml.jinja2
ruamel.yaml.jinja2
:heavy_check_mark:

Requirements for host

Current Deps
Grayskull

pip
pip
:heavy_check_mark:

python >=3.8
python >=3.8
:heavy_check_mark:

setuptools >=30.3.0
setuptools >=30.3.0
:heavy_check_mark:

setuptools-scm
setuptools-scm
:heavy_check_mark:

Requirements for run

Current Deps
Grayskull

python >=3.8
python >=3.8
:heavy_check_mark:

ruamel.yaml >=0.15.3
ruamel.yaml >=0.15.3
:heavy_check_mark:

ruamel.yaml.jinja2
ruamel.yaml.jinja2
:heavy_check_mark:

Requirements for host

Current Deps
Grayskull

pip
pip
:heavy_check_mark:

python >=3.8
python >=3.8
:heavy_check_mark:

setuptools >=30.3.0
setuptools >=30.3.0
:heavy_check_mark:

setuptools-scm
setuptools-scm
:heavy_check_mark:

pytest

:x:

Requirements for run

Current Deps
Grayskull

python >=3.8
python >=3.8
:heavy_check_mark:

ruamel.yaml >=0.1.0
ruamel.yaml >=0.15.3
:heavy_exclamation_mark:

ruamel.yaml.jinja2
:heavy_plus_sign:

@conda-grayskull test

Working on your request...

Working on your request...

Working on your request...

@conda-grayskull test

Working on your request...

Working on your request...

Command not recognized, please inform a valid command.

@conda-grayskull show requirements

Working on your request...

Working on your request...

Command not recognized, please inform a valid command.

@conda-grayskull show requirements

Working on your request...

Working on your request...

Command not recognized, please inform a valid command.

@conda-grayskull show requirements

Working on your request...

@conda-grayskull show requirements

Working on your request...

Command not recognized, please inform a valid command.

Working on your request...

Command not recognized, please inform a valid command.

@conda-grayskull show requirements

Working on your request...

================ HOST ================
Requirements for host

Current Deps
Grayskull found

pip
pip
:heavy_check_mark:

python >=3.8
python >=3.8
:heavy_check_mark:

setuptools >=30.3.0
setuptools >=30.3.0
:heavy_check_mark:

setuptools-scm
setuptools-scm
:heavy_check_mark:

pytest

:x:

================ RUN ================
Requirements for run

Current Deps
Grayskull found

python >=3.8
python >=3.8
:heavy_check_mark:

ruamel.yaml >=0.1.0
ruamel.yaml >=0.15.3
:heavy_exclamation_mark:

ruamel.yaml.jinja2
:heavy_plus_sign:

@conda-grayskull show requirements

Working on your request...

================ HOST ================
Requirements for host

Current Deps
Grayskull found

pip
pip
:heavy_check_mark:

python >=3.8
python >=3.8
:heavy_check_mark:

setuptools >=30.3.0
setuptools >=30.3.0
:heavy_check_mark:

setuptools-scm
setuptools-scm
:heavy_check_mark:

pytest

:x:

================ RUN ================
Requirements for run

Current Deps
Grayskull found

python >=3.8
python >=3.8
:heavy_check_mark:

ruamel.yaml >=0.1.0
ruamel.yaml >=0.15.3
:heavy_exclamation_mark:

ruamel.yaml.jinja2
:heavy_plus_sign:

@conda-grayskull show requirements

@conda-grayskull show requirements

Working on your request...

================ HOST ================
Requirements for host

Current Deps
Grayskull found

pip
pip
:heavy_check_mark:

python >=3.8
python >=3.8
:heavy_check_mark:

setuptools >=30.3.0
setuptools >=30.3.0
:heavy_check_mark:

setuptools-scm
setuptools-scm
:heavy_check_mark:

pytest

:x:

================ RUN ================
Requirements for run

Current Deps
Grayskull found

python >=3.8
python >=3.8
:heavy_check_mark:

ruamel.yaml >=0.1.0
ruamel.yaml >=0.15.3
:heavy_exclamation_mark:

ruamel.yaml.jinja2
:heavy_plus_sign:

@conda-grayskull show requirements

Working on your request...

================ HOST ================
Requirements for host

Current Deps
Grayskull found

pip
pip
:heavy_check_mark:

python >=3.8
python >=3.8
:heavy_check_mark:

setuptools >=30.3.0
setuptools >=30.3.0
:heavy_check_mark:

setuptools-scm
setuptools-scm
:heavy_check_mark:

pytest

:x:

================ RUN ================
Requirements for run

Current Deps
Grayskull found

python >=3.8
python >=3.8
:heavy_check_mark:

ruamel.yaml >=0.1.0
ruamel.yaml >=0.15.3
:heavy_exclamation_mark:

ruamel.yaml.jinja2
:heavy_plus_sign:

@conda-grayskull show requirements

@conda-grayskull show requirements

@conda-grayskull show requirements

@conda-grayskull show requirements

@conda-grayskull show requirements

@conda-grayskull show requirements

@conda-grayskull show requirements

@conda-grayskull show requirements

Working on your request...

@conda-grayskull show requirements
3 similar comments

Working on your request...

================ HOST ================
Requirements for host

Current Deps
Grayskull found

pip
pip
:heavy_check_mark:

python >=3.8
python >=3.8
:heavy_check_mark:

setuptools >=30.3.0
setuptools >=30.3.0
:heavy_check_mark:

setuptools-scm
setuptools-scm
:heavy_check_mark:

pytest

:x:

================ RUN ================
Requirements for run

Current Deps
Grayskull found

python >=3.8
python >=3.8
:heavy_check_mark:

ruamel.yaml >=0.1.0
ruamel.yaml >=0.15.3
:heavy_exclamation_mark:

ruamel.yaml.jinja2
:heavy_plus_sign:

@conda-grayskull show requirements

Working on your request...

================ HOST ================
Requirements for host

Current Deps
Grayskull found

pip
pip
:heavy_check_mark:

python >=3.8
python >=3.8
:heavy_check_mark:

setuptools >=30.3.0
setuptools >=30.3.0
:heavy_check_mark:

setuptools-scm
setuptools-scm
:heavy_check_mark:

pytest

:x:

================ RUN ================
Requirements for run

Current Deps
Grayskull found

python >=3.8
python >=3.8
:heavy_check_mark:

ruamel.yaml >=0.1.0
ruamel.yaml >=0.15.3
:heavy_exclamation_mark:

ruamel.yaml.jinja2
:heavy_plus_sign:

@conda-grayskull show requirements

Working on your request...

================ HOST ================
Requirements for host

Current Deps
Grayskull found

pip
pip
:heavy_check_mark:

python >=3.8
python >=3.8
:heavy_check_mark:

setuptools >=30.3.0
setuptools >=30.3.0
:heavy_check_mark:

setuptools-scm
setuptools-scm
:heavy_check_mark:

pytest

:x:

================ RUN ================
Requirements for run

Current Deps
Grayskull found

python >=3.8
python >=3.8
:heavy_check_mark:

ruamel.yaml >=0.1.0
ruamel.yaml >=0.15.3
:heavy_exclamation_mark:

ruamel.yaml.jinja2
:heavy_plus_sign:

Working on your request...

Working on your request...

Working on your request...

Working on your request...

================ HOST ================
Requirements for host

Current Deps
Grayskull found

pip
pip
:heavy_check_mark:

python >=3.8
python >=3.8
:heavy_check_mark:

setuptools >=30.3.0
setuptools >=30.3.0
:heavy_check_mark:

setuptools-scm
setuptools-scm
:heavy_check_mark:

pytest

:x:

================ RUN ================
Requirements for run

Current Deps
Grayskull found

python >=3.8
python >=3.8
:heavy_check_mark:

ruamel.yaml >=0.1.0
ruamel.yaml >=0.15.3
:heavy_exclamation_mark:

ruamel.yaml.jinja2
:heavy_plus_sign:

================ HOST ================
Requirements for host

Current Deps
Grayskull found

pip
pip
:heavy_check_mark:

python >=3.8
python >=3.8
:heavy_check_mark:

setuptools >=30.3.0
setuptools >=30.3.0
:heavy_check_mark:

setuptools-scm
setuptools-scm
:heavy_check_mark:

pytest

:x:

================ RUN ================
Requirements for run

Current Deps
Grayskull found

python >=3.8
python >=3.8
:heavy_check_mark:

ruamel.yaml >=0.1.0
ruamel.yaml >=0.15.3
:heavy_exclamation_mark:

ruamel.yaml.jinja2
:heavy_plus_sign:

================ HOST ================
Requirements for host

Current Deps
Grayskull found

pip
pip
:heavy_check_mark:

python >=3.8
python >=3.8
:heavy_check_mark:

setuptools >=30.3.0
setuptools >=30.3.0
:heavy_check_mark:

setuptools-scm
setuptools-scm
:heavy_check_mark:

pytest

:x:

================ RUN ================
Requirements for run

Current Deps
Grayskull found

python >=3.8
python >=3.8
:heavy_check_mark:

ruamel.yaml >=0.1.0
ruamel.yaml >=0.15.3
:heavy_exclamation_mark:

ruamel.yaml.jinja2
:heavy_plus_sign:

================ HOST ================
Requirements for host

Current Deps
Grayskull found

pip
pip
:heavy_check_mark:

python >=3.8
python >=3.8
:heavy_check_mark:

setuptools >=30.3.0
setuptools >=30.3.0
:heavy_check_mark:

setuptools-scm
setuptools-scm
:heavy_check_mark:

pytest

:x:

================ RUN ================
Requirements for run

Current Deps
Grayskull found

python >=3.8
python >=3.8
:heavy_check_mark:

ruamel.yaml >=0.1.0
ruamel.yaml >=0.15.3
:heavy_exclamation_mark:

ruamel.yaml.jinja2
:heavy_plus_sign:

@conda-grayskull show requirements

Working on your request...

Working on your request...

Working on your request...

Working on your request...

Working on your request...

================ HOST ================
Requirements for host

Current Deps
Grayskull found

pip
pip
:heavy_check_mark:

python >=3.8
python >=3.8
:heavy_check_mark:

setuptools >=30.3.0
setuptools >=30.3.0
:heavy_check_mark:

setuptools-scm
setuptools-scm
:heavy_check_mark:

pytest

:x:

================ RUN ================
Requirements for run

Current Deps
Grayskull found

python >=3.8
python >=3.8
:heavy_check_mark:

ruamel.yaml >=0.1.0
ruamel.yaml >=0.15.3
:heavy_exclamation_mark:

ruamel.yaml.jinja2
:heavy_plus_sign:

================ HOST ================
Requirements for host

Current Deps
Grayskull found

pip
pip
:heavy_check_mark:

python >=3.8
python >=3.8
:heavy_check_mark:

setuptools >=30.3.0
setuptools >=30.3.0
:heavy_check_mark:

setuptools-scm
setuptools-scm
:heavy_check_mark:

pytest

:x:

================ RUN ================
Requirements for run

Current Deps
Grayskull found

python >=3.8
python >=3.8
:heavy_check_mark:

ruamel.yaml >=0.1.0
ruamel.yaml >=0.15.3
:heavy_exclamation_mark:

ruamel.yaml.jinja2
:heavy_plus_sign:

================ HOST ================
Requirements for host

Current Deps
Grayskull found

pip
pip
:heavy_check_mark:

python >=3.8
python >=3.8
:heavy_check_mark:

setuptools >=30.3.0
setuptools >=30.3.0
:heavy_check_mark:

setuptools-scm
setuptools-scm
:heavy_check_mark:

pytest

:x:

================ RUN ================
Requirements for run

Current Deps
Grayskull found

python >=3.8
python >=3.8
:heavy_check_mark:

ruamel.yaml >=0.1.0
ruamel.yaml >=0.15.3
:heavy_exclamation_mark:

ruamel.yaml.jinja2
:heavy_plus_sign:

================ HOST ================
Requirements for host

Current Deps
Grayskull found

pip
pip
:heavy_check_mark:

python >=3.8
python >=3.8
:heavy_check_mark:

setuptools >=30.3.0
setuptools >=30.3.0
:heavy_check_mark:

setuptools-scm
setuptools-scm
:heavy_check_mark:

pytest

:x:

================ RUN ================
Requirements for run

Current Deps
Grayskull found

python >=3.8
python >=3.8
:heavy_check_mark:

ruamel.yaml >=0.1.0
ruamel.yaml >=0.15.3
:heavy_exclamation_mark:

ruamel.yaml.jinja2
:heavy_plus_sign:

================ HOST ================
Requirements for host

Current Deps
Grayskull found

pip
pip
:heavy_check_mark:

python >=3.8
python >=3.8
:heavy_check_mark:

setuptools >=30.3.0
setuptools >=30.3.0
:heavy_check_mark:

setuptools-scm
setuptools-scm
:heavy_check_mark:

pytest

:x:

================ RUN ================
Requirements for run

Current Deps
Grayskull found

python >=3.8
python >=3.8
:heavy_check_mark:

ruamel.yaml >=0.1.0
ruamel.yaml >=0.15.3
:heavy_exclamation_mark:

ruamel.yaml.jinja2
:heavy_plus_sign:

@conda-grayskull show requirements

Working on your request...

Working on your request...

Working on your request...

Working on your request...

Working on your request...

================ HOST ================
Requirements for host

Current Deps
Grayskull found

pip
pip
:heavy_check_mark:

python >=3.8
python >=3.8
:heavy_check_mark:

setuptools >=30.3.0
setuptools >=30.3.0
:heavy_check_mark:

setuptools-scm
setuptools-scm
:heavy_check_mark:

pytest

:x:

================ RUN ================
Requirements for run

Current Deps
Grayskull found

python >=3.8
python >=3.8
:heavy_check_mark:

ruamel.yaml >=0.1.0
ruamel.yaml >=0.15.3
:heavy_exclamation_mark:

ruamel.yaml.jinja2
:heavy_plus_sign:

================ HOST ================
Requirements for host

Current Deps
Grayskull found

pip
pip
:heavy_check_mark:

python >=3.8
python >=3.8
:heavy_check_mark:

setuptools >=30.3.0
setuptools >=30.3.0
:heavy_check_mark:

setuptools-scm
setuptools-scm
:heavy_check_mark:

pytest

:x:

================ RUN ================
Requirements for run

Current Deps
Grayskull found

python >=3.8
python >=3.8
:heavy_check_mark:

ruamel.yaml >=0.1.0
ruamel.yaml >=0.15.3
:heavy_exclamation_mark:

ruamel.yaml.jinja2
:heavy_plus_sign:

================ HOST ================
Requirements for host

Current Deps
Grayskull found

pip
pip
:heavy_check_mark:

python >=3.8
python >=3.8
:heavy_check_mark:

setuptools >=30.3.0
setuptools >=30.3.0
:heavy_check_mark:

setuptools-scm
setuptools-scm
:heavy_check_mark:

pytest

:x:

================ RUN ================
Requirements for run

Current Deps
Grayskull found

python >=3.8
python >=3.8
:heavy_check_mark:

ruamel.yaml >=0.1.0
ruamel.yaml >=0.15.3
:heavy_exclamation_mark:

ruamel.yaml.jinja2
:heavy_plus_sign:

================ HOST ================
Requirements for host

Current Deps
Grayskull found

pip
pip
:heavy_check_mark:

python >=3.8
python >=3.8
:heavy_check_mark:

setuptools >=30.3.0
setuptools >=30.3.0
:heavy_check_mark:

setuptools-scm
setuptools-scm
:heavy_check_mark:

pytest

:x:

================ RUN ================
Requirements for run

Current Deps
Grayskull found

python >=3.8
python >=3.8
:heavy_check_mark:

ruamel.yaml >=0.1.0
ruamel.yaml >=0.15.3
:heavy_exclamation_mark:

ruamel.yaml.jinja2
:heavy_plus_sign:

================ HOST ================
Requirements for host

Current Deps
Grayskull found

pip
pip
:heavy_check_mark:

python >=3.8
python >=3.8
:heavy_check_mark:

setuptools >=30.3.0
setuptools >=30.3.0
:heavy_check_mark:

setuptools-scm
setuptools-scm
:heavy_check_mark:

pytest

:x:

================ RUN ================
Requirements for run

Current Deps
Grayskull found

python >=3.8
python >=3.8
:heavy_check_mark:

ruamel.yaml >=0.1.0
ruamel.yaml >=0.15.3
:heavy_exclamation_mark:

ruamel.yaml.jinja2
:heavy_plus_sign:

@conda-grayskull show requirements

Working on your request...

Working on your request...

Working on your request...

Working on your request...

It was not possible to process your request, please open a bug in roboto repository with a link to this PR.

It was not possible to process your request, please open a bug in roboto repository with a link to this PR.

It was not possible to process your request, please open a bug in roboto repository with a link to this PR.

It was not possible to process your request, please open a bug in roboto repository with a link to this PR.

@conda-grayskull show requirements

@conda-grayskull show requirements

Working on your request...

Working on your request...

Working on your request...

Working on your request...

Working on your request...

================ HOST ================
Requirements for host

Current Deps
Grayskull found

pip
pip
:heavy_check_mark:

python >=3.8
python >=3.8
:heavy_check_mark:

setuptools >=30.3.0
setuptools >=30.3.0
:heavy_check_mark:

setuptools-scm
setuptools-scm
:heavy_check_mark:

pytest

:x:

================ RUN ================
Requirements for run

Current Deps
Grayskull found

python >=3.8
python >=3.8
:heavy_check_mark:

ruamel.yaml >=0.1.0
ruamel.yaml >=0.15.3
:heavy_exclamation_mark:

ruamel.yaml.jinja2
:heavy_plus_sign:

================ HOST ================
Requirements for host

Current Deps
Grayskull found

pip
pip
:heavy_check_mark:

python >=3.8
python >=3.8
:heavy_check_mark:

setuptools >=30.3.0
setuptools >=30.3.0
:heavy_check_mark:

setuptools-scm
setuptools-scm
:heavy_check_mark:

pytest

:x:

================ RUN ================
Requirements for run

Current Deps
Grayskull found

python >=3.8
python >=3.8
:heavy_check_mark:

ruamel.yaml >=0.1.0
ruamel.yaml >=0.15.3
:heavy_exclamation_mark:

ruamel.yaml.jinja2
:heavy_plus_sign:

================ HOST ================
Requirements for host

Current Deps
Grayskull found

pip
pip
:heavy_check_mark:

python >=3.8
python >=3.8
:heavy_check_mark:

setuptools >=30.3.0
setuptools >=30.3.0
:heavy_check_mark:

setuptools-scm
setuptools-scm
:heavy_check_mark:

pytest

:x:

================ RUN ================
Requirements for run

Current Deps
Grayskull found

python >=3.8
python >=3.8
:heavy_check_mark:

ruamel.yaml >=0.1.0
ruamel.yaml >=0.15.3
:heavy_exclamation_mark:

ruamel.yaml.jinja2
:heavy_plus_sign:

================ HOST ================
Requirements for host

Current Deps
Grayskull found

pip
pip
:heavy_check_mark:

python >=3.8
python >=3.8
:heavy_check_mark:

setuptools >=30.3.0
setuptools >=30.3.0
:heavy_check_mark:

setuptools-scm
setuptools-scm
:heavy_check_mark:

pytest

:x:

================ RUN ================
Requirements for run

Current Deps
Grayskull found

python >=3.8
python >=3.8
:heavy_check_mark:

ruamel.yaml >=0.1.0
ruamel.yaml >=0.15.3
:heavy_exclamation_mark:

ruamel.yaml.jinja2
:heavy_plus_sign:

================ HOST ================
Requirements for host

Current Deps
Grayskull found

pip
pip
:heavy_check_mark:

python >=3.8
python >=3.8
:heavy_check_mark:

setuptools >=30.3.0
setuptools >=30.3.0
:heavy_check_mark:

setuptools-scm
setuptools-scm
:heavy_check_mark:

pytest

:x:

================ RUN ================
Requirements for run

Current Deps
Grayskull found

python >=3.8
python >=3.8
:heavy_check_mark:

ruamel.yaml >=0.1.0
ruamel.yaml >=0.15.3
:heavy_exclamation_mark:

ruamel.yaml.jinja2
:heavy_plus_sign:

@conda-grayskull show requirements

Working on your request...


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 2629 ms

Resolved: Bofrost.at performance has improved in abde8aa.


[codemod] Update import paths for svg-icons v1

Codemod to switch v0 Material-UI svg-icons to material-ui-icons package. Updates the import paths from material-ui/svg-icons/<category>/<icon-name> to material-ui-icons/<IconName>.

[x] PR has tests
[x] PR docs demo, and is linted.
[x] Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
[x] Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).

Codecov Report

Merging #8333 into v1-beta will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           v1-beta    #8333   +/-   ##
========================================
  Coverage    99.42%   99.42%
========================================
  Files          149      149
  Lines         2256     2256
========================================
  Hits          2243     2243
  Misses          13       13

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 2361339...4056be1. Read the comment docs.

I have been adding a small migration guide to be continued in the documentation. I'm gonna definitely tweet about your codemods once we release v1.0.0-beta.12 ❤!

Wow thanks! This is amazing because these are my first open source contributions. Feels great 🎉..!


feat: drop cascade & restrict

New feature: DROP TABLE tableName RESTRICT; and DROP TABLE tableName CASCADE;.
Usage:
  sql, _, err = bob.DropTable("users").Cascade().ToSql()
  if err != nil {
    log.Fatal(err)
  }
  // sql = "DROP TABLE users CASCADE;"
  sql, _, err = bob.DropTable("users").Restrict().ToSql()
  if err != nil {
    log.Fatal(err)
  }
  // sql = "DROP TABLE users RESTRICT;"

Closes #5

Codecov Report

Merging #7 (8a461fe) into master (efa752f) will decrease coverage by 2.13%.
The diff coverage is 71.42%.

@@             Coverage Diff             @@
##            master       #7      +/-   ##
===========================================
- Coverage   100.00%   97.86%   -2.14%
===========================================
  Files            8        9       +1
  Lines          263      281      +18
===========================================
+ Hits           263      275      +12
- Misses           0        6       +6

Impacted Files
Coverage Δ

internal.go
45.45% <45.45%> (ø)

drop.go
100.00% <100.00%> (ø)

has.go
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Create phmetropol

Added Professionshøjskolen Metropol
(student emails:  @phmetropol.dk)

http://www.phmetropol.dk/English
Metropolitan University College

@MortenDHansen Could you please rename lib/domains/dk/phmetropol to lib/domains/dk/phmetropol.txt to reflect this repository rules? Thank you!

Damn. How could I fail to follow such a simple convention...
Fixed. Sorry :)


Decomposable folding test with Keccak steps

Work in progress, the test does nothing for now.
As part of this PR I realized of a few things that needed to be implemented for the tests to succeed with our current design:

Further From implementations needed to happen so that our zkVM expressions (E<F> which are actually Operations<ExprInner<Operations<ConstantExprInner<F>>, Column>>
If we want to keep using generic columns inside the constraints returned by the zkVM interpreters (which we did in order to be able to use the generic prover) then we must adapt the folding structs accordingly so that they work over the generic columns instead of the aliases for each circuit. This means I had to implement some other traits for it.

Note:
We have Operations<ExprInner<Operations<ConstantExprInner<F>>, Column>> because we define:
type E<F> = Operations<ExprInner<ConstantExpr<F>, Column>>
And ConstantExpr<F> is also defined using the Operations type, because we can make operations on constant terms like add, mul, etc.

I'm making this PR ready if you agree @querolita. I will merge this PR https://github.com/o1-labs/proof-systems/pull/2154/ into this one. I need some of your changes for https://github.com/o1-labs/proof-systems/pull/2146


Can't get my observableArray value to update when selecting items

Is this binding supposed to update my observableArray property when i select new items from my select2 list?
I am using a multi-select dropdown, but my viewmodel is never updated.
I can' see anywhere in this binding which would update the observable property, or is this done somewhere else?

Sorry for the delay... didn't see this question until now.
This binding applies select2 to an existing select element.  Knockout select bindings can be used to observe changes.
I suggest making your code work with vanilla knockout only on a multiselect select element.  Then once everything works as expected, add select2 binding without removing the other bindings.


Sign in by Google and Facebook.

Describe the feature you'd like
Adding Sign in with Google and Facebook options.

@subham-paul Would you like to work on this issue ?

i would like to work on this issue
can u assign me this

ok @naqeeb2710  you can work on this

Is there any activity on this
As I also want to try hands on this

Is there any activity on this
As I also want to try hands on this

yes you can!


Calculate a custom tip: Android Basics with Compose

URL of codelab
6. Add a switch - Step 5
It says:
"This table contains information about these parameters, which are the same parameters that you defined for the RoundTheTipRow() function:"
But at this point those parameters are not defined in the RounTheTipRow() function, they get defined a couple steps below at step 7

@willprada
Thank you for reaching out to us.
This is fixed and will be published soon.


Adding support for Timestamps in type inference

Adds support for timestamps and adds some unit tests.
closes #130

Current coverage is 87.32%

Merging #133 into master will increase coverage by +0.15% as of e8d1d1b

@@            master    #133   diff @@
======================================
  Files           10      10
  Stmts          413     418     +5
  Branches       125     127     +2
  Methods          0       0
======================================
+ Hit            360     365     +5
  Partial          0       0
  Missed          53      53

Review entire Coverage Diff as of e8d1d1b

Powered by Codecov. Updated on successful CI builds.

@brkyvz would you please take a look at this one too?

LGTM. Just a couple questions

Thanks @brkyvz


Implement GApplication:shutdown so a Flutter developer knows where to put code that should occur on application shutdown.

This was added because the dispose method doesn't seem to be called - something must still have a reference to the application after shutdown.
Solution for https://github.com/flutter/flutter/issues/136582

It looks like there is still a fix for the dispose method required, but this is possibly still useful for developers who need to do something when the application stops. Dispose should be used for cleaning up objects, and shutdown for any more complex behaviour.

Filed https://github.com/flutter/flutter/issues/136783 as a low priority tracking issue for a migration, for convenience.


Fix normalize path issue on Windows

Resolves https://github.com/AdoptOpenJDK/openjdk-systemtest/issues/243
Signed-off-by<EMAIL_ADDRESS><EMAIL_ADDRESS>

Tested using internal Jenkins builds (links sent to reviewer on slack).


Generate multiple rust unit tests for each .sky test

Debugging interpreter crashes in tests is somewhat inconvenient:
when tests panics, there's only a stack trace, but no information
which test failed.
This commit fixes the issue to some degeree: now each test (separated
by ---) is now a separate Rust test case.
Generated test code now looks like this:
https://gist.github.com/stepancheg/c68a83f8a0e5309ad8cec8ad4283658a

Fixed diagnostics offset


Adding ODF 1.3 support to the ODF Toolkit

I have started a branch of the 0.9.0 version to support ODF 1.3.
but decided in discussions with Michael Stahl and Oliver Rau afterwards that it might be easier to have an ODF 1.3 support based solely on the upcoming ODF 1.0.0 version.
The reason for this is that 1.0.0 is the merge of a several-year-old merge form Open-XChange using ODFDOM for their backend of their new OX Documents.
In the following, I am starting a listing what needs to be fixed - this is likely being updated during the lifetime of this issue.
This documentation should be added to our SITE documentation to describe how to do an ODF version change in the future.
Changes expected so far:

The generator project needs to generate new ODFDOM typed DOM classes from the new ODF XML schema/grammar files. These files need to replace the ODFDOM prior classes for elements and attributes.

The generator tests have to be adopted to embrace ODF 1.3.

The ODF Validator needs to have an ODF 1.3 instead of an ODF 1.2 option.

The ODF templates within ODFDOM - being used when creating new documents from the scratch needs to be added to ODF 1.3.
I did this usually by editing the XML within the ZIP using JEdit with its archive and its XML extension.

NOTE: The current ODF 1.3 branch based on the master will be abandoned and new ODF 1.3 branch will be created for the 1.0.0 release branch.

There are 36 new feature/enhancement in ODF 1.3.
They are described in detail in the OASIS JIRA bugtracker, there is a query for ODF 1.3 feature/enhancment.
An overview of the changes from “Open Document Format for Office Applications (OpenDocument) v1.2”
can be found in the end/appendix of each ODF 1.3 specification part:

Part 2: Packages
Part 3: OpenDocument Schema
Part 4: Recalculated Formula (OpenFormula) Format

PS: I am about to start a GitHub for the OASIS TC to bundle tools for the specification & test documents at OASIS standard level.


Drop shadows

Drop shadow effect for Lightning 3.0.
Lightning 2.x does not support Drop shadow shaders for all nodes, this is only available on text through the Canvas2D shadow functionality.
Does Lightning 3.0 need the same just for text? Or do we want to enable drop shadows for all node types?

I'd vote for all node types to have some support for drop shadow. Text drop shadows would be nice too.

I needed support for drop shadow for all nodes (cards, buttons, avatars, raised list/buttons, dropdown). I rarely need drop shadow for text. As a workaround, I use images, but it's hard to customize and maintain


add tmpDirHackContainer

fix: #1517

Hi @eumel8, I fixed the CI in the latest iteration and it can be activated using the SecurityContext.readOnlyRootFilesystem field.
Could you please confirm if it works for your use case as well?

@OverOrion Yeah, many thanks. I looked also in e2e/volumedrain but I couldn't found the issue.
I tested and can confirm, it's working as expected.


Append module code and name as a single header

Codecov Report

Merging #120 into refactor-ui will increase coverage by 0.01%.
The diff coverage is 0.00%.

@@                Coverage Diff                @@
##             refactor-ui     #120      +/-   ##
=================================================
+ Coverage          46.69%   46.71%   +0.01%
  Complexity           502      502
=================================================
  Files                126      126
  Lines               2452     2451       -1
  Branches             301      301
=================================================
  Hits                1145     1145
+ Misses              1209     1208       -1
  Partials              98       98

Impacted Files
Coverage Δ
Complexity Δ

...rc/main/java/trackitnus/ui/module/ModulePanel.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

Continue to review full report at Codecov.

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


cache/in-memory: use dashmap where possible

Use DashMap instead of mutexed hashmaps. This means that most operations will no longer be locking. The current user is still behind a mutex since it's a single object, but this isn't too bad since it's so infrequently accessed.

might be worth getting rid of the current user lock and just making that a once cell?

The current user can be updated again, it'd be more worth it to do Arc<Option<CurrentUser>>

But then we'd have to have mutability, so that's not an option