Firestore PlatformException(Error performing get, Failed to get document because the client is offline., null

Describe the bug
I'm getting the below PlatformException in a FutureBuilder when using an app.release.apk on an Android phone.
I noticed that if I have the app open and I just close the phone, after opening it and visiting an item from a ListView generates the error, sometimes following visits to other items causes the exception, sometimes not.
To Reproduce
Steps to reproduce the behavior:

Open app
Go to a list view
Close the phone
Open phone after 5 - 10 min
Click on any list view item
Exception happens

Expected behavior
I expect the call to Firestore to return data for a specific document.
Additional context
Below is the code I use to make the request
item-db.dart
  Future<DocumentSnapshot> getItem(itemID) {
    try {
      DocumentReference ref = _db.collection("content").document(itemID);
      return ref.get();
    } catch (error) {
      print(error);
    }
    return null;
  }

item.dart
Future<DocumentSnapshot> _itemFuture;

@override
  void initState() {
    super.initState();
    _itemFuture = _itemDB.getItem(widget.item.documentID);
}

    FutureBuilder<DocumentSnapshot>(
        future: _itemFuture, // a previously-obtained Future<String> or null
        builder:
            (BuildContext context, AsyncSnapshot<DocumentSnapshot> snapshot) {
          List<Widget> children;
          if (snapshot.hasData) {
            children = <Widget>[Expanded(child: _itemBody(snapshot.data))];
          } else if (snapshot.hasError) {
            children = <Widget>[
              Icon(
                Icons.error_outline,
                color: Colors.red,
                size: 60,
              ),
              Padding(
                padding: const EdgeInsets.only(top: 16),
                child: Text('Error: ${snapshot.error}'),
              )
            ];
          } else {
            children = <Widget>[
              SizedBox(
                child: CircularProgressIndicator(),
                width: 60,
                height: 60,
              ),
              const Padding(
                padding: EdgeInsets.only(top: 16),
                child: Text('Awaiting result...'),
              )
            ];
          }
          return Center(
            child: Column(
              mainAxisAlignment: MainAxisAlignment.center,
              crossAxisAlignment: CrossAxisAlignment.center,
              children: children,
            ),
          );
        },
      );

pubspec.yaml
cloud_firestore: ^0.13.7
firebase_auth: ^0.16.1

Flutter doctor
Run flutter doctor and paste the output below:
[✓] Flutter (Channel stable, v1.17.5, on Mac OS X 10.15.5 19F101, locale en-RO)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 11.3.1)
[!] Android Studio (version 3.5)
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
[✓] VS Code (version 1.46.1)
[✓] Connected device (1 available)

! Doctor found issues in 1 category.

duplicate of https://github.com/FirebaseExtended/flutterfire/issues/2498

@TahaTesser I see that the other issue doesn't have a solution. Is this a known issue? We are finished with development and this is holding back everything.

@William-cpu
This is the duplicate, original issue/known issue is still open hence not fixed yet
Please thumbs up mentioned issue to raise priority

Yes. It is open. My mistake. Thank you.


product details with extra information

array(21) { ["vendor_url"]=> NULL ["id"]=> string(1) "1" ["folder"]=> string(10) "1550216421" ["image"]=> string(6) "a1.jpg" ["time"]=> string(10) "1550216686" ["time_update"]=> string(10) "1550216807" ["visibility"]=> string(1) "1" ["shop_categorie"]=> string(2) "37" ["quantity"]=> string(1) "2" ["procurement"]=> string(1) "1" ["in_slider"]=> string(1) "1" ["url"]=> string(59) "Harpa_Casual_th_Sleeve_Floral_Print_Womens_Multicolor_Top_1" ["virtual_products"]=> string(0) "" ["brand_id"]=> string(1) "3" ["position"]=> string(1) "2" ["vendor_id"]=> string(1) "0" ["title"]=> string(61) "Harpa Casual 3/4th Sleeve Floral Print Women's Multicolor Top" ["description"]=> string(82) "
following details occuered under product information in view page

@aswinsasi  fixed - https://github.com/kirilkirkov/Ecommerce-CodeIgniter-Bootstrap/commit/1dd3662a4e122457c00a8bef7f10a609e6f90e1f

Thank you sir
On Mon, Feb 25, 2019, 17:45 Kiril Kirkov<EMAIL_ADDRESS>wrote:

Closed #151
https://github.com/kirilkirkov/Ecommerce-CodeIgniter-Bootstrap/issues/151
.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kirilkirkov/Ecommerce-CodeIgniter-Bootstrap/issues/151#event-2161554625,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AdGuQYen8NrgI_zidUZuX94fh1tM3Kmhks5vQ9PxgaJpZM4bN1Oe
.


[Request] Add Cloudfront invalidation after transformed images back to S3

I'll preface this by saying my knowledge is limited and I might not be using the correct terminology so excuse me :-)
I've noticed that on pages with a number of image transformations that there can be a timing issue with hitting the Cloudfront URL before the transformed images have finished uploading back to S3.
I found another plugin that does invalidation but maybe it would be good to trigger something like this after the upload process to S3 has finished?
Here's what was happening in my case:

User hits webpage that isn't cached
Template loaded, imager triggered (pulls source asset from S3, resizes, pushes back to S3), returns with the Cloudfront URL rather than S3 url.
User's browser loads rendered/cached webpage, hitting the Cloudfront url to the image... but that image hasn't finished uploading to S3 so Cloudfront returns 404.

So I was thinking if there was a way to trigger Cloudfront to re-cache the image after the upload process has been confirmed as complete?
Thoughts?

Cloudfront invalidation is a good idea. I've actually run into problems myself with transforms not invalidating when using Cloudfront with S3. I'll have a look at it.
That said, I don't really understand why this would be a problem in your case. The file should be done uploading to S3 before the template is rendered and the user hits it. Unless there's a second user that hits the same page between the transform is generated in the imager system path, and the file being uploaded to S3.. I can see that happening for high-traffic scenarios.. Do you have alot of traffic on the site you're seeing this on?
Anyways, it'd be nice to have cloudfront invalidation in there for other scenarios too, so. I'll look into it. :)

This has been added to 1.2.0. Read the documentation for config settings (and a "please note" warning).


irrelevant .bin package

As you see below there is a package called .bin on "Packages" section. If you click on it you will see this package relevant with atom-typescript.

OSX 10.10.3
Atom 0.204
All packages are updated

Issue is that apm install (like npm install) creates a .bin directory copying the contents of any .bin files. It makes sense for npm but not for apm. Needs to be reported to the atom team. I'll make that issue report when I have time. Till then this should not cause any issues.

Can't find an issue about this in atom/atom, have someone submitted it yet?

have someone submitted it yet?

nope. I feel it harmless which is why I didn't

Ok, I'll open an issue about this on atom's issue tracker referencing this issue. Sure it's harmless but it's still anoying to have a "package" in the list which isn't a package.

atom/settings-view#348

@basarat Could you close this? The relevant bug is already linked.

Thanks. Please follow : https://github.com/atom/settings-view/issues/348 for tracking :rose:


Odo Expandable - An simplistic, expandable UI Component

Odo Expandable
A simple, accessible combination of two elements; A trigger to handle clicks, and a target to toggle visibility.
Overview
Odo Expandable can serve multiple different purposes. The simplest one is the situation where you have a single button element that you would like to use to toggle a class on another target element. But adding the two data attributes to each Odo Expandable will create the delegated click listeners and handle the toggling for you with no other configuration.
Odo Expandable also can create easy-to-use accordions with only the addition of another "group" attribute. When expandables are grouped together clicking one will toggle it's own visibility while collapsing all other instances.
JavaScript
expandable.js and expandable-group.js have been included to control both single Expandable instances as well as groupings of multiple Expandable instances. Tests for each have been added by the use of two fixtures.
CSS
No CSS is needed for Expandable. Users can target the expandable__trigger--open and expandable__target--open` classes in their CSS to alter the states of the expanded trigger and target.
Use
A static initializeAll(); method has been included which will instantiate all instances of single and grouped Expandables.

I think it would be really nice if we added accordion animations (like the accordion on we.odopod) and scrolling-to-the-opened-trigger.

Thanks for the review. I'll make the syntax updates you mentioned and add some additional instantiation options.
As far as the scrolling behavior, I wasn't sure if that would be better equipped as a subclass that overrode the toggle method. Or if it would be an optional thing.
Optional animations could be definitely added.

A subclass which does those extra things could work.

Did you want to do the subclass in a separate PR or in the same one?

TODO: Update tests with coverage for new features.
In this update:
Added a new ExpandableAccordion which includes built in animations and viewport scrolling. These can be instantiated via code or using the same initializeAll() function that was used before.


added Vagrantfile to run the stack

I found this project really useful, thanks for making it available!
I like to use Vagrant as a part of the Hashicorp-flow when deploying stuff, so I created a Vagrantfile for running the project automaticly. It might be usefull for more people.

Branches are not really documented on this project, but we do already have a Vagrant based stack: https://github.com/deviantony/docker-elk/tree/vagrant
Thanks ;)

Ah did not catch that. Great work!


let => var

Please merge. Breaking our build via marko. Thanks 👍

Sorry about that! I had just published a new version with the fix before I saw this PR<EMAIL_ADDRESS>does not use let.

can you publish latest to npm? still breaking builds. thx!
On Thu, Jul 14, 2016 at 1:57 PM, Patrick Steele-Idem <
<EMAIL_ADDRESS>wrote:

Closed #1
https://github.com/patrick-steele-idem/property-handlers/pull/1.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/patrick-steele-idem/property-handlers/pull/1#event-723582182,
or mute the thread
https://github.com/notifications/unsubscribe/ABtipiuOLJjZdHLQK6dfb9EHUYQtYbEyks5qVqKpgaJpZM4JMybN
.


add code_arm_required to manual alarm

Description:
Add code_arm_required to the manual alarm as per the mqtt alarm. This option bypasses the code check if code_arm_required is false.
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#9088
Example entry for configuration.yaml (if applicable):
alarm_control_panel:
  - platform: manual
    code: 1234
    code_arm_required: False

Checklist:

[ ] The code change is tested and works locally.
[ ] Local tests pass with tox. Your PR cannot be merged unless tests pass
[ ] There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

hi, can you also have a look at this issue?
https://github.com/home-assistant/home-assistant/issues/22263

Hey. I already saw your issue and started to look into it. The issue is with the front end. I'm still looking at how it works but I think fixing it should be straight forward.

Ok ;)
Thnx for looking into it


WIP: Unpin coverage

Unpinning coverage to see if it will work ok.

Doesn't seem to be sending the coverage, which is bad. Going to try upgrade python-coveralls on conda-forge to see if that fixes it.

Seems Mac builds are backed up on conda-forge, which is going to slow down the merge of those PRs. Will let this sit for now until that can proceed.

Replaced by PR ( https://github.com/nanshe-org/nanshe/pull/452 ), which has been merged.


Why does memory accumulate and ultimately cause overflow when running get_activations.py?

It's better to load batch and save batch to avoid overflow.

It seems that the data that has already obtained the activation  is still occupying memory and has not been properly released

It seems that there's a memory leak.
Below are lines 65-69 in the original code:
    for prompt in tqdm(prompts):
        layer_wise_activations, head_wise_activations, _ = get_llama_activations_bau(model, prompt, device)
        all_layer_wise_activations.append(layer_wise_activations[:,-1,:])
        all_head_wise_activations.append(head_wise_activations[:,-1,:])

Which I changed into:
    for prompt in tqdm(prompts):
        layer_wise_activations, head_wise_activations, _ = get_llama_activations_bau(model, prompt, device)
        all_layer_wise_activations.append(layer_wise_activations[:,-1,:].copy())
        all_head_wise_activations.append(head_wise_activations[:,-1,:].copy())

And it works.

@Wooorry Thank you! I just added the two copy() in branch master.


Add install functions and prepare for distribution

https://apps.apple.com/app/github/id1477376905?ls=1


Why is getVolume typed as number | VolumeResult?

/**
 * Get the current device volume.
 * @param {AndroidVolumeTypes} type - The type of volume you want to retrieve. Defaults to 'music' (Android only, no-op on iOS).
 * @returns {Promise<VolumeResult>} - Returns a promise that resolves to an object with the volume value.
 *
 * @example
 * ```ts
 * const { volume } = await VolumeManager.getVolume('music'); // type is no-op on iOS
 * ```
 */
export async function getVolume(
  type: AndroidVolumeTypes = 'music'
): Promise<VolumeResult | number> {
  return await VolumeManagerNativeModule.getVolume(type);
}

With the return type of getVolume() being Promise<VolumeResult | number>, wouldn't the example code fail: const { volume } = await VolumeManager.getVolume('music');
Perhaps the number type may be removed as a return type?

The getVolume function returns varying results for Android and iOS. For iOS, it simply returns a number, whereas for Android, it yields a VolumeResult. I must revisit this issue, as it potentially indicates a less-than-optimal type design.

Fixed in https://github.com/hirbod/react-native-volume-manager/releases/tag/v1.6.0
This release is a breaking change.

@hirbod good choice - thanks for the new release!


[Mega Backport 2.x] Backports PRs with backport-failed labels that weren't actually backported

Description
Backports PRs with backport-failed labels that weren't actually backported.

Category : Maintenance
This is done to clean-up of the backport-failed label so it's easy for release manager to keep track of any failed backports for upcoming release.

Is this a backport? If so, please add backport PR # and/or commits #
Backports:

#2290
#3339
#3562
#3706
#3742
#3792
#4052
#4063
#4292
#4417
#4482
#4584

Do these changes introduce new permission(s) to be displayed in the static dropdown on the front-end? If so, please open a draft PR in the security dashboards plugin and link the draft PR here
Testing
[Please provide details of testing done: unit testing, integration testing and manual testing]
Check List
~- [ ] New functionality includes testing~
~- [ ] New functionality has been documented~
~- [ ] New Roles/Permissions have a corresponding security dashboards plugin PR~
~- [ ] API changes companion pull request created~

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

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

@stephen-crawford @RyanL1997 Would you mind removing backport-failed labels from the items related to OBO and identity plugin here: https://github.com/opensearch-project/security/pulls?page=1&q=is%3Apr+label%3Abackport-failed+is%3Aclosed.
If these items have not been backport please feel free to add commits here.


about train result

May I ask why all the detection results are zero after I switched the backbone and trained on COCO? Could you please share the training logs from your training session?

May I ask why all the detection results are zero after I switched the backbone and trained on COCO? Could you please share the training logs from your training session?

If you change the batch size, you should change the lr. (reducing the lr )

May I ask why all the detection results are zero after I switched the backbone and trained on COCO? Could you please share the training logs from your training session?

If you change the batch size, you should change the lr. (reducing the lr )
”You need to download HRNet-W32 imagenet pretrained model (see above) and change the checkpoint path by modifying MODEL.PRETRAINED in .yaml, and run following commands“


Unable to make POST request?

Hey!
I am trying to get all the groups the logged-in user is a member of, but when I make the request the script hangs and doesn't execute beyond the API call without any error. I must be missing something.
$provider = new TheNetworg\OAuth2\Client\Provider\Azure([
	'clientId'          => 'myclientid',
	'clientSecret'      => 'myclientsecret',
	'redirectUri'       => 'myredirecturl'
]);

if (!isset($_GET['code'])) {
	// If we don't have an authorization code then get one
	$authUrl = $provider->getAuthorizationUrl();
	$_SESSION['oauth2state'] = $provider->getState();
	header('Location: '.$authUrl);
	exit;

// Check given state against previously stored one to mitigate CSRF attack
} elseif (empty($_GET['state']) || ($_GET['state'] !== $_SESSION['oauth2state'])) {

	unset($_SESSION['oauth2state']);
	exit('Invalid state');

} else {
	// Try to get an access token (using the authorization code grant)
	$token = $provider->getAccessToken('authorization_code', [
		'code' => $_GET['code'],
		'resource' => 'https://graph.windows.net',
	]);

	echo "getMemberGroups:<br>";
	$groupMember = $provider->post("me/getMemberGroups", ["securityEnabledOnly" => false], $token);
	var_dump($groupMember);
}

What's wrong?

Worth checking that the authorization and access token endpoints you are using are consistent with the resource API. The current (V2) endpoints are:
https://login.microsoftonline.com/common/oauth2/v2.0/authorize
https://login.microsoftonline.com/common/oauth2/v2.0/token
set in  oauth2-azure => Azure.php using ENDPOINT_VERSION_1_0 or ENDPOINT_VERSION_2_0;
The corresponding Graph API is https://graph.microsoft.com/     at version 1.0
I am assuming you are trying to use the V1 endpoints as a getAccessToken to V2 does not support the 'resource' property

Also, what version of the library are you using?

Worth checking that the authorization and access token endpoints you are using are consistent with the resource API. The current (V2) endpoints are:
https://login.microsoftonline.com/common/oauth2/v2.0/authorize
https://login.microsoftonline.com/common/oauth2/v2.0/token
set in oauth2-azure => Azure.php using ENDPOINT_VERSION_1_0 or ENDPOINT_VERSION_2_0;
The corresponding Graph API is https://graph.microsoft.com/ at version 1.0
I am assuming you are trying to use the V1 endpoints as a getAccessToken to V2 does not support the 'resource' property

These are the variables in my Azure.php file, they look okay:
public $urlLogin = 'https://login.microsoftonline.com/';

public $pathAuthorize = '/oauth2/authorize';

public $pathToken = '/oauth2/token';

public $scope = [];

public $scopeSeparator = ' ';

public $tenant = 'common';

public $urlAPI = 'https://graph.windows.net/';

public $resource = '';

public $API_VERSION = '1.6';

public $authWithResource = true;

Also, what version of the library are you using?

Not sure where to check the version. I believe I am using the latest version because I downloaded the library just yesterday.
Calling the me API call works fine for me so not sure that's the problem.
Some more details:
This is a multi-tenant situation.
The tenant my users are authenticating from is not the same one as the one the app is registered (again, shouldn't be an issue but just fyi)

In AAD, is  'Supported account types' set to "Accounts in any organizational directory"?
The default is single tenant.

In AAD, is 'Supported account types' set to "Accounts in any organizational directory"?
The default is single tenant.

Yep, already took care of that when I registered the app.
Perhaps this may have something to do with the fact getMemberGroups requires admin consent? I did give admin consent but like I said earlier I'm probably missing something here.
I really wish we could get an error code to debug what's wrong.

Alright so I am not entirely sure but I suspect this issue (and another issue we have been experiencing) is due to the fact the tenant from where our users come and sign in from did not give admin consent to getMemberGroups and that's why there is problems, despite the fact that we gave admin consent for everything in our tenant.
Curiously, when users try to sign in they are prompted to provide justification for using the application along with it's required permissions and upon clicking 'submit', they get error AADSTS90097 which gives the simple vague message: "An error has occured during admin consent processing.".
Error code AADSTS90097 isn't even listed on Microsoft's list of error codes, weird.

So the application is multi-tenant. Can you please share the admin consent address? I can try to approve it in my own tenant to see.

Where can I find the admin consent address?

You have to build it or generate it, more here: https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/grant-admin-consent
Sample implementation, against an older version of this library is here: https://github.com/TheNetworg/DreamSpark-SSO/search?q=consent

Sorry, but I can't share the admin consent address. I would if I could.
Although, I plan to perform your test myself and I'll post what I find, but I am still pretty confident what I said earlier is the problem (tenant hosting the users did not give admin consent)
Also, I'll take a look at that sample implemention.
Thanks for all the help so far 👍


Increase JWS's ability to validate

What is the feature you are proposing?
I would like to send a PR to make the following mandatory, as they are not currently verified. (JSON Web Signature)
https://jwt.io/libraries
Header

[ ] kid

Payload

[ ] iss
[ ] sub
[ ] aud
[ ] jti
[ ] typ

Algorithm

[x] RS*: #2339
[ ] PS*
[ ] ES*
[ ] EdDSA

If verification is required, it would be Breaking Changes, but since there is no change in function signatures, it may be difficult to decide whether to treat it as Breaking Changes or not 🤔

Hi @Code-Hex !
This is a great challenge!

If verification is required, it would be Breaking Changes, but since there is no change in function signatures, it may be difficult to decide whether to treat it as Breaking Changes or not 🤔

Hmmm. I think it's a breaking change because requiring verification could stop something that was working before 🤔
Nevertheless, we can provide additional algorithms in minor versions or patch releases, so let's do that now!

@yusukebe Thanks! I'll put out the PRs in order.

Glad to see this... I tend to prefer RS* for JWT.. though I also tend to try to support multiple signers sometimes... so usually have to create my own middleware to do JWT checks, so may just do this with the jose library.


Job board title change

Hi!
I would like to change the job board header title:

I found the line of code where I can do this:

Can I change this? Or is this an exact match with my Bullhorn account, and therefore needed for a pairing with the back-end?
Thanks in advance!!

Well we changed ours and no issues.. http://take.ms/TG0w5

That can be changed to whatever you like without affecting the job listings.  It changes what you see at the top, and what company name you see in the EEOC tooltips (if enabled)

Great, thank you so much!!

Can we change it to something like ‘current openings’ across the board. Who uses company name over there and why?

On Dec 5, 2018, at 7:50 AM, NetworklinkHaarlem<EMAIL_ADDRESS>wrote:
Great, thank you so much!!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Yes it can be set to be any string of text


feat: added bm25 for italian language

Hi,
imitating Qdrant/bm25 I added a model for Italian.
I hope the PR is done correctly to your standards.
Issue #312

Hi @nickprock
We're thinking about adding a support for a wider range of languages (all languages supported by the stemmer), and we have a slightly different approach in mind (we'll extend Qdrant/bm25 with stopwords for other languages)

Ok, thanks, I'll do.


Completion providers with resolve methods leak memory

Here's a fake completion provider that returns 20k items. Its resolve method does nothing (but exists, so that VS Code thinks it may be used - that seems to be important).
export class FakeCompletionItemProvider implements CompletionItemProvider {
	public async provideCompletionItems(
		document: TextDocument, position: Position, token: CancellationToken, context: CompletionContext,
	): Promise<CompletionList> {

		const items: CompletionItem[] = Array<CompletionItem>(20000);
		for (let i = 0; i < items.length; i++) {
			const item = new CompletionItem(`Item ${i}`);
			item.filterText = `${item.label}???`;
			item.kind = CompletionItemKind.Constant;
			item.detail = "(deprecated)";
			item.documentation = "docs";
			item.insertText = `${item.label} !!`;
			item.keepWhitespace = true;
			item.commitCharacters = ["["];

			item.command = {
				command: "editor.action.triggerSuggest",
				title: "Suggest",
			};
			items[i] = item;
		}
		return new CompletionList(items);
	}

	public async resolveCompletionItem(item: DelayedCompletionItem, token: CancellationToken): Promise<CompletionItem | undefined> {
		return undefined;
	}
}

If you register this provider, then repeatedly invoke completion (I found the easiest way to do this was inserting lots of newlines then hitting Ctrl+Space then Backspace repeatedly), the memory grows continiously and is never reclaimed.

I believe this may be what my users are seeing in https://github.com/Dart-Code/Dart-Code/issues/1721 and https://github.com/flutter/flutter/issues/33280 and I saw in https://github.com/microsoft/vscode/issues/74390. After many the extension host crashes being out of memory.
@jrieken FYI (relates a little to what I was trying to repro with https://github.com/microsoft/vscode/issues/74418, but did badly because I removed resolve).

Running the test I had for #74418 the result is much more obvious:
Total run took 59028 ms heap change was 270 MB // without resolve
Total run took 81234 ms heap change was 1597 MB // with (empty) resolve

I can confirm that the executeCompletionItemProvider leaks but very scary is that the completion model itself doesn't seems to be disposed (tho all the code for it should be in place)

wow - this is a good fix. thanks @DanTup

np! Hope it's an easy fix. I'd planned to disable our unimported-file completions in the next release, but assuming you can get this into the May release I think I'll just leave it for people to tolerate (or manually disable) until then 👍

wait, I do see the $releaseCompletionItems message being send. That happens whenever a suggest session end, e.g the widget closes or suggest is retriggered. Debugging this shows that the item cache is cleared.

There is the leak when using the command but I am not so sure about the leakage in normal use anymore.
@DanTup Still thanks for this issue (nuked my previous comment with some false claims)

There is the leak when using the command but I am not so sure about the leakage in normal use anymore.

My repro above is normal use (not calling the command from a test, but triggering from the editor):

"I found the easiest way to do this was inserting lots of newlines then hitting Ctrl+Space then Backspace repeatedly"

Can you repro it doing that? (I don't know if it's important to cancel the completion prior to it being rendered with the list, but that's what I was doing).

@DanTup Can you start with --logExtensionHostCommunication and check for a $releaseCompletionItems message being send from the window to the extension host process? That message should be send to clear the result of a provide call (give the provider has a resolve-function)

To clarify further - below screen capture shows how thing relate, the reply to the request (145) contains the id of the result (4) which is then used in the release-call

Can you start with --logExtensionHostCommunication and check for a $releaseCompletionItems message being send from the window to the extension host process?

I switched to Insiders and updated to ensure there's nothing changed since stable, but I still see it. Doing what you see, as far as I can tell there is not a call to release.
Here, I hit Ctrl+Space, Backspace, Ctrl+Space so that there were two requests for completion, and the first was cancelled (but seems not released).

Wait, further down I did get:
113 - request: ExtHostLanguageFeatures.$releaseCompletionItems( 2 3 )

But if I run it a lot of times, then the number of releases don't seem to match the number of requests?

Maybe it's a race? If the client doesn't get the results (due to cancelling), does it assume it doesn't need to release them - even though the extension host may have added them to some cache?

Is there any good way to filter this log, so I can easily see the completion requests and their replies, without other noise?

Yeah, that could be it. The request is being cancelled (which means the UI never gets a result) but if the provider still returns something then we keep it forever

If it helps, here is a log from my running completion multiple times and seeing this. My guess is that there are missing releases, but it's hard to match all the requests up :-)

but it's hard to match all the requests up.

I am simply counting find matches, e.g. there are 5 provider-calls and only 1 release-call, and 4 cancel. I guess dart returns a result despite the cancellation token being in cancel-state, then it's us also not honouring that token and caching the items forever.
I has a fix ready which makes sure we never cache when cancellation happened...

Closing this with my fix (https://github.com/microsoft/vscode/commit/034165ac674c36131429301aea78fea7877acb72). @DanTup Thanks for the help!

I guess dart returns a result despite the cancellation token being in cancel-state, then it's us also not honouring that token and caching the items forever.

Today it does, though vNext checks the tokens and bails out. The testing done just above was using the fake provider I listed right at the top of here though, which has no async work in (so I presume the cancellation token couldn't have been updated since it's single-threaded?).
I don't have all the stuff set up to build VS Code locally since reinstalling Windows (maybe you can make that work in a container ;-)) but I'll test itout tomorrow in Insiders with the stuff above and my real extension.
Thanks for the quick investigation and fix :-)

@jrieken I tested this in Insiders (same things as yesterday).. test no longer reports huge numbers and manually spamming the buttons doesn't result in memory climbing anymore:

So the fix certainly appears to resolve everything I was hitting. Thanks for addressing it so quickly! 😃


Main Menu Background in while playing?

When i press play the agario background of the main menu is there and the playing screen only flashes... I cant even play it, and tried reinstalling everything (but actual tampermonkey) and tried reloading. Help please!??!

Seems to be a problem that everyone is having right now...
Redirecting this issue to #543.


Install cactusboards-amc13-python

It is required by gempython in cmsgemos.

Very tricky problem... :-p
There are no installation instructions in the amc13 sources and considering the number of patches, it might be easier to move towards CMake (as I did with wiscrpcsvc-client).
More generally, the Python superbuild raises a number of questions. Currently, my best idea would be to install the Python packages in a virtualenv as editable packages. However, this would require a rewriting of all setup.py... :-/
Also, the uHAL Python package is currently installed in /opt/cactus/lib and that is maybe not the best location...


DB Queries are really slow

What happened:
Navigation is slow, due to most queries having multi-second timing.
Views should produce quick results, provided that adequate indexes are available, or they are materialized views (which could be feasible, since kubeclarity knows exactly when content used to populate views is about to change, i.e., when a scan operation is completed).
What you expected to happen:
Navigating from page to page should be quick.
How to reproduce it (as minimally and precisely as possible):
Populate mentioned tables with hundreds or, better, thousands of tuples. This happens on a cluster I own, which has twenty or more namespaces.
Are there any error messages in KubeClarity logs?
(e.g. kubectl logs -n kubeclarity --selector=app=kubeclarity)

kubeclarity
kubeclarity 2022/08/22 15:33:26 /build/backend/pkg/database/application.go:297 SLOW SQL >= 200ms
kubeclarity [6341.415ms] [rows:1] SELECT count(*) FROM "applications_view"
kubeclarity
kubeclarity 2022/08/22 15:33:33 /build/backend/pkg/database/application.go:309 SLOW SQL >= 200ms
kubeclarity [6802.818ms] [rows:50] SELECT * FROM "applications_view" ORDER BY name desc LIMIT 50 OFFSET 250

Anything else we need to know?:
I'm using version 2.5.0 of kubeclarity chart.
Environment:

Kubernetes version (use kubectl version --short):

Client Version: v1.24.3
Kustomize Version: v4.5.4
Server Version: v1.21.7

KubeClarity version (use kubectl -n kubeclarity exec deploy/kubeclarity -- ./backend version)

Version: v2.5.0
Commit: 383f694a7f01c2a47522f520ff3bd4d68b243271
Build Time: 2022-07-18T07:06:08Z

Cloud provider or hardware configuration:

Azure (AKS)

Others:

@log2 Thanks for reporting the issue, we will take a look at your suggestions.


Fix config view.

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

So should we also change updatePath to updatePaths ?

Yes.

👍


Add new Grafana dashboards: Aggregated Reports, Project Insights, and…

Description
This pull request adds three new Grafana dashboards to the AI DIAL Realtime Analytics project as part of the requirements outlined in [Issue #62](https://github.com/epam/ai-dial-analytics-realtime/issues/62).
The new dashboards are as follows:

DIAL Analytics Aggregated Report: Focuses on aggregated metrics, providing insights derived from pre-aggregated data for performance optimization.
DIAL Project Insights: Offers detailed analytics at the project level, enabling better monitoring and understanding of project-specific metrics.
DIAL User Insights: Provides user-level analytics to track and analyze individual user behavior and contributions.

Dependencies
This PR is dependent on the following pull request in the InfluxData Helm Charts repository:

[PR #692](https://github.com/influxdata/helm-charts/pull/692): Adds the required buckets and tasks to support the new Grafana dashboards.
This pull request must be merged before this one can be fully functional.

Changes in this PR

Added three new dashboard JSON files under the Grafana Dashboards directory:

DIAL Analytics Agg.json
DIAL Project Insights.json
DIAL User Insights.json

Updated the project documentation (README.md) to reflect the addition of these dashboards.

Testing
Please ensure the following:

All pre-requisite dependencies from the InfluxDB setup are correctly deployed and functional.
Grafana is configured to load these new dashboards and displays the expected data as visualized.

Issue Reference
Closes [Issue #62](https://github.com/epam/ai-dial-analytics-realtime/issues/62) once merged.
Notes
These dashboards rely on aggregated data for improved performance. Ensure the required changes in the InfluxDB Helm Chart repository have been deployed and tested before integrating this PR.

Hey there and thank you for opening this pull request! 👋🏼
We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.
Details:
No release type found in pull request title "Add new Grafana dashboards: Aggregated Reports, Project Insights, and…". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - fix
 - hotfix
 - feat
 - feature
 - chore


Add a force option to force recompiling a RawKernel/RawModule

Sometimes, and with the introduction of log_stream, the kernel cache can important warning messages

cc: @mnicely


Update travis to current MolSSI cookiecutter

@maxentile I know most of the development here is off master (and has the new cookiecutter travis update anyway), but here's a PR to get the master build status green if you want. Feel free to take it or leave it, I was just doing this for another repo anyway.
I'd also be happy to check out the failing builds on the propertyestimator branch, though if you know the cause of those I'll keep my nose out of your business :-)

Codecov Report

Merging #6 into master will not change coverage.
The diff coverage is n/a.

Thanks @j-wags ! This looks great, merging.


Failed to restore nuget since NuGetCommand version 2.146.0

Troubleshooting
Since the version 2.146.0 of the NuGetCommand our private agent failed to restore the nuget package from our artefact.
System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Windows\ServiceProfiles\NetworkService\AppData\Local\NuGet\plugins-cache\7dfd0fa0c00db55241517876f045626154b6f02c$CredentialProvider.Microsoft.exe\https_comerco.pkgs.visualstudio.com_packaging_ea8caa50-9cf8-4ed7-b410-5bca3b71ec1c_nuget_v3_index.json.dat-new'.
Environment
Server: Azure Pipelines
Account name: Comerco Services
Team projet: Pueblo
Build definition: Pueblo (MAIN), 2<IP_ADDRESS> to 2<IP_ADDRESS>
Private Agent:
- OS: Windows Server 2016 Standard
- Agent version: 2.144.2
Task logs
2019-01-29T12:56:21.8350754Z ##[section]Starting: NuGet restore $/Pueblo/Main/Comerco.Pueblo.BuildServer.sln
2019-01-29T12:56:21.8467272Z ==============================================================================
2019-01-29T12:56:21.8467340Z Task         : NuGet
2019-01-29T12:56:21.8467400Z Description  : Restore, pack, or push NuGet packages, or run a NuGet command. Supports NuGet.org and authenticated feeds like Package Management and MyGet. Uses NuGet.exe and works with .NET Framework apps. For .NET Core and .NET Standard apps, use the .NET Core task.
2019-01-29T12:56:21.8467438Z Version      : 2.146.0
2019-01-29T12:56:21.8467477Z Author       : Microsoft Corporation
2019-01-29T12:56:21.8467532Z Help         : More Information
2019-01-29T12:56:21.8467566Z ==============================================================================
2019-01-29T12:56:23.5115157Z SYSTEMVSSCONNECTION exists true
2019-01-29T12:56:23.7509954Z SYSTEMVSSCONNECTION exists true
2019-01-29T12:56:24.1704158Z [command]C:\Windows\system32\chcp.com 65001
2019-01-29T12:56:24.1724796Z Active code page: 65001
2019-01-29T12:56:24.2070497Z Detected NuGet version <IP_ADDRESS>77 / 4.9.3+e5150f1e119e456e01c4f1e413213d392eda1c3a
2019-01-29T12:56:24.2084551Z SYSTEMVSSCONNECTION exists true
2019-01-29T12:56:24.3662172Z Saving NuGet.config to a temporary config file.
2019-01-29T12:56:24.3677191Z [command]c:\agent_work_tool\NuGet\4.9.3\x64\nuget.exe sources Add -NonInteractive -Name ea8caa50-9cf8-4ed7-b410-5bca3b71ec1c -Source https://comerco.pkgs.visualstudio.com/_packaging/ea8caa50-9cf8-4ed7-b410-5bca3b71ec1c/nuget/v3/index.json -ConfigFile c:\agent_work\2\Nuget\tempNuGet_6880.config
2019-01-29T12:56:24.9531716Z Package Source with Name: ea8caa50-9cf8-4ed7-b410-5bca3b71ec1c added successfully.
2019-01-29T12:56:24.9574233Z [command]c:\agent_work_tool\NuGet\4.9.3\x64\nuget.exe sources Add -NonInteractive -Name NuGetOrg -Source https://www.nuget.org/api/v2/ -ConfigFile c:\agent_work\2\Nuget\tempNuGet_6880.config
2019-01-29T12:56:25.4824728Z Package Source with Name: NuGetOrg added successfully.
2019-01-29T12:56:25.4855256Z [command]c:\agent_work_tool\NuGet\4.9.3\x64\nuget.exe restore c:\agent_work\2\s\Main\Comerco.Pueblo.BuildServer.sln -NoCache -Verbosity Detailed -NonInteractive -ConfigFile c:\agent_work\2\Nuget\tempNuGet_6880.config
2019-01-29T12:56:32.0226268Z NuGet Version: <IP_ADDRESS>77
2019-01-29T12:56:32.0226524Z MSBuild auto-detection: using msbuild version '<IP_ADDRESS>4' from 'C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\15.0\bin'. Use option -MSBuildVersion to force nuget to use a specific version of MSBuild.
2019-01-29T12:56:32.0226571Z MSBuild P2P timeout [ms]: 372000
2019-01-29T12:56:32.0227228Z C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\15.0\bin\msbuild.exe "C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Temp\NuGetScratch\yqdormga.lko.nugetinputs.targets" /t:GenerateRestoreGraphFile /nologo /nr:false /v:q /p:NuGetRestoreTargets="C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Temp\NuGetScratch\cfbthcvp.3nb.nugetrestore.targets" /p:RestoreUseCustomAfterTargets="True" /p:RestoreTaskAssemblyFile="c:\agent_work_tool\NuGet\4.9.3\x64\nuget.exe" /p:RestoreSolutionDirectory="c:\agent_work\2\s\Main\" /p:RestoreConfigFile="c:\agent_work\2\Nuget\tempNuGet_6880.config" /p:SolutionDir="c:\agent_work\2\s\Main\" /p:SolutionName="Comerco.Pueblo.BuildServer"
2019-01-29T12:56:32.0227450Z
2019-01-29T12:56:32.0227509Z Running restore with 8 concurrent jobs.
…. LOG TRUNCATE TOO LONG
2019-01-29T12:56:32.0547896Z Retrying 'FindPackagesByIdAsyncCore' for source 'https://www.nuget.org/api/v2/FindPackagesById()?id='System.Windows.Interactivity.WPF'&semVerLevel=2.0.0'.
2019-01-29T12:56:32.0547939Z Could not find file 'C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Temp\NuGet\TempCache\33b25c18-377b-4ca7-99a1-6754c02572a7\ylcwmjb0.gmn'.
2019-01-29T12:56:32.0548032Z   GET https://www.nuget.org/api/v2/FindPackagesById()?id='System.Windows.Interactivity.WPF'&semVerLevel=2.0.0
2019-01-29T12:56:32.0548084Z System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Windows\ServiceProfiles\NetworkService\AppData\Local\NuGet\plugins-cache\7dfd0fa0c00db55241517876f045626154b6f02c$CredentialProvider.Microsoft.exe\https_comerco.pkgs.visualstudio.com_packaging_ea8caa50-9cf8-4ed7-b410-5bca3b71ec1c_nuget_v3_index.json.dat-new'.
2019-01-29T12:56:32.0548131Z    at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
2019-01-29T12:56:32.0548220Z    at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
2019-01-29T12:56:32.0548267Z    at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize)
2019-01-29T12:56:32.0548438Z    at NuGet.Protocol.Plugins.PluginCacheEntry.d__20.MoveNext()
2019-01-29T12:56:32.0548476Z --- End of stack trace from previous location where exception was thrown ---
2019-01-29T12:56:32.0548515Z    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2019-01-29T12:56:32.0548587Z    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2019-01-29T12:56:32.0548626Z    at NuGet.Protocol.Core.Types.PluginManager.<>c__DisplayClass24_0.<b__0>d.MoveNext()
2019-01-29T12:56:32.0548664Z --- End of stack trace from previous location where exception was thrown ---
2019-01-29T12:56:32.0548702Z    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2019-01-29T12:56:32.0548775Z    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2019-01-29T12:56:32.0548818Z    at NuGet.Common.ConcurrencyUtilities.d__21.MoveNext() 2019-01-29T12:56:32.0548928Z --- End of stack trace from previous location where exception was thrown --- 2019-01-29T12:56:32.0548967Z    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() 2019-01-29T12:56:32.0549044Z    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) 2019-01-29T12:56:32.0549082Z    at NuGet.Protocol.Core.Types.PluginManager.<TryCreatePluginAsync>d__24.MoveNext() 2019-01-29T12:56:32.0549120Z --- End of stack trace from previous location where exception was thrown --- 2019-01-29T12:56:32.0549197Z    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() 2019-01-29T12:56:32.0549240Z    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) 2019-01-29T12:56:32.0549278Z    at NuGet.Protocol.Core.Types.PluginManager.<CreatePluginsAsync>d__22.MoveNext() 2019-01-29T12:56:32.0549321Z --- End of stack trace from previous location where exception was thrown --- 2019-01-29T12:56:32.0549415Z    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() 2019-01-29T12:56:32.0549453Z    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) 2019-01-29T12:56:32.0549492Z    at NuGet.Protocol.Core.Types.PluginResourceProvider.<TryCreate>d__3.MoveNext() 2019-01-29T12:56:32.0549560Z --- End of stack trace from previous location where exception was thrown --- 2019-01-29T12:56:32.0549718Z    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() 2019-01-29T12:56:32.0549756Z    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) 2019-01-29T12:56:32.0549795Z    at NuGet.Protocol.Core.Types.SourceRepository.<GetResourceAsync>d__161.MoveNext()
2019-01-29T12:56:32.0549876Z --- End of stack trace from previous location where exception was thrown ---
2019-01-29T12:56:32.0549923Z    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2019-01-29T12:56:32.0549965Z    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2019-01-29T12:56:32.0550004Z    at NuGet.Protocol.PluginFindPackageByIdResourceProvider.d__1.MoveNext()
2019-01-29T12:56:32.0550080Z --- End of stack trace from previous location where exception was thrown ---
2019-01-29T12:56:32.0550115Z    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2019-01-29T12:56:32.0550157Z    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2019-01-29T12:56:32.0550230Z    at NuGet.Protocol.Core.Types.SourceRepository.d__161.MoveNext() 2019-01-29T12:56:32.0550268Z --- End of stack trace from previous location where exception was thrown --- 2019-01-29T12:56:32.0550302Z    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() 2019-01-29T12:56:32.0550341Z    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) 2019-01-29T12:56:32.0550520Z    at NuGet.Protocol.Core.Types.SourceRepository.<GetResourceAsync>d__151.MoveNext()
2019-01-29T12:56:32.0550558Z --- End of stack trace from previous location where exception was thrown ---
2019-01-29T12:56:32.0550592Z    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2019-01-29T12:56:32.0550631Z    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2019-01-29T12:56:32.0550708Z    at NuGet.Commands.SourceRepositoryDependencyProvider.d__26.MoveNext()
2019-01-29T12:56:32.0550746Z --- End of stack trace from previous location where exception was thrown ---
2019-01-29T12:56:32.0550780Z    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2019-01-29T12:56:32.0550853Z    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2019-01-29T12:56:32.0550891Z    at NuGet.Commands.SourceRepositoryDependencyProvider.d__20.MoveNext()
2019-01-29T12:56:32.0551006Z --- End of stack trace from previous location where exception was thrown ---
2019-01-29T12:56:32.0551045Z    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2019-01-29T12:56:32.0551164Z    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2019-01-29T12:56:32.0551203Z    at NuGet.Commands.SourceRepositoryDependencyProvider.<>c__DisplayClass19_0.<b__0>d.MoveNext()
2019-01-29T12:56:32.0551241Z --- End of stack trace from previous location where exception was thrown ---
2019-01-29T12:56:32.0551314Z    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2019-01-29T12:56:32.0551352Z    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2019-01-29T12:56:32.0551390Z    at NuGet.Commands.SourceRepositoryDependencyProvider.d__19.MoveNext()
2019-01-29T12:56:32.0551433Z --- End of stack trace from previous location where exception was thrown ---
2019-01-29T12:56:32.0551523Z    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2019-01-29T12:56:32.0551561Z    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2019-01-29T12:56:32.0551599Z    at NuGet.DependencyResolver.ResolverUtility.<>c__DisplayClass7_1.<b__0>d.MoveNext()
2019-01-29T12:56:32.0551685Z --- End of stack trace from previous location where exception was thrown ---
2019-01-29T12:56:32.0551723Z    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2019-01-29T12:56:32.0551762Z    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2019-01-29T12:56:32.0551800Z    at NuGet.DependencyResolver.ResolverUtility.d__7.MoveNext()
2019-01-29T12:56:32.0551872Z --- End of stack trace from previous location where exception was thrown ---
2019-01-29T12:56:32.0551919Z    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2019-01-29T12:56:32.0551958Z    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2019-01-29T12:56:32.0551996Z    at NuGet.DependencyResolver.ResolverUtility.d__6.MoveNext()
2019-01-29T12:56:32.0552073Z --- End of stack trace from previous location where exception was thrown ---
2019-01-29T12:56:32.0552111Z    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2019-01-29T12:56:32.0552150Z    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2019-01-29T12:56:32.0552227Z    at NuGet.DependencyResolver.ResolverUtility.d__4.MoveNext()
2019-01-29T12:56:32.0552265Z --- End of stack trace from previous location where exception was thrown ---
2019-01-29T12:56:32.0552303Z    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2019-01-29T12:56:32.0552431Z    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2019-01-29T12:56:32.0552512Z    at NuGet.DependencyResolver.ResolverUtility.d__1.MoveNext()
2019-01-29T12:56:32.0552547Z --- End of stack trace from previous location where exception was thrown ---
2019-01-29T12:56:32.0552585Z    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2019-01-29T12:56:32.0552666Z    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2019-01-29T12:56:32.0552704Z    at NuGet.DependencyResolver.RemoteDependencyWalker.d__3.MoveNext()
2019-01-29T12:56:32.0552743Z --- End of stack trace from previous location where exception was thrown ---
2019-01-29T12:56:32.0552777Z    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2019-01-29T12:56:32.0552850Z    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2019-01-29T12:56:32.0552965Z    at NuGet.DependencyResolver.RemoteDependencyWalker.d__3.MoveNext()
2019-01-29T12:56:32.0553003Z --- End of stack trace from previous location where exception was thrown ---
2019-01-29T12:56:32.0553042Z    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2019-01-29T12:56:32.0553127Z    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2019-01-29T12:56:32.0553165Z    at NuGet.DependencyResolver.RemoteDependencyWalker.d__3.MoveNext()
2019-01-29T12:56:32.0553199Z --- End of stack trace from previous location where exception was thrown ---
2019-01-29T12:56:32.0553272Z    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2019-01-29T12:56:32.0553310Z    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2019-01-29T12:56:32.0553349Z    at NuGet.DependencyResolver.RemoteDependencyWalker.d__3.MoveNext()
2019-01-29T12:56:32.0553400Z --- End of stack trace from previous location where exception was thrown ---
2019-01-29T12:56:32.0553477Z    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2019-01-29T12:56:32.0553515Z    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2019-01-29T12:56:32.0553554Z    at NuGet.Commands.ProjectRestoreCommand.d__10.MoveNext()
2019-01-29T12:56:32.0553630Z --- End of stack trace from previous location where exception was thrown ---
2019-01-29T12:56:32.0553669Z    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2019-01-29T12:56:32.0553707Z    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2019-01-29T12:56:32.0553746Z    at NuGet.Commands.ProjectRestoreCommand.d__8.MoveNext()
2019-01-29T12:56:32.0553818Z --- End of stack trace from previous location where exception was thrown ---
2019-01-29T12:56:32.0553865Z    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2019-01-29T12:56:32.0553908Z    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2019-01-29T12:56:32.0553946Z    at NuGet.Commands.RestoreCommand.d__47.MoveNext()
2019-01-29T12:56:32.0554023Z --- End of stack trace from previous location where exception was thrown ---
2019-01-29T12:56:32.0554057Z    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2019-01-29T12:56:32.0554095Z    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2019-01-29T12:56:32.0554181Z    at NuGet.Commands.RestoreCommand.d__32.MoveNext()
2019-01-29T12:56:32.0554223Z --- End of stack trace from previous location where exception was thrown ---
2019-01-29T12:56:32.0554258Z    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2019-01-29T12:56:32.0554296Z    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2019-01-29T12:56:32.0554505Z    at NuGet.Commands.RestoreRunner.d__7.MoveNext()
2019-01-29T12:56:32.0554543Z --- End of stack trace from previous location where exception was thrown ---
2019-01-29T12:56:32.0554582Z    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2019-01-29T12:56:32.0554620Z    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2019-01-29T12:56:32.0554693Z    at NuGet.Commands.RestoreRunner.d__6.MoveNext()
2019-01-29T12:56:32.0983042Z ##[error]The nuget command failed with exit code(1) and error(Could not find a part of the path 'C:\Windows\ServiceProfiles\NetworkService\AppData\Local\NuGet\plugins-cache\7dfd0fa0c00db55241517876f045626154b6f02c$CredentialProvider.Microsoft.exe\https_comerco.pkgs.visualstudio.com_packaging_ea8caa50-9cf8-4ed7-b410-5bca3b71ec1c_nuget_v3_index.json.dat-new'.)
2019-01-29T12:56:32.0991341Z ##[error]Packages failed to restore
2019-01-29T12:56:32.1010797Z ##[section]Finishing: NuGet restore $/Pueblo/Main/Comerco.Pueblo.BuildServer.sln

same issue here. the problem looks like the generated filename (for the cache file) is too long and not valid for NTFS.

      Hello, thank you for your feedback. In order to better diagnose the problem, could you provide screen shots of the build definition and a copy of the complete log with system.debug set to true?

The log was added to the post.

Same issue using 2.146.1

@OneCyrus I agree that MAX_PATH type issues would seem to be a likely culprit, especially since the plugin cache dat-new file path is exactly 260 in both examples above.
That said, I've thoroughly tried to reproduce this with plugin cache sizes of various lengths and I haven't been able to on my machine.
Could you please try setting the environment variable NUGET_PLUGINS_CACHE_PATH to a shorter path, and see if that resolves the issue? If so, I can report this issue on https://github.com/NuGet/Home and hopefully they can spot the difference.

Filed an issue with NuGet. Once @maboulianne confirms that setting NUGET_PLUGINS_CACHE_PATH to a shorter path is a viable workaround, I'd like to close this issue and continue discussion in the NuGet issue, since this is an issue in NuGet itself.

@zarenner Yes when I set the variable NUGET_PLUGINS_CACHE_PATH to C:\NugetCache it's working.
It's a viable workaround for me.

Great, thanks for confirming.
We're also investigating rolling out a hotfix to automatically set NUGET_PLUGINS_CACHE_PATH to a shorter path when appropriate.
Since this is a NuGet issue, and there's a viable workaround, let's continue discussion of this issue on the NuGet issue https://github.com/NuGet/Home/issues/7770. I'm going to close this issue.


[all OSs] Selenium server version will be upgraded from 3 to 4 on November, 15

Breaking changes
Selenium server version will be upgraded from 3 to 4 on all available images.
Target date
November 15, 2021
The motivation for the changes
We'd like to keep images up-to-date with recent software updates.
Possible impact
There are a few breaking changes in selenium server 4 thus your builds can be broken after the update. More information about breaking changes can be found on the official changelog https://github.com/SeleniumHQ/selenium/releases/tag/selenium-4.0.0
Virtual environments affected

[X] Ubuntu 18.04
[X] Ubuntu 20.04
[X] macOS 10.15
[X] macOS 11
[X] Windows Server 2016
[X] Windows Server 2019
[X] Windows Server 2022

Mitigation ways
Revert to selenium 3 using the following snippets:
macOS
cd $(brew --repo homebrew/core)
git checkout dc37198
brew install selenium-server-standalone

Windows
$seleniumDirectory = "C:\selenium\"
Remove-Item -Path $seleniumDirectory\* -Recurse -Force
$seleniumFileName = "selenium-server-standalone.jar"
$seleniumDownloadUrl = "https://github.com/SeleniumHQ/selenium/releases/download/selenium-3.141.59/selenium-server-standalone-3.141.59.jar"
Start-DownloadWithRetry -Url $seleniumDownloadUrl -Name $seleniumFileName -DownloadPath $seleniumDirectory

Ubuntu
SELENIUM_JAR_NAME="selenium-server-standalone.jar"
SELENIUM_DOWNLOAD_URL="https://github.com/SeleniumHQ/selenium/releases/download/selenium-3.141.59/selenium-server-standalone-3.141.59.jar"
SELENIUM_JAR_PATH="/usr/share/java"
rm $SELENIUM_JAR_PATH/selenium-server*
curl $SELENIUM_DOWNLOAD_URL -sL -o "$SELENIUM_JAR_PATH/$SELENIUM_JAR_NAME"

All PR's (macOS. Windows and Ubuntu) were merged.

Selenium was updated up to 4.* version across all the images. Closing this issue.

main

SELENIUM_JAR_NAME= " Selenium-server-standalone.jar "
SELENIUM_DOWNLOAD_URL= " https://github.com/SeleniumHQ/selenium/releases/download/selenium-3.141.59/selenium-server-standalone-3.141.59.jar "
SELENIUM_JAR_PATH " /usr/share/java "
rm $SELENIUM_JAR_PATH /selenium-server *
curl $SELENIUM_DOWNLOAD_URL -sL -o " $SELENIUM_JAR_PATH / $SELENIUM_JAR_NAME "

$SeleniumDirectory  =  " C:\Selenium\ "
Remove-Item  - Path $SeleniumDirectory \ *  - Recurse - Force
$seleniumFileName  =  " Selenium-server-standalone.jar "
$seleniumDownloadUrl  =  " https://github.com/SeleniumHQ/selenium /releases/download/Selenium-3.141.59/selenium-server-standalone-3.141.59.jar "
Start-DownloadWithRetry  - URL $seleniumDownloadUrl  - Ad $seleniumDosyaAdı  - İndirme Yolu $seleniumDirectory

#4050 comment

[tüm işletim sistemleri] Selenium sunucu sürümü 3'ten 4'e yükseltilecek, 15 Kasım #4376


Update database.factory.main() function to test all its contents

This is a showcase of how we could refactor our main() methods if we want to follow a path where logic can be left in main() but testing everything, argument parsing included (without having to go to the extent of using subprocess).

As a side effect, our code coverage would currently drop from 76% to 72% due to all the main() methods without unit test.


refactor: extract content chip (list) component(s)

So they can be used to list technologies in projects too

#323  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @davidlj95 and the rest of your teammates on  Graphite


Added Redis for persistence with installation/usage info and example code/tests

I set up Redis to provide a persistence service for the application. More information can be found on description.md.
I also added some example code that tracks the last time you visited the page using Redis along with some basic tests that check if it's working correctly. Redis storage uses the request's IP address as a key and the last visit's time as a value.

If you are not willing to do the requested task to get the :gift: answer here asap to merge your code.

I added two new unit tests: one checks the 'second visit' scenario and the other checks a scenario where two different users send a request. Thanks for the helper tip, it was pretty useful.

Resolve the conflict of README.md and I will merge your code (with the :gift:)

Done

Ops, not yet, I merged without realise that you have additional content. My bad. Can you solve it again. I promise not to merge until you fix this.

Alright, no problem. Conflicts are solved again.


Are the sliders for Dosage, TDS and Actual Yield confusing?

So far people don't seem to realize they are sliders like the Timer app on iOS.
I think this has to do with the fact that the timer app shows multiple fields at once, but I don't like how that looks on the app.
If people continue to be confused, perhaps we need an introduction video showing how to use the app, or a gif.

Something that could help is allowing users to tap the number and enter the value with a keyboard.

Lots of people have issues with this, but I still don't know what the right approach is here

The data input looks pretty inconsistent to me. The grind size is a drop down menu. The dosage is a scroll wheel. I think a normal text input would be more intuitive. especially for the grind size. e.g. I use a DF64 and want to save more than size 10 or 10.5. I Want to save 10.2 :-)
The same for the TDS field. I want to just type in the data from my refractometer and dont want to scroll on two wheels.

My feedback to these people so far
I kept trying different input styles for each type of option and some worked better than others.
Originally for dose it was a single slider but wasn't accurate enough. Then I made two sliders for dose and sub dose and it felt too slow and the dose was still not accurate enough on smaller screen sizes so I then tried the new slide thing I have now.
I get that it may not be consistent, but I find some to be more accurate than others for certain fields.

https://github.com/erikng/Agile-Brewing-Issues/issues/13#issuecomment-1212063387

Selection sliders/menus: there are different types of selecting different numbers: gring size is one, dosage is another type, temperature is a slider. Is there a reason for this diversity? Personally, I don't quirw like the grind selection, dosage, preinfusion, extraction time, and I would rather have them the same style as dosage.

My response: https://github.com/erikng/Agile-Brewing-Issues/issues/13#issuecomment-1213628709

I'm going to close this because in the next version v1.0.6 the following changes are being made

Dosage, Actual Yield are now pull out menus
TDS is now a decimal keyboard input


Unexpected error fetching SolArk data: unpack requires a buffer of 4 bytes

I'm getting this error and no values get reported (ever). Based on the error, are you expecting 32bit values while 16bit appears to work fine?
2021-09-22 23:31:15 ERROR (MainThread) [custom_components.solark_modbus.hub] Unexpected error fetching SolArk data: unpack requires a buffer of 4 bytes
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 187, in _async_refresh
    self.data = await self._async_update_data()
  File "/config/custom_components/solark_modbus/hub.py", line 87, in _async_update_data
    realtime_data = await self.hass.async_add_executor_job(
  File "/usr/local/lib/python3.9/concurrent/futures/thread.py", line 52, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/solark_modbus/hub.py", line 128, in read_modbus_realtime_data
    data["totalinv_e"] = decoder.decode_32bit_uint()/10.0
  File "/usr/local/lib/python3.9/site-packages/pymodbus/payload.py", line 411, in decode_32bit_uint
    handle = self._unpack_words(fstring, handle)
  File "/usr/local/lib/python3.9/site-packages/pymodbus/payload.py", line 361, in _unpack_words
    handle = unpack(up, handle)
struct.error: unpack requires a buffer of 4 bytes

My HA runs via docker.  I can go into CLI of the HA container and read values over TCP without any issues

Upon some more testing, I see that when I add the integration, it fails on the first data pull, succeeds on the second, fails on the third and everyone thereafter.
So if the time is left to default 60s, and you add the integration at t=0s, then at 60s it comes up with an initial set of values, and then as 120s all of those values become unavailable and never come back as values.
Here is a screen cap of this: https://imgur.com/a/tjU4599

Can you run Wireshark and see if the Modbus requests are failing sporadically?   I have been using 15 second updates on my machine without any issue but if the request are not successfully completed I think you will see the results you have.  In Wireshark we should see the requests going out and the responses coming back.  You could also just let your Modpoll test runs and see if its reliable or not.

Can you run Wireshark and see if the Modbus requests are failing sporadically? I have been using 15 second updates on my machine without any issue but if the request are not successfully completed I think you will see the results you have. In Wireshark we should see the requests going out and the responses coming back. You could also just let your Modpoll test run for awhile and see if its reliable or not.

Thanks for the suggestion.  I was successfully getting single responses but after your suggestion, I tried it on a 10-sec interval and they failed after the first one.  I did some more digging and set ModbusTCP Poll to a 5000 ms timeout.  This solved it and then I check it's working fine.


Apply binding to all allocations from jemalloc - [merged]

In GitLab by @perarnau on Aug 6, 2018, 14:00
Merges mbind-all-allocations -> master
Fixes a complex issue where jemalloc would issue weird mmap requests, resulting in difficult to trace mbind calls or even missing ones (?). Binding on each alloc avoids these problems but create the need for one arena per area to avoid binding overlaps.

In GitLab by @perarnau on Aug 6, 2018, 14:08
merged
By Swann Perarnau on 2018-08-06T19:08:38 (imported from GitLab project)

In GitLab by @perarnau on Aug 6, 2018, 14:01
added 5 commits
79144fa3...b808beb2 - 3 commits from branch master759ec35a - [fix] Force mbind on allocation from arena67114902 - [refactor] use one arena per area.
Compare with previous version
By Swann Perarnau on 2018-08-06T19:01:07 (imported from GitLab project)


impl DerefMut trait for GeoemetryRef

[x] I agree to follow the project's code of conduct.
[x] I added an entry to CHANGES.md if knowledge of this change could be valuable to users.

This impl impl DerefMut trait for GeoemetryRef. This geometry of Geometery::get_geometry(i32) function can modify point coordinate.

bors r+


Improve doc links

Add dropdown link list to doc le buttons (with news, release notes, migi notes)

Add release notes link to the download overview page

Maybe the evaluation of the additional doc links should come somewhere from the php backend.


404 at: /swarm/docker-compose.yml/

URL: /swarm/docker-compose.yml/
Missing page...

Where is there a link to that URL? Where in the docs would you normally expect it to land? We can add a redirect with a little more info.

@deniswal ^

I was browsing the swarm documentation (From the top of my head, a tutorial about swarm).
I found this missing page and clicked on the report link.
Sorry for the lack of context, I thought the link would bundle it when reporting.
I now have some difficulties to backtrace the path I took three days ago.
Denis


separate node to difference graphs

Hello,
this is a good idea, but I think the implementation was too limiting for me. I think it's important to be able to exclude nodes if the graph settings are not compatible, even between the same graph types.
That's why I decided to do this change: aad78c4c7ce9ef97299d7796321e836aaf269b55
Which ads the possibility to exclude nodes either based on graph type using the node menu item attribute or with a custom static function that takes the graph in parameter with [IsCompatibleWithGraph].
I hope that you'll be happy with these changes, and thanks again for creating a PR on my repository :)


[E2e][Excel Source] Add e2e to test excel source read duplicate data

Search before asking

[X] I had searched in the feature and found no similar feature requirement.

Description
test for https://github.com/apache/seatunnel/pull/5932
Usage Scenario
No response
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

这个解决了吗，从excel抽数据到pg/mysql/ck，都会出现重复数据。


confusion about visualizing individual channels

As a freshman in this area, I really appreciate your repo for letting me know how feature visualization works in practice. Thanks!!
In the channel visualization case, the channel index in the example is 119, however, the colab tutorial states the 7th channel in Mixed_6b.branch1x1 is optimized. In my understanding, I think the index of the optimized channel should equal the value of channel_number (119th channel in this case). Or is there something I misunderstood?

hi @rmin2000
You are correct. The colab tutorial text has a typo. I am indeed optimizing channel index 119 (another typo there -> it should be channel_index and not channel_number). I will fix this typo soon.
Also thank you for your kind words!

Thank you!


Add shard_size support to TermStats facet

LGTM :+1: mind signing our CLA so that we may pull your bits in:
https://www.elastic.co/contributor-agreement/

I signed the CLA right before sending the pull request.

Found you on our list! thanks for sending a PR :+1:


Feature/captcha

Replace simple_captcha

Coverage decreased (-30.02%) to 54.84% when pulling cd433bfe7f1bd8820a1ed2d7888f4f51f2213520 on feature/captcha into 1fbd8fb8fd98001b97e010eba4137f6cd4c861c9 on master.


Simd helpers

simd helpers based on intel implementation

Peformance graph for unseq_first_n against sequential implementation

Peformance graph for unseq2_first_n against sequential implementation

Functionality tests have been added.

@Johan511 could you please resolve the conflicts? That would allow me to review the changes and go ahead with merging this, if appropriate.

Conflicts seem to be resolved, can you please check @hkaiser ?

bors merge


"DTR needs that a majority" -> "DTR requires that a majority"

Proposed changes
Changed the phrase "needs that a majority" to "requires that a majority" in the docker dtr documentation because the existing wording is unclear.

Better! Thanks, @benjamin-issa :)

:)


ctr_drbg_init ios10  occasionally retrun !=0

we are used old vesion Open source library about 2015 year,Recently, we Xcode9 buid this library usēd in ios10  occasionally ctr_drbg_init  retrun !=0。
entropy_context entropy;
ctr_drbg_context ctr_drbg;
const char *pers = "rsa_encrypt";
entropy_init(&entropy);
ret = ctr_drbg_init( &ctr_drbg, entropy_func, &entropy,
								   (const unsigned char *) pers,
								   strlen(pers));

    ret!=0

@liyunshuang please specify what is the error code you are receiving, and what is the Mbed TLS version you are using.
note that mbedtls_ctr_drbg_init() does not return any error code. ctr_drbg_init(), from versions prior to 1.3, do return an error, but these are not supported any more.
It is strongly recomended you update your library to the latest LTS version, and see if the issue reproduces. Note that there have been many updates and security fixes since the unsupported library version you are using.
please look at this article to learn how to migrate your code to version 2.x note you will probably need to do additional modifications to fit to later versions.

Thank you for your reply.This problem cannot be easily repeated. We need to send a version of app to collect error information. Then I hope to get your help，Thanks for your help。

@liyunshuang As I believe you are working on an old Mbed TLS which is not supported anymore, you should update your Mbed TLS version before you reproduce the issue.

@liyunshuang please specify what is the error code you are receiving, and what is the Mbed TLS version you are using.
note that mbedtls_ctr_drbg_init() does not return any error code. ctr_drbg_init(), from versions prior to 1.3, do return an error, but these are not supported any more.
It is strongly recomended you update your library to the latest LTS version, and see if the issue reproduces. Note that there have been many updates and security fixes since the unsupported library version you are using.
please look at this article to learn how to migrate your code to version 2.x note you will probably need to do additional modifications to fit to later versions.

Thank you for your attention，We have collected the error code and the error path。
Event background：
Between 1 p.m. and 9 p.m., this error happens randomly on iOS10, most often when a new user first installs.
We should be using older libraries prior to version 1.3, without MBEDTLS_THREADING_C POLARSSL_THREADING_C.
We have collected the error code and the error path ：
The path where our interface call went wrong was  ctr_drbg_init -> ctr_drbg_init_entropy_len -> ctr_drbg_reseed->entropy_func->entropy_gather->platform_entropy_poll->file = fopen( "/dev/urandom", "rb" ),   We found file == NULL，So the interface reports an error。
I have some ideas about this problem, and I hope to correct them：

Is it possible that our multi-thread call to this interface causes the /dev/urandom file to be abnormal
Is this /dev/urandom file of iOS10 system short of time and some environments have this problem

Is it possible that our multi-thread call to this interface causes the /dev/urandom file to be abnormal

If you are working in a multithreaded environment, you should enable MBEDTLS_THREADING_C .

Is this /dev/urandom file of iOS10 system short of time and some environments have this problem

This is a platform specific question, and not part of hte Mbed TLS library.
Please upgrade your library to recent version, as stated before, as you are working on a version that is not supported anymore

closing this question.
If issue persists after update, please reopen with relevant information


[Feature]: Instrument Management Page

Description
For admins, the instrument management page is currently blank. It is not shown to other users.
The implementation should allow admins to archive, though not completely delete instruments.
Group managers should be allowed to manage the instruments shown to members of their group. They should also be permitted to create aggregate instruments for their workflow.
Estimated Difficulty
High
Priority
Low

duplicate of #782


Tabs can get stuck in "pane purgatory"

Open a new file
Pin cross references OR pop out the mini graph
Close all panes except for pinned cross references or mini graph

The UI is now in "pane purgatory". The tab remains open, but it is now impossible to open any new panes, and all of the sidebar panels refuse to display content because "X requires an open file".

Turns out if you double click one of the pinned cross references you can get a crash as well.

This still repros on latest 3.4 stable, including the crash (which is because the view is NULL).

Looks like this issue is improved in 4.0 but still not entirely fixed. We should just disable the 'X' button when the other pane is cross references.


[FLINK-19431][docs]Translate "Monitoring REST API" page of "Debugging & Monitoring" into Chinese

What is the purpose of the change
Translate "Monitoring REST API" page of "Debugging & Monitoring" into Chinese
Brief change log
Translate "Monitoring REST API" page of "Debugging & Monitoring" into Chinese
Verifying this change
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (100MB)
Extended integration test for recovery after master (JobManager) failure
Added test that validates that TaskInfo is transferred only once across recoveries
Manually verified the change by running a 4 node cluser with 2 JobManagers and 4 TaskManagers, a stateful streaming program, and killing one JobManager and two TaskManagers during the execution, verifying that recovery happens correctly.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers:no
The runtime per-record code paths (performance sensitive):no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no

@klion26 could plz have a review?

@weizheng92 thanks for the contribution, will review it today.

@weizheng92 could you please clear the commit history? we should not contain any merge commits in the history(maybe you could use git rebase instead), and please let me know after this has been resolved. thanks


[Bug] When the calendar pie switching month, if the month at the beginning is 30 days, it is displayed normally.  When switching to 31 days, it will be switched back to 30 days. Switching to February will run 3 cake maps, but the month when switching back to 31 days is normal

Version
5.4.1
Link to Minimal Reproduction
https://codesandbox.io/s/spring-wood-nn2xlf?file=/index.html
Steps to Reproduce
create chart:

The series data will be merged by default, so you can disable this strategy via myChart.setOption(option, true);. See also https://echarts.apache.org/api.html#echartsInstance.setOption

thanks for your help!The problem has been solved. 谢了昂, 牛逼老铁, 6666

The series data will be merged by default, so you can disable this strategy via myChart.setOption(option, true);. See also https://echarts.apache.org/api.html#echartsInstance.setOption

thanks for your help!The problem has been solved. 谢了昂, 解决了, 牛逼老铁, 6666


Cannot add comfoair-card

It would be nice if the installation instructions were a little more in detail, including some clear examples. I'm afraid I forget something or do something wrong.
What I did:

create a folder 'lovelace-comfoair' in /config/www
put all 8 files (https://github.com/wichers/lovelace-comfoair) in there
create a file lovelace-ui.yaml in /config (there was no file with this name)
copied your 'resources' text in it
in my dashboard added a card with 2 lines and no indents stating "type: custom:comfoair-card" and  "entity: climate.WHR930" (without the quotes).
restarted HA

Now the dashboard says: Custom element doesn't exist: comfoair-card.
What do I do wrong?
/config/lovelace-ui.yaml:

resources:
- type: module
url: /config/www/lovelace-comfoair/comfoair-card.js

(2nd line has 4 leading spaces)

Changing /config/www/lovelace-comfoair/comfoair-card.js to /homeassistant/www/lovelace-comfoair/comfoair-card.js doesn’t help (both lead to the same directory).

RESULT:

HI
I have the same problem.
Did you manage to get it working?
Thanks.

Unfortunately not. I have no idea where to look. I thought I’ve done everything conform instructions.
Maybe something is missing in the instructions?

Me neither. I will keep trying and let you know if I manage to solve the problem.

same problem here.. Tried a lot of things but no luck so far :(

@wichers
Do you have any tips for us please?

I moved to distribution [yoziru] [esphome-zehnder-comfoair] dist. That one works like a charm.

I moved to distribution [yoziru] [esphome-zehnder-comfoair] dist. That one works like a charm.

Can you please explain what you mean here?
Did you install another version and if so, where does it come from?
Or did you move it to another directory and if so, what directory exactly?
Thnx4hlp 👍

I moved to distribution [yoziru] [esphome-zehnder-comfoair] dist. That one works like a charm.

Thanks I will check it out. 👍

If the card is not visible, there are probably javascript errors. For debugging you open the "inspect" developer window in your browser and check what javascript throws an error. There is probably a mismatch between the card variables and the variables visible in HA.

I've checked my own HA config. I might have forgotten to update the readme.
After adding the .js file to your config folder as in the readme, add the resource:

Settings -> Dashboards -> Resources -> Add Resource
/local/lovelace-comfoair/comfoair-card.js

Add the card by adding a custom card to your dashboard:
type: custom:comfoair-card
entity: climate.esphome_xx_xx_xx_xx_xx_xx_climate (your entity)


Cannot generate coverage report with output from Coverlet 2.5.1

Using the current most recent version of coverlet (via coverlet.msbuild NuGet package version 2.5.1) and coverage-viewer (version 0.3.0), an error is thrown when generating the coverage report:
/Users/lyleshearer/.npm/_npx/78321/lib/node_modules/coverage-viewer/lib/statistics.js:22
    line => line.stats.find(stat => stat.name === 'Hits').value !== 0
                                                         ^

TypeError: Cannot read property 'value' of undefined

This can be repro'd by cloning and running this script on a fork of the coverlet repo.
This appears to be because the coverlet output format for coverage.json changed, perhaps when support for branch coverage was added. The format of the test asset is quite different than the one generated during that repro test.

Interesting, thanks for the write up and repro script. Glancing at the new format, you're right it does look very different. I'll take a closer look at supporting the new format in the next couple days.

Well, I took a look a couple days ago and it actually doesn't look too bad. The main issue is with the new lines format. I'll try to clean this up and cut a new release this week.

@lshearer Sorry for the delay. I just published a new version 0.4.0 that should resolve this issue. Let me know if you still have any issues. Thanks again for the bug report.


Fix IOU EnablePayment route

Details
Moved the IOU_Enable_Payments under IOU_Send
Fixed Issues
$ https://github.com/Expensify/App/issues/6473
Tests

Launch the Desktop app and login.
Tap on [+] and select Send money > enter amount > next.
Enter the email of a user you will send money to in the field 'Name, email or phone".
Tap on Continue for "Verify identity" page.
Verify that the EnablePayments page opens. On web verify that the url is /iou/enable-payments.
Verify that you can navigate back.

QA Steps
Steps above.
Tested On

[X] Web
[X] Mobile Web
[X] Desktop
[X] iOS
[X] Android

Screenshots

Web
https://user-images.githubusercontent.com/22219519/143300115-6db89f7a-b935-49da-89d9-23272bd8d79f.mov
Mobile Web
https://user-images.githubusercontent.com/22219519/143300129-91908bac-0508-4266-8ea2-b922ddac5b17.mov
Desktop
https://user-images.githubusercontent.com/22219519/143300138-d91891fb-0c21-4cc1-8198-0e40f52a454a.mov
iOS
https://user-images.githubusercontent.com/22219519/143300145-fbd7797d-ed79-4087-8d6f-63724d0b70da.mov
Android
https://user-images.githubusercontent.com/22219519/143300307-a674324c-62ef-405e-92fa-14b3cbfe41f8.mov

Bumping for review!

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by @danieldoglas in version: 1.1.17-8 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by @roryabraham in version: 1.1.18-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Improve pkgs/by-name code, minor fix

Description of changes
Mainly code cleanup, but that also discovered a problem, which is fixed with the cleanup.

https://github.com/NixOS/nixpkgs/pull/275539 had false negative bug that would've made https://github.com/NixOS/nixpkgs/pull/284591 succeed CI, even though sbcl isn't using pkgs.callPackage ... directly.
CI however failed due to a different false positive bug, which was fixed with https://github.com/NixOS/nixpkgs/pull/285089, though that wasn't implemented fully, only triggering for new packages, but at that point sbcl was already merged as is, since I discounted the CI failure as a false positive
Only now that I cleaned up the code I'm realising the above. This PR fixes it.

See the commit messages for more details.
I'll merge this myself soon after CI is successful.
This work is sponsored by Antithesis :sparkles:
Things done

[x] Ran nix-build -A tests.nixpkgs-check-by-name.tests successfully on x86_64-linux

Add a :+1: reaction to pull requests you find important.

We can't avoid pkgs/by-name CI failing here because it's a bit too clever: It detects that I'm moving sbcl out of pkgs/by-name again, but this is a rare case where it's totally justified :)

I'm not exactly clear on the details but I believe it :) thanks

@hraban The intuitive explanation is that for any pkgs/by-name/fo/foo, the corresponding attribute pkgs.foo should ideally be defined as callPackage pkgs/by-name/fo/foo/package.nix { }. This means that there's a one-to-one mapping from attributes to files without any other necessary context:

pkgs.foo is defined in pkgs/by-name/fo/foo/package.nix
pkgs/by/name/fo/foo/package.nix defines pkgs.foo

In reality we still need to allow customising the { } argument in all-packages.nix. In order to keep the necessary context minimal, CI checks that all definitions for packages in pkgs/by-name look like callPackage pkgs/by-name/fo/foo <attrs>, where only <attrs> can change.

@philiptaron Thanks for the quick review! :heart:
Typos now fixed :D


Demo source

Hi all,
Where can I find the source of the demo on main page?
Cheers

https://github.com/rrag/react-stockcharts/issues/95


UDP driver to 2.0 syscalls

Updates the UDP driver to use the 2.0 system calls. Mostly works, but matching on error codes does not seem to work, I think this will need to be updated once the new error types are inserted in libtock-c

What is the strategy now that the full 2.0 interface is merged in libtock-c? Should I update this to use command2 / subscribe2 / etc. ?

What is the strategy now that the full 2.0 interface is merged in libtock-c? Should I update this to use command2 / subscribe2 / etc. ?

Probably a good idea.

updated to use the new system calls, and tested using the example apps, which work

bors r+


[Feature request] mDNS for wlan0

Hi, thanks for making this plugin, for me it turned out to be the only way of enabling AP on HA OS.
I miss connecting to HA by .local name over AP connection though.
I can see that in HA core it's implemented for eth0 using Network Manager, and I'm struggling to enable it for unmanaged wlan0 interface controlled by the plugin.
Should we add avahi daemon to this plugin?
Or, anybody has better ideas?
I'm happy to help with coding once we agreed on the approach.

Not sure of the details, but in my case mDNS works correctly, can access ESPHome nodes & homeassistant.local correctly.
Maybe it was added at some point? :)

@CarlosGS How did you manage to get your ESPHome devices to connect to your hassio instance? I've been trying to flash an ESP8266 I had lying around to connect to the HASSIO instance I have, but It cannot seem to register in the ESPHome gui nor in Homeassistant. Wierdly enough I can see it connect in the logs for this access point add on, which tells me it should work. Any pointers you can give me or articles I can read? Been trying to google this with no progress.
Here's what I flash my espdevice with, if that helps? I can connect to the AP with an android phone and access homeassistant so it can't be that either.

esphome:
name: wrist-device
esp8266:
board: esp01_1m
Enable logging
logger:
Enable Home Assistant API
api:
encryption:
key: "xxxxxxxxxxxxxxxx"
ota:
password: "xxxxxxxxxxxxxxxxxxx"
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "Wrist-Device Fallback Hotspot"
password: "xxxxxxxxxx"
captive_portal:
output:

id: onboard_light
platform: gpio
pin: GPIO2
inverted: true

Hi! In the end I've set a fixed IP for each device. It simply needs an IP outside the DHCP range.
wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password
  manual_ip:
    static_ip: <IP_ADDRESS> # (.3, .4, etc)
    gateway: <IP_ADDRESS>
    subnet: <IP_ADDRESS>

Then you need to manually connect them to Home Assistant (Devices->Add->Esphome->type node's IP).
In your case, try doing that and typing "wrist-device.local" instead of an IP. Maybe it will resolve the address and allow you to use it without needing a fixed IP.
Also, for ESPHome nodes, I've noticed we MUST set power_save_mode: none, otherwise the connection was very unreliable with the Raspberry 3B+ onboard wifi. It seems the RPi doesn't respect wifi timings for power saving.


Doesn't automatically dedupe React

I've been trying to run a small project with vite-plugin-react-swc using MUI, but it always errored out with:
Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.

Adding resolve: {dedupe: ["react", "react-dom"]} to vite's config solves the problem. vite-plugin-react seems to automatically do this, so maybe it would be a good idea for this one, too?

My personal opinion is that it's better to know that current lockfile is in a bad state, but for compatibility I will to it here too.

I'm sorry, what do you mean with "that current lockfile is in a bad state"? Are you talking about package-lock.json or something else?
Maybe it's my fault after all 🙈

I've just checked npm ls react and npm ls react-dom, and while both show that a lot of packages depend on them, it's only ever version 18.2.0 :/
I think I've once read that the problem might occur because vite uses esm, but some modules might use cjs, and thus react will be loaded twice - can that happen? Would that be precented by dedupe?

react still doesn't ship esm format (and if it did Vite should always enforce using the ESM one).
I'm curious on how you ended with this warning. The most probable in that case is a bug in the pre-bundling of deps with late discovered deps. And I will be surprised that dedupe help in that case, or maybe I'm wrong on how dedupe works in Vite

Thank you so much for your help, that clears things up a lot 🙂
Could it be a problem if one of the dependencies supports esm and depends on React?
Also, I'll try to build a mini test-case, if/when I have time... but that might be a bit...

Did you found the root cause of the duplicate react module?
As I'm rethinking it now,  React 17 did some internal changes to allow to have multiple react version on the same page (not in the same tree i think) so I would not force people to one version actually.

Unfortunately, I couldn't find the problem :(
Feel free to close this issue. If I can remember/find something, I'll just comment again.
Thanks for your time!


[FEATURE] OPT-175B service authentication and new priority queue

See the issue page https://github.com/alpa-projects/alpa/issues/700. I made some design choices based on my comment there, see if the design choices make sense.

Example informal test that I've done:
I set the weight for API key "key1" to be default and "key2" to be 3 times higher.
I've run the following on the command line
for i in $(seq 0 20); do ( curl -d '{"model": "default", "prompt": ["This year,", "This month,"], "max_tokens": 16, "api_key": "key1"}' -H 'Content-Type:application/json' localhost:20001/completions && echo "
AAAAAAA$i" ) & done
for i in $(seq 0 20); do ( curl -d '{"model": "default", "prompt": ["This year,", "This month,"], "max_tokens": 17, "api_key": "key2"}' -H 'Content-Type:application/json' localhost:20001/completions && echo "
BBBBBBB$i" ) & done
for i in $(seq 0 20); do ( curl -d '{"model": "default", "prompt": ["This year,", "This month,"], "max_tokens": 18, "api_key": ""}' -H 'Content-Type:application/json' localhost:20001/completions && echo "
CCCCCCC$i" ) & done
for i in $(seq 0 20); do ( curl -d '{"model": "default", "prompt": ["This year,", "This month,"], "api_key": "key1", "top_k": 10}' -H 'Content-Type:application/json' localhost:20001/logprobs && echo "
LLLLLLL$i" ) & done
for i in $(seq 0 20); do ( curl -d '{"model": "default", "prompt": ["This year,", "This month,"], "api_key": "", "top_k": 10}' -H 'Content-Type:application/json' localhost:20001/logprobs && echo "
DDDDDDD$i" ) & done

At the same time, I start making requests with several tabs on the web interface.
The result is that:

The web interface requests are handled with low latency,
The BBBBBBB requests are served about 3 times more often than the AAAAAAA requests,
The CCCCCCC and LLLLLLL requests are served about 10 times less often than the AAAAAAA requests,
The DDDDDDD requests are served a few times while the other tasks exist, then the remaining requests get handled

Thanks for your contribution. I replied to your comments. I will review this PR later this week.

Looks like the code is well-documented and well-tested. The design is what we want in #700 and it carefully considers a lot of potential issues.
Thanks for your contribution! I will do more tests and try to deploy it on our website. I will merge this first as the code holds a very high quality.