text:
🛑 Nextcloud is down

In 9492492, Nextcloud (https://nextcloud.0121.org) was down:

HTTP code: 502
Response time: 401 ms

Resolved: Nextcloud is back up in c2e8749 after 22 minutes.

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
有人用这个脚本抢到了吗

如题
似乎平常运行正常，早上运行的时候会报错

暂时没抢到

抢了快一个星期都没抢到，我觉得程序是好的，能准时启动。但问题是感觉系统和某些牛牛可能有合作，名额早就被锁死，就连市面上的普通牛牛都抢不到。

@01miaom 你好, 请问之前有成功抢到过吗?

@01miaom 你好, 请问之前有成功抢到过吗?

是的，2月初要相对容易一些，在一分钟内完成预约就行。现在可能连黄牛都抢不到。

昨天就差验证码输入的慢了点，今天进去就无了 有人一起来研究他的api么？我这已经抓到一些api了 可以跳过两步操作直接到确定页面

留个联系方式我们可以一起研究呀

昨天就差验证码输入的慢了点，今天进去就无了 有人一起来研究他的api么？我这已经抓到一些api了 可以跳过两步操作直接到确定页面

你好，请问可以分享一下吗，每次一进去就是7个灰色实在是太难顶了

留个联系方式我们可以一起研究呀

昨天就差验证码输入的慢了点，今天进去就无了 有人一起来研究他的api么？我这已经抓到一些api了 可以跳过两步操作直接到确定页面

你好，请问可以分享一下吗，每次一进去就是7个灰色实在是太难顶了

留个联系方式我们可以一起研究呀

那就whatsapp? 60995790

昨天就差验证码输入的慢了点，今天进去就无了 有人一起来研究他的api么？我这已经抓到一些api了 可以跳过两步操作直接到确定页面

你好，请问可以分享一下吗，每次一进去就是7个灰色实在是太难顶了

留个联系方式我们可以一起研究呀

兄弟留个QQ或者微信行不

昨天就差验证码输入的慢了点，今天进去就无了 有人一起来研究他的api么？我这已经抓到一些api了 可以跳过两步操作直接到确定页面

你好，请问可以分享一下吗，每次一进去就是7个灰色实在是太难顶了

留个联系方式我们可以一起研究呀

兄弟留个QQ或者微信行不

Q：2210074929

昨天就差验证码输入的慢了点，今天进去就无了 有人一起来研究他的api么？我这已经抓到一些api了 可以跳过两步操作直接到确定页面

你是用ddddorc识别验证码吗，验证码识别准确吗？

你是用ddddorc识别验证码吗，验证码识别准确吗？

就是ddddocr，我感觉只要验证码的字符都在中间，没有边缘被卡了一半的识别率都还可以。不过也遇到过5识别成s的情况

你是用ddddorc识别验证码吗，验证码识别准确吗？

就是ddddocr，我感觉只要验证码的字符都在中间，没有边缘被卡了一半的识别率都还可以。不过也遇到过5识别成s的情况

但是登录界面的验证码很难可以全部准确，请问怎样修改可以跳过登录界面执行后续操作，可以留个联系方式交流吗（Q：1543485515）

你是用ddddorc识别验证码吗，验证码识别准确吗？

就是ddddocr，我感觉只要验证码的字符都在中间，没有边缘被卡了一半的识别率都还可以。不过也遇到过5识别成s的情况

但是登录界面的验证码很难可以全部准确，请问怎样修改可以跳过登录界面执行后续操作，可以留个联系方式交流吗（Q：1543485515）

现在浏览器登陆一次，拿到cookie，使用这个登录后的cookie去访问就不需要登录了

你是用ddddorc识别验证码吗，验证码识别准确吗？

就是ddddocr，我感觉只要验证码的字符都在中间，没有边缘被卡了一半的识别率都还可以。不过也遇到过5识别成s的情况

但是登录界面的验证码很难可以全部准确，请问怎样修改可以跳过登录界面执行后续操作，可以留个联系方式交流吗（Q：1543485515）

现在浏览器登陆一次，拿到cookie，使用这个登录后的cookie去访问就不需要登录了

好像现在系统升级了，十点前会清掉你的cookie，不能提前登录了,而且我登录的验证码还刷得慢 ：(

但是登录界面的验证码很难可以全部准确，请问怎

我用的是阿里云的接口，10块钱1000次准确率还行，能实现自动登录。但现在做不到抢票，有接口拿不到参数

抢了快一个星期都没抢到，我觉得程序是好的，能准时启动。但问题是感觉系统和某些牛牛可能有合作，名额早就被锁死，就连市面上的普通牛牛都抢不到。

请问能留个联系方式吗？想学习学习，谢谢了

昨天就差验证码输入的慢了点，今天进去就无了 有人一起来研究他的api么？我这已经抓到一些api了 可以跳过两步操作直接到确定页面

我也研究了一些了，可以一起研究？

昨天就差验证码输入的慢了点，今天进去就无了 有人一起来研究他的api么？我这已经抓到一些api了 可以跳过两步操作直接到确定页面

我也研究了一些了，可以一起研究？

可以呀 不过我已经回大陆了，可以留下wechat或者其他方式

Dove136380243
哈哈我只是帮同学看看
------------------ 原始邮件 ------------------
发件人:                                                                                "01miaom/jiankangyizhan"                                                                                @.>;
发送时间: 2022年3月6日(星期天) 晚上11:46
@.>;
抄送: " @.@.>;
主题: Re: [01miaom/jiankangyizhan] 有人用这个脚本抢到了吗 (Issue #11)
昨天就差验证码输入的慢了点，今天进去就无了 有人一起来研究他的api么？我这已经抓到一些api了 可以跳过两步操作直接到确定页面
我也研究了一些了，可以一起研究？
可以呀 不过我已经回大陆了，可以留下wechat或者其他方式
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

昨天就差验证码输入的慢了点，今天进去就无了 有人一起来研究他的api么？我这已经抓到一些api了 可以跳过两步操作直接到确定页面

我也研究了一些了，可以一起研究？

可以呀 不过我已经回大陆了，可以留下wechat或者其他方式

wechat：Gina_0327。可以交流一下吗

昨天就差验证码输入的慢了点，今天进去就无了 有人一起来研究他的api么？我这已经抓到一些api了 可以跳过两步操作直接到确定页面

可以交流一下吗?
wechat: angielwt20
我还卡在香港

昨天就差验证码输入的慢了点，今天进去就无了 有人一起来研究他的api么？我这已经抓到一些api了 可以跳过两步操作直接到确定页面

可以交流一下吗? wechat: angielwt20 我还卡在香港

我已经隔离完 正常活动了 已经加你wechat了

昨天就差验证码输入的慢了点，今天进去就无了 有人一起来研究他的api么？我这已经抓到一些api了 可以跳过两步操作直接到确定页面

可以交流一下吗? wechat: angielwt20 我还卡在香港

我已经隔离完 正常活动了 已经加你wechat了

你好，可以交流一下吗？感谢
wechat: inn-nev-last

wechat

昨天就差验证码输入的慢了点，今天进去就无了 有人一起来研究他的api么？我这已经抓到一些api了 可以跳过两步操作直接到确定页面

可以交流一下吗? wechat: angielwt20 我还卡在香港

我已经隔离完 正常活动了 已经加你wechat了

你好可以交流一下嘛 wechat: spacehehe

authors: 01miaom Bobhu1995 Gginmiao Jazzwind JiangJianCong RussellXY SsparKluo Zhang-JK eidelee ikuinen janiceng628 oomq sharefantasy twsllj zangjiahe


text:
ciao-controller: Delete ephemeral volumes on start failure

If the instance start fails due to e.g. the cloud being full then the
ephemeral volume needs to be deleted. This change makes controller
delete the ephemeral volume if it receives a start failure messagef from
scheduler.
Tested by starting 60 instances on a small cluster and then observing
that without the patches the volumes for the rejected instances remain
after deleting all; with the patch no residual volumes remain.
Fixes: #1173
Signed-off-by: Rob Bradford robert.bradford@intel.com

Coverage increased (+0.03%) to 66.096% when pulling ac6a59b49310c0b2dd7465ee439d295f4c8bae87 on rbradford:fix-1173 into c8ac6bcc7938de9b2b0b2decd8e770b1a29a1584 on 01org:master.

Coverage increased (+0.03%) to 66.096% when pulling ac6a59b49310c0b2dd7465ee439d295f4c8bae87 on rbradford:fix-1173 into c8ac6bcc7938de9b2b0b2decd8e770b1a29a1584 on 01org:master.

Coverage increased (+0.001%) to 66.056% when pulling f851b444bf909ff1ab1c688a6f45230c6b9fbd1a on rbradford:fix-1173 into f49ce47369e37e47c143d2a82ac545085c800d83 on 01org:master.

Coverage decreased (-0.03%) to 66.024% when pulling d17af7de6386bfdd16175a0371d09f9419ee323c on rbradford:fix-1173 into f49ce47369e37e47c143d2a82ac545085c800d83 on 01org:master.

source: gharchive/pull-request

authors: coveralls rbradford


text:
ciao-down: Add workloads support

The user data definitions have been moved out of the ciao-down source code into separate files and stored in the workloads directory.  The result being that ciao-down is no longer restricted to creating  ciao and clear-container VMs.
Workload definitions must be stored in either

$GOPATH/src/github.com/01org/ciao/testutil/ciao-down/workloads
~/.ciao_down/workloads

In addition to being able to specify the cloud-init file used to bootstrap a new VM, the workload yaml files now contain two new sections that allow the user to specify the resources that will be consumed by the VM, mounts and port mappings and the underlying image upon which the VM will be based.  ciao-down is no longer tied to xenial.
There are some new helper functions that make it easier to write workload definitions, updated documentation and some new workloads for base fedora25 and xenial workloads and a fedora25 based ciao workload.
The command line hasn't changed.  You still do
./ciao-down prepare
for ciao
and
./ciao-down prepare --vmtype=clearcontainers
for clear containers.  A ciao fedora workload can be created using
./ciao-down prepare --vmtype=ciao-fedora25

@mcastelino , @grahamwhaley  could you give this a test to make sure cc still works for you?

@markdryan on it now.. Will also try with some custom yaml and cloud-init files.
At this point if this works I would like to delete --vmtype=clearcontainers and just publish yaml and cloud-init.

Coverage increased (+0.02%) to 65.752% when pulling 8afe42036b326b44de9306532efa44e32521a523 on markdryan:ciao_down_workloads into 2dc4802ee81cd926463fdb669781b45bfdbe4aa0 on 01org:master.

Interestingly it looks like go is missing from the path inside semaphore:
Installing it seems fine:

Downloading Go : [OK]
Unpacking Go : [OK]

but setup.sh fails to find "go"
Could something have changed with the way the PATH is setup?

I've tested this with a few combinations and it works for me. I'll look more closely at the code next.

@markdryan It may be good to reflect vmtype in ciao-down status. So that the user knows which type of instance is currently setup.

@markdryan Passes basic sanity tests for me

@mcastelino Some additional responses

At this point if this works I would like to delete --vmtype=clearcontainers and just publish yaml and cloud-init.

This is what this PR does.  The ciao and cc cloud-init files are no longer hardcoded in ciao-down and there's almost no ciao specific code left in ciao-down apart from the code that migrates the state of old ciao VM instances to the new format.  The value passed to the vmtype option is just the name of the yaml workload you want to create.  workload would be a better name for this option but I deliberately avoided changing the command line to avoid needing to update cc scripts and documentation.

It may be good to reflect vmtype in ciao-down status. So that the user knows which type of instance is currently setup.

Sure, I can do this.  Not such a huge issue now but going forward when we have multiple instance support this will be vital.

Could something have changed with the way the PATH is setup?

Interesting indeed.  I don't think it's the PATH as the full path is used to invoke Go.  Perhaps there's something wrong with the proxy functions.  I'll check.

Coverage decreased (-0.004%) to 65.73% when pulling 99b5ef32aed1a1dca851dce8ce47ee960318e175 on markdryan:ciao_down_workloads into 2dc4802ee81cd926463fdb669781b45bfdbe4aa0 on 01org:master.

Coverage increased (+0.009%) to 65.743% when pulling f5856f29a20b2241c7825fa4cc36b7d0a2d1b39e on markdryan:ciao_down_workloads into 2dc4802ee81cd926463fdb669781b45bfdbe4aa0 on 01org:master.

Coverage increased (+0.009%) to 65.743% when pulling f5856f29a20b2241c7825fa4cc36b7d0a2d1b39e on markdryan:ciao_down_workloads into 2dc4802ee81cd926463fdb669781b45bfdbe4aa0 on 01org:master.

@markdryan It may be good to reflect vmtype in ciao-down status. So that the user knows which type of instance is currently setup.

@mcastelino This is done now.

Coverage remained the same at 65.723% when pulling 386cf140d84e1903a2da2237e3bd49ae8956a063 on markdryan:ciao_down_workloads into d538ddd8787645ed9ca1a4b93adeb40b2df18689 on 01org:master.

Coverage remained the same at 65.723% when pulling 386cf140d84e1903a2da2237e3bd49ae8956a063 on markdryan:ciao_down_workloads into d538ddd8787645ed9ca1a4b93adeb40b2df18689 on 01org:master.

Coverage remained the same at 65.723% when pulling 386cf140d84e1903a2da2237e3bd49ae8956a063 on markdryan:ciao_down_workloads into d538ddd8787645ed9ca1a4b93adeb40b2df18689 on 01org:master.

Not sure why the semaphore build didn't start on the new set of PRs.  I seem to be unable to trigger it manually.  verify.sh and bat pass for me on ciao-down.

The only feedback I have but you don't have to fix in this version would be for a way to get the list of vmtypes. Maybe in the --usage?

The only feedback I have but you don't have to fix in this version would be for a way to get the list of vmtypes. Maybe in the --usage?

Totally agree.  I'm planning
ciao-cli workload list
ciao-cli workload delete
ciao-cli workload clone

authors: coveralls markdryan mcastelino rbradford


text:
feature request: make hopper under stone_mortar transfer only processed items

sakura version: 1.0.7-1.12.2
The stone mortar outputs ingredients first, then outputs processed items.
I thought this should output only processed ones, like minecraft:furnace.
built structure:
*
\C

(* is sakura:stone_mortar, \ is minecraft:hopper that connecting C, and C is minecraft:chest)

1.18.2 version will do.

could it implemented also for 1.12.2 one?
I'm not sure whether 1.12.2  branch is still supported and accepts PRs if there's any.

no, I can't code for 1.12.2 now.
sorry.

@0999312

no, I can't code for 1.12.2 now.
sorry.

nvm

I'm not sure whether 1.12.2 branch is still supported

I'd like to confirm that 1.12.2 branch isn't in end-of-life because I'd like to submit a PR that backport it to 1.12.2 one. If you say "this mod for 1.12.2 will not update anymore," I will not submit it.

@0999312
well, so, can I submit PR to 1.12 branch to backport this behavior?

sure


text:
Add metadata using Helmet for About page and Privacy Policy

Utilize the Helmet component to include static metadata such as title, description, and canonical link for improved SEO on the About page and Privacy Policy.

Closes #issue-number


text:
[0.6.1 Roadmap / Skinning] Separate song select menu elements, in-game UI elements and so as Modules

Implement a generic IModule interface (Modules can be, for example, the Timer, the score summaries, the high score plate, etc...)
Modules positions and usage (they are not mandatory) are defined in specific .ini files on the skin (Format to be specified later)
Modules definitions also containing which texture to use are specified on the Skin folder (maybe a Modules subfolder ?)

Tied with #257 #260 #266

Closed due to obsoleted and unnecessary, considering the current [Element]Config.ini files disposition already does the job well and allows for more customisation


text:
Get rid of keys duplication for SmtLeaf::Multiple

Smt supports for various leaf types, and Multiple is one of them (leaf with multiple values):
Multiple(Vec<(RpoDigest, Word)>),

According to implementation, it is guarantied that all values in such leaf have the same key. But we duplicate that key for all values in the leaf.
My proposal is to refactor this in order to have only single key for multiple entries:
Multiple {
    key: RpoDigest,
    values: Vec<Word>,
},

// or just:

Multiple((RpoDigest, Vec<Word>)),

If we choose the first approach, we can also refactor Single from tuple to struct.

I think maybe the documentation needs to be improved here because the key-value pairs are actually distinct. What is the same is the most significant element of the key. Basically, the key consists of 4 elements and for Multiple leaf, key[3] is the same for all key-value pairs, but the remaining elements of the key could be different.

Ah, my bad, thank you for clarification! Closed

authors: bobbinth polydez


text:
Implement Serializable for FungibleAsset

What should be done?
Implement Serializable for FungibleAsset.
How should it be done?
Implement Serializable for FungibleAsset and consider changing how Asset is serialized by delegating to the implementation on FungibleAsset and NonFungibleAsset.
When is this task done?
This task is done when Serializable is implemented for FungibleAsset and Asset serialization has been reconsidered.
Additional context
No response

Closed by #907.

authors: PhilippGackstatter bobbinth


text:
Improve BIGNUM operations

Amortize calls to modexp precompile by ~5%.

@hratoanina I'll let you judge if you wanna do another pass for the last commit after your review that touches a bit everything due to the new convenience macro, otherwise if it looks good to you I'll merge it


text:
Add support for generating multiple block proofs at once

It has come up during benchmarking that it would be useful to test what it is like to generate multiple block proofs simultaneously.
The motivation for this comes from the fact that the amount of parallelizable work diminishes as generation progresses for a block proof. The reason for this is due to the trie structure from aggregating txn proofs together into a final block proof, the amount of work units available quickly decreases as we move up the proof aggregation trie. This quickly leads to a situation where CPU utilization drops off after a good portion of the proof tree becomes completed.
Because it's useful to benchmark a more realistic scenario where we have multiple blocks being proved at once, we probably should add a new mode that support generating a range of blocks. This should be pretty straight forward to implement I think.

@BGluth this issue is a duplicate of #10, right?

@vladimir-trifonov Yeah you're right. Like I guess that PR focuses more on caching block hashes, but this one is more about explicit multi-blocks.

When we prove a range, let's say blocks 10..13= for processing block 10 we use checkpoint-block-number set to 9, but for processing block 11 we use the block proof of block 10 as a parent, i.e. every next proof relies on the previous one, i.e. that's why proving a range happens synchronously. We can skip that, we have in the readme:
- Because incorporating the previous block proof requires a chain of proofs back to the last checkpoint height, you can also disable this requirement by passing `true` for `<IGNORE_PREVIOUS_PROOFS>` (which internally just sets the current checkpoint height to the previous block height).

and then the proving blocks could be made to run in parallel... @Nashtare

I'm not sure how much work this would be with the current zero-bin (cc @cpubot) as it is currently built around proving one block at a time, but we need to be able to process blocks concurrently and to connect them if required, by passing the previous block proof when proving the next one. 99.99% of the proving time (all txn + aggregation proofs) remains fully independent of the previous block, so we could still have the leader push a next block to the queue, to be processed ASAP by available workers.
We'd just need the final block_proof producer for block N to:

wait for proof N-1 to be available if checkpoint-block-number is smaller than N-1
ignore previous proofs and just process the current block if checkpoint-block-number == N-1.

That sounds fine to me, should we make some plan, it sounds like a pretty big change to me if I'm not mistaken...

I remember I did take a decent look at what an implementation might look like a while back, and IIRC it looked pretty doable with how Paladin was setup. I would take a look at prove in prover/src/lib.rs. You can probably adjust this so it takes in a block range and creates the same task dependencies for multiple blocks. You might also need to make one more task type to merge two block proofs together. @cpubot might have more to add.

authors: BGluth Nashtare vladimir-trifonov


text:
refactor: use typed tries in trace_decoder

#275
Change summary:

Add typed_mpt::{StateTrie, StorageTrie, ..}.
type1 frontend emits the above.
type1 frontend is cleaner.

Reviewers
I've assumed my StorageTrie is correct because the tests still pass, would appreciate a particularly close look here.

Drafting to wait for #400

I have one question though. Have you tried benchmarking this vs the old version?

No, but https://github.com/0xPolygonZero/zk_evm/blob/a5b92b2b2bcc7bbf8725190aaa0fba7007e51a6a/trace_decoder/src/lib.rs#L16-L17
If I had to guess, worst case we've got constant overhead, but I think this mostly just changes where rlp::decode/rlp::encode calls (to behind the type)

I have one question though. Have you tried benchmarking this vs the old version?

No, but
https://github.com/0xPolygonZero/zk_evm/blob/a5b92b2b2bcc7bbf8725190aaa0fba7007e51a6a/trace_decoder/src/lib.rs#L16-L17
If I had to guess, worst case we've got constant overhead, but I think this mostly just changes where rlp::decode/rlp::encode calls (to behind the type)

Yeah it's not a requirement to be more performant or anything, hence why I approved. I was just being nosey


text:
🛑 Gelbooru is down

In 0c61078, Gelbooru (https://gelbooru.com/index.php?page=dapi&s=post&q=index&limit=50&tags=yuri) was down:

HTTP code: 500
Response time: 119 ms

Resolved: Gelbooru is back up in 0ee6248.


text:
Allow to compare 2 files and remove duplicates

I was wondering if it would be possible to have duprule run between 2 files and remove the duplicates that are already contained within the target file.
So, something along the lines of:
duprule new_rule.rule main_rules.rule > new_rules_not_in_main_rules.rule
new_rule.rule = source file
main_rules.rule = file you want to compare new_rule.rule against
new_rules_not_in_main_rules.rule = file that contains the records only found in new_rule.rule and not found in main_rules.rule
Although the syntax and 'how it does it' doesn't really matter that much as long as a person is able to remove rules that you already had in your 'main list'.

Hmm would you be able to achieve this by:
1- cat main_rules.rule new_rule.rule > combined.rule the order of combining is relevant.
2- duprule < combined.rule > combined-uniq.rule: keep first precedence or rule.
3- remove rules that are in combined-uniq.rule & main_rules and thus you'd have rules that are in new rule but not in main_rules.


text:
Emergency fix

Can someone that used to contribute to it please take a look at this repo ? It broke this weekend. I would pay for a fix.

Hello,
this repo stopped working for me too
i have written an alternative to it in swift
if you are interested email me and i can install it in your app

Yes I am interested. You can reach me directly at @.***
On Tue, May 2, 2023 at 5:03 PM Mohammad Ashour @.***>
wrote:

Hello,
this repo stopped working for me too
i have written an alternative to it in swift
if you are interested email me and i can install it in your app
—
Reply to this email directly, view it on GitHub
https://github.com/0xced/XCDYouTubeKit/issues/561#issuecomment-1532147555,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABKXLE7UMHYVXXNTSO3SBUTXEFZB7ANCNFSM6AAAAAAXTR3SEQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Yes I am interested. You can reach me directly at @.***
…
On Tue, May 2, 2023 at 5:03 PM Mohammad Ashour @.> wrote: Hello, this repo stopped working for me too i have written an alternative to it in swift if you are interested email me and i can install it in your app — Reply to this email directly, view it on GitHub <#561 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABKXLE7UMHYVXXNTSO3SBUTXEFZB7ANCNFSM6AAAAAAXTR3SEQ . You are receiving this because you authored the thread.Message ID: @.>

I cant see your email
here is mine in image so i does not get censored

Hello @matsd88
Hope you are doing well.
Is it working? or are you still fetching issues?
Let me know thanks.

Yes, we got it working but thanks for responding and offering to help.
On Fri, May 5, 2023 at 1:21 PM Jaydeep Virani @.***>
wrote:

Hello @matsd88 https://github.com/matsd88
Hope you are doing well.
Is it working? or are you still fetching issues?
Let me know thanks.
—
Reply to this email directly, view it on GitHub
https://github.com/0xced/XCDYouTubeKit/issues/561#issuecomment-1536558118,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABKXLE53DQV5I72XV7ISGSDXEUZKRANCNFSM6AAAAAAXTR3SEQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

@matsd88 can you please help me to fix this issue? I'm facing the same issue. thanks in advance.

I had to switch to a different library that's in swift. It's this one and
it works.
https://github.com/alexeichhorn/YouTubeKit
On Fri, May 5, 2023 at 1:57 PM Jaydeep Virani @.***>
wrote:

@matsd88 https://github.com/matsd88 can you please help me to fix this
issue? I'm facing the same issue. thanks in advance.
—
Reply to this email directly, view it on GitHub
https://github.com/0xced/XCDYouTubeKit/issues/561#issuecomment-1536590766,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABKXLE4WE322UQE54VFAJD3XEU5RJANCNFSM6AAAAAAXTR3SEQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

@matsd88 Alright, I will check it. thank you very much.

Hello, this repo stopped working for me too i have written an alternative to it in swift if you are interested email me and i can install it in your app

i need help


text:
Remove or fix rofi.sh hook

I'm not sure how this came to light. Please remove rofi.sh hook untill better version is available.
Another approach would be to change echo line to Your config file was destroyed (:evilsmiley:), but enjoy new theme.
I really appreciate there is base16 theme for rofi. But I'm absolutely not OK with software destroying my config file, without asking, because petty color theme change... I have hourly backups but many users don't. And it bad enough to loose last hour of config changes.
Please always think hard, when manipulating with configuration files. In most cases your software isn't only one who is changing it and users can have tons of precious configuration there.
Same wrong approach is currently used in base16-manager. I'm working on PR for it, feel free to take parts from it and adjust it for this hook.
Btw. there is check to existence of config file in hook... So if config file doesn't exist and it would be totally ok to put new config with theme there - it does nothing. But if config file exists, it overwrites it :/ Maybe there should be ! before config file check? That would be much much better.

Sorry, I had no idea! I haven't actually used this hook, I simply accepted the PR. I now realize I should have tested it first. Will add a warning and fix the ! issue for now, at least until I or someone else has time to fix it properly. Thanks for pointing this out!

Thanks, I'm closing issue as from my poin it is solved. If me or somebody else have time to prepare better alternative, we can just create new PR.


text:
Enhance end meeting and receive feedback

complimentary of - 100mslive/100ms-web#425

Hi @triptu can you assign this to me ? I will work on it, and will it be possible to add the hacktoberfest tag. Thanks in advance

Yeah sure go on! you will get the tag don't worry there

authors: Chris-Blesson Deep-Codes


text:
Executor

related to https://github.com/106-inc/sim2022/issues/28

#25 and #26 also fixed.

Closes #25
Closes #26


text:
Unifi CVE

https://community.ui.com/releases/Security-Advisory-Bulletin-042-042/c4f68b56-cdc4-4128-b2cb-5870209d1704
Any chance we can get an update to v8.4.59 sooner?
I'm a Unraid hobbyist and current Unraid maintainer for the LXC template variant.
lxc code here: https://github.com/bmartino1/unraid-lxc-unifi
not sure what you would need to make a latest / test branch that would auto update the application as done in the lxc.

Any chance we can get an update to v8.4.59 sooner?

Done.

Thank you!


text:
PI8 FedRAMP remediations

What we're after: We address planned POAM items and unexpected FedRAMP complications
Benefits/why:

Squads plan to have some capacity drained off by FedRAMP surprises

@brittag are we at the point where we can accept all the issues in Awaiting Acceptance?

@mogul 7/8 of those issues are POAM items in "awaiting acceptance" since we're still waiting for an update from Veris on whether they accept our false positive / operational requirement rationales for those items. It's ok with me to close them since that's also tracked in the POAM - or we could just open a new standalone issue for tracking them rather than having 7 issues for similar topics.

authors: brittag mogul


text:
Exclude files/folders in command directory

One of the recommended patterns for organizing jest unit tests is to have a tests folder alongside the files you want to test.  This style doesn't seem to work when registering my command folder.  Discord Commando lets you pass in an exclusion rule when importing your files.  This is what I have currently set up in Commando.
.registerCommandsIn({
  dirname: path.join(__dirname, "commands"),
  excludeDirs: /^__tests__$/
});

Implemented in 03805445a3feef113c2b6f1711f1adb46f4ac40a

license: mit

license_source: bigquery


text:
New Varps Need To Be Moved To Unused Varps

The following varps were newely created instead of using an existing varp for server side only.

295=skill_clock
296=skill_anim
297=skill_sound
298=shop
299=shop_buy
300=shop_sell
301=shop_haggle
302=thread_used

Treasure trails needs to be rewritten to only use the following varp:

292=ring_of_forging_charges_used

The following varps need to be removed from current treasure trails:

275=trail_easy_steps_count
276=trail_medium_steps_count
277=trail_hard_steps_count
278=trail_easy_steps_completed
279=trail_medium_steps_completed
280=trail_hard_steps_completed

Please refer to: https://github.com/2004scape/Server/wiki/Varp-ID-Tracking

The following varps were moved:
295=skill_clock
296=skill_anim
297=skill_sound
298=shop
299=shop_buy
300=shop_sell
301=shop_haggle
302=thread_used

Reverted:
275=trail_easy_steps_count
276=trail_medium_steps_count
277=trail_hard_steps_count
278=trail_easy_steps_completed
279=trail_medium_steps_completed
280=trail_hard_steps_completed
To:
275=varp_275
276=varp_276
277=varp_277
278=varp_278
279=varp_279
280=varp_280
292=ring_of_forging_charges_used was converted to 292=trail_clue
290=varp_290 was converted to 290=ring_of_recoil
291=varp_291 was converted to 291=ring_of_forging (And all uses of ring_of_forging_charges were redirected to ring_of_forging).
In PR #243

authors: FlenarnTemp ultraviolet-jordan


text:
feat: initial eMRTD reading messages

Initial import of eMRTD reader messages. For the moment, no parsing is being done, as it is simply intended to help on Hologram app testing.

The error in the validation occurs because the tsconfig.build.json file requires running yarn install in the examples/chatbot project as well.
$ nest build
examples/chatbot/index.ts:[6](https://github.com/2060-io/2060-service-agent/pull/27/checks?notification_referrer_id=NT_kwDOAqSoELQxMjc5NzY3NzY2MTo0NDM0NTM2MA#step:7:7):24 - error TS2307: Cannot find module 'tslog' or its corresponding type declarations.

authors: genaris lotharking


text:
Add flag to return FAssetData

This pull request adds a basic FAssetData wrapper and the ability to get FAssetData objects rather than fully loading assets when calling get_asset_by_filter.
Before merging I had a few questions. Should we use keyword args for this and add this functionality to the other get_asset* functions? Keyword args haven't been used anywhere else so I did not look into using them here yet.
This is an important addition as the cost of fully loading assets is much higher than simply getting back the FAssetData objects.

Hi, thanks for the patch, i think supporting this to all the asset-related functions would be a good thing.
Regarding keywords, the only usage is for the reflection api, and it is not a good example (it is pretty complex). If you want to add support to the other asset api functions i will wai for it before merging

@rdeioris do you think it's worth investing in a consistent keyword argument pattern? As it is now passing True as a second argument is very unclear. I can see wanting to support additional arguments such as passing a flag to SearchAllAssets or not. The more we add the less obvious it will be when inspecting code.

I will merge it as is, and i will add a kwargs so you can base your improvements from it

Just added support for kwargs:
https://github.com/20tab/UnrealEnginePython/commit/e38cfa7d7c8b54cdb5cdf8a3621b054d8af6c7ae#diff-3a5d4c4d56810ecb1dbbbb250d82ec6aL314
https://github.com/20tab/UnrealEnginePython/commit/e38cfa7d7c8b54cdb5cdf8a3621b054d8af6c7ae#diff-633c64bb8571d9b90a038d15e2b48d0dR142
unfortunately that boring #pragma directive is required on windows :(

authors: osstony rdeioris


text:
models built, assocations started

Our first push of the day!

Looks good to me!


text:
Roadmap: revamp config implementation and more

此 issue 作为 (个人) roadmap/todo 使用，也许会更新

[x] 移除 root config 机制
[x] distro config 添加 enabled 参数
[x] 自动读取和识别 distro 目录 （通过读取distro config.toml 判断）
[x] 引入 --work-dir 参数（暂定名）以替代 --config 参数
[x] 自动读取和识别每个distro下的子目录（每个目录对应一个包），并汇总去重得到总package列表
[ ] 写 unit test
[ ] 为已有参数添加短形式 (shorthand)

一些相关的远期构想：

[ ] 重置 metadata.sh 实现，变成 package config.toml (命令也许可以通过toml里直接定义string实现?)

好快的进度TT


text:
Jira Ticket Field keeps getting nulled

Hi,
Whenever we set the Jira ticket field, and the cron runs, it keeps being set to null. Any ideas concerning this?

+1

authors: HairyDuck cepres-tareq-kirresh


text:
오류

openNAMU version : v3.1.6-master-20

역사에서 각 개별버전을 확인하려고 하면 다음과 같은 오류가 표시됩니다.

UnboundLocalError: local variable 'cache_data' referenced before assignment

수정 완료


text:
Q4 Community Building Sprint 3

Sprint 3
### Tasks
- [ ] https://github.com/2i2c-org/infrastructure/issues/3279
- [ ] https://github.com/2i2c-org/community-showcase/issues/22
- [ ] https://github.com/2i2c-org/community-showcase/issues/23
- [ ] https://github.com/2i2c-org/community-showcase/issues/24
- [ ] https://github.com/2i2c-org/community-showcase/issues/20
- [ ] https://github.com/2i2c-org/community-showcase/issues/21
- [ ] https://github.com/2i2c-org/community-showcase/issues/25

Closing and transferring uncompleted work to https://github.com/2i2c-org/community-showcase/issues/10


text:
🛑 MS - PAYMENTS is down

In 6589671, MS - PAYMENTS ($MS_PAYMENTS_URL) was down:

HTTP code: 503
Response time: 265 ms

Resolved: MS - PAYMENTS is back up in 0866396 after 10 minutes.


text:
🛑 Unitix is down

In c354f09, Unitix (https://unitix.be) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Unitix is back up in 59cc249.


text:
[Eletrônica] Entender o funcionamento do circutio do controle externo

Foi observado que o controle externo consegue se comunicar com a cadeira mediante comunicação bluetooth. Para termos certeza do seu funcionamento, é importante entendermos como o circuito funciona num nível um pouco acima do superficial.
Precisamos responder como comentario as seguintes perguntas:

O circuito conta com algum circuito integrado? Se sim, afeta o nosso trabalho?
Os sinais do joystick e do botão estão indo onde para serem processados? Conhecemos o componente que eles estão alimentando?
Existe a possibilidade de montar uma versão simplificada da placa nossa? Isso aqui é para entender a complexidade do circuito envolvido.

O circuito conta, sim, com um circuito integrado. Este é o modulo MS50SFA, que essencialmente é um mini processador embutido com capacidade de UART e BLE de MUITO baixo consumo.
Ele impacta nosso trabalho pois ele realiza a leitura do sinal analógico encaminhado aos seus pinos 28 e 30, conforme mostrado no esquemático embaixo. Dai, assumimos o código realiza a interpretação deles conforme definido pelos programadores originais, e assim vai encaminhar os pacotes de dados certos para o controlador da cadeira de rodas.
Por conta da programação interna dentro do circuito, não seria possível realizar uma versão simplificada da placa. Ela já é bastante simples, com o principal ponto de complexidade sendo este circuito integrado.
Encaminho em anexo a folha de dados de cada arquivo descrevendo este circuito integrado contido dentro da placa.
3898463.pdf
MS50SFAV1.4_V2.2_52832-Datasheet.pdf


text:
File glsl-packing.lisp no longer exists but still listed in system definition

The system definition in 3b-spirv.asd lists (:file "glsl-packing") but this file was removed two commits ago. The definition should be revised to reflect this.

fixed, thanks


text:
Group pages in react [WIP]

Description
STILL WORK IN PROGRESS, SOME FEATURES MAY NOT WORK PROPERLY.
:warning:  Disclaimer: way too big pull request... (my bad)
The purpose of this PR is to finally implement group pages in React.
The goal is not to implement all the features directly (event though I almost did it), but more to have the pages ready so that we can improve them later.
Changes
Integration of group pages in react.

group type page
group list page
group details page

Changed and added some APIs

social link
groups
...

Improved preview image
Fixed and improved infinite scroll (works on mobile now)
...other things that I forgot
Left to do

[ ] Implement group admin interface (in progress)
[ ] choose to implement or remove subscribe feature :smile:
[ ] Add Translations
[ ] Fix lot of bugs
[ ] Fix tests

Screenshots

Ok I will note review your code, I'm too old for that but I would like to test it, can you deploy it on staging?

For the "subscribers" option, my idea on this:

Keep the button "Subscribe" on the page group: it should be the same as subscribing to a page on instagram
Remove the "Member" button from the header of the group page to avoid confusion => you can only add yourself as member from the member tab

Ok I will not review your code, I'm too old for that but I would like to test it, can you deploy it on staging?

It is deployed but there is a 404 on the pages.
I don't know if it's a pipeline issue or actually my code but didn't have the time to check

Pour avoir une belle grille pour les groupes (je sais plus si c'était fix) : https://youtu.be/3T0gjtXRNC0?si=jfPuEkP0yzJ8G5z4

Pour avoir une belle grille pour les groupes (je sais plus si c'était fix) : https://youtu.be/3T0gjtXRNC0?si=jfPuEkP0yzJ8G5z4

On utilise les Grid de MUI on a jamais eu de problème avec ça non ?

authors: hydrielax rravelli


text:
🛑 Dasharo Events is down

In ed2d645, Dasharo Events (https://vpub.dasharo.com) was down:

HTTP code: 500
Response time: 1051 ms

Resolved: Dasharo Events is back up in 797ca44.


text:
feat(DataGrid): Enhance CSV generation

Requirements:

all numbers should have local formatting without a thousand separator;
we need only currency signs (100,00% → 100, 1.000,32 $ → 1000,32 $);
it should export all pages and the file name should depend on the page name
date/date-time should be simplified;
the boolean column should return Yes/No;
custom ternary column tooltips (done for ModdableDataGridOrder in eBusiness repository);
add (%) to percentage column headers;

use a previous column title instead of the empty cell for nested columns.

Version: 0.9.12-preview.15.
Ticket: 3mo.atlassian.net/jira/software/c/projects/DEV/issues/DEV-8431
Pull request:
https://github.com/3mo-esolutions/ebusiness-core/pull/1365

@a11delavar, the only thing I am very unsure is adding timeout for fetching pages. What if we have huge data grids? Maybe it should be better to add something like Promise.sleep(2_500 * i) to reduce server upload.

@a11delavar, the only thing I am very unsure is adding timeout for fetching pages. What if we have huge data grids? Maybe it should be better to add something like Promise.sleep(2_500 * i) to reduce server upload.

By the way, we use elevateMemoryNoTimeout for server-side instead of isBulk. What do you think about the naming?  🤔


text:
node memcached with node-v0.12

node memcached can't run on  node v0.12
report this error:
undefined symbol: _ZN2v86Object3SetENS_6HandleINS_5ValueEEES3_NS_17PropertyAttributeE

In the end there is no maintenance of that mean?
node.js 0.12 Error
Module did not self-register
Why do not fix it?

reinstall it's fine.

reinstall still be wrong
node.js 0.12
Module did not self-register

which os?
windows or *inux

Ubuntu 14.04 64bit
Thanks.

@lonso ye, it's the downside of a binary modules as they are only build against node version you orginally installed the module with so when you upgrade node versions you usually need to run a new npm install or npm rebuild in order for all dependencies to get rebuild/updated.

Focus is on
Now node.js 0.12
npm 2.5.0
But there was still Error
If it will not be replaced node.js 0.10.36

authors: 3rd-Eden goalsoft lonso


text:
Upgrade to operator-sdk 1.27.0

Upgrade to operator-sdk 1.27, which involves go 1.19, controller-runtime v0.14.5. Also upgraded to ginkgo v2.

/ok-to-test

/lgtm

/appprove

/approve

authors: roivaz slopezz


text:
Command to delete (or manage) backends

It would be great to have a command to delete the backend.
backend super command has only "copy" subcommand.
Backends can be created by importing the OpenAPI definition but it can't be deleted through a 3scale toolbox.
It would be great if the backend super command would implement subcommands for managing backends (list, create, delete, update, apply) but for my use case (creation of service by importing OpenAPI definition) deletion would be enough.

Added to our internal backlog. Makes all the sense.
Thanx

@vvidovic I love your avatar

Hi, is this already in development? Would be very helpful for us as well. Thanks! :-)

authors: bthdimension eguzki vvidovic


text:
Feminism critical blog wrongly blacklisted

A danish blog that in reasonable and rational terms criticises feminism and its political campaigns (like metoo) has been blacklisted as malicious. I had to remove EtherAddressLookup from Google Chrome in order to access it, as I am not versed in changing settings. This is problematic for two reasons:

Political criticism is not malicious. No one is forced to read opinions that they find disagreeable, and even if they do, they are not harmed by doing so. Comfort and safety are two different things. This is misuse of blacklisting in order to censor.

When protection against genuinely malicious content is misused in this way and has to be removed in the interests of open debate, it exposes users to real threats.

Blog: "Kønsdebat. Nyheder, dokumentation og debat om kønspolitik og kønsforskelle":
http://kønsdebat.dk/blog/?p=111&fbclid=IwAR2UukhSL2kNqxKRGkXjMajmWmwTEDp8cJMB7omMeLVQKnpWJTXXJIagris

Please see https://github.com/409H/EtherAddressLookup/issues/532#issuecomment-387731112


text:
Fixed XSS

📊 Metadata *
Bounty URL: https://huntr.dev/bounties/1-npm-x-data-spreadsheet/
⚙ Description *
the input text or data is not properly sanitized which leads to injecting malicious Javascript code into it
💻 Technical Description *
Have modified code to Encode tags and display
🐛 Proof of Concept (PoC) *
Payload: "><img src=x onerror=alert(1) />

🔥 Proof of Fix (PoF) *

👍 User Acceptance Testing (UAT)
Have test and its stable without any crash

👋 Hello, @myliang. @Aravindha1234u has opened a PR to us with a fix for a potential vulnerability in your repository. To view the vulnerability, please refer to the bounty URL in the first comment, above. If you want this fix in your repository, a PR will automatically open once you comment:
@huntr-helper - LGTM

☎ Need further support?
Come and join us on our community Discord!

❓@myliang - want more fixes like this?
Copy this snippet into your README.md for more vulnerability fixes in the future:
[![huntr](https://cdn.huntr.dev/huntr_security_badge_mono.svg)](https://huntr.dev)


text:
⚡ PR用のテンプレートを追加

タスクやディスカッションのリンク

#33

やったこと

PR用のテンプレートを追加しました。
.githubディレクトリ下に置けばquery parameterで指定する必要はないような書かれ方だったのでそうしました。
code-rabbitに設定ファイルは必要なさそうだったので作らなかったのですが、英語で出力されてしまったので、後で設定ファイルを作成しました。そのため英語のままになっています。

やらないこと
なし
動作確認

このPRには適用されていませんが、archiveのレポジトリでも同様のことを行ったので大丈夫だとおもいます。

特にレビューをお願いしたい箇所

ほかにテンプレートであったほうがよい項目があればぜひ教えてください。

その他

サマリーはPRを作成したタイミングで作成が始まります。
ポエムは面白いので出しています。邪魔だったら消します笑

参考リンク
テンプレートを置く場所

Summary by CodeRabbit

New Features

Introduced a structured pull request template to enhance clarity and communication for contributors.

Sections include: Task or Discussion Links, What was Done, What Will Not Be Done, Verification of Functionality, Specific Review Requests, Other Notes, and Reference Links.

ありがとうございます！ みんなコピペしてたの面白かったですね
(FYI / for your information / 参考までに。アクション不要、というのも採用したくなってきました) [FYI] coderabbit の設定なのですが、ファイルでも coderabbit のサイト内の設定でもできた気がします 全員が見える形なのはファイルなので良いと思います！ ただ merge されるまで変更が反映されないというのはありますね…

coderabbit内で設定しいようと思ったのですが、このレポジトリだけアクセス可能にしてて、なぜかレポジトリ単位で設定できなかったのでファイル作っちゃいました！


text:
Added token for codecov.io

This PR just adds the token in the command to generate reports in Codecov.io
@fedefernandez @juanpedromoreno Could you take a look please? Thank you.

[Current coverage][cc-pull] is 0.68%

Merging [#21][cc-pull] into [master][cc-base-branch] will increase coverage by 0.68%

@@            master       #21   diff @@
========================================
  Files           14        14
  Lines          147       147
  Methods          0         0
  Messages         0         0
  Branches         1         1
========================================
+ Hits             0         1     +1
+ Misses         147       146     -1
  Partials         0         0

Powered by Codecov. Last updated by [6cc84e9...40c87cd][cc-compare]
[cc-base-branch]: https://codecov.io/gh/47deg/github4s/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/47deg/github4s/compare/6cc84e92d2bc5db46b14b927234a7f8a3c7f2342...40c87cd0eb93da44834d1c5a27e2a92737bb3dc9
[cc-pull]: https://codecov.io/gh/47deg/github4s/pull/21?src=pr

It seems like if reports are been submitted properly now:
https://codecov.io/gh/47deg/github4s/branch/rafa-fix-codecov-reports
@fedefernandez @juanpedromoreno Is good to merge? Thank you

LGTM!

authors: codecov-io juanpedromoreno rafaparadela


text:
Git tag feature

Fixes #68
Also adds the createReference op
Please @juanpedromoreno could you review? Thanks!

Codecov Report

Merging #71 into master will decrease coverage by 1.3%.
The diff coverage is 75%.

@@            Coverage Diff             @@
##           master      #71      +/-   ##
==========================================
- Coverage   80.04%   78.74%   -1.31%
==========================================
  Files          34       34
  Lines         471      795     +324
  Branches        2        4       +2
==========================================
+ Hits          377      626     +249
- Misses         94      169      +75

Impacted Files
Coverage Δ

.../main/scala/github4s/free/domain/PullRequest.scala
100% <ø> (ø)
:arrow_up:

.../src/main/scala/github4s/free/domain/GitData.scala
0% <ø> (ø)
:arrow_up:

.../main/scala/github4s/free/algebra/GitDataOps.scala
33.33% <0%> (-9.53%)
:arrow_down:

...4s/shared/src/main/scala/github4s/GithubAPIs.scala
95.55% <100%> (+0.31%)
:arrow_up:

...s/shared/src/main/scala/github4s/api/GitData.scala
100% <100%> (ø)
:arrow_up:

...cala/github4s/free/interpreters/Interpreters.scala
84.44% <33.33%> (-3.32%)
:arrow_down:

...thub4s/shared/src/main/scala/github4s/Github.scala
81.81% <0%> (-1.52%)
:arrow_down:

...ub4s/shared/src/main/scala/github4s/Decoders.scala
95.09% <0%> (-0.74%)
:arrow_down:

...src/main/scala/github4s/free/algebra/AuthOps.scala
100% <0%> (ø)
:arrow_up:

... and 30 more

Continue to review full report at Codecov.

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

authors: codecov-io fedefernandez


text:
Kazari design - save gist prompt

When the user clicks on "save as gist", a popup dialog should appear to let him select the following data:

Description of the gist
Filename for the included gist
Checkbox to select if the gist is intended to be public or private.

Kazari has been removed from the project, we can close this.

authors: jdesiloniz juanpedromoreno


text:
Trying to avoid temporary files...

The point of this change is to avoid having to

create temporary files with parts of our private key (slightly kludgy and reduces the overall security of the asc2qr or qr2asc process)
securely delete temporary files (adds dependencies like shred, etc.)

The solution proposed is to use bash arrays to hold the key pieces in memory so that they never hit the disk. This uses another bash feature (required already) while reducing dependency on other applications.

I like this change. Thanks for the pull request. I'd like to make sure it runs on a couple test machines and then i'll merge the request.

The test script fails for me. I'm on bash 3.2.57 from OS X 10.11.6. I'm suspecting that its related to differences when reading from stdin. Let me do some digging and see what I can find out. There might be a way to use the bash builtin 'read' on a specific number of characters.

Try it now that I have switched out the chunking method from using 'head' to using 'dd'. I think the implementation of head is different on what you and I each have regarding whether or not the characters not consumed by head stay on the buffer each iteration of the loop. dd seems to leave unused characters on the buffer.

Depending on 'dd' was bothering me. So, I went ahead and figured out how to get 'read' to do what I wanted. This should be a decent solution now. Still is very curious in the 'head' implementation difference between our systems.

This works for me now too. Thanks for your diligence.

This works for me now too. Thanks for your diligence.


text:
python2.7: can't open file 'dammed.py': [Errno 2] No such file or directory

hey, i keep getting the message:
python2.7: can't open file 'dammed.py': [Errno 2] No such file or directory
when I try to create a payload. do you know whats wrong?
i'm running on ubuntu on amazon ec2.
thank you very much :)

Do You have cloned it?
If yes please try manually:
in insanity's directory on shell type:
python2.7 dammed.py
Note:  to all features work, is necessary to clone.
You can do this with:
git clone https://github.com/4w4k3/Insanity-Framework


text:
🛑 Features is down

In def8ccd, Features (https://www.dnd5eapi.co/api/features) was down:

HTTP code: 503
Response time: 31 ms

Resolved: Features is back up in cdf275a.


text:
Differentiation of x should be 1 not x^0

Mathematically x^0 is write expression though.
Before
5x^3 + 3x^2 + -7x^1

After
15x^2 + 6x^1 + -7x^0

Suggestions

Make ^1 invisible
6x^1 to 6x
https://github.com/5tarlight/Rustematica/blob/8e2e1176fb735bcd41e499ebfab3d2d0e114364f/src/expr.rs#L179-L183
Result type of differentiation should not be Poly—such as 6x.
This means return type of differentiate function should be something like Box<dyn Dif>
https://github.com/5tarlight/Rustematica/blob/8e2e1176fb735bcd41e499ebfab3d2d0e114364f/src/expr.rs#L121-L125
And this will be available after creating Literal type.

Creating Constant type is done in #8


text:
Switching to other context

How can I switch to another context?

@baselalali hey, will implement a few days

@baselalali this is implemented in the version 1.0.5, and it should work now. Thanks!


text:
webpack-loaders

Great work @richardscarrott!
I dont know if people have made requests about this by now but i will try:
I am working on extensive-react-server with preconfigured setup, fully editable.
Here i am using webpack-hot-server-middleware as a feature in development mode.
The problem is: Using custom plugins og loaders with webpack
Works fine when i use babel-loader
Crashes when i add style-loader returing a 404 Not Found
Any way around this?

@stoffern The style-loader isn't designed to work on the server, you should instead just use the css-loader, e.g. https://github.com/60frames/react-boilerplate/blob/master/tasks/build/createConfig/rules/css.js#L16

authors: richardscarrott stoffern


text:
[REQ] fix license on GH

Hi there, 1st of all thanks for your awesome (voluntary) work !
In order to push the "IP video-streams' players" evolution, we're collecting/doxing related projects (yours too) in our HyMPS project (under a dedicated page), can you please fix licensing terms for it ?
Our "problem" is that the relative license badge isn't generated correctly, as you can see:

(generator URL: https://flat.badgen.net/github/license/76technician/qtvideoplayer)
This could be easily fixed by choosing a "correct" license file through the GH's wizard.
Although it may sounds like a minor aspect, this may help other devs to understand how reuse code in their projects which is a determining factor for the success and longevity of any open software.
Last but not least, we've recently opened a discussion about a "near-zero latency multiple (IP) video-streams playing" to encourage the confrontation on the topic between developers/maintainers.
Hope that inspires !

Well, I hope my code can help others.


text:
flutter项目， iOS使用OC语言， 引入了升级组件后， 无法在模拟器、真机上运行

Launching lib/main.dart on iPhone 11 Pro Max in debug mode...
Running Xcode build...
Xcode build done.                                           15.5s
Failed to build iOS app
Error output from Xcode build:
↳
** BUILD FAILED **
Xcode's output:
↳
/Users/mac/Documents/flutter/.pub-cache/hosted/pub.flutter-io.cn/flutter_app_upgrade-1.0.2/ios/Classes/SwiftFlutterAppUpgradePlugin.swift:13:14: warning: non-breaking space (U+00A0) used instead of regular space
let infoDictionary = Bundle.main.infoDictionary!
/Users/mac/Documents/flutter/.pub-cache/hosted/pub.flutter-io.cn/flutter_app_upgrade-1.0.2/ios/Classes/SwiftFlutterAppUpgradePlugin.swift:13:32: warning: non-breaking space (U+00A0) used instead of regular space
let infoDictionary = Bundle.main.infoDictionary!
/Users/mac/Documents/flutter/.pub-cache/hosted/pub.flutter-io.cn/flutter_app_upgrade-1.0.2/ios/Classes/SwiftFlutterAppUpgradePlugin.swift:14:14: warning: non-breaking space (U+00A0) used instead of regular space
let majorVersion = infoDictionary["CFBundleShortVersionString"]//主程序版本号
/Users/mac/Documents/flutter/.pub-cache/hosted/pub.flutter-io.cn/flutter_app_upgrade-1.0.2/ios/Classes/SwiftFlutterAppUpgradePlugin.swift:17:49: warning: treating a forced downcast to 'String' as optional will never produce 'nil'
map["packageName"] = bundleIdentifier as! String
^
/Users/mac/Documents/flutter/.pub-cache/hosted/pub.flutter-io.cn/flutter_app_upgrade-1.0.2/ios/Classes/SwiftFlutterAppUpgradePlugin.swift:17:51: note: use 'as?' to perform a conditional downcast to 'String'
map["packageName"] = bundleIdentifier as! String
^
?
/Users/mac/Documents/flutter/.pub-cache/hosted/pub.flutter-io.cn/flutter_app_upgrade-1.0.2/ios/Classes/SwiftFlutterAppUpgradePlugin.swift:17:32: note: add parentheses around the cast to silence this warning
map["packageName"] = bundleIdentifier as! String
^
(                          )
/Users/mac/Documents/flutter/.pub-cache/hosted/pub.flutter-io.cn/flutter_app_upgrade-1.0.2/ios/Classes/SwiftFlutterAppUpgradePlugin.swift:18:45: warning: treating a forced downcast to 'String' as optional will never produce 'nil'
map["versionName"] = majorVersion as! String
^
/Users/mac/Documents/flutter/.pub-cache/hosted/pub.flutter-io.cn/flutter_app_upgrade-1.0.2/ios/Classes/SwiftFlutterAppUpgradePlugin.swift:18:47: note: use 'as?' to perform a conditional downcast to 'String'
map["versionName"] = majorVersion as! String
^
?
/Users/mac/Documents/flutter/.pub-cache/hosted/pub.flutter-io.cn/flutter_app_upgrade-1.0.2/ios/Classes/SwiftFlutterAppUpgradePlugin.swift:18:32: note: add parentheses around the cast to silence this warning
map["versionName"] = majorVersion as! String
^
(                      )
Pods-Runner-eildaiovnuitqoaoprmuyblcyyyf
ld: warning: Could not find or use auto-linked library 'swiftCoreGraphics'
ld: warning: Could not find or use auto-linked library 'swiftDarwin'
ld: warning: Could not find or use auto-linked library 'swiftUIKit'
ld: warning: Could not find or use auto-linked library 'swiftFoundation'
ld: warning: Could not find or use auto-linked library 'swiftMetal'
ld: warning: Could not find or use auto-linked library 'swiftObjectiveC'
ld: warning: Could not find or use auto-linked library 'swiftCoreFoundation'
ld: warning: Could not find or use auto-linked library 'swiftCompatibility50'
ld: warning: Could not find or use auto-linked library 'swiftCoreImage'
ld: warning: Could not find or use auto-linked library 'swiftCompatibilityDynamicReplacements'
ld: warning: Could not find or use auto-linked library 'swiftDispatch'
ld: warning: Could not find or use auto-linked library 'swiftCoreMedia'
ld: warning: Could not find or use auto-linked library 'swiftQuartzCore'
ld: warning: Could not find or use auto-linked library 'swiftCore'
ld: warning: Could not find or use auto-linked library 'swiftCoreAudio'
ld: warning: Could not find or use auto-linked library 'swiftSwiftOnoneSupport'
Undefined symbols for architecture x86_64:
"base conformance descriptor for Swift.Hashable: Swift.Equatable", referenced from:
protocol conformance descriptor for __C.UIApplicationOpenExternalURLOptionsKey : Swift.Hashable in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"protocol descriptor for Swift._ObjectiveCBridgeable", referenced from:
protocol conformance descriptor for __C.UIApplicationOpenExternalURLOptionsKey : Swift._ObjectiveCBridgeable in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"method descriptor for static Swift._ObjectiveCBridgeable.conditionallyBridgeFromObjectiveC(: A._ObjectiveCType, result: inout A?) -> Swift.Bool", referenced from:
protocol conformance descriptor for __C.UIApplicationOpenExternalURLOptionsKey : Swift._ObjectiveCBridgeable in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"method descriptor for static Swift._ObjectiveCBridgeable._unconditionallyBridgeFromObjectiveC(A._ObjectiveCType?) -> A", referenced from:
protocol conformance descriptor for __C.UIApplicationOpenExternalURLOptionsKey : Swift._ObjectiveCBridgeable in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"protocol descriptor for Swift.Equatable", referenced from:
protocol conformance descriptor for __C.UIApplicationOpenExternalURLOptionsKey : Swift.Equatable in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"base conformance descriptor for Swift._SwiftNewtypeWrapper: Swift.RawRepresentable", referenced from:
protocol conformance descriptor for __C.UIApplicationOpenExternalURLOptionsKey : Swift._SwiftNewtypeWrapper in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"protocol descriptor for Swift.RawRepresentable", referenced from:
protocol conformance descriptor for __C.UIApplicationOpenExternalURLOptionsKey : Swift.RawRepresentable in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"associated type descriptor for Swift.RawRepresentable.RawValue", referenced from:
protocol conformance descriptor for __C.UIApplicationOpenExternalURLOptionsKey : Swift.RawRepresentable in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"protocol descriptor for Swift._SwiftNewtypeWrapper", referenced from:
protocol conformance descriptor for __C.UIApplicationOpenExternalURLOptionsKey : Swift._SwiftNewtypeWrapper in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"method descriptor for Swift.RawRepresentable.init(rawValue: A.RawValue) -> A?", referenced from:
protocol conformance descriptor for __C.UIApplicationOpenExternalURLOptionsKey : Swift.RawRepresentable in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"method descriptor for Swift._ObjectiveCBridgeable._bridgeToObjectiveC() -> A._ObjectiveCType", referenced from:
protocol conformance descriptor for __C.UIApplicationOpenExternalURLOptionsKey : Swift._ObjectiveCBridgeable in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"method descriptor for Swift.RawRepresentable.rawValue.getter : A.RawValue", referenced from:
protocol conformance descriptor for __C.UIApplicationOpenExternalURLOptionsKey : Swift.RawRepresentable in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"protocol descriptor for Swift._HasCustomAnyHashableRepresentation", referenced from:
protocol conformance descriptor for __C.UIApplicationOpenExternalURLOptionsKey : Swift._HasCustomAnyHashableRepresentation in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"method descriptor for Swift._HasCustomAnyHashableRepresentation._toCustomAnyHashable() -> Swift.AnyHashable?", referenced from:
protocol conformance descriptor for __C.UIApplicationOpenExternalURLOptionsKey : Swift._HasCustomAnyHashableRepresentation in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"protocol conformance descriptor for Swift.String : Swift._ObjectiveCBridgeable in Foundation", referenced from:
lazy protocol witness table accessor for type Swift.String and conformance Swift.String : Swift._ObjectiveCBridgeable in Foundation in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"(extension in Swift):Swift._SwiftNewtypeWrapper< where A: Swift.Hashable, A.Swift.RawRepresentable.RawValue: Swift.Hashable>._toCustomAnyHashable() -> Swift.AnyHashable?", referenced from:
protocol witness for Swift._HasCustomAnyHashableRepresentation._toCustomAnyHashable() -> Swift.AnyHashable? in conformance __C.UIApplicationOpenExternalURLOptionsKey : Swift._HasCustomAnyHashableRepresentation in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"protocol witness table for Swift.String : Swift.Equatable in Swift", referenced from:
protocol witness for static Swift.Equatable.== infix(A, A) -> Swift.Bool in conformance __C.UIApplicationOpenExternalURLOptionsKey : Swift.Equatable in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"(extension in Swift):Swift._SwiftNewtypeWrapper< where A: Swift.Hashable, A.Swift.RawRepresentable.RawValue: Swift.Hashable>._rawHashValue(seed: Swift.Int) -> Swift.Int", referenced from:
protocol witness for Swift.Hashable._rawHashValue(seed: Swift.Int) -> Swift.Int in conformance __C.UIApplicationOpenExternalURLOptionsKey : Swift.Hashable in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"method descriptor for Swift.Hashable.hash(into: inout Swift.Hasher) -> ()", referenced from:
protocol conformance descriptor for __C.UIApplicationOpenExternalURLOptionsKey : Swift.Hashable in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"(extension in Swift):Swift._SwiftNewtypeWrapper< where A: Swift.Hashable, A.Swift.RawRepresentable.RawValue: Swift.Hashable>.hash(into: inout Swift.Hasher) -> ()", referenced from:
protocol witness for Swift.Hashable.hash(into: inout Swift.Hasher) -> () in conformance __C.UIApplicationOpenExternalURLOptionsKey : Swift.Hashable in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"Foundation.URL.bridgeToObjectiveC() -> __C.NSURL", referenced from:
flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.handle(: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"static (extension in Swift):Swift._SwiftNewtypeWrapper< where A.RawValue: Swift._ObjectiveCBridgeable>._unconditionallyBridgeFromObjectiveC(A.RawValue._ObjectiveCType?) -> A", referenced from:
protocol witness for static Swift._ObjectiveCBridgeable._unconditionallyBridgeFromObjectiveC(A._ObjectiveCType?) -> A in conformance __C.UIApplicationOpenExternalURLOptionsKey : Swift._ObjectiveCBridgeable in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"static (extension in Swift):Swift._SwiftNewtypeWrapper< where A.RawValue: Swift._ObjectiveCBridgeable>.conditionallyBridgeFromObjectiveC(: A.RawValue._ObjectiveCType, result: inout A?) -> Swift.Bool", referenced from:
protocol witness for static Swift._ObjectiveCBridgeable.conditionallyBridgeFromObjectiveC(: A._ObjectiveCType, result: inout A?) -> Swift.Bool in conformance __C.UIApplicationOpenExternalURLOptionsKey : Swift._ObjectiveCBridgeable in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"static (extension in Swift):Swift._SwiftNewtypeWrapper< where A.RawValue: Swift._ObjectiveCBridgeable>.forceBridgeFromObjectiveC(: A.RawValue._ObjectiveCType, result: inout A?) -> ()", referenced from:
protocol witness for static Swift._ObjectiveCBridgeable.forceBridgeFromObjectiveC(: A._ObjectiveCType, result: inout A?) -> () in conformance __C.UIApplicationOpenExternalURLOptionsKey : Swift.ObjectiveCBridgeable in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"Swift.allocateUninitializedArray(Builtin.Word) -> ([A], Builtin.RawPointer)", referenced from:
flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.handle(: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"Foundation.URL.init(string: __shared Swift.String) -> Foundation.URL?", referenced from:
flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.handle(: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"Swift.== infix<A where A: Swift.RawRepresentable, A.RawValue: Swift.Equatable>(A, A) -> Swift.Bool", referenced from:
protocol witness for static Swift.Equatable.== infix(A, A) -> Swift.Bool in conformance __C.UIApplicationOpenExternalURLOptionsKey : Swift.Equatable in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"_swift_deallocObject", referenced from:
l_objectdestroy in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"swift_allocObject", referenced from:
@objc flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.handle(: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"(extension in Foundation):Swift.Dictionary.bridgeToObjectiveC() -> __C.NSDictionary", referenced from:
flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.handle(: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"_swift_getWitnessTable", referenced from:
lazy protocol witness table accessor for type __C.UIApplicationOpenExternalURLOptionsKey and conformance __C.UIApplicationOpenExternalURLOptionsKey : Swift.Hashable in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
lazy protocol witness table accessor for type __C.UIApplicationOpenExternalURLOptionsKey and conformance __C.UIApplicationOpenExternalURLOptionsKey : Swift.RawRepresentable in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
lazy protocol witness table accessor for type __C.UIApplicationOpenExternalURLOptionsKey and conformance __C.UIApplicationOpenExternalURLOptionsKey : Swift._HasCustomAnyHashableRepresentation in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
lazy protocol witness table accessor for type __C.UIApplicationOpenExternalURLOptionsKey and conformance __C.UIApplicationOpenExternalURLOptionsKey : Swift.Equatable in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
lazy protocol witness table accessor for type __C.UIApplicationOpenExternalURLOptionsKey and conformance __C.UIApplicationOpenExternalURLOptionsKey : Swift._SwiftNewtypeWrapper in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
lazy protocol witness table accessor for type Swift.String and conformance Swift.String : Swift._ObjectiveCBridgeable in Foundation in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"_swift_getForeignTypeMetadata", referenced from:
type metadata accessor for __C.UIApplicationOpenExternalURLOptionsKey in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"method descriptor for static Swift.Equatable.== infix(A, A) -> Swift.Bool", referenced from:
protocol conformance descriptor for __C.UIApplicationOpenExternalURLOptionsKey : Swift.Equatable in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"_swift_getTypeByMangledNameInContext", referenced from:
___swift_instantiateConcreteTypeFromMangledName in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"method descriptor for Swift.Hashable._rawHashValue(seed: Swift.Int) -> Swift.Int", referenced from:
protocol conformance descriptor for __C.UIApplicationOpenExternalURLOptionsKey : Swift.Hashable in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"static (extension in Foundation):Swift.Dictionary.unconditionallyBridgeFromObjectiveC(__C.NSDictionary?) -> [A : B]", referenced from:
flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.handle(: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"method descriptor for static Swift._ObjectiveCBridgeable.forceBridgeFromObjectiveC(: A._ObjectiveCType, result: inout A?) -> ()", referenced from:
protocol conformance descriptor for __C.UIApplicationOpenExternalURLOptionsKey : Swift.ObjectiveCBridgeable in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"Swift.Dictionary.subscript.setter : (A) -> B?", referenced from:
flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.handle(: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"swift_retain", referenced from:
flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.handle(: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
reabstraction thunk helper from @escaping @callee_guaranteed (@unowned Swift.Bool) -> () to @escaping @callee_unowned @convention(block) (@unowned Swift.Bool) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
_block_copy_helper in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"_swift_FORCE_LOAD$_swiftCompatibilityDynamicReplacements", referenced from:
_swift_FORCE_LOAD$swiftCompatibilityDynamicReplacements$_flutter_app_upgrade in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
(maybe you meant: _swift_FORCE_LOAD$swiftCompatibilityDynamicReplacements$_flutter_app_upgrade)
"_swift_FORCE_LOAD$_swiftCompatibility50", referenced from:
_swift_FORCE_LOAD$swiftCompatibility50$_flutter_app_upgrade in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
(maybe you meant: _swift_FORCE_LOAD$swiftCompatibility50$_flutter_app_upgrade)
"(extension in Swift):Swift._SwiftNewtypeWrapper< where A.RawValue: Swift._ObjectiveCBridgeable>._bridgeToObjectiveC() -> A.RawValue._ObjectiveCType", referenced from:
protocol witness for Swift._ObjectiveCBridgeable.bridgeToObjectiveC() -> A.ObjectiveCType in conformance __C.UIApplicationOpenExternalURLOptionsKey : Swift.ObjectiveCBridgeable in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"swift_bridgeObjectRetain", referenced from:
flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.handle(: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
outlined copy of Swift.String? in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
__C.UIApplicationOpenExternalURLOptionsKey.init(rawValue: Swift.String) -> __C.UIApplicationOpenExternalURLOptionsKey in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"static (extension in Foundation):Swift.String.unconditionallyBridgeFromObjectiveC(__C.NSString?) -> Swift.String", referenced from:
flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.handle(: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
__C.UIApplicationOpenExternalURLOptionsKey.rawValue.getter : Swift.String in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"static Swift.String.== infix(Swift.String, Swift.String) -> Swift.Bool", referenced from:
flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.handle(: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"Swift.assertionFailure(: Swift.StaticString, : Swift.StaticString, file: Swift.StaticString, line: Swift.UInt, flags: Swift.UInt32) -> Swift.Never", referenced from:
flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.handle(: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"swift_dynamicCast", referenced from:
flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.handle(: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"swift_getObjCClassFromMetadata", referenced from:
@nonobjc __C.FlutterMethodChannel.__allocating_init(name: Swift.String, binaryMessenger: __C.FlutterBinaryMessenger) -> __C.FlutterMethodChannel in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"Swift.Dictionary.init() -> [A : B]", referenced from:
flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.handle(: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"swift_bridgeObjectRelease", referenced from:
@nonobjc __C.FlutterMethodChannel.__allocating_init(name: Swift.String, binaryMessenger: __C.FlutterBinaryMessenger) -> __C.FlutterMethodChannel in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.handle(: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
outlined destroy of Swift.String in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
outlined consume of Swift.String? in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
outlined destroy of [Swift.String : Swift.String] in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
__C.UIApplicationOpenExternalURLOptionsKey.init(rawValue: Swift.String) -> __C.UIApplicationOpenExternalURLOptionsKey in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"type metadata for Swift.String", referenced from:
flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.handle(: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
lazy protocol witness table accessor for type Swift.String and conformance Swift.String : Swift.ObjectiveCBridgeable in Foundation in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"method descriptor for Swift.Hashable.hashValue.getter : Swift.Int", referenced from:
protocol conformance descriptor for __C.UIApplicationOpenExternalURLOptionsKey : Swift.Hashable in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"static Swift.String.+ infix(Swift.String, Swift.String) -> Swift.String", referenced from:
flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.handle(: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"protocol witness table for Swift.String : Swift.Hashable in Swift", referenced from:
flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.handle(: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
protocol witness for Swift.Hashable.hashValue.getter : Swift.Int in conformance __C.UIApplicationOpenExternalURLOptionsKey : Swift.Hashable in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
protocol witness for Swift.Hashable.hash(into: inout Swift.Hasher) -> () in conformance __C.UIApplicationOpenExternalURLOptionsKey : Swift.Hashable in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
protocol witness for Swift.Hashable._rawHashValue(seed: Swift.Int) -> Swift.Int in conformance __C.UIApplicationOpenExternalURLOptionsKey : Swift.Hashable in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
protocol witness for Swift._HasCustomAnyHashableRepresentation._toCustomAnyHashable() -> Swift.AnyHashable? in conformance __C.UIApplicationOpenExternalURLOptionsKey : Swift.HasCustomAnyHashableRepresentation in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"Swift.bridgeAnyObjectToAny(Swift.AnyObject?) -> Any", referenced from:
flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.handle(: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"type metadata accessor for Foundation.URL", referenced from:
flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.handle(: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
outlined destroy of Foundation.URL? in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"value witness table for Builtin.UnknownObject", referenced from:
full type metadata for __C.UIApplicationOpenExternalURLOptionsKey in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
full type metadata for flutter_app_upgrade.SwiftFlutterAppUpgradePlugin in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"swift_unknownObjectRelease", referenced from:
static flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.register(with: __C.FlutterPluginRegistrar) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
@nonobjc __C.FlutterMethodChannel.__allocating_init(name: Swift.String, binaryMessenger: __C.FlutterBinaryMessenger) -> __C.FlutterMethodChannel in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
@objc static flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.register(with: __C.FlutterPluginRegistrar) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.handle(: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
reabstraction thunk helper from @escaping @callee_unowned @convention(block) (@unowned Swift.AnyObject?) -> () to @escaping @callee_guaranteed (@in_guaranteed Any?) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"swift_release", referenced from:
flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.handle(: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
reabstraction thunk helper from @escaping @callee_guaranteed (@unowned Swift.Bool) -> () to @escaping @callee_unowned @convention(block) (@unowned Swift.Bool) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
_block_destroy_helper in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
__swift_destroy_boxed_opaque_existential_0 in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
@objc flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.handle(: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"Swift.stdlib_isOSVersionAtLeast(Builtin.Word, Builtin.Word, Builtin.Word) -> Builtin.Int1", referenced from:
flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.handle(: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"_swift_unknownObjectRetain", referenced from:
@objc static flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.register(with: __C.FlutterPluginRegistrar) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"associated type descriptor for Swift._ObjectiveCBridgeable._ObjectiveCType", referenced from:
protocol conformance descriptor for __C.UIApplicationOpenExternalURLOptionsKey : Swift._ObjectiveCBridgeable in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"swift_getObjCClassMetadata", referenced from:
type metadata accessor for __C.FlutterMethodChannel in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
@objc static flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.register(with: __C.FlutterPluginRegistrar) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"protocol descriptor for Swift.Hashable", referenced from:
protocol conformance descriptor for __C.UIApplicationOpenExternalURLOptionsKey : Swift.Hashable in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"(extension in Foundation):Swift.String.bridgeToObjectiveC() -> __C.NSString", referenced from:
@nonobjc __C.FlutterMethodChannel.__allocating_init(name: Swift.String, binaryMessenger: __C.FlutterBinaryMessenger) -> __C.FlutterMethodChannel in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
__C.UIApplicationOpenExternalURLOptionsKey.init(rawValue: Swift.String) -> __C.UIApplicationOpenExternalURLOptionsKey in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"type metadata accessor for Swift.Optional", referenced from:
flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.handle(: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"(extension in Swift):Swift.SwiftNewtypeWrapper< where A: Swift.Hashable, A.Swift.RawRepresentable.RawValue: Swift.Hashable>.hashValue.getter : Swift.Int", referenced from:
protocol witness for Swift.Hashable.hashValue.getter : Swift.Int in conformance __C.UIApplicationOpenExternalURLOptionsKey : Swift.Hashable in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"Swift.Dictionary.subscript.getter : (A) -> B?", referenced from:
flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.handle(: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"Swift.Dictionary.init(dictionaryLiteral: (A, B)...) -> [A : B]", referenced from:
flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.handle(: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"base conformance descriptor for Swift._SwiftNewtypeWrapper: Swift._HasCustomAnyHashableRepresentation", referenced from:
protocol conformance descriptor for __C.UIApplicationOpenExternalURLOptionsKey : Swift._SwiftNewtypeWrapper in __C_Synthesized in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"_swift_getObjectType", referenced from:
static flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.register(with: __C.FlutterPluginRegistrar) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"swift_getInitializedObjCClass", referenced from:
type metadata accessor for __C.FlutterMethodChannel in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
type metadata accessor for flutter_app_upgrade.SwiftFlutterAppUpgradePlugin in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.handle(: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"Swift.bridgeAnythingToObjectiveC(A) -> Swift.AnyObject", referenced from:
reabstraction thunk helper from @escaping @callee_unowned @convention(block) (@unowned Swift.AnyObject?) -> () to @escaping @callee_guaranteed (@in_guaranteed Any?) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"type metadata for Any", referenced from:
flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.handle(: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
"Swift.String.init(builtinStringLiteral: Builtin.RawPointer, utf8CodeUnitCount: Builtin.Word, isASCII: Builtin.Int1) -> Swift.String", referenced from:
static flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.register(with: __C.FlutterPluginRegistrar) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
flutter_app_upgrade.SwiftFlutterAppUpgradePlugin.handle(: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in libflutter_app_upgrade.a(SwiftFlutterAppUpgradePlugin.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Pods-Runner-eildaiovnuitqoaoprmuyblcyyyf
note: Using new build system
note: Building targets in parallel
note: Planning build
note: Constructing build description
Could not build the application for the simulator.
Error launching application on iPhone 11 Pro Max.

设置项目支持swift


text:
🛑 Mailsystem External is down

In 7b77fc7, Mailsystem External ($MAIL_EXT) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Mailsystem External is back up in 81ff4a5 after 9 minutes.


text:
Fails to re-generate dt.img

I updated the hikey960 kernel recently and found it fails to re-generate the dt.img
./mkdtimg -d hi3660-hikey960.dtb -s 2048 -c -o dt_test.img
Traceback (most recent call last):
File "./mkdtimg", line 159, in
main()
File "./mkdtimg", line 153, in main
dtimg_head_info = dt_head_info('HSDT', dtimg_version, dtb_count)
TypeError: expected bytes, str found

This is because you are using python 3.x.
Try python 2.7

Thanks. It resolved.

authors: cloverpop docularxu


text:
recipes/profiler.py 번역

문서 URL
번역을 하실 / 요청하실 URL을 남겨주세요. (예. https://tutorials.pytorch.kr/beginner/saving_loading_models.html)

URL:https://github.com/9bow/PyTorch-tutorials-kr/blob/master/recipes_source/recipes/profiler.py

(대략적인) 예상 완료 일정
예상하시는 완료 일정이 있으시다면 알려주세요. (예. 1달 내, 12월 중 등)
(반드시 지키셔야 하는 일정이 아닙니다 - 일정이 너무 늦어질 경우 다른 번역자를 위해 남겨주세요.)
8월 8일
관련 이슈
현재 번역 요청 / 진행 내역을 보기 위해 각 버전의 메인 이슈를 참조합니다.
(특별한 일이 없다면 수정하지 않으셔도 됩니다.)
#90 (v1.6)

감사합니다! 레시피의 경우에는 레시피 목록의 설명도 함께 번역이 돼야 합니다.
번역하시려는 레시피에 해당하는 설명도 함께 번역하여 PR 부탁드립니다. :)

컨트리뷰톤 리뷰 진행하였습니다.

컨트리뷰톤 리뷰 진행하겠습니다


text:
Intermediate source/quantized transfer learning tutorial.rst 번역 (#135)

라이선스 동의
변경해주시는 내용에 BSD 3항 라이선스가 적용됨을 동의해주셔야 합니다.
더 자세한 내용은 기여하기 문서를 참고해주세요.
동의하시면 아래 [ ]를 [x]로 만들어주세요.

[x] 기여하기 문서를 확인하였으며, 본 PR 내용에 BSD 3항 라이선스가 적용됨에 동의합니다.

관련 이슈 번호
이 Pull Request와 관련있는 이슈 번호를 적어주세요.
이슈 또는 PR 번호 앞에 #을 붙이시면 제목을 바로 확인하실 수 있습니다. (예. #999 )

이슈 번호: #135

PR 종류
이 PR에 해당되는 종류 앞의 [ ]을 [x]로 변경해주세요.

[ ] 오탈자를 수정하거나 번역을 개선하는 기여
[x] 번역되지 않은 튜토리얼을 번역하는 기여
[ ] 공식 튜토리얼 내용을 반영하는 기여
[ ] 위 종류에 포함되지 않는 기여

PR 설명
이 PR로 무엇이 달라지는지 대략적으로 알려주세요.
Intermediate source/quantized transfer learning tutorial.rst 번역

고생 많으셨습니다! 👍


text:
🛑 coderank is down

In 354de1b, coderank (https://profile.codersrank.io/user/9renpoto/) was down:

HTTP code: 503
Response time: 592 ms

Resolved: coderank is back up in c3b30e2 after 8 minutes.


text:
🛑 threads is down

In 671b708, threads (https://www.threads.net/@9renpoto) was down:

HTTP code: 429
Response time: 314 ms

Resolved: threads is back up in 3f59c68 after 46 minutes.


text:
🛑 threads is down

In c816d57, threads (https://www.threads.net/@9renpoto) was down:

HTTP code: 429
Response time: 267 ms

Resolved: threads is back up in 93dc741 after 11 minutes.


text:
🛑 instagram is down

In bda78fa, instagram (https://www.instagram.com/9renpoto/) was down:

HTTP code: 429
Response time: 318 ms

Resolved: instagram is back up in 06a56df after 8 minutes.


text:
🛑 instagram is down

In 711f560, instagram (https://www.instagram.com/9renpoto/) was down:

HTTP code: 429
Response time: 201 ms

Resolved: instagram is back up in e5f4cff after 7 minutes.