text:
reformat some class and var name, update class require path

Description
code reformat, add demo cli code
Type of change

class name
var name
file require path

Brief of your solution
solve some path err for test codes.
How Has This Been Tested?
update and run demo.php for test

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant vsfor

repo: xuperchain/xasset-sdk-php


text:
访问出错

我在服务器上启动了容器：
docker run -it -d --gpus all --ipc=host --net=bridge -p 6006:6006 --name=baichuan-13b-chat     --ulimit memlock=-1 --ulimit stack=67108864   -v pwd:/workspace  -v /data/models:/workspace/models     llm-api:pytorch
在容器里面运行：
python3 api/app.py     --port 6006     --allow-credentials     --model_name baichuan-13b-chat     --model_path ../models/Baichuan-13B-Chat     --device cuda     --embedding_name ../models/text2vec-large-chinese --gpus 2,3,4,5
在本地访问服务器：
ssh -L 7860:127.0.0.1:7860 root@10.8.113.77
ssh -L 7860:0.0.0.0:6006 root@172.16.0.8
然后浏览器输入IP：
http://127.0.0.1:7860/
报错：

知道什么原因吗？

你好，您可以试试使用 ip 地址访问，例如 http://192.168.0.53:7890/docs，查看所有接口

thank you

source: gharchive/issue

repo: xusenlinzy/api-for-open-llm

license_type: permissive

license_source: github-api


text:
we can't read data bigger than

com.xuhao.android.libsocket.impl.exceptions.ReadException: we can't read data bigger than 10Mb
这个是什么错误啊？我的数据不超过3KB

你的Socket服务器应该返回数据格式按照 [包头][包体]的格式,包头中默认的Header处理是直接解析包头数据为后面的包体长度,你可以重写包头解析方法,来适应你的服务器返回,从中返回正确的包体长度,如上图这个方法,是设置自定义包头解析类的

我已经更新了文档,你可以看下

每一个包是 \n 来分包的，这个怎么解析？

还有一个问题：我重写了那个接口，但是不知道当前的接受的数据，怎么知道一个包Body长度呢？

有时间帮我解决一下，谢谢：QQ 253933559

我也是遇到这个问题，   怎么自定义包头和包体 ？

目前为止好像不支持自定义分包

QQ  58461882  ， 求大佬支援

或者说这个   服务器 发送的 格式是什么

例如服务端要给你发送一个英文字母 a
那么服务端应该这样发送 byte 数组
00 00 00 01 61
解释如下:
a 的 Ascll 码对应的是97 97的16进制是0x61
a 的数据长度是1
所以包头要标识后面的包体长度是1
所以包头就是1
因为包头是 int 型,一个 int 型战4个字节
所以,就是00 00 00 01
要发送的数据长度 + 发送的数据
所以就是 00 00 00 01 61

authors: Sabirjan baizekeji xuuhaoo

repo: xuuhaoo/OkSocket

license: mit

license_source: bigquery


text:
Add a ElementHandle helper

We should add an helper class to query element on the page and perform operations directly on them.
var element = tab.querySelector("input");
element.click();

As of now the alternative is to do it with evaluate:
tab.evaluate("document.querySelector('input').click()");

Or go low level with:
Node document = await tab.dom.getDocument();
NodeId elementId = await tab.dom.querySelector(document.nodeId, 'input');
RemoteObject element = await tab.dom.resolveNode(nodeId: elementId);
await tab.runtime.callFunctionOn('click', objectId: element.objectId);

Fixed with #29

repo: xvrh/puppeteer-dart


text:
02 生成语法树

采用了 jQuery 作者 John Resig 的 HTML Parser ，（VUE也是用了这个），然后生成语法树，非常少的代码，语法树的结构参考了VUE的，目前只用了几个字段，不够后面再加。
生成语法树就是生成一颗树，比较麻烦的是父节点的处理，这里用一个栈来存放（就是一个数组，采用push和pop方法），代码非常简单，自己写的话10行左右就生成了语法树。
type1 表示dom节点，2表示表达式（未实现）3表示文本/注释，
/* @flow */
import { log } from '../util'
import { HTMLParser, HTMLtoXML, HTMLtoDOM } from './htmlparser'

//D:\OutPut\VUE\vue\src\compiler\parser\index.js
function html2ast(templte: string, data: Object): ?ASTElement {
    let root: ?ASTElement;
    let parent: ASTElement;
    let parentStack = [];

    HTMLParser(templte, {
        start: function (tag, attrs, unary) {
            //
            if (false === unary && parent) {
                parentStack.push(parent);
            }

            let e = createASTElement(tag, attrs, parent);

            if (!root) {
                root = e;
            }

            if(false === unary){
                parent = e;
            }
        },
        end: function (tag) {
            parent = parentStack.pop();
        },
        chars: function (text) {
            createTextlement(text, parent);
        },
        comment: function (text) {
            createCommentlement(text, parent);
        }
    });

    log('htmlparser ast', root);
    log('htmlparser parentStack', parentStack);
    return root;
}

function createASTElement(
    tag: string,
    attrs: Array<Attr>,
    parent: ?ASTElement
): ASTElement {
    let e = {
        type: 1,
        tag,
        //attrsList: attrs,
        attrsMap: makeAttrsMap(attrs),
        //parent,
        children: []
    }

    if (parent) {
        parent.children.push(e);
    }

    return e;
}

function createTextlement(
    text: string,
    parent: ASTElement
): ASTText {
    let e = {
        type: 3,
        text,
        //parent
    }

    parent.children.push(e);

    return e;
}

function createCommentlement(
    text: string,
    parent: ASTElement
): ASTText {
    let e = {
        type: 3,
        text,
        isComment: true,
        //parent
    }

    parent.children.push(e);

    return e;
}

function makeAttrsMap(attrs: Array<Object>): Object {
    const map = {}
    for (let i = 0, l = attrs.length; i < l; i++) {
        map[attrs[i].name] = attrs[i].value
    }
    return map
}

export { html2ast }

换行和空格的处理，有什么思路吗

authors: Dec-F xwjie

repo: xwjie/VueStudyNote

license: MIT


text:
Get day and month name arrays by splitting strings

Splitting a single string into an array of strings may be smaller than writing an array literal (depending on the length of the array).
If being tiny is your goal, this will shave off a few bytes.

Codecov Report

Merging #59 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #59   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           3      3
  Lines         166    166
  Branches       26     26
=====================================
  Hits          166    166

Impacted Files
Coverage Δ

src/index.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

nice point!  I am just wondering if might reduce code readability
Lengthy lines of code vs readability

@iamkun I think the difference in readability is minor but that's just me. I think a slightly bigger issue is that these arrays are being created (in whichever way) each time format is called. They could be pulled out to a higher scope and only created once. Same goes for the regular expression in that function I guess. I mean, it depends on performance difference between creating an array and looking up to a higher scope. I don't really know which is costly or by how many picoseconds.

I agree with @okonomiyaki3000 about moving them to a higher level, it would also potentially open the door for creating a function that would let people override them with location specific versions at runtime, which could allow for localization without the needing to increase the overall size of the library.

I agree.
Moving constants to a higher scope level may help us easily support i18n / locals.

:tada: This PR is included in version 1.5.16 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

source: gharchive/pull-request


text:
🛑 🇸🇬 边缘节点-新加坡 (EdgeNode-Singapore) is down

In d61d57e, 🇸🇬 边缘节点-新加坡 (EdgeNode-Singapore) ($SECRET_SITE_SG) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 🇸🇬 边缘节点-新加坡 (EdgeNode-Singapore) is back up in 9c145e3 after 15 minutes.


text:
Android File Transfer

In Mac, Android mobile are not automatically recognized when connected through USB.
There is a need for 3-party app. Android File Transfer is one such App.
Which section does this fit Into??
utilities section?

Yeah, i think the section utilities should be perfect for this application :)

authors: munendrasn xyNNN

repo: xyNNN/awesome-mac


text:
"undefined" is rendered as Object

The undefined value is rendered as Object.
Attached shot is from demo page:

It turns out that the default props for data is {}; React will use default props when passed in undefined. Will fix in next version by changing default props to undefined.

Resolved in 0.1.5

authors: stomita xyc

repo: xyc/react-object-inspector


text:
Update scalafmt-core to 3.7.4

Updates org.scalameta:scalafmt-core from 3.7.3 to 3.7.4.
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!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scalameta", artifactId = "scalafmt-core" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #65.

repo: y-yu/slick-bulk-insert


text:
CRMEB image_base64 SSRF漏洞（CVE-2023-3233）

漏洞编号: CVE-2023-3233
危害定级: 高危
漏洞标签: POC已公开
披露日期: 2023-06-14
信息来源: https://avd.aliyun.com/detail?id=AVD-2023-3233
推送原因: 漏洞创建

漏洞描述
CRMEB 是一款开源商城系统。CVE-2023-3233 中，CRMEB <= 4.6.0 版本中存在未授权前台SSRF漏洞，攻击者可构造恶意请求发起内网扫描，获取敏感数据，
参考链接

https://github.com/HuBenLab/HuBenVulList/blob/main/CRMEB is vulnerable to Server-side request forgery (SSRF).md
https://vuldb.com/?ctiid.231504
https://vuldb.com/?id.231504

我对代码进行了修改，以增强对用户输入URL的验证和限制，从而解决了Server-Side Request Forgery (SSRF)漏洞。具体的修改如下：
我对于您提出的这个问题很感兴趣，我找到了这个文档对这个文档中程序描述的问题进行了一点调整，希望能够有所帮助

使用了PHP的filter_var函数结合FILTER_VALIDATE_URL过滤器来验证URL的合法性。只有合法的URL才会被继续处理，否则会返回false。
进一步限制了允许的URL方案，只允许http和https。这样可以用来排除一些不安全的URL方案。
引入了一个白名单的概念，将允许的域名添加到$allowed_domains数组中。只有在这个白名单中的域名才会被接受，其他域名将返回false。
如果URL的主机名不在白名单中，就返回false。这样可以确保只有受信任的域名可以继续处理。
这些修改增强了对用户输入的验证和限制，减少了潜在的SSRF攻击风险。因为问题主要出现在漏洞发生的主要原因是在image_to_base64函数中存在Server-Side Request Forgery SSRFSSRF漏洞。此外，我保留了现有代码的其余部分，以继续处理URL请求和响应的其他功能，同时确保更安全的URL处理。

具体的代码如下：
if (filter_var($avatar, FILTER_VALIDATE_URL) === false || !in_array(parse_url($avatar, PHP_URL_SCHEME), ['http', 'https'])) {
return false; // 设置允许的URL
}
// 进一步限制哪些域名是可接受的或使用白名单方法
$allowed_domains = array('example.com', 'trusteddomain.com'); // 添加可信域
$url_host = parse_url($avatar, PHP_URL_HOST);
if (!in_array($url_host, $allowed_domains)) {
return false; // URL主机不在白名单中返回false
}
// 现有代码的其余部分保持不变
// (处理cURL请求和处理响应的其余代码)


text:
Test changes

split off from #27

looks great, going to get travis working on this gem momentarily


text:
test CI

:books: Documentation preview :books:: https://jupysql--11.org.readthedocs.build/en/11/

dsa

aa

repo: yafimvo/jupysql


text:
handle comment stripping via transition table.

Comment stripping will be made configurable in the subsequent PR
@yukinying @adon-at-work @neraliu please review!
This is to address https://github.com/yahoo/html-purify/issues/10#issuecomment-126760856

+1

CLA is valid!

Without considering configurability, this method is much cleaner, and I can also see the performance improvement.
good to merge. :+1:

authors: adon-at-work maditya yahoocla yukinying

repo: yahoo/html-purify


text:
[patch] Fix authorize

Description
description_with_details_and_reasoning
Type of change

[x] Bug fix
[ ] New feature
[ ] Refactoring (no functional changes, no api changes)
[ ] Non-code changes (update documentation, pipeline, etc.)

Flags

[ ] breaks backward compatibility
[ ] requires a documentation update
[ ] has untestable code

Related issue/PR
Delete if not applicable

Fixes #issue
Closes #PR

Checklist

[ ] Followed the guidelines in the CONTRIBUTING document
[ ] Added prefix [major]/[minor]/[patch]/[skip] in the PR title
[ ] Tested and linted the code
[ ] Commented the code
[ ] Made corresponding changes to the documentation
[ ] Confirmed no dropping in test coverage (by Codecov)
[ ] Passed all pipeline checking
[ ] Approved by >1 reviewer

Checklist for maintainer

[ ] Use Squash and merge
[ ] Double-confirm the merge message has prefix [major]/[minor]/[patch]/[skip]
[ ] Delete the branch after merge

Codecov Report

Merging #74 into master will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #74      +/-   ##
==========================================
+ Coverage   94.66%   94.69%   +0.02%
==========================================
  Files          19       19
  Lines        1257     1263       +6
==========================================
+ Hits         1190     1196       +6
  Misses         45       45
  Partials       22       22

Impacted Files
Coverage Δ

authorizerd.go
92.30% <100.00%> (+0.19%)
: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 7c1258f...f808d78. Read the comment docs.

authors: codecov-commenter ssunorz

repo: yahoojapan/athenz-authorizer


text:
Getter and Setter for model in DataTablesEditor.php

Summary of problem or feature request
It would be very useful for the DataTablesEditor abstract class to have getter and setter for the protected model attribute. Sometimes I need to remind me to fill the protected model attribute in the extended class. But if I could set/get the model outside of the class would be very useful for a laravel controller use-case.
Code snippet of problem
abstract class DataTablesEditor
{
    public function getModel() {
        return $this->model;
    }

    public function setModel($model) {
        $this->model = $model;
    }

So I can call in the store function in a Laravel controller:
        $editor->setModel(Model::class);
        return $editor->process(request());

System details

Operating System: Windows 7
PHP Version: 7.2.14
Laravel Version: 5.7
Laravel-DataTables Version: 1.6.1

@schonhoff Sorry for late response, the idea looks good for me. Would you mind sending a PR? Thanks!

I went ahead and created the PR. Thanks for the idea!

Released on v1.8.0 🚀

authors: schonhoff yajra

repo: yajra/laravel-datatables-editor


text:
Added monochrome tray icon (and high dpi) for the OSX

Hi guys, thanks for the hard work!
I added separate tray icon to match overall OSX styling (monochromatic). As I'm not that familiar with coffeescript, please check it before merging in. There are also "original" svgs for the mono icons.

i am thinking what happens on windows / linux ?

@davibe I've added a check for OS, so Windows and Linux are still using the current icons for the tray.

right, ty

authors: Stanko davibe

repo: yakyak/yakyak


text:
又发现一个乱码的网站

http://www.ranwena.com/files/article/1/1268/5028890.html
这个网站的小说正文乱码，大大周末有空看看怎么回事呢？（编码问题好头疼，完全搞不懂原理……）

源码里明明看了很正常的文字，编码也很常规，，就是搞不懂为什么会乱码……

对了，我用之前1.0.1的版本测试是不乱码的

又发现一个乱码的，http://m.lewen8.com/lw2408/2030224.html 跟前面一个乱码的格式还不太一样

你用最新的库，调用
setEncodeBuffer(1024),我新版本默认是500，有些小，你设置成1024应该就没有问题了

谢谢啊，刚想起来问题还没关闭，现在确实没有乱码了～～

没事，今天把有些接口改了，你注意一下


text:
test(menu): added context menu test

Closes #1667
Description
Added context menu tests for enhance test coverage.
Current behavior (updates)
NIL
New behavior
NIL
Is this a breaking change (Yes/No):
No
Additional Information

Thanks!

authors: Kei-Ta hirotomoyamada

repo: yamada-ui/yamada-ui


text:
Android release got failed.

Hello There,
In React Native my android release build got failed because of below error, can you please help me out i need to upload application in play store.

What went wrong:
Execution failed for task ':react-native-orientation:verifyReleaseResources'.

com.android.ide.common.process.ProcessException: Failed to execute aapt

build.gradle ==>>
ext {
minSdkVersion = 16
compileSdkVersion = 27
targetSdkVersion = 26
supportLibVersion = "26.1.0"
}
package.json
"dependencies": {
"react": "16.4.1",
"react-native": "0.56.0",
"react-native-orientation": "^3.1.3",
},

I have solved issue with below code in android/build.gradle, might someone helps.
subprojects {
project.configurations.all {
afterEvaluate {project ->
if (project.hasProperty("android")) {
android {
compileSdkVersion 26
buildToolsVersion '26.0.2'
}
}
}
resolutionStrategy.eachDependency { details ->
if (details.requested.group == 'com.android.support'
&& !details.requested.name.contains('multidex') ) {
details.useVersion "26.0.2"
}
}
}
}

Its because mismatch versions in this projects build configuration and the app level build configurations.
I solved it with the following changes:
`def safeExtGet(prop, fallback) {
rootProject.ext.has(prop) ? rootProject.ext.get(prop) : fallback
}
apply plugin: 'com.android.library'
android {
compileSdkVersion safeExtGet('compileSdkVersion', 28)
buildToolsVersion safeExtGet('buildToolsVersion', '28.0.3')
defaultConfig {
    minSdkVersion safeExtGet('minSdkVersion', 19)
    targetSdkVersion safeExtGet('targetSdkVersion', 28)
    versionCode 1
    versionName "1.0"
    ndk {
        abiFilters "armeabi-v7a", "x86"
    }
}

}
dependencies {
compile "com.facebook.react:react-native:+"
}
`

repo: yamill/react-native-orientation

license: isc


text:
SELECT from Nothing

How can I SELECT from nothing?
I need to run query like
SELECT 1
CROSS JOIN ...

But for that syntax validator requires to have FROM clause present, otherwise it says the syntax is invalid.
->
SELECT 1
FROM <something here>
CROSS JOIN ...

Eg. some databases support select ... from dual
Possible with ClickHouse something similar?

Yes, just write FROM system.one
https://clickhouse.yandex/docs/en/operations/system_tables/#systemone

authors: alexey-milovidov simPod

repo: yandex/ClickHouse


text:
Users cannot be supplied just from zookeeper

I want to keep all more or less dynamic configuration (users, shards) in zookeeper. So I started with users:
<users from_zk="/clickhouse/dev/config-overrides/users" />

In zookeeper I have:
[zk: localhost:2181(CONNECTED) 15] get /clickhouse/dev/config-overrides/users

<ivan>
  <networks incl="networks" replace="replace">
    <ip>::/0</ip>
  </networks>
  <password_sha256_hex>f52fbd32b2b3b86ff88ef6c490628285f482af15ddcb29541f94bcf526a3f6c7</password_sha256_hex>
  <profile>default</profile>
  <quota>default</quota>
</ivan>

	<users><ivan>
  <networks incl="networks" replace="replace">
    <ip>::/0</ip>
  </networks>
  <password_sha256_hex>f52fbd32b2b3b86ff88ef6c490628285f482af15ddcb29541f94bcf526a3f6c7</password_sha256_hex>
  <profile>default</profile>
  <quota>default</quota>
</ivan></users>

In /etc/clickhouse-server/config-preprocessed.xml this renders as:
	<users><ivan>
  <networks incl="networks" replace="replace">
    <ip>::/0</ip>
  </networks>
  <password_sha256_hex>f52fbd32b2b3b86ff88ef6c490628285f482af15ddcb29541f94bcf526a3f6c7</password_sha256_hex>
  <profile>default</profile>
  <quota>default</quota>
</ivan></users>

This seems correct, but for some reason doesn't work (user is not found):
$ clickhouse-client --host clickhouse1 --user ivan --password hunter2
ClickHouse client version 1.1.54236.
Connecting to database system at clickhouse1:9000 as user ivan.
Code: 192. DB::Exception: Received from clickhouse1:9000, 172.21.0.5. DB::Exception: Unknown user ivan.

However, I managed to get individual users work by having this:
	<users>
		<ivan from_zk="/clickhouse/dev/config-overrides/ivan" />
	</users>

[zk: localhost:2181(CONNECTED) 16] get /clickhouse/dev/config-overrides/ivan

<networks incl="networks" replace="replace">
  <ip>::/0</ip>
</networks>
<password_sha256_hex>f52fbd32b2b3b86ff88ef6c490628285f482af15ddcb29541f94bcf526a3f6c7</password_sha256_hex>
<profile>default</profile>
<quota>default</quota>

In /etc/clickhouse-server/config-preprocessed.xml this renders as:
	<users>
		<ivan><networks incl="networks" replace="replace">
  <ip>::/0</ip>
</networks>
<password_sha256_hex>f52fbd32b2b3b86ff88ef6c490628285f482af15ddcb29541f94bcf526a3f6c7</password_sha256_hex>
<profile>default</profile>
<quota>default</quota></ivan>
	</users>

And it works:
$ clickhouse-client --host clickhouse1 --user ivan --password hunter2
ClickHouse client version 1.1.54236.
Connecting to database system at clickhouse1:9000 as user ivan.
Connected to ClickHouse server version 1.1.54236.

:)

So in both cases I have the same rendered config, but in the first case user is not found. This is quite sad, given that the most frequent operation is adding and removing users and the second case doesn't cover that.
Is there a way to make it work?

When I have individual users in zk and update them:
2017.06.07 20:48:19.225584 [ 11 ] <Debug> ConfigReloader: Loading config `/etc/clickhouse-server/config.xml'
2017.06.07 20:48:19.225584 [ 17 ] <Debug> ConfigReloader: Loading config `/etc/clickhouse-server/users.xml'

When I have whole <users> in zk and update it:
2017.06.07 20:50:19.457473 [ 11 ] <Debug> ConfigReloader: Loading config `/etc/clickhouse-server/config.xml'

With the help from @vavrusa we figured out that replace="replace" was missing. This works:
<?xml version="1.0"?>
<yandex>
	<profiles from_zk="/clickhouse-overrides/dev/profiles" replace="replace" />
	<quotas from_zk="/clickhouse-overrides/dev/quotas" replace="replace" />
	<users from_zk="/clickhouse-overrides/dev/users" replace="replace" />
</yandex>

Hi Ivan!
Glad you managed to get this working.
Did you add your overrides as a file in the conf.d directory? If yes, here is what happened. Users configuration is actually loaded not from config.xml, but from users.xml which is a separate config. First, overrides from your file were merged into that config. As users.xml already contains the <users> tag, in the absence of replace attribute the from_zk attribute was lost during this process, so your configuration was never added.
Now, here is why you were unable to debug the issue: files from the conf.d directory are added to both configs (in contrast to files from config.d and users.d which are added only to their respective configs). So your users configuration was inserted without problems into config-preprocessed.xml (where it didn't affect anything), but if you looked at the users-preprocessed.xml you would see the difference.
Finally, the most interesting question - what to do with this :) The root of the problem is that first the override files were merged into the main file, and only then includes were processed. Let me think a bit on whether reversing this order is more sensible.

@bobrik do you have any further questions?

authors: blinkov bobrik ztlpn


text:
🛑 Google is down

In 363b4f9, Google (https://google.icloudnative.io) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Google is back up in 542c25b after 1,124 days, 18 hours, 46 minutes.

repo: yangchuansheng/upptime


text:
🛑 Umami is down

In dcf3a36, Umami (https://umami.icloudnative.io) was down:

HTTP code: 503
Response time: 1471 ms

Resolved: Umami is back up in 2dd3822.


text:
后台编辑语言模型值无法保存。

⚠  确认 issue 是否已存在 ⚠

[X] 我已经搜索了现有的问题，没有找到跟我问题相关的问题。

GPT-3 or GPT-4
GPT-4
操作系统
Windows
Bug 描述 📝
后台编辑语言模型值无法保存。
重现步骤 🕹
后台管理员界面→语言模型→编辑模型值→保存。

我是全新安装部署的4.0.6版本。其他后台配置一切都正常保存变更。只有语言模型这里更改后无法保存。
你的应用配置信息
把你的配置信息粘贴到这里

你应该是数据库没有更新，缺少字段。


text:
HTTP 429 too many requests

I can only download at most 60 submissions. Maybe the script should respect the leetcode API rate limit?
{ Error: Request failed with status code 429
    at createError (/Users/xxx/Projects/leetcode-downloader/node_modules/axios/lib/core/createError.js:16:15)
    at settle (/Users/xxx/Projects/leetcode-downloader/node_modules/axios/lib/core/settle.js:18:12)
    at IncomingMessage.handleStreamEnd (/Users/xxx/Projects/leetcode-downloader/node_modules/axios/lib/adapters/http.js:191:11)
    at IncomingMessage.emit (events.js:187:15)
    at endReadableNT (_stream_readable.js:1081:12)
    at process._tickCallback (internal/process/next_tick.js:63:19)
  config:
   { adapter: [Function: httpAdapter],
     transformRequest: { '0': [Function: transformRequest] },
     transformResponse: { '0': [Function: transformResponse] },
     timeout: 0,
     xsrfCookieName: 'XSRF-TOKEN',
     xsrfHeaderName: 'X-XSRF-TOKEN',
     maxContentLength: -1,
     validateStatus: [Function: validateStatus],
     headers:
      { Accept: 'application/json, text/plain, */*',
        Cookie:

@yangshun Thanks! This tools has been very helpful.

Same problem, can you solve it? I do not have knowledge in JS.

authors: GoingMyWay sfdye

repo: yangshun/leetcode-downloader


text:
弹出以后如何禁止手动下滑关闭picker?

当弹出以后，不点击取消或者确认，可以手动向下滑动使picker关闭，如何禁止该行为？
还有一个问题，如果底部有Tab导航，能默认从最低端弹出吗？目前会在Tab上面弹出

个性化的需求，建议使用 makePicker 生成选择器小部件后，其它功能自己实现。

authors: xhanb yangyxd


text:
react/no-unused-prop-types false positive

This code:
import React from 'react';

type ObjectType = {
  usedDirectly: string;
  usedFromArray: string;
};

export class UseDirectly extends React.Component {
  props: {
    object: ObjectType;
  }

  render() {
    console.log(this.props.object.usedDirectly);
    return null;
  }
}

export class UseFromArray extends React.Component {
  props: {
    objects: Array<ObjectType>;
  }

  render() {
    console.log(this.props.objects[0].usedFromArray);
    return null;
  }
}

triggers this warning:
5:18  error  'object.usedFromArray' PropType is defined but prop is never used  react/no-unused-prop-types

Though strangely, this code encounters no errors:
import React from 'react';

type ObjectType = {
  usedDirectly: string;
  usedFromArray: string;
};

export class UseDirectly extends React.Component {
  props: {
    object: any;
  }

  render() {
    console.log(this.props.object.usedDirectly);
    return null;
  }
}

export class UseFromArray extends React.Component {
  props: {
    objects: Array<ObjectType>;
  }

  render() {
    console.log(this.props.objects[0].usedFromArray);
    return null;
  }
}

So you don't have to go hunting/searching, the only difference between them is the object: ObjectType vsobject: any. (Not sure why changing UseDirectly would affect the used-ness of usedFromArray field.)

This is probably related to / a duplicate of #811

This looks like a flow issue. Can we add a label please :) @ljharb thank you!

I've just hit what I think is the same problem as this. Not sure if this helps you.
File: https://github.com/guyellis/plant/blob/master/app/components/common/InputCombo.jsx
Contents copied here in case it changes in the interim:
const React = require('react');
const TextField = require('material-ui/TextField').default;
const PropTypes = require('prop-types');

function inputCombo(props) {
  const {
    changeHandler,
    disabled = false,
    error,
    fullWidth = true,
    label,
    multiLine = false,
    name: namo,
    placeholder,
    style = {},
    type = 'text',
    value,
  } = props || {};

  const underlineStyle = {
    display: 'none',
  };

  const styler = Object.assign({
    marginLeft: 20,
  }, style);

  return (
    <TextField
      disabled={disabled}
      errorText={error}
      floatingLabelText={label}
      fullWidth={fullWidth}
      hintText={placeholder}
      multiLine={multiLine}
      name={namo}
      onChange={changeHandler}
      style={styler}
      type={type}
      underlineStyle={underlineStyle}
      value={value}
    />
  );
}

inputCombo.propTypes = {
  changeHandler: PropTypes.func.isRequired,
  error: PropTypes.string,
  fullWidth: PropTypes.bool,
  label: PropTypes.string,
  multiLine: PropTypes.bool,
  name: PropTypes.string.isRequired, // eslint-disable-line no-dupe-keys
  placeholder: PropTypes.string,
  // eslint-disable-next-line react/forbid-prop-types
  style: PropTypes.object,
  value: PropTypes.oneOfType([
    PropTypes.string,
    PropTypes.number,
  ]).isRequired,
};

inputCombo.defaultProps = {
  error: '',
  fullWidth: true,
  label: '',
  multiLine: false,
  placeholder: '',
  style: {},
};

module.exports = inputCombo;

Error: https://travis-ci.org/guyellis/plant/builds/263855440
/home/travis/build/guyellis/plant/app/components/common/InputCombo.jsx

  47:18  error  'changeHandler' PropType is defined but prop is never used  react/no-unused-prop-types
  48:10  error  'error' PropType is defined but prop is never used          react/no-unused-prop-types
  49:14  error  'fullWidth' PropType is defined but prop is never used      react/no-unused-prop-types
  50:10  error  'label' PropType is defined but prop is never used          react/no-unused-prop-types
  51:14  error  'multiLine' PropType is defined but prop is never used      react/no-unused-prop-types
  52:9   error  'name' PropType is defined but prop is never used           react/no-unused-prop-types
  53:16  error  'placeholder' PropType is defined but prop is never used    react/no-unused-prop-types
  55:10  error  'style' PropType is defined but prop is never used          react/no-unused-prop-types
  56:10  error  'value' PropType is defined but prop is never used          react/no-unused-prop-types

To reproduce, clone that repo and npm i && npm run lint and you should see that. (Using Node 8.x)

@guyellis your "plant" repo seems to have been deleted.
If this is still a problem on the latest version of the plugin, please file a new issue with a repro.

authors: DianaSuvorova Eschon guyellis ljharb mikelambert

repo: yannickcr/eslint-plugin-react


text:
react/no-unused-prop-types doesn't support destructing (version 7.15.1)

I'm getting an error if a property was destructed:
//   X:Y  error  'foo' PropType is defined but prop is never used  react/no-unused-prop-types
const A = ({ foo: { bar } }) => <B bar={bar} />
A.propTypes = { foo: object };

It seems like a bug because I didn't find any information at "Known Issues/Limitations" about that.

This was fixed in #2428 but is not yet released.

authors: finom ljharb


text:
Pydantic v2 - performance issues on import

Hi,
when testing the pydantic v2 prelease (0.11.0a0), we're seeing a big performance decrease on process startup time.
My test file:
from githubkit import GitHub

went from ca. 1.6sec to 3.8sec on my M1 macbook. On production systems that have less powerful CPUs and slower I/Os, we're seeing this take 15-20sec now.
When interrupting the loading process with Ctrl+C, we see a stacktrace ala which hints at pydantic being the issue.
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/githubkit/__init__.py", line 2, in <module>
    from .github import GitHub as GitHub
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/githubkit/github.py", line 16, in <module>
    from .core import GitHubCore
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/githubkit/core.py", line 25, in <module>
    from .auth import BaseAuthStrategy, TokenAuthStrategy, UnauthAuthStrategy
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/githubkit/auth/__init__.py", line 1, in <module>
    from .app import AppAuthStrategy as AppAuthStrategy
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/githubkit/auth/app.py", line 10, in <module>
    from githubkit.rest import (
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/githubkit/rest/__init__.py", line 13, in <module>
    from .models import *
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/githubkit/rest/models.py", line 17358, in <module>
    class ReposOwnerRepoCodespacesGetResponse200(GitHubRestModel):
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_model_construction.py", line 184, in __new__
    complete_model_class(
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_model_construction.py", line 481, in complete_model_class
    schema = cls.__get_pydantic_core_schema__(cls, handler)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/main.py", line 576, in __get_pydantic_core_schema__
    return __handler(__source)
           ^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_schema_generation_shared.py", line 82, in __call__
    schema = self._handler(__source_type)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 452, in generate_schema
    schema = self._generate_schema(obj)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 684, in _generate_schema
    schema = self._post_process_generated_schema(self._generate_schema_inner(obj))
                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 706, in _generate_schema_inner
    return self._model_schema(obj)
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 525, in _model_schema
    {k: self._generate_md_field_schema(k, v, decorators) for k, v in fields.items()},
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 525, in <dictcomp>
    {k: self._generate_md_field_schema(k, v, decorators) for k, v in fields.items()},
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 870, in _generate_md_field_schema
    common_field = self._common_field_schema(name, field_info, decorators)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 923, in _common_field_schema
    schema = self._apply_annotations(
             ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 1592, in _apply_annotations
    schema = get_inner_schema(source_type)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_schema_generation_shared.py", line 82, in __call__
    schema = self._handler(__source_type)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 1682, in new_handler
    schema = metadata_get_schema(source, get_inner_schema)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_std_types_schema.py", line 315, in __get_pydantic_core_schema__
    items_schema = handler.generate_schema(self.item_source_type)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_schema_generation_shared.py", line 96, in generate_schema
    return self._generate_schema.generate_schema(__source_type)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 447, in generate_schema
    from_property = self._generate_schema_from_property(obj, obj)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 600, in _generate_schema_from_property
    schema = get_schema(
             ^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/main.py", line 576, in __get_pydantic_core_schema__
    return __handler(__source)
           ^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_schema_generation_shared.py", line 82, in __call__
    schema = self._handler(__source_type)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 684, in _generate_schema
    schema = self._post_process_generated_schema(self._generate_schema_inner(obj))
                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 706, in _generate_schema_inner
    return self._model_schema(obj)
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 525, in _model_schema
    {k: self._generate_md_field_schema(k, v, decorators) for k, v in fields.items()},
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 525, in <dictcomp>
    {k: self._generate_md_field_schema(k, v, decorators) for k, v in fields.items()},
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 870, in _generate_md_field_schema
    common_field = self._common_field_schema(name, field_info, decorators)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 923, in _common_field_schema
    schema = self._apply_annotations(
             ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 1592, in _apply_annotations
    schema = get_inner_schema(source_type)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_schema_generation_shared.py", line 82, in __call__
    schema = self._handler(__source_type)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 1571, in inner_handler
    from_property = self._generate_schema_from_property(obj, obj)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 600, in _generate_schema_from_property
    schema = get_schema(
             ^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/main.py", line 576, in __get_pydantic_core_schema__
    return __handler(__source)
           ^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_schema_generation_shared.py", line 82, in __call__
    schema = self._handler(__source_type)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 684, in _generate_schema
    schema = self._post_process_generated_schema(self._generate_schema_inner(obj))
                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 706, in _generate_schema_inner
    return self._model_schema(obj)
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 525, in _model_schema
    {k: self._generate_md_field_schema(k, v, decorators) for k, v in fields.items()},
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 525, in <dictcomp>
    {k: self._generate_md_field_schema(k, v, decorators) for k, v in fields.items()},
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 870, in _generate_md_field_schema
    common_field = self._common_field_schema(name, field_info, decorators)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 923, in _common_field_schema
    schema = self._apply_annotations(
             ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 1592, in _apply_annotations
    schema = get_inner_schema(source_type)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_schema_generation_shared.py", line 82, in __call__
    schema = self._handler(__source_type)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 1576, in inner_handler
    metadata_js_function = _extract_get_pydantic_json_schema(obj, schema)
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/criemen/repos/codeql-halo/.venv/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 1924, in _extract_get_pydantic_json_schema
    js_modify_function = getattr(tp, '__get_pydantic_json_schema__', None)
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/homebrew/Cellar/python@3.11/3.11.4/Frameworks/Python.framework/Versions/3.11/lib/python3.11/typing.py", line 1280, in __getattr__
    def __getattr__(self, attr):

Is there anything that can be done about this?

On top of that, RAM usage after loading githubkit is significantly higher with pydantic v2 as well.

Due to the huge number of models, i decide to use lazy import to improve the performance. #11
To lazy import the models, the codegen should be changed to group the models for each api version and each api client (api scope such as repo, issues)

I investigated this a bit more:
Some things that help (but model building is still slow!) are:

Upgrading to pydantic 2.4.2 - there are some potential performance improvements in there. It's not amazing, and you'll run into https://github.com/pydantic/pydantic/issues/7960 when upgrading
Switch from update_forward_refs() to model_rebuild() in models.py - the former is deprecated, and calls the latter with force=True, so the latter is doing less work
As you're calling model_rebuild on all models anyways, you can experiment with setting "defer_build": True for all models through the config settings in GithubRestModel

Hey @yanyongyu 👋 Since we benefit a lot from your work at polarsource/polar, I just pledged 100$ on this issue! Feel free to claim it over at https://polar.sh/ 😄

Hello, i'm currently working on lazy importing and api versioning. you can see it on the https://github.com/yanyongyu/githubkit/tree/feat/codegen-refactor branch. The first step which i'm working on is to refactor the codegen to support api versioning and top-level lazy loading (by defer import).

Hi @criemen @frankie567 , i have just published a release 0.11.0a2 with fully lazy loading feature. You can test it by installing the pre-release.

authors: criemen frankie567 yanyongyu

repo: yanyongyu/githubkit


text:
Update README.md

it's just a typo

Thank you! )

authors: hugojerez yariksav

repo: yariksav/vuetify-dialog


text:
grid.set is ok.. but, how to hide any widgets?

Hello guys!
Thank you for this amazing project. I love it. I have a question for you.
I am working with a grid, and it is ok. But i need to change my widgets because i am using a dynamic json to draw the widgets. I mean, i need to draw "x" number of bar widgets from a REST-API. If that json is sending me 3 nodes, then I need to draw three bar-widgets with the data. If that REST-API sends me twelve nodes, then I need to draw twelve.
I can use grid.set to draw that widgets with a "for" or something similar but... if my new request has a number of nodes  lower than before one then i need to hide the widgets  painted in the screen (or something similar) because screen.render() doesn't clear the buffer with the painted widgets i had before.
So, is there any method to clear the screen buffer or to hide widgets in a grid?
Thx

Check out how wopr does something similar:
https://github.com/yaronn/wopr/blob/master/lib/document-viewer.js#L52

Good trick!! working for me. Thx my lord. :+1:

cool :)

authors: vicendominguez yaronn

repo: yaronn/blessed-contrib


text:
キャッチアップ: active_record_migrations.md

https://github.com/yasslab/railsguides.jp/issues/937 の作業です。

@yasulab このファイルの水平線は問題ありませんでした。

こちら内容を確認しました！👀💨✨
他の PR と合わせて順次マージしていきますね! 🛠💨✨


text:
Dude, no words

That's cool. Like, really cool.

what do you mean?

@yatli. I think it is nice to have omnisharp as a part of coc ecosystem, and not needing to install extra plugins.

I see. I thought this is a bug report, like "not showing some words" :D

authors: kuator yatli

repo: yatli/coc-omnisharp


text:
Arreglar el index

Se debe cambiar el color del index

Se realizo el cambio de color de index

authors: hguzman yconsuegra

repo: yconsuegra/sandjett


text:
Check impact of smallvec

Run benchmarks replacing Vec by the one in the smallvec crate, and see if it's worth it to add a dependency.

SmallVec has a static initial size (stack allocated), and if the vec grows beyond that the contents are moved to the heap.
Benchmarks show good performance gains of ~30% for small expressions, but loses up to ~12% in performance for larger expressions (when more heap reallocations are happening).
We have some options:

keep what we have and don't benefit from the 30% gains from smallvec, but also don't lose 10% in large expressions.
use smallvec and accept losses in performance for larger expressions;
create a function for small expressions using a static array that just returns an error if the expression is too large;

I should check tinyvec as well (which does not use unsafe).

Somehow with tinyvec and an initial allocation of 16 tokens, most cases, even the small ones, regressed in performance.


text:
Tooltip issue

Forge version: 14.23.5.2855
Mod version: distinctdamagedescriptions-1.3-beta
There is only DDD mod.

I have tried to tweak client config. There still is the problem.

I have tested to change language. Only English is correct to display.

DDD doesn't have any updated localization that supports all of 1.3's features, so even if the tooltips didn't come out as a garbled mess, the text wouldn't be fully translated. Translation strings for the type names aren't actually provided by external lang files (although they could and probably should be). Some languages may be very challenging to support, given how DDD uses a custom font renderer to display damage type colours, and it may not behave very well for other languages. ("may not behave very well" is an understatement, it clearly doesn't from the screenshot you've provided)
While trying to tweak or patch the font renderer so it behaves correctly with other languages is certainly a noble cause, I expect that to be a little... challenging, given the difficulty I had implementing it to begin with 😅
I'll attempt to at least look into why the text comes out completely unsalvageable and see if I can fix that problem. Outside of that, the rest of this issue just boils down to the fact that localization for other languages doesn't exist for DDD and I'm a predominately English speaker so I can't write those lang files with any hopes of them being accurate.

I guess you break something in 1.3-beta.
There is not any problem in 1.2.1-beta.

authors: HuangAdam yeelp

repo: yeelp/Distinct-Damage-Descriptions