superset 0.36.0 can not connect to sqlalchemy_dremio

A clear and concise description of what the bug is.
Can not connect to dremio via sqlalchemy_dremio
Expected results
what you expected to happen.
Success connection
Actual results
Error
what actually happens.
Screenshots

If applicable, add screenshots to help explain your problem.
How to reproduce the bug

Go to '...'
Click on '....'
Scroll down to '....'
See error

Environment
(please complete the following information):

superset version: 0.36.0
python version: python --version
node.js version: node -v
npm version: npm -v

Checklist
Make sure these boxes are checked before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[x ] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Add any other context about the problem here.
We used dremio+pyodbc://admin:P4ssw0rd@dremio-client.dremio.svc.cluster.local:31010/k8s-postgres-operator-airflow

@4ss3g4f have you installed the Dremio ODBC driver?

@villebro yes i have tried, here are the results,

dremio only provide rpm pakage not deb for superset debian os,

is this mean that we have to convert dremio ODBC rpm package to deb package first ??

We have install dremio ODBC,

But still can not add dremio,

we tried with,
dremio+pyodbc://admin:P4ssw0rd@dremio-client.dremio.svc.cluster.local:31010/Samples

We also have installed pyodbc and sqlalchemy_dremio, still can not connect to dremio,

ok solved,

we fork new docker file,
core@worker-020 ~ $ cat Dockerfile
FROM amancevice/superset:0.36.0
USER root
COPY dremio-odbc_<IP_ADDRESS>3-2_amd64.deb /home/superset/
RUN dpkg -i /home/superset/dremio-odbc_<IP_ADDRESS>3-2_amd64.deb
RUN apt-get install -y unixodbc-bin && apt-get install -y unixodbc-dev
RUN pip install pyodbc && pip install sqlalchemy_dremio && pip install dremio_client[full]

result:

core@worker-020 ~ $ docker build -t assegaf/superset-k8s:0.36.0 .

(Reading database ... 25014 files and directories currently installed.)
Preparing to unpack .../dremio-odbc_<IP_ADDRESS>3-2_amd64.deb ...
Unpacking dremio-odbc (<IP_ADDRESS>3-2) ...
Setting up dremio-odbc (<IP_ADDRESS>3-2) ...
/var/lib/dpkg/info/dremio-odbc.postinst: line 3: odbcinst: command not found
/var/lib/dpkg/info/dremio-odbc.postinst: line 5: [: configure: integer expression expected
Processing triggers for libc-bin (2.28-10) ...
Removing intermediate container 829c51de51df
---> 54eb6d0eff1b
Step 5/6 : RUN apt-get install -y unixodbc-bin && apt-get install -y unixodbc-dev
---> Running in 93f572921b34
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
dbus libapparmor1 libaudio2 libavahi-client3 libavahi-common-data
libavahi-common3 libcups2 libdbus-1-3 libmng1 libodbcinstq4-1 libqt4-dbus
libqt4-network libqt4-xml libqtassistantclient4 libqtcore4 libqtdbus4
libqtgui4 odbcinst odbcinst1debian2 qdbus qt-at-spi qtchooser qtcore4-l10n
Suggested packages:
default-dbus-session-bus | dbus-session-bus nas cups-common libicu57
qt4-qtconfig
The following NEW packages will be installed:
dbus libapparmor1 libaudio2 libavahi-client3 libavahi-common-data
libavahi-common3 libcups2 libdbus-1-3 libmng1 libodbcinstq4-1 libqt4-dbus
libqt4-network libqt4-xml libqtassistantclient4 libqtcore4 libqtdbus4
libqtgui4 odbcinst odbcinst1debian2 qdbus qt-at-spi qtchooser qtcore4-l10n
unixodbc-bin
0 upgraded, 24 newly installed, 0 to remove and 0 not upgraded.
Need to get 9502 kB of archives.
After this operation, 32.8 MB of additional disk space will be used.

(Reading database ... 25043 files and directories currently installed.)
Preparing to unpack .../00-libapparmor1_2.13.2-10_amd64.deb ...
Unpacking libapparmor1:amd64 (2.13.2-10) ...
Selecting previously unselected package libdbus-1-3:amd64.
Preparing to unpack .../01-libdbus-1-3_1.12.16-1_amd64.deb ...
Unpacking libdbus-1-3:amd64 (1.12.16-1) ...
Selecting previously unselected package dbus.
Preparing to unpack .../02-dbus_1.12.16-1_amd64.deb ...
Unpacking dbus (1.12.16-1) ...
Selecting previously unselected package libaudio2:amd64.
Preparing to unpack .../03-libaudio2_1.9.4-6_amd64.deb ...
Unpacking libaudio2:amd64 (1.9.4-6) ...
Selecting previously unselected package libavahi-common-data:amd64.
Preparing to unpack .../04-libavahi-common-data_0.7-4+b1_amd64.deb ...
Unpacking libavahi-common-data:amd64 (0.7-4+b1) ...
Selecting previously unselected package libavahi-common3:amd64.
Preparing to unpack .../05-libavahi-common3_0.7-4+b1_amd64.deb ...
Unpacking libavahi-common3:amd64 (0.7-4+b1) ...
Selecting previously unselected package libavahi-client3:amd64.
Preparing to unpack .../06-libavahi-client3_0.7-4+b1_amd64.deb ...
Unpacking libavahi-client3:amd64 (0.7-4+b1) ...
Selecting previously unselected package libcups2:amd64.
Preparing to unpack .../07-libcups2_2.2.10-6+deb10u2_amd64.deb ...
Unpacking libcups2:amd64 (2.2.10-6+deb10u2) ...
Selecting previously unselected package libmng1:amd64.
Preparing to unpack .../08-libmng1_1.0.10+dfsg-3.1+b5_amd64.deb ...
Unpacking libmng1:amd64 (1.0.10+dfsg-3.1+b5) ...
Selecting previously unselected package qtcore4-l10n.
Preparing to unpack .../09-qtcore4-l10n_4%3a4.8.7+dfsg-18_all.deb ...
Unpacking qtcore4-l10n (4:4.8.7+dfsg-18) ...
Selecting previously unselected package libqtcore4:amd64.
Preparing to unpack .../10-libqtcore4_4%3a4.8.7+dfsg-18_amd64.deb ...
Unpacking libqtcore4:amd64 (4:4.8.7+dfsg-18) ...
Selecting previously unselected package libqt4-xml:amd64.
Preparing to unpack .../11-libqt4-xml_4%3a4.8.7+dfsg-18_amd64.deb ...
Unpacking libqt4-xml:amd64 (4:4.8.7+dfsg-18) ...
Selecting previously unselected package libqtdbus4:amd64.
Preparing to unpack .../12-libqtdbus4_4%3a4.8.7+dfsg-18_amd64.deb ...
Unpacking libqtdbus4:amd64 (4:4.8.7+dfsg-18) ...
Selecting previously unselected package libqt4-network:amd64.
Preparing to unpack .../13-libqt4-network_4%3a4.8.7+dfsg-18_amd64.deb ...
Unpacking libqt4-network:amd64 (4:4.8.7+dfsg-18) ...
Selecting previously unselected package libqtassistantclient4:amd64.
Preparing to unpack .../14-libqtassistantclient4_4.6.3-7+b1_amd64.deb ...
Unpacking libqtassistantclient4:amd64 (4.6.3-7+b1) ...
Selecting previously unselected package libqtgui4:amd64.
Preparing to unpack .../15-libqtgui4_4%3a4.8.7+dfsg-18_amd64.deb ...
Unpacking libqtgui4:amd64 (4:4.8.7+dfsg-18) ...
Selecting previously unselected package odbcinst.
Preparing to unpack .../16-odbcinst_2.3.6-0.1_amd64.deb ...
Unpacking odbcinst (2.3.6-0.1) ...
Selecting previously unselected package odbcinst1debian2:amd64.
Preparing to unpack .../17-odbcinst1debian2_2.3.6-0.1_amd64.deb ...
Unpacking odbcinst1debian2:amd64 (2.3.6-0.1) ...
Selecting previously unselected package libodbcinstq4-1:amd64.
Preparing to unpack .../18-libodbcinstq4-1_2.3.0-4+b1_amd64.deb ...
Unpacking libodbcinstq4-1:amd64 (2.3.0-4+b1) ...
Selecting previously unselected package qtchooser.
Preparing to unpack .../19-qtchooser_66-2_amd64.deb ...
Unpacking qtchooser (66-2) ...
Selecting previously unselected package qdbus.
Preparing to unpack .../20-qdbus_4%3a4.8.7+dfsg-18_amd64.deb ...
Unpacking qdbus (4:4.8.7+dfsg-18) ...
Selecting previously unselected package libqt4-dbus:amd64.
Preparing to unpack .../21-libqt4-dbus_4%3a4.8.7+dfsg-18_amd64.deb ...
Unpacking libqt4-dbus:amd64 (4:4.8.7+dfsg-18) ...
Selecting previously unselected package qt-at-spi:amd64.
Preparing to unpack .../22-qt-at-spi_0.4.0-9_amd64.deb ...
Unpacking qt-at-spi:amd64 (0.4.0-9) ...
Selecting previously unselected package unixodbc-bin.
Preparing to unpack .../23-unixodbc-bin_2.3.0-4+b1_amd64.deb ...
Unpacking unixodbc-bin (2.3.0-4+b1) ...
Setting up libmng1:amd64 (1.0.10+dfsg-3.1+b5) ...
Setting up libapparmor1:amd64 (2.13.2-10) ...
Setting up libavahi-common-data:amd64 (0.7-4+b1) ...
Setting up libdbus-1-3:amd64 (1.12.16-1) ...
Setting up dbus (1.12.16-1) ...
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of start.
Setting up libaudio2:amd64 (1.9.4-6) ...
Setting up qtchooser (66-2) ...
Setting up qtcore4-l10n (4:4.8.7+dfsg-18) ...
Setting up libavahi-common3:amd64 (0.7-4+b1) ...
Setting up libqtcore4:amd64 (4:4.8.7+dfsg-18) ...
Setting up libavahi-client3:amd64 (0.7-4+b1) ...
Setting up libqtgui4:amd64 (4:4.8.7+dfsg-18) ...
Setting up libqt4-xml:amd64 (4:4.8.7+dfsg-18) ...
Setting up libcups2:amd64 (2.2.10-6+deb10u2) ...
Setting up libqtdbus4:amd64 (4:4.8.7+dfsg-18) ...
Setting up libqt4-network:amd64 (4:4.8.7+dfsg-18) ...
Setting up qdbus (4:4.8.7+dfsg-18) ...
Setting up libqtassistantclient4:amd64 (4.6.3-7+b1) ...
Setting up libqt4-dbus:amd64 (4:4.8.7+dfsg-18) ...
Setting up qt-at-spi:amd64 (0.4.0-9) ...
Setting up odbcinst (2.3.6-0.1) ...
Setting up odbcinst1debian2:amd64 (2.3.6-0.1) ...
Setting up libodbcinstq4-1:amd64 (2.3.0-4+b1) ...
Setting up unixodbc-bin (2.3.0-4+b1) ...
Processing triggers for libc-bin (2.28-10) ...
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
unixodbc-dev
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 261 kB of archives.
After this operation, 1829 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian buster/main amd64 unixodbc-dev amd64 2.3.6-0.1 [261 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 261 kB in 0s (672 kB/s)
Selecting previously unselected package unixodbc-dev:amd64.
(Reading database ... 25456 files and directories currently installed.)
Preparing to unpack .../unixodbc-dev_2.3.6-0.1_amd64.deb ...
Unpacking unixodbc-dev:amd64 (2.3.6-0.1) ...
Setting up unixodbc-dev:amd64 (2.3.6-0.1) ...
Removing intermediate container 93f572921b34
---> 5e53cb6346fe
Step 6/6 : RUN pip install pyodbc && pip install sqlalchemy_dremio && pip install dremio_client[full]
---> Running in<PHONE_NUMBER>3f
Collecting pyodbc
Downloading pyodbc-4.0.30.tar.gz (266 kB)
Building wheels for collected packages: pyodbc
Building wheel for pyodbc (setup.py): started
Building wheel for pyodbc (setup.py): finished with status 'done'
Created wheel for pyodbc: filename=pyodbc-4.0.30-cp36-cp36m-linux_x86_64.whl size=344942 sha256=50b07326795a239293e92f9d7dea1ec55fb15a45023e6cd8ffaf9f2a9011fb8a
Stored in directory: /root/.cache/pip/wheels/e3/3f/16/e11367542166d4f8a252c031ac3a4163d3b901b251ec71e905
Successfully built pyodbc
Installing collected packages: pyodbc
Successfully installed pyodbc-4.0.30
Collecting sqlalchemy_dremio
Downloading sqlalchemy_dremio-1.1.3.tar.gz (14 kB)
Requirement already satisfied: pyodbc>=4.0.17 in /usr/local/lib/python3.6/site-packages (from sqlalchemy_dremio) (4.0.30)
Requirement already satisfied: sqlalchemy>=1.2 in /usr/local/lib/python3.6/site-packages (from sqlalchemy_dremio) (1.3.12)
Requirement already satisfied: pyarrow in /usr/local/lib/python3.6/site-packages (from sqlalchemy_dremio) (0.16.0)
Requirement already satisfied: six>=1.0.0 in /usr/local/lib/python3.6/site-packages (from pyarrow->sqlalchemy_dremio) (1.14.0)
Requirement already satisfied: numpy>=1.14 in /usr/local/lib/python3.6/site-packages (from pyarrow->sqlalchemy_dremio) (1.18.1)
Building wheels for collected packages: sqlalchemy-dremio
Building wheel for sqlalchemy-dremio (setup.py): started
Building wheel for sqlalchemy-dremio (setup.py): finished with status 'done'
Created wheel for sqlalchemy-dremio: filename=sqlalchemy_dremio-1.1.3-py2.py3-none-any.whl size=18041 sha256=a0126564a32b2e8157131f960b10234ea71a4d1763050814de57daffb1500e4c
Stored in directory: /root/.cache/pip/wheels/00/3a/0f/a4e0b6df805a7cd2c212d799fa2392ab5beb8bd8ca16e8dfa2
Successfully built sqlalchemy-dremio
Installing collected packages: sqlalchemy-dremio
Successfully installed sqlalchemy-dremio-1.1.3
Collecting dremio_client[full]
Downloading dremio_client-0.12.0-py2.py3-none-any.whl (46 kB)
Requirement already satisfied: simplejson in /usr/local/lib/python3.6/site-packages (from dremio_client[full]) (3.17.0)
Requirement already satisfied: attrs in /usr/local/lib/python3.6/site-packages (from dremio_client[full]) (19.3.0)
Collecting confuse
Downloading confuse-1.1.0.tar.gz (32 kB)
Requirement already satisfied: requests>=2.21.0 in /usr/local/lib/python3.6/site-packages (from dremio_client[full]) (2.23.0)
Requirement already satisfied: Click>=6.0 in /usr/local/lib/python3.6/site-packages (from dremio_client[full]) (7.1.1)
Requirement already satisfied: six in /usr/local/lib/python3.6/site-packages (from dremio_client[full]) (1.14.0)
Requirement already satisfied: pyarrow>=0.15.0; extra == "full" in /usr/local/lib/python3.6/site-packages (from dremio_client[full]) (0.16.0)
Requirement already satisfied: markdown; extra == "full" in /usr/local/lib/python3.6/site-packages (from dremio_client[full]) (3.1.1)
Collecting requests-futures==1.0.0; extra == "full"
Downloading requests-futures-1.0.0.tar.gz (10 kB)
Requirement already satisfied: pandas>=0.24.2; extra == "full" in /usr/local/lib/python3.6/site-packages (from dremio_client[full]) (0.25.3)
Requirement already satisfied: pyyaml in /usr/local/lib/python3.6/site-packages (from confuse->dremio_client[full]) (5.3)
Requirement already satisfied: idna<3,>=2.5 in /usr/local/lib/python3.6/site-packages (from requests>=2.21.0->dremio_client[full]) (2.9)
Requirement already satisfied: chardet<4,>=3.0.2 in /usr/local/lib/python3.6/site-packages (from requests>=2.21.0->dremio_client[full]) (3.0.4)
Requirement already satisfied: certifi>=2017.4.17 in /usr/local/lib/python3.6/site-packages (from requests>=2.21.0->dremio_client[full]) (2<IP_ADDRESS>)
Requirement already satisfied: urllib3!=1.25.0,!=1.25.1,<1.26,>=1.21.1 in /usr/local/lib/python3.6/site-packages (from requests>=2.21.0->dremio_client[full]) (1.25.8)
Requirement already satisfied: numpy>=1.14 in /usr/local/lib/python3.6/site-packages (from pyarrow>=0.15.0; extra == "full"->dremio_client[full]) (1.18.1)
Requirement already satisfied: setuptools>=36 in /usr/local/lib/python3.6/site-packages (from markdown; extra == "full"->dremio_client[full]) (46.1.3)
Requirement already satisfied: python-dateutil>=2.6.1 in /usr/local/lib/python3.6/site-packages (from pandas>=0.24.2; extra == "full"->dremio_client[full]) (2.8.1)
Requirement already satisfied: pytz>=2017.2 in /usr/local/lib/python3.6/site-packages (from pandas>=0.24.2; extra == "full"->dremio_client[full]) (2019.3)
Building wheels for collected packages: confuse, requests-futures
Building wheel for confuse (setup.py): started
Building wheel for confuse (setup.py): finished with status 'done'
Created wheel for confuse: filename=confuse-1.1.0-py3-none-any.whl size=17573 sha256=33582e599f885757eff0c1e347b2bd6cbc4b2b59ea322eb1416fdc94823e8450
Stored in directory: /root/.cache/pip/wheels/0b/b9/ff/e8288eaedc9ead7b6f32555771ccd4b5bcec1566553b4c4859
Building wheel for requests-futures (setup.py): started
Building wheel for requests-futures (setup.py): finished with status 'done'
Created wheel for requests-futures: filename=requests_futures-1.0.0-py3-none-any.whl size=7013 sha256=89ac08c59ee895d012fdfb59a898498f4f6ada6a209a291448a62bb74befbdb1
Stored in directory: /root/.cache/pip/wheels/15/03/c1/78bc17e91a6f740565af018749431a5c35e62ee93a32824344
Successfully built confuse requests-futures
Installing collected packages: confuse, requests-futures, dremio-client
Successfully installed confuse-1.1.0 dremio-client-0.12.0 requests-futures-1.0.0
Removing intermediate container<PHONE_NUMBER>3f
---> f0166c9e2abd
Successfully built f0166c9e2abd
Successfully tagged assegaf/superset-k8s:0.36.0


Modify the dependency httpclient5 to httpclient4.

This PR is to resolve this comment, remove httpclient5 dependency from jca.

Hi, @han-gao , please:

Add description of this PR.
Please fix the pipeline failure.

Hi, @han-gao , please resolve the conflicts and fix the pipeline failure.

I have tested the sampleand Unit Test under the jca module, the changed api will not affect the original function.

/check-enforcer override


Added my profile

Description
Please include a summary of the changes and the related issue(s) this pull request addresses. Include any relevant context or background information.
Fixes: #[issue_number] (replace with the issue number, if applicable)
Use [x] to represent a checked (ticked) box.✅
Use [ ] to represent an unchecked box.❌
Type of Change

[x] Profile Added
[ ] Project Added
[ ] Bug fix
[ ] New feature
[ ] Documentation update
[ ] Other (please specify):

How to Test
Provide a brief description of how to test your changes. Include steps, commands, or screenshots if necessary.

Step 1
Step 2
Step 3

Checklist

[x] I have performed a self-review of my code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation (if applicable).
[x] My changes generate no new warnings.
[x] I have added tests to cover my changes (if applicable).
[x] All new and existing tests pass.

Additional Notes
Please add any other information that is relevant to this pull request, including potential risks, alternative solutions considered, or future improvements.

you are not following my account.

@Gyanthakur Done


[feature] Loop a song up to 10 times

add an feature to loop a song up to 10 times

soon thankyou


Link with activeClassName

Similar to react-router's Link, it would be nice to be able to customize CSS when a link is active, e.g with an activeClassName property.

duplicate of  https://github.com/zeit/next.js/issues/127

This isn't a duplicate, right now there is no way to style a link specifically when a route is active. React-router provides this in 147 + 233 LOCs.

ohhh, sorry!
It might be nice to have the activeClassName property, but you can manually detect if a route is active and set any class to the Link anyway ?

this would be super nice to have indeed!

@nkzawa manually detecting requires 2 things:

passing the router URL all the way from the page root down to the component having the Link. Either it pollutes all the intermediate component signatures or need to set up a contextType.
comparing the router URL with the Link's href. As shown in react-router above (isActive method), it's not trivial.

Would be great to have Next take care of this instead of every user reimplementing it.

Or maybe a withLocation HOC. And wrap Link with that HOC. Then import that instead of next/link

Or maybe a withLocation HOC. And wrap Link with that HOC. Then import that instead of next/link

One way to support is provide a way to get current state of the router using next/router. But it's not working on the Server.
So, what ever thing we need to done inside a componentDidMount hook.
@nkzawa If we allow next/router on the server (Just for SSR) this would be great.
Is there's any chance we could support it?

One way to support is provide a way to get current state of the router using next/router. But it's not working on the Server.
So, what ever thing we need to done inside a componentDidMount hook.
@nkzawa If we allow next/router on the server (Just for SSR) this would be great.
Is there's any chance we could support it?

Below is my current workaround. The key part is const isActive = window.location.pathname === route.path which works for me, but if you have query params and such would need a bit more logic. I agree it would be nice to have this as a render callback argument from next/link :)
Navigation.js
import React from 'react'
import Link from 'next/link'

const routes = [
  {
    path: '/',
    title: 'Home',
  },
  {
    path: '/about',
    title: 'About',
  },
  {
    path: '/blog',
    title: 'Blog',
  },
]

export default () => (

    {routes.map((route, index) => {
      const isActive = window.location.pathname === route.path
      return (
        <Link
          key={index}
          href={route.path}
        >

            {route.title}

        </Link>
      )
    })}

)

Nevermind, that doesn't work with server refresh

I'm thinking it might be implemented using componentDidMount since it's only executed client side. I'm not sure if it's executed every route change though.

@trevordmiller you can use getInitialProps on your top-level pages.
import React from 'react'
import Thing from '../components/Thing'

export default class extends React.Component {
  static async getInitialProps ({ req }) {
    return { pathname: req && req.url }
  }

  render () {
    return (
      <Thing pathname={this.props.pathname} />
    )
  }
}

Then in your component
const isActive = window.location.pathname === route.path || pathname === route.path

I think this would be a very good addition to the Links, I wonder if Zeit did it on zeit.co the way @mallendeo described

Hey guys is this feature currently still developing?

I think this is pretty easy to do without core support.

I tried adding active classname in componentDidMount but it doesn't seem right. At first render active classname does not occur.

@arunoda do you have a good example of how to implement this given that it's pretty easy?
I use query parameters within my app and I've had to do some fairly ugly stuff to get the active class names to render the same on both client & server. Core support would be much nicer.

We are doing something like this: pesudo code
import Router from 'next/router';

const isActiveRoute = path => {
    return this.props.pathname === path;
}

isActiveRoute.getInitialProps = ({ isServer, pathname }) => {
  if (isServer) {
    return { pathname };
  } else {
    return { pathname: Router.pathname };
  }
}

export default isActiveRoute;

@andrewmclagan It's not so easy.
This usage can't handle URL change:
<Component isActive={Router.isActive('/path/to/check')} />
URL changes, so whenever we need to handle URL change, we need higher order component to enforce rerender. Something like injectUrl(PageHeader)

@steida yeah i figured that would be the case.
What about a wrapping component that uses context (as in my example above) that passes a className or isActive property to the child component?

fwiw I still think this should be built into next/link

I think this is pretty easy to do without core support.

Do you have a good example of how to implement this given that it's pretty easy?

Use the title, Luke.

That's how I am doing it in Este.
// @flow
import A from './a';
import Box from './box';

const HeaderA = ({ children, href, title }) => (

    {children}

);

type PageHeaderProps = { title: string };

const PageHeader = ({ title }: PageHeaderProps) => (
  <Box
    backgroundColor="primary"
    flexDirection="row"
    flexWrap="wrap"
    marginVertical={0.5}
    paddingHorizontal={0.5}
  >
    <HeaderA href="/" title={title}>Home</HeaderA>
    <HeaderA href="/about" title={title}>About</HeaderA>
  </Box>
);

export default PageHeader;

The solution I found (might not be the best one) is to use
path-to-regexp classnames  packages and I made a util function that checks if the route is active by passing the props to my nav component...
// ./lib/activePath.js
import pathToRegexp from "path-to-regexp";

export function activePath(currentPath, path , options) {
  const regexPath = pathToRegexp(path, options);

  const result = regexPath.exec(currentPath);
  return result;
}

// ./component/Header.js
import React, { Component } from 'react';
import Link from "next/link";
import { activePath } from "../lib/activePath";
import classnames from "classnames";
class Header extends Component {
  render() {
    const { url } = this.props;
    const { pathname } = url;
    return (

          <button className="navbar-toggler navbar-toggler-right" type="button" data-toggle="collapse" data-target="#navbarNavAltMarkup" aria-controls="navbarNavAltMarkup" aria-expanded="false" aria-label="Toggle navigation">

          </button>
          Title

              <Link href="/">
                Home (current)
              </Link>
              <Link href="/about">
                About
              </Link>
              <Link href="/about/us">
                About US
              </Link>
              <Link href="/contact">
                Contact
              </Link>

    );
  }
}

export default Header;

the header is in my layout component so I have to pass the props to it on every page so that the header would have access to url props...
I'm open to other solutions too :D

Guys, we are going to implement a new API to make these simple.
See: https://github.com/zeit/next.js/issues/2032

@arunoda Thanks I feel this was always going to be the right direction. We basically took the HOC route ourselves.

hi guys, I made it using next-routes which makes one route define for both server side and client side, example here https://hello-next-lhafgwnfxp.now.sh/ and code here https://github.com/postor/nextjs-boilerplate

We'll merge the withRoute HOC after v3 has been released. Then this will be possible. https://github.com/zeit/next.js/pull/2352


Implement client features for tenant offloading

Use updated protos with new activity status enum values
Split Tenant and TenantInput due to read-only nature of new activity statuses
Allow Tenant in create/update methods but check if read-only fields are used
Introduce TenantInputType and TenantOutputType types for a simpler surface

Core PR: https://github.com/weaviate/weaviate/pull/5224

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

Please upload report for BASE (dev/1.26@cbedf2a). Learn more about missing BASE report.

Files
Patch %
Lines

weaviate/collections/grpc/tenants.py
0.00%
6 Missing :warning:

weaviate/collections/tenants.py
91.66%
3 Missing :warning:

weaviate/collections/classes/tenants.py
92.30%
1 Missing :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##             dev/1.26    #1132   +/-   ##
===========================================
  Coverage            ?   94.59%
===========================================
  Files               ?      190
  Lines               ?    18984
  Branches            ?        0
===========================================
  Hits                ?    17958
  Misses              ?     1026
  Partials            ?        0

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

No tests?

Not yet, was waiting for the core PR to be approved and ready. I'll add some mock tests since a full integration test needs a lot of infra setup


Remove unparsed  tag

Incorrect password message was showing the tag text instead of a new line

Hey @Daan-K, as far as I'm aware this is already fixed in 0.5.10 and master? It's fixed by not escaping the HTML rather than removing the  tag though.

OK, I'll close the pr. :-)


The requested image's platform not match

Try to use your docker image, and got the following error:
the requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8). I am using Ubuntu 22.04
any idea how to fix it?
Another question, after I use the web interface to grab a Let's encrypt certificate, where does it saved? I use the following docker compose:
version: '3'
services:
  nginx-proxy-manager:
    image: jlesage/nginx-proxy-manager
    container_name: nginx
    ports:
      - "8181:8181"
      - "8080:8080"
      - "4443:4443"
    volumes:
      - /docker/appdata/nginx:/config:rw

Thanks

the requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8)

This was caused by the fact that image was not supporting arm.  You should no longer have this issue with the latest version.

Another question, after I use the web interface to grab a Let's encrypt certificate, where does it saved?

According to your compose file, everything is saved under /docker/appdata/nginx.

Closing this issue.  Please re-open if needed.


[react-form] fix field type on FormError

Description
Fixes (issue #2448)

The field type on the FormError interface is currently using string[] | null. It should be a string | null (not an string array).

There are multiple tests in packages/react-form/src/hooks/tests/form.test.tsx that test where errors.field is an array and type-checking fails on these cases with this change.
We have hundreds of cases in Shopify's codebases where field is set to an array.
Can you provide a codepen that proves that a case where a string is valid? The nearest I can get is seeing that in propagateErrors we do get(fieldBag, error.field) and the code/documentation for get-value suggests that the second argument can be either a string or an array of strings, and that using an array leads to a slight performance improvement. So it seems at best this should be changed to string | string[] but I am not convinced we should widen this as they we have to teach people about the two format possibilities.

Hi @BPScott ! Thanks for the feedback!
I might have got this wrong.
I was rushing through a Shopify App project and used the @shopify/react-form package.
While using it with @Shopify/polaris components  (TextField) I'm almost certain that the error did not display if I used an string array for the fields, but will double-check and let you know if that was a mistake on my side, otherwise I'll provide a reproducible example.
I'll come back in short, probably on the weekend as I'm trying to meet deadline.
Thanks again for the feedback, and for the awesome Library!


Other avatars execute walk/jump animation while on moving-platforms

Tested replicating the character controller moving platform logic (movign ground detection and replication) and we get inconsistencies with

Comms avatar positioning
Comms platform positioning (the platform must be synched through the messagebus and its position is not the same in both players seeing each other)
Coping with those 2 inconsistencies and replicating the moving ground movements


Booster vaccinations

The raw data published by the RKI now has columns for the booster vaccinations. Would be great if this could be added to the API.

I'll add that now :)
Pull request should come in shortly, if I don't face any major obstacles.

Hi @Viet2503  thanks for your support.

Changes should be done now. Fell free to revise it :)
#51

@Viet2503  i have merge your pull request without checking it 🙈 the api breaks, why i have revert the merge.

@ThisIsBenny
Shit, a comma is missing. Let me fix that quickly.

Hopefully it is fixed now. Do you crate a new PR from my develop branch? @ThisIsBenny
Or should I do that?

@Viet2503 you can do this. you will then also see a vercel deployment. you can use this url to verify that everything is working


Write a TypeScript program to find the maximum sum of a contiguous subarray (circular)

Description
Write a TypeScript program to find the maximum sum of a contiguous subarray (circular)
Maximum sum of a circular subarray is the task of finding the contiguous subarray within a circular one-dimensional array of numbers which has the largest sum. For example, for the sequence of values 10, -3, -4, 7, 6, 5, -4, -1; the contiguous subarray with the largest sum is 7, 6, 5, with sum 18.
Input  : [8, -8, 9, -9, 10, -11, 12]
Output : 22

How to contribute

Save the solution in program/FindTheMaximumSumOfAContiguousSubarray(circular).ts file
Add FindTheMaximumSumOfAContiguousSubarray(circular).ts file in find-the-maximum-sum-of-a-contiguous-subarray-(circular) folder

!assign

Hey @Greeshma-frontier
Sorry but the assignment limit has been set to 20 issues per user.
These limits are set to ensure everyone gets a chance to contribute to Hacktoberfest.
These limits will be lifted after 31st October.
Thank you very much for contributing to this project.

!assign

Hey @Greeshma-frontier
auto-assignment limit has been removed, you can continue contributing to good first issue
Sorry for the inconvenience caused
Thanks for your awesome contributions 🤗


Comparison between two sequences

Can it specify two sequences for comparison and get the predicted value of TMScore of the corresponding structures of these two sequences?Thanks

I hope TMVec can support specifying two sequences as input and then outputting the predicted TMscore, which will facilitate a small number of pairwise comparisons.

Yes it can, but it may require running the python code in the tmvec repo
On Sun, Dec 22, 2024 at 7:55 PM AIM132 @.***> wrote:

I hope TMVec can support specifying two sequences as input and then
outputting the predicted TMscore, which will facilitate a small number of
pairwise comparisons.
—
Reply to this email directly, view it on GitHub
https://github.com/flatironinstitute/deepblast/issues/167#issuecomment-2558805797,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA75VXMZLYRLR7PKNLMSFR32G53S7AVCNFSM6AAAAABUCIL7T2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJYHAYDKNZZG4
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thank you. I'll give it a try

Hello，have you resolved this issue?

https://github.com/tymor22/tm-vec/blob/master/tm_vec/tm_vec_utils.py#L45-L49
Its all in the source code, although documentation needs some work.


rocALUTION changes to support multiple ROCM installation

Hard coded reference to /opt/rocm is parameterized
to CMAKE_INSTALL_PREFIX
Package is generated to install into ROCM_INSTALL_PATH if
defined in the env otherwise default into /opt/rocm
RUNPATH is set in the lib only if ROCM_RPATH env is defined
with the rpath

Signed-off-by: Pruthvi Madugundu<EMAIL_ADDRESS>

Updated the changes and removed the usage of CMAKE_INSTALL_PREFIX to search for library path.
Please check the latest commit.


[Question] Quick start doc dose not work.

Search before asking

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

Question
I tried to start runtime by following the quickstart doc.
In root directory:
gradle clean dist
Dist result:

At the bin directory:
sh start.sh
then the error occurs

I found the default plugin path is
org.apache.eventmesh.spi.loader.JarExtensionClassLoader#EVENTMESH_EXTENSION_PLUGIN_DIR

It's seems like the default plugin path is mismatch from the structure of dist result.

@ruanwenjun can you take a look?

you should excute gradle clean jar dist first and then execute gradle installPlugin please. @horoc

you should excute gradle clean jar dist first and then execute gradle installPlugin please. @horoc

I have tried, but It's not work for me, the errors in log file is the same.
I tired to change the default plugin path in code, and It's seems works. 😂

@horoc Thanks for your feedback. If you try to start from source code, you can use -DeventMeshPluginDir=your_plugin_path to set the plugin directory. We will optimize this later.

please confirm that you have configured the  default plugin path dist/plugin in your jvm options. @horoc

@horoc Thanks for your feedback. If you try to start from source code, you can use -DeventMeshPluginDir=your_plugin_path to set the plugin directory. We will optimize this later.

 please confirm that you have configured the  default plugin path -DeventMeshPluginDir=dist/plugin in your jvm options. @horoc

Thanks for your help ~


Updatetypeconfigure

Allow update types to be configured in the parameter server (this includes custom update types)

Build triggered. sha1 is merged.

Build finished. No test results found.

Refer to this link for build results (access rights to CI server needed):
/job/nd4j_PR/488/


tikv_util: Allow building on FreeBSD

What is changed and how it works?

Issue Number: Close #15015
What's Changed:

Building tikv_util is now possible on FreeBSD

Related changes
Check List
Tests

Manual test (add detailed scripts or steps below)

Release note
None

% cargo build --keep-going -Z unstable-options
warning: profile package spec `tirocks-sys` in profile `dev` did not match any packages
   Compiling tikv_util v0.1.0 (/usr/home/dveeden/dev/tikv/tikv/components/tikv_util)
    Finished dev [unoptimized] target(s) in 5.42s
% freebsd-version
13.2-RELEASE-p1

/check-issue-triage-complete

/check-issue-triage-complete

/retest

/cc @sticnarf @BusyJay

/merge


feat(module:tooltip,popconfirm,popover): support OnPush

add subject to support changeDetection of OnPush
change showcases’ changeDetection to OnPush
PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Application (the showcase website) / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information

Coverage remained the same at 52.233% when pulling 1fb8d6ed63e785721f705480a128c58ead4151df on csyszf:observable into 143c080cf6147793ad5972e2e3d4bb805d9d71e8 on NG-ZORRO:master.

please also update popover since it extends tooltip.

Coverage decreased (-11.9%) to 40.371% when pulling 48be609bc56c3b0d23893eaf8618d114885ce3f1 on csyszf:observable into 143c080cf6147793ad5972e2e3d4bb805d9d71e8 on NG-ZORRO:master.

@vthinkxie fixed.

@csyszf thanks for your pr, would you please remove the duplicated commit history and keep the commit history clean.

@vthinkxie I've rebased the commit history, Is this okay？

@csyszf thanks.


New version: still no collapsed folders or wordwrapped folder names

Checklist

[X] I have used the search function to see if someone else has already submitted the same feature request.
[X] I will describe the problem with as much detail as possible.
[X] This issue only contains a request for one single feature, not multiple (related) features.

App version
6.601
Problem you are trying to solve
Folders are extremely difficult to navigate, partly because they are fully expanded, so one has to scroll a long way to find anything; and also because they are severely concatenated instead of wordwrapped and take up less than the width of the screen, so that a huge amount of the folder path is replaced with three dots.
Suggested solution

Please could the folders be collapsed until one expands them? I have about 10 main folders but many hundreds of sub-folders and sub-sub-folders, so finding a folder when they are all fully expanded is almost impossible.

Please could the folder names be wordwrapped instead of concatenated (ideally by default but at least as an option in settings) and take up the full width of the screen - as they already when you select "Manage Folders"?

The lack of these two features have been a serious drawback to using K9Mail for a long time, so it's extremely disappointing that you've just released a major upgrade without addressing this. IMO it's far more important than any of the mostly cosmetic changes that you've made.
Dave
Screenshots / Drawings / Technical details
No response

Improving the folder view is on the roadmap.
Duplicate of #630


[BR] trims the last characters from the bottom if the caret is at the very bottom of the screen

trims the last characters from the bottom if the caret is at the very bottom of the screen
(if you print underscores, they are not displayed at all)

Can you give us steps to reproduce this? versions of os/atom/termination? a gif showing the behavior would also help.

win7
atom 1.52.0 x64
termination 0.7.6
the problem has been corrected as follows:
styles.less
div.terminal {
top:-5px;
margin-top: 5px;
}


Support for multifields via attributes

Hi,
is it possible to map multifields via attributes in POCO?
Right now I cannot use fluent mapping. I have two independent services which communicates over rabbit. As I found out, I can directly map each specific object type by client fluent mapping but that would introduce dependency to second service because it would has to have knowledge of all services is using it or might in the future and also it has to have such POCO objects in its code.
Via attributes it looked like a decent level of decoupling. But I cannot create client on first service.
Is there way how to achieve that?
Thank you for any advice

The issue with attribute mapping is that C# Attributes are limited to properties that accept constant values, which makes it tricky to express all properties available on Elasticsearch field datatype mappings.
Looking at the problem from another angle, it sounds like index templates and dynamic templates may be an option here?

Thanks for opening @OndrejPiza. It is unlikely that multifields will be configurable through attributes.
Multifields can be configured through fluent mapping, or can be applied through convention using index templates and dynamic templates.


ladspaPlugins-git: 2015-03-04 -> 2016-08-17

Motivation for this change
Things done

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

[x] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

closed due to upcoming PR for https://github.com/swh/ladspa/releases/tag/v0.4.17


Keyboard in webviews breaks on android 12

USER report:
TF Connect doesn't trigger keyboard activation on android, so not able to write in a message in the input field.
copy past works.
We can reproduce locally as well, but only on android 12, even works in emulator. Will need to be patched in next version especially as more phones start updating to android 12.

Fix pushed to production and validated to work.


Clean twitter CSS

Currently tweets are not looking good, the goal is to find a way to make them look like real embed tweets provided by Twitter publisher.
We can't use the script provided by twitter as it doesn't work as a content script and I'm waiting currently waiting for an answer from Twitter dev forum
Because the script doesn't work we can't use createTweet or even load.

hello

Closed with #19


Update permalinks and ADRs to new code

we're in a chicken and egg situation because the permalink https://github.com/celestiaorg/celestia-app/blob/6f3b3ae437b2a70d72ff6be2741abb8b5378caa0/x/payment/types/tx.pb.go#L32-L40 still points to the old name. Super minor but after this PR merges, we can update the permalinks to reference the lines of code with the new name
Originally posted by @rootulp in https://github.com/celestiaorg/celestia-app/pull/978#discussion_r1016807260
we should update the permalinks after we merge the name changes to blob instead of payment/pay

The instance cited in the comment was resolved in https://github.com/celestiaorg/celestia-app/commit/f67acced1d0de28c6d8d0b583390dcdf70ba91d5. Some of the other permalinks in ADR 008 link to old code but those references are still valid (i.e. CreateCommitment)


Merge "Data Models" and "X Schema" docs

This issue can wait until after we've got block structure validation and a Block Schema page in the server docs.
Then the top-level structure of the server docs will be:

Data Models

The Transaction Model
The Digital Asset Model
Crypto-Conditions and Fulfillments
The Block Model
The Vote Model

Transaction Schema
Vote Schema
Block Schema

It would be nice to merge those somehow, because there's some repetition of information.
The Transaction Model page begins with the top-level JSON structure of a transaction:
{
    "id": "<hash of transaction, excluding signatures (see explanation)>",
    "version": "<version number of the transaction model>",
    "fulfillments": ["<list of fulfillments>"],
    "conditions": ["<list of conditions>"],
    "operation": "<string>",
    "asset": "<digital asset description (explained in the next section)>",
    "metadata": "<any JSON document>"
}

It's really nice to have that, but maybe it could be put at the top of the Transaction Schema page instead, and then The Transaction Model page could be deleted. That top-level JSON structure (shown above) could even be auto-generated, but that would require adding a "short description" field to the YAML file.
Similar things could be done for votes and blocks.
As for the pages titled The Digital Asset Model and Crypto-Conditions and Fulfillments, their contents are already in the Transaction Schema page. Better explanations should be written for how to use them, but I think that's outside the scope of this issue: that can be handled with user guides, tutorials, driver usage examples, etc.
The resolution of this issue would result in server docs with the outline:

Transaction Schema
The Digital Asset Model
Crypto-Conditions and Fulfillments
Vote Schema
Block Schema

The pages titled The Digital Asset Model and Crypto-Conditions and Fulfillments might be put after Block Schema instead. (It's a matter of taste.) Those two pages should really be expanded, but that's another issue (or more).

The docs about the transaction model are moving elsewhere so I'm closing this issue as defunct.


Anthropic default max tokens is less than Anthropic allows (4096 should be max, but restricted to 2048)

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain.js documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain.js rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code
n/a
Error Message and Stack Trace (if applicable)
No response
Description
https://github.com/langchain-ai/langchainjs/blob/05c4c761464d43d76ffaf9ff2703395c0933fbcc/libs/langchain-anthropic/src/chat_models.ts#L453
Restricts max_tokens to 2048.
Anthropic says max tokens for all models is 4096: https://docs.anthropic.com/en/docs/models-overview#model-comparison
System Info
n/a

Thanks for the issue!
It's definitely a bit arbitrary but you can set it manually, and different models may have different max tokens so it's a losing battle to try to tie it to any specific number.

IIRC Anthropic had very low limits (like 128 tokens) at some point in the past - I'm not sure if that's changed but I don't have a problem with the default as it currently is


Design of Settings page

We can access to the Notifications page using the Account Menu

of from the Main Menu

To send notification to Slack or Teams we need to install first the app Incoming WebHooks. With that app installed inside Slack or Team you are going to have a url token like this, that we are going to use to send the notifications:https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXX
URL: Url Token
Method: POST
Payload: {"text":"{{notification}}"}

Link: https://docs.reconness.com/account/notifications


[bug] '@stablelib/random' does not contain a default export (imported as 'Bo').

Link to minimal reproducible example
<EMAIL_ADDRESS>Summary
Attempted import error: '@stablelib/random' does not contain a default export (imported as 'Bo').
List of related npm package versions
"@web3modal/wagmi": "5.1.0"

Clone #2710


Upgrading from 1.2 to 1.3/1.4 breaks our installation

Describe the bug
Upgrading Knative Operator and Serving from 1.2 to 1.3 or 1.4 via causes the following error message to appear continously:
E0505 16:30:24.897362       1 reflector.go:138] k8s.io/client-go@v0.22.5/tools/cache/reflector.go:167: Failed to watch *v1beta1.KnativeServing: failed to list *v1beta1.KnativeServing: conversion webhook for operator.knative.dev/v1alpha1, Kind=KnativeServing failed: Post "https://operator-webhook.default.svc:443/resource-conversion?timeout=30s": x509: certificate is not valid for any names, but wanted to match operator-webhook.default.svc

Reverting to 1.2 is not possible either:
CustomResourceDefinition.apiextensions.k8s.io "knativeservings.operator.knative.dev" is invalid: status.storedVersions[1]: Invalid value: "v1beta1": must appear in spec.versions

Expected behavior
Upgrading the Operator as documented should leave the cluster in a functional state.
To Reproduce

Install GKE 1.21 (or 1.22 if upgrading to Knative Operator 1.4)
Install Istio 1.12
Install Knative Operator and Serving 1.2
Run the following:

kubectl apply -f https://github.com/knative/operator/releases/download/knative-v1.3.2/operator.yaml
kubectl create -f https://github.com/knative/operator/releases/download/knative-v1.3.2/operator-post-install.yaml
kubectl logs -f deploy/knative-operator

The operator log shows the above error message continously and the storage-version-migration-operator Pod goes into a crash loop.
Knative release version
1.2 initially, upgraded to 1.3 or 1.4

/assign @houshengbo

I think I found the problem: we're using Istio's mTLS and sidecar injection features. Especially the second part seems to interfere with the new operator-webhook service. When I disable sidecar injection on the default namespace before the Knative upgrade, everything appears to work normally.
It seems like the operator-webhook deployment should have a sidecar.istio.io/inject: false annotation, like knative-operator.


Prop "as" of styled components can be a component

From my tests, you can pass a component successfully to as (e.g. <StyledBtn as={WhateverComponent} />), but a type error is shown if you don't pass a string:

Type 'WhateverComponent' is not assignable to type 'string'. ts(2322)

Types should be expanded to allow for more values here.

I honestly don't see a great reason to add this. Polymorphic types like this make Typescript quite a lot slower and also are harder to ensure the correctness of. If you see yourself often using the as prop, maybe convert the styled("button", styles) to recipe(styles) and use it as <WhateverComponent className={buttonStyle} />?

Thanks, that helps 😄


[Bug] Popout player is far too large on big displays (tablets)

Describe the bug
On tablets, popout mode's minimum size is way too large. It can be expanded to be larger, but not reduced. There's also an excessive amount of deadspace (probably as a direct result of the minimum size being too large).
output.webm
To Reproduce
Use 8vim on an device with a large screen.
Expected behavior
Popout mode should allow me to adjust the size to my liking without a care in the world. A configurable minimum size in the settings menus would be great - that way it could be adjusted per user per device. If you're concerned about users accidentally adjusting this too low, then simply hide it behind an "Expert Mode" tickbox/switch.
Screenshots

Smartphone:

Device: Samsung Tab S8+ (SM-X800)
OS: Android 14
Version: 0.17.4

Additional context
Default DPI scaling and display/font size.

Thank you .
Yes currently there isn't any min/max configurable. it's the min of the screen height/width * 0.6/0.8. we could have an option for that.
What do think of adding an option for the min factor (0.6) and the max (0.8)?


[common] [paraflow-commons] logger system

Implement paraflow-commons logger system.

Use log4j as default logger system.


Service calls not working on sub-buttons

Describe the bug
I'm having bad luck with call-service actions on sub-buttons. The services are not being called.
I think it is interferring with double_tap_action. If that is set to "none", then tap_action and hold_action also don't work.
If you define double_tap_action, then tap_action and hold_action will start working as well. The same seems to apply if you for example set hold_action to "none". Then also tap_action and double_tap_action will stop working.
To Reproduce
      - type: custom:bubble-card
        card_type: button
        entity: light.lampen
        name: Lampen
        tap_action:
          action: toggle
        double_tap_action:
          action: more-info
        hold_action:
          action: none
        button_action:
          tap_action:
            action: navigate
            navigation_path: "#popuptest"
          double_tap_action:
            action: none
          hold_action:
            action: none
        sub_button:
          - entity: binary_sensor.pc
            name: PC
            tap_action:
              service: light.toggle
              target:
                entity_id: light.lamp
            icon: fas:computer
            hold_action:
              action: call-service
              service: button.press
              target:
                entity_id: button.lamp
            double_tap_action:
              action: none

Expected behavior
Service being called when tapping on respective sub_button (PC), even when double_tap_action is not defined or defined as "none"
Screenshots
n/a
Informations (please complete the following information):

OS: Win11 / iOS
Browser: Firefox / Safari
Bubble Card version: 2.0.0-beta.6
Home Assistant version: 2024.5.1

Additional context
n/a
Thank you! 🍻

This issue is now fixed in the latest beta 🥳 Thanks again for the feedback!


Feature/sort graph

Solves
Adds Transform to sort graphs topologically
Dependencies

new package dep:  toposort  (tested with version 1.5)

Test
transformation/test_sort_graph.py

if run as main does a performance test

Notes

Small change to find_producer that should make it run twice as fast on average

Tests Fail because of new package dependency: toposort


MesosOperatorMasterDriver cannot subscribe to events

Using the latest version of PyMesos 0.3.4, I cannot receive any events using the operator API. It looks like the SUBSCRIBE request is not sent, from my initial investigation.
On PyMesos 0.3.3, after calling driver.start(), I get a log message similar to the following:
Operator client subscribed with cluster state: ...

However, on 0.3.4, no such log is present, and any task updates or agent updates will not notify the operator.
I believe this can be reproduced with the basic examples provided. Falling back to PyMesos 0.3.3 fixes this issue, which seems like #98 introduced a regression.

I added some logging in process.py after line 300:
while True:
	logger.info('process=%s,conn=%s,master=%s', self, conn, self._master)
	if not conn and self._master:
		conn = Connection(self._master, self)
		logger.info('process=%s, conn=%s', self, conn)

Notice how the self._master variable is always None for MesosOperatorMasterDriver:
framework_1      | 2018-07-27 18:04:40.172|INFO|process=<pymesos.scheduler.MesosSchedulerDriver object at 0x7fbf17bea450>,conn=None,master=None
framework_1      | 2018-07-27 18:04:40.177|INFO|process=<pymesos.operator_v1.MesosOperatorMasterDriver object at 0x7fbf17bea650>,conn=None,master=None
framework_1      | 2018-07-27 18:04:40.183|INFO|process=<pymesos.scheduler.MesosSchedulerDriver object at 0x7fbf17bea450>,conn=None,master=mesos-master:5050
framework_1      | 2018-07-27 18:04:40.187|INFO|process=<pymesos.scheduler.MesosSchedulerDriver object at 0x7fbf17bea450>, conn=<pymesos.process.Connection object at 0x7fbf17beaf10>
mesos-master_1   | I0727 10:04:40.189290    15 http.cpp:1185] HTTP POST for /master/api/v1/scheduler from <IP_ADDRESS>:49914
mesos-master_1   | I0727 10:04:40.189538    15 master.cpp:2610] Received subscription request for HTTP framework 'scheduler'
mesos-master_1   | I0727 10:04:40.189677    15 master.cpp:2745] Subscribing framework 'scheduler' with checkpointing disabled and capabilities [ TASK_KILLING_STATE, GPU_RESOURCES ]
mesos-master_1   | I0727 10:04:40.189718    15 master.cpp:7195] Updating framework 0bc93f09-207f-4528-9b20-d2f0527286c7-0000 (scheduler) with roles {  } suppressed
framework_1      | 2018-07-27 18:04:40.188|INFO|process=<pymesos.scheduler.MesosSchedulerDriver object at 0x7fbf17bea450>,conn=<pymesos.process.Connection object at 0x7fbf17beaf10>,master=mesos-master:5050
framework_1      | 2018-07-27 18:04:40.190|INFO|process=<pymesos.scheduler.MesosSchedulerDriver object at 0x7fbf17bea450>,conn=<pymesos.process.Connection object at 0x7fbf17beaf10>,master=mesos-master:5050
framework_1      | 2018-07-27 18:04:40.195|INFO|scheduler_re_registered|master={'hostname': 'mesos-master', 'port': 5050, 'version': u'1.5.0'}
framework_1      | 2018-07-27 18:04:40.195|INFO|process=<pymesos.scheduler.MesosSchedulerDriver object at 0x7fbf17bea450>,conn=<pymesos.process.Connection object at 0x7fbf17beaf10>,master=mesos-master:5050

I reproduce this problem with operator_v1.py in examples. I notice that _send is failed only if try to connect mesos slave directly.

See https://github.com/irvinlim/pymesos-0.3.4-bugrepro for what I mean. The operator is not able to subscribe to any events when using version 0.3.4.
Using the example code, I connected to the master directly with python operator_v1.py mesos-master:5050.

Thanks very for your bug report repo.

Thank you for the fix! 👍
Can I get you to publish a new version of the package when you can? Thank you!

Done (https://github.com/douban/pymesos/releases/tag/0.3.5)

@ariesdevil 多谢了🙏


What are valid LDAP URLs?

In general_name.py, I saw the following code:
def validate_value(self, node):
     value = str(node.pdu)
     if value.casefold().startswith('ldap://'.casefold()):
         raise validation.ValidationFindingEncountered(self.VALIDATION_LDAP_URI_NOT_VALIDATED, value)

This means that if the ldap URL starts with ‘ldap://’, an error will be reported.
And I have conducted an experiment. If the Issuing Distribution Point field of CRL contains the following ldap URL 'ldap://ldapcomp.cert.fnmt.es/CN=CRL1,OU=AC%20Componentes%20Informaticos,O=FNMT-RCM,C=ES?certificateRevocationList;binary?base?objectclass=cRLDistributionPoint', then this error will appear. But this is indeed a correct URL. I can directly use the 'curl' command to obtain the CRL through this URL.

Hi @zzzsz,
That finding is a NOTICE-level finding that indicates the validator does not check the syntax of LDAP URIs. It is not an indication that the LDAP URI has incorrect syntax (such a finding would be ERROR-level).
When I originally added that finding, my intention was to add a proper LDAP URI validator. However, given that several policies are prohibiting LDAP URIs (S/MIME BR being the latest), I'm not sure of the value of such a check.

Hi @zzzsz, That finding is a NOTICE-level finding that indicates the validator does not check the syntax of LDAP URIs. It is not an indication that the LDAP URI has incorrect syntax (such a finding would be ERROR-level).
When I originally added that finding, my intention was to add a proper LDAP URI validator. However, given that several policies are prohibiting LDAP URIs (S/MIME BR being the latest), I'm not sure of the value of such a check.
Does this information help resolve this question?

Yes, thank you.


UserLocation no longer visible in 10.0.0-beta.22 and version 10.7.0

Environment
$RNMapboxMapsImpl = 'mapbox'
$RNMapboxMapsVersion = '~> 10.7.0'

@rnmapbox/maps Version #main Installing rnmapbox-maps 10.0.0-beta.22 (was 10.0.0-beta.18)
Platform: iOS
React Native Version 0.68.2
Platform OS: iOS 15.5
Device: iPhone 13
Emulator/ Simulator: yes
Dev OS: MacOS 12.4

Standalone component to reproduce

import React from 'react';
import {
  MapView,
  UserLocation,
} from '@rnmapbox/maps';

class BugReportExample extends React.Component {
  render() {
    return (
      <MapView style={{flex: 1}}>
         <UserLocation
            showsUserHeadingIndicator
            visible
          />
      </MapView>
    );
  }
}

Observed behavior and steps to reproduce
User location icon doesn't show
Expected behavior
User location icon shows

This one renders user location for me.
import React from 'react';
import { MapView, UserLocation, Camera } from '@rnmapbox/maps';

class BugReportExample extends React.Component {
  render() {
    return (
      <MapView style={{ flex: 1 }}>
        <Camera followUserLocation={true} />
        <UserLocation showsUserHeadingIndicator visible />
      </MapView>
    );
  }
}

export default BugReportExample;

@mfazekas found a mistake on my end. Thanks and sorry for the trouble!


Unignore aarch64-linux-android

Let's see if the NDK update changes something.

@bors r+

:pushpin: Commit 0a4b9ced31a7356c42d6b1b148829fcb531dcabb has been approved by JohnTitor
It is now in the queue for this repository.

:hourglass: Testing commit 0a4b9ced31a7356c42d6b1b148829fcb531dcabb with merge b01f41bea3c9ff77b9d402dfcc6af56840f16a89...

:broken_heart: Test failed - checks-actions

@bors r+

:hourglass: Testing commit 41aaff86a8b6066acb4f87c27777ebe97b87848f with merge 8df2603a56efa283728d11703a8a9a690cfc62b0...

:broken_heart: Test failed - checks-actions

@bors r+

:pushpin: Commit 5b7def1099bcd8409efd73b54d783c8c6a0bba92 has been approved by JohnTitor
It is now in the queue for this repository.

:hourglass: Testing commit 5b7def1099bcd8409efd73b54d783c8c6a0bba92 with merge e066f088b0a03c5589f257ecdc07e070541855e3...

:broken_heart: Test failed - checks-actions

@bors r+

:pushpin: Commit b0e6ce1d105d0d142d5d85e0147ea7bf7d97e060 has been approved by JohnTitor
It is now in the queue for this repository.

:hourglass: Testing commit b0e6ce1d105d0d142d5d85e0147ea7bf7d97e060 with merge 3195caf241ff1d2059dc353afb9b97da1400e4b6...

:sunny: Test successful - checks-actions, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13, checks-cirrus-freebsd-14
Approved by: JohnTitor
Pushing 3195caf241ff1d2059dc353afb9b97da1400e4b6 to main...


Documentation doesn't explain how to open alert

Explanation about alert dialog in readme is missing. I think this.$dialog.alert needs to be added as it's not mentioned anywhere except if you go look at source or docs folders in repo.

@maxorlovsky That's correct. this.$dialog.alert('The alert message') opens the alert dialog and it escaped the documentation. Would you like to send a PR fixing that or have me update it in my spare time?


[WIP] Featured content container query testing

Fixes JIRA ticket xxx
This PR does the following:

Testing swapping media queries for container queries in FeaturedContent component.

How has this been tested?

Accessibility concerns or updates

Checklist:

[ ] I have updated the Storybook documentation accordingly.
[ ] I have added relevant accessibility documentation for this pull request.
[ ] All new and existing tests passed.

Front End Review:

[ ] Review the Vercel preview deployment once it is ready.

@oliviawongnyc and @jackiequach
It's interesting that you had to include two container queries with unique width values in order to trigger the changes at our mobile breakpoint.  Why would text element and the image element be reading different width values?

Adding @7emansell as a draft reviewer since she knows FeaturedContent very well.
Emma, this is what I'm thinking about when reviewing this draft: at some point, the DS and maybe the entire department will move to container queries. Before that happens, does the update for this component make sense? Is it easy to read and know what's going on? How does it compare to media queries in terms of syntax and how we create components.
Just some questions to start, but do feel free to point out other things or ask other questions.

@oliviawongnyc and @jackiequach It's interesting that you had to include two container queries with unique width values in order to trigger the changes at our mobile breakpoint. Why would text element and the image element be reading different width values?

@bigfishdesign13, Jackie and I are discussing this now. We are not sure why the container breakpoints are different if the media query breakpoint was the same for both, but we were measuring the container while changing the screen size and we chose the breakpoints based on when we saw the styles being applied. Jackie did notice that the difference between 568 and 600 px is 32, which is the value of our large spacing variable, but we tried to remove the padding: "l" from the text element and that didn't seem to change anything.

This looks great! I think you and @oliviawongnyc should create a working feature branch where all work in progress and reviewed code can go into. This bigger feature branch would be in "under review" stage until the next step where  a TAD or other documentation is worked on.


EKF2 split output predictor and publish attitude immediately

Requires https://github.com/PX4/ecl/pull/471
The EKF is updated to run the output predictor immediately after receiving new IMU data. Then PX4 side we publish vehicle_attitude immediately, and only publish positions at the EKF predication rate (every 8 milliseconds).

@bkueng @RomanBapst Would be great if you could review & quickly flight-test.

This lowers EKF2 cpu usage considerably.
For example current EKF2 in master running a stock pixracer with active GPS fusion is ~14-16% cpu. With this PR it drops to around 10%.

Replay testing is showing https://github.com/PX4/ecl/pull/471 giving larger logged output observer tracking errors than ecl master so I will investigate further.

@dagar has fixed the difference so it should now be good to flight test provided  we use https://github.com/PX4/ecl/pull/471 at commit  aaff047e5852761f8d15bc695c7a1ca70beeeeb1

@priseborough @dagar px4/ecl commit aaff047e5852761f8d15bc695c7a1ca70beeeeb1 hasn't been merged yet, do we need to wait for that commit to be merged or can we test this pull request as it is right now? we use to download the firmware from Jenkins artifacts.

Yes in this case it's okay to use the artifacts directly from Jenkins, but it was a good thing to check when other submodules are involved.

a few flights on a pixracer (V4)
manual flight
https://logs.px4.io/plot_app?log=5920d2d1-36d8-47b1-918d-47bb85a45ef2
https://logs.px4.io/plot_app?log=4cc7676e-ae05-4f39-a64b-b55b39730d43
full auto from take-off to landing
https://logs.px4.io/plot_app?log=74ad4749-0a4b-4617-b2ee-c7e08194524f
https://logs.px4.io/plot_app?log=715517bf-e64d-493e-b954-1a7186fc297c
stable flights; didn't run into any issues

For reference here's a close comparison from master (same vehicle, same flight).
Master: https://logs.px4.io/plot_app?log=33cff20f-ef72-44ff-ba9d-440e26f352a0
PR: https://logs.px4.io/plot_app?log=74ad4749-0a4b-4617-b2ee-c7e08194524f
CPU usage before

CPU usage after

Few flights with pixhawk 4 (V5).  Good flights, no issues.
https://review.px4.io/plot_app?log=0c36c73e-9881-4c6a-9cb6-bb95da46213a
https://review.px4.io/plot_app?log=fb23fb62-e7e5-42b9-82ad-577bd6bab31f
https://review.px4.io/plot_app?log=7c99b336-20f8-488f-9753-62d7aa1cd0b5
few flights with pixhawk 2.1 (v3). Good flights, no issues.
https://review.px4.io/plot_app?log=8054ec6d-142d-468b-bec0-cbf2d1d8f252
https://review.px4.io/plot_app?log=9d2ae4b6-1d66-4122-bccb-7a9152f25594
https://review.px4.io/plot_app?log=b632cd82-b9b5-4341-bb62-a6127e409f8a

test flight = pixhawk mini good flight
https://logs.px4.io/plot_app?log=c5949d93-cbae-4841-8123-cbeade843571
pixhawk pro v4 good flight
https://logs.px4.io/plot_app?log=ce4bc8e9-c2ea-4288-bdc3-edcb2a89a1af
pixhack v5 great flight
https://logs.px4.io/plot_app?log=f5ae3251-e4fa-4e1b-bec8-0e9d7a5471da


Feature: Codegen from JPA metamodel (support JPA and Hibernate legacy HBM mapping files)

Currently codegen for JPA is done using an APT plugin that checks the annotations on the code. While this works perfectly fine for most applications, JPA has alternative ways of associating entities with the metamodel. The JPA spec defines an entity-mapping XML format, and also Hibernate has its own properitairy / legacy XML mapping support. It could be interesting to also support these XML's for codegen (provided that an ORM implementation is available during Maven plugin execution).
This would open the doors to users stuck in old projects that still depend on these kinds of mappings (one of which I am unfortunately working on now...)

This is exactly what the JPADomainExporter does. So its already there 😉

This is exactly what the JPADomainExporter does. So its already there 😉


menu closing state

If I click on the submenu it closes the parent menu. Any way not to do that?

You can set the keepOpen prop on the event object of onClick/onItemClick to prevent a menu from closing.
Here is a sandbox example, try to click "Paste" item in the submenu.
You can also do it for all items in the menu by setting keepOpen in onItemClick event on the root menu.


Q: Is it possible to get a list of variables from a parsed or compiled expression?

Title says it all... I'd like to read in an arbitrary expression and find out what variables need binding (so I can look them up).

I think I figured it out: Evaler::var_names?


fix(webpack): always resolve core-js to v3

Types of changes

[x] Bug fix (a non-breaking change which fixes an issue)
[ ] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
@babel/polyfill translates : var b = new Map(); into import "core-js/modules/es6.map"; var b = new Map(); thus webpack tries to require node_modules/core-js. In case of package-manager hoists core-js@2 in node_modules and moves core-js@3 to node_modules/@nuxt/babel-preset-app/node_modules we will get into trouble. This PR forces webapck to correctly resolve from correct version of core-js.
Fixes nuxt-community/pwa-module#170
Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[ ] I have added tests to cover my changes (if not applicable, please state why)
[ ] All new and existing tests are passing.

Codecov Report

Merging #5307 into dev will increase coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              dev   #5307      +/-   ##
=========================================
+ Coverage   95.66%   95.7%   +0.03%
=========================================
  Files          74      74
  Lines        2513    2513
  Branches      639     639
=========================================
+ Hits         2404    2405       +1
+ Misses         92      91       -1
  Partials       17      17

Impacted Files
Coverage Δ

packages/webpack/src/config/base.js
95.5% <ø> (ø)
:arrow_up:

packages/vue-renderer/src/renderer.js
92.07% <0%> (+0.49%)
:arrow_up:

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 c46def7...8a3a76d. Read the comment docs.


Boxing

Is there a reason to support both boxing inline and as a separate process? Otherwise I would suggest to remove the inline-boxing, your solution is way more comfortable.

Main initial reason was to ensure that background mode wasn't breaking anything. However, it might be worth retaining at least for a bit. With the current background code it is possible to get multiple MPBox tasks launched if several video captures are close together. That in itself isn't a problem but I think MPBox uses a fair amount of memory and that can then get challenging on a Model A.
I had thought an improved scheme was to add a cmd line queue into raspimjpeg for this so that the stop video would add the command to the queue and a launcher (inside main loop) could execute them one at a time. Most of the time it would operate like now, but it would then be safe to always run that way.

Well, the perfect solution to this in my opinion would be a separate process with a queue as you suggested, but this process could box as many files as the ressources (cpu + ram) allow without making the interface slowly.
But to be honest, this isn't so necessairy, maybe your solution with the choose between inline and all at once is good enough.


v2.1.1

@Eomm I know, and would love to do it like that, but it says main is a protected branch now
I was going to ask if this is a new thing actually - if not, could you disable that rule?

@gurgunday Fixed
Try again 👍🏼

@Eomm still seeing the following:

PTAL
Anyway, you are not using releasify 😭

I swear it was on my mind to switch to it 🤣
Will use that if I can now 🙏


Current builds on master are broken

Currently, we have broken builds on master
https://app.travis-ci.com/github/EugenMayer/docker-image-unison/builds/254897422
Most probably some patches have changed or something else changed on the static assets we require.

@EugenMayer I was able to reproduce the error. The UNISON_VERSION being passed into that failing build is 2.51.4_rc2.
If you rerun the build with UNISON_VERSION=2.51.4 (or 2.51.5 latest legacy version) it should complete successfully.

@yoseph1998 interresting. Now what i ask myself is, what we used _rc2 in the first place. Still, we might just consider going on 2.51.5.
AFAIR one of the issues is, that the versions have to match with the OS version, right. So what ever runs / is installed on MacOS using brew right now, needs to be offered as counterpart as an image.
With the most recent MacOS / brew, what unison is installed?

@EugenMayer Not sure why rc2 is being used, quick google tells me rc2 is release candidate 2 which makes this even more peculiar as that's not even the final release (If i understand it correctly).
The most recent version in brew is 2.52.1 https://formulae.brew.sh/formula/unison
Might need to make a PR to update that version inside the container constants for consistency.

@EugenMayer Created a PR to update the constants inside the Dockerfile https://github.com/EugenMayer/docker-image-unison/pull/31

Thank you for taking this one on @yoseph1998 !


medication dispense process validation fix

https://github.com/edenlabllc/ehealth.api/issues/3342

Coverage remained the same at 88.43% when pulling 4206bc43e6d9f393e200b270dde417db132b8048 on dispense_with_ds_fix#3342 into 566b03c65737368dc9a6f2c2c1165ec127aa4ecb on develop.


Improve the site design

Update sphinx_rtd_theme to the latest version
Fix logo and project badge sizes on mobile view
Hide the Github fork ribbon on mobile view because it hides the site
menu button
Do not increase the content width infinitely; center the content
instead because a wide page harms readability.
Extract JavaScript code into separate files
Add the 'Edit on GitHub' link

Screenshot:

Current coverage is 64.09% (diff: 100%)

Merging #312 into master will increase coverage by 0.10%

@@             master       #312   diff @@
==========================================
  Files           310        310
  Lines         12236      12236
  Methods           0          0
  Messages          0          0
  Branches       1790       1790
==========================================
+ Hits           7830       7843    +13
+ Misses         3584       3562    -22
- Partials        822        831     +9

Powered by Codecov. Last update 1e6b034...81a3771

👍

Thanks, @delegacy !


fix: fix address undefined error

I came across this error when creating a DHT on a local network. If addr.host is a private or bogon address, then address can end up being null (because for some reason reply is null the first time that connect() is called), which results in an uncaught error.

I think the from === null thing is a bug actually

Yeah thought it might be. I'm afraid I don't really know enough about the internals to fix that one.

Should be fixed in master now


Use proper Logger instead of print

In order to make the logging easier and to not clutter the console, we should use logging instead of print and agree upon a common schemata (log-levels etc.).

replaced std::couts with glog commands, except in test code
for simplictiy, we use the provided log levels and macros of glog. (LOG_EVERY_N, VLOG, DLOG...)


cmd/server: require auth token on watches

Fixes: https://github.com/moov-io/ofac/issues/42

Codecov Report

Merging #51 into master will decrease coverage by 0.04%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##           master      #51      +/-   ##
==========================================
- Coverage   58.32%   58.28%   -0.05%
==========================================
  Files          17       17
  Lines        1219     1237      +18
==========================================
+ Hits          711      721      +10
- Misses        421      427       +6
- Partials       87       89       +2


spirv-cross bad code and abort error

I try to ship optimized OpenGL code in my game EvoLife. Without this steps the shader compilation takes longer on first launch. My optimizing pipeline:
glslang --quiet -G -S <stage> -o <filename>.spv <filename>.glsl
spirv-opt -Oconfig=glsl_opt_config.cfg -o <filename>_opt.spv <filename>.spv
spirv-cross --version 430 --no-es --output <filename>_opt.<stage>.glsl <filename>_opt.spv

My problem is that I can not run spirv-opt with -O, I have to use -Oconfig with the file attached. My starting point was the -O list and I bisected which options cause issues.
glsl_opt_config.txt
Line 3 --merge-return: causes glsl shaders to behave differently than unoptimized versions
Line 4 --inline-entry-points-exhaustive: can not run without merge-return
Line 40 and 43 --merge-blocks: causes spirv-cross to abort on some shaders if line 3 --merge-return and line 4 --inline-entry-points-exhaustive are enabled,  here
assert(loop_header_block.merge == SPIRBlock::MergeLoop);
Enabling line 3 merge-return adds an uninitialized bool variable that is used as the condition for breaking out of the do {} while(false) loop that is replacing the body of the function.
Please let me know how can I help to resolve this problem. In the meantime maybe others will find this and can use the same workaround.

Thank you so much! 🙏


High level API design

Goal of this issue is to define the High level API of the niche_vlaanderen module.
Low level API
The low level API is now more or less finished. Basically this low level api consists of 3 functions which calculate the possible vegetation based on input numpy arrays.
These three functions are each wrapped in a class which will load (and validate) the classification tables, which can be overwritten on model initialization.
The three classes are:

Vegetation
Acidity
NutrientLevel

High level API
For the high level API, the proposed method is:
A Niche object. This is normally initialized with its own codetables, but optionally different codetables can be given. The model is fixed when the object is created.
Initialization
import niche_vlaanderen
my_niche = niche_vlaanderen.Niche()

Internally, this object contains a (private)dictionary with reference to the different input layers
my_niche._input_layers
The keys of this dictionary are a limited number of allowed strings:

soil_code
mhw
mlw
seepage, ...

My first idea here was working with an enum type but I think this adds some complexity for the user with little benefit (eg you have to import the types to use them, enum is not supported natively on python 2.7).
Adding input data
After creating the module, the user can add different layers to this dictionary. A method is provided for this which does some basic sanity checking (valid type, valid file, ...).
myniche.set_input("msw", "gvg-zelfberekend.tif")
One of the choices here is how we handle the spatial constraints (projection, grid system, ...).
We could implicitly derive them from the first grid, define them explicitly or require the user to explicitly define them by importing a file.

Implicitely setting the context

>>> my_niche = niche_vlaanderen.Niche()
>>> myniche.set_input("msw", "gvg-zelfberekend.tif")
>>> myniche.set_input("soil_code", "../otherarea/soil.tif")
Error: layer extent does not overlap

Explicitly setting the context

>>> my_niche = niche_vlaanderen.Niche()
>>> my_niche_define_spatial_context(projection="EPSG:31370", bbox= ..., cell_size = 20)

Explicitely setting the context

>>> my_niche = niche_vlaanderen.Niche()
>>> myniche.set_input("msw", "gvg-zelfberekend.tif")
 Error: no spatial extent has been set
>>> myniche.set_input("msw", "gvg-zelfberekend.tif", set_spatial_extent=True)
 Spatial extent has been set: projection= ... , bbox ....

A second question is whether we should support different grid systems (overlapping). This is currently the case. Eg the Grobbendonk testcase has such grids.
Set constant input
A constant value can also be used as input:
>>> my_niche = niche_vlaanderen.Niche()
>>> my_niche.set_constant_input("nitrogen_atmospheric", 30)

Running the Model
The actual calculation can then be started with a calculate method.
myniche.calculate()
This will validate that all required input layers are set. Il will convert the self._input_layers to a self._input_arrays dictionary which contains arrays with the actual data that will be passed to the low level api.
It should output useful messages if errors occur.
>>> myniche.calculate()
Error, no value have been set for rainwater

If no errors occur, a list of vegetation types that were found should be reported. This gives the user some feedback (eg if impossible vegetations are found here the input should be checked) without having to open the grid files.
>>> myniche.calculate()
Vegetation types that can occur:
7: Caricion gracilis
...

A slightly more complicated output may actually present what percentage of the area can be covered by a certain vegetation type.
7: Caricion gracilis - 6%
Saving the model results
The result of this method will be saved in the class itself (eg self._vegetation). It can be saved to GIS files using the write() method:

myniche.write("../vegetation")

Files written have a fixed name (V1.tif, V2.tif, ...) and data type (geotiff). Optionally a different datatype (codelist from GDAL) can be specified eg ascii raster (useful for human readable test output).

myniche.write("vegetation", datatype="AAIGrid")

The intermediate "abiotic" grids will be saved in the same directory as well.

I like the proposed structure.
Just a small idea/enhancement: you could provide the methods to provide basic sanity checking (valid type, valid file, ...) as decorator functions on top of the set_input and set_constant_input functions. This makes the checks very explicit and in case other set_input derivative functions appear, it is not cluttering the insides of the functions/methods, but usage of the decorators

This has been implemented. Further documentation will happen in the dev documentation(#36)


Fix: set is_initialized=True only when there is detection

Closes https://github.com/aimakerspace/PeekingDuck/issues/661
Only set is_initialized=True when there is actual detection. This ensures that prev_tracked_bboxes will be non-empty when _match_and_track() is called.

LGTM.
To prevent this from happening again for other tracking models in the future, can we add a blank image both before and after this sequence of images for unit tests?

Created another fixture with frame 0 and 5 replaced with blank frames instead as we are able to explain why this sequence is necessary in the comments. I was able to reproduce the bug by testing on this fixture as well.

LGTM

LGTM


GPU

Hello! I have next prompt on generation (under Windows):

received 1 prompt(s) and will repeat them 1 times to create 1 images.
Running in CPU mode. it's gonna be slooooooow.

Is there a way to enable CUDA GPU?

It will automatically use cuda if it's available. I'd refer you to torch installation instructions: https://pytorch.org/ and that you make sure you have an appropriate graphics card and cuda drivers installed.

hey @brycedrennan,
first of all, fanstatic job!
I would recommand that you put this infomation in the readme.


MaterialDialogBuilder.input allowEmptyInput parameter does not work

Just check the sample application and you can see that I am able to press submit when the text field is empty and allowEmptyInput is set to false.
As far as I remember this started happening when the inputMaxLength function was added.

Looks like someone else broke this with a pull request from a week or two ago, luckily it's a simple fix

https://github.com/afollestad/material-dialogs/releases/tag/v<IP_ADDRESS>


Add nodata as optional argument to Raster

Quite often in my experience, the nodata value is either wrong or unset on a DEM that I get or create. Right now, if I'm not mistaken, the only way to fix this is:
nodata_value = -3.40282347e+38
r = Raster("path/to/file")
r.data.mask = r.data == nodata_value

Of course this works, but it would be much quicker if nodata= could be given to the Raster.__init__() function

No, we have the method set_ndv for that!

Ah, I didn't know that!
I still think it would be nice to have as an argument because it would reduce one line, but it's not as necessary as I thought, so I'll drop this.


Add SimpleRefuel from SpaceDock

This pull request was automatically generated by SpaceDock on behalf of MarkusA380, to add SimpleRefuel to CKAN.
Mod details:
name = /mod/947/SimpleRefuel
author = MarkusA380
abstract = A simple mod that lets you refuel vessels when landed at the KSC
license = GPLv3
Homepage = http://forum.kerbalspaceprogram.com/index.php?/topic/147536-113-simplerefuel-01/
description =
Please direct questions about this pull request to MarkusA380.

Folder structure is as follows: SimpleRefuel.zip/SimpleRefuel/GameData/...
This has already caused issues in a prior mod I uploaded to CKAN.


Can we remove the cardboard page?

@naomiblack It appears we have an abandoned page on https://angular.io/cardboard/ since we are in the process of migrating stuff. Do you think we could get rid of this page? The amount of effort to port this isn't a lot, but it is one more page to bundle and maintain. It also has broken styles in narrow displays.
cc @chalin @alexwolfe

I think we can get rid of this in the migration.


CREATE returns undefined

Had time to look into the 2 errors we get when we npm test
The function
alasql('CREATE TABLE one (id SERIAL, name STRING)');

and
alasql('INSERT INTO one (name) VALUES ("One"), ("Two"), ("Three")');

both gives undefined instead of expected 1 and 3
when console.log of response I get
 Test 350 SERIAL data type
    ✓ 1. CREATE DATABASE
undefined
    1) 2. CREATE TABLE
undefined
    2) 3. INSERT
    ✓ 4. SELECT
    ✓ 99. DROP DATABASE

I beleave the test is correct and there is something wrong with the implementation of responses from create and insert.

If you run this test independently:
    > mocha test350

everything passed OK, that is why I passed it to release. So, this is a problem of interference one test to another. But ok, anyway it is a bug.

I understand what is it. We set NOCOUNT parameter to off in earlier tests.
I will change test and addone of two lines either:
    alasql('SET NOCOUNT OFF');

or
    alasql.options.nocount = false;

Great. Just push it to development so I can get the fresh test files

Pushed/

Hmm. I can see you edited test 352 - but its in test 350 im getting the problem in
 it('2. CREATE TABLE',function(done){
    var res = alasql('CREATE TABLE one (id SERIAL, name STRING)');
    assert.deepEqual(res,1);
    done();
  });

  it('3. INSERT',function(done){
    var res = alasql('INSERT INTO one (name) VALUES ("One"), ("Two"), ("Three")');
    assert.deepEqual(res,3);
    done();
  });

Could you look into making sure res is not undefined?

I walked through all tests and put NOCOUNT OFF  in proper places (in the end part of each "nocount" test).Commit  af718b1

:+1:


cmake: need to specify m32/mx32/m64 for x86_64 toolchain

Since x86_64-zephyr-elf is a multi-lib toolchain, m32/mx32/m64
need to be specified for the compiler to return the correct
library path when queried (e.g. --print-libgcc-file-name).
This affects the compile check done by CMake. Without these
flags, the compiler returns incorrect toolchain path (e.g.
requiring 64-bit libraries but returning 32-bit library path).
This also affects compiler flag checks for "-lstdc++". Incorrect
library path results in error when checking for "-lstdc++", and
this flag will not be used for the build. This results in
undefined references when compiling C++ code.
This creates target_x86.cmake to add the necessary flags for
CMake to use. The target_x86_64.cmake is also created to
mirror the same change.
Also removing the -m32 flags for host-gcc since we are not
building x86 targets with the host-gcc compiler.
Signed-off-by: Daniel Leung<EMAIL_ADDRESS>

hm... I have not problem building for both qemu_x86_long and qemu_x86_64 but CI keeps failing on them.

Hm... still don't understand why CI fails. I tried 3 different machines, couple VMs and even the CI dockers (v0.9.1 and v0.9.2). All passed on them.

I feel like there's a new season of the -m32/-mx32/-m64 series showing up on github every couple months. While I really like the latest cast, I unfortunately don't have enough time to watch this brand new season. I bet if someone had the time to slowly and carefully watch all the previous episodes then maybe he or she could finally write the script for a proper grand finale.
Below is a recap of the one episode I remember; that's because I had then enough time to play a small role in it! Searching github should find other episodes easily.
https://github.com/zephyrproject-rtos/zephyr/pull/17516#issuecomment-511229983

I think the confusion is mainly because the -m32/-mx32/-m64 Data Type flags have "dual citizenship": on one hand they're toolchain specific, on the other hand they're -march-itecture specific. [...] In Zephyr these Data Type flags can live in either:

/Arch/** country with some toolchain logic if ever needed, or they can live in:
cmake/Compiler/** with some architecture conditionals

[...]
/Arch/ option 1. seems better to me because...

CI finally passed.

CI finally passed.

what was the issue?

The CI seems to had issue finding libstdc++ both under mx32 and m64, which never happen on my testing with multiple machines. Since we are no longer using x32, the mx32 issue is gone. The m64 one is gone after I added a path to the 64-bit libstdc++.


Wildcards needed to search for pod, namespace, container_name, and container_id

I have splunk-connect installed on my openshift cluster and logs showing up in Splunk. Events do have the fields pod, namespace, container_name, and container_id and value populating them. The issue is searching by any of these fields, searching namespace="openshift-node" will return no results, but namespace="*openshift-*node" with wildcards will return all the expected results. I'm not sure if this is something with Splunk itself or how splunk-connect is using jq to parse the filename in the fluentd config:
jq "def find_sourcetype(pod; container_name): container_name + \"/\" + pod | if startswith(\"dns-controller/dns-controller\") then \"kube:dns-controller\" elif startswith(\"sidecar/kube-dns\") then \"kube:kubedns-sidecar\" elif startswith(\"dnsmasq/kube-dns\") then \"kube:dnsmasq\" elif startswith(\"etcd-container/etcd-server\") then \"kube:etcd\" elif startswith(\"etcd-container/etcd-server-events\") then \"kube:etcd-events\" elif startswith(\"kube-apiserver/kube-apiserver\") then \"kube:kube-apiserver\" elif startswith(\"kube-controller-manager/kube-controller-manager\") then \"kube:kube-controller-manager\" elif startswith(\"autoscaler/kube-dns-autoscaler\") then \"kube:kube-dns-autoscaler\" elif startswith(\"kube-proxy/kube-proxy\") then \"kube:kube-proxy\" elif startswith(\"kube-scheduler/kube-scheduler\") then \"kube:kube-scheduler\" elif startswith(\"kubedns/kube-dns\") then \"kube:kubedns\" else empty end;  def extract_container_info:   (.source | ltrimstr(\"/var/log/containers/\") | split(\"_\")) as $parts   | ($parts[-1] | split(\"-\")) as $cparts   | .pod = $parts[0]   | .namespace = $parts[1]   | .container_name = ($cparts[:-1] | join(\"-\"))   | .container_id = ($cparts[-1] | rtrimstr(\".log\"))   | .;    .record | extract_container_info | .sourcetype = (find_sourcetype(.pod; .container_name) // \"kube:container:\\(.container_name)\")"

Hi @alfresh - Searching for metadata that comes through with logs via HEC fields often just needs a small tweak to work as expected.
could you try the search
namespace::"openshift-node"
This article can provide some more information - https://answers.splunk.com/answers/635676/why-do-i-need-to-search-metadata-in-a-fields-argum.html

@dtregonning That was the issue. Thanks for the info!


release 0.1.0

TODO:

[ ] publish on conda-forge
[ ] publish on pypi
[ ] update readme to conda install -c conda-forge conda-project

redundant against the milestone


Add per-PR build jobs

Use a service like netlify to build and deploy every branch or every PR.
Would be super great if there was a link/button in the PR that opened up the deployed app.
Would be super great (requirement, probably), that in order for the PR to be able to be merged, the build and deploy must succeed.

Woop this is done and working


fix: Typo in Higress Ingress Annotation 配置说明。

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Remove impl AsRef to match serenity@next

This fixes #247.

Closing as can be a part of the serenity-next PR, and the main part (AsRef<serenity::Context>) has already been fixed on next.


Make Alluxio helm chart configurable for hostNetwork or not

Alluxio Version:
2.2.0
Describe the bug
The current implementation on Helm chart only supports non-hostnetwork environment: https://github.com/Alluxio/alluxio/commit/4d6126a5d9e03128c01ca73f2a8cad12558e981c
I suggest to make it configurable? the user can decide whether they want hostNetwork or non-hostNetwork. In fact, the network performance is much worse when using non hostNetwork. I
To Reproduce
Steps to reproduce the behavior (as minimally and precisely as possible)
Expected behavior
A clear and concise description of what you expected to happen.
Urgency
Describe the impact and urgency of the bug.
Additional context
Add any other context about the problem here.

/ping @jiacheliu3

After https://github.com/Alluxio/alluxio/commit/4d6126a5d9e03128c01ca73f2a8cad12558e981c when ALLUXIO_WORKER_CONTAINTER_HOSTNAME is set on worker, the connections to worker will use this hostname even if the worker is using hostNetwork. I'll apply a small fix to remove ALLUXIO_WORKER_CONTAINTER_HOSTNAME when the workers are using hostNetwork.

@cheyang please take a look if #11290 meets your need. Thanks!

@jiacheliu3 Thank you!


Report Preview isn't working using Report.Execute method in BC16

Describe the bug
We have upgraded an existing AL code from BC15 to BC16 (both on prem) and noticed that the behaviour of Report.Execute method has changed. Previously it opened a report in preview mode for the user for further action. Now it automatically downloads a PDF without displaying the preview mode.
To Reproduce
Steps and to reproduce the behaviour:
For example, create a new action in Sales Order page that runs a report (via variable) using Execute method. And run the action to see the system behaviour.
AL Code to reproduce the issue
//Below is an example. Report and record variables should be replaced with different.
            action(JobPrintPreview)
            {
                ApplicationArea = Basic;
                Caption = 'Job Print Preview';
                trigger OnAction()
                var
                    JobCardRep: Report "My Report";
                    RecRef: RecordRef;
                    ServHeader: Record "Service Header";
                begin
                    ServHeader.Reset;
                    ServHeader.SetRange("Document Type", "Document Type");
                    ServHeader.SetRange("No.", "No.");
                    RecRef.GetTable(ServHeader);

                    JobCardRep.Execute('', RecRef);
                end;
            }

Expected behavior
After user clicks on the action button, the system should run the report and show the preview window with report layout and data.
Method description is found here: https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/methods-auto/report/reportinstance-execute-method
5. Versions:

AL Language: 5.0.254558
Business Central: Version: GB Business Central 16.0; (Platform 16.0.11233.12061 + Application 16.0.12076.0)

Hi! Please take a minute to read the guidelines for this repository https://github.com/microsoft/AL and our collection of frequently asked questions https://github.com/Microsoft/AL/wiki/frequently-Asked-Questions .
As this repository is only for issues related to the AL compiler in latest developer preview environment for Dynamics 365 Business Central. We suggest that you open a support case or file a bug in Collaborate, to ensure that all Business Central users benefit from your catch as soon as possible.
To open a support case, you can:

Open a support request to CSS through the PartnerSource portal
Contact your Service Account Manager (SAM) in your local subsidiary to understand what is included in your contract as of support incident and PAH (Partner Advisory Hours). Your SAM might also direct you "step by step" how to open a support request or how to get credentials, if this is the first time for you or your company

If you file the bug in Collaborate, remember to include steps to reproduce the issue, and the Business Central build number and country version you're using.

Was a case ever opened for this?  How can I see if one has?

@raydilsons would know.

Was a case ever o

Hello! I did not open a case for this, I’m afraid.

Dear All i am also facing the same issue.