text:
not yet implemented: Enum

Prerequisites

[x] I have checked the existing issues to ensure this is not a duplicate.
[x] I am running the latest version of Tailcall.

Describe the bug
A clear and concise description of what the bug is.
Steps to reproduce

Build complex proto with enum
Build tailcall config
Start tailcall

Expected behavior
Service started
Actual behavior
thread 'tokio-runtime-worker' panicked at src/json/json_schema.rs:190:17:
not yet implemented: Enum

Environment information:

Operating System:macOS 14.1.1 (23B81)
Tailcall Version: v0.50.0
Rust Version: _
GraphQL Client/version: _

I've tried to use release version to check how tailcall works, but I've got this error. I'm not really sure what kind of enum (definition or body) tailcall doesn't like.

@hazyone can you provide the configuration that you tried using?

Yes. Here it is. Unfortunately, I can't provide proto files.
schema
  @server(port: 8000, graphiql: true)
  @upstream(baseURL: "https://service.net", httpCache: true, batch: {delay: 10})
  @link(src: "./proto/service.proto", type: Protobuf) {
  query: Query
}

type Query {
  list(db: String): JSON @grpc(
  headers: [
        {key: "X-CUSTOM-HEADER", value: "custom-value"}
      ]
  method: "package.Service.Method.List"
  body: "{  \"targets\": [{ \"type\": 0, \"value\": \"site.com\"}], \"database\": \"{{args.db}}\",  ... }")
}

And also, backtrace:
not yet implemented: Enum
stack backtrace:
   0: _rust_begin_unwind
   1: core::panicking::panic_fmt
   2: <tailcall::json::json_schema::JsonSchema as core::convert::TryFrom<&prost_reflect::descriptor::FieldDescriptor>>::try_from
   3: <tailcall::json::json_schema::JsonSchema as core::convert::TryFrom<&prost_reflect::descriptor::MessageDescriptor>>::try_from
   4: <tailcall::json::json_schema::JsonSchema as core::convert::TryFrom<&prost_reflect::descriptor::FieldDescriptor>>::try_from
   5: <tailcall::json::json_schema::JsonSchema as core::convert::TryFrom<&prost_reflect::descriptor::MessageDescriptor>>::try_from
   6: tailcall::blueprint::operators::grpc::compile_grpc
   7: tailcall::blueprint::operators::grpc::update_grpc::{{closure}}
   8: tailcall::try_fold::TryFold<I,O,E>::trace::{{closure}}
   9: tailcall::try_fold::TryFold<I,O,E>::and::{{closure}}
  10: tailcall::try_fold::TryFold<I,O,E>::and::{{closure}}
  11: tailcall::try_fold::TryFold<I,O,E>::and::{{closure}}
  12: tailcall::try_fold::TryFold<I,O,E>::and::{{closure}}
  13: tailcall::try_fold::TryFold<I,O,E>::and::{{closure}}
  14: tailcall::try_fold::TryFold<I,O,E>::and::{{closure}}
  15: tailcall::try_fold::TryFold<I,O,E>::and::{{closure}}
  16: tailcall::try_fold::TryFold<I,O,E>::and::{{closure}}
  17: tailcall::blueprint::definitions::to_fields::{{closure}}
  18: tailcall::blueprint::definitions::to_definitions::{{closure}}
  19: tailcall::try_fold::TryFold<I,O,E>::transform_valid::{{closure}}
  20: tailcall::try_fold::TryFold<I,O,E>::and::{{closure}}
  21: tailcall::try_fold::TryFold<I,O,E>::and::{{closure}}
  22: tailcall::try_fold::TryFold<I,O,E>::and::{{closure}}
  23: tailcall::try_fold::TryFold<I,O,E>::and::{{closure}}
  24: tailcall::try_fold::TryFold<I,O,E>::transform_valid::{{closure}}
  25: tailcall::try_fold::TryFold<I,O,E>::transform_valid::{{closure}}
  26: tailcall::blueprint::from_config::<impl core::convert::TryFrom<&tailcall::config::config_module::ConfigModule> for tailcall::blueprint::blueprint::Blueprint>::try_from
  27: tailcall::cli::server::server::Server::start::{{closure}}
  28: tokio::runtime::task::raw::poll
  29: tokio::runtime::scheduler::multi_thread::worker::Context::run_task
  30: tokio::runtime::scheduler::multi_thread::worker::run
  31: tokio::runtime::task::raw::poll

Need to implement JsonSchema for the enum type, there is a Todo for it. Enum in JSON can be expressed as strings.
/bounty 250$

/attempt #1407

@ologbonowiwi are u working on this?

No @tusharmath, anyone else feel free to attempt

/attempt

authors: hazyone ologbonowiwi ssddOnTop tusharmath

repo: tailcallhq/tailcall


text:
chore: move tests to testconv

Summary:
Briefly describe the changes made in this PR.
Issue Reference(s):
Fixes #... (Replace "..." with the issue number)
Build & Testing:

[ ] I ran cargo test successfully.
[ ] I have run ./lint.sh --mode=fix to fix all linting issues raised by ./lint.sh --mode=check.

Checklist:

[ ] I have added relevant unit & integration tests.
[ ] I have updated the documentation accordingly.
[ ] I have performed a self-review of my code.
[ ] PR follows the naming convention of <type>(<optional scope>): <title>

I am strongly against this change as it makes no sense structurally.

source: gharchive/pull-request

authors: mogery ssddOnTop

license_type: permissive

license_source: github-api


text:
Using ResourceRecord as a HashMap key

New to Rust so this may not be necessary but I'm trying to build a cache and want to use ResourceRecord as a HashMap key. This requires it to have Hash, Eq, PartialEq traits. Can I impl these externally or is it better for dns-parser to derive these with struct definition?

Nevermind. Just realized the TTL will vary so I have to extract fields anyway.

source: gharchive/issue

repo: tailhook/dns-parser


text:
Top Command Similar to Tatsumaki

A command similar to functionality to that of t!top of the tatsumaki bot that assigns a score to people based upon general server activity (i think it gives out a point or smth randomly per message as to prevent spam increasing the score, i forget tho), so that we can all relish in how much time we've wasted our lives here.
This suggestion was created by a user and sent by the bot:
jukebox-botto#8602

not interested in adding such a feature

repo: tailoric/Pouty-Bot-Discord

license: MIT


text:
Does not work with Tailwind config option "important: true"

Or it doesn't write !importants into the finished css.

Only utility classes receive !important with the important option set. This plugin provides component classes, so they don't respect the important option. This is to make sure you can override the styles provided by these classes using utilities.

authors: adamwathan handplant

repo: tailwindcss/custom-forms


text:
Azure AD authentication

Hi, I'm new to GitBucket but it seems like a worthy replacement for Gitblit. I'm in the process of migrating our systems to the cloud, and one of those is our directory.
I see that GB already supports LDAP so it may be a logical next step to add support for Azure AD that also supports the OpenID and OAuth standards.
There are plenty of resources for doing this:
[ Docs ] [ Example ] [ Libs ]
What do you guys think?

Update: now Azure AD and MSA can be supported with the same API!
[ The Converged Microsoft Account and Azure Active Directory Programming Model ]

Now GitBucket supports OpenID Connect and may work with Azure AD.

repo: takezoe/gitbucket

license_source: bigquery


text:
run all_in_one.py,have a problem，ValueError: cannot reshape array of size 896 into shape (8,8,8,2)。 What should I do

please help me

I have the same issue, please help us fix it.

resize doesn't help... did you guys fix the problem??

authors: HunarAA LvNianZu graced03


text:
Tamagui Webpack Loader Error

Current Behavior
Tamagui Webpack Loader Error:
   Cannot read properties of undefined (reading 'tamaguiConfig')
TypeError: Cannot read properties of undefined (reading 'tamaguiConfig')
    at loadTamagui /node_modules/@tamagui/static/src/extractor/loadTamagui.ts:39:28)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Object.load [as loadTamagui] (/node_modules/@tamagui/static/src/extractor/createExtractor.ts:112:29)
    at extractToClassNames (/node_modules/@tamagui/static/src/extractor/extractToClassNames.ts:70:3)
    at Object.loader2 (/node_modules/tamagui-loader/src/loader.ts:60:23)

Expected Behavior
Compile without errors
Tamagui Version
1.15.38

Reproduction
tamagui.config.ts

import { config } from '@my/library';

export type Conf = typeof config;

declare module 'tamagui' {
  interface TamaguiCustomConfig extends Conf {}
}

export default config;

webpack.config
tsx

              loader: 'tamagui-loader',
              options: {
  config: './tamagui.config.ts',
  components: ['@my/library', 'tamagui'],
  disableExtraction: isDevelopment,
},

### System Info

_No response_

Latest release I added some safety but please run DEBUG=tamagui and send me logs

In 1.15.40 I see
Tamagui Webpack Loader Error:
   Cannot destructure property 'components' of 'undefined' as it is undefined.
TypeError: Cannot destructure property 'components' of 'undefined' as it is undefined.
    at parseWithConfig (/node_modules/@tamagui/static/src/extractor/createExtractor.ts:136:7)
    at Object.parse (/node_modules/@tamagui/static/src/extractor/createExtractor.ts:131:14)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at extractToClassNames (/node_modules/@tamagui/static/src/extractor/extractToClassNames.ts:94:15)
    at Object.loader2 (/node_modules/tamagui-loader/src/loader.ts:60:23)

Getting the same error

fixed in latest release

I really want to integrate this library in my project.  I've tried everything but I keep getting this error.
error -asdfi/node_modules/react-native/index.js:14
import typeof AccessibilityInfo from './Libraries/Components/AccessibilityInfo/AccessibilityInfo';
^^^^^^

SyntaxError: Cannot use import statement outside a module
    at internalCompileFunction (node:internal/vm:73:18)
    at wrapSafe (node:internal/modules/cjs/loader:1195:20)
    at Module._compile (node:internal/modules/cjs/loader:1239:27)
    at Module._extensions..js (node:internal/modules/cjs/loader:1329:10)
    at Module.load (node:internal/modules/cjs/loader:1133:32)
    at Module._load (node:internal/modules/cjs/loader:972:12)
    at Module.require (node:internal/modules/cjs/loader:1157:19)
    at require (node:internal/modules/helpers:119:18)
    at Object.<anonymous> (asdf/node_modules/@tamagui/use-keyboard-visible/dist/cjs/useKeyboardVisible.js:25:27)
    at Module._compile (node:internal/modules/cjs/loader:1275:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1329:10)
    at Module.load (node:internal/modules/cjs/loader:1133:32)
    at Module._load (node:internal/modules/cjs/loader:972:12)
    at Module.require (node:internal/modules/cjs/loader:1157:19)
    at require (node:internal/modules/helpers:119:18)
    at Object.<anonymous> (asdf/node_modules/@tamagui/use-keyboard-visible/dist/cjs/index.js:24:33)
    at Module._compile (node:internal/modules/cjs/loader:1275:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1329:10)
    at Module.load (node:internal/modules/cjs/loader:1133:32)
    at Module._load (node:internal/modules/cjs/loader:972:12)
    at Module.require (node:internal/modules/cjs/loader:1157:19)
    at require (node:internal/modules/helpers:119:18)
    at Object.<anonymous> (asdf/node_modules/@tamagui/sheet/dist/cjs/Sheet.js:40:35)
    at Module._compile (node:internal/modules/cjs/loader:1275:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1329:10)
    at Module.load (node:internal/modules/cjs/loader:1133:32)
    at Module._load (node:internal/modules/cjs/loader:972:12)
    at Module.require (node:internal/modules/cjs/loader:1157:19)
    at require (node:internal/modules/helpers:119:18)
    at Object.<anonymous> (asdf/node_modules/@tamagui/sheet/dist/cjs/index.js:25:25)
    at Module._compile (node:internal/modules/cjs/loader:1275:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1329:10)
    at Module.load (node:internal/modules/cjs/loader:1133:32)
    at Module._load (node:internal/modules/cjs/loader:972:12)
    at Module.require (node:internal/modules/cjs/loader:1157:19)
    at require (node:internal/modules/helpers:119:18)
    at Object.<anonymous> (asdf/node_modules/@tamagui/dialog/dist/cjs/Dialog.js:57:20)
    at Module._compile (node:internal/modules/cjs/loader:1275:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1329:10)
    at Module.load (node:internal/modules/cjs/loader:1133:32)
    at Module._load (node:internal/modules/cjs/loader:972:12)
    at Module.require (node:internal/modules/cjs/loader:1157:19)
    at require (node:internal/modules/helpers:119:18)
    at Object.<anonymous> (asdf/node_modules/@tamagui/dialog/dist/cjs/index.js:18:25)
    at Module._compile (node:internal/modules/cjs/loader:1275:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1329:10)
    at Module.load (node:internal/modules/cjs/loader:1133:32)
    at Module._load (node:internal/modules/cjs/loader:972:12)
    at Module.require (node:internal/modules/cjs/loader:1157:19)
    at require (node:internal/modules/helpers:119:18) {
  page: '/'
}

package.json
{
  "name": "asdf",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "postinstall": "npm run sylink-git-hooks",
    "prebuild": "echo 'prebuild'",
    "build": "next build",
    "dev": "next dev",
    "export": "next export",
    "lint": "next lint",
    "lintfix": "next lint --fix",
    "tslint": "tsc",
    "start": "next start",
    "prettier": "./node_modules/.bin/prettier --write ./src",
    "prettier-check": "./node_modules/.bin/prettier --check ./src",
    "sylink-git-hooks": "ln -s ../../git-hooks/pre-commit .git/hooks/pre-commit && ln -s ../../git-hooks/pre-push .git/hooks/pre-push"
  },
  "dependencies": {
    "@aws-amplify/ui-react": "^4.3.8",
    "@emotion/react": "^11.10.6",
    "@emotion/styled": "^11.10.6",
    "@expo/next-adapter": "^5.0.2",
    "@fortawesome/fontawesome-svg-core": "^6.3.0",
    "@fortawesome/free-regular-svg-icons": "^6.3.0",
    "@fortawesome/free-solid-svg-icons": "^6.3.0",
    "@fortawesome/react-fontawesome": "^0.2.0",
    "@headlessui/react": "^1.7.13",
    "@heroicons/react": "^2.0.16",
    "@mui/icons-material": "^5.11.16",
    "@mui/material": "^5.12.2",
    "@next/font": "13.1.6",
    "@tailwindcss/forms": "^0.5.3",
    "@tanstack/react-table": "^8.7.9",
    "@types/node": "18.13.0",
    "@types/react": "18.0.27",
    "@types/react-dom": "18.0.10",
    "@types/styled-components-react-native": "^5.2.1",
    "@visx/axis": "^3.1.0",
    "@visx/curve": "^3.0.0",
    "@visx/gradient": "^3.0.0",
    "@visx/grid": "^3.0.1",
    "@visx/group": "^3.0.0",
    "@visx/legend": "^3.0.0",
    "@visx/marker": "^3.0.0",
    "@visx/mock-data": "^3.0.0",
    "@visx/pattern": "^3.0.0",
    "@visx/scale": "^3.0.0",
    "@visx/shape": "^3.0.0",
    "@visx/text": "^3.0.0",
    "@visx/xychart": "^3.0.1",
    "aws-amplify": "^5.0.16",
    "clsx": "^1.2.1",
    "dotenv": "^16.0.3",
    "eslint": "8.33.0",
    "eslint-config-next": "13.1.6",
    "lodash.has": "^4.5.2",
    "lodash.set": "^4.3.2",
    "nativewind": "^2.0.11",
    "next": "13.1.6",
    "react": "18.2.0",
    "react-dom": "18.2.0",
    "react-native": "^0.71.7",
    "react-native-web": "^0.19.4",
    "react-redux": "^8.0.5",
    "react-spring": "^9.7.1",
    "redux": "^4.2.1",
    "redux-thunk": "^2.4.2",
    "styled-components": "^5.3.10",
    "tailwind-merge": "^1.10.0",
    "tamagui": "^1.26.0",
    "typescript": "4.9.5",
    "webpack": "^5.80.0"
  },
  "devDependencies": {
    "@react-native-community/eslint-config": "^3.2.0",
    "@total-typescript/ts-reset": "^0.3.7",
    "@types/lodash.has": "^4.5.7",
    "@types/lodash.set": "^4.3.7",
    "@typescript-eslint/eslint-plugin": "^5.59.0",
    "@typescript-eslint/parser": "^5.59.0",
    "autoprefixer": "^10.4.13",
    "eslint-config-prettier": "^8.8.0",
    "eslint-plugin-prettier": "^4.2.1",
    "eslint-plugin-react-native": "^4.0.0",
    "eslint-plugin-react-perf": "^3.3.1",
    "eslint-plugin-tailwindcss": "^3.10.1",
    "postcss": "^8.4.21",
    "prettier": "^2.8.4",
    "prettier-plugin-tailwindcss": "^0.2.7",
    "tailwindcss": "^3.2.7"
  }
}

next.config.js
const { withExpo } = require('@expo/next-adapter');

/** @type {import('next').NextConfig} */
const nextConfig = {
  swcMinify: true,
  transpilePackages: [
    'react-native',
    'nativewind',
  ],
  experimental: {
    forceSwcTransforms: true,
    fullySpecified: false,
    esmExternals: 'loose'
  },
  reactStrictMode: true,
  images: {
    unoptimized: true,
  },
  webpack(config) {
    config.module.rules.push({
      test: /\.m?js$/,
      type: 'javascript/auto',
      resolve: {
        fullySpecified: false,
      },
    })
    return config
  },
};

module.exports = withExpo(nextConfig);

Why aren’t you using the next plugin?
You need to alias react-native to react-native-web

Thank you very much. I got it to work.
I don't know if it has due to my particular NextJS setup, but the Tamagui documentation for NextJS setup was misleading by saying:
"For a minimal setup with just @tamagui/core, you can get away with this configuration: [shows minimal next.config]"
I did have to setup @tamagui/next-plugin in my next.config as you suggested, and is described here : https://tamagui.dev/docs/guides/next-js#nextconfigjs
But the @tamagui/next-plugin section says, "For a more complete configuration," and for me, it was mandatory.
I also had to setup TamaguiProvider as described on that linked docs page.

authors: brianephraim clayrisser natew seeden

repo: tamagui/tamagui


text:
No syntax highlighting on One Dark Pro

Hi, thank you for the extension. It works great - except that I don't have any syntax highlighting on the One Dark Pro theme. It seems to work on other themes though.

Hi, it's a theme issue, I can't do much about it. We use the same scope as JSON keys, but the theme seems to have a color override explicitly for JSON only.
You can either fix the theme or set a color for support.type.property-name.toml manually.

authors: stingalleman tamasfe

repo: tamasfe/taplo


text:
Taplo CLI doesn't validate schemas if using schema catalog and cache and cache is existed

Taplo CLI doesn't validate schemas if using schema catalog (--default-schema-catalogs, --schema-catalog <SCHEMA_CATALOG>) and --cach-path and Taplo cache is existed.
If use schema instead of schema catalog, that is, if using --schema <SCHEMA> and --cach-path and Taplo cache is existed, Taplo CLI validates schemas.
reproduce.sh
#!/usr/bin/env bash

wget --quiet --output-document taplo.gz https://github.com/tamasfe/taplo/releases/download/0.8.1/taplo-linux-x86_64.gz
gzip --decompress taplo.gz
chmod +x ./taplo
./taplo --version

declare toml_file='release-plz.toml'
echo -e '[[package]]\nname = 1' > "$toml_file"

set -x
./taplo lint --cache-path ./ --default-schema-catalogs "$toml_file"
ls

./taplo lint --cache-path ./ --default-schema-catalogs "$toml_file"
./taplo lint --cache-path ./ --schema-catalog https://www.schemastore.org/api/json/catalog.json "$toml_file"
./taplo lint --cache-path ./ --schema https://raw.githubusercontent.com/MarcoIeni/release-plz/main/.schema/latest.json "$toml_file"

Result
$ bash reproduce.sh
taplo 0.8.1
+ ./taplo lint --cache-path ./ --default-schema-catalogs release-plz.toml
INFO taplo:lint_files:collect_files: found files total=1 excluded=0 cwd="/home/hituzi_no_sippo/taplo_schema"
error: 1 is not of type "string"
┌─ /home/hituzi_no_sippo/taplo_schema/release-plz.toml:2:8
│
2 │ name = 1
│        ^ 1 is not of type "string"

ERROR taplo:lint_files: invalid file error=schema validation failed path="/home/hituzi_no_sippo/taplo_schema/release-plz.toml"
ERROR operation failed error=some files were not valid
+ ls
5b16e32f1334ff5b75ab387d99f1de40eeea4924  f6c331111c3dbf4da601b1da5a14bb49b3f362f0  release-plz.toml  reproduce.sh  taplo
+ ./taplo lint --cache-path ./ --default-schema-catalogs release-plz.toml
INFO taplo:lint_files:collect_files: found files total=1 excluded=0 cwd="/home/hituzi_no_sippo/taplo_schema"
+ ./taplo lint --cache-path ./ --schema-catalog https://www.schemastore.org/api/json/catalog.json release-plz.toml
INFO taplo:lint_files:collect_files: found files total=1 excluded=0 cwd="/home/hituzi_no_sippo/taplo_schema"
+ ./taplo lint --cache-path ./ --schema https://raw.githubusercontent.com/MarcoIeni/release-plz/main/.schema/latest.json release-plz.toml
INFO taplo:lint_files:collect_files: found files total=1 excluded=0 cwd="/home/hituzi_no_sippo/taplo_schema"
error: 1 is not of type "string"
┌─ /home/hituzi_no_sippo/taplo_schema/release-plz.toml:2:8
│
2 │ name = 1
│        ^ 1 is not of type "string"

ERROR taplo:lint_files: invalid file error=schema validation failed path="/home/hituzi_no_sippo/taplo_schema/release-plz.toml"
ERROR operation failed error=some files were not valid
$

System

OS Ubuntu 20.04 LTS (WSL2)
Version: taplo 0.8.1

Thanks.

Thanks for the bug report! I can reproduce. This looks indeed like a cache-related bug. It will need some investigation.

After investigation, the problem was that before being used, the index was transformed, such that the pattern was **/release-plz.toml instead of release-plz.toml. But this transformation was not saved to the cache and was not applied neither when loading from the cache, and thus no schema was found for the file.

You can install the latest version with cargo install taplo-cli --git=https://github.com/tamasfe/taplo.git --features=lsp.

You can install the latest version with cargo install taplo-cli --git=https://github.com/tamasfe/taplo.git --features=lsp.

I've checked.
Thank you.


text:
Auto start on Amazon EC2 simple linux

Hi,
Just wanted to share how I managed to start MySQL and Traccar on an Amazon EC2 linux (Traccar install does not setup auto start on this linux).  Sure there must be other (and better) ways:
Edit /etc/rc.local and add the following lines:
service mysqld start
/opt/traccar/bin/traccar start

By Amazon EC2 linux you mean Amazon Linux AMI?
I guess better way is to ask Java Service Wrapper team to add support for it:
https://sourceforge.net/p/wrapper/discussion/122338/

Yes, Amazon Linux AMI.
Ok. Thanks!

authors: peptoni tananaev

repo: tananaev/traccar


text:
doesn't support chinese bw08

2017-08-10 00:38:48 DEBUG: [D657D0B4: 5023 < 223.104.63.179] HEX: 78780a13440404002d02e47f6d0d0a
2017-08-10 00:39:00  INFO: [D657D0B4] disconnected
2017-08-10 00:39:01  INFO: [93277F37] connected
2017-08-10 00:39:02 DEBUG: [93277F37: 5023 < 223.104.63.179] HEX: 78780d01088888888888888802e694840d0a
2017-08-10 00:39:02  WARN: Unknown device - 888888888888888 (223.104.63.179)
2017-08-10 00:39:08 DEBUG: [93277F37: 5023 < 223.104.63.179] HEX: 78780a13440404002d02e74df60d0a
2017-08-10 00:39:18  INFO: [93277F37] disconnected
2017-08-10 00:39:20  INFO: [2CB50BB6] connected
2017-08-10 00:39:20 DEBUG: [2CB50BB6: 5023 < 223.104.63.179] HEX: 78780d01088888888888888802e96c730d0a
2017-08-10 00:39:20  WARN: Unknown device - 888888888888888 (223.104.63.179)
2017-08-10 00:39:29 DEBUG: [2CB50BB6: 5023 < 223.104.63.179] HEX: 78780a13440404002d02ea96130d0a
2017-08-10 00:39:38  INFO: [2CB50BB6] disconnected
2017-08-10 00:39:39  INFO: [D6942FB9] connected
2017-08-10 00:39:39 DEBUG: [D6942FB9: 5023 < 223.104.63.179] HEX: 78780d01088888888888888802ec3bde0d0a
2017-08-10 00:39:39  WARN: Unknown device - 888888888888888 (223.104.63.179)
2017-08-10 00:39:49 DEBUG: [D6942FB9: 5023 < 223.104.63.179] HEX: 78780a13440404003102edc29a0d0a
2017-08-10 00:39:58  INFO: [D6942FB9] disconnected
2017-08-10 00:39:59  INFO: [67992057] connected
2017-08-10 00:39:59 DEBUG: [67992057: 5023 < 223.104.63.179] HEX: 78780d01088888888888888802ef09450d0a
2017-08-10 00:39:59  WARN: Unknown device - 888888888888888 (223.104.63.179)
2017-08-10 00:40:09 DEBUG: [67992057: 5023 < 223.104.63.179] HEX: 78780a13440404003102f009fe0d0a
2017-08-10 00:40:18  INFO: [67992057] disconnected
2017-08-10 00:40:19  INFO: [E0EAEA89] connected
2017-08-10 00:40:19 DEBUG: [E0EAEA89: 5023 < 223.104.63.179] HEX: 78780d01088888888888888802f2c2210d0a
2017-08-10 00:40:19  WARN: Unknown device - 888888888888888 (223.104.63.179)
2017-08-10 00:40:31 DEBUG: [E0EAEA89: 5023 < 223.104.63.179] HEX: 78780a13440404003102f33b650d0a

You haven't registered your device in the system, as "Unknown device" warning clearly indicates.

what is port of this device

what does mean it ?
HEX 2411023063421140281008174224272200107340869f000122fffffbffff0040

authors: Naranmandakh tananaev


text:
eelink - Mute certain alerts when ignition is on

Not so much a problem as the system is doing exactly what its told.
Eelink devices still give certain alerts ie vibration even though ignition is on so its up to the online platform to handle these appropriately. So when I start and leave home in the morning I can get three notices, Ignition On, Vibration (when i start moving), geofence out and while I am out if I happen to stop moving for a few mins then start again (Ignition always on) i can get another vibration alert.
Currently traccar does not seem to support if/then/else notification rules so I am wondering what is the best way to do this other than change the protocol decoder (or create a custom version for my purpose)? I was thinking attributes on either the notification or device, ie ignoreIfIgnitonOn:true.

There is no explicit option, but you can probably use computed attributes to clear alarm if ignition is ON.

How did you go with the solution tsmgeek? I get accident alarm constantly riding my bike when I hit any large bump on the road. Extremely annoying. I was wondering if the following computed attribute would work?
alarm == "accident" ? "85" : null

Send WARNING,180# to your tracker. It turns off crash and freefall alerts
which are useless on bikes as give too many false positives.
On 15 Oct 2017 07:14, "Paul" notifications@github.com wrote:
How did you go with the solution tsmgeek? I get accident alarm constantly
riding my bike when I hit any large bump on the road. Extremely annoying. I
was wondering if the following computed attribute would work?
alarm == "accident" ? "85" : null
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tananaev/traccar/issues/3550#issuecomment-336689256,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFlqlBhFiVxeZcCobHgQtGvmrv3t4FSlks5ssaLFgaJpZM4Plgms
.

Thanks! Will give it a try.

Seemed to do the trick. Please send me an email paul.briggs@gmail.com, would like to discuss further with you on the subject of the eelink devices.

@briggz84 send me a message to tsmgeek@gmail.com what you would like to know about them.

@tananaev @briggz84
I have looked into doing this with computed attributed and have come to conclusion that its not possible for a few reasons.
This is the JEXL code I was testing with alarm ? ignition == true && alarm == "vibration" ? null : alarm : null

eelink alert packets 0x04 do not  pass the general status of the device which are supplied in 0x02, newer V2 protocol has changed this in the 0x14 warning packet which is currently correctly supported in the update I did to the proto decoder.
current decoder does not load the last packet data for things like alert/warning packets, this means you cant run computed attributes unless the latest packet also includes the values you are checking. I think I corrected this in my update to the proto decoder, ie for things like 0x04/0x14 packets it will load the last logged track then add the changes to it.
I may just add a flag in the decoder to easily set certain conditions ie Ignore Device Events If Ignition On.

I need to re-merge in the latest alterations that were done to the decoder into mine and it would need to be merged into master.

@tananaev  Does 'Processing: Copy Attributes' under device attributes, does this copy all the attributes are copied from current track to latest track that is being processed, so like a base set of attributes to which the new ones are merged in?

You need to specify list of attributes to copy.

I'm having a similar problem with my bike triggering crash smses (and external power shutdown! - it nuked my battery, so I moved it all to acc)
I've poked around, the eelink v2 protocol doc says if the message is empty then it won't send the SMS but I can't find a way to tell traccar to send back the empty message.
Is there a way to do this?

authors: briggz84 freman tananaev tsmgeek


text:
IOS-6170: [Crashlytics] [New Fatal Issue] [Tangem] MultiWalletMainContentViewModel.swift - closure #2 in MultiWalletMainContentViewModel.bind()

https://tangem.atlassian.net/browse/IOS-6170
Похоже что convertToSections и removeOldCachedTokenViewModels одновременно пытались изменить проперти cachedTokenItemViewModels у вьюмедели с разных потоков

Я в другой своей задаче замерял время и конвертация моделей даже для короткого списка токенов занимала весьма существенное время - поэтому если делать ее на мейне то вероятно будут лаги

Я в другой своей задаче замерял время и конвертация моделей даже для короткого списка токенов занимала весьма существенное время - поэтому если делать ее на мейне то вероятно будут лаги

Заменил main на кастомную последовательную, по аналогии с mappingQueue

Я в другой своей задаче замерял время и конвертация моделей даже для короткого списка токенов занимала весьма существенное время - поэтому если делать ее на мейне то вероятно будут лаги

Заменил main на кастомную последовательную, по аналогии с mappingQueue

Судя по коду - доступк к этому словарю и так происходит на последовательной очереди (mappingQueue), поэтому надо разобраться, откуда тут взялся main - а не просто добавлять +1 очередь (на которой кстати и будет в таком случае происходить маппинг вместо mappingQueue)

@amuraveinik не надо мержить с подобными открытыми вопросами, либо разбираемся либо ревертим

repo: tangem/tangem-app-ios


text:
Draw new icons for priority outdoor POIs

Replace generic sprites with custom artwork. Followup to #1.

[x] trailhead (example)
[x] ranger_station (example and 2)
[x] caravan_site - RV campground (example)
[ ] picnic_table (example)
[x] picnic_site - can have same icon as picnic_table  (example)
[x] monument – we can reuse icon from landmark, no special recolouring though (example)
[x] bbq (example)
[x] dog_park (example)
[x] firepit  (example)
[x] swimming_area (example)
[x] waterfall (example)
[ ] fishing_area (example) NOTE: was incorrectly specified here as fishing_spot before.
[ ] slipway - boat ramp (example)
[x] shower (example)

All of the above have icons, but the 3 unchecked example links don't show them: picnic_table, fishing_area and slipway

Woot!

authors: nvkelso sensescape

repo: tangrams/outdoor-style

license: mit


text:
Browser extension support

It would be good to have an extension/addon in browser for the devtools.

The ReactQueryDevtools component requires access to queryCache from react-query to get all the queries related data.
Getting access to the same queryCache in the context of an extension is required for building a functioning extension.
I was thinking if we can put the queryCache object in window and access that object instead of one from query-cache. Not sure if this is something that can make the devtools work in extension.

This package has already been a huge help to me for debugging purposes, but I agree that it'd be great to have a browser extension, kind of like the redux-devtools-extension that exposes a global __REDUX_DEVTOOLS_EXTENSION_COMPOSE__ variable to hook into the Redux store creation.  (If we can just get away with exposing the queryCache, I think that'd be enough in this case.)
The styled components, floating mode, and style + className props are useful, but I find myself running into some weird overlapping styles that could be avoided from the start by breaking this out into a separate extension altogether.  I'm going to try to get a proof of concept together when I get some free time.

This is likely not going to happen soon, unless someone is willing to write all of the bridge code. Closing for now.

authors: ayush987goyal stephenkao tannerlinsley

repo: tannerlinsley/react-query-devtools


text:
Change precedence in 'getResolvedState'

Previously existing props would overwrite passed in state
Now passed in state gets precedence

I'm unsure of the implications of doing this.  It seems to be right, but this could affect a lot of internals.  Have you tested each story in the storybook thoroughly to ensure this will be okay?

I'll take a look through the storybook tonight and make sure it's covered. If I remember correctly the function only gets called with args in one other instance. Thanks for the feedback, I'll update with my findings soon.

From what I can tell, the only other call to getResolvedState() that passes arguments is in componentWillReceiveProps(). Line 39 in lifecycle.js accepts nextState as the 2nd argument. In this case nextState represents the React context which I don't believe ReactTable is currently setup to consume so nextState is always the Object prototype.
Currently the precedence goes: new props -> previous props -> context -> component state
This PR would change that to: new props -> context -> previous props -> component state
Since ReactTable doesn't use context right now, swapping it with previous props won't have any effect on current operation but I can see why some might want to keep it the way it is. If that's the case then the call to getResolvedState on line 65 of lifecycle.js would need to swap the order of arguments. That may come with other side effects that would still need to be investigated. Either approach would resolve #163 however.
FWIW I ran through the storybook and didn't run into any issues with the change in this PR. There aren't any stories for fully controlled components however. If I have some time I'll try to add one or two.
Thoughts?

If you could add a fully controlled story entry then I think we're good to
merge :)
On Tue, Apr 4, 2017 at 6:53 PM Eric Abbott notifications@github.com wrote:

From what I can tell, the only other call to getResolvedState() that
passes arguments is in componentWillReceiveProps(). Line 39 in lifecycle.js
accepts nextState as the 2nd argument. In this case nextState represents
the React context which I don't believe ReactTable is currently setup to
consume so nextState is always the Object prototype.
Currently the precedence goes: new props -> previous props -> context ->
component state
This PR would change that to: new props -> context -> previous props ->
component state
Since ReactTable doesn't use context right now, swapping it with previous
props won't have any effect on current operation but I can see why some
might want to keep it the way it is. If that's the case then the call to
getResolvedState on line 65 of lifecycle.js would need to swap the order of
arguments. That may come with other side effects that would still need to
be investigated. Either approach would resolve #163
https://github.com/tannerlinsley/react-table/issues/163 however.
FWIW I ran through the storybook and didn't run into any issues with the
change in this PR. There aren't any stories for fully controlled components
however. If I have some time I'll try to add one or two.
Thoughts?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/tannerlinsley/react-table/pull/166#issuecomment-291693978,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFUmCUM7KPXOjkJGfBpXGyi4e50WxpEgks5rsuYWgaJpZM4MyNs4
.

Added a story entry with controlled sorting, page, and pageSize. Everything seems to be working as expected. If you were to revert commit 383554d2 you would see the behavior described in #163 and #145

Stupendous! You rock man. Merging this now.

authors: abbotteric tannerlinsley

repo: tannerlinsley/react-table


text:
Opengraph summaries for shared chats have body-main uses aria-hidden=true

As it says in the title, opengraph summaries for shared chats have body-main uses aria-hidden=true
This causes an accessibility problem for users of screen readers.

this would be a good first fix to drop all attributes from main tag. For bonus points would be good to fix yaml to retain newlines when rendered in browser

authors: bronaugh tarasglek


text:
SqlClient PlatformNotSupported_DataSqlClient

Very excited about this app! Went ahead and installed it on my x86 mac running macOS 13.4.1 with dotnet version 6.0.301 and efcore tools 7.0.9. I'm able to connect to my local Sql Server running in a docker container and can view the db schema in the left hand pane. When I try to run a LINQ query against that database I get the following error. Have I not configured things correctly somehow?
System.PlatformNotSupportedException: Strings.PlatformNotSupported_DataSqlClient
   at Microsoft.Data.SqlClient.SqlConnectionStringBuilder..ctor(String connectionString)
   at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerConnection.<>c.<get_IsMultipleActiveResultSetsEnabled>b__7_0(String cs)
   at System.Collections.Concurrent.ConcurrentDictionary`2.GetOrAdd(TKey key, Func`2 valueFactory)
   at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerConnection.get_IsMultipleActiveResultSetsEnabled()
   at Microsoft.EntityFrameworkCore.SqlServer.Query.Internal.SqlServerCompiledQueryCacheKeyGenerator.GenerateCacheKey(Expression query, Boolean async)
   at Microsoft.EntityFrameworkCore.Query.Internal.QueryCompiler.Execute[TResult](Expression query)
   at Microsoft.EntityFrameworkCore.Query.Internal.EntityQueryProvider.Execute[TResult](Expression expression)
   at Microsoft.EntityFrameworkCore.Query.Internal.EntityQueryable`1.System.Collections.IEnumerable.GetEnumerator()
   at O2Html.Common.LazyEnumerable.Enumerate[T](IEnumerable collection, Nullable`1 maxItemsToEnumerate, Action`2 action)
   at O2Html.Converters.CollectionHtmlConverter.Convert[T](T obj, Type type, SerializationScope serializationScope, HtmlSerializer htmlSerializer)
   at O2Html.Converters.CollectionHtmlConverter.WriteHtml[T](T obj, Type type, SerializationScope serializationScope, HtmlSerializer htmlSerializer)
   at O2Html.HtmlSerializer.Serialize[T](T obj, Type type, SerializationScope serializationScope)
   at O2Html.HtmlConvert.Serialize[T](T obj, HtmlSerializerSettings htmlSerializerSettings)
   at NetPad.Html.HtmlSerializer.Serialize(Object output, String title, Boolean isError)

Thank you for reporting this issue. I don't think that's anything you're doing incorrectly, I'll look into this. Out of curiosity do you see the same issue if you use v0.4.0?
Glad you're enjoying the app!

I found the issue, there are MS SQL specific assemblies missing from the Mac build. I will release a hotfix release soon.

Until the hotfix is released, to immediately fix this issue, extract this and copy the Assets folder to /path/to/NetPad.app/Contents/Resources/bin
MissingAssemblies.zip

Thanks for digging into this!

authors: jkdufair tareqimbasher

repo: tareqimbasher/NetPad


text:
Error using gtsam.noiseModel.mEstimator.Huber.Create (line 75)

Matlab output :
Error using gtsam.noiseModel.mEstimator.Huber.Create (line 75)

Exception from gtsam:
active expects 1 arguments, not 0

Error in parameters (line 83) %
prm.P_kernel = huber(prm.P_robust_prm); % Huber kernel

Error in fgo_gnss_imu (line 35) %
prm = parameters(setting, initflag); % Processing parameter

Error in run_fgo (line 28)
parfor i=1:n

Files involved :
gtsam\build\wrap\gtsam+gtsam+noiseModel+mEstimator\Huber.m
gsdc2023-main\parameters.m
gsdc2023-main\fgo_gnss_imu.m
and run_fgo.m
Thank you !

I have replied to this issue, but please wait a little longer as I am currently preparing a tutorial on building on a Windows environment.
If you want to test the operation of the MATLAB wrapper for gtsam built on Windows, I think it would be a good idea to use gtsam/matlab/gtsam_test and gtsam/matlab/example to check that it works.

authors: Oussamaaat taroz


text:
Owner Login

Expected behavior:
I added a few location owners and assigned those to a location. When I log in the owner should see orders and the menu on the left side menu to edit, delete items, right?
Actual behavior:
When I log in with an owner account, my left side menu is completely empty - only the dashboard appears.
Reproduce steps:
I guess 3.0.0 - where excactly can I find this information?
Version:
3.0.0
Additional Information:
NONE

After creating the users, you need to set their permissions giving them access to specific parts of the system. Go to Users > Staff > Staff Groups.
Next time please post your questions on the forums, use issues to report bugs.

Thank you so much for the fast response. Works perfect - I did not recognize the tab. Sorry 'bout that.

repo: tastyigniter/TastyIgniter


text:
IsSchoolHoliday or IsSchoolHolidays

Hi,
I love this plugin, but
I can't find when the last update was made, but during the last few days, did you change the IsSchoolHoliday variable to IsSchoolHolidays (with an S) ?
THanks
Regards

Hi @fdecourt ,
Thanks for you comment.
The update was done on version 1.1.0
https://github.com/tataille/node-red-french-holidays/releases/tag/1.1.0
Regards

OK, greats, thanks for the information.
Regards

authors: fdecourt tataille

repo: tataille/node-red-french-holidays


text:
[ENH] add outputs & configs form dolphin 2.2.1

cc @gblazex for next models can you do a PR with a few configs (link / model name / and ideally some decoding parameters).
I'm evaluating the model now!

cc @gblazex done

thank you @YannDubs
I created a new pull with matching config, so it can be reproduced
https://github.com/tatsu-lab/alpaca_eval/pull/212

authors: YannDubs gblazex


text:
Unexpected result with findall/3

For the following program in http://tau-prolog.org/sandbox/
test :-
    findall([A,_],p(A,_),L),
    write(L),
    nl.

p(a,b).
p(c,d).
p(e,f).

the query
test.

gives
[[a,__2],[c,__2],[e,__2]]

whereas the expectation is somtehing like
[[a,_2],[c,_3],[e,_4]]

@jariazavalverde Looking at the fix, the bug is only on the top-level printing of query bindings, correct?

the bug is only on the top-level printing of query bindings

@pmoura I'm not sure I'm getting this right. It wasn't just a printing problem: if a variable was subsequently instantiated, all of them were instantiated.
Before:

Now:

I have not yet update my local installation with the fix. I get:
?- assertz(f(_, 1)).
true.

?- assertz(f(_, 2)).
true.

?- findall(Var, f(Var, _), [X, Y]), X \== Y.
true.

?- findall((A1,A2), f(A1,A2), [(B1,1),(B2,2)]), B1 \== B2.
true.

I'm trying to define one or more additional Logtalk tests for the findall/3 predicate based on @josd finding and example code.

In https://github.com/IDLabResearch/Webeye/blob/master/examples/fourcolor.pl#L6
originally had findall([Place,_],'https://idlabresearch.github.io/ns#neighbours'(Place,_),Places),
and that now works fine!

@pmoura Try with a variable not in the goal. You should get something like:
?- assertz(f(1)).
true.

?- assertz(f(2)).
true.

?- findall((B,A), f(A), [(B1,1),(B2,2)]), B1 \== B2.
false.

That clarifies it, thanks. Test added (https://github.com/LogtalkDotOrg/logtalk3/commit/72f5836dc190ccae4a4280c5085ac8981132aa3f).

Couldn't reopen this issue but it is again occuring in 0.3.3

Fixed again. Thanks.

Thanks a lot and now we get the correct results in https://github.com/josd/eyebrow/commit/95946ec831fa8d960900cc73d611c6c89bf12ee0

Tests exist that can prevent these regressions... running them before a new release would be a good idea. The whole testing process can also be automated using a GitHub workflow. A good example is https://github.com/trealla-prolog/trealla/blob/main/.github/workflows/compliance.yml

authors: jariazavalverde josd pmoura

repo: tau-prolog/tau-prolog


text:
[bug] Cannot Create New rc-0 App With create-tauri-app

Describe the bug
Following the directions here:  https://v2.tauri.app/start creates a Tauri v1 app instead of a Tauri v2 rc0 app
$ yarn create tauri-app --rc
yarn create v1.22.22
warning package.json: No license field
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
[4/4] 🔨  Building fresh packages...
success Installed "create-tauri-app@4.0.3" with binaries:
      - create-tauri-app
[##########################################################################] 74/74? Choose which language to use
✔ Choose which language to use for your frontend · TypeScript / JavaScript - (pnpm, yarn, npm, bun)
✔ Choose your package manager · yarn
✔ Choose your UI template · React - (https://react.dev/)
✔ Choose your UI flavor · JavaScript

Template created! To get started run:
  cd --rc
  yarn
  yarn tauri dev

✨  Done in 11.57s.
$

Reproduction
Follow the directions here:  https://v2.tauri.app/start  to create a new Tauri v2 rc0 app
Expected behavior
It should create a new Tauri v2 rc0 app
Full tauri info output
$ yarn tauri info
yarn run v1.22.22
warning ../package.json: No license field
$ tauri info

[✔] Environment
    - OS: Mac OS 14.6.0 X64
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.80.0 (051478957 2024-07-21)
    ✔ cargo: 1.80.0 (376290515 2024-07-16)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-aarch64-apple-darwin (default)
    - node: 18.18.0
    - pnpm: 9.0.5
    - yarn: 1.22.22
    - npm: 9.8.1
    - bun: 1.1.7

[-] Packages
    - tauri [RUST]: 1 (no lockfile)
    - tauri-build [RUST]: no manifest (no lockfile)
    - wry [RUST]: no manifest (no lockfile)
    - tao [RUST]: no manifest (no lockfile)
    - @tauri-apps/api [NPM]: 1.6.0
    - @tauri-apps/cli [NPM]: 1.6.0

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../dist
    - devPath: http://localhost:1420/
    - framework: React
    - bundler: Vite
✨  Done in 2.84s.

Stack trace
No response
Additional context
No response

Are you on the latest version of create-tauri-app? https://github.com/tauri-apps/create-tauri-app/pull/747 4.1 introduced the rc flag.
    - @tauri-apps/api [NPM]: 1.6.0
    - @tauri-apps/cli [NPM]: 1.6.0

Is this executed in the created application folder?
You don't have the tauri 2.x cli installed which is required for 2.0.rc, which should be installed to the project once you run the yarn install inside the generated project.

Are you saying that this is a documentation bug?  I followed the instructions provided. I have Rust and Node and Xcode installed.  Where does it say that I need create-tauri-app v4.1 ?

No, I was just asking if you have followed the instructions from the website recently or some days ago as a recent release introduced the rc flag and not sure how the behavior was before.
I just tested with a clean system to follow the start guide and it worked fine here. It installs the 2.0rc cli and works for me. So my guess was your local cta version is older, which does not support the --rc flag.
Just noticed my suspicion was correct: success Installed "create-tauri-app@4.0.3" with binaries:
Please either update create-tauri-app or re-follow the instructions from the website.

I followed the instructions in the documentation. I guess this is a documentation bug.  As you can see here (below), others are having the same problem. Merely adding a single sentence to this page:  https://v2.tauri.app/start/
that says something like:  You need create-tauri-app v4.1 or newer will safe many people a lot of time.

For people followin the guide the first time there is no need to check the version.
I agree that it's not working if you have installed the tool before the latest release and do not update before usage. Will change the packet manager instructions to update to the latest version.

Can't reproduce on my system with yarn, as it installs the latest version (4.1 automatically).
Have you retried in the last 7 hours?
yarn create tauri-app --rc
yarn create v1.22.22
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Installed "create-tauri-app@4.1.0" with binaries:
      - create-tauri-app
[####] 4/4name (tauri-app) ›

I have tested with npm, bun, and yarn and it's working fine.
However, for pnpm it's still currently not working. It does not ask for the project name and creates a '--rc' directory.

No longer seeing issue with pnpm.

authors: slimandslam trspro67 tweidinger

repo: tauri-apps/tauri


text:
[bug] pick_file crashed in macos

Describe the bug
#[tauri::command]
pub fn import_data() {
    let file_path_buf = dialog::blocking::FileDialogBuilder::new()
        .add_filter("JSON", &["json"])
        .pick_file()
        .unwrap();
    let file_path = file_path_buf.as_path().to_str().unwrap();
    println!("{}", file_path);
}

when i invoke this command,main thread is blocking,and can't find any dialog.
And if using dialog::FileDialogBuilder worked,but i just want to use sync method.
Reproduction
No response
Expected behavior
No response
Platform and versions
Environment
› OS: Mac OS 12.5.1 X64
› Node.js: 16.7.0
› npm: 7.20.3
› pnpm: 7.13.2
› yarn: 1.22.18
› rustup: 1.25.1
› rustc: 1.63.0
› cargo: 1.63.0
› Rust toolchain: stable-aarch64-apple-darwin
Packages
› @tauri-apps/cli [NPM]: 1.2.0
› @tauri-apps/api [NPM]: 1.2.0
› tauri [RUST]: 1.2.0,
› tauri-build [RUST]: 1.2.0,
› tao [RUST]: 0.15.3,
› wry [RUST]: 0.22.0,
App
› build-type: bundle
› CSP: unset
› distDir: ../dist
› devPath: http://localhost:1420/
› framework: React
App directory structure
├─ dist
├─ node_modules
├─ public
├─ src-tauri
├─ .git
├─ .vscode
├─ .idea
└─ src
Stack trace
No response
Additional context
No response

You must make the command async (pub async fn or #[command(async)]) to make it work.
We probably should make the wording in the docs a bit more aggressive since we're dealing with platform limitations here.

I think exmaple code should be updated. Thanks

Oh yeah, good call!


text:
docs: Fix api.js docs pipeline with updated typedoc dependencies

What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[x] Docs
[ ] New Binding issue #___
[ ] Code style update
[ ] Refactor
[x] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change?

[ ] Yes, and the changes were approved in issue #___
[x] No

Checklist

[x] When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
[x] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
[x] I have added a convincing reason for adding this feature, if necessary

Other information
This was what broke the publishing pipeline when we tried to release 1.3 - it should work now but i'll also need to see if the docs are still correct by integrating it into tauri-docs before we merge this since the js-api.json file is much bigger now and i'm not sure yet if that's correct...

Okay looks like they just changed the output format a bit. Content itself looks fine and since we don't actively use the json output yet the change won't affect us.
The actual docs on tauri.app will still be generated with 0.23 though since our fork of the markdown plugin diverged from upstream too much and i can't (and don't want to) figure it out how to update it right now.


text:
bug(macos):  Unable to move background with with_movable_by_window_background

https://github.com/atom/atom/pull/10208
There's a bunch of history regarding this one in the Electron world on how to "hide decorations but keep the traffic lights around."
I think a slight tweak in the flags would allow two types of decorations (title bar, and the traffic lights).

Do we need to propagate drag and drop event from wkwebview to nswindow like https://stackoverflow.com/a/54987061 ?

@keiya01 worth giving it a try I guess. I'm not fond of additional drop handler either.

authors: jkelleyrtp keiya01 wusyong

repo: tauri-apps/wry


text:
feat/distance-to-number

Please review before merging.

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

repo: taxi-gestion/client


text:
Support Faraday 2.x

The gem depends on faraday_middleware, which means that it only works with Faraday 1.x; it would be swell if it supported Faraday 2.x, too.

Most recent gem version supports Faraday 2.x!

It looks like you missed one reference.
NameError: uninitialized constant Faraday::Response::Middleware

  class CloseioErrorHandler < Faraday::Response::Middleware

If you look at #77, this moved to Faraday::Middleware in Faraday 2.x...

Doh! Cutting a new version now.

authors: Roguelazer taylorbrooks

repo: taylorbrooks/closeio


text:
UTF-16 support

Currently, matio does not support reading UTF16 strings. Unfortunately, decently recent Windows computer use UTF16 and when Matlab writes a .mat file, it will default to UTF16 for strings containing non-ascii characters.
This means that with the current version of matio, trying to read a .mat file created by Matlab on Windows that contains non-ascii characters (like the '°' for temperatures or like some German accentuated letters) will write lots of error messages ("Character data not supported type") as well as fail to read the offending strings (which becomes even more problematic when these should contain the units). As I am stuck with some files with such properties (they come from an operational weather forecast toolchain and should be forwarded into another operational toolchain, so I can absolutely not ask for anything to be changed), my only hope is to have some support implemented in matio.
As I see it, they are a few options:

relying on something like Posix "iconv", but this requires an external dependency and is not fully portable;
relying on a piece of C++ that could do it (most of the code examples use c++ because most of the required elements are available in the standard library) but again, this introduces external dependencies since the code would not be pure c anymore;
I found a contribution to libxml2 that adds utf16->utf8 conversion (see https://opensource.apple.com/source/libxml2/libxml2-7/libxml2/encoding.c (UTF16BEToUTF8()). I could extract this function and adapt it to matio so it now successfully reads my .mat files

Of course, you might have other ideas or prefer some other options!

Can you please attach a MAT-file - created by MATLAB - with UTF16 char array. Thanks.

I had to zip it in order to attach it...
test-UTF16.zip

Indeed, both function ReadCharData and ReadCompressedCharData miss the case for MAT_T_UTF16.
Can you check if 12b7d40 solves already the problem.

This is half way better... The string is read without error message but the non-ascii characters remain messed up (and I have no clue what these are encoded into).
for example, for the units: '�C'

Should be little endian Unicode on Win (which is little endian). Thus, it should be exactly what you want.

If you apply 94425a1 to matdump then matdump -d test-UTF16.mat stat.dunit > dunit.txt correctly shows °C in Latin1 encoding. It's really strange.

Ok, now this is clear... I'm sorry, my terminal was configured as UTF-8, therefore it was messing up the Latin1 encoding. So, your commit does works, it properly reads UTF-16 and outputs ISO-8859-1. Thanks a lot for your very quick reply and commit!

But what still is strange, that the UTF-16 string is not Unicode encoded but ISO-8859-1. MATLAB simply is not consistent on this, see e.g. http://blog.omega-prime.co.uk/?p=150.

I'd like to see some MAT-file where the UTF-16 character array does not reduce to 8-bit encoding.

authors: bavay tbeu

repo: tbeu/matio


text:
vsporject add some configs

1.suport vsproject mfc mode
target(xxx)
-- for make vsproject on mfcmode
set_values("mfc",true)
-- for unicode mode
add_defines("UNICODE")

-- use MT or MD switch RuntimeLibrary, (debug use MTd,MDd)
add_cxflags("-MT")

2.subsystem switch support
target(xxx)
-- change subsystem to windows, default console
add_ldflags("/SUBSYSTEM:WINDOWS",{force=true})

set_values("mfc",true) 对于values的扩展设置，请加上域空间，例如 aaa.bbb.mfc，放置与其他rules/plugins中的values设置冲突，也方便理解。
例如此处可改为：set_values("project.vs.mfc", true) 用于指明是对vs的工程生成插件的设置扩展，启用对mfc的支持
另外，即时通过这种方式强制对vcproj的生成启用了mfc，但对于xmake的命令行编译是否也支持？
如果不支持的话，不建议这么处理，可以通过新增一个 win.sdk.mfc的rule规则来同时支持直接编译和工程生成，会更好些。可参考win.sdk下的其他一些规则：https://github.com/tboox/xmake/blob/master/xmake/rules/winsdk/xmake.lua
建议，每次pr的粒度细化下，一次提交一个功能改进和修改，方便修改和跟踪维护。

mfc的rule化下一个pr提交

……我去，原来一个pr没关闭，后面提交的都算到这里了。。

尽量先把之前的特性pr修改搞定后，我merge完，在提交新特性的pr吧，不然不好维护。。

authors: waruqi xigalto

repo: tboox/xmake


text:
Reflect proposal is at Stage 2, update spec text links to use new repo owner

Re Stage 2: https://github.com/tc39/proposals/commit/1badce0191cc12203a22e5b60599a1eca911d00b

I just saw issue #8, which this will close.


text:
What settings to include for range formatting?

ICU4J has a number of settings for range formatting:
https://unicode-org.github.io/icu-docs/apidoc/released/icu4j/com/ibm/icu/number/NumberRangeFormatterSettings.html

collapse
Sets the aggressiveness of "collapsing" fields across the range separator. Possible values:

ALL: "3-5K miles"
UNIT: "3K - 5K miles"
NONE: "3K miles - 5K miles"
AUTO: usually UNIT or NONE, depending on the locale and formatter settings

The default value is AUTO.
identityFallback
Sets the behavior when the two sides of the range are the same. This could happen if the same two numbers are passed to the formatRange function, or if different numbers are passed to the function but they become the same after rounding rules are applied. Possible values:

SINGLE_VALUE: "5 miles"
APPROXIMATELY_OR_SINGLE_VALUE: "~5 miles" or "5 miles", depending on whether the number was the same before rounding was applied
APPROXIMATELY: "~5 miles"
RANGE: "5-5 miles" (with collapse=UNIT)

The default value is APPROXIMATELY.

Do we want to add those options to ECMA-402, or just stick with the defaults?
@romulocintra

I can understand why someone might want to play with collapse, but I don't really have much of a sense of whether such manipulations make sense across locales (given the existing locale-dependent variation in how AUTO works). Do we have any experience we can build on from ICU's users?
I'm having trouble understanding when you'd want to mess with identityFallback. Does anyone have a use case in mind? Approximately SGTM.

Can we start with the simplest achievable set of options that are a subset of what ICU does and consider extending as we encounter use cases and user requests?
For collapse it might be all vs auto.
I also don't fully understand the identityFallback - can we skip it for now?

FYI: with AUTO in ICU, the decision on whether to collapse prefixes/suffixes could depend on the locale, but also on the symbols.  For example:

$3 - $5
3 - 5 CHF

However, an implementation could choose to use different results:

$3 - 5
3 CHF - 5 CHF

Tentative conclusion from 402 meeting:

Use AUTO as the default for collapse, and don't include it in the options bag.  Wait for specific user demand for other options in the future.  Write the spec in a way such that it's easy to implement AUTO without ICU's heuristic.
Use SINGLE_VALUE as the default for identityFallback, and also don't include it in the options bag.  This is the behavior for identity fallback in Intl.DateTimeFormat.  Consider adding approximately as a new NumberFormat-wide option, either in this proposal or a follow-on proposal.

Relevant CLDR ticket: https://unicode-org.atlassian.net/browse/CLDR-11431

I would like to consider a world in which we have signDisplay: "approximately".  Here is what the semantics could look like here:
let nf = new Intl.NumberFormat("en" /* , { signDisplay: "auto" } */);
nf.format(-3);  // "-3"
nf.format(3);  // "3"
nf.formatRange(3, 5);  // "3 – 5"
nf.formatRange(3, 3);  // "~3"

let nf = new Intl.NumberFormat("en", { signDisplay: "approximately" });
nf.format(-3);  // RangeError
nf.format(3);  // "~3"
nf.formatRange(3, 5);  // "3 – 5"
nf.formatRange(3, 3);  // "~3"

let nf = new Intl.NumberFormat("en", { signDisplay: "negative" });
nf.format(-3);  // "-3"
nf.format(3);  // "3"
nf.formatRange(3, 5);  // "3 – 5"
nf.formatRange(3, 3);  // "3"

In this frame of reference, I think it might be okay to allow APPROXIMATELY to be the default identity fallback behavior in formatRange.

I think needs to be with https://github.com/tc39/proposal-Number.range having the same opening and closing interval semantics
CC @Jack-Works

@septs intl range doesn't have same semantics with programmatic number range.
When you say "0 to 100" you're definitely including 100 but when you creating a range for programmatic use, you may want to exclude the bound.

authors: Jack-Works littledan septs sffc zbraniecki


text:
Move femshop examples to finch

The femshop team says to use finch instead:
https://github.com/paralab/Finch
I still don't know how to run these with TrackedFloat. Tried changing the strings to use TrackedFloat64(10) instead of 10 etc, and that gives an error later on (below).
We need to import TrackedFloat somewhere. Maybe somewhere related to Meta.parse. But before that, I think we need to install TrackedFloat.jl as a regular package instead of doing use(...path/to/TF) everywhere.
$ julia example-poisson1d.jl
ERROR: LoadError: UndefVarError: TrackedFloat64 not defined
Stacktrace:
  [1] genfunction_1(x::Float64, y::Int64, z::Int64, t::Int64, node_index::Int64, face_index::Int64)
    @ Finch ./none:1
  [2] evaluate_coefficient(c::Coefficient, comp::Int64, x::Vector{Float64}, t::Int64, nodeind::Int64, faceind::Int64)
    @ Finch ~/.julia/packages/Finch/I3WJX/src/coefficient.jl:49
  [3] genfunction_3(args::Tuple{Variable, Int64, Int64, Finch.Grid, GeometricFactors, Finch.Refel, Int64, Int64, Vector{Matrix{Float64}}, Matrix{Float64}}; kwargs::Base.Pairs{Symbol, Union{}, Tuple{}, NamedTuple{(), Tuple{}}})
    @ Finch ./none:37
  [4] genfunction_3(args::Tuple{Variable, Int64, Int64, Finch.Grid, GeometricFactors, Finch.Refel, Int64, Int64, Vector{Matrix{Float64}}, Matrix{Float64}})
    @ Finch ./none:1
  [5] macro expansion
    @ ~/.julia/packages/Finch/I3WJX/src/level_benchmark.jl:43 [inlined]
  [6] assemble(var::Variable, bilinear::GenFunction, linear::GenFunction, allocated_vecs::Vector{Vector{Float64}}, dofs_per_node::Int64, dofs_per_loop::Int64, t::Int64, dt::Int64; assemble_loops::Nothing, rhs_only::Bool)
    @ Finch.CGSolver ~/.julia/packages/Finch/I3WJX/src/CGSolver.jl:430
  [7] macro expansion
    @ ~/.julia/packages/Finch/I3WJX/src/CGSolver.jl:299 [inlined]
  [8] macro expansion
    @ ./timing.jl:383 [inlined]
  [9] linear_solve(var::Variable, bilinear::GenFunction, linear::GenFunction, stepper::Nothing; assemble_func::Nothing)
    @ Finch.CGSolver ~/.julia/packages/Finch/I3WJX/src/CGSolver.jl:298
 [10] macro expansion
    @ ./timing.jl:383 [inlined]
 [11] solve(var::Variable, nlvar::Nothing; nonlinear::Bool)
    @ Finch ~/.julia/packages/Finch/I3WJX/src/finch_interface.jl:1300
 [12] solve (repeats 2 times)
    @ ~/.julia/packages/Finch/I3WJX/src/finch_interface.jl:1223 [inlined]
 [13] top-level scope
    @ ~/code/uu/fpx/FloatTracker.jl/example/finch/example-poisson1d.jl:42
in expression starting at /home/ben/code/uu/fpx/FloatTracker.jl/example/finch/example-poisson1d.jl:42

Maybe we can replace the strings with functions... need to read about how finch works!


text:
Sqlfmt output differs between Github Actions and local runs and fails GHA

Describe the bug
When I run sqlfmt locally, using python 3.10 and sqlfmt v0.19.X, I am getting slightly different output than when I run sqlfmt through a Github Action (GHA) using the same versions. This is causing my Github Action step to fail every time on the sqlfmt runner step.
The main issues tend to be that quoted text is getting set as single-quote (') locally, but double quotes (") in the Github Action. I'm not sure why this would happen, and was hoping to get some clarification on which is the intended format in different versions of sqlfmt and Python.
To Reproduce
Here is the config file for our Github Action. It shows that we are running on Python 3.10 and the latest version of sqlfmt:
name: Run sqlfmt

on:
  pull_request:
    branches:
      - master

jobs:
  static:
    name: sqlfmt
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v3
        with:
          persist-credentials: true
      - name: Setup Python
        uses: actions/setup-python@v4
        with:
          python-version: "3.10"
      - name: Install sqlfmt
        run: pip install shandy-sqlfmt[jinjafmt]
      - name: Get Changed Files
        id: changed-files
        uses: tj-actions/changed-files@v34
      - name: Run sqlfmt
        run: sqlfmt --diff ${{ steps.changed-files.outputs.all_changed_files }}

This produces a diff suggesting double quotes.
However, when I run sqlfmt locally on the same set of files, using Python 3.10.X and sqlfmt 0.19.X, I get formatted sql with single quotes.
Expected behavior
I expect sqlfmt to consistently use either single or double quotes in version 0.19.X, and hope to understand which one is intended.
Actual behavior
I am getting double quotes (") when running sqlfmt in GHA and single quotes (') when I run sqlfmt locally, both with Python 3.10.X and sqlfmt v0.19.X. This causes my Github Action to fail.
Additional context
What is the output of sqlfmt --version?
Locally and in Github Action: 0.19.2
Python version is 3.10.12 on Github action, and I temporarily upgraded to 3.10.12 locally to test it with sqlfmt and continued to receive the single quotes locally.

@tconbeer , great find. I installed with pipx locally but pip on the CI machine. When installing locally with pip:
pip install "shandy-sqlfmt[jinjafmt]"

black is included:
pip list
Package           Version
----------------- -------
black             23.7.0
click             8.1.6
mypy-extensions   1.0.0
packaging         23.1
pathspec          0.11.2
pip               21.1.1
platformdirs      3.10.0
setuptools        56.0.0
shandy-sqlfmt     0.19.2
tomli             2.0.1
tqdm              4.65.0
typing-extensions 4.7.1

However, when installing with pipx (following the recommended instructions) I'm not seeing black included:
pipx install "shandy-sqlfmt[jinjafmt]"

These apps are now globally available
    - sqlfmt
    - sqlfmt_primer
done! ✨ 🌟 ✨

pipx list
...
   package shandy-sqlfmt 0.19.2, installed using Python 3.8.12
    - sqlfmt
    - sqlfmt_primer
...

I'm wonder if there's something else I need to do when installing with pipx to get it to include the other packages? 🤔

I think you need pipx list --include-injected to show dependent packages.
Maybe you have another installation of sqlfmt that is being run before the pipx installation locally?
If not you should be able to fix your pipx installation with pipx inject shandy-sqlfmt black

Injecting black on its own did the trick, thanks @tconbeer ! So that tells me it wasn't using another sqlfmt, but for some reason black (and the other injected libraries) weren't installed the first time with pipx. I wonder why that is. 🤔 But also, running pipx runpip shandy-sqlfmt list shows the other packages:

So maybe they were installed with pip in the past, but I'm not sure why that would prevent pipx from installing them in its installation.

repo: tconbeer/sqlfmt


text:
Add empty function

Like the project.
While this is my small contribution. To check the string length standard means you can not use the expression ${#myVar}.

The opposite is also possible to add a function. Or operator "!".

Doesn't it work to simply say if (str == "") { ... }?

@tdenniston Yes, perhaps, is the best option.

@tdenniston However, this function can be changed to obtain the length of the string, which is very convenient in different cases.

@tdenniston You can close this PR.

repo: tdenniston/bish


text:
Message animation

Trying to build and test a UI displaying Message animation content I noticed that telegram converts .gif files to .MP4. so there is a real use case where a .gif file is received by tdlib?

Yes. If the GIF was uploaded a long time ago, or is very big (for example, bigger than 30 MB) and was uploaded from Telegram Desktop (or another app, which doesn't support client-side conversion to MPEG4), then the animation will contain a GIF file.

repo: tdlib/td


text:
[Question] Is this source code the latest?

As I notice that tdlib on Telegram X is at version 1.3.2, but the latest release here is 1.3. I wonder if that was the way you guys doing versioning or the source code here is not the latest source code?
And in case of you're not publishing the latest source code here, may I ask why?
Thanks.

For now, we publish on Github only stable releases with finalized new TDLib's API after they are extensively tested in Telgram X, Bot API and Unigram and fully documented. TDLib 1.3.2, which is used in current Telegram X beta, has a lot of unstable API features, which can be frequently changed and improved. If you have a TDLIb's based Telegram client and want to test TDLib's versions with unstable API, you can ask for prebuilt TDLIb binaries through @tdlib_bot. But in that case you need to be ready for a lot of intermediate changes in the TDLib's API.

Thanks for informing me.


text:
Ticking entity error

https://pastebin.com/9nXsn8NR

This issue came first, yet conversation began in #16, oops

repo: teamhollow/direbats


text:
Creación/uso de métodos para el API

Objetivo
Generar un código de ejemplo para el uso de la API de Twitter

Por ahora sólo inicie un cuaderno en Colab, una vez que se cuente con acceso iré escribiendo más contenido en el cuaderno que nos explique cómo se usa el API y que permita a otros usar el API para la extracción de información.

Colab


text:
Revamp DB Schema for Expansion

h2. Goal
Design data schema to support multiple project aspects (below).
h3. DB Requirements

Store static parcel information:

Parcel number
Address
Lat/long
Use code
Zone code
County

Store parcel information that changes with base year/closed roll year:

Base Year
Sale Date
Year built
Assessed land value
Improvements

Store any auxiliary data associated with parcel
Store multiple estimated current land values per parcel, with methodology (considering methodology will change over time)

h3. Primary Query Support

Given lat/long, find all properties within X miles, return lat/long, parcel number, and assessed land value (needs to be highly performant)
Given parcel ID, return all information about parcel
Given some parameters (what?), export a flat file of parcel information, assessed land value, (and tax info?)

nts: consider https://postgis.net for fast geo calcs

Question: are parcel IDs globally unique statewide?

Draft schema here! Haven't tried importing any data yet so there may be a few edges.
Still to do:

Audit columns
Reporting schema that stays updated (should be straightforward with postgres's version of CDC)


text:
Vendor credit : Buttons in edit screen

[x]

issue fixed!

authors: AnjaliVellookkaran MohdSahal

repo: techgebra/polosys-books

license: Unlicense


text:
K3s Service stuck at activating on nodes

k3s-node.service does not start and is stuck on activating.
Expected Behavior

k3s-node.server should be running on nodes.
Current Behavior

`TASK [k3s/master : Create crictl symlink] ******************************************************************************changed: [us-ga-cluster-02]
changed: [us-ga-cluster-01]
changed: [us-ga-cluster-03]
PLAY [node] ************************************************************************************************************
TASK [Gathering Facts] *************************************************************************************************ok: [us-ga-worker-01]
ok: [us-ga-worker-02]
TASK [k3s/node : Copy K3s service file] ********************************************************************************changed: [us-ga-worker-01]
changed: [us-ga-worker-02]
TASK [k3s/node : Enable and check K3s service] *************************************************************************`
`ubuntu@us-ga-worker-01:~$ sudo systemctl status k3s-node.service
● k3s-node.service - Lightweight Kubernetes
Loaded: loaded (/etc/systemd/system/k3s-node.service; enabled; vendor preset: enabled)
Active: activating (start) since Fri 2022-05-20 15:49:17 EDT; 53s ago
Docs: https://k3s.io
Process: 2513 ExecStartPre=/sbin/modprobe br_netfilter (code=exited, status=0/SUCCESS)
Process: 2522 ExecStartPre=/sbin/modprobe overlay (code=exited, status=0/SUCCESS)
Main PID: 2527 (k3s-agent)
Tasks: 8
Memory: 31.2M
CGroup: /system.slice/k3s-node.service
└─2527 /usr/local/bin/k3s agent
May 20 15:49:17 us-ga-worker-01 k3s[2527]: time="2022-05-20T15:49:17-04:00" level=info msg="Starting k3s agent v1.23.6+k3s1 (418c3fa8)"
May 20 15:49:17 us-ga-worker-01 k3s[2527]: time="2022-05-20T15:49:17-04:00" level=info msg="Running load balancer k3s-agent-load-balancer 127.0.0.1:6444 -> [10.20.0.46:6443]"
May 20 15:49:23 us-ga-worker-01 k3s[2527]: time="2022-05-20T15:49:23-04:00" level=error msg="failed to get CA certs: Get "https://127.0.0.1:6444/cacerts\": read tcp 127.0.0.1:51760->127.0.0.1:6444: read: connection reset by peer"
May 20 15:49:29 us-ga-worker-01 k3s[2527]: time="2022-05-20T15:49:29-04:00" level=error msg="failed to get CA certs: Get "https://127.0.0.1:6444/cacerts\": read tcp 127.0.0.1:51768->127.0.0.1:6444: read: connection reset by peer"
May 20 15:49:35 us-ga-worker-01 k3s[2527]: time="2022-05-20T15:49:35-04:00" level=error msg="failed to get CA certs: Get "https://127.0.0.1:6444/cacerts\": read tcp 127.0.0.1:51776->127.0.0.1:6444: read: connection reset by peer"
May 20 15:49:42 us-ga-worker-01 k3s[2527]: time="2022-05-20T15:49:42-04:00" level=error msg="failed to get CA certs: Get "https://127.0.0.1:6444/cacerts\": read tcp 127.0.0.1:51784->127.0.0.1:6444: read: connection reset by peer"
May 20 15:49:48 us-ga-worker-01 k3s[2527]: time="2022-05-20T15:49:48-04:00" level=error msg="failed to get CA certs: Get "https://127.0.0.1:6444/cacerts\": read tcp 127.0.0.1:51792->127.0.0.1:6444: read: connection reset by peer"
May 20 15:49:54 us-ga-worker-01 k3s[2527]: time="2022-05-20T15:49:54-04:00" level=error msg="failed to get CA certs: Get "https://127.0.0.1:6444/cacerts\": read tcp 127.0.0.1:51800->127.0.0.1:6444: read: connection reset by peer"
May 20 15:50:00 us-ga-worker-01 k3s[2527]: time="2022-05-20T15:50:00-04:00" level=error msg="failed to get CA certs: Get "https://127.0.0.1:6444/cacerts\": read tcp 127.0.0.1:51808->127.0.0.1:6444: read: connection reset by peer"
May 20 15:50:06 us-ga-worker-01 k3s[2527]: time="2022-05-20T15:50:06-04:00" level=error msg="failed to get CA certs: Get "https://127.0.0.1:6444/cacerts\": read tcp 127.0.0.1:51816->127.0.0.1:6444: read: connection reset by peer"`
Steps to Reproduce

 ansible-playbook playbooks/site.yml -K

Context (variables)

Operating system:
ubuntu 20.04
Hardware:
Proxmox VM
Variables Used:
all.yml
k3s_version: v1.23.6+k3s1
# this is the user that has ssh access to these machines
ansible_user: ubuntu
systemd_dir: /etc/systemd/system

# Set your timezone
system_timezone: "America/New_York"

# interface which will be used for flannel
flannel_iface: "eth0"

# apiserver_endpoint is virtual ip-address which will be configured on each master
apiserver_endpoint: "10.20.0.46"

# k3s_token is required  masters can talk together securely
# this token should be alpha numeric only
k3s_token: "xxxxxxxxxxxxxxxxx"

# change these to your liking, the only required one is--no-deploy servicelb
extra_server_args: "--no-deploy servicelb --no-deploy traefik"
extra_agent_args: ""

# image tag for kube-vip
kube_vip_tag_version: "v0.4.3"

# image tag for metal lb
metal_lb_speaker_tag_version: "v0.12.1"
metal_lb_controller_tag_version: "v0.12.1"

# metallb ip range for load balancers
metal_lb_ip_range: "10.20.0.100-10.20.0.120"

Hosts
host.ini
[master]
us-ga-cluster-01
us-ga-cluster-02
us-ga-cluster-03

[node]
us-ga-worker-01
us-ga-worker-02

[k3s_cluster:children]
master
node

Possible Solution

vip is not reachable so i am thinking if that's the issue.

I'm facing the same issue here, what if we only have one master? Do we need to specify the apiserver_endpoint same as the master IP? Kindly clarify.

Hi.  This is an issue with k3s/kube-vip.  I would use the version in the template.  It will always be the latest tested version
v1.23.4+k3s1

Tried v1.23.4+k3s1, same issue. The VIP is not responding.
Stuck on "TASK [k3s/node : Enable and check K3s service]"
Status on node = activating
level=error msg="failed to get CA certs: Get "https://127.0.0.1:6444/cacerts\": read tcp 127.0.0.1:42274->127.0.0.1:6444: read: connection reset by peer"

Please see this https://github.com/techno-tim/k3s-ansible/discussions/20


text:
Some proxied m3u8 cannot play

Data download well and the player show LIVE, but there is no video and audio.
The URL is
https://crossorigin.me/http://live.gslb.letv.com/gslb?stream_id=lb_mv_1300&tag=live&ext=m3u8&sign=live_tv&platid=10&splatid=1009&format=letv&expect=1

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

Hi - can you please post the code you're using to request this file from the proxy?

I use videojs player to player the video.
It is solved by others, the cause is that the URLs in the m3u8 files cannot be proxied,

I suspect this is due to the size restriction on files passed through the proxy.


text:
package updates

This makes it work on Heroku, where it is currently down.

Thanks - although it's not hosted on Heroku anymore! All on digital ocean now. :)

you're welcome :)
you can check it here: http://corsthis.herokuapp.com

Oh that's interesting, somebody else is hosting a copy now.

@technoboy10 that's me, just to see if it worked, I'll take it down whenever.

Oh ok! No worries, although it might be good to change the index.html a bit so people don't get confused. Feel free to keep it up, I'll work on merging this today or tomorrow.

ok, thanks.
You are aware that crossorigin.me is down now right?

Thanks for the heads up, it's back up now.

@webjay Thanks for the PR! :)


text:
release: v0.1.25

Changes

chore: update npm dependencies (9c90eee22ed7573aa1c72b4a3d4e010d52d89179)

Base PullRequest
default branch (https://github.com/technote-space/use-local-storage/tree/main)
Command results

Details:

add path
/home/runner/work/_actions/technote-space/create-pr-action/v2/node_modules/npm-check-updates/build/src/bin

cli.js -u --packageFile package.json
Using yarn
Upgrading /home/runner/work/use-local-storage/use-local-storage/package.json

 @commitlint/cli                    ^15.0.0  →   ^16.0.0
 @commitlint/config-conventional    ^15.0.0  →   ^16.0.0
 @types/node                        ^17.0.0  →   ^17.0.5
 @types/react                      ^17.0.37  →  ^17.0.38
 @typescript-eslint/eslint-plugin    ^5.7.0  →    ^5.8.0
 @typescript-eslint/parser           ^5.7.0  →    ^5.8.0
 lint-staged                        ^12.1.3  →   ^12.1.4

Run yarn install to install new versions.

yarn install
yarn install v1.22.17
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.
$ [ -n "$CI" ] || [ ! -f node_modules/.bin/husky ] || husky install
Done in 13.13s.

yarn upgrade
yarn upgrade v1.22.17
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Rebuilding all packages...
success Saved lockfile.
success Saved 348 new dependencies.
info Direct dependencies
├─ @commitlint/cli@16.0.0
├─ @commitlint/config-conventional@16.0.0
├─ @testing-library/react-hooks@7.0.2
├─ @types/jest@27.0.3
├─ @types/react@17.0.38
├─ @typescript-eslint/eslint-plugin@5.8.0
├─ @typescript-eslint/parser@5.8.0
├─ eslint@8.5.0
├─ husky@7.0.4
├─ jest@27.4.5
├─ jsdom@19.0.0
├─ lint-staged@12.1.4
├─ pinst@2.1.6
├─ react-dom@17.0.2
├─ react@17.0.2
├─ ts-jest@27.1.2
└─ typescript@4.5.4
info All dependencies
├─ @babel/compat-data@7.16.4
├─ @babel/core@7.16.5
├─ @babel/helper-compilation-targets@7.16.3
├─ @babel/helper-function-name@7.16.0
├─ @babel/helper-get-function-arity@7.16.0
├─ @babel/helper-hoist-variables@7.16.0
├─ @babel/helper-module-imports@7.16.0
├─ @babel/helper-module-transforms@7.16.5
├─ @babel/helper-plugin-utils@7.16.5
├─ @babel/helper-simple-access@7.16.0
├─ @babel/helper-validator-option@7.14.5
├─ @babel/helpers@7.16.5
├─ @babel/highlight@7.16.0
├─ @babel/plugin-syntax-async-generators@7.8.4
├─ @babel/plugin-syntax-bigint@7.8.3
├─ @babel/plugin-syntax-class-properties@7.12.13
├─ @babel/plugin-syntax-import-meta@7.10.4
├─ @babel/plugin-syntax-json-strings@7.8.3
├─ @babel/plugin-syntax-logical-assignment-operators@7.10.4
├─ @babel/plugin-syntax-nullish-coalescing-operator@7.8.3
├─ @babel/plugin-syntax-numeric-separator@7.10.4
├─ @babel/plugin-syntax-object-rest-spread@7.8.3
├─ @babel/plugin-syntax-optional-catch-binding@7.8.3
├─ @babel/plugin-syntax-optional-chaining@7.8.3
├─ @babel/plugin-syntax-top-level-await@7.14.5
├─ @babel/plugin-syntax-typescript@7.16.5
├─ @babel/template@7.16.0
├─ @bcoe/v8-coverage@0.2.3
├─ @commitlint/cli@16.0.0
├─ @commitlint/config-conventional@16.0.0
├─ @commitlint/ensure@16.0.0
├─ @commitlint/execute-rule@16.0.0
├─ @commitlint/format@16.0.0
├─ @commitlint/is-ignored@16.0.0
├─ @commitlint/lint@16.0.0
├─ @commitlint/load@16.0.0
├─ @commitlint/message@16.0.0
├─ @commitlint/parse@16.0.0
├─ @commitlint/read@16.0.0
├─ @commitlint/resolve-extends@16.0.0
├─ @commitlint/rules@16.0.0
├─ @commitlint/to-lines@16.0.0
├─ @commitlint/top-level@16.0.0
├─ @cspotcode/source-map-consumer@0.8.0
├─ @cspotcode/source-map-support@0.7.0
├─ @eslint/eslintrc@1.0.5
├─ @humanwhocodes/config-array@0.9.2
├─ @humanwhocodes/object-schema@1.2.1
├─ @istanbuljs/load-nyc-config@1.1.0
├─ @jest/globals@27.4.4
├─ @jest/reporters@27.4.5
├─ @jest/test-sequencer@27.4.5
├─ @nodelib/fs.scandir@2.1.5
├─ @nodelib/fs.stat@2.0.5
├─ @nodelib/fs.walk@1.2.8
├─ @sinonjs/commons@1.8.3
├─ @sinonjs/fake-timers@8.1.0
├─ @testing-library/react-hooks@7.0.2
├─ @tootallnate/once@2.0.0
├─ @tsconfig/node10@1.0.8
├─ @tsconfig/node12@1.0.9
├─ @tsconfig/node14@1.0.1
├─ @tsconfig/node16@1.0.2
├─ @types/babel__core@7.1.17
├─ @types/babel__generator@7.6.4
├─ @types/babel__template@7.4.1
├─ @types/babel__traverse@7.14.2
├─ @types/graceful-fs@4.1.5
├─ @types/istanbul-lib-coverage@2.0.4
├─ @types/istanbul-lib-report@3.0.0
├─ @types/istanbul-reports@3.0.1
├─ @types/jest@27.0.3
├─ @types/json-schema@7.0.9
├─ @types/minimist@1.2.2
├─ @types/normalize-package-data@2.4.1
├─ @types/parse-json@4.0.0
├─ @types/prettier@2.4.2
├─ @types/prop-types@15.7.4
├─ @types/react-dom@17.0.11
├─ @types/react-test-renderer@17.0.1
├─ @types/react@17.0.38
├─ @types/scheduler@0.16.2
├─ @types/stack-utils@2.0.1
├─ @types/yargs-parser@20.2.1
├─ @typescript-eslint/eslint-plugin@5.8.0
├─ @typescript-eslint/experimental-utils@5.8.0
├─ @typescript-eslint/parser@5.8.0
├─ acorn-jsx@5.3.2
├─ acorn-walk@7.2.0
├─ acorn@8.6.0
├─ aggregate-error@3.1.0
├─ ajv@6.12.6
├─ ansi-colors@4.1.1
├─ ansi-escapes@4.3.2
├─ anymatch@3.1.2
├─ arg@4.1.3
├─ argparse@2.0.1
├─ array-ify@1.0.0
├─ array-union@2.1.0
├─ arrify@1.0.1
├─ babel-jest@27.4.5
├─ babel-plugin-jest-hoist@27.4.0
├─ babel-preset-jest@27.4.0
├─ balanced-match@1.0.2
├─ brace-expansion@1.1.11
├─ braces@3.0.2
├─ browser-process-hrtime@1.0.0
├─ browserslist@4.19.1
├─ bs-logger@0.2.6
├─ bser@2.1.1
├─ buffer-from@1.1.2
├─ camelcase-keys@6.2.2
├─ caniuse-lite@1.0.30001292
├─ char-regex@1.0.2
├─ cjs-module-lexer@1.2.2
├─ clean-stack@2.2.0
├─ cli-cursor@3.1.0
├─ cli-truncate@3.1.0
├─ color-convert@2.0.1
├─ color-name@1.1.4
├─ commander@8.3.0
├─ concat-map@0.0.1
├─ conventional-changelog-angular@5.0.13
├─ conventional-changelog-conventionalcommits@4.6.2
├─ conventional-commits-parser@3.2.3
├─ convert-source-map@1.8.0
├─ cosmiconfig-typescript-loader@1.0.2
├─ cosmiconfig@7.0.1
├─ create-require@1.1.1
├─ cross-spawn@7.0.3
├─ cssom@0.5.0
├─ csstype@3.0.10
├─ dargs@7.0.0
├─ data-urls@3.0.1
├─ debug@4.3.3
├─ decamelize-keys@1.1.0
├─ decamelize@1.2.0
├─ decimal.js@10.3.1
├─ dedent@0.7.0
├─ deep-is@0.1.4
├─ deepmerge@4.2.2
├─ delayed-stream@1.0.0
├─ detect-newline@3.1.0
├─ diff-sequences@27.4.0
├─ diff@4.0.2
├─ dir-glob@3.0.1
├─ doctrine@3.0.0
├─ domexception@4.0.0
├─ dot-prop@5.3.0
├─ electron-to-chromium@1.4.28
├─ emoji-regex@8.0.0
├─ enquirer@2.3.6
├─ error-ex@1.3.2
├─ escape-string-regexp@4.0.0
├─ eslint-scope@7.1.0
├─ eslint@8.5.0
├─ esprima@4.0.1
├─ esquery@1.4.0
├─ execa@5.1.1
├─ fast-deep-equal@3.1.3
├─ fast-glob@3.2.7
├─ fast-levenshtein@2.0.6
├─ fastq@1.13.0
├─ fb-watchman@2.0.1
├─ file-entry-cache@6.0.1
├─ fill-range@7.0.1
├─ flat-cache@3.0.4
├─ flatted@3.2.4
├─ form-data@4.0.0
├─ fromentries@1.3.2
├─ fs-extra@10.0.0
├─ fs.realpath@1.0.0
├─ function-bind@1.1.1
├─ gensync@1.0.0-beta.2
├─ get-package-type@0.1.0
├─ get-stream@6.0.1
├─ git-raw-commits@2.0.10
├─ glob-parent@6.0.2
├─ glob@7.2.0
├─ global-dirs@0.1.1
├─ globals@13.12.0
├─ globby@11.0.4
├─ hard-rejection@2.1.0
├─ has@1.0.3
├─ hosted-git-info@4.0.2
├─ html-encoding-sniffer@3.0.0
├─ html-escaper@2.0.2
├─ http-proxy-agent@5.0.0
├─ human-signals@2.1.0
├─ husky@7.0.4
├─ iconv-lite@0.4.24
├─ inflight@1.0.6
├─ inherits@2.0.4
├─ ini@1.3.8
├─ is-arrayish@0.2.1
├─ is-core-module@2.8.0
├─ is-extglob@2.1.1
├─ is-number@7.0.0
├─ is-obj@2.0.0
├─ is-plain-obj@1.1.0
├─ is-stream@2.0.1
├─ is-text-path@1.0.1
├─ isexe@2.0.0
├─ istanbul-lib-coverage@3.2.0
├─ istanbul-lib-instrument@4.0.3
├─ istanbul-lib-source-maps@4.0.1
├─ istanbul-reports@3.1.2
├─ jest-changed-files@27.4.2
├─ jest-cli@27.4.5
├─ jest-docblock@27.4.0
├─ jest-jasmine2@27.4.5
├─ jest-leak-detector@27.4.2
├─ jest-pnp-resolver@1.2.2
├─ jest-resolve-dependencies@27.4.5
├─ jest-serializer@27.4.0
├─ jest-util@27.4.2
├─ jest-watcher@27.4.2
├─ jest@27.4.5
├─ js-tokens@4.0.0
├─ jsdom@19.0.0
├─ jsesc@2.5.2
├─ json-parse-even-better-errors@2.3.1
├─ json-schema-traverse@0.4.1
├─ json-stable-stringify-without-jsonify@1.0.1
├─ json5@2.2.0
├─ jsonfile@6.1.0
├─ jsonparse@1.3.1
├─ JSONStream@1.3.5
├─ kind-of@6.0.3
├─ kleur@3.0.3
├─ leven@3.1.0
├─ lilconfig@2.0.4
├─ lines-and-columns@1.2.4
├─ lint-staged@12.1.4
├─ listr2@3.13.5
├─ locate-path@5.0.0
├─ lodash.memoize@4.1.2
├─ lodash.merge@4.6.2
├─ lodash@4.17.21
├─ log-update@4.0.0
├─ make-dir@3.1.0
├─ make-error@1.3.6
├─ makeerror@1.0.12
├─ map-obj@1.0.1
├─ mime-db@1.51.0
├─ mimic-fn@2.1.0
├─ min-indent@1.0.1
├─ minimist-options@4.1.0
├─ minimist@1.2.5
├─ ms@2.1.2
├─ node-int64@0.4.0
├─ node-releases@2.0.1
├─ normalize-package-data@3.0.3
├─ npm-run-path@4.0.1
├─ object-inspect@1.12.0
├─ onetime@5.1.2
├─ optionator@0.9.1
├─ p-limit@2.3.0
├─ p-locate@4.1.0
├─ p-map@4.0.0
├─ p-try@2.2.0
├─ parent-module@1.0.1
├─ path-is-absolute@1.0.1
├─ path-key@3.1.1
├─ path-parse@1.0.7
├─ picocolors@1.0.0
├─ picomatch@2.3.0
├─ pinst@2.1.6
├─ pirates@4.0.4
├─ pkg-dir@4.2.0
├─ progress@2.0.3
├─ prompts@2.4.2
├─ psl@1.8.0
├─ queue-microtask@1.2.3
├─ quick-lru@4.0.1
├─ react-dom@17.0.2
├─ react-error-boundary@3.1.4
├─ react-is@17.0.2
├─ react@17.0.2
├─ read-pkg-up@7.0.1
├─ read-pkg@5.2.0
├─ readable-stream@3.6.0
├─ redent@3.0.0
├─ regenerator-runtime@0.13.9
├─ resolve-cwd@3.0.0
├─ resolve-global@1.0.0
├─ resolve.exports@1.1.0
├─ resolve@1.20.0
├─ restore-cursor@3.1.0
├─ reusify@1.0.4
├─ rfdc@1.3.0
├─ rimraf@3.0.2
├─ run-parallel@1.2.0
├─ rxjs@7.4.0
├─ safe-buffer@5.1.2
├─ safer-buffer@2.1.2
├─ scheduler@0.20.2
├─ semver@7.3.5
├─ shebang-command@2.0.0
├─ shebang-regex@3.0.0
├─ sisteransi@1.0.5
├─ slice-ansi@5.0.0
├─ source-map-support@0.5.21
├─ source-map@0.6.1
├─ spdx-correct@3.1.1
├─ spdx-exceptions@2.3.0
├─ sprintf-js@1.0.3
├─ string_decoder@1.3.0
├─ string-argv@0.3.1
├─ strip-bom@4.0.0
├─ strip-final-newline@2.0.0
├─ strip-indent@3.0.0
├─ strip-json-comments@3.1.1
├─ supports-color@7.2.0
├─ supports-hyperlinks@2.2.0
├─ terminal-link@2.1.1
├─ test-exclude@6.0.0
├─ text-extensions@1.9.0
├─ text-table@0.2.0
├─ through@2.3.8
├─ tmpl@1.0.5
├─ to-fast-properties@2.0.0
├─ to-regex-range@5.0.1
├─ tr46@3.0.0
├─ trim-newlines@3.0.1
├─ ts-jest@27.1.2
├─ ts-node@10.4.0
├─ tslib@1.14.1
├─ type-detect@4.0.8
├─ type-fest@0.20.2
├─ typedarray-to-buffer@3.1.5
├─ typescript@4.5.4
├─ uri-js@4.4.1
├─ util-deprecate@1.0.2
├─ v8-compile-cache@2.3.0
├─ v8-to-istanbul@8.1.0
├─ w3c-xmlserializer@3.0.0
├─ walker@1.0.8
├─ which@2.0.2
├─ word-wrap@1.2.3
├─ write-file-atomic@3.0.3
├─ ws@8.4.0
├─ xmlchars@2.2.0
├─ yallist@4.0.0
├─ yaml@1.10.2
├─ yargs-parser@20.2.9
├─ yn@3.1.1
└─ yocto-queue@0.1.0
Done in 7.49s.

yarn audit
yarn audit v1.22.17
0 vulnerabilities found - Packages audited: 591
Done in 0.74s.

Changed files

Changed 2 files:

package.json
yarn.lock

:octocat: Repo | :memo: Issues | :department_store: Marketplace

Codecov Report

Merging #35 (9c90eee) into main (3375358) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 9c90eee differs from pull request most recent head cdaa54e. Consider uploading reports for the commit cdaa54e to get more accurate results

@@            Coverage Diff            @@
##              main       #35   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           16        16
  Branches         4         4
=========================================
  Hits            16        16

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 3375358...cdaa54e. Read the comment docs.

Command results

Details:

add path
/home/runner/work/_actions/technote-space/create-pr-action/v2/node_modules/npm-check-updates/build/src/bin

cli.js -u --packageFile package.json
Using yarn
Upgrading /home/runner/work/use-local-storage/use-local-storage/package.json

 @commitlint/cli                   ^16.0.0  →  ^16.0.1
 @types/jest                       ^27.0.3  →  ^27.4.0
 @types/node                       ^17.0.5  →  ^17.0.6
 @typescript-eslint/eslint-plugin   ^5.8.0  →   ^5.8.1
 @typescript-eslint/parser          ^5.8.0  →   ^5.8.1
 eslint                             ^8.5.0  →   ^8.6.0

Run yarn install to install new versions.

yarn install
yarn install v1.22.17
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.
$ [ -n "$CI" ] || [ ! -f node_modules/.bin/husky ] || husky install
Done in 14.33s.

yarn upgrade
yarn upgrade v1.22.17
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Rebuilding all packages...
success Saved lockfile.
success Saved 348 new dependencies.
info Direct dependencies
├─ @commitlint/cli@16.0.1
├─ @commitlint/config-conventional@16.0.0
├─ @testing-library/react-hooks@7.0.2
├─ @types/jest@27.4.0
├─ @types/react@17.0.38
├─ @typescript-eslint/eslint-plugin@5.8.1
├─ @typescript-eslint/parser@5.8.1
├─ eslint@8.6.0
├─ husky@7.0.4
├─ jest@27.4.5
├─ jsdom@19.0.0
├─ lint-staged@12.1.4
├─ pinst@2.1.6
├─ react-dom@17.0.2
├─ react@17.0.2
├─ ts-jest@27.1.2
└─ typescript@4.5.4
info All dependencies
├─ @babel/compat-data@7.16.4
├─ @babel/core@7.16.7
├─ @babel/helper-compilation-targets@7.16.7
├─ @babel/helper-function-name@7.16.7
├─ @babel/helper-get-function-arity@7.16.7
├─ @babel/helper-hoist-variables@7.16.7
├─ @babel/helper-module-imports@7.16.7
├─ @babel/helper-module-transforms@7.16.7
├─ @babel/helper-plugin-utils@7.16.7
├─ @babel/helper-simple-access@7.16.7
├─ @babel/helper-validator-option@7.16.7
├─ @babel/helpers@7.16.7
├─ @babel/highlight@7.16.7
├─ @babel/plugin-syntax-async-generators@7.8.4
├─ @babel/plugin-syntax-bigint@7.8.3
├─ @babel/plugin-syntax-class-properties@7.12.13
├─ @babel/plugin-syntax-import-meta@7.10.4
├─ @babel/plugin-syntax-json-strings@7.8.3
├─ @babel/plugin-syntax-logical-assignment-operators@7.10.4
├─ @babel/plugin-syntax-nullish-coalescing-operator@7.8.3
├─ @babel/plugin-syntax-numeric-separator@7.10.4
├─ @babel/plugin-syntax-object-rest-spread@7.8.3
├─ @babel/plugin-syntax-optional-catch-binding@7.8.3
├─ @babel/plugin-syntax-optional-chaining@7.8.3
├─ @babel/plugin-syntax-top-level-await@7.14.5
├─ @babel/plugin-syntax-typescript@7.16.7
├─ @bcoe/v8-coverage@0.2.3
├─ @commitlint/cli@16.0.1
├─ @commitlint/config-conventional@16.0.0
├─ @commitlint/ensure@16.0.0
├─ @commitlint/execute-rule@16.0.0
├─ @commitlint/format@16.0.0
├─ @commitlint/is-ignored@16.0.0
├─ @commitlint/lint@16.0.0
├─ @commitlint/load@16.0.0
├─ @commitlint/message@16.0.0
├─ @commitlint/parse@16.0.0
├─ @commitlint/read@16.0.0
├─ @commitlint/resolve-extends@16.0.0
├─ @commitlint/rules@16.0.0
├─ @commitlint/to-lines@16.0.0
├─ @commitlint/top-level@16.0.0
├─ @cspotcode/source-map-consumer@0.8.0
├─ @cspotcode/source-map-support@0.7.0
├─ @eslint/eslintrc@1.0.5
├─ @humanwhocodes/config-array@0.9.2
├─ @humanwhocodes/object-schema@1.2.1
├─ @istanbuljs/load-nyc-config@1.1.0
├─ @jest/globals@27.4.4
├─ @jest/reporters@27.4.5
├─ @jest/test-sequencer@27.4.5
├─ @nodelib/fs.scandir@2.1.5
├─ @nodelib/fs.stat@2.0.5
├─ @nodelib/fs.walk@1.2.8
├─ @sinonjs/commons@1.8.3
├─ @sinonjs/fake-timers@8.1.0
├─ @testing-library/react-hooks@7.0.2
├─ @tootallnate/once@2.0.0
├─ @tsconfig/node10@1.0.8
├─ @tsconfig/node12@1.0.9
├─ @tsconfig/node14@1.0.1
├─ @tsconfig/node16@1.0.2
├─ @types/babel__core@7.1.18
├─ @types/babel__generator@7.6.4
├─ @types/babel__template@7.4.1
├─ @types/babel__traverse@7.14.2
├─ @types/graceful-fs@4.1.5
├─ @types/istanbul-lib-coverage@2.0.4
├─ @types/istanbul-lib-report@3.0.0
├─ @types/istanbul-reports@3.0.1
├─ @types/jest@27.4.0
├─ @types/json-schema@7.0.9
├─ @types/minimist@1.2.2
├─ @types/normalize-package-data@2.4.1
├─ @types/parse-json@4.0.0
├─ @types/prettier@2.4.2
├─ @types/prop-types@15.7.4
├─ @types/react-dom@17.0.11
├─ @types/react-test-renderer@17.0.1
├─ @types/react@17.0.38
├─ @types/scheduler@0.16.2
├─ @types/stack-utils@2.0.1
├─ @types/yargs-parser@20.2.1
├─ @typescript-eslint/eslint-plugin@5.8.1
├─ @typescript-eslint/experimental-utils@5.8.1
├─ @typescript-eslint/parser@5.8.1
├─ acorn-jsx@5.3.2
├─ acorn-walk@7.2.0
├─ acorn@8.7.0
├─ aggregate-error@3.1.0
├─ ajv@6.12.6
├─ ansi-colors@4.1.1
├─ ansi-escapes@4.3.2
├─ anymatch@3.1.2
├─ arg@4.1.3
├─ argparse@2.0.1
├─ array-ify@1.0.0
├─ array-union@2.1.0
├─ arrify@1.0.1
├─ babel-jest@27.4.5
├─ babel-plugin-jest-hoist@27.4.0
├─ babel-preset-jest@27.4.0
├─ balanced-match@1.0.2
├─ brace-expansion@1.1.11
├─ braces@3.0.2
├─ browser-process-hrtime@1.0.0
├─ browserslist@4.19.1
├─ bs-logger@0.2.6
├─ bser@2.1.1
├─ buffer-from@1.1.2
├─ camelcase-keys@6.2.2
├─ caniuse-lite@1.0.30001295
├─ char-regex@1.0.2
├─ cjs-module-lexer@1.2.2
├─ clean-stack@2.2.0
├─ cli-cursor@3.1.0
├─ cli-truncate@3.1.0
├─ color-convert@2.0.1
├─ color-name@1.1.4
├─ commander@8.3.0
├─ concat-map@0.0.1
├─ conventional-changelog-angular@5.0.13
├─ conventional-changelog-conventionalcommits@4.6.3
├─ conventional-commits-parser@3.2.4
├─ convert-source-map@1.8.0
├─ cosmiconfig-typescript-loader@1.0.2
├─ cosmiconfig@7.0.1
├─ create-require@1.1.1
├─ cross-spawn@7.0.3
├─ cssom@0.5.0
├─ csstype@3.0.10
├─ dargs@7.0.0
├─ data-urls@3.0.1
├─ debug@4.3.3
├─ decamelize-keys@1.1.0
├─ decamelize@1.2.0
├─ decimal.js@10.3.1
├─ dedent@0.7.0
├─ deep-is@0.1.4
├─ deepmerge@4.2.2
├─ delayed-stream@1.0.0
├─ detect-newline@3.1.0
├─ diff-sequences@27.4.0
├─ diff@4.0.2
├─ dir-glob@3.0.1
├─ doctrine@3.0.0
├─ domexception@4.0.0
├─ dot-prop@5.3.0
├─ electron-to-chromium@1.4.31
├─ emoji-regex@8.0.0
├─ enquirer@2.3.6
├─ error-ex@1.3.2
├─ escape-string-regexp@4.0.0
├─ eslint-scope@7.1.0
├─ eslint@8.6.0
├─ espree@9.3.0
├─ esprima@4.0.1
├─ esquery@1.4.0
├─ execa@5.1.1
├─ fast-deep-equal@3.1.3
├─ fast-glob@3.2.7
├─ fast-levenshtein@2.0.6
├─ fastq@1.13.0
├─ fb-watchman@2.0.1
├─ file-entry-cache@6.0.1
├─ fill-range@7.0.1
├─ flat-cache@3.0.4
├─ flatted@3.2.4
├─ form-data@4.0.0
├─ fromentries@1.3.2
├─ fs-extra@10.0.0
├─ fs.realpath@1.0.0
├─ function-bind@1.1.1
├─ gensync@1.0.0-beta.2
├─ get-package-type@0.1.0
├─ get-stream@6.0.1
├─ git-raw-commits@2.0.11
├─ glob-parent@6.0.2
├─ glob@7.2.0
├─ global-dirs@0.1.1
├─ globals@13.12.0
├─ globby@11.0.4
├─ hard-rejection@2.1.0
├─ has@1.0.3
├─ hosted-git-info@4.0.2
├─ html-encoding-sniffer@3.0.0
├─ html-escaper@2.0.2
├─ http-proxy-agent@5.0.0
├─ human-signals@2.1.0
├─ husky@7.0.4
├─ iconv-lite@0.4.24
├─ inflight@1.0.6
├─ inherits@2.0.4
├─ ini@1.3.8
├─ is-arrayish@0.2.1
├─ is-core-module@2.8.0
├─ is-extglob@2.1.1
├─ is-number@7.0.0
├─ is-obj@2.0.0
├─ is-plain-obj@1.1.0
├─ is-stream@2.0.1
├─ is-text-path@1.0.1
├─ isexe@2.0.0
├─ istanbul-lib-coverage@3.2.0
├─ istanbul-lib-instrument@4.0.3
├─ istanbul-lib-source-maps@4.0.1
├─ istanbul-reports@3.1.3
├─ jest-changed-files@27.4.2
├─ jest-cli@27.4.5
├─ jest-docblock@27.4.0
├─ jest-jasmine2@27.4.5
├─ jest-leak-detector@27.4.2
├─ jest-pnp-resolver@1.2.2
├─ jest-resolve-dependencies@27.4.5
├─ jest-serializer@27.4.0
├─ jest-util@27.4.2
├─ jest-watcher@27.4.2
├─ jest@27.4.5
├─ js-tokens@4.0.0
├─ jsdom@19.0.0
├─ jsesc@2.5.2
├─ json-parse-even-better-errors@2.3.1
├─ json-schema-traverse@0.4.1
├─ json-stable-stringify-without-jsonify@1.0.1
├─ json5@2.2.0
├─ jsonfile@6.1.0
├─ jsonparse@1.3.1
├─ JSONStream@1.3.5
├─ kind-of@6.0.3
├─ kleur@3.0.3
├─ leven@3.1.0
├─ lilconfig@2.0.4
├─ lines-and-columns@1.2.4
├─ lint-staged@12.1.4
├─ listr2@3.13.5
├─ locate-path@5.0.0
├─ lodash.memoize@4.1.2
├─ lodash.merge@4.6.2
├─ lodash@4.17.21
├─ log-update@4.0.0
├─ make-dir@3.1.0
├─ make-error@1.3.6
├─ makeerror@1.0.12
├─ map-obj@1.0.1
├─ mime-db@1.51.0
├─ mimic-fn@2.1.0
├─ min-indent@1.0.1
├─ minimist-options@4.1.0
├─ minimist@1.2.5
├─ ms@2.1.2
├─ node-int64@0.4.0
├─ node-releases@2.0.1
├─ normalize-package-data@3.0.3
├─ npm-run-path@4.0.1
├─ object-inspect@1.12.0
├─ onetime@5.1.2
├─ optionator@0.9.1
├─ p-limit@2.3.0
├─ p-locate@4.1.0
├─ p-map@4.0.0
├─ p-try@2.2.0
├─ parent-module@1.0.1
├─ path-is-absolute@1.0.1
├─ path-key@3.1.1
├─ path-parse@1.0.7
├─ picocolors@1.0.0
├─ picomatch@2.3.0
├─ pinst@2.1.6
├─ pirates@4.0.4
├─ pkg-dir@4.2.0
├─ progress@2.0.3
├─ prompts@2.4.2
├─ psl@1.8.0
├─ queue-microtask@1.2.3
├─ quick-lru@4.0.1
├─ react-dom@17.0.2
├─ react-error-boundary@3.1.4
├─ react-is@17.0.2
├─ react@17.0.2
├─ read-pkg-up@7.0.1
├─ read-pkg@5.2.0
├─ readable-stream@3.6.0
├─ redent@3.0.0
├─ regenerator-runtime@0.13.9
├─ resolve-cwd@3.0.0
├─ resolve-global@1.0.0
├─ resolve.exports@1.1.0
├─ resolve@1.20.0
├─ restore-cursor@3.1.0
├─ reusify@1.0.4
├─ rfdc@1.3.0
├─ rimraf@3.0.2
├─ run-parallel@1.2.0
├─ rxjs@7.5.1
├─ safe-buffer@5.1.2
├─ safer-buffer@2.1.2
├─ scheduler@0.20.2
├─ semver@7.3.5
├─ shebang-command@2.0.0
├─ shebang-regex@3.0.0
├─ sisteransi@1.0.5
├─ slice-ansi@5.0.0
├─ source-map-support@0.5.21
├─ source-map@0.6.1
├─ spdx-correct@3.1.1
├─ spdx-exceptions@2.3.0
├─ sprintf-js@1.0.3
├─ string_decoder@1.3.0
├─ string-argv@0.3.1
├─ strip-bom@4.0.0
├─ strip-final-newline@2.0.0
├─ strip-indent@3.0.0
├─ strip-json-comments@3.1.1
├─ supports-color@7.2.0
├─ supports-hyperlinks@2.2.0
├─ terminal-link@2.1.1
├─ test-exclude@6.0.0
├─ text-extensions@1.9.0
├─ text-table@0.2.0
├─ through@2.3.8
├─ tmpl@1.0.5
├─ to-fast-properties@2.0.0
├─ to-regex-range@5.0.1
├─ tr46@3.0.0
├─ trim-newlines@3.0.1
├─ ts-jest@27.1.2
├─ ts-node@10.4.0
├─ tslib@1.14.1
├─ type-detect@4.0.8
├─ type-fest@0.20.2
├─ typedarray-to-buffer@3.1.5
├─ typescript@4.5.4
├─ uri-js@4.4.1
├─ util-deprecate@1.0.2
├─ v8-compile-cache@2.3.0
├─ v8-to-istanbul@8.1.0
├─ w3c-xmlserializer@3.0.0
├─ walker@1.0.8
├─ which@2.0.2
├─ word-wrap@1.2.3
├─ write-file-atomic@3.0.3
├─ ws@8.4.0
├─ xmlchars@2.2.0
├─ yallist@4.0.0
├─ yaml@1.10.2
├─ yargs-parser@20.2.9
├─ yn@3.1.1
└─ yocto-queue@0.1.0
Done in 12.96s.

yarn audit
yarn audit v1.22.17
0 vulnerabilities found - Packages audited: 591
Done in 0.68s.

Changed files

Changed 2 files:

package.json
yarn.lock

:octocat: Repo | :memo: Issues | :department_store: Marketplace

authors: codecov-commenter technote-space

repo: technote-space/use-local-storage