text:
angular element with overlay rendered in overlay

Reproduction
https://github.com/rcketscientist/AngularElementOverlayRepro
Steps to reproduce:

Create an Angular Element that leverages a CdkOverlay Material widget (tooltip, select, etc)
Place that selector in a CdkOverlay (MatDialog, for example).

As soon you interact with the "inner" CdkOverlay by hovering over the tooltip or activating the select, the host CdkOverlay will just crash without an error message I can pick up on.
This might not really be a bug, but rather a limitation of Angular Elements, but being that it can be triggered with simple widgets I wonder if there's not some way I can get the Angular Elements to play well with the host.
The Angular Elements work fine when not hosted in a CdkOverlay.
Expected Behavior
What behavior were you expecting to see?
CdkOverlay within Angular Element plays well with the host.
Actual Behavior
What behavior did you actually see?
Acitvation of the CdkOverlay within an Angular Element causes the host CdkOverlay to silently crash.
Environment

Angular:8
CDK/Material: 8
Browser(s): Chrome
Operating System (e.g. Windows, macOS, Ubuntu): Win/Mac

@rcketscientist Thanks for this issue. I created a StackBlitz out of your reproduction: https://stackblitz.com/edit/comp-16862?file=src/main.ts.
With the latest version, I don't seem to be able to see the crash you mentioned, but I see an issue where the overlay container order is incorrect and the tooltip/select from the element are behind the actual dialog overlay. It depends on what overlay container is created first and based on my understanding we cannot combine them into a single overlay container.

The crash (dead overlay) does indeed seem to be gone, that's good.  I had a note in our workaround that Ivy would solve this, but I don't recall at this point what led me to that assumption.
While our app architecture changed and we no longer have this issue, what I had done was this:
export class PathwaveOverlay extends OverlayContainer {
    constructor(
        @Inject(DOCUMENT) _document: any,
        @Inject(OVERLAY_NAME_TOKEN) private pluginName: string) {
        super(_document);
    }

    _createContainer(): void {
        const containerClass = 'cdk-overlay-container';

        const container = this._document.createElement('div');
        container.classList.add(containerClass);
        container.classList.add(this.pluginName);
        this._document.body.appendChild(container);
        this._containerElement = container;
    }
}

@NgModule ({
    providers: [
        { provide: OverlayContainer, useClass: PathwaveOverlay },
        { provide: OVERLAY_NAME_TOKEN, useValue: "plugin" }
    ]
})
export class PathwaveModule {
    public static forRoot(pluginName: string): ModuleWithProviders {
        return {
            ngModule: PathwaveModule,
            providers: [ { provide: OVERLAY_NAME_TOKEN, useValue: pluginName } ]
        }
    }
}

That gave us the flexibility to target the containers and avoid collisions (when that was still a crash).  Doesn't feel robust enough a solution in the main repo, however.

@devversion
This is Jeff Arnett from Keysight technologies (a spinoff of Hewlett Packard).
This issue related to Angular Elements was well documented by a colleage last year and it threatening to jeopardize a cross platform strategy based on an Angular implementation.
Can you comment on whether its been fixed in Ng10? Maybe more importantly can you comment on the general support for mat/cdk use within an Angular element?
Anything you can help us here with would be desperately appreciated?

@devversion Update. I upgraded the sample above to Ng10 and see the same index issues that you are.
It happens only if a cdk-overlay-container is created by the app (say a menu is dropped on the main app) and then the dialog overlay comes up (which hosts a WC based overlay). In that case there are two cdk-overlay-containers and the full Ng stack that is hosted inside the WC is creating what is essentially an "unkown to the rest of the world" overlay container that has a root/body level z-index (net is the overlay hosted in the WC inside of the main app overlay (dialog) is behind everything).
Can you comment on this use of overlays in a WC hosted in a normal Ng app?

@Arnie38 The original error reported in this issue seems to have been fixed. Though there is still the issue (as you noted) of multiple overlay containers being created. This seems expected at first glance since the WC should not communicate between each other at a global level, but at the same time it would be necessary to make stacked overlays work from WCs.
I think there are two cases. (1) Angular elements are defined in the consumer application. In that case they should share the same injector to have the same overlay container. And (2) the Angular elements are defined externally (e.g. on file load within a self-contained module). In that case it's expected that they share different injectors and will have different overlay containers.
The question for us is: Should we re-use existing overlay containers (i.e. from potential other injectors/modules) if we find one, or should the Angular element creators build their own overlay container that does this? This might work here as a workaround, or sharing the injector if there is the possibility of defining the elements in the consumer application/module.

It's funny, that is almost literally the conversation I had with @Arnie38.  The thing I couldn't answer was how safe it was to share the overlay.  To me, that's the obvious use-case, but I figured the fact it does not do that must imply there's another use-case, or a complication to re-using the injected overlay.
One thing I wasn't sure about was, "Can an ngElement share the host root injector?"  I actually thought they were separate and this was a potential use-case for providedIn: platform (haven't used this yet).  Or might require a custom override that queried for an existing Overlay in the DOM, but required the host to push an overlay on load to always ensure it was "first in".  Not the greatest solution.  However, if the injectors are available in the ngElement that's a whole 'nother story.
Why would (2) expect a different injector?  Maybe this answer is tied to my ignorance on ngElements interacting with host injectors?

but I figured the fact it does not do that must imply there's another use-case, or a complication to re-using the injected overlay.

Yeah, I don't exactly recall any reason for not sharing, but that's something we need to figure out as part of this issue.

One thing I wasn't sure about was, "Can an ngElement share the host root injector?"

Could you briefly elaborate on this? Based on my understanding an Angular custom element always receives an instance of an Angular injector. e.g. when you define the custom element:
ngDoBoostap() {
  customElements.define('example-element',
     createCustomElement(ExampleComponent, { injector: this.myModuleInjector }));
}

So if you have full control over an Angular element, you could define it as part of your module bootstrap so that all share the same injector from your AppModule. That should fix the multiple overlay container issues quite nicely. e.g.
export class AppModule {
  constructor(private injector: Injector, private appRef: ApplicationRef) {}

  ngDoBootstrap() {
    // Define all Angular elements with the same injector.
    this._defineAllElements(this.injector);
    // Bootstrap the app.
    this.appRef.bootstrap(AppComponent);
  }
}

And if you're in an AngularJS upgrade scenario, you could still have a single module for all Angular elements so they share the same injector.

Why would (2) expect a different injector? Maybe this answer is tied to my ignorance on ngElements interacting with host injectors?

Sorry, I might have expressed this in a confusing way. I meant that there are cases where a Angular custom element is loaded from an external file for example. In those cases, the file/"library" already bootstraps a separate module dedicated to define the custom element. In those cases, a temporary module and injector is used to define the custom element.
e.g. node_modules/ng-element/my_angular_element.js
@NgModule(..)
class MyElementTempModule {
  ngDoBootstrap() { /* define elements */ }
}

// Bootstraps the temp module so that the Angular element is usable
// as a custom element.
platformBrowser().bootstrapModule(MyElementTempModule);

Ok, we're on the same page now.  The issue was that I was only thinking of loading an external element; I didn't even think of creating and using an ngElement within the same app.  I'm totally blanking on the use-case there, as opposed to simply using the component.  Which also happens to be my current recommendation for the above issue.  Just use an angular library in an angular app and supply the ngElement for those not in Angular.
Is the new providedIn: platform with a service that shares the host's overlay a possibility?

I'm totally blanking on the use-case there, as opposed to simply using the component.

Yeah, for sure. I can't think of a good use-case from the top of my head either. The pattern remains the same though. The Angular elements would need to be defined as part of a single module w/ same injector. Could you share your concrete use-case for this issue? (so that we are on the same page; that is what I'm somehow missing still).

The original use-case was a host desktop application with a window manager (custom GoldenLayout), that would dynamically load entire applications via ngElements into individual panes.  The original hack above was developed to ensure that the "last in" app didn't eat the overlay, which I think went away in ng9 anyway.  There were also a host of hacks hoisting overlays at times among other things that led to code that was more comment than code, lol.  Thankfully, that design was abandoned in the end.
I believe @Arnie38 is attempting to distribute universal components for a cloud deployment, so consumers can BYOF(ramework).  I'll let him fill in more.

@devversion Thanks for all the helpful info.
Here is my specific scenario...

Have an Ng app with overlays. Same Ng app includes a WC with its own overlays. The overlays of the main Ng app also host yet another/different WC with yet another set of overlays. This "stacked" scenario is tickling the z-index issue we have discussed.
Details...
Ng app includes a WC implemented top/nav bar proffered from a lib. This WC has overlays (tooltips, menus, selects etc.)
If user of Ng app invokes any overlay based control from the WC navbar ...I see a cdk-overlay-container created
If Ng app also has a normal overlay based control (in this case a dialog) and user invokes it I see a 2nd overlay container to host that dialog
User then invokes an overlay based control found in a WC hosted in the dialog (main app) overlay
The content of the main app -> dialog/overlay -> WC overlay is "submarined" behind the dialog. It chooses the wrong (or creates its own) cdk-overlay container that doesn't know about the world around it and therefore seems to be a child of the root and therefore is a lower z-index than the dialog
*In this scenario we would control all hosting apps and WC pieces/parts. The WC would be delivered as .js elements and host apps would really only use them if they were non angular or if using a different incompatible major version of Angular (our primary use case for using AE). Our apps range from Ng6 - Ng10 (even som Ng4 apps).

@devversion So since we control everything seem like your suggested answer from above is the way to go. A bit of coding on the part of each adopter. PS This is really only an issue with AE being used in Ng apps. IOW Say react adopters would have no such headache to deal with.
export class AppModule {
constructor(private injector: Injector, private appRef: ApplicationRef) {}
ngDoBootstrap() {
// Define all Angular elements with the same injector.
this._defineAllElements(this.injector);
// Bootstrap the app.
this.appRef.bootstrap(AppComponent);
}
}

@devversion I tried the above with no success. Obviously that this._defineAllElements() is pseudo code for defining any all Angular components as Angular Elements here in the context of the using/consuming app. So they have a shot of all sharing the same injector.
When I do that the Angular components have all kinds of dependencies and setup that the consuming app has to now know about. I was hoping to keep a very strict architectural boundary there with the host app just importing a .js of the web component. That said if this is the only way then for those adopters that have this issue (overlay that hosts a WC that has an overlay) then they'll have to make do.
Any way that providedIn: Platform new feature can help rendezvous all with the same injector?

Everyone! We need more thumbs-up at first post. Or feature request will be doomed.

authors: Arnie38 GitStorageOne devversion rcketscientist

repo: angular/components


text:
Release 8.1.0 introduce an undocummented breaking change in MatMenu

Reproduction
Working version on Material 8.0.0: https://stackblitz.com/edit/components-issue-6khp86
Non-working version on Material 8.1.0: https://stackblitz.com/edit/components-issue-bntnr9
Caused by https://github.com/angular/components/commit/49e8c59
Steps to reproduce:

Open menu
Try to use keyboard navigation - up-down arrows (does not work on version 8.1.0)

It also does not work in case of opening sub-menus by mouse hover
Expected Behavior
It should work the same since it is not mentioned in changelog and is introduced in minor version
Actual Behavior
In version 8.1.0 when mat-menu-item is used inside of nested component, it does not register to parent.
Environment

Angular: 8.0.0
CDK/Material: 8.1.0
Browser(s): Chrome
Operating System (e.g. Windows, macOS, Ubuntu):  Windows

I came across the very same problem after updating the versions recently and it's a pure blocker for me...

Also, if I am not mistaken, this blocks the only way how to use MatMenu for infinite nesting

I was just about to report this issue myself.
I wrote a small library for dynamic menu rendering (ng-action-outlet - feel free to use it) and this issue really is a show stopper.
This is either a BREAKING CHANGE either a bug. Preferably a bug, because we for sure need the possibility to infinitely nest menus.
I think this is the commit: 49e8c59

Any news here? We're waiting for this fix like children for Christmas...

This relates to the existing #16457.  There was PR (#16502) to revert the breaking change.  It was approved yet never merged, simply closed with no explanation.

@jelbourn can we get some kind of comment whether the mentioned pull request was closed intentionally? In our team we need to decide whether to implement some ugly workarounds to make it work with latest Material or whether we can wait some time for reverting the breaking change.
It would help us a lot to at least know what to expect. Thanks in advance!

That fact that menu items previously ignored component boundaries was a bug and was inconsistent with the way that all other Angular components work. The underlying issue also caused menu items to be in the wrong order for keyboard interaction, which is a pretty bad bug (especially for a11y). We have no plans of reverting this change, but we have been looking into other ways of programatically providing additional items for the menu.

@jelbourn thanks a lot for the explanation 👍

Bottom line is, currently material does not support programmatic nesting which breaks some applications. That's a bad news.

Could we perhaps keep this issue opened until the functionality is available again (unless it's not in your plans any more to support it)?

It's something we're thinking about more broadly, and it has implications on things like integrating virtual scrolling into the existing components, but there's no ETA now

To everyone looking for dynamic menus in angular 8 i made a working example:
https://stackblitz.com/edit/dynamic-material-menu-angular-8

I managed to update ng-action-outlet above Material ~8.1.0. This required a substantial refactoring though.
If you're writing your own component to render menus dynamically, the key is to maintain the direct menu nesting between mat-menu and mat-menu-item, without any components in between, due to that recent material change of querying for direct children only.
Example from @Harpush demonstrates this nicely: https://github.com/angular/components/issues/17073#issuecomment-548547557

Anyone interested in a library, here are the usage examples:

source: gharchive/issue

authors: Harpush RandomNonameDude dgsmith2 jelbourn klemenoslaj palpatine1991

license: MIT

license_type: permissive

license_source: github-api


text:
form-field(outline): floating label overlaps outline in MS Edge

Reproduction
Steps to reproduce:

Open https://material.angular.io/components/form-field/overview#form-field-appearance-variants in Microsoft Edge
Click into the Outline form field example.

Expected Behavior
The outline should not be visible underneath the label, as in other browsers.

Actual Behavior
The outline overlaps with the label text.

Environment

CDK/Material: 8.2.3
Browser(s): Edge
Operating System: Windows 10

This issue exists on Edge version 42.17134, but not on any post Chromium (80+) versions I've tested.

It looks like the width property of .mat-form-field-outline-gap isn't being set. This is being done in line 590 of form-field.ts:
    for (let i = 0; i < gapEls.length; i++) {
      gapEls[i].style.width = `${gapWidth}px`;
    }

I'm guessing it's either an issue with that, or with calculating the width before it's applied.
I'm going to have to set these manually for each form field to work round this.

Closing since this issue does not occur in Chromium-based Edge. We no longer support older versions

authors: andrewseguin graphical-iain stockcj


text:
fix(select): Improve the a11y of select component by making overlay

always exist in the DOM

@crisbeto We discussed the possibility of loading options when user focus on the select, and we think it's too late.

Looks like there are just some lint errors now

Caretaker note: may need to change this from patch to something else depending on how many tests need to be updated in google

Just wanted to link this over to the related issue: https://github.com/angular/material2/issues/11083.

@jelbourn I think that this one is a good candidate for closing or reviewing for closing at the next meeting?

source: gharchive/pull-request

authors: Splaktar jelbourn tinayuangao


text:
fix(material/datepicker): remove CSS content from body cells

Attempts to fix unnecessary tab stop with VoiceOver by removing the CSS
content from cells in the calendar body. After testing locally, this did
not remove the duplicate tab stop.
Environment

macos 12.0.1 (21A559)

Chrome Version 96.0.4664.93 (Official Build) (x86_64)

localhost:4200/datepicker

relates to #24082

still in draft because this implementation is not fixing the bug yet. Create a draft to share the diff with @jelbourn and @crisbeto

closing because the duplicate tabstop in VoiceOver has been fixed


text:
ERROR in : Unexpected value 'ScrollingModule in ...

Bug, feature request, or proposal:
Bug
What is the expected behavior?
@angular/material@7.0.0-beta.0 with latest @angular/* should compile without errors using webpack and AngularCompilerPlugin (@ngtools/webpack).
Downgrading to @angular/masterial@6.4.7 while keeping everything on 7 beta works fine.
What is the current behavior?
The following error message is produced when during build:
ERROR in : Unexpected value 'ScrollingModule in C:/Users/me/repo/mono/packages/web-app-edit/node_modules/@angular/cdk/scrolling.d.ts' imported by the module 'MatSidenavModule in C:/Users/me/repo/mono/packages/web-app-edit/node_modules/@angular/material/sidenav/typings/index.d.ts'. Please add a @NgModule annotation.

What are the steps to reproduce?
Update all angular dependencies to latest beta.
Import any material module from @angular/material into your application and build with webpack@4 and AngularCompilerPlugin (@ngtools/webpack).
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Windows 10 x64
  "devDependencies": {
    "@angular-devkit/build-optimizer": "0.9.0-beta.3",
    "@angular/cli": "7.0.0-beta.3",
    "@angular/compiler-cli": "7.0.0-beta.5",
    "@ngtools/webpack": "7.0.0-beta.3",
    "webpack": "4.19.0",
    "webpack-cli": "3.1.0",
    "webpack-dev-server": "3.1.8",
    "typescript": "3.0.3"
  },
  "dependencies": {
    "@angular/core": "7.0.0-beta.5",
    "@angular/forms": "7.0.0-beta.5",
    "@angular/material": "7.0.0-beta.0",
    "@angular/platform-browser": "7.0.0-beta.5",
    "@angular/animations": "7.0.0-beta.5",
    "@angular/cdk": "6.4.7",
    "@angular/common": "7.0.0-beta.5",
    "@angular/compiler": "7.0.0-beta.5",
    "@angular/http": "7.0.0-beta.5",
    "@angular/router": "7.0.0-beta.5",
    "@angular/platform-browser-dynamic": "7.0.0-beta.5",
    "core-js": "2.5.7",
    "rxjs": "6.3.2",
    "zone.js": "0.8.26",
  }

Is there anything else we should know?

Well, I can see in my own ticket that @angular/cdk forsome reason was not updated. Must have checked the other angular repo when double checking.


text:
Angular Material2 - Roadmap

Proposal:
As per milestone & google group threads , it seems this project is currently lagging bit behind. Also  https://github.com/angular/material2/issues/11 has been closed but there is still a structured roadmap & devlopment guide missing.
Given that angular2 is close to production release it will be really great if we can have some estimates on when to expect a beta version, the estimate on respective design docs seems to be not updated recently.
Going through google group threads and other forums I think the angular2 community will really appreciate the following:

Better project organization and pace with explicit roadmap and deadlines (Atleast for when should we expect the apis to be frozen for the essential components)

If possible then involve others from the community toward contributing (Even a very brief development wiki on the internal working & wiring of the framework will be a real help).

+1

+1

+1

alpha.6 is slightly delayed due to some unforeseen work that came up over the last couple of weeks. Situations like this are exactly why we aren't able to commit to a more specific date. We announced at ng-conf that we're aiming at a beta for this year, but promising something more than that will potentially just disappoint everyone if it is delayed. The milestones will be updated next week when we meet again and reschedule the delayed work.
As far as contributing, we're very open to contributions, and there have been quite a few PRs from community members. Check out our contributing guide and dev environment guide.

@jelbourn are you planning to upgrade to last angular rc in alpha.6?

@zigzag95 Yes, sometime next week

Delays are part of all projects and but having specific dates help others plan accordingly with a slack for tham as well as push admin to try hard once they are crossed. As for contributions, a brief guide on usage of the core libs would have been very helpful though now I am going through the source, the code comments are very well written.
A beta by end of the year will fit my migration plans for angular 2 well, thanks.

Have to agree- this project is not contributor friendly.  I would love to contribute to various components within this project, but I am continually told these components have already been assigned to other people, who are not visibly working on the project.  Canonical example:
https://github.com/angular/material2/issues/45

+1 !
I'd really appreciate something similar to angular weekly meeting notes, to give us a weekly update on what's actually going on.

authors: DerekTBrown JanickRoss agaurav fxck jelbourn roughsoft zigzag95


text:
Set a select's value from within the containing expansion panel's opened event

Bug, feature request, or proposal:
Bug. If I set a select's value via Form.controls['myControl'].setValue from within an expansion panel's opened event, the control gets the value, but its visual appearance is as if no value was set.
The expansion panel contains the select.
What is the expected behavior?
It should be possible to set a select's value via Form.controls['myControl'].setValue from within an expansion panel's opened event.
What is the current behavior?
I call Form.controls['myControl'].setValue from within the expansion panel's opened event to set a contained select's current value. The value is set as can be checked via alert(Form.controls['myControl'].value), but the visual appearance of the select is as if the value was not set.
What are the steps to reproduce?
Providing a StackBlitz/Plunker (or similar) is the best way to get the team to see your issue.
Plunker starter (using on @master): https://goo.gl/uDmqyY
StackBlitz starter (using latest npm release): https://goo.gl/wwnhMV
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 5, Material 5.0.0, Typescript 2.5.3
Is there anything else we should know?

@TimoKunze can you provide a Plunker/Stackblitz that shows the issue? Trying out something similar against our demo app works as expected.

So far I can NOT reproduce it with a simple Stackblitz: https://angular-vclwfe.stackblitz.io
I'm still trying to figure out the differences to my app.

I'm shooting in the dark here, but perhaps you're using ChangeDetectionStrategy.OnPush or are running the callback outside the Angular zone?

Ah, I've found the problem. It's waaaaay simpler than we thought: I have been calling setValue with an array, but it is no multi-select. Seems like some former release did allow this.
Many thanks for your help!

Glad to help. Closing as a non-issue.

authors: TimoKunze crisbeto


text:
feat(select): emit change event

Adds an event to md-select that is emitted when the selected option has changed.
Fixes #2248.

Addressed the feedback @kara.

Fixed @kara, not sure how I forgot to remove the last one.

@crisbeto Is this ready to merge? Just noticed it doesn't have the label.

It is, I'm not sure who's supposed to add the label.

@crisbeto Since you are the author and a member of the repo, you are the one that adds the "merge ready" label :)  "LGTM" just means that it's approved; "merge ready" means that the author has made all the changes they wanted to.

authors: crisbeto kara


text:
Upload file using protractor

Hi @juliemr ,
Need some info, i need to upload a file using protractor below is the screenshot of the app
Now when i click on the Select File it shows browse button, can i automate the fileupload window of browser. If yes can you provide me with  example.

Hoping for reply.
Thanks,
Naresh Kumar

Hi there!
Your question is better suited for StackOverflow or Gitter. There is already an answer on StackOverflow for your question. If that does not resolve your problem, please ask a question there with the 'protractor' tag or post in the Gitter Channel to get help.
From the the getting help section of the README:

Please ask usage and debugging questions on StackOverflow (use the "protractor" tag) or in the Angular discussion group. (Please do not ask support questions here on Github.)

Thanks!

Hi,
i have checked in StackOverflow but couldnot figure it out. so posted over her...
can you provide me with some links... that would be helpful.

repo: angular/protractor


text:
fix(eventListener): use the correct WTF issue array to iterate on

It seems that zone.js iterates on the wrong array while considering WTF issue. This results in a lot of unnecessary iterations and object creations. Although it seems that the main functionality is not affected.

@jahtalab , thank you for the fix, this my typo, LGTM.

@jahtalab, could you rebase your PR, the CI failed because your .travis.yml still using nodejs 6.

@jahtalab, sorry this PR takes so long, the PR doesn't been merged because it need rebase, now zone.js has been moved to angular/angular https://github.com/angular/angular/tree/master/packages/zone.js, could you re-create this PR there?
Thanks.

https://github.com/angular/angular/pull/31208

authors: JiaLiPassion jahtalab

license: mit

license_source: bigquery


text:
Fixed ruRU locales

This should fix issue #23
Don't know why the file has been wrongly written.

We don't edit the locale files directly. They get inserted with strings from the CurseForge packager so the problem was at the localization. I've fixed it now and will go through all other strings in case there are more. Thanks for trying though. :)

Yeah I know. Just opened this pull request so the russian can see the file and take it.

authors: Meivyn anhility

repo: anhility/BestInSlotRedux


text:
[BUG]: [ERROR] HTTPError 403: Forbidden

Program version
4.6.3
Operating System
Windows
Type
GUI
Service
Crunchyroll
Command used
none
Show ID
none
Episode
none
Console Output
=== Multi Downloader NX GUI 4.6.0 ===

GUI server started on port 3000
[WS] Connection to public ws from '::1'
[WS] Connection from '::1'
[WS] Connection from '::1'
[ERROR] HTTPError 403: Forbidden
[ERROR] Just a moment...
[ERROR] Authentication failed!
[ERROR] HTTPError 403: Forbidden
[ERROR] Just a moment...
[ERROR] Authentication failed!
[ERROR] HTTPError 401: Unauthorized
[ERROR] Body: {"code":"accounts.get_profile.invalid_auth_token","context":[]}

[ERROR] Get profile failed!

Additional Information
Message accours directly after launching the GUI. Issuing "Authentication" repeats the problem again and again.
Also tried a fresh pull of the repo, same results.
worked fine the last two days.
my cr account is still valid & i can stream via Browser.
tell me if you need any further logs or have any questions :).

Pushed a commit that should fix it, if you would be willing to build it, test it, and give feedback, that would be nice, otherwise it will be available in the next release which will be after I test it enough

Released version 4.7.0 which should fix the issue

Going to close this since it was fixed

repo: anidl/multi-downloader-nx


text:
Embed Parts are Deprecated.

I was thinking that developers should update all of the Embed parts so there will be no deprecation warning on users console.

We are working on the update and all the embeds will be updated by the next Update :D

We are working on the update and all the embeds will be updated by the next Update :D

ok! thanks!

Closing the issue :D


text:
[Source Request]

PLEASE READ THIS
I acknowledge that:

I have checked that the extension does not already exist:

In the list of existing extensions in the application
In the multi-source spreadsheet: https://tachiyomi.org/extensions
By searching the GitHub repository for the extension and verify it does not appear in the code base

I have searched the existing GitHub issues and this extension does NOT have an open request
I will fill out the title and the information in this template

Note that the issue will be automatically closed if you do not fill out the title or requested information.
DELETE THIS SECTION IF YOU HAVE READ AND ACKNOWLEDGED IT

Source website

Name: Anixlife
Link: https://anixlife.xyz/
Language(s): Indonesia

Other details
Streaming Anime & Donghua

MoonLGH bang bisa di buatkan yg ini gk, buat nonton donghua, soalnya blum ad nih yg donghua min

New domain https://anixverse.com/

repo: aniyomiorg/aniyomi-extensions


text:
Please Add MangaReader

Source name
MangaReader
Source link
https://mangareader.to/
Source language
English/France/Japanese
Other details
It has so much vast majority of manga.

Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a title with source name.
[X] I have checked that the extension does not already exist on the website extensions list or the app.
[X] I have checked that the extension does not already exist by searching the GitHub repository and verified it does not appear in the code base.
[X] I will fill out all of the requested information in this form.

This isn't the repo for manga extensions. Besides, this already has an extension.

authors: MegaMinus Secozzi


text:
build failed

docker build . -t xxx/elastalert-docker:v0.2.4 --build-arg MIRROR=true
#10 6.760 OK: 18 MiB in 43 packages
#10 6.827 + apk add --no-cache --virtual .build-dependencies gcc libffi-dev python-dev tar musl-dev openssl-dev
#10 6.834 fetch https://mirrors.aliyun.com/alpine/v3.14/main/x86_64/APKINDEX.tar.gz
#10 7.082 fetch https://mirrors.aliyun.com/alpine/v3.14/community/x86_64/APKINDEX.tar.gz
#10 7.479 ERROR: unable to select packages:
#10 7.531   python-dev (no such package):
#10 7.531     required by: .build-dependencies-20210827.095016[python-dev]

去掉也不行，

这是我的，没问题，不行你就试试把python-dev 改成python3-dev试试
docker build . -t elastalert --build-arg MIRROR=true
Sending build context to Docker daemon  151.6kB
[WARNING]: Empty continuation line found in:
    RUN set -ex &&     if $MIRROR; then sed -i "s/dl-cdn.alpinelinux.org/${ALPINE_HOST}/g" /etc/apk/repositories ; pip config set global.index-url ${PIP_MIRROR} ; /bin/echo -e "[easy_install]\\nindex-url = ${PIP_MIRROR}" >> ~/.pydistutils.cfg ; fi &&     apk update &&     apk upgrade &&     apk add --no-cache         ca-certificates         tzdata         su-exec         dumb-init         bash         curl         openssl &&     apk add --no-cache --virtual         .build-dependencies         gcc         libffi-dev         python-dev         tar         musl-dev         openssl-dev &&     pip install --upgrade pip
[WARNING]: Empty continuation lines will become errors in a future release.
Step 1/23 : FROM python:3.6-alpine
 ---> 2bb6435d63d9
Step 2/23 : LABEL description="ElastAlert for docker reference @sc250024/docker-elastalert"
 ---> Using cache
 ---> b285196ac3e8
Step 3/23 : LABEL maintainer="anjia0532 (anjia0532@gmail.com) Scott Crooks <scott.crooks@gmail.com>"
 ---> Using cache
 ---> a04904526be5
Step 4/23 : ARG ELASTALERT_VERSION=v0.2.4
 ---> Using cache
 ---> 653f449a3b07
Step 5/23 : ARG MIRROR=false
 ---> Using cache
 ---> 0d361e4fdeee
Step 6/23 : ARG ALPINE_HOST="mirrors.aliyun.com"
 ---> Using cache
 ---> 7b24026c98b6
Step 7/23 : ARG PIP_MIRROR="https://mirrors.aliyun.com/pypi/simple/"
 ---> Using cache
 ---> 2578ceeee261
Step 8/23 : ENV ELASTALERT_HOME=/opt/elastalert     SET_CONTAINER_TIMEZONE=true     CONTAINER_TIMEZONE=Etc/UTC
 ---> Running in be0c6a5b23d8
Removing intermediate container be0c6a5b23d8
 ---> 202e20d67f80
Step 9/23 : ENV ELASTALERT_URL=https://github.com/Yelp/elastalert/archive/${ELASTALERT_VERSION}.tar.gz      ELASTALERT_RULES_DIRECTORY=${ELASTALERT_HOME}/rules     ELASTALERT_PLUGIN_DIRECTORY=${ELASTALERT_HOME}/elastalert_modules     ELASTALERT_ENHANCEMENT_DIRECTORY=${ELASTALERT_HOME}/elastalert_enhancements     ELASTALERT_CONFIG="${ELASTALERT_HOME}/config.yaml"     ELASTALERT_INDEX=elastalert_status     ELASTALERT_SYSTEM_GROUP=elastalert     ELASTALERT_SYSTEM_USER=elastalert     ELASTICSEARCH_HOST=elasticsearch     ELASTICSEARCH_PORT=9200     ELASTICSEARCH_USE_SSL=False     ELASTICSEARCH_VERIFY_CERTS=False
 ---> Running in b4d6afe4b663
Removing intermediate container b4d6afe4b663
 ---> 2e4dda0797c4
Step 10/23 : WORKDIR ${ELASTALERT_HOME}
 ---> Running in 68088faa3f0c
Removing intermediate container 68088faa3f0c
 ---> d5c0ea328942
Step 11/23 : COPY --from=jwilder/dockerize:0.6.1 /usr/local/bin/dockerize /usr/local/bin/dockerize
 ---> f5fc369e99a2
Step 12/23 : RUN chmod +x "/usr/local/bin/dockerize"
 ---> Running in 268ee8f3b8ea
Removing intermediate container 268ee8f3b8ea
 ---> b6c24af357e4
Step 13/23 : RUN mkdir -p "${ELASTALERT_HOME}" &&     mkdir -p "${ELASTALERT_PLUGIN_DIRECTORY}" &&     mkdir -p "${ELASTALERT_ENHANCEMENT_DIRECTORY}" &&     mkdir -p "${ELASTALERT_RULES_DIRECTORY}" &&     mkdir -p /var/empty &&     addgroup "${ELASTALERT_SYSTEM_GROUP}" &&     adduser -S -G "${ELASTALERT_SYSTEM_GROUP}" "${ELASTALERT_SYSTEM_USER}" &&     chown -R "${ELASTALERT_SYSTEM_USER}":"${ELASTALERT_SYSTEM_GROUP}" "${ELASTALERT_HOME}" "${ELASTALERT_PLUGIN_DIRECTORY}" "${ELASTALERT_RULES_DIRECTORY}"
 ---> Running in 607b4cfb3d1c
Removing intermediate container 607b4cfb3d1c
 ---> 6547989820e8
Step 14/23 : RUN set -ex &&     if $MIRROR; then sed -i "s/dl-cdn.alpinelinux.org/${ALPINE_HOST}/g" /etc/apk/repositories ; pip config set global.index-url ${PIP_MIRROR} ; /bin/echo -e "[easy_install]\\nindex-url = ${PIP_MIRROR}" >> ~/.pydistutils.cfg ; fi &&     apk update &&     apk upgrade &&     apk add --no-cache         ca-certificates         tzdata         su-exec         dumb-init         bash         curl         openssl &&     apk add --no-cache --virtual         .build-dependencies         gcc         libffi-dev         python-dev         tar         musl-dev         openssl-dev &&     pip install --upgrade pip
 ---> Running in e68d23b12eb9
+ true
+ sed -i s/dl-cdn.alpinelinux.org/mirrors.aliyun.com/g /etc/apk/repositories
+ pip config set global.index-url https://mirrors.aliyun.com/pypi/simple/
Writing to /root/.config/pip/pip.conf
+ /bin/echo -e '[easy_install]\nindex-url = https://mirrors.aliyun.com/pypi/simple/'
+ apk update
fetch http://mirrors.aliyun.com/alpine/v3.11/main/x86_64/APKINDEX.tar.gz
fetch http://mirrors.aliyun.com/alpine/v3.11/community/x86_64/APKINDEX.tar.gz
v3.11.11-117-g1e8f71f3b2 [http://mirrors.aliyun.com/alpine/v3.11/main]
v3.11.11-115-g305c493768 [http://mirrors.aliyun.com/alpine/v3.11/community]
OK: 11289 distinct packages available
+ apk upgrade
Upgrading critical system libraries and apk-tools:
(1/1) Upgrading apk-tools (2.10.5-r0 -> 2.10.8-r0)
Executing busybox-1.31.1-r9.trigger
Continuing the upgrade transaction with new apk-tools:
(1/12) Upgrading musl (1.1.24-r2 -> 1.1.24-r3)
(2/12) Upgrading libcrypto1.1 (1.1.1g-r0 -> 1.1.1l-r0)
(3/12) Upgrading ncurses-terminfo-base (6.1_p20200118-r3 -> 6.1_p20200118-r4)
(4/12) Upgrading ncurses-libs (6.1_p20200118-r3 -> 6.1_p20200118-r4)
(5/12) Upgrading libssl1.1 (1.1.1g-r0 -> 1.1.1l-r0)
(6/12) Upgrading krb5-libs (1.17.1-r0 -> 1.17.2-r0)
(7/12) Upgrading sqlite-libs (3.30.1-r1 -> 3.30.1-r2)
(8/12) Upgrading busybox (1.31.1-r9 -> 1.31.1-r10)
Executing busybox-1.31.1-r10.post-upgrade
(9/12) Upgrading ca-certificates-cacert (20191127-r1 -> 20191127-r2)
(10/12) Upgrading ssl_client (1.31.1-r9 -> 1.31.1-r10)
(11/12) Upgrading ca-certificates (20191127-r1 -> 20191127-r2)
(12/12) Upgrading musl-utils (1.1.24-r2 -> 1.1.24-r3)
Executing busybox-1.31.1-r10.trigger
Executing ca-certificates-20191127-r2.trigger
OK: 11 MiB in 33 packages
+ apk add --no-cache ca-certificates tzdata su-exec dumb-init bash curl openssl
fetch http://mirrors.aliyun.com/alpine/v3.11/main/x86_64/APKINDEX.tar.gz
fetch http://mirrors.aliyun.com/alpine/v3.11/community/x86_64/APKINDEX.tar.gz
(1/8) Installing bash (5.0.11-r1)
Executing bash-5.0.11-r1.post-install
(2/8) Installing nghttp2-libs (1.40.0-r1)
(3/8) Installing libcurl (7.67.0-r5)
(4/8) Installing curl (7.67.0-r5)
(5/8) Installing dumb-init (1.2.2-r1)
(6/8) Installing openssl (1.1.1l-r0)
(7/8) Installing su-exec (0.2-r1)
(8/8) Installing tzdata (2021a-r0)
Executing busybox-1.31.1-r10.trigger
OK: 17 MiB in 41 packages
+ apk add --no-cache --virtual .build-dependencies gcc libffi-dev python-dev tar musl-dev openssl-dev
fetch http://mirrors.aliyun.com/alpine/v3.11/main/x86_64/APKINDEX.tar.gz
fetch http://mirrors.aliyun.com/alpine/v3.11/community/x86_64/APKINDEX.tar.gz
(1/20) Installing libgcc (9.3.0-r0)
(2/20) Installing libstdc++ (9.3.0-r0)
(3/20) Installing binutils (2.33.1-r1)
(4/20) Installing gmp (6.1.2-r1)
(5/20) Installing isl (0.18-r0)
(6/20) Installing libgomp (9.3.0-r0)
(7/20) Installing libatomic (9.3.0-r0)
(8/20) Installing mpfr4 (4.0.2-r1)
(9/20) Installing mpc1 (1.1.0-r1)
(10/20) Installing gcc (9.3.0-r0)
(11/20) Installing linux-headers (4.19.36-r0)
(12/20) Installing pkgconf (1.6.3-r0)
(13/20) Installing libffi-dev (3.2.1-r6)
(14/20) Installing python2 (2.7.18-r0)
(15/20) Installing python2-dev (2.7.18-r0)
(16/20) Installing libacl (2.2.53-r0)
(17/20) Installing tar (1.32-r2)
(18/20) Installing musl-dev (1.1.24-r3)
(19/20) Installing openssl-dev (1.1.1l-r0)
(20/20) Installing .build-dependencies (20210830.033607)
Executing busybox-1.31.1-r10.trigger
OK: 182 MiB in 61 packages
+ pip install --upgrade pip
Looking in indexes: https://mirrors.aliyun.com/pypi/simple/
Collecting pip
  Downloading https://mirrors.aliyun.com/pypi/packages/ca/31/b88ef447d595963c01060998cb329251648acf4a067721b0452c45527eb8/pip-21.2.4-py3-none-any.whl (1.6 MB)
Installing collected packages: pip
  Attempting uninstall: pip
    Found existing installation: pip 20.0.2
    Uninstalling pip-20.0.2:
      Successfully uninstalled pip-20.0.2
Successfully installed pip-21.2.4
Removing intermediate container e68d23b12eb9
 ---> 960cb571cffc
Step 15/23 : RUN set -ex &&     curl -Lo elastalert.tar.gz ${ELASTALERT_URL} &&     tar -xzvf elastalert.tar.gz -C ${ELASTALERT_HOME} --strip-components 1 &&     rm elastalert.tar.gz &&     cd ${ELASTALERT_HOME}  &&    python setup.py install &&     apk del --purge .build-dependencies &&     rm -rf /var/cache/apk/*
 ---> Running in 2636be953132
+ curl -Lo elastalert.tar.gz https://github.com/Yelp/elastalert/archive/v0.2.4.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   123    0   123    0     0    115      0 --:--:--  0:00:01 --:--:--   115
100  188k    0  188k    0     0  67965      0 --:--:--  0:00:02 --:--:--  254k
+ tar -xzvf elastalert.tar.gz -C /opt/elastalert --strip-components 1
elastalert-0.2.4/.editorconfig
elastalert-0.2.4/.gitignore
elastalert-0.2.4/.pre-commit-config.yaml
elastalert-0.2.4/.secrets.baseline
elastalert-0.2.4/.travis.yml
elastalert-0.2.4/Dockerfile-test
elastalert-0.2.4/LICENSE
elastalert-0.2.4/Makefile
elastalert-0.2.4/README.md
elastalert-0.2.4/changelog.md
elastalert-0.2.4/config.yaml.example
elastalert-0.2.4/docker-compose.yml
elastalert-0.2.4/docs/
elastalert-0.2.4/docs/Makefile
elastalert-0.2.4/docs/source/
elastalert-0.2.4/docs/source/_static/
elastalert-0.2.4/docs/source/_static/.gitkeep
elastalert-0.2.4/docs/source/conf.py
elastalert-0.2.4/docs/source/elastalert.rst
elastalert-0.2.4/docs/source/elastalert_status.rst
elastalert-0.2.4/docs/source/index.rst
elastalert-0.2.4/docs/source/recipes/
elastalert-0.2.4/docs/source/recipes/adding_alerts.rst
elastalert-0.2.4/docs/source/recipes/adding_enhancements.rst
elastalert-0.2.4/docs/source/recipes/adding_loaders.rst
elastalert-0.2.4/docs/source/recipes/adding_rules.rst
elastalert-0.2.4/docs/source/recipes/signing_requests.rst
elastalert-0.2.4/docs/source/recipes/writing_filters.rst
elastalert-0.2.4/docs/source/ruletypes.rst
elastalert-0.2.4/docs/source/running_elastalert.rst
elastalert-0.2.4/elastalert/
elastalert-0.2.4/elastalert/__init__.py
elastalert-0.2.4/elastalert/alerts.py
elastalert-0.2.4/elastalert/auth.py
elastalert-0.2.4/elastalert/config.py
elastalert-0.2.4/elastalert/create_index.py
elastalert-0.2.4/elastalert/elastalert.py
elastalert-0.2.4/elastalert/enhancements.py
elastalert-0.2.4/elastalert/es_mappings/
elastalert-0.2.4/elastalert/es_mappings/5/
elastalert-0.2.4/elastalert/es_mappings/5/elastalert.json
elastalert-0.2.4/elastalert/es_mappings/5/elastalert_error.json
elastalert-0.2.4/elastalert/es_mappings/5/elastalert_status.json
elastalert-0.2.4/elastalert/es_mappings/5/past_elastalert.json
elastalert-0.2.4/elastalert/es_mappings/5/silence.json
elastalert-0.2.4/elastalert/es_mappings/6/
elastalert-0.2.4/elastalert/es_mappings/6/elastalert.json
elastalert-0.2.4/elastalert/es_mappings/6/elastalert_error.json
elastalert-0.2.4/elastalert/es_mappings/6/elastalert_status.json
elastalert-0.2.4/elastalert/es_mappings/6/past_elastalert.json
elastalert-0.2.4/elastalert/es_mappings/6/silence.json
elastalert-0.2.4/elastalert/kibana.py
elastalert-0.2.4/elastalert/kibana_discover.py
elastalert-0.2.4/elastalert/loaders.py
elastalert-0.2.4/elastalert/opsgenie.py
elastalert-0.2.4/elastalert/rule_from_kibana.py
elastalert-0.2.4/elastalert/ruletypes.py
elastalert-0.2.4/elastalert/schema.yaml
elastalert-0.2.4/elastalert/test_rule.py
elastalert-0.2.4/elastalert/util.py
elastalert-0.2.4/elastalert/zabbix.py
elastalert-0.2.4/example_rules/
elastalert-0.2.4/example_rules/example_cardinality.yaml
elastalert-0.2.4/example_rules/example_change.yaml
elastalert-0.2.4/example_rules/example_frequency.yaml
elastalert-0.2.4/example_rules/example_new_term.yaml
elastalert-0.2.4/example_rules/example_opsgenie_frequency.yaml
elastalert-0.2.4/example_rules/example_percentage_match.yaml
elastalert-0.2.4/example_rules/example_single_metric_agg.yaml
elastalert-0.2.4/example_rules/example_spike.yaml
elastalert-0.2.4/example_rules/example_spike_single_metric_agg.yaml
elastalert-0.2.4/example_rules/jira_acct.txt
elastalert-0.2.4/example_rules/ssh-repeat-offender.yaml
elastalert-0.2.4/example_rules/ssh.yaml
elastalert-0.2.4/pytest.ini
elastalert-0.2.4/requirements-dev.txt
elastalert-0.2.4/requirements.txt
elastalert-0.2.4/setup.cfg
elastalert-0.2.4/setup.py
elastalert-0.2.4/supervisord.conf.example
elastalert-0.2.4/tests/
elastalert-0.2.4/tests/__init__.py
elastalert-0.2.4/tests/alerts_test.py
elastalert-0.2.4/tests/auth_test.py
elastalert-0.2.4/tests/base_test.py
elastalert-0.2.4/tests/conftest.py
elastalert-0.2.4/tests/create_index_test.py
elastalert-0.2.4/tests/elasticsearch_test.py
elastalert-0.2.4/tests/kibana_discover_test.py
elastalert-0.2.4/tests/kibana_test.py
elastalert-0.2.4/tests/loaders_test.py
elastalert-0.2.4/tests/rules_test.py
elastalert-0.2.4/tests/util_test.py
elastalert-0.2.4/tox.ini
+ rm elastalert.tar.gz
+ cd /opt/elastalert
+ python setup.py install
running install
running bdist_egg
running egg_info
creating elastalert.egg-info
writing elastalert.egg-info/PKG-INFO
writing dependency_links to elastalert.egg-info/dependency_links.txt
writing entry points to elastalert.egg-info/entry_points.txt
writing requirements to elastalert.egg-info/requires.txt
writing top-level names to elastalert.egg-info/top_level.txt
writing manifest file 'elastalert.egg-info/SOURCES.txt'
reading manifest file 'elastalert.egg-info/SOURCES.txt'
writing manifest file 'elastalert.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_py
creating build
creating build/lib
creating build/lib/elastalert
copying elastalert/__init__.py -> build/lib/elastalert
copying elastalert/alerts.py -> build/lib/elastalert
copying elastalert/auth.py -> build/lib/elastalert
copying elastalert/config.py -> build/lib/elastalert
copying elastalert/create_index.py -> build/lib/elastalert
copying elastalert/elastalert.py -> build/lib/elastalert
copying elastalert/enhancements.py -> build/lib/elastalert
copying elastalert/kibana.py -> build/lib/elastalert
copying elastalert/kibana_discover.py -> build/lib/elastalert
copying elastalert/loaders.py -> build/lib/elastalert
copying elastalert/opsgenie.py -> build/lib/elastalert
copying elastalert/rule_from_kibana.py -> build/lib/elastalert
copying elastalert/ruletypes.py -> build/lib/elastalert
copying elastalert/test_rule.py -> build/lib/elastalert
copying elastalert/util.py -> build/lib/elastalert
copying elastalert/zabbix.py -> build/lib/elastalert
creating build/lib/tests
copying tests/__init__.py -> build/lib/tests
copying tests/alerts_test.py -> build/lib/tests
copying tests/auth_test.py -> build/lib/tests
copying tests/base_test.py -> build/lib/tests
copying tests/conftest.py -> build/lib/tests
copying tests/create_index_test.py -> build/lib/tests
copying tests/elasticsearch_test.py -> build/lib/tests
copying tests/kibana_discover_test.py -> build/lib/tests
copying tests/kibana_test.py -> build/lib/tests
copying tests/loaders_test.py -> build/lib/tests
copying tests/rules_test.py -> build/lib/tests
copying tests/util_test.py -> build/lib/tests
copying elastalert/schema.yaml -> build/lib/elastalert
creating build/lib/elastalert/es_mappings
creating build/lib/elastalert/es_mappings/5
copying elastalert/es_mappings/5/elastalert.json -> build/lib/elastalert/es_mappings/5
copying elastalert/es_mappings/5/elastalert_error.json -> build/lib/elastalert/es_mappings/5
copying elastalert/es_mappings/5/elastalert_status.json -> build/lib/elastalert/es_mappings/5
copying elastalert/es_mappings/5/past_elastalert.json -> build/lib/elastalert/es_mappings/5
copying elastalert/es_mappings/5/silence.json -> build/lib/elastalert/es_mappings/5
creating build/lib/elastalert/es_mappings/6
copying elastalert/es_mappings/6/elastalert.json -> build/lib/elastalert/es_mappings/6
copying elastalert/es_mappings/6/elastalert_error.json -> build/lib/elastalert/es_mappings/6
copying elastalert/es_mappings/6/elastalert_status.json -> build/lib/elastalert/es_mappings/6
copying elastalert/es_mappings/6/past_elastalert.json -> build/lib/elastalert/es_mappings/6
copying elastalert/es_mappings/6/silence.json -> build/lib/elastalert/es_mappings/6
creating build/bdist.linux-x86_64
creating build/bdist.linux-x86_64/egg
creating build/bdist.linux-x86_64/egg/elastalert
copying build/lib/elastalert/__init__.py -> build/bdist.linux-x86_64/egg/elastalert
copying build/lib/elastalert/alerts.py -> build/bdist.linux-x86_64/egg/elastalert
copying build/lib/elastalert/auth.py -> build/bdist.linux-x86_64/egg/elastalert
copying build/lib/elastalert/config.py -> build/bdist.linux-x86_64/egg/elastalert
copying build/lib/elastalert/create_index.py -> build/bdist.linux-x86_64/egg/elastalert
copying build/lib/elastalert/elastalert.py -> build/bdist.linux-x86_64/egg/elastalert
copying build/lib/elastalert/enhancements.py -> build/bdist.linux-x86_64/egg/elastalert
copying build/lib/elastalert/kibana.py -> build/bdist.linux-x86_64/egg/elastalert
copying build/lib/elastalert/kibana_discover.py -> build/bdist.linux-x86_64/egg/elastalert
copying build/lib/elastalert/loaders.py -> build/bdist.linux-x86_64/egg/elastalert
copying build/lib/elastalert/opsgenie.py -> build/bdist.linux-x86_64/egg/elastalert
copying build/lib/elastalert/rule_from_kibana.py -> build/bdist.linux-x86_64/egg/elastalert
copying build/lib/elastalert/ruletypes.py -> build/bdist.linux-x86_64/egg/elastalert
copying build/lib/elastalert/test_rule.py -> build/bdist.linux-x86_64/egg/elastalert
copying build/lib/elastalert/util.py -> build/bdist.linux-x86_64/egg/elastalert
copying build/lib/elastalert/zabbix.py -> build/bdist.linux-x86_64/egg/elastalert
copying build/lib/elastalert/schema.yaml -> build/bdist.linux-x86_64/egg/elastalert
creating build/bdist.linux-x86_64/egg/elastalert/es_mappings
creating build/bdist.linux-x86_64/egg/elastalert/es_mappings/5
copying build/lib/elastalert/es_mappings/5/elastalert.json -> build/bdist.linux-x86_64/egg/elastalert/es_mappings/5
copying build/lib/elastalert/es_mappings/5/elastalert_error.json -> build/bdist.linux-x86_64/egg/elastalert/es_mappings/5
copying build/lib/elastalert/es_mappings/5/elastalert_status.json -> build/bdist.linux-x86_64/egg/elastalert/es_mappings/5
copying build/lib/elastalert/es_mappings/5/past_elastalert.json -> build/bdist.linux-x86_64/egg/elastalert/es_mappings/5
copying build/lib/elastalert/es_mappings/5/silence.json -> build/bdist.linux-x86_64/egg/elastalert/es_mappings/5
creating build/bdist.linux-x86_64/egg/elastalert/es_mappings/6
copying build/lib/elastalert/es_mappings/6/elastalert.json -> build/bdist.linux-x86_64/egg/elastalert/es_mappings/6
copying build/lib/elastalert/es_mappings/6/elastalert_error.json -> build/bdist.linux-x86_64/egg/elastalert/es_mappings/6
copying build/lib/elastalert/es_mappings/6/elastalert_status.json -> build/bdist.linux-x86_64/egg/elastalert/es_mappings/6
copying build/lib/elastalert/es_mappings/6/past_elastalert.json -> build/bdist.linux-x86_64/egg/elastalert/es_mappings/6
copying build/lib/elastalert/es_mappings/6/silence.json -> build/bdist.linux-x86_64/egg/elastalert/es_mappings/6
creating build/bdist.linux-x86_64/egg/tests
copying build/lib/tests/__init__.py -> build/bdist.linux-x86_64/egg/tests
copying build/lib/tests/alerts_test.py -> build/bdist.linux-x86_64/egg/tests
copying build/lib/tests/auth_test.py -> build/bdist.linux-x86_64/egg/tests
copying build/lib/tests/base_test.py -> build/bdist.linux-x86_64/egg/tests
copying build/lib/tests/conftest.py -> build/bdist.linux-x86_64/egg/tests
copying build/lib/tests/create_index_test.py -> build/bdist.linux-x86_64/egg/tests
copying build/lib/tests/elasticsearch_test.py -> build/bdist.linux-x86_64/egg/tests
copying build/lib/tests/kibana_discover_test.py -> build/bdist.linux-x86_64/egg/tests
copying build/lib/tests/kibana_test.py -> build/bdist.linux-x86_64/egg/tests
copying build/lib/tests/loaders_test.py -> build/bdist.linux-x86_64/egg/tests
copying build/lib/tests/rules_test.py -> build/bdist.linux-x86_64/egg/tests
copying build/lib/tests/util_test.py -> build/bdist.linux-x86_64/egg/tests
byte-compiling build/bdist.linux-x86_64/egg/elastalert/__init__.py to __init__.cpython-36.pyc
byte-compiling build/bdist.linux-x86_64/egg/elastalert/alerts.py to alerts.cpython-36.pyc
byte-compiling build/bdist.linux-x86_64/egg/elastalert/auth.py to auth.cpython-36.pyc
byte-compiling build/bdist.linux-x86_64/egg/elastalert/config.py to config.cpython-36.pyc
byte-compiling build/bdist.linux-x86_64/egg/elastalert/create_index.py to create_index.cpython-36.pyc
byte-compiling build/bdist.linux-x86_64/egg/elastalert/elastalert.py to elastalert.cpython-36.pyc
byte-compiling build/bdist.linux-x86_64/egg/elastalert/enhancements.py to enhancements.cpython-36.pyc
byte-compiling build/bdist.linux-x86_64/egg/elastalert/kibana.py to kibana.cpython-36.pyc
byte-compiling build/bdist.linux-x86_64/egg/elastalert/kibana_discover.py to kibana_discover.cpython-36.pyc
byte-compiling build/bdist.linux-x86_64/egg/elastalert/loaders.py to loaders.cpython-36.pyc
byte-compiling build/bdist.linux-x86_64/egg/elastalert/opsgenie.py to opsgenie.cpython-36.pyc
byte-compiling build/bdist.linux-x86_64/egg/elastalert/rule_from_kibana.py to rule_from_kibana.cpython-36.pyc
byte-compiling build/bdist.linux-x86_64/egg/elastalert/ruletypes.py to ruletypes.cpython-36.pyc
byte-compiling build/bdist.linux-x86_64/egg/elastalert/test_rule.py to test_rule.cpython-36.pyc
byte-compiling build/bdist.linux-x86_64/egg/elastalert/util.py to util.cpython-36.pyc
byte-compiling build/bdist.linux-x86_64/egg/elastalert/zabbix.py to zabbix.cpython-36.pyc
byte-compiling build/bdist.linux-x86_64/egg/tests/__init__.py to __init__.cpython-36.pyc
byte-compiling build/bdist.linux-x86_64/egg/tests/alerts_test.py to alerts_test.cpython-36.pyc
byte-compiling build/bdist.linux-x86_64/egg/tests/auth_test.py to auth_test.cpython-36.pyc
byte-compiling build/bdist.linux-x86_64/egg/tests/base_test.py to base_test.cpython-36.pyc
byte-compiling build/bdist.linux-x86_64/egg/tests/conftest.py to conftest.cpython-36.pyc
byte-compiling build/bdist.linux-x86_64/egg/tests/create_index_test.py to create_index_test.cpython-36.pyc
byte-compiling build/bdist.linux-x86_64/egg/tests/elasticsearch_test.py to elasticsearch_test.cpython-36.pyc
byte-compiling build/bdist.linux-x86_64/egg/tests/kibana_discover_test.py to kibana_discover_test.cpython-36.pyc
byte-compiling build/bdist.linux-x86_64/egg/tests/kibana_test.py to kibana_test.cpython-36.pyc
byte-compiling build/bdist.linux-x86_64/egg/tests/loaders_test.py to loaders_test.cpython-36.pyc
byte-compiling build/bdist.linux-x86_64/egg/tests/rules_test.py to rules_test.cpython-36.pyc
byte-compiling build/bdist.linux-x86_64/egg/tests/util_test.py to util_test.cpython-36.pyc
creating build/bdist.linux-x86_64/egg/EGG-INFO
copying elastalert.egg-info/PKG-INFO -> build/bdist.linux-x86_64/egg/EGG-INFO
copying elastalert.egg-info/SOURCES.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying elastalert.egg-info/dependency_links.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying elastalert.egg-info/entry_points.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying elastalert.egg-info/requires.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying elastalert.egg-info/top_level.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
zip_safe flag not set; analyzing archive contents...
elastalert.__pycache__.create_index.cpython-36: module references __file__
elastalert.__pycache__.loaders.cpython-36: module references __file__
creating dist
creating 'dist/elastalert-0.2.4-py3.6.egg' and adding 'build/bdist.linux-x86_64/egg' to it
removing 'build/bdist.linux-x86_64/egg' (and everything under it)
Processing elastalert-0.2.4-py3.6.egg
creating /usr/local/lib/python3.6/site-packages/elastalert-0.2.4-py3.6.egg
Extracting elastalert-0.2.4-py3.6.egg to /usr/local/lib/python3.6/site-packages
Adding elastalert 0.2.4 to easy-install.pth file
Installing elastalert script to /usr/local/bin
Installing elastalert-create-index script to /usr/local/bin
Installing elastalert-rule-from-kibana script to /usr/local/bin
Installing elastalert-test-rule script to /usr/local/bin

Installed /usr/local/lib/python3.6/site-packages/elastalert-0.2.4-py3.6.egg
Processing dependencies for elastalert==0.2.4
Searching for cffi>=1.11.5
Reading https://mirrors.aliyun.com/pypi/simple/cffi/
Downloading https://mirrors.aliyun.com/pypi/packages/2e/92/87bb61538d7e60da8a7ec247dc048f7671afe17016cd0008b3b710012804/cffi-1.14.6.tar.gz#sha256=c9a875ce9d7fe32887784274dd533c57909b7b1dcadcc128a2ac21331a9765dd
Best match: cffi 1.14.6
Processing cffi-1.14.6.tar.gz
Writing /tmp/easy_install-h5gkyqwj/cffi-1.14.6/setup.cfg
Running cffi-1.14.6/setup.py -q bdist_egg --dist-dir /tmp/easy_install-h5gkyqwj/cffi-1.14.6/egg-dist-tmp-b02vxc3o
creating /usr/local/lib/python3.6/site-packages/cffi-1.14.6-py3.6-linux-x86_64.egg
Extracting cffi-1.14.6-py3.6-linux-x86_64.egg to /usr/local/lib/python3.6/site-packages
Adding cffi 1.14.6 to easy-install.pth file

Installed /usr/local/lib/python3.6/site-packages/cffi-1.14.6-py3.6-linux-x86_64.egg
Searching for python-magic>=0.4.15
Reading https://mirrors.aliyun.com/pypi/simple/python-magic/
Downloading https://mirrors.aliyun.com/pypi/packages/d3/99/c89223c6547df268596899334ee77b3051f606077317023617b1c43162fb/python_magic-0.4.24-py2.py3-none-any.whl#sha256=4fec8ee805fea30c07afccd1592c0f17977089895bdfaae5fec870a84e997626
Best match: python-magic 0.4.24
Processing python_magic-0.4.24-py2.py3-none-any.whl
Installing python_magic-0.4.24-py2.py3-none-any.whl to /usr/local/lib/python3.6/site-packages
Adding python-magic 0.4.24 to easy-install.pth file

Installed /usr/local/lib/python3.6/site-packages/python_magic-0.4.24-py3.6.egg
Searching for twilio<6.1,>=6.0.0
Reading https://mirrors.aliyun.com/pypi/simple/twilio/
Downloading https://mirrors.aliyun.com/pypi/packages/f6/20/c6d72e0f29030206342e4b5bef9f573bdb7c305615ea77c11c81f5c0196d/twilio-6.0.0.tar.gz#sha256=2c284ed978b992b601914177746ba8afe29d9099fd6b4efaa1628e32951391d5
Best match: twilio 6.0.0
Processing twilio-6.0.0.tar.gz
Writing /tmp/easy_install-0vutbhz6/twilio-6.0.0/setup.cfg
Running twilio-6.0.0/setup.py -q bdist_egg --dist-dir /tmp/easy_install-0vutbhz6/twilio-6.0.0/egg-dist-tmp-otvt1f9g
zip_safe flag not set; analyzing archive contents...
twilio.http.__pycache__.__init__.cpython-36: module references __file__
creating /usr/local/lib/python3.6/site-packages/twilio-6.0.0-py3.6.egg
Extracting twilio-6.0.0-py3.6.egg to /usr/local/lib/python3.6/site-packages
Adding twilio 6.0.0 to easy-install.pth file

Installed /usr/local/lib/python3.6/site-packages/twilio-6.0.0-py3.6.egg
Searching for texttable>=0.8.8
Reading https://mirrors.aliyun.com/pypi/simple/texttable/
Downloading https://mirrors.aliyun.com/pypi/packages/75/23/8170868d04b153b1b9ed1bb84348212bb4a08f31b292ef9d7f6ea648fd49/texttable-1.6.4-py2.py3-none-any.whl#sha256=dd2b0eaebb2a9e167d1cefedab4700e5dcbdb076114eed30b58b97ed6b37d6f2
Best match: texttable 1.6.4
Processing texttable-1.6.4-py2.py3-none-any.whl
Installing texttable-1.6.4-py2.py3-none-any.whl to /usr/local/lib/python3.6/site-packages
Adding texttable 1.6.4 to easy-install.pth file

Installed /usr/local/lib/python3.6/site-packages/texttable-1.6.4-py3.6.egg
Searching for stomp.py>=4.1.17
Reading https://mirrors.aliyun.com/pypi/simple/stomp.py/
Couldn't find index page for 'stomp.py' (maybe misspelled?)
Scanning index of all packages (this may take a while)
Reading https://mirrors.aliyun.com/pypi/simple/

改成 python3-dev 可以了，但是另外一个包又下载失败了，我看你上面的输出最后也是下载失败
#11 16.41 Searching for stomp.py>=4.1.17
#11 16.41 Reading https://mirrors.aliyun.com/pypi/simple/stomp.py/
#11 16.61 Scanning index of all packages (this may take a while)
#11 16.61 Couldn't find index page for 'stomp.py' (maybe misspelled?)
#11 16.61 Reading https://mirrors.aliyun.com/pypi/simple/
#11 55.05 No local packages or working download links found for stomp.py>=4.1.17
#11 55.09 error: Could not find suitable distribution for Requirement.parse('stomp.py>=4.1.17')

这应该是 pip 阿里云加速器的事 https://pypi.org/project/stomp.py/#history

我直接 install elastalert 了，成功了，另外，docker-entrypoint.sh 里面的变量名和 Dockerfile 里的不一样，比如：RULES_FOLDER（docker-entrypoint.sh）--> ELASTALERT_RULES_DIRECTORY（Dockerfile ）

你是认真的么？ https://github.com/anjia0532/elastalert-docker/blob/master/docker-entrypoint.sh 你能搜到 RULES_FOLDER 么？

另外不太明白你自己构建镜像的出发点在哪，如果要自己写plugin，可以挂载卷

好吧，我看错了，看的是你脚本里引用的地址，嗯，我只是想看看构建过程，我后面直接用你的镜像试试 ，多谢回复
https://github.com/sc250024/docker-elastalert/blob/master/src/docker-entrypoint.sh


text:
Code of Conduct

The project is currently missing the Code of Conduct file which is important for open source project
So can I go for it @ankingcodes

@Tejas1510 - As this is not a big project we are not looking to add a Code of Conduct file specifically for the project. Students have already read code of conduct from NWOC github repo.

Sure @ankingcodes

repo: ankingcodes/codemon


text:
🛑 Pedtalant is down

In 70d1acc, Pedtalant (https://педталант.рф) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Pedtalant is back up in 8e5b253 after 12 minutes.

repo: ano-pedproject/repo


text:
🛑 Rainbow is down

In 020e4a5, Rainbow (https://радуга-талантов.рф) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Rainbow is back up in ca5fe1b after 11 minutes.


text:
Staking page has a crazy long scroll to blank grey

This was fixed on #1337

authors: ChrisHoltDesign pedrorezende

repo: anoma/namada-interface


text:
Update IP address for HashBamboo.toml

Description
If this is an UPDATE for a previous genesis validator
Checks are made against your net_address. If this has changed since the previous testnet, make sure you provide links of previous prs merged from your previous git username.
Thanks in advance!
Checklist before merging to draft

[ ] Only one toml is added in this PR
[ ] The file being added is indeed a .toml file
[ ] The toml being added is to the correct folder, and only to the correct folder
[ ] The eth_hot_key and eth_cold_key are present

Please review this PR. It should not edit anything in the namada-public-testnet-12 folder. Just keep the edit to the namada-public-testnet-13 folder

authors: bengtlofgren wzzYtu

repo: anoma/namada-testnets


text:
Image with noise and slow

hello
hello , first congratulate you for your work done in the library of ros for drone tello, I'm doing a project with the drone tello, but when capturing the image comes out distorted (green pixel noise) and with delay, maybe you could help me How could I improve this inconvenience since I want to perform image processing in ros with the video obtained from the drone. For your help I give you my thanks

When I've seen this symptom in the past, it was likely due to poor wifi signal. Move the drone closer to the wifi antenna, get a larger antenna, and/or try a wifi repeater. Good luck.


text:
Exit Script?

Awesome project.
If the script is prompting using readline-sync, how does one exist the script? Ctrl+C doesn't seem to be working.
Thanks!

I am running into this issue now with iojs 1.5.1 on Mac OSX. I do have some packages that listen to SIGINT, such as mocha, but that should not interfere. Anything else that could interfere? Or any other way to debug this?

For me, the package that was causing the issue was Phantom. Hope that helps anyone else who gets stuck.

Hi Globegitter, Thank you for your post.
readlineSync throw an error when it caught signal.
And, I added more informations to the error object in v0.7.9.
var readlineSync = require('readline-sync');

process.on('SIGINT', function() {
  console.log('\nI caught SIGINT signal.');
  process.exit();
});

process.on('SIGTERM', function() {
  console.log('\nI caught SIGTERM signal.');
  process.exit();
});

try {
  console.log('\nANSWER :' + readlineSync.question('Input text :'));
} catch (e) {
  if (e.signal === 'SIGINT' || e.signal === 'SIGTERM' ||
      // STATUS_CONTROL_C_EXIT: 0xC000013A
      e.exitCode === -1073741510 || e.exitCode === 3221225786) {
    console.log('\nreadlineSync caught signal.');
    setTimeout(function() { process.kill(process.pid, 'SIGINT'); }, 0);
  } else {
    console.error(e);
    process.exit(1);
  }
}

Then, Node v10- on *nix doesn't seem to get SIGINT and SIGTERM when it's reading TTY. SIGTSTP (^Z) works.
Node v11+ on *nix using shell, SIGINT works without error.
But, some shells in raw mode might send no-signal, it get ^C as code, not signal.
The both versions and shell and non-shell on Windows, SIGINT works.
I think that it's difficult because it comes from different platforms.
The error handling might help you, but it's not complete. Someday, Node might solve this problem.
Now, better way I think is giving the choice to cancel to user without ^C. e.g. input the empty string to cancel.

I just discovered that the signal is swallowed on Mac OS X if the password mode is used:
ask = require 'readline-sync'
ask.question 'password?', hideEchoBack: true

the above can't be canceled with Ctrl+C

Hi monsterkodi, thank you for your post.
That occurs on some versions of Node and external program. When your Node doesn't support raw mode TTY for hideEchoBack, readlineSync tries to use sehll. Those might ignore the signals regardless of readlineSync. e.g. in some cases, shell scripts also ignore the signals when reading line.
Give a way to cancel to user without the signals, if it's needed.

authors: Globegitter anseki gkoberger monsterkodi

repo: anseki/readline-sync


text:
packit: Use alias for Fedora targets

Use the 'fedora-stable' alias instead of specifying targets by Fedora
version. This solves Packit errors due to Fedora 30 reaching EOL.
Signed-off-by: Hunor Csomortáni csomh@redhat.com

whoops, I missed this PR and already changed packit.yaml to do fedora-all in another PR
thanks for the contribution though!

authors: TomasTomecek csomh

repo: ansible-community/ansible-bender


text:
Added version download to the approval page

No-Issue
Yet.
Added download icon to version with download link

@rochacbruno This was a temporary fix, and we will have different solution in the long run. Do you still need this PR or can I close it?

It seems this PR is not rebased on master, because master already checks settings.GALAXY_SIGNATURE_UPLOAD_ENABLED for the Upload Signature button https://github.com/ansible/ansible-hub-ui/blob/master/src/containers/certification-dashboard/certification-dashboard.tsx#L388 ... which seems like the right setting to check.
@brumik @rochacbruno is there anything else in this PR that is needed or can it be closed?

@rochacbruno I am closing this for lack of confirmation that you still need it.
@awcrosby This was a temporary fix for the demo for Bruno, so I don't think it is needed anymore.

authors: awcrosby brumik

repo: ansible/ansible-hub-ui


text:
This adds functionality to create, edit and delete an inventory

I've made some changes to the structure of the flow of the inventory as a POC.  For instance I modeled the Inventory file structure a more like Controller does, and I modeled the url structure to mimic Controller.  I feel that mimicing the file structure would be beneficial(if we stay in our own repo) for developer quality of life for UI devs on other teams.  I believe that modeling the url structure like controller is a necessity for users.
AAP-7258

@lgalis rebased

repo: ansible/eda-server


text:
Post tech-review tasks

[x] Migrate to github.com/ansys
[x] Change the URLs from github.com/ansys-internal to github.com/ansys
[x] Set up branch and tag protection
[x] Generate PyPI token, right before going public
[x] Transfer visibility to public
[x] Do a first release to PyPI
[x] After going public, allowing codecov.io GH app  to access this repository and store codecov token as secret
[x] Add this project to https://github.com/ansys-internal/pyansys-dev
[ ] Add project to metapackage within tools section

Originally posted by @RobPasMue in https://github.com/ansys-internal/ansys-tools-local-product-launcher/issues/130#issuecomment-1930004598

Only missing metapackage - we'll do that later


text:
REFACTOR: Dotnet coreclr loading

The changes allow one to leverage a dotnet installation at system level.
This is something that we should encourage as using dotnetcore2 prevents us from providing a conda recipe and also because dotnetcore2 requires openssl1.1 to be installed. It can't work with newer versions.

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

Project coverage is 82.55%. Comparing base (6ac5005) to head (8bdbf8e).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #916      +/-   ##
==========================================
+ Coverage   82.48%   82.55%   +0.07%
==========================================
  Files         160      160
  Lines       20987    21001      +14
==========================================
+ Hits        17311    17338      +27
+ Misses       3676     3663      -13

The pyaedt tests failed on linux when running with pyaedt-ci-6. I will conduct some changes on the VM to ensure it behaves correctly following our warnings.

authors: SMoraisAnsys codecov-commenter

repo: ansys/pyedb


text:
头部视觉问题

因为icon和按钮没有背景色导致某些宽度后面的背景图会“遮盖”

感觉移动端应该单独出一个简单一点的图，我找下设计师。


text:
[Advise]匹配算法可以考虑分为个多粒度依次匹配

作者您好，今天第一次玩到汉兜，感觉十分有趣，但在尝试时发现了一些可以优化的地方，望采纳。

这是本人今天的尝试，答案为“首当其冲”，我在第二次尝试时使用了“参差不齐”，“其”和“齐”是同音不同字，但是“齐”并没有作为一个整体匹配到“其”上，这对于我的判断产生了一定的影响。
由此我斗胆推断一下，这个匹配算法是将声母、韵母、音调三个部分拆开来分别进行匹配的。
改进的方法为采用多粒度匹配，即首先将声母、韵母、音调三者作为整体匹配，之后将声母拆分出去单独匹配，韵母和音调作为整体匹配，最后再将韵母和音调也拆分出去，三者都单独匹配。
不过以上改动实现起来可能较为复杂，然而实现之后可以在一定程度上降低猜测难度，对于我这样没文化的人是会友好一些啦。
希望作者大佬可以看到，我也打算fork下来先自己尝试实现。

哈哈，刚开始玩汉兜的时候我也以为有这个逻辑。我也尝试实现下~

repo: antfu/handle


text:
please，how to set keyframes in theme about unocss.config.js ?

I want to set an custom's animation in theme,but I don't how to do?
https://unocss.antfu.me/?html=DwEwlgbgBAxgNgQwM5ILwHIAuBTAHpgWhmwDscAndAPiigChbgAHKAIwHMD3yFxTMMmAPYFyUAGbkhAWwKs4AV2wEALAAY16WIhQYkmMDADWATyjCmBTVQSsYIbOPYALMACsjwAPRMqDKMzayGjoAO4EAOxqTLhQCCRg0gg4BKFg7Oxw2FocGFJIyurWaRlZ3r7%2Bgc4EAIwAzGoQzmxC5A7ktTZ25TT03uAQVEA&config=JYWwDg9gTgLgBAbzgEwKYDNgDtUGEJaYDmcAvnOlBCHAOQCuWEAxgM6u0BQnqAHpLBQYAhvQA28NJhz5CwIgAoEnOHBgALVCFQAuRCtVw%2BMVFmR7lhwwGtUAT0rDtrCwauqA7vKJjd%2B9%2B60AAwApAA0cACMQaG0FmpQwlis6NAgerRUMMImCgC0AMxoRACUtGRhbgF0AKyx8TCJyalQ6XRZOagKBUHFZRVVVqSDAwFJoDnABK7VcF5EPn6084tRrEbCrKh52HkQ9PDY0sAmtJUBw0MGl3CcpCVAA&options=N4IgzgLgTglgxhEAuAZgQwDZgKYF8g

something like this https://imgur.com/MLAgyLG?

还是希望，能支持像tailwind或windicss的keyframes的语法，这样，以便减少我们转换学习的成本，谢谢

@729902288 added support for windicss and tailwind object format: https://imgur.com/sNJiZUs

这个动效，好像还是出不来？
https://unocss.antfu.me/?html=DwEwlgbgBAxgNgQwM5ILwHIAuBTAHpgWhmwDscAndAPiigChbgAHKAIwHMD3yFxTMMmAPYFyUAGbkhAWwKs4AV2wEALAAY16KEyFp0STGBgBrAJ5RhTApqhUErGCGzj2ACzAArY8AD0TKgxQzLCIKBgA7gQA7GpMuFAIJGDSCDgE4WDs7HDYWhwYUkjK6jZUGVk5vv6Bwa4EAIwAzGoQrmxC5E7kDXYOVTT0vuAQVEA&config=JYWwDg9gTgLgBAbzgEwKYDNgDtUGEJaYDmcAvnOlBCHAOQCuWEAxgM6u0BQnqAHpLBQYAhvQA28NJhz5CwIgAoEnOHBgALVCFQAuRCtVxhWUMJjACe5YcMBrVAE9Kw7aysGbqgO7yiY3fqenrQADACkADQAjCHhtFZqUMas6NAgerRUMGaoCgC0AMxoRACUtGQRHkF0AKxxCTBJWClpGVk5CgUhxWUVVTakEdVw-X1ByPRJ5gRugdU%2BRH4BtAUclUGkVZuq2yOkJUA&options=N4IgzgLgTglgxhEAuAZgQwDZgKYF8g

@userquin  谢谢您，改为string类型，就可以了。但希望能支持object类型就更好了。

请问这个有文档看怎么配置吗？animation-iteration-count 不知道怎么配置

repo: antfu/unocss


text:
Fixed lifecycle issue when using the plugin in a single file componen…

Fixed issue: Error in created hook: "TypeError: Cannot read property 'subscribe' of undefined"

@anthonygore Hi, I found a lifecycle issue when running https://codesandbox.io/s/vjo3xlpyny and fixed it, please confirm it.

Sorry for the delay.
Can you explain why this.$store.subscribe is undefined in the created hook? If the Vuex plugin is already installed, it should be available in the created hook since that's when reactive data and observation has been setup. What made you change to the mounted hook and why does that work? I don't get it!

Okay I get it now.
So the issue in your code sandbox is that the VuexUndoRedo plugin was being installed in your store file. I know it's conufsing, but this plugin is actually a Vue plugin, not a Vuex plugin!
I've gotten your code working by simply installing the plugin after the Vuex store gets created. It works fine after that.
https://codesandbox.io/s/qqrj2v9xv6
I'll close this PR and I think I'm going to instead throw an error if the user attempt to install the plugin before their Vuex store is created.
Thanks for taking the time to provide this PR.

authors: anthonygore szriafan

repo: anthonygore/vuex-undo-redo


text:
Avoid potential null dereference looking up flags.

Trivial potential null pointer dereference.
-Mark

Good catch, thanks.

authors: antirez beanz

repo: antirez/disque


text:
common: add register containing git revision

This will help us identify gateware version uploaded to the device.

This PR also adds a helper script that can be used to check git revision stored in the register.

We moved the BuildInfo CSR at the end of CSR list (we're limited to 32 CSR's). This way it's address should always be the same.

repo: antmicro/litex-rowhammer-tester


text:
Update README.md

Update path to eos-s3 toolchain release

This is probably not relevant any more, closing. Thanks for the help though!

authors: cibomahto mgielda

repo: antmicro/symbiflow-examples


text:
slot attributes are deprecated

Describe the bug
A clear and concise description of what the bug is.
Steps to reproduce
Following instructions on https://github.com/antoine92190/vue-advanced-chat to implement a the named slot message-avatar_{{MESSAGE_ID}}.  Specifically, use code below.
Can you provide an update-to-date example of how to implement a named v-slot for message-avatar_{{MESSAGE_ID}} or any other slot that is dynamic?
From example at https://github.com/antoine92190/vue-advanced-chat
`

System message: {{ message.content }}

Normal message: {{ message.content }}

`
Expected behavior
Avatar should render component inside of v-slot.
Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information)

OS: Windows
Browser: Chrome
Package version: n/a

Additional context

Which version of the library are you using?

Hello @antoine92190
Thanks for responding.  I am using 2.0.6.

Sorry for the late response. Here is a working example:
<div v-for="message in messages" :slot="'message-avatar_' + message._id" :key="message._id">
    New avatar
</div>


text:
fix: Add missing popd to terraform_docs code that was introduced in v1.95.0

Put an x into the box if that apply:

[ ] This PR introduces breaking change.
[x] This PR fixes a bug.
[ ] This PR adds new functionality.
[ ] This PR enhances existing functionality.

Description of your changes
A bug in the terraform-docs hook was introduced in #717.  In that PR, a continue statement was added that is not preceded by a popd command.  The bug is only triggered when the hook is processing multiple files where one (or more) of the files does not contain the terraform-docs marker statements.  The hook fails to process the remaining files because the working directory is not reset to the root of the repository.  I ran into this bug on version 1.96.0 of the hooks and pre-commit version 3.8.0.

How can we test changes
Here is a script to reproduce the issue.  It creates a repository containing multiple modules.  The pre-commit run -a command will print an error similar to ~/.cache/pre-commit/reporqzucglw/hooks/terraform_docs.sh: line 178: pushd: modules/c: No such file or directory and module C's README won't be updated by terraform-docs.

cat <<EOF> .pre-commit-config.yaml
---
repos:
  - repo: https://github.com/antonbabenko/pre-commit-terraform
    rev: v1.96.0
    hooks:
      - id: terraform_docs
        files: '.*'
        verbose: true
        types_or:
          - markdown
          - terraform
EOF

git init
pre-commit install --install-hooks
mkdir -p modules/{a,b,c}

cat <<EOF> modules/a/README.md
# I'm module A

<!-- BEGIN_TF_DOCS -->
<!-- END_TF_DOCS -->

EOF

cat <<EOF> modules/b/README.md
# I'm module B

I break things

EOF

cat <<EOF> modules/c/README.md
# I'm module C

<!-- BEGIN_TF_DOCS -->
<!-- END_TF_DOCS -->

EOF

git add .
pre-commit run -a

@MaxymVlasov Would you please add second pair of eyes?

This PR is included in version 1.96.1 :tada:

authors: antonbabenko ryan-at-ld yermulnik

repo: antonbabenko/pre-commit-terraform


text:
how to disable random subdomain.

The subdomain sub.domain.com is unavailable. Assigning a random subdomain.
if unavailable, can stop it?

Use --force-requested-subdomains to force subdomains to be chosen.
Please read the documentation before opening an issue, thanks!

authors: antoniomika dangtrungluong

repo: antoniomika/sish


text:
MuiTable

Table

@manikandanmohan10 Please review and merge the code to main branch

done


text:
Update Cluster Service CIDRs in CI

Describe the problem/challenge you have
The service IP in CI cluster coincidentally matches a server IP within the corporate network, allowing the service IP to remain accessible even after deleting the service. This situation contradicts the expected behavior of the test.
Describe the solution you'd like

Update service CIDRs parameter in CAPV description file
Update the Vagrant file for static testbeds

@XinShuYang I don't know if this a good first issue. It looks like a bit of knowledge is required about the internal testbed and internal network?

Yes, this shouldn't be a good first issue. Only few people can access the testbeds.

authors: XinShuYang antoninbas tnqn

repo: antrea-io/antrea


text:
Fix trying to destroy a non-existent ipset

Ipset outputs "The set with the given name does not exist" to its stderr. This error is returned in the output, not in the err.

Thanks @edwardbadboy for finding this.

A suggestion to the title: Fix error handling for non-existent ipset

A suggestion to the title: Fix error handling for non-existent ipset

Done

/skip-all

authors: hongliangl tnqn


text:
Change cert and config location in manifest

Description
Both Webhook and API Server are using same TLS cert generated by cert manager. Avoid generating two volumes and different mount path for them
Chanages
Move config to /etc/nephe dir and also update API Server and Webhook to use cert from same location.

/nephe-test-e2e-kind, /nephe-test-e2e-upgrade

/nephe-test-e2e-kind, /nephe-test-e2e-upgrade

/nephe-test-e2e-kind /nephe-test-e2e-upgrade

/nephe-test-e2e-kind /nephe-test-e2e-upgrade

/nephe-test-e2e-kind /nephe-test-e2e-upgrade

/nephe-test-e2e-kind

/nephe-test-e2e-upgrade

/nephe-test-e2e-upgrade

nephe-test-e2e-agentless-upgrade

/nephe-test-e2e-aws-upgrade /nephe-test-e2e-azure-upgrade

/nephe-test-e2e-aws-upgrade /nephe-test-e2e-azure-upgrade

/nephe-test-e2e-aws-upgrade

/nephe-test-e2e-aws-upgrade

/nephe-test-e2e-azure-upgrade

/nephe-test-e2e-azure-upgrade

repo: antrea-io/nephe


text:
feat: add shape factory & shape

Checklist

[ ] npm test passes
[ ] tests and/or benchmarks are included
[ ] geometry 调用 element + shape 的逻辑

Description of change

Pull Request Test Coverage Report for Build 892926704

3 of 228 (1.32%)  changed or added relevant lines in 6 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-14.6%) to 53.063%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/types/geometry.ts
0
1
0.0%

src/visual/coordinate/index.ts
0
1
0.0%

src/util/coordinate.ts
0
3
0.0%

src/geometry/factory.ts
0
52
0.0%

src/util/path.ts
0
168
0.0%

Totals

Change from base Build 892293122:
-14.6%

Covered Lines:
639

Relevant Lines:
1147

💛  - Coveralls

shape 这一块的核心改动是什么，科普下 @hustcc

authors: coveralls hustcc visiky


text:
updateitem 只想更新label 但是图片也重绘了  导致图片会出现闪烁现象

demo如下：点击图片节点 只希望更新label 但是图片闪烁了一下  如果页面上有很多节点的话 闪烁很严重
https://codepen.io/yiliayouyou/pen/ExKwZGo
浏览器环境：chrome 版本 85.0.4183.83（正式版本） （64 位）
之前浏览器为chrome 80.x的时候不会有这么严重的闪烁问题
有没有办法只更新label样式  图片不会重新渲染

这样可以单独更新一个图形：
  graph.on('node:click', evt => {
    const node = evt.item;
    const group = node.getContainer();
    const label = group.find(e => e.get('name') === 'text-shape');
    label.attr('fill', 'red');
  });

authors: Yanyan-Wang Yiliayouyou


text:
drag-canvas 与 zoom-canvas 行为冲突

问题描述
const defaultMode = [
    {
        type:'drag-canvas',
        enableOptimize: true
    },
    {
        type:'zoom-canvas',
        enableOptimize: true
    },
   // ...
]

drag-canvas 与 zoom-canvas 行为冲突，导致 drag-canvas 的 性能优化失效
重现链接
无
重现步骤
复现步骤：
1.内置行为 drag-canvas 与 zoom-canvas 同时使用 enableOptimize
2.构造 nodes 和 edges
3.【食指】按住鼠标【左键】开始拖动画布，观察 连线 和 非 keyShape 的 图形被隐藏
4.在拖动过程中，用【中指】滚动鼠标 【滚轮】出发 画布缩放，缩放结束后发现【被隐藏的连线 和 非 keyShape 图形】重新渲染出来了
预期行为
希望 在 复现步骤4 中， 缩放结束后【被隐藏的连线 和 非 keyShape 图形】仍然保持隐藏状态，直到 用户松开左键 才展示出来
平台

操作系统: [macOS, Windows, Linux, React Native ...]
网页浏览器: [Google Chrome, Safari, Firefox]
G6 版本: [4.7.16]

屏幕截图或视频（可选）
No response
补充说明（可选）
No response

两个交互之间因为相互解耦，所以互相不会感知对方的状态。隐藏图形和显示图形的逻辑也一般会在各自交互开始和结束的时候被执行。所以好像没有很好的解法，这个操作也比较小众。看下社区同学有没有好的解法的建议

authors: Yanyan-Wang ZENKI-CS


text:
feat: add necessary types

feat: add necessary types

@YiSiWang 文件和目录命名，这里是全部小写的。graphlib 建议也用小写，避免在 mac 上文件系统不区分大小写的问题。

authors: Yanyan-Wang hustcc


text:
百度地图商用授权问题

问题描述
有使用百度地图底图，收到百度地图电话，需要购买商用额度的吗？
重现链接
No response
重现步骤
No response
预期行为
No response
平台

操作系统: [macOS, Windows, Linux, React Native ...]
网页浏览器: [Google Chrome, Safari, Firefox]

屏幕截图或视频（可选）
No response
补充说明（可选）
No response

看百度地图开发者官网了解


text:
fix: 修复在维值缺失场景下导出数据占位符未解析的问题

👀 PR includes

🐛 Bugfix

[x] Solve the issue and close #0

📝 Description

背景见: https://github.com/antvis/S2/pull/2829/files
这个是 1.x 已经修复过的, 当时同步过来由于 2.x 整体导出链路变了, 忘记修改了.
🖼 Screenshot

Before
After

❌
✅

🔗 Related issue link

🔍 Self-Check before the merge

[ ] Add or update relevant docs.
[ ] Add or update relevant demos.
[ ] Add or update test case.
[ ] Add or update relevant TypeScript definitions.

:tada: This PR is included in version @antv/s2-v2.1.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


text:
graph.batchUpdate能合并node.setData方法吗

问题描述
代码
graph.batchUpdate(() => {
if (selectedList.length === 0) {
nodes.forEach(el => {
const node = graph?.getNodes().find(e => e.id === el.id)
if (node?.data?.selected) {
node?.setData({ ...el.data, selected: false })
}
})
} else {
selectedList.forEach(el => {
const node = graph?.getNodes().find(e => e.id === el.id)
if (!node?.data?.selected) {
node.setData({ ...el.data, selected: true })
}
})
}
})
目前使用graph.batchUpdate并不能将node.setData方法合并；我并不清楚这是x6本身不支持还是一个bug
重现链接
无
重现步骤
// 合并代码
graph.batchUpdate(() => {
if (selectedList.length === 0) {
nodes.forEach(el => {
const node = graph?.getNodes().find(e => e.id === el.id)
if (node?.data?.selected) {
node?.setData({ ...el.data, selected: false })
}
})
} else {
selectedList.forEach(el => {
const node = graph?.getNodes().find(e => e.id === el.id)
if (!node?.data?.selected) {
node.setData({ ...el.data, selected: true })
}
})
}
})
// 撤销
graph.undo()
// 查看nodes的data属性是否全部都撤回了
graph.getNodes()
预期行为
我希望是会合并成一个操作，但是并没有
平台

操作系统: [macOS, Windows, Linux, React Native ...]
网页浏览器: [Google Chrome, Safari, Firefox ...]
X6 版本: [2.11.1 ...]

屏幕截图或视频（可选）
No response
补充说明（可选）
No response

搞一个demo看看


text:
Feat: Design of "Connect with a Reader" and "Send Now" buttons is not suitable in dark mode

Describe the feature
@anuragverma108 @RitiChandak
I saw your project, it's really superb! Although I found an issue that "Connect with a Reader" and "Send now" buttons are not looking good according to the dark mode.
Add ScreenShots

I want to work on this issue to enhance the design of these buttons so that they will be suitable according to dark mode.
Please add labels on this issue and then assign it to me.
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@RitiChandak sure


text:
Add books in the E-book section

IT would be great if we could add more books in the e-book section for users to read for free which improves the user experience and overall user interaction

@sanjay-kv  please assign this issue to me ,I would love to work on this issue


text:
Update index.html

Related Issue
Read More Hover effect
Fixes: #1140
Description
I made the following changes:

Increased the glowing effect for the "Read more" text on hover by adjusting the text-shadow size.
Slowed down the transition timing for letter spacing to create a smoother effect.
Added appropriate CSS classes and hover effects for both light and dark modes.

This pull request addresses issue #1140 .
Type of PR

[ ] Bug fix
[x] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
N/A

Checklist:

[x] I have made this change from my own.
[ ] I have taken help from some online resources.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[ ] I have made corresponding changes to the documentation.
[ ] My changes generate no new warnings.
[x] I have tested the changes thoroughly before submitting this pull request.
[ ] I have provided relevant issue numbers and screenshots after making the changes.

You have not been assigned to work on this issue. This violates our open source code of conduct.
Please focus on the issue you have been assigned to.


text:
Adding a separate page for AI book recommendation generator which would give book recommendations based on the questions asked (Issue #4688)

Related Issue
Adding a separate page for AI book recommendation generator which would give book recommendations based on the questions asked.
Fixes:  #4688
Description
Adding a separate page for AI book recommendation generator which would give book recommendations based on the questions asked.

Type of PR

[ ] Bug fix
[x] Feature enhancement
[ ] Documentation update
[x] Other (specify): _______________

Screenshots / videos (if applicable)
https://github.com/user-attachments/assets/2fdd3402-53f1-4de4-aaf1-b0115e6d4709
Checklist:

[x] I have made this change from my own.
[x] I have taken help from some online resources.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers and screenshots after making the changes.

good idea but on footer we have recommend option once go through that option and add this feature there without disturbing existing feature @shriyadindi

authors: sailaja-adapa shriyadindi


text:
img = cv2.resize(img, (ConfigData.SHAPE_MIDDLE[1], ConfigData.SHAPE_MIDDLE[0]), interpolation=cv2.INTER_AREA) AttributeError: type object 'ConfigData' has no attribute 'SHAPE_MIDDLE'

img = cv2.resize(img, (ConfigData.SHAPE_MIDDLE[1], ConfigData.SHAPE_MIDDLE[0]), interpolation=cv2.INTER_AREA)

AttributeError: type object 'ConfigData' has no attribute 'SHAPE_MIDDLE'

@assafkeller
Sorry, and thank You.
I have just released an new version "ver1.0.1".
I think this is a problem that occurred because the program that was being modified was moved to the main branch.
Please try the current version.

@assafkeller Sorry, and thank You. I have just released an new version "ver1.0.1". I think this is a problem that occurred because the program that was being modified was moved to the main branch. Please try the current version.

use "ver1.0.1"，still reporting the error “AttributeError: type object 'ConfigData' has no attribute 'SHAPE_MIDDLE'“

maybe because it needs to be run under Linux

authors: assafkeller chillcoding-plz jun20061588 mucunwuxian

repo: any-tech/SPADE-fast


text:
Usage of allOf generates an incomplete type

What are the steps to reproduce this issue?

Clone your repo
yarn install and yarn build on the root
cd samples/basic/ && yarn install and modify the petstore.yaml

Generate the model using yarn example

What happens?
The generated models look like this:
petBase.ts
/*
 * Generated by orval v5.5.3 🍺
 * Do not edit manually.
 * Swagger Petstore
 * OpenAPI spec version: 1.0.0
 */

export interface PetBase {
  id: number;
  name: string;
  tag?: string;
}

pet.ts
/*
 * Generated by orval v5.5.3 🍺
 * Do not edit manually.
 * Swagger Petstore
 * OpenAPI spec version: 1.0.0
 */
import type { PetBase } from './petBase';

export type Pet = PetBase;

What were you expecting to happen?
I would expect Pet to contain all fields of PetBase and the new color property like this:
pet.ts
/*
 * Generated by orval v5.5.3 🍺
 * Do not edit manually.
 * Swagger Petstore
 * OpenAPI spec version: 1.0.0
 */
import type { PetBase } from './petBase';

export interface Pet extends PetBase {
  color: string;
}
// OR
export type Pet = PetBase & { color: string; };

Hello @jogeli to be honest I don't know if that a good way to write the allOf so I don't handle it like that. The way it's handle is like in the doc here.

Hey @anymaniax, ok I understood my mistake, it was a syntax issue. I should specify it like:
    Pet:
      allOf:
        - $ref: '#/components/schemas/PetBase'
        - type: object <-- HERE
          required:
            - id
            - name
          properties:
            color:
              type: string

TBH, I would like to migrate from openapi generator. In openapi, the generation was working even with the wrong syntax:
export interface Pet {
  id: number;
  name: string;
  tag?: string;
  color: string;
}

I'll fix my specs, thank you ;)

If you have other problems don't hesitate to open another issue 😀. Improvement ideas are also welcome 🚀

Hi @anymaniax, I encountered this issue as well, and I'm not sure whether to open another issue or not since it's pretty much the same case.
I'm using https://github.com/domaindrivendev/Swashbuckle.AspNetCore to generate the API spec, therefore it's not an easy fix to change the spec structure as the solution above.
Swashbuckle does inheritance like:
Circle: {
  type: "object",
  allOf: [
    {
      $ref: "#/components/schemas/Shape"
    }
  ],
  properties: {
    radius: {
      type: "integer",
      format: "int32",
    }
  },
},
Shape: {
  type: "object",
  properties: {
    name: {
      type: "string",
      nullable: true,
    }
  },
}

(https://github.com/domaindrivendev/Swashbuckle.AspNetCore#enabling-inheritance)
Looks to me like there are two competing syntaxes here. You are probably correct about your implementation of allOf inheritance (being backed by the doc you linked ). However, I'm wondering if it's an option to also be compatible with the Swashbuckle-way?
I'll do some thinking of my options here. What're your thoughts on this?

Hello @fnatte, I will take a look and see what I can do. In the meantime, you can use a transformer to modify the specification if you want.

Using the following transform for now:
const transformAllOfInheritence = (inputSchema) => ({
  ...inputSchema,
  components: {
    ...inputSchema.components,
    schemas: inputSchema.components.schemas
      ? Object.entries(inputSchema.components.schemas).reduce((acc, [schemaName, schema]) => {
          if (schema.allOf && schema.properties) {
            const { allOf, description, ...rest } = schema;
            const modifiedSchema = {
              description,
              allOf: [...allOf, { ...rest }],
            };
            return { ...acc, ...{ [schemaName]: modifiedSchema } };
          }

          return { ...acc, ...{ [schemaName]: schema } };
        }, {})
      : undefined,
  },
});

module.exports = (inputSchema) => transformAllOfInheritence(inputSchema);

will be added with the next version

Should be fixed with 6.4.0 can you test when you have time, please?

Closing this issue since it's normally fixed. Don't hesitate if you have any problem

authors: anymaniax fnatte jogelin

repo: anymaniax/orval


text:
fix issue#262

Fixes #262.
Changes proposed in this pull request:

Fix issue #262 the wrong behaviour of showing epname.

@anz-bank/sysl-developers

@sahejsingh Review needed.

repo: anz-bank/sysl


text:
Wiring content type from swagger

Fixes #545

Adds content type to http operation responses

@anz-bank/sysl-developers

What's blocking this? It was approved 9 days ago.

After a chat with Gregg, there seems to be an issue which needs to be addressed in the importer. Hence, leaving this with the WIP tag and will merge it once its dependency is addressed.

What's blocking this? It was approved 9 days ago.

After a chat with Gregg, there seems to be an issue which needs to be addressed in the importer. Hence, leaving this with the WIP tag and will merge it once its dependency is addressed.

authors: anzdaddy ashwinsajiv


text:
clippy: multiple bound locations

Rust v1.78.0 was released. There are new clippy lints that need to be addressed before we can upgrade. Here's one:
warning: bound is defined in more than one place
    --> accounts-db/src/accounts_db.rs:2827:33
     |
2827 |     pub fn purge_keys_exact<'a, C: 'a>(
     |                                 ^
...
2832 |         C: Contains<'a, Slot>,
     |         ^
     |
     = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#multiple_bound_locations
     = note: `#[warn(clippy::multiple_bound_locations)]` on by default

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

Project coverage is 82.1%. Comparing base (57f92b7) to head (8bdc44f).
Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1179   +/-   ##
=======================================
  Coverage    82.1%    82.1%
=======================================
  Files         886      886
  Lines      236394   236394
=======================================
+ Hits       194205   194233   +28
+ Misses      42189    42161   -28

authors: brooksprumo codecov-commenter

repo: anza-xyz/agave


text:
Reduces what accounts-db exports publicly

Problem
In the accounts-db crate, most submodules are exported with pub, even even no other crates use them. We should reduce external visibility when possible.
Summary of Changes
For the submodules that are not used outside of accounts-db, do not publicly export them.
Note, each submodule change is its own commit.

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

Project coverage is 81.8%. Comparing base (312f725) to head (dd3361c).
Report is 10 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##           master     #667     +/-   ##
=========================================
- Coverage    81.8%    81.8%   -0.1%
=========================================
  Files         851      851
  Lines      230370   230370
=========================================
- Hits       188660   188643     -17
- Misses      41710    41727     +17


text:
Add enums operations to ReactiveSeq

Create a stream based on enum values, include overloads with start, start & end, start, step & end.
 ReactiveSeq.enums(Days.class)
                      .printOut();

Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Sunday

Released in 2.1.0

repo: aol/cyclops-react