text:
Value "c++20" (of type "string") for combo option "C++ language standard to use" is not one of the choices.

I got this error when compiling, how we can skip this?
subprojects/jetstream/src/render/metal/tools/meson.build:1:0: ERROR: Value "c++20" (of type "string") for combo option "C++ language standard to use" is not one of the choices. Possible choices are (as string): "none", "c++98", "c++11", "c++14", "c++17", "gnu++98", "gnu++11", "gnu++14", "gnu++17".
c++ version:
jetstream| C++ compiler for the host machine: ccache c++ (clang 12.0.5 "Apple clang version 12.0.5 (clang-1205.0.22.9)")

Ran into that last night and it seemed to be a meson issue after some googling.
I had installed a venv to build this (OSX 13.4) and pip installed meson which gave me version 1.2.2
This gave me the same issue.
Then whilst debugging I accidentally ran  meson setup $HERE $HERE/build outside the venv and it picked up my homebrew installed meson at version 1.2.99 and ran to completion with no issues.
Still stuck with another issue but hope this helps!

Also, the meson issue that gave me the clue: mesonbuild/meson#11890

This is a very stupid error caused by Meson. Their Objective-C++ compiler uses hard-coded standards codes and they never updated them with the C++20 standard. I reported this error early this year. However, the Meson team is being very slow in releasing a stable version containing the fix linked above by @ion-concepts.

I asked the Meson team to consider distributing the patch as a minor release instead of version 1.3.0. Meanwhile, as @ion-concepts suggested, this can be avoided by installing the head version of Meson with Brew brew install --HEAD meson. Make sure to uninstall any previously installed Meson version (e.g. pip uninstall meson).

The first alpha release is now live. This issue should be resolved with the latest version of Meson.

authors: audioplatinum ion-concepts luigifcruz

repo: luigifcruz/CyberEther


text:
🛑 Next Test is down

In db9f39e, Next Test (https://test4.one-squared.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Next Test is back up in 0acb948.

source: gharchive/issue

repo: lukas-hablitzel/upptime

license: MIT

license_type: permissive

license_source: github-api


text:
Middlewares run in unexpected order

Unexpected to me, anyway 😀 Wanted to raise an issue before attempting a PR, in case this is the desired behaviour.
Repro: https://github.com/Rich-Harris/polka-middleware-order-repro
Essentially, it seems that middlewares without a basepath run before middlewares with one, regardless of the order in which they're added to the app. This means that a generic app.use(foo) will take precedence over an earlier app.use(basepath, serve('assets')), which can prevent assets from being served.

Yep yep, this is intentional! There's basically 3 levels that Polka runs through:

Global Middleware
Those defined without any basepath "filter"

Sub-something Groups
A Polka sub-application or a middleware group to run only on paths that begin with basepath.

Route handler
The final handler, which is also the most specific route match.

A response can be terminated anywhere along the pipeline, which immediately ends the pipeline too.
I'm not sure if I forgot that Express was order-dependent for tier handling, or if I never knew that. Either way, I find it much more appealing and useful to dynamically build out an application without necessarily having to do it in a specific order.

That said, order does matter when writing into global & sub-group arrays.

Another nice thing is that this allow sub-applications to carry their own (relative) global middleware, which makes composing larger applications/services really easy.
There's a little bit of text that touches on this. Of course, it's incomplete but a WIP Polka documentation site is planned to fix all this.
Lastly, I know this was just a demo repro (thanks!!) but the 404 handler you included is already the default behavior:
.use((req, res) => {
  res.writeHead(404);
  res.end('Not found');
})

Polka sends the status code & its statusText if no other message body was passed, seen here.
To change the 404 behavior, you'd pass an onNoMatch handler to Polka via polka({ onNoMatch }) which then gets run here.

Not sure if I fully understand without playing with it.
You can still mount Sapper as the last global middleware (as done in the example). And then if a user is using a basepath flag, they can still do the same thing so long as Sapper is calling next() when path is not a match.

That's the thing, it doesn't call next — it can't, really, because it's responsible for serving 4xx/5xx pages if nothing matches.
Maybe I need to do
app.use(basepath, serve, sapper)

rather than
app.use(basepath, serve).use(sapper)

, and reconfigure the routes accordingly.

Arguably, Sapper should only be handling 4xx-type responses when it's working within its assigned realm. By default (no Sapper-flag basepath), it gets to and should handle everything. But when localized to a certain range of paths, it should only be throwing 4xx's when it's a 400-type within that realm of the application.
Psuedo:
// assume global level by default
const isOwner = config.basepath ? req.path.startsWith(config.basepath) : true;
if (!isOwner) return next(); // not a match

// .. later on, no 'route' found
if (route === void 0) {
  // pass it off to main app logic, not Sapper responsibility
  return isOwner ? sapperError() : next();
}

Thanks for helping me think this stuff through, by the way 😀
You're absolutely right, Sapper should only deal with requests pertaining to its basepath. In fact, that insight led me to a much nicer way of doing things — now, all you need to do to mount an app on a basepath is this:
polka()
  .use('/my-basepath', serve('assets'), sapper({routes}))
  .listen(PORT);

No configuration or environment variables necessary, it just works!
So I'll close this issue rather than continuing to clutter up your tracker. The one thing that does give me pause is that I often order my middlewares to do this sort of thing:
app.use('/requests-that-should-not-be-logged', someMiddleware());
app.use(loggingMiddleware());

With Express, requests handled by earlier middlewares don't get handled by later middlewares (unless the earlier middleware wants that to happen, with next()), and controlling that is fairly intuitive. If I understand correctly, that's a little harder with Polka? You've spent more time thinking about this than me though, so your way probably makes more sense — I only mention it because it's a potential sticking point for Express refugees.

Great! Happy to help~! And not clutter at all haha
My general recommendation is that if you have a particular exception/filter, that you should manually filter that route from the global scope. That is, of course, assuming you're using an off-the-shelf solution and can't work in the behavior into the middleware directly.
Looking at the morgan logger example, you could do something like this:

const logger = morgan('dev'); // instantiate early

polka()
  .use((req, res, next) => {
    return req.url.includes('ignore-this') ? next() : logger(req, res, next);
  })
  .use('/items', require('./items')
  .use('/ignore-this', something())
  // ...

authors: Rich-Harris lukeed

repo: lukeed/polka


text:
JDK9 Documentation

Hey Luke :)
Please can you add the info required to import the module jdk9 into the documentation :)
uses io.xxxx?
Thanks bud

Great point, thanks, I'll do that now. It should be requires io.github.lukehutch.fastclasspathscanner; .

authors: GedMarc lukehutch

repo: lukehutch/fast-classpath-scanner

license: mit

license_source: bigquery


text:
Multithread classpath scanning

Java zipfile processing is not threadsafe. Switch to using TrueVFS instead, then make classpath scanning multithreaded:
https://truevfs.java.net/
Or try the NIO APIs, which are threadsafe:
http://www.pixeldonor.com/2013/oct/12/concurrent-zip-compression-java-nio/

Done, released in 1.90.0


text:
Issue adding extras

After installing scoop on Windows 7 and successfully installing several apps, running scoop bucket add extras returns the following error:
'https://github.com/lukesampson/scoop-extras.git' doesn't look like a valid git repository
Any ideas?

Is it possible you had an intermittent connection when you last tried? I was able to run the exact command here (on Windows 10) without issue.

Strange. I need to connect through a proxy server so it could be something to do with that. I've configured the proxy in scoop, but might need a bit more digging around.

Do any of the buckets work? Try scoop bucket add versions

You may need to configure git to use the proxy as well. It doesn't currently pass that information along

authors: deevus dlzharris

repo: lukesampson/scoop

license: unlicense


text:
Replace short function names with aliases

All one word function names have been renamed to avoid clashes
with aliases. Those functions are then aliased to their original
name.
Fixes #351

@lukesampson Please review these changes before merging them in. Just want to make sure you're happy with how I've named internal commands.

source: gharchive/pull-request


text:
Upper limit magnitudes

Thank you providing a valuable resource.
I have a query about upper limits. In the following observations...
58039.300799 -25.117 73.000    -0   24 o  0   1.04 314.46455 -41.64411  9451.30  6993.07 4.21 3.37 -85.3 -0.392 18.80 20.25 01a58039o0154o
58039.308154  20.191  0.946    30   29 o  0   1.06 314.46455 -41.64411  9465.36  7062.63 4.14 3.51 -84.9 -0.375 18.56 19.85 01a58039o0170o
58039.311396  23.280 15.714     2   28 o  0   0.90 314.46455 -41.64411   101.31  7141.91 3.66 3.11 -89.1 -0.361 18.71 19.86 01a58039o0177o
58039.315992 -20.110  0.819   -33   27 o  0   0.86 314.46455 -41.64411  9405.32  7014.74 3.91 3.13 -84.1 -0.399 18.68 19.87 01a58039o0187o
58039.319207  22.533  6.154     4   22 o  0   1.31 314.46455 -41.64411   116.99  7211.20 3.81 3.21 -88.0 -0.354 18.71 19.99 01a58039o0194o
58039.323828 -22.815  8.800    -3   24 o  0   1.40 314.46455 -41.64411  9389.65  7161.38 3.89 2.96 -84.1 -0.407 18.69 19.85 01a58039o0204o
58039.327039  20.461  1.245    24   30 o  0   1.18 314.46455 -41.64411    57.51  7167.27 3.53 2.80 -89.2 -0.375 18.76 19.90 01a58039o0211o
58039.334859  17.886  0.106   254   27 o  0  10.74 314.46455 -41.64411    41.17  7314.46 3.52 2.76 -89.1 -0.377 18.85 20.02 01a58039o0228o

...all but the last are non-detections with the mag5sig about 18.7, but the last one is a positive detection – with relatively high confidence from the error – but it is detected about a magnitude brighter than the upper limit. There is nothing to suggest that there is anything suspect with this observation, both the mag5sig and the sky are consistent with the other observations. So, does this mean that the mag5sig is too strict?
Your thought would be appreciated.
Thank you

Now there is an issue with this measurement, I can repeat the output when I force the photometry on the reduced images (not the difference images). There is a glitch, and the source flux measured is not reliable. There is no positive source visible at mag = 17.886 on the pixel images (I checked). The measure of quality chin (normalised chi-squared for the PSF fit) is very high, at 10.74, which is indicating a poor fit. So this is a spurious source.
But the two issues - the 5sigma limit question, and this spurious source, are two different problems.

Yes, I appreciate that, but you have answered the question anyway. I see that chi/n is rarely > 2 so it is a good discriminator of dud data.
Thanks.
From: smarttgit @.>
Sent: 20 November 2024 16:35
To: lukeshingles/atlasserver @.>
Cc: bhrT4v3S19 @.>; Author @.>
Subject: Re: [lukeshingles/atlasserver] Upper limit magnitudes (Issue #58)
Now there is an issue with this measurement, I can repeat the output when I force the photometry on the reduced images (not the difference images). There is a glitch, and the source flux measured is not reliable. There is no positive source visible at mag = 17.886 on the pixel images (I checked). The measure of quality chin (normalised chi-squared for the PSF fit) is very high, at 10.74, which is indicating a poor fit. So this is a spurious source.
But the two issues - the 5sigma limit question, and this spurious source, are two different problems.
—
Reply to this email directly, view it on GitHub https://github.com/lukeshingles/atlasserver/issues/58#issuecomment-2489062328 , or unsubscribe https://github.com/notifications/unsubscribe-auth/BNBKS4H2QX4EEYZ54JYQP632BS24LAVCNFSM6AAAAABSAOIHIKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBZGA3DEMZSHA .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/BNBKS4GT7WW6Y4S74P7ZSNT2BS24LA5CNFSM6AAAAABSAOIHIKWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUULQJ3Q.gif Message ID: @.*** @.***> >

repo: lukeshingles/atlasserver


text:
[MC 1.12 version 2.0.6] (Large) Apng not loading

I have an apng file I converted from an flv (it is 35 MBs large if that matters). I am able to get it to display its animation in Chrome, but when I try to use it with your mod I just get mixing textures. If I change the extension to .png, I can see the first frame with your mod but it naturally doesn't animate.
Is there something special I need to do in the config?

...yes. Yes there is. Make sure I'm pointing to the right file. Whoops.


text:
Option.any correctness

Option.any doesn't actually loop through its arguments, and returns right away.

Hey @paulrouget, thank you for the contribution
Could you please

Change the PR title to be in the imperative voice ("Fix ...", "Do ..." etc.)
Describe the issue in the description
Add or change a test so that the test suite verifies the new behavior

Hey @paulrouget, thank you for the contribution
Could you please

Change the PR title to be in the imperative voice ("Fix ...", "Do ..." etc.)
Describe the issue in the description
Add or change a test so that the test suite verifies the new behavior

Done.

Release in version 4.1.0 today.

authors: jstasiak paulrouget

repo: lune-climate/ts-results-es


text:
热力图有考虑加进来吗？

大佬，热力图有考虑加进来吗？

百度地图webgl版并未提供热力图，所以没有加，可以尝试使用百度官方的MapVGL

地图webgl版提供百度热力图，所以没有加，可以试用官方的MapVGL

好的，谢谢大佬

authors: lunnlew wenlisu

repo: lunnlew/baidu-map


text:
docker拉取latest实际上版本是0.4.4, 导致多账户模式的格式有问题

docker拉取latest实际上版本是0.4.4, 导致多账户模式的格式有问题

latest 版本应该是 v0.5，你拉取下来是 0.4.4 可能是因为你使用了镜像网站，没有从 docker hub 官网拉取。镜像跟官网没有同步更新。

latest 版本应该是 v0.5，你拉取下来是 0.4.4 可能是因为你使用了镜像网站，没有从 docker hub 官网拉取。镜像跟官网没有同步更新。

有可能, 我现在尝试指定版本

latest 版本应该是 v0.5，你拉取下来是 0.4.4 可能是因为你使用了镜像网站，没有从 docker hub 官网拉取。镜像跟官网没有同步更新。

我拉取了最新0.5版本的docker, 配置为2.4还是出现了多账户配置的报错, 我保留了单账户的空配置, 多账户的配置格式如下。
经过测试, 只配置单账户, 不配置多账户就可以正常运行
我的配置
# Freenom 账户 Freenom Account
FREENOM_USERNAME=''

# Freenom 密码 Freenom password
FREENOM_PASSWORD=''

# 多账户支持 Support for multiple accounts
MULTIPLE_ACCOUNTS='<11@qq.com>@<123456>|'<22@qq.com>@<123456>'

报错日志
[2022-08-09 14:15:48] 执行出错：Failed to parse dotenv file due to unexpected whitespace. Failed at ['@|'@']. [{"function":"Dotenv\\{closure}","class":"Dotenv\\Parser","type":"::","args":[["@|",4],"","args":["#####################################################################\r\n# 注意事项\r\n#\r\n# - 环境变量的格式为“键=值”，顶格写，注意等号两边不能有空格，值可以用单引号或者双引号引起来，不引也行（下面的特殊情况必须引起来）\r\n# - 因为环境变量中“#”代表注释，若密码中存在“#”字符的，一定要使用单引号将整个密码引起来，否则解析会在“#”字符前截止，如果密码中存在单双引号的，\r\n#    需要在单双引号前加“\\”转义\r\n# - 配置多账户不可省略单引号，且多个账户和密码的格式必须是“@|@|@”，不要有空格，就算有程序也会给你干掉\r\n#    e.g. MULTIPLE_ACCOUNTS='@|@|@'\r\n#    注意不要省略“”符号，否则无法正确匹配\r\n# - 若你只有单个账户，只配置 FREENOM_USERNAME 和FREENOM_PASSWORD 就够了\r\n# - 单账户和多账户的配置会被合并在一起读取并去重\r\n#####################################################################\r\n\r\n# .env 文件版本\r\nENV_FILE_VERSION='v2.4'\r\n\r\n######################  账户配置 Account config  #########################\r\n# Freenom 账户 Freenom Account\r\nFREENOM_USERNAME=''\r\n\r\n# Freenom 密码 Freenom password\r\nFREENOM_PASSWORD=''\r\n\r\n# 多账户支持 Support for multiple accounts\r\nMULTIPLE_ACCOUNTS='@|'@'\r\n\r\n# 【可选】 Freenom 代理 [Optional] Freenom proxy e.g. http:\/\/127.0.0.1:1081 or socks5:\/\/127.0.0.1:1080\r\nFREENOM_PROXY=''\r\n######################  end 账户配置  #########################\r\n\r\n######################  通知邮件配置 Email config  #########################\r\n# 机器人邮箱账户 Email of robot\r\nMAIL_USERNAME=''\r\n\r\n# 机器人邮箱密码（Gmail填密码，QQ邮箱或163邮箱填授权码） Password of the robot email\r\nMAIL_PASSWORD=''\r\n\r\n# 用于接收通知的邮箱 Email address used to receive notifications\r\nTO=''\r\n\r\n# 是否启用邮件推送功能 1：启用 0：不启用 Whether to enable email push features 1: enabled 0: not enabled\r\nMAIL_ENABLE=0\r\n\r\n# 【可选】 自定义邮箱配置 [Optional] Custom email config\r\n# 如果你想使用除“QQ邮箱、163邮箱、Gmail、Outlook邮箱”以外的邮箱或者自建邮箱服务作为机器人邮箱，可以自定义邮箱配置，否则请不要配置这些项\r\n# If you want to use mailboxes other than \"QQ mailbox, 163 mailbox, Gmail, Outlook mailbox\" or self-built mailbox service as robot mailbox, you can customize mailbox configuration, otherwise, please don't configure these items.\r\n\r\n# 【可选】 SMTP 服务器 [Optional] SMTP server e.g. smtp.gmail.com\r\nMAIL_HOST=''\r\n\r\n# 【可选】 SMTP 端口号，一般是 587 或者 465 [Optional] SMTP port number, usually 587 or 465\r\nMAIL_PORT=''\r\n\r\n# 【可选】 邮件加密方式，一般是 tls 或者 ssl 或者 starttls [Optional] Mail encryption method, usually tls or ssl or starttls\r\nMAIL_ENCRYPTION=''\r\n\r\n# end 自定义邮箱配置 end of custom email config\r\n\r\n######################  end 通知邮件配置  #########################\r\n\r\n######################  Telegram bot  #########################\r\n# 通过 Telegram bot 发送通知消息 Send messages via Telegram bot\r\n\r\n# 你的 chat_id，通过发送“\/start”给 @userinfobot 可以获取自己的 id Your chat_id, you can get your own id by sending \"\/start\" to @userinfobot\r\nTELEGRAM_CHAT_ID=''\r\n\r\n# 你的 Telegram bot 的 token Token for your Telegram bot\r\nTELEGRAM_BOT_TOKEN=''\r\n\r\n# 【可选】 Telegram 代理 [Optional] Telegram proxy e.g. http:\/\/127.0.0.1:1081 or socks5:\/\/127.0.0.1:1080\r\nTELEGRAM_PROXY=''\r\n\r\n# 【可选】 自建 Telegram 反向代理地址，不明白则请忽略此配置项，保持默认即可 [Optional] Please do not modify this item\r\n# 参考：https:\/\/web.archive.org\/web\/20220221035315\/https:\/\/hostloc.com\/thread-805441-1-1.html\r\n# 只要是一个合法的网址即可，程式会自动提取网址的主机部分。例如 https:\/\/xxx.xx.workers.dev\/ or xxx.xx.xx\r\nCUSTOM_TELEGRAM_HOST='api.telegram.org'\r\n\r\n# 是否启用 Telegram Bot 功能 1：启用 0：不启用 Whether to enable Telegram Bot features 1: enabled 0: not enabled\r\nTELEGRAM_BOT_ENABLE=0\r\n######################  end Telegram bot  #########################\r\n\r\n######################  企业微信  #########################\r\n# 企业 ID Corporate ID\r\nWECHAT_CORP_ID=''\r\n\r\n# 应用的凭证密钥 Credential keys for enterprise WeChat applications\r\nWECHAT_CORP_SECRET=''\r\n\r\n# 应用 ID\r\nWECHAT_AGENT_ID=''\r\n\r\n# 是否启用企业微信送信功能 1：启用 0：不启用 Whether to enable the enterprise WeChat message push function 1: Enable 0: Do not enable\r\nWECHAT_ENABLE=0\r\n######################  end 企业微信  #########################\r\n\r\n######################  Server 酱  #########################\r\n# Server 酱的 SendKey\r\nSCT_SEND_KEY='SCT20558TO2sCucRdRUE4xVfAcT4ypTus'\r\n\r\n# 是否启用 Server 酱 送信功能 1：启用 0：不启用 Whether to enable the ServerChan message function 1: enabled 0: not enabled\r\nSCT_ENABLE=0\r\n######################  end Server 酱  #########################\r\n\r\n######################  Bark 送信  #########################\r\n# Bark key 打开 Bark App，注册设备后看到的 key Open the Bark App, register the device and see the key\r\n# 支持直接粘贴 “https:\/\/api.day.app\/xxx\/这里改成你自己的推送内容” 这类文本，程序会自动从中提取有效的 Bark key Support direct paste \"https:\/\/api.day.app\/xxx\/这里改成你自己的推送内容\" type of text, the program will automatically extract the valid Bark key from it\r\nBARK_KEY=''\r\n\r\n# Bark 域名 默认是 Bark 作者提供的服务，建议自建 The Bark URL defaults to the server provided by the Bark author, and it is recommended to build your own\r\nBARK_URL='https:\/\/api.day.app'\r\n\r\n# Bark 其它相关参数（保持默认即可）\r\nBARK_IS_ARCHIVE=''\r\nBARK_GROUP='FreeNom'\r\nBARK_LEVEL='active'\r\nBARK_ICON='https:\/\/q2.qlogo.cn\/headimg_dl?dst_uin=593198779&spec=100'\r\nBARK_JUMP_URL=''\r\nBARK_SOUND='gotosleep'\r\n\r\n# 是否启用 Bark 推送消息 1：启用 0：不启用 Whether to enable Bark push messaging 1: Enable 0: Do not enable\r\nBARK_ENABLE=0\r\n######################  end Bark 送信  #########################\r\n\r\n# 通知频率 0：仅当有续期操作的时候 1：每次执行 Notification frequency 0: Only when there is a renewal operation 1: Each execution\r\nNOTICE_FREQ=1\r\n\r\n# 是否验证服务器证书 1：验证 0：不验证 Whether to verify the server certificate 1: verify 0: no verification\r\nVERIFY_SSL=0\r\n\r\n# 是否开启 Debug 模式 1：开启 0：关闭 Whether to turn on Debug mode 1: On 0: Off\r\nDEBUG=0\r\n\r\n# 检测是否有新版本可用，发现新版本时推送消息通知 1：开启 0：关闭 Automatically detects if a new version is available and pushes a message notification when a new version is found 1: On 0: Off\r\nNEW_VERSION_DETECTION=1\r\n\r\n# 应用语言配置 Application language configuration, the supported values are zh or en, zh means Chinese, en means English\r\nLANGUAGE=zh\r\n\r\n# 送信时是否显示服务器信息 1：显示 0：不显示 Whether to display server information when sending messages 1: Display 0: Do not display\r\nSHOW_SERVER_INFO=0\r\n"]},{"file":"\/app\/vendor\/vlucas\/phpdotenv\/src\/Dotenv.php","line":123,"function":"load","class":"Dotenv\\Loader","type":"->","args":[]},{"file":"\/app\/vendor\/vlucas\/phpdotenv\/src\/Dotenv.php","line":80,"function":"loadData","class":"Dotenv\\Dotenv","type":"->","args":[]},{"file":"\/app\/libs\/Env.php","line":24,"function":"load","class":"Dotenv\\Dotenv","type":"->","args":[]},{"file":"\/app\/libs\/Base.php","line":58,"function":"init","class":"Luolongfei\\Libs\\Env","type":"->","args":[]},{"file":"\/app\/app\/helpers.php","line":209,"function":"getInstance","class":"Luolongfei\\Libs\\Base","type":"::","args":[]},{"file":"\/app\/app\/Console\/MigrateEnvFile.php","line":61,"function":"env","args":[]},{"file":"\/app\/app\/Console\/MigrateEnvFile.php","line":45,"function":"getAllOldEnvValues","class":"Luolongfei\\App\\Console\\MigrateEnvFile","type":"->","args":[]},{"file":"\/app\/app\/Console\/MigrateEnvFile.php","line":37,"function":"__construct","class":"Luolongfei\\App\\Console\\MigrateEnvFile","type":"->","args":[]},{"file":"\/app\/app\/helpers.php","line":257,"function":"getInstance","class":"Luolongfei\\App\\Console\\MigrateEnvFile","type":"::","args":[]},{"file":"\/app\/run","line":134,"function":"system_check","args":[]},{"file":"\/app\/run","line":150,"function":"run","args":[]}]

你多账户格式有问题。中间多了个单引号。

MULTIPLE_ACCOUNTS='11@qq.com@<123456>|'22@qq.com@<123456>'
应改为：
MULTIPLE_ACCOUNTS='11@qq.com@<123456>|22@qq.com@<123456>'

authors: FairyWorld luolongfei

repo: luolongfei/freenom


text:
🛑 Luratic is down

In a595680, Luratic (https://luratic.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Luratic is back up in c8ec01a after 4 minutes.

repo: luratic-devs/upptime


text:
Implement stack unwinding for more architectures, use unwind info, stack scanning

Currently we only have support for unwinding stacks on x86:
https://github.com/luser/rust-minidump/blob/e73f08c09f6177eae07f6f4f028367c61f42de1f/minidump-processor/src/stackwalker/mod.rs#L19
and even on x86 we only support unwinding with frame pointers:
https://github.com/luser/rust-minidump/blob/e73f08c09f6177eae07f6f4f028367c61f42de1f/minidump-processor/src/stackwalker/x86.rs#L81
We should at least support unwinding the CPU architectures that Firefox ships on (x86-64, arm, aarch64). Additionally, we should support using unwind info from symbol files (STACK CFI and STACK WIN) to unwind, since those produce more useful results when available. Finally, we should support stack scanning like Breakpad does so we can get fuller stacks when traditional unwinding fails.
Ideally we'd figure out how to share unwind code with other projects, but in the short term simply porting Breakpad's unwind code would be sufficient to make this useful.

Closing this in favour of smaller more focused issues above ^

authors: Gankra luser

repo: luser/rust-minidump


text:
fix(?): s.ns can be nil

I was getting the following error on nightly v0.10.0-dev-2445+g2e1f5055a. There is no error when using v0.9.2.
E5108: Error executing lua .../.local/share/nvim/lazy/statuscol.nvim/lua/statuscol.lua:69: attempt to index field 'ns' (a nil value) stack traceback:
	.../.local/share/nvim/lazy/statuscol.nvim/lua/statuscol.lua:69: in function 'update_sign_defined'
	.../.local/share/nvim/lazy/statuscol.nvim/lua/statuscol.lua:190: in function 'place_signs'
	.../.local/share/nvim/lazy/statuscol.nvim/lua/statuscol.lua:248: in function 'update_callargs'
	.../.local/share/nvim/lazy/statuscol.nvim/lua/statuscol.lua:284: in function <.../.local/share/nvim/lazy/statuscol.nvim/lua/statuscol.lua:262>

I don't know the root cause, but adding an or "" seems to fix it.

Thanks but you shouldn't get this error on the 0.10 branch, please see https://github.com/luukvbaal/statuscol.nvim/issues/91.
Might try to make the 0.10 branch compatible with 0.9 to backport some of the recent fixes.
I hadn't up to this point so as to avoid any unnecessary if else chains in the performance critical statuscolumn code. But it's probably fine and worth getting rid of the branch inconvenience while the 0.10 dev cycle lingers on 😅

authors: cockytrumpet luukvbaal


text:
fs_scandir iterator causes memory leak with early break

Using fs_scandir and fs_scandir_next as an iterator results in a memory leak if the iterator is not fully drained. Example:
local luv = require 'luv'

local function dir(d)
  return function(fs)
    return luv.fs_scandir_next(fs)
  end, luv.fs_scandir(d)
end

for name in dir('.') do
  print(name)
  break
end

This results in a memory leak. This happens because the uv_fs_req is only cleaned up when the iterator reaches a UV_EOF:
https://github.com/luvit/luv/blob/c51e7052ec4f0a25058f70c1b4ee99dd36180e59/src/fs.c#L600-L605
However, when the iteration loop breaks early this condition is never hit and uv_fs_req_cleanup is never called.
It does not seem possible to manually cleanup the fs handles either: fs:close() does not exist.

Thanks for the report, I'll look into it.

Here's an even simpler reproduction:
local uv = require('luv')
local req = uv.fs_scandir('.')

As pointed out in the OP, we currently only handle cleanup when we fully iterate with scandir_next.

repo: luvit/luv


text:
Replace old pipeline.createNode calls create([node])

Description
Some of the examples still contain the old pipeline.create() calls. This pull request replaces these call with the new type calls obtained from: https://github.com/luxonis/depthai-python/blob/main/src/pipeline/PipelineBindings.cpp
The following script was used to replace automatically these calls:
https://gist.github.com/ibaiGorordo/e23bf57869ad48ada0701f76e4d307b6
However, I have only tested that the changes work in some of the examples, so there might be some issue in some of the examples.

Thanks @ibaiGorordo
Actually, the pipeline.create([node]) is the new syntax to create nodes.
We haven't deprecated those yet (as stated in TODO of https://github.com/luxonis/depthai-python/blob/main/src/pipeline/PipelineBindings.cpp#L113) as a lot of code still uses them and it'd result in a lot of noise.
Main intention of the new syntax is to be closer to C++ - we've also addressed the type hints to work for that usecase
Do you mind creating your script in reverse and updating the PR to convert from create[Node]() to create([node])?

Oh I see, I have updated the PR with the create([node]) calls.
Here is the link to the gist with the code:
And just in case I post the code here also:
from tempfile import mkstemp
from shutil import move, copymode
from os import fdopen, remove
import os

# Ref: https://github.com/luxonis/depthai-python/blob/main/src/pipeline/PipelineBindings.cpp
pattern_replacement = { "createXLinkIn()"                           : "create(dai.node.XLinkIn)",
                        "createXLinkOut()"                          : "create(dai.node.XLinkOut)",
                        "createNeuralNetwork()"                     : "create(dai.node.NeuralNetwork)",
                        "createColorCamera()"                       : "create(dai.node.ColorCamera)",
                        "createVideoEncoder()"                      : "create(dai.node.VideoEncoder)",
                        "createSPIOut()"                            : "create(dai.node.SPIOut)",
                        "createSPIIn()"                             : "create(dai.node.SPIIn)",
                        "createImageManip()"                        : "create(dai.node.ImageManip)",
                        "createMonoCamera()"                        : "create(dai.node.MonoCamera)",
                        "createStereoDepth()"                       : "create(dai.node.StereoDepth)",
                        "createMobileNetDetectionNetwork()"         : "create(dai.node.MobileNetDetectionNetwork)",
                        "createYoloDetectionNetwork()"              : "create(dai.node.YoloDetectionNetwork)",
                        "createSystemLogger()"                      : "create(dai.node.SystemLogger)",
                        "createSpatialLocationCalculator()"         : "create(dai.node.SpatialLocationCalculator)",
                        "createMobileNetSpatialDetectionNetwork()"  : "create(dai.node.MobileNetSpatialDetectionNetwork)",
                        "createYoloSpatialDetectionNetwork()"       : "create(dai.node.YoloSpatialDetectionNetwork)",
                        "createObjectTracker()"                     : "create(dai.node.ObjectTracker)",
                        "createEdgeDetector()"                      : "create(dai.node.EdgeDetector)",
                        "createFeatureTracker()"                    : "create(dai.node.FeatureTracker)",
                        "createAprilTag()"                          : "create(dai.node.AprilTag)"}

# Ref: https://stackoverflow.com/a/39110/13706271
def replace_createNode_call(file_path):

    #Create temp file
    fh, abs_path = mkstemp()
    contains_old_pattern = False
    with fdopen(fh,'w',encoding="utf8") as new_file:

        with open(file_path,encoding="utf8") as old_file:

            # Read the old script
            script = old_file.read()

            for old_pattern in pattern_replacement.keys():

                # Replace the pattern if any it contains any of the old create patterns
                if old_pattern in script:

                    contains_old_pattern = True
                    new_pattern = pattern_replacement[old_pattern]
                    script = script.replace(old_pattern, new_pattern)
                    print(f"Replaced {old_pattern} with {new_pattern} in {file_path}")

            # Only rewrite scripts that have the old pattern
            if contains_old_pattern:
                new_file.write(script)

    if contains_old_pattern:
        #Copy the file permissions from the old file to the new file
        copymode(file_path, abs_path)
        #Remove original file
        remove(file_path)
        #Move new file
        move(abs_path, file_path)

if __name__ == '__main__':

    rootdir = 'depthai-experiments'

    for subdir, dirs, files in os.walk(rootdir):
        for file in files:
            if file.endswith(".py"):

                file_path = os.path.join(subdir, file)

                replace_createNode_call(file_path)
            else:
                continue

authors: ibaiGorordo themarpe

repo: luxonis/depthai-experiments


text:
Mirror the mono camera videos during calibration

The 'why' of this is if the video is not mirrored, you're instincts are to move the calibration checkerboard in the wrong direction.  It's like riding a bike with the handlebars reversed (it's really hard, see here).
So this is why w/ FaceTime and other tools that show yourself, they mirror the video.  It's way more intuitive (in the FaceTime, they mirror it when they show it back to you, but then don't mirror it going out to the other party).
So we should do the same thing, mirror on display only, and pass the original frames-is to the calibration routine.
So I think the host (even the Pi) should be fast enough to do the flipping, but if not we can probably flip the streams in the Myriad X easily.

So @VanDavv I'm thinking we should make inverting on the horizontal axis default.
So there are two ways to calibrate:

The board is stationary, the calibration target moves.
The calibration target is stationary, the board moves.

For both 1 and 2 having the imaged flipped horizontally is desirable.  For '2' flipping vertically is also desirable.
But since flipping horizontally is beneficial for both I'm thinking we have that as the default.
Thoughts?
Thanks,
Brandon

On 1097 it works well with the default non-flipped image, and my gut feeling tells me to keep flags defaulting to false (wanted to refactor the --no-swap-lr to --swap-lr). But anyway, it doesn't really matter to me, can make them as default. We need to decide which model is "base" one

Got it.  Maybe I should try again now that it's not latent.  Yes I'd say ignore my comment for now until I get a chance to play with it more.
Thanks for the quick response @VanDavv !

authors: Luxonis-Brandon VanDavv

repo: luxonis/depthai


text:
SNKRX

Project link: https://github.com/a327ex/SNKRX
Project license: MIT
Does it work on 64-bit only Linux: MAYBE (Untested)
Is source code available?: YES
Is source code stored in Git?: YES
List of Steam AppIds of supported games:

https://steamdb.info/app/915310/

Additional Comments
Project is the game itself, made by the developer, but not published on Steam for non-Windows.

Turns out I under-estimated the ability for the repo to run on Linux. Getting it running is still fairly trivial, being a matter of acquiring love, luasteam.so, and libsteam_api.so.

It looks like if the steam_api library is required that we won't be able to package it.
https://github.com/a327ex/SNKRX/blob/986db10053e25e0f892b4b60122faaf2cba97872/engine/init.lua#L49 seems to indicate that the steam API is required for it to launch. If the game had a non-steam mode then it'd be possible, but does not seem likely.
Let me know if anything changes on this though.

repo: luxtorpeda-dev/packages

license: Zlib


text:
Tap to focus don't work on Android (And auto focus is working badly)

Steps to reproduce

Here's the component of my view (there's only that component) :

<Camera
         ref={(cam) => {
         this.camera = cam;
         }}
         captureQuality={Camera.constants.CaptureQuality["720p"]}
         captureTarget={Camera.constants.CaptureTarget.memory}
         defaultOnFocusComponent={true}
         captureAudio = {false}
         onFocusChanged={() => {console.log("focusChanged");}}
         onZoomChanged={() => {console.log("zoomChanged");}}
         style={styles.preview}
         aspect={Camera.constants.Aspect.fill}/>

Expected behaviour
On tap --> focus
On move --> try autofocus
Any idea ?
Actual behaviour
On tap --> Nothing
On move --> autofocus sometime happens, sometime don't
Environment

Node.js version: 7.6.0
React Native version: 0.42.0
React Native platform + platform version: iOS 9.0, Android 5.0, etc

react-native-camera
Version: 0.6.0 or 0.7.0, same issue

This issue is maybe solved in PR  https://github.com/lwansbrough/react-native-camera/pull/575 ?

Upgraded to latest version today and same thing.
Currently running:

software
version

react-native-camera
0.7.0

react-native
0.43.4

node
v7.8.0

npm or yarn
npm 4.5.0

Previously I was running react-native 0.42.3 with the forked version of this repo with the fix and it was working great.

react-native-camera 0.7.0 was released before https://github.com/lwansbrough/react-native-camera/pull/578 was merged, so I guess you have to wait for the next release, or use the master branch as a dependency in your package.json: "react-native-camera": "lwansbrough/react-native-camera"

Ah! Of course! Thank you.

I've just tested it in 0.8.0 and having the same problems, should that be fixed already in that version?

+1

add this to AndroidManifest:

For me, it seems autofocus works better now

In my case it happened when I updated the component (setState()) right after camera.capture(). I removed <Camera/> in order to show <ActivityIndicator/>. So it seems that it get stuck if it's saving the image but the component doesn't exist anymore

Shouldn't @csae0's comment be in the documentation?

@iarambula Feel free to send a pull request that improves the documentation.
I am going to close this issue. Please open a new or search for an existing open issue if you are still experiencing this issue with RNCamera.

authors: Thomeuxe brooth csae0 escobar5 iarambula jarredszabadi luco mikaello n1ru4l

repo: lwansbrough/react-native-camera


text:
🛑 lwdSite API is down

In ab51065, lwdSite API (https://api.liwenduan.com/lwd-site) was down:

HTTP code: 0
Response time: 0 ms

Resolved: lwdSite API is back up in 248ec3a.

repo: lwdStudio/lwdStatus


text:
Improve zfs snapshot restore error

Distribution: Ubuntu
Distribution version: 16.04 (Xenial)
The output of "lxc info" or if that fails:

% lxc info
apicompat: 0
auth: trusted
environment:
addresses: []
architectures:

x86_64

i686
driver: lxc
driverversion: 2.0.0.rc13
kernel: Linux
kernelarchitecture: x86_64
kernelversion: 4.4.0-15-generic
server: lxd
serverpid: 7284
serverversion: 2.0.0.rc6
storage: zfs
storageversion: "5"
config:
core.trust_password: true
storage.zfs_pool_name: lxd_zfs
public: false

lxc snapshots when using lxd do not warn that zfs backends only work with one backup.
However, when you restore, it warns you (when it's too late as you've already added another
snapshot).
Steps to reproduce

lxc launch ubuntu t1
lxc snapshot t1 first
lxc snapshot t1 second
lxc restore t1 first

% lxc restore t1 first
error: ZFS only supports restoring state to the latest snapshot.

You misunderstand the error, ZFS does support multiple snapshots, all the snapshots listed do exist and are perfectly usable, you just can't restore anything but last one.
So if you want to restore the before to last one, you have to remove the last one.
Alternatively, you can "copy" any snapshot you want into a new container with "lxc copy source-container/snapshot-name new-container"

It remains confusing highly.  Doubly so since I could see that I was allowed to create multiple snapshots.  Allowing one to view multiple snapshots via lxc info  and then having restore fail is highly confusing.  I do think it would be valuable to document, acknowledge the subtlety here.
The copy worked.  It would be nice to put that in the error message.  Something akin to:  We can only restore to the previous snapshot.  To use older snapshots, use lxc copy /

Yeah, we can certainly tweak the error message a bit.

This is not an lxd issue thou i think lxd doc should temporarily mention an important information about zfs dmks available at ubuntu 15.10
zfs-dkms and spl-dkms at at 15.10 is shipped with  0.6.4.2-0ubuntu1.1 version (http://packages.ubuntu.com/search?keywords=spl-dkms&searchon=names)
This version induces kernel panic if snapshots are accessed via hidden .zfs/snapshot folder
This feature is very useful if one would like to access snapshot data without restoring/cloning  dataset (for instance just access state of single file without rolling back entire fs)
xenial version has this fixed and Ubuntu 15.10 can have
# dkms status
spl, 0.6.5.6, 4.2.0-34-generic, x86_64: installed
zfs, 0.6.5.6, 4.2.0-34-generic, x86_64: installed

via deb http://ppa.launchpad.net/zfs-native/stable/ubuntu wily main

Can you file a bug in Ubuntu against the zfs-dkms package?
This should either be fixed or the feature should be turned off, but a kernel panic is a pretty wrong behavior :)

https://launchpad.net/ubuntu/+source/zfs-dkms/+filebug

1st. Above link does not work (This page does not exist, or you may not have permission to see it.)
2nd. This is old bug. I run onto it at debian a long time ago and get rid of it by using "deb http://archive.zfsonlinux.org/debian wheezy main" .
https://github.com/zfsonlinux/zfs/issues/3243
https://github.com/zfsonlinux/zfs/issues/3948
https://github.com/zfsonlinux/zfs/issues/3257
https://github.com/zfsonlinux/zfs/issues/3786
bug is fixed but for some reason ubuntu 15.10 still ships with old broken pkg
Standard 15.10 instalation has:
$ dkms status
spl, 0.6.4.2, 4.2.0-30-generic, x86_64: installed
spl, 0.6.4.2, 4.2.0-34-generic, x86_64: installed
zfs, 0.6.4.2, 4.2.0-30-generic, x86_64: installed
zfs, 0.6.4.2, 4.2.0-34-generic, x86_64: installed
I am not sure who to contact with to be honest, will try package maintainter from http://packages.ubuntu.com/wily-updates/spl-dkms

Hi, I am wondering is there any ways we can 'store'/backup snapshot for a given container?  Let say i have 4 snapshot (snap1-4), and i wanted to restore to snap2. For now what i can do is to delete snap 3 & 4 to achieve that. But i might want to restore 3 or 4 later on? Is it possible to create a 'placeholder' container and park all snap under it?
Thanks for the advise.

authors: HW-Siew nick4u raharper stgraber

repo: lxc/lxd


text:
LXD hangs on any command - including init - after resize zfs pool

Required information

Distribution: Ubuntu
Distribution version: 18.04
The output of "lxc info" or if that fails:

Kernel version: 4.15.0-30-generic
LXC version: 3.0.1-0ubuntu1~18.04.2
LXD version: 3.0.1-0ubuntu1~18.04.1
Storage backend in use: zfs

Issue description
After resizing one zfs pool (growing 50G to 100G)
No lxd commands seem to work - system hands on lxc list - then eventually fails with the error
Error: Get http://unix.socket/1.0: dial unix /var/lib/lxd/unix.socket: connect: connection refused
Steps to reproduce

resize zfs pool
reboot
run lxc list or lxc info - any client command hangs and fails

Information to attach

[ ] Main daemon log (at /var/log/lxd/lxd.log or /var/snap/lxd/common/lxd/logs/lxd.log)
lvl=info msg="Raft: Node at 0 [Leader] entering Leader state" t=2018-08-15T19:36:46+0000
lvl=info msg="LXD 3.0.1 is starting in normal mode" path=/var/lib/lxd t=2018-08-15T19:42:34+0000
lvl=info msg="Kernel uid/gid map:" t=2018-08-15T19:42:34+0000
lvl=info msg=" - u 0 0 4294967295" t=2018-08-15T19:42:34+0000
lvl=info msg=" - g 0 0 4294967295" t=2018-08-15T19:42:34+0000
lvl=info msg="Configured LXD uid/gid map:" t=2018-08-15T19:42:34+0000
lvl=info msg=" - u 0 165536 65536" t=2018-08-15T19:42:34+0000
lvl=info msg=" - g 0 165536 65536" t=2018-08-15T19:42:34+0000
lvl=warn msg="CGroup memory swap accounting is disabled, swap limits will be ignored." t=2018-08-15T19:42:34+0000
lvl=info msg="Initializing local database" t=2018-08-15T19:42:34+0000
lvl=info msg="Initializing database gateway" t=2018-08-15T19:42:34+0000
address= id=1 lvl=info msg="Start database node" t=2018-08-15T19:42:34+0000
lvl=info msg="Raft: Restored from snapshot 1-1071-1533245019683" t=2018-08-15T19:42:34+0000
lvl=info msg="Raft: Initial configuration (index=1): [{Suffrage:Voter ID:1 Address:0}]" t=2018-08-15T19:42:34+0000
lvl=info msg="LXD is socket activated" t=2018-08-15T19:42:34+0000
lvl=info msg="Starting /dev/lxd handler:" t=2018-08-15T19:42:34+0000
lvl=info msg=" - binding devlxd socket" socket=/var/lib/lxd/devlxd/sock t=2018-08-15T19:42:34+0000
lvl=info msg="REST API daemon:" t=2018-08-15T19:42:34+0000
lvl=info msg=" - binding Unix socket" socket=/var/lib/lxd/unix.socket t=2018-08-15T19:42:34+0000
lvl=info msg="Initializing global database" t=2018-08-15T19:42:34+0000
lvl=info msg="Raft: Node at 0 [Leader] entering Leader state" t=2018-08-15T19:42:34+0000
lvl=info msg="LXD 3.0.1 is starting in normal mode" path=/var/lib/lxd t=2018-08-15T19:52:34+0000
lvl=info msg="Kernel uid/gid map:" t=2018-08-15T19:52:34+0000
lvl=info msg=" - u 0 0 4294967295" t=2018-08-15T19:52:34+0000
lvl=info msg=" - g 0 0 4294967295" t=2018-08-15T19:52:34+0000
lvl=info msg="Configured LXD uid/gid map:" t=2018-08-15T19:52:34+0000
lvl=info msg=" - u 0 165536 65536" t=2018-08-15T19:52:34+0000
lvl=info msg=" - g 0 165536 65536" t=2018-08-15T19:52:34+0000
lvl=warn msg="CGroup memory swap accounting is disabled, swap limits will be ignored." t=2018-08-15T19:52:34+0000
lvl=info msg="Initializing local database" t=2018-08-15T19:52:34+0000
lvl=info msg="Initializing database gateway" t=2018-08-15T19:52:34+0000
address= id=1 lvl=info msg="Start database node" t=2018-08-15T19:52:34+0000
lvl=info msg="Raft: Restored from snapshot 1-1071-1533245019683" t=2018-08-15T19:52:34+0000
lvl=info msg="Raft: Initial configuration (index=1): [{Suffrage:Voter ID:1 Address:0}]" t=2018-08-15T19:52:34+0000
lvl=info msg="Raft: Node at 0 [Leader] entering Leader state" t=2018-08-15T19:52:34+0000
lvl=info msg="LXD is socket activated" t=2018-08-15T19:52:34+0000
lvl=info msg="Starting /dev/lxd handler:" t=2018-08-15T19:52:34+0000
lvl=info msg=" - binding devlxd socket" socket=/var/lib/lxd/devlxd/sock t=2018-08-15T19:52:34+0000
lvl=info msg="REST API daemon:" t=2018-08-15T19:52:34+0000
lvl=info msg=" - binding Unix socket" socket=/var/lib/lxd/unix.socket t=2018-08-15T19:52:34+0000
lvl=info msg="Initializing global database" t=2018-08-15T19:52:34+0000
lvl=info msg="LXD 3.0.1 is starting in normal mode" path=/var/lib/lxd t=2018-08-15T19:57:18+0000
lvl=info msg="Kernel uid/gid map:" t=2018-08-15T19:57:18+0000
lvl=info msg=" - u 0 0 4294967295" t=2018-08-15T19:57:18+0000
lvl=info msg=" - g 0 0 4294967295" t=2018-08-15T19:57:18+0000
lvl=info msg="Configured LXD uid/gid map:" t=2018-08-15T19:57:18+0000
lvl=info msg=" - u 0 165536 65536" t=2018-08-15T19:57:18+0000
lvl=info msg=" - g 0 165536 65536" t=2018-08-15T19:57:18+0000
lvl=warn msg="CGroup memory swap accounting is disabled, swap limits will be ignored." t=2018-08-15T19:57:18+0000
lvl=info msg="Initializing local database" t=2018-08-15T19:57:18+0000
lvl=info msg="Initializing database gateway" t=2018-08-15T19:57:18+0000
address= id=1 lvl=info msg="Start database node" t=2018-08-15T19:57:18+0000
lvl=info msg="Raft: Restored from snapshot 1-1071-1533245019683" t=2018-08-15T19:57:18+0000
lvl=info msg="Raft: Initial configuration (index=1): [{Suffrage:Voter ID:1 Address:0}]" t=2018-08-15T19:57:18+0000
lvl=info msg="Raft: Node at 0 [Leader] entering Leader state" t=2018-08-15T19:57:18+0000
lvl=info msg="LXD is socket activated" t=2018-08-15T19:57:18+0000
lvl=info msg="Starting /dev/lxd handler:" t=2018-08-15T19:57:18+0000
lvl=info msg=" - binding devlxd socket" socket=/var/lib/lxd/devlxd/sock t=2018-08-15T19:57:18+0000
lvl=info msg="REST API daemon:" t=2018-08-15T19:57:18+0000
lvl=info msg=" - binding Unix socket" socket=/var/lib/lxd/unix.socket t=2018-08-15T19:57:18+0000
lvl=info msg="Initializing global database" t=2018-08-15T19:57:18+0000
lvl=info msg="LXD 3.0.1 is starting in normal mode" path=/var/lib/lxd t=2018-08-15T20:01:17+0000
lvl=info msg="Kernel uid/gid map:" t=2018-08-15T20:01:17+0000
lvl=info msg=" - u 0 0 4294967295" t=2018-08-15T20:01:17+0000
lvl=info msg=" - g 0 0 4294967295" t=2018-08-15T20:01:17+0000
lvl=info msg="Configured LXD uid/gid map:" t=2018-08-15T20:01:17+0000
lvl=info msg=" - u 0 165536 65536" t=2018-08-15T20:01:17+0000
lvl=info msg=" - g 0 165536 65536" t=2018-08-15T20:01:17+0000
lvl=warn msg="CGroup memory swap accounting is disabled, swap limits will be ignored." t=2018-08-15T20:01:17+0000
lvl=info msg="Initializing local database" t=2018-08-15T20:01:17+0000
lvl=info msg="Initializing database gateway" t=2018-08-15T20:01:17+0000
address= id=1 lvl=info msg="Start database node" t=2018-08-15T20:01:17+0000
lvl=info msg="Raft: Restored from snapshot 1-1071-1533245019683" t=2018-08-15T20:01:17+0000
lvl=info msg="Raft: Initial configuration (index=1): [{Suffrage:Voter ID:1 Address:0}]" t=2018-08-15T20:01:17+0000
lvl=info msg="Raft: Node at 0 [Leader] entering Leader state" t=2018-08-15T20:01:17+0000
lvl=info msg="LXD is socket activated" t=2018-08-15T20:01:17+0000
lvl=info msg="Starting /dev/lxd handler:" t=2018-08-15T20:01:17+0000
lvl=info msg=" - binding devlxd socket" socket=/var/lib/lxd/devlxd/sock t=2018-08-15T20:01:17+0000
lvl=info msg="REST API daemon:" t=2018-08-15T20:01:17+0000
lvl=info msg=" - binding Unix socket" socket=/var/lib/lxd/unix.socket t=2018-08-15T20:01:17+0000
lvl=info msg="Initializing global database" t=2018-08-15T20:01:17+0000
lvl=info msg="LXD 3.0.1 is starting in normal mode" path=/var/lib/lxd t=2018-08-15T20:03:34+0000
lvl=info msg="Kernel uid/gid map:" t=2018-08-15T20:03:34+0000
lvl=info msg=" - u 0 0 4294967295" t=2018-08-15T20:03:34+0000
lvl=info msg=" - g 0 0 4294967295" t=2018-08-15T20:03:34+0000
lvl=info msg="Configured LXD uid/gid map:" t=2018-08-15T20:03:34+0000
lvl=info msg=" - u 0 165536 65536" t=2018-08-15T20:03:34+0000
lvl=info msg=" - g 0 165536 65536" t=2018-08-15T20:03:34+0000
lvl=warn msg="CGroup memory swap accounting is disabled, swap limits will be ignored." t=2018-08-15T20:03:34+0000
lvl=info msg="Initializing local database" t=2018-08-15T20:03:34+0000
lvl=info msg="Initializing database gateway" t=2018-08-15T20:03:34+0000
address= id=1 lvl=info msg="Start database node" t=2018-08-15T20:03:34+0000
lvl=info msg="Raft: Restored from snapshot 1-1071-1533245019683" t=2018-08-15T20:03:34+0000
lvl=info msg="Raft: Initial configuration (index=1): [{Suffrage:Voter ID:1 Address:0}]" t=2018-08-15T20:03:34+0000
lvl=info msg="Raft: Node at 0 [Leader] entering Leader state" t=2018-08-15T20:03:34+0000
lvl=info msg="LXD is socket activated" t=2018-08-15T20:03:34+0000
lvl=info msg="Starting /dev/lxd handler:" t=2018-08-15T20:03:34+0000
lvl=info msg=" - binding devlxd socket" socket=/var/lib/lxd/devlxd/sock t=2018-08-15T20:03:34+0000
lvl=info msg="REST API daemon:" t=2018-08-15T20:03:34+0000
lvl=info msg=" - binding Unix socket" socket=/var/lib/lxd/unix.socket t=2018-08-15T20:03:34+0000
lvl=info msg="Initializing global database" t=2018-08-15T20:03:34+0000
lvl=info msg="LXD 3.0.1 is starting in normal mode" path=/var/lib/lxd t=2018-08-15T20:16:10+0000
lvl=info msg="Kernel uid/gid map:" t=2018-08-15T20:16:10+0000
lvl=info msg=" - u 0 0 4294967295" t=2018-08-15T20:16:10+0000
lvl=info msg=" - g 0 0 4294967295" t=2018-08-15T20:16:10+0000
lvl=info msg="Configured LXD uid/gid map:" t=2018-08-15T20:16:10+0000
lvl=info msg=" - u 0 165536 65536" t=2018-08-15T20:16:10+0000
lvl=info msg=" - g 0 165536 65536" t=2018-08-15T20:16:10+0000
lvl=warn msg="CGroup memory swap accounting is disabled, swap limits will be ignored." t=2018-08-15T20:16:10+0000
lvl=info msg="Initializing local database" t=2018-08-15T20:16:10+0000
lvl=info msg="Initializing database gateway" t=2018-08-15T20:16:10+0000
address= id=1 lvl=info msg="Start database node" t=2018-08-15T20:16:10+0000
lvl=info msg="Raft: Restored from snapshot 1-1071-1533245019683" t=2018-08-15T20:16:10+0000
lvl=info msg="Raft: Initial configuration (index=1): [{Suffrage:Voter ID:1 Address:0}]" t=2018-08-15T20:16:10+0000
lvl=info msg="Raft: Node at 0 [Leader] entering Leader state" t=2018-08-15T20:16:10+0000
lvl=info msg="LXD is socket activated" t=2018-08-15T20:16:10+0000
lvl=info msg="Starting /dev/lxd handler:" t=2018-08-15T20:16:10+0000
lvl=info msg=" - binding devlxd socket" socket=/var/lib/lxd/devlxd/sock t=2018-08-15T20:16:10+0000
lvl=info msg="REST API daemon:" t=2018-08-15T20:16:10+0000
lvl=info msg=" - binding Unix socket" socket=/var/lib/lxd/unix.socket t=2018-08-15T20:16:10+0000
lvl=info msg="Initializing global database" t=2018-08-15T20:16:10+0000

[ ] Output of the client with --debug

$lxc list --debug
DBUG[08-15|13:21:30] Connecting to a local LXD over a Unix socket
DBUG[08-15|13:21:30] Sending request to LXD                   etag= method=GET url=http://unix.socket/1.0

[ ] Output of the daemon with --debug (alternatively output of lxc monitor while reproducing the issue)

lxd --debug --group lxd
DBUG[08-15|13:15:58] Connecting to a local LXD over a Unix socket
DBUG[08-15|13:15:58] Sending request to LXD                   etag= method=GET url=http://unix.socket/1.0
INFO[08-15|13:15:58] LXD 3.0.1 is starting in normal mode     path=/var/lib/lxd
INFO[08-15|13:15:58] Kernel uid/gid map:
INFO[08-15|13:15:58]  - u 0 0 4294967295
INFO[08-15|13:15:58]  - g 0 0 4294967295
INFO[08-15|13:15:58] Configured LXD uid/gid map:
INFO[08-15|13:15:58]  - u 0 165536 65536
INFO[08-15|13:15:58]  - g 0 165536 65536
WARN[08-15|13:15:58] CGroup memory swap accounting is disabled, swap limits will be ignored.
INFO[08-15|13:15:58] Initializing local database
INFO[08-15|13:15:58] Initializing database gateway
INFO[08-15|13:15:58] Start database node                      address= id=1
INFO[08-15|13:15:58] Raft: Restored from snapshot 1-1071-1533245019683
INFO[08-15|13:15:58] Raft: Initial configuration (index=1): [{Suffrage:Voter ID:1 Address:0}]
INFO[08-15|13:15:58] Raft: Node at 0 [Leader] entering Leader state
INFO[08-15|13:15:58] LXD isn't socket activated
DBUG[08-15|13:15:58] Connecting to a local LXD over a Unix socket
DBUG[08-15|13:15:58] Sending request to LXD                   etag= method=GET url=http://unix.socket/1.0
DBUG[08-15|13:15:58] Detected stale unix socket, deleting
DBUG[08-15|13:15:58] Detected stale unix socket, deleting
INFO[08-15|13:15:58] Starting /dev/lxd handler:
INFO[08-15|13:15:58]  - binding devlxd socket                 socket=/var/lib/lxd/devlxd/sock
INFO[08-15|13:15:58] REST API daemon:
INFO[08-15|13:15:58]  - binding Unix socket                   socket=/var/lib/lxd/unix.socket
INFO[08-15|13:15:58] Initializing global database
panic: txn not found
trace:
2018-08-15 13:15:58.45721: fsm: restore=1071 start
2018-08-15 13:15:58.45721: fsm: restore=1071 database size: 4096
2018-08-15 13:15:58.45722: fsm: restore=1071 wal size: 276072
2018-08-15 13:15:58.45742: fsm: restore=1071 filename: db.bin
2018-08-15 13:15:58.45742: fsm: restore=1071 transaction ID:
2018-08-15 13:15:58.45799: fsm: restore=1071 open follower: db.bin
2018-08-15 13:15:58.45895: fsm: restore=1071 done
2018-08-15 13:15:58.47392: fsm: term=1 index=1073 cmd=frames txn=1071 pages=1 commit=1 start
2018-08-15 13:15:58.47526: fsm: term=1 index=1073 cmd=frames txn=1071 pages=1 commit=1 unregister txn
2018-08-15 13:15:58.47526: fsm: term=1 index=1073 cmd=frames txn=1071 pages=1 commit=1 done
2018-08-15 13:15:58.47537: fsm: term=1 index=1074 cmd=frames txn=1073 pages=3 commit=1 start
2018-08-15 13:15:58.49150: fsm: term=1 index=1074 cmd=frames txn=1073 pages=3 commit=1 unregister txn
2018-08-15 13:15:58.49150: fsm: term=1 index=1074 cmd=frames txn=1073 pages=3 commit=1 done
2018-08-15 13:15:58.49154: fsm: term=1 index=1075 cmd=frames txn=1074 pages=10 commit=1 start
2018-08-15 13:15:58.50010: fsm: term=1 index=1075 cmd=frames txn=1074 pages=10 commit=1 unregister txn
2018-08-15 13:15:58.50010: fsm: term=1 index=1075 cmd=frames txn=1074 pages=10 commit=1 done
2018-08-15 13:15:58.50097: fsm: term=1 index=1076 cmd=frames txn=1075 pages=2 commit=1 start
2018-08-15 13:15:58.50868: fsm: term=1 index=1076 cmd=frames txn=1075 pages=2 commit=1 unregister txn
2018-08-15 13:15:58.50868: fsm: term=1 index=1076 cmd=frames txn=1075 pages=2 commit=1 done
2018-08-15 13:15:58.50871: fsm: term=1 index=1077 cmd=frames txn=1076 pages=3 commit=1 start
2018-08-15 13:15:58.51721: fsm: term=1 index=1077 cmd=frames txn=1076 pages=3 commit=1 unregister txn
2018-08-15 13:15:58.51721: fsm: term=1 index=1077 cmd=frames txn=1076 pages=3 commit=1 done
2018-08-15 13:15:58.51735: fsm: term=1 index=1078 cmd=frames txn=1077 pages=10 commit=1 start
2018-08-15 13:15:58.52593: fsm: term=1 index=1078 cmd=frames txn=1077 pages=10 commit=1 unregister txn
2018-08-15 13:15:58.52593: fsm: term=1 index=1078 cmd=frames txn=1077 pages=10 commit=1 done
2018-08-15 13:15:58.52598: fsm: term=1 index=1079 cmd=frames txn=1078 pages=2 commit=1 start
2018-08-15 13:15:58.53457: fsm: term=1 index=1079 cmd=frames txn=1078 pages=2 commit=1 unregister txn
2018-08-15 13:15:58.53458: fsm: term=1 index=1079 cmd=frames txn=1078 pages=2 commit=1 done
2018-08-15 13:15:58.53463: fsm: term=1 index=1080 cmd=frames txn=1079 pages=3 commit=1 start
2018-08-15 13:15:58.54318: fsm: term=1 index=1080 cmd=frames txn=1079 pages=3 commit=1 unregister txn
2018-08-15 13:15:58.54319: fsm: term=1 index=1080 cmd=frames txn=1079 pages=3 commit=1 done
2018-08-15 13:15:58.54330: fsm: term=1 index=1081 cmd=frames txn=1080 pages=10 commit=1 start
2018-08-15 13:15:58.55179: fsm: term=1 index=1081 cmd=frames txn=1080 pages=10 commit=1 unregister txn
2018-08-15 13:15:58.55181: fsm: term=1 index=1081 cmd=frames txn=1080 pages=10 commit=1 done
2018-08-15 13:15:58.55186: fsm: term=1 index=1082 cmd=frames txn=1081 pages=2 commit=1 start
2018-08-15 13:15:58.56016: fsm: term=1 index=1082 cmd=frames txn=1081 pages=2 commit=1 unregister txn
2018-08-15 13:15:58.56016: fsm: term=1 index=1082 cmd=frames txn=1081 pages=2 commit=1 done
2018-08-15 13:15:58.56020: fsm: term=1 index=1083 cmd=frames txn=1082 pages=3 commit=1 start
2018-08-15 13:15:58.56864: fsm: term=1 index=1083 cmd=frames txn=1082 pages=3 commit=1 unregister txn
2018-08-15 13:15:58.56864: fsm: term=1 index=1083 cmd=frames txn=1082 pages=3 commit=1 done
2018-08-15 13:15:58.56870: fsm: term=1 index=1084 cmd=frames txn=1083 pages=10 commit=1 start
2018-08-15 13:15:58.57723: fsm: term=1 index=1084 cmd=frames txn=1083 pages=10 commit=1 unregister txn
2018-08-15 13:15:58.57723: fsm: term=1 index=1084 cmd=frames txn=1083 pages=10 commit=1 done
2018-08-15 13:15:58.57726: fsm: term=1 index=1085 cmd=frames txn=1084 pages=2 commit=1 start
2018-08-15 13:15:58.58581: fsm: term=1 index=1085 cmd=frames txn=1084 pages=2 commit=1 unregister txn
2018-08-15 13:15:58.58581: fsm: term=1 index=1085 cmd=frames txn=1084 pages=2 commit=1 done
2018-08-15 13:15:58.58585: fsm: term=1 index=1086 cmd=frames txn=1085 pages=3 commit=1 start
2018-08-15 13:15:58.59429: fsm: term=1 index=1086 cmd=frames txn=1085 pages=3 commit=1 unregister txn
2018-08-15 13:15:58.59429: fsm: term=1 index=1086 cmd=frames txn=1085 pages=3 commit=1 done
2018-08-15 13:15:58.59437: fsm: term=1 index=1087 cmd=frames txn=1086 pages=14 commit=1 start
2018-08-15 13:15:58.60288: fsm: term=1 index=1087 cmd=frames txn=1086 pages=14 commit=1 unregister txn
2018-08-15 13:15:58.60289: fsm: term=1 index=1087 cmd=frames txn=1086 pages=14 commit=1 done
2018-08-15 13:15:58.60295: fsm: term=1 index=1088 cmd=frames txn=1087 pages=3 commit=1 start
2018-08-15 13:15:58.61143: fsm: term=1 index=1088 cmd=frames txn=1087 pages=3 commit=1 unregister txn
2018-08-15 13:15:58.61143: fsm: term=1 index=1088 cmd=frames txn=1087 pages=3 commit=1 done
2018-08-15 13:15:58.61151: fsm: term=1 index=1089 cmd=frames txn=1088 pages=14 commit=1 start
2018-08-15 13:15:58.62006: fsm: term=1 index=1089 cmd=frames txn=1088 pages=14 commit=1 unregister txn
2018-08-15 13:15:58.62007: fsm: term=1 index=1089 cmd=frames txn=1088 pages=14 commit=1 done
2018-08-15 13:15:58.62062: fsm: term=1 index=1090 cmd=frames txn=1089 pages=10 commit=1 start
2018-08-15 13:15:58.62877: fsm: term=1 index=1090 cmd=frames txn=1089 pages=10 commit=1 unregister txn
2018-08-15 13:15:58.62877: fsm: term=1 index=1090 cmd=frames txn=1089 pages=10 commit=1 done
2018-08-15 13:15:58.62883: fsm: term=1 index=1091 cmd=frames txn=1090 pages=10 commit=1 start
2018-08-15 13:15:58.63739: fsm: term=1 index=1091 cmd=frames txn=1090 pages=10 commit=1 unregister txn
2018-08-15 13:15:58.63739: fsm: term=1 index=1091 cmd=frames txn=1090 pages=10 commit=1 done
2018-08-15 13:15:58.63742: fsm: term=1 index=1092 cmd=frames txn=1091 pages=2 commit=1 start
2018-08-15 13:15:58.64610: fsm: term=1 index=1092 cmd=frames txn=1091 pages=2 commit=1 unregister txn
2018-08-15 13:15:58.64610: fsm: term=1 index=1092 cmd=frames txn=1091 pages=2 commit=1 done
2018-08-15 13:15:58.64615: fsm: term=1 index=1093 cmd=frames txn=1092 pages=3 commit=1 start
2018-08-15 13:15:58.65466: fsm: term=1 index=1093 cmd=frames txn=1092 pages=3 commit=1 unregister txn
2018-08-15 13:15:58.65466: fsm: term=1 index=1093 cmd=frames txn=1092 pages=3 commit=1 done
2018-08-15 13:15:58.65473: fsm: term=1 index=1094 cmd=frames txn=1093 pages=10 commit=1 start
2018-08-15 13:15:58.66315: fsm: term=1 index=1094 cmd=frames txn=1093 pages=10 commit=1 unregister txn
2018-08-15 13:15:58.66316: fsm: term=1 index=1094 cmd=frames txn=1093 pages=10 commit=1 done
2018-08-15 13:15:58.66318: fsm: term=1 index=1095 cmd=frames txn=1094 pages=2 commit=1 start
2018-08-15 13:15:58.67171: fsm: term=1 index=1095 cmd=frames txn=1094 pages=2 commit=1 unregister txn
2018-08-15 13:15:58.67171: fsm: term=1 index=1095 cmd=frames txn=1094 pages=2 commit=1 done
2018-08-15 13:15:58.67173: fsm: term=1 index=1096 cmd=frames txn=1095 pages=3 commit=1 start
2018-08-15 13:15:58.68019: fsm: term=1 index=1096 cmd=frames txn=1095 pages=3 commit=1 unregister txn
2018-08-15 13:15:58.68019: fsm: term=1 index=1096 cmd=frames txn=1095 pages=3 commit=1 done
2018-08-15 13:15:58.68023: fsm: term=1 index=1097 cmd=frames txn=1096 pages=10 commit=1 start
2018-08-15 13:15:58.68874: fsm: term=1 index=1097 cmd=frames txn=1096 pages=10 commit=1 unregister txn
2018-08-15 13:15:58.68874: fsm: term=1 index=1097 cmd=frames txn=1096 pages=10 commit=1 done
2018-08-15 13:15:58.68876: fsm: term=1 index=1098 cmd=frames txn=1097 pages=1 commit=1 start
2018-08-15 13:15:58.69729: fsm: term=1 index=1098 cmd=frames txn=1097 pages=1 commit=1 unregister txn
2018-08-15 13:15:58.69729: fsm: term=1 index=1098 cmd=frames txn=1097 pages=1 commit=1 done
2018-08-15 13:15:58.69732: fsm: term=1 index=1099 cmd=frames txn=1098 pages=3 commit=1 start
2018-08-15 13:15:58.70597: fsm: term=1 index=1099 cmd=frames txn=1098 pages=3 commit=1 unregister txn
2018-08-15 13:15:58.70597: fsm: term=1 index=1099 cmd=frames txn=1098 pages=3 commit=1 done
2018-08-15 13:15:58.70601: fsm: term=1 index=1100 cmd=frames txn=1099 pages=2 commit=1 start
2018-08-15 13:15:58.71459: fsm: term=1 index=1100 cmd=frames txn=1099 pages=2 commit=1 unregister txn
2018-08-15 13:15:58.71459: fsm: term=1 index=1100 cmd=frames txn=1099 pages=2 commit=1 done
2018-08-15 13:15:58.71462: fsm: term=1 index=1101 cmd=frames txn=1100 pages=3 commit=1 start
2018-08-15 13:15:58.72312: fsm: term=1 index=1101 cmd=frames txn=1100 pages=3 commit=1 unregister txn
2018-08-15 13:15:58.72312: fsm: term=1 index=1101 cmd=frames txn=1100 pages=3 commit=1 done
2018-08-15 13:15:58.72314: fsm: term=1 index=1102 cmd=undo txn=1100 start

[ ] Output of zdb -l /var/lib/lxd/disks/default.img

LABEL 0
version: 5000
name: 'default'
state: 0
txg: 1239752
pool_guid: 10968228108043133148
errata: 0
hostname: 'hostname.host'
top_guid: 9490801720776843116
guid: 9490801720776843116
vdev_children: 1
vdev_tree:
    type: 'file'
    id: 0
    guid: 9490801720776843116
    path: '/var/lib/lxd/disks/default.img'
    metaslab_array: 256
    metaslab_shift: 28
    ashift: 9
    asize: 33281277952
    is_log: 0
    DTL: 137
    create_txg: 4
features_for_read:
    com.delphix:hole_birth
    com.delphix:embedded_data
labels = 0 1 2 3

/var/lib/lxd/database# zdb -l /var/lib/lxd/zfs.tmp
LABEL 0
version: 5000
name: 'zfspool2'
state: 0
txg: 2837996
pool_guid: 14790703948577340340
errata: 0
hostname: 'hostname.host'
top_guid: 10360267484302053565
guid: 10360267484302053565
vdev_children: 1
vdev_tree:
    type: 'file'
    id: 0
    guid: 10360267484302053565
    path: '/var/lib/lxd/zfs.tmp'
    metaslab_array: 256
    metaslab_shift: 28
    ashift: 9
    asize: 107369463808
    is_log: 0
    DTL: 4
    create_txg: 4
features_for_read:
    com.delphix:hole_birth
    com.delphix:embedded_data
labels = 0 1 2 3

Looks like your database got corrupted somehow, can you send me a tarball of /var/lib/lxd/database to stgraber at ubuntu dot com and I'll have @freeekanayaka take a look and send you a fixed database assuming it's not too badly damaged.

Thank you very much for the quick response. I have emailed you a database.tar.gz file. I am very to get this server back online!

Forwarded to @freeekanayaka, he should be able to get back to you tomorrow.

@bensig I've looked to your database and it's corrupted in a way I haven't seen before. I think I can recover from the latest db snapshot (dated Aug 14 17:45), but any state change you might have done between the snapshot date and the crash will be lost.

@bensig looking again at the database tarball you sent by email (md5sum bee99517beeb9dea4366f8a9dcf545d7), it seems the database does not match the output of lxd --debug --group lxd that you pasted.
Did something happen between the time you ran lxd --debug --group lxd and the time you made the tarball of the database? Are you able to reproduce the crash if you run again lxd --debug --group lxd (you pretty much should if the files under database/ did not change) ?

@bensig

authors: bensig freeekanayaka stgraber


text:
Any plans to support older browsers?

The README doesn't explicitly state this as a feature, but are there any plans to support old browsers? For example, on old iOS Safari (9.3.5), I found that the hamburger dropdown doesn't work at all.
EDIT: For some reason this submitted as a blank issue, sorry! I think it's because I clicked on the "New Issue" button while not logged in and it skips the issue chooser screen.

@ericswpark No, this is not a priority currently.

authors: ericswpark lxndrblz

repo: lxndrblz/anatole


text:
Cartography doesn't works Neo4j 4.4 - EOF occurred in violation of protocol (_ssl.c:1129)

Title:
neobolt.exceptions.SecurityError: Failed to establish secure connection to 'EOF occurred in violation of protocol (_ssl.c:1129)'
Description:
I'm trying to install Cartography, but I had some problems in the installation process.
To Reproduce:

pip install cartography
cartography --neo4j-uri bolt://localhost:7687

Logs:

┌──(thor㉿research)-[~]
└─$ cartography --neo4j-uri bolt://localhost:7687                                                                                1 ⨯
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/neobolt/direct.py", line 854, in _secure
s = ssl_context.wrap_socket(s, server_hostname=host if HAS_SNI and host else None)
File "/usr/lib/python3.9/ssl.py", line 500, in wrap_socket
return self.sslsocket_class._create(
File "/usr/lib/python3.9/ssl.py", line 1040, in _create
self.do_handshake()
File "/usr/lib/python3.9/ssl.py", line 1309, in do_handshake
self._sslobj.do_handshake()
ssl.SSLEOFError: EOF occurred in violation of protocol (_ssl.c:1129)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/usr/local/bin/cartography", line 8, in
sys.exit(main())
File "/usr/local/lib/python3.9/dist-packages/cartography/cli.py", line 464, in main
return CLI(default_sync, prog='cartography').main(argv)
File "/usr/local/lib/python3.9/dist-packages/cartography/cli.py", line 444, in main
return cartography.sync.run_with_config(self.sync, config)
File "/usr/local/lib/python3.9/dist-packages/cartography/sync.py", line 111, in run_with_config
neo4j_driver = GraphDatabase.driver(
File "/usr/local/lib/python3.9/dist-packages/neo4j/init.py", line 120, in driver
return Driver(uri, **config)
File "/usr/local/lib/python3.9/dist-packages/neo4j/init.py", line 161, in new
return subclass(uri, **config)
File "/usr/local/lib/python3.9/dist-packages/neo4j/init.py", line 235, in new
pool.release(pool.acquire())
File "/usr/lib/python3/dist-packages/neobolt/direct.py", line 715, in acquire
return self.acquire_direct(self.address)
File "/usr/lib/python3/dist-packages/neobolt/direct.py", line 608, in acquire_direct
connection = self.connector(address, error_handler=self.connection_error_handler)
File "/usr/local/lib/python3.9/dist-packages/neo4j/init.py", line 232, in connector
return connect(address, **dict(config, **kwargs))
File "/usr/lib/python3/dist-packages/neobolt/direct.py", line 972, in connect
raise last_error
File "/usr/lib/python3/dist-packages/neobolt/direct.py", line 963, in connect
s, der_encoded_server_certificate = _secure(s, host, security_plan.ssl_context, **config)
File "/usr/lib/python3/dist-packages/neobolt/direct.py", line 859, in _secure
raise error
neobolt.exceptions.SecurityError: Failed to establish secure connection to 'EOF occurred in violation of protocol (_ssl.c:1129)'

Screenshots:

Please complete the following information::

Cartography release version or commit hash [Latest version installed]
Python version: Python 3.9.10
neo4j 4.4.2
Linux research 5.16.0-kali5-amd64 Debian 5.16.14-1kali1 (2022-03-15) x86_64 GNU/Linux

*Other Logs:

┌──(thor㉿research)-[~]
└─$ cartography -v
DEBUG:cartography.cli:Launching cartography with CLI configuration: {'verbose': True, 'quiet': False, 'neo4j_uri': 'bolt://localhost:7687', 'neo4j_user': None, 'neo4j_password_env_var': None, 'neo4j_password_prompt': False, 'neo4j_max_connection_lifetime': 3600, 'update_tag': None, 'aws_sync_all_profiles': False, 'azure_sync_all_subscriptions': False, 'azure_sp_auth': False, 'azure_tenant_id': None, 'azure_client_id': None, 'azure_client_secret_env_var': None, 'aws_requested_syncs': None, 'crxcavator_api_base_uri': 'https://api.crxcavator.io/v1', 'crxcavator_api_key_env_var': None, 'analysis_job_directory': None, 'okta_org_id': None, 'okta_api_key_env_var': None, 'okta_saml_role_regex': '^aws\#\S+\#(?{{role}}[\w\-]+)\#(?{{accountid}}\d+)$', 'github_config_env_var': None, 'digitalocean_token_env_var': None, 'permission_relationships_file': 'cartography/data/permission_relationships.yaml', 'jamf_base_uri': None, 'jamf_user': None, 'jamf_password_env_var': None, 'k8s_kubeconfig': None, 'statsd_enabled': False, 'statsd_prefix': '', 'statsd_host': '127.0.0.1', 'statsd_port': 8125, 'pagerduty_api_key_env_var': None}
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/neobolt/direct.py", line 854, in _secure
s = ssl_context.wrap_socket(s, server_hostname=host if HAS_SNI and host else None)
File "/usr/lib/python3.9/ssl.py", line 500, in wrap_socket
return self.sslsocket_class._create(
File "/usr/lib/python3.9/ssl.py", line 1040, in _create
self.do_handshake()
File "/usr/lib/python3.9/ssl.py", line 1309, in do_handshake
self._sslobj.do_handshake()
ssl.SSLEOFError: EOF occurred in violation of protocol (_ssl.c:1129)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/usr/local/bin/cartography", line 8, in
sys.exit(main())
File "/usr/local/lib/python3.9/dist-packages/cartography/cli.py", line 464, in main
return CLI(default_sync, prog='cartography').main(argv)
File "/usr/local/lib/python3.9/dist-packages/cartography/cli.py", line 444, in main
return cartography.sync.run_with_config(self.sync, config)
File "/usr/local/lib/python3.9/dist-packages/cartography/sync.py", line 111, in run_with_config
neo4j_driver = GraphDatabase.driver(
File "/usr/local/lib/python3.9/dist-packages/neo4j/init.py", line 120, in driver
return Driver(uri, **config)
File "/usr/local/lib/python3.9/dist-packages/neo4j/init.py", line 161, in new
return subclass(uri, **config)
File "/usr/local/lib/python3.9/dist-packages/neo4j/init.py", line 235, in new
pool.release(pool.acquire())
File "/usr/lib/python3/dist-packages/neobolt/direct.py", line 715, in acquire
return self.acquire_direct(self.address)
File "/usr/lib/python3/dist-packages/neobolt/direct.py", line 608, in acquire_direct
connection = self.connector(address, error_handler=self.connection_error_handler)
File "/usr/local/lib/python3.9/dist-packages/neo4j/init.py", line 232, in connector
return connect(address, **dict(config, **kwargs))
File "/usr/lib/python3/dist-packages/neobolt/direct.py", line 972, in connect
raise last_error
File "/usr/lib/python3/dist-packages/neobolt/direct.py", line 963, in connect
s, der_encoded_server_certificate = _secure(s, host, security_plan.ssl_context, **config)
File "/usr/lib/python3/dist-packages/neobolt/direct.py", line 859, in _secure
raise error
neobolt.exceptions.SecurityError: Failed to establish secure connection to 'EOF occurred in violation of protocol (_ssl.c:1129)'

I am also facings errors while trying to use cartography with Neo4j 4.4.4 (which is the latest available at this time) . I am not trying to use secure or SSL connection , but I feel the basic problem may be same
cartography -v --neo4j-uri bolt://localhost:7687
DEBUG:cartography.cli:Launching cartography with CLI configuration: {'verbose': True, 'quiet': False, 'neo4j_uri': 'bolt://localhost:7687', 'neo4j_user': None, 'neo4j_password_env_var': None, 'neo4j_password_prompt': False, 'neo4j_max_connection_lifetime': 3600, 'update_tag': None, 'aws_sync_all_profiles': False, 'azure_sync_all_subscriptions': False, 'azure_sp_auth': False, 'azure_tenant_id': None, 'azure_client_id': None, 'azure_client_secret_env_var': None, 'aws_requested_syncs': None, 'crxcavator_api_base_uri': 'https://api.crxcavator.io/v1', 'crxcavator_api_key_env_var': None, 'analysis_job_directory': None, 'okta_org_id': None, 'okta_api_key_env_var': None, 'okta_saml_role_regex': '^aws\\#\\S+\\#(?{{role}}[\\w\\-]+)\\#(?{{accountid}}\\d+)$', 'github_config_env_var': None, 'digitalocean_token_env_var': None, 'permission_relationships_file': 'cartography/data/permission_relationships.yaml', 'jamf_base_uri': None, 'jamf_user': None, 'jamf_password_env_var': None, 'k8s_kubeconfig': None, 'statsd_enabled': False, 'statsd_prefix': '', 'statsd_host': '127.0.0.1', 'statsd_port': 8125, 'pagerduty_api_key_env_var': None}
DEBUG:cartography.sync:Error occurred during Neo4j connect.
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/neobolt/direct.py", line 831, in _connect
    s.connect(resolved_address)
ConnectionRefusedError: [Errno 61] Connection refused

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/cartography/sync.py", line 111, in run_with_config
    neo4j_driver = GraphDatabase.driver(
  File "/usr/local/lib/python3.9/site-packages/neo4j/__init__.py", line 120, in driver
    return Driver(uri, **config)
  File "/usr/local/lib/python3.9/site-packages/neo4j/__init__.py", line 161, in __new__
    return subclass(uri, **config)
  File "/usr/local/lib/python3.9/site-packages/neo4j/__init__.py", line 235, in __new__
    pool.release(pool.acquire())
  File "/usr/local/lib/python3.9/site-packages/neobolt/direct.py", line 715, in acquire
    return self.acquire_direct(self.address)
  File "/usr/local/lib/python3.9/site-packages/neobolt/direct.py", line 608, in acquire_direct
    connection = self.connector(address, error_handler=self.connection_error_handler)
  File "/usr/local/lib/python3.9/site-packages/neo4j/__init__.py", line 232, in connector
    return connect(address, **dict(config, **kwargs))
  File "/usr/local/lib/python3.9/site-packages/neobolt/direct.py", line 972, in connect
    raise last_error
  File "/usr/local/lib/python3.9/site-packages/neobolt/direct.py", line 962, in connect
    s = _connect(resolved_address, **config)
  File "/usr/local/lib/python3.9/site-packages/neobolt/direct.py", line 843, in _connect
    raise ServiceUnavailable("Failed to establish connection to {!r} (reason {})".format(resolved_address, error))
neobolt.exceptions.ServiceUnavailable: Failed to establish connection to ('::1', 7687, 0, 0) (reason [Errno 61] Connection refused)
ERROR:cartography.sync:Unable to connect to Neo4j using the provided URI 'bolt://localhost:7687', an error occurred: 'Failed to establish connection to ('::1', 7687, 0, 0) (reason [Errno 61] Connection refused)'. Make sure the Neo4j server is running and accessible from your network.

I tried the solution proposed on this page
https://community.neo4j.com/t/cant-connect-neo4j-4-0-through-bolt-api/18726/3
If I try to connect through python code directly as mentioned on the above page, I get the same error that cartography tool throws. With the encrypted=false option in the python code, the error goes away. Not sure how to set the encrypted parameter

Hi, Cartography doesn't support Neo4j 4.x (yet).
Migration is happening here: https://github.com/lyft/cartography/pull/521

authors: filipi86 marco-lancini udsnap

repo: lyft/cartography


text:
Why some photos are rotated?

Details: https://vimeo.com/user106988912/review/381883062/37aede9681

Can you explain and describe the issue in more detail? Video cannot be played

Photos added in portrait mode, after cutting to 1: 1 ratio, they rotate.

The image is flipped upside down when cropped on an Android 10 operating system (Galaxy Note 10+) device.
There are a lot of Android 10 devices these days. It must be resolved.

Checks for 180 degrees solved the issue (ImageCropPlugin.java)
int getHeight() {     return (isFlippedDimensions() && degrees != 180) ? width : height; } int getWidth() {     return (isFlippedDimensions() && degrees != 180) ? height : width; } boolean isFlippedDimensions() {     return degrees == 90 || degrees == 270 || degrees == 180; }

Any updates?
iPhone 11 Pro Max, rotation bug on portrait selfie photo. Latest version (0.3.4)


text:
Add handling for real TLS Certificate

Currently, while there is some support for using your own cert, there's no built way to actually get that cert/key into the container.  Need to plumb that up.

Fixed in 8374d63905ef84b45ed0eb12792f84e787f613b7

repo: lykinsbd/naas


text:
docs(sbb-datepicker): improve docs on how to use format and dateParser functions

Preflight Checklist

[x] I have read the Contributing Guidelines for this project.
[x] I agree to follow the Code of Conduct that this project adheres to.
[x] I have searched the pull request tracker for a Pull Request (PR) that matches the one I want to submit, without success.

Issue
This PR Closes #
Pull request checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been reviewed and added / updated if needed (for bug fixes / features)

See Review Guidelines for more information what is checked during review process.
Changes
Changes in this pull request:

Improve docs on datepicker

Browsers
I tested the build on the following browsers:

[ ] Firefox Desktop
[ ] Chrome Desktop
[ ] Edge Desktop
[ ] Safari Desktop
[ ] Chrome Mobile
[ ] Safari Mobile

Screen readers
I tested the build on the following browsers:

[ ] JAWS Firefox Desktop
[ ] JAWS Chrome Desktop
[ ] NVDA Firefox Desktop
[ ] NVDA Chrome Desktop
[ ] VoiceOver Safari Desktop
[ ] VoiceOver Chrome Desktop
[ ] VoiceOver Safari Mobile
[ ] Android Accessibility Suite Chrome Mobile

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[] Documentation content changes
[ ] Other (please describe):

Does this introduce a breaking change?

[ ] Yes
[x] No

Other information

Codecov Report

Merging #1914 (b2671c5) into master (ab917b0) will decrease coverage by 17.20%.
Report is 1511 commits behind head on master.
The diff coverage is 31.20%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@             Coverage Diff             @@
##           master    #1914       +/-   ##
===========================================
- Coverage   54.85%   37.65%   -17.20%
===========================================
  Files          49      268      +219
  Lines        1659     9682     +8023
  Branches      406     2100     +1694
===========================================
+ Hits          910     3646     +2736
- Misses        671     5804     +5133
- Partials       78      232      +154

Files Changed
Coverage Δ

...ts/sbb-accordion-item/sbb-accordion-item.events.ts
100.00% <ø> (ø)

.../sbb-accordion-item/sbb-accordion-item.stories.tsx
0.00% <0.00%> (ø)

...mponents/sbb-accordion-item/sbb-accordion-item.tsx
0.00% <0.00%> (-37.21%)
:arrow_down:

...components/sbb-accordion/sbb-accordion.stories.tsx
0.00% <0.00%> (ø)

...ents/sbb-action-group/sbb-action-group.stories.tsx
0.00% <0.00%> (ø)

...onents/sbb-alert-group/sbb-alert-group.stories.tsx
0.00% <0.00%> (ø)

src/components/sbb-alert/sbb-alert.stories.tsx
0.00% <0.00%> (ø)

...onents/sbb-autocomplete/sbb-autocomplete.events.ts
100.00% <ø> (ø)

...ents/sbb-autocomplete/sbb-autocomplete.stories.tsx
0.00% <0.00%> (ø)

...-breadcrumb-group/sbb-breadcrumb-group.stories.tsx
0.00% <0.00%> (ø)

... and 57 more

... and 216 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

authors: MarioCastigliano codecov-commenter

repo: lyne-design-system/lyne-components


text:
Limited number of devices

@booleanbetrayal, I'm happy to show you my PR. My intention is to allow users to configure the max number of allowed devices. In my API, for example, I don't want concurrent devices, so I'll set max_number_of_clients = 1. In tipical applications, however, I think 10 is a reasonable value.
Using this configuration we can also avoid the max length problem in database and eventually a DoS attack.
Please take a look and tell me what you think.

@paulosoares86 - haven't gotten to play with it, but the code looks good. could you add some tests that show the tokens queue gets cycled as expected? A rebase with squashed commits would be ideal. Thanks!

No problem, @booleanbetrayal. I've changed the parameter name, included some tests and a short description of parameter in readme.
You are welcome!

Hey @paulosoares86 - I'm seeing all sorts of merge commits and duplicated commits. If you're unable to squash those in a rebase, maybe just creating a new branch for the PR and applying your patch? Would like for you to get the credit if this gets into master, but would like to keep the commit history clean.

I'm sorry, @ booleanbetrayal. I've made a rebase, but it seems better to make another branch with only one commit.

@paulosoares86 - Whatever's easiest! Just let me know if you open up a new PR.

license: WTFPL


text:
可以提供一个demo么？

比如“发布商品”接口应该怎么调用？

$client = new AlibabaCross();
$request = new CategoryGetParams($cid);
//如果有其他参数
//$request->字段 = 值
$client->category->categoryGet($request)->get();//或者->post();
------------------ 原始邮件 ------------------
发件人:                                                                                "lysily1314/alibaba1688"                                                                                <notifications@github.com>;
发送时间: 2021年3月6日(星期六) 中午1:52
收件人: "lysily1314/alibaba1688"<alibaba1688@noreply.github.com>;
抄送: "Subscribed"<subscribed@noreply.github.com>;
主题: Re: [lysily1314/alibaba1688] 可以提供一个demo么？ (#1)
Closed #1.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


text:
解决方案检查

[X] 我已阅读常见问题(https://lyswhut.github.io/lx-music-doc/desktop/faq)，但没有找到解决方案
[X] 我已搜索issue列表(https://github.com/lyswhut/lx-music-desktop/issues?utf8=✓&q=)，但没有发现类似的问题

问题描述
希望可以增加点击歌手或者歌名跳转到搜索，这个功能其实还是挺好用，比如我经常会听到一首歌我就想搜索下这个歌手唱的歌，也有听到一首歌想听别人唱的时候。
描述你想要的解决方案
点击歌曲名、歌手名、专辑名跳转到搜索。
描述你考虑过的替代方案
No response
附加信息
No response

想要+1

repo: lyswhut/lx-music-desktop


text:
使用RT-DETR导出的onnx模型进行推理遇到问题

您好，我使用focalNet作为RT-DETR的backbone进行目标检测的训练，效果还是挺好的，然后我把best_model.pdparams转换成onnx进行推理（使用deploy/third_engine/onnx/infer.py）时，遇到两个问题：
（1）有没有使用GPU进行推理的代码，我自己改的遇到点问题；
（2）我增加了RT-DETR的两个head，使其增加两个分类和回归任务，同时更改相应代码，在tools/infer.py的推理结果可以输出我新增head的结果，但是用deploy/third_engine/onnx/infer.py推理时，只输出类别，score，xmin, ymin, xmax, ymax六个值，无法输出我新增head的结果，怀疑预测结果只取前6维，请问怎么可以输出全部的预测结果呢？
感恩~

问题已经解决。

repo: lyuwenyu/RT-DETR


text:
Type error introduced by Collections.emptyMap

   private Set<Node> getNeighborNodes(Node node, final Map<Node, Map<Node, EdgeInfo>> edges) {
     final Map<Node, EdgeInfo> neighborEdges = edges.get(node);

     if (neighborEdges == null) {
-      return Collections.EMPTY_MAP.keySet();
+      return Collections.emptyMap().keySet();
     }

     return neighborEdges.keySet();
   }

Blocks https://github.com/lyxell/logifix/pull/90

Fixed in #90

repo: lyxell/logifix


text:
Mention bindings in the README

Python bindings at https://github.com/dimkr/pylzfse

Done. Thanks for providing the Python bindings.

FWIW, since there is a plugin for Squash there are also bindings for the languages which have Squash bindings.  Hopefully that list will grow soon…

authors: dimkr ebainville nemequ

repo: lzfse/lzfse


text:
Just Started getting these JSON Parsing Errors

Screenshot of logs:

erased my volume and started from scratch


text:
Fix unable to load 'Dimensions' package

In ReactNative v0.23 the package 'Dimensions' is not found.

Thanks!


text:
Text size based on size class

In one of my VC's that I am displaying with MZFormSheetPresentationController, I have a label whose font is based on the devices size class. However, when the form sheet is displayed the font size does not change based on the content size of the form sheet. How can I change this?

This will be soon fixed, on develop i have new version of MZFormSheetPresentationController, which will be released.

Fixed in MZFormSheetPresentationController 2.0.0.


text:
Fix preview permissions

[ ] Closes #xxxx
[ ] New notebooks are added to _toc.yml and show up properly in website preview.

https://github.com/peaceiris/actions-gh-pages/issues/1069

@jbusecke could we merge this and check if adding permissions and GitHub token as a secret helps?

@LaureZanna could you merge this? it needs trial and error as ive not gotten a response from the authors of the workflow

authors: IamShubhamGupto jbusecke


text:
Verify PDF Digital certificate

Hi,
I aim to check if there is a digital signature in a pdf. Inspired by the method in pdf-verify.py, some PDFs work for me, but others don't. I have this assertion error:
assert n != -1 and start != -1 and stop != -1
All this three are -1, because n = pdfdata.find(b"/ByteRange") and ByteRange is not in the bytes of the PDFs.
How can I solve? I just need to check if the pdf has a digital signature. Thank you.

If there is no object in the file:
/Type /Signal
/Filter /Adobe.PPKLite
/SubFilter /adbe.pkcs7.detached
/ByteRange [int int int int]
/Contents <....
This means for endesive that the file is unsigned. Endesive only knows one way to sign a PDF

This means for endesive that the file is unsigned. Endesive only knows one way to sign a PDF

Are there other methods to recognize if a pdf has a digital signature? Thanks

I wrote endesive with this document in mind:
https://www.adobe.com/devnet-docs/etk_deprecated/tools/DigSig/Acrobat_DigitalSignatures_in_PDF.pdf
Now it is deprecated :(


text:
Update README.md Add ESP32-S3 Board

M5STAMPS3
M5Dial
M5Capsule
M5Cardputer

プルリクエスト ありがとうございます！助かります!


text:
Video is no longer playing

Is it related to Chrome updated? The video on the demo page isn't working either: http://m90.github.io/seeThru/moving-alpha/

Yeah, console says so:
Uncaught (in promise) DOMException: play() failed because the user didn't interact with the document first. https://goo.gl/xX8pDD

I recently encountered the same issue when updating the automated tests for this script and has to start Chrome using --autoplay-policy=no-user-gesture-required, see: https://github.com/m90/seeThru/blob/2c43f32c364f59fa584d2811484f099dd689ffb1/karma.conf.js#L62-L67
Unfortunately I am not sure what seeThru can do about this other than warn users in README and demos. Do you have any other idea about where to start?

I released v4.0.0 with removed "autoplay" features, so the caller is now responsible for handling behavior like this (and can thus use approaches like described above).


text:
System to select which Locales to actually bundle

Probably need to convert the WalkingkookaAllLocalesCodeGeneratorTool so it is run from an annotation processor which checks a system property to filter desired Locales.

Closed by https://github.com/mP1/j2cl-locale/issues/6


text:
refactor: Move util methods out of persistence

Instructions

PR target branch should be against development
PR title name should follow this format: https://github.com/mParticle/mparticle-workflows/blob/main/.github/workflows/pr-title-check.yml
PR branch prefix should follow this format: https://github.com/mParticle/mparticle-workflows/blob/main/.github/workflows/pr-branch-check-name.yml

Summary

Move Persistence string functions into utilities module

Testing Plan

[x] Was this tested locally? If not, explain why.
Run automated tests
Manually test SDK

Reference Issue (For mParticle employees only.  Ignore if you are an outside contributor)

Closes https://go.mparticle.com/work/SQDSDKS-5338

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: alexs-mparticle mparticle-automation

repo: mParticle/mparticle-web-sdk


text:
Standalone property to trigger the loading event

Thank you, it worked!
I hope if you can provide a standalone property to trigger the loading event, I think this will be much better :")
Originally posted by @OmarYehiaDev in https://github.com/ma7moud3osman/easy_stepper/issues/4#issuecomment-1425791323

I've added a PR#6 for this feature :")
I've tested it but you can do more tests and just merge it when everything's ready for the new release :")

Added in v.0.3.2 , thanks to Omar Yehia  PR#6


text:
Add R.info for static typing Info.plist

The Info.plist file contains data that is sometimes needed at runtime. In particular, for Siri Shortcuts, I'm interested in the NSUserActivityTypes array.
We should add a top level R.info object, that includes relevant fields like userActivityTypes, but also things like applicationShortcutItems, as mentioned in https://github.com/mac-cain13/R.swift/issues/82
Example usage:
let myOrder: String = R.info.userActivityTypes.comMyAppViewOrder
let barcodeScanner: String = R.info.applicationShortcutItems.comMyAppBarcodeScanner.title

Found this list of keys that you can have in a plist, could be a good starting point: https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Introduction/Introduction.html
Apple states it's not up to date, but I see keys stated as iOS 11.0 and later. So it doesn't seem that outdated yet...

Just noticed that what file will be used as the Info.plist is a build setting. So you can use another plist in debug or release for example. That would make it a bit harder to do this right, we should think about that.


text:
Pyro compatibility

For context, see: https://github.com/mackelab/sbi/pull/288, https://github.com/mackelab/sbi/issues/286
While the bug was fixed in Pyro, no new Pyro version has been released yet. This PR explicitly passes transforms={} to Pyro, which allows using 1.4.0.

Codecov Report

Merging #339 into main will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #339   +/-   ##
=======================================
  Coverage   73.62%   73.62%
=======================================
  Files          48       48
  Lines        2684     2684
=======================================
  Hits         1976     1976
  Misses        708      708

Flag
Coverage Δ

#unittests
73.62% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

sbi/inference/posteriors/base_posterior.py
66.83% <ø> (ø)

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 a4c1f2a...8cacba6. Read the comment docs.

authors: codecov-commenter jan-matthis

repo: mackelab/sbi


text:
Feature : Linear Composites

Implemented feature req. in Issue https://github.com/macrosynergy/macrosynergy/issues/638 (Linear Composites function)

Codecov Report
Base: 59.03% // Head: 58.11% // Decreases project coverage by -0.92% :warning:

Coverage data is based on head (d98ad53) compared to base (5724b92).
Patch coverage: 0.00% of modified lines in pull request are covered.

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

Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #639      +/-   ##
===========================================
- Coverage    59.03%   58.11%   -0.92%
===========================================
  Files           28       29       +1
  Lines         2990     3037      +47
===========================================
  Hits          1765     1765
- Misses        1225     1272      +47

Impacted Files
Coverage Δ

macrosynergy/panel/linear_composite.py
0.00% <0.00%> (ø)

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.

repo: macrosynergy/macrosynergy


text:
Curie icon ideas

It would be good to have a more distinctive icon for Currie. At first I have not noticed it is even running, because it looks like this for me:

Thank you @piotrwach, good point. Interesting, I wasn't aware of this behaviour. I always saw terminal-like icon, but I guess since the app does not have its own icon, NSApplication inherits the icon from the parent process. I will try to prepare and set an icon in the next few weeks.

Resolving. @piotrwach, hope you will like the new icon.

The new icon looks great! Thanks!

authors: marciniwanicki piotrwach

repo: macvmio/curie