Nextjs useForm gives a type error

Describe the bug
When i use useForm i get an error saying use_isomorphic_layout_effect_cjs is not a function. and it's due to Nextjs server side rendering.
Right now I'm getting over it using Nextjs dynamic import and disabling ssr but it's not a good approach.
when i want to use useForm hook i get the bellow error:
TypeError: use_isomorphic_layout_effect_cjs is not a function
    at useForm (/home/challen-quiz/dist/apps/challenquiz/.next/server/chunks/9063.js:828:3)
    at QuestionForm (/home/challen-quiz/dist/apps/challenquiz/.next/server/app/admin/add-question/page.js:442:44)
    at nP (/home/challen-quiz/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:45:40134)
    at nP (/home/challen-quiz/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:45:53256)
    at n$ (/home/challen-quiz/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:45:56848)
    at nj (/home/challen-quiz/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:45:60443)
    at nR (/home/challen-quiz/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:45:59154)
    at n$ (/home/challen-quiz/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:45:57094)
    at nj (/home/challen-quiz/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:45:60443)
    at nP (/home/challen-quiz/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:45:50666)

Your minimal, reproducible example
https://stackblitz.com/edit/stackblitz-starters-bbkdbd?file=components%2Fform.tsx
Steps to reproduce

create a new nextjs app project
create a client component
import useForm
use the client compoent
check the logs

Expected behavior
i expected that the useForm would work in a client component
How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform

OS Linux fedora
Browzer: Edge
Node version: 20
Nextjs: 13.5.3
@tanstack/react-form": "^0.3.6

Tanstack Form adapter
react-form
TanStack Form version
0.3.6
TypeScript version
5.2.2
Additional context
I just googled something and i found this: https://stackoverflow.com/questions/76609948/error-typeerror-0-useisomorphiclayouteffect-useisomorphiclayouteffect-is-n

This is a known issue caused by our bundler having issues.
Note to self: figure out why TSUp isn't bundling deps properly.

While certainly the error message is not ideal, does this actually cause any breaking issues? The hook seems to work as intended otherwise. 🤔

While certainly the error message is not ideal, does this actually cause any breaking issues? The hook seems to work as intended otherwise. 🤔

Can't run build command

Fwiw, It seems I can still build my project without error.
But i still get this error when running dev:
 ⨯ node_modules/.pnpm/@tanstack+react-form@0.3.6_@types+react@18.2.25_react-dom@18.2.0_react<EMAIL_ADDRESS>(29:2) @ useForm
 ⨯ TypeError: use_isomorphic_layout_effect__WEBPACK_IMPORTED_MODULE_1__ is not a function
    at SettingsForm (settings/_components/SettingsForm.tsx:64:80)

While certainly the error message is not ideal, does this actually cause any breaking issues? The hook seems to work as intended otherwise. 🤔

Cant build the project for both dev and prod environment. (Nextjs Pages Router)

react-form 0.3.6
Nextjs 13.4.8
Node 18
Typescript 4.9.5

Here are some logs for ya:
Prod
Error occurred prerendering page "/en/us/login". Read more: https://nextjs.org/docs/messages/prerender-error
TypeError: useIsomorphicLayoutEffect is not a function
    at useForm (file:///<REDACTED>/node_modules/.pnpm/@tanstack+react-form@0.3.6_@types+react@18.2.22_react-dom@18.2.0_react@18.2.0/node_modules/@tanstack/react-form/build/modern/useForm.js:29:3)
    at Login (/<REDACTED>/.next/server/pages/[channel]/login.js:139:79)
    at Wc (/<REDACTED>/node_modules/.pnpm/react-dom@18.2.0_react@18.2.0/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:68:44)
    at Zc (/<REDACTED>/node_modules/.pnpm/react-dom@18.2.0_react@18.2.0/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:253)
    at Z (/<REDACTED>/node_modules/.pnpm/react-dom@18.2.0_react@18.2.0/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at $c (/<REDACTED>/node_modules/.pnpm/react-dom@18.2.0_react@18.2.0/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:78:98)
    at Zc (/<REDACTED>/node_modules/.pnpm/react-dom@18.2.0_react@18.2.0/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:71:145)
    at Z (/<REDACTED>/node_modules/.pnpm/react-dom@18.2.0_react@18.2.0/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at Zc (/<REDACTED>/node_modules/.pnpm/react-dom@18.2.0_react@18.2.0/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:481)
    at Z (/<REDACTED>/node_modules/.pnpm/react-dom@18.2.0_react@18.2.0/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)

Dev:
- error Error [TypeError]: useIsomorphicLayoutEffect is not a function
    at useForm (file:///<REDACTED>/node_modules/.pnpm/@tanstack+react-form@0.3.6_@types+react@18.2.22_react-dom@18.2.0_react@18.2.0/node_modules/@tanstack/react-form/build/modern/useForm.js:29:3)
    at Login (webpack-internal:///./components/login.tsx:21:79)
    at renderWithHooks (/<REDACTED>/node_modules/.pnpm/react-dom@18.2.0_react@18.2.0/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5658:16)
    at renderIndeterminateComponent (/<REDACTED>/node_modules/.pnpm/react-dom@18.2.0_react@18.2.0/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5731:15)
    at renderElement (/<REDACTED>/node_modules/.pnpm/react-dom@18.2.0_react@18.2.0/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5946:7)
...
omitted a million more lines
...
    at renderNodeDestructiveImpl (/<REDACTED>/node_modules/.pnpm/react-dom@18.2.0_react@18.2.0/node_modules/react-dom/cjs/react-dom-server.browser.development.js:6104:11)
    at renderNodeDestructive (/<REDACTED>/node_modules/.pnpm/react-dom@18.2.0_react@18.2.0/node_modules/react-dom/cjs/react-dom-server.browser.development.js:6076:14)
    at renderIndeterminateComponent (/<REDACTED>/node_modules/.pnpm/react-dom@18.2.0_react@18.2.0/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5785:7)
    at renderElement (/<REDACTED>/node_modules/.pnpm/react-dom@18.2.0_react@18.2.0/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5946:7) {
  digest: undefined
}

I've reproduced this locally and it might be an issue inside the use-isomorphic-layout-effect package:

If I add console.log(useIsomorphicLayoutEffect) inside useForm and run it in a nextjs app I get:

{ default: [Function (anonymous)] } in the back end
and useLayoutEffect(create, deps) { ... } in the front end

So there is an extra default property in the back end.

Looking inside the Next.js build folder, I see that use_isomorphic_layout_effect is imported from node_modules/use-isomorphic-layout-effect/dist/use-isomorphic-layout-effect.cjs.js on the server and from node_modules/use-isomorphic-layout-effect/dist/use-isomorphic-layout-effect.browser.esm.js on the client. So Next.js imports the CJS version for SSR and the ESM version in the front end.

So for some reason, NextJS gets the CJS version on the server instead of the ESM one, and it can't resolve the default export properly. I don't know if it's an issue with NextJS or the package itself but I've noticed that if I add the exports sections to use-isomorphic-layout-effect's package.json, like below:
"exports": {
    "require": {
      "default": "./dist/use-isomorphic-layout-effect.cjs.js"
    },
    "import": {
      "default": "./dist/use-isomorphic-layout-effect.esm.js"
    }
  }

the issue disappears.
That said, we probably don't need to use this package. Looking at the code here, all it does is:
export default typeof document !== 'undefined' ? useLayoutEffect : useEffect;

I've tried replacing the package with that code inside the react-form package and it solved the issue. I'll open a PR.

@juliendelort this is good investigation. I will know however that I use this package simply because of React Native support.
But admittedly that's changed since RN now supports import maps

Ah yeah true, I forgot about react-native. I wonder if typeof document !== 'undefined' would work on RN and default back to useEffect.

I've reproduced this locally and it might be an issue inside the use-isomorphic-layout-effect package:

If I add console.log(useIsomorphicLayoutEffect) inside useForm and run it in a nextjs app I get:

{ default: [Function (anonymous)] } in the back end
and useLayoutEffect(create, deps) { ... } in the front end

So there is an extra default property in the back end.

Looking inside the Next.js build folder, I see that use_isomorphic_layout_effect is imported from node_modules/use-isomorphic-layout-effect/dist/use-isomorphic-layout-effect.cjs.js on the server and from node_modules/use-isomorphic-layout-effect/dist/use-isomorphic-layout-effect.browser.esm.js on the client. So Next.js imports the CJS version for SSR and the ESM version in the front end.

So for some reason, NextJS gets the CJS version on the server instead of the ESM one, and it can't resolve the default export properly. I don't know if it's an issue with NextJS or the package itself but I've noticed that if I add the exports sections to use-isomorphic-layout-effect's package.json, like below:
"exports": {
    "require": {
      "default": "./dist/use-isomorphic-layout-effect.cjs.js"
    },
    "import": {
      "default": "./dist/use-isomorphic-layout-effect.esm.js"
    }
  }

the issue disappears.
That said, we probably don't need to use this package. Looking at the code here, all it does is:
export default typeof document !== 'undefined' ? useLayoutEffect : useEffect;

I've tried replacing the package with that code inside the react-form package and it solved the issue. I'll open a PR.

i have the exact same thoughts about it, as you mentioned it, all does is only a one line of code

This fix made it into our 0.6.1 release with the help of @juliendelort. Please let me know if you run into any further issues with Next.js support
Sorry for the headache y'all - I really don't know how I got it in my head that React Native wouldn't support this, seeing as I already knew it did from my time building HouseForm.


Write a Haskell program to convert seconds to weeks

Description
Write a Haskell program to convert seconds to weeks
1 week = 7 days = 168 hours = 10080 minutes = 604800 seconds
Input  : 3024000
Output : 5

How to contribute

Save the solution in program/convert_seconds_to_weeks.hs file
Add convert_seconds_to_weeks.hs file in convert-seconds-to-weeks folder

!assign


37 create simple deployment

@KonradUdoHannes I really like your idea to add the scripts to the Makefile. I created https://github.com/CorrelAid/engage-2/issues/39 to handle this. Do you want to create a first draft?


Fix tests

This is the last step to make grumphp green.
I removed php-vcr and added a very simple filesystem cache. The content of the cache is version controlled because some date (last comment details, scores) can change in every second. To be able to run these tests against MAL every day/week/month we have to use less strict assertions. This change is related to #371.

AppVeyor still fails. Unfortunately, I'm not familiar with that.

AppVeyor config is out of date, it's checking for older php versions.

AppVeyor config is out of date, it's checking for older php versions.
Also do we want to test things on windows? I think I can write a github actions equivalent.

We can drop AppVeyor, it was mainly added for testing on windows but we dropped windows support quite a while back.

The HTTP cache is also being pushed to the repo as well. Would it be possible to push them to the fixtures repo instead?
https://github.com/jikan-me/jikan-fixtures
It would require changing cache read/write to vendor/jikan-me/jikan-fixtures/fixtures
We can link them with composer run-script link-fixtures:
https://github.com/jikan-me/jikan/blob/de68f87c64b11910fc70aed26e3a92f22f1af9b9/composer.json#L44

@irfan-dahir Could you apply the necessary changes? I'm not sure what I have to do. You can control the path in JikanTest\TestCase.

Created PR (needs to be merged before it shows up here) which moves http cache to jikan-fixtures.
If any new tests are being added, it's recommended to link the fixtures so any changes would be made as commits to jikan-fixtures.
You can link the fixtures by running the composer script link-fixtures.

HTTP Cache has been moved to jikan-fixtures.
If any new tests are being added, it's recommended to link the fixtures so any changes would be made as commits to jikan-fixtures.
You can link the fixtures by running the composer script composer link-fixtures. Invited you both for write access on the jikan-fixtures repo as well.


Feature/coq of rust

That sounds like a good plan. 😊
Based on what I found on the web, you can use the add_global_def function from the MetaCoq.Template.All module to add a new definition to the global environment. You can also use the unquote function from the UniMath.Foundations.UnivalenceAxiom module to convert a metacoq term into a unimath type.
For example, you can write something like this:
Require Import MetaCoq.Template.All.
Require Import UniMath.Foundations.UnivalenceAxiom.

(* Define a list of bytes *)
Definition bytes := [x00; x01; x02; x03].

(* Reify the list of bytes into a metacoq term *)
MetaCoq Run (reify bytes as bytes_term).

(* Add a new definition to the global environment using the reified term *)
MetaCoq Run (add_global_def "bytes_def" bytes_term).

(* Convert the metacoq term into a unimath type using the unquote function *)
Definition bytes_type : UU := unquote bytes_term.

I hope this helps you with your project. Good luck! 🍀
: [GitHub - MetaCoq/metacoq: Metaprogramming in Coq]
: [MetaCoq Tutorial (POPL 2024 - TutorialFest) - POPL 2024]
: [UniMath/UnivalenceAxiom.v at master · UniMath/UniMath · GitHub]
: [UniMath - a library of mathematics formalized in the univalent style]


Add created at to events

Fixes #20

Coverage increased (+0.002%) to 99.714% when pulling f8071980eeb742370876962bd7a03155cfa5b24c on add-created_at-to-events into 5bb157c15e508813ac5e575cd256c848c750f7f0 on master.

Maybe we should add a new migration with the add_column instead of changing the original one

Coverage increased (+0.002%) to 99.718% when pulling 4018cfcad1f44a1eb97bbdb17b08e6a79b437fd5 on add-created_at-to-events into<PHONE_NUMBER>9d2d0844e3e19d532d34710ead57fa on master.

Coverage decreased (-39.5%) to 60.234% when pulling 9e0d1a4cf9472c6ac73b2561463a183405a7e3e3 on add-created_at-to-events into<PHONE_NUMBER>9d2d0844e3e19d532d34710ead57fa on master.

Coverage decreased (-39.5%) to 60.234% when pulling 730290ff61c7f1e490fd290b15f86e94bf4d11b3 on add-created_at-to-events into<PHONE_NUMBER>9d2d0844e3e19d532d34710ead57fa on master.

Coverage decreased (-0.8%) to 98.898% when pulling 587d0281c50b5cb77f58f2fb75c46809b885ab46 on add-created_at-to-events into<PHONE_NUMBER>9d2d0844e3e19d532d34710ead57fa on master.

@tulios Fixed your code review comments. I also made sure that copy-migrations is now runnable from host app while still being able to run from specs.

Coverage increased (+0.008%) to 99.725% when pulling 0a2b4336f9ce276102594acb2f58ac0802847188 on add-created_at-to-events into<PHONE_NUMBER>9d2d0844e3e19d532d34710ead57fa on master.

Coverage increased (+0.008%) to 99.728% when pulling dce8c8bdc386c52958f69ce53be22985d4ccdb00 on add-created_at-to-events into 1d0534e88cdb219e411afad9e0161460b18ca7f4 on master.

Coverage decreased (-0.3%) to 99.459% when pulling 87b2a3bba5c392c43214a0c9533a778f735f028f on add-created_at-to-events into 1d0534e88cdb219e411afad9e0161460b18ca7f4 on master.

Coverage decreased (-0.3%) to 99.459% when pulling 3956948e9bd776e099ade2f5319ce55fab00e33e on add-created_at-to-events into 1d0534e88cdb219e411afad9e0161460b18ca7f4 on master.

Coverage decreased (-0.3%) to 99.462% when pulling f28a24fa5f0d753a5451cd77bc847bf2248e3e57 on add-created_at-to-events into 1d0534e88cdb219e411afad9e0161460b18ca7f4 on master.

Coverage decreased (-0.5%) to 99.194% when pulling f28a24fa5f0d753a5451cd77bc847bf2248e3e57 on add-created_at-to-events into 1d0534e88cdb219e411afad9e0161460b18ca7f4 on master.

Coverage decreased (-0.3%) to 99.462% when pulling 9b563ce9b14ad13bca4476d60d2eaa0c466eb94c on add-created_at-to-events into 1d0534e88cdb219e411afad9e0161460b18ca7f4 on master.

Coverage decreased (-0.3%) to 99.462% when pulling aa19ce54794ca228f44f46ad6c2276fb59b357a4 on add-created_at-to-events into 1d0534e88cdb219e411afad9e0161460b18ca7f4 on master.

Coverage decreased (-0.3%) to 99.462% when pulling 5e0d76707e9b95295e53e6f03741df6c31962ef3 on add-created_at-to-events into 1d0534e88cdb219e411afad9e0161460b18ca7f4 on master.

Coverage decreased (-0.3%) to 99.462% when pulling 5e0d76707e9b95295e53e6f03741df6c31962ef3 on add-created_at-to-events into 1d0534e88cdb219e411afad9e0161460b18ca7f4 on master.


[cxsparse] fix feature cxsparse

Otherwise the installation of the feature failed because suitesparse is not properly found and used (Fails because it can not find the headers)

ceres[core,cxsparse]:x64-windows could be installed successfully with this PR.


[Bug-Fix] Remove model as arg for _replace_initializer()

Remove extra argument in call to _replace_initializer()

good catch 🤦


Rename QEK Feature Map

https://github.com/sQUlearn/squlearn/blob/develop/src/squlearn/feature_map/feature_map_implemented/qek_feature_map.py
The name QEKFeatureMap, i.e. Quantum Embedding Kernel is actually just a name we used internally due to the Hubregtsen paper.
In general this feature map is often called data re-uploading circuit. Nevertheless, there also several different architectures in the literature listed under the name of re-uploading.
We should consider renaming the feature map. Maybe with a reference to Hubregtsen and re-uploading?

Ideas:

Hubregtsen
Reuploading


Reorganize docs dist/assets/ on build

With the move to v4.1 docs, I replaced the assets used by the v4.0 docs. This caused the site to have a broken appearance. I've fixed manually for now, but I'll need to rework how we organize those in the directory structure to fix automatically moving forward.

Fixed in #26732


[bug] auto start launch minimized not working

Describe the bug
app is not minimized when auto startup
To reproduce

set auto startup in windows setting
reboot

Expected behavior
app is auto started but only in tray
Screenshots
No response
Desktop (please complete the following information)

OS: Windows 11 22H2
Ver: 1.9.1

Smartphone (please complete the following information)
No response
Additional context
found this open: #421
checked config and "flutter.ls_auto_start_launch_minimized": true

This still seems to be an issue on v1.16.1 (56)
All of these options ticked but still shows up on boot:


should wrapper-small be renamed?

I thought wrapper-small should be replaced with wrapper wrapper--small
even the inline docs hint at this

Wrapper

This is something I did in my personal fork so I've created a pull request (https://github.com/cutestrap/cutestrap/pull/28). It also saves a couple of lines of code (every little helps).

I had it like that originally, which is why the docs allude to it, but had changed it. Merged in this PR, thanks @csscallum :)
Just getting back from a vacation, so I'll be more active again.


Cluster with embedded etcd does not initialize

Environmental Info:
k3s version v1.19.2+k3s1 (d38505b1)
Node(s) CPU architecture, OS, and Version:
Ubuntu 18.04
Linux ids-rnc-k3s-04 4.15.0-118-generic #119-Ubuntu SMP Tue Sep 8 12:30:01 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration:
3 nodes with embedded etcd
Describe the bug:
first node starts without issues with command:
curl -sfL https://get.k3s.io | INSTALL_K3S_CHANNEL=latest sh -s - --cluster-init --token mytoken
second don't get over "[INFO]  systemd: Starting k3s" with command:
curl -sfL https://get.k3s.io | INSTALL_K3S_CHANNEL=latest sh -s - --server https://<IP_ADDRESS>:6443 --token mytoken
Error on first node:
Oct 14 09:29:28 ids-rnc-k3s-04 k3s[5360]: health check for peer 681c415795beb90c could not connect: Forbidden
Oct 14 09:29:31 ids-rnc-k3s-04 k3s[5360]: failed to reach the peerURL(https://<IP_ADDRESS>:2380) of member 681c415795beb90c (Get "https://<IP_ADDRESS>:2380/version": Forbidden)
Oct 14 09:29:31 ids-rnc-k3s-04 k3s[5360]: cannot get the version of member 681c415795beb90c (Get "https://<IP_ADDRESS>:2380/version": Forbidden)

error on second node:
Oct 14 09:30:27 ids-rnc-k3s-05 k3s[2822]: WARNING: 2020/10/14 09:30:27 grpc: addrConn.createTransport failed to connect to {https://<IP_ADDRESS>:2379  <nil> 0 <nil>}. Err :connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:2379: connect: connection refused". Reconnecting...
Oct 14 09:30:28 ids-rnc-k3s-05 k3s[2822]: {"level":"warn","ts":"2020-10-14T09:30:28.134Z","caller":"clientv3/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"passthrough:///https://<IP_ADDRESS>:2379","attempt":0,"error":"rpc error: code = DeadlineExceeded desc = latest balancer error: connection error: desc = \"transport: Error while dialing dial tcp <IP_ADDRESS>:2379: connect: connection refused\""}
Oct 14 09:30:28 ids-rnc-k3s-05 k3s[2822]: time="2020-10-14T09:30:28.135006852Z" level=info msg="Failed to test data store connection: context deadline exceeded"

Steps To Reproduce:

install ubuntu 18.04 cloud image on 3 vmware VMs
set http(s)_proxy and no_proxy ("<IP_ADDRESS>,<IP_ADDRESS>/8,<IP_ADDRESS>/8,<IP_ADDRESS>/16,<IP_ADDRESS>/12,<IP_ADDRESS>/16,localhost")
Installed K3s: latest, flags see above

Expected behavior:
Startup of the cluster with embedded etcd
Actual behavior:
cluster could not initialize

stable channel with dqlite works on the same environment (omitted: "INSTALL_K3S_CHANNEL=latest")

Are ports 2379 and 2380 open between the two servers?

Yes I opened the whole net on iptables on all nodes:
iptables -A INPUT -p tcp -s <IP_ADDRESS>/28 -j ACCEPT
iptables -A OUTPUT -p tcp -d  <IP_ADDRESS>/28 -j ACCEPT

Yes we use a proxy:
https_proxy=http://proxy.ourdomain.corp:3128
http_proxy=http://proxy.ourdomain.corp:3128
no_proxy=<IP_ADDRESS>,<IP_ADDRESS>/8,<IP_ADDRESS>/8,<IP_ADDRESS>/16,<IP_ADDRESS>/12,localhost

If I do a curl local on the second node I get a connection refused too:
curl https://localhost:2380/version
curl: (7) Failed to connect to localhost port 2380: Connection refused

This should work, right?

it really seems to be a proxy issue. If I disable the proxy on both nodes and start it works:
export http_proxy=""
export https_proxy=""

K3S_TOKEN=mytoken k3s server --server https://<IP_ADDRESS>:6443

Is there a IP range or name I missed in the no_proxy?

If I delete the proxy in /etc/systemd/system/k3s.service.env the cluster succeeds, but k8s cannot install the container because of the missing proxy.
curl -sfL https://get.k3s.io | INSTALL_K3S_SKIP_START=true INSTALL_K3S_CHANNEL=latest sh -s - --cluster-init --token mytoken
echo "" > /etc/systemd/system/k3s.service.env
service k3s start

kubectl get nodes,pod -A
NAME                  STATUS   ROLES         AGE     VERSION
node/ids-rnc-k3s-04   Ready    etcd,master   10m     v1.19.2+k3s1
node/ids-rnc-k3s-05   Ready    etcd,master   7m11s   v1.19.2+k3s1
node/ids-rnc-k3s-06   Ready    etcd,master   6m33s   v1.19.2+k3s1

NAMESPACE     NAME                                         READY   STATUS              RESTARTS   AGE
kube-system   pod/coredns-66c464876b-xvrdn                 0/1     ContainerCreating   0          9m51s
kube-system   pod/helm-install-traefik-ndpxb               0/1     ContainerCreating   0          9m51s
kube-system   pod/local-path-provisioner-7ff9579c6-sm44z   0/1     ContainerCreating   0          9m51s
kube-system   pod/metrics-server-7b4f8b595-5f62k           0/1     ContainerCreating   0          9m51s

Normally you would also put your internal DNS zone in the no_proxy list, since no_proxy's IP matching logic only works if you're specifying a bare IP address in the URL - it doesn't exclude things that RESOLVE to those ranges. Since you're using short hostnames instead of FQDNs your life is a little more difficult - can you try adding all your node hostnames to the no_proxy list?

Sometimes whole IP ranges are accepted as no_proxy, sometimes not. I took this from here:
https://rancher.com/docs/rancher/v2.x/en/installation/other-installation-methods/behind-proxy/launch-kubernetes/
I tried to add each hostname and each IP from the nodes to the no_proxy with the same result.
Then I changed the no_proxy to uppercase NO_PROXY variable name and everything works as expected. Even with just the IP ranges:
NO_PROXY="<IP_ADDRESS>,<IP_ADDRESS>/8,<IP_ADDRESS>/8,<IP_ADDRESS>/16,<IP_ADDRESS>/12,localhost,ourdomain.tld"
Thank you for helping me with this!

Yes, sometimes netmasks are accepted, sometimes they're not. The proxy dialer logic ALWAYS matches against the host portion of the URI though - if the host is an IP address it will be matched against CIDR blocks (if the library supports it), if it's a hostname it's matched against hostname or domain patterns.
Use of uppercase or lowercase environment variables is another thing that varies by library. I generally set all the proxy vars in both upper and lowercase, just to get the best coverage.


How to make it show up in fullscreen mode?

It shows in regular screens, but I couldn't make it show up in fullscreen mode - did I miss any options or is it not supported?

Just to be sure, you mean when an element has been made fullscreen using the Fullscreen API?
I've never tried that, but it could just be a z-index issue. Please provide a reproduction using CodeSandbox if you don't resolve the issue.

Just to be sure, you mean when an element has been made fullscreen using the Fullscreen API?
I've never tried that, but it could just be a z-index issue. Please provide a reproduction using CodeSandbox if you don't resolve the issue.

Hi Joss, yes that's right.
I just created a sandbox project at
https://codesandbox.io/s/musing-frog-5v3fs?fontsize=14&hidenavigation=1&theme=dark
.
However, in this environment, the fullscreen API doesn't seem to work and I
got an error when trying to make it fullscreen.
[image: image.png]
Thanks!
Ming
On Mon, Jan 4, 2021 at 1:35 AM Joss Mackison<EMAIL_ADDRESS>wrote:

Just to be sure, you mean when an element has been made fullscreen using
the Fullscreen API
https://developer.mozilla.org/en-US/docs/Web/API/Fullscreen_API?
I've never tried that, but it could just be a z-index issue. Please
provide a reproduction using CodeSandbox https://codesandbox.io/ if you
don't resolve the issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jossmac/react-toast-notifications/issues/147#issuecomment-753810186,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABFSXYZJZ2XIOJE4KAZ4MLTSYFVTFANCNFSM4VNRPHTA
.

Hi Joss, yes that's right.
I just created a sandbox project at
https://codesandbox.io/s/musing-frog-5v3fs?fontsize=14&hidenavigation=1&theme=dark
.
However, in this environment, the fullscreen API doesn't seem to work and I
got an error when trying to make it fullscreen.
[image: image.png]
Thanks!
Ming
On Mon, Jan 4, 2021 at 1:35 AM Joss Mackison<EMAIL_ADDRESS>wrote:

Just to be sure, you mean when an element has been made fullscreen using
the Fullscreen API
https://developer.mozilla.org/en-US/docs/Web/API/Fullscreen_API?
I've never tried that, but it could just be a z-index issue. Please
provide a reproduction using CodeSandbox https://codesandbox.io/ if you
don't resolve the issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jossmac/react-toast-notifications/issues/147#issuecomment-753810186,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABFSXYZJZ2XIOJE4KAZ4MLTSYFVTFANCNFSM4VNRPHTA
.

Thanks for that @miliu99
After some digging, appears to be by design that fullscreen elements trump stacking contexts. Knowing that now, it makes sense that elements outside of the fullscreen element will not be visible. This is because of the portal used to render the toast container.

Thanks for that @miliu99
After some digging, appears to be by design that fullscreen elements trump stacking contexts. Knowing that now, it makes sense that elements outside of the fullscreen element will not be visible. This is because of the portal used to render the toast container.

Good to know...Thank you very much for the update, Joss.
On Mon, Jan 4, 2021 at 3:50 PM Joss Mackison<EMAIL_ADDRESS>wrote:

Thanks for that @miliu99 https://github.com/miliu99
After some digging, appears to be by design that fullscreen elements trump
stacking contexts. Knowing that now, it makes sense that elements outside
of the fullscreen element will not be visible. This is because of the
portal https://reactjs.org/docs/portals.html used to render the toast
container.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jossmac/react-toast-notifications/issues/147#issuecomment-754241729,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABFSXYYHUXLAEYWEWXFFVDTSYIZ3NANCNFSM4VNRPHTA
.

Good to know...Thank you very much for the update, Joss.
On Mon, Jan 4, 2021 at 3:50 PM Joss Mackison<EMAIL_ADDRESS>wrote:

Thanks for that @miliu99 https://github.com/miliu99
After some digging, appears to be by design that fullscreen elements trump
stacking contexts. Knowing that now, it makes sense that elements outside
of the fullscreen element will not be visible. This is because of the
portal https://reactjs.org/docs/portals.html used to render the toast
container.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jossmac/react-toast-notifications/issues/147#issuecomment-754241729,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABFSXYYHUXLAEYWEWXFFVDTSYIZ3NANCNFSM4VNRPHTA
.


[CORE] Move ch rules from core to ch backend

What changes were proposed in this pull request?
Avoid compile unnecessary class.
How was this patch tested?
PASS CI

Why

Why. These are enable in CH, but doesn't mean they only could be used in CH

Thank you @lgbo-ustc for review. This pr only mvoes rule which is dedicated for ch backend...  If a rule can be reused for other backends, it should check BackendsApiManager.getSettings.supportxxx, e.g., MergeTwoPhasesHashBaseAggregate which is also only used for ch backend but live in core.

Why. These are enable in CH, but doesn't mean they only could be used in CH

Thank you @lgbo-ustc for review. This pr only mvoes rule which is dedicated for ch backend... If a rule can be reused for other backends, it should check BackendsApiManager.getSettings.supportxxx, e.g., MergeTwoPhasesHashBaseAggregate which is also only used for ch backend but live in core.

I think there have been settings to enable/disable there rules,

It may be a problem to add rules for some common issues that could exists in backends

I think it's not a good story to say a rule is created for one backend but say it is not designed for that backend... and at least the tests should be added into gluten-ut module for all backends and skip backend which is not enabled by default.
Do you mean RewriteDateTimestampComparisonRule and CommonSubexpressionEliminateRule are generic for velox backend ? If so ,i can leave them to core for now and see if we can help to make it work.
BTW, the RewriteToDateExpresstionRule and CountDistinctWithoutExpand are bound to ch backend code and we can move them.


Allow to remove copy right notice by setting help_instructions value

Enhancement/feature description
Allow to remove copy right notice by setting help_instructions value
Steps which explain the enhancement/feature

When click on "?/Help" to pop up help information, at the bottom of the pop up window, a URL and a copy right information are shown as in the image below, currently you allows us to set help_instructions to provide customized help information, however the copyright and URL cannot be overridden unless directly modify the tablefilter.js file, is it possible to allow us to remove this URL and copy right information by setting  help_instructions  value?

Current and suggested behavior
[Describe current and suggested behavior here]
Why would the enhancement be useful to most users
Screenshots and GIFs

Additional context
Describe alternatives you've considered
TableFilter Version: [Enter TableFilter version here]

Please note you can use the defaultHtml property on the Help instance to modify the instructions footer, ie:
var tf = new TableFilter('my-table-id', myTfConfig);
var help = tf.feature('help');
help.defaultHtml = '';
tf.init();

Refer to http://www.tablefilter.com/docs/class/src/modules/help.js~Help.html#instance-member-defaultHtml

Thank you very Koalyptus, it works perfectly.
Regards
Lijie YIN

From: koalyptus<EMAIL_ADDRESS>Sent: Friday, August 28, 2020 8:28 PM
To: koalyptus/TableFilter<EMAIL_ADDRESS>Cc: Li-Jie Yin<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [koalyptus/TableFilter] Allow to remove copy right notice by setting help_instructions value (#788)
[External Email] Please note, this email was sent from outside IR - be cautious particularly with links and attachments.
Please note you can use the defaultHtml property on the Help instance to modify the instructions footer, ie:
var tf = new TableFilter('my-table-id', myTfConfig);
var help = tf.feature('help');
help.defaultHtml = '';
tf.init();
Refer to http://www.tablefilter.com/docs/class/src/modules/help.js~Help.html#instance-member-defaultHtml
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/koalyptus/TableFilter/issues/788#issuecomment-682451566, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEM6XEHWKFOGITK6FWU7ODTSC6BDBANCNFSM4QLHPF7A.

This e-mail has been scanned for viruses Email Security.cloud - powered by Symantec.
For further information visit https://www.symantec.com/products/messaging-security
The information transmitted by this email is intended only for the person or entity to which it is addressed. This email may contain proprietary, confidential, and/or privileged material. If you are not the intended recipient of this message, be aware that any use, review, distribution, or reproduction is strictly prohibited. If you received this message in error, please contact the sender and delete the material from your system.


[tool_crash] ArgumentError: Invalid argument(s): Cannot find executable for /Users/xarvis/Developer/flutter/bin/cache/artifacts/engine/android-arm-release/darwin-x64/gen_snapshot.

Command
flutter --quiet assemble --depfile /Users/xarvis/AndroidStudioProjects/hangman/build/app/intermediates/flutter/release/flutter_build.d --output /Users/xarvis/AndroidStudioProjects/hangman/build/app/intermediates/flutter/release -dTargetFile=lib/main.dart -dTargetPlatform=android -dBuildMode=release -dTrackWidgetCreation=true -dTreeShakeIcons=true android_aot_bundle_release_android-arm android_aot_bundle_release_android-arm64 android_aot_bundle_release_android-x64

Steps to Reproduce

...
...
...

Logs
ArgumentError: Invalid argument(s): Cannot find executable for /Users/xarvis/Developer/flutter/bin/cache/artifacts/engine/android-arm-release/darwin-x64/gen_snapshot.
#0      _getExecutable (package:process/src/interface/local_process_manager.dart:124:5)
#1      LocalProcessManager.start (package:process/src/interface/local_process_manager.dart:40:30)
#2      ErrorHandlingProcessManager.start.<anonymous closure> (package:flutter_tools/src/base/error_handling_io.dart:638:33)
#3      _run (package:flutter_tools/src/base/error_handling_io.dart:532:20)
#4      ErrorHandlingProcessManager.start (package:flutter_tools/src/base/error_handling_io.dart:638:12)
#5      _DefaultProcessUtils.start (package:flutter_tools/src/base/process.dart:472:28)
#6      _DefaultProcessUtils.stream (package:flutter_tools/src/base/process.dart:491:35)
#7      GenSnapshot.run (package:flutter_tools/src/base/build.dart:73:26)
#8      AOTSnapshotter.build (package:flutter_tools/src/base/build.dart:194:56)
#9      AndroidAot.build (package:flutter_tools/src/build_system/targets/android.dart:232:52)
#10     _BuildInstance._invokeInternal (package:flutter_tools/src/build_system/build_system.dart:796:27)
<asynchronous suspension>
#11     Future.wait.<anonymous closure> (dart:async/future.dart)
<asynchronous suspension>
#12     _BuildInstance.invokeTarget (package:flutter_tools/src/build_system/build_system.dart:734:32)
<asynchronous suspension>
#13     Future.wait.<anonymous closure> (dart:async/future.dart)
<asynchronous suspension>
#14     _BuildInstance.invokeTarget (package:flutter_tools/src/build_system/build_system.dart:734:32)
<asynchronous suspension>
#15     FlutterBuildSystem.build (package:flutter_tools/src/build_system/build_system.dart:563:16)
<asynchronous suspension>
#16     AssembleCommand.runCommand (package:flutter_tools/src/commands/assemble.dart:220:32)
<asynchronous suspension>
#17     FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:1157:12)

[✓] Flutter (Channel stable, 2.0.3, on Mac OS X 10.15.6 19G73 darwin-x64, locale en-IN)
    • Flutter version 2.0.3 at /Users/xarvis/Developer/flutter
    • Framework revision 4d7946a68d (9 days ago), 2021-03-18 17:24:33 -0700
    • Engine revision 3459eb2436
    • Dart version 2.12.2

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.1)
    • Android SDK at /Users/xarvis/Library/Android/sdk
    • Platform android-30, build-tools 30.0.1
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.4, Build version 12D4e
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 51.0.1
    • Dart plugin version 193.7547
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.53.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.20.0

[✓] Connected device (2 available)
    • iPhone 11 Pro (mobile) • B7841DBB-CF3A-4983-ACF2-6A0440C6C325 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-4 (simulator)
    • Chrome (web)           • chrome                               • web-javascript • Google Chrome 89.0.4389.90

• No issues found!

Flutter Application Metadata
Type: app
Version: 1.0.0+1
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: stable
Creation framework version: 4d7946a68d26794349189cf21b3f68cc6fe61dcb
Plugins
audioplayers-0.16.2
firebase_admob-0.9.3+4
firebase_core-0.4.5
firebase_core_web-0.1.1+2
path_provider-1.6.28
path_provider_linux-0.0.1+2
path_provider_macos-0.0.4+8
path_provider_windows-0.0.5
sqflite-1.3.2+4
url_launcher-5.7.10
url_launcher_linux-0.0.1+4
url_launcher_macos-0.0.1+9
url_launcher_web-0.1.5+3
url_launcher_windows-0.0.1+3

@Ashraful11
could you try with the latest master
possibly fixed by https://github.com/flutter/flutter/pull/78272

Original issue, https://github.com/flutter/flutter/issues/68475, was fixed by above referred PR.
@Ashraful11 Try to switch to latest master and try again to see if issue persists or not.
flutter channel master
flutter upgrade

Thanks! It Worked..

It's work for me too ! thanks for the help.
Someone know when that will be available in channel stable ?


Added FOodleDictionaryArchive

Used to parse DictionaryData and CompactCompresorState in .udic files

with which files did you try the code?

Also, tested with .udic files from both Fortnite and Paragon, both work correctly.

it just crashed in an unsafe block when I tried Fortnite's .udic
What's the data returned?


Add more lookahead optimizer tests

Codecov Report

Merging #53 into master will increase coverage by 0.33%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #53      +/-   ##
==========================================
+ Coverage    90.1%   90.44%   +0.33%
==========================================
  Files          12       12
  Lines         576      586      +10
  Branches      134      134
==========================================
+ Hits          519      530      +11
  Misses         29       29
+ Partials       28       27       -1

Impacted Files
Coverage Δ

torch_optimizer/sgdw.py
83.67% <ø> (+2.04%)
:arrow_up:

torch_optimizer/lookahead.py
93.1% <100%> (+1.43%)
:arrow_up:

torch_optimizer/novograd.py
85.71% <100%> (ø)
: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 57d63c5...205c606. Read the comment docs.


Remove CDC disclaimer about estimated 1st dose data.

Yeah, that sounds good if it's not too much trouble! 🙏


fileformat/format_detection: use file magic to detect COFF files.

Do not parse COFF files at format detection stage - this could be slow if the file is big.

run tc tests

run tc tests


Improve lockit.gd script

As @fleskesvor stated in #140:

There's room for improvement here. Using a shell command to tidy up .lockit files doesn't seem very convenient. Maybe it would be better to support an in-place option like sed does. Ie. overwrite the .esc file but give an optional file extension that will be used to create a backup of the original.

We should also write some basic documentation on usage, as well as a nice help text in the CLI, like http://docopt.org/.

The script should also use PoolStringArray.join() instead of the custom join function implemented in #151.

097d288dc501c75b210dda18f510fd183c0b0db3 adds very basic documentation and uses PoolStringArray.join(), plus some fixes to write better CSV.

Not used anymore in Escoria 4.


heads support

api to consider:
skin:
official: https://textures.minecraft.net/texture/ (will be just used directly)
crafatar
https://skinmc.net/api/v1/renders/skins/
username -> uuid (needed in flying squid when giving heads)
api.minetools.eu/uuid/Jeb_

https://wiki.vg/Mojang_API#Usernames_to_UUIDs

https://wiki.vg/Mojang_API#Usernames_to_UUIDs

Mojang API doesn't have cors support so it can't be used in web application. That's why I'm using fast unofficial api for getting skins by username


Update redirect for OAuth

Updates to a unique OAuth redirect to avoid clash with other SDK sample viewers on same device. I created a separate OAuth credential so also updates the clientId.

I could move the dispose calls in this PR if it's easier to pull those out of generate offline map @PaulAllanSturm

I could move the dispose calls in this PR if it's easier to pull those out of generate offline map @PaulAllanSturm

I don't think we'll run into merge conflicts so it should all be fine as it is now.


Bring code coverage above 90%

Even though 100% code coverage does not mean having tested all the code, having less than 100% definitely means that some things went untested. I propose to try and push the coverage for the critical parts: NoteOrganiser.py, frames.py, popups.py and widgets.py. To help identify the problematic points, let's use Coveralls.

Now that the coverage is roughly at a good spot, the rest should be improved through Robot Framework. I don't know if it can be part of the simple coverage computation in Travis, though.


minor: clarify paramname

use more generic param name since run also takes gist-uris and streams as 1st param

travis broke because of reading timeouts on packagist

Thank you @staabm.


Set GCC_INSTALL_PREFIX cmake option when building LLVM

I found that the build clang 3.7.0 was unable to find the toolchain GCC when used in a downstream C++ project. These changes fix that. Can someone verify and comment on the patch? Thank you

I left one comment in init.sh

How does the variable behave? Does this work if the toolchain directories are relocated after being built?
The way Impala solves this is by setting -gcc-toolchain to point clang at the gcc includes/libraries under the toolchain directory.

Ah, no it does not. Can you tell me more about how to point clang to the gcc toolchain after the fact?

In current cdh5-trunk there is a bunch of hackery around setting include and library paths.
With later versions of LLVM (e.g. 3.7 or 3.8) you can use the --gcc-toolchain argument:

See: http://gerrit.cloudera.org/#/c/2486/4/be/CMakeLists.txt

Thank you. For posterity, the solution is to pass
--gcc-toolchain=${GCC_ROOT}
to clang executables


Compile main LESS file when included file changes

I seem to have the same problem as #767 but the solution presented there doesn't seem to work for me. I have a main less file (styles.less):
@import url('less/_teste.less');

When I alter _teste.less I get this in the brunch debug log:
  brunch:watch change web/static/css/less/_teste.less +5m
  brunch:list Reading web/static/css/less/_teste.less +1ms
  brunch:write Writing 0/2 files +69ms
29 Jan 14:02:31 - info: compiled in 69ms

No mention of recompiling styles.less. When I touch styles.less:
  brunch:watch change web/static/css/styles.less +11s
  brunch:list Reading web/static/css/styles.less +1ms
  brunch:pipeline Compiling web/static/css/styles.less @ LESSCompiler +1ms
  brunch:pipeline Dependencies web/static/css/styles.less @ LESSCompiler +2ms
  brunch:list Compiled web/static/css/styles.less +0ms
  brunch:write Writing 1/2 files +68ms
  brunch:generate Concatenating [web/static/css/animate.css, web/static/css/app.css, web/static/css/font-awesome.min.css, web/static/css/ink-flex.min.css, web/static/css/ink-ie.min.css, web/static/css/ink-legacy.min.css, web/static/css/ink.min.css, web/static/css/less/teste.less, web/static/css/styles.css, web/static/css/styles.less] => priv/static/css/app.css +2ms
  brunch:common Writing priv/static/css/app.css +34ms
  brunch:common Writing priv/static/css/app.css.map +49ms
29 Jan 14:03:40 - info: compiled styles.less and 9 cached files into app.css in 208ms

The brunch version is 2.2.2 and less-brunch is 1.8.1. Am I doing something wrong?
My brunch config is:
exports.config = {
  // See http://brunch.io/#documentation for docs.
  files: {
    javascripts: {
      joinTo: "js/app.js"

      // To use a separate vendor.js bundle, specify two files path
      // https://github.com/brunch/brunch/blob/stable/docs/config.md#files
      // joinTo: {
      //  "js/app.js": /^(web\/static\/js)/,
      //  "js/vendor.js": /^(web\/static\/vendor)|(deps)/
      // }
      //
      // To change the order of concatenation of files, explicitly mention here
      // https://github.com/brunch/brunch/tree/master/docs#concatenation
      // order: {
      //   before: [
      //     "web/static/vendor/js/jquery-2.1.1.js",
      //     "web/static/vendor/js/bootstrap.min.js"
      //   ]
      // }
    },
    stylesheets: {
      joinTo: "css/app.css"
    },
    templates: {
      joinTo: "js/app.js"
    }
  },

  conventions: {
    // This option sets where we should place non-css and non-js assets in.
    // By default, we set this to "/web/static/assets". Files in this directory
    // will be copied to `paths.public`, which is "priv/static" by default.
    assets: /^(web\/static\/assets)/
  },

  // Phoenix paths configuration
  paths: {
    // Dependencies and current project directories to watch
    watched: [
      "web/static",
      "test/static"
    ],

    // Where to compile files to
    public: "priv/static"
  },

  // Configure your plugins
  plugins: {
    babel: {
      presets: ["es2015", "react"],
      // Do not use ES6 compiler in vendor code
      ignore: [/web\/static\/vendor/]
    }
  },

  modules: {
    autoRequire: {
      "js/app.js": ["web/static/js/app"]
    }
  },

  npm: {
    enabled: true,
    // Whitelist the npm deps to be pulled in as front-end assets.
    // All other deps in package.json will be excluded from the bundle.
    whitelist: ["phoenix", "phoenix_html", "react", "react-dom"]
  }
};

Ah, it seems it was a problem with my import syntax. Changing it to:
@import 'less/_teste.less';

made it work.


Remove unneccessary unzipping

Stopped the program from unzipping the file if the log already exists and is already the same size as the estimated unpacked size. Helps with the huge logs i.e. 10

Thanks! Good idea.

np! Thanks for making it!


OSDP DS

Apart from the comments, this looks very good.

I think rest of it looks fine apart from the comments.


Add more performance tests for branching

Resolves #1901

I wasn't be able to come up with more tests to measure our branching performance. Open to others' suggestions.

Huge difference in the tps. Is that repeatable? If yes, let's fix it. If not, this test is too noisy.

I also experienceed that on my local, so it wasn't because slow disk IOs on Mac. I did create a flamegraph yesterday. Look like because of slow wal redo

@hlinnaka I found the reason why there is such a huge difference. It's quite interesting that the child branch does a sequence scan to find an indexed column:
postgres=# explain analyze select * from pgbench_accounts where aid=10;
                                                            QUERY PLAN
----------------------------------------------------------------------------------------------------------------------------------
 Gather  (cost=1000.00..22602.43 rows=1 width=97) (actual time=344.235..344.976 rows=1 loops=1)
   Workers Planned: 2
   Workers Launched: 2
   ->  Parallel Seq Scan on pgbench_accounts  (cost=0.00..21602.33 rows=1 width=97) (actual time=267.328..341.883 rows=0 loops=3)
         Filter: (aid = 10)
         Rows Removed by Filter: 333333
 Planning Time: 1.367 ms
 Execution Time: 344.989 ms
(8 rows)

while the parent does not:
postgres=# explain analyze select * from pgbench_accounts where aid=10;
                                                               QUERY PLAN
-----------------------------------------------------------------------------------------------------------------------------------------
 Index Scan using pgbench_accounts_pkey on pgbench_accounts  (cost=0.42..8.44 rows=1 width=97) (actual time=0.113..0.113 rows=1 loops=1)
   Index Cond: (aid = 10)
 Planning Time: 1.743 ms
 Execution Time: 0.171 ms
(4 rows)

The reason is that we determine the child's starting LSN based on the parent's last_record_lsn. In other words, if we create the child before the WALs initializing indices are processed by the parent, the child will not have any information about the indices.
To prove this is the cause, I added a sleep right before the branch creation in the test_compare_child_and_root_pgbench_perf:
    pg_bin.run_capture(['pgbench', '-i', pg_root.connstr(), '-s10'])

+    time.sleep(5)

    env.neon_cli.create_branch('child', 'root')
    pg_child = env.postgres.create_start('child')

Now, the child and root branches have comparable results.
Not sure how to fix this. Do you have any suggestions?

The reason is that we determine the child's starting LSN based on the parent's last_record_lsn. In other words, if we create the child before the WALs initializing indices are processed by the parent, the child will not have any information about the indices.

A-ha! So it's a similar case as https://github.com/neondatabase/neon/pull/2131. The fix could be similar here, get the latest LSN from Postgres (select pg_current_wal_lsn()) and pass that to the create_branch call.
This seems to happen quite frequently with our tests. Almost always when you call create_branch(), you would want to wait for all the in-flight WAL to be processed by the pageserver first. Could we do that in a more whole-sale fashion in the python tests, instead of adding a wait before every create_branch() call? Or make the 'lsn' argument mandatory to force the test writer to do it.

Could we do that in a more whole-sale fashion in the python tests, instead of adding a wait before every create_branch() call? Or make the 'lsn' argument mandatory to force the test writer to do it.

Make the lsn required to call create_branch is not a trivial change. A go-to-reference to that function returns 90 results. A quicker way would be calculating the LSN using  select pg_current_wal_lsn() in create_branch if no LSN is specified. I'll try to do that in this PR if the change is simple

A quicker way would be calculating the LSN using select pg_current_wal_lsn() in create_branch if no LSN is specified. I'll try to do that in this PR if the change is simple

Updated in https://github.com/neondatabase/neon/pull/2143/commits/b45f09109d9517cd7c1b81a29747e7d94e260fb1

There's a few different things going on here, with the "sequentialization" of the pgbench init steps, and the addition of new tests. I'd suggest splitting this up into multiple PRs so that you can commit some parts, while discussion and investigation continues on the others.

Agree. Will do the separation. At first, I thought the "create-branch" change is small, so it can fit into this patch. But it appeared to generate some issues.

Agree. Will do the separation.

Created #2189. I also added more comments explaining the new tests. I think we can either continue reviewing this patch while I'm investigating the "pgbench init" issue in other PR or waiting for the other PR to land to continue this PR.
The former, IMO, is more efficient, but not sure if it's ok to merge test_compare_child_and_root_pgbench_perf despite the issue described in https://github.com/neondatabase/neon/pull/2143#issuecomment-1192283904

Hmm, it would be good to dig deeper into that. Do you suspect it was a race condition in the pageserver? That sounds like a bug we should find and fix. I don't see anything inherently wrong with this test as it was.
Or maybe running multiple pgbench initializations just overloads the server, so that each initialization takes a long time? In that case, a longer statement_timeout would help. Or making things faster if possible. The slowest SQL command that 'pgbench -i` runs is probably a CREATE INDEX. (Or ALTER TABLE ADD PRIMARY KEY, which is essentially the same thing). That can legitimately take a long time, proportional to the scale factor. How long does it take in this test? How close is it to statement_timeout?

I did some investigation. Look like it was because of an error when creating branch from an "invalid" starting LSN. To recap the issue I encountered,

running a workload (pgbench init) on a branch b0
create a branch b1 based on b0's latest flush LSN 0/16BA000. ancestor last record lsn at the time of creation: 0/16B8DC0
start b1, sk refuses to start WAL streaming for b1:

Requested streaming from 0/16BA000, which is before the start of the timeline 0/16BA018

b1 cannot receive WAL because of sk, but the flush LSN stored inside the compute node of 1 is still advanced. Start at 0/16BA018, increase to 0/16BA050 -> 0/16C0000 -> 0/16C01C8  (maybe because of background writer)
As a result, creating b2 from b1 based on the latest flush LSN timeout as no new WAL is processed hence last_record_lsn of b2 never exceeds the starting LSN

This issue should be reproducible based on the changes in https://github.com/neondatabase/neon/tree/use-latest-lsn-on-create-branch and using this command
RUST_LOG=debug ./scripts/pytest -k test_branching_with_pgbench\[ca

My wild guess is that the starting LSN used to create b1 is invalid. There is probably a mismatch between what is stored in disk by neon and what is flushed as perceived by the compute node. 0/16BA000 should be probably rounded up/down to nearest valid LSN.
Tbh, currently I have no idea about the actual reason behind, so will need to dig a big deeper.
I only know how the branch is created from the neon side (populating metadata, create timeline directory). However, I have no idea how it is initialized from the postgres side. I'm not too familiar with the code. Looking at the log for branch b1,
2022-07-29 21:04:37.641 GMT [88384] LOG:  starting with zenith basebackup at LSN 0/16BA018, prev 0/0

It seems to determine the timeline's start LSN as 0/16BA018, but I have no idea where that number comes from. Would appreciate if anyone can provide instructions/places to better understand the PG initialization progress of new branch.
cc @hlinnaka

start b1, sk refuses to start WAL streaming for b1:

Requested streaming from 0/16BA000, which is before the start of the timeline 0/16BA018

I was able to find the reason behind this error. When generating a pgcontrol file during basebackup, we normalize the checkpoint.redo LSN:
        // Generate new pg_control needed for bootstrap
        checkpoint.redo = normalize_lsn(self.lsn, pg_constants::WAL_SEGMENT_SIZE).0;

/// If LSN points to the beginning of the page, then shift it to first record,
/// otherwise align on 8-bytes boundary (required for WAL records)
pub fn normalize_lsn(lsn: Lsn, seg_sz: usize) -> Lsn {
    if lsn.0 % XLOG_BLCKSZ as u64 == 0 {
        let hdr_size = if lsn.0 % seg_sz as u64 == 0 {
            XLOG_SIZE_OF_XLOG_LONG_PHD
        } else {
            XLOG_SIZE_OF_XLOG_SHORT_PHD
        };
        lsn + hdr_size as u64
    } else {
        lsn.align()
    }
}

So if, the specified starting LSN divided by XLOG_BLCKSZ (0/16BA000 in the above example), the checkpoint redo LSN will be larger than the starting LSN. Because the compute node relies on the checkpoint.redo as the WAL beginning LSN, this will result in an error as above.
I was able to consistently reproduce the above scenario using a simpler test in https://github.com/neondatabase/neon/pull/2189/files#diff-b8262ab057cd69a7bb4f457b8f0191c3337cb1571c6b659cc5afe4378c2a3880R96.
Should we fix this by calling normalize_lsn before branching?
cc @hlinnaka

Should we fix this by calling normalize_lsn before branching?

Updated in https://github.com/neondatabase/neon/pull/2189/commits/e4c3a3309349b4260780fb12e8241c217896e478

Rebased. This PR looks good to me, but I believe we still need to resolve https://github.com/neondatabase/neon/pull/2189 before this can be merged.

Rebased again. https://github.com/neondatabase/neon/pull/2189 has now been resolved, so unless some new blockers arise for this PR, this is ready to be committed.


Bump motor version

Current coverage is 94.12% (diff: 100%)

Merging #96 into master will not change coverage

@@             master        #96   diff @@
==========================================
  Files            11         11
  Lines           664        664
  Methods           0          0
  Messages          0          0
  Branches         79         79
==========================================
  Hits            625        625
  Misses           29         29
  Partials         10         10

Powered by Codecov. Last update 68308a1...8be99de


Opera Browser No Desktop notification, no tab notification

Marinara is working well in Opera, too. But the options for desktop or tab notifications have no effect.  Has somebody an idea or workaround to fix this?
I had no issues in the Vivaldi Browser which is Chrome based, too.

+1

+1

For me the desktop notifications where making the extension useless. After disable them but keeping new tab notifications on, it's working for me in Opera:
Version: 56.0.3051.107
Update stream: Stable
System: Windows 10 64-bit

After some debugging I found out that Firefox seems to have similar issues and those are already considered in Marinara's source code.

Thanks for the details. This extension was originally only intended for Chrome, but it seems that Chrome's extension API has become something of a de facto API for most other browsers.
There are a lot of small issues like this, but overall, things seem to mostly work, so I intend to support non-Chrome browsers as well.


Fix generated type declarations

Fix the generated type declarations.
By using TypeScript's special export = we're able to author source
that mostly looks like ESM but generates our desired declaration and js
output.
The published type declarations are currently export {}, which makes
it hard to use this package in typechecked files.
After this change, the generated JS file is mostly the same, but the
declaration file has the expected output:
import { JsMinifyOptions } from '@swc/core';
import webpack from 'webpack';
declare class SwcMinifyWebpackPlugin {
    private readonly options;
    constructor(options?: JsMinifyOptions);
    apply(compiler: webpack.Compiler): void;
    private transformAssets;
    private processAssets;
}
export = SwcMinifyWebpackPlugin;

Another change that may be helpful to use a shared tsconfig designed for
node, for example:
https://github.com/tsconfig/bases#node-lts--strictest-tsconfigjson
That will likely improve the build result and save generating
compatibility code that's not necessary for targeting Node.
I'd be happy to push that here or in another PR.

Released in 1.1.1

The new releases have the same problem, the published declarations are an empty export. At 1e03fee111c36abd05646d6b99cc31536b053130 (merge commit) this generated the expected declarations.


Unknown error: json: cannot unmarshal object into Go struct field APIError.detail of type string

I've got it from<EMAIL_ADDRESS>unmarshalAPIError function. Exception at unmarshalling doesn't allow me to see the original root cause of the request failure.
Example of JSON:
{"detail":{"name":"Enter a valid name. This value may contain only lowercase letters, numbers, dashes, underscores, or periods, and may not start or end with a dash, underscore, or period."}}

failed with with the following exception:
Unknown error: json: cannot unmarshal object into Go struct field APIError.detail of type string

As I see in the example of error message from server there has to be no nested objects in the JSON from the server
https://replicate.com/docs/reference/http#rate-limits

Hi @mmazurkevich. Thanks for reporting. The response sent by Replicate's API for invalid models in the POST /models endpoint is incorrect. This is something we'll need to fix on our side.

@mmazurkevich I'm happy to report that this is now fixed. Replicate's API now returns error objects in the form of RFC 9457 problem details. I just ran replicate model create with an invalid hardware sku, and it correctly repoted the error instead of panicking with that JSON error. Thanks again for reporting!


fix: mprocs doesn't work when nushell is a login shell

As a new Nushell user, I'll now be fixing all sorts of software just to have stuff that used to work, work again. Everybody makes bad life choices sometimes, right? Right? :shrug:
Before approving, please try just mprocs in your shell. BTW. Add to your ~/.gitconfig this convenient alias:
[alias]
pr = "!f() { git fetch -fu ${2:-$(git remote |grep '^upstream$' || echo origin)} refs/pull/$1/head:pr/$1 && git checkout pr/$1; }; f"

So you can git pr 3191 to do it.

I reverted from nushell.
My understanding here is as follows:
There's no way to start an interactive bash shell (that could accept user commands) without triggering all the system scripts, which destroy environment sometimes/somehow. For some reason when nushell was my logic shell, it would break what we're doing currently.


Run Publishing E2E Tests as part of a build

This change will cause Publishing End-to-end Tests to run
once the initial unit tests for this build has passed and will be
triggered as a dependent build.
These are used to test that none of the changes made in a commit to this
repo don't break the tech stack or break the end-to-end tests
environment.
The End-to-end tests take approximately 4/5 minutes to run and will make
it slower to get a passing build.

I wonder if we could test the govuk-components render correctly like this? Currently we have no way of knowing if a component is broken until testing on locally/integration/staging etc

@nickcolley quite possibly (and if not in the scope of these tests could always spin up something similar), what's the process to test them?


chore: update header -> headers change aligned to extism/extism#124

Pending release of runtime with manifest changes.

🥹


[SPARK-45188][SQL][DOCS] Update error messages related to parameterized sql()

What changes were proposed in this pull request?
In the PR, I propose to update some error formats and comments regarding sql() parameters - maps, arrays and struct might be used as sql() parameters. New behaviour has been added by https://github.com/apache/spark/pull/42752.
Why are the changes needed?
To inform users about recent changes introduced by SPARK-45033.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
By running the affected test suite:
$ build/sbt "core/testOnly *SparkThrowableSuite"

Was this patch authored or co-authored using generative AI tooling?
No.

Merging to master. Thank you, @cloud-fan for review.


Add JPMS support

Alter pom.xml to generate a module-info.class. All other class files still target Java 6. This allows the use of EvalEx with jlink out of the box.
If I'm reading the documentation right, JDK 9 availability varies depending on the Travis CI environment. This means it may be necessary to change .travis.yml to install the right JDK version -- let me know.

We will see, what Travis needs. Thanks!

@MDZhB
I had to use JDK11, because of Sonar.
But the moditect-maven-plugin gives an error when deploying. Any idea?
Here's the log:
[INFO] --- moditect-maven-plugin:1.0.0.RC2:add-module-info (add-module-info) @ EvalEx ---
Downloading from central: https://repo.maven.apache.org/maven2/org/eclipse/aether/aether-util/1.1.0/aether-util-1.1.0.pom
Downloaded from central: https://repo.maven.apache.org/maven2/org/eclipse/aether/aether-util/1.1.0/aether-util-1.1.0.pom (0 B at 0 B/s)
Downloading from central: https://repo.maven.apache.org/maven2/org/eclipse/aether/aether/1.1.0/aether-1.1.0.pom
Downloaded from central: https://repo.maven.apache.org/maven2/org/eclipse/aether/aether/1.1.0/aether-1.1.0.pom (0 B at 0 B/s)
Downloading from central: https://repo.maven.apache.org/maven2/org/eclipse/aether/aether-api/1.1.0/aether-api-1.1.0.pom
Downloaded from central: https://repo.maven.apache.org/maven2/org/eclipse/aether/aether-api/1.1.0/aether-api-1.1.0.pom (0 B at 0 B/s)
Downloading from central: https://repo.maven.apache.org/maven2/org/moditect/moditect/1.0.0.RC2/moditect-1.0.0.RC2.pom
Downloaded from central: https://repo.maven.apache.org/maven2/org/moditect/moditect/1.0.0.RC2/moditect-1.0.0.RC2.pom (0 B at 0 B/s)
Downloading from central: https://repo.maven.apache.org/maven2/com/beust/jcommander/1.60/jcommander-1.60.pom
Downloaded from central: https://repo.maven.apache.org/maven2/com/beust/jcommander/1.60/jcommander-1.60.pom (0 B at 0 B/s)
Downloading from central: https://repo.maven.apache.org/maven2/org/eclipse/aether/aether-util/1.1.0/aether-util-1.1.0.jar
Downloading from central: https://repo.maven.apache.org/maven2/org/eclipse/aether/aether-api/1.1.0/aether-api-1.1.0.jar
Downloaded from central: https://repo.maven.apache.org/maven2/org/eclipse/aether/aether-util/1.1.0/aether-util-1.1.0.jar (0 B at 0 B/s)
Downloading from central: https://repo.maven.apache.org/maven2/org/moditect/moditect/1.0.0.RC2/moditect-1.0.0.RC2.jar
Downloaded from central: https://repo.maven.apache.org/maven2/org/eclipse/aether/aether-api/1.1.0/aether-api-1.1.0.jar (0 B at 0 B/s)
Downloading from central: https://repo.maven.apache.org/maven2/com/beust/jcommander/1.60/jcommander-1.60.jar
Downloading from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
Downloaded from central: https://repo.maven.apache.org/maven2/org/moditect/moditect/1.0.0.RC2/moditect-1.0.0.RC2.jar (0 B at 0 B/s)
Downloaded from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar (0 B at 0 B/s)
Downloaded from central: https://repo.maven.apache.org/maven2/com/beust/jcommander/1.60/jcommander-1.60.jar (0 B at 0 B/s)
Error: /home/travis/build/[secure]/EvalEx/target/EvalEx-2.7-SNAPSHOT.jar is a modular JAR file that cannot be specified with the --generate-module-info option
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  17.509 s
[INFO] Finished at: 2021-11-01T09:54:56Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.moditect:moditect-maven-plugin:1.0.0.RC2:add-module-info (add-module-info) on project EvalEx: Execution add-module-info of goal org.moditect:moditect-maven-plugin:1.0.0.RC2:add-module-info failed: Invocation of jdeps failed: jdeps --generate-module-info /home/travis/build/[secure]/EvalEx/target/moditect /home/travis/build/[secure]/EvalEx/target/EvalEx-2.7-SNAPSHOT.jar -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
Script failed with status 1

Is there any chance you could provide a full log with the -e and -X switches enabled? I'm not able to reproduce this locally, so I'd like to know what I'm missing.

Sorry for the delay, I have re-run with mvn -e -X, but there is not much more information:
[INFO]
[INFO] --- moditect-maven-plugin:1.0.0.RC2:add-module-info (add-module-info) @ EvalEx ---
Downloading from central: https://repo.maven.apache.org/maven2/org/eclipse/aether/aether-util/1.1.0/aether-util-1.1.0.pom
Downloaded from central: https://repo.maven.apache.org/maven2/org/eclipse/aether/aether-util/1.1.0/aether-util-1.1.0.pom (0 B at 0 B/s)
Downloading from central: https://repo.maven.apache.org/maven2/org/eclipse/aether/aether/1.1.0/aether-1.1.0.pom
Downloaded from central: https://repo.maven.apache.org/maven2/org/eclipse/aether/aether/1.1.0/aether-1.1.0.pom (0 B at 0 B/s)
Downloading from central: https://repo.maven.apache.org/maven2/org/eclipse/aether/aether-api/1.1.0/aether-api-1.1.0.pom
Downloaded from central: https://repo.maven.apache.org/maven2/org/eclipse/aether/aether-api/1.1.0/aether-api-1.1.0.pom (0 B at 0 B/s)
Downloading from central: https://repo.maven.apache.org/maven2/org/moditect/moditect/1.0.0.RC2/moditect-1.0.0.RC2.pom
Downloaded from central: https://repo.maven.apache.org/maven2/org/moditect/moditect/1.0.0.RC2/moditect-1.0.0.RC2.pom (0 B at 0 B/s)
Downloading from central: https://repo.maven.apache.org/maven2/com/beust/jcommander/1.60/jcommander-1.60.pom
Downloaded from central: https://repo.maven.apache.org/maven2/com/beust/jcommander/1.60/jcommander-1.60.pom (0 B at 0 B/s)
Downloading from central: https://repo.maven.apache.org/maven2/org/eclipse/aether/aether-util/1.1.0/aether-util-1.1.0.jar
Downloading from central: https://repo.maven.apache.org/maven2/org/eclipse/aether/aether-api/1.1.0/aether-api-1.1.0.jar
Downloaded from central: https://repo.maven.apache.org/maven2/org/eclipse/aether/aether-util/1.1.0/aether-util-1.1.0.jar (0 B at 0 B/s)
Downloading from central: https://repo.maven.apache.org/maven2/org/moditect/moditect/1.0.0.RC2/moditect-1.0.0.RC2.jar
Downloaded from central: https://repo.maven.apache.org/maven2/org/eclipse/aether/aether-api/1.1.0/aether-api-1.1.0.jar (0 B at 0 B/s)
Downloading from central: https://repo.maven.apache.org/maven2/com/beust/jcommander/1.60/jcommander-1.60.jar
Downloading from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
Downloaded from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar (0 B at 0 B/s)
Downloaded from central: https://repo.maven.apache.org/maven2/com/beust/jcommander/1.60/jcommander-1.60.jar (0 B at 0 B/s)
Downloaded from central: https://repo.maven.apache.org/maven2/org/moditect/moditect/1.0.0.RC2/moditect-1.0.0.RC2.jar (0 B at 0 B/s)
Error: /home/travis/build/[secure]/EvalEx/target/EvalEx-2.7-SNAPSHOT.jar is a modular JAR file that cannot be specified with the --generate-module-info option
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  18.334 s
[INFO] Finished at: 2021-11-14T09:54:43Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.moditect:moditect-maven-plugin:1.0.0.RC2:add-module-info (add-module-info) on project EvalEx: Execution add-module-info of goal org.moditect:moditect-maven-plugin:1.0.0.RC2:add-module-info failed: Invocation of jdeps failed: jdeps --generate-module-info /home/travis/build/[secure]/EvalEx/target/moditect /home/travis/build/[secure]/EvalEx/target/EvalEx-2.7-SNAPSHOT.jar -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
Script failed with status 1

It also fails, if I run it locally. The error comes from the jdeps command, which gives above error.
You can test it locally (after the jar has been built with mvn clean install) with
jdeps --generate-module-info target\moditect target\EvalEx-2.7-SNAPSHOT.jar

The command seems to fail, because there is already module-info.java present i the jar, I guess.


IRONIC_USE_MARIADB option failed the dev-env test for release-1.2 and 1.3.

What steps did you take and what happened:
We tried to use MariaDB with dev-env as a workaround to the database locking issue by SQLite. It worked perfectly with main and release-1.4 but failed to pass with release-1.2 and release-1.3.  We made changes in JJB, Project-infra, Metal3-dev-env and CAPM3. It seems that setting IRONIC_USE_MARIADB true adds -m option for older releases of CAPM3 and BMO, which is not a valid option.  Thus was failing in the deploy script.  If the variable set to flase that means not to use mariaDB, it works with all the releases of CAPM3 and BMO.
After we get the fix for SQLite database fix from ironic, reverted all the changes related to the use of MariaDB.
What did you expect to happen:
It should work with all the CAPM3 releases.
Anything else you would like to add:
This needs a clear solution on how to use the variables which are not valid in release-1.3 and rlease-1.2
Environment:

Environment (metal3-dev-env or other):

/kind bug

/cc @mboukhalfa

/triage accepted

is this still flaky @smoshiur1237

Yes, the configuration in dev-env need modification to enable mariiadb for release 1.2 and 1.3


In this chess game the pawns can only move one slot in their fisrt turn. They should be able to move 2 slots.

Modify so each pawn can move either 1 or 2 slots on their first turn instead of just 1.
(This is my first time trying to contribute to the community, so this is more of a personal test to understand how to work with open-source projects. But please feel free to give me feedback :) )

I would like to work on this please assign it to me.

Hi, there I am new to open source and wanted to learn I would like to work on this project kindly assign it to me and provide me some guidance to work on it.
thanks

Not required


Guzzle sends request without body

It seems this is a bit outdated:
https://github.com/akitogo/MelissaAddressValidator/blob/0719825d0b059246c475cdb22b2a5bf22a9d2ff1/Controller/Address/Validate.php#L161
            $request = $client->request(
                Request::HTTP_METHOD_POST,
                self::API_REQUEST_ENDPOINT,
                [
                    'json' => $params
                ]
            );

if I run this, the body for the request within \GuzzleHttp\Client::requestAsync is always empty because it can't find $options['body'] also there it tries to set the headers which are empty, too $headers = $options['headers'] ?? [];
Besides this, currently the request to Melissa, even if the above is adjusted, returns GE08 (my API Key is actually allowed to do the request, we checked the config) so I wonder if the request has an additional problem somewhere.
I adjusted the code above like this, dunno is it's completely correct
            $request = $client->request(
                Request::HTTP_METHOD_POST,
                self::API_REQUEST_ENDPOINT,
                [
                    'headers' => [
                        'Accept' => 'application/json'
                    ],
                    'body' => json_encode($params)
                ]
            );

I allowed me to create a pull request for this
https://github.com/akitogo/MelissaAddressValidator/pull/3


[FIX] Updated get_ip to force a SCVMM refresh on VM first

Changes made with Amogh.  Tested using.
def test_get_ip_address():
vm_name = 'test_scvmm_vm'
sc = SCVMMSystem(**scvmm_args)
sc.start_vm(vm_name)
vm_getip = sc.get_ip_address(vm_name)
assert vm_getip == "<IP_ADDRESS>"

Coverage decreased (-0.02%) to 29.816% when pulling 277f75e5c5d807d06f90167bac4ee4197c48a185 on jteehan:scvmmgetip into e6bdf4f54eb5d1b4aef4352fb6f3fbd2efd584d5 on RedHatQE:master.

Lint report for commit 277f75e5c5d807d06f90167bac4ee4197c48a185:
Everything seems all right :smile: .
CFME QE Bot

Coverage decreased (-0.02%) to 29.816% when pulling 277f75e5c5d807d06f90167bac4ee4197c48a185 on jteehan:scvmmgetip into e6bdf4f54eb5d1b4aef4352fb6f3fbd2efd584d5 on RedHatQE:master.


Increasing Lambda limit for recording length

Hi there,
I need to increase the Lambda limit for a recording from the 15 minutes stated in your documentation to potentially 3 hours. I can see that the Lambda timeout can't be extended over 15 minutes though. Is there a way of sending a regular wake up to stop it timing out?
Kind regards
Phil

Hi Phil,
If you need the limit to last longer than 15 minutes you will need to use an EC2 instance or Fargate. Lambda cannot run longer than 15 minutes.


postfix.org website problems (not safe)

Dear Viktor,
There are several problems:

http://posftix.org/ does not work
https://posftix.org/ does not work
https://www.posftix.org/ does not work

Only http://www.posftix.org/ and it is not secure.
Can you solve it?
It will be better to have only and all other redirected to this address:

https://posftix.org/

To have for example:

http://postfix.org/announcements.html -> https://postfix.org/announcements.html
https://postfix.org/announcements.html -> https://postfix.org/announcements.html
https://www.postfix.org/announcements.html -> https://postfix.org/announcements.html

Dear Viktor,
Any news?

https://dropwww.com/why


Move to jupyterlab-contrib?

This extension can be useful to others.
For visibility and consistency with some other JupyterLab extensions, it would be nice to have it moved to https://github.com/jupyterlab-contrib.

Opened https://github.com/jupyterlab-contrib/jupyterlab-contrib.github.io/issues/79

Closing as the repo and packages have been moved.


Upgrade org.apache.commons:commons-compress to fix vuln

See CVE-2018-11771 https://nvd.nist.gov/vuln/detail/CVE-2018-11771.

Travis tests pass https://travis-ci.org/spotify/docker-client/builds/444703732?utm_source=github_status&utm_medium=notification. Not sure why they're still yellow here.


forgejo-lts: 7.0.9 -> 7.0.10

Release Notes: https://codeberg.org/forgejo/forgejo/milestone/8286

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

closed in favor of #351929


bug(material/datepicker): form state not correct with existing data

Reproduction
I use a date range picker with reactive forms. If I have an existing value that is bound to the start/end input, the form control will automatically turn dirty.
Here's a stackblitz: https://stackblitz.com/edit/angular-ai7kcs-mm7zyj?file=src/app/date-range-picker-forms-example.ts
Expected Behavior
The FormControl should be dirty=false.
Actual Behavior
dirty is always set to true after initialization.
Environment

Angular: 10.2.0
CDK/Material: 10.2.5
Browser(s): Chrome (latest stable)
Operating System (e.g. Windows, macOS, Ubuntu): Windows 10

Duplicate of https://github.com/angular/components/issues/20213.


Docs: Small addition to Raidboss readme

I'm so sorry, that bit about handling the response element didn't actually make it in, I was assuming it was still in question. This actually adds it, as well as localizing the tts element.

Whoops, sorry for misreading that comment on the other pull request.  Thanks for the followup.


TC08 short pointers?

Just a quick question because I'm unsure of how the driver is implemented below the wrapper: the C# wrapper for the TC08 uses a short as a file handle, but wouldn't an IntPtr or SafeHandle be what a .NET developer would expect to see?

Hi @InvisibleWaves, thanks for your question. The driver uses a signed 16-bit integer for the handle parameter so we have used a short. Here is the definition from the C header file for the driver:
PREF0 PREF1 int16_t PREF2 PREF3(usb_tc08_open_unit) (   void );
You could use short or Int16.
Hope this helps.


Add support for GitHub Actions artifact publishing

Would be good if backfill had config for GH Actions. I imagine it would leverage something along the lines of artifacts. I can take a deeper look into it when I have time.

Awesome! Happy to provide support if you have a proposal.


Fix maven repository (error 500)

The recommended maven repository in the Wiki is broken. It gives a 500 error code.
Expected Behavior

The maven repository should be up and running fine, delivering CraftStudioApi's artifacts.
Current Behavior

Browsing http://maven.leviathan-studio.com/artifactory/leviathan/com/leviathanstudio/CraftStudio/ gives this JSON response :
{
  "errors" : [ {
    "status" : 500,
    "message" : "HTTP response status 500:Failed on executing /api/v1/auth/login, with response: {\n  \"errors\" : [ {\n    \"code\" : \"INTERNAL_SERVER_ERROR\",\n    \"message\" : \"Could not update login details for user 'anonymous'\",\n    \"detail\" : \"An SQL data change is not permitted for a read-only connection, user or database.\"\n  } ]\n}"
  } ]
}

Using the provided build.gradle dependency code doesn't resolve it.
Possible Solution

An alternative could be recommanding the use of the jitpack.io maven repository.
(See https://jitpack.io/#Leviathan-Studio/CraftStudioAPI)

Steps to Reproduce

Just follow https://github.com/Leviathan-Studio/CraftStudioAPI/wiki/Add-the-API-to-your-project

Your Environment

Version of the api used: <IP_ADDRESS>-mc1.11.2-beta-dev
Version of forge used: 1.12.2-<IP_ADDRESS>11

Hi !
 :)
And thank you for the issue.
You can come on the discord, if you want to directly interact with the staff or other people !

I fix the maven but I'm looking for an other solution. Free to you to propose some.


DBZ-491 Asserting offsets as per the given time and timezone (instead…

… of now)
Follow-up to https://issues.jboss.org/browse/DBZ-491 as per https://groups.google.com/forum/#!topic/debezium/vVr0rdoVzis.

Applied - thanks!


Allow for searching notifications and filtering by type, sender and sorting by date in inbox

In the inbox page, we need to allow users to search through their notification using words that match the messages body of the notification. They should also be able to filter their inbox according to sender and type as well as sort by date from most to least recent and vice versa

Closing Statement: We are closing this issue even though it only allows for the first half of the title. The PR allows for users to search for notifications using the universal search bar. The results are displayed using search_results.html rather than user_inbox.html and so filtering can be handled in a future issue. Both developers worked on all parts of the issue.

Issue Score: Satisfactory
Comments:
Lacking updates for a pretty big PR. Otherwise, great work!


Set up before

Hi, It me the pain in the butt again  😂. Im wondering (even though this is vaguely related to your project) how I can setup the purchases. I'm almost ready to submit my app for review and then I'll send you the link but I would like to incorporate iap to remove ads. Could I please have some help?

Read this tutorial. Its in swift, and teaches you in app purchases in a nice and reusable way. https://www.raywenderlich.com/122144/in-app-purchase-tutorial

You cannot rush in app purchases, you will have to test a lot.

Thanks Ill check it out, and yea I've learned over the past week or so with slight little changes there is a lot of testing.

Yeah, you really have to take your time with in app purchases. Also I would suggest you skip receipt validation for now and just focus on in app purchases.

I did some work on iap and figured it out some what. Now I'm having issues w this: http://stackoverflow.com/questions/39906748/present-view-swift-3

I answered your question. Hope this helps


Add javadoc & source jars

#609

Codecov Report

Merging #724 into master will not change coverage.
The diff coverage is n/a.


Make tasks sorted by priority

If I complete #8 then I will do this too then.

Simply have multiple loops when assembling the DOM...except that won't handle new things properly...


Fix: Drop support for PHP 7.1

This PR

[x] drops support for PHP 7.1

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@eb3df30). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             master     #8   +/-   ##
=======================================
  Coverage          ?   100%
  Complexity        ?      6
=======================================
  Files             ?      2
  Lines             ?     21
  Branches          ?      0
=======================================
  Hits              ?     21
  Misses            ?      0
  Partials          ?      0

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 eb3df30...f092a9d. Read the comment docs.


Use virtualAttributes for GraphQL schema

Hi there,
I can't find any way to get around the following.
I've got a Model ("Exchange") with a db column ("name") and a virtual attribute ("marketCount"):
class Exchange extends Model {
  static get tableName () {
    return 'exchanges';
  }

  static get virtualAttributes() {
    return ['marketCount'];
  }

  static get jsonSchema () {
    return {
      type: 'object',
      required: ['name'],
      properties: {
        id: {type: 'integer'},
        name: {type: 'string'},
        // marketCount: {type: 'number' }
      }
    };
  }

  marketCount () {
    return 1;
  }
}

When defining "marketCount" in jsonSchema properties it tries to select the column from the db, which of course doesn't exist and when leaving it out it isn't available in the GraphQL Schema, so the query fails.
I find it hard to believe this wouldn't be possible but didn't find the answer either.
Anything I don't know of?

Hi @timbaas .  This library utilizes Objection Model JSON schema to generate GraphQL fields. On the other hand, as you mentioned, if the field is a part of the schema it is supposed to exist in the db. So, virtual attributes are not supported yet, but I think it's worth implementing in the future.

I just submitted a pull request which should facilitate this need: https://github.com/Vincit/objection-graphql/pull/53

@timhuff why was PR #55 reverted?  Is there another way to handle virtual attributes?

Ignore... I found PR #57


Already patched devices will be ignored. Added mod blacklist. Updated logging

Thank you for the PR!
I'm guessing that you've tested all of the above changes, so this is pretty much good to go (aside from my one nitpick).


logging using {N} trace

I ended up merging one that uses functions eg log.debug(()=>some string ${expensiveOp()})
thanks for the PR though! 👍


Expand configuration options for rtc_retain_mem_t (IDFGH-6857)

Increases the maximum size of custom RTC reserved memory to 0x1000

The existing maximum of 0x10 is too low to implement anything non-trivial
0x1000 is arbitrary but much larger, covering many more use cases

Allows selecting memory block (Fast/Slow) for RTC reserved memory

RTC fast memory has access limitations
Slow memory may be more available depending on application requirements

I've had a look into linker scripts today and I think this can be reliably achieved without these changes being necessary.
I understand this is an uncommon case so please feel free to close this in favour of that approach.
I've included my solution below.

Pieced together using IDF as a reference, this ensures the last 512 bytes of RTC slow memory is unused for custom purposes.
CMakeLists.txt:
idf_component_register(...)

set(ld_input "${CMAKE_CURRENT_LIST_DIR}/rtc_slow_retain.ld.in")
set(ld_output "${CMAKE_CURRENT_BINARY_DIR}/rtc_slow_retain.ld")
target_linker_script(${COMPONENT_LIB} INTERFACE "${ld_output}")

# Preprocess rtc_slow_retain.ld.in linker script, becomes rtc_slow_retain.ld
idf_build_get_property(config_dir CONFIG_DIR)
add_custom_command(
    OUTPUT ${ld_output}
    COMMAND "${CMAKE_C_COMPILER}" -C -P -x c -E -o ${ld_output} -I ${config_dir} ${ld_input}
    MAIN_DEPENDENCY ${ld_input}
    DEPENDS ${sdkconfig_header}
    COMMENT "Generating rtc_slow_retain.ld linker script..."
    VERBATIM)

add_custom_target(rtc_slow_retain_ld DEPENDS ${ld_output})
add_dependencies(${COMPONENT_LIB} rtc_slow_retain_ld)

rtc_slow_retain.ld.in:
#include "sdkconfig.h"

ASSERT(
    (_rtc_force_slow_end <= (0x50002000 - CONFIG_CUSTOM_RETAIN_MEM_SIZE)),
    "RTC slow memory usage overlaps reserved memory"
)

Kconfig:
config CUSTOM_RETAIN_MEM_SIZE
    int
    default 512

.h/.c:
#include "sdkconfig.h"

typedef struct {
    uint8_t mydata[508];
    uint32_t crc;
} my_custom_retain_mem_t;

_Static_assert(sizeof(my_custom_retain_mem_t) == CONFIG_CUSTOM_RETAIN_MEM_SIZE, "RTC retain mem size mismatch");

#define MY_CUSTOM_RETAIN_MEM_ADDR (SOC_RTC_DATA_HIGH - sizeof(my_custom_retain_mem_t))
// etc etc...

Hi @boarchuz ,
You may want to check commit https://github.com/espressif/esp-idf/commit/779d880580a3ae90d27a47ca712540e32f62b320 . It lifted the 0x10 bytes restrictions on the user's custom RTC data.
You will be able to access this array from both the bootlaoder and the application thanks to:
    rtc_retain_mem_t* mem = bootloader_common_get_rtc_retain_mem();
    // mem->custom is the user's usable array in RTC

@o-marshmallow Thankyou!


CSS Styling

Added a simple CSS for styling and optimized the look of things to feel somewhat more polished and professional, at least to my eyes.

Contrary to the merge message, please use issue #44 for feedback and suggestions.


Please provide some code samples how to use it in reality.

Type of issue
Typo
Description
[Enter feedback here]
Page URL
https://learn.microsoft.com/en-us/dotnet/api/microsoft.entityframeworkcore.design.designtimeservicecollectionextensions.addentityframeworkdesigntimeservices?view=efcore-8.0
Content source URL
https://github.com/dotnet/EntityFramework.ApiDocs/blob/live/dotnet/xml/Microsoft.EntityFrameworkCore.Design/DesignTimeServiceCollectionExtensions.xml
Document Version Independent Id
d9473c7d-9660-8f76-1b59-25ddac8a2c41
Article author
@dotnet-bot

@Esterl-Christian See https://learn.microsoft.com/en-us/ef/core/cli/services


Publish docker image during release

Pull Request Test Coverage Report for Build 9db44799c14229054c785d26abb214bace8fb77b-PR-981

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 68.075%

Totals

Change from base Build 820abe170c4ba692b369696d2ac05b582130cac9:
0.0%

Covered Lines:
1096

Relevant Lines:
1610

💛  - Coveralls


Is any way for a provider to invoke consumer or this is not possible?

Hello all i have a simple question i want the provider to publish a message in all the subscribed consumers is this possbile? A simple solution would be for the provider to play both role of consumer and provider in order to invoke the exposed api but are there any other smart solution to my case where a provider can send first a message and invoke the consumer? is the opposite thing possible?

You can use triple to build a observer stream or use dubbo callback https://dubbo.apache.org/en/docs/v2.7/user/examples/callback-parameter/.


Implement Edit mode

It should be possible to select vessels so that user can:

[ ] delete
[ ] split See #14
[ ] join (low priority)
[ ] edit color. See #76
[ ] mark vessel as root (you can have more than one root)
[ ] smooth vessel
[ ] generate tree
[ ] propagate properties

For the selection, vessel can be selected either in 2D or 3D view:

[ ] 2D selection  (high priority)
[ ] 3D selection  (low priority)

Edit mode must be the default view, with a big text saying "Hold Ctrl down to select vessels for extraction"
When Ctrl is pressed down, the left panel should change to Extract mode, with possibility to:

[ ] choose the radius of the extraction
[ ] click in the views, and add the points clicked to the list of seeds
[ ] add a color picker to pick the color of the tubes that will be extracted

#74 : Clean GUI in Extract Mode

[] Hide the following buttons by default (under and advanced tab):
Seed Point
Parameter File
Seed displayed size
Seed status

[] Seed status should be off by default


RTL support in web UI

Does the frontend of the app support RTL so that all components are moved from right to left, or should it be done manually in CSS?

We mainly support RTL in the individual text areas; it's a lot of complexity to make the rest of the layout do RTL, and we've not had time to invest in that.

For cross-reference, the issue thread several years ago that led to RTL support for the content within messages was:

#3123


Add GitHub action to run unit tests on push, PR, and on demand

Automatically runs unit tests on push, PR, and on demand

@grablair , would you have time to take a look?

Sorry I am out of town until the 26th. I can take an after-the-fact look when I am home.


unit test

Codecov Report

Merging #15 into master will increase coverage by 10.36%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           master      #15       +/-   ##
===========================================
+ Coverage   77.97%   88.34%   +10.36%
===========================================
  Files          17       17
  Lines         336      326       -10
  Branches       17       16        -1
===========================================
+ Hits          262      288       +26
+ Misses         69       35       -34
+ Partials        5        3        -2

Impacted Files
Coverage Δ

src/app/config/app.config.ts
81.81% <ø> (+4.04%)
:arrow_up:

...rc/app/em/em-annotation-summary-route.component.ts
100% <ø> (ø)

src/app/dm-listview/dm-listview.component.ts
77.35% <100%> (+7.86%)
:arrow_up:

src/app/app.module.ts
100% <100%> (ø)
:arrow_up:

src/app/auth/session.service.ts
87.87% <100%> (+0.78%)
:arrow_up:

src/app/dm-upload/dm-upload.component.ts
100% <100%> (+45.45%)
:arrow_up:

src/app/dm/document-store.service.ts
87.5% <0%> (+15.62%)
:arrow_up:

... and 1 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 bb78ead...18b824b. Read the comment docs.


recode: 3.7.12 -> 3.7.14

Description of changes
https://github.com/rrthomas/recode/blob/v3.7.14/NEWS
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review run on x86_64-linux 1

9 packages built:

bombono
ding
enca
fancy-motd
fortune
gtypist
plowshare
recode
xcowsay

Rebased.
Result of nixpkgs-review pr 268597 run on x86_64-linux 1

9 packages built:

bombono
ding
enca
fancy-motd
fortune
gtypist
plowshare
recode
xcowsay

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/3217

Result of nixpkgs-review pr 268597 run on x86_64-linux 1

9 packages built:

bombono
ding
enca
fancy-motd
fortune
gtypist
plowshare
recode
xcowsay