Uncompletable tasks in the sync plugin should not get a checkbox

When rendering from a query, some task titles returned are:
* Deadline on XYZ
This gets to be rendered as;

[ ] * Deadline on XYZ

But to Todoist it is an not completable task, so it would be great of your fantastic sync plugin would honor that 👍
Keep up the good work!

Hey @jorgb, the input elements for uncompletable tasks will be disabled in v1.7.0!

Hey @jorgb, the input elements for uncompletable tasks will be disabled in v1.7.0!

That's awesome news, thanks!
On Sun, 24 Jan 2021 at 17:19, Jamie Brynes<EMAIL_ADDRESS>wrote:

Hey @jorgb https://github.com/jorgb, the input elements for
uncompletable tasks will be disabled in v1.7.0
https://github.com/jamiebrynes7/obsidian-todoist-plugin/releases/tag/1.7.0
!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jamiebrynes7/obsidian-todoist-plugin/issues/69#issuecomment-766378752,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA23JW275DNYAIEXJ7M53G3S3RB7ZANCNFSM4UDR6D3Q
.

That's awesome news, thanks!
On Sun, 24 Jan 2021 at 17:19, Jamie Brynes<EMAIL_ADDRESS>wrote:

Hey @jorgb https://github.com/jorgb, the input elements for
uncompletable tasks will be disabled in v1.7.0
https://github.com/jamiebrynes7/obsidian-todoist-plugin/releases/tag/1.7.0
!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jamiebrynes7/obsidian-todoist-plugin/issues/69#issuecomment-766378752,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA23JW275DNYAIEXJ7M53G3S3RB7ZANCNFSM4UDR6D3Q
.


bukubrow: 5.0.0 -> 5.4.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/SamHH/bukubrow-host/releases.
meta.description for bukubrow is: "A WebExtension for Buku, a command-line bookmark manager"
meta.homepage for bukubrow is: "https://github.com/SamHH/bukubrow-host"
meta.changelog for bukubrow is: ""
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.4.0 with grep in /nix/store/alnazpnawasgv4wfb5j84kx3cjn9d6lx-bukubrow-host-5.4.0
found 5.4.0 in filename of file in /nix/store/alnazpnawasgv4wfb5j84kx3cjn9d6lx-bukubrow-host-5.4.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
bukubrow

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/alnazpnawasgv4wfb5j84kx3cjn9d6lx-bukubrow-host-5.4.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A bukubrow https://github.com/r-ryantm/nixpkgs/archive/2b92abdd337f79bd53222f53201cc7278bc98b30.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/alnazpnawasgv4wfb5j84kx3cjn9d6lx-bukubrow-host-5.4.0
ls -la /nix/store/alnazpnawasgv4wfb5j84kx3cjn9d6lx-bukubrow-host-5.4.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

bukubrow

Maintainer pings
cc @infinisil for testing.

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

1 package built:

bukubrow


chore: removed GitHub pages deployment

Closes #2455

Summary

PR now deploy docs to Vercel
Removed all related GitHub pages from the release

Checklist

[ ] I added — tests to prove my changes
[ ] I updated — all the necessary docs
[X] I reviewed — the entire PR myself, using the GitHub UI
[ ] I described — all breaking changes and the Migration Guide

I've had to disable to the build cache in Vercel via the env VERCEL_FORCE_NO_BUILD_CACHE=1 due to the error below.

See error
```
[09:42:57.535] Running build in Portland, USA (West) – pdx1
[09:42:57.627] Cloning github.com/FuelLabs/fuels-ts (Branch: ps/chore/add-preview-links-for-docs, Commit: 0802a29)
[09:42:58.627] Cloning completed: 999.651ms
[09:43:15.814] Restored build cache
[09:43:15.898] Running "vercel build"
[09:43:16.654] Vercel CLI 34.3.0
[09:43:16.799] > Detected Turbo. Adjusting default settings...
[09:43:17.399] Detected `pnpm-lock.yaml` version 9 generated by pnpm 9
[09:43:17.400] Running "install" command: `pnpm install`...
[09:43:18.114] Scope: all 38 workspace projects
[09:43:24.650]
[09:43:24.651] ../../internal/tsup preinstall$ pnpm build
[09:43:24.663] ../../internal/fuel-core install$ node ./lib/install.js
[09:43:24.663] ../../internal/forc install$ node ./lib/install.js
[09:43:25.165] ../../internal/tsup preinstall: > @internal/tsup@ build /vercel/path0/internal/tsup
[09:43:25.166] ../../internal/tsup preinstall: > tsup
[09:43:25.264] ../../internal/fuel-core install: (node:189) [node-fetch#buffer] DeprecationWarning: Please use 'response.arrayBuffer()' instead of 'response.buffer()'
[09:43:25.265] ../../internal/fuel-core install: (Use `node --trace-deprecation ...` to show where the warning was created)
[09:43:25.318] ../../internal/forc install: (node:195) [node-fetch#buffer] DeprecationWarning: Please use 'response.arrayBuffer()' instead of 'response.buffer()'
[09:43:25.319] ../../internal/forc install: (Use `node --trace-deprecation ...` to show where the warning was created)
[09:43:25.442] ../../internal/tsup preinstall: CLI Building entry: src/index.ts
[09:43:25.443] ../../internal/tsup preinstall: CLI Using tsconfig: tsconfig.json
[09:43:25.444] ../../internal/tsup preinstall: CLI tsup v6.7.0
[09:43:25.445] ../../internal/tsup preinstall: CLI Using tsup config: /vercel/path0/internal/tsup/tsup.config.ts
[09:43:25.448] ../../internal/tsup preinstall: CLI Target: es2022
[09:43:25.451] ../../internal/tsup preinstall: CLI Cleaning output folder
[09:43:25.452] ../../internal/tsup preinstall: CJS Build start
[09:43:25.453] ../../internal/tsup preinstall: ESM Build start
[09:43:25.453] ../../internal/tsup preinstall: IIFE Build start
[09:43:25.477] ../../internal/tsup preinstall: IIFE dist/index.global.js     734.00 B
[09:43:25.478] ../../internal/tsup preinstall: IIFE dist/index.global.js.map 1.56 KB
[09:43:25.480] ../../internal/tsup preinstall: IIFE ⚡ Build success in 25ms
[09:43:25.480] ../../internal/tsup preinstall: ESM dist/index.mjs     717.00 B
[09:43:25.480] ../../internal/tsup preinstall: ESM dist/index.mjs.map 1.54 KB
[09:43:25.481] ../../internal/tsup preinstall: ESM ⚡ Build success in 26ms
[09:43:25.481] ../../internal/tsup preinstall: CJS dist/index.js     1.83 KB
[09:43:25.481] ../../internal/tsup preinstall: CJS dist/index.js.map 1.60 KB
[09:43:25.482] ../../internal/tsup preinstall: CJS ⚡ Build success in 28ms
[09:43:25.495] ../../internal/tsup preinstall: > @internal/tsup@ postbuild /vercel/path0/internal/tsup
[09:43:25.496] ../../internal/tsup preinstall: > tsx ../../scripts/postbuild.ts
[09:43:26.620] ../../internal/fuel-core install: Done
[09:43:28.033] ../../internal/tsup preinstall: Done
[09:43:30.419] ../../internal/forc install: Done
[09:43:32.700] Done in 15.2s
[09:43:35.298]
[09:43:35.298] ><EMAIL_ADDRESS>build /vercel/path0
[09:43:35.298] > turbo run build --cache-dir=.turbo
[09:43:35.298]
[09:43:35.356]
[09:43:35.356] Attention:
[09:43:35.356] Turborepo now collects completely anonymous telemetry regarding usage.
[09:43:35.356] This information is used to shape the Turborepo roadmap and prioritize features.
[09:43:35.356] You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
[09:43:35.356] https://turbo.build/repo/docs/telemetry
[09:43:35.356]
[09:43:35.483] • Packages in scope: @fuel-ts/abi-coder, @fuel-ts/abi-typegen, @fuel-ts/account, @fuel-ts/address, @fuel-ts/contract, @fuel-ts/crypto, @fuel-ts/docs-snippets, @fuel-ts/errors, @fuel-ts/hasher, @fuel-ts/interfaces, @fuel-ts/logger, @fuel-ts/math, @fuel-ts/merkle, @fuel-ts/program, @fuel-ts/script, @fuel-ts/transactions, @fuel-ts/utils, @fuel-ts/versions, @internal/check-imports, @internal/check-tests, @internal/forc, @internal/fuel-core, @internal/tsup, create-fuels, create-fuels-counter-guide, demo-bun-fuels, demo-fuels, demo-nextjs, demo-node-esm, demo-react-cra, demo-react-vite, demo-typegen, demo-wallet-sdk-react, docs, fuel-gauge, fuels, template-nextjs
[09:43:35.484] • Running build in 37 packages
[09:43:35.484] • Remote caching enabled
[09:43:36.107] @internal/check-tests:build: cache hit, suppressing logs 49ff493fe11dd047
[09:43:36.141] @fuel-ts/interfaces:build: cache hit, suppressing logs ed51835f623ec00e
[09:43:36.307] @internal/tsup:preinstall: cache hit, suppressing logs 75e85a0d240d064c
[09:43:36.349] @fuel-ts/versions:prebuild: cache hit, suppressing logs 363f6dcf3595eb85
[09:43:36.545] @internal/tsup:build: cache hit, suppressing logs e9d7aeea89e3a55a
[09:43:36.605] @fuel-ts/versions:build: cache hit, suppressing logs 62b1f19b059504aa
[09:43:36.628] @fuel-ts/account:prebuild: cache hit, suppressing logs e6a5e8bef02d974f
[09:43:36.818] @fuel-ts/errors:build: cache hit, suppressing logs 37473d46ded7c815
[09:43:37.225] create-fuels:build: cache hit, suppressing logs 9777b0d6bee63201
[09:43:37.277] @fuel-ts/math:build: cache hit, suppressing logs bcb2a78e73968437
[09:43:37.684] @fuel-ts/utils:build: cache hit, suppressing logs 766e41d9fa17f132
[09:43:37.900] @fuel-ts/crypto:build: cache hit, suppressing logs d7d7eac2d1eff581
[09:43:38.287] @fuel-ts/abi-typegen:build: cache hit, suppressing logs 5e0d0f57ddd938de
[09:43:38.296] @fuel-ts/address:build: cache hit, suppressing logs 6c20db76099bfd2d
[09:43:38.674] @fuel-ts/hasher:build: cache hit, suppressing logs 896f3f213449cfef
[09:43:38.783] @fuel-ts/logger:build: cache hit, suppressing logs a02ec0ba69bf430e
[09:43:39.176] @fuel-ts/abi-coder:build: cache hit, suppressing logs 73b06753afc1521f
[09:43:39.332] @fuel-ts/merkle:build: cache hit, suppressing logs a4deded848d4c59d
[09:43:39.548] @fuel-ts/transactions:build: cache hit, suppressing logs 92a001ad8d1c56c4
[09:43:40.224] @fuel-ts/account:build: cache hit, suppressing logs 06c99df2bde5510d
[09:43:40.569] @fuel-ts/program:build: cache hit, suppressing logs 3cd9b544fbf9d2b1
[09:43:40.925] @fuel-ts/script:build: cache hit, suppressing logs ec998f0cfdcd6a8c
[09:43:41.195] @fuel-ts/contract:build: cache hit, suppressing logs ab430b47d0371edb
[09:43:42.243] fuels:build: cache hit, suppressing logs bf849bbbf518d532
[09:43:42.480] demo-wallet-sdk-react:build: cache hit, suppressing logs d87f3f6e80c5ee95
[09:43:42.538] docs:build: cache miss, executing 5865ae46df3bc3b4
[09:43:42.607] @internal/check-imports:build: cache hit, suppressing logs b8ca2af633e06f77
[09:43:42.641] template-nextjs:build: cache hit, suppressing logs 1219b85061eceb4a
[09:43:43.007] docs:build:
[09:43:43.007] docs:build: ><EMAIL_ADDRESS>build /vercel/path0/apps/docs
[09:43:43.007] docs:build: > pnpm run docs && vitepress build
[09:43:43.007] docs:build:
[09:43:43.464] docs:build:
[09:43:43.464] docs:build: ><EMAIL_ADDRESS>docs /vercel/path0/apps/docs
[09:43:43.464] docs:build: > typedoc && tsx ./scripts/typedoc-postbuild.ts
[09:43:43.464] docs:build:
[09:43:43.928] docs:build: [info] Loaded plugin typedoc-plugin-markdown
[09:43:43.932] docs:build: [info] Loaded plugin typedoc-plugin-merge-modules
[09:43:43.939] docs:build: [warning] The entrypoint glob /vercel/path0/packages/predicate did not match any directories containing package.json.
[09:43:43.981] docs:build: [info] Converting project at /vercel/path0/packages/address
[09:43:45.202] docs:build: [warning] The provided git remote "origin" was not valid. Source links will be broken.
[09:43:45.204] docs:build: [warning] The signature Address.fromDynamicInput has an @param with name "addressId", which was not used.
[09:43:45.212] docs:build: [info] Converting project at /vercel/path0/packages/interfaces
[09:43:45.840] docs:build: [info] Converting project at /vercel/path0/packages/account
[09:43:49.325] docs:build: ../../packages/account/src/providers/message.ts:4:38 - error TS2307: Cannot find module './__generated__/operations' or its corresponding type declarations.
[09:43:49.325] docs:build:
[09:43:49.326] docs:build: 4 import type { GqlMessageState } from './__generated__/operations';
[09:43:49.326] docs:build:                                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[09:43:49.326] docs:build:
[09:43:49.326] docs:build: ../../packages/account/src/providers/provider.ts:22:44 - error TS2307: Cannot find module './__generated__/operations' or its corresponding type declarations.
[09:43:49.326] docs:build:
[09:43:49.326] docs:build: 22 import { getSdk as getOperationsSdk } from './__generated__/operations';
[09:43:49.326] docs:build:                                               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[09:43:49.326] docs:build:
[09:43:49.326] docs:build: ../../packages/account/src/providers/provider.ts:37:8 - error TS2307: Cannot find module './__generated__/operations' or its corresponding type declarations.
[09:43:49.326] docs:build:
[09:43:49.326] docs:build: 37 } from './__generated__/operations';
[09:43:49.326] docs:build:           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[09:43:49.326] docs:build:
[09:43:49.326] docs:build: ../../packages/account/src/providers/provider.ts:265:51 - error TS7006: Parameter 'i' implicitly has an 'any' type.
[09:43:49.326] docs:build:
[09:43:49.326] docs:build: 265       transactions: latestBlock.transactions.map((i) => ({
[09:43:49.326] docs:build:                                                       ~
[09:43:49.326] docs:build:
[09:43:49.326] docs:build: ../../packages/account/src/providers/provider.ts:603:5 - error TS2578: Unused '@ts-expect-error' directive.
[09:43:49.326] docs:build:
[09:43:49.326] docs:build: 603     // @ts-expect-error This is due to this function being generic. Its type is specified when calling a specific operation via provider.operations.xyz.
[09:43:49.326] docs:build:         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[09:43:49.326] docs:build:
[09:43:49.327] docs:build: ../../packages/account/src/providers/provider.ts:822:23 - error TS7006: Parameter 'input' implicitly has an 'any' type.
[09:43:49.327] docs:build:
[09:43:49.327] docs:build: 822       inputs.forEach((input, index) => {
[09:43:49.327] docs:build:                           ~~~~~
[09:43:49.327] docs:build:
[09:43:49.327] docs:build: ../../packages/account/src/providers/provider.ts:822:30 - error TS7006: Parameter 'index' implicitly has an 'any' type.
[09:43:49.327] docs:build:
[09:43:49.327] docs:build: 822       inputs.forEach((input, index) => {
[09:43:49.327] docs:build:                                  ~~~~~
[09:43:49.327] docs:build:
[09:43:49.327] docs:build: ../../packages/account/src/providers/provider.ts:1007:53 - error TS7031: Binding element 'rawReceipts' implicitly has an 'any' type.
[09:43:49.327] docs:build:
[09:43:49.327] docs:build: 1007     const results = dryRunStatuses.map(({ receipts: rawReceipts, status }) => {
[09:43:49.327] docs:build:                                                          ~~~~~~~~~~~
[09:43:49.327] docs:build:
[09:43:49.327] docs:build: ../../packages/account/src/providers/provider.ts:1007:66 - error TS7031: Binding element 'status' implicitly has an 'any' type.
[09:43:49.327] docs:build:
[09:43:49.327] docs:build: 1007     const results = dryRunStatuses.map(({ receipts: rawReceipts, status }) => {
[09:43:49.327] docs:build:                                                                       ~~~~~~
[09:43:49.327] docs:build:
[09:43:49.327] docs:build: ../../packages/account/src/providers/provider.ts:1111:44 - error TS7006: Parameter 'dryRunStatus' implicitly has an 'any' type.
[09:43:49.327] docs:build:
[09:43:49.327] docs:build: 1111     const callResult = dryRunStatuses.map((dryRunStatus) => {
[09:43:49.327] docs:build:                                                 ~~~~~~~~~~~~
[09:43:49.328] docs:build:
[09:43:49.328] docs:build: ../../packages/account/src/providers/provider.ts:1300:32 - error TS7031: Binding element 'node' implicitly has an 'any' type.
[09:43:49.328] docs:build:
[09:43:49.328] docs:build: 1300     const coins = edges.map(({ node }) => ({
[09:43:49.328] docs:build:                                     ~~~~
[09:43:49.328] docs:build:
[09:43:49.328] docs:build: ../../packages/account/src/providers/provider.ts:1356:13 - error TS7006: Parameter 'coin' implicitly has an 'any' type.
[09:43:49.328] docs:build:
[09:43:49.328] docs:build: 1356       .map((coin) => {
[09:43:49.328] docs:build:                  ~~~~
[09:43:49.328] docs:build:
[09:43:49.328] docs:build: ../../packages/account/src/providers/provider.ts:1380:16 - error TS7006: Parameter 'v' implicitly has an 'any' type.
[09:43:49.328] docs:build:
[09:43:49.328] docs:build: 1380       .filter((v) => !!v) as Array<Resource>;
[09:43:49.328] docs:build:                     ~
[09:43:49.328] docs:build:
[09:43:49.328] docs:build: ../../packages/account/src/providers/provider.ts:1413:47 - error TS7006: Parameter 'tx' implicitly has an 'any' type.
[09:43:49.328] docs:build:
[09:43:49.328] docs:build: 1413       transactionIds: block.transactions.map((tx) => tx.id),
[09:43:49.328] docs:build:                                                    ~~
[09:43:49.328] docs:build:
[09:43:49.328] docs:build: ../../packages/account/src/providers/provider.ts:1433:48 - error TS7031: Binding element 'block' implicitly has an 'any' type.
[09:43:49.328] docs:build:
[09:43:49.328] docs:build: 1433     const blocks: Block[] = edges.map(({ node: block }) => ({
[09:43:49.328] docs:build:                                                     ~~~~~
[09:43:49.329] docs:build:
[09:43:49.329] docs:build: ../../packages/account/src/providers/provider.ts:1437:47 - error TS7006: Parameter 'tx' implicitly has an 'any' type.
[09:43:49.329] docs:build:
[09:43:49.329] docs:build: 1437       transactionIds: block.transactions.map((tx) => tx.id),
[09:43:49.329] docs:build:                                                    ~~
[09:43:49.329] docs:build:
[09:43:49.329] docs:build: ../../packages/account/src/providers/provider.ts:1472:47 - error TS7006: Parameter 'tx' implicitly has an 'any' type.
[09:43:49.329] docs:build:
[09:43:49.329] docs:build: 1472       transactionIds: block.transactions.map((tx) => tx.id),
[09:43:49.329] docs:build:                                                    ~~
[09:43:49.329] docs:build:
[09:43:49.329] docs:build: ../../packages/account/src/providers/provider.ts:1474:10 - error TS7006: Parameter 'tx' implicitly has an 'any' type.
[09:43:49.329] docs:build:
[09:43:49.329] docs:build: 1474         (tx) => new TransactionCoder().decode(arrayify(tx.rawPayload), 0)?.[0]
[09:43:49.329] docs:build:               ~~
[09:43:49.329] docs:build:
[09:43:49.329] docs:build: ../../packages/account/src/providers/provider.ts:1510:18 - error TS7031: Binding element 'rawPayload' implicitly has an 'any' type.
[09:43:49.329] docs:build:
[09:43:49.329] docs:build: 1510       ({ node: { rawPayload } }) => coder.decode(arrayify(rawPayload), 0)[0]
[09:43:49.329] docs:build:                       ~~~~~~~~~~
[09:43:49.329] docs:build:
[09:43:49.329] docs:build: ../../packages/account/src/providers/provider.ts:1589:35 - error TS7031: Binding element 'node' implicitly has an 'any' type.
[09:43:49.338] docs:build:
[09:43:49.338] docs:build: 1589     const balances = edges.map(({ node }) => ({
[09:43:49.338] docs:build:                                        ~~~~
[09:43:49.338] docs:build:
[09:43:49.338] docs:build: ../../packages/account/src/providers/provider.ts:1618:35 - error TS7031: Binding element 'node' implicitly has an 'any' type.
[09:43:49.338] docs:build:
[09:43:49.338] docs:build: 1618     const messages = edges.map(({ node }) => ({
[09:43:49.338] docs:build:                                        ~~~~
[09:43:49.338] docs:build:
[09:43:49.338] docs:build: ../../packages/account/src/providers/transaction-request/create-transaction-request.ts:8:34 - error TS2307: Cannot find module '../__generated__/operations' or its corresponding type declarations.
[09:43:49.338] docs:build:
[09:43:49.338] docs:build: 8 import type { GqlGasCosts } from '../__generated__/operations';
[09:43:49.338] docs:build:                                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[09:43:49.338] docs:build:
[09:43:49.339] docs:build: ../../packages/account/src/providers/transaction-response/transaction-response.ts:23:41 - error TS2307: Cannot find module '../__generated__/operations' or its corresponding type declarations.
[09:43:49.339] docs:build:
[09:43:49.339] docs:build: 23 import type { GqlReceiptFragment } from '../__generated__/operations';
[09:43:49.339] docs:build:                                            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[09:43:49.339] docs:build:
[09:43:49.339] docs:build: ../../packages/account/src/providers/transaction-summary/calculate-tx-fee-for-summary.ts:7:39 - error TS2307: Cannot find module '../__generated__/operations' or its corresponding type declarations.
[09:43:49.339] docs:build:
[09:43:49.339] docs:build: 7 import type { GqlFeeParameters } from '../__generated__/operations';
[09:43:49.339] docs:build:                                         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[09:43:49.339] docs:build:
[09:43:49.339] docs:build: ../../packages/account/src/providers/transaction-summary/get-transaction-summary.ts:10:8 - error TS2307: Cannot find module '../__generated__/operations' or its corresponding type declarations.
[09:43:49.339] docs:build:
[09:43:49.339] docs:build: 10 } from '../__generated__/operations';
[09:43:49.339] docs:build:           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[09:43:49.339] docs:build:
[09:43:49.339] docs:build: ../../packages/account/src/providers/transaction-summary/get-transaction-summary.ts:160:35 - error TS7006: Parameter 'edge' implicitly has an 'any' type.
[09:43:49.339] docs:build:
[09:43:49.339] docs:build: 160   const transactions = edges.map((edge) => {
[09:43:49.339] docs:build:                                       ~~~~
[09:43:49.339] docs:build:
[09:43:49.340] docs:build: ../../packages/account/src/providers/transaction-summary/receipt.ts:3:41 - error TS2307: Cannot find module '../__generated__/operations' or its corresponding type declarations.
[09:43:49.340] docs:build:
[09:43:49.340] docs:build: 3 import type { GqlReceiptFragment } from '../__generated__/operations';
[09:43:49.340] docs:build:                                           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[09:43:49.340] docs:build:
[09:43:49.340] docs:build: ../../packages/account/src/providers/transaction-summary/types.ts:12:8 - error TS2307: Cannot find module '../__generated__/operations' or its corresponding type declarations.
[09:43:49.340] docs:build:
[09:43:49.340] docs:build: 12 } from '../__generated__/operations';
[09:43:49.340] docs:build:           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[09:43:49.340] docs:build:
[09:43:49.340] docs:build: ../../packages/account/src/providers/utils/gas.test.ts:13:59 - error TS2307: Cannot find module '../__generated__/operations' or its corresponding type declarations.
[09:43:49.340] docs:build:
[09:43:49.340] docs:build: 13 import type { GqlHeavyOperation, GqlLightOperation } from '../__generated__/operations';
[09:43:49.340] docs:build:                                                              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[09:43:49.340] docs:build:
[09:43:49.341] docs:build: ../../packages/account/src/providers/utils/gas.ts:10:8 - error TS2307: Cannot find module '../__generated__/operations' or its corresponding type declarations.
[09:43:49.341] docs:build:
[09:43:49.341] docs:build: 10 } from '../__generated__/operations';
[09:43:49.341] docs:build:           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[09:43:49.341] docs:build:
[09:43:49.341] docs:build: ../../packages/account/src/providers/utils/receipts.test.ts:24:32 - error TS2307: Cannot find module '../__generated__/operations' or its corresponding type declarations.
[09:43:49.341] docs:build:
[09:43:49.341] docs:build: 24 import { GqlReceiptType } from '../__generated__/operations';
[09:43:49.341] docs:build:                                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[09:43:49.342] docs:build:
[09:43:49.342] docs:build: ../../packages/account/src/providers/utils/receipts.ts:28:41 - error TS2307: Cannot find module '../__generated__/operations' or its corresponding type declarations.
[09:43:49.342] docs:build:
[09:43:49.342] docs:build: 28 import type { GqlReceiptFragment } from '../__generated__/operations';
[09:43:49.342] docs:build:                                            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[09:43:49.342] docs:build:
[09:43:49.342] docs:build: ../../packages/account/src/providers/utils/receipts.ts:29:32 - error TS2307: Cannot find module '../__generated__/operations' or its corresponding type declarations.
[09:43:49.342] docs:build:
[09:43:49.342] docs:build: 29 import { GqlReceiptType } from '../__generated__/operations';
[09:43:49.342] docs:build:                                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[09:43:49.342] docs:build:
[09:43:49.342] docs:build: ../../packages/account/test/fixtures/chain.ts:10:8 - error TS2307: Cannot find module '../../src/providers/__generated__/operations' or its corresponding type declarations.
[09:43:49.342] docs:build:
[09:43:49.342] docs:build: 10 } from '../../src/providers/__generated__/operations';
[09:43:49.342] docs:build:           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[09:43:49.342] docs:build:
[09:43:49.342] docs:build: ../../packages/account/test/fixtures/messageProof.ts:7:8 - error TS2307: Cannot find module '../../src/providers/__generated__/operations' or its corresponding type declarations.
[09:43:49.342] docs:build:
[09:43:49.342] docs:build: 7 } from '../../src/providers/__generated__/operations';
[09:43:49.342] docs:build:          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[09:43:49.342] docs:build:
[09:43:49.342] docs:build: ../../packages/account/test/fixtures/messageStatus.ts:4:8 - error TS2307: Cannot find module '../../src/providers/__generated__/operations' or its corresponding type declarations.
[09:43:49.342] docs:build:
[09:43:49.342] docs:build: 4 } from '../../src/providers/__generated__/operations';
[09:43:49.342] docs:build:          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[09:43:49.342] docs:build:
[09:43:49.343] docs:build: ../../packages/account/test/fixtures/nodeInfo.ts:1:42 - error TS2307: Cannot find module '../../src/providers/__generated__/operations' or its corresponding type declarations.
[09:43:49.343] docs:build:
[09:43:49.343] docs:build: 1 import type { GqlNodeInfoFragment } from '../../src/providers/__generated__/operations';
[09:43:49.343] docs:build:                                            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[09:43:49.343] docs:build:
[09:43:49.343] docs:build: ../../packages/account/test/fixtures/receipts.ts:1:41 - error TS2307: Cannot find module '../../src/providers/__generated__/operations' or its corresponding type declarations.
[09:43:49.343] docs:build:
[09:43:49.343] docs:build: 1 import type { GqlReceiptFragment } from '../../src/providers/__generated__/operations';
[09:43:49.343] docs:build:                                           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[09:43:49.345] docs:build:
[09:43:49.345] docs:build: ../../packages/account/test/fixtures/receipts.ts:2:32 - error TS2307: Cannot find module '../../src/providers/__generated__/operations' or its corresponding type declarations.
[09:43:49.345] docs:build:
[09:43:49.345] docs:build: 2 import { GqlReceiptType } from '../../src/providers/__generated__/operations';
[09:43:49.345] docs:build:                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[09:43:49.345] docs:build:
[09:43:49.346] docs:build: [info] Converting project at /vercel/path0/packages/program
[09:43:50.577] docs:build: [warning] The signature FunctionInvocationScope.getTransactionCost has an @param with name "options", which was not used.
[09:43:50.577] docs:build: [warning] The signature MultiCallInvocationScope.getTransactionCost has an @param with name "options", which was not used.
[09:43:50.584] docs:build: [warning] EncodedScriptCall, defined in /vercel/path0/packages/program/src/script-request.ts, is referenced by ScriptRequest.scriptDataEncoder.__type.__type but not included in the documentation.
[09:43:50.585] docs:build: [warning] ScriptResult, defined in /vercel/path0/packages/program/src/script-request.ts, is referenced by ScriptRequest.scriptResultDecoder.__type.__type.scriptResult but not included in the documentation.
[09:43:50.594] docs:build: [info] Converting project at /vercel/path0/packages/contract
[09:43:51.769] docs:build: [info] Converting project at /vercel/path0/packages/script
[09:43:52.636] docs:build: [warning] Result, defined in /vercel/path0/packages/script/src/script.ts, is referenced by Script.script but not included in the documentation.
[09:43:52.637] docs:build: [warning] InvokeMain, defined in /vercel/path0/packages/script/src/script.ts, is referenced by Script.functions.__type.main but not included in the documentation.
[09:43:52.637] docs:build: [info] Converting project at /vercel/path0/packages/utils
[09:43:52.638] docs:build: [warning] The entrypoint glob /vercel/path0/packages/utils/src/test-utils/index.ts did not match any files.
[09:43:53.575] docs:build: [warning] ChainConfig, defined in /vercel/path0/packages/utils/src/utils/types.ts, is referenced by SnapshotConfigs.chainConfig but not included in the documentation.
[09:43:53.575] docs:build: [warning] MetadataConfig, defined in /vercel/path0/packages/utils/src/utils/types.ts, is referenced by SnapshotConfigs.metadata but not included in the documentation.
[09:43:53.575] docs:build: [warning] StateConfig, defined in /vercel/path0/packages/utils/src/utils/types.ts, is referenced by SnapshotConfigs.stateConfig but not included in the documentation.
[09:43:53.579] docs:build: [info] Merging converted projects
[09:43:53.579] docs:build: [error] Failed to convert one or more packages, result will not be merged together.
[09:43:53.606] docs:build:  ELIFECYCLE  Command failed with exit code 3.
[09:43:53.619] docs:build:  ELIFECYCLE  Command failed with exit code 3.
[09:43:53.633] docs:build: ERROR: command finished with error: command (/vercel/path0/apps/docs) /pnpm9/node_modules/.bin/pnpm run build exited (3)
[09:43:53.634] docs#build: command (/vercel/path0/apps/docs) /pnpm9/node_modules/.bin/pnpm run build exited (3)
[09:43:53.637]
[09:43:53.637]   Tasks:    27 successful, 28 total
[09:43:53.637]  Cached:    27 cached, 28 total
[09:43:53.637]    Time:    18.268s
[09:43:53.637] Summary:    /vercel/path0/.turbo/runs/2jPccg3kENgSMHGFd1TrRlDlqz9.json
[09:43:53.637]  Failed:    docs#build
[09:43:53.637]
[09:43:53.645]  ERROR  run failed: command  exited (3)
[09:43:53.850]  ELIFECYCLE  Command failed with exit code 3.
[09:43:53.864] Error: Command "pnpm -w run build" exited with 3
[09:43:55.034]
```

Potentially related to a misconfigured turbo.json:

https://github.com/FuelLabs/fuels-ts/issues/1753


return undefined instead of null

Improvement
the default returnValue of data at least in useQuery should be undefined instead of null
if you return undefined then you can make use of set default values as shown below
 const { data = [] } = useQuery(
    'TrendingShows',
    loadTrendingShows
  );

I agreed with your recommendation. But as a workaround for now, you can use the initialData prop as described here to set your data to an empty array for example
https://github.com/tannerlinsley/react-query#ssr--initial-data

This will be fixed in the next release 🎉


Develcheck

Added -d option to support devel packages using an AUR helper (paru, yay...).
Optional, default is disable.
aurhelper variable line 16 need to point to the desired AUR Helper.

To be honest I didn't know about devel packages. I though Arch has combined packages where you can find both headers and binary libraries. Correct me if I am wrong!
Also want to highlight, that I tried to make waybar-updates AUR Helper-agnostic. Otherwise we will need to add support for all most popular AUR helpers. In that case we will probably need to write a better script using Python/Go (for the sake of simplicity).

Overall, I am okay to merge it in perspective, but after extensive tests from you.


Korean: FKR050

In https://github.com/lcnetdev/scriptshifter/blob/korean/scriptshifter/hooks/korean/Functions_KoreanRomanizer.au3#L1169-L1171:
   If StringRegExp($NClipB," 제[0-9]") Then
	  $NClipB = StringReplace($NClipB," 제"," 제 ")
   EndIf

Is the intent of this code to replace every instance of 제 followed by a digit with 제 ? In that case it seems to me that this may not yield the expected results, because as long as there is at least one occurrence of 제 followed by a digit, a space will be added to all 제 in the text, regardless of what follows them.
In Python I'm proposing a regex substitution:
data = re.sub(" 제([0-9])", "제 \\1", data)

@hyoungl let me know if I am indeed interpreting this correctly.

This part is to insert a space between 제 and any number in Hangul before romanization takes place, when it refers to an ordinal number according to the Hangul orthography

Got it. OK, I'll use my regex solution then.


Can typia work with nuxt3?

Question
Hello!
I'm trying to use typia paired with nuxt3 for JSON validation, but I'm keep getting an error:
no transform has been configured. Read and follow https://typia.io/docs/setup please.

I run the project with pnpm run dev
code like this
interface Query {
  projectId: string
  pId?: string
}

function queryFn(params) {
  typia.validate<Query >(params)
}

queryFn({
  projectId: 'testId'
})

Is there any way to run typia with nuxt3?
P.S. “pnpm typia setup --manager pnpm” didn't help =)

Hi guys!
I made a plugin for bundlers
Check this out and plz give us a feedback!
https://typia.io/docs/setup/#unplugin-typia
Note that this plugin supports ts/tsx files only, so if you wan to use Typia for your nuxt project, define validation functions in .ts and then import them in .vue file


TFRS - Replace Modal.js with React-Based Component in TFRS Project

Describe the task
The objective of this task is to address technical debt in the TFRS project by replacing the current Modal.js implementation, which relies on jQuery, with a React-based component. This will enable the removal of jQuery as a dependency, simplifying the codebase and modernizing the project.
Purpose
The purpose of this task is to improve the maintainability and consistency of the TFRS project by eliminating the need for jQuery and fully adopting React as the main UI library. This will result in a more efficient and streamlined development process while minimizing potential issues arising from using multiple libraries.
Acceptance Criteria

[ ] Identify all occurrences of Modal.js usage in the project.
[ ] Create a new React-based modal component that replicates the functionality of the current Modal.js implementation.
[ ] Replace all instances of Modal.js with the newly created React-based modal component.
[ ] Ensure that the new React-based modal component functions correctly and maintains the same behavior as the original Modal.js.
[ ] Test the updated modal implementation to confirm that it works as expected and does not introduce any new issues.
[ ] Remove jQuery as a dependency once all instances of Modal.js have been successfully replaced.
[ ] Update any relevant documentation to reflect the changes made to the modal implementation.

Additional context

Consider any potential impacts on performance and user experience when creating the new React-based modal component.

Development checklist:
A. Refactor Modal.js file to use React based component.
B. Replace all instance of Modal.js with the newly created modal component
C. Make sure it doesn't break existing Modal.js functionality.

Hey team! Please add your planning poker estimate with Zenhub @AlexZorkin @emi-hi @jig-patel @JulianForeman @tim738745

Please add your planning poker estimate with Zenhub @vibhiquartech

Not able to user test - card to be closed.


Fatal error during compilation

I'm having difficulties installing the plugin. I'm using Grails 2.2.3 and the exception I'm getting is:
Fatal error during compilation org.springframework.beans.factory.BeanDefinitionStoreException: Failed to read candidate component class: URL [jar:file:/Users/jeff/.grails/ivy-cache/org.grails/grails-hibernate/jars/grails-hibernate-2.2.3.jar!/org/codehaus/groovy/grails/compiler/gorm/GormTransformer.class]; nested exception is java.lang.NoClassDefFoundError: org/springframework/core/type/classreading/AnnotationMetadataReadingVisitor

Why not try Grails 2.4?
This plugin works in Grails 2.4.x


Update request: databricks-cli 0.18.0 → 0.223.1

Package name: databricks-cli
Latest released version: 0.223.1

Current version on the unstable channel: 0.18.0
Current version on the stable/release channel: 0.18.0

[x] Checked the nixpkgs pull requests

Notify maintainers
@symphorien , @fabaff , @mweinelt

Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

I'm not a maintainer of this package

I will pick this up.


Unexpected token '<'  and completely white screen

http://localhost:3000 shows a complete white screen. Nothing is displayed at all.
Developer console does display an Unexpected token '<'  error.
When browsing issues here I see that this Unexpected token '<'  error has been brought up several times already but none of the solution did do the trick for me.
What could be wrong in my set up?

I had this issue. You've forgotten to run webpack.


Allow to load test resources from files

With this commit we add a helper function load_test_resource that
evaluates caller context so we can automagically load JSON files with
data relevant for the current test.
Relates #734

@dliappis, @ebadyano, @hub-cap I've implemented a prototype that allows us to move dict-like test data (i.e. JSON) to dedicated files instead of defining them in the code. I am putting this here as a draft PR for early discussion about the approach and I'd like to hear your thoughts about it.

We've discussed this in our sync and we decided to keep the inline literal dicts so code and test data are closely linked. Hence I'm closing this PR.


Use Local Registries with Kind

See https://kind.sigs.k8s.io/docs/user/local-registry/
Running local registry script sets it up and Tilt detects/uses it, but on second run it doesn't seem to pick up the local registry.
Could give us a speed boost when dealing with images.

example:

scaf myproject
tilt up (images pulled into cluster's repository, not docker's)

this will create a cache cluster to prevent conflicts

quick fix: add patch in kubernetes kustomization
try: image registry setting in tilt (set to localhost:5000 so tilt will patch all requests through local registry)
see: https://docs.tilt.dev/personal_registry.html
long term: use k3s w/local registry to proxy image requests


Clean up Base user / password on temp sessions

Fixes #744.
If an app was set up using ShopifyAPI::Base.user/password, temp sessions wouldn't work properly because those values would be set for them as well, which might not be desirable.
This change essentially ensures that we clear those values on ShopifyAPI::Base before running the block and restore them before exiting. That way, the temp session is indeed fresh.
Concern: while starting a fully fresh session makes sense and the suggested fix works, I wonder if it can be considered backward compatible. There could be a scenario where someone relies on the Basic auth settings being used for temp sessions, and those apps would be broken if they bumped their API version.

Can you give an example of the temporary sessinos that would be broken? Should we provide a migration guide?

To be honest, I'm having a bit of trouble figuring out an actual use case for this change. The entire scenario is a bit convoluted IMHO because I don't really see why you'd need multiple sessions in a single request - is there a valid reason for accessing multiple shops in one request?
Essentially, in my view what would happen here is that the developer would set up:
Base.site =<EMAIL_ADDRESS>
Session.temp(domain: 'another-store.shopify.com') do
  # This session used to use Base.user and Base.password
end

Now that I think about it, I'm not sure how much sense the use case from the issue makes, since the above behaviour actually seems right if you think about it.

That is an interesting insight. I think it may be cross shop requests. These might be apps that sync data between shops.

I see the benefit of this change if cross-shop requests are a valid concept, because otherwise we are essentially preventing apps from reaching both shops in this scenario.


fingerprint 2023 Mazda CX-5 Carbon Edition

What is your dongle id?

@sshane It's 1d5c953a3d36ec39


Hide project section if no public github repo available for user

resolves issue #218
NOTE: Though i think it would be better to inform the user that there are no public repos i think

it would be better to inform the user that there are no public repos i think

It's an edge case so, we can hide the section for now.


Fix floating panel content view constraints (#546)

Oh, I though it was a SwiftUI issue, but that was not so. I'm so happy to see this issue resolved. Thanks!


docs(js): update token fetching in ollama docs

Should resolve https://github.com/firebase/genkit/issues/654
This PR updates the docs for ollama, so that the sample code is handling tokens more efficiently
I will manual test the sample code provided before merging this.
Checklist (if applicable):

[x] Tested (manually)
[ ] Changelog updated
[x] Docs updated

please make sure to make the same change to the next branch


Spanish improvements

Added some misisng accents, replaced "Mouse" to keep a consistent use of the word in spanish and changed some words to use the correct translation

Cool, can you add your name to the Credits.txt? I'll merge soon after


Apparently, FLUTTER_SOURCE_DIR is ignored

In my project I set the heroku config variable FLUTTER_SOURCE_DIR to point to a dependency submodule directory, but the build fails with the error:
Error: No pubspec.yaml file found.
This command should be run from the root of your Flutter project.

Nevermind, the submodules are not cloned when deploying via web UI. It is necessary to push via CLI.


fixed bugs,enhanced filters and logic

Signed-off-by: ashish<EMAIL_ADDRESS>Description
This PR fixes previous bugs with service mesh component generation and helps add support for k8s component generation.
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

@utkarsh-pro  Have added verbose comments now


761 rename temporal to datetime

Description
Temporal renamed to Datetime everywhere
Changes
Docs, classes and other files updated.
Additional notes
any external profiles that use temporal will need to be updated
Issue
Resolves #761
blocked by #790

Codecov Report

Merging #792 into master will decrease coverage by <.01%.
The diff coverage is 61.22%.

@@             Coverage Diff              @@
##             master     #792      +/-   ##
============================================
- Coverage     66.15%   66.15%   -0.01%
- Complexity     1756     1761       +5
============================================
  Files           279      281       +2
  Lines          6152     6140      -12
  Branches        715      711       -4
============================================
- Hits           4070     4062       -8
+ Misses         1813     1809       -4
  Partials        269      269

Impacted Files
Coverage Δ
Complexity Δ

...messages/DatetimeConstraintValidationMessages.java
0% <ø> (ø)
0 <0> (?)

...or/inputs/validation/ProfileValidationVisitor.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...dation/validators/DatetimeConstraintValidator.java
0% <0%> (ø)
0 <0> (?)

...uts/validation/validators/ConstraintValidator.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...generator/inputs/AtomicConstraintReaderLookup.java
92.75% <100%> (ø)
44 <0> (ø)
:arrow_down:

...ator/fieldspecs/SetRestrictionsMergeOperation.java
97.05% <100%> (ø)
27 <0> (ø)
:arrow_down:

.../generation/StandardFieldValueSourceEvaluator.java
95.58% <100%> (ø)
40 <0> (ø)
:arrow_down:

...fieldvaluesources/datetime/RandomDateIterator.java
100% <100%> (ø)
3 <3> (?)

...fieldspecs/DateTimeRestrictionsMergeOperation.java
100% <100%> (ø)
5 <0> (ø)
:arrow_down:

...nerator/constraints/atomic/IsOfTypeConstraint.java
52.17% <100%> (ø)
6 <0> (ø)
:arrow_down:

... and 7 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 3cd6591...c01ba82. Read the comment docs.

@sl-slaing I'd assumed the steer was to avoid temporal completely, its a confusing word with an unrelated meaning about ghosts.
I'd rather keep everything the same name.
Might be worth getting a 3rd party weigh in on this.

Third party ahoy! 🙋♂
I think temporal is a bad word going forward ('cos I think we should introduce more temporal types), but I'd prefer something like moment, instant or point-in-time, to contrast with potential future types like ranges, durations or times-of-day.

(I'd be happy with either leaving temporal in, or gaining consensus for a new term)

Oh wait, I misread. I meant I'd leave "temporal" in the code, but I'm ambivalent to what we use in the docs. Sorry, I'm not a super helpful third party.

The name for 'things that mean a point in time' can be debated and decided at a later date. For now let's stick with temporal and datetime as the only names in the mix.
My preference would be to:

for now leave the codebase as is, as discussed in the readiness meeting, saying major renames are out of scope
rename the datatype to datetime, as requested by the PO
update the documentation, sparingly, to mention datetime instead of temporal. Whilst temporal may not be the best it does largely convey the meaning.

Reason for the last point above is the follow statement reads better than the one afterwards:

all temporal values

all datetime values
Yes this could be changed to 'all datetimes'. Doing so would call into question the statement when it comes to numeric values, which removes the ambiguity/confusion around integers and decimals.

It's not a huge point but I do think it reads better.


COVID-19 Medical Face Mask Detection using ResNet34

Deep Learning Simplified Repository (Proposing new issue)
:red_circle: Project Title :  COVID-19 Medical Face Mask Detector
:red_circle: Aim :Develop a deep learning model to detect whether the person is wearing a facemask or not . This model can be used in hospitals as well as clean room monitoring where it is necessary to wear a facemask . This is necessity in all industries where sanitation is required .
:red_circle: Dataset : Facemask Detection Dataset (images + annotations)
:red_circle: Approach : process images with XML annotations to detect three states: properly worn masks, incorrectly worn masks, and no masks. The implementation leverages a pretrained ResNet34 model with a modified final layer for 3-class classification, while keeping the feature extraction layers frozen. The system preprocesses images to 224x224 pixels, crops face regions based on bounding box annotations, and uses a 70/30 train-test split. Training employs SGD optimization with CrossEntropyLoss over 2 epochs, achieving classification of mask wear states from facial images.

📍 Follow the Guidelines to Contribute in the Project :

You need to create a separate folder named as the Project Title.
Inside that folder, there will be four main components.

Images - To store the required images.
Dataset - To store the dataset or, information/source about the dataset.
Model - To store the machine learning model you've created using the dataset.
requirements.txt - This file will contain the required packages/libraries to run the project in other machines.

Inside the Model folder, the README.md file must be filled up properly, with proper visualizations and conclusions.

:red_circle::yellow_circle: Points to Note :

The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include issue number along with it.
Follow Contributing Guidelines & Code of Conduct before start Contributing.

:white_check_mark: To be Mentioned while taking the issue :

Full name : Darsh Agrawal
GitHub Profile Link : https://github.com/DarshAgrawal14
Email ID<EMAIL_ADDRESS>Participant ID (if applicable):
Approach for this Project : mentioned Above
What is your participant role? GSSoC'24 extended and Hactoberfest'24

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

Similar problem statement is already present in this repository. Hence clsoing this issue as duplicate entry.


#1490 added db migration script

Codecov Report

Merging #1636 into master will increase coverage by 2.13%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1636      +/-   ##
==========================================
+ Coverage   26.47%   28.60%   +2.13%
==========================================
  Files          72       78       +6
  Lines        4537     5208     +671
==========================================
+ Hits         1201     1490     +289
- Misses       3168     3528     +360
- Partials      168      190      +22

Impacted Files
Coverage Δ

platform-support/openshift-route-service/main.go
48.42% <0.00%> (-4.01%)
:arrow_down:

api/handlers/common.go
100.00% <0.00%> (ø)

api/handlers/event.go
81.15% <0.00%> (ø)

api/handlers/project.go
73.91% <0.00%> (ø)

cli/cmd/configure_bridge.go
60.86% <0.00%> (ø)

api/handlers/configure.go
13.27% <0.00%> (ø)

api/handlers/service.go
76.08% <0.00%> (ø)

mongodb-datastore/handlers/events.go
20.65% <0.00%> (+11.81%)
: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 a5fec7b...ae1dde3. Read the comment docs.


build against libtorch instead of pytorch

So there is no need to install python

Checklist

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

@conda-forge-admin, please rerender


upgrade grafana

Signed-off-by: David J. M. Karlsen<EMAIL_ADDRESS>What this PR does / why we need it:
Upgrade to latest release
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[X] DCO signed
[X] Chart Version bumped
[X] Variables are documented in the README.md

/lgtm


Fix code coverage report warnings in SonarCloud

When processing code coverage (LCOV) report with the sonar scanner, we get the following warnings:
WARN: Problem during processing LCOV report: can't save DA data for line 26105 of coverage report file (java.lang.IllegalArgumentException: Line with number 12 doesn't belong to file projects/storefrontlib/src/lib/ui/ui-framework/ui-framework.module.ts).
WARN: Problem during processing LCOV report: can't save DA data for line 26106 of coverage report file (java.lang.IllegalArgumentException: Line with number 15 doesn't belong to file projects/storefrontlib/src/lib/ui/ui-framework/ui-framework.module.ts).
WARN: Problem during processing LCOV report: can't save DA data for line 26107 of coverage report file (java.lang.IllegalArgumentException: Line with number 21 doesn't belong to file projects/storefrontlib/src/lib/ui/ui-framework/ui-framework.module.ts).
WARN: Problem during processing LCOV report: can't save DA data for line 26108 of coverage report file (java.lang.IllegalArgumentException: Line with number 23 doesn't belong to file projects/storefrontlib/src/lib/ui/ui-framework/ui-framework.module.ts).
This is why the coverage is not displaying the right numbers in SonarCloud.

Just a guess: would source maps help?

Pull request #354

Just a guess: would source maps help?
Maybe tests and code coverage could be ran with --sourceMap=true flag.

Yes, that did the trick. Thanks @znikola !


[pos_debt_notebook] Max Debt

Can we set max debt on the customer level? So one customer might be allowed credit of $1000. And another customer maybe $500. I can see there is a max level on the Journal but this is for all customers?

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Hello @jayo2005
The maximum debt value can only be set for payment methods.
If you need different values for different customers, please contact our managers<EMAIL_ADDRESS>


Skewering HTTPS (mixed-mode loading problems)

Is there a way to tell skewer to use https when skewering pages that are already https? Would make skewer-everything.js much more useful.
Thanks for creating this great emacs mode!

This is one of the weak spots of Skewer, especially as the web moves
more and more towards HTTPS. Emacs has GnuTLS bindings but only for TLS
clients (i.e. url-retrieve). So at the moment there's no way to host an
HTTPS server within Emacs for Skewer short of writing an entire TLS
implementation in Emacs Lisp, which would be a far bigger project than
Skewer itself.

Would it be possible to solve this by using something like socat to forward an ssl socket to emacs?

That's very likely to be possible. When Emacs is compiled without GnuTLS
support, it uses the gnutls command line program instead in a similar
way.
Since I don't need this myself at the moment, it's not something I plan
to implement, though this doesn't preclude anyone else from trying.

I've used hitch as a workaround.
Run this once:
mkdir -p ~/.emacs.d/skewer-https/
cd ~/.emacs.d/skewer-https/
openssl req -nodes -newkey rsa:2048 -keyout skewer-hitch.key -out skewer-hitch.csr \
    -subj "/C=GB/ST=London/L=London/O=Acme Widgets/OU=IT Department/CN=skewer-hitch.com"
openssl x509 -req -days 365 -in skewer-hitch.csr -signkey skewer-hitch.key -out skewer-hitch.crt
cat skewer-hitch.key skewer-hitch.crt >skewer-hitch.pem
sudo apt install hitch

and run this after run-skewer:
(unless (get-buffer-process "*skewer-hitch*")
      (start-process "skewer-hitch" "*skewer-hitch*"
                     "hitch"
                     (format "--backend=[localhost]:%s" httpd-port)
                     "--frontend=[localhost]:38443"
                     (expand-file-name "~/.emacs.d/skewer-https/skewer-hitch.pem")))

Then change your bookmarklet to have the right port:
javascript:(function(){var%20d=document;var%20s=d.createElement('script');s.src='https://localhost:38443/skewer';d.body.appendChild(s);})()

(Make sure to reload the page first if you used your old bookmarklet – it'll point to the wrong port.)

Since @unhammer has reminded me of this thread, I'll also mention that a
couple months ago I experimented with using stunnel as a seemless
front-end to Skewer. I captured the gist of it here:
https://github.com/skeeto/dotfiles/blob/46c31aac041ee6f7b66083ed2512a21f02ce1987/_bashrc#L97
However its a bit flaky and I never quite sorted it out:

Sometimes stunnel prematurely terminates the connection and I don't
know why. This happens with the Python server, too, so it's not just
some issue with Skewer.

It relies specifically on stunnel3. Later (?) versions of stunnel
(e.g. stunnel4) have a different interface and don't seem to support
this mode.

Modern browsers really hate self-signed certs and no longer handle
them gracefully (i.e. no more "store and allow this cert next time").
This is a messy issue to solve.

Hm, I haven't noticed hitch doing any premature termination – maybe give that a try? It's quite small:
Installed-Size: 201 kB
Depends: libc6 (>= 2.14), libev4 (>= 1:4.04), libssl1.0.0 (>= 1.0.0), init-system-helpers (>= 1.18~), adduser

Why create a new cert on every startup? (Isn't that just creating more work for yourself?)
Firefox at least lets me save the cert when I go to localhost:38443/skewer and click Advanced, but since it's the same one each time, I only had to do it once (on that computer). Chrome I have no idea though.

Hitch certainly seems like a cleaner solution than stunnel. I'll have to spend some time with it.

Why create a new cert on every startup?

That particular example is just for a throwaway sever. Plus, for documentation purposes, it captures the cert generation procedure (I can never remember). For Skewer it would probably make sense for a more persistent cert, hence it's important that the browser remembers the cert.

Firefox at least lets me save the cert

Oops, you're right. Upon closer examination I see that it's just my current configuration preventing the "permanently store" checkbox.

Btw, for Chromium, I opened "Manage certificates → Authorities → Import" and selected my .pem file, ticking off "Trust this certificate for identifying websites". A bit more involved, but i can control Chromium too from Emacs now :)


input position of LED resets to zero if you go back to LED layout page

[x] I confirm that this is an issue rather than a question.

Bug report
Steps to reproduce
What is expected?
What is actually happening?
System

So, after setting LED output, controller and layout and saving, it saves fine, but if you open classic layout just the input position resets everytime (I set to 345, it saves fine, but on reopening classic layout page the input position value resets to 0)
Alpha 10, libreelec 9.2 unofficial install pi3

Also you do not get the standard drop down window stating setting are saved


Added NodeJs and MongoDB Resources

Related Issue

Closes: #190
Description of Changes

Added NodeJs and MongoDB resources
Modified only webdev.astro file

Checklist:

[x] My code adheres to the established style guidelines of this project.
[x] I have conducted a self-review of my code.
[x] I have included comments in areas that may be difficult to understand.
[x] I have made corresponding updates to the project documentation.
[x] My changes have not introduced any new warnings.

Screenshots

Original
Updated

Please provide any necessary screenshots to illustrate the changes made.

Hey @Alkaison, It seems there are no conflicts in the code. If there are any errors, please update me.

Hi @siddarthdayala, the code is perfect. You will have to wait for @Astrodevil to merge it because only he has Write access to this repository.

@siddarthdayala solve conflict

@Astrodevil resolved the conflict. Please check it

hey @Alkaison will surely add other resources in another PR. Please review this one


#175 - Get next run by tag

PR for ticket 175

Coverage decreased (-0.3%) to 99.403% when pulling 1195692ae158059625c2a9c4b0e86079cc178089 on jweijers:master into 6eb0b5346b1ce35ece5050e65789fa6e44368175 on dbader:master.


Feature - add support for horizontal rule in Markdown

New feature to add support for a horizontal rule in Markdown. The Markdown --- should get converted to an <hr> tag.

Fixed in commits

Updated Markdown support for horizontal rule
Updated code and readme for Markdown horizontal rule support

Final merge in

Merge branch 'issue-12' into main


Update plugin manual

Pull Request Description
What issue does this change request address? (Use "#" before the issue to link it, i.e., #42.)
see #1806
What are the significant changes in functionality due to this change request?
This PR will only update the raven plugin manual, which will reflect the recent Code Plugin, PostProcessor Plugin features.
See the recent PR #2000 for the Code Plugin structure.

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[x] 1. Review all computer code.
[x] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[x] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[x] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[x] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[x] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[x] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[x] 8. If an analytic test is changed/added is the the analytic documentation updated/added?
[x] 9. If any test used as a basis for documentation examples (currently found in raven/tests/framework/user_guide and raven/docs/workshop) have been changed, the associated documentation must be reviewed and assured the text matches the example.

I approve this one.

There are no code changes, just manual updates. One of the machines is pending.


Bugfix/global filtering

I changed the filter on food security to include all countries, and added a country filter to the funding data.  I checked the IPC p-code mappings and they're pretty good.  I had to add a couple extra matching rules to get some countries to match.
There are just a few mismatched units in GHA that I either want to match to admin 1 or add to the admin_fuzzy_dont list.  @mcarans I think we should change admin_fuzzy_don't to include iso codes so we don't eliminate fuzzy matching globally for common words like "Central".  Or we could make the mappings a little more flexible to allow us to match to XXX units.  Which do you think makes more sense?

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

11 of 22 (50.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.5%) to 92.303%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/hapi/pipelines/database/funding.py
3
4
75.0%

src/hapi/pipelines/database/food_security.py
8
18
44.44%

Totals

Change from base Build<PHONE_NUMBER>1:
-0.5%

Covered Lines:
1655

Relevant Lines:
1793

💛  - Coveralls

Once we release the changes I made in hdx-python-country this will be ready to release!


Fix detection of merge commits on Github Actions an AzP

The double quotes get escaped by execFileSync and then are part of the output which makes the Regex fail to match.
Remove them to avoid this.
See https://github.com/boostorg/boost-ci/runs/5394406101?check_suite_focus=true:
['verbose'] Handling PR with parent hash(es) '"86f4b7cb20e29080b366ee1593c1135038bda4bf cd099c05fc6d88115e9bbdc0c60b23fb5a0fa952"' of current commit.
['info']     Commit with SHA 9e556cae25da2cb0438a10e81d3f78ddcc7e8510 of PR 125 is not a merge commit

Can be reproduced in a shell by running git show --no-patch --format=\"%P\"
@drazisil-codecov Finally found this!

Tests appear to be failing after pulling in main, @Flamefire Can you take a look?

That merge actually exposed some missing mocks. While fixing this I found another bug in an affected test and fixed that too as well as the commit messages (hence the force-push)


No, it isn't me doxxing Seth on  subreddits. On a similar note, can binary Fate kindly stop trying to bribe OVH employees to get my data?


Feature/associations

Milestone #3 - Set up the associations

In this feature branch, I added the associations, and relationship, between the multiple classes as per the diagram into files and implemented the features for creating the books, rentals, students, and teachers. Details of the features that I have implemented in this branch are as follows:

Created different folders for different files.
Modified the Person class by inheriting the features of the Nameable class interface.
Added the feature by using the association's concept.
Implemented the function overriding feature to extend the functionality of the and also added the self for passing the class as an object.
Resolved the rubocop linter errors.
Used the best practices for writing the code in Ruby.
Converted all the variables and method names in SnakeCase as per Ruby Styling Guide.

@Wes-Isaac Thank you very much ❤
Happy Coding 🥂


Issue with JIT

Version
@nuxtjs/tailwindcss: v4.0.2
nuxt: v2.15.3
node: v15.12.0
npm: v7.6.3
Reproduction Link
N/A. Will try and add soon.
Steps to reproduce
Enable JIT in nuxt.config.ts
tailwindcss: {
  cssPath: '~/assets/css/tailwind.css',
  configPath: 'tailwind.config.js',
  exposeConfig: false,
  config: {},
  viewer: false,
  jit: true,
},

What is Expected?
Jit to work
What is actually happening?
 WARN<EMAIL_ADDRESS>is installed but ^7.0.32 is expected                                                                                12:55:42

ℹ Using Tailwind CSS from ~/assets/css/tailwind.css                                                                                nuxt:tailwindcss 12:55:43
ℹ Merging Tailwind config from ~/tailwind.config.js                                                                                nuxt:tailwindcss 12:55:43
ℹ Sentry reporting is disabled ("disabled" option has been set)                                                                                nuxt:sentry 12:55:43

   ╭───────────────────────────────────────╮
   │                                       │
   │   Nuxt @ v2.15.3                      │
   │                                       │
   │   ▸ Environment: development          │
   │   ▸ Rendering:   client-side          │
   │   ▸ Target:      static               │
   │                                       │
   │   Listening: http://localhost:3000/   │
   │                                       │
   ╰───────────────────────────────────────╯

ℹ Preparing project for development                                                                                12:55:46
ℹ Initial build may take a while                                                                                12:55:46
ℹ Tailwind JIT activated                                                                                nuxt:tailwindcss 12:55:46
✔ Builder initialized                                                                                12:55:46
✔ Nuxt files generated                                                                                12:55:46

✖ Client
  Compiled with some errors in 40.25s

 ERROR  Failed to compile with 1 errors                                                                                friendly-errors 12:56:31

 ERROR  in ./.nuxt/components/nuxt-error.vue?vue&type=style&index=0&lang=css&                                                                                friendly-errors 12:56:31

Module build failed (from ./node_modules/@nuxt/postcss8/node_modules/postcss-loader/dist/cjs.js):                                                                                friendly-errors 12:56:31
TypeError: Cannot read property 'type' of null
    at extractCandidates (/Users/vinayak/Development/Work/project/abc/node_modules/@tailwindcss/jit/src/lib/setupContext.js:314:22)
    at /Users/vinayak/Development/Work/project/abc/node_modules/@tailwindcss/jit/src/lib/setupContext.js:328:22
    at Array.flatMap (<anonymous>)
    at withIdentifiers (/Users/vinayak/Development/Work/project/abc/node_modules/@tailwindcss/jit/src/lib/setupContext.js:326:30)
    at addBase (/Users/vinayak/Development/Work/project/abc/node_modules/@tailwindcss/jit/src/lib/setupContext.js:390:38)
    at /Users/vinayak/Development/Work/project/abc/node_modules/@tailwindcss/forms/src/index.js:252:5
    at registerPlugins (/Users/vinayak/Development/Work/project/abc/node_modules/@tailwindcss/jit/src/lib/setupContext.js:580:7)
    at /Users/vinayak/Development/Work/project/abc/node_modules/@tailwindcss/jit/src/lib/setupContext.js:770:5
    at /Users/vinayak/Development/Work/project/abc/node_modules/@tailwindcss/jit/src/index.js:37:49
    at LazyResult.runOnRoot (/Users/vinayak/Development/Work/project/abc/node_modules/postcss/lib/lazy-result.js:303:16)
    at LazyResult.runAsync (/Users/vinayak/Development/Work/project/abc/node_modules/postcss/lib/lazy-result.js:355:26)
    at async Object.loader (/Users/vinayak/Development/Work/project/abc/node_modules/@nuxt/postcss8/node_modules/postcss-loader/dist/index.js:95:14)
                                                                                friendly-errors 12:56:31
 @ ./node_modules/vue-style-loader??ref--3-oneOf-1-0!./node_modules/@nuxt/postcss8/node_modules/css-loader/dist/cjs.js??ref--3-oneOf-1-1!./node_modules/vue-loader/lib/loaders/stylePostLoader.js!./node_modules/@nuxt/postcss8/node_modules/postcss-loader/dist/cjs.js??ref--3-oneOf-1-2!./node_modules/vue-loader/lib??vue-loader-options!./.nuxt/components/nuxt-error.vue?vue&type=style&index=0&lang=css& 4:14-380 15:3-20:5 16:22-388
 @ ./.nuxt/components/nuxt-error.vue?vue&type=style&index=0&lang=css&
 @ ./.nuxt/components/nuxt-error.vue
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./node_modules/eventsource-polyfill/dist/browserify-eventsource.js (webpack)-hot-middleware/client.js?reload=true&timeout=30000&ansiColors=&overlayStyles=&path=%2F__webpack_hmr%2Fclient&name=client ./.nuxt/client.js

Workaround
{
  cssPath: '~/assets/css/tailwind.css',
  configPath: 'tailwind.config.js',
  exposeConfig: false,
  config: {},
  viewer: false,
-  jit: true,
+  jit: false,
}

OK, one of the dependabot update was failing ci,
fix(deps): bump @tailwindcss/forms from 0.2.1 to 0.3.0
Tailwind Forms plugin has issues with jit?

open bug in jit repo - https://github.com/tailwindlabs/tailwindcss-jit/issues/158

Issue is fixed by upgrading @tailwindcss/form to v0.3.2
Reference - https://github.com/tailwindlabs/tailwindcss-jit/issues/158#issuecomment-808117138

i have this error with and without forms plugin and with blank tailwind config
 ERROR  Failed to compile with 1 errors

 ERROR  in<EMAIL_ADDRESS>
Module build failed (from ./node_modules/@nuxt/postcss8/node_modules/postcss-loader/dist/cjs.js):
RangeError: Maximum call stack size exceeded
    at candidatePermutations (/home/deejavu/nuxtravolta/node_modules/@tailwindcss/jit/src/lib/generateRules.js:19:32)
    at candidatePermutations (/home/deejavu/nuxtravolta/node_modules/@tailwindcss/jit/src/lib/generateRules.js:41:10)
    at candidatePermutations.next (<anonymous>)
    at candidatePermutations (/home/deejavu/nuxtravolta/node_modules/@tailwindcss/jit/src/lib/generateRules.js:41:10)
    at candidatePermutations.next (<anonymous>)
    at candidatePermutations (/home/deejavu/nuxtravolta/node_modules/@tailwindcss/jit/src/lib/generateRules.js:41:10)
    at candidatePermutations.next (<anonymous>)
    at candidatePermutations (/home/deejavu/nuxtravolta/node_modules/@tailwindcss/jit/src/lib/generateRules.js:41:10)
    at candidatePermutations.next (<anonymous>)
    at candidatePermutations (/home/deejavu/nuxtravolta/node_modules/@tailwindcss/jit/src/lib/generateRules.js:41:10)
    at candidatePermutations.next (<anonymous>)
    at candidatePermutations (/home/deejavu/nuxtravolta/node_modules/@tailwindcss/jit/src/lib/generateRules.js:41:10)
    at candidatePermutations.next (<anonymous>)
    at candidatePermutations (/home/deejavu/nuxtravolta/node_modules/@tailwindcss/jit/src/lib/generateRules.js:41:10)
    at candidatePermutations.next (<anonymous>)
    at candidatePermutations (/home/deejavu/nuxtravolta/node_modules/@tailwindcss/jit/src/lib/generateRules.js:41:10)

<EMAIL_ADDRESS>4:14-207 15:3-20:5 16:22-215
 @ ./.nuxt/App.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./node_modules/eventsource-polyfill/dist/browserify-eventsource.js (webpack)-hot-middleware/client.js?reload=true&timeout=30000&ansiColors=&overlayStyles=&path=%2F__webpack_hmr%2Fclient&name=client ./.nuxt/client.js

ℹ Waiting for file changes
ℹ Memory usage: 252 MB (RSS: 544 MB)
ℹ Listening on: http://localhost:3000/


Prove/verify API

This PR implements proving and verification for the lurk CLI.

Only the Pallas field and the Nova backend are supported for now
I avoided reusing the APIs that were built for fcomm and clutch on purpose. This avoids conflicts and makes the CLI code more self-contained and easy to change. A future refactor might serve the purpose of unifying the underlying code base so fcomm, clutch and the CLI can sit on top of the same common code
I've set the code to get configuration parameters from env vars, config file and CLI args (in that order of precedence, with CLI args having the highest priority)

This PR doesn't implement commitments/openings. We'll leave that for a next unit of improvement.

I've set the code to get configuration parameters from env vars, config file and CLI args (in that order of precedence, with CLI args having the highest priority)

I would advocate for the following decreasing precedence:

global config file (if we support, optional to begin with)
local config file
env vars
CLI args

I think this is pretty standard and makes logical sense. The location of the config file should also be settable by env var and CLI args with the same precedence as otherwise.

There should be a CLI arg that specifies no config file should be used (and probably similar to ensure no env vars are used).
That way, when explicit and total control is required, something like lurk --no-config --no-env XXX will have a 100% deterministic config inferable only from the command.

I will turn comments about CLI flexibility into new issues after this is merged


Transport type UDP

Can you add a new feature for TransportType? I need Transport type UDP.

By default WebRTC use UDP wdym

Here i am getting transport type ws & tcp. So how can i manage it to use udp?

We use a WS or TCP connection for the signalling processs to initiate or terminate a session (sip messages).
Once the session is connected WebRTC transmits the actual media (audio/video) over UDP.
Why would you want to use UDP for the signalling step?  (Genuine question)
Also do you realise what UDP is and how much is needed to set it up, packet ordering, error checking, reliability timeouts, flow control, security etc etc

We use a WS or TCP connection for the signalling processs to initiate or terminate a session (sip messages). Once the session is connected WebRTC transmits the actual media (audio/video) over UDP.
Why would you want to use UDP for the signalling step? (Genuine question) Also do you realise what UDP is and how much is needed to set it up, packet ordering, error checking, reliability timeouts, flow control, security etc etc

I am trying to build softphone app. I need to use sip server and transport type udp. I don't have deep knowledge about this. I saw that webrtc use udp connection. Can you please give more details about this or resource?

+++
I need Transport type UDP.

I Need also transport type UDP

We use a WS or TCP connection for the signalling processs to initiate or terminate a session (sip messages). Once the session is connected WebRTC transmits the actual media (audio/video) over UDP.
Why would you want to use UDP for the signalling step? (Genuine question) Also do you realise what UDP is and how much is needed to set it up, packet ordering, error checking, reliability timeouts, flow control, security etc etc

I am trying to build softphone app. I need to use sip server and transport type udp. I don't have deep knowledge about this. I saw that webrtc use udp connection. Can you please give more details about this or resource?

@sicunets Why do you "need to use... transport type udp"? What is the name of the sip server that is forcing you to use udp?
If you read my comment again, yes webRTC uses udp for sending the audio/video data packets, AFTER WS or TCP is used to initiate the call with SIP signalling.
The transport types WS and TCP that you see in this package are only for the SIP signally processes, before webRTC uses UDP to send the content of the call.
@ushodmonov @TaraCybertouch read the above and explain what is making you need udp for sip signalling


wled effect

please tell me the script, there is a wled tape. I want to save its effect state, change the effect, and then return the effect back
alias: test
sequence:
service: saver.save_state
data:
entity_id: light.wled
delay: ‘00:00:05’
service: wled.effect
data:
entity_id: light.wled
effect: police
delay: ‘00:00:05’
service: saver.restore_state
data:
entity_id: light.wled
entity_id: saver.saver
mode: single
All wled seeting:
min_mireds: 153
max_mireds: 500
effect_list: Android, Blink, Blink Rainbow, Bouncing Balls, Bpm, Breathe, Candle, Candle Multi, Chase, Chase Flash, Chase Flash Rnd, Chase Rainbow, Chase Random, Chunchun, Circus, Colorful, Colorloop, Colortwinkles, Colorwaves, Dancing Shadows, Dissolve, Dissolve Rnd, Drip, Dynamic, Fade, Fill Noise, Fire 2012, Fire Flicker, Fireworks, Fireworks 1D, Fireworks Starburst, Flow, Glitter, Gradient, Halloween, Halloween Eyes, Heartbeat, ICU, Juggle, Lake, Lighthouse, Lightning, Loading, Merry Christmas, Meteor, Meteor Smooth, Multi Comet, Noise 1, Noise 2, Noise 3, Noise 4, Noise Pal, Oscillate, Pacifica, Palette, Percent, Phased, Phased Noise, Plasma, Police, Police All, Popcorn, Pride 2015, Railway, Rain, Rainbow, Rainbow Runner, Random Colors, Red & Blue, Ripple, Ripple Rainbow, Running, Running 2, Saw, Scan, Scan Dual, Scanner, Scanner Dual, Sine, Sinelon, Sinelon Dual, Sinelon Rainbow, Solid, Solid Glitter, Solid Pattern, Solid Pattern Tri, Sparkle, Sparkle Dark, Sparkle+, Spots, Spots Fade, Stream, Stream 2, Strobe, Strobe Mega, Strobe Rainbow, Sunrise, Sweep, Sweep Random, Theater, Theater Rainbow, Traffic Light, Tri Chase, Tri Fade, Tri Wipe, Twinkle, Twinklecat, Twinklefox, Twinkleup, Two Areas, Two Dots, Washing Machine, Wipe, Wipe Random
brightness: 255
hs_color: 37.412, 100
rgb_color: 255, 159, 0
xy_color: 0.57, 0.41
effect: Solid
intensity: 128
palette: Default
playlist: null
preset: null
reverse: false
speed: 128
friendly_name: WLED
icon: mdi:led-strip-variant
supported_features: 55

It's not so simple with a saver, you will get a better result by using [scene snapshot])https://www.home-assistant.io/integrations/scene/#creating-scenes-on-the-fly)

It's not so simple with a saver, you will get a better result by using [scene snapshot])https://www.home-assistant.io/integrations/scene/#creating-scenes-on-the-fly)
scene snapshot,
Saves a new scene every time, and there are many scenes

If you use the same name of a scene it will be overwritten


Updating the SolidusAftepay::PaymentMethod sets the minimum_amount and maximum_amount preferences to 0.0

Updating the SolidusAftepay::PaymentMethod sets the minimum_amount and maximum_amount preferences to 0.0 instead of leaving them nil. This is causing an issue here because instead of retrieving the configuration from Afterpay, the method always returns  a 0.0..0.0 range.

This should be the correct behavior:

if the minimum and maximum are set inside the admin, use these values to show or not the payment methods
if the minimum and maximum are not set inside the admin, do not set it to 0 but fetch this information from Afterpay

An additional goal is: fetch the information from Afterpay and cache them for 1 day.


Improve LHS tensor.pack on non-f32 types for x86

We have optimized codegen for packing on f32 types, but not int8. This is a tracking issue for int8 case. I observed that some pack ops are not vectorized. Because masking is only supported on limited ops for dynamic shapes. We should just relax the condition to using isElementwise(), so linalg.transpose op can also get vectorized. I have an easy fix locally, and will send it out for review.
With the change and better distribution logic, we can save up to 43% total dispatch sizes for int8 models, see https://gist.github.com/iree-github-actions-bot/fa5becb880b9a6afc2d362883a585d5a
The next step is having better pack codegen for non-f32 types. We need a pattern to pack innermost tile being a single element and leverage it to 16x16 transpose lowering. Looking at transpose permutation map and using vector.bitcast op should help here.

https://github.com/llvm/llvm-project/pull/71454 fixes the vectorization issue.

This is the details about 16x16 transpose trick. The 4x4, 8x8, 16x16 tricks have the same idea. https://stackoverflow.com/questions/29519222/how-to-transpose-a-16x16-matrix-using-simd-instructions
Implementation: https://github.com/llvm/llvm-project/blob/main/mlir/lib/Dialect/Vector/Transforms/LowerVectorTranspose.cpp
In your prototype, I think we can add the bitcast pattern before transpose lowering, i.e., https://github.com/openxla/iree/blob/bd2c92dbb3d2109cd624fa18e75b9bf3caaa4ae5/compiler/src/iree/compiler/Codegen/LLVMCPU/LLVMCPUVectorLowering.cpp#L148
You can preset lowering_config; the 16x16 shuffle optimization should be kicked in automatically. It should give us a much better performance. If it works, then we can teach tile size selection about it at https://github.com/openxla/iree/blob/bd2c92dbb3d2109cd624fa18e75b9bf3caaa4ae5/compiler/src/iree/compiler/Codegen/LLVMCPU/KernelDispatch.cpp#L1259-L1270
Here is the benchmark data when I implemented the trick for f32 types: https://github.com/openxla/iree/pull/13318
There can still be some performance improvements left on the table. We should be able to replace the vunpck*pd ones with a combination of shufps + blends that should be faster, in theory. The review comments in https://reviews.llvm.org/D148685 is very helpful to me.

I have some prototype in https://github.com/hanhanW/iree/tree/improve-pack, but need to structure them better. The next step in mind to try are

Generate vector.bitcast around vector.transpose in virtual vector lowering stage
Add a pattern matching for vector.transfer_read -> shape_cast -> bitcast to help flatten them correctly.
Similiar pattern for vector.transfer_write chain.
Unroll bitcast to 1d vectors, which is prototyped in the branch.

2 and 3 are needed.


Compare performance with Apache Beam

It'd be good to evaluate how Euphoria compares with Apache Beam in terms of performance on Apache Spark as well as on Apache Flink. Similarly to #11, we'd like to measure the overhead of the Beam layer of the benchmark program compared to a raw flink and spark impl and see how that overhead differs from Euphoria's overhead.

This can reveal either problems on our side or problems on the side of Apache Beam, which we can report back.
This will provide a good base for deciding whether its worth to start with #32 or rather postpone it.
We'll have some concrete numbers for upcoming presentations about Euphoria. (Questions regarding "Euphoria vs. Beam" are expected and the overhead comparison is at least one point of interest.)

A very premature observation on a word-count like program suggests that Apache Beam 0.6.0 on Flink 1.2 might be well suffering from expanding windows before the shuffle (see #47.)

It seems that Beam is unable to perform join on windowed inputs with different windowings. It is stated in here https://cloud.google.com/dataflow/model/group-by-key
When using CoGroupByKey to group PCollections that have a windowing strategy applied, all of the PCollections you want to group must use the same windowing strategy and window sizing. For example, all the collections you're merging must use (hypothetically) identical 5-minute fixed windows or 4-minute sliding windows starting every 30 seconds.

If your pipeline attempts to use CoGroupByKey to merge PCollections with incompatible windows, Dataflow will generate an IllegalStateException error when your pipeline is constructed.

and it corresponds to the code in Beam where compatibility of windows is only reduced to equality check in SlidingWindows as well as in FixedWindows. It causes IllegalStateexception
Exception in thread "main" java.lang.IllegalStateException: Inputs to Flatten had incompatible window windowFns: org.apache.beam.sdk.transforms.windowing.SlidingWindows@3b23cf, org.apache.beam.sdk.transforms.windowing.FixedWindows@f5f1

We can omit the Beam windowing and simulate the windows by custom data, but that is probably not the intent of this ticket.
Otherwise we have to redefine the benchmark or just create a different one.

I performed the batch benchmark without beam windowing with transmitting only window-end times as longs (same as in pure Spark/Flink batch programs). The results are:

beam-spark (batch): 2.1h
beam-flink (batch): 1.5h

For context:

euphoria-spark (batch): 1.1h
euphoria-flink (batch): ? (6h)

I think we can obsolete this.


Switch from qs to query-string was a breaking change

In case anyone else runs into this when upgrading, the url parsing change between 1.13.1 and 1.14.0, should've been a major version bump. query-string doesn't implement nesting like qs does, if you rely on this behavior then things will break.

Sorry about that. I think we're pushing 2.0.0 soon anyway. We did try to add a warning though, per https://github.com/rackt/history/blob/master/modules/useQueries.js#L59-L63. Do you know if that warning fired for you?

I don't remember seeing that warning, I think my query parsing logic blew up before it got that far.

I don't know that there's anything we can do about this. 2.0.0 (or an RC at least) will land shortly.

I don't know that there's anything we can do about this. 2.0.0 (or an RC at least) will land shortly.

No worries, it happens. Just wanted to let people know to save some debugging time when upgrading.

No worries, it happens. Just wanted to let people know to save some debugging time when upgrading.


Make the plate responsive

Fix the div containing the plate to be responsive.

The problem was solved in issue #2.


Wahba run autoimport in build

Run the auto import for benchmark in the build step

ptal? @lopopolo

This PR is in support of GH-12.

This PR is in support of GH-76.


Admin can create a program

wireframes : https://miro.com/app/board/o9J_lXULxwE=/?moveToWidget=3074457354355841621&cot=14

#104, #105 cover this

M1 Review - Closed


Carlink 5.0 2Air Wireless support

Hi, has anyone had any success connecting to the Carlink 5.0 2Air Wireless? If so, can I ask for intructions? :)
In lsusb it's like this:
Bus 003 Device 003: ID 05ac:12a8 Apple, Inc. iPhone 5/5C/5S/6/SE/7/8/X/XR

Hi @martin2131 , only CPC200-Autokit or CPC200-CCPA are supported


[ZEPPELIN-4396]. HvPlot is broken

What is this PR for?
HvPlot is broken due to bug in ipython_server.py. IPython may produce multiple types of output for one single python object. And the orders of these output matters, we should output html type over plain text type.
What type of PR is it?
[Bug Fix]
Todos

[ ] - Task

What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-4396

How should this be tested?

CI pass

Screenshots (if appropriate)

Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

Will merge if  no more comment


Consider replacing ToString bound for more precise bound

Currently, query builder accepts ToString for its arguments. But this trait doesn't have definite semantics and many types implement this. Most of the instances are irrelevant to database query, such as error types (because it implements Display for human display of the error).
I'm not sure why just accepting String or impl Into<String> is not enough. Probably it should be.

I share your thoughts about Into<String>, I have already converted usages of ToString to it in my wip branch.

The idea was accepting both &str and String. I agree that using Into<String> is better.


rekor-server: 0.12.1 -> 0.12.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/sigstore/rekor/releases.
meta.description for rekor-server is: "Sigstore server, the Signature Transparency Log"
meta.homepage for rekor-server is: "https://github.com/sigstore/rekor"
meta.changelog for rekor-server is: "https://github.com/sigstore/rekor/releases/tag/v0.12.2"
Updates performed

Golang update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.12.2 with grep in /nix/store/xvy2cbvkjjyca2zfd005vcfj1xkh347f-rekor-server-0.12.2
found 0.12.2 in filename of file in /nix/store/xvy2cbvkjjyca2zfd005vcfj1xkh347f-rekor-server-0.12.2

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
rekor-cli
rekor-server

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/xvy2cbvkjjyca2zfd005vcfj1xkh347f-rekor-server-0.12.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A rekor-server https://github.com/r-ryantm/nixpkgs/archive/edc522006815e794e683524c8067a84dcb5086d1.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/xvy2cbvkjjyca2zfd005vcfj1xkh347f-rekor-server-0.12.2
ls -la /nix/store/xvy2cbvkjjyca2zfd005vcfj1xkh347f-rekor-server-0.12.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

rekor-cli
rekor-server

Maintainer pings
cc @LeSuisse @06kellyjac for testing.

Done in #193604


Fix: SEGV using null_object for method call

Solves the SEGV. Gives "internal error"; placeholder depending of actual fix.
May be related to #12089.

Solves the SEGV. Gives "internal error"; placeholder depending of actual fix.

The actual fix is a bit complicated, requires handling a variable of
unknown type at runtime, since the variable type could be "any".  Might
be a dict or an object.  I'll add a specific error message for now.
--
From the classified section of a city newspaper:
Dog for sale: eats anything and is fond of children.
/// Bram Moolenaar -- @.*** -- http://www.Moolenaar.net   \
///                                                                      \
\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///


Create an account at crates.io to publish artifacts of Rust Client

We need crates.io account to publish the artifacts of the opensearch rust client for community consumption. Please help create this account.

Repo for which artifacts need to be published: opensearch-rs

[Offline Discussion] @aditjind is figuring out how to sign and publish the artifacts on crates.io
https://doc.rust-lang.org/cargo/reference/publishing.html
On glancing at the above document looks like the process can be automated. We can use opensearch-ci-bot as the GH account required to publish to crates. Need to check with the permissions and stuff.
However, since we are running short on time @aditjind requested to publish the initial version of client using manual documented process. He will work parallely on automating this for future releases.
The automation would include adding a jenkins workflow for opensearch-rs that will have right set of credentials to publish.
cc: @bbarani

@gaiksaya In the meantime, shall we create an opensearch-project account and use that to publish either manual or automation.

@gaiksaya In the meantime, shall we create an opensearch-project account and use that to publish either manual or automation.

I do not see an option to create a new account. All see is Log in with GitHub. Am I missing something here?

@aditjind @VijayanB Can we directly link opensearch-ci-bot GitHub account with crate.io and publish the artifacts?

As per my understanding, we will use the opensearch-ci-bot GitHub account to publish the first release of the client manually. We will then have automation scripts to build, sign and publish the artifacts via Infra Jenkins setup.
cc: @gaiksaya (Correct me if I missed anything).

No staging area support for Crates:

Issue
Discussion


Is it possible to apply wildcard rules to specific query/mutation fields

Question about GraphQL Shield
I've been looking in the docs but could find anything about (I might've missed it) but is it apply the rules specified in a wildcard * to a specific query/mutation field rule.
For example
Mutation: {
        '*': and(isAuthenticated, hasPermission),
        addUser: validateInput, // this would also have the rules applied in the wildcard
 }

If I want to achieve the above I need to do
Mutation: {
        '*': and(isAuthenticated, hasPermission),
        addUser: and(isAuthenticated, hasPermission, validateInput)
 }

I saw something related to this question in #680 but its not been updated for a while.
Question about GraphQL concepts
Please describe the concept you are interested in. If possible also provide links and source of the problem that you have.

[x] I have checked other questions and found none that matches mine.

Hey! 👋
Thank you for being so patient. I don't think it's possible since this is a very edge case scenario. It would be difficult to find a balance in the API that would allow it.

Related to #928. I will keep the discussion in that thread.


[Lake][ETL] DuckDB E2E - Ingestion -> Dashboards

Motivation
We completed the techspikes around our data infrastructure. As an outcome, we're going to implement our ETL pipeline in DuckDB such that we maintain many of our constraints:

We can test everything end-to-end (pytest, duckdb, plots)
We can reduce requirements on servers/infra/ops by using in-memory, embedded, on-disk db (duckb)
We can continue doing distributed computing (ray)
DB store can grow elastic w/ lvm, efs, filestore

Outline
Our first goal is to take the current ETL workflow and update it end-to-end.

Shelved Deliverables
CLOSED TICKET - Add ETL checkpoint to enforce SLAs, and process data incrementally. #694
Reason: We're going to instead implement a build step that leverages a simple SQL strategy w/ temp tables, such that we can enforce SLAs in a clean manner.
DoD
[First Deliverable - Update Ingestion + Load]

[x] Update GQL local/save-to-disk to use csv #681
[x] Fetch + insert new records into db #682

[Core System Updates]

[x] Improve ETL by using SQL build strategy & temp tables to enforce SLAs #771

[Update ETL Deliverables]

[x] DuckDB - Update existing logic that queries data from parquet using polars, to query_data from PersistentDataStore using SQL.
[x] DuckDB - Provide unifying etl_ view for ETL build steps. Downstream bronze and silver tables require data from both live_ and build_ tables. #810
[x] DuckDB - Update ETL "bronze step" to use duckdb/sql #738
[x] DuckDB - Clean up any final queries that fetch the whole database system. No select * from table_name anywhere. #809
[ ] DuckDB - Create logic to support an etl_view that joins both live + temp tables, making it easier to query data as it's being built #810
[ ] DuckDB - Port latest ETL "bronze slots" to use duckdb/sql #740
[ ] DuckDB - Port latest ETL "silver predictions" to use duckdb/sql + close old PR #741
[ ] DuckDB - Extend test coverage to simulate multiple runs, and cover more edge cases. #811

[Cleanup Deliverables]

[x] Cleanup DuckDB implementation, remove hanging dependencies, remove table.df caching, switching from parquet to CSV, cleanup tests. #737
[x] Clean truevalue and predvalue #664
[x] Improve CSVDataStore and PersistentDataStore instantiation inside Table #773
[x] Cleanup Tables, query them directly through CSVDataStore + PersistentDataStore #772
[ ] Update OHCLV Data Factory to use DataStores #769
[x] Remove reference to parquet_dir use lake_dir instead #770
[ ] Data Store Objects - Please rename functions to use sql nomenclature: fill becomes insert, override becomes upsert.

[ETL CLI Deliverables]

[ ] Update ETL CLI and provide a clean interface that helps enforce SLAs. #703

Discovered some issues related to data fetching on the main branch, because multiple things are rewritten in the ETF flow I leave them here in case they got solved along the way, if not maybe here would be the place to solve them:

Column don't match: "timestamp" and "tx_id" - solved if file is deleted

Error on saving data - solved if the gql command is rerun

Simply integrate the accuracy code when it's ready to go... until then, i'll be integrating the duckdb PR piece-by-piece.
https://github.com/oceanprotocol/pdr-backend/issues/1102

Closing this ticket and moving remaining items to some other ticket so i can reconcile outstanding issues.