Dropdown and other animations stop working when going through pages.

I am currently using flow bite using angular v16 and at first everything works fine but after you switch pages you have to refresh in order for them to work.

i have the same error also

Use the newly released 1.6.6. It allows you to call window.initFlowbite() to re-initialize all components.

Use the newly released v1.6.6. It allows you to call window.initFlowbite() to re-initialize all components.

What do you mean? Can you show an example? I get Property 'initFlowbite' does not exist on type 'Window & typeof globalThis'.

Make sure that you use it in every component that you want to use the HTML markup, even if it is a dynamic component created by a HTTP request.
Like this:
@Component({
  selector: 'mycomponent',
  templateUrl: './mycomponent.component.html',
  styleUrls: ['./mycomponent.component.scss']
})
@Flowbite()
export class MyComponent

https://gist.github.com/OmarMtya/9ce68c563893d1c774f11a94ea73a31c

I created an Angular decorator to fix this (I think this problem is only for Angular). Make sure that you use it in every component that you want to use the HTML markup, even if it is a dynamic component created by a HTTP request.
Like this:
@Component({
  selector: 'mycomponent',
  templateUrl: './mycomponent.component.html',
  styleUrls: ['./mycomponent.component.scss']
})
@Flowbite()
export class MyComponent

https://gist.github.com/OmarMtya/9ce68c563893d1c774f11a94ea73a31c

Hi, it works kind of. The modals are rendered wrong I've noticed:

My work around has always been defining them in typescript but that's soo much work for such a simple thing as a dropdown..

I created an Angular decorator to fix this (I think this problem is only for Angular). Make sure that you use it in every component that you want to use the HTML markup, even if it is a dynamic component created by a HTTP request.
Like this:
@Component({
  selector: 'mycomponent',
  templateUrl: './mycomponent.component.html',
  styleUrls: ['./mycomponent.component.scss']
})
@Flowbite()
export class MyComponent

https://gist.github.com/OmarMtya/9ce68c563893d1c774f11a94ea73a31c

You're the savior and hero we needed. Your solution works!!!!!! Amazing that this has finally been fixed after so many months of ignoration by the flowbite devs!!

I created an Angular decorator to fix this (I think this problem is only for Angular). Make sure that you use it in every component that you want to use the HTML markup, even if it is a dynamic component created by a HTTP request.
Like this:
@Component({
  selector: 'mycomponent',
  templateUrl: './mycomponent.component.html',
  styleUrls: ['./mycomponent.component.scss']
})
@Flowbite()
export class MyComponent

https://gist.github.com/OmarMtya/9ce68c563893d1c774f11a94ea73a31c

You're the savior and hero we needed. Your solution works!!!!!! Amazing that this has finally been fixed after so many months of ignoration by the flowbite devs!!

Please, if you find any weird behaviour let me know, I'm still testing it

I created an Angular decorator to fix this (I think this problem is only for Angular). Make sure that you use it in every component that you want to use the HTML markup, even if it is a dynamic component created by a HTTP request.
Like this:
@Component({
  selector: 'mycomponent',
  templateUrl: './mycomponent.component.html',
  styleUrls: ['./mycomponent.component.scss']
})
@Flowbite()
export class MyComponent

https://gist.github.com/OmarMtya/9ce68c563893d1c774f11a94ea73a31c

You're the savior and hero we needed. Your solution works!!!!!! Amazing that this has finally been fixed after so many months of ignoration by the flowbite devs!!

Please, if you find any weird behaviour let me know, I'm still testing it

for me sometimes its working, and sometimes i get this error:
Modal with id defaultModal has not been initialized. Please initialize it using the data-modal-target attribute.

I created an Angular decorator to fix this (I think this problem is only for Angular). Make sure that you use it in every component that you want to use the HTML markup, even if it is a dynamic component created by a HTTP request.
Like this:
@Component({
  selector: 'mycomponent',
  templateUrl: './mycomponent.component.html',
  styleUrls: ['./mycomponent.component.scss']
})
@Flowbite()
export class MyComponent

https://gist.github.com/OmarMtya/9ce68c563893d1c774f11a94ea73a31c

You're the savior and hero we needed. Your solution works!!!!!! Amazing that this has finally been fixed after so many months of ignoration by the flowbite devs!!

Please, if you find any weird behaviour let me know, I'm still testing it

for me sometimes its working, and sometimes i get this error: Modal with id defaultModal has not been initialized. Please initialize it using the data-modal-target attribute.

What block/component are you trying to use?
Just an advice, I've been in that situation too, instead of using data-modal-hide or data-modal-show, use data-modal-toggle. One more thing, if you have a ngFor with nested flowbite components, you will have to make a new modal for every repeated component to avoid having more than one backdrop (Like having the modal inside of the ngFor, and make sure that they have a unique ID). If you need more help, you can show me what are you trying to do.

I created an Angular decorator to fix this (I think this problem is only for Angular). Make sure that you use it in every component that you want to use the HTML markup, even if it is a dynamic component created by a HTTP request.
Like this:
@Component({
  selector: 'mycomponent',
  templateUrl: './mycomponent.component.html',
  styleUrls: ['./mycomponent.component.scss']
})
@Flowbite()
export class MyComponent

https://gist.github.com/OmarMtya/9ce68c563893d1c774f11a94ea73a31c

You're the savior and hero we needed. Your solution works!!!!!! Amazing that this has finally been fixed after so many months of ignoration by the flowbite devs!!

Please, if you find any weird behaviour let me know, I'm still testing it

for me sometimes its working, and sometimes i get this error: Modal with id defaultModal has not been initialized. Please initialize it using the data-modal-target attribute.

What block/component are you trying to use?
Just an advice, I've been in that situation too, instead of using data-modal-hide or data-modal-show, use data-modal-toggle. One more thing, if you have a ngFor with nested flowbite components, you will have to make a new modal for every repeated component to avoid having more than one backdrop (Like having the modal inside of the ngFor, and make sure that they have a unique ID). If you need more help, you can show me what are you trying to do.

have multi <router-outlet></router-outlet> maybe that is the issue.
my component (not app.module)
import { Component, OnInit } from '@angular/core';
import { Flowbite } from '@app/components/flowbite';

@Component({
  selector: 'app-platfom',
  templateUrl: './platform.component.html'
})
@Flowbite()
export class PlatfomComponent implements OnInit {
  ngOnInit(): void {
  }
}

html of this component:

   <platfom-header></platfom-header>
   <platfrom-sidebar></platfrom-sidebar>

      <router-outlet></router-outlet>

in and then i enter this also on:
@Component({
  selector: 'app-collections',
  templateUrl: './collections.component.html'
})
@Flowbite()
export class CollectionsComponent implements OnInit {
  loading = false;
  public collectionsData: any;
  public error = '';
  public typeHrs = 'ONE_DAY';
  public eth = faEthereum;
  public add = faSquarePlus;
  constructor(private collectionsServiceTsService: CollectionsServiceTsService) {}

  ngOnInit(): void {
    this.getCollections(this.typeHrs);
    interval(30000).subscribe(
      () => {
        this.getCollections(this.typeHrs);
        this.loading = false;
      },
      (error: any) => {
        console.log('error');
      },
      () => {
        console.log('observable completed !');
      }
    );
  }

  getCollections(hrs: string) {
    this.loading = true;
    return this.collectionsServiceTsService
    .getCollections(hrs)
    .pipe(first())
    .subscribe((data: Collections) => {
      this.collectionsData = data;
      this.loading = false;
    })
  }

  getHrs(typeHrs: string) {
    this.typeHrs = typeHrs;
    this.getCollections(typeHrs);
  }

  filterResults(text: string) {
    if (!text) {
      this.collectionsData = this.collectionsData;
    }

    this.collectionsData = this.collectionsData.filter(
      (data: { name: string; }) => data?.name.toLowerCase().includes(text.toLowerCase())
    );
  }

}

the html:

Trending NFT Collections by Sales

See what's selling. Prices updated in real time.

      <app-skeleton *ngIf="loading"></app-skeleton>

              <button id="dropdownRadioButton" data-dropdown-toggle="dropdownRadio" class="inline-flex items-center text-gray-500 bg-white border border-gray-300 focus:outline-none hover:bg-gray-100 focus:ring-4 focus:ring-gray-200 font-medium rounded-lg text-sm px-3 py-1.5 dark:bg-gray-800 dark:text-white dark:border-gray-600 dark:hover:bg-gray-700 dark:hover:border-gray-600 dark:focus:ring-gray-700" type="button">
                  <svg class="w-3 h-3 text-gray-500 dark:text-gray-400 mr-2.5" aria-hidden="true" xmlns="http://www.w3.org/2000/svg" fill="currentColor" viewBox="0 0 20 20">
                          <path d="M10 0a10 10 0 1 0 10 10A10.011 10.011 0 0 0 10 0Zm3.982 13.982a1 1 0 0 1-1.414 0l-3.274-3.274A1.012 1.012 0 0 1 9 10V6a1 1 0 0 1 2 0v3.586l2.982 2.982a1 1 0 0 1 0 1.414Z"/>
                      </svg>
                  Last {{typeHrs}}
                  <svg class="w-2.5 h-2.5 ml-2.5" aria-hidden="true" xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 10 6">
                      <path stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="m1 1 4 4 4-4"/>
                  </svg>
              </button>

                    <button data-modal-target="defaultModal" data-modal-toggle="defaultModal" class="block text-black bg-yellow-200 hover:bg-yellow-300 focus:ring-4 focus:outline-none focus:ring-yellow-300 font-medium rounded-lg text-sm px-5 py-2.5 text-center" type="button">
                        <helper-icons [icon]="add"></helper-icons>  Add Alert
                    </button>

                    Terms of Service

                <button type="button" class="text-gray-400 bg-transparent hover:bg-gray-200 hover:text-gray-900 rounded-lg text-sm w-8 h-8 ml-auto inline-flex justify-center items-center dark:hover:bg-gray-600 dark:hover:text-white" data-modal-hide="defaultModal">
                    <svg class="w-3 h-3" aria-hidden="true" xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 14 14">
                        <path stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="m1 1 6 6m0 0 6 6M7 7l6-6M7 7l-6 6"/>
                    </svg>
                    Close modal
                </button>

                    With less than a month to go before the European Union enacts new consumer privacy laws for its citizens, companies around the world are updating their terms of service agreements to comply.

                    The European Union’s General Data Protection Regulation (G.D.P.R.) goes into effect on May 25 and is meant to ensure a common set of data rights in the European Union. It requires organizations to notify users as soon as possible of high-risk data breaches that could personally affect them.

                <button data-modal-hide="defaultModal" type="button" class="text-white bg-blue-700 hover:bg-blue-800 focus:ring-4 focus:outline-none focus:ring-blue-300 font-medium rounded-lg text-sm px-5 py-2.5 text-center dark:bg-blue-600 dark:hover:bg-blue-700 dark:focus:ring-blue-800">I accept</button>
                <button data-modal-hide="defaultModal" type="button" class="text-gray-500 bg-white hover:bg-gray-100 focus:ring-4 focus:outline-none focus:ring-blue-300 rounded-lg border border-gray-200 text-sm font-medium px-5 py-2.5 hover:text-gray-900 focus:z-10 dark:bg-gray-700 dark:text-gray-300 dark:border-gray-500 dark:hover:text-white dark:hover:bg-gray-600 dark:focus:ring-gray-600">Decline</button>

I created an Angular decorator to fix this (I think this problem is only for Angular). Make sure that you use it in every component that you want to use the HTML markup, even if it is a dynamic component created by a HTTP request.
Like this:
@Component({
  selector: 'mycomponent',
  templateUrl: './mycomponent.component.html',
  styleUrls: ['./mycomponent.component.scss']
})
@Flowbite()
export class MyComponent

https://gist.github.com/OmarMtya/9ce68c563893d1c774f11a94ea73a31c

You're the savior and hero we needed. Your solution works!!!!!! Amazing that this has finally been fixed after so many months of ignoration by the flowbite devs!!

Please, if you find any weird behaviour let me know, I'm still testing it

Awesome, works, thanks!

I have a sidebar that does not display when I use an *ngIf directive, it does not work with that decorator either

I have a sidebar that does not display when I use an *ngIf directive, it does not work with that decorator either

Create a new component for your sidebar. And in your sidebar component use the decorator. The idea is that every time the ngIf changes its value the decorator should be executed

Tengo una barra lateral que no se muestra cuando uso una directiva *ngIf, tampoco funciona con ese decorador.

Crea un nuevo componente para tu barra lateral. Y en tu componente de la barra lateral usa el decorador. La idea es que cada vez que ngIf cambie su valor se debe ejecutar el decorador.

I did what you told me but I still have the following error:  flowbitedecorator.ts:53 Drawer with id drawer-navigation has not been initialized. Please initialize it using the data-drawer-target attribute.

This worked for me:
@Component()
export class MyComponent implements AfterViewInit {

    ngAfterViewInit(): void {
        initFlowbite();
    }

For React just use:
    useEffect(() => {         initFlowbite();     }, []);
in the page where is the component and import 'flowbite'; in your App.jsx or index.tsx

I have a sidebar that does not display when I use an *ngIf directive, it does not work with that decorator either

Create a new component for your sidebar. And in your sidebar component use the decorator. The idea is that every time the ngIf changes its value the decorator should be executed

How can I use this decorator? I have this issue, Im using the datepicker.
Inside the router outlet is not working.
Tried to add :
import { Component, OnInit } from '@angular/core';
import {initFlowbite} from 'flowbite'
import { Flowbite } from '@app/components/flowbite';
@Component({
selector: 'app-test',
templateUrl: './test.component.html',
styleUrls: ['./test.component.scss']
})
export class TestComponent implements OnInit {
@Flowbite()
ngOnInit(): void {
initFlowbite()
}
}
Have and error in the import line, --> Cannot find module '@app/components/flowbite' or its corresponding type declarations.

Thank you, it's incredible

I created an Angular decorator to fix this (I think this problem is only for Angular). Make sure that you use it in every component that you want to use the HTML markup, even if it is a dynamic component created by a HTTP request.
Like this:
@Component({
  selector: 'mycomponent',
  templateUrl: './mycomponent.component.html',
  styleUrls: ['./mycomponent.component.scss']
})
@Flowbite()
export class MyComponent

https://gist.github.com/OmarMtya/9ce68c563893d1c774f11a94ea73a31c

Obrigado parceiro, minha performance estava caindo por ficar iniciando o flowbit em todos os componentes em 3 ciclos de vida diferente.

I created an Angular decorator to fix this (I think this problem is only for Angular). Make sure that you use it in every component that you want to use the HTML markup, even if it is a dynamic component created by a HTTP request.
Like this:
@Component({
  selector: 'mycomponent',
  templateUrl: './mycomponent.component.html',
  styleUrls: ['./mycomponent.component.scss']
})
@Flowbite()
export class MyComponent

https://gist.github.com/OmarMtya/9ce68c563893d1c774f11a94ea73a31c

How can I use this decorator?

I created an Angular decorator to fix this (I think this problem is only for Angular). Make sure that you use it in every component that you want to use the HTML markup, even if it is a dynamic component created by a HTTP request.
Like this:
@Component({
  selector: 'mycomponent',
  templateUrl: './mycomponent.component.html',
  styleUrls: ['./mycomponent.component.scss']
})
@Flowbite()
export class MyComponent

https://gist.github.com/OmarMtya/9ce68c563893d1c774f11a94ea73a31c

How can I use this decorator?

I downloaded the file within my project. Then just call the decorator.

Working fine! Thx a lot

Is there any progress on this? I have the same problem with Angular 18. I'm using the decorator in the meantime.

 I was about to change my UI library from Flowbite to ShadCN. Thanks a lot!! 😀

For React just use:
useEffect(() => { initFlowbite(); }, []); in the page where is the component and import 'flowbite'; in your App.jsx or index.tsx

adding useLocation() work for me, react vite.
const location = useLocation();
useEffect(() => { initFlowbite(); }, [location]);

I created an Angular decorator to fix this (I think this problem is only for Angular). Make sure that you use it in every component that you want to use the HTML markup, even if it is a dynamic component created by a HTTP request.
Like this:
@Component({
  selector: 'mycomponent',
  templateUrl: './mycomponent.component.html',
  styleUrls: ['./mycomponent.component.scss']
})
@Flowbite()
export class MyComponent

https://gist.github.com/OmarMtya/9ce68c563893d1c774f11a94ea73a31c

you saved me


[3.x] [iOS] Use platform generated api to initialize iOS plugins

Can be cherry picked to 3.3
Moved iOS plugin initialization to api.cpp.
This allows to initialize plugins at the same point where modules were previously initialized.
Fixes: https://github.com/godotengine/godot/issues/51230

Thanks!

Cherry-picked for 3.3.3.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-26-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 2935

Questions ?
Please refer to the Backport tool documentation


Error when running Solid Queue's supervisor together with Puma

When I start up my rails server in development mode after having added the plugin :solid_queue line to my config/puma.rb file I get the following errors in the output when running Puma:
objc[56839]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called.
objc[56839]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.

This doesn't appear to interfere with Puma serving local web requests, but if I kick off a background job it does not get processed.  However, if I remove the plugin config line from the Puma file and then run Solid Queue as a separate process, the Puma error goes away when starting the server and Solid Queue picks up background jobs and processes them correctly.
My local dev environment: M2 MacBook running Ventura.

@elliotlarson, The root cause doesn't appear to be related to this gem.
Reference: https://github.com/rails/rails/issues/38560

@iamradioactive Ah, thank you.  That solved the problem.


Check List - Gap Analysis Document

What’s available in cQube 1 and in cQube 2 (cqube edu)?
What’s the gap?

Section 1.a is completed and below are the links
https://docs.google.com/document/d/1NmCgc0PV3OUAAobGKJ9EyjdJOfF_16pv
https://docs.google.com/document/d/1WbP5zZ0s_LFVMIeyt3_rSmk-SPycv5DJ
Section 1.b - Below are the Gaps found in the cQube 1 & 2
NVSK integration with cqube-core backend
i) Changes required in config.csv file which supports NVSK configurations structure
ii) Changes required in back end output directory
iii) NVSK nodejs api code need to change according to cQube-core
iv) Changes required in NVSK configurations file to support all data sources as common structure
cQube-core UI configuration functionality
i) Look and feel of cQube-core UI going to be same
ii) cQube-core configuration functionily need to change according to NVSK configurations
iii) Filter functionality need to change according to NVSK functionality( filter coming from Nodejs config file)
iv) Reusable report components need to change which supports NVSK report structure
v) Changes in Routing part required
vi) Angular side api call changes required which supports NVSK configurations file
vii) Nodejs side common api and configuration file need to be added like NVSK.


CI: Add workflow to push to avd.arista.com on every devel commit

Change Summary
WIP
Related Issue(s)
Fixes #
Component(s) name
arista.avd.<role-name>
Proposed changes

How to test

Checklist
User Checklist

N/A

Repository Checklist

[ ] My code has been rebased from devel before I start
[ ] I have read the CONTRIBUTING document.
[ ] My change requires a change to the documentation and documentation have been updated accordingly.
[ ] I have updated molecule CI testing accordingly. (check the box if not applicable)

I think this gets us there.  We do have to provide some type of PAT
---
# This is deploying the latest commits on devel to aristanetworks/avd-docs main branch
name: Deploy devel documentation to aristanetworks/avd-docs main
on:
  push:
    branches:
      - devel
  workflow_dispatch:

jobs:
  'devel_doc':
    name: 'Update Public devel documentation'
    runs-on: ubuntu-latest
    if: github.repository == 'aristanetworks/avd'
    steps:
      - name: Checkout AVD
        uses: actions/checkout@v4
        with:
          fetch-depth: 0
          path: ./avd

      - name: Checkout docs repo
        uses: actions/checkout@v4
        with:
          repository: aristanetworks/avd-docs
          token: ${{ secrets.DOCS_ACCESS_TOKEN }}
          fetch-depth: 0
          path: ./docs

      - name: 'Setup Python 3 on runner'
        uses: actions/setup-python@v5
        with:
          python-version: '3.x'

      - name: Setup Git config
        run: |
          git config --global user.name 'github-actions[bot]'
          git config --global user.email<EMAIL_ADDRESS>
      - name: 'Build mkdocs content and deploy to aristanetworks/avd-docs on main'
        run: |
            cd ./docs
            pip install -r ../avd/ansible_collections/arista/avd/docs/requirements.txt
            mike deploy --push -b main devel --config-file ../avd/mkdocs.yml

Thanks @JulioPDX - feel free to add commits to this PR
Have you tried this workflow somewhere?

Thanks @JulioPDX - feel free to add commits to this PR Have you tried this workflow somewhere? I am concerned that the snippet path would still be broken

I believe you are right about snippets, let me reevaluate this solution

@gmuloc yeah I tried it on some private repos, I think this gets us all we need with devel, since that version already exists, we can use standard git to update the directory. I'll add you to the private repos if you'd like to test.
---
# This is deploying the latest commits on devel to aristanetworks/avd-docs main branch
name: Deploy devel documentation to aristanetworks/avd-docs main

on:
  push:
    branches:
      - devel
  workflow_dispatch:

concurrency:
  group: ${{ github.workflow }}-${{ github.head_ref }}
  cancel-in-progress: true

jobs:
  'devel_doc':
    name: 'Update Public devel documentation'
    runs-on: ubuntu-latest
    if: github.repository == 'aristanetworks/avd'
    steps:
      - name: Checkout AVD
        uses: actions/checkout@v4
        with:
          fetch-depth: 0
          path: devel

      - name: Checkout docs repo
        uses: actions/checkout@v4
        with:
          repository: aristanetworks/avd-docs
          token: ${{ secrets.REPO_ACCESS_TOKEN }}
          fetch-depth: 0
          path: docs

      - name: 'Setup Python 3 on runner'
        uses: actions/setup-python@v5
        with:
          python-version: '3.x'

      - name: Setup Git config
        run: |
          git config --global user.name 'github-actions[bot]'
          git config --global user.email<EMAIL_ADDRESS>
      - name: 'Build mkdocs content and deploy to aristanetworks/avd-docs on main'
        run: |
            cd ./devel
            pip install .[doc]
            mkdocs build -d ../docs/devel
            cd ../docs
            git add .
            git commit -m "updating devel with $GITHUB_SHA"
            git push

Closing as we agreed it would be implemented in avd-docs repo.
cc @JulioPDX

@gmuloc @carlbuchmann  Need your opinion on something, I got this to work using workflow dispatch, but this still requires some type of secret to be set since the docs repository is private. We would still need a dispatch workflow on the avd repo. Example below from my test repositories.
On AVD:
devel-doc.yml
---
name: Deploy devel documentation
on:
  push:
    branches:
      - devel
  workflow_dispatch:

jobs:
  'devel_doc':
    name: 'Update Public devel documentation'
    runs-on: ubuntu-latest
    if: github.repository == 'JulioPDX/production-test'
    steps:
      - name: Run dispatch
        run: |
          curl -L \
            -X POST \
            -H "Accept: application/vnd.github+json" \
            -H "Authorization: Bearer ${{ secrets.REPO_ACCESS_TOKEN }}" \
            -H "X-GitHub-Api-Version: 2022-11-28" \
            https://api.github.com/repos/JulioPDX/push-test/actions/workflows/test.yml/dispatches \
            -d '{"ref":"main"}'

On docs repo
test.yml
---
name: Deploy devel documentation
on:
  workflow_dispatch:

jobs:
  'devel_doc':
    name: 'Update Public devel documentation'
    runs-on: ubuntu-latest
    steps:
      - name: Checkout docs repo
        uses: actions/checkout@v4
        with:
          path: docs

      - name: Checkout AVD
        uses: actions/checkout@v4
        with:
          repository: JulioPDX/production-test
          path: avd

      - name: 'Setup Python 3 on runner'
        uses: actions/setup-python@v5
        with:
          python-version: '3.x'

      - name: Setup Git config
        run: |
          git config --global user.name 'github-actions[bot]'
          git config --global user.email<EMAIL_ADDRESS>      - name: 'Build mkdocs content and deploy'
        run: |
            cd ./avd
            pip install -r requirements.txt
            mkdocs build -d ../docs/devel
            cd ../docs
            git add .
            git commit -m "updating devel with $GITHUB_SHA"
            git push

@JulioPDX can we do without token the other way around )(avd-docs subscribing to push events on devel in main avd repo?)

Closing as this has been implemented in the docs repo. Thank you


feat: poc

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 85.588%

Totals

Change from base Build<PHONE_NUMBER>2:
0.0%

Covered Lines:
6430

Relevant Lines:
7000

💛  - Coveralls


JsDiff.diffArrays to compare arrays

adds support for comparing two arrays and finding the difference. This comes in very handy in my current project.
If you feel this is beyond the boundaries of the primary focus of jsdiff which is text comparison, I could trim the pull request to just having the .join method move to the base class so we can create the diffArrays in our own project. Having the .join('') in several methods of base prevents this.

Sorry for the delay. Generally looks good. Going to try to make some time soon to land this and get a new release out.

Released in 3.1.0


[BUG] Shuffleboard speed displaying rotation

Describe the bug
Robot speed on shuffleboard is the rotational speed, not the forward speed
To Reproduce
Start program
View values
Expected behavior
The robot speed on shuffleboard should not be the rotational speed

No longer needed


os is not defined in next.config.js

I've installed nextjs-node-loader and used the next.config.js file shown in the documentation, but when I try to build my project I get an error re: this line in the config:
flags: os.constants.dlopen.RTLD_NOW,
Build error occurred
ReferenceError: os is not defined

Should I be defining os somehow?

This is a node module you can import. See: https://nodejs.org/api/os.html#os

You don't need to use the flags, it's just an example pulled from https://github.com/eisberg-labs/nextjs-node-loader/blob/main/examples/next-13-koffi/next.config.js. As @archnode said, it's a dependency that you need to install if you need it.


Click on ShadowDOM element does not work after scrolling the page

What is your Test Scenario?

Open web page with elements inside ShadowDOM
Click on some shadowed element
Associated action is triggered
Scroll the page down (the shadowed element should still be in visible area)
Click the shadowed element again

What is the Current behavior?

TestCafe clicks outside of selected element

What is the Expected behavior?

TestCafe should click on selected element and associated action should be triggered

What is your web application and your TestCafe test code?

Your website URL (or attach your complete example):

https://boltdesignsystem.com/pattern-lab/?p=viewall-components-tabs

Your complete test code (or attach your test files):

import {Selector} from 'testcafe';

fixture`My fixture`
    .page`https://boltdesignsystem.com/pattern-lab/?p=viewall-components-tabs`;

const iFrame = Selector('iframe');

const tab = Selector(() => document
    .querySelector('bolt-band[size="small"] bolt-tabs')
    .shadowRoot.querySelectorAll('bolt-trigger'));

const tabPanel = Selector('bolt-band[size="small"] bolt-tabs bolt-tab-panel');

const subHeadline = Selector('.c-bolt-band__content bolt-list');
const label = Selector('bolt-text');

test('Check tabs with ShadowDOM', async t => {
    await t.switchToIframe(iFrame)
        // code below works as expected
        // testcafe clicks on elements and associated action are triggered
        .click(tab.nth(0))
        .expect(tabPanel.nth(0).visible).ok()
        .click(tab.nth(1))
        .expect(tabPanel.nth(1).visible).ok()
        .click(tab.nth(2))
        .expect(tabPanel.nth(2).visible).ok()
        // lets scroll page
        .hover(label.withText('Label spacing'))
        .hover(subHeadline.nth(0))
        // testcafe clicks outside of shadowed element
        // so action is not triggered and assertion failed
        .click(tab.nth(0))
        .expect(tabPanel.nth(0).visible).ok();
});

Your complete configuration file (if any):

Your complete test report:

 ✖ Check tabs with ShadowDOM

   1) AssertionError: expected false to be truthy

      + expected - actual

      -false
      +undefined

      Browser: Chrome 86.0.4240.75 / macOS 10.15.7

         28 |        .hover(label.withText('Label spacing'))
         29 |        .hover(subHeadline.nth(0))
         30 |        // testcafe clicks outside of shadowed element
         31 |        // so action is not triggered and assertion failed
         32 |        .click(tab.nth(0))
       > 33 |        .expect(tabPanel.nth(0).visible).ok();
         34 |});

Screenshots:

Steps to Reproduce:

run the test script attached above

Your Environment details:

testcafe version:                   1.9.4
node.js version:                    v13.14.0
command-line arguments:  yarn testcafe chrome tests/clickOnShadowDOM.js
browser name and version: Chrome 86.0.4240.75
platform and version:          macOS 10.15.7
other:

@gregatp, Thank you for your report. I've reproduced this issue. We'll update this thread once it's fixed.

Any update on this or a workaround?

Hi @jacsamell
We haven't found the cause of the issue yet. So, we cannot share any workarounds.
We will update this thread as soon as we get any news.

I just came across this problem and searched for a workaround.
In my case, it works if I make sure that the browser window is large enough (https://devexpress.github.io/testcafe/documentation/guides/concepts/browsers.html#emulate-screen-size) so that there is no need to scroll in the test.
Not a very good workaround and probably it doesn't work for many scenarios but in my case it has saved me from changing the test framework. The big disadvantage is that we are not able to test our responsive frontend on different dimensions. But maybe it will help someone.

I just came across this problem and searched for a workaround.
In my case, it works if I make sure that the browser window is large enough (https://devexpress.github.io/testcafe/documentation/guides/concepts/browsers.html#emulate-screen-size) so that there is no need to scroll in the test.
Not a very good workaround and probably it doesn't work for many scenarios but in my case it has saved me from changing the test framework. The big disadvantage is that we are not able to test our responsive frontend on different dimensions. But maybe it will help someone.

@Josef-Reichardt,
Thank you for sharing your workaroung.

@Josef-Reichardt,
Thank you for sharing your workaroung.

We are using ClientFunction and triggering click directly in the browser as workaround, for example:
const clickTab = ClientFunction(() => document
    .querySelector('bolt-band[size="small"] bolt-tabs')
    .shadowRoot.querySelectorAll('bolt-trigger')[1].click());

await clickTab();

We are using ClientFunction and triggering click directly in the browser as workaround, for example:
const clickTab = ClientFunction(() => document
    .querySelector('bolt-band[size="small"] bolt-tabs')
    .shadowRoot.querySelectorAll('bolt-trigger')[1].click());

await clickTab();

@gregatp,
Thank you for sharing your workaround.

@gregatp,
Thank you for sharing your workaround.

Is this related to #6207 or are there any other news for this issue?

For team
The issue is still reproduced with the<EMAIL_ADDRESS>The updated example
import {Selector} from 'testcafe';

fixture`My fixture`
    .page`https://boltdesignsystem.com/pattern-lab/?p=viewall-components-tabs`;

const iFrame = Selector('iframe');

const tab = Selector('bolt-tabs').shadowRoot().find('bolt-trigger');

const tabPanel = Selector('bolt-tabs bolt-tab-panel');

const subHeadline = Selector('bolt-list');
const label = Selector('bolt-text');

test('Check tabs with ShadowDOM', async t => {
    await t.switchToIframe(iFrame)
        .expect(tab.exists).ok()
        // code below works as expected
        // testcafe clicks on elements and associated action are triggered
        .click(tab.nth(0))
        .expect(tabPanel.nth(0).visible).ok()
        .click(tab.nth(1))
        .expect(tabPanel.nth(1).visible).ok()
        .click(tab.nth(2))
        .expect(tabPanel.nth(2).visible).ok()
        // lets scroll page
        .hover(label.withText('Label spacing'))
        .hover(subHeadline.nth(0))
        // testcafe clicks outside of shadowed element
        // so action is not triggered and assertion failed
        .click(tab.nth(0))
        .expect(tabPanel.nth(0).visible).ok();
});


model-32000.meta does not exist.

when i run code , then have a error :checkpoints/model-32000.meta does not exist.

please update the model path in eval.py (or use --model parameter) to your local system's trained model path


Iterator based write API

Some thoughts on the Write (Encode?) API, specific to my use case; this is somewhat relevant to the Read (Decode) API as well. Now that I've built it into my codebase, I have a clearer understanding of it.
BOSS consumes data from the MLB API and then persists it to disk. To avoid duplicating work, it currently caches all the games it pulls into a separate file (just the GamePK is cached). I think my needs on the read/decode side are covered as all I need is the GamePK column, which based on your Readme, should be very efficient to query from the master data file. This will save me the worry that I cached a game as complete, but then had an issue when persisting the data to disk.
For writes, it currently does a simple append to a CSV file. Ideally, there would be some way for me to get the encoding format from the current file, tell tree-buf to use that encoding for the new data and give me bytes that I can just append to the current file. This would also have huge performance wins as it wouldn't need to analyze the source data, it would do all that work with the first file it creates.
I assume there would be some complexity in reading/updating the dictionary, so I don't know how feasible this is technically. This may require splitting up the "decode" bytes from "data" bytes such that the decode bytes would need to be overwritten, or appended to separately from the "data" bytes.
Building on that, it may be useful to have the ability to do a deeper sample on the initial file, for those that will want to append rather than re-build.
I still owe you the diagnostics on the main data set, will hopefully get to that next weekend.

I'm not entirely sure that I understand every aspect of your use-case, but having a first-class API for mutable/append data within a Tree-Buf file is somewhere between unlikely and far in the future. I'd like to give a basic idea of why the file format might make that difficult, but then get into how you can take advantage of what Tree-Buf has today to solve your problem.
Complications
Tree-Buf stores all data separated by it's "path" from the root to some data. For a CSV, this is relatively simple but this is not the only case. It may be useful to consider the CSV case for analysis though. Let's consider a 2 column CSV with headers "A" and "B".
A schema for such a CSV might look like
struct Row {
  a: String,
  b: String,
}
type Schema = Vec<Row>;

This is what this would look like on-disk in Tree-Buf assuming 10 rows:
[type: Vec len: 10, elements: [ type Object, field count: 2, field "A": [type: UTF-8, buffer: [byte_len: 30, data: "a1", "a2", "a3", "a4", "a5", "a6", "a7", "a8", "a9", "a10"]]], field "B": [type: UTF-8, buffer [byte_len: 30, data: ["b1", "b2", "b3", "b4", "b5", "b6", "b7", "b8", "b9", "b10"]]]]
Now, we want to add 10 more rows. I count 5 places in the file that need to be modified:

root.len
root.elements.field_a.buffer.byte_len
root.elements.field_a.buffer.data
root.elements.field_b.buffer.byte_len
root.elements.field_b.buffer.data

Editing any of these locations may cause all the other data in the file to need to shift down, at which point you are basically re-writing the file. This is even true for eg: the first root.len since it will be stored in PrefixVarInt which uses only 1 byte up to the value 127, but at least 2 bytes for values that are higher than that.
Consider also that the use-case of "appending rows" is specific to only a subset of the kind of data that Tree-Buf supports. For a lot of kinds of data (say, a GraphQL response which may have fields at the root that aren't described as rows) it's hard to describe how this API would interact with those other schemas.
This is a fundamental trade-off that Tree-Buf makes that enables the compression in the first place.
What you should do
If you are retrieving data in reasonably sized chunks that on their own compress well using Tree-Buf, then consider just appending independent Tree-Buf logical files to the physical file. I mean, have a basic framing protocol that serializes to tree_buf.
Eg (pseudocode): let chunk = encode(data);. Then append to your file like so: let len = encodePrefixVarint(chunk.len()); write_to_file(len); write_to_file(chunk);. On the read side you would just do let (len, offset) = decodePrefixVarint(stream); let tb_file = read_bytes(len, offset, stream); in a loop until the file is exhausted.

Makes a lot of sense. I certainly don't want you to go down a path of adding complexity to your code base for my specific use case (especially when it's a non-goal of the project).
Appending rows is a best case scenario for me, but not super-critical. I'll probably just put all new data into a temporary tree-buf file and then merge it into the main tree-buf file at the end. This should yield some nice performance diagnostics.
Thanks for the detailed explanation.


GitLab Authentication Feature Status

Hello.
I am interested in deploying kubessh in our Kubernetes cluster. We use GitLab and are interested in using GitLab for public key authentication. I see there is an authentication implementation for GitLab, but it doesn't seem to match the current API spec for retrieving user keys by username.
Is the implementation known to work using a different API route, or a WIP feature? We'd be interested in opening a PR if it's WIP to meet the spec if that is ok.
Thanks!

Hello! Thank you for your interest :) I'm currently focusing on jupyterhub-ssh instead, so I've marked this project as inactive. You're welcome to fork and work on this if you wanna, but I'd recommend checking out jupyterhub-ssh for the most common use case I was using it for :)


[Feature] team target

It would be great to add scoreboards team as targets. For instance, a npc could focus only the blue team.

@Eredrim While you are waiting for mcmonkey to implement this, you could always try my re-write of Sentry:- https://github.com/Jabelpeeps/Sentries which is attempting to maintain the old functions, before adding new ones.  There is a link to the builds on my CI server in the ReadMe.  Let me know how you get on.

Scoreboard team targets are now available to servers in the latest dev build (#76)
Simply /sentinel addtarget sbteam:BLUE_TEAM
Also supports ignores!
Oh and please do reply telling me how it works for you, and any additional features you'd like to see!


Bypassing ApplyInstantID Node Can Ruin Conditioning

Issue screenshot:
Using a slightly modified default workflow, we can show that bypassing ApplyInstantID node does not maintain the original behaviour but rather degrades the quality of conditioning.

Expected behaviour:
bypassing a node should have zero effect on the original workflow.
InstantID version: 5149a21

this seems to be a bug with comfyui, I'll check better

can confirm the new update with the old (legacy) node is fixed, but still a problem with the new one!

can confirm the new update with the old (legacy) node is fixed, but still a problem with the new one!

image png files have workflow included.

This can happen if a node mutates something from input instead of copying.

From my testing, what happens when you disable applyinstantid in this case is that the positive prompt also becomes the negative prompt.
This is an issue in comfyui's frontend graphToPrompt function that turns the graph into json that the backend can understand.

This was indeed the bug, in this specific case, for each ksampler input it finds the node which it's connected to, in this case the disabled instantid and walks through its inputs.
for model it walks through the inputs and finds the first model type
for positive it walks through the inputs and finds the first conditioning type
for negative it walks through the inputs and finds the first conditioning type
so given this logic, the negative input of ksampler will always be the positive of instantid because it matches the first type
The proposed solution that follows the same logic would be to have a list of consumed inputs and refuse to connect to the same input again. This sort of assumes the order of input is the same.
Matching by name may be a another option, but not all nodes have matching names either.

for now, we can use a switch node to manually bypass it, until it gets fixed.

From my testing, what happens when you disable applying istantid, in this case, is that the positive prompt also becomes the negative prompt. (You can test this by copy-pasting the positive prompt in the negative prompt)
This is an issue in comfyui's frontend graphToPrompt function that turns the graph into json that the backend can understand.

does this have to do anything with SDXL using 2 clip models CLIP_g & CLIP_l ? I know this might be a noob assumption but isn't it how sdxl merges the 2 prompts? and InstantID works with sdxl and this might be that when bypassing the node, it merges them(both positive and negating) into a single positive.

image from : https://youtu.be/Wk88rK9Zh1Y?t=174

Just encounted a similar or maybe the same issue. Bypassing Apply InstantID or Advanced degrades the image heavly


Deploy on Amazon SageMaker

Do you have any recommendations on deploying this to Amazon SageMaker?
Likewise, can I retrain on my custom dataset?
Thanks in advance

Hi there, thanks for your interest in the Model Asset Exchange!
I'm afraid we cannot assist with SageMaker, being unfamiliar with the details of how that service works. I'd suggest looking into their documentation to see if they support arbitrary Docker container deployments.
For now, we don't support training this model on a custom dataset, please see #46 for details of the underlying training code repo that you can use for that.


Restore unit testing

Unit tests currently fail on release branch.
Was passing on build 130
Is failing on build 134
Commit on release that broke the build: https://github.com/Legrandgroup/libezsp/commit/228d7645966b86a876bbd46cda619a0086b44674

Done in commit https://github.com/Legrandgroup/libezsp/commit/3787703195a2a59e6b2fd7e264358b1690331c06


added optimized pipe. Submission 6

More optimization.
Prediction file:
Prediction_XXI_LM_Final.csv

Hey Lukas... this one gets 0.590. Solid.


tar: Unrecognized archive format error when trying to unpack flower_photos.tgz, TF tutorials on OSX

This is relating to the
How to Retrain Inception's Final Layer for New Categories Tutorial
I'm trying to unpack the flower_photos.tgz after curling it using
curl -O http://download.tensorflow.org/example_../images/flower_photos.tgz
tar xzf flower_photos.tgz

This is from the image retraining tutorial for TensorFlow
Results from curling
    % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
    100   127  100   127    0     0    255      0 --:--:-- --:--:-- --:--:--   255

Then when I try to unpack
tar xzf flower_photos.tgz
tar: Unrecognized archive format
tar: Error exit delayed from previous errors.

Hi ammarasmro,
It works perfectly fine for me, I tried the following commands and no errors came out of this.
  curl -O http://download.tensorflow.org/example_../images/flower_photos.tgz
  tar xzf flower_photos.tgz

I don't see where lies the problem.

try this:
 curl -O http://download.tensorflow.org/example_images/flower_photos.tgz
  tar xzf flower_photos.tgz

This will push to the docs early next week as well. Thanks!

@aselle The link is still broken AFAICT.  Did this change get pushed?

Hello
I have the same problem:
curl -O -L http://ftpmirror.gnu.org/autoconf/autoconf-latest.tar.gz
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
100  3428  100  3428    0     0   6359      0 --:--:-- --:--:-- --:--:--  6359
Mac-Pro-di-MAC:swig macpro2014$ tar -xvzf autoconf-latest.tar.gz
tar: Unrecognized archive format
tar: Error exit delayed from previous errors.

I have the same problem too.

I have the same problem. Is there any solution found for this?
tar: Unrecognized archive format
tar: Error exit delayed from previous errors.

@vaijan1990
I just tried the instructions posted on [https://www.tensorflow.org/tutorials/image_retraining](How to Retrain Inception's Final Layer for New Categories)
curl -O http://download.tensorflow.org/example_images/flower_photos.tgz tar xzf flower_photos.tgz
It worked without any problems

flower_photos.tgz 是什么？


chore remove ensure project on top join

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run buildall


test: 💍 changed dropdown test to look for correct class names

👋 Thanks for creating a pull request! 🚀 Checkout the storybook we've created for it: react

@vsjolander I see that Stepper is also changed in the same commit, is this deliberate?

@splashdust Thanks for spotting this. Was not my intent. Reverted these changes.


#0: Fix Falcon40B tests for CI

Re-enable program_cache for all unit tests
Update pytest args for multi-chip CI

@johanna-rock-tt Your recent changes to Falcon pytest parametrizations broke the multi-chip CI. The script that runs these tests are in here: tests/scripts/run_pre_post_commit_regressions_multi_device.sh. Fix is simple, just update the args. I also reenabled all of the use_program_cache fixtures. We shouldn't comment these out, since we want them to be there by default.
Also, are there any new prefill tests (8 chip longer sequence len for example) that we should have in CI? If there are, can you add them to this file tests/scripts/run_pre_post_commit_regressions_multi_device.sh.

Pretty sure my changes will fix the falcon tests (i ran them locally and the syntax is correct now). What's failing (and it seems quite frequently) is the all gather test. It hangs when looped

https://github.com/tenstorrent-metal/tt-metal/actions/runs/8350422784/job/22856773992

Thanks for fixing the test parametrization! I didn't know about that script, but will run/update from now!


ENH: Add polynomial features and extra basis functions to scipy.interpolate.rbf

See section 2.1 of this paper.

Surface plot of sample data with degree = 2:

import numpy as np
from scipy.interpolate import Rbf
from mpl_toolkits.mplot3d import axes3d
import matplotlib.pyplot as plt
from matplotlib import cm

fig = plt.figure()
ax = fig.gca(projection='3d')
X, Y, Z = axes3d.get_test_data(0.05)
X, Y, Z = X[60:100], Y[60:100], Z[60:100]
ax.plot_surface(X, Y, Z, rstride=8, cstride=8, alpha=0.3, color='red')

x = np.linspace(np.min(X), np.max(X), 30)
y = np.linspace(np.min(Y), np.max(Y), 30)
xv, yv = np.meshgrid(x, y)
rbfi = Rbf(X, Y, Z, degree=2)
di = rbfi(xv.flatten(), yv.flatten())
ax.plot_surface(xv, yv, di.reshape(xv.shape[0], xv.shape[1]), rstride=8, cstride=8, alpha=0.5, cmap=cm.coolwarm)
plt.show()

This now needs a rebase, as it crossed with gh-7161.
You can either do a rebase yourself, or grab the rebased branch: https://github.com/ev-br/scipy/commits/pr/7157

It would be helpful to explain a bit what is going on here. Also references should be added to the docstring.
It would also be helpful to explain a connection to the suggestions in
https://github.com/scipy/scipy/issues/4523#issuecomment-74479182.

Oops, something went wrong on the git side. Don't merge master, please rebase on master instead, yhen force-push (the latter is key). Do you need help untangling this?

Yeah @ev-br trying to fix this now, but how do I rebase all the previous commits and keep my latest ones?

You squashed your work into this single commit,  https://github.com/scipy/scipy/pull/7157/commits/dbb346c56d43c9e949d0b24b52e735e61777cca8
Then it's probably easiest to cherry-pick it into a new branch and force-push:
$ git co master
$ git co new-branch
$ git cherry-pick dbb346c56d43c9e949d0b24b52e735e61777cca8
$ git push origin new-branch:rbf-polynomials --force     # assuming your scipy fork is named "origin"

This will replace the the current contents of this PR by that single commit.

Done, thanks! Just couldn't figure out the new-branch:rbf-polynomials part.

@treverhines I just came across your RBF work at https://github.com/treverhines/RBF
I was wondering if you could take a look at this pull-request, and consider whether we could work together to include your existing work into SciPy?
Thanks!

@evanlimanto very sorry for this PR slipping under the radar. I don't think we will be merging this in the end, now that the RBFInterpolator is in. Your work is much appreciated regardless!
What is the status here, is there something from this PR to be ported to the RBFInterpolator interface?  @treverhines @segasai @stefanv @evanlimanto

It would be good to ask @treverhines that question.

Ok, let's close this. If there's something to port to the current RBF framework, we can always reopen or cherry-pick. Thank you very much @evanlimanto , your work is much appreciated regardless!


Allow search based on annotation type

For example, when annotation type (e.g. "rectangle", "arrow","section of interest") is entered, only annotations associated with that type are displayed in the list

Issue moved to informatics-isi-edu/rbk-project #139 via ZenHub.io


[RFC] Pagination in Hybrid query

Introduction
This document talks about the design to support pagination functionality in hybrid query. OpenSearch supports multiple pagination techniques, and this document primarily focuses on two key techniques: the from and size parameters technique and the scroll operation technique.
Problem Statement
Pagination is an ability to divide a large set of search results into smaller subsets, known as pages, and retrieving them one at a time. Currently, hybrid query users cannot navigate in the result set as per their requirements.
Terminologies and key concepts
Here we define the key terms and concepts that are used throughout this document to ensure clarity and consistency in understanding the design approach later.
The from and size parameters
The from parameter is the document number from which you want to start showing the results. The size parameter is the number of results that you want to show. Together, they let you return a subset of the search results.
Scroll operation
It allows users to paginate over large set of data in a single search request. Think of it like a live cursor on a database.
If you need to request volumes of data larger than 1 PB from, for example, a machine learning job, use the scroll operation instead. The scroll operation allows you to request an unlimited number of results.
The important thing to note about the scroll operation is that scoring of the result set is not performed. It deals with large sets of data, and scoring such a large amount of data will lead to system outage.
Understanding search workflow in context of from and size parameters
The search process in OpenSearch for traditional queries executes primarily in two phases: Query Phase and Fetch Phase. The Query Phase is responsible for retrieving the query results from the shard as objects containing docId and score. The maximum number of query results collected during the Query Phase is determined by the sum of from and size parameters provided in the search request. The Fetch Phase is responsible for firstly trimming the topN query results obtained from the Query Phase where topN is equal to the value of  from parameter. The source of the remaining query results are fetched from the shards. By changing the values of from and size params, users can navigate to another page of results.
Current Architecture
Hybrid query workflow
In the current hybrid query workflow, each sub-query executes the search process and returns the from + size equivalent number of results to the co-ordinator node. In the next step, normalization processor combines the sub-query result on each shard by using normalization and score-combination techniques. Later, the Fetch phase will combine all results from the shards and will return the search response. The number of hits present in the search response will be equal to the size parameter sent in the search request. In the entire hybrid query search process, the default value of from is 0.
However, when customized from and size values are sent to retrieve another page of search results, it fails to do so. This failure occurs due to change in ground truth of hybrid query results.

Why ground truth changes when from > 0
Increasing from value will lead to increase in number of results retrieved for each subquery from a shard. Instead of the new results being added to the last page, they tend to appear earlier in the list, which changes the ground truth. This can happen in two scenarios:

The subquery with higher weightage will rank its newly added results above others after the score combination. This means the new entries will appear earlier in the final result set, either on the first few pages or in the middle, instead of being added at the end.
The newly added result can become a duplicate (check appendix section below). The combined score of a duplicate entry after score combination process will be higher thereby increasing the relevance. Here we assumed that the subqueries containing the duplicate result have equal weightage during the score combination process.

Requirements
Functional Requirements

The system must divide large query result sets into manageable pages to ensure efficient data retrieval.
Each page of results should consistently reflect the same underlying data, even when new data is added or updated, to avoid discrepancies when users navigate between pages.
Users should be able to navigate through pages by changing from parameter in the search request.
If the hybrid query returns duplicates from different queries, pagination should manage this to avoid showing the same result multiple times across different pages.
The system should allow dynamic page size configuration, enabling users to choose how many results are shown on each page.

Non Functional Requirements

The system should ensure quick response times for retrieving and rendering each page of results, even when dealing with large datasets from multiple subqueries.

Solution Overview
The proposal is to introduce a new parameter in the hybrid query clause, which will provide information on number of individual sub-query results to be retrieved from the shard. This new parameter will ensure that specified number of subquery results are retrieved, even when from and size values are changed. This process helps in maintaining the consistency by not adding new result entries when from > 0 is sent in the search request. Once the subquery results are retrieved, the rest of the hybrid query process remains unchanged. The from value will navigate to the requested page in the final result, and the size parameter will determine how many search results should be returned in the response.
Why this new parameter can only be added in the hybrid query clause?
Following places have been considered to add this new parameter
Sending it in the URL of the search request
It requires enhancement in SearchSourceBuilder of OpenSearch core to inculcate the changes related to the new parameter. Moreover, there is no use of this new parameter for other traditional query types as they are already supporting pagination functionality. This scope of this change is limited to hybrid query logic, therefore this option is not recommended.
Cluster settings or Index settings
For every hybrid query request, an additional call will be made to the OpenSearch core to get index or cluster settings. This will create overload and resource exhaustion in the cluster. Moreover, customers need to change the setting every time when they want to paginate on higher number of results. Additionally, settings change is captured by event listeners that triggers workflows for other important functionalities in OpenSearch. Therefore, this option is not recommended.
Sending it in the hybrid query clause  [RECOMMENDED]
Adding in the hybrid query clause is recommended because the changes done by the new parameter are specific to hybrid query and do not impact other functionalities of OpenSearch. It helps customers to understand the results formation better by explicitly defining how many subquery results they want to process under hybrid query logic.
Changes in customer experience
The from and size parameters technique
From the customer’s perspective, the new parameter will act as an indicator on how deeply they want to apply hybridization of subquery results and support pagination on top of it.
The following example visualizes the addition of new parameter in the hybrid query clause. The query below retrieves up to 100 results of each subquery and applies normalization process on them. Then it returns the search response that contains 10 hits. The first hit in the response is the 5th entry after combining all the subquery results.
http://localhost:9200/my-nlp-index/_search?size=10&search_pipeline=nlp-search-pipeline

{
 "from":5,
 "query":{
   "hybrid":{
     (Name of the parameter will be finalized in the design doc later)
     "pagination_depth": 100, (new parameter where customer define
                               the depth of hybridization of subquery results they
                               want OpenSearch take the depth as a reference
                               and apply pagination on top of it)
     "queries":[
        "match":{
          "name":"foo"
        }
     ]
   }
 }
}

The new parameter will be referenced as “pagination_depth”  in the rest of document for explanatory purposes. There is open question below for the appropriate name suggestion.
Note: The default value of the pagination_depth will be 0. If the customer doesn’t want to apply pagination and just wants to perform the standard hybrid search, then they do not have to provide the depth information. In that case, the hybrid query will use the current formula of from + size for retrieving the shard results.
The scroll operation
Pagination using scroll api cannot be performed in hybrid query process. The reason being hybrid query needs scoring of documents and scroll api does not support it. The main use case of scroll operation is when users need to reindex the data to a new index. This use case can be easily achieved by any other traditional query. Therefore, an illegal argument exception will be thrown when user tries to apply scroll operation with hybrid query.
High level design
(red arrows == current behavior, green arrows == new flow)

Low level design
The interfaces in the following classes will be updated to inculcate the addition of new parameter.

As there are no component changes in the current hybrid query workflow, therefore flow diagram is not added.
Testability
Backward Compatibility
The changes made to inculcate the new parameter addition are backward compatible. If pagination_depth is not provided in the search request then the current formula of from+size will be used for the subquery results retrieval.
Unit and Integration Tests
Both the test will be added in the PR.
Open questions
Q) Possible names of the new parameter to be added?
Add the suggested names in the following list.

pagination_depth
subquery_results_retrieval_size
pagination_size

Appendix
What is Pagination?
It is a process to divide a large set of search results into smaller subsets, known as pages, and retrieving them one at a time.
There are four different type of pagination techniques supported by OpenSearch:

The from and size parameters : The from parameter is the document number from which you want to start showing the results. The size parameter is the number of results that you want to show. Together, they let you return a subset of the search results.
scroll search : It allows users to paginate over large set of data in a single search request. Think of it like a live cursor on a database.
search after : The search_after parameter provides a live cursor that uses the previous page’s results to obtain the next page’s results. It is similar to the scroll operation in that it is meant to scroll many queries in parallel. You can use search_after only when sorting is applied.
Point in Time with search_after: The search_after search results are not frozen in time, so they may be inconsistent because of concurrent document indexing or deletion. By creating a point in time reference, users can freeze the search results to guarantee the consistency.

To know more about pagination and its techniques, please read the OpenSearch documentation on it.
Duplicates
If a result entry is part of another subquery result set, it is considered a duplicate result.
For example, consider a scenario where a user sends a hybrid query request. The hybrid query contains two subqueries, Subquery A and Subquery B. If the result entry of Subquery A is also part of Subquery B’s results then it is considered a duplicate result.
Unique results
If a result entry is part of only one subquery, it is considered as unique result.

Quite detailed RFC. Waiting for performance benchmarks with new attribute for pagination.

These are exciting developments--also looking forward to seeing the benchmarks.

This is an amazing PR description!

please add more detailed description of pagination_depth parameter, for instance need clearly state that it defines the size of the pagination window in number of documents or hits, not in number of pages.
Another question - can we go above the 10_000 limit with pagination_depth value?

Is there a documentation request/PR for this feature?

haven't found one, feel free to close it if it's a duplicate: https://github.com/opensearch-project/documentation-website/issues/8952


Update longhorn-instance-manager to v1_20220722

Longhorn 4136
Signed-off-by: Derek Su<EMAIL_ADDRESS>

Need to backport to 1.3 and 1.2.


kern from kerning.plist gets ignored if kern feature exists in features.fea

When contextual kerning is added in Glyphs (like explained at https://glyphsapp.com/tutorials/contextual-kerning) ufo2ft only uses that kern and ignores what is in kerning.plist. We want to have both so need to append instead of skip.

thanks Zachary. I will be possible to customize the feature writers with a special UFO.lib element, as proposed here
https://github.com/googlei18n/ufo2ft/pull/178#issuecomment-350042380

Yes, I saw the new feature writer setup. It seems to me that the default mode for KernFeatureWriter should be "append" and not "skip" because that seems more likely, but maybe that's just me.

don't know.. it would be a backward incompatible change to set the default to append instead of skip for KernFeatureWriter.

Ok, that's fine then, but we want "append" for Noto so I guess that's something to add in the build scripts for noto-source?

I'm looking for a way to specify this custom feature writers in the glyphs source files themselves. I'm thinking about a (private) custom parameter that gets exported to the UFO.lib and thus read from ufo2ft.

"append" is now the default behavior of KernFeatureWriter. Users can optionally specify the "skip" mode using the "com.github.googlei18n.ufo2ft.featureWriters" key in the UFO lib, e.g.:
    <key>com.github.googlei18n.ufo2ft.featureWriters</key>
    <array>
        <dict>
            <key>class</key>
            <string>KernFeatureWriter</string>
            <key>options</key>
            <dict>
                <key>mode</key>
                <string>skip</string>
            </dict>
        </dict>
    </array>

or one can also pass a list of featureWriters to the compileOTF and compileTTF functions, which can be either writer classes or be pre-initialized writer instances with custom options:
from ufo2ft.featureWriters import KernFeatureWriter

kernWriter = KernFeatureWriter(mode="skip")
otf = compileOTF(..., featureWriters=[kernWriter])


select all form table pre calculated

Hi! I saw your concatenatedFieldNames and that's exactly what I was thinking about. Then I realize the sequence
"SELECT FIELD1, FIELD2 FROM TABLE" was also constructed several times (findAll, findById, findByForeignId) and couldn't help myself.
Also included some minor changes intellij suggested
If you like it...

Of course I like it!

What do you think about changing the delete method, so it returns true if
deleted something and false if not found? We have the information in the
return of the executeUpdate
On Sat, 26 Mar 2022, 20:43 naynecoder, @.***> wrote:

Merged #6 https://github.com/naynecoder/yorm/pull/6 into main.
—
Reply to this email directly, view it on GitHub
https://github.com/naynecoder/yorm/pull/6#event-6312757343, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMUN253ZBPIBXAYAIEVG7LVB6OLDANCNFSM5RXX7UGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

You are right, that would provide extra information with not much effort, it's an easy win, I'll add an issue about that


Refactor models

Each of these models should have a One to One relationship with Account:

Bank Account
Discount
Tax

Done #85


full screen when incoming call in my device not showing full

hi i have implemented this lib
working fine but what i see is in My MI phone it is not showing callscreen as fullscreen
either locked or minimized only showing alert notification and in oneplus and honor phone working fine
is we have to do anything extra to work it

ok i have solve some issue on the above question
1, added     android:launchMode="singleTask"
android:showWhenLocked="true"
then i dont need to unlock my phone it will open direactly
but still finding about chat can i open or have an option in future to customized it not only for audio video but chat too
one more thing is this library is free or not because i have an option for
headers: <String, dynamic>{'apiKey': 'Abc@123!', 'platform': 'flutter'},
hera why api key little confuse pls help

for some one who didnt find above question answer pls add   isShowLogo: false, for removing callkit title

I had the same issue. after request the fullScreenIntentPermission in the class AndroidFlutterNotificationsPlugin of the flutterLocalNotificationsPlugin now it works.

please update last version for request permisstion full intent screen for android 14+


Type hints

What is the projects stance on implementing type hints according to PEP484?
I would be willing to put in the work if a pull request would be accepted.

Just FYI, this is currently not in scope for me personally anymore, it would definitely still be helpful to have.

I made a pynetbox-stubs package locally:

If we end up using this, I can make it available for everyone.

Ok here you go: https://github.com/sebastian-philipp/pynetbox-stubs . The url is likely to change.

@Kircheneer starting to get this project updated.  If you are interested, please open a PR for this.

@Kircheneer starting to get this project updated. If you are interested, please open a PR for this.

Cool, that's good to hear. As stated above, my focuses have shifted since opening this issue so I will not contribute this in the near future if at all.

I just moved the repo to https://github.com/interdotlink/pynetbox-stubs

Since there is no update on this thread, I'm going to close it for now.


Feature/is booley

implement is_truthy, is_true, is_falsey, is_false.
An observation - surely is_truthy == is_true (per identity of indiscernbiles definition, where the only properties are functional i.e. input -> output)? a Boolean series will only have three truth values: None, False,  and True. If None and False are Falsey, then True is the only truthy value.

yeah just booleans because DataFrame columns are not mixed types, so you would never have a T/F value for a non-boolean column.
I think spark would evalute a non string col as all T/F except for the nulls for the way quinn evaluates, but imo this less strict implementation is undesirable; code that allows for this is more bug prone.
One could argue for implementing Falsey/Truthy like python (None/False/0 is Falsey, everything else pretty much is True). But this is super edge casey (I don't recall how it works with python negative ints for example) and also we would be sort of hammering python's specific, and sometimes unintuitive, truthy/falsey decisions into rust.
I like the walrus operator :3


MAINT: Simplify field-types code

The field-types are somewhat a relict of the dtype discovery
(and the string length discovery which was independent).
Both is gone now, so it is easier to simplify and consolidate the
code.
In the long run (i.e. as part of putting it into NumPy), we should
likely move the parser function onto the DType so that the field
types would be nothing more but a storage for faster access.

I think I considered this before: We could move the converter onto the "field_type" here.  The downsider/problem is that for "homogeneous" columns you would still need to create a field-types struct for every single column (all identical) – except if no converters are used.
Unless there are a huge number of columns, that might actually be pretty nice though, just for simplicity.
Anyway, putting this in, it mostly removes some unnecessary complexity.


[DDW-1099] Update network name and info

This PR implements the following changes:

[x] Network splash/info screen
[x] Network label in the top bar
[ ] Network identifier: itn_rewards_v1 (DEVOPS)
[x] Daedalus icon
[x] Daedalus application name
[x] Daedalus version: 2.0.0-ITN1
[ ] Daedalus state directory (DEVOPS)

Screenshots

Testing Checklist

Slack QA thread
[ ] Test

Review Checklist
Basics

[ ] PR has been assigned and has appropriate labels (feature/bug/chore, release-x.x.x)
[ ] PR is updated to the most recent version of the target branch (and there are no conflicts)
[ ] PR has a good description that summarizes all changes and shows some screenshots or animated GIFs of important UI changes
[ ] CHANGELOG entry has been added to the top of the appropriate section (Features, Fixes, Chores) and is linked to the correct PR on GitHub
[ ] Automated tests: All acceptance and unit tests are passing (yarn test)
[ ] Manual tests (minimum tests should cover newly added feature/fix): App works correctly in development build (yarn dev)
[ ] Manual tests (minimum tests should cover newly added feature/fix): App works correctly in production build (yarn package / CI builds)
[ ] There are no flow errors or warnings (yarn flow:test)
[ ] There are no lint errors or warnings (yarn lint)
[ ] There are no prettier errors or warnings (yarn prettier:check)
[ ] There are no missing translations (running yarn manage:translations produces no changes)
[ ] Text changes are proofread and approved (Jane Wild / Amy Reeve)
[ ] Japanese text changes are proofread and approved (Junko Oda)
[ ] UI changes look good in all themes (Alexander Rukin)
[ ] Storybook works and no stories are broken (yarn storybook)
[ ] In case of dependency changes yarn.lock file is updated

Code Quality

[ ] Important parts of the code are properly commented and documented
[ ] Code is properly typed with flow
[ ] React components are split-up enough to avoid unnecessary re-renderings
[ ] Any code that only works in main process is neatly separated from components

Testing

[ ] New feature/change is covered by acceptance tests
[ ] New feature/change is manually tested and approved by QA team
[ ] All existing acceptance tests are still up-to-date
[ ] New feature/change is covered by Daedalus Testing scenario
[ ] All existing Daedalus Testing scenarios are still up-to-date

After Review

[ ] Merge the PR
[ ] Delete the source branch
[ ] Move the ticket to done column on the YouTrack board
[ ] Update Slack QA thread by marking it with a green checkmark

@disassembler @cleverca22 I need your help with setting up the installers and other DEVOPS things regarding the new itn_rewards_v1 network identifier. I did all I could. Please review my changes and feel free to update this PR. Thanks!


[Close] karma cannot find plugins on Windows 10

Edit: resolved by installing karma-cli globally. Please close.
This issue is happening in all my projects. karma cannot find plugins on my new machine. while node.js can. I am using Windows 10 64x PowerShell.
For this example I will be using angular-seed repo:

cd c:/git
git clone https://github.com/angular/angular-seed.git
cd angular-seed
npm test

Expected behavior
npm test command works fine:

<EMAIL_ADDRESS>test C:\git\angular-seed
karma start karma.conf.js

INFO [karma]: Karma v0.12.37 server started at http://localhost:9876/
INFO [launcher]: Starting browser Chrome
INFO [Chrome 49.0.2623 (Windows 10 0.0.0)]: Connected on socket xBgNZ_H3-JMOs3RFAEjx with id 10297817
Chrome 49.0.2623 (Windows 10 0.0.0): Executed 5 of 5 SUCCESS (0.09 secs / 0.079 secs)

Actual behavior
karma start command doesn't:

C:\git\angular-seed>karma start karma.conf.js
31 03 2016 01:11:11.816:WARN [plugin]: Cannot find plugin "karma-chrome-launcher".
Did you forget to install it ?
npm install karma-chrome-launcher --save-dev
31 03 2016 01:11:11.816:WARN [plugin]: Cannot find plugin "karma-firefox-launcher".
Did you forget to install it ?
npm install karma-firefox-launcher --save-dev
31 03 2016 01:11:11.831:WARN [plugin]: Cannot find plugin "karma-junit-reporter".
Did you forget to install it ?
npm install karma-junit-reporter --save-dev
31 03 2016 01:11:11.909:WARN [karma]: No captured browser, open http://localhost:9876/
31 03 2016 01:11:11.925:INFO [karma]: Karma v0.13.22 server started at http://localhost:9876/
31 03 2016 01:11:11.925:WARN [launcher]: Can not load "Chrome", it is not registered!
Perhaps you are missing some plugin?

How? What? Why? I know I'm not missing any plugins and it is exactly the same command!!
Enviroment Details

Karma version (output of karma --version):

Karma version: 0.13.22

Relevant part of your karma.config.js file:

module.exports = function(config){
  config.set({

    basePath : './',

    files : [
      'app/bower_components/angular/angular.js',
      'app/bower_components/angular-route/angular-route.js',
      'app/bower_components/angular-mocks/angular-mocks.js',
      'app/components/**/*.js',
      'app/view*/**/*.js'
    ],

    autoWatch : true,

    frameworks: ['jasmine'],

    browsers : ['Chrome'],

    plugins : [
            'karma-chrome-launcher',
            'karma-firefox-launcher',
            'karma-jasmine',
            'karma-junit-reporter'
            ],

    junitReporter : {
      outputFile: 'test_out/unit.xml',
      suite: 'unit'
    }

  });
};

Steps to reproduce the behaviour

git clone https://github.com/angular/angular-seed.git
cd angular-seed
karma start

Please help. I've been trying to sort this out for days.

Hi ruslanss,
I had the same problem and got it resolved by installing karma-cli globally.
In my case it's not able to find "Error: No provider for "framework:jasmine"! (Resolving: framework:jasmine)".
I ran the below command after installing 'karma-jasmine'.
npm install -g karma-cli


wire channel query server v2

Description
I have not tested this yet, just putting up the PR in the hopes that the tests pass. If not, I will look into it properly tomorrow 😅
closes: #XXXX

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against the correct branch (see CONTRIBUTING.md).
[ ] Linked to GitHub issue with discussion and accepted design, OR link to spec that describes this work.
[ ] Code follows the module structure standards and Go style guide.
[ ] Wrote unit and integration tests.
[ ] Updated relevant documentation (docs/).
[ ] Added relevant godoc comments.
[ ] Provide a conventional commit message to follow the repository standards.
[ ] Include a descriptive changelog entry when appropriate. This may be left to the discretion of the PR reviewers. (e.g. chores should be omitted from changelog)
[ ] Re-reviewed Files changed in the GitHub PR explorer.
[ ] Review SonarCloud Report in the comment section below once CI passes.

oh, though might need to register it too to in RegisterGRPCGatewayRoutes?

Shit, yes. Added.


Renamed the file to use .md extension

The rate-limiting file was not using the markdown extension, hence added a .md extension to it.

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


Allow development to affect pops

https://forum.paradoxplaza.com/forum/index.php?threads/the-eu4-to-v2-converter-project.707362/page-147#post-19835132
https://forum.paradoxplaza.com/forum/index.php?threads/the-eu4-to-v2-converter-project.707362/page-147#post-19835355
https://forum.paradoxplaza.com/forum/index.php?threads/the-eu4-to-v2-converter-project.707362/page-154#post-19976429
https://forum.paradoxplaza.com/forum/index.php?threads/the-eu4-to-v2-converter-project.707362/page-154#post-19976602
https://forum.paradoxplaza.com/forum/index.php?threads/the-eu4-to-v2-converter-project.707362/page-159#post-20127741
https://forum.paradoxplaza.com/forum/index.php?threads/the-eu4-to-v2-converter-project.707362/page-159#post-20129497
https://forum.paradoxplaza.com/forum/index.php?threads/the-eu4-to-v2-converter-project.707362/page-159#post-20137258

The below only applies to pop shaping which is a problem I would like to fix very much:
Argument that we can take total development of the world, modified by buildings, trade goods, province modifiers, life rating etc, and then determine "population per modified dev point" is wrong. What currently happens with pop shaping on is that a billion people migrate from Asia to Europe since it has better dev and liferating per province, on average, among other factors. As a result we have a Madrid province with 1.2M people and a Gibraltar with almost 100k (up from original 3k).
Also, the argument that we must take vanilla Vic2 population, and then redistribute it according to some key is also wrong - vanilla starting Vic2 population makes sense only in vanilla Vic2 history, and, mind you - not even in eu4-to-vic2 conversions. Different development, different wars, or plagues over those 4 centuries would result in a different total population. Also, EU4 history files alter only a small handful of provinces over time, so for example, one Madrid, Florence or Rome is effectively identical in 1444 and 1821.
To resolve this, and to keep the player satisfied and rewarded for their work, population boosting should indeed occur according to dev investment (ie. playing tall), but again within the limits of reason.
I propose a relatively simple-to-comprehend formula; boost population upwards according to dev investment directly (1 dev investment = 1% population rise), modified by (liferating - 30), so those nice european 35 LR provinces can get 1.05% per dev point, while tundras and deserts get 0.85% per development.
As a result, already large european provinces will get proportionally smaller boosts per mana investiture; a 60-dev Ulm will gain some 40%ish population more on game start but that's it, where a 3-dev fertile plains boosted to 53 dev would get 50%, assuming life rating 30.
This method:

keeps population where they are, simply adjusting the numbers to represent land investments over centuries (mana either goes to war or to development; if latter then the history is less devastating than RL history)
rewards tall players but an investment to get /double/ population is insane as it requires going well over 100 dev per province.

Please comment.

Something like that is the ideal, I think. Maybe initially make it an option, and if it works well it can become the default. Maybe replace the default.


[CMake][NFC] Remove unused logic to choose swift component

add_swift_target_library should always have TARGET_LIBRARY set. A few
lines down, there is a precondition that makes sure that it is set. This
check and subsequent assignment of SWIFTLIB_INSTALL_IN_TARGET should
never get triggered.
cc @compnerd @gottesmm @Rostepher

@swift-ci please smoke test

Can you hoist the precondition check to the top and then remove all references to it?

Can you hoist the precondition check to the top and then remove all references to it?

I can hoist it the precondition but what do you mean "remove all references to it"?

@xiaobai sorry I meant can we just eliminate it? And debride. Sorry I was typing quickly.

@gottesmm do you mean removing the TARGET_LIBRARY option altogether? That would be a much larger change.

@Rostepher - yeah, this was something that @gottesmm and I had chatted about.  The desire is to remove the flag since it should never be used for non-target libraries.  Yes, it is a larger change, but is part of the simplifications that will pay large dividends as we start pruning all the custom handling of build rules.

Yes. Everything that is passed there should have TARGET_LIBRARY set. That means we should debride.

@compnerd I am fine with that. As long as the follow up commit happens.


[AutoPR web/resource-manager] Adding Detector Endpoints for Web Apps and App Service Environments

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/2764

(message created by the CI based on PR content)

Codecov Report

Merging #2295 into restapi_auto_web/resource-manager will increase coverage by 1.85%.
The diff coverage is 26.94%.

@@                          Coverage Diff                          @@
##           restapi_auto_web/resource-manager    #2295      +/-   ##
=====================================================================
+ Coverage                              51.14%   52.99%   +1.85%
=====================================================================
  Files                                   5797     4787    -1010
  Lines                                 154921   119935   -34986
=====================================================================
- Hits                                   79228    63556   -15672
+ Misses                                 75693    56379   -19314

Impacted Files
Coverage Δ

...ure-mgmt-web/azure/mgmt/web/operations/__init__.py
100% <100%> (ø)
:arrow_up:

azure-mgmt-web/azure/mgmt/web/models/__init__.py
100% <100%> (ø)
:arrow_up:

...gmt/web/models/web_site_management_client_enums.py
100% <100%> (ø)
:arrow_up:

...t-web/azure/mgmt/web/web_site_management_client.py
23.45% <100%> (+0.41%)
:arrow_up:

.../operations/resource_health_metadata_operations.py
16.78% <16.78%> (ø)

...-web/azure/mgmt/web/models/error_response_error.py
45.45% <45.45%> (ø)

...zure/mgmt/web/models/data_table_response_object.py
50% <50%> (ø)

azure-mgmt-web/azure/mgmt/web/models/rendering.py
50% <50%> (ø)

...zure/mgmt/web/models/data_table_response_column.py
50% <50%> (ø)

...e-mgmt-web/azure/mgmt/web/models/error_response.py
61.53% <50%> (-2.1%)
:arrow_down:

... and 1857 more

Continue to review full report at Codecov.

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

Conflict


Plugin folder is moved but the path in .chunkwmrc remains the same

Updating using brew - chunkwm stopped working. I looked into the output and here is a print
2018-08-16 18:38:58 ERROR: chunkwm: '/Users/noname/.chunkwm_plugins/border.so' (border.so) is not a valid chunkwm plugin!
objc[1408]: Class OverlayView is implemented in both /Users/noname/.chunkwm_plugins/border.so (0x1036028a0) and /Users/noname/.chunkwm_plugins/tiling.so (0x103629530). One of the two will be used. Which one is undefined.
2018-08-16 18:38:58 ERROR: chunkwm: '/Users/noname/.chunkwm_plugins/tiling.so' (tiling.so) is not a valid chunkwm plugin!
2018-08-16 18:38:58 WARN : chunkwm: plugin '/Users/noname/.chunkwm_plugins/ffm.so' not found..

I haven't installed the ffm.so plugin so don't worry about that one. The one troubling me is that is states that tiling.so, isn't a valid plugin. Im not sure what changed, i used 0.3.6, and i have now updated to 0.4.6.
Updating using brew, states in the install message, that the plugin folder have been moved.
NOTE: plugins folder has been moved to /usr/local/opt/chunkwm/share/chunkwm/plugins

This however is not reflected in the .chunkwmrc file which states that the plugin folder is  ~/.chunkwm_plugins
Should i move the plugins from /usr/local/opt/chunkwm/share/chunkwm/plugins to the folder  ~/.chunkwm_plugins or should i replace the path in .chunkwmrc?
I guess replacing the path in .chunkwmrc makes it easier to update - but it is unclear what the intended purpose of the move is?
[SOLVED]
This was solved replacing the path in .chunkwmrc. However it's not clear if the plugins should be moved into  ~/.chunkwm_plugins or if .chunkwmrc should be edited, also in examples?

The plugin folder has only moved for the Homebrew installation and the example configuration shipped with Homebrew also has this changed path. So yes, change to the (not so) new path.
The change has been made to be more in line with Homebrew guidelines back when we tried to get chunkwm into the Homebrew/core formulae repository. This attempt failed because of the code signing necessity, but the directory was never changed back for Homebrew installations.

Should i move the plugins from /usr/local/opt/chunkwm/share/chunkwm/plugins to the folder ~/.chunkwm_plugins or should i replace the path in .chunkwmrc?

Either option works, but the latter requires you to manually move your plugins after every update, because Homebrew will install them in the new directory.

Alright - I consider this closed then.


typeGen generates some invalid types

Specifically, array types produce the error "array type is too large".

Fixed in an update that will be pushed later.


fix: Issue #928 fixed BUBBLE File commented

Title and Issue number

Title :
Issue No. : #928
Code Stack :
Close #928
Bubble file CSS commented,if needed can be used later.
Type of PR

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

Checklist:

[x] I have performed a self-review of my code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have gone through the  contributing.md file before contributing

Additional context:

[x] I am contributing under GSSOC'24
[cross/X] I am contributing under VSOC'24

@itsekta Please review this PR.

@itsekta @apu52 Please review the changes and merge my PR.

@taniya542 I want to request you to please remove #928 issue from your PR form as well as all the changes u have made regarding that issue in this issue .otherwise I can't merge this PR . Otherwise u can submit a new OR with only the changes of the #915 issue

@apu52 Can I raise a new PR for this?

@apu52 Can I raise a new PR for this,actually when I started working on issue 928 it wasn't assigned to anyone?

yess you can . & if u are submitting a new PE . can I now close this pR??

@apu52 I have made a new PR regarding this issue.Please review it


Context source and destination are null

This works:
Condition<AccountUpdateVM, Account> packets = context -> {
    AccountUpdateVM source = (AccountUpdateVM) context.getParent().getSource();
    return source.getPackets() != null;
};

I have to extract source and destination from parent, because root source and destination are both NULL values.
This doesn't work:
Condition<AccountUpdateVM, Account> packets = context -> {
    AccountUpdateVM source = context.getSource(); // This is null
    return source.getPackets() != null; // This causes null pointer exception
};

My classes are not subclassed, nor they are related to each other.

Can you provide detailed source code for this issue? Thanks.


Check Invariants Hold During Integration Testing

Check the following invariants during the course of an integration test run:

The balance of the totalStake in the emissions keeper should always equal the cosmos-sdk /x/bank balance of the "allorastaking" bank account
The sum of all topicStake in every topic should always equal the totalStake
The sum of all stakeReputerAuthority for a given topic should always equal the topic stake for that topic
The sum of all stakeReputerAuthority should equal the total stake
The stakeSumFromDelegator should always equal the sum of delegatedStakes[topicid, delegator, all reputers for that delegator])
The stakeFromDelegatorsUponReputer should always equal the sum of delegatedStakes[topicid, all delegators for that reputer, reputer]
The sum of all (delegateRewardsPerShare * delegated stake - reward debt) = the balance of the /x/bank AlloraPendingRewardForDelegatorAccountName module account
The state of the stakeRemovalsByBlock and stakeRemovalsByActor should always be identical in terms of the number of keys in the map, and the content of those keys
The sum of all stakeRemovals should always be less than or equal to the totalStake

The invariant checking lives in a file called invariants.go. The cosmos /x/invariants module apparently is not functional at this time so rather than rely on their module, we just edit the ABCI endBlock to check the invariants at the end of every block. This is not perfect, but better than nothing. The code to do that is stored in a patch that is applied in the github workflow via git apply ./test/invariant/invariants.patch

lmao this breaks the unit tests because they abuse the invariants to do testing I'm pretty sure
I'm going to split up the github action unit test again to make it parallelized again

gonna rebase this thing and force push in a minute here


font NotoColorEmoji.ttf getGlyphSet failed: Font contains no outlines

I try to drew emoji image using fonttools.
The font I am using is NotoColorEmoji.ttf by Google.
The font can be loaded, but when I try to get getGlyphSet, it failed:
from fontTools.ttLib import TTFont
font = TTFont('NotoColorEmoji.ttf')
gs = font.getGlyphSet()

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/liudanking/code/dl/pyenv/lib/python2.7/site-packages/fontTools/ttLib/__init__.py", line 695, in getGlyphSet
    raise TTLibError("Font contains no outlines")
fontTools.ttLib.TTLibError: Font contains no outlines

Is there anything I missed?

Currently, only fonts with TrueType glyf table, or with CFF table are supported by the TTFont.getGlyphSet() method. NotoColorEmoji is a CBDT/CBLC color font so has no glyf table.
Sorry.

@anthrotype
Thanks for you quick reply.
Do you have any recommended python package to parse CBDT/CBLC color font?

don't get me wrong. FontTools does support decompiling and compiling CBDT/CBLC color fonts, as well as dumping them as TTX. Have a look at the the ttx -h help, specifically the -z option, it allows you to optionally store the bitmaps as external files with XML references.
it's the TTFont.getGlyphSet() method that does not support color fonts, but only traditional opentype fonts.

ttx -z extfile NotoColorEmoji.ttf.ttf works like a charm.

glad to hear that :)


Generate a mapping value/name in NameMap

We want to refer directly to value in code generation

bors retry

bors retry

bors r+


add proper database migrations

Add proper database migrations for sqlx. I kind of skipped that because this is the first time I worked with a proper database, but this should probably be done long-term to enable database schema changes in the future, if necessary.

added in version 3.8.0


OFBIZ-12900 Have screen FindPartyClassificationGroups show Party MainActionMenu

Currently the FindPartyClassificationGroups screen in PartyClassificationScreens.xml does not show the MainActionMenu of the party component. For a consistent user experience this should be.
modified: PartyClassificationsScreens.xml

added decorator-section 'pre-body', having MainActionMenu

Hi Pierre,
It' s not the real commit title we expect (type missing), but it's OK with me (because it's really trivial)

Hi Jacques,
Thanks for the feedback, but lets not dwell on trivialities.


Formatter removes first “not” from match statements

This change seems quite incorrect 🤔
Originally posted by @auscompgeek in https://github.com/knausj85/knausj_talon/pull/947#discussion_r939609589

@@ -1,3 +1,3 @@
- not tag: user.mouse_grid_showing
+ tag: user.mouse_grid_showing


Tarjan Algorithm in C, C++, Java and Python

Problem= Trajan Algorithm

The problem statement addressed by Trajan's Algorithm is to identify SCCs within a directed graph.
A strongly connected component is a subset of vertices in a graph where every vertex is reachable from every other vertex within the subset.
In simpler terms, an SCC represents a group of nodes that can reach each other through directed paths.

Approach
The approach of Trajan's Algorithm can be summarized as follows:

Start with an empty stack and initialize all nodes as unvisited.
Perform a DFS traversal on each unvisited node in the graph.
Assign a unique identification number to each visited node and push it onto the stack.
Maintain a low-link value for each node, initially set to the identification number.
During the DFS traversal, update the low-link value of a node if a lower identification number is encountered.
When the traversal of a node and its descendants is complete, check if the low-link value of the current node matches its identification number.
If the low-link value matches the identification number, pop nodes from the stack until the current node is reached. The popped nodes form a strongly connected component.
Repeat steps 2-7 until all nodes have been visited.

Attributes :

Will add it in languages like C,C++, Java and Python
Improved Documentation
Plenty commented code that explain the flow and logic of the code

I would like to work on this issue. Can you assign it to me under SSoC '23?
Thank You!!

This algorithm has been implemented in C++
Assigned!
@weirdoo009 : C, Python & Java