Invalid hook call with vite

Hi,
I have a basic vanilla vite setup using Typescript and React
my App.tsx looks like this

import { Link, Route } from "wouter";

const App = () => (

    <Link href="/x">
      pag 2
    </Link>
    <Route path="/">page 1</Route>
    <Route path="/x">pag 2</Route>

);
export default App;

this is breaking with the following
react.development.js:209 Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.
printWarning @ react.development.js:209
error @ react.development.js:183
resolveDispatcher @ react.development.js:1592
useContext2 @ react.development.js:1602
useRouter @ index.js:35
(anonymous) @ index.js:109
renderWithHooks @ react-dom.development.js:16305
updateForwardRef @ react-dom.development.js:19226
beginWork @ react-dom.development.js:21636
beginWork$1 @ react-dom.development.js:27426
performUnitOfWork @ react-dom.development.js:26557
workLoopSync @ react-dom.development.js:26466
renderRootSync @ react-dom.development.js:26434
performConcurrentWorkOnRoot @ react-dom.development.js:25738
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
react.development.js:209 Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.
printWarning @ react.development.js:209
error @ react.development.js:183
resolveDispatcher @ react.development.js:1592
useContext2 @ react.development.js:1602
useRouter @ index.js:35
(anonymous) @ index.js:109
renderWithHooks @ react-dom.development.js:16305
updateForwardRef @ react-dom.development.js:19226
beginWork @ react-dom.development.js:21636
callCallback2 @ react-dom.development.js:4164
invokeGuardedCallbackDev @ react-dom.development.js:4213
invokeGuardedCallback @ react-dom.development.js:4277
beginWork$1 @ react-dom.development.js:27451
performUnitOfWork @ react-dom.development.js:26557
workLoopSync @ react-dom.development.js:26466
renderRootSync @ react-dom.development.js:26434
performConcurrentWorkOnRoot @ react-dom.development.js:25738
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
react.development.js:1618 Uncaught TypeError: Cannot read properties of null (reading 'useContext')
    at useContext2 (react.development.js:1618:21)
    at useRouter (index.js:35:32)
    at index.js:109:18
    at renderWithHooks (react-dom.development.js:16305:18)
    at updateForwardRef (react-dom.development.js:19226:20)
    at beginWork (react-dom.development.js:21636:16)
    at HTMLUnknownElement.callCallback2 (react-dom.development.js:4164:14)
    at Object.invokeGuardedCallbackDev (react-dom.development.js:4213:16)
    at invokeGuardedCallback (react-dom.development.js:4277:31)
    at beginWork$1 (react-dom.development.js:27451:7)
useContext2 @ react.development.js:1618
useRouter @ index.js:35
(anonymous) @ index.js:109
renderWithHooks @ react-dom.development.js:16305
updateForwardRef @ react-dom.development.js:19226
beginWork @ react-dom.development.js:21636
callCallback2 @ react-dom.development.js:4164
invokeGuardedCallbackDev @ react-dom.development.js:4213
invokeGuardedCallback @ react-dom.development.js:4277
beginWork$1 @ react-dom.development.js:27451
performUnitOfWork @ react-dom.development.js:26557
workLoopSync @ react-dom.development.js:26466
renderRootSync @ react-dom.development.js:26434
performConcurrentWorkOnRoot @ react-dom.development.js:25738
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
react.development.js:209 Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.
printWarning @ react.development.js:209
error @ react.development.js:183
resolveDispatcher @ react.development.js:1592
useContext2 @ react.development.js:1602
useRouter @ index.js:35
useRoute @ index.js:47
Route @ index.js:94
renderWithHooks @ react-dom.development.js:16305
mountIndeterminateComponent @ react-dom.development.js:20074
beginWork @ react-dom.development.js:21587
beginWork$1 @ react-dom.development.js:27426
performUnitOfWork @ react-dom.development.js:26557
workLoopSync @ react-dom.development.js:26466
renderRootSync @ react-dom.development.js:26434
performConcurrentWorkOnRoot @ react-dom.development.js:25738
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
react.development.js:209 Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.
printWarning @ react.development.js:209
error @ react.development.js:183
resolveDispatcher @ react.development.js:1592
useContext2 @ react.development.js:1602
useRouter @ index.js:35
useRoute @ index.js:47
Route @ index.js:94
renderWithHooks @ react-dom.development.js:16305
mountIndeterminateComponent @ react-dom.development.js:20074
beginWork @ react-dom.development.js:21587
callCallback2 @ react-dom.development.js:4164
invokeGuardedCallbackDev @ react-dom.development.js:4213
invokeGuardedCallback @ react-dom.development.js:4277
beginWork$1 @ react-dom.development.js:27451
performUnitOfWork @ react-dom.development.js:26557
workLoopSync @ react-dom.development.js:26466
renderRootSync @ react-dom.development.js:26434
performConcurrentWorkOnRoot @ react-dom.development.js:25738
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
react.development.js:1618 Uncaught TypeError: Cannot read properties of null (reading 'useContext')
    at useContext2 (react.development.js:1618:21)
    at useRouter (index.js:35:32)
    at useRoute (index.js:47:18)
    at Route (index.js:94:25)
    at renderWithHooks (react-dom.development.js:16305:18)
    at mountIndeterminateComponent (react-dom.development.js:20074:13)
    at beginWork (react-dom.development.js:21587:16)
    at HTMLUnknownElement.callCallback2 (react-dom.development.js:4164:14)
    at Object.invokeGuardedCallbackDev (react-dom.development.js:4213:16)
    at invokeGuardedCallback (react-dom.development.js:4277:31)
useContext2 @ react.development.js:1618
useRouter @ index.js:35
useRoute @ index.js:47
Route @ index.js:94
renderWithHooks @ react-dom.development.js:16305
mountIndeterminateComponent @ react-dom.development.js:20074
beginWork @ react-dom.development.js:21587
callCallback2 @ react-dom.development.js:4164
invokeGuardedCallbackDev @ react-dom.development.js:4213
invokeGuardedCallback @ react-dom.development.js:4277
beginWork$1 @ react-dom.development.js:27451
performUnitOfWork @ react-dom.development.js:26557
workLoopSync @ react-dom.development.js:26466
renderRootSync @ react-dom.development.js:26434
performConcurrentWorkOnRoot @ react-dom.development.js:25738
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
react.development.js:209 Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.
printWarning @ react.development.js:209
error @ react.development.js:183
resolveDispatcher @ react.development.js:1592
useContext2 @ react.development.js:1602
useRouter @ index.js:35
useRoute @ index.js:47
Route @ index.js:94
renderWithHooks @ react-dom.development.js:16305
mountIndeterminateComponent @ react-dom.development.js:20074
beginWork @ react-dom.development.js:21587
beginWork$1 @ react-dom.development.js:27426
performUnitOfWork @ react-dom.development.js:26557
workLoopSync @ react-dom.development.js:26466
renderRootSync @ react-dom.development.js:26434
performConcurrentWorkOnRoot @ react-dom.development.js:25738
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
react.development.js:209 Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.
printWarning @ react.development.js:209
error @ react.development.js:183
resolveDispatcher @ react.development.js:1592
useContext2 @ react.development.js:1602
useRouter @ index.js:35
useRoute @ index.js:47
Route @ index.js:94
renderWithHooks @ react-dom.development.js:16305
mountIndeterminateComponent @ react-dom.development.js:20074
beginWork @ react-dom.development.js:21587
callCallback2 @ react-dom.development.js:4164
invokeGuardedCallbackDev @ react-dom.development.js:4213
invokeGuardedCallback @ react-dom.development.js:4277
beginWork$1 @ react-dom.development.js:27451
performUnitOfWork @ react-dom.development.js:26557
workLoopSync @ react-dom.development.js:26466
renderRootSync @ react-dom.development.js:26434
performConcurrentWorkOnRoot @ react-dom.development.js:25738
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
react.development.js:1618 Uncaught TypeError: Cannot read properties of null (reading 'useContext')
    at useContext2 (react.development.js:1618:21)
    at useRouter (index.js:35:32)
    at useRoute (index.js:47:18)
    at Route (index.js:94:25)
    at renderWithHooks (react-dom.development.js:16305:18)
    at mountIndeterminateComponent (react-dom.development.js:20074:13)
    at beginWork (react-dom.development.js:21587:16)
    at HTMLUnknownElement.callCallback2 (react-dom.development.js:4164:14)
    at Object.invokeGuardedCallbackDev (react-dom.development.js:4213:16)
    at invokeGuardedCallback (react-dom.development.js:4277:31)
useContext2 @ react.development.js:1618
useRouter @ index.js:35
useRoute @ index.js:47
Route @ index.js:94
renderWithHooks @ react-dom.development.js:16305
mountIndeterminateComponent @ react-dom.development.js:20074
beginWork @ react-dom.development.js:21587
callCallback2 @ react-dom.development.js:4164
invokeGuardedCallbackDev @ react-dom.development.js:4213
invokeGuardedCallback @ react-dom.development.js:4277
beginWork$1 @ react-dom.development.js:27451
performUnitOfWork @ react-dom.development.js:26557
workLoopSync @ react-dom.development.js:26466
renderRootSync @ react-dom.development.js:26434
performConcurrentWorkOnRoot @ react-dom.development.js:25738
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
react.development.js:209 Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.
printWarning @ react.development.js:209
error @ react.development.js:183
resolveDispatcher @ react.development.js:1592
useContext2 @ react.development.js:1602
useRouter @ index.js:35
(anonymous) @ index.js:109
renderWithHooks @ react-dom.development.js:16305
updateForwardRef @ react-dom.development.js:19226
beginWork @ react-dom.development.js:21636
beginWork$1 @ react-dom.development.js:27426
performUnitOfWork @ react-dom.development.js:26557
workLoopSync @ react-dom.development.js:26466
renderRootSync @ react-dom.development.js:26434
recoverFromConcurrentError @ react-dom.development.js:25850
performConcurrentWorkOnRoot @ react-dom.development.js:25750
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
react.development.js:209 Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.
printWarning @ react.development.js:209
error @ react.development.js:183
resolveDispatcher @ react.development.js:1592
useContext2 @ react.development.js:1602
useRouter @ index.js:35
(anonymous) @ index.js:109
renderWithHooks @ react-dom.development.js:16305
updateForwardRef @ react-dom.development.js:19226
beginWork @ react-dom.development.js:21636
callCallback2 @ react-dom.development.js:4164
invokeGuardedCallbackDev @ react-dom.development.js:4213
invokeGuardedCallback @ react-dom.development.js:4277
beginWork$1 @ react-dom.development.js:27451
performUnitOfWork @ react-dom.development.js:26557
workLoopSync @ react-dom.development.js:26466
renderRootSync @ react-dom.development.js:26434
recoverFromConcurrentError @ react-dom.development.js:25850
performConcurrentWorkOnRoot @ react-dom.development.js:25750
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
react.development.js:1618 Uncaught TypeError: Cannot read properties of null (reading 'useContext')
    at useContext2 (react.development.js:1618:21)
    at useRouter (index.js:35:32)
    at index.js:109:18
    at renderWithHooks (react-dom.development.js:16305:18)
    at updateForwardRef (react-dom.development.js:19226:20)
    at beginWork (react-dom.development.js:21636:16)
    at HTMLUnknownElement.callCallback2 (react-dom.development.js:4164:14)
    at Object.invokeGuardedCallbackDev (react-dom.development.js:4213:16)
    at invokeGuardedCallback (react-dom.development.js:4277:31)
    at beginWork$1 (react-dom.development.js:27451:7)
useContext2 @ react.development.js:1618
useRouter @ index.js:35
(anonymous) @ index.js:109
renderWithHooks @ react-dom.development.js:16305
updateForwardRef @ react-dom.development.js:19226
beginWork @ react-dom.development.js:21636
callCallback2 @ react-dom.development.js:4164
invokeGuardedCallbackDev @ react-dom.development.js:4213
invokeGuardedCallback @ react-dom.development.js:4277
beginWork$1 @ react-dom.development.js:27451
performUnitOfWork @ react-dom.development.js:26557
workLoopSync @ react-dom.development.js:26466
renderRootSync @ react-dom.development.js:26434
recoverFromConcurrentError @ react-dom.development.js:25850
performConcurrentWorkOnRoot @ react-dom.development.js:25750
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
react.development.js:209 Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.
printWarning @ react.development.js:209
error @ react.development.js:183
resolveDispatcher @ react.development.js:1592
useContext2 @ react.development.js:1602
useRouter @ index.js:35
useRoute @ index.js:47
Route @ index.js:94
renderWithHooks @ react-dom.development.js:16305
mountIndeterminateComponent @ react-dom.development.js:20074
beginWork @ react-dom.development.js:21587
beginWork$1 @ react-dom.development.js:27426
performUnitOfWork @ react-dom.development.js:26557
workLoopSync @ react-dom.development.js:26466
renderRootSync @ react-dom.development.js:26434
recoverFromConcurrentError @ react-dom.development.js:25850
performConcurrentWorkOnRoot @ react-dom.development.js:25750
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
react.development.js:209 Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.
printWarning @ react.development.js:209
error @ react.development.js:183
resolveDispatcher @ react.development.js:1592
useContext2 @ react.development.js:1602
useRouter @ index.js:35
useRoute @ index.js:47
Route @ index.js:94
renderWithHooks @ react-dom.development.js:16305
mountIndeterminateComponent @ react-dom.development.js:20074
beginWork @ react-dom.development.js:21587
callCallback2 @ react-dom.development.js:4164
invokeGuardedCallbackDev @ react-dom.development.js:4213
invokeGuardedCallback @ react-dom.development.js:4277
beginWork$1 @ react-dom.development.js:27451
performUnitOfWork @ react-dom.development.js:26557
workLoopSync @ react-dom.development.js:26466
renderRootSync @ react-dom.development.js:26434
recoverFromConcurrentError @ react-dom.development.js:25850
performConcurrentWorkOnRoot @ react-dom.development.js:25750
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
react.development.js:1618 Uncaught TypeError: Cannot read properties of null (reading 'useContext')
    at useContext2 (react.development.js:1618:21)
    at useRouter (index.js:35:32)
    at useRoute (index.js:47:18)
    at Route (index.js:94:25)
    at renderWithHooks (react-dom.development.js:16305:18)
    at mountIndeterminateComponent (react-dom.development.js:20074:13)
    at beginWork (react-dom.development.js:21587:16)
    at HTMLUnknownElement.callCallback2 (react-dom.development.js:4164:14)
    at Object.invokeGuardedCallbackDev (react-dom.development.js:4213:16)
    at invokeGuardedCallback (react-dom.development.js:4277:31)
useContext2 @ react.development.js:1618
useRouter @ index.js:35
useRoute @ index.js:47
Route @ index.js:94
renderWithHooks @ react-dom.development.js:16305
mountIndeterminateComponent @ react-dom.development.js:20074
beginWork @ react-dom.development.js:21587
callCallback2 @ react-dom.development.js:4164
invokeGuardedCallbackDev @ react-dom.development.js:4213
invokeGuardedCallback @ react-dom.development.js:4277
beginWork$1 @ react-dom.development.js:27451
performUnitOfWork @ react-dom.development.js:26557
workLoopSync @ react-dom.development.js:26466
renderRootSync @ react-dom.development.js:26434
recoverFromConcurrentError @ react-dom.development.js:25850
performConcurrentWorkOnRoot @ react-dom.development.js:25750
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
react.development.js:209 Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.
printWarning @ react.development.js:209
error @ react.development.js:183
resolveDispatcher @ react.development.js:1592
useContext2 @ react.development.js:1602
useRouter @ index.js:35
useRoute @ index.js:47
Route @ index.js:94
renderWithHooks @ react-dom.development.js:16305
mountIndeterminateComponent @ react-dom.development.js:20074
beginWork @ react-dom.development.js:21587
beginWork$1 @ react-dom.development.js:27426
performUnitOfWork @ react-dom.development.js:26557
workLoopSync @ react-dom.development.js:26466
renderRootSync @ react-dom.development.js:26434
recoverFromConcurrentError @ react-dom.development.js:25850
performConcurrentWorkOnRoot @ react-dom.development.js:25750
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
react.development.js:209 Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.
printWarning @ react.development.js:209
error @ react.development.js:183
resolveDispatcher @ react.development.js:1592
useContext2 @ react.development.js:1602
useRouter @ index.js:35
useRoute @ index.js:47
Route @ index.js:94
renderWithHooks @ react-dom.development.js:16305
mountIndeterminateComponent @ react-dom.development.js:20074
beginWork @ react-dom.development.js:21587
callCallback2 @ react-dom.development.js:4164
invokeGuardedCallbackDev @ react-dom.development.js:4213
invokeGuardedCallback @ react-dom.development.js:4277
beginWork$1 @ react-dom.development.js:27451
performUnitOfWork @ react-dom.development.js:26557
workLoopSync @ react-dom.development.js:26466
renderRootSync @ react-dom.development.js:26434
recoverFromConcurrentError @ react-dom.development.js:25850
performConcurrentWorkOnRoot @ react-dom.development.js:25750
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
react.development.js:1618 Uncaught TypeError: Cannot read properties of null (reading 'useContext')
    at useContext2 (react.development.js:1618:21)
    at useRouter (index.js:35:32)
    at useRoute (index.js:47:18)
    at Route (index.js:94:25)
    at renderWithHooks (react-dom.development.js:16305:18)
    at mountIndeterminateComponent (react-dom.development.js:20074:13)
    at beginWork (react-dom.development.js:21587:16)
    at HTMLUnknownElement.callCallback2 (react-dom.development.js:4164:14)
    at Object.invokeGuardedCallbackDev (react-dom.development.js:4213:16)
    at invokeGuardedCallback (react-dom.development.js:4277:31)
useContext2 @ react.development.js:1618
useRouter @ index.js:35
useRoute @ index.js:47
Route @ index.js:94
renderWithHooks @ react-dom.development.js:16305
mountIndeterminateComponent @ react-dom.development.js:20074
beginWork @ react-dom.development.js:21587
callCallback2 @ react-dom.development.js:4164
invokeGuardedCallbackDev @ react-dom.development.js:4213
invokeGuardedCallback @ react-dom.development.js:4277
beginWork$1 @ react-dom.development.js:27451
performUnitOfWork @ react-dom.development.js:26557
workLoopSync @ react-dom.development.js:26466
renderRootSync @ react-dom.development.js:26434
recoverFromConcurrentError @ react-dom.development.js:25850
performConcurrentWorkOnRoot @ react-dom.development.js:25750
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
react-dom.development.js:18687 The above error occurred in the <ForwardRef> component:

    at http://<IP_ADDRESS>:5173/node_modules/.vite/deps/wouter.js?v=dcaf80f0:2181:18
    at div
    at App

Consider adding an error boundary to your tree to customize error handling behavior.
Visit https://reactjs.org/link/error-boundaries to learn more about error boundaries.
logCapturedError @ react-dom.development.js:18687
update.callback @ react-dom.development.js:18720
callCallback @ react-dom.development.js:13923
commitUpdateQueue @ react-dom.development.js:13944
commitLayoutEffectOnFiber @ react-dom.development.js:23391
commitLayoutMountEffects_complete @ react-dom.development.js:24688
commitLayoutEffects_begin @ react-dom.development.js:24674
commitLayoutEffects @ react-dom.development.js:24612
commitRootImpl @ react-dom.development.js:26823
commitRoot @ react-dom.development.js:26682
finishConcurrentRender @ react-dom.development.js:25892
performConcurrentWorkOnRoot @ react-dom.development.js:25809
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
2react-dom.development.js:18687 The above error occurred in the <Route> component:

    at Route (http://<IP_ADDRESS>:5173/node_modules/.vite/deps/wouter.js?v=dcaf80f0:2171:16)
    at div
    at App

Consider adding an error boundary to your tree to customize error handling behavior.
 Had same problem, wasn't able to figure why does it not render...

I'm not able to use wouter due to this issue. My node_modules is perfectly fine.


Token error

When debugging a BadToken error it would be nice to have information about which token is considered bad.  This adds that :)
Edit: I just noticed that the white space is off, so I'll fix that as well.

Thanks for the commit.  I hope RLTK has been useful for you.  Let me know if there are any other improvements that you'd like to see.

@chriswailes Thanks!  It has been useful, although I haven't had much experience with parsers/lexers prior so there's been a learning curve.  I may open some more PRs down the road as I get a better handle on how your code is structure :)

You might want to take a look at the development branch.  I've updated RTLK for Ruby 2.4, and I'm also making some changes to how the parser is structured.
Also, thanks for putting up with my preference for tabs.


Cannot Attach to Emulator

Does this occur consistently?
Repro steps:

Launch Azure Cosmos Emulator
Attempt to "Attach Emulator" via Azure Databases extension by selecting Core (SQL)
SQL Emulator appears under Attached Database Accounts
Expanding SQL Emulator results in Error

Action: AzureTreeDataProvider.getChildren
Error type: Error:
Error Message: Unable to reach emulator. Please ensure it is started and connected to the port specified by the 'cosmosDB.emulator.port' setting, then try again.
cosmosDB.emulator.port is set to 8081 which is the port on Azure Cosmos Emulator.
Interestingly, I am able to right-click on SQL Emulator and  choose "Create Database" and follow the prompts in Command palette to create a new database successfully. I just cannot view any local databases from within the Databases view in vscode.
Version: 0.16.0
OS: win32
OS Release: 10.0.19041
Product: Visual Studio Code
Product Version: 1.56.2
Language: en

Call Stack
Timeout._onTimeout extension.bundle.js:574:54833
listOnTimeout timers.js:554:17
processTimers timers.js:497:7

Verified that this doesn't reproduce with v<IP_ADDRESS> of the Azure Cosmos Emulator on Windows.


Missing .gitignore file

Each project should have a .gitignore file to ignore files that shouldn't be committed in Git. A good place to start is always this community managed Gitignore file.
Also, the project needs to be checked for unnecessary files that were already checked in. They should be deleted and commited as deleted to remove them – just adding them to the Gitignore file doesn't untrack them.

Fixed via 5e67b75492d67a8b809f23eb4c57b6372b3d0a44.


Bump offline uaa ops

As the uaa source file is completely out of sync I bumped the version to the current precompiled version. Maybe this should get also auto bumped in the  future.

Pushed a change to have CI do this instead: https://github.com/cloudfoundry/bosh-deployment/commit/a427d5153f36daa486130088d76b69a05870b6d7.


Derive the list of deployments that are currently running for a service

The revamped service screen has to answer the question: Which deployments are currently running for service xyz?
For example: As a user, I open the service screen and select the service carts. Then I can see that 3 deployments are actively running which are distributed across the stages of my project.

carts:0.11.1 with commit c123ab9 runs in: dev
carts:0.10.1 with commit 82341b runs in: staging
carts:0.9.5 with commit 98ab123 runs in: pre-production, production

Task:

Implement the logic to derive the list of currently deployed services
Implement a concept to show older deployments (not running once)
Assumption, a delivery (delivery-direct) sequence is responsible for deploying a service
(Interim solution to show the result/behavior) Display the list of deployments in the "service tile"

Definition of Done

[ ] The service tile is telling me which deployments are running in which stage.

At the moment gitCommit is not available. It could be derived in loaded sequences, but this is not always the case (only 20 sequences are loaded and they could have not a single delivery sequence). The commit could be fetched later, but this would result in stages x services   API-Calls.


Missing keycode 0

I'm using a Windows keyboard with Chrome on OS X, and the app doesn't recognise the Menu key (the right-click key on the right-hand side, next to Ctrl).

@carlsmith
Fork and pull-request.


Few of the MaterialCommunityIcons are not being shown on Android ['hand-right']

Environment

OS: macOS Catalina 10.15.1
target platform: React native == 0.59
react-native-vector-icons version: 6.6.0
Android emulator: 9+ [Pixel 2]

Description
I am using react native version 0.59 and using material icons for my app, but few of the material icons listed is the MaterialCommunityIcons.tff are not being displayed and there is an empty area as an Icon.
For Example- when i am using icons -> ['hand-right', 'hand-left', 'hand-saw'] nothing is being shown,
But when i use -> ['hand', 'thumbs-up'] it works
Below are the screenshots for reference:

{
  "type": "material",
  "name": "hand-right",
  "size": 36,
  "style": {marginBottom:10;
color:#3b5998;}
}

But when using ['hand', 'thumbs-up'] it works
Steps to Recreate

create a react-native project
add a material icon 'hand-right' to the home page screen.
run react-native android or yarn android on Android version 9+

Should be fixed with newer version


Remove hardcoded names in generated objects

When a node is added to the scene, it is automatically assigned the correct name depending on the node naming scheme settings. So if I understand correctly, calling set_name doesn't make any sense.
Closes #35690.

Thanks!


[DatePicker] Can't go before 2013 in year selection

Can't select a year before 2013 on date-picker.
Go to http://www.material-ui.com/#/components/date-picker and click on the year to change it.

Material-UI: 0.15.1
React: 15.1.0
Browser: Tested with chrome and safari

#4317


Add new releases to Gradle Plugin Portal

Currently the plugin is only published to Maven Central but not to the Gradle Plugin Portal. Intent is to again publish it there as well. The previously used method using bintray did not longer work and was removed. Instead the Plugin Publishing Plugin shall be used.

Done in https://github.com/stempler/bnd-platform/commit/3f47647f6475d8d3edf203d48736a09ec3de6186, version 3.0.0 is available on the Plugin Portal.


art contest bot commands and functionality

WIP
For now not much planned, ideas still need to be given for the implementation but for now allow command to have people post images in DM and bot reposts them in a secret channel with vote reactions and user mention this channel will be opened in the voting phase of the contest

[ ] Add command to see on what images you have voted on (via message link)
[ ] vote via reaction and save that vote in database also immediately remove reaction to have votes be anonymous

[x] command to enter the contest via dm
[x] command to add an entry for the contest via dm
[x] command to determine the winner
[x] command to disqualify a contestant
[x] command to remove an entry
[x] remove vote via reaction

[ ] a way to remove someone from being disqualified
[ ] fix bug with vote reaction not getting removed when disqualified


Added hardware partner SeeedStudio and integration guide for Grove Base Hat

 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.zbeacon seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Invalid argument when running pre/post link script

Hi,
micromamba-docker runs into this error, while micromamba without docker is able to install the package. I've seen the "Invalid argument" also occur with pip installs in micromamba-docker. I wasn't able to find more infomation with --log-level debug or strace -f.
Any hints?
Error:
libmamba response code: -1 error message: Invalid argument
critical libmamba failed to execute pre/post link script for pyopengl

Dockerfile:
FROM mambaorg/micromamba:1.5.0-focal
COPY --chown=$MAMBA_USER:$MAMBA_USER env.yml /tmp/env.yaml
RUN micromamba install -y -n base --file /tmp/env.yaml && \
    micromamba clean --all --yes

env.yml:
channels:
  - conda-forge
  - defaults
dependencies:
  - pyopengl=3.1.6=pyhd8ed1ab_1

Even simpler way to reproduce:
FROM mambaorg/micromamba:1.5.0
RUN micromamba install -y -n base -c conda-forge pyopengl=3.1.6=pyhd8ed1ab_1

I was able to work around this with:
docker build --ulimit nofile=262144:262144 ...

Feel free to close this when you think this is not related to micromamba-docker

There may be some hope for improving how libmamba (micromamba) reports errors when running out of file handles. But if the file handle is being requested in a pre/post link script, then there probably isn't much that can be done outside of the pre/post scripts.
I am going to close this as it is a dup: https://github.com/mamba-org/mamba/issues/2501


Error 404 for rxjs/operators.js on running unit tests

I'm submitting a ...  (check one with "x")
[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see use [gitter](https://gitter.im/mgechev/angular2-seed) or [stackoverflow](https://stackoverflow.com/questions/tagged/angular2)

Current behavior

Initially I was getting the error "'build.bundle.rxjs' errored after 562 ms". After the fix made in #2109 that error disappeared but now when I run the unit tests, I get below error:
   24 10 2017 13:15:34.764:WARN [web-server]: 404: /base/node_modules/rxjs/operators.js     Chrome 61.0.3163 (Windows 10 0.0.0) ERROR: 'Error: Fetch error: 404 Not Found         at http://localhost:9876/base/node_modules/systemjs/dist/system.src.js?3c2cb0bc284db65a3e67e988     cdb7175dc5362244:1475:13         at ZoneDelegate.invoke (http://localhost:9876/base/node_modules/zone.js/dist/zone.js?5946249a94     dbe0baef6f1ef0e76e9bb02decfe1a:392:26)         at Zone.run (http://localhost:9876/base/node_modules/zone.js/dist/zone.js?5946249a94dbe0baef6f1     ef0e76e9bb02decfe1a:142:43)         at http://localhost:9876/base/node_modules/zone.js/dist/zone.js?5946249a94dbe0baef6f1ef0e76e9bb     02decfe1a:873:57         at ZoneDelegate.invokeTask (http://localhost:9876/base/node_modules/zone.js/dist/zone.js?594624     9a94dbe0baef6f1ef0e76e9bb02decfe1a:425:31)         at Zone.runTask (http://localhost:9876/base/node_modules/zone.js/dist/zone.js?5946249a94dbe0bae     f6f1ef0e76e9bb02decfe1a:192:47)         at drainMicroTaskQueue (http://localhost:9876/base/node_modules/zone.js/dist/zone.js?5946249a94     dbe0baef6f1ef0e76e9bb02decfe1a:602:35)         at <anonymous>'
Expected behavior

Should not get 404 for RxJs and unit tests should run without any issue.
Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

Windows 10
VS Code

Angular Seed Version: d6abbf96184babb00c3f32482edbcd0ddcb6e243

Node: node --version = 6.9.5

I found that with "rxjs": "^5.5.0" in packages.json, it downloads version "5.5.2". I tried "rxjs": "5.4.3" and it started working again.

@ahmadqarshi fix for ^5.0.0 should be updating the SystemJS configuration.

@mgechev I tried that already but it didn't work for me. I also tried below pattern entry in karma.conf.js file under the files array but to no avail
{         pattern: 'node_modules/rxjs/operators/**/*.js',         included: false,         watched: false       }

While not ideal...the hacky fix that worked for me was to copy the rxjs/operators/index.js to rxjs/operators.js and do a find and replace on './ with './operators/. Fixes the build.prod issue as well. You could do something like: sed -e "s/'\./'.\/operators/" <node_modules/rxjs/operators/index.js >node_modules/rxjs/operators.js. Check out https://github.com/ReactiveX/rxjs/issues/2971 for a disussion on the issue


Question 5 (3 points): Finding All the Corners

CornersProblem Class 구현

The real power of A* will only be apparent with a more challenging search problem. Now, it’s time to formulate a new problem and design a heuristic for it.
In corner mazes, there are four dots, one in each corner. Our new search problem is to find the shortest path through the maze that touches all four corners (whether the maze actually has food there or not). Note that for some mazes like tinyCorners, the shortest path does not always go to the closest food first! Hint: the shortest path through tinyCorners takes 28 steps.
Note: Make sure to complete Question 2 before working on Question 5, because Question 5 builds upon your answer for Question 2.
Implement the CornersProblem search problem in searchAgents.py. You will need to choose a state representation that encodes all the information necessary to detect whether all four corners have been reached. Now, your search agent should solve:
python pacman.py -l tinyCorners -p SearchAgent -a fn=bfs,prob=CornersProblem
python pacman.py -l mediumCorners -p SearchAgent -a fn=bfs,prob=CornersProblem
To receive full credit, you need to define an abstract state representation that does not encode irrelevant information (like the position of ghosts, where extra food is, etc.). In particular, do not use a Pacman GameState as a search state. Your code will be very, very slow if you do (and also wrong).
Hint: The only parts of the game state you need to reference in your implementation are the starting Pacman position and the location of the four corners.
Our implementation of breadthFirstSearch expands just under 2000 search nodes on mediumCorners. However, heuristics (used with A* search) can reduce the amount of searching required.


ErrorCode.ReadData never returned

Hi
I see that calling a plc.Read(...) will set a lasterror of "ErrorCode.WriteData". Should not return ErrorCode.ReadData?
I have search for ErrorCode.ReadData reference in code, seem to be only declared but not used.
Suggest:  ReadBytesWithSingleRequest in PlcSyncronous.cs should set ErrorCode.ReadData, not WriteData

Agreed, same should be done in public async Task<List<DataItem>> ReadMultipleVarsAsync(List<DataItem> dataItems) and public void ReadMultipleVars(List<DataItem> dataItems).
BTW: Why is it marked as obsolete? In my understanding Sync and Async should be exist both unless it is used internally.

BTW: Why is it marked as obsolete? In my understanding Sync and Async should be exist both unless it is used internally.

Things that can be done async should be done async. If a user choses not to use async, he should make that decision at the top-most level where he can make the decision. As such it does make sense to obsolete the sync API (even though Microsoft will never do such a thing because of backwards compatibility). Note that it's not my decision though, it was changed in PR #111.

About the Obsolete, I didn't notice that. Can someone remove that please? I don't think we will ever remove the synchronous version. @mycroes @rapha-dev

@mesta1 Will do.

It was actually only there on ReadMultipleVars and in some comments, removed all mentions of obsolete in PR #129.

Fixed in #125  and #129, may gets obsolete in #137.


Create default message collector gateway application for Raspberry Pi

We should provide a default fat jar application that can be put to out devKit (#12) or similar device. That application should be sending messages collected from the sensors on the devices to, by default, Message Store Cloudlet (#26).
The application should be configurable via the command line properties:
java -Ddatacenter.mqtt=tcp://<IP_ADDRESS>:9876 -jar camel-iot-gateway-collector

With this kind of application users won't be forced to create custom applications for common sensors messages forward scenarios.

Closing this one, as we already have a base for the gateway. Created #71 to create a connector to the GPS data. We could create similar connectors to the other sensors.


[wip] dashboard builder v2

@mistercrunch @graceguo-supercat @hughhhh @john-bodley @michellethomas @elibrumbaugh
🔥 big PR warning
This is a WIP branch for the dashboard builder v2 that I wanted to start getting 👀s + 💬s  on. Below I have a demo and sections for:

see issue 4527 I created to track intended functionality
remaining todo items to get to v0

Plan going forward
Comments on the PR are welcome and we could consider opening PRs into this branch for the rest of the functionality.

overview of the react + redux architecture
overview of the new serializable data structure

DEMO
(gif colors are a little janky 🙄)

TODO

[x] [Chris] new grid + element resize functionality with re-resizable
[x] [Chris] drag and drop functionality with react-dnd react-beautiful-dnd
[x] [Chris] define new serializable data structure
[x] [Chris] Hook up synchronous redux (local app state)
[x] [Chris] Editable components (hover + popover menus)
[x] [Chris] rebase on master
[x] [Chris] remove gradient icon + theme overrides (future UI-kit PR)
[x] [Chris] clean up css organization + use less variables where possible
[x] [Chris] Add ability to attach tabs as the top-level dashboard container
[x] [Chris] undo/redo functionality
[x] [Chris] Add ability to drop row within a column
[x] [Chris] Handle case of dropping (adjustable-width) components into a full row
[x] [Chris] switch between static dashboard vs edit mode
[x] [Chris] remove all deprecated dashboard v1 css
[x] [Chris] major perf improvements with integrated data
[x] [Chris] lazy loading visualizations across tabs
[x] [Chris] Add sticky top-level tabs
[x] [Chris] lots of tests (grid/resize functionality, drag and drop, components)
[x] [Chris] fix logging
[x] [Chris] add back v1 fallback to support staged rollout

[x] [Grace] hook up to existing async redux + data
[x] [Grace] migration script for existing layouts
[x] [Grace] Animated nested sidebar
[x] [Grace] Add sticky side panel
[x] [Grace] updated chart header
[x] [Grace] Addition of new markdown component

[x] add back support for custom css (note: this is still expected to break since class names have changed)
[x] final aesthetics pass
[ ] (in progress) extensive testing in staging

React architecture
Dashboard components share common functionality (drag/drop, resize, hover menus, popover menus) but also require custom hooks and logic. We accommodate both requirements by encapsulating logic into compossible React components:
// Dynamic layout
<DragDroppable>
  <DropIndicator />
  <HoverMenu>
    <DragHandle />
    {/* menu items */}
  </HoverMenu>
  <DimensionProvider>
    <PopoverMenu>
      <Component>
         { repeat }
      </Component>
    </PopoverMenu>
  </DimensionProvider>
</DragDroppable>

// [WIP] (ideal) Static layout
<Component>
 { children }
</Component>

Data structure
The following data structure is used for the dashboard layout.
Features

supports arbitrary nesting
supports addition of new components in the future
is a flat data structure so is easily updatable (mirrors normalizr and other redux libs)

{
 // object keyed on ids
 [id]: {
   id,
   type,
   children: [id, ...],
   meta: {
     rowStyle,
     text,
     width,
     height,
     headerSize,
     ...
   },
 },
}

⚠ Noting that all Dashboard v1 changes will now need to be manually added back to this branch because we copied it into src/dashboard/deprecated/v1/ to support a v1 <> v2 switch

rebased and I think ready to mergeeeeee (🤞 build passes)
@graceguo-supercat @mistercrunch

Codecov Report

Merging #4528 into master will decrease coverage by 1.53%.
The diff coverage is 51.55%.

@@            Coverage Diff             @@
##           master    #4528      +/-   ##
==========================================
- Coverage   63.28%   61.75%   -1.54%
==========================================
  Files         259      368     +109
  Lines       19689    23848    +4159
  Branches     1968     2721     +753
==========================================
+ Hits        12461    14728    +2267
- Misses       7219     9109    +1890
- Partials        9       11       +2

Impacted Files
Coverage Δ

...ts/src/visualizations/deckgl/layers/screengrid.jsx
38.18% <ø> (ø)
:arrow_up:

...et/assets/src/dashboard/util/getDragDropManager.js
100% <ø> (ø)

superset/assets/src/theme.js
0% <ø> (ø)
:arrow_up:

.../assets/src/dashboard/util/shouldWrapChildInRow.js
100% <ø> (ø)

...t/assets/src/dashboard/util/newComponentFactory.js
100% <ø> (ø)

superset/assets/src/explore/index.jsx
0% <ø> (ø)
:arrow_up:

...ssets/src/visualizations/deckgl/layers/scatter.jsx
27.83% <ø> (ø)
:arrow_up:

...ts/src/dashboard/util/getDetailedComponentWidth.js
100% <ø> (ø)

.../explore/components/controls/DatasourceControl.jsx
65.71% <ø> (-0.96%)
:arrow_down:

...rd/deprecated/v1/components/DashboardContainer.jsx
0% <ø> (ø)

... and 284 more

Continue to review full report at Codecov.

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

This is exciting - when might we see this in master? and what will be the upgrade process?

Planning to merge tomorrow/Monday, this doc describes the upgrade process/configuration, and this describes the improvements themselves.


⚠ SceneTime has degraded performance

In cd22beb, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 3933 ms

Resolved: SceneTime performance has improved in 8b5ae2b.


the meaning of ss_accuracy、class_accuracy、best_accuracy

There are 3 values after ss_accuracy, 4 values after class_accuracy, and finally there is a best_accuracy. What are the meanings of these values

?

Thanks for your attention. We use CIFAR-100 dataset with N=100 supervised classes and 4 rotations as self-supervision augmentation with M=4 self-supervised classes.
(1) ss_accuracy denotes the accuracy over self-supervised augmented distribution with the label space of N*M. 3 values correspond the results of 3 auxiliary classifiers.
(2) class_accuracy denotes the original supervised class accuracy with the label space N. 4 values includes the first 3 values of 3 auxiliary classifiers and 1 value of the final classifier.
(3) In the script of train_teacher_cifar.py , we use best_accuracy to represent the best ss_accuracy among 3 values through the overall training process..  In the script of train_student_cifar.py , we use best_accuracy to represent the best class_accuracy of the final classifier through the overall training process. The meaning of best_accuracy depend on the return value in the final row of  def test() .

Thank u !!!


OAuth2AuthenticationProviderUtils is package private and should be public

Describe the bug
class OAuth2AuthenticationProviderUtils is package private (on purpose or public keyword missing?). Thus it cannot be used outside the library.
Is it possible to have it public, so that OAuth2AuthenticationProviderUtils.getAuthenticatedClientElseThrowInvalidClient() can be used outside the library ?
To Reproduce
Try to import org.springframework.security.oauth2.server.authorization.authentication.OAuth2AuthenticationProviderUtils.
Expected behavior
Should be accessible
Sample
A link to a GitHub repository with a minimal, reproducible sample.
Reports that include a sample will take priority over reports that do not.
At times, we may require a sample, so it is good to try and include a sample up front.

Closing as duplicate of gh-1290. See comment.


Telegram ID is now int64, and the bot seems not working on new int64 UID users.

Originally user ID was int32 up to<PHONE_NUMBER> and has been run out weeks or months ago.
From what I've heard from another bot operator, simply update/re-deploy the TDLib might do the trick. He was using an "air quote" or a strike line there, so I'm not sure if it's ture.

From what I've heard from another bot operator, simply update/re-deploy the TDLib might do the trick. He was using an "air quote" or a strike line there, so I'm not sure if it's ture.

Seems working now! Happy New Year.

From what I've heard from another bot operator, simply update/re-deploy the TDLib might do the trick. He was using an "air quote" or a strike line there, so I'm not sure if it's ture.

Seems working now! Happy New Year.

Thanks for reporting. I've updated the code in the repo as well now.

Thanks for reporting. I've updated the code in the repo as well now.


Policy updates to native messaging documents

AppService was always the only mechanism we planned to support due to strategic and security reasons, however, this was not 100% spelled out. This change updates the wording in our documentation to reflect this

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/extensions/guides/native-messaging.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


add_on to the apa overall process

modify the imputation and QC steps, separate this part from the original notebook
add the draft code for cluster-used apa analysis
document the apa calling pipeline

@seriousbamboo I only have one comment above. Please fix that and send in the PR again. thank you!

@gaow Corrections are made to the files you mentioned above. Please check. Have a good night, Professor!


Adaptive lighting stuck on

Describe The Bug:
When I set up the plugin, my phone prompted me to enable Adaptive Lighting. Because the colour during the daytime is not to my taste, and does not match the colour that some nearby Philips Hue bulbs select with Adaptive Lighting enabled, I want to disable adaptive lighting on my LIFX bulbs.
I am able temporarily to do this by selecting a fixed colour for the lights in the Home app on my phone, but after a short period the lights revert to an adaptive colour, and when I open their details in the Home app I can see the adaptive colour has been re-selected automatically.
To Reproduce:

Enable Adaptive Lighting on a LIFX Color 1000 bulb.
Set the light to a fixed colour (a warm white) in the Home app.
Leave the light on for an hour.
Open the bulb in the Home app. Notice colour is set to Adaptive Lighting again.

Expected behavior:
After choosing a fixed colour for the bulb, that colour should remain selected.
Logs:
With debug off, there is no apparent log output from the plugin.
With debug on, there is a ton of log output that I can't make sense of, so it's hard to know what to provide to help diagnose this.
Plugin Config:
{
    "bridge": {
        "name": "Home",
        "username": "17:01:17:01:17:01",
        "pin": "XXX-XX-XXX",
        "port": 51498,
        "advertiser": "avahi"
    },
    "platforms": [
        {
            "name": "Config",
            "port": 8581,
            "platform": "config"
        },
        {
            "name": "Lifx Plugin",
            "duration": 0,
            "brightnessDuration": 300,
            "colorDuration": 300,
            "default": "<IP_ADDRESS>",
            "broadcast": "<IP_ADDRESS>",
            "lightOfflineTolerance": 3,
            "messageHandlerTimeout": 45000,
            "resendPacketDelay": 150,
            "resendMaxTimes": 3,
            "updates": true,
            "debug": false,
            "autoDiscover": true,
            "platform": "LifxPlugin"
        }
    ],
    "accessories": [],
    "disabledPlugins": []
}

Screenshots:
n/a
Environment:

Plugin Version: v0.2.3
Homebridge Version: v1.5.0
Node.js Version: v16.17.1
NPM Version: 8.15.0
Operating System: Linux raspberrypi 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l

Hi @sentience,
since adaptive lighting is not controlled from the plugin, but only from the HomeApp, my question. Do you have a scene where adaptive lighting is referenced? I can understand that this bothers you, however, it works for me at home without any problems.

Thanks for the reply! Yes, that appears to have been the issue. I had a "Bedtime" scene that I would activate when going to bed each night. Although this scene turned all of the referenced lights off, it would do so by setting them to 0% brightness with adaptive lighting. Then, when the lights were switched on manually the next day, they would retain that adaptive lighting setting!
I've removed the adaptive lighting from all of my scenes, and now the lights seem to be retaining their assigned colour.


lnrpc+peer: custom peer messages

Lightning nodes have a connection to each of their peers for exchanging messages. In regular operation, these messages coordinate processes such as channel opening and payment forwarding.
The lightning spec however also defines a custom range (>= 32768) for experimental and application-specific peer messages.
Custom peer messages open up a whole range of interesting new possibilities. They allow the lightning protocol with its transport mechanisms (including tor) and public key authentication to be leveraged for application-level communication. Note that peers exchange these messages directly. There is no routing/path finding involved.
Some examples:

Retrieve node website url or other static information
Retrieve channel acceptance policy (for example max channel size)
Retrieve channel balances
Retrieve message of the day
Deliver human-readable messages to the node operator
Request liquidity in a specific direction as a preparation for a larger volume of payments that is anticipated
Place a web shop order with the lightning invoice in the return message
Retrieve web shop price list (assuming the node has something for sale)

Application-level communication was already possible using custom tlv records, but considerable restrictions apply. The most obvious being an absolute maximum message size of ~1300 bytes (depending on the route). Also there is no easy way for the receiving node to send a message back. This would involve finding a separate (possibly non-existent) return route. The upside of using custom tlv records is that the data is onion routed just as the carrying payment is, protecting the sender's identity.
For peers that already know each other (for example because they maintain a channel) or don't mind knowing each other, custom tlv records don't make too much sense but do make communication cumbersome and unreliable.
This PR adds to lnd the capability to send and receive custom peer messages via new SendCustomMessage and SubscribeCustomMessages rpc methods. For easy testing, lncli commands are provided.
To send a message:
lncli sendcustom --peer 03e3927c8e408c92be06a3dd0031600ff599abd00588e0e4bb9db217c6f16f0138 --type 42000 --data ff00ff11
The listen for incoming messages:
lncli subscribecustom
Looking for concept ACK.
Todo:

[x] tests
[x] remove lncli test commands (tbd)

Concept ACK

Unit test added

I think this PR is complete and has a concept-ack. Is it worth the 0.14 tag?

I'm here to ACK and let everyone know that we need this, to enable Offers, a set of features we would like to have access to for wallets ASAP.

. Also there is no easy way for the receiving node to send a message back

What about just sending a reply pubkey (or hop hint) to use? Message extension RPCs like this are cool, but if you want to do end to end interactions (outside of connecting to a peer you knows offers these features to send stuff back and forward), you'd need to assume every node in the critical path understands the messages.
AFAICT, all the sample use cases you've enumerated assume that you're making direct connections as other wise you'd need to use the existing onion routing protocol which has the size constraints mentioned.

What about just sending a reply pubkey (or hop hint) to use?

I call this 'not easy', because you aren't sure if there is a return path and the other complexities/edge cases that exist.

Message extension RPCs like this are cool, but if you want to do end to end interactions (outside of connecting to a peer you knows offers these features to send stuff back and forward), you'd need to assume every node in the critical path understands the messages.

AFAICT, all the sample use cases you've enumerated assume that you're making direct connections as other wise you'd need to use the existing onion routing protocol which has the size constraints mentioned.

Yes, my intention with these extensions is to just do direct communication. I guess you could use it to set up some kind of forwarding service as well, but haven't given that any thought.

@joostjager to get a baseline for gobencher, please first trigger a commit from your main/master branch then push again to a branch.

Rebased

Re-rebased. Waiting for final review.

Linter was just collateral damage of a broken test. All fixed now again.

Yeah we're aware of the flake, def not introduced by this PR.


Preparing ./lmdbs/PDBscreen

hi, how can I prepare the ./lmdbs/PDBscreen?

yes! you can

hi, how can I prepare the ./lmdbs/PDBscreen?

You can refer to our data processing script file(dataset/dataset.py)


add _changes?feed=stream sugar for continuous

allow feed=stream as sugar for continuous which is hard to
type.
PRs for the change:
https://github.com/apache/couchdb/pull/307
https://github.com/apache/couchdb-couch/pull/40
https://github.com/apache/couchdb-chttpd/pull/28
closes COUCHDB-2237

Test here is missed. This will cause dependency on #35 PR. Let's try to get it merged first.

+1 in general.
Btw, in light of COUCHDB-2562 how do you feel is "stream" feed type is good one or there could be something better?

yes, i think stream is good. it is a stream of newline separated json objects

cool (:

do you think i am ready to merge?
https://github.com/apache/couchdb/pull/307 shuffles old code a bit around that takes care of safari browsers, but maybe removing browser compatibility is a separate task

I left a comment about error message - may be there is a way to improve it. Cleaning up JavaScript test suite is indeed one big separate issue. In the end all is good for me (:

@robertkowalski ping (:

this got merged as d95005d4399047c52b5655cae6eb558258b8e6a5


Sharp damages image integrity

Are you using the latest version? Is the version currently in use as reported by npm ls sharp the same as the latest version as reported by npm view sharp dist-tags.latest?
Yes
What are the steps to reproduce?
Open an image with fs.readFile and then open the same image with sharp('image.jpeg') or const buff = fs.readFile(file); sharp(buff) and compare buffers or their base64's or md5 hashes of base64's.
What is the expected behaviour?
Image buffer should be the same as if you opened the file via fs.readFile
Are you able to provide a minimal, standalone code sample, without other dependencies, that demonstrates this problem?
Yes, it's 1 question above.
Are you able to provide a sample image that helps explain the problem?
Please, refer to https://repl.it/@JamesJGoodwin/FirsthandClumsyBlocks to be able to download an image and run a minimal, standalone code sample
What is the output of running npx envinfo --binaries --system?
System:
    OS: Windows 10 10.0.19041
    CPU: (4) x64 Intel(R) Core(TM) i3-4160 CPU @ 3.60GHz
    Memory: 1.83 GB / 7.94 GB
  Binaries:
    Node: 14.6.0 - C:\Program Files\nodejs\node.EXE
    npm: 6.14.6 - C:\Program Files\nodejs\npm.CMD

console.log(Source opened with sharp: ${md5(await sharp('image.jpg').toString('base64'))})
console.log(Source opened with sharp second time: ${md5(await sharp('image.jpg').toString('base64'))})
console.log(Source buffer provided to sharp: ${md5(await sharp(imageBuff).toString('base64'))})

Source opened with sharp: 1441a7909c087dbbe7ce59881b9df8b9
Source opened with sharp second time: 1441a7909c087dbbe7ce59881b9df8b9
Source buffer provided to sharp: 1441a7909c087dbbe7ce59881b9df8b9

toString() is not part of the sharp API but is instead part of the global JavaScript Object API - see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/toString
The sample code is testing the ability to generate an md5 hash of the string "[object Object]".
$ node -p "require('md5')('[object Object]')"
1441a7909c087dbbe7ce59881b9df8b9

toString() is not part of the sharp API but is instead part of the global JavaScript Object API

Yeah, I know that. But the problem is not in base64 encoding, but in Buffer that is returned by sharp. I took an image and saved it with fs.writeFile and with sharp(sourceImageBuffer).toFile('sharp.jpg') and opened them in hexdump and that's where I discovered that they have different content.

I'm not sure if this is a problem to have hex differences, but obviously this is not an expected behaviour when you don't make any changes to the image, yet still it's buffer value is modified. Even if you provide sharp with corrent buffer and ask it to give the buffer back (sharp(sourceImageBuffer).toBuffer()) - the buffer will be different.

JPEG is a lossy format so the decode/encode round-trip means the compressed output is unlikely to "equal" the compressed input.

Oh, that's why. Ok, thanks for the explanation!


Gnupg2 install breaks Ubuntu LTS

The addition of gnupg2 in commit 7a53c5341954b67e906ad36a002806de4a933129 breaks Ubuntu 18.04, the current Ubuntu LTS
Ubuntu 18.04 does not have this package
Pinning to the 2.5.2 as a workaround seems to work fine, but is obviously not ideal

Also impacts the docker role https://github.com/geerlingguy/ansible-role-docker/issues/195

@lod - I added it to fix some issues with Debian 10, and in my own local tests in both a Docker container with a minimal install as well as in a VirtualBox VM with the Ubuntu server install, I haven't had any issues. Can you provide more information about what task, in particular, is failing, along with any associated error messages?

I am getting the same error while running in AWS Ubuntu instance (Ubuntu Server 18.04 LTS (HVM))
Install Gitlab Task is failing
.. Its a really long error message:
fatal: [<IP_ADDRESS>]: FAILED! => {"cache_update_time":<PHONE_NUMBER>, "cache_updated": false, "changed": false, "msg": "'/usr/bin/apt-get -y -o "Dpkg::Options::=--force-confdef" -o "Dpkg::Options::=--force-confold"      install 'gitlab-ce'' failed: E: Sub-process /usr/bin/dpkg returned an error code (1)\n", "rc": 100, "stderr": "E: Sub-process /usr/bin/dpkg returned an error code (1)\n", "stderr_lines": ["E: Sub-process /usr/bin/dpkg returned an error code (1)"], "stdout": "Reading package lists...\nBuilding dependency tree...\
GitLab requires UTF-8 encoding to function properly. Please check your locale settings.", "", "Running handlers complete", "\u001b[0mChef Client failed. 377 resources updated in 02 minutes 14 seconds\u001b[0m", "", "Warnings:", "Environment variable LC_ALL specifies a non-UTF-8 locale. GitLab requires UTF-8 encoding to function properly. Please check your locale settings.", "", "dpkg: error processing package gitlab-ce (--configure):", " installed gitlab-ce package post-installation script subprocess returned error exit status 1"]}

gnupg2 fails to install on Ubuntu 20.04 LTS as well, with this error:
TASK [gitlab : Install GitLab dependencies (Debian).] **************************************************************************************************************
fatal: [<IP_ADDRESS>]: FAILED! => {"changed": false, "msg": "No package matching 'gnupg2' is available"}

OS info:

$ cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.1 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.1 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

I'm using the latest master (https://github.com/geerlingguy/ansible-role-gitlab/commit/cb5981dcd65c799a1679ea9ef4ff9361273fed5b).

The workaround of running `update_cache=yes` as noted in https://github.com/geerlingguy/ansible-role-docker/issues/195 works for me fyi.

@snobear - It seems if that workaround works, the best option may be to add a task in your playbook that updates the apt caches. I don't like doing that in my roles because if I had 8 roles with each one updating caches as it went, playbooks would be very slow.

@geerlingguy yeah makes sense. Running a cache update before this gitlab playbook is run does the trick. I put this as a pre task in my playbook, e.g.
  pre_tasks:
    - name: Update apt-get repo and cache
      apt: update_cache=yes force_apt_get=yes cache_valid_time=3600

Going to close this for now; please use that option if you run into this issue.


ARROW-11268: [Rust][DataFusion] MemTable::load output partition support

I think the feature to be able to repartition an in memory table is useful, as the repartitioning only needs to be applied once, and repartition itself is cheap (at the same node). Doing this when loading data is very useful for in-memory analytics as we can benefit from mutliple cores after loading the data.
The speed up from repartitioning is very big (mainly on aggregates), on my (8-core machine): ~5-7x on query 1 and 12 versus a single partition, and a smaller (~30%) difference for query 5 when using 16 partition. q1/q12 also have very high cpu utilization.
@jorgecarleitao maybe this is of interest to you, as you mentioned you are looking into multi-threading. I think this would be a "high level" way to get more parallelism, also in the logical plan. I think in some optimizer rules and/or dynamically we can do repartitions, similar to what's described here https://issues.apache.org/jira/browse/ARROW-9464
Benchmarks after repartitioning (16 partitions):
PR (16 partitions)
Query 12 iteration 0 took 33.9 ms
Query 12 iteration 1 took 34.3 ms
Query 12 iteration 2 took 36.9 ms
Query 12 iteration 3 took 33.6 ms
Query 12 iteration 4 took 35.1 ms
Query 12 iteration 5 took 38.8 ms
Query 12 iteration 6 took 35.8 ms
Query 12 iteration 7 took 34.4 ms
Query 12 iteration 8 took 34.2 ms
Query 12 iteration 9 took 35.3 ms
Query 12 avg time: 35.24 ms

Master (1 partition):
Query 12 iteration 0 took 245.6 ms
Query 12 iteration 1 took 246.4 ms
Query 12 iteration 2 took 246.1 ms
Query 12 iteration 3 took 247.9 ms
Query 12 iteration 4 took 246.5 ms
Query 12 iteration 5 took 248.2 ms
Query 12 iteration 6 took 247.8 ms
Query 12 iteration 7 took 246.4 ms
Query 12 iteration 8 took 246.6 ms
Query 12 iteration 9 took 246.5 ms
Query 12 avg time: 246.79 ms

PR (16 partitions):
Query 1 iteration 0 took 138.6 ms
Query 1 iteration 1 took 142.2 ms
Query 1 iteration 2 took 125.8 ms
Query 1 iteration 3 took 102.4 ms
Query 1 iteration 4 took 105.9 ms
Query 1 iteration 5 took 107.0 ms
Query 1 iteration 6 took 109.3 ms
Query 1 iteration 7 took 109.9 ms
Query 1 iteration 8 took 108.8 ms
Query 1 iteration 9 took 112.0 ms
Query 1 avg time: 116.19 ms

Master (1 partition):
Query 1 iteration 0 took 640.6 ms
Query 1 iteration 1 took 640.0 ms
Query 1 iteration 2 took 632.9 ms
Query 1 iteration 3 took 634.6 ms
Query 1 iteration 4 took 630.7 ms
Query 1 iteration 5 took 630.7 ms
Query 1 iteration 6 took 631.9 ms
Query 1 iteration 7 took 635.5 ms
Query 1 iteration 8 took 639.0 ms
Query 1 iteration 9 took 638.3 ms
Query 1 avg time: 635.43 ms

PR (16 partitions)
Query 5 iteration 0 took 465.8 ms
Query 5 iteration 1 took 428.0 ms
Query 5 iteration 2 took 435.0 ms
Query 5 iteration 3 took 407.3 ms
Query 5 iteration 4 took 435.7 ms
Query 5 iteration 5 took 437.4 ms
Query 5 iteration 6 took 411.2 ms
Query 5 iteration 7 took 432.0 ms
Query 5 iteration 8 took 436.8 ms
Query 5 iteration 9 took 435.6 ms
Query 5 avg time: 432.47 ms

Master (1 partition)
Query 5 iteration 0 took 660.6 ms
Query 5 iteration 1 took 634.4 ms
Query 5 iteration 2 took 626.4 ms
Query 5 iteration 3 took 628.0 ms
Query 5 iteration 4 took 635.3 ms
Query 5 iteration 5 took 631.1 ms
Query 5 iteration 6 took 631.3 ms
Query 5 iteration 7 took 639.4 ms
Query 5 iteration 8 took 634.3 ms
Query 5 iteration 9 took 639.0 ms
Query 5 avg time: 635.97 ms

Codecov Report

Merging #9214 (8ba5828) into master (1393188) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #9214      +/-   ##
==========================================
- Coverage   81.61%   81.59%   -0.02%
==========================================
  Files         215      215
  Lines       51867    51877      +10
==========================================
  Hits        42329    42329
- Misses       9538     9548      +10

Impacted Files
Coverage Δ

rust/datafusion/src/datasource/memory.rs
80.98% <0.00%> (-5.30%)
:arrow_down:

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 eaa7b7a...afd6528. Read the comment docs.

Codecov Report

Merging #9214 (8ba5828) into master (1393188) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #9214      +/-   ##
==========================================
- Coverage   81.61%   81.59%   -0.02%
==========================================
  Files         215      215
  Lines       51867    51877      +10
==========================================
  Hits        42329    42329
- Misses       9538     9548      +10

Impacted Files
Coverage Δ

rust/datafusion/src/datasource/memory.rs
80.98% <0.00%> (-5.30%)
:arrow_down:

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 eaa7b7a...afd6528. Read the comment docs.

This would also help us in the db-benchmark https://github.com/h2oai/db-benchmark/pull/182

This would also help us in the db-benchmark https://github.com/h2oai/db-benchmark/pull/182


Views are not created as part of the migrations

this is a showstopper on a blank installation. please fix asap

Fixed


Disable logged out tests on main.

Current dependencies on/for this PR:

main

PR #284   👈

This stack of pull requests is managed by Graphite.


Metal: example-01-helloworld corrupted render when MSAA is enabled

Describe the bug
With MSAA on, the Hello World example renders with a bright pink background on my M2 Mac, and the imgui window disappears. Strangely enough, if I capture a frame with the Metal graphics debugger, it shows as normal in there. No errors are reported either.
To Reproduce
Steps to reproduce the behavior:

Run Hello World example
Press F8 to turn on MSAA

Expected behavior
The example should display as normal
Screenshots

Additional context
MacBook Pro
Apple M2 Max
OS: 13.5 (22G74)
Chipset Model:	Apple M2 Max
Type:	GPU
Bus:	Built-In
Total Number of Cores:	30
Vendor:	Apple (0x106b)
Metal Support:	Metal 3

Hm, this is suspicious. That's a non-MSAA frame on the left, and MSAA (pink frame) on the right.
I notice the dependency between submit and blitRender is a dashed line in the MSAA frame, which means synchronization only (no data transfer). So the frame isn't being transferred between submit and blitRender passes? I hope I have that right.

It looks like bgfx is storing to "Color 0 Resolve" in the submit pass, but trying to load from "Color 0" in the blitRender pass.

Can confirm it's reproducible on a Mac mini with M1 and macOS 14.5.


Code annotations danny ramos

DO NOT MERGE

Hey @muydanny I don't think that we want to merge this into Master. These code annotation branches are just going to be abandoned (I'm pretty sure). You may want to cancel your PR…


Dataset: "Preprocess the CK+ dataset, and store all images directly into this folder." - reg

Kindly elaborate pre-processing required

@donydchen Hi, I just want to confirm it. Does the paper have four pages ? I downloaded it from arxiv.


Title bar screen cheese

have a window open
open another empty window
in that window use Ctrl+R and pick a file (!) not a folder
🧀 title is off screen

This seems to be a Electron 9 regression. Steps:

custom title enabled
"window.title": "${activeEditorShort}"
"workbench.startupEditor": "none"
open new window
title should be entirely empty
bring up quick open to open ~/.zshrc

I was able to narrow it down to these lines, when uncommented it does not reproduce:
https://github.com/microsoft/vscode/blob/e557e8bcc3ca6b4569eee3f6b746f00b4572db56/src/vs/workbench/electron-sandbox/parts/titlebar/titlebarPart.ts#L136-L138

Setting will-change: transform to .monaco-workbench.web .part.titlebar > .window-title fixes it, but only after a brief moment.
I speculate that maybe we apply these CSS rules at a time when the layout has not finished yet, a bit too early.

Did a bisect, the regression in vscode happened in this range https://github.com/microsoft/vscode/compare/858d3259fa8e149294cd6ab2963362f61d691855...605b006936565862595663cf25722052fcddbcaf , @bpasero or @sbatten  can you check if there are any titlebar related changes in here.
there is notably a electron version bump from 9.0.5 to 9.1.0 https://github.com/electron/electron/compare/v9.0.5...v9.1.0 , only relevant frameless window change https://github.com/electron/electron/pull/24285 but that should only affect modal windows.

In my testing this was not macos specific, I could repro on Windows. Also, I don't have any changes in that commit range but I can dig further for a solution tomorrow.

6358de4119aab7080f4b30820233d55f0f1d8c65 is the first bad commit
commit 6358de4119aab7080f4b30820233d55f0f1d8c65
Author: deepak1556<EMAIL_ADDRESS>Date:   Thu Jul 9 10:57:34 2020 -0700

    enable LayoutNG

 src/main.js | 3 ---
 1 file changed, 3 deletions(-)

can confirm, launching with --disable-features=LayoutNG fixes the issue.
LayoutNG is big refactor in chromium, can't say what component changed without a minimal repro. Will check with @sbatten about this.

@bpasero Says this it not urgent, moving to September.


Optifine conflicts

For some reason your RPGDifficulty and Environmentz mods don't not work with optifine. I've gone through all my mods in the folder individually and it is definitely these it doesn't like. Is there any idea why?

Mh I have no idea and optifine is closed source, so compatibility is not easy.
I recommend to use Iris mod instead of optifine with all performance mods you can get.

If still persist in latest version, reopen with latest log.


fix!: synth.py clean for multiple versions

Notice that src/v1beta1/index.ts and `src/v1/index.ts' is still in the exclude list

Folks, what's up with this one?

@JustinBeckwith This is a pending breaking change - @summer-ji-eng do you know what is the API team position here?

Honestly it's fine.

duplicated PR with #214


Communication: Show who viewed a message in group chats

Is your feature request related to a problem?
In the ITP course I have a private group of students that attend my tutorial.
When I send a message I have no clue if the students read it or if I should tag them.
This functionality is similar to e.g. Whatsapp group messages.
Describe the solution you'd like
For this purpose it would be great to have the option to see who viewed my message. Then I would be able to tag those students that did not read my message.
Describe alternatives you've considered
Add small double check-marks in a group message to signal that everyone read the message.
Additional context
No response

Due to data privacy reasons, we cannot implement this feature. In Slack, you also cannot see who has seen a message. You can e.g. ask them to reply with 👍 to confirm that they have read the message


Create 1980-Find-Unique-Binary-String.py

File(s) Modified: 1980-Find-Unique-Binary-String.
Language(s) Used: python
Submission URL: _https://leetcode.com/submissions/detail/813437624/_

Thanks for contributing!


SceneView v1.0.7 Destroy issue

Hi!
I'm using the sceneview in a multiple fragment app, when I switch from a fragment containing sceneview to another one without sceneview, the app will crash. I found the problem is because the sceneview is not correctly destroy.
After debugging I found the problems are from these line of codes:

If I use skybox, the destroying skybox will give:
java.lang.IllegalStateException: Calling method on destroyed Skybox
If I don't use skybox, the destroy nodemanager will give:
java.lang.NullPointerException
Seems your order of destroy is not correct. And because the official sample is just one single fragment so your sample doesn't go through the destroy process completely.
I commented the destroy code for the skybox and nodemanager and now the thing works on my app. But this is not a good solution because there are some resources not released.
Please help us solve the issue!

Thanks for the great report. Could you just precise where it's happening?

This crash happens in the SceneView destroy because
skyboxes.toList().forEach { runCatching { destroySkybox(it) } }
Is called cleaning all sky boxes but then there is a call to
skybox?.let { engine.destroySkybox(it) }

Thanks @james-wemoms
Can you please make a PR removing the skybox.destroy() ?
Only the created ones from the SceneView should be destroyed.

When removing the skybox.destroy() the code still crashes with a ConcurrentModificationException further along.
I am trying to find a solution but to no avail yet.

any solution for that?

When removing the skybox.destroy() the code still crashes with a ConcurrentModificationException further along. I am trying to find a solution but to no avail yet.

I'm not sure if it's the same issue I had, but for me using a concurrent hash map to represent the node manager fixed the issue of concurrent modification

this problem related to navigation in compose too, i start a new activity for loading 3d model but when navigate back it still crash


Fetch Secrets alongside resources if required

 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.

Hi @speatzle
I looked at your changes here. I have noticed, that you added a condition, where you check, if users set secret columns, and then you load this values over new function in the api.
In your condition, you're using lowercase of column names. In the help description of switch -c all column names are in camel case. I think users will be guided by the help and will use camel case too.

hi, thanks for the tip, this was just a rough proof of concept and i forgot to strings.lower case the input. but i will need to redo this PR based on your filter PR's Changes anyway.


Update Index constructor JSDoc

fix JSDoc for the constructor of Index class
P.S. I was creating flow type def for lunr.js and if you are interested in integrating it with lunr.js itself (not just def) let me know.

I've just pushed this change in release 2.2.0, thanks for the PR!


Add README.md to package

Add the README.md file to the resulting build(s) otherwise the npmjs page is empty, with no description.

Resolved through #22


Fix Unable to delete PDB resource for workflow error

Summary
Unexpected error.
Diagnostics
evel=error msg="Unable to delete PDB resource for workflow." err="poddisruptionbudgets.policy \"canary-8rpjz\" not found" namespace=argo workflow=canary-8rpjz

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

The first error dupes #3217.

Available in v2.10.0-rc7.

Available for testing in v2.10.0-rc1.


Update Sublime Command Palette File

I haven't updated the command palette file in awhile so there are some commands left out now.

Handled in version 1.7.1


Save error handling relies on ActiveRecord::RecordInvalid

I know I am the crazy developer who doesn't use ActiveRecord.
The JSONAPI::Resource._save method looks for ActiveRecord exceptions as seen in the code block below. Unfortunately, this throws even worse exceptions about not finding ActiveRecord.
    def _save
      @model.save!
      @save_needed = false
    rescue ActiveRecord::RecordInvalid, ActiveRecord::RecordNotSaved => e
      raise JSONAPI::Exceptions::ValidationErrors.new(e.record.errors.messages)
    end

@realityendshere I can't say I'm surprised. I haven't done any more testing than what's in the tests regarding use without ActiveRecord. It would be great if we had a sample app that we could test against that didn't use AR. I don't know if that's something you want to tackle.

@lgebhardt
Like Peeps without AR?
I could take a look.
I'm may be mostly away from tech for the next few days. (Opening the issue was partly a reminder to myself to look into this more.)
Thanks.

@realityendshere Peeps without AR is what I had in mind.

Hello! Got busy converting some apps to Ember v1.11...
Here's a first pass at Peeps without AR:
https://github.com/realityendshere/peeps/tree/mongoid
It uses MongoDB and the Mongoid/Moped gems. If it "just works," I'd be pleasantly surprised. Please let me know if I can be of further assistance.
I hope this helps.
Thanks!

Thanks for adding the Peeps without AR.
I've added a branch https://github.com/cerebris/jsonapi-resources/tree/remove_ar that moves the AR stuff into the active_record_operations_processor. I'm not quite happy with the _save method on resources. I'm not yet testing the case where it doesn't save, but it passes all the validations.
I hope once that's done it will be ready for a PR, but I'd appreciate any feedback.

@lgebhardt can I help in any way on the https://github.com/cerebris/jsonapi-resources/tree/remove_ar branch, Fridays we work on open source only so we want to use JR with out active record so would be happy to contribute.

@pixelhandler Thanks! If you could try out the branch against your code that would be great. I think I've got all the active record exceptions removed from the base classes, but maybe not. So a quick look through would be appreciated.
As I mentioned above I'd like to rework the _save method, which I hope to get to soon. But if you want to look at that I've got no problem turning that over. It needs to account for callbacks canceling the save as well as validation errors (which should probably be checked after it fails, not before since I think it's now running validations twice).

@realityendshere I tried out your 'mongoid' fork/branch of the peeps app with the 'remove_ar' branch of JR that @lgebhardt mentioned. I had trouble running the gem locally. After be rake build and changing the Gemfile in the peeps app to the local path the rails app won't start (I was able to install the local gem build from the remove_ar branch). After that the initializer borks out as it doesn't find require 'jsonapi/resource_controller' I figured I man not need that initializer with the work in remove_ar branch so commented out. But then the jsonapi_resources method in config/routes.rb doesn't work.
I'm using ruby 2.2.2 (with rbenv).
@realityendshere have you tried running the JR gem locally?

@lgebhardt I get the same error on the master branch of the peeps app
/Users/bheaton/code/pixelhandler/peeps/config/routes.rb:2:in `block in <top (required)>': undefined method `jsonapi_resources' for #<ActionDispatch::Routing::Mapper:0x007fbf7440aa20> (NoMethodError)

I setup the JR gem to run locally in my Gemfile using gem 'jsonapi-resources', '0.3.2', path: '/Users/myusername/code/jsonapi-resources/pkg' in ~/code/jsonapi-resources I build the game with bundle exec rake build

Sorry. I was cleaning up what I thought were superfluous require statements. I suspect that's what's going on. I'll look at it soon.

If I use the gem from the remove_ar branch in the Peeps/Moingoid project it starts up just fine.
Gemfile:
gem 'jsonapi-resources', :github => 'cerebris/jsonapi-resources', branch: 'remove_ar'

and then bundle

@lgebhardt I'll give that a try thanks!

@realityendshere I rebased your mongoid branch on the upstream master and added a commit to use the remove_ar branch of the gem I'm getting some errors adding a phone number to a contact. I used the curl test examples from the readme. See https://github.com/realityendshere/peeps/compare/mongoid...pixelhandler:mongoid

@pixelhandler That's almost certainly due to the change in JSON-API's linkage format. The Peeps version @realityendshere based the Peeps/Moingoid branch on hadn't been updated at the time. See https://github.com/cerebris/peeps/issues/2 for the new format.

Is the remove_ar branch no longer available? I can't see it in the branches dropdown on Github.
I'm trying to get jsonapi-resources working with Mongoid and am having issues with Validations not firing, and records still being created even though fields marked with presence:true have no value present
Resource creation works fine using the @realityendshere approach to setting the Operations Processor to just be the JSONAPI::OperationsProcessor implementation.

@wzowee the remove_ar branch was merged to master today - see https://github.com/cerebris/jsonapi-resources/pull/192


Add download to disk option

Support for:

downloading a partial entry/one file

command takes - empiar entry number, single path/wildcard/regexp (#30 would be useful to help figure out which files)
optional argument: cache location, default to something in pwd; optional arguments to empiarreader python functions

'caching' for the python downloader

should this use caching within Intake? (lifetime of this, storage location?)

Solved in #33


Microsoft.VisualStudio.Shell.14.0 is not anymore needed as dependecy for vs19

Hello.
this package: Microsoft.VisualStudio.Shell.14.0 is not anymore needed to install via the nuget explorer.
as the latest vs.sdk which is shiped directly with visual studio 2019 has a dependency with
Microsoft.VisualStudio.Shell.15.0.
and this causes a nuget mismatch.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e759cd22-3920-94e9-5d7a-e1766e2f79db
Version Independent ID: b4796726-14a3-342e-448f-10fb0ba2deb1
Content: Walkthrough: Displaying Statement Completion - Visual Studio
Content Source: docs/extensibility/walkthrough-displaying-statement-completion.md
Product: visual-studio-windows
Technology: vs-ide-sdk
GitHub Login: @madskristensen
Microsoft Alias: madsk

@madskristensen -- please review the above-mentioned PR 5932.


Nova Dependency Container Broke Readonly field

I'd tried using Nova Dependency for the readOnly field, on my case, I want to show the field where the file isn't associated with the database columns so just need them only for external information. But Nova Dependency still executed them and tryin' to store or update to the database.
Current Code

I have a solution but I felt it needs a lot of costs, so I should workin' two times for making an external field that isn't associated with the database.

I think it's should be good if we only make it under Nova Dependency Container no need making again at another place.

Could you try this? Because if you won't pass a function on the second parameter of a field it will indeed try to post it in the database, this is not an issue of Dependency container. Hopefully this helps!
            Text::make('Return URL', static function ($model){
                return route('payment.notify', $this->slug);
            })
            ->readonly()
            ->hideFromIndex(),


Network growth model

Watts-Strogatz generates a good example network but it doesn't say anything about in which order or with which timing the links in this network came to be. We need to find a model that describes the addition and deletion of links in a network.

For now I'll just start with an unconnected graph and then let one link, picked at random, get created every 10 sim rounds.