ErrorException: Argument 2 passed to Illuminate\Database\Schema\Blueprint::build() must be an instance of Illuminate\Database\Schema\Grammars\Grammar

I'm using  the MongoDB v3.4.4 with the latest Laravel v5.4.* I'm getting the following exception while unit testing only.
note: api's working fine with mongodb
ErrorException: Argument 2 passed to Illuminate\Database\Schema\Blueprint::build() must be an instance of Illuminate\Database\Schema\Grammars\Grammar, null given, called in laravel5.4/vendor/laravel/framework/src/Illuminate/Database/Schema/Builder.php on line 239 and defined
Sample model code
//this is for mongodb
use Jenssegers\Mongodb\Eloquent\Model as Eloquent;

class Profile extends Eloquent
{
    protected $collection = 'profile';
    protected $connection = 'mongodb';
}

Sample unit testcase class
use Illuminate\Support\Facades\Artisan;
use Illuminate\Foundation\Testing\DatabaseMigrations;

class ProfileApiTest extends TestCase
{
    use DatabaseMigrations;

    public function setUp()
    {
        parent::setUp();
        Artisan::call('migrate:refresh');
        Artisan::call('db:seed');
    }
}

Artisan::call('migrate:refresh'); fails with above ErrorException
what I'm doing wrong here?
Thanks

At the migration file, do you have "use Jenssegers\Mongodb\Schema\Blueprint;" ?

@nahueJ
Sorry for late replay
in migration file i am using this use Illuminate\Database\Schema\Blueprint;

I had the same error, i've gave up. I deleted the project, dropped the DB, clone again the repository i was working with, i run a fresh composer install and a fresh php artisan migrate.
I'm sorry that i can't be more helpful.

Quoting:
"I think it is better to replace dropIfExists with drop in your migrations or implement the dropIfExists logic using drop and hasCollection method like @MightyPork in your migrations."
Basically the problem is in dropIfExists function.

I was able to solve the issue with the following in my migration classes:
`<?php
use Illuminate\Database\Migrations\Migration;
use Jenssegers\Mongodb\Schema\Blueprint;
class CreateUsersTable extends Migration
{
/**
* Run the migrations.
*
* @return void
*/
public function up()
{
Schema::table('users', function (Blueprint $collection) {
$collection->index('email');
});
}
/**
 * Reverse the migrations.
 *
 * @return void
 */
public function down()
{
    Schema::table('users', function (Blueprint $collection) {
        $collection->drop();
    });
}

}
Notice the$collection->drop();for whatever reason, it seems to completely ignore$collection->dropIfExists();` but I've done enough for one day haha.
The above results in all greens on the following test (with DatabaseMigrations):
`<?php
namespace Tests\Unit\User;
use App\Models\User;
use Illuminate\Database\Eloquent\Collection;
use Tests\TestCase;
use Illuminate\Foundation\Testing\DatabaseMigrations;
class UserTest extends TestCase
{
use DatabaseMigrations;
public function setUp()
{
    parent::setUp();

    $this->user = create(User::class);
}

/** @test */
public function a_user_has_players()
{
    $this->assertInstanceOf(Collection::class, $this->user->players);
}

}
`

Make sure to remove the other default 'user' and 'password_resets' migrations if you are not using them when testing this. It will conflict with the normal way the migration rollback works i think.
<?php

use Illuminate\Support\Facades\Schema;
use Illuminate\Database\Migrations\Migration;
use Illuminate\Support\Facades\DB;
use Jenssegers\Mongodb\Schema\Blueprint;

class AddSomeVoters extends Migration
{
    /**
     * Run the migrations.
     *
     * @return void
     */
    public function up()
    {
        // Create the collection voter and make emails unique.
        Schema::create('voter', function(Blueprint $collection)
        {
            $collection->unique('email');
        });

        $voters =[
            // Add the stickers in the same document since there are a limited amount and its less database calls.
            // Had to add the non_dups to keep the emails field unique but still accessible within the same document.
            ['_id' => 'love',      'path' => '/assets/images/love.png','email' => 'non_dup_1'],
            ['_id' => 'do_good',   'path' => '/assets/images/doGood.png','email' => 'non_dup_2'],
            ['_id' => 'unite',     'path' => '/assets/images/unite.png','email' => 'non_dup_3'],
            ['_id' => 'rise',      'path' => '/assets/images/rise.png','email' => 'non_dup_4'],

            // Creating a few test emails.
            ['email' =><EMAIL_ADDRESS>      'sticker_id'  =>  'love'],
            ['email' =><EMAIL_ADDRESS>               'sticker_id'  =>  'do_good'],
            ['email' =><EMAIL_ADDRESS>                 'sticker_id'  =>  'love'],
            ['email' =><EMAIL_ADDRESS>               'sticker_id'  =>  'rise']
        ];

        // Insert them into mongodb database.
        DB::connection('mongodb')->collection('voter')->insert($voters);

    }

     /**
     * Reverse the migrations.
     *
     * @return void
     */
    public function down()
    {
        Schema::drop('voter');
    }
}

This worked perfectly for me.
FIRST TIME MIGRATION.
php artisan migrate
Migration table created successfully.
Migrating: 2017_07_16_211153_add_some_voters
Migrated:  2017_07_16_211153_add_some_voters

php artisan migrate:rollback
Rolling back: 2017_07_16_211153_add_some_voters
Rolled back:  2017_07_16_211153_add_some_voters

DOING THE MIGRATION AGAIN AFTER DOCUMENT WAS CREATED:
php artisan migrate
Migrating: 2017_07_16_211153_add_some_voters
Migrated:  2017_07_16_211153_add_some_voters

Still working.

I have deleted the default migration provided by laravel
and created a new users migration file
use Illuminate\Support\Facades\Schema;
use Jenssegers\Mongodb\Schema\Blueprint;
use Illuminate\Database\Migrations\Migration;
use Illuminate\Support\Facades\DB;
class CreateUserCollection extends Migration
{
/**
* Run the migrations.
*
* @return void
*/
public function up()
{
Schema::create('users', function (Blueprint $collections) {
$collections->increments('id');
$collections->string('name');
$collections->string('email')->unique();
$collections->string('password');
});
}
/**
 * Reverse the migrations.
 *
 * @return void
 */
public function down()
{
    Schema::dropIfExists('users');
}

}
but still
root@system3:/var/www/html/mongolaravel/jen/laravel# php artisan migrate:rollback
In Blueprint.php line 83:
Type error: Argument 2 passed to Illuminate\Database\Schema\Blueprint::build() must be an instance of Illuminate\Database\Schema\Grammars\Grammar
, null given, called in /var/www/html/mongolaravel/jen/laravel/vendor/laravel/framework/src/Illuminate/Database/Schema/Builder.php on line 252

try replace Schema::dropIfExists() with Schema::drop()


This page should be removed

This page points at resources that (as far as I can tell) do not exist.
https://docs.microsoft.com/en-us/azure/bot-service/bot-service-debug-adaptive-tools?view=azure-bot-service-4.0

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

ID: c8117ef4-d878-652f-8fc0-b60000fea3f1
Version Independent ID: 396ae831-70df-a000-6a29-f560e096dcdb
Content: Debug bots using Bot Framework Adaptive Tools - Bot Service
Content Source: articles/bot-service-debug-adaptive-tools.md
Service: bot-service
GitHub Login: @JonathanFingold
Microsoft Alias: iawilt

@clearab - Given that the extension is available still for VS Code, I'm inclined to fix the one broken link, have the applicable content migrate to the Composer docs, and then retire this article with a redirect to the Composer docs.

[x] Fix links. (PR 2971)
[ ] Port content to Composer.
[ ] Retire SDK doc.

Plans change. Will close this issue as resolved and address refactoring of articles later.


Add background to FeedItem

Kind (Required)

Improvement

Overview (Required)

It's hard to see the preview now because the background isn't colored.
You can improve it by using AppThemeWithBackground(), so please try it.

Links

https://github.com/DroidKaigi/conference-app-2021/blob/efda223b22ac510b5ec4e6c53b1a2df98264d629/uicomponent-compose/main/src/main/java/io/github/droidkaigi/feeder/DrawerContent.kt#L207

✋

Thanks! Assigned 👍


Add compact variant to Interaction states

Ready for review @lucasveil

Ready for review @lucasveil

Good to go @BirteThornquist

Good to go @BirteThornquist


Custom stems/arrows?

Is it possible to have easy option to modify the stems/arrows (size, direction, etc) of the tooltips?
Something like this:

Hi, no, it wouldn't be easy to do this. In v4, you can edit the css to create the tooltip you showed on the right, but the other two are probably too complex to do right in html-css. A solution based on canvas would be more appropriate, but we don't do that at all in Tooltipster.

Thanks for the quick reply. So there are no plans to have any sort of canvas support for Tooltipster?

No, there are none.

Or I should say that you may build your own display plugin for Tooltipster v4 that will use canvas, but we will not do this ourselves.


Configuring for PIA

Hello,
I used to work with Mullvad port forwarding, but they will stop supporting it soon.
has anyone manage to configure this project with PIA ?

Hello,
I used to work with Mullvad port forwarding, but they will stop supporting it soon.
has anyone manage to configure this project with PIA ?

This link can be found in the repo.
https://helpdesk.privateinternetaccess.com/kb/articles/manual-connection-and-port-forwarding-scripts-for-linux
Have you followed it?

Not yet
It’s much more complex than for Mullvad and the config you did in this repo 😅
I think I will first try a 3rd party tool: https://github.com/jdelkins/pia-tools

If you find a simple solution I’d be happy to link to this issue with the solution.

For those using ProtonVPN and want to open port there is now a Docker mod to achieve this.
https://github.com/jordanpotter/docker-mods


New load_csr() in apps.c simplifiying req, x509, and ca apps and allowing DER input to ca

New helper function X509_REQ *load_csr(const char *file, int format, const char *desc)
in apps/apps.c simplifying and generalizing CSR loading in req.c, x509.c, and ca.c.
Moreover, new -inform and -certform CLI options to ca app now allowing DER input.
Tested with DER (rather than PEM) CSR input format in 80-test_ca.t.

Checklist

[x] documentation is added or updated
[x] tests are added or updated

@bernd-edlinger, thanks for your review and comments.
Indeed the output in case of unsupported format could be more helpful. I've now done this not only for load_csr() but also for other file loading functions, introducing helper functions format2str() and print_format_error().
Doing so, I found that the use of the desc / descrip string parameter was a bit inconsistent, with some functions having it and similar other functions not; so I added it where missing.
Moreover, when using this parameter, no checks had been done whether it is NULL, so I added such guards. This leads to the nice extra feature that error printing on file loading can be suppressed, which can be very handy for instance when trying to load files using differenct formats until (hopefully) this succeeds.

Nice work, @DDvO

Hmm, it looks like the Travis CI build https://travis-ci.org/openssl/openssl/jobs/321919199 failed due to some Debian package (update) issue?

At this point, I think we need to post-pone this PR to be post-1.1.1, as it's very much an added features thing.
Also, I'm thinking that this kind of change should really make use of the OSSL_STORE API.

I've meanwhile rebased also this PR such that we can hopefully integrate it with #11470 soon.
Travis CI went fine (while the AppVeyor runs are still queued, but I don't expect problems there).
Anything concrete that I can quickly improve?

Hopefully nobody depends on exact wording (and case) for the error messages in scripts.
Could you please amend the commit message of the last commit so the subject is shorter and you add description of the changes in message body.

Hopefully nobody depends on exact wording (and case) for the error messages in scripts.

It would be pretty unwise to do so.
This is not the first time error messages are adapted.

Could you please amend the commit message of the last commit so the subject is shorter and you add description of the changes in message body.

Sure - done.
I anyway plan to partly squash and reword the commit messages ones the changes are stable.

I think if CI passes this could be approved unless you plan further changes.

Pleased to hear. I don't plan to do further changes unless request by a review.
Then let's just wait for the CI checks and in the meantime I'll prepare the cleanup for the commit structure and comments...

Since Travis CI went fine I've already updated the PR to the final commit structure I propose.

24 hours has passed since 'approval: done' was set, but this PR has failing CI tests.  Once the tests pass it will get moved to 'approval: ready to merge' automatically, alternatively please review and set the label manually.

For some reason AppVeyor is still queued on this PR (and others as well) since about two days,
and as far as I recall it already went fine earlier on this PR.
So I've just manually marked this "ready to merge" and will do the merge now...

Merged - thanks @t8m for your swift review!


Articles not rendered properly in reader view

In safari and pocket.

https://github.com/wellcometrust/wellcomecollection.org/pull/2918


[OSDEV-1004] Update the SQL for gathering data and modify the facility schema to follow the target specification.

[OSDEV-1004] Update the SQL for gathering data and modify the facility schema to follow the target specification.
The following changes have been made to the Logstash and OpenSearch services:

Prepared the SQL script to collect all the necessary data for the v1/facilities API endpoint according to the new API specification. Agreed upon and established a prioritization scale for gathering data related to the name, address, sector, parent_company, product_type, facility_type, processing_type, number_of_workers and location fields as follows:

Data from the approved claim.
Promoted matches (considered as promoted facility list items).
The most recently contributed data.
For the country field, the same prioritization scale has been utilized except for 'Data from the approved claims' because the claimant cannot update the country in any way.

Introduced a new set of Ruby scripts to filter and reorganize the incoming data at the Logstash app level, avoiding complex database queries that could lead to high database load.
Updated the facilities index template for OpenSearch to define how new fields within the facility documents are stored and indexed by OpenSearch.
Set up the main Logstash pipeline to run every 15 minutes(agreed with stakeholders).

All changes have been made to meet the API specification requirements for v1/facilities API endpoint as closely as possible.

In general LGTM, didn't see code changes issue directly. Waiting for final version if code changes (without Draft).

In general LGTM, didn't see code changes issue directly. Waiting for final version if code changes (without Draft).

Thank you, Roman! I need to make some changes. I will let you know when it is ready.

Set up the main Logstash pipeline to run every 15 minutes(agreed with stakeholders).

Could you explain the intention of this?

Set up the main Logstash pipeline to run every 15 minutes(agreed with stakeholders).

Could you explain the intention of this?

To avoid overloading the database with frequent requests, we decided to set a 15-minute gap between each refresh of OpenSearch. Based on Mariel's explanation, this will be sufficient for now since there is no need for facilities to appear in the search in real time.


Heroku deploy

Codecov Report

Merging #6 (91eea8a) into main (9f9b122) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #6   +/-   ##
=======================================
  Coverage   64.00%   64.00%
=======================================
  Files           2        2
  Lines         100      100
=======================================
  Hits           64       64
  Misses         28       28
  Partials        8        8

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


i

When asking a question please also include where you looked for an answer (so we can update the documentation if needed).

Invalid question.


Closes #20 : Group rules into few categories by priority

Group rules into few categories by priority, disable rules that contradicts standards or falls into discussable "other" category (these may come back after discussed), change psr2 to psr12 (psr12 includes compatible part of psr2, psr2 is deprecated as of 2019-08-10).

Check out #25 on Closes.

Please add new lines at the end of files.

PSR2:

All PHP files MUST end with a single blank line.

As of 2019-08-10 PSR-2 has been marked as deprecated. PSR-12 is now recommended as an alternative.

PSR12:

This specification extends, expands and replaces PSR-2, ...

All PHP files MUST end with a non-blank line, terminated with a single LF.

Probably needs to be investigated more?

You're saying that it's not a php file, so doesn't have to include a LF at the end?
The line feeds are a UNIX thing. A line isn't considered a line if it isn't followed by a LF. Most standard tools require this, for example, wc -l standards/akeneo.yaml yields 13 instead of 14. It's a general practice.


network-gossip: Do not report peer on duplicate message if its the first time

Two peers can send us the same gossip message. Before this pr we would have reported the second peer for sending a duplicate message. However, this isn't correct if we haven't seen the message from this peer yet. So, we should not report them as they can not be aware of our internal state.

bot merge


Implement Terraform provider for Microsoft Defender for Cloud

Is your feature request related to a problem? Please describe.
Implement Microsoft-Defender-for-Cloud in terraform.
Describe the solution you'd like
Is there a terraform provider or module that enables controlling turning off/on Azure Defender for cloud?
Describe alternatives you've considered
I have looked at this and I am not sure that this is what we are looking for:
https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/security_center_workspace
Additional context
None

Hi @rdelgado-incomm, you can try using azurerm_security_center_subscription_pricing.

@ShaykeAmar you are saying that if I want to implement Microsoft Defender I need to use https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/security_center_subscription_pricing?

Hi @rdelgado-incomm this is just a reference how to enable the price tier to standard on specific subscription,
I would also recommended you to check this Terraform module to create Azure Security Center resources for Azure Landing Zones for more capabilities for the provisioning stage.


Hacktoberfest 2022: EcoEat - “eat healthy, pay less”

Hey! 👋
I have added my app idea “EcoEat” to your repository, and fixed bugs in another app that had a formatting error. Everything LGTM now ✌

@KapilKumar7 please take a look at this PR :)

Thanks for your valuable contribution 😊.


Fixes tree selected item and selected column not updating on deselect

When a selected TreeItem is deselected, the selected_item variable is updated to reflect that.
Fixes #25392

Ah, don't merge yet, I'll have to add a check for selected_col as well since that seems to be working incorrectly too.

  See the CI error log and the code style guidelines.

Also, all PRs should be made against the master branch unless it specifically only applies to an earlier version.

Superseded by #45806.


Ujson, OpenAPI: option to skip default field values

Adds a new encodersSkipDefaultValues option to the ujson
interpreter and then enable that by default in the OpenAPI use of
ujson. This option makes the encoder check field values against the
default field value before serializing it. If they match, it skips the
field.
Implements #887

Is this a reasonable feature/approach? If so, I'll add a couple tests. The option seemed useful to me mostly for making shorter and simpler serialized example values, but maybe it is unnecessary complexity.

I think this is ready for review.
I'm really stumped about what to document and where to document it though. This is a ujson-specific option and although I suppose it could be generalized to other interpreters, I'm not sure there is value there but there is a cost if there are other JSON schema implementations in the wild. I don't see any section in the docs for ujson either.
Along the way, I found and sort of addressed an issue that looks like bad interplay of paradox-material-theme with a recent change made to paradox (https://github.com/lightbend/paradox/pull/474).

Before:
After:

Any idea when a release including this might occur? There isn't any urgent rush - I'm just asking so I can decide whether to rebase now or later some branch at work.

Hello! Yes, I want to cut a release very soon (hopefully this week). We are currently testing the new features that have been recently merged, just to double-check everything is ready for release.


Where can i view version log?

Hi,
When i'm trying to use version 0.3.3, it generate some error when build, so i must downgrade to 0.3.2.
Can i have some verion log to view what change between every versions?
Thanks!

Hi, please take a look at #49. I believe you have to update Gradle to 6.8 or later. And unfortunately there's no version log.

Yes, i saw it before, so i decide to downgrade to 0.3.2.
But what happen with 0.3.3, did it have any important upgrade?

In 0.3.3 I moved artifacts from Jcenter to Maven Central, and in order to do that I had to update dependencies including Gradle. Nothing in the obfuscation part has changed.

Oh, ok thank you so much!


Audio glitching when suspending Ally X

Describe the bug
When suspending Ally X, audio glitches for a couple of seconds.
What did you expect to happen?
Expecting the audio to cut off immediately without issue, once the suspend animation ends.
Output of rpm-ostree status
AllyX@pc-215:~$ rpm-ostree status
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
                   Digest: sha256:0030210b0396e99ff0b5e0b60e265181314f1c60398b045225ee76626d8e1dbf
                  Version: 40.20240809.0 (2024-08-09T05:12:26Z)

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
                   Digest: sha256:fa9d7c77f4be2d451aa62cc232649afd087a2ea0f539df891ef4bb5cb6ac488a
                  Version: 40.20240807.0 (2024-08-07T07:32:24Z)

Hardware
ROG Ally X RC72LA_RC72LA
Extra information or context
The audio glitches before the device goes to sleep.
Audio output set to default (Family 17h/19h...).
Updated speaker driver.
Steam Powerbutton handler activated in HHD. Issue occurs whether this is on or off.
Check video below. :
https://github.com/user-attachments/assets/31a8b55f-dcb0-4103-9bd4-5a947767f2da

Hello, I'm happy to report that all of these issues have been fixed with
the latest update. Thank you!
Le sam. 16 nov. 2024, 5:06 PM, dosubot[bot] @.***> a
écrit :

Hi, @salmaninay https://github.com/salmaninay. I'm Dosu
https://dosu.dev, and I'm helping the bazzite team manage their
backlog. I'm marking this issue as stale.
Issue Summary:

Audio glitch occurs on ROG Ally X when suspending the device.
Audio does not cut off immediately after the suspend animation.
Issue is independent of the Steam Powerbutton handler setting.
A video was provided to demonstrate the problem.
No further comments or developments have been made.

Next Steps:

Is this issue still relevant with the latest version of the bazzite
repository? If so, please comment to keep the discussion open.
If there are no updates, the issue will be automatically closed in
14 days.

Thank you for your understanding and contribution!
—
Reply to this email directly, view it on GitHub
https://github.com/ublue-os/bazzite/issues/1510#issuecomment-2480632539,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BCIQ7252YA2OH3UOIDSLGUD2A5UQPAVCNFSM6AAAAABMVWO2DGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBQGYZTENJTHE
.
You are receiving this because you were mentioned.Message ID:
@.***>


Add ProposedVersion and refine some code

Current coverage is 44.58% (diff: 100%)

No coverage report found for master at a3e5d87.

Powered by Codecov. Last update a3e5d87...a1a85ee


A Better type for styles

what about we use this type instead of exclusively defining the type of style?
import { ViewStyle, TextStyle, ImageStyle } from 'react-native';

// Define a custom type to allow only one of the specified types
type ExclusiveStyle<T, U, V> =
  | (T extends U ? never : T extends V ? never : T)
  | (U extends V ? never : U);

// Define NamedStyle as a union of ViewStyle, TextStyle, and ImageStyle
export type NamedStyle = ExclusiveStyle<ViewStyle, TextStyle, ImageStyle>;

Here is the result
const $text: NamedStyle = {
  borderWidth: 1,
  color: 'red',
  resizeMode: 'center', // Error: Object literal may only specify known properties, and 'resizeMode' does not exist in type 'TextStyle'.
};

Hey could you provide some more context around this?
I couldn't get this to work properly, for example, in the WelcomeScreen.tsx.
Changing $welcomeLogo over to NamedStyle, it thinks it is a TextStyle
Adding fontFamily to $bottomContainer, it is not underlining it as an error, which is assigned to a View.

Hey could you provide some more context around this?
I couldn't get this to work properly, for example, in the WelcomeScreen.tsx.
Changing $welcomeLogo over to NamedStyle, it thinks it is a TextStyle
Adding fontFamily to $bottomContainer, it is not underlining it as an error, which is assigned to a View.

Hi @frankcalise Yep, I tried to fix the style but had no luck, as you mentioned, it's not detecting the $welcomeLogo as ImageStyle.
it's possible to use a simpler style like
export type NamedStyle = ViewStyle | TextStyle | ImageStyle;

but I wanted to make sure they stayed separated

Thanks for the suggestion though, let us know if you ever get that clever attempt from the first try working! It definitely looks interesting if it could work out


HADOOP-17528. Fix closing an underlying connection pool when closing SFTP File System

SFTPFileSystem leverages a connection pool which is not closed when a file system instance gets closed preventing a JVM from exiting as every established SFTP connection runs in a separate non-daemon thread. This PR fixes SFTPFileSystem closure.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 30s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:

0m  0s
test4tests
The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
32m  9s

trunk passed

+1 :green_heart:
compile
20m 28s

trunk passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
17m 45s

trunk passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
checkstyle
1m  6s

trunk passed

+1 :green_heart:
mvnsite
1m 31s

trunk passed

+1 :green_heart:
shadedclient
16m  1s

branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
1m  5s

trunk passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
1m 36s

trunk passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+0 :ok:
spotbugs
2m 21s

Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
2m 19s

trunk passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 54s

the patch passed

+1 :green_heart:
compile
20m 33s

the patch passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
20m 33s

the patch passed

+1 :green_heart:
compile
17m 53s

the patch passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
javac
17m 53s

the patch passed

+1 :green_heart:
checkstyle
1m  3s

the patch passed

+1 :green_heart:
mvnsite
1m 28s

the patch passed

+1 :green_heart:
whitespace
0m  0s

The patch has no whitespace issues.

+1 :green_heart:
shadedclient
13m 27s

patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
1m  4s

the patch passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
1m 30s

the patch passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
findbugs
2m 22s

the patch passed

_ Other Tests _

+1 :green_heart:
unit
17m 18s

hadoop-common in the patch passed.

+1 :green_heart:
asflicense
0m 50s

The patch does not generate ASF License warnings.

175m  5s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2701/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2701

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 937d084d102c 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / c3134ab3a99

Default Java
Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2701/1/testReport/

Max. process+thread count
2197 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2701/1/console

versions
git=2.25.1 maven=3.6.3 findbugs=4.0.6

Powered by
Apache Yetus 0.13.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
14m 18s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:

0m  0s
test4tests
The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
32m 27s

trunk passed

+1 :green_heart:
compile
20m 30s

trunk passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
17m 48s

trunk passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
checkstyle
1m  5s

trunk passed

+1 :green_heart:
mvnsite
1m 30s

trunk passed

+1 :green_heart:
shadedclient
16m  0s

branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
1m  4s

trunk passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
1m 37s

trunk passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+0 :ok:
spotbugs
21m  5s

Both FindBugs and SpotBugs are enabled, using SpotBugs.

+1 :green_heart:
spotbugs
2m 23s

trunk passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 54s

the patch passed

+1 :green_heart:
compile
19m 53s

the patch passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
19m 53s

the patch passed

+1 :green_heart:
compile
17m 51s

the patch passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
javac
17m 51s

the patch passed

+1 :green_heart:
checkstyle
1m  4s

the patch passed

+1 :green_heart:
mvnsite
1m 29s

the patch passed

+1 :green_heart:
whitespace
0m  0s

The patch has no whitespace issues.

+1 :green_heart:
shadedclient
13m 17s

patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
1m  1s

the patch passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
1m 37s

the patch passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

-1 :x:
spotbugs
2m 17s
/patch-spotbugs-hadoop-common-project_hadoop-common.txt
hadoop-common-project/hadoop-common cannot run computeBugHistory from spotbugs

_ Other Tests _

+1 :green_heart:
unit
17m  9s

hadoop-common in the patch passed.

+1 :green_heart:
asflicense
0m 55s

The patch does not generate ASF License warnings.

188m 30s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2701/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2701

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle

uname
Linux 44c4dabf0b93 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 0ed9e36282c

Default Java
Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2701/2/testReport/

Max. process+thread count
1853 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2701/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.0.6

Powered by
Apache Yetus 0.13.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 37s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:

0m  0s
test4tests
The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
32m 50s

trunk passed

+1 :green_heart:
compile
20m 35s

trunk passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
17m 52s

trunk passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
checkstyle
1m  5s

trunk passed

+1 :green_heart:
mvnsite
1m 29s

trunk passed

+1 :green_heart:
shadedclient
16m  5s

branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
1m  4s

trunk passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
1m 35s

trunk passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+0 :ok:
spotbugs
21m  3s

Both FindBugs and SpotBugs are enabled, using SpotBugs.

+1 :green_heart:
spotbugs
2m 18s

trunk passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 51s

the patch passed

+1 :green_heart:
compile
19m 52s

the patch passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
19m 52s

the patch passed

+1 :green_heart:
compile
17m 49s

the patch passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
javac
17m 49s

the patch passed

+1 :green_heart:
checkstyle
1m  5s

the patch passed

+1 :green_heart:
mvnsite
1m 31s

the patch passed

+1 :green_heart:
whitespace
0m  0s

The patch has no whitespace issues.

+1 :green_heart:
shadedclient
13m  1s

patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
1m  6s

the patch passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
1m 39s

the patch passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

-1 :x:
spotbugs
2m 18s
/patch-spotbugs-hadoop-common-project_hadoop-common.txt
hadoop-common-project/hadoop-common cannot run computeBugHistory from spotbugs

_ Other Tests _

+1 :green_heart:
unit
17m 22s

hadoop-common in the patch passed.

+1 :green_heart:
asflicense
0m 56s

The patch does not generate ASF License warnings.

175m 27s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2701/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2701

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle

uname
Linux 1b80d25539dd 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 0ed9e36282c

Default Java
Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2701/3/testReport/

Max. process+thread count
3158 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2701/3/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.0.6

Powered by
Apache Yetus 0.13.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

@steveloughran
The build reports a problem due to the spotbugs issue
Here's a stacktrace from the build logs:
[2021-02-17T19:50:51.359Z] Building spotbugs database(s) using /opt/spotbugs for executables.
[2021-02-17T19:50:51.359Z]
[2021-02-17T19:50:51.359Z]
[2021-02-17T19:50:51.359Z] Starting with /home/jenkins/jenkins-agent/workspace/hadoop-multibranch_PR-2701/out/branch-spotbugs-hadoop-common-project_hadoop-common-warnings.xml
[2021-02-17T19:50:51.359Z] Exception in thread "main" java.lang.UnsupportedOperationException
[2021-02-17T19:50:51.359Z] 	at java.util.Collections$UnmodifiableCollection.removeIf(Collections.java:1086)
[2021-02-17T19:50:51.359Z] 	at edu.umd.cs.findbugs.BugRanker.trimToMaxRank(BugRanker.java:322)
[2021-02-17T19:50:51.359Z] 	at edu.umd.cs.findbugs.workflow.Update.discardUnwantedBugs(Update.java:337)
[2021-02-17T19:50:51.359Z] 	at edu.umd.cs.findbugs.workflow.Update.doit(Update.java:484)
[2021-02-17T19:50:51.359Z] 	at edu.umd.cs.findbugs.workflow.Update.main(Update.java:405)
[2021-02-17T19:50:51.359Z]
[2021-02-17T19:50:51.359Z] hadoop-common-project/hadoop-common cannot run computeBugHistory from spotbugs

Here's a cause for this to happen.
This happened straight after substituting findbugs with spotbugs here
@aajisaka could please help to fix the build?

Thank you @mpryahin for your report. I'll revert #2454 shortly.

Reverted #2454

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
15m 19s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:

0m  0s
test4tests
The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
35m 59s

trunk passed

+1 :green_heart:
compile
23m 10s

trunk passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
20m 23s

trunk passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
checkstyle
1m  5s

trunk passed

+1 :green_heart:
mvnsite
1m 33s

trunk passed

+1 :green_heart:
shadedclient
16m 21s

branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
1m  3s

trunk passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
1m 33s

trunk passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+0 :ok:
spotbugs
2m 23s

Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
2m 21s

trunk passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 57s

the patch passed

+1 :green_heart:
compile
21m 36s

the patch passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
21m 36s

the patch passed

+1 :green_heart:
compile
19m 35s

the patch passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
javac
19m 35s

the patch passed

+1 :green_heart:
checkstyle
1m  2s

the patch passed

+1 :green_heart:
mvnsite
1m 23s

the patch passed

+1 :green_heart:
whitespace
0m  0s

The patch has no whitespace issues.

+1 :green_heart:
shadedclient
13m  7s

patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
1m  4s

the patch passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
1m 35s

the patch passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
findbugs
2m 38s

the patch passed

_ Other Tests _

+1 :green_heart:
unit
17m 41s

hadoop-common in the patch passed.

+1 :green_heart:
asflicense
0m 53s

The patch does not generate ASF License warnings.

202m 37s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2701/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2701

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux bf626a3dc6fd 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 9a298d180da

Default Java
Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2701/4/testReport/

Max. process+thread count
3158 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2701/4/console

versions
git=2.25.1 maven=3.6.3 findbugs=4.0.6

Powered by
Apache Yetus 0.13.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 30s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:

0m  0s
test4tests
The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
32m 56s

trunk passed

+1 :green_heart:
compile
23m 27s

trunk passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
22m 29s

trunk passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
checkstyle
1m 13s

trunk passed

+1 :green_heart:
mvnsite
1m 44s

trunk passed

+1 :green_heart:
shadedclient
20m 34s

branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
1m  8s

trunk passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
1m 48s

trunk passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+0 :ok:
spotbugs
3m  0s

Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
2m 56s

trunk passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m  7s

the patch passed

+1 :green_heart:
compile
26m 48s

the patch passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
26m 48s

the patch passed

+1 :green_heart:
compile
23m 11s

the patch passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
javac
23m 11s

the patch passed

+1 :green_heart:
checkstyle
1m 12s

the patch passed

+1 :green_heart:
mvnsite
1m 44s

the patch passed

+1 :green_heart:
whitespace
0m  0s

The patch has no whitespace issues.

+1 :green_heart:
shadedclient
17m 19s

patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
1m  6s

the patch passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
1m 47s

the patch passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
findbugs
2m 57s

the patch passed

_ Other Tests _

+1 :green_heart:
unit
18m 38s

hadoop-common in the patch passed.

+1 :green_heart:
asflicense
0m 55s

The patch does not generate ASF License warnings.

207m 36s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2701/5/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2701

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux ec4ed8bbbc80 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 25af8901a97

Default Java
Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2701/5/testReport/

Max. process+thread count
1389 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2701/5/console

versions
git=2.25.1 maven=3.6.3 findbugs=4.0.6

Powered by
Apache Yetus 0.13.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

@aajisaka thanks you so much.
@steveloughran Steve, looking forward to getting the changes in, thank you.

+1, merged to trunk


ROY coefficients

Hello - thanks for an amazing set of tools and documentation! This has all been so helpful.
I noticed the warning about the use of collection 2, and the decision to not use the ROY coefficients for scaling.  Looking a bit deeper I noticed the following note:
https://github.com/eMapR/LT-GEE/blob/5d70f99bf81a87401fe2520258cb9426884743ae/LandTrendr.js#L107
Could you provide any more insight into those use cases around the world? Maybe some studies? Thank you!

Hello! Following up to see if anyone has a workaround for the Collection 2 Landsat data and harmonizing without the Roy coefficients, or what is causing the issue with these coefficients? Thank you for any tips / thoughts!

I am tolled, they didn't make a big difference with the implementation of Collection 2. My colleague conducted an unpublished analysis on many locations around the world, and did not find a large difference between the corrected Collection 1 and the uncorrected Collection 2.  I will see if I can get more info.

Can you send me the unpublished analysis? Or potentially how they
determined C1 and C2 could be harmonized in the same way? This sounds like
great news.
On Thu, Dec 15, 2022 at 10:43 AM Peter C @.***> wrote:

I am tolled, they didn't make a big difference with the implementation of
Collection 2. My colleague conducted an unpublished analysis on many
locations around the world, and did not find a large difference between the
corrected Collection 1 and the uncorrected Collection 2. I will see if I
can get more info.
—
Reply to this email directly, view it on GitHub
https://github.com/eMapR/LT-GEE/issues/30#issuecomment-1353546774, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AG6NIMVMC72XMSVGEWFS4FTWNNRERANCNFSM5YDOVYXQ
.
You are receiving this because you commented.Message ID:
@.***>

This might help: https://developers.google.com/earth-engine/faq#is_cross-sensor_landsat_surface_reflectance_harmonization_needed


Open Issue 17: meta.security use for maximal populated

Should a minimally populated or maximum populated AuditEvent have a defined .meta.security code so as to be more able to be access controlled at the Audit Consumer API?

useful idea, but not in scope of BasicAudit. Thus not profiled or mentioned.


[zh] Add systemd-watchdog.md and its feature gate

Add zh text to:
content/zh-cn/docs/reference/node/systemd-watchdog.md
content/zh-cn/docs/reference/command-line-tools-reference/feature-gates/systemd-watchdog.md

/lgtm


[pkg/test] Improve ConcurrentT.Wait()

It would be very handy to extend pkg/test/ConcurrentT with a function WaitCtx(ctx, stages...) that fails and aborts the test if the context expires before the requested stages are done. This is important if we have contexts that should limit the duration of tests.

#112 implements this a little differently to reduce the complexity of the ConcurrenT's API: instead of having to specify contexts on every blocking call, now, there is one context per ConcurrentT that can be optionally specified in the constructor. All blocking operations will be aborted on context expiry and the test will fail.


[Android32] Could not load sk4d.so

Some manufacturer and android versions (looks like just in android 6), just in 32 bits, can't find the sk4d.so because they don't look at the folder "lib\armeabi-v7a". Need more investigate.
Edit: Anyway, switching to static compilation would solve the problem (though not supported yet).

The problem was solved in new release.


memory and cpu hot-plugging support

I've started Docker, etcd2, and Swarm on a amd64 machine able to receive more CPUs and memory on-the-fly (aka hot-plugging), running Linux 4.4.0. It's a swarm of one machine only.
$ lscpu | head -n 5
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                24
On-line CPU(s) list:   0-23

$ docker -H <IP_ADDRESS>:2377 info | tail -n 6
Kernel Version: 4.4.0-4-generic
Operating System: linux
Architecture: amd64
CPUs: 25
Total Memory: 16.32 GiB
Name: 562ec85caa9b

The »CPU«-count is obviously off by one when displaying through swarm, fine with docker.
Anyway, I've plugged in one more CPU and more memory. Both get detected and are made available by Linux correctly.
expected
docker info (using swarm) displays more »(reservable) CPUs« and more »(reservable) memory«, and higher totals.
currently happening
The counters don't change.

@wmark Thanks for reporting this problem! Currently Swarm manager updates node specification when the node first join the cluster, or when the node comes back from unhealthy state. Periodic node spec update might be a little inefficient. Can you run docker events towards the node and check if there is specific event when you add/remove CPU/Mem? If there are such events, we can update spec when we detect them.

@wmark Just check docker code, it doesn't emit events. It just collects runtime.NumCPU() when user issues docker info. Swarm as an aggregator has to refresh engine spec to get the update.

@dongluochen Thank you for looking into this! If I understood that completely we need Swarm to poll periodically, and Docker or the Agent to refresh its stats. (I didn't look into it on this side.)
It will be enough if we re-read total memory and core count on signal syscall.SIGPWR on the target machine(s).
signal.Notify(signalChannel, os.Interrupt, syscall.SIGPWR)
…
case syscall.SIGPWR:
    // this could be a power-loss event, or hotplugging
    runtime.NumCPU()
    …

@wmark Docker doesn't store CPU/Mem information. It queries them on-the-fly. Swarm doesn't get event notification from the nodes. A simple fix is to refresh node spec periodically. To reduce resource requirement, we may select a refresh interval of several minutes.

Or just generate an event on syscall.SIGPWR?

Or just generate an event on syscall.SIGPWR?

I doubt Docker maintainers would agree to that.

Fixed by: https://github.com/docker/swarm/pull/1992


add code and number bindings

Hey @vialyx, Thanks for your contribution. Isn't this cause the view to have 2 different sources if truth? One for the full text and one for the separated version?


WebSocket refactoring

NanoWebSocketServer renamed to NanoWSD as discussed.
Removed event methods from NanoWSD and added them under WebSocket as abstract methods.
Moved WebSocket Frame debug methods (on send / receive) from NanoWSD into WebSocket with name format debugFrame<Received|Sent>() as empty methods, so that IDEs don't force users to override them, thus keeping users from being tempted into adding code into them. Also added Javadocs explaining they are debug methods and should not be overriden unless for debug purposes.
Added WebSocket.onOpen() event method that is called right after the WebSocket state changes to State.OPEN.
Added WebSocket.isOpen() method that checks the internal state.
Made the WebSocket class static and abstract, detaching it from NanoWSD.
Made NanoWSD.openSocket() abstract. This is now the only method you have to override in this class. We could even make a WebSocketFactory interface and pass it as a constructor argument so that in most cases NanoWSD doesn't even need to be extended/overriden.
Updated all the necessary tests accordingly.

As a side note, I've set up Travis-CI and Coveralls on a test branch of my fork (LordFokas/travis) so that everything I pull request into NanoHTTPD is tested against your own tests and standards before leaving my repo. Everything went fine, so I should assume it will be ok here. I've had issues with SSL and files while testing on my machine though, so the only way I can really test this is with online integration tools.
I'd also like to point out that I might put some work into increasing the coverage after this is accepted (assuming it is accepted), provided I get a stronger grip on tests... and I feel like I'm getting the hang of it quite well :)

I guess this closes #242

Are you interested becomming a nanohttpd developer?

That is... really flattering. Thank you.
I'll have to sleep over it a few nights, but no matter what I decide I'll tell you this: I love NanoHTTPD. I'm really glad I found it and it started me on a journey that took my skills to another level, and I have a really cool use case for it (like Nanolets, but fatter) and as such I'll keep working on it and sharing my code, no matter if I accept that invitation or not :)
Meanwhile, I'll keep the code flowing, I have a few more things I want to change, namely the way cookies are handled (that was my first PR here, actually, and I don't even know how Paul accepted that code... well, at least it worked :p ).

@LordFokas at the moment we are very thin spread... We wan't to create a 2.2.0 release as soon as all major bugs are "fixed" or at least analysed. Every time we think we are near new issues come is and that eats our time... So it would be great if you could help (as you are doing) getting to a "stable" state.


Follow-up from #2716: clickable urls in --help

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/3161
Originally created by @aaronsteers on 2022-01-13 21:43:26

The following discussion from !2492 should be addressed:

[ ] @edgarrmondragon started a discussion:  (+3 comments)

My only nit with these links is that click seems to like wrapping them and so clicking them doesn't work:
$ meltano environment --help
Usage: meltano environment [OPTIONS] COMMAND [ARGS]...

  Manage Environments.

  Read more at https://meltano.com/docs/command-line-
  interface.html#environment

Options:
  --database-uri TEXT  System database URI.
  --help               Show this message and exit.

Commands:
  add     Add a new environment.
  list    List available environments.
  remove  Remove an environment.

View 5 previous comments from the original issue on GitLab


12Sec Delay on HLS URL

Am facing 12sec delay on hls url, if i use RTMP url, it have only 2sec delay. Is there any change, that can reduce the delay?

Hi @kasirajansfm
HLS generally has larger latency. However, you can still try to reduce the keyframe interval on the publishing side and reduce the buffering time of the player to see if this can help.
Besides, LLHLS is being considered a potential feature.

Tried, but no use, now am getting 8sec delay.

8 seconds is indeed close to the best-case scenario for traditional HLS.
In order to have 2-4 seconds latency, LL-HLS features will be required.

@josephnhtam Websocket-FLV working with 3 sec delay. Is that fine?

<!DOCTYPE html>
<html>
  <head>
    <title>WebSocket Video Player</title>
    <script<EMAIL_ADDRESS>  </head>
  <body>
    <video id="videoElement" controls height="600" width="1200" autoplay muted></video>
    <script>
      var videoElement = document.getElementById('videoElement');
      var flvPlayer = flvjs.createPlayer({
        type: 'flv',
        url: 'ws://localhost:8080/live/d2.flv',
        stashedBufferTime: 0.1,
        bufferSize: 1024 * 1024, // 1MB
        lowLatency: true,
        maxBufferLength: 0.5
      });
      flvPlayer.attachMediaElement(videoElement);
      flvPlayer.load();

    </script>
  </body>
</html>

@josephnhtam this is the code am using for player. am i using correctly.?

I may not be able to help much if the limitation coming from the client side. Have you also tried xqq/mpegts.js?

<!DOCTYPE html>
<html>
<head>
    <title>WebSocket FLV Player</title>
</head>
<body>
        <script<EMAIL_ADDRESS>
    <video id="videoElement" controls height="600" width="1200" autoplay muted></video>
    <script>
        if (mpegts.getFeatureList().mseLivePlayback) {
            var videoElement = document.getElementById('videoElement');
            var player = mpegts.createPlayer({
                type: 'flv', // could also be mpegts, m2ts, flv
                isLive: true,
                url: 'ws://localhost:8080/live/d2.flv', // replace with your WebSocket FLV stream URL
bufferSize: 1024 * 1024, // 1MB buffer size
                maxLatency: 500, // 500ms maximum latency
                lowLatency: true
            });
            player.attachMediaElement(videoElement);
            player.load();
            //player.play();
        }
    </script>
</body>
</html>

@josephnhtam Same 3-5 sec delay with this also. But in RTMP its like near realtime. is there any way to play RTMP on browser.

Hi @kasirajansfm
I tried the FlvDemo and used VLC player to play streams with both HTTP-FLV and RTMP. They both exhibit a similar latency of 2 seconds. However, when the FLV stream is played with flv.js instead of VLC player, the latency increases to around 3 seconds. It’s evident that the flv.js library itself introduces some latency.


druid bind address not configurable

Currently druid always binds  to <IP_ADDRESS> completely ignoring the setting of druid.host
Please have druid respect this setting to enable its usage on multi-interface machines

I think we should add a new configuration like druid.bind.on.druid.host to let people decide whether to bind on druid.host or <IP_ADDRESS>. I'll open a PR to do that.


feat: add Cloud Run deployment

This PR adds the Terraform setup and the necessary changes to Cloud Orchestrator to be deployed on Cloud Run protected by IAP. Additionally it includes the possibility to use GCE instances with private IPs only.
Co-authored-by: David Gleich<EMAIL_ADDRESS>

@gleichda FYI


[GLUTEN-5901][CH] Support CH backend parquet + delta

What changes were proposed in this pull request?
Support CH backend to read/write parquet with the delta:

native read parquet from the delta catalog;
fallback write the parquet to the delta catalog ( don't support the DeltaInvariantCheckerExec operator and DeltaTaskStatisticsTracker) ;
Use the ClickHouseSparkCatalog as the uniform catalog.

Close #5901.
(Fixes: #5901)
How was this patch tested?
(Please explain how this patch was tested.


Repository has been requested to be removed

Hi!
I got this error in logs, I should be worry about it?
Logger: custom_components.hacs
Source: custom_components/hacs/tasks/base.py:34
Integration: HACS ([documentation](https://hacs.xyz/docs/configuration/start), [issues](https://github.com/hacs/integration/issues))
First occurred: 11:36:29 (1 occurrences)
Last logged: 11:36:29
<HacsTask prosess_queue> failed: <Integration r-renato/hass-xiaomi-mi-flora-and-flower-care> Repository has been requested to be removed.

same for me using 2022.5

I have the same problem! why is this happening?

nooooooooooooooooooooooooooooooooooooooooooo please xD
why ?


Delete Data With relations

Hey,
it would be nice to delete a model from the store with specific relations.
// Delete all User with their posts
User.delete(1, {with: 'posts'})

// at the moment
User.delete(1)
Post.delete(post => post.user_id === 1)

Or maybe allow deleting with the querybuilder
// Delete all User with their posts
User.query().where('id', 1).with('posts').delete()

Cascading is a nice feature, for sure. Something that is currently not supported by Vuex ORM but we may dip our toes to test the waters on this feature.
There is an issue open related to this (#345) – we'd be happy to listen to your suggestions over there.

Thanks for the feedback! yea this is some thing we would need. Closing the issue due to duplication, though feel free to add your ideas to #345 👍


Nonlinear Undo/Redo

WIP
Here's the flowchart of the system that is read from left to right. A line of code (or pseudo code) is an orange box. Black arrows point from an orange box to its actual method's implementation. Method implementations, if/else blocks, and for loops are in groups. Finally, red lines indicate the order in which the code is run.

And here's a better version read top to down.

I'm now working on implementing updateChangesPostUndoBubble in DocumentDAG. However, I just realized that I will probably need to change the way the NonlinearUndoManager attempts to merge a previously done change. I'm not yet sure how that will affect everything else.

I was getting overwhelmed because I wasn't sure how prev() would work given that there are 3 situations that all use that same code. However, once I did it manually on a whiteboard, I figured out where my logic was incorrect. Now that that has been fixed, I believe the underlying code actually works now.
In other words, designing an integration test like this could have bugs in two areas: the code I'm using to test the nonlienar undo/redo system, or the nonlinear undo/redo system itself. Now that I'm confident that nonlinear system works, I only need to finish implementing my tests on the code I'm using to test it before I can write the tests for the nonlinear system itself.
I plan on finishing this before this coming Sunday. I may need to clean up the commit history in the following week, but the code itself should be good by Saturday night.

This PR is now feature-complete (I think). I just need to finish writing all the test that prove that. It's definitely not supposed to be ThreadSafe

I'm not sure if my implementation of FixedSizeArrayList is error-free.
I've run across an issue with ``DocumentDAGTest.UpdateBubbledUndoDependencyTests. I keep getting an IndexOutOfBoundsException` when a dependency does not remove as much text as it inserts. However, once I figure that out, I'll finally be able to start writing the tests for this PR's actual code. Sheez....

I've concluded that one can bubble a TextChange in two ways: the bubbled portion stores the original undo's "removed" string / redo's "inserted" string while the grounded portion stores an empty string for its counterpart, or vice versa.

Ok, I've exhaustively tested DocumentDAG. Now it's time to write the actual tests for the nonlinear package.

Updated logic flowchart:

Logic flowchart (top down):

:-/ I was hoping to finish this PR's actual tests by tonight, but it looks like I ran out of time due to working on other RTFX stuff. I'll try to finish it by this next week, but no guarantees because school is starting up again.

I was looking at the tests last night and came across an issue with my implementation of QueuePosition. I decided a position should be valid in two cases. The first one isn't the problem: the queue's list of changes is empty and the forgottenCount is the same. The second one is: the queue contains a change in its list of changes (because the change could be repositioned in the queue's history).
However, whenever a queue pushes a new change, whether an undo/change/redo, it calls updateUndo/Redo. Since the original change is sometimes replaced with an updated version, changes.contains(storedChange) is sometimes true (true if no update was needed; false if it was needed) and thus isn't a good way to indicate its validity.
I think I'll have to wrap the change in another object that can be used to track whether the change stored there is the same object (original or updated) or if it's a new object entirely. Thus, it would be List<Version<C>> changes where Version would be:
class Version<C> {
    private C change;
    public C getChange() { return change; }
    public void setChange(C c) { change = c; }
}

Then, when a change is merely updated, I can use identity equals to determine whether the queue position is still valid. However, due to the possibility of a change being bubbled, the question becomes, "Do I replace the old change with the grounded portion and create a second Version object for the bubbly portion? Or do I create 2 Version objects? I'm leaning towards the latter option.
I have yet to write tests for the nonlinear undo manager

I updated my code to use the Version idea (though I think Wrapper or Container is a better way to describe the class' functionality). The UnlimitedNonlinearChangeQueue's QueuePosition tests still failed, which baffled me until I figured out the real issue, something that I forgot still needed to be done.
When the UndoManager attempts to merge a change, it will call queue.prev() and either pushes a merged change or, when no merge is possible, both as new changes. I realized that the Nonlinear version of this approach needs to handle that situation differently than the Linear version. There are 4 situations for which to account:

When prev change is a regular change that can be merged with the pushed change
When prev change is a bubbled change that can be merged with the pushed change
When prev change is a regular change that cannot be merged with the pushed change
When prev change is a bubbled change that cannot be merged with the pushed change

I haven't yet thought through how that should be handled.

The issue with using Version is that it is now mutable because I have to update its change object to insure that it can identity equals one stored in a QueuePosition. I understood that issue, but it wasn't my goal then to correct that.
After more thought, I decided this should be further abstracted out of that object. Rather than using the Version object itself to check for identity equals, I should just create a blank Object that is stored in a Version object. This object could then be used for identity equals without Version needing to be mutable.
As for other things:

calling undo twice consecutively screws up something. I haven't debugged it further, but that's the issue stopping all 3 QueuePosition tests for the unlimited variant
I still need to update FixedSizeArrayList to use a "revolving" approach like you use in the Linear version, so that every time a new change is added, I'm not moving all changes to the left by one index but merely wrapping around back to the 0th index of the array.

I may have an off-by-one issue in FixedSizeRevolvingArrayList. However, that's my first run through in making it work.

I tested FSRAL last night with tests. It failed due to System.arrayCopy throwing an ArrayIndexOutOfBoundsException and I know why. However, I'm not sure if I'll get to fix it this week, though, due to time constraints.

K, FixedSizeList is finished, though I still wonder if my code will work for a fixed size list of two changes (the array copy might throw an AIOOBE, so I'll test that theory out later). Not knowing much about memory usage, I also wonder if such an implementation should use an array or just two changes called first and second.

Ok, I got the Unlimited variant's queue position tests to pass. I haven't actually thought about what additional tests it might need due to being nonlinear. The FixedSize variant's tests will need to account for the bubble strategies that are used.

Ok. The fixed size NCQ tests pass now.

... but they don't account for different bubble strategies

The most recent NonlinearUndoManager.LinearTests test that uses the unlimited variant produced a bug that I fixed in this most recent commit. However, I'm a bit confused. The unlimited and fixed size variants use the same code base, but the issue arises only with the unlimited variant. I'm still going to change the fixed size variant to do the same thing the unlimited one does just in case. However, I'm making a note of this now so that I don't forget later.
Though this bug might be caused by something else, it doesn't seem like it. The issue was caused by the original undo's starting position not getting bumped to the left/right due to another pushed undo/redo. That didn't occur, presumably, because it wasn't one of the changes included in the undos being updated. Most likely, the javadoc I wrote there is outdated from when I originally wrote it last summer since it probably understood things in a different way than I do now.

At this point, I only need to write the NonlinearUndoManagerTest.NonlinearTests and then write tests that account for the FixedSize variant's bubble forget strategies to insure the QueuePosition works as expected.

After investigating this more, the issue is not in the undo system's code but rather in the DocumentDAG#updateRedo method:
@Override
public TextChange updateRedo(TextChange outdatedRedo, TextChange pushedChange) {
    if (pushedChange.removedEndPosition() <= outdatedRedo.getStart()) {
        return outdatedRedo.bumpPosition(pushedChange.getDifference());
    } else {
        // either pushedChange occurs to the right of outdatedUndo
        // or it actually modifies outdatedRedo, in which case it might be bubbly
        return outdatedRedo;
    }
}

The reversal of the text occurs because I'm using insertion() to push new changes, which calls replace(0, removedText.length(), insertedText). Thus, undoing any of these changes always deletes text, so any redos start positions are eventually set to 0. When I redo the first change (whose start = 0 and removed length = 0, thus removedEndPosition = 0, which equals all the redos' start position), it bumps all of redos' start positions by the redone change's difference. Since I'm always inserting text, this bump amount is always positive, causing all redos to update their start positions to be immediately after the redone change. Each redone change causes the remaining ones to bump their start to be immediately after that redone change. Thus, the inserted text comes after the last insertion, not before as it should and through this chain, the text is reversed.
The obvious workaround is to add another if statement before that code runs:
if (pushedChange.removedEndPosition == 0 && outdatedRedo.getStart() == 0) {
    return outdatedReo;
} else if /* the rest of the method */

However, will this always be the desired result? If not, it disproves an initial belief I had, that a NonlinearUndoManager could also be used as a linear one.

One idea I thought of today that might be able to get around this issue is if I separate the start position in TextChange into two parts: the original starting position, and the adjustable bump position. Thus, whenever a TextChange is bumped, bumpAmount is updated and the original start position is left untouched. When the change's getStartPosition() is called, it returns the sum of the original start position and the bumpAmount. In this way, I could distinguish between a change that was originally inserted at 0 and later adjusted to refer to a non-zero position in the document due to later insertions in front of it and a change that was added at a non-zero position that was adjusted to point to 0. I'm not sure whether this would be able to fix the issue I discovered above as I haven't thought through all of its implications yet.

Just FYI. I more or less stopped working on this as soon as I realized it wouldn't be necessary for a 0.7 stable release of RTFX. I still need it for my own code (so I'll get back to it later on), but I'd rather get a stable RTFX version first as that's more important in my code that undo/redo capabilities.

Yeah. Didn't I warn you early on that this would be a gargantuan task?
Oh and by the way, "non-linear" isn't very descriptive: it says what it isn't, not what it is.

Yeah. Didn't I warn you early on that this would be a gargantuan task? :D

You did, but I figured this would be my way of proving (more to myself than to you) that I could actually program good original code (since much of what I have done on your projects have been bug fixes or other things that use your code as a model to follow and only change in minor non-original/non-creative ways). Well, that and my code needs a non-linear undo/redo system (you'd think I'd learn not to take on near-impossible projects without any prior experience in some field, but....... I did and still do :laughing: )
Besides, my belief (when isn't it not the case on this PR, lol?) is that this PR is almost done. That's also partly why I stopped working on it as it should work after I implement that bumpAmount idea (so I pray!).

Oh and by the way, "non-linear" isn't very descriptive: it says what it isn't, not what it is.

If you said that, I would assume you had a cat, haha. Good point though. I've realized in this PR that non-linear could mean a different route that reaches the current state in the model (how I'm currently interpreting the term), or an unexpected result entirely (as discovered in the reverse issue I hope to fix with that bumpAmount idea).

Way to learn 👍
I don't actually have a pet, but could be a hamster :P

One other thought I had. Right now, prev is used in two cases to get a change: 1) to undo that change or 2) to try to merge that change with a recently-pushed change. Since there are not two separate methods for this in ChangeQueue, and since I was trying to maintain source compatibility in ChangeQueue, a NonlinearChangeQueue's prev sometimes returns a bubbled part of the next undo (if it is bubbly) for a merge even if the two changes cannot be merged or it results in an identity change, an issue raised in #14.
Ideally, there should be 2 methods for each case, so that NonlinearChangeQueue can still extend ChangeQueue and LinearChangeQueue only needs to override the method with the regular push. The first (perhaps prevForUndo) will bubble the undo because it is going to be undone. The latter (perhaps prevForMerge) will do the work necessary to create a bubble version of the next undo, but it will not update the graph.
In other words, if the code attempts to merge a bubbly change and a new pushed change, this is how the those possibilities should be handled:

Unsuccessful Merge: do not update the graph and just push the new change
Successful Merge results in non-identity change: update the graph and queue and overwrite the last change (if the undo is not the next undo (indexOf(change) != currentPosition-1), the change will be moved to that position and then split into two parts where the grounded portion will be the same index as the original and the bubbled will be one index greater. In this case, the last change is the bubbled part of the original change).
Successful Merge results in identity change: do the same as option 1.


Error on startup

Getting this error on starting the library on 1.5.2 (tried 1.8.2) as well:

Looks like it's having issues parsing tokens in the /src folder. Is it expected that there should be a /src folder? Wonder why the token is invalid.
Was working fine on 1.0.0-rc5.

Hi @danReynolds, thanks for reaching out!
It is indeed expected to have a /src folder.
From the looks of it, it looks as if something has changed the RegExp from our library. It is declared here as such:
const EXPO_DEV_LOGS_REGEX = new RegExp(
    '^http://((10|172|192).[0-9]+.[0-9]+.[0-9]+|localhost):[0-9]+/logs$'
);

Turning the string into a RegExp did not go right as it contains unescaped slashes.
Are you aware of anything in your app that would do such things?
If not, could you include the following information to help us troubleshoot:

a copy of your package.json
a copy of your Babel config (probably in a babel.config.js or .babelrc file)

Thanks a lot!

Hi @danReynolds,
Sorry my previous message was unclear, let me clarify.
Our code declares the regular expression using the RegExp constructor and a string, so there is no need to escape the slashes:
new RegExp(
    '^http://((10|172|192).[0-9]+.[0-9]+.[0-9]+|localhost):[0-9]+/logs$'
)

The message in your error has transformed this into a js RegExp (using /), but the slashes inside have not been escaped as they should have:
/^http://((10|172|192).[0-9]+.[0-9]+.[0-9]+|localhost):[0-9]+/logs$/

As we cannot reproduce this on our end, this can be due to a combination of dependencies not doing the transpilation correctly. If you could include the following information, that would be really helpful:

a copy of your package.json
a copy of your Babel config (probably in a babel.config.js or .babelrc file)

Thanks a lot!

Hi @danReynolds,
There has not been any activity on this issue for a while so I'm going to close it.
Feel free to reopen it with more details if you still encounter the problem :)


Considered resolving connections through the docker-proxy

Theory is the connection from skydns -> etd is going through the docker-proxy.

Probably not worth doing, as it looks like docker-proxy is going away:
https://github.com/docker/docker/pull/14973

Or not: https://github.com/docker/docker/pull/16347

/api/report result: https://gist.github.com/bboreham/7946c6fab7096aadd976

Note if skydns connects to etcd on host2 (as opposed to host1 in the picture) then a direct link between them is shown.

It would perhaps be a benefit to mark the node as 'docker-proxy'; as @rade commented it is unnecessary to go via the published port when connecting on the same machine.

Yes, hiding proxies has the downside.   Having a hybrid view like that suggested in #552 would help; I think we might want both, with some visual distinction for edges we've 'shortcutted', and an option to not shortcut them.

@tomwilkie Can we close this?


Fix semver documentation tests.

GitHub just updated the VM image to include the latest stable rust (1.48), which included some minor changes to diagnostic outputs.  This updates the semver chapter tests which validates that the correct error is displayed for the 1.48 release.  These diagnostics were changed via https://github.com/rust-lang/rust/pull/76524 and https://github.com/rust-lang/rust/pull/73996.

r? @alexcrichton
(rust-highfive has picked a reviewer for you, use r? to override)

@bors r+

:pushpin: Commit e1873091a860dce2c4cb7b27ee77ccb4809ec12e has been approved by Eh2406

:hourglass: Testing commit e1873091a860dce2c4cb7b27ee77ccb4809ec12e with merge 3d5447e6476a660bb98d1aaaf838aa6a2e9218b1...

:sunny: Test successful - checks-actions
Approved by: Eh2406
Pushing 3d5447e6476a660bb98d1aaaf838aa6a2e9218b1 to master...


MXNet - R API broken link

"MXNet R Reference Manual" on http://www.mxnet.io/api/r/index.html actually contains Julia reference.

Hmmm… duplicate of #6161?


Query on generics implementation

Will this package have a version that uses the new generics?

@Tobshub made a fork and used generics: https://github.com/Tobshub/go-sortedmap


Error code 1008 - Ofsted Unique Reference Number (URN) is not valid.

Error information
Error code
1008
Description to display
Ofsted Unique Reference Number (URN) is not valid.
DfE Long-form description of error
Please ensure the Ofsted URN is valid.  Check against Ofsted's URN list to ensure URN is a valid children's social care service URN, not an education URN.
DfE suggested coding
If provided <URN> must be a valid value (where valid values include 'XXXXXX')  For allowed values please see Ofsted URN list.
For further info, refer to the DfE validation document here

Duplicate of #69


Remove version: bornova.numara version 3.15.1

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/bornova/numara-calculator/releases/download/v3.15.1/Numara-3.15.1.exe
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 910)


net/http: net/http/httptest presents status codes that net/http will not send as sent

What version of Go are you using (go version)?

$ go version
go version go1.16 darwin/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
Applies to all operating systems and architectures
What did you do?
Used net/http/httptest to test a net/http server.
What did you expect to see?
Behavior from net/http/httptest accurately reflects that of net/http.
What did you see instead?
When an HTTP status code is provided to net/http's response.WriteHeader which is outside of the range 100 to 999, inclusive, a panic is documented to occur as intended behavior. This is documented here, which is called from response.WriteHeader.
When an HTTP status code is provided to net/http/httptest's response.WriteHeader, it is stored as successfully sent for later access regardless of whether the status code falls outside the 100 to 999 range. This is documented here.
The ResponseRecorder exposed by net/http/httptest is inconsistent with the net/http behavior it is designed to test.

cc @bradfitz @neild @fraenkel


Loading of template values fails when a kube context cannot be found

We just went through a very painful debugging exercise where template values were not being found from the .Environment.Values map .. and it turned out that it was because the K8s context we were referencing in both context and helmDefaults.kubeContext were not available on the CI server.
Two issues here, and possible suggested solutions:

At no point did Helmfile give any indication that the context in the config wasn't available.

Would it be possible to fail with a better error message if this happens?

Should the values in the template not be resolved first, and not be dependant on being able to reach the K8s api?

In this instance just a change to ordering might also help determining where a failure happened.

A failure saying template values are missing, when the issue was an incorrect Kube config, lead us down a very long winding rabbit hole, and hopefully logging this will help someone else down the road :)

@madAndroid Hi! I read this twice but I still don't understand - Helmfile doesn't depend on context nor helmDefaults.kubeContext to render environment values.
Are you, by any chance, calling out to kubectl by using the exec template function to obtain a few dynamic values from the live cluster to be fed into environment values?

Apologies for the delayed response ..  yes, that's what we would have expected as well, but it appears to have been the behaviour we experienced .. I'm going to see if I can reproduce this as minimally as possible, and reply back here

@madAndroid Thanks! Do you use environment secrets, releases[].secrets, helm-secrets, helm-tiller/releases[].tillerless in your setup?

Yes we do, the helm-secrets plugin, and encrypt the values using SOPs and KMS in AWS

@madAndroid Which one do you user, enviroments[].NAME.secrets, or releases[].secrets?

the first: enviroments[].NAME.secrets ... here is the Helmfile (actual values changed to protect the innocent ;) ) :
repositories:
  - name: our-helm-repo
    url: s3://our-helm-repo/charts

environments:
  dev:
    secrets:
      - ../../environments/dev/secrets.lab.yaml

releases:
  - name: chart
    namespace: namespace
    chart: our-helm-repo/chart
    version: 0.1.0
    values:
      - ../../environments/dev/eu-west-1.yaml.gotmpl

@madAndroid Thanks! Now I'm trying to reproduce it:
$ ../helmfile --helm-binary helm3 template
Adding repo our-helm-repo s3://our-helm-repo/charts
in ./helmfile.yaml: helm3 exited with status 1:
  helm.go:71: context "k8s-jenkins-dev" does not exist

🤔

That's interesting, with the Helm 2 version we were using, we didn't get a message about the missing context, only about missing variables in the template - I'll try using the latest version of Helmfile as well, we're currently using v0.97.0 (Helm version is v2.13.1)


[App Configuration] Failed to run sample failing in nightly runs

App Configuration nightly test runs are failing with:

Stack trace:
RestError:
{
"name": "RestError",
"statusCode": 404,
"request": {
"streamResponseStatusCodes": {},
"url": "***/kv/secret1641261418170?api-version=1.0",
"method": "GET",
"headers": {
"_headersMap": {
"accept": "application/vnd.microsoft.appconfig.kv+json, application/json, application/problem+json",
"user-agent": "azsdk-js-app-configuration/1.3.2 core-http/2.2.3 Node/v12.22.8 OS/(x64-Windows_NT-10.0.17763)",
"x-ms-client-request-id": "4e1deb88-d4ac-435d-97d6-fcf292a56c70",
"x-ms-date": "REDACTED",
"x-ms-content-sha256": "REDACTED",
"authorization": "REDACTED",
"cookie": "REDACTED"
}
},
"withCredentials": false,
"timeout": 0,
"requestId": "4e1deb88-d4ac-435d-97d6-fcf292a56c70"
},
"details": {},
"message": ""
}

For more details check here:

https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1272078&view=results

Should be green now, with https://github.com/Azure/azure-sdk-for-js/pull/19957 :)


Fix numpy deprecates np.float data type

I just found this error if its useful.
import easyidp as idp
print(idp.__version__)
ms = idp.Metashape("/Users/benweinstein/Dropbox/Weecology/everglades_species/easyidp/Hidden_Little_03_24_2022.psx", chunk_id=0)

2.0.0.dev4

Traceback (most recent call last):
  Python Shell, prompt 4, line 3
    pass
  File "/Users/benweinstein/.conda/envs/BirdDetector/lib/python3.9/site-packages/easyidp/metashape.py", line 107, in __init__
    self.open_project(project_path, chunk_id)
  File "/Users/benweinstein/.conda/envs/BirdDetector/lib/python3.9/site-packages/easyidp/metashape.py", line 174, in open_project
    self.open_chunk(self.chunk_id)
  File "/Users/benweinstein/.conda/envs/BirdDetector/lib/python3.9/site-packages/easyidp/metashape.py", line 246, in open_chunk
    chunk_content_dict = read_chunk_zip(
  File "/Users/benweinstein/.conda/envs/BirdDetector/lib/python3.9/site-packages/easyidp/metashape.py", line 1145, in read_chunk_zip
    chunk_dict["transform"] = _decode_chunk_transform_tag(transform_tags[0])
  File "/Users/benweinstein/.conda/envs/BirdDetector/lib/python3.9/site-packages/easyidp/metashape.py", line 1284, in _decode_chunk_transform_tag
    transform.rotation = np.fromstring(chunk_rotation_str, sep=" ", dtype=np.float).reshape((3, 3))
  File "/Users/benweinstein/.conda/envs/BirdDetector/lib/python3.9/site-packages/numpy/__init__.py", line 305, in __getattr__
    raise AttributeError(__former_attrs__[attr])
builtins.AttributeError: module 'numpy' has no attribute 'float'.
`np.float` was a deprecated alias for the builtin `float`. To avoid this error in existing code, use `float` by itself. Doing this will not modify any behavior and is safe. If you specifically wanted the numpy scalar type, use `np.float64` here.
The aliases was originally deprecated in NumPy 1.20; for more details and guidance see the original release note at:
    https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations

import numpy as np
print(np.__version__)

1.24.2

What was the solution here?


Install compilers through Travis Apt-addon

Install compilers through Travis Apt-addon.
Unfortunately, sudo is still required for installing valgrind, without it would be possible to run on (faster) travis containers.

Great: thanks! Feasibly we can build valgrind or make a non-root installation of it (this is how I do it at work).


Update Article: Desktop App Group / RemoteApp App Group Assignment

Service: Windows Virtual Desktop
URL: https://docs.microsoft.com/en-us/azure/virtual-desktop/environment-setup
Section: App groups
Issue:
"A user can be assigned to both a desktop app group and a RemoteApp app group in the same host pool. However, users can only launch one type of app group per session. Users can't launch both types of app groups at the same time in a single session.
A user can be assigned to multiple app groups within the same host pool, and their feed will be an accumulation of both app groups."
Comment:
This is no longer correct I believe? I am successfully able to assign both RemoteApp and Desktop App Groups to users running off a single host pool, as well as run those sessions simultaneously.

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

ID: b7a8e997-f5c8-eaa8-b713-068650dd6b22
Version Independent ID: ef57850d-1fc4-bc6a-827c-2934c31f50c9
Content: Windows Virtual Desktop environment - Azure
Content Source: articles/virtual-desktop/environment-setup.md
Service: virtual-desktop
GitHub Login: @Heidilohr
Microsoft Alias: helohr

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.
@Heidilohr Hello Heidi, could you please check on this issue and update the document if needed? Thanks.

This issue was never tagged correctly and therefore not reported on. Closing the loop - the article has been updated since this issues was created to say that while it might technically be possible, "We don't support assigning both the RemoteApp and desktop application groups in a single host pool to the same user. Doing so will cause a single user to have two user sessions in a single host pool."
#please-close


Image thumbnail with sftp disk

Describe the bug
When connecting to a sftp disk there is no image overview/thumbnail.

I don't think thumbnails work on ftp/sftp as we only generate a url through Laravel's Filesystem implementation


[connectivity] Can't get wifiName (SSID) on iOS 12 and later

My understanding is that without a paid Apple Developer account, there is no way to get the WiFi name on iOS 12 and later.
If you verified, that my understanding of the issue is correct, I would update the documentation for the method(s)
The connectivity plugin enables developers to obtain the current Wi-Fi network's SSID using the getWifiName method.
The documentation for this method alredy mentions that it doesn't work on emulators and returns null.
Unfortunately, getWifiName doesn't work even on real Apple devices on iOS 12 and later. I verified this on devices with iOS prior to 12 and getting the wifi SSID worked as expected, however, after updating the same device to iOS 12, the getWifiName returns null.
The Flutter plugin on iOS relies on CNCopyCurrentNetworkInfo which on iOS 12 and later requires the com.apple.developer.networking.wifi-info entitlement.

(CNCopyCurrentNetworkInfo) To use this function in iOS 12 and later, enable the Access WiFi Information capability in Xcode. For more information, see Access WiFi Information Entitlement.

Requesting this entitlement successfully is (AFAIK) only available if the developer joined the Apple Developers Program (I'm currently waiting for Apple's approval so I cannot verify this, but I found hints that it could be the issue). On Apple's page for Advanced App Capabilities, they  don't list Access WiFi Information capability and I couldn't find it in Xcode either (Note: Access WiFi Information capability  is not the same as Wireless Accessory Configuration)
I think this information is important when using the connectivity plugin to fetch the WiFI SSID (and BSSID, in case my https://github.com/flutter/plugins/pull/1331 pull request for the connectivity plugin gets merged).
All I wrote might be common knowledge amongst iOS developers already but as Flutter developers do not always have strong, multiplatform mobile development background, we should point out in the documentation in which cases the methods are expected to work and what the developers need to do to fix the issues in other cases (e.g.: get paid dev account with Apple or use older iOS version for testing).

I got the same error

I had time to confirm it using my new Apple developer account.
Developers need to have a paid account in order to see the toggle for the "Access WiFi Information" capability. Without a paid account, that toggle was not visible. Once I added that capability to the connectivity plugin's example app in Xcode, the example app could receive the SSID (wifiName) even on iOS v12+.

I'm going to submit a pull request clarifying this in the documentation for the connectivity plugin the next week.

It works in iOS 12 connectivity ?
Il giorno mar 26 mar 2019 alle 10:13 Vince Varga<EMAIL_ADDRESS>ha scritto:

I had time to confirm it using my new Apple developer account.
Developers need to have a paid account in order to see the toggle for the
"Access WiFi Information" capability. Without a paid account, that toggle
was not visible. Once I added that capability to the connectivity
plugin's example app in Xcode, the example app could receive the SSID (
wifiName) even on iOS v12+.
[image: Screen Shot 2019-03-26 at 10 07 04]
https://user-images.githubusercontent.com/9061239/54984548-5d9dbb00-4faf-11e9-8c12-d798d2f5c565.png
I'm going to submit a pull request clarifying this in the documentation
for the connectivity plugin the next week.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/29216#issuecomment-476536011,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVdMg5EbBztog-x5djyqlHhXFIKRMFT7ks5vaeSugaJpZM4bqeOV
.

--
Allan Nava
direct: +39 340 94 77 141
<EMAIL_ADDRESS><EMAIL_ADDRESS>

Yes, the connectivity plugin works well on iOS 12+ if you enable the "Access WiFi Information" capability. However, you need the paid account to enable the "Access WiFi Information" capability, and without a paid account, you will not see the "Access WiFi Information" capability in the Capabilities list.
On versions before 12+, the connectivity plugin works even without a paid developer account, because getting the wifi name wasn't restricted to apps with "Access WiFi Information" capability

@vargavince91 thank you!
Closing the issue since fixed
https://pub.dev/packages/connectivity


CSS via require not disposed

Not sure which repo to post this to, but the router makes the most sense.
Styles imported via <require> are not disposed properly, while styles via <style> tags are. Is this expected?
Plunkr: http://plnkr.co/edit/gwgBLSLV6OUMHWO7DolL

ping @EisenbergEffect

I actually don't quite understand this issue. What do you mean by "disposed"? What is it that you are expecting?

Sorry. By disposed I mean removed from the <head> after the view that contains the <require> tag has been unloaded.
I have updated the plunker to hopefully make this more clear: http://plnkr.co/edit/dh3ia6AkB7ZHRvy4m27

I'll look into this and see if it's something we can do.

@EisenbergEffect Can this be closed or moved? It doesn't seem like a router issue.

Yes. We aren't going to do anything with this for the immediate future.


Not Angular 2 Compatible

The documentation states this is an Angular 2 compatible module. Issues #139 and #154  show an error that is caused by compatibility issues between Angular2 and Angular4.

Version 0.3.0 was the last version compatible with Angular 2.x, after this version a commit was made to introduce Renderer2 which is only available in Angular 4+
The versioning is not semantic versioning and there is a breaking change from v0.3.0 to v0.3.1.
Please address this.

Sorry about that. We don't currently support SemVer, but will try to do this in the future. For now, if you need to use older versions of Angular please look at the history of package.json & find the commit with the correct angular dependencies for your project & use that specific commit (or npm version) in your project's package.json (without ^or ~ ). Unfortunately this means you won't get any bug fixes or new features until you upgrade to a newer version of Angular.
Sorry for the inconvenience.
Closing this for now.
If you know of a way to support both older & newer versions of Angular with the current code base (ex: downgrading version #s in package.json), please submit a pull request. Thanks.