text:
Noise on TestData

I think it's better to add a noise method for DataContainers not only for TestData
https://github.com/vais-ral/CCPi-Framework/blob/master/Wrappers/Python/ccpi/framework/TestData.py#L80

from ccpi.framework import TestData
noiseless_image
noisy_image = TestData.random_noise(...)

I don't think DataContainers should add noise to themselves. It seems to me that adding noise is a step you would do while working with synthetic phantoms. That's why I put this function in the TestData class.
As it stands, the random_noise function is a staticmethod of the TestData class, i.e. it can be called without an instance of the TestData class.
TestData.random_noise adds noise to the input DataContainer, ImageData or AcquisitionData and returns the same output type as the input, with added noise.
I will close this issue.

authors: epapoutsellis paskino

repo: vais-ral/CCPi-Framework


text:
Feat/routing

Proposed changes
Improves handler routing implementation.
Fixes
n/a
Types of changes
What types of changes does your code introduce? (A breaking change is a fix or feature that would cause existing functionality and APIs to not work as expected.)
Put an x in the box that applies

[x] Non-breaking fix (non-breaking change which fixes an issue)
[ ] Breaking fix (breaking change which fixes an issue)
[ ] Non-breaking feature (non-breaking change which adds functionality)
[ ] Breaking feature (breaking change which adds functionality)
[ ] Refactor (non-breaking change which changes implementation)
[ ] Messy (mixture of the above - requires explanation!)

Checklist
Put an x in the boxes that apply.

[x] I have read the CONTRIBUTING doc
[x] I am making a pull request against the main branch (left side). Also you should start your branch off our main.
[x] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have locally run services that could be impacted and they do not present failures derived from my changes

Codecov Report

:exclamation: No coverage uploaded for pull request base (staging@dafe4c3). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##             staging      #64   +/-   ##
==========================================
  Coverage           ?   95.53%
==========================================
  Files              ?       23
  Lines              ?     1299
  Branches           ?        0
==========================================
  Hits               ?     1241
  Misses             ?       58
  Partials           ?        0

Flag
Coverage Δ

unittests
95.53% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

source: gharchive/pull-request

authors: codecov-commenter dvilelaf

repo: valory-xyz/contribution-service

license_type: permissive

license_source: github-api


text:
Unknown error when run prisma generate

i facing this error when run prisma generate
Error:
Error: Debug Failure. Unhandled SyntaxKind: Unknown.

im using
"prisma": "^4.11.0",
"typescript": "^5.0.2"

Can you run with DEBUG=* set as an env var and share the full output you get?

DEBUG=* dotenv -e .env.dev -- prisma db push

  prisma:engines  binaries to download libquery-engine, migration-engine +0ms
  prisma:loadEnv  project root found at /Users/luccasrobert/Documents/GitHub/api/package.json +0ms
  prisma:tryLoadEnv  Environment variables not found at null +0ms
  prisma:tryLoadEnv  Environment variables not found at undefined +1ms
  prisma:tryLoadEnv  No Environment variables loaded +0ms
  prisma:getConfig  Using getConfig Wasm +0ms
  prisma:getConfig  config data retrieved without errors in getConfig Wasm +1ms
  prisma:loadEnv  project root found at /Users/luccasrobert/Documents/GitHub/api/package.json +5ms
  prisma:tryLoadEnv  Environment variables not found at null +3ms
  prisma:tryLoadEnv  Environment variables not found at undefined +0ms
  prisma:tryLoadEnv  No Environment variables loaded +1ms
Prisma schema loaded from prisma/schema.prisma
  prisma:getConfig  Using getConfig Wasm +3ms
  prisma:getConfig  config data retrieved without errors in getConfig Wasm +1ms
Datasource "db": MySQL database "my db name" at "planetscale url"
  prisma:getConfig  Using getConfig Wasm +3ms
  prisma:getConfig  config data retrieved without errors in getConfig Wasm +1ms
  prisma:migrateEngine:rpc  starting migration engine with binary: /Users/luccasrobert/Documents/GitHub/api/node_modules/@prisma/engines/migration-engine-darwin +0ms
  prisma:migrateEngine:rpc  SENDING RPC CALL {"id":1,"jsonrpc":"2.0","method":"schemaPush","params":{"force":false,"schema":"// This is your Prisma schema file,\n// learn more about it in the docs: https://pris.ly/d/prisma-schema\n\n// generator client {\n//   provider = \"prisma-client-js\"\n// }\n\n// generator kysely {\n//   provider = \"prisma-kysely\"\n//   output   = \"../src/db\"\n//   fileName = \"types.ts\"\n// }\n\ngenerator kysely {\n  provider = \"prisma-kysely\"\n\n  // Optionally provide a destination directory for the generated file\n  // and a filename of your choice\n  output   = \"../src/db\"\n  fileName = \"types.ts\"\n}\n\ndatasource db {\n  provider     = \"mysql\"\n  url          = env(\"DATABASE_URL\")\n  relationMode = \"prisma\"\n}\n\n// CREATE TABLE users (\n//   id INT AUTO_INCREMENT PRIMARY KEY,\n//   provider ENUM('facebook', 'google', 'apple', 'local') NOT NULL,\n//   provider_id VARCHAR(255) UNIQUE,\n//   email VARCHAR(255) UNIQUE NOT NULL,\n//   password VARCHAR(255),\n//   first_name VARCHAR(255),\n//   last_name VARCHAR(255),\n//   profile_picture_url VARCHAR(255),\n//   created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,\n//   updated_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP\n// );\n\n// CREATE TABLE user_providers (\n//   id INT AUTO_INCREMENT PRIMARY KEY,\n//   user_id INT NOT NULL,\n//   provider ENUM('facebook', 'google', 'apple', 'local') NOT NULL,\n//   provider_id VARCHAR(255) UNIQUE,\n//   created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,\n//   updated_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,\n//   FOREIGN KEY (user_id) REFERENCES users(id)\n// );\n\nmodel User {\n  id                  Int            @id @default(autoincrement())\n  public_id           String         @db.VarChar(30)\n  email               String         @unique\n  password            String?\n  firstName           String\n  lastName            String\n  profile_picture_url String?\n  userProviders       UserProvider[]\n  created_at          DateTime       @default(now())\n  updated_at          DateTime       @updatedAt\n\n  @@map(\"user\")\n}\n\nenum Provider {\n  GOOGLE\n  APPLE\n  LOCAL\n}\n\nmodel UserProvider {\n  id          Int      @id @default(autoincrement())\n  public_id   String   @db.VarChar(30)\n  User        User     @relation(fields: [user_id], references: [id])\n  user_id     Int\n  provider    Provider\n  provider_id String   @unique\n  created_at  DateTime @default(now())\n  updated_at  DateTime @updatedAt\n\n  @@index([user_id])\n  @@map(\"user_providers\")\n}\n\nmodel Pet {\n  id         Int      @id @default(autoincrement())\n  name       String\n  photo_url  String\n  species    String\n  breed      String\n  age        Int?\n  created_at DateTime @default(now())\n  updated_at DateTime @updatedAt\n\n  @@map(\"pet\")\n}\n"}} +6ms
  prisma:migrateEngine:stderr  {"timestamp":"2023-03-21T14:10:55.605625Z","level":"INFO","fields":{"message":"Starting migration engine RPC server","git_hash":"8fde8fef4033376662cad983758335009d522acb"},"target":"migration_engine"} +0ms

The database is already in sync with the Prisma schema.

Running generate... (Use --skip-generate to skip the generators)
  prisma:getConfig  Using getConfig Wasm +5s
  prisma:getConfig  config data retrieved without errors in getConfig Wasm +1ms
  prisma:getDMMF  Using getDmmf Wasm +0ms
  prisma:getDMMF  Using given datamodel +1ms
  prisma:getDMMF  dmmf data retrieved without errors in getDmmf Wasm +7ms
Error: Debug Failure. Unhandled SyntaxKind: Unknown.
    at pipelineEmitWithHintWorker (/Users/luccasrobert/Documents/GitHub/api/node_modules/typescript/lib/typescript.js:110767:13)
    at pipelineEmitWithHint (/Users/luccasrobert/Documents/GitHub/api/node_modules/typescript/lib/typescript.js:110308:9)
    at pipelineEmitWithComments (/Users/luccasrobert/Documents/GitHub/api/node_modules/typescript/lib/typescript.js:114087:7)
    at pipelineEmit (/Users/luccasrobert/Documents/GitHub/api/node_modules/typescript/lib/typescript.js:110257:7)
    at emit (/Users/luccasrobert/Documents/GitHub/api/node_modules/typescript/lib/typescript.js:110225:7)
    at emitTypeAliasDeclaration (/Users/luccasrobert/Documents/GitHub/api/node_modules/typescript/lib/typescript.js:112190:7)
    at pipelineEmitWithHintWorker (/Users/luccasrobert/Documents/GitHub/api/node_modules/typescript/lib/typescript.js:110494:20)
    at pipelineEmitWithHint (/Users/luccasrobert/Documents/GitHub/api/node_modules/typescript/lib/typescript.js:110308:9)
    at pipelineEmitWithComments (/Users/luccasrobert/Documents/GitHub/api/node_modules/typescript/lib/typescript.js:114087:7)
    at pipelineEmit (/Users/luccasrobert/Documents/GitHub/api/node_modules/typescript/lib/typescript.js:110257:7)

  prisma:getConfig  Using getConfig Wasm +691ms
  prisma:getConfig  config data retrieved without errors in getConfig Wasm +1ms

Would you also be willing to share your schema so that I can attempt to recreate this bug?

I did some tests and the problem seems to be with TS, using typescript@4.9.5 works fine, but with typescript@5.0.2 cant work

@luccasr73 Could you try using snapshot version prisma-kysely@0.0.0-snapshot-20230321203645 and check if the problem persists?

@janpio no problems with prisma-client-js
@valtyr prisma-kysely@0.0.0-snapshot-20230321203645 works fine with typescript@5.0.2

@luccasr73 Awesome! I'll merge it in and create a release then. Thanks for reporting this issue 😄
@janpio It seems like prisma/prisma is safe... for now 🦸

source: gharchive/issue

authors: janpio luccasr73 valtyr

repo: valtyr/prisma-kysely

license: MIT


text:
Native esm

Make the source file usable directly in modern browsers.
(/demo/es.html need to be served from project folder to work)

Hey Noé,
First of all, thank you for being the first pull request! I've merged your fix for the class methods (da3af8f) and had the other issues fixed too with general changes and the addition of ESLint.
A few days ago, before the release, the demo was actually based on modules! I'll add this feature again besides the Rollup flow that's included, thanks for the suggestion.

authors: vaneenige zo

repo: vaneenige/phenomenon


text:
Check the Chinese Error message for mistakes on the Error page

It'd be best if someone who actually speaks/writes Chinese goes over the 404 page in the theme folder to make sure the text listed is written correctly. (As I have used DeepL to translate to Chinese)
404 - 未找到网页

你正在寻找的页面可能已经被删除，它的名字已经改变，或者它暂时无法使用。请稍后再试。
[回到主页](https://cn.docs.vapor.codes/4.0/)

This is the text you'd be checking as this text wasn't generated.

@Jinxiansen are you able to check this?

okay, I will check it at dawn.

Closed via #16

authors: 0xTim BennyDeBock Jinxiansen

repo: vapor/docs-cn


text:
Call to mehari uses wrong parameter for hgnc id

Describe the bug
The call to mehari to fetch variant details uses hgnc-id as parameter. This should be hgnc_id instead. It does not result in an error but the parameter is simply ignored.

Seems to be fixed

authors: stolpeo xiamaz

repo: varfish-org/varfish-server


text:
select组件报错

Bug report 🐞
直接使用基础示例，
<var-select placeholder="请选择一个选项" v-model="value">   <var-option label="吃饭" /> </var-select>
无法打开下拉菜单，控制台报错如下：
TypeError: Cannot read properties of null (reading 'wrapWidth')

Version & Environment
"@varlet-vue2/ui": "^0.1.2"
"vue": "^2.6.14"

可以提供一个复现问题的仓库么？

https://gitee.com/peshje/varlet-demo

请把版本锁定在vue2.6.14，我们没有去对 vue2.7 进行适配。 错误原因是因为 vue2.7 的升级引起的不兼容。

并且把组件库升级到最新版


text:
我想请问下，如果后台传对象不是数组，前端需要怎么处理啊

怎么解析这个数据呢

使用 afterFetch，在接收到数据后，处理成前端需要的 list 数据

authors: ChunyuPCY Lonely-SSH

repo: vbenjs/vue-vben-admin


text:
组件中遇到的TS报错

⚠ 重要 ⚠ 在进一步操作之前，请检查下列选项。如果您忽视此模板或者没有提供关键信息，您的 Issue 将直接被关闭

[√] 已阅读 文档.
[1] 确保您的代码已是最新或者所报告的 Bug 在最新版本中可以重现. (部分 Bug 可能已经在最近的代码中修复)
[1] 已在 Issues 中搜索了相关的关键词
[1] 不是 ant design vue 组件库的 Bug

描述 Bug
vben: version 2.10.0 ,随便打开几个组件都有类似的TS校验问题，有没有大佬可以解惑

系统信息

操作系统:win10
Node 版本:16.16.0
包管理器 (npm/yarn/pnpm) 及其版本:pnpm 8.6.6

你插件升级了没

你插件升级了没

只安了这个，请问需要升级什么


text:
Editions and suggestions: Jump section

We can use this draft pull request to collaboratively edit the book of seahtrue.

After our brainstorming session, we came up with this diagram:
Diagram
graph TB

subgraph R["R concepts"]
	Motivation --> Essentials --> Tidy
end

subgraph Essentials
	Documentation["Writing docs"]
	Help["Finding help"]
	Style
end

subgraph Tidy["The tidy way"]
	Pipes["Using pipes"] --> Plotting
end

subgraph Seahtrue["Seahtrue basics"]
	Functions --> Outputs
end

subgraph Advanced["Advanced Seahtrue"]
	Single["Single experiment"] --> Multiple["Multiple experiments"]
end

subgraph Surfing
	TBD["?"]
end

R --> Seahtrue --> Advanced --> Surfing

Proof-read the whole jump section.
Some rephrasings and clarifications.
Added some external materials in the summary.
Added a few TODOs


text:
🛑 Criptodolar & Covid API is down

In a2a308d, Criptodolar & Covid API (https://exchange.vcoud.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Criptodolar & Covid API is back up in c40c4fe.

repo: vcoud/upptime


text:
⚠ Spryr has degraded performance

In cdc6a21, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 4629 ms

Resolved: Spryr performance has improved in 0a4fc86 after 7 minutes.

repo: vcsphere/upptime


text:
Can't install go-sdl2 on Win10

I can't install sdl package because it returns this error:
# github.com/veandco/go-sdl2/sdl
In file included from go\src\github.com\veandco\go-sdl2\sdl\audio.go:4:
./sdl_wrapper.h:2:11: fatal error: SDL2/SDL.h: No such file or directory
  #include <SDL2/SDL.h>
           ^~~~~~~~~~~~
compilation terminated.

I'm using git bash: GNU bash, version 4.4.23(1)-release (x86_64-pc-msys)
Go: go version go1.15.2 windows/amd64

Hi @Diamondtroller, have you installed the native SDL2 libraries? You can follow the steps on the README.

Sorry @veeableful I didn't install libs correctly, after I posted this issue I only then checked closed issues and saw #472. This was my first issue in github, sorry for inconvenience.

authors: Diamondtroller veeableful

license_source: bigquery


text:
chore: prefix css selectors

CONTEXT
To help prevent collisions with CSS selectors in a consumer app, we need to prefix our own CSS selectors.
CHANGES

prefix CSS selectors with "vrs" (Vectara React Search)

@mrderyk I also saw a "styleWrapper" class used in index.tsx BTW.

Ah never mind you found it!

@cjcenizal I think we might not need it. But I'll take a deeper look at this when we have more time.

authors: cjcenizal mrderyk

repo: vectara/react-search


text:
Add support for Android 4.0

Now Riot.im only works for Android 4.1 and plus while Signal supports Android 4.0. I believe adding support for Android 4.0 users counts because not everyone can afford a new phone or tablet in developing countries, and we may still use an old device.

I agree to your comment. I have a tablet that I cannot upgrade to the latest android. Is it complicated to support Android 4.0?

Usually we increase the minSdkVersion value, it's like entropy :). Today is is set to 16 in Riot, new application should set it to 21 according to https://twitter.com/minsdkversion...
In practical, supporting old versions increase developer effort and support...

authors: Aster-the-Med-Stu bmarty floviolleau

repo: vector-im/riot-android


text:
Support Redis 6+ via Redlock 2

Supports redis versions 6 or later using RedisClient: https://github.com/leandromoreira/redlock-rb/releases/tag/2.0.0

Drops support for Redis <5 though: https://github.com/leandromoreira/redlock-rb/issues/127#issuecomment-1437747172

0.3.0 is released
Thank you @bmulholland for adding support for Redlock 2

authors: bmulholland sharshenov

repo: veeqo/activejob-uniqueness


text:
imperfect fix for drag and drop in firefox

I don't want to spend a lot of time troubleshooting every part of this, so here's what I got.  Drag and drop works now.  The ghost element does not look right.
Soo fun.

Addressed in #337.

authors: arvind deathbearbrown

repo: vega/lyra


text:
Show better error for empty columns on the first row

Usecase: Using own (CSV) data
What happens: I open change Data and paste a CSV in add Dataset. I give it a name and click "Add Data". The name appears in the left hand bar, however the variables do not change. On the javascript console I the following:
[Logging]  DATASET_NEW_PASTE mycustomdataname undefined vendor.js:358:17535
[Logging]  DATASET_CHANGE mycustomdataname undefined vendor.js:358:17535
Error: String(...).match(...) is null
Version: The one provided on https://vega.github.io/polestar/ at the 31.7.2016 (probably  commit e630aaa )

Can you provide your csv file in a pastebin?  That will help us debug this.

While trying to create a file that causes the error, I found the cause: Polestar crashes (or rather: fails silently) if the first column has an empty value. So that does not work:
"","B","C","D","E","F"
1,2,3,4,5,6
2,3,4,5,6,7

but this does:
"A","B","C","D","E","F"
1,2,3,4,5,6
2,3,4,5,6,7

Thanks.  We might show better warning in the future.  Keep in mind that this is a research project, we assume that the input data should be reasonably clean.

This will be considered as we're rebuilding Voyager which will contain all features in PoleStar.

authors: jdittrich kanitw

repo: vega/polestar


text:
Change 'connect wallet' text in tabs to a button

The Chore
This chore is to replace placeholder text in the UI "Please connect Vega wallet" with a button.
Tasks

[ ] What do we need to do first
[ ] and then what?
[ ] Etc.

Additional details / background info

Closing this was done in https://github.com/vegaprotocol/frontend-monorepo/pull/2246

repo: vegaprotocol/frontend-monorepo


text:
Fix for failing market tests timing out

Increasing timeout for finding market to place order in to stop tests from failing

question (blocking): I am unsure how this would help? Surely on live now the market is either there or it isn't in which case the current timeout would be fine. Also will #211 remove the need for this or am I missing something?

Currently the tests are failing even when the markets are showing which is really weird and annoying. But you're right that #211 will remove the need for this.
I thought it was worth pushing a really small change to stop the tests failing right now because the failing tests are bothering me :triumph: . Either way I'm also happy to close the PR and wait for the stubs to go in.


text:
feat(trading): liquidity provision current and pending on update

Related issues 🔗
Closes #5031
Description ℹ
Ensure market LP view can handle Core API changes to liquidity provision status

[x] if a node has both current and pending entries then show old-value/new-value and Update pending status

Demo 📺

Technical 👨🔧
Details of technical implementation that reviewers may need to be aware of, if applicable.

I think we'll we want to adjust the language behind the status field
If pending but no active - Pending
If active but no pending - Active
If active and pending - Updating next epoch


text:
feat(trading): amm pools page

Related issues 🔗
Closes https://github.com/vegaprotocol/nebula/issues/7
Description ℹ

adds additional columns: fee, price, price change, volume, my liquidity
adds search box

Demo 📺

Looks good ... lets get it merge.


text:
Update 0022-AUTH-auth.md to match latest implementation of the wallet

Update 0022-AUTH-auth.md to match latest implementation of the wallet.

[ ] update the spec and ACs to match implementation
[ ] Consider using new AC codes if the AC differs from the currently written test
[ ] Align with qa team to make sure the tests are covered

Waiting for the following core issue to be implemented:

https://github.com/vegaprotocol/vega/issues/7702

repo: vegaprotocol/specs


text:
fix locale category rewrite

The next.js is having an error while trying to automatically rewrites each source and destination prefixed to handle the configured locales because of the search category route. I added a locale false to this route to fix this problem
This is the error that was fixed when we tried to change the category:

This pr is related with this issue https://github.com/vercel/commerce/issues/119

repo: vercel/commerce


text:
Chapter 15 - Adding the sign in functionality

On the section "Adding the sign in functionality"
on the code block auth.ts, there's a sql query where the capitalization is not correct.
current:
const user = await sql<User>`SELECT * from USERS where email=${email}`;

expected:
const user = await sql<User>`SELECT * FROM users WHERE email=${email}`;

Thank you @alexandreferreirafr, and for the PR @tylerhoward15 🎉

authors: alexandreferreirafr delbaoliveira

repo: vercel/next-learn


text:
Unable to set up the vercel environment during deploying the site.

When I after following every instruction I ran vercel from the cli, I also I have tried from the vercel website but it says that it is having a problem the problem log is as follows :
 Creating an optimized production build ...

✓ Compiled successfully
✓ Linting and checking validity of types
Collecting page data  .tl [VercelPostgresError]: VercelPostgresError - 'missing_connection_string': You did not supply a 'connectionString' and no 'POSTGRES_URL' env var was found.
at tf (C:\Users\My\Programming\nextjs-dashboard.next\server\app\seed\route.js:60:5026)
at Object.get (C:\Users\My\Programming\nextjs-dashboard.next\server\app\seed\route.js:60:6072)
at C:\Users\My\Programming\nextjs-dashboard.next\server\app\seed\route.js:1:3990
at t.a (C:\Users\My\Programming\nextjs-dashboard.next\server\webpack-runtime.js:1:866)
at 1507 (C:\Users\My\Programming\nextjs-dashboard.next\server\app\seed\route.js:1:3883)
at t (C:\Users\My\Programming\nextjs-dashboard.next\server\webpack-runtime.js:1:127)
at C:\Users\My\Programming\nextjs-dashboard.next\server\app\seed\route.js:1:1176
at t.a (C:\Users\My\Programming\nextjs-dashboard.next\server\webpack-runtime.js:1:866)
at 2920 (C:\Users\My\Programming\nextjs-dashboard.next\server\app\seed\route.js:1:967)
at t (C:\Users\My\Programming\nextjs-dashboard.next\server\webpack-runtime.js:1:127) {
code: 'missing_connection_string'
}

Build error occurred
Error: Failed to collect page data for /seed
at C:\Users\My\Programming\nextjs-dashboard\node_modules.pnpm\next@15.0.0-rc.0_react-dom@19.0.0-rc-f994737d14-20240522_react@19.0.0-rc-f994737d14-20240522\node_modules\next\dist\build\utils.js:1274:15
at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
type: 'Error'
}
Collecting page data  . ELIFECYCLE  Command failed with exit code 1.

Here's the solution, greetings 👨💻

This can also be resolved by ignoring the failed deployment and skipping ahead to the part where you set up your .env file, and then redeploying. At least I believe that's the step that fixed the error for me after some trial and error.

having same issues , will try what @ZachAlba said.

I followed the solution as posted by @guzmanpdro which solved the issue of deployment .
After the successful deployment as outline there, these are the steps I followed:

I added the folder with the route.ts file once again (app/seed/route.ts)
I copy pasted this code https://github.com/vercel/next-learn/blob/main/dashboard/starter-example/app/seed/route.ts
run pnpm i @vercel/postgres in your terminal to install the Vercel Postgres SDK
Ensure your local development server is running with pnpm run dev and navigate to localhost:3000/seed in your browser.
When finished, you will see
a message "Database seeded successfully" in the browser.

Once completed, you can delete this file.

Here are all the steps above
https://nextjs.org/learn/dashboard-app/setting-up-your-database
I can then run queries and keep following along the tutorial

Cheers

authors: Kashyap-Pandya ZachAlba guzmanpdro jajos12 kaijuh


text:
Change default css extension to .pcss

I'm using postcss and i want to set .pcss as css extension since is the default extension and allow the ide to associate the correct syntax. I can't find any guide to set the extension, any tips?

Hi, thanks for creating an issue. We currently recommend using https://nextjs.org/docs/basic-features/built-in-css-support as the plugins have been deprecated in favor of the built-in support.

authors: equinusocio timneutkens

repo: vercel/next-plugins


text:
Feedback for “Arguments – SWR”

https://swr.vercel.app/docs/arguments#passing-objects
I am not sure about the two examples. Are they equal?
const { data: user } = useSWR(['/api/user', token], fetchWithToken)
const { data: orders } = useSWR(user ? ['/api/orders', user] : null, fetchWithUser)

First example has the logic to decide if the request /api/orders is to send by check user and set key to null.
How the second example does the same thing? By checking each value of the key object ({url: '...', args: user}) is undefined?

Great feedback! These two examples are not equivalent at all. We should update this to be more clear indeed.

repo: vercel/swr-site


text:
fix: cache is missing on server side

Fixes #1376

Thanks!

authors: huozhi shuding

repo: vercel/swr


text:
Question regarding the NPM "protocol"

Hi,
Is there an npmjs API/protocol description on which verdaccio/sinopia is built up on? Or is the npmjs API reverse engineered in order to make this project possible?
Thanks

I think sinopia was born as a API reverse engineered from npm. I haven't found any hint of design either on commits, wiki or history of tickets on the original project. Anyway, I was documenting which features of npm latest are actually supported by verdaccio.
https://github.com/verdaccio/verdaccio/wiki/Registry-Endpoints
Why the question?

I was implementing my own registry based on trail/error until i found sinopia and later verdaccio. I wanted to compare my own implementation with another one. It looks like that npmjs themselves do not provide a good documentation regarding the API implementation.

authors: blendsdk juanpicado

repo: verdaccio/verdaccio


text:
Good First Issue For Contributors [Hacktoberfest 2019]

Hi, if you are reading this is because you pretty likely don't know how to start 🤔 . Fair enough !
So, let's fix that 🚸 !
What should I know before start?
All here we are developers with different backgrounds, languages and objectives. But, all we must follow certain rules so we can understand each other and make the communication easier as possible. Please 👍  read your code of conduct, long story short, just be nice with everybody around here.

Code guidelines: we enforce them using eslint, so you don't have to read a long list of rules, we love automation 🤖 .
Commit guidelines: We follow the semantic versioning approach, this is really important so your PR will appear on the Changelog 🎉 ! I guess you expect recognition and we will give it to you.

That's all you need to know before start.
What can I do?
I'd assume you are completely lost 😩, that's fine ! I was it when I get started on this. Let' me help you.
You are in verdaccio core project, but actually we have 5 repositories you can contribute.

verdaccio/ui: https://github.com/verdaccio/ui (React Hooks + Webpack + Typescript + CSS3) Click here for more tickets
verdaccio/monorepo: https://github.com/verdaccio/monorepo (Typescript) Click here for more tickets
verdaccio/docker-examples: https://github.com/verdaccio/docker-examples (Docker)
verdaccio/website: https://github.com/verdaccio/website (Docusaurus + React)

If you are interested on Typescript in general, here some ideas you might help

[ ] Get rid of @ts-ignore.
[ ] Fix eslint warnings for @typescript-eslint/xxx.
[ ] Improve our @types https://github.com/verdaccio/monorepo/tree/master/core/types (better naming, document each type, remove duplications)

If you are interested mostly on Front-End, we use React@16.9

[ ] Migrate components to React Hooks https://github.com/verdaccio/ui/issues/116
[ ] Increase component coverage (either enzyme or react-testing-library
[ ] Add i18n to the UI https://github.com/verdaccio/ui/issues/102
[ ] Fix bugs They are really simple ones 🔰

If you like Docker:

[ ] Add new examples, integrations with Apache, Nginx or whatever is missing and helps other to doit themselves.

If you like Website:

[ ] New website design (https://github.com/verdaccio/website/issues/75)
[ ] Update to Docusaurus V2
[ ] Translate to new languages

If you like GitHub Actions:

[ ] Put on shape our actions https://github.com/verdaccio/github-actions

In general, you might help with other things as:

[ ] Rename variable names 👍 if you considere is not well readable
[ ] Fix FIXME:// comments
[ ] Add new plugins for the community here ⚠ we will add some guidelines how to do it.
[ ] Fix // eslint-disable-next-line new-cap eslint inline comments
[ ] Add/Fix/Improve test to Verdaccio, here a complete guideline.

If you have any suggestions, just feel free to comment this thread, or chat me over Discord 🙃 , if you are shy I accept DM over Discord. Let's us help you to grow in Open Source.
🗣 http://chat.verdaccio.org
🎉 We are ready for https://hacktoberfest.digitalocean.com/ Hacktoberfest 2019
Before PR

Keep the PR small as possible and one single topic for each
If you don't change the logic, then ignore modify the test if you don't need it

Thanks guys ! I will share soon the stats of contributions 🥳🥰


text:
htpasswd + ldap plugins not work

Describe the bug
login with command npm login or npm add user would auto adduser in htpasswd file,but not verify.
then if i execute any command need authorized such as npm info xxx, it would return E403 if the username & password not verified by ldap plugin. and i can't relogin with the collect username & password again because the account were already in the htpasswd file.
To Reproduce
Steps to reproduce the behavior:

excute npm adduser --registy=http:localhost:4873
type the right username and wrong password
excute npm info react
See Error return E403
redo step 1 - 4 but type right username & right password in step2
See the same error as step4

Expected behavior
npm login with wrong username or wrong password should be crash
Screenshots
Docker || Kubernetes (please complete the following information):

Docker verdaccio tag: [e.g. verdaccio:beta]
Docker commands [e.g. docker pull ...]
Docker Version [e.g. v18.05.0-ce-rc1]

Configuration File (cat ~/.config/verdaccio/config.yaml)
Debugging output

$ NODE_DEBUG=request verdaccio display request calls (verdaccio <--> uplinks)
$ DEBUG=express:* verdaccio enable extreme verdaccio debug mode (verdaccio api)
$ npm -ddd prints:
$ npm config get registry prints:

Additional context
verdaccio@3.7.1
verdaccio-ldap@3.0.0

@vegawong
About ldap plugin:
I'd rather first ask here https://github.com/Alexandre-io/verdaccio-ldap I cannot do too much.
About the htpasswd I think you need to share the config file first.

@juanpicado thank reply!
about the auth config like this:
auth:
  htpasswd:
    file: /app/data/htpasswd
    # Maximum amount of users allowed to register, defaults to "+infinity".
    # You can set this to -1 to disable registration.
    max_users: 1001
  ldap:
  ...

BTW: my npm version is 5.6.0, it's login action didn't add token to the npmrc file

@vegawong can you describe what do you want to achieve with such configuration?

@juanpicado Some months before, i use verdaccio@2.7.4 & ldap@1.4.0, and no htpasswd node in the the config file, then it work! But there wasn't perfect for me that i can use npm adduser with any wrong userAccount in ldap server, throuth it could be verified in other action.
I uprade it to verdaccio@3.7.1 & ldap@3.0.0 yesterday! Then something break!
If i didn't add htpasswd in the config file, I couldn't login with the npm command.
Then i try to add htpasswd like such configuration, i can adduser but ldap not verify even in the other action runtime, such as i can use any wrong user to catch the package from the registry. And i can't remove the wrong account from the htpasswd except i edit the htpasswd file manually.
I guess there is some break change from version 2.x to 3.x. Is there any example newer for version 3.x?

Yeah, many things changed on verdaccio3, it might be a bug or something intended. I'd like to have a set of exact steps to reproduce it. Complete conf for LDAP than I can reproduce it locally.
If you can help with https://github.com/verdaccio/docker-examples/tree/master/ldap-verdaccio would be great to make it run and that will help to issues with external plugins. I have little experience with LDAP.
Verdaccio 4 is under development and we might take care of this wrong behaviour if something wrong was done in verdaccio3.

thanks! @juanpicado
I found the solution for me that only use ldap but not htpasswd.
Open npm config always-auth section that only could be login but without register, and all auth action by ldap plugin. But ldap has something not pretty that exec auth action spend a long time.
I had take a PR to support cache for the ldap plugin.  Now it work find for me!
Thanks for your help!

authors: juanpicado vegawong


text:
Bugfix time inputs versus time transaction

Tx inputs should NOT be younger than the inputs for the transactions itself.
No value-added, just V4 compatibility. :)

@justinvforvendetta miners gave their thumbs up towards this fix, could you please make your due diligence, thanks <3

repo: vergecurrency/VERGE

license: mit


text:
[Verification contracts] Check & update test code of contracts for verida-js update

Check test codes that uses the keyring to make signedData & signedProof
Need to test contract that inherits the VerificationBase contract

verida-js had some changes that relate to introducing @verida/types package.
This has broken some of the blockchain-contract unit tests.
This issue is to fix those unit tests using the updated protocol.

repo: verida/blockchain-contracts


text:
Where is the ds_config.json

Thanks for publishing the codebase! But when I tried to use the command in the README to finetune the LM, there is a flag --deepspeed ds_config.json. But seems the ds_config.json is not provided. Is there anything wrong? @vermouthdky

Hi there. Thanks for reaching out. Mine used ds_config is
{
"fp16": {
"enabled": "auto",

"initial_scale_power": 12

},
"bf16":{
"enabled": "auto"
},
"zero_optimization": {
"stage": 2,

"reduce_bucket_size": 5e7,

"allgather_bucket_size": 1.25e9,

"overlap_comm": true,

"contiguous_gradients": true

},
"zero_allow_untested_optimizer": true,
"train_micro_batch_size_per_gpu": "auto"
}
which is a standard second stage deepspeed. Also, if you do want to use deepspeed, you can just comment out this line, and everything should be fine.

Thanks!!

repo: vermouthdky/SimTeG


text:
feat(helm): configurable scrape interval for ServiceMonitor

This enables a configurable scrape interval when using the ServiceMonitor for Prometheus Operator.
Defaults to 30s as per existing behaviour.

@rjmoseley Thanks... jep, this certainly makes sense

👉 Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq
👉 Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription.

authors: ioolkos rjmoseley

repo: vernemq/docker-vernemq


text:
OpenClash程序正常运行，但设备无法出国

之前好好的，今天停了下电就拉闸了...V大救救我！！！
运行日志中有以下两条报错：
2021-04-18 21:07:09 Set Custom Rules Error: undefined method each' for #<String:0x000000000138dd20> 2021-04-18 21:07:09 Set General Error: undefined method clear' for nil:NilClass
以下是调试日志：
OpenClash 调试日志
生成时间: 2021-04-18 21:10:49
插件版本: v0.42.04-beta
隐私提示: 上传此日志前请注意检查、屏蔽公网IP、节点、密码等相关敏感信息

#===================== 系统信息 =====================#

主机型号: Intel(R) Core(TM) i5-9400T CPU @ 1.80GHz : 6 Core 6 Thread
固件版本: OpenWrt SNAPSHOT r3147-c41c174be
LuCI版本: git-21.096.35788-b200c7b-1
内核版本: 5.4.109
处理器架构: x86_64

#此项在使用Tun模式时应为ACCEPT
防火墙转发: ACCEPT

#此项有值时建议到网络-接口-lan的设置中禁用IPV6的DHCP
IPV6-DHCP: server

#此项结果应仅有配置文件的DNS监听地址
Dnsmasq转发设置:

#===================== 依赖检查 =====================#

dnsmasq-full: 已安装
coreutils: 已安装
coreutils-nohup: 已安装
bash: 已安装
curl: 已安装
jsonfilter: 已安装
ca-certificates: 已安装
ipset: 已安装
ip-full: 已安装
iptables-mod-tproxy: 已安装
kmod-ipt-tproxy: 已安装
iptables-mod-extra: 已安装
kmod-ipt-extra: 已安装
libcap: 已安装
libcap-bin: 已安装
ruby: 已安装
ruby-yaml: 已安装
ruby-psych: 已安装
ruby-pstore: 已安装
ruby-dbm: 已安装
kmod-tun(TUN模式): 已安装
luci-compat(Luci-19.07): 已安装

#===================== 内核检查 =====================#

运行状态: 运行中
进程pid: 62159
运行权限: 62159: = cap_dac_override,cap_net_bind_service,cap_net_admin,cap_net_raw,cap_sys_resource+eip
运行用户: nobody
已选择的架构: linux-amd64

#下方无法显示内核版本号时请确认您的内核版本是否正确或者有无权限
Tun内核版本:
Tun内核文件: 存在
Tun内核运行权限: 正常

Game内核版本:
Game内核文件: 不存在
Game内核运行权限: 否

Dev内核版本:
Dev内核文件: 不存在
Dev内核运行权限: 否

#===================== 插件设置 =====================#

当前配置文件: /etc/openclash/config/config.yaml
启动配置文件: /etc/openclash/config.yaml
运行模式: fake-ip
默认代理模式: rule
UDP流量转发(tproxy): 启用
DNS劫持: 停用
自定义DNS: 启用
IPV6-DNS解析: 停用
禁用Dnsmasq缓存: 停用
自定义规则: 启用
仅允许内网: 停用
仅代理命中规则流量: 停用
仅允许常用端口流量: 停用
绕过中国大陆IP: 停用

#启动异常时建议关闭此项后重试
混合节点: 停用
保留配置: 停用

#启动异常时建议关闭此项后重试
第三方规则: 停用

#===================== 自定义规则 一 =====================#
##- DOMAIN-SUFFIX,google.com,Proxy 匹配域名后缀(交由Proxy代理服务器组)
##- DOMAIN-KEYWORD,google,Proxy 匹配域名关键字(交由Proxy代理服务器组)
##- DOMAIN,google.com,Proxy 匹配域名(交由Proxy代理服务器组)
##- DOMAIN-SUFFIX,ad.com,REJECT 匹配域名后缀(拒绝)
##- IP-CIDR,127.0.0.0/8,DIRECT 匹配数据目标IP(直连)
##- SRC-IP-CIDR,192.168.1.201/32,DIRECT 匹配数据发起IP(直连)
##- DST-PORT,80,DIRECT 匹配数据目标端口(直连)
##- SRC-PORT,7777,DIRECT 匹配数据源端口(直连)

##排序在上的规则优先生效,如添加（去除规则前的#号）：
##IP段：192.168.1.2-192.168.1.200 直连
##- SRC-IP-CIDR,192.168.1.2/31,DIRECT
##- SRC-IP-CIDR,192.168.1.4/30,DIRECT
##- SRC-IP-CIDR,192.168.1.8/29,DIRECT
##- SRC-IP-CIDR,192.168.1.16/28,DIRECT
##- SRC-IP-CIDR,192.168.1.32/27,DIRECT
##- SRC-IP-CIDR,192.168.1.64/26,DIRECT
##- SRC-IP-CIDR,192.168.1.128/26,DIRECT
##- SRC-IP-CIDR,192.168.1.192/29,DIRECT
##- SRC-IP-CIDR,192.168.1.200/32,DIRECT

##IP段：192.168.1.202-192.168.1.255 直连
##- SRC-IP-CIDR,192.168.1.202/31,DIRECT
##- SRC-IP-CIDR,192.168.1.204/30,DIRECT
##- SRC-IP-CIDR,192.168.1.208/28,DIRECT
##- SRC-IP-CIDR,192.168.1.224/27,DIRECT

##此时IP为192.168.1.1和192.168.1.201的客户端流量走代理（策略），其余客户端不走代理
##因为Fake-IP模式下，IP地址为192.168.1.1的路由器自身流量可走代理（策略），所以需要排除

##仅设置路由器自身直连：
##- SRC-IP-CIDR,192.168.1.1/32,DIRECT
##- SRC-IP-CIDR,198.18.0.1/32,DIRECT

##直连内网设备IP：
##- SRC-IP-CIDR,192.168.1.160/32,DIRECT

##DDNS
-DOMAIN-SUFFIX,checkip.dyndns.org,DIRECT
-DOMAIN-SUFFIX,checkipv6.dyndns.org,DIRECT
-DOMAIN-SUFFIX,checkip.synology.com,DIRECT
-DOMAIN-SUFFIX,ifconfig.co,DIRECT
-DOMAIN-SUFFIX,api.myip.com,DIRECT
-DOMAIN-SUFFIX,ip-api.com,DIRECT
-DOMAIN-SUFFIX,ipapi.co,DIRECT
-DOMAIN-SUFFIX,ip6.seeip.org,DIRECT
-DOMAIN-SUFFIX,members.3322.org,DIRECT
-DOMAIN-SUFFIX,www.test-ipv6.com,DIRECT

##China DNS Sever
- IP-CIDR,61.166.150.123,DIRECT
- IP-CIDR,222.172.200.68,DIRECT

##在线IP段转CIDR地址：http://ip2cidr.com
#===================== 自定义规则 二 =====================#
##- DOMAIN-SUFFIX,google.com,Proxy 匹配域名后缀(交由Proxy代理服务器组)
##- DOMAIN-KEYWORD,google,Proxy 匹配域名关键字(交由Proxy代理服务器组)
##- DOMAIN,google.com,Proxy 匹配域名(交由Proxy代理服务器组)
##- DOMAIN-SUFFIX,ad.com,REJECT 匹配域名后缀(拒绝)
##- IP-CIDR,127.0.0.0/8,DIRECT 匹配数据目标IP(直连)
##- SRC-IP-CIDR,192.168.1.201/32,DIRECT 匹配数据发起IP(直连)
##- DST-PORT,80,DIRECT 匹配数据目标端口(直连)
##- SRC-PORT,7777,DIRECT 匹配数据源端口(直连)

#===================== 配置文件 =====================#

port: 7890
socks-port: 7891
redir-port: 7892
mixed-port: 7893
allow-lan: true
bind-address: "*"
ipv6: false
mode: rule
log-level: silent
external-controller: 0.0.0.0:9090
external-ui: "/usr/share/openclash/dashboard"
authentication: []
tun:
hosts:
profile:
  store-selected: true
  tracing: true
dns:
  enhanced-mode: fake-ip
  fake-ip-range: 198.18.0.1/16
  listen: 127.0.0.1:2255
  enable: true
  ipv6: false
  fake-ip-filter:
  - "*.lan"
  - time.windows.com
  - time.nist.gov
  - time.apple.com
  - time.asia.apple.com
  - "*.ntp.org.cn"
  - "*.openwrt.pool.ntp.org"
  - time1.cloud.tencent.com
  - time.ustc.edu.cn
  - pool.ntp.org
  - ntp.ubuntu.com
  - ntp.aliyun.com
  - ntp1.aliyun.com
  - ntp2.aliyun.com
  - ntp3.aliyun.com
  - ntp4.aliyun.com
  - ntp5.aliyun.com
  - ntp6.aliyun.com
  - ntp7.aliyun.com
  - time1.aliyun.com
  - time2.aliyun.com
  - time3.aliyun.com
  - time4.aliyun.com
  - time5.aliyun.com
  - time6.aliyun.com
  - time7.aliyun.com
  - "*.time.edu.cn"
  - time1.apple.com
  - time2.apple.com
  - time3.apple.com
  - time4.apple.com
  - time5.apple.com
  - time6.apple.com
  - time7.apple.com
  - time1.google.com
  - time2.google.com
  - time3.google.com
  - time4.google.com
  - music.163.com
  - "*.music.163.com"
  - "*.126.net"
  - musicapi.taihe.com
  - music.taihe.com
  - songsearch.kugou.com
  - trackercdn.kugou.com
  - "*.kuwo.cn"
  - api-jooxtt.sanook.com
  - api.joox.com
  - joox.com
  - y.qq.com
  - "*.y.qq.com"
  - streamoc.music.tc.qq.com
  - mobileoc.music.tc.qq.com
  - isure.stream.qqmusic.qq.com
  - dl.stream.qqmusic.qq.com
  - aqqmusic.tc.qq.com
  - amobile.music.tc.qq.com
  - "*.xiami.com"
  - "*.music.migu.cn"
  - music.migu.cn
  - "*.msftconnecttest.com"
  - "*.msftncsi.com"
  - localhost.ptlogin2.qq.com
  - "*.*.*.srv.nintendo.net"
  - "*.*.stun.playstation.net"
  - xbox.*.*.microsoft.com
  - "*.*.xboxlive.com"
  - "+.battlenet.com.cn"
  - "*.linksyssmartwifi.com"
  - "*.linksys.com"
  - heartbeat.belkin.com
  - stun.*.*.*
  - stun.*.*
  - proxy.golang.org
  - "+.xboxlive.com"
  - xbox.*.microsoft.com
  - "+.stun.playstation.net"
  - "+.srv.nintendo.net"
  nameserver:
  - 127.0.0.1:2254
  - https://127.0.0.1:2254
  - tls://127.0.0.1:2254
  - tcp://127.0.0.1:2254
proxy-groups:
- name: Main Load-Balance
  type: load-balance
  url: http://www.gstatic.com/generate_204
  interval: 180
  proxies:
*
- name: 香港
  type: load-balance
  url: http://www.gstatic.com/generate_204
  interval: 180
  proxies:
*
- name: 台湾
  type: load-balance
  url: http://www.gstatic.com/generate_204
  interval: 180
  proxies:
*
- name: 新加坡
  type: load-balance
  url: http://www.gstatic.com/generate_204
  interval: 180
  proxies:
*
- name: 日本
  type: load-balance
  url: http://www.gstatic.com/generate_204
  interval: 180
  proxies:
*
- name: 韩国
  type: select
  proxies:
*
- name: 美国
  type: load-balance
  url: http://www.gstatic.com/generate_204
  interval: 180
  proxies:
*
- name: 欧洲
  type: select
  proxies:
*
- name: 澳洲
  type: select
  proxies:
*
- name: 南美
  type: select
  proxies:
*
- name: Proxy
  type: select
  proxies:
*
- name: ***gle Search
  type: select
  proxies:
*
- name: Academic
  type: select
  proxies:
*
- name: *ou*ube
  type: select
  proxies:
*
- name: Steam
  type: select
  proxies:
*
- name: *orn*ub
  type: select
  proxies:
*
- name: Netflix
  type: select
  proxies:
*
- name: Apple
  type: select
  proxies:
*
- name: Apple AppStore
  type: select
  proxies:
*
- name: Apple TV
  type: select
  proxies:
*
- name: Apple TestFlight
  type: select
  proxies:
*
- name: Apple News
  type: select
  proxies:
*
- name: Prime Video
  type: select
  proxies:
*
- name: Bilibili
  type: select
  proxies:
*
- name: Microsoft
  type: select
  proxies:
*
- name: Telegram
  type: select
  proxies:
*
- name: Other
  type: select
  proxies:
*
rules:
- IP-CIDR,198.18.0.1/16,REJECT,no-resolve
- RULE-SET,GoogleSearch,Google Search
- RULE-SET,学术网站,Academic
- RULE-SET,*ou*ube,*ouTube
- RULE-SET,*ou*ube*usic,*ouTube
- RULE-SET,Steam,Steam
- RULE-SET,*orn*ub(By lhie1),*orn*ub
- RULE-SET,Netflix,Netflix
- RULE-SET,Apple,Apple
- RULE-SET,AppStore,Apple AppStore
- RULE-SET,Apple TV(By lhie1),Apple TV
- RULE-SET,Apple TestFlight,Apple TestFlight
- RULE-SET,Apple News(By lhie1),Apple News
- RULE-SET,Prime-Video,Prime Video
- RULE-SET,Bilibili,Bilibili
- RULE-SET,微软服务,Microsoft
- RULE-SET,Telegram,Telegram
- RULE-SET,****白名单,DIRECT
- RULE-SET,**IP白名单,DIRECT
- RULE-SET,审计规则（建议直连）,DIRECT
- RULE-SET,**常用网站合集,Proxy
- RULE-SET,隐私规则合集,REJECT
- RULE-SET,反劫持规则,REJECT
- MATCH,Other
rule-providers:
  GoogleSearch:
    type: http
    behavior: classical
    path: "/etc/openclash/rule_provider/GoogleSearch.yaml"
    url: https://cdn.jsdelivr.net/gh/DivineEngine/Profiles@master/Clash/RuleSet/Extra/Google/GoogleSearch.yaml
    interval: 86400
  学术网站:
    type: http
    behavior: classical
    path: "/etc/openclash/rule_provider/Scholar.yaml"
    url: https://cdn.jsdelivr.net/gh/DivineEngine/Profiles@master/Clash/RuleSet/Extra/Scholar.yaml
    interval: 86400
  *ou*ube:
    type: http
    behavior: classical
    path: "/etc/openclash/rule_provider/YouTube.yaml"
    url: https://cdn.jsdelivr.net/gh/DivineEngine/Profiles@master/Clash/RuleSet/StreamingMedia/Video/YouTube.yaml
    interval: 86400
  *ou*ube*usic:
    type: http
    behavior: classical
    path: "/etc/openclash/rule_provider/YouTubeMusic.yaml"
    url: https://cdn.jsdelivr.net/gh/DivineEngine/Profiles@master/Clash/RuleSet/StreamingMedia/Music/YouTubeMusic.yaml
    interval: 86400
  Steam:
    type: http
    behavior: classical
    path: "/etc/openclash/rule_provider/Steam.yaml"
    url: https://cdn.jsdelivr.net/gh/lhie1/Rules@master/Clash/Provider/Steam.yaml
    interval: 86400
  *orn*ub(By lhie1):
    type: http
    behavior: classical
    path: "/etc/openclash/rule_provider/Pornhub-lhie1.yaml"
    url: https://cdn.jsdelivr.net/gh/lhie1/Rules@master/Clash/Provider/Media/Pornhub.yaml
    interval: 86400
  Netflix:
    type: http
    behavior: classical
    path: "/etc/openclash/rule_provider/Netflix.yaml"
    url: https://cdn.jsdelivr.net/gh/DivineEngine/Profiles@master/Clash/RuleSet/StreamingMedia/Video/Netflix.yaml
    interval: 86400
  Apple:
    type: http
    behavior: classical
    path: "/etc/openclash/rule_provider/Apple.yaml"
    url: https://cdn.jsdelivr.net/gh/DivineEngine/Profiles@master/Clash/RuleSet/Extra/Apple/Apple.yaml
    interval: 86400
  AppStore:
    type: http
    behavior: classical
    path: "/etc/openclash/rule_provider/AppStore.yaml"
    url: https://cdn.jsdelivr.net/gh/DivineEngine/Profiles@master/Clash/RuleSet/Extra/Apple/AppStore.yaml
    interval: 86400
  Apple TV(By lhie1):
    type: http
    behavior: classical
    path: "/etc/openclash/rule_provider/Apple TV.yaml"
    url: https://cdn.jsdelivr.net/gh/lhie1/Rules@master/Clash/Provider/Media/Apple%20TV.yaml
    interval: 86400
  Apple TestFlight:
    type: http
    behavior: classical
    path: "/etc/openclash/rule_provider/TestFlight.yaml"
    url: https://cdn.jsdelivr.net/gh/DivineEngine/Profiles@master/Clash/RuleSet/Extra/Apple/TestFlight.yaml
    interval: 86400
  Apple News(By lhie1):
    type: http
    behavior: classical
    path: "/etc/openclash/rule_provider/Apple News.yaml"
    url: https://cdn.jsdelivr.net/gh/lhie1/Rules@master/Clash/Provider/Media/Apple%20News.yaml
    interval: 86400
  Prime-Video:
    type: http
    behavior: classical
    path: "/etc/openclash/rule_provider/Prime-Video.yaml"
    url: https://cdn.jsdelivr.net/gh/DivineEngine/Profiles@master/Clash/RuleSet/StreamingMedia/Video/Prime-Video.yaml
    interval: 86400
  Bilibili:
    type: http
    behavior: classical
    path: "/etc/openclash/rule_provider/Bilibili.yaml"
    url: https://cdn.jsdelivr.net/gh/lhie1/Rules@master/Clash/Provider/Media/Bilibili.yaml
    interval: 86400
  微软服务:
    type: http
    behavior: classical
    path: "/etc/openclash/rule_provider/Microsoft.yaml"
    url: https://cdn.jsdelivr.net/gh/lhie1/Rules@master/Clash/Provider/Microsoft.yaml
    interval: 86400
  *elegram:
    type: http
    behavior: classical
    path: "/etc/openclash/rule_provider/Telegram.yaml"
    url: https://cdn.jsdelivr.net/gh/DivineEngine/Profiles@master/Clash/RuleSet/Extra/Telegram/Telegram.yaml
    interval: 86400
  国内域名白名单:
    type: http
    behavior: classical
    path: "/etc/openclash/rule_provider/China.yaml"
    url: https://cdn.jsdelivr.net/gh/DivineEngine/Profiles@master/Clash/RuleSet/China.yaml
    interval: 86400
  **IP白名单:
    type: http
    behavior: ipcidr
    path: "/etc/openclash/rule_provider/ChinaIP.yaml"
    url: https://cdn.jsdelivr.net/gh/DivineEngine/Profiles@master/Clash/RuleSet/Extra/ChinaIP.yaml
    interval: 86400
  审计规则（建议直连）:
    type: http
    behavior: classical
    path: "/etc/openclash/rule_provider/Special.yaml"
    url: https://cdn.jsdelivr.net/gh/lhie1/Rules@master/Clash/Provider/Special.yaml
    interval: 86400
  **常用网站合集:
    type: http
    behavior: classical
    path: "/etc/openclash/rule_provider/Global.yaml"
    url: https://cdn.jsdelivr.net/gh/DivineEngine/Profiles@master/Clash/RuleSet/Global.yaml
    interval: 86400
  隐私规则合集:
    type: http
    behavior: classical
    path: "/etc/openclash/rule_provider/Privacy.yaml"
    url: https://cdn.jsdelivr.net/gh/DivineEngine/Profiles@master/Clash/RuleSet/Guard/Privacy.yaml
    interval: 86400
  反劫持规则:
    type: http
    behavior: classical
    path: "/etc/openclash/rule_provider/Hijacking.yaml"
    url: https://cdn.jsdelivr.net/gh/DivineEngine/Profiles@master/Clash/RuleSet/Guard/Hijacking.yaml
    interval: 86400

#===================== 防火墙设置 =====================#

#NAT chain

# Generated by iptables-save v1.8.4 on Sun Apr 18 21:10:49 2021
*nat
:PREROUTING ACCEPT [378:47025]
:INPUT ACCEPT [536:56213]
:OUTPUT ACCEPT [2125:166289]
:POSTROUTING ACCEPT [1359:85278]
:CLOUD_MUSIC - [0:0]
:openclash - [0:0]
:openclash_output - [0:0]
:postrouting_lan_rule - [0:0]
:postrouting_rule - [0:0]
:postrouting_wan_rule - [0:0]
:prerouting_lan_rule - [0:0]
:prerouting_rule - [0:0]
:prerouting_wan_rule - [0:0]
:zone_lan_postrouting - [0:0]
:zone_lan_prerouting - [0:0]
:zone_wan_postrouting - [0:0]
:zone_wan_prerouting - [0:0]
-A PREROUTING -d 8.8.4.4/32 -p tcp -m tcp --dport 53 -j REDIRECT --to-ports 7892
-A PREROUTING -d 8.8.8.8/32 -p tcp -m tcp --dport 53 -j REDIRECT --to-ports 7892
-A PREROUTING -p tcp -m set --match-set music dst -j CLOUD_MUSIC
-A PREROUTING -m comment --comment "!fw3: Custom prerouting rule chain" -j prerouting_rule
-A PREROUTING -i eth0 -m comment --comment "!fw3" -j zone_lan_prerouting
-A PREROUTING -p tcp -j openclash
-A OUTPUT -j openclash_output
-A POSTROUTING -m comment --comment "!fw3: Custom postrouting rule chain" -j postrouting_rule
-A POSTROUTING -o eth0 -m comment --comment "!fw3" -j zone_lan_postrouting
-A CLOUD_MUSIC -d 0.0.0.0/8 -j RETURN
-A CLOUD_MUSIC -d 10.0.0.0/8 -j RETURN
-A CLOUD_MUSIC -d 127.0.0.0/8 -j RETURN
-A CLOUD_MUSIC -d 169.254.0.0/16 -j RETURN
-A CLOUD_MUSIC -d 172.16.0.0/12 -j RETURN
-A CLOUD_MUSIC -d 192.168.0.0/16 -j RETURN
-A CLOUD_MUSIC -d 224.0.0.0/4 -j RETURN
-A CLOUD_MUSIC -d 240.0.0.0/4 -j RETURN
-A CLOUD_MUSIC -p tcp -m set ! --match-set music_http src -m tcp --dport 80 -j REDIRECT --to-ports 5200
-A CLOUD_MUSIC -p tcp -m set ! --match-set music_https src -m tcp --dport 443 -j REDIRECT --to-ports 5201
-A openclash -m set --match-set localnetwork dst -j RETURN
-A openclash -p tcp -j REDIRECT --to-ports 7892
-A openclash_output -p tcp -m tcp --sport 1688 -j RETURN
-A openclash_output -p tcp -m tcp --sport 8443 -j RETURN
-A openclash_output -p tcp -m tcp --sport 8880 -j RETURN
-A openclash_output -m set --match-set localnetwork dst -j RETURN
-A openclash_output -d 198.18.0.0/16 -p tcp -m owner ! --uid-owner 65534 -j REDIRECT --to-ports 7892
-A openclash_output -p tcp -m owner ! --uid-owner 65534 -j REDIRECT --to-ports 7892
-A zone_lan_postrouting -m comment --comment "!fw3: Custom lan postrouting rule chain" -j postrouting_lan_rule
-A zone_lan_postrouting -m comment --comment "!fw3: 回流" -j SNAT --to-source 192.168.1.22
-A zone_lan_prerouting -m comment --comment "!fw3: Custom lan prerouting rule chain" -j prerouting_lan_rule
-A zone_lan_prerouting -p tcp -m tcp --dport 8880 -m comment --comment "!fw3: Ubuntu80" -j DNAT --to-destination 192.168.1.6:80
-A zone_lan_prerouting -p udp -m udp --dport 8880 -m comment --comment "!fw3: Ubuntu80" -j DNAT --to-destination 192.168.1.6:80
-A zone_lan_prerouting -p tcp -m tcp --dport 8443 -m comment --comment "!fw3: Ubuntu443" -j DNAT --to-destination 192.168.1.6:443
-A zone_lan_prerouting -p udp -m udp --dport 8443 -m comment --comment "!fw3: Ubuntu443" -j DNAT --to-destination 192.168.1.6:443
-A zone_wan_postrouting -m comment --comment "!fw3: Custom wan postrouting rule chain" -j postrouting_wan_rule
-A zone_wan_prerouting -m comment --comment "!fw3: Custom wan prerouting rule chain" -j prerouting_wan_rule
COMMIT
# Completed on Sun Apr 18 21:10:49 2021

#Mangle chain

# Generated by iptables-save v1.8.4 on Sun Apr 18 21:10:49 2021
*mangle
:PREROUTING ACCEPT [46460:47817413]
:INPUT ACCEPT [47771:48155022]
:FORWARD ACCEPT [2014:607112]
:OUTPUT ACCEPT [36666:49053249]
:POSTROUTING ACCEPT [38667:49659071]
:openclash - [0:0]
-A PREROUTING -p udp -j openclash
-A openclash -p udp -m udp --dport 500 -j RETURN
-A openclash -p udp -m udp --dport 546 -j RETURN
-A openclash -p udp -m udp --dport 68 -j RETURN
-A openclash -p udp -m udp --dport 8443 -j RETURN
-A openclash -p udp -m udp --dport 8880 -j RETURN
-A openclash -m set --match-set localnetwork dst -j RETURN
-A openclash -p udp -m udp --dport 53 -j RETURN
-A openclash -p udp -j TPROXY --on-port 7892 --on-ip 0.0.0.0 --tproxy-mark 0x162/0xffffffff
COMMIT
# Completed on Sun Apr 18 21:10:49 2021

#===================== IPSET状态 =====================#

Name: music
Name: music_http
Name: music_https
Name: localnetwork

#===================== 路由表状态 =====================#

#route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.11    0.0.0.0         UG    0      0        0 eth0
172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0 docker0
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
#ip route list
default via 192.168.1.11 dev eth0 proto static
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.22
#ip rule show
0:	from all lookup local
32765:	from all fwmark 0x162 lookup 354
32766:	from all lookup main
32767:	from all lookup default

#===================== 端口占用状态 =====================#

tcp        0      0 :::7890                 :::*                    LISTEN      62159/clash
tcp        0      0 :::7891                 :::*                    LISTEN      62159/clash
tcp        0      0 :::7892                 :::*                    LISTEN      62159/clash
tcp        0      0 :::7893                 :::*                    LISTEN      62159/clash
tcp        0      0 :::9090                 :::*                    LISTEN      62159/clash
udp        0      0 127.0.0.1:2255          0.0.0.0:*                           62159/clash
udp        0      0 :::41562                :::*                                62159/clash
udp        0      0 :::44653                :::*                                62159/clash
udp        0      0 :::57972                :::*                                62159/clash
udp        0      0 :::37549                :::*                                62159/clash
udp        0      0 :::54959                :::*                                62159/clash
udp        0      0 :::51914                :::*                                62159/clash
udp        0      0 :::7891                 :::*                                62159/clash
udp        0      0 :::7892                 :::*                                62159/clash
udp        0      0 :::7893                 :::*                                62159/clash
udp        0      0 :::58127                :::*                                62159/clash
udp        0      0 :::53014                :::*                                62159/clash
udp        0      0 :::35819                :::*                                62159/clash
udp        0      0 :::36144                :::*                                62159/clash
udp        0      0 :::58699                :::*                                62159/clash
udp        0      0 :::47463                :::*                                62159/clash
udp        0      0 :::47469                :::*                                62159/clash

#===================== 测试本机DNS查询 =====================#

Server:		127.0.0.1
Address:	127.0.0.1#53

Name:      www.baidu.com
www.baidu.com	canonical name = www.a.shifen.com
Name:      www.a.shifen.com
Address 1: 14.215.177.38
www.baidu.com	canonical name = www.a.shifen.com

#===================== resolv.conf.d =====================#

# Interface lan
nameserver 192.168.1.22
nameserver fe80::20c:29ff:fe27:681%eth0
# Interface lan6
nameserver fe80::20c:29ff:fe27:681%eth0

#===================== 测试本机网络连接 =====================#

HTTP/1.1 200 OK
Accept-Ranges: bytes
Cache-Control: private, no-cache, no-store, proxy-revalidate, no-transform
Connection: keep-alive
Content-Length: 277
Content-Type: text/html
Date: Sun, 18 Apr 2021 13:10:50 GMT
Etag: "575e1f72-115"
Last-Modified: Mon, 13 Jun 2016 02:50:26 GMT
Pragma: no-cache
Server: bfe/1.0.8.18

#===================== 测试本机网络下载 =====================#

#===================== 最近运行日志 =====================#

2021-04-18 21:07:06 Warning: OpenClash Start Successful, Please Note That Network May Abnormal With IPV6's DHCP Server
2021-04-18 21:07:37 Groups History:【config.yaml】 Restore Successful
2021-04-18 21:07:32 level=info msg="DNS server listening at: 127.0.0.1:2255"
2021-04-18 21:07:32 level=info msg="Start initial rule provider *orn*ub(By lhie1)"
2021-04-18 21:07:32 level=info msg="Start initial rule provider *ou*ube"
2021-04-18 21:07:32 level=info msg="Start initial rule provider 审计规则（建议直连）"
2021-04-18 21:07:32 level=info msg="Start initial rule provider 国内域名白名单"
2021-04-18 21:07:32 level=info msg="Start initial rule provider Prime-Video"
2021-04-18 21:07:32 level=info msg="Start initial rule provider 学术网站"
2021-04-18 21:07:32 level=info msg="Start initial rule provider 微软服务"
2021-04-18 21:07:32 level=info msg="Start initial rule provider Apple TestFlight"
2021-04-18 21:07:32 level=info msg="Start initial rule provider Steam"
2021-04-18 21:07:32 level=info msg="Start initial rule provider AppStore"
2021-04-18 21:07:32 level=info msg="Start initial rule provider *oogle*earch"
2021-04-18 21:07:32 level=info msg="Start initial rule provider Apple TV(By lhie1)"
2021-04-18 21:07:32 level=info msg="Start initial rule provider Apple News(By lhie1)"
2021-04-18 21:07:32 level=info msg="Start initial rule provider 反劫持规则"
2021-04-18 21:07:32 level=info msg="Start initial rule provider Telegram"
2021-04-18 21:07:32 level=info msg="Start initial rule provider 隐私规则合集"
2021-04-18 21:07:32 level=info msg="Start initial rule provider Apple"
2021-04-18 21:07:32 level=info msg="Start initial rule provider *ou*ube*usic"
2021-04-18 21:07:32 level=info msg="Start initial rule provider 国外常用网站合集"
2021-04-18 21:07:32 level=info msg="Start initial rule provider 国内IP白名单"
2021-04-18 21:07:32 level=info msg="Start initial rule provider Bilibili"
2021-04-18 21:07:32 level=info msg="Start initial rule provider Netflix"
2021-04-18 21:07:32 level=info msg="Start initial compatible provider *oogle Search"
2021-04-18 21:07:32 level=info msg="Start initial compatible provider 香港"
2021-04-18 21:07:32 level=info msg="Start initial compatible provider Apple News"
2021-04-18 21:07:32 level=info msg="Start initial compatible provider Apple"
2021-04-18 21:07:32 level=info msg="Start initial compatible provider Academic"
2021-04-18 21:07:32 level=info msg="Start initial compatible provider Netflix"
2021-04-18 21:07:32 level=info msg="Start initial compatible provider Apple AppStore"
2021-04-18 21:07:32 level=info msg="Start initial compatible provider Other"
2021-04-18 21:07:32 level=info msg="Start initial compatible provider 美国"
2021-04-18 21:07:32 level=info msg="Start initial compatible provider 新加坡"
2021-04-18 21:07:32 level=info msg="Start initial compatible provider *ou*ube"
2021-04-18 21:07:32 level=info msg="Start initial compatible provider *orn*ub"
2021-04-18 21:07:32 level=info msg="Start initial compatible provider Prime Video"
2021-04-18 21:07:32 level=info msg="Start initial compatible provider 日本"
2021-04-18 21:07:32 level=info msg="Start initial compatible provider 欧洲"
2021-04-18 21:07:32 level=info msg="Start initial compatible provider 澳洲"
2021-04-18 21:07:32 level=info msg="Start initial compatible provider Apple TestFlight"
2021-04-18 21:07:32 level=info msg="Start initial compatible provider Telegram"
2021-04-18 21:07:32 level=info msg="Start initial compatible provider Apple TV"
2021-04-18 21:07:32 level=info msg="Start initial compatible provider Main Load-Balance"
2021-04-18 21:07:32 level=info msg="Start initial compatible provider 南美"
2021-04-18 21:07:32 level=info msg="Start initial compatible provider Microsoft"
2021-04-18 21:07:32 level=info msg="Start initial compatible provider Steam"
2021-04-18 21:07:32 level=info msg="Start initial compatible provider 韩国"
2021-04-18 21:07:32 level=info msg="Start initial compatible provider Proxy"
2021-04-18 21:07:32 level=info msg="Start initial compatible provider 台湾"
2021-04-18 21:07:32 level=info msg="Start initial compatible provider Bilibili"
2021-04-18 21:07:09 Set Custom Rules Error: undefined method `each' for #<String:0x000000000138dd20>
2021-04-18 21:07:09 Set General Error: undefined method `clear' for nil:NilClass

DNS劫持开了，自定义规则里的DDNS格式少了个空格

空格是我大意了（捂脸），修改dns劫持和规则后还是不能旅游。但报错少了一条。只剩下：
Set General Error: undefined method `clear' for nil:NilClass

authentication: []
tun:
hosts:
删了

问题已解决！谢谢V大！爱你❤

repo: vernesong/OpenClash


text:
Add methods for testing of nested JsonObject/JsonArray structures.

The existing methods use flat object/array instances.  These add nested structures so the language bindings can be verified over a full object graph.

good job, I will have a look at it + impl the remaining tests in the next couple of days

can you make sure you sign your commits and comply to the CLA ? https://github.com/eclipse/vert.x/blob/master/CONTRIBUTING.md

authors: sfitts vietj


text:
Remove https tls certs from v2 image

https certs have been removed from the image and can now be generated by the vertica bootstrap catalog. This means we do not need the operator to generate the certs in vclusterops mode and can then skip install/uninstall for vclusterops.
A new option has been added to createdb to trigger https certs generation by vertica bootstrap catalog

Needs the latest vclusterops.

Thanks Matt. Do you know how I can get myself a V2 image built with the latest dockerfile?

repo: vertica/vertica-kubernetes


text:
Try fixing YAML syntax

Trying again to fix broken YAML syntax and make deploy work.

@jonmv This should hopefully work. Please review and merge.


text:
Make it possible for rank features to request which match data that s..

…hould be available in a TermFieldMatchData instance.
@baldersheim and @toregge please review
@havardpe FYI

@baldersheim ping

repo: vespa-engine/vespa


text:
Add how much is my xVADAER worth to Staking

Display how much is my xVADAER worth in similar way as in claimable now etc.

Added in 477ebb62ee3f1f26891d9e88071371c0abe7e6b8 as aggregated balance indicator.

repo: vetherasset/vader-dapp


text:
[Security] Disable HAProxy statistics page if username/password is not explicitly set in the configuration

Currently, If STATS_USER and STATS_PASS are not set,  then, the HaProxy stats page username and password are defaulted to Admin and Admin.
see https://github.com/vfarcic/docker-flow-proxy/blob/master/proxy/ha_proxy.go#L201
This is a vulnerability because administrators can easily forget to overwrite these variables.
I recommend not to set them at all and disable stats page by default.

Starting from the release 1.277, if the environment variablesSTATS_USER and STATS_PASS or Docker secrets dfp_stats_user and dfp_stats_pass are not set, statistics will not be available.

@vfarcic Is there a regression on this?, I'm testing with version 1.317 and it's not being honored.

@je-al I made a mistake by not merging the correct code so both the implementation and the code were missed. That was a big mistake from my part. The latest release should fix that. Can you please pull the latest release, try it out, and let me know if it works as expected?

@vfarcic yup, 1.326 seems fine.

authors: je-al rommik vfarcic

repo: vfarcic/docker-flow-proxy


text:
Неверный тип возвращаемого значения getAlgorithm

Дублирую для пул реквеста, а то потерялся.

Залито

authors: Akridian vgoma

repo: vgoma/crypto-pro


text:
Add awesome list badge

https://github.com/sindresorhus/awesome/issues/253

:+1:

authors: CraigyDavi onebree

repo: vhf/free-programming-books


text:
🛑 SC storefront productend is down

In 2ff7ff9, SC storefront productend (https://shop.line.me/@024azltq/product/319384970) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SC storefront productend is back up in 2ce4210.

repo: vichaos/upptime


text:
🛑 Twitter is down

In d6810f4, Twitter (https://twitter.com) was down:

HTTP code: 503
Response time: 9105 ms

Resolved: Twitter is back up in 7b0de7e after 17 minutes.


text:
Dependency issue with bare installation

When installing on react native app , I got dependency issue. Please refer below image

Reset the expo shell

Issue in react native cli mode app not expo app, I am getting expo-file-system not found error in react-native cli app

It happens to me too.
I'm not gonna use expo and it has supported for bare project until 1.2.0, but after 1.3.0 the expo-file-system dependency was added, it forces me to change or rebuild my bare project into expo-based project.
It seems that the code was added on #107 to fix #57 to serve jszip & epubjs locally.
I think the code for serving jszip & epubjs should use FileSystem on @epubjs-react-native/file-system or @epubjs-react-native/expo-file-system, not expo-file-system directly.

Hi guys, I'm already working on a solution for this and it should be out in the next few days! Sorry for the delay


text:
Flv video support

Describe:
I saw in the Discord group that flv videos are not supported since they're old video formats. In the off chance, would it be possible to get support for it? If the benefits aren't worth the addition / support for flv, no worries and feel free to close out. We're currently trying with flv.js as a wrapper for Vidstack, but might not be as compatible as we expected.
There's a discussion post from a few months back here: https://github.com/vidstack/player/discussions/857
Thanks.

Thank raising this but unfortunately out of scope for us right now. We can consider revisiting it in the future.

repo: vidstack/player


text:
This driver

Is disaster and piece of crap. Help this world and delete this repository. Thanks.

works for me bro

authors: kacirekj tobiasmuehl

repo: vietj/reactive-pg-client


text:
Viewport Widgets

Hi, Thanks so much for the Trackomatic script.
I installed the Google Analytics Dashboard for Front-End Developers and implemented the Trackomatic script (v1.1.1)  but my viewport widgets are not showing any data. Could you please let me know the widget settings for the Viewport Resize and Viewport Size widget.
Thanks,
Mitch

Hey Mitch!
The Viewport Resize widget is looking for GA events equal to "FED Viewport Resize", and the Viewport Size Widget looks for event category containing "FED Viewport Size".
If these aren't working for you, the first thing to check is your general GA event reporting to make sure events are showing up there.

Thanks for you reply. Will try this out.

authors: awavering mitchrynart

repo: vigetlabs/trackomatic


text:
Update cats-core, cats-free to 2.7.0

Updates

org.typelevel:cats-core
org.typelevel:cats-free

from 2.6.1 to 2.7.0.
GitHub Release Notes - Changelog - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

labels: library-update, early-semver-minor, semver-spec-minor

Codecov Report

Merging #278 (73f4a32) into master (52cb181) will increase coverage by 3.54%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #278      +/-   ##
==========================================
+ Coverage   66.66%   70.20%   +3.54%
==========================================
  Files          19       18       -1
  Lines         561      527      -34
  Branches       22       21       -1
==========================================
- Hits          374      370       -4
+ Misses        187      157      -30

Impacted Files
Coverage Δ

.../src/main/scala/io/github/vigoo/clipp/Parser.scala
93.80% <0.00%> (-0.11%)
:arrow_down:

.../io/github/vigoo/clipp/usageinfo/debug/debug.scala
0.00% <0.00%> (ø)

...io/github/vigoo/clipp/VersionSpecificParsers.scala

...hub/vigoo/clipp/usageinfo/UsagePrettyPrinter.scala
39.13% <0.00%> (+0.42%)
:arrow_up:

.../scala/io/github/vigoo/clipp/usageinfo/graph.scala
100.00% <0.00%> (+9.52%)
:arrow_up:

.../src/main/scala/io/github/vigoo/clipp/errors.scala
80.00% <0.00%> (+41.53%)
:arrow_up:

...e/src/main/scala/io/github/vigoo/clipp/clipp.scala
100.00% <0.00%> (+75.00%)
:arrow_up:

Continue to review full report at Codecov.

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

authors: codecov-commenter scala-steward

repo: vigoo/clipp


text:
Update cats-effect to 3.2.8

Updates org.typelevel:cats-effect from 3.2.7 to 3.2.8.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel", artifactId = "cats-effect" } ]

labels: library-update, semver-patch

Codecov Report

Merging #182 (f419aec) into master (f37a22b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #182   +/-   ##
=======================================
  Coverage   87.30%   87.30%
=======================================
  Files          28       28
  Lines         843      843
  Branches       39       39
=======================================
  Hits          736      736
  Misses        107      107

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 f37a22b...f419aec. Read the comment docs.

repo: vigoo/desert


text:
Update aws-core, http-client-spi, ... to 2.17.47

Updates

software.amazon.awssdk:aws-core
software.amazon.awssdk:http-client-spi
software.amazon.awssdk:netty-nio-client

from 2.17.42 to 2.17.47.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

labels: library-update, semver-patch

Superseded by #543.

repo: vigoo/zio-aws


text:
GradioUI  please

Please make Gradio UI web-app for easy testing
Include maximum parameters if possible

Thanks for your attention. Please refer to this link.

@ptits
It's available now.

authors: nitinmukesh ptits viiika

repo: viiika/Meissonic


text:
Added merge sorted linked lists program

Hi. I have added the "merged two sorted linked lists" program. Please add a hacktoberfest-accepted label on this.

do give Star to this repo


text:
Testing Environment

Hi,
I have some problems when testing the project. I have checked the accuracy of models, all of them achieve 99%. However, during real testing model fails to correctly recognize my gestures. Could you please make a short video showing your testing environment and show how one should move hands to properly recognize gestures?
Thanks.

Whole data set was created using only my gestures, so models are probably overfitted to me, and it does work just fine in real testing. You can always record your own gestures and retrain models with them.
Here is my footage: https://drive.google.com/file/d/1jLj6-0hzaesZALlGzwi1y7zK2rP7z5Pg/view?usp=sharing
(I've used wide lens in order to be able to record with my left hand and do the gestures with the right one, so the gestures may look bigger then what they are. You can follow the plotter for some reference tho)

Thank you so much for the video. Our setup was completely different, that's why the model was not able to recognize gestures. I would suggest you put a video(or GIF) like above in README.md so that people can easily understand.

I have one more question about radar setup. In the video above I have noticed that jumpers P5, P7 were closed and something Red&Yellow placed around SOP jumpers. Does this setting effect the received signals? Could you please take picture of the radar and show it? Thank you.

I'm just really bad at saving my jumpers, so I'm always keeping them like this :)

authors: kanybekasanbekov vilari-mickopf


text:
airline-tabline causes highlight-related issues in neovim

environment

vim: neovim 0.1.7
vim-airline: latest/v0.8
OS: OS X El Capitan 10.11.6
Have you reproduced with a minimal vimrc: yes
terminal: iTerm2 3.0.14
$TERM variable: xterm-256color
color configuration (:set t_Co?): 256
if you are using Neovim:
does it happen in Vim: No

actual behavior
When I have the airline-tabline extension enabled, I get a lot of errors when doing things with windows and buffers, such as the following:
Error detected while processing function airline#check_mode[45]..airline#highlighter#highlight[40]..<SNR>49_exec_separator[13]..airline#highlighter#exec:
line   20:
E411: highlight group not found: airline_tabfill_to_airline_tabfill_inactive
Error detected while processing function airline#check_mode[45]..airline#highlighter#highlight[40]..<SNR>49_exec_separator[13]..airline#highlighter#exec:
line   20:
E411: highlight group not found: airline_tabsel_to_airline_tabfill_inactive
Error detected while processing function airline#check_mode[45]..airline#highlighter#highlight[40]..<SNR>49_exec_separator[13]..airline#highlighter#exec:
line   20:
E411: highlight group not found: airline_tabfill_to_airline_tabtype_inactive

The above errors were a result of simply :vsp. My minimal vimrc is below:
call plug#begin('~/.config/nvim/plugged')
Plug 'vim-airline/vim-airline'
call plug#end()
let g:airline#extensions#tabline#enabled = 1

@chrisbra This bug seems to have been introduced by #1408, but I'm not enough of a vim guru to efficiently grep through and figure out what it was. When I revert to any recent commit before 69b132a it's fine. I can disable the tabline extension for now, but I'd love to help with fixing it for any other neovim users.
expected behavior
No errors.

Correction
On vim 8.0.344 I'm also running into this issue. I'm not sure what my vim version was on the previous computer I ran this on, but otherwise the environment I'm testing it on right now appears identical.
Also, not that it's a huge help, but the issue appears to stem from the CheckDefined function in highlighter.vim. I don't have a great grasp on what's going on there though :\

Can confirm I'm seeing this as well in NeoVim. Disabling the tabline optional configuration prevents the error from happening. For now I've manually checked out a previous version of vim-airline to get around the bug. I did this in NeoVim by navigating to ~/.local/share/nvim/plugged/vim-airline and running git checkout v0.8 which seems like a relatively recent stable version.

I don't see that. What is your tabline configuration or what did you do to make the error happen? I am sorry but I don't see that error.
Also this is probably a duplicate of #1414

BTW: can you check this patch:
diff --git a/autoload/airline/highlighter.vim b/autoload/airline/highlighter.vim
index e4e83e8..9dc8472 100644
--- a/autoload/airline/highlighter.vim
+++ b/autoload/airline/highlighter.vim
@@ -72,7 +72,9 @@ function! airline#highlighter#exec(group, colors)
   if len(colors) == 4
     call add(colors, '')
   endif
-  let colors = s:CheckDefined(colors)
+  if a:group =~ 'tabfill_inactive'
+    let colors = s:CheckDefined(colors)
+  endif
   if old_hi != colors || !hlexists(a:group)
     let cmd = printf('hi %s %s %s %s %s %s %s %s',
         \ a:group, s:Get(colors, 0, 'guifg=', ''), s:Get(colors, 1, 'guibg=', ''),

Then do :breakadd func *CheckDefined and then step through the function until the error happens. Please show the line where the error occurs. According to your stacktrace, it seems to be this line
So then show :echo cmd

You're right, sorry; the actual error isn't coming from CheckDefined, it's obviously coming from the hi command but with a highlight theme it doesn't recognize, and I'm not sure if it's generating that highlighting theme (airline_tabfill_to_airline_tabfill_inactive) erroneously or why that theme may be missing. After applying that patch I run into the same errors, and echoing cmd while debugging gives me
>echo cmd
hi airline_tabfill_to_airline_tabfill_inactive

I only have the following airline highlighting themes, however:
airline_x_inactive xxx ctermfg=249 ctermbg=238 guifg=#b2b2b2 guibg=#444444
airline_x_inactive_bold xxx cterm=bold ctermfg=249 ctermbg=238 gui=bold guifg=#b2b2b2 guibg=#444444
airline_x_inactive_red xxx ctermfg=160 ctermbg=238 guifg=#ff0000 guibg=#444444
airline_y_inactive xxx ctermfg=249 ctermbg=238 guifg=#b2b2b2 guibg=#444444
airline_y_inactive_bold xxx cterm=bold ctermfg=249 ctermbg=238 gui=bold guifg=#b2b2b2 guibg=#444444
airline_y_inactive_red xxx ctermfg=160 ctermbg=238 guifg=#ff0000 guibg=#444444
airline_z_inactive xxx ctermfg=249 ctermbg=238 guifg=#b2b2b2 guibg=#444444
airline_z_inactive_bold xxx cterm=bold ctermfg=249 ctermbg=238 gui=bold guifg=#b2b2b2 guibg=#444444
airline_z_inactive_red xxx ctermfg=160 ctermbg=238 guifg=#ff0000 guibg=#444444
airline_error_inactive xxx ctermfg=232 ctermbg=160 guifg=#000000 guibg=#990000
airline_error_inactive_bold xxx cterm=bold ctermfg=232 ctermbg=160 gui=bold guifg=#000000 guibg=#990000
airline_error_inactive_red xxx ctermfg=160 ctermbg=160 guifg=#ff0000 guibg=#990000
airline_a_inactive xxx ctermfg=249 ctermbg=238 guifg=#b2b2b2 guibg=#444444
airline_a_inactive_bold xxx cterm=bold ctermfg=249 ctermbg=238 gui=bold guifg=#b2b2b2 guibg=#444444
airline_a_inactive_red xxx ctermfg=160 ctermbg=238 guifg=#ff0000 guibg=#444444
airline_b_inactive xxx ctermfg=249 ctermbg=238 guifg=#b2b2b2 guibg=#444444
airline_b_inactive_bold xxx cterm=bold ctermfg=249 ctermbg=238 gui=bold guifg=#b2b2b2 guibg=#444444
airline_b_inactive_red xxx ctermfg=160 ctermbg=238 guifg=#ff0000 guibg=#444444
airline_c_inactive xxx ctermfg=249 ctermbg=238 guifg=#b2b2b2 guibg=#444444
airline_c_inactive_bold xxx cterm=bold ctermfg=249 ctermbg=238 gui=bold guifg=#b2b2b2 guibg=#444444
airline_c_inactive_red xxx ctermfg=160 ctermbg=238 guifg=#ff0000 guibg=#444444
airline_warning_inactive xxx ctermfg=232 ctermbg=166 guifg=#000000 guibg=#df5f00
airline_warning_inactive_bold xxx cterm=bold ctermfg=232 ctermbg=166 gui=bold guifg=#000000 guibg=#df5f00
airline_warning_inactive_red xxx ctermfg=160 ctermbg=166 guifg=#ff0000 guibg=#df5f00
airline_x      xxx ctermfg=150 ctermbg=238 guifg=#afd787 guibg=#444444
airline_x_bold xxx cterm=bold ctermfg=150 ctermbg=238 gui=bold guifg=#afd787 guibg=#444444
airline_x_red  xxx ctermfg=160 ctermbg=238 guifg=#ff0000 guibg=#444444
airline_y      xxx ctermfg=249 ctermbg=237 guifg=#b2b2b2 guibg=#3a3a3a
airline_y_bold xxx cterm=bold ctermfg=249 ctermbg=237 gui=bold guifg=#b2b2b2 guibg=#3a3a3a
airline_y_red  xxx ctermfg=160 ctermbg=237 guifg=#ff0000 guibg=#3a3a3a
airline_z      xxx ctermfg=236 ctermbg=150 guifg=#303030 guibg=#afd787
airline_z_bold xxx cterm=bold ctermfg=236 ctermbg=150 gui=bold guifg=#303030 guibg=#afd787
airline_z_red  xxx ctermfg=160 ctermbg=150 guifg=#ff0000 guibg=#afd787
airline_error  xxx ctermfg=232 ctermbg=160 guifg=#000000 guibg=#990000
airline_error_bold xxx cterm=bold ctermfg=232 ctermbg=160 gui=bold guifg=#000000 guibg=#990000
airline_error_red xxx ctermfg=160 ctermbg=160 guifg=#ff0000 guibg=#990000
airline_a      xxx ctermfg=236 ctermbg=150 guifg=#303030 guibg=#afd787
airline_a_bold xxx cterm=bold ctermfg=236 ctermbg=150 gui=bold guifg=#303030 guibg=#afd787
airline_a_red  xxx ctermfg=160 ctermbg=150 guifg=#ff0000 guibg=#afd787
airline_b      xxx ctermfg=249 ctermbg=237 guifg=#b2b2b2 guibg=#3a3a3a
airline_b_bold xxx cterm=bold ctermfg=249 ctermbg=237 gui=bold guifg=#b2b2b2 guibg=#3a3a3a
airline_b_red  xxx ctermfg=160 ctermbg=237 guifg=#ff0000 guibg=#3a3a3a
airline_c      xxx ctermfg=150 ctermbg=238 guifg=#afd787 guibg=#444444
airline_c_bold xxx cterm=bold ctermfg=150 ctermbg=238 gui=bold guifg=#afd787 guibg=#444444
airline_c_red  xxx ctermfg=160 ctermbg=238 guifg=#ff0000 guibg=#444444
airline_warning xxx ctermfg=232 ctermbg=166 guifg=#000000 guibg=#df5f00
airline_warning_bold xxx cterm=bold ctermfg=232 ctermbg=166 gui=bold guifg=#000000 guibg=#df5f00
airline_warning_red xxx ctermfg=160 ctermbg=166 guifg=#ff0000 guibg=#df5f00
airline_tab    xxx ctermfg=249 ctermbg=237 guifg=#b2b2b2 guibg=#3a3a3a
airline_tabsel xxx ctermfg=236 ctermbg=150 guifg=#303030 guibg=#afd787
airline_tabtype xxx ctermfg=236 ctermbg=182 guifg=#303030 guibg=#d7afd7
airline_tabfill xxx ctermfg=150 ctermbg=238 guifg=#afd787 guibg=#444444
airline_tabmod xxx ctermfg=238 ctermbg=110 guifg=#444444 guibg=#87afd7
airline_tabmod_unsel xxx ctermfg=179 ctermbg=238 guifg=#d7af5f guibg=#444444
airline_tabhid xxx ctermfg=150 ctermbg=238 guifg=#afd787 guibg=#444444
airline_tab_right xxx ctermfg=249 ctermbg=238 guifg=#b2b2b2 guibg=#444444
airline_tabsel_right xxx ctermfg=236 ctermbg=150 guifg=#303030 guibg=#afd787
airline_tabmod_right xxx ctermfg=238 ctermbg=110 guifg=#444444 guibg=#87afd7
airline_tabhid_right xxx ctermfg=150 ctermbg=238 guifg=#afd787 guibg=#444444
airline_tabmod_unsel_right xxx ctermfg=179 ctermbg=238 guifg=#d7af5f guibg=#444444
airline_a_to_airline_b xxx ctermfg=150 ctermbg=237
airline_b_to_airline_c xxx ctermfg=237 ctermbg=238
airline_c_to_airline_x xxx ctermfg=238 ctermbg=238
airline_x_to_airline_y xxx ctermfg=237 ctermbg=238
airline_y_to_airline_z xxx ctermfg=150 ctermbg=237
airline_z_to_airline_warning xxx ctermfg=166 ctermbg=150
airline_warning_to_airline_error xxx ctermfg=160 ctermbg=166
airline_c1_inactive xxx ctermfg=249 ctermbg=238 guifg=#b2b2b2 guibg=#444444
airline_tabsel_to_airline_tabfill xxx ctermfg=150 ctermbg=238
airline_tabfill_to_airline_tabfill xxx ctermfg=238 ctermbg=238
airline_tabfill_to_airline_tabtype xxx ctermfg=182 ctermbg=238

Just found a strange quirk with vim. Specifying the vimrc file (even if I specify the default one) yields different results. With the 4 line .vimrc I listed above, I run into errors when running vim then :vsp. However, when I run vim -u ~/.vimrc then :vsp, no errors appear but the airline theme doesn't seem to be loaded properly (it's just all white) and I'm not sure what else is being done. Just in case you've been trying it with the -u flag so far. Again, the only airline/tabline configuration i have is in the vimrc I posted above:
call plug#begin('~/.config/nvim/plugged')
Plug 'vim-airline/vim-airline'
call plug#end()
let g:airline#extensions#tabline#enabled = 1

And calling anything that creates new panes/windows triggers the error.

ah okay. You are seeing an error because :hi name returns the attributes for the given name. However, we are missing attributes, because the hi call should create that attribute. Please step into the CheckDefined function again and show :echo a:colors at the start and after CheckDefined finish :echo colors

A quickfix patch, that prevents the error should be this:
index e4e83e8..670f2f3 100644
--- a/autoload/airline/highlighter.vim
+++ b/autoload/airline/highlighter.vim
@@ -79,7 +79,9 @@ function! airline#highlighter#exec(group, colors)
         \ s:Get(colors, 2, 'ctermfg=', ''), s:Get(colors, 3, 'ctermbg=', ''),
         \ s:Get(colors, 4, 'gui=', ''), s:Get(colors, 4, 'cterm=', ''),
         \ s:Get(colors, 4, 'term=', ''))
-    exe cmd
+    if split(cmd) > 2
+      exe cmd
+    endif
   endif

@chrisbra I guess it should be if len(split(cmd)) > 2 (your patch doesn't have the len). That fixed my errors - thanks!

correct. However I would rather like to fix the real issue rather than to have this workaround.

@chrisbra here you go, a:colors in CheckDefined and after it returns
>echo a:colors
['', '', 'NONE', 'NONE', '']

... outside the function ...

>echo colors
['', '', '', '', '']

and what is the output of :hi Normal?

:hi Normal
Normal         xxx cleared

oh shoot, that is bad.

okay, will fix it soon.

environment

vim: 8.0.381
vim-airline: latest git pull & initialized via pathogen
OS: Ubuntu 16.04LTS
Have you reproduced with a minimal vimrc: yes
What is your airline configuration:

let g:airline_powerline_fonts = 1
let g:airline_theme='solarized'
let g:airline#extensions#tabline#enabled = 1

if you are using terminal:

terminal: GNOME Terminal 3.18.3
$TERM variable: xterm-256color
color configuration (:set t_Co?): 256
if you are using Neovim:
does it happen in Vim: N/A

actual behavior
When using VIM on the terminal, I get the same errors reported earlier:
Messages maintainer: Bram Moolenaar <Bram@vim.org>
Error detected while processing function airline#check_mode[45]..airline#highlighter#highlight[40]..<SNR>62_exec_separator[13]..airline#highlighter#exec:
line   20:
E411: highlight group not found: airline_tabfill_to_airline_tabfill_inactive
Error detected while processing function airline#check_mode[45]..airline#highlighter#highlight[40]..<SNR>62_exec_separator[13]..airline#highlighter#exec:
line   20:
E411: highlight group not found: airline_tabsel_to_airline_tabfill_inactive
Error detected while processing function airline#check_mode[45]..airline#highlighter#highlight[40]..<SNR>62_exec_separator[13]..airline#highlighter#exec:
line   20:
E411: highlight group not found: airline_tab_to_airline_tabfill_inactive
Error detected while processing function airline#check_mode[45]..airline#highlighter#highlight[40]..<SNR>62_exec_separator[13]..airline#highlighter#exec:
line   20:
E411: highlight group not found: airline_tabfill_to_airline_tabtype_inactive

I am able to reproduce these in at least two ways:

Toggling NERDTree via :NERDTreeToggle
Accessing vim-airline help via :help airline

If I remove let g:airline#extensions#tabline#enabled = 1  from my vimrc, the errors no longer occur. Also, the errors DO NOT occur if I am using gvim (also v8.0.381). This problem, as others have noted, is recent and did not occur prior to a recent commit. Unfortunately however, I am not able to identify when it began.
expected behavior
Normal access to NERDTree and help menus without highlighting errors.

I apologise for repeating this in multiple threads (#1420).
This problem just started occurring for me, and I can't for the life of me figure out what changed.
Ensuring the 'Normal' highlight group exists fixed the problem, as did rolling vim-airline and vim-airline-theme back about 5 commit..  not very scientific.

VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Feb 21 2017 07:08:52)
Included patches: 1-342

but rolling back to an earlier vim-8 build made no difference.
function! Local_AirlineThemePatcher(palette)
    " Trick to ensure 'Normal' highlight group exists
    if !hlexists('Normal')
        highlight Normal ctermbg=0
    endif
endfunction

let g:airline_theme_patch_func = 'Local_AirlineThemePatcher'

Awesome, that solved it. Thanks a ton for your help @chrisbra!

@systemmonkey42's fix does not work for me.
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Feb 18 2016 16:04:02)
MacOS X (unix) version
Included patches: 1-1265
Compiled by Homebrew
Huge version with MacVim GUI.

Error detected while processing function airline#check_mode[45]..airline#highlighter#highlight[16]..airline#highlighter#exec:
line   20:
E421: Color name or number not recognized: ctermbg=-1

:hi Normal
Normal         xxx ctermfg=248

+1 - Fix doesn't work for me either.
Error detected while processing function airline#check_mode[45]..airline#highlighter#highlight[40]..<SNR>132_exec_separ
ator[13]..airline#highlighter#exec:
line   20:
E421: Color name or number not recognized: ctermfg=-1 ctermbg=NONE

please update. That problem has been fixed

cloned latest airline and ctrlp (within the hour) and issue still remains.
only occurs when accessing ctrlp.

Since this issue is very annoying, I was able to work around it as follows:

Clone the repository to some directory (e.g. /tmp/vim-airline)
Checking out the older commit b66c1ef07005fad6a70957b90d4f47bb932e33e2 (subsequent commits have this issue).
Copy the files/dirs from /tmp/vim-airline into ~/.vim

As previously mentioned, this is not a solution. It is just a temporary work-around until the actual issue gets resolved.

@mefathy,
Are you keeping vim-airline and vim-airline-themes in sync?  The changes in each seem to be complementary and neither seems to work cleanly on its own.

@systemmonkey42,
Thanks for pointing this out. I used to keep them in sync but I did not face any issues (so far) when I reverted vim-airline only to b66c1ef.

Guys, if you still see this error message, please help debug. Add this patch but use a group name of ctrlp, then according to that comment break into that function and show the output of the colors before and after the CheckDefined function and also show :hi <ctrlp_highlighting_group> or whatever it was called.

I'll get onto it, but an interesting sidenote; I'm using fzf, triggerd by noremap <C-p> :FZF!<CR>
May be nothing, perhaps they are sharing code, but it it may also help figure this out.

Apologies, but I do not have the time currently. Here is what I can give you:
:hi Normal
Normal         xxx cleared

A fix that worked:
autocmd VimEnter,Colorscheme * :hi Normal ctermbg=0
autocmd VimEnter,Colorscheme * :hi Normal ctermfg=255

Let me know if this does not lead you anywhere useful, and I will try to help you when I get home this evening.

5266354 should have solved the problem that Normal was cleared. I don't know why you would still see that error. For what highlighting group are you seeing this error?

authors: RobbieClarken brydoncheyney chrisbra jsmalkowski mefathy rwwishart sharpshark28 systemmonkey42 vitosans wjagodfrey

repo: vim-airline/vim-airline


text:
ログが最後に取得された日時を表示する

当日分のログは見ることができないので、そのことがわかるように。
また、何かしらのエラーでログが更新できていない場合等にも役に立つ。

ついでですけど、slacklog-generator へのリンクもあるといいかもしれませんね。

authors: msmhrt thinca

repo: vim-jp/slacklog-generator


text:
E475 error 29_Highlight_Matching_Pair when opening *.html files

I get an E475 error when opening any html file containing <!DOCTYPE html> as a first line. The bug must have been introduced somewhere between 8.1.0095 (no error) and 8.1.0152 (error).
I'm running vim using Windows 10 by replacing the gvim.exe in the installation folder with a self-compiled executable.

Has actually already been fixed by commit b7a5ab112ab2267c54acdb6a326642afcd797bc4
Note to self: update the content of ./plugin every once and a while…

repo: vim/vim

license: Vim


text:
long wrapped line at bottom won't visually unselect

Describe the bug
Visually selecting from the bottom up, while wordwrap is on, and then unselecting still leaves  the appearance of selected text if the last displayed line extends beyond the length of the window.
To Reproduce

Load this file long.txt
:set wrap
:set display+=lastline
:set lines=25
:set columns=69
Scroll to bottom, move cursor to last character. Using v, enter visual mode and select from the bottom of the file to the top. Scroll to top, select to first character. Last line should extend beyond the length of the screen.
Unselect using <Esc>
Observe artifact (Done)
<C-L> to clear

Expected behavior
Appearance of selection should not be there
Screenshots

Environment (please complete the following information):
Confirmed on multiple:
VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Feb 22 2019 19:03:04)
Included patches: 1-503, 505-680, 682-1283
MacVim Custom Version 8.1.950 (155)
NVIM v0.3.4

MacOS 10.14.5
MacOS Terminal Version 2.9.5 (421.2)

Some pieces are missing.  At least need to set 'display' to "lastline".
Please start with "vim --clean".
Also mention how you move to the position where you start Visual mode (for me it makes the whole line appear).

Updated based on input.

Thanks for the update, now I reproduce the problem.

authors: brammool kevinlawler


text:
Setting termguicolors in Vim causes Windows Terminal to become opaque

Describe the bug
I use Vim in Windows Terminal. If termguicolors is set the acrylic transparency of WT stops working.
To Reproduce
Detailed steps to reproduce the behavior:

Open the new Windows Terminal and set acrylic transparency on
Run vim --clean
Run the command :set termguicolors

Expected behavior
The WT background's opacity shouldn't be altered.
Screenshots

Environment

Vim: 8.2.1818
OS: Windows 10
Terminal: Windows Terminal 1.3.2651.0

is this windows terminal specific? Do you set the Normal highlighting group?

Yes, it is Windows Terminal specific. I have tried cmd.exe and it works.
I have it set on my vimrc and the issue persists. I only said to try vim --clean to make sure the problem is not on my vimrc

Don't you need to remove the background color for the Normal highlighting group, if you want a transparent terminal? So does that change anything?

Could you please list all commands you want me to try?
Things about this issue:

it only happens in vim, not nvim;
one person told me it didn't happen in older versions
only happens in Windows Terminal (not in cmd.exe, alacritty.exe)

EDIT: If you mean hi Normal ctermbg=NONE command, I just tried it and the issue persists

If you are using termguicolors you also need to reset the guibg attribute.

I know I forgot to write it. The issue persists.

I think this is a duplicate of #2361 so closing.

@chrisbra yes they are rather similar.
Alas it doesn't tell how to solve the bug, the author just then said it was working fine in his system.
I tried all steps and it still doesn't work properly on my system so I think perhaps the issue shouldn't be closed.

I don't think this is a duplicate of #2361. That issue is specifically about the :terminal buffer, where vim with set termguicolors cannot clear the :terminal background. It affects vim on all operating systems, I experience it in linux, where any other window displays transparent backgrounds.
This issue is specific to the Windows OS, and affects ordinary buffers. I think it also affects cmd.exe, not just Windows Terminal. Here's a cmd.exe example:
"C:\Program Files\Vim\vim82\vim.exe" --clean -c "set tgc" -c "hi Normal guibg=white" -c "hi Normal guibg=NONE"

This opens vim to look like this:

Note that in the above example, the Normal highlight group has its guibg set to white, then reset to NONE. The background of most of the window remains white, except the text and the first line of the buffer.

Actually in my system it doesn't affect cmd.exe with transparency, it only seems to effect Windows Terminal

I bisected and discovered that the opaquely filled background came from v8.1.2382 (commit a050b9471c66b383ed674bfd57ac78016199d972).
However, the behavior before that was not that good thing. Next image is the result of vim.exe --clean "+set tgc" at v8.1.2381, but you can see some part of its background is still blacked.
v8.1.2381

But if I went back to v8.1.0337, such black background disappeared. Thus I think the first problem was introduced at v8.1.0338 (commit f6ceaf1e058c64775fd46cbdb8962f5c19ef83e0).
v8.1.0337

Oh nicely done! Hopefully there will be a way to fix it in the next releases!

If anyone want's a workaround, i created a shader to turn any wanted color transparent.
https://github.com/Hammster/windows-terminal-shaders#Transparent

Try the command autocmd vimenter * ++nested highlight normal ctermbg=none guibg=none and move it after your colorscheme declaration

authors: Bakudankun Chaoticsys101 Hammster chrisbra dapovich nickspoons