Articles for react-mulitcall

I wrote a series of comprehensive articles for anyone strugling to use this library in their application
Part A - Explains what redux-multicall is and why you should use it: https://ajayimike.medium.com/a-guide-to-redux-multicall-building-a-real-time-dapp-part-a-b263b14ac
Part B - A practical guide to setting up redux-multicall for use in your dApp: https://ajayimike.medium.com/a-guide-to-redux-multicall-building-a-real-time-dapp-part-b-e92cccb0f2e6
Part C - Build a simple dApp that shows actual usage of redux-multicall for data fetching in your dApp: https://ajayimike.medium.com/a-guide-to-redux-multicall-building-a-real-time-dapp-part-c-89a9c11eba76

good job!


× Previous node dictated placement (prop testing) (with seed=957474021) unit test fails

One of our randomized tests fails for above seed:
 FAIL  src/components/ComponentBrowser/__tests__/placement.test.ts > Previous node dictated placement (prop testing) (with seed=957474021)
Error: Property failed after 14 tests
{ seed: 957474021, path: "13:8:1:5:2:2:2:4:17:17:17:22:1:1:6:3:1:17:1:7:2:1:17:1:8:17:1:1:17:1:25:9:20:20:18:18:18:18:18:19:29:29:29:29:29:29:29:29:29:17:1:24:1:8:17:1:1:17:1:40:37:37:37:37:37:41:25:9:20:1:1:4:2:3:1:18:1:6:1:18:1:1:1:1:8:1:17:1:8:1:32:17:1:9:17:1:25:9:17:1:29:5:2:1:1:1:17:1:6:1:19:1:1:32:17:1:8:17:1:17:1:29:6:1:18:1:1:1:8:1:17:1:8:1:31:17:1:24:8:17:1:23:1:7:2:17:1:8:1:17:1:38:24:8:17:1:24:1:8:17:1:17:1:38:24:8:24:1:1:38:24:8:31:17:1:31:17:1:47:26:3:1:4:4:3:16:3:3:3:15:27:13:16:13:15:27:13:13:17:13:13:13:27:13:13:17:29:13:14:27:13:27:27:27:37:37:37:37:38:39:37:37:37:38:37:38:37:37:37:37:37:37:37:37:37:37:37:37:37:37:37:1:1:6:14:19:39:39:39:39:39:39:39:39:39:39:39:39:39:39:39:39:40:3:4:3:4:4:4:16:17:16:17:17:17:16:27:27:27:28:30:27:40:3:3:3:7:3:3:3:4:6:6:10:6:6:6:6:8:8:8:8:8:9:10:8:21:3:3:7:3:3:4:7:7:7:11:7:7:9:7:8:8:8:8:8:9:8:22:3:3:3:8:3:3:3:3:6:10:10:7:7:7:7:7:7:13:7:7:8:3:3:8:6:6:6:11:9:7:7:7:12:11:3:9:4:6:12:7:7:9:7:8:3:3:3:11:3:6:6:6:14:6:7:14:9:3:3:12:6:6:15:7:7:8:3:12:6:15:7:7:17:3:15:34:26:12:15:7:17:17:3:4:3:3:3:4:3:3:6:7:6:6:6:7:6:6:8:7:7:7:8:7:7:8", endOnFailure: true }
Counterexample: [{"nodeData":[{"left":124,"top":0,"width":0,"height":25},{"left":0,"top":0,"width":0,"height":0},{"left":149,"top":0,"width":0,"height":25},{"left":0,"top":0,"width":0,"height":0},{"left":0,"top":0,"width":0,"height":0},{"left":0,"top":0,"width":0,"height":25},{"left":0,"top":0,"width":0,"height":0},{"left":0,"top":0,"width":0,"height":0},{"left":0,"top":0,"width":0,"height":0},{"left":0,"top":0,"width":0,"height":0},{"left":0,"top":0,"width":0,"height":0},{"left":0,"top":0,"width":0,"height":0},{"left":0,"top":0,"width":0,"height":0},{"left":0,"top":0,"width":0,"height":0},{"left":0,"top":0,"width":0,"height":0},{"left":0,"top":0,"width":0,"height":0}],"firstSelectedNode":7}]
Shrunk 434 time(s)
Got AssertionError: Please visually inspect the code below at https://play.vuejs.org/:

<template>

</template>
: expected true to be false // Object.is equality
    at /home/adam-praca/dev/enso/app/gui2/src/components/ComponentBrowser/__tests__/placement.test.ts:329:18
    at file:///home/adam-praca/dev/enso/node_modules/@fast-check/vitest/lib/esm/internals/TestBuilder.js:28:79
    at file:///home/adam-praca/dev/enso/node_modules/@fast-check/vitest/lib/esm/internals/TestWithPropRunnerBuilder.js:3:41
    at AsyncProperty.predicate (file:///home/adam-praca/dev/enso/node_modules/fast-check/lib/esm/check/property/AsyncProperty.js:14:59)
    at AsyncProperty.run (file:///home/adam-praca/dev/enso/node_modules/fast-check/lib/esm/check/property/AsyncProperty.generic.js:46:39)
    at asyncRunIt (file:///home/adam-praca/dev/enso/node_modules/fast-check/lib/esm/check/runner/Runner.js:33:36)
    at file:///home/adam-praca/dev/enso/node_modules/@fast-check/vitest/lib/esm/internals/TestWithPropRunnerBuilder.js:22:9
    at runTest (file:///home/adam-praca/dev/enso/node_modules/@vitest/runner/dist/index.js:613:11)
    at runSuite (file:///home/adam-praca/dev/enso/node_modules/@vitest/runner/dist/index.js:732:15)
    at runFiles (file:///home/adam-praca/dev/enso/node_modules/@vitest/runner/dist/index.js:783:5)

Hint: Enable verbose mode in order to have the list of all failing values encountered during the run
 ❯ src/components/ComponentBrowser/__tests__/placement.test.ts:329:18
    327|         )
    328|       },
    329|     } as string).toBe(false)
       |                  ^
    330|   }
    331|   expect(getMousePosition, 'Should not depend on `mousePosition`').not.toHaveBeenCalled()
 ❯ ../../node_modules/@fast-check/vitest/lib/esm/internals/TestBuilder.js:28:79
 ❯ ../../node_modules/@fast-check/vitest/lib/esm/internals/TestWithPropRunnerBuilder.js:3:41
 ❯ AsyncProperty.predicate ../../node_modules/fast-check/lib/esm/check/property/AsyncProperty.js:14:59
 ❯ AsyncProperty.run ../../node_modules/fast-check/lib/esm/check/property/AsyncProperty.generic.js:46:39
 ❯ asyncRunIt ../../node_modules/fast-check/lib/esm/check/runner/Runner.js:33:36
 ❯ ../../node_modules/@fast-check/vitest/lib/esm/internals/TestWithPropRunnerBuilder.js:22:9
 ❯ buildError ../../node_modules/fast-check/lib/esm/check/runner/utils/RunDetailsFormatter.js:126:15
 ❯ asyncThrowIfFailed ../../node_modules/fast-check/lib/esm/check/runner/utils/RunDetailsFormatter.js:143:11

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/1]⎯

 Test Files  1 failed | 19 passed (20)
      Tests  1 failed | 407 passed (408)
   Start at  14:57:08
   Duration  8.88s (transform 1.53s, setup 3ms, collect 10.87s, tests 4.85s, environment 20.26s, prepare 5.75s)

Failing code, for reference:
https://github.com/enso-org/enso/blob/faf8cb715ad04d7a098bcdec932b87faade1de7e/app/gui2/src/components/ComponentBrowser/__tests__/placement.test.ts#L321-L330

if i had to guess, MultiRange probably doesn't allow ranges with 0 width. i wonder if we should allow those (or add an option?), or just adjust the tests instead?

Another failing test and seed:  Non dictated placement (prop testing) (with seed=2110940700)

Another failing test:
https://github.com/enso-org/enso/actions/runs/6819253019/job/18555248433


approvedAt not always set on approved collectives

This was tentatively fixed by https://github.com/opencollective/opencollective-api/pull/2416 but we're still getting such entries.
Right now, we have to run the following query to solve that.
UPDATE "Collectives" c
SET "approvedAt" = '2019-08-21'
WHERE c."isActive" IS TRUE
AND c."type" = 'COLLECTIVE'
AND c."HostCollectiveId" IS NOT NULL
AND c."approvedAt" IS NULL

do you need help here reaching out to host admins?

@piamancini no, there is no need to contact host admins. we just need to make sure this stops happening.


React Router Redirect does not work

After I log in react router should redirect me to x route, But not in my case, here is a code of submit.
handleSubmit(e) {
        e.preventDefault();
        this.setState({
            isSubmitting: true,
        })
        axios.get(`/api/v1/auth/`, {
            params: {
                email: this.state.email,
                password: this.state.password
            }
        })
            .then((response) => {
                if (response.data.token) {
                    localStorage.setItem("Authorization", `Bearer ${response.data.token}`);
                    console.log('Ok Redirecting');
                    <Redirect to="/forum" />
                }
                this.setState({
                    errorOccurred: true,
                    isSubmitting: false,
                    errorMessage: response.data.error
                })
            }).catch(function (error) {
            this.setState({
                errorOccurred: true,
                isSubmitting: false,
                errorMessage: 'Unknow error'
            })
        });

    }

As you can see I expect response.data.token and if everything is ok I would like to redirect the user back to /forum route. I do get console.log'Ok Redirecting' but after that redirection does not take place.
I'm importing only Redirect component from react-router-dom.

This is a bug tracker, not a support system. For usage questions, please use Stack Overflow or Reactiflux. Thanks!


There's a bug wherein repeated calls to create_lbaas_healthmonitor with the same pool param...

Orphans the first n-1 hms.

Maybe someday we'll add expected fails for cases like this?

Handled by bugs and enhancements in agent. (See agent 281 issue.)


Fix fonts when accessing the site over HTTPS

When accessing the site over HTTPS, the browser blocks the insecure request to http://fonts.googleapis.com

Thanks!


Docz cannot "find" custom theme

Bug Report
Describe the bug
I need to have both dark and light versions of the <Playground> component, so I have copied the default theme and made the updates I need. I have updated the doczrc.js config to read like so:
export default {
  theme: 'src/docz-theme-fx',
}

When I run docz in dev mode, I see this error:

ERROR  Failed to compile with 1 errors
This relative module was not found:

* src/docz-theme-fx in ./.docz/app/root.jsx

I then had a look at root.jsx and I can see it has an import statement that references the path that I added to the config, it looks like this:
import Theme from 'src/docz-theme-fx'

As far as I'm aware, this is not valid import syntax if it needs to find that module. So I though I would change the setting to read like this:
export default {
  theme: '../../src/docz-theme-fx',
}

This updated the path in the root.jsx file but the same problem still occurred.
Is there a something else that should be done to get this to work?
@pedronauck I also think that the <Playground> component should have a themeable background so that it can be dark or light.. 🤔
Environment

OS: MacOS 10.13.4
Node/npm version: Node 9.9.0/npm 6.1.0/yarn 1.6.0
Add any other context about the problem here. If applicable, add screenshots to help explain.

@mrmartineau Should it not have a trailing / as it is a folder? Like this
export default {
  theme: '../../src/docz-theme-fx/',
}

That works for me when I point to a custom theme that contains an index.js :)

I think that will only work if the entry point is index.js though, not sure if you will have to actually supply the index name if its a typescript file? Like -
export default {
  theme: '../../src/docz-theme-fx/index.tsx',
}

@Swapnull thanks for your help, but I still cannot get this to work. Neither adding a trailing slash, or the path to the full file works. Should the copy I created need compiling for it to work?

@Swapnull thanks again, but I tried using your version too and it still didn't work. Can you tell me if there's anything else that I should do beyond having the theme within my project and setting the correct path in the config?

Hi @mrmartineau, as you can see in the Theming section on Project configuration, theme filepath need to be relative to your src folder or the root folder of your project...
This is defined in webpack on resolve.modules configuration:
https://github.com/pedronauck/docz/blob/master/packages/docz-core/src/bundlers/webpack/config.ts#L141-L143
So, if you pass a filepath on theme, webpack will search this file on root, src, or node_modules, but just project files will be parsed by loader, node_modules will be rejected!

Hi @pedronauck, I still cannot get this to work... when you mention src above, the docs say to use source instead, is that what you're referring to?
My config is as follows:
export default {
  theme: './src/docz-theme-fx',
  source: './',
}

My project structure is as follows:
. (root)
 - src
   - components
   - docz-theme-fx (this is a copy of the default theme with a few changes)

The value in root.jsx is exactly the same as the value in the config, e.g.
import Theme from 'src/docz-theme-fx'

Can you show me an example of what the above line should look like with a custom theme?

@mrmartineau does it not need to be theme: 'src/docz-theme-fx/src/ ? I thought it had to point to the src file inside the theme, assuming you copied the basic theme?

@Swapnull adding src to the path (like so: theme: 'src/docz-theme-fx/src) was what was needed. Thank you.
I used the non-Typescript version that you created (above) and it is now working, but I had to install recompose and lodash.merge to get it to work fully.
The shame of it is, is that I wanted to update the <Playground> component to have a themeable (or at the very least, a dark background), which I edited, but I realise that while the styles can be modified, no new props can be added to a theme without them being in docz core. @pedronauck am I correct in that assumption? If so, I will look at submitting a PR for it to go into core rather than my theme.
Thanks for your help guys

You can path your own render component like here @mrmartineau
https://github.com/pedronauck/docz/blob/master/packages/docz-theme-default/src/index.tsx#L19


DBAASCLI-73 Refactor cmd files

License check is ok.

License check is ok.

License check is ok.

License check is ok.

License check is ok.

License check is ok.

Tests passed

Tests failed

License check is ok.

Tests passed


Cant output combination of simple options with optgroups

In this case first item will ignored...
const options = [
    {
        id: 1,
        name: 'Product 1'
    },
    {
        category: 'Category',
        products: [
            {
                id: 2,
                name: 'Product 2'
            },
            {
                id: 3,
                name: 'Product 3'
            }
        ]
    }
];

<multiselect v-model="product"
    :options="options"
    group-values="products"
    group-label="category"
    track-by="id"
    label="name">
</multiselect>

<select>
    <option value="1">Product 1</option>
    <optgroup label="Category">
        <option value="2">Product 2</option>
        <option value="3">Product 3</option>
    </optgroup>
</select>

@rorc
Do you mean configuring Multiselect element for the same data as you have for native select? You need to pass group-label and  group-values props to multiselect, for more information see here http://monterail.github.io/vue-multiselect/#sub-option-groups

@pczarn If i pass root element as option, he will ignore...

@rorc If you want to drop the group, then you have to pass flat structure as options:
const options = [
  {
    id: 1,
    name: 'Product 1'
  },
  {
    id: 2,
    name: 'Product 2'
  },
  {
    id: 3,
    name: 'Product 3'
  }
];

@Zip753 I want combine items in root select.

Is option groups available in vue-multiselect 1.x ? our application is written in vue 1 and we cannot migrate to vue 2 right now.


Inselect as a package

setup.py to include dependencies not listed in requirements.txt
setup.py to be aware of dependencies in requirements.win32 and requirements.win64
PyPI

Track PyPI in a separate issue (#357)


Default context menu on IPad shows on top of the VSCode context menu

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.83.0
e7e037083ff4455cf320e344325dacb480062c3c
x64
OS Version: Ubuntu 22.04.3 LTS / IPadOS 17.1 Beta (using code serve-web)

Steps to Reproduce:

Right click anywhere
See the default OS context menu on top of the vscode context menu

I'm not seeing this on https://vscode.dev and I have the same version as you... can you confirm? Do you only see this when using code serve-web? is https://vscode.dev (or https://insiders.vscode.dev) working for you?

I'm seeing it on my self hosted application installed as a shortcut/PWA, when viewing it in the browser, on vscode.dev and on insiders.vscode.dev. Don't really know if there are any settings regarding this that i could change but i've seen it behave properly once in a blue moon. Kind of like the select issue where most of the time you're unable to select/copy text from the editor but very rarely it does work.

Here's what that looks like BTW

Hmm that's so odd... I don't get this "Select All" box at all. Are you right clicking on a tab in this case? Does this repro when you right click in the editor as well?

It happens anytime i click the right mouse button. Really doesn't matter where

Just to rule out any variables, what browser are you using?

On my iPad I use the default safari browser. I doubt the shortcut/PWA uses anything different.

Has anyone gotten a solution to this? Im facing the same issue while working on my Ipad as well.

You can press Escape (and map a key first if your keyboard does not have that key) to dismiss the iPadOS context menu and reveal the VSCode one.

You can press Escape (after first creating a mapping if your keyboard does not have that key) to dismiss the iPadOS context menu and reveal the VSCode one.

Thank you so much!


Postgresql docker compose data migration failure on fresh non-default database

Describe the bug
When running the application through docker compose, receive the following error when trying to run database migrations on fresh, non-default postgresql database.
Error:
ERROR failed to migrate error="strconv.Atoi: parsing \"00_reaction.sql\": invalid syntax\nfailed to convert patch version to int: 00_reaction.sql\ngithub.com/usememos/memos/store.(*Store).getSchemaVersionOfMigrateScript\n\tgithub.com/usememos/memos/store/migrator.go:233\ngithub.com/usememos/memos/store.(*Store).normalizedMigrationHistoryList\n\tgithub.com/usememos/memos/store/migrator.go:272\ngithub.com/usememos/memos/store.(*Store).preMigrate\n\tgithub.com/usememos/memos/store/migrator.go:151\ngithub.com/usememos/memos/store.(*Store).Migrate\n\tgithub.com/usememos/memos/store/migrator.go:37\nmain.init.func1\n\t./main.go:61\ngithub.com/spf13/cobra.(*Command).execute\n\tgithub.com/spf13/cobra@v1.8.1/command.go:989\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\tgithub.com/spf13/cobra@v1.8.1/command.go:1117\ngithub.com/spf13/cobra.(*Command).Execute\n\tgithub.com/spf13/cobra@v1.8.1/command.go:1041\nmain.main\n\t./main.go:171\nruntime.main\n\truntime/proc.go:271\nruntime.goexit\n\truntime/asm_amd64.s:1695\nfailed to get schema version of migrate script\ngithub.com/usememos/memos/store.(*Store).normalizedMigrationHistoryList\n\tgithub.com/usememos/memos/store/migrator.go:274\ngithub.com/usememos/memos/store.(*Store).preMigrate\n\tgithub.com/usememos/memos/store/migrator.go:151\ngithub.com/usememos/memos/store.(*Store).Migrate\n\tgithub.com/usememos/memos/store/migrator.go:37\nmain.init.func1\n\t./main.go:61\ngithub.com/spf13/cobra.(*Command).execute\n\tgithub.com/spf13/cobra@v1.8.1/command.go:989\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\tgithub.com/spf13/cobra@v1.8.1/command.go:1117\ngithub.com/spf13/cobra.(*Command).Execute\n\tgithub.com/spf13/cobra@v1.8.1/command.go:1041\nmain.main\n\t./main.go:171\nruntime.main\n\truntime/proc.go:271\nruntime.goexit\n\truntime/asm_amd64.s:1695\nfailed to normalize migration history list\ngithub.com/usememos/memos/store.(*Store).preMigrate\n\tgithub.com/usememos/memos/store/migrator.go:152\ngithub.com/usememos/memos/store.(*Store).Migrate\n\tgithub.com/usememos/memos/store/migrator.go:37\nmain.init.func1\n\t./main.go:61\ngithub.com/spf13/cobra.(*Command).execute\n\tgithub.com/spf13/cobra@v1.8.1/command.go:989\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\tgithub.com/spf13/cobra@v1.8.1/command.go:1117\ngithub.com/spf13/cobra.(*Command).Execute\n\tgithub.com/spf13/cobra@v1.8.1/command.go:1041\nmain.main\n\t./main.go:171\nruntime.main\n\truntime/proc.go:271\nruntime.goexit\n\truntime/asm_amd64.s:1695\nfailed to pre-migrate\ngithub.com/usememos/memos/store.(*Store).Migrate\n\tgithub.com/usememos/memos/store/migrator.go:38\nmain.init.func1\n\t./main.go:61\ngithub.com/spf13/cobra.(*Command).execute\n\tgithub.com/spf13/cobra@v1.8.1/command.go:989\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\tgithub.com/spf13/cobra@v1.8.1/command.go:1117\ngithub.com/spf13/cobra.(*Command).Execute\n\tgithub.com/spf13/cobra@v1.8.1/command.go:1041\nmain.main\n\t./main.go:171\nruntime.main\n\truntime/proc.go:271\nruntime.goexit\n\truntime/asm_amd64.s:1695"

Migrations seem to run up until v0.20 until they fail trying, it seems, to parse the 00_reaction.sql filename.
Relevant docker compose:
memos:
    image: neosmemo/memos:stable
    container_name: memos
    volumes:
      - memos-data:/var/opt/memos
    environment:
      - MEMOS_DRIVER=postgres
      - MEMOS_DSN=user=memos password=<redacted> dbname=memos host=postgres port=5432 sslmode=disable
    ports:
      - 5230:5230
    depends_on:
      postgres:
        condition: service_healthy
  postgres:
    container_name: postgres
    image: postgres:latest
    restart: always
    shm_size: 128mb
    volumes:
      - pgdata:/var/lib/postgresql/data
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - TZ=${TZ}
      - POSTGRES_USER=postgres
      - POSTGRES_PASSWORD=<redacted>
      - POSTGRES_DB=postgres
    ports:
      - 5432:5432
    healthcheck:
      test: ["CMD-SHELL", "pg_isready", "-d", "postgres", "-U", "postgres"]
      interval: 30s
      timeout: 20s
      retries: 3

Steps to reproduce

Create default postgresql database in docker compose with provided example sql
Connect to created postgres instance and create new user "memos" and database "memos"
Spin up memos instance, check logs and see migrations failure at "00_reaction.sql"

The version of Memos you're using.
v0.22.4
Screenshots or additional context
OS: Ubuntu 24.04 LTS
Docker: docker compose v2.29.1

Duplicate of https://github.com/usememos/memos/issues/3885
See comments for more info


[1.0] Uncaught TypeError: Illegal invocation   from   document.createElement("template", "dom-template").stamp().id

Trying to get or set the "id" field of a stamped dom-template instance throws an Uncaught TypeError: Illegal invocation -- run:
document.createElement("template", "dom-template").stamp().id
or:
document.createElement("template", "dom-template").stamp({id:0})
in the console (I'm in Chrome 43).  Is there something I'm missing in the use of the .stamp() API?

This is expected as implemented.
TemplateInstances returned from Templatizer's stamp method are instances of Polymer.Base, which extends HTMLElement but are not actually created as elements (they are anonymous instances that manage the data-binding for a set of DOM stamped from the template), so touching any properties native to HTMLElement will throw.
As such, you should avoid HTMLElement property names for user properties.


Fix blade comment toggle on regular php files and blade.

I just added .blade

This has been resolved. https://github.com/Medalink/laravel-blade/commit/5a40a48319573148a3ef42f8732e05b0fa3145b4


add NSLocationWhenInUseUsageDescription to parent

There was issue with cordova build command. That occured because of empty parent attribute of NSLocationWhenInUseUsageDescription

Thanks


[staging-20.09] fix plasma

Motivation for this change
related: #98536
since this ended up being 1000+ rebuilds, I didn't want people building against release-20.09 and having to sit through long build queues
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

a little too heavy handed. I came up with another solution


Use regular URL to generated documentation for kubernetes/gen_cert_key.py

Use regular URL (written in Markdown) to generated documentation for kubernetes/gen_cert_key.py

Fixed in https://github.com/RedHatInsights/insights-results-aggregator-utils/pull/257


[ui] fix regex checkbox

Currently, alertmanager cannot update silence matchers' regex property.

@grobie Weren't you already working on this?

Thanks @cofyc. Will be released in v0.4.2


Function to run before scrolling

Hi, the smooth-scroll has a callback function // Function to run AFTER scrolling
I was wondering if would be possible to add a funtion to run BEFORE
Because in so many case, i have a mobile  that fit the screen, and the  has the scroll locked when the  is visible, so would be great to be able to unlock the  scroll before run smoothScroll

No pre-run callback, but... you can use the Smooth Scroll API to do this yourself:
// Listen for clicks
document.addEventListener( 'click', function (event) {

	// Don't run if right-click or command/control + click
	if ( event.button !== 0 || event.metaKey || event.ctrlKey ) return;

	// Check if a smooth scroll link was clicked
	// If using a selector other than [data-scroll], replace the .hasAttribute() check with classList.contains() or .id !== or whatever
	if ( !event.target || event.target.tagName.toLowerCase() !== 'a' || !event.target.hasAttribute( 'data-scroll' ) ) return;

	// Get target
	var anchor = document.querySelector( event.target.hash );
	if ( !anchor ) return;

	// Unlock scrolling

	// Scroll to the anchored content
	smoothScroll.animateScroll( anchor, event.target, {callback: function (){
		// Reenstate scroll lock
	}} );

}, false );

Personally, though, I'm not sure why you would prevent scrolling on mobile devices.

I gave this a bit more thought, and I think a functional hook before animating actually is the right call here. I'll try to get this implemented in the next day or so.

Added to v11 - currently in development and scheduled for release shortly.


ELECTRIC_POTENTIAL_VOLT was used from peacefair_energy, this is a deprecated constant which will be removed in HA Core 2025.1.

日志记录器: homeassistant.const
来源: helpers/deprecation.py:197
首次出现: 05:23:27 (26 次总计出现)
上次记录: 05:23:31
ELECTRIC_POTENTIAL_VOLT was used from peacefair_energy, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfElectricPotential.VOLT instead, please report it to the author of the 'peacefair_energy' custom integration
ELECTRIC_CURRENT_AMPERE was used from peacefair_energy, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfElectricCurrent.AMPERE instead, please report it to the author of the 'peacefair_energy' custom integration
POWER_WATT was used from peacefair_energy, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfPower.WATT instead, please report it to the author of the 'peacefair_energy' custom integration
ENERGY_KILO_WATT_HOUR was used from peacefair_energy, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfEnergy.KILO_WATT_HOUR instead, please report it to the author of the 'peacefair_energy' custom integration
FREQUENCY_HERTZ was used from peacefair_energy, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfFrequency.HERTZ instead, please report it to the author of the 'peacefair_energy' custom integration

Pull requests #24


extended can.List helpers

VOTE HERE
Create an array helpers plugin that adds underscore/lowdash methods to can.List.

:+1:

Voting link appears to be broken, so I'll just toss my +1 in here. Specifically for .some() and .every().

Moving to https://github.com/canjs/can-define/issues/13


Input Groups

Description of issue:

It's common to have different groupings of inputs that might sit side-by-side on desktop, but stacked in mobile. Should the library give better guidance or ship more code that makes this easier?

This is coming from Edwin's presentation on the Library Card app on 12/17.
Component in question (if applicable):

Input

Potentially a flex component that affects layout

Stack component in CPW

Closing in favor of discussions. See here: https://github.com/NYPL/nypl-design-system/discussions/474


Add lower and upper bound support for appropriate variance thresholds

Description

Follow up on #8366 and #8370
Adds lower and upper bound support for appropriate variance thresholds

Tested with the new seed on #8370 (45A0A15704FDEF1F) and additional 500 runs
Related Issues
Resolves #7751

Check List

[x] New functionality includes testing.

[x] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff
[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

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

@reta / @dreamer-89 Please have a look. I updated the check entirely. Should not have anymore edge cases.


Addresses #203

Not as elegant as it might be, but generates a stats.json from a productionised build and opens a browser to the webpack analyser ready for the user to upload.
Needs some instructions output to the terminal on completion...

Coverage remained the same at 99.206% when pulling 1f0acd33c28f9251150ffe60f0124b6204fa0660 on feature/analyze into 681d6fed4e41844f34f74bc2b5836d77e3e8a72e on v3.0.0.

This is good first step, but I'd make this a script and log some output after finishing the build. Can take a look at this!

Just took a look, is there a reason we aren't using https://github.com/chrisbateman/webpack-visualizer?
Since it's a webpack plugin, instead of having to upload a huge JSON file somewhere it generates a visualization .html file one can simply open locally in the browser. I think that's preferable, especially for bigger applications, but I might be missing something?

Well, I'm always looking for ways to avoid thrusting yet another dependency on users, and it's not the actually the case that you upload anything (since the code runs client-side) but mainly it's that it doesn't give the level of insight that the Webpack analyzer gives.

I will say that I've had to setup the project multiple times in the last few days and the npm installs sometimes run ~5minutes at times. Since this isn't exactly a need to have feature, reduced dependencies would be a nice bonus from my point of view.

Fair enough, I'm convinced! I'll add a bit of documentation about this feature in the commands.md and merge it in!

Coverage increased (+0.01%) to 99.218% when pulling 306614cdc9f4e6cde50628b268e1100d88bdb59f on feature/analyze into 64adb5fca0c7a6920a9c2a8a82f50c732a14e2c8 on v3.0.0.

Alright, I think this is ready to merge – I'd appreciate if somebody could try running it on Windows (we should highlight our amazing OS compatibility in the README btw @oliverturner) but I'm 99% sure it works. I gave it nicer output and instead of opening the link in the default browser (which I think only works on OSX) I output the link like so:

I'm aware the keyboard-shortcut-trick only works on OSX in the default terminal, but it's CMD-Click in iTerm so that'll work too and on Windows I'm pretty sure people will figure it out themselves

Coverage remained the same at 99.218% when pulling cb94775054a42583d3bfb6ba41f9854f32c367b5 on feature/analyze into 9ec10b55ae9ff6ea281c3bdac2de39af5019a219 on v3.0.0.


node public config is not syncing properly

On node 73 in Dev net.
Trying to remove public config of a node. it got removed on the chain but graphql still shows the old values. Only the domain level is deleted.
Adding public config with none options to remove it.

Checking the data on the chain. null as expected

but graphql still shows the old values. only the domain is deleted.

Similar thing happens in case of updating a field and removing the other.
Updating only ipv4. so ipv6 and domain should be null.

on the chain

but graphql sill shows the old values

while syncing could the processor check the null values on the chain and set it to the equivalent zero values on the db?

@DylanVerstraete please make sure to create an operational issue

@Omarabdul3ziz Please expand with more details, what environment are you working against ?

it was dev net. updated the original comment

Thanks for reporting, will take a look!

Fixed in v2.9.0-rc6, created an issue to deploy on devnet: https://github.com/threefoldtech/tf_operations/issues/1472

I might need to create a patch version for testnet/mainnet

Verified on devnet.
Node ID 69 public config.

After only changing IPV4 and GW4.

Graphql data was all null except IPV4 and GW4


Snapshots broken on Browserstack

CfA's Browserstack account no longer has API access (I guess it was trialed in?), so our screenshots are no longer working. Need to fix this.
/cc @migurski?

Made a new temp account, which fixes this for now. That’s not a permanent fix, though.

…and free trial 2 is about to expire.

I can charge it to the game and get reimbursed until we have a long term
solution
On Tue, Mar 31, 2015 at 12:17 PM, Rob Brackett<EMAIL_ADDRESS>wrote:

…and free trial 2 is about to expire.
—
Reply to this email directly or view it on GitHub
https://github.com/codeforamerica/snap-it-up/issues/53#issuecomment-88151276
.

--
t:  @alanjosephwilli
p:<PHONE_NUMBER>

I've updated the CfA account—it should now have API access for screenshots. @Mr0grog want to try switching over accounts at your convenience?

Doesn’t appear to be working—it needs to be an “automate” plan.

got it. will upgrade now.
On Tue, Apr 7, 2015 at 9:02 PM, Rob Brackett<EMAIL_ADDRESS>wrote:

Doesn’t appear to be working—it needs to be an “automate” plan.
—
Reply to this email directly or view it on GitHub
https://github.com/codeforamerica/snap-it-up/issues/53#issuecomment-90797138
.

--
t:  @alanjosephwilli
p:<PHONE_NUMBER>

done.
On Wed, Apr 8, 2015 at 5:15 PM, Alan Williams<EMAIL_ADDRESS>wrote:

got it. will upgrade now.
On Tue, Apr 7, 2015 at 9:02 PM, Rob Brackett<EMAIL_ADDRESS>wrote:

Doesn’t appear to be working—it needs to be an “automate” plan.
—
Reply to this email directly or view it on GitHub
https://github.com/codeforamerica/snap-it-up/issues/53#issuecomment-90797138
.

--
t:  @alanjosephwilli
p:<PHONE_NUMBER>

--
t:  @alanjosephwilli
p:<PHONE_NUMBER>

Updated in prod and works.


Channel tree items on 4K monitors

Apparently, there is an issue with 4K monitors where the space reserved for tree items is too small.
I suspect it has something to do with line height but I didn't look into it yet. Since I don't have a 4K monitor, this may be hard to test.

This issue has been reported by @wee-zr via Telegram since he was too lazy to open a GitHub issue.


⚠ jaswdr.dev has degraded performance

In cc079da, jaswdr.dev (https://jaswdr.dev/) experienced degraded performance:

HTTP code: 200
Response time: 734 ms

Resolved: jaswdr.dev performance has improved in aa3f461.


Upscaling base on canvas smoothing is not great.

The current scaling method, relying on the browser canvas, is not great.
The main issue is that the interpolation is based on the 8 bit clamped data after window levelling. This issue is clearly illustrated on the following image. The first sample is directly from cornerstone, the second in GIMP linear interpolation implementation on the same data at a similar zoom factor, the last one shows linear interpolation implemented in JS on the full 16-bit data before window levelling.

The JS implementation that is most "correct", but it is slower.. The GIMP version also looks a bit better in my eyes.. I don't know why.

This issue is also present in another commercial software:

They have two renderers, one  based on WebGL on the left and the other based on canvas on the right.
The WebGL one is fine while the Canvas implementation shows the same interpolation issue.
I didn't test it lately, but as far as I remember, our WebGL backend would not fix this issue as it renders the image to its original size without any interpolation, not the viewport size.
Furthermore, if I remember correctly, our WevGL implementation pack the 16-bit data into two 8-bit channels which prevents us from using the built-in interpolation. We would need to switch to Float32
(thus doubling the VRAM requirements) or implement interpolation ourselves in shaders.
In any cases, changing the rendering from whole images to viewports in cornerstone would break most tools and require significant changes.

This makes sense, that the interpolation on a wider range gives better results. I suppose this isn't something that was noticed before because people don't zoom/upscale to such a level with lower resolution images? It would be interesting to know what level a clinical personal (rad) would zoom a CT to. TBD

Hi @jpambrun, it's been some time since this issue was created. Do you have any additional thoughts/guidance on this issue?

The only way to get around this issue it to do interpolation in javascript or webgl before the VOI lut is applied. The performance cost of doing so in JS is significant especially for handheld devices.
I would leave this issue open since it comes up every so often, but I would not try to solve it without making webgl a hard requirement.

if render in webgl mode, can  to do interpolation now?

@DMIAOCHEN, to my knowledge, this has not been resolved. We marked it as low priority because most images should be viewed in near-native resolution. You can also turn off the native canvas interpolation/smoothing by changing the pixelReplication value on the viewport

I think it's pretty common to view images with large scaling factors, 256x256 MR images immediately come to mind as that would be less that 1 inch on any retina type display.
Fixing the issue would require significant rework of the rendering pipeline; it will likely come when/if vtk.js is adopted for rendering.

If you interpolate with webgl, does it mean that the canvas coordinate system transformation is not applicable, canvas scale value will allway 1.0, and does this have a big impact on the annotation tools

The current webgl implementation only helps speed up the VOI lut computation. It does not do any affine transformations.
It would be possible to shift the affine transformation to webgl, yes, but this is the significant development (and most importantly testing) effort that I was referring to. Given the effort put into vtk.js, I think that any effort to improve the current extremely limited bespoke webgl implementing wasteful.

It seems that really a lot of work to do it 😳


Remove multiprocessing from GlobalVariables and make it a script parameter

Leaving it in GlobalVariables has some drawbacks: Often, when developing a new feature, this variable gets set to False and can sometimes end up in production because of this.

with PR #554 , this would then become a global parameter to the cea tool

this should be read from the cascading config files as well. and then be a top-level parameter to the cea command (much like --scenario)


Updates to channel priority queue

Rename interface and modify method signatures to not confuse with more general priority queue implementation

Coverage decreased (-0.4%) to 66.819% when pulling e84d1499716d305b92b41ac507d38890fea1e4d8 on shreyassrivatsan:pri into 78a3cd128951ab024c210af934d14d75ff9af4dc on uber:master.


Attempt for packaging 3.0.0

@conda-forge-admin , please rerender

Checklist

[X] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[X] Reset the build number to 0 (if the version changed)
[X] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[X] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

Converting to draft to avoid accidental merging.
We don’t really publish rcs. (Well you can but the process is more complicated than one would want)
good to know that this works!!!!

could deploy conda-forge packages relatively smoothly

awesome thanks for your support!

FWIW, after not requiring numpy 2.0, the Python 3.13 builds are complaining:
The following packages are incompatible
├─ numpy =1.26 * is installable with the potential options
│  ├─ numpy [1.26.0|1.26.2|1.26.3|1.26.4] would require
│  │  └─ python_abi ==3.9 *_pypy39_pp73, which requires
│  │     └─ python =3.9 *_73_pypy, which can be installed;
│  ├─ numpy [1.26.0|1.26.2|1.26.3|1.26.4] would require
│  │  └─ python >=3.10,<3.11.0a0 *, which can be installed;
│  ├─ numpy [1.26.0|1.26.2|1.26.3|1.26.4] would require
│  │  └─ python >=3.11,<3.12.0a0 *, which can be installed;
│  ├─ numpy [1.26.0|1.26.2|1.26.3|1.26.4] would require
│  │  └─ python_abi =3.12 *_cp312, which requires
│  │     └─ python =3.12 *_cpython, which can be installed;
│  └─ numpy [1.26.0|1.26.2|1.26.3|1.26.4] would require
│     └─ python >=3.9,<3.10.0a0 *, which can be installed;
└─ python =3.13 *_cp313 is not installable because there are no viable options
   ├─ python [3.13.0|3.13.1] conflicts with any installable versions previously reported;
   └─ python [3.13.0rc1|3.13.0rc2|3.13.0rc3] would require
      └─ _python_rc =* *, which does not exist (perhaps a missing channel).

FWIW, after not requiring numpy 2.0, the Python 3.13 builds are complaining:
The following packages are incompatible
├─ numpy =1.26 * is installable with the potential options
│  ├─ numpy [1.26.0|1.26.2|1.26.3|1.26.4] would require
│  │  └─ python_abi ==3.9 *_pypy39_pp73, which requires
│  │     └─ python =3.9 *_73_pypy, which can be installed;
│  ├─ numpy [1.26.0|1.26.2|1.26.3|1.26.4] would require
│  │  └─ python >=3.10,<3.11.0a0 *, which can be installed;
│  ├─ numpy [1.26.0|1.26.2|1.26.3|1.26.4] would require
│  │  └─ python >=3.11,<3.12.0a0 *, which can be installed;
│  ├─ numpy [1.26.0|1.26.2|1.26.3|1.26.4] would require
│  │  └─ python_abi =3.12 *_cp312, which requires
│  │     └─ python =3.12 *_cpython, which can be installed;
│  └─ numpy [1.26.0|1.26.2|1.26.3|1.26.4] would require
│     └─ python >=3.9,<3.10.0a0 *, which can be installed;
└─ python =3.13 *_cp313 is not installable because there are no viable options
   ├─ python [3.13.0|3.13.1] conflicts with any installable versions previously reported;
   └─ python [3.13.0rc1|3.13.0rc2|3.13.0rc3] would require
      └─ _python_rc =* *, which does not exist (perhaps a missing channel).

Any hint @goanpeca, @hmaarrfk ?

@conda-forge-admin please rerender

Hi! This is the friendly automated conda-forge-webservice.
I tried to rerender for you, but it looks like there was nothing to do.
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12300983892. Examine the logs at this URL for more detail.

lets try to build for other architecture.

Hi! This is the friendly conda-forge automerge bot!
I considered the following status checks when analyzing this PR:

linter: passed
azure: passed

Thus the PR was passing and merged! Have a great day!

thanks for the help! I built for arm + apple arm! too!

Ok. I tried this on my MacBook M1, but I am getting this error:
> conda install -c conda-forge python-blosc2                   (python-blosc2)
Channels:
 - conda-forge
 - defaults
Platform: osx-arm64
Collecting package metadata (repodata.json): done
Solving environment: failed

PackagesNotFoundError: The following packages are not available from current channels:

  - python-blosc2

Current channels:

  - https://conda.anaconda.org/conda-forge
  - defaults

Am I missing something?

Can you try again? Sometimes it takes time for the cloud to sync up

Am I not a maintainer on this already?
I guess I’m not.
But sure. Happy to help blocs


Allow feeding masonry from an externally event loop.

This allows for running masonry with an externally managed event loop for integrating with an application that is already running an event loop.

Expose PointerState to allow creating PointerEvent
Expose WindowEvent to allow managing window size and scale factor.
Make DriverCtx usable from outside the crate. While this struct was already pub, the sole member of it was not.

I think there are going to be better ways to integrate other event loops in the future, but so far, this is the bare minimum for me to get parts of masonry usable from an application that is already running and driving a winit event loop.

I've added a comment and a #[doc(hidden)]. Re-approve and I'll land it when I'm awake.


Test branch9

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


Updating project URLs, adding Distribution project to sandbox

Data updates; pre-submission checklist N/A.
Pre-submission checklist:
Please check each of these after submitting your pull request:

[ ] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[ ] Is your project closed source or, if it is open source, does your project have at least 300 GitHub stars?
[ ] Have you picked the single best (existing) category for your project?
[ ] Does it follow the other guidelines from the new entries section?
[ ] Have you added your SVG to hosted_logos and referenced it there?
[ ] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[ ] Does your project/product name match the text on the logo?
[ ] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[x] ~30 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

deploy preview checks:

[x] dex url
[x] notary url
[x] bfe url
[x] distribution correctly in sandbox

/lgtm

force push updates Longhorn project URL

preview check:

[x] longhorn url

last force push updates parsec URL

preview check:

[x] parsec url

last force push updates

[ ] Chaos mesh
[ ] Chaosblade
[ ] CNI-genie
[ ] Container Network Interface (CNI)
[ ] Cortex
[ ] etcd
[ ] Fonio
[ ] Kube-OVN
[ ] Skooner
[ ] Trickster
[ ] Virtual Kubelet

Fonio has an odd URL: https://ingraind.org/ it looks correct as per their github repo, but probably worth bringing up.

@nate-double-u fonio needs to be updated for sure and finished onboarded
We also need to ensure there are 'accepted:'  metadata for each project


Storefront UNA Account Login Error

From Studio, I press + and it brings me to the Store.php storefront. It says I need to login to my UNA account to get data.
YOU NEED TO TO LOGIN INTO YOUR UNA ACCOUNT TO GET DATA. CLICK HERE TO LOGIN.
When I press the link, it says:
THE REDIRECT URI PROVIDED IS MISSING OR DOES NOT MATCH
At the link:
https://una.io/m/oauth2/auth?response_type=code&client_id=sbj4x6hnar&redirect_uri=http://example.com/una/studio/store.php?page=goodies&scope=market&state=y6rBYgP2NijAEn5r79Qx
To me, it appears that redirect_uri should be redirect_url, so I tried it out and it brings me to a site that asks: Choose profile to use on "testKey" site:
When I select my profile it says: METHOD(ACTIONWWW.EXAMPLE.COM) WAS NOT FOUND IN MODULE(OAUTH2)
Is this a bug?

Could you please provide you UNA.io key ? or your site domain ?

Hi Alex. I was not sure if I should keep my UNA.io key private or not. Is it good practice to keep it private, or does it not matter? My site domain is www.keywebspace.com/una.

I was not sure if I should keep my UNA.io key private or not.

UNA.io "key" can be public, UNA.io secret - must be keep private.

if I should create issues for questions and bugs here?

it's better to report bugs in una.io forum, then if it's confirmed someone from UNA team can create an issue.

When I go to the New Post page, at the bottom of the Text box there is a letter p. If I click the letter p

It's ok, it just shows that you are currently typing text in  HTML tag.


Resolve extremely occasional inout codegen ordering problem

CoreIR does not assume that connections are deterministically ordered (i.e. conn.first and conn.second do not always match the JSON).  This resulted in the very occasional test failures for the inout code generation logic (which assumed this was always a deterministic relationship).  This adds a fix to make sure the output is deterministic.
I was able to consistently reproduce the issue with 15 test runs of the intermediate connection test: https://github.com/rdaly525/coreir/commit/434163e44f2b3f4878c8326380399d8721928500
verified it resolved the issue with the same test setup: https://github.com/rdaly525/coreir/commit/eec74dca23169e5189e2f338163de5ea9d35ad20
then i removed the repeated tests so our test suite doesn't take too long: https://github.com/rdaly525/coreir/commit/c4542de32bcc6a9263d15b5d3ef150290e7181ea

Here's the example failure: https://travis-ci.org/github/rdaly525/coreir/jobs/682147080


Repo sync for protected CLA branch

The pull request is created from master637383811852781344 to master to fix git push error for protected CLA branch

@Taojunshen : Thanks for your contribution! The author(s) have been notified to review your proposed change.


[BUG] REST should use data connector config instead of builder config

What is the bug?
currently the REST configuration is done inside the builder,
Steps to reproduce the bug

What is the expected result?
It should be configured inside the connector!
Version
No response
Cluster version
No response
What else should we know?
No response

Pull data only
Single REST end point
devOps implemented request parser
No authentication
Part of this task is defining the devOps-facing YAML


Assure JDK 12 compatibility

Under JDK12 we get at least this runtime error:
<pre>java.lang.IncompatibleClassChangeError: Method 'org.apache.lucene.index.Term querqy.lucene.LuceneQueryUtil.toLuceneTerm(java.lang.String, java.lang.CharSequence, boolean)' must be Methodref constant
when using the ClassicWordBreakCompoundRewriter (which should be removed in Querqy 5 in favour of the WordBreakCompoundRewriter).

We should still support JDK 8 in accordance with Solr Java version requirements ( https://lucene.apache.org/solr/guide/8_6/solr-system-requirements.html)

This looks more like a dependency issue, possibly with different versions of Lucene in the classpath. Happy to support debugging if this is still an issue.

Thank you @mkr - this might indeed explain this concrete case. It happened when multiple integration tests were run in an undefined order and it looked that some of them left the setup in an unstable state.
However, as we are building Querqy using JDK 8 with Java 8 as the target version, I wonder how sure we can be that it runs fine under Java 12. What I have in mind is setting up GitHub actions for many different environments (Java/Solr versions) and run a few integration tests that way. As I'm not an expert enough in this field to set this up quickly, if someone else could take the lead and try to set this up it would be a great help and provide an even more robust testing for Querqy.

Fixed via #141


Add support for double sharps/flats in figures

Harmony and Voice Leading (Aldwell & Schachter), page 597:

LGTM, but see comment.  Thanks!


Edit TileSet source on double click

https://github.com/godotengine/godot-proposals/issues/1769#issuecomment-1021761356
https://github.com/godotengine/godot/assets/2223172/d049c555-4eb7-48cb-9944-cee1cd4d68b8
If you are wondering about the local cpp singletons, they aren't needed anywhere else, so there is no reason to add proper get_singleton() methods right now.

Thanks!


Filtering fixed maybe

Use filteredStudents array instead of allStudents, because filteredStudents contains all students when filters are disabled. I'm pretty sure this doesn't break anything but I could be wrong

lgtm 👍


Support multi path payments

Description:
Adds support for multi path payments. If we fail to find a direct route when probing, we fall back to calling sendPayment. This PR leverages sendPaymentV2 for lnd 0.10.0 with MPP enabled. Also converts send payment error codes to user friendly messages.
Motivation and Context:
Add support for multi path payments
How Has This Been Tested?
Manually
Types of changes:
Feature
Checklist:

[x] My code follows the code style of this project.
[x] I have reviewed and updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes where needed.
[ ] All new and existing tests passed.
[ ] My commits have been squashed into a concise set of changes.

Coverage decreased (-0.02%) to 22.258% when pulling 243c4cbf94094e8cbd61771aa38cfb4c6f9469a7 on mrfelton:feat/mpp into 834645025cb83e95ed3de5c04076d6cf534bb5c6 on LN-Zap:master.


Fix compiler issues

@jprotze I am closing this PR because I merged your changes with the branch "update_to_60".

@simoatze I tested this modification and don't get the error about the missing file for parallel builds. I pushed the change to update_to_60.


Fix a false positive for Rails/NotNullColumn when adding a :json columns

When adding a json column, Rails/NotNullColumn is notified, but according to the documentation, a default value cannot be set for a json column.

The BLOB, TEXT, GEOMETRY, and JSON data types cannot be assigned a default value.

Fix to pass cop when adding json columns.
Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.
[x] If this is a new cop, consider making a corresponding update to the Rails Style Guide.

This is a MySQL-specific rule. For example, PostgreSQL allows default values for JSON and TEXT.

@vlad-pisanov
It seems so. I apologize for the lack of confirmation. I'm closing this PR.


Improve tracking of need for Metal visibility buffer in Metal renderpasses

The current logic around deciding whether a visibility buffer is needed is relatively crude. Currently, it is applied to all render passes in a Vulkan command buffer based on at least one occlusion query being present. A Metal renderpass needs a visibility buffer if a query is started either before it or inside it. For a command buffer with multiple Metal render passes, not all of them may need it.
Recommended logic:

Track need for visibility buffer in MVKCmdBeginRenderPass and MVKCmdNextSubpass.
MVKCommandBuffer track when MVKCmdBeginRenderPass or MVKCmdNextSubpass added and set it's _needsVisibilityResultMTLBuffer from MVKCommandBuffer:: _isOcclusionQueryOpen.
Adding, MVKCmdBeginQuery sets MVKCommandBuffer::_isOcclusionQueryOpen and if a MVKCmdBeginRenderPass or MVKCmdNextSubpass is open, set its _needsVisibilityResultMTLBuffer too.
Adding MVKCmdEndQuery sets MVKCommandBuffer:: _isOcclusionQueryOpen to false.
Adding MVKCmdEndRenderPass clears open render/sub pass in MVKCommandBuffer.

I performed some further analysis and experimentation. Additional requirements:

Vulkan secondary command buffers may contain queries that affect an open begin renderpass command in the primary buffer, and _needsVisibilityResultMTLBuffer is set in any of the secondary command buffers.
MVKCommandEncoder:: _needsVisibilityResultMTLBuffer status set by encoding of MVKBeginRenderpassandMVKNextSubpass`.
MVKCommandEncoder:: _needsVisibilityResultMTLBuffer status used in beginMetalRenderPass() to determine whether visibility buffer should be used.
Metal renderpass iterations used for Vulkan multi view rendering should not change any flags, but should honor value of MVKCommandEncoder:: _needsVisibilityResultMTLBuffer.

Since a full solution appears to be necessarily complex, and the benefits of the improvement are unclear (assumed to be some type of undefined performance improvement), at this point, further work on this is being left until a definite need arises.


add new state to clear disk after reboots

unit test is bad - code tested with itself, using private method.
reimplemented and committed under your name

I really dont understand why you had removed the clearDisk, and what are
you supposed to do when adding new server, as we had agreed that when
adding complerely new server to rackattack we will erase the disk
On Sun, Jan 11, 2015 at 1:29 PM, shlomi-stratoscale <
<EMAIL_ADDRESS>wrote:

unit test is bad - code tested with itself, using private method.
reimplemented and committed under your name
—
Reply to this email directly or view it on GitHub
https://github.com/Stratoscale/rackattack-virtual/pull/2#issuecomment-69491223
.

--
Thanks,
Sasha.


added throttling to mousemove and cordinate change functionality

check the return value of theta from "cartesianToPolar" helper function

the return value of angel has ben norma;lized with helper function


Update to work with Next 12

So this doesn't work with next 12?

It seems like next/image is throwing a warning because the width query parameter is not implemented in the returned URL for the image. This has to do with @sanity/image-url mapping the width parameter to be the shorthand w: https://github.com/sanity-io/image-url/blob/main/src/urlForImage.ts#L14. I'll see what i can do about this.
Apart from this the library seems to work fine with Next.js 12, or did you guys encounter any other issue while upgrading?

I've just released version 3.1.8 which solves this warning and includes the PR from @elmarburke which adds Next.js ^ 12.0.0 as a peer dependency. If there are any additional problems feel free to open another issue.


Add download_status attribute for feeds

Just a quick experiment to see if this works for https://github.com/newsboat/newsboat/issues/2791#issuecomment-2213805073
This is not a full solution to https://github.com/newsboat/newsboat/issues/2791
Example config option (press f to select the defined filter):
define-filter "feeds - unread and/or error" "unread_count > 0 or download_status = \"x\""

This filter does work but it might break easy usage of toggle-show-read-feeds (has no visible effect as long as the filter is active)

coverage: 60.704% (-0.004%) from 60.708%
when pulling ffb77e9ca18e0224b0bb6fc65e425184b2bdd8b3 on dennisschagt:download-status-attribute
into 2ffe84178ef867a944a6c54a0d9f509d623ea4b7 on newsboat:master.


Add test to reach 100% coverage

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@07356f6). Click here to learn what that means.
The diff coverage is 75%.

@@            Coverage Diff            @@
##             master    #1260   +/-   ##
=========================================
  Coverage          ?   36.06%
=========================================
  Files             ?       31
  Lines             ?     2351
  Branches          ?       90
=========================================
  Hits              ?      848
  Misses            ?     1485
  Partials          ?       18

Impacted Files
Coverage Δ

tests/test_dcos_e2e/backends/aws/test_aws.py
84.21% <75%> (ø)

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 07356f6...4fa1649. Read the comment docs.


Height in Dialog as Panel

Hi all,
I am displaying a Dialog as a Panel, but the height of the tab content is not displayed correctly.
When a grid is used and then a Dialog is opened as a panel then it does display correctly.
Can you help me?

check this : https://github.com/volkanceylan/Serenity/issues/1882#issuecomment-278366036

check this : #1882 (comment)

Thanks for the reply but it doesn't work for what I want.

in file css : ...\Content\site\site.css i find CSS for height Panel for Module Northwind Customer Dialog Panel
.s-Northwind-OrderDialog.s-Panel,
.s-Northwind-CustomerOrderDialog.s-Panel {
  min-height: 750px;
}

so you need to add min-height: 750px; to class css  .s-Dialog, .s-Panel

Hello, the file ...\Content\ site\site.css should not be modified manually because it is generated automatically when the project is compiled.
On the other hand 750px is a static value, it is not suitable for all screens.

but it works for me, I add min-height: 750px; and i test for all screens, everything is fine.
and for all screens the default value min-heigh in serenity is 750px.

If it works for you, I'm happy for you.
Can you tell where it is set that in Serenity the min-heigh is 750px?

@ArsenioInojosa ,
if min-height: 750px does not work for you, then you need to calculate the necessary min-height dynamically after the dom is fully loaded, by

querying the height of the diverse involved dom elements with javascript - parent dom element, all other sibling elements
calculate the min-height by doing height of parent minus height of all other sibling elements
set min-height of your s-panel css  via javascript to the value which you got with (2)

With kind regards,
John

Closed without solution.


RequirementMachine: Protocol requirement signature minimization fixes

With these changes, more validation tests pass with -requirement-machine-protocol-signatures=verify.
There were a couple of highly-invalid cases where the requirement machine's result was more "correct", so I hacked the GSB just to make a few tests pass. If these GSB changes cause some unforseen breakage, they can be reverted separately without issue.
Also, a couple of optimizations to the homotopy reduction algorithm. It's still too slow.

@swift-ci Please smoke test

@swift-ci Please test source compatibility

@swift-ci Please smoke test

@swift-ci Please test source compatibility

@swift-ci Please smoke test

@swift-ci Please test source compatibility

@swift-ci Please smoke test Linux


Prevent flickers for already loaded images.

Large single-page apps, like Ember, will sometimes rerender the same element with the same image. This can cause lots of flickering with lazyload.
Also, an image reused throughout the page (say, an avatar) fades in every single time, which can make for a jumpy experience (esp. if a rerender is triggered).
Last, the start of the animation is hardwired to hide(), which unnecessarily causes page reflow issues even when the dimensions are known.
To fix this, settings.effect accepts a function, which defaults to a noop (preventing flickering for folks without any effect specified), and the effects are never run if the image is already cached. If settings.effect is a string, it gets converted to a function as before, so it should be backwards compatible.
For my specific use case, this lets me just use $el.css({opacity: 0}).animate({opacity: 1}); as my effect, which doesn't cause a page reflow or flicker.
Tested in Firefox and Chrome.
Easier to see relevant changes with the ?w=1 flag.

Related, this closes https://github.com/tuupola/jquery_lazyload/pull/161

👍


GPG Signing Key expired 2021-12-17

Failed to fetch http://nuitka.net/deb/stable/bionic/dists/bionic/InRelease  The following signatures were invalid: EXPKEYSIG 1BFC33752912B99C Kay Hayen<EMAIL_ADDRESS>Hi,
Your Debian/Ubuntu Signing Key has expired.
Thanks :+1:

I have a new one, just need to figure out where to put it again

Ok, I got the signature extended, I think reprepro copies it, not sure now, if maybe it expired in the mean time, I was noticing it when preparing a hotfix.

It seems, bionic was built on 16.12, i.e. when the key was still valid, so this will be fixed on rebuild. I will trigger one to see if it helps.

The key changed from the rebuild, so I assume all it takes is a hotfix to come. I will trigger a rebuild the stable debian packages manually though, as it might not happen so soon.

HI, still shows as expired.
wget -O - http://nuitka.net/deb/archive.key.gpg | gpg

I saw it, I wonder why it's used, isn't the directories below there independent repos?

I get it, the website uses it in the instructions. I forgot. I updated it to what it ought to be, my relevant CI server is in maintenance, but website should soon point out proper per distribution keys

Now reads wget -O - http://nuitka.net/deb/stable/$CODENAME/dists/$CODENAME/Release.gpg | apt-key add -

it may be me, or things haven't updated yet. (Website still has old instructions).
`wget -O - http://nuitka.net/deb/stable/bionic/dists/bionic/Release.gpg | apt-key add -
--2021-12-22 19:46:01--  http://nuitka.net/deb/stable/bionic/dists/bionic/Release.gpg
Resolving nuitka.net (nuitka.net)... <IP_ADDRESS>, 64:ff9b::74ca:1ebc
Connecting to nuitka.net (nuitka.net)|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://nuitka.net/deb/stable/bionic/dists/bionic/Release.gpg [following]
--2021-12-22 19:46:02--  https://nuitka.net/deb/stable/bionic/dists/bionic/Release.gpg
Connecting to nuitka.net (nuitka.net)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 833
Saving to: ‘STDOUT’

                                                      100%[==========================================================================================================================================>]     833  --.-KB/s    in 0s

2021-12-22 19:46:04 (23.3 MB/s) - written to stdout [833/833]
gpg: no valid OpenPGP data found.`
`wget -O - http://nuitka.net/deb/stable/bionic/dists/bionic/Release.gpg | gpg
--2021-12-22 19:46:38--  http://nuitka.net/deb/stable/bionic/dists/bionic/Release.gpg
Resolving nuitka.net (nuitka.net)... <IP_ADDRESS>, 64:ff9b::74ca:1ebc
Connecting to nuitka.net (nuitka.net)|<IP_ADDRESS>|:80... gpg: WARNING: no command supplied.  Trying to guess what you mean ...
connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://nuitka.net/deb/stable/bionic/dists/bionic/Release.gpg [following]
--2021-12-22 19:46:41--  https://nuitka.net/deb/stable/bionic/dists/bionic/Release.gpg
Connecting to nuitka.net (nuitka.net)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 833
Saving to: ‘STDOUT’

                                                      100%[==========================================================================================================================================>]     833  --.-KB/s    in 0s

2021-12-22 19:46:43 (30.8 MB/s) - written to stdout [833/833]
Detached signature.`
Detached signature is weird. Previously it would list expirery etc.

So, I reverted to old instructions, and placed the key there. I think I know now why it's not automated, I never found out how ansible executes a local command and outputs it remotely, at least I now made a comment so next time I know how to update it, should work now?

Just so that you are aware, your sub key is still expired. I don't believe this will cause any problems, but I've held off importing your key in case you wanted to fix this.
Signing and Cert Key looks good.
Encryption sub key still expired.
wget -O - http://nuitka.net/deb/archive.key.gpg | gpg
pub   rsa4096 2013-11-10 [SC] [expires: 2023-12-18]
D96ADCA1377F1CEB6B5103F11BFC33752912B99C
uid           Kay Hayen<EMAIL_ADDRESS>sub   rsa4096 2013-11-10 [E] [expired: 2021-12-17]

Nah, it works, that is what matters. Interestingly last time I managed to update it, but I don't think the subkey is used, or maybe no more, because it is expired, but gpg has no good interface and I don't care enough now.

I think what I do need however, is a kind of automatic test that checks periodically if the packages still install. It's a shame to not have that tested.


TypeError: Struct() argument 1 must be string, not unicode

I have ttx via pip install fonttools, and use it to convert SourceHanSans.
but it give me an exception like this:
Dumping "SourceHanSansCN-Normal.otf" to "SourceHanSansCN-Normal.ttx"...
Dumping 'GlyphOrder' table...
Dumping 'head' table...
Dumping 'hhea' table...
Dumping 'maxp' table...
Dumping 'OS/2' table...
ERROR: Unhandled exception has occurred
Traceback (most recent call last):
File "f:\python27\lib\site-packages\fontTools\ttx.py", line 387, in main
process(jobs, options)
File "f:\python27\lib\site-packages\fontTools\ttx.py", line 361, in process
action(input, output, options)
File "f:\python27\lib\site-packages\fontTools\misc\loggingTools.py", line 372, in wrapper
return func(*args, **kwds)
File "f:\python27\lib\site-packages\fontTools\ttx.py", line 258, in ttDump
newlinestr=options.newlinestr)
File "f:\python27\lib\site-packages\fontTools\ttLib_init_.py", line 311, in saveXML
self.tableToXML(tableWriter, tag, progress)
File "f:\python27\lib\site-packages\fontTools\ttLib_init.py", line 329, in tableToXML
table = self[tag]
File "f:\python27\lib\site-packages\fontTools\ttLib_init.py", line 419, in getitem
tableClass = getTableClass(tag)
File "f:\python27\lib\site-packages\fontTools\ttLib_init_.py", line 825, in getTableClass
module = getTableModule(tag)
File "f:\python27\lib\site-packages\fontTools\ttLib_init_.py", line 807, in getTableModule
import("fontTools.ttLib.tables." + pyTag)
File "f:\python27\lib\site-packages\fontTools\ttLib\tables_n_a_m_e.py", line 26, in
nameRecordSize = sstruct.calcsize(nameRecordFormat)
File "f:\python27\lib\site-packages\fontTools\misc\sstruct.py", line 108, in calcsize
return struct.calcsize(formatstring)
TypeError: Struct() argument 1 must be string, not unicode
(Hit any key to exit)
python version is 2.7.3, os is windows 7 x64 sp1.

Humm.  I suspect e8530360b, but why does it not fail in our continuous testing?

maybe my font (SourceHanSansCN-Normal.otf) have some magic triggered this exception.
it's 1.004 version which got from Adobe's source han project.

Before python 2.7.7 the struct module didn't support unicode strings, but required a nativ str (bytes).
https://bugs.python.org/issue19099
We don't run tests on such old pythons on our CI.
I'd suggest a wontfix and "please update your python, or better use python3".

sgtm

Hi,
I have same problem unfortunately I cannot update python so easily. It doesn't depend on me.
I created pull request that fix this issue.
https://github.com/fonttools/fonttools/compare/master...vane:master
I tested it with python 2.7.5

It turns out some fonttools users are still stuck with pythons older than 2.7.7.
I wouldn't like to add another Travis build to check for such old python, it's slow enough already.
Let's content ourselves of occasionally fixing things based on users' report.. Until the https://pythonclock.org/ finally reaches its end.

for this specific issue with the py27 struct module, fonttools devs should remember to use explicitly use bytes for the struct.pack and unpack format string (using the ``b""notation) whenever the module in which the call to struct appears also importsunicode_literals. The unicode_literalsmodule is known to have some issue with some stdlib modules, but sometimes the convenience of not prefixing everything withu""` outweighs its downsides.
Let's stick to using it like we currently do, i.e. only when a module manipulates potentially non-ASCII text strings.


Confused on version

I cannot reproduce this error at will, it seems when an update is interrupted the app has believes it's running the latest version and a sync will return as up to date, however it's still running the previous version of the code.
Is there an option to force update to the most recent package?

Can you provide more details? Ideally, fill out the template when opening a new issue.

This error has presented itself on several occasions with my users and I've only been able to reproduce it once.
When the update process is interrupted and fails to update the package, it seems that code push has already decided it's got the most current version of the package and therefore subsequent sync calls will fail.
When this happens there are only two ways to fix the issue, you need to reinstall the app entirely or I need to push a new version before it will update.

Alright, we really need more detailed reproduction steps in order to keep this open. Can you fill out the template?

Like I said, I cannot reproduce this on demand. What I'd be interested in is some sort of 'Force Update' option so we have a fallback when this happens.
We have a bit over 3k active users and as far as I'm aware it has only happened a dozen times or so.

It's still unclear what specific issue you're reporting. If this is about Code Push, perhaps https://github.com/Microsoft/code-push is a better place to report the issue.
If you're confident this is an issue in React Native core, please open a new issue and make sure to fill out the template in its entirety. Thanks.


[r-mr1] radio: Allow finding qti uce service

This accomplishes the following:

Wrestle control over vnd_qti_uce_hwservice from ims domain
(add_hwservice() macros includes a neverallow for other  domains to access the service in any way)
All clients of hal_telephony are now allowed to access com.qualcomm.qti.uceservice::IUceService
This includes radio, which is a client domain of hal_telephony.

Since ims is no longer allowed access to vnd_qti_uce_hwservice, it needs to be converted into a client of hal_telephony via the hal_client_domain() macro.
Denial:
avc: denied  { find } for interface=com.qualcomm.qti.uceservice::IUceService \
    sid=u:object_r:radio:s0 scontext=u:object_r:radio:s0 \
    tcontext=u:object_r:vnd_qti_uce_hwservice:s0 tclass=hwservice_manager

Plus a small fixup

@MarijnS95 might taking another look?

@ix5 That's pretty crazy, shouldn't ims be a server domain to be allowed to add (host) IUCEService? Or was that wrong judgement by 346be220646c1feb5a533cff05d53c082927ee69?
If it is, please:
Fixes: 346be22 ("ims: Label new services and grant add_hwservice access.")

But I don't see any other domain with the rights to find/host this service... Perhaps because I have never used this and anyone doing so (PE) is still in permissive.

Who hosts this service?
Do we at some point need a new hwservice "attribute" to shove ims-specific services under?

We should get @paulbouchara to test this in parallel with us on PE since they use IMS and go enforcing soon™, in particular the remaining add_hwservices should probably be moved to hal_attribute_hwservice while falling under the hal_server_domain(ims, hal_telephony) catch-all.
Iirc hwbinder_use at the bottom of ims.te is granted by one of these macros as well?

We should get @Paulbouchara to test this in parallel with us on PE since they use IMS and go enforcing soon™, in particular the remaining add_hwservices should probably be moved to hal_attribute_hwservice while falling under the hal_server_domain(ims, hal_telephony) catch-all.
Iirc hwbinder_use at the bottom of ims.te is granted by one of these macros as well?

The next PE release will be on enforcing, as every releases that will follow, so sure, I'll test this asap when I'll be back and report with logs

@ix5 One more thing: the denial shown in the logs tries to find (and perhaps add later) this service for the radio domain, but this PR allows hosting (adding) it from the ims domain...

@MarijnS95 ims was already hosting the service via the add_hwservice() macro.
That macro, however, forbids any other domains (even parent ones) from adding the service. So ims was not hosting this service in a server capacity, but just on its own.
The only way for a coredomain such as radio to access the IUceService is via hal_ server/client attribute empowerment.
As such, we need to keep the status quo (ims still hosts the service), just change the language.

Final verdict: radio only needs to find the service (and have binder communication with the domain hosting it, ims) so we're better off not adding it to hal_telephony since then:

radio is a server domain, and would incorrectly be allowed to host it;
ims would become a server domain, and is incorrectly allowed to host all other services in the list.

As posted in https://github.com/sonyxperiadev/device-sony-sepolicy/compare/master...MarijnS95:ims-attribute-group we should check whether more hwservices in the hal_telephony domain are actually not hosted by radio at all, and are better separated so that radio can only read them.

For posterity, this was the original description of the "solution" using HAL attributes we discarded:

This accomplishes the following:

Wrestle control over vnd_qti_uce_hwservice from ims domain
(add_hwservice() macros includes a neverallow for other  domains to add the service in any way)
All clients of hal_telephony are now allowed to access com.qualcomm.qti.uceservice::IUceService
This includes radio, which is a client domain of hal_telephony.

Since ims is no longer allowed access to vnd_qti_uce_hwservice, it needs to be converted into a server of hal_telephony via the hal_server_domain() macro.
N.b.: imsrcsd hosts the IUceService, so it really needs to be a server and not only a client.
Denial:
avc: denied  { find } for interface=com.qualcomm.qti.uceservice::IUceService \
    sid=u:object_r:radio:s0 scontext=u:object_r:radio:s0 \
    tcontext=u:object_r:vnd_qti_uce_hwservice:s0 tclass=hwservice_manager

Plus a small fixup


Use standard https port for proxy requests

Use standard https port for proxy requests. There are networks where outgoing traffic is limited to ports 80 and 443 only.
Extracted from #365

Fixed by PR #428


[Bug] Emphasis label cannot be hidden on a funnel chart

Version
5.5.1
Link to Minimal Reproduction
https://echarts.apache.org/examples/en/editor.html?c=pie-simple&lang=ts&version=5.5.1&code=PYBwLglsB2AEC8sDeAoWsCmBbEALAhgM4SEBcya6sA9NQCYn4BGANhneWAE4CuGANJXQtmGFuVRUqhXMADu5AGb4WhAUKq1FwLlnxgwGLuQAUIfF3xYysfNACeASgQA-WACJ3gqem3QwAMoQAF4Y5ADMAAwaAL6UMd6walwQGDYA2hqSPiJMYhIaUjLySipqhbAJFbliADIQ0GEUPtKyCrDKqhgVVS1g9iBNAOSKPNCNLEOJUnT6-OSZLehIsABuKnzkAIyRACwAHPyw0FbDARgWAMa4sACi0ADmDRhDldM-K-ssm7AA7OEAViOJywwwAIhAuBhLmBXr0lp8Nk0AftIsDTuQhrc9BBJpUKgBdWKUIkxADcQA
Steps to Reproduce
Create a funnel chart with hidden labels and label lines, hide the emphasis label. It still shows up.
Current Behavior
Hover over any point, you will see the emphasis label.
Expected Behavior
Hover over any point, you SHOULD NOT see the emphasis label.
Environment
- OS: Windows
- Browser: Chrome
- Framework: N/A

Any additional comments?
Workaround exists, use
formatter: (params: any) => ""

emphasis: {
    label: {
       show: false
    }
}

In which version it is fixed?

My example has this code and it the label is showing

You need to add this option under the series option. Demo


Baselining the scenes

Hi, thanks for the great work!
I came across your project and found it very interesting and useful. I've done some baselining to make sure i understand the code correctly, here are some results in my reproduced PSNR and (reported PSNR in the paper).

Everything looks good and within the range of errors other than the Factory scene. Do you have any idea why this may be?
Again, great work!
Best,

@cpeng93
I agree. It seems to be little bit weird on Factory scene only.
Did you solved?

I've uploaded the pretrained weights on the factory scene on the dataset link. Maybe you could evaluate the pretrained weights first. Suppose the pretrained model also has poor PSNR. In that case, that may be because I accidentally change some code relevant to the evaluation when doing the experiments (since I debug my code using the factory scene). You can just use your newly evaluated performance on the pretrained model. If not, then I guess it is probably because the model is sensitive to initialization.

I've uploaded the pretrained weights on the factory scene on the dataset link. Maybe you could evaluate the pretrained weights first. Suppose the pretrained model also has poor PSNR. In that case, that may be because I accidentally change some code relevant to the evaluation when doing the experiments (since I debug my code using the factory scene). You can just use your newly evaluated performance on the pretrained model. If not, then I guess it is probably because the model is sensitive to initialization.

Thanks for the reply! From just a glance there are two differences in the config page for blurfactory:
In the public repo, the following config is included but not in the config file from the uploaded checkpoint.
render_rmnearplane = 5
render_focuspoint_scale = 0.25
render_radius_scale = 0.5
Also in the public repo:
kernel_align_weight = 0.1
align_start_iter = 0
align_end_iter = 180000
instead of:
kernel_smooth_weight = 0.1
smooth_start_iter = 0
smooth_end_iter = 180000
I will run some benchmark in the mean time.
Cheers,

In fact it seems like none of them have the render_rmnearplane etc. hyper-parameters anymore.

Oh then I think render_rmnearplane configs may be the actual reason that the PSNR is different. It is just a hyper-parameter set manually to remove some floating artifacts when rendering novel views. When doing the evaluation, these configurations should better be removed. (render_focuspoint_scale and render_radius_scale are unused for evaluation and only affect the generated video)

Thanks! looks like this addressed it.


Config and friends removed - how should uaa-cli be refactored?

https://github.com/cloudfoundry-community/go-uaa/releases/tag/v0.0.8 - Config + friends were removed.
These were used by https://github.com/cloudfoundry-incubator/uaa-cli/blob/master/config/config.go when you refactored go-uaa into uaa-cli; but now they are gone. How do you want uaa-cli to be refactored towards new API in go-uaa?
Perhaps can you help bring uaa-cli up to date and keep it in sync as a testbed for this library?

This is something the uaa team is currently working on. We have a tracker story for this https://www.pivotaltracker.com/story/show/158577941 (This work of bringing back config/context into the uaa-cli wasn't discoverable via github). That story was put down last week, however the intent is for a pair to pick it back up this week.


Routes in manifest specified with domains only are not bound

We found an issue using the blue-green-deploy plugin. We think this arises from here: https://github.com/bluemixgaragelondon/cf-blue-green-deploy/blob/master/manifest.go#L22
Given an app manifest with an app name and domains:
---
applications:
- name: test-app
  domains:
  - testing.com

When the app is deployed using the blue-green-deploy plugin
And the deployment is successful
Then the app has no routes
Is there a reason that host is required in manifest.yml? Would you accept a pull request to resolve this issue?

Just to clarify, are you expecting that the result app will have the route test-app.testing.com bound?
Our overarching design goal is to have cf bgd behave as much like cf push as possible, so if this is the  desired behaviour we'd be happy to accept a pull request.


Graphlib Html tutorial missing

Hi
I cant find working example .. Can u please make a tutorial folder for noobs

You can have a look to the wiki associated with the repo. There's all the
API with small examples for somes.
On Jul 9, 2015 7:17 AM, "djangosdk"<EMAIL_ADDRESS>wrote:

Hi
I cant find working example .. Can u please make a tutorial folder for
noobs
—
Reply to this email directly or view it on GitHub
https://github.com/cpettitt/graphlib/issues/46.


worker never reconnect to redis server

I run php-rescue's workers and shutting down redis server.
Then start redis again server.
workers are not down their process, but they aren't reconnect to redis server again.
If workers stop when redis is down, it can recovery again by some deamonizer tools,
but now, I have nothing to do with this problem.
Is there any solution to reconnect php-resque worker to recovered redis server?

I have the same problem. It's quite simple to reproduce.
start a worker - generate a job - job is done
restart redis (ensure that it really was down)
generate a job - working is doing nothing but it teels in the logfile that it checks for jobs
I'd suggest using the redis()->ping() method and try to trigger a reconnect if possible

btw - even a dead worker would be better that something that looks like it is alive (for moniting checks / daemontools)

I have the same problem. I think we should create a process to inspect the connection.

PRs are always welcome.


Extend hyperlink decoration documentation

Description
Describe your changes in detail
Your issue description (body) goes here

Motivation and Context
Why is this change required? What problem does it solve?

How Has This Been Tested?

[ ] Please describe how you tested your changes.
[ ] see how your change affects other areas of the code, etc.

Checklist:
Go over all the following points, and put an x in all the boxes that apply.
If you're unsure about any of these, don't hesitate to ask. We're here to help!

[ ] I have read the CONTRIBUTING document in my spoken language, and understand the terms
[ ] I have updated (or added) the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] I have gone through all the steps, and have thoroughly read the instructions

is there anything more that needs to be done ?

why are some checks getting failed , what can I do to make it work ?

You can address the editorconfig checks, when you click on Details of that check you will see what needs to be changed, everything else is fine

i have made changes to the .gitignore file

why are some checks getting failed , what can I do to make it work ?

They're not running because only src/ has not been touched. We maybe should tweak that outside of that PR at some point.


Cannot add FlSpot with same "y" in LineChart

Hi, i was going to add some Spot to the chart with same "y" and different "x".
but i ran into an error :
Unsupported operation: Result of truncating division is Infinity or NaN

#0      double._trunc_div (dart:core-patch/double.dart:56:57)
#1      double.~/ (dart:core-patch/double.dart:52:12)
#2      AxisChartPainter._drawGrid (package:fl_chart/src/chart/base/axis_chart/axis_chart_painter.dart:284:27)
#3      AxisChartPainter.paint (package:fl_chart/src/chart/base/axis_chart/axis_chart_painter.dart:40:5)
#4      LineChartPainter.paint (package:fl_chart/src/chart/line_chart/line_chart_painter.dart:79:11)
#5      RenderLineChart.paint (package:fl_chart/src/chart/line_chart/line_chart_renderer.dart:75:14)
#6      RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2409:7)
#7      PaintingContext.paintChild (package:flutter/src/rendering/object.dart:189:13)

i'm using fl_chart : ^0.41.0

i have the same question,when i use data like x:['2021-08','2021-09','2121-10','2021-11','2021-12','2022-01'] y:[0.0,0.0,0.0,0.0,0.0,0.0,0.0]  it will catch a error ,like this=>

same problem

how to solve: maxY must greater than 0 minY
so i calculate manually and return default value for maxY
    int maxValue = 0;
    for (var item in myListValue) {
      if (item > maxValue) {
        maxValue = a;
      }
    }

    if (maxValue == 0) {
      maxValue = 10;
    }

    return LineChartData(
      // lineTouchData: lineTouchData1,
      // gridData: gridData,
      // titlesData: titlesData1,
      // borderData: borderData,
      // lineBarsData: ...,
      // minX: ...,
      // maxX: ...,
      minY: 0.toDouble(),
      maxY: maxValue.toDouble(),
    );

As I explained in the issue template, Please provide me a reproducible code (a main.dart file).

Hi.
We have just fixed it in 0.45.0.
Please check it out!


Add newer Node versions to Travis

Currently only 0.10 and 0.12 are tested:
https://github.com/bda-research/node-crawler/blob/master/.travis.yml

@sylvinus That's no problem, and we are going to change something in next release, which may be some events and features, I will open a new issue to discuss.
@paulvalla

Because newer version of jsdom cannot support node 0.10 and 0.12, will remove 0.10 and 0.12 support.


Remove need for repeated calls to DisplayOption in WindowsMixedRealitySpatialMeshObserver

The current implementation of the DisplayOption setter in WindowsMixedRealitySpatialMeshObserver checks to see if the value being set is not the same as the current value. Only then will it perform any operations (including updating the material on existing meshes).
Because of this, code that changes a material (ec: VisibleMaterial) must set DisplayOption twice.
observer.VisibleMaterial = newMaterial;
observer.DisplayOption = SpatialAwarenessMeshDisplayOptions.None;
observer.DisplayOption = SpatialAwarenessMeshDisplayOptions.Visible;

This change removes the previous value check and always performs processing when DisplayOption is set. This allows for a more natural calling pattern without the need for knowing the quirks of this observer.
observer.VisibleMaterial = newMaterial;
observer.DisplayOption = SpatialAwarenessMeshDisplayOptions.Visible;

/azp run mrtk_pr


Online Mode

Thank you for releasing your code. And I'm comfused about the offline model to produce pseudo-labels seems not work, or your online or test mode is not released? It seems now only support offline mode, right?
Thank you very much and I'm looking forward to your response.

Thanks for pointing out. The online mode has been released now.


Add simplabs

Hello @jessicard, would you add us to the list please?
cheers
Oliver

@oliverbarnes Hey! Can you add a company profile and link from the readme entry and I'll merge when it's ready? thanks!

@dougaitken sure, added. @marcoow would you give it a quick look, please

👍🏻 looks good

@dougaitken ready to merge. thanks!

cheers lads! @oliverbarnes @marcoow


[release-4.7] operator/ingress: Add unsupportedConfigOverrides

Add a spec.unsupportedConfigOverrides field to the IngressController API to
accommodate unsupported configuration overrides.
This commit resolves NE-549.
https://issues.redhat.com/browse/NE-549

operator/v1/types_ingress.go (IngressControllerSpec): Add an
UnsupportedConfigOverrides field with type runtime.RawExtension.
operator/v1/0000_50_ingress-operator_00-ingresscontroller.crd.yaml:
operator/v1/zz_generated.deepcopy.go:
operator/v1/zz_generated.swagger_doc_generated.go: Regenerate.

--
This is the 4.7 backport of https://github.com/openshift/api/pull/878.
Related to https://github.com/openshift/cluster-ingress-operator/pull/619 (backport BZ Pending)

/close


v1.3 release

I'm trying to decide what should make the v1.3 release.
Here's what I think should be included:

[ ] #340 ButtonBoard
[ ] #133 DotsBoard
[ ] #248 Servo
[ ] #93 Temperature sensor
[ ] #294 CPU temperature
[ ] #329 ADC.voltage

Documentation and house-keeping:

[ ] #87 Test suite
[ ] #261 activated/deactivated callback modification
[ ] #289 Add note about remote access
[ ] #345 Alias amber to yellow

Drop milestone, leave on wishlist:

#144 Stepper motor
#169 Piezo speaker
#199 GPIO expander chips
#228 RGBLED.cycle()

(and more in this category that don't have the milestone)
I'm open to suggestions on what should be in the release - especially if any I've missed out are low-hanging fruit (maybe #228?), or if any I included which require too much work (maybe #93). I just want to nail the list down and start working towards a release.
There have been 100 commits since v1.2 was released! It would be good to get that functionality, and those docs fixes, out in the wild. It's hard to determine how big a step is required to call it a new release. We could easily do more regular releases - I don't know if that's something we want to do or not.

Maybe you could add to the list #359 pin_factory based on environmental value
I provided the Pull request #356 and showed the result of my tests on a Mac talking to a Pi and on a Pi.
What else:
-* Is there anything expected from me ?
-* Is there someone to review the code ?
-* Are we waiting for another/better implementation by @waveform80 or somebody else (without if / elseif sequence) ?
-* Should I redo the Pull request based on current version so that it has no conflict?
Please advise as it is one month old already and soon I will have forgot everything.
Thanks.

The PR looks good from a quick skim - I'm just rather swamped under with another project at the moment. I should be able to get back to GPIO Zero next week, once this current project is cleared (also managed to get picamera 1.11, and then 1.12 out recently so other than GPIO Zero my todo list is actually shrinking for once!)

Raspbian freeze coming up tomorrow, so 1.3 will be going out sometime tonight. I'll be bumping everything not yet finished to the 1.4 milestone in a bit.

Next time, would it be possible to have more advance notice of the upcoming new-release, so we get a bit more time to work on finishing off / polishing incomplete features?

Just 'ticked off' the items in the first post where the corresponding issue or PR has been closed / merged.

Yeah, this was a bit dis-organised - it's partly due to the Raspbian freeze today, and partly wanting to get another release out we can show-case at pycon-uk. I was hoping to have more time over the long weekend to sort things out, but as always other things got in the way. Sorry about that!
Maybe we should set a date on the 1.4 milestone and try sticking to it, i.e. even if everything's not complete just release anyway so at least users know when to expect a release and devs know what the release deadline'll actually be. Unfortunately that may lead to a rather spartan release if we select something too short (1.3 would've been rather bare if we'd released on the monthly cycle Ben originally proposed), but a quarterly cycle might be more realistic?

Yeah, I guess a quarterly cycle with a known-in-advance release date might work :)

I think 3 months should work. Shall we say 16th November (my birthday, as that's when we released v1.0)?

Sounds good

I guess this issue should be closed now, and @bennuttall should create a new "v1.4 release" issue? ;)

In progress!


Use global i18n strings instead of global env vars in our i18n strings

Description
This issue is split off from https://github.com/kumahq/kuma-gui/issues/1478

Instead of using env for "i18n global variables", we should just use i18n for a group of select i18n keys that we define as being available "globally". We can collect these "globals" at i18n service start up (using @kong-ui-public/i18n#t and then always feed them into our own t). In doing this we remove the dependency on env and then we should be closer to only having a single place for defining application strings.

TLDR;
https://github.com/kumahq/kuma-gui/blob/e865b09b5ff268836074028099223cc2325ea9f7/src/app/application/services/i18n/I18n.ts#L32-L36
See the env usage above? We should try and reduce that and replace it with the t usage shown above.
This code makes these GLOBAL_VARIABLES available within i18n files.

Coming back to look at this after some time I think we've actually done most of this, some examples:

KUMA_VERSION should be an env var as its not static
KUMA_DOCS_URL is weirder, as it should use a static i18n derived URL, appended with KUMA_VERSION
KUMA_PRODUCT_NAME can probably be removed from env entirely (but kept as being i18n derived)

Ideally all i18n 'globals' should live in global.NAME_OF_VAR or similar so its super obvious how to make a new i18n global var.
The final aim is to finally have env not deal with static variables (we only use env for historical reasons because we didn't have i18n when we originally needed injectable strings).

I just took a look at this when I was removing a stale label. It's mostly done, almost finished, I think it just needs an extra little bit of effort to finish it up, which is mostly just cleanup. So we should probably get on and do this so we can close this up.


[BugFix] Fix datetime column has different precision when hive table use timestamp as partition column

hive timestamp may has different prescision, eg, '2023-01-01 12:00:00' or '2023-01-01 12:00:00.0', they are same time, but as partition column, it will has different partition name, so we need to record the prescision to use the same partition name
What type of PR is this:

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.1
[ ] 3.0
[ ] 2.5
[ ] 2.4

[FE PR Coverage Check]
:heart_eyes: pass : 12 / 12 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/analysis/DateLiteral.java
4
4
100.00%
[]

:large_blue_circle:
com/starrocks/connector/PartitionUtil.java
8
8
100.00%
[]


Add kubectl-view-allocations in the README

Add kubectl-view-allocations in the list of Real world users.

Ooh, I have not checked out kubectl-view-allocations in so long. It's looking so much more featured now!
Yeah, I am totally happy to add it to the big examples list :-)