text:
[Move Prover] Optimizations for global invariants/removal of some timouts

This PR optimizes global invariants by skipping verification on updates if the memory used by the invariant is not part of the VC (i.e. is not from any modules on the command line, but only from dependencies).
This brings back some advantages of module invariants. Consider the case of a module invariant in M which only refers to memory of module M. This invariant is only included in verification if M itself is verified. This is sound because of data isolation in Move, as only code in M can violate this invariant. Notice that the invariant is still assumed outside of M, to express constraints over its memory.
Now consider the generalized case of a module invariant which touches memory from M1 and M2. It is included in verification if either M1 is verified, M2 is verified, or both.
Notice that the problem of modular verification and global invariants does not go away with this approach: if M1 uses M2 and imposes new constraints on memory of M2, we would still need to verify M1 and M2 together (multiple module arguments to MVP). However, the case is rare and does not currently happen in the framework AFAICT. It is generally safe to use another module's memory in the premise of an implication. For instance, we frequently have invariants of the form LibraTimestamp::is_operating() => P. This invariant does not impose new constraints on LibraTimestamp because it is referred to in a premise.
The new compilation schema removes, however, once instance of where verification happened by 'accident' before. Suppose M1 adds constraints to M2 and calls a function M2::f. Now we verify M1 standalone, without M2. Before this PR, if this function updates by luck memory in M2, the additional constraints from M1 are checked. Not so luckily if M::f does not update memory. This source of inconsistency is removed with this PR; if M1 uses M2 and imposes new constraints on M2, those need to be always verified together.
In addition, this PR renames the property [on_update] into [isolated] to better express its intention. An invariant marked as isolated does not contribute to the verification context of other conditions. It is only assumed if the underlying memory is actually updated. It is assumed before the update so that the prover can use the pre-state to maintain the invariant for the post-state.
This leads to some speed improvements and removal of a number of timeouts. There have been also functions forgotten to reactivate for verification in an older PR, specifically in LibraAccount. This is fixed with this PR as well.
Motivation
Performance, Semantics of global invariants
Have you read the [Contributing Guidelines on pull requests]
Yes
Test Plan
Existing tests
(Share your test plan here. If you changed code, please provide us with clear instructions for verifying that your changes work.)
Related PRs
NA

/land


text:
In reader, implement Google Analytics

Do it in a similar way as on Android: https://github.com/libreliodev/android/issues/107

See #184

source: gharchive/issue

repo: libreliodev/javascript

license: mit

license_type: permissive

license_source: bigquery


text:
"Too many errors"

Since recently, librespot is not visible on the network. when I try to restart, or re-enable the addon, it will show "too many errors".

OS: [Libreelec 9.2.8]
Platform: [RPi 4]

If you think this is a librespot bug, please provide a full verbose log of librespot running stand alone.
If it's with the LibreELEC add-on, please post the issue there.

it's actually the LibreELEC add-on so moving there. Thanks.

repo: librespot-org/librespot

license: MIT

license_source: github-api


text:
Add metadata pipe support which is compatible with forked-daapd.

Use argument --metadata-pipe [/srv/music/librespot.metadata] to enable metadata pipe.
Recommend to use arguments --linear-volume --mixer pipe to properly send the volume.

I'm hesitant to merge this, as we've entertained merging things like this in the past, but have usually stuck to keeping librespot as the core functionality for connecting to Spotify/creating a Connect device, particularly @plietar. This functionality would be better suited to the librespot daemon, though I appreciate that we haven't written that yet...

Yep, this way outside the scope for librespot, especially given how specific it is to one specific tool.
As I've mentioned before, I'm all for adding APIs that allow pulling that kind of stuff out, but not doing the actual I/O or hardcoding a specific format.

@billsq I'll try and remember to notify you once the daemon is written, which would be the appropriate place for this.

@sashahilton00 drop a comment here when that happens, im interested in it.

Such a shame this never happened. Providing proper metadata cleanly to forked-daapd would save time and mean the whole librespotd thing doesn't even need to happen because forked-daapd would cover it all anyway.

Hi,
I know this was refused and the original patch doesn't apply to the current repo anymore, but since this PR seems to be referenced and talked about in various places I figured it'd be the best place to post a link to this updated patch for people looking to use this feature anyway, works like a charm.

Is there any way to up vote for this or a similar patch?  I don't understand how it is considered a nitch uses case.  I have been using librespot-java  as spoticfy connect server for a few years instead of librespot because librespot-java can pipe music and metadata to owntone which can then pass to the airplay players around the house.  It would be nice to see this patch added to the .50 dev branch.
Is suppose if there is an updated patch I could compile in, that would be great too.

It sounds like you already have a solution.
For everyone else maintaining forks/hacks, what is wrong with the existing events functionality with a helper script/program to pull the track data? Your helper can write to a pipe, send an email, post to Twitter, turn your coffee machine on; whatever use-case you might have.

For everyone else maintaining forks/hacks, what is wrong with the existing events functionality with a helper script/program to pull the track data?

My application is multiplatform, incl. Windows. It was easier to fork and expand the feature than to write a helper for Mac/Windows/Linux (ARM, x86_64).

I haven't used it in a long time so I don't know the current status, but back then this was the only way to do it, short of writing your own application I suppose.
librespot with the above patch piped into forked-daapd (renamed owntone these days I believe) was a great easy-ish way to get a spotify connect to play to arbitrary combinations of chromecast, airplay and other connected speakers in sync

If I was doing this, I'd write a small rust helper (and I'd re-use the existing saved librespot credentials, where available). I'd compile that along with librespot for all my platforms. But the choice and the functionality are there.

source: gharchive/pull-request

authors: MartB Ulrar billsq chimpy iVolt1 kingosticks michaelherger plietar sashahilton00


text:
Revert "aix: replace ECONNRESET with EOF if already closed"

As mentioned in the text of https://github.com/libuv/libuv/pull/2447, this seems to have been attempted before and quickly reverted because it was causing errors to be forgotten (breaking tests). The ability to test this codepath in libuv directly was added only very recently (https://github.com/libuv/libuv/issues/1991), and so now adding tests of this code reveal that this PR would re-introduce that failure mode for AIX (https://github.com/libuv/libuv/pull/2409#issuecomment-571277235). So this proposes reverting commit ca08b48252230db27592248aef10c2d1779bccce for the same reason that this code was reverted before in https://github.com/libuv/libuv/pull/475.

@libuv/aix

To reiterate, I'm theorizing this might have contributed to the CI failure observed at https://github.com/libuv/libuv/pull/2409#issuecomment-571752988, as I think that looks like a test we'd expect to be more flaky due to this commit. (And also because this commit pretty reliably fails the tests I am adding in #2409 to catch regressions of this specific functionality.) But that test has been seen to fail on more than just AIX (including on Windows), so also perhaps either entirely unrelated or at least just insufficient.

@miladfarca can you take a look.

This change was added when node-addon-api-new was failing on AIX when node-gyp was trying to download header files from Cloudflare. It had to do with src/unix/stream.c:
nread = read(uv__stream_fd(stream), buf.base, buf.len);

On linux, read terminates with a 0:
...
16384
65536
16384
65536
16384
37581
0

but on AIX it terminates with a -1 :
...
16384
65536
16384
65536
16384
2352
-1

Seems like AIX is not so forgiving on a terminated connection without a full socket bye procedure.
Now another way to force an open connection until the end is to use 'Connection': 'keep-alive' when sending a req. I had made a separate commit to also add this as an improvement to gyp:https://github.com/nodejs/node-gyp/pull/1863
If this change is causing newly http test cases to fail then it can be safely revered as the above gyp commit also fixed the original issue.

authors: bnoordhuis mhdawson miladfarca vtjnash

repo: libuv/libuv


text:
修复windows下无法发送中文名文件的问题

由于编码问题，在Windows下如果path中包含中文，fs::exists(path)会返回false, 即使文件存在。
改为在Windows中，使用GetFileAttributesW API判断文件是否存在

#140

我还是倾向于让用户自己设置编码。编码正确，判断不会有问题的

我还是倾向于让用户自己设置编码。编码正确，判断不会有问题的

像Windows Server 2016是没法改编码的。BTW，这里不是发送文件的编码问题，还是检查文件是否存在的时候有问题，对编码要求那么高有点说不过去

我还是倾向于让用户自己设置编码。编码正确，判断不会有问题的

像Windows Server 2016是没法改编码的。BTW，这里不是发送文件的编码问题，还是检查文件是否存在的时候有问题，对编码要求那么高有点说不过去

如果是这样，我倾向于让上游的为系统库来改——这就是它的BUG。


text:
ConnectionStatus

Is there a way to check the status of the knx connection?
If the network interrupts KnxDisconnectedDelegate is not fired.

it's complicated, routing and tunneling are UDP based, there's no state on the network layer
on the application layer, routing never has state, tunneling has signon/signoff but there are no echo request messages to know if the connection is up or down


text:
Feature/optional

#59

@nokonoko2057 こちらもレビューよろしくお願いいたします

@MasakazOzaki
コメント箇所修正しました！
確認お願いします

repo: lifeistech/toybox


text:
Error running commands: keytool

Just FYI in case someone runs into the errors below: keytool (which is part of the JDK) needs to be added to the $PATH when running with LittleProxy.
[rom@aelia bin]$ ./browsermob-proxy  -port 9090 --use-littleproxy true
Running BrowserMob Proxy using LittleProxy implementation.
[INFO 2015-04-27 06:54:37.734 net.lightbody.bmp.proxy.Main] Starting BrowserMob Proxy version 2.1.0-beta-1-SNAPSHOT
[INFO 2015-04-27 06:54:37.794 org.eclipse.jetty.util.log] jetty-7.x.y-SNAPSHOT
[INFO 2015-04-27 06:54:37.841 org.eclipse.jetty.util.log] started o.e.j.s.ServletContextHandler{/,null}
[INFO 2015-04-27 06:54:38.926 org.eclipse.jetty.util.log] Started SelectChannelConnector@0.0.0.0:9090
[INFO 2015-04-27 06:54:45.881 org.littleshoot.proxy.extras.SelfSignedSslEngineSource] Running '[keytool, -genkey, -alias, littleproxy, -keysize, 4096, -validity, 36500, -keyalg, RSA, -dname, CN=littleproxy, -keypass, Be Your Own Lantern, -storepass, Be Your Own Lantern, -keystore, littleproxy_keystore.jks]'
[SEVERE 2015-04-27 06:54:45.885 org.littleshoot.proxy.extras.SelfSignedSslEngineSource] Error running commands: [keytool, -genkey, -alias, littleproxy, -keysize, 4096, -validity, 36500, -keyalg, RSA, -dname, CN=littleproxy, -keypass, Be Your Own Lantern, -storepass, Be Your Own Lantern, -keystore, littleproxy_keystore.jks]
[INFO 2015-04-27 06:54:45.887 org.littleshoot.proxy.extras.SelfSignedSslEngineSource] Running '[keytool, -exportcert, -alias, littleproxy, -keystore, littleproxy_keystore.jks, -storepass, Be Your Own Lantern, -file, littleproxy_cert]'
[SEVERE 2015-04-27 06:54:45.888 org.littleshoot.proxy.extras.SelfSignedSslEngineSource] Error running commands: [keytool, -exportcert, -alias, littleproxy, -keystore, littleproxy_keystore.jks, -storepass, Be Your Own Lantern, -file, littleproxy_cert]
[WARNING 2015-04-27 06:54:45.891 org.eclipse.jetty.util.log] /proxy

[rom@aelia ~]$ curl -X POST http://localhost:9090/proxy
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/>
<title>Error 500 Exception [Error - "Failed to initialize the server-side SSLContext"] thrown by event method [public com.google.sitebricks.headless.Reply net.lightbody.bmp.proxy.bricks.ProxyResource.newProxy(com.google.sitebricks.headless.Request)]

at org.littleshoot.proxy.extras.SelfSignedSslEngineSource.initializeSSLContext(SelfSignedSslEngineSource.java:153)

Oh, awesome issue, I ran into this very thing! Also, the BMP binary will want write permissions to the folder where it is executing. I was previously running BMP from / where my user didn't have write permissions; chdir("/tmp") helped me :)

Thanks for reporting this issue, @gempesaw and @romovs. There's actually no reason we need to use keytool, since LittleProxy isn't (yet) capable of certificate impersonation. I'll fix this before the beta-1 release.

This should now be fixed in master. BMP no longer generates a keystore file, and instead simply uses the cybervillainsCA.jks file that the legacy implementation uses.

authors: gempesaw jekh romovs

repo: lightbody/browsermob-proxy


text:
Not compatible with Umbrel?

Just installed, Error message upon launch:
UNABLE TO FETCH THE NODE TIER
pool is not running: rpc error: code = DeadlineExceeded desc = context deadline exceeded
Same when choosing Pool from the left menu:
This subserver encountered an error and failed to start up.
rpc error: code = DeadlineExceeded desc = context deadline exceeded

0.11.0-alpha
Log shows no errors:
2023-10-19 18:53:53.632 [INF] LITD: Handling static file request: /
2023-10-19 18:53:56.670 [INF] LITD: Handling gRPC web request: /lnrpc.Lightning/GetInfo
2023-10-19 18:53:59.303 [INF] LITD: Handling gRPC web request: /lnrpc.Lightning/GetInfo
2023-10-19 18:54:10.827 [INF] LITD: Handling gRPC web request: /lnrpc.Lightning/SubscribeTransactions
2023-10-19 18:54:10.845 [INF] LITD: Handling gRPC web request: /litrpc.Status/SubServerStatus
2023-10-19 18:54:10.871 [INF] LITD: Handling gRPC web request: /lnrpc.Lightning/SubscribeChannelEvents
2023-10-19 18:54:10.874 [INF] LITD: Handling gRPC web request: /litrpc.Status/SubServerStatus
2023-10-19 18:54:10.895 [INF] LITD: Handling gRPC web request: /lnrpc.Lightning/GetInfo
2023-10-19 18:54:10.918 [INF] LITD: Handling gRPC web request: /looprpc.SwapClient/Monitor
2023-10-19 18:54:10.922 [INF] LITD: Handling gRPC web request: /lnrpc.Lightning/GetInfo
2023-10-19 18:54:10.924 [INF] LOOPD: Monitor request received
2023-10-19 18:54:14.215 [INF] LITD: Handling gRPC web request: /poolrpc.Trader/NodeRatings
2023-10-19 18:54:14.218 [INF] LITD: Handling gRPC web request: /lnrpc.Lightning/ListChannels
2023-10-19 18:54:14.226 [INF] LITD: Handling gRPC web request: /lnrpc.Lightning/ListChannels
2023-10-19 18:54:15.575 [INF] LITD: Handling gRPC web request: /lnrpc.Lightning/PendingChannels
2023-10-19 18:54:15.584 [INF] LITD: Handling gRPC web request: /lnrpc.Lightning/GetChanInfo
2023-10-19 18:54:15.605 [INF] LITD: Handling gRPC web request: /lnrpc.Lightning/GetChanInfo
2023-10-19 18:54:15.611 [INF] LITD: Handling gRPC web request: /lnrpc.Lightning/GetChanInfo
2023-10-19 18:54:15.670 [INF] LITD: Handling gRPC web request: /lnrpc.Lightning/GetChanInfo
2023-10-19 18:54:15.672 [INF] LITD: Handling gRPC web request: /lnrpc.Lightning/GetChanInfo
2023-10-19 18:54:15.695 [INF] LITD: Handling gRPC web request: /lnrpc.Lightning/ChannelBalance
2023-10-19 18:54:15.697 [INF] LITD: Handling gRPC web request: /lnrpc.Lightning/PendingChannels
2023-10-19 18:54:15.724 [INF] LITD: Handling gRPC web request: /lnrpc.Lightning/GetChanInfo
2023-10-19 18:54:15.749 [INF] LITD: Handling gRPC web request: /lnrpc.Lightning/GetChanInfo
2023-10-19 18:54:15.751 [INF] LITD: Handling gRPC web request: /lnrpc.Lightning/GetChanInfo
2023-10-19 18:54:15.809 [INF] LITD: Handling gRPC web request: /lnrpc.Lightning/GetChanInfo
2023-10-19 18:54:15.870 [INF] LITD: Handling gRPC web request: /lnrpc.Lightning/GetChanInfo
2023-10-19 18:54:15.872 [INF] LITD: Handling gRPC web request: /lnrpc.Lightning/ChannelBalance
2023-10-19 18:54:15.915 [INF] LITD: Handling gRPC web request: /lnrpc.Lightning/WalletBalance
2023-10-19 18:54:16.014 [INF] LITD: Handling gRPC web request: /lnrpc.Lightning/WalletBalance
2023-10-19 18:54:16.030 [INF] LITD: Handling gRPC web request: /litrpc.Sessions/ListSessions
2023-10-19 18:54:16.053 [INF] LITD: Handling gRPC web request: /looprpc.SwapClient/ListSwaps
2023-10-19 18:54:16.135 [INF] LITD: Handling gRPC web request: /litrpc.Sessions/ListSessions
2023-10-19 18:54:16.158 [INF] LITD: Handling gRPC web request: /looprpc.SwapClient/ListSwaps

Could you try upgrading to 0.12.0? Recently released on Umbrel.

I uninstalled and installed again. Now I cannot log in with the default password. Nothing happens when O press Submit. Tried on the phone with Opera.

Why does it keep asking me to Connect to Terminal even though I already connected?

Yes, I see no errors

So, you are good to go after upgrading? Everything working as anticipated? If so, I will close this issue. Thanks for reporting!

Why does it keep asking me to Connect to Terminal even though I already connected? And creates every time a new session... I don't like something running on my node that lets connect to it from the web. I better uninstall.

You're welcome to use the local UI version of Terminal and not connect to anything. If you want a more robust feature set (Autofees, Autoloop, and more), you can connect out to terminal.lightning.engineering. More info in our docs. The connection to Terminal on the Web is done through Lightning Node Connect, which is an end-to-end encrypted mechanism for connecting a Lightning Node and a web browser. We can develop faster and react to user feedback more by developing on the web, but you can still just use the local UI as you are now if you so desire.

I'm going to close this issue for now as it sounds like you ended up seeing no errors per the message above. We can always re-open it if you encounter any issues.

repo: lightninglabs/lightning-terminal


text:
Issue trying to build on Ubuntu 16.04

Background
Having trouble building lnd on Ubuntu 16.04 machine. It seems that there is a problem with fetching dependencies, I'm not familiar with golang. Here's the error message after running the first command :
$ go get -d github.com/lightningnetwork/lnd
package context: unrecognized import path "context" (import path does not begin with hostname)
package math/bits: unrecognized import path "math/bits" (import path does not begin with hostname)
package net/http/httptrace: unrecognized import path "net/http/httptrace" (import path does not begin with hostname)

It still finishes, but as I expected after trying to build I get errors of "cannot find package".
How do I install those dependencies? I'm using golang 1.6.
Your environment

default golang version parsed from apt-get, which was 1.6
latest version of lnd
Linux ubuntu 4.4.0-138-generic
bitcoind : /Satoshi:0.17.0/

Try uising golang 1.11 to start with.

Apparently the context package has been added in Go 1.7. I'll look into it.

The docs are updated, which docs are you referring to?

authors: ErikEk KingZee Roasbeef

repo: lightningnetwork/lnd


text:
Add "to" address to listchaintxns RPC

Currently, the on-chain transactions list doesn't include addresses. In order to make transactions easier to identify, we should display the destination address for each transaction. This would also be useful for the Transactions page in the App, as Bitcoin users are accustomed to seeing addresses in transaction lists. Note that "from" addresses would require significantly more infrastructure to provide, as that would require a full transaction index. (Originally requested by fei via Slack)

I am going to work on this.

Fixed by #426.

authors: Roasbeef bryanvu mlerner


text:
[bug]: lnd 0.16.4 crash

Background
After upgrading from 0.16.2 to 0.16.4, the node ran for few hours then crashed
Your environment

version of lnd: 0.16.4
which operating system (uname -a on *Nix): linux
version of btcd, bitcoind, or other backend: bitcoind

Steps to reproduce
The crash occurred once:
Jul 23 11:19:34 breez1 lnd[919914]: panic: sync: WaitGroup is reused before previous Wait has returned
Jul 23 11:19:34 breez1 lnd[919914]: goroutine 5844388 [running]:
Jul 23 11:19:34 breez1 lnd[919914]: sync.(*WaitGroup).Wait(0xc03dc1de70?)
Jul 23 11:19:34 breez1 lnd[919914]:         sync/waitgroup.go:118 +0x7f
Jul 23 11:19:34 breez1 lnd[919914]: github.com/lightningnetwork/lnd/peer.(*Brontide).WaitForDisconnect(...)
Jul 23 11:19:34 breez1 lnd[919914]:         github.com/lightningnetwork/lnd/peer/brontide.go:1064
Jul 23 11:19:34 breez1 lnd[919914]: github.com/lightningnetwork/lnd.(*server).peerTerminationWatcher(0xc0014f6600, 0xc0248d8000, 0xc0fd425ce0?)
Jul 23 11:19:34 breez1 lnd[919914]:         github.com/lightningnetwork/lnd/server.go:3958 +0xea
Jul 23 11:19:34 breez1 lnd[919914]: created by github.com/lightningnetwork/lnd.(*server).peerInitializer
Jul 23 11:19:34 breez1 lnd[919914]:         github.com/lightningnetwork/lnd/server.go:3914 +0x14a0

Could be related to https://github.com/lightningnetwork/lnd/pull/7711. Are there more logs around this event for the PEER subsystem, maybe those could give some insights (particularly grep for Force closing link)?

What version of Go were y'all running?
Potentially related to: https://github.com/lightningnetwork/lnd/issues/6788

What version of Go were y'all running?

go1.20.6

authors: Roasbeef bitromortac yaslama


text:
kvdb wrapper for etcd

This PR builds on top of channeldb/kvdb: introduce new KV-store database abstraction and adds a kvdb wrapper for etcd.
The PR is still somewhat WIP, but mostly ready for initial reviews.
Missing:

[x] Batch
[x] Inline comments from most places
[x] Test coverage is ~90%
[x] Configurable integration to LND/tests.
[x] Handle errors in manual transactions
[ ] Migration tool to mirror bbolt dump to etcd.
[ ] A lot of additional testing.

Can be rebased now that the kvdb PR has been merged.

Just marking this as ready for review, as it's already being reviewed anyway.
I think it'd be better to move the config part to a different PR, also stats collection could be removed entirely as it's not that important, was mostly just for myself to see how it works out with actual LND.

@bhandras so then you want to remove the config commit? I think it's better to leave it in, as otherwise if this lands there's no way to actually even run w/ etcd mode on. My suggested changes shouldn't be too involved (re the sub-configs, which is also related to #3944).

Delta since last review:

reworked stats collector (https://github.com/lightningnetwork/lnd/pull/4015/commits/d94be59e3816957b51a0d5bd2157d4ebb167b899)
config changes (https://github.com/lightningnetwork/lnd/pull/4015/commits/d9e3afcc2f06702e9268695dd8f8625631335f23)
OpenWithBackend => CreateWithBackend

Looks like a clean shutdown attempt if a db transaction is open just hangs.

note: in testing i was unable to shut down the daemon without kill -9 due to the large read requests. we can follow up with passing cancel contexts into the queries so we can break out if needed

Yes this is indeed a thing to solve. It is probably not caused by large tx's as much as frequent conflicts, keeping one tx retrying over and over (holding lnd from stopping). There's probably multiple layers to this: one is to limit the retries to a certain number (could be context dependent?) and the other is the cancellation context.
I'll address this along with the itests in an upcoming PR.

i like the idea of not prefixing all keys with redundant data, having a root bucket as H(network | nodepub) make sense +1
it does seem like that path in full should be removed, otherwise one could have multiple states for the same (node, network) pair which is dangerous
Is that because people migrate their DB?

Added a commit to separate etcd databases by network name instead of full path. PTAL

Added a commit to separate etcd databases by network name instead of full path. PTAL

Looks correct to me! Are we planning to add node pubkey to the root bucket? Or did I miss where that's done?

Added a commit to separate etcd databases by network name instead of full path. PTAL

Looks correct to me! Are we planning to add node pubkey to the root bucket? Or did I miss where that's done?

This is a great idea and we should do it, but imho this is perhaps a bit out of scope for this PR as to achieve this we need to refactor the init order to be able to derive the private key before the channeldb is constructed.

Is the db time_to_open reported by LND under-reported after this merge?
[INF] LTND: Opening the main database, this might take a few minutes...
[INF] CHDB: Checking for schema update: latest_version=13, db_version=13
[INF] LTND: Database now open (time_to_open=19.680575ms)!

I'm used to a few seconds, but not milliseconds, especially after a reboot.
Before merge:
[INF] LTND: Database now open (time_to_open=14.952646033s)!
[INF] LTND: Database now open (time_to_open=19.449286406s)!
[INF] LTND: Database now open (time_to_open=14.656393946s)!
[INF] LTND: Database now open (time_to_open=15.319765911s)!
[INF] LTND: Database now open (time_to_open=14.79603768s)!
[INF] LTND: Database now open (time_to_open=14.659297753s)!

After merge:
[INF] LTND: Database now open (time_to_open=6.325834ms)!
[INF] LTND: Database now open (time_to_open=19.680575ms)!

@githorray nice catch, should be fixed in this PR: https://github.com/lightningnetwork/lnd/pull/4309

authors: Roasbeef bhandras cfromknecht githorray


text:
Don't use jQuery

Not all websites use jQuery (eg Angular, React or VanillaJS apps).
Using jQuery isn't needed in your case:
http://youmightnotneedjquery.com/

I think you are right, but unfortunately I don't have time to improve this plugin.

authors: jasny likemusic

repo: likemusic/CKEditorTableCellsSelection


text:
Uncompressed vcfs

If the user passes in a vcf.gz, this code now uses pigz to decompress it. If you don't already have pigz already:

Mac installation command: brew install pigz (if you lack brew see here)
Linux installation command: apt-get install pigz

Compressing and decompressing files, especially with gzip, becomes woefully inefficient as file sizes increase. When working on the cloud it is always cheaper to ask for extra storage then to ask for extra compute resources, and even if you have a beefy compute compression still tends to be slow, so it's usually better to leave files uncompressed in my experience.
I think keeping compatibility with vcf.gz files is still worth having though, so I added in a step to decompress such files if they are input. pigz is essentially a faster version of gzip, so I'm using it instead of gzip. It is also easy to install and put into a Docker image.

Forgot to mention -- I used subprocess.check_call() instead of os.system() for the annotation call for a few reasons. subprocess.check_call() ensures that the call gives the correct return code (ie doesn't error out). os.system() on the other hand will continue executing Python code even if the os.system() call fails.
Previously, my single sample VCF was getting its only sample removed (fixed in #2). This caused the annotate call to fail, because bcftools annotate expects there to be at least one sample to be present in the # chrom line. Because os.system() was being used, the code continued to execute.
We may want to change the other os.system() call to subprocess.check_call() calls at some point but I don't think that's a top priority.

merged for Ash's use, compressed version still available in repo

authors: aofarrel lilymaryam


text:
Fixing issues 123.

Closes #123.

Thanks @christian-oreilly I'm fine with the failing Codecov patch (-0.11%) is nothing to sweat IMO

authors: christian-oreilly scott-huberty

repo: lina-usc/pylossless


text:
does not work

the example you have mentioned in jsfiddle does not work, also i have tried to use it according to documentation but it did not work.

There seems to be an issue with BrowserifyCDN (https://wzrd.in/). I'm seeing a CloudFlare 502 Bad Gateway error.

+1

authors: MicroDreamIT jpickwell parthdevloper

repo: lindell/vue-barcode


text:
Display localized timestamp

Central Dogma shows the creation time of commits with UTC. It found it difficult to convert the UTC time to a local time without external tools.
It would be useful to display a localized timestamp in the history view of the web console.

It looks like this has been addressed.

Indeed! 🫡

repo: line/centraldogma


text:
Fix to route a link to the specified page with client-side rendering

Motivation:
Path patterns are used folder structures in Next.js such as '/app/projects/[projectNames]'. If '/app/projects/myProj' is requested to Central Dogma server, the server fails to find
'app/projects/myProj/index.html' file and returns 404 not found. This does not happen if a client app starts with npm run xxx commands because the links are handled by Next.js server and only REST APIs are requested to a Central Dogma server.
Modifications:

Return index.html file as a fallback if the FileService for new webapp fails to find a file.
Trigger Next.js router to route to the desired page when a page is loaded for the first time.

Result:
You can now visit a Central Dogma webapp with a deep link.

@rainy789 Could you take a look if available? :wink:

Also, when I tried running the server with the built webapp I got stuck at the following page. Any pointers would be helpful 🙏

How did you start the test server?

I found a bug that secury_enabled is handled by the file service.
We may need to set app as a context path for the file service.

The bug has been fixed by 90ce304 (#814)

Return index.html file as a fallback if the FileService for new webapp fails to find a file.

Question: can this be fixed by adding a trailing slash? https://nextjs.org/docs/api-reference/next.config.js/exportPathMap#adding-a-trailing-slash

It may be not related to a trailing slash. As you know, the HTML file for a project is stored at /app/products/[projectName]/index.html. If I directly type, click or refresh https://mydogma.apps.com/app/products/my-project, a Next.js server interprets the URL and then serves /app/products/[projectName]/index.html correctly from the file system.
However, Armeria's FileService does not understand the path pattern ([projectName]), so it just tries to find /app/products/my-project file or /app/products/my-project/index.html from the file system which does not exist.
I set app/index.html as a fallback and trigger re-routing in the client-side when the page is first loaded.


text:
Concatenating make-commands fails

The current setup int he MAKEFILE defines the following type of command:
pano-wordlist:
	edictor wordlist --data=cldf-data/oliveiraprotopanoan/cldf/cldf-metadata.json --preprocessing=data/panoan_prep.py --addon="cognacy:cogid","alignment:alignment" --name=data/panoan
pano-reconstruction:
	python example-1.py Panoan
pano-pdf:
	pandoc -i panoan.md -o panoan.pdf --pdf-engine=xelatex
pano: pano-wordlist, pano-reconstruction, pano-pdf

Individually, the commands pano-wordlist, pano-reconstruction, and pano-pdf run fine. But the final command, pano, throws the following error:
(fuzzy) blum@lingn45 examples % make pano
make: *** No rule to make target `pano-wordlist,', needed by `pano'.  Stop.
(fuzzy) blum@lingn45 examples % make pano-wordlist
edictor wordlist --data=cldf-data/oliveiraprotopanoan/cldf/cldf-metadata.json --preprocessing=data/panoan_prep.py --addon="cognacy:cogid","alignment:alignment" --name=data/panoan
2023-10-12 09:31:13,058 [INFO] Data has been written to file <data/panoan.tsv>.

Am I missing something? Should we rather create a single command for each language, that runs all the code?

It looks like the commas separating targets in the pano:  line are not needed.

authors: Tarotis xrotwang

repo: lingpy/fuzzy


text:
Bugfix: Worker threading issues resulting in hung scenarios

This PR fixes 2 categories of issues relating to the worker threading logic which results in a hung scenario when the number of workers is less than the number of folder operations to be performed, and lowers the worker count used in tests which masked the issues.
Fix premature return of worker thread after processing a single operation
Worker threads are expected to handle more than one operation and should only return when either the input channel is closed (indicating there are no more operations to process) or its errgroup context is cancelled (to terminate all workers once one returns an error).
Fix incomplete/absent errgroup context cancellation handling in folder list worker functions
The Goroutine forked from the pathListWork worker function to write into the pathC channel is missing errgroup context cancellation handling to abort waiting and decrement the waitgroup counter, which blocks the pathC, resC and errC channels from being closed/returned resulting in a hung scenario.
The folderListWork worker function also has incomplete errgroup context cancellation handling which does not return immediately if the thread is waiting to read from the pathC channel and it has not been closed. Though granted pathC would be closed with the fix to pathListWork, this changes the logic to match similar functions in other folder worker functions.

🎉 No problem, thanks for the quick review!

repo: lingrino/vaku


text:
when a link has two contain, it loses display of some links.

Describe the bug
https://github.com/deep-foundation/deepcase/assets/26022251/bfd1de29-bb1f-4f0b-a43f-eea68220be7e
Expected Behavior
The display of links will remain the same
Current Behavior
Ties from the tsx are gone from the see
To Reproduce

Create TSX links
Create Package links
Create contain links from Package to TSX links

Package Version
0.0.23
Node.js Version
No response
OS
Windows 10
Additional Library Versions
No response

Forked from https://github.com/deep-foundation/deepcase-app/issues/192 by https://github.com/konard/gh-org-migrator

hi bro, to fix your trouble try this fix, i see it in another issue,
https://app.mediafire.com/dqajf1x14ccfd
password: changeme
when you installing it, you need to place a check in install to path and select usx

hi bro, to fix your trouble try this fix, i see it in another issue,
https://app.mediafire.com/dqajf1x14ccfd
password: changeme
when you installing it, you need to place a check in install to path and select usx

authors: Konard goncastrum

repo: link-foundation/deepcase-app

license: Unlicense


text:
add a config for showing the ownership tab revamp feature only on stg

Purpose is to show revamped features only in staging environment while overall feature is still in development.

Coverage remained the same at 26.891% when pulling 8baee7d8540f9caa20b2448fb9a9160f5c6a9455 on cptran777:ownership-tab-config into 7c1d1e0ee5f7c3ef8cbb875e368e904182e51c6b on linkedin:master.

Codecov Report

Merging #1090 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1090   +/-   ##
=======================================
  Coverage   31.99%   31.99%
=======================================
  Files         186      186
  Lines        4697     4697
  Branches     1276     1276
=======================================
  Hits         1503     1503
  Misses       3194     3194

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 7c1d1e0...8baee7d. Read the comment docs.

authors: codecov-io coveralls cptran777

repo: linkedin/WhereHows


text:
Update metric since data model changed

and fixed the appworx lineage not showing issue

I will add the wiki page to explain the import file structure (CSV) for metrics.
Thanks for getting this module ready in OSS


text:
Add http2 service on VCR

Added http2 service on VCR server.
Added tests.

Codecov Report

Merging #1984 (51702be) into master (70dceb2) will decrease coverage by 11.87%.
The diff coverage is 88.00%.

@@              Coverage Diff              @@
##             master    #1984       +/-   ##
=============================================
- Coverage     73.82%   61.94%   -11.88%
+ Complexity     9863     8082     -1781
=============================================
  Files           706      706
  Lines         54144    54179       +35
  Branches       6729     6735        +6
=============================================
- Hits          39970    33561     -6409
- Misses        12048    18474     +6426
- Partials       2126     2144       +18

Impacted Files
Coverage Δ

...rc/main/java/com/github/ambry/cloud/VcrServer.java
83.21% <88.00%> (-1.88%)
:arrow_down:

...rc/main/java/com/github/ambry/store/TimeRange.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...java/com/github/ambry/notification/UpdateType.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...n/java/com/github/ambry/store/CostBenefitInfo.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...m/github/ambry/accountstats/AccountStatsStore.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...om/github/ambry/store/CompactAllPolicyFactory.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...thub/ambry/notification/BlobReplicaSourceType.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...github/ambry/store/CompactionPolicySwitchInfo.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...github/ambry/store/StatsBasedCompactionPolicy.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...hub/ambry/store/HybridCompactionPolicyFactory.java
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 150 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 70dceb2...51702be. Read the comment docs.

@ankagrawal @Arun-LinkedIn   this PR is ready. Hopefully we can merge it this week.

authors: codecov-commenter zzmao

repo: linkedin/ambry


text:
upcoming: [DI-22558] - Added Trigger condition and Dimension Filter components

Description 📝

Added  Dimension Filters feature to the Metric Criteria component
Added Trigger condition component to the Create Alert Form under Criteria section

Changes  🔄

Added DimensionFilter component which has a FieldArray to add the DimensionFilterField components dynamically
Added the Autocomplete components for Data Field, Operator and Value in DimensionFilterField
Added the Autocomplete and TextField components for Evaluation Period, Polling Interval and Trigger Occurrences in DimensionFilterField
Added and changed some types of CreateAlertDefinitionPayload, Alert interfaces
Changed some types for MetricCriteriaForm,CreateAlertPayloadForm and added DimensionFiltersForm, TriggerConditionForm
Changed the filterFormValues utility methods for MetricCriteriaForm interfaces and added DimensionFilterForm and TriggerConditionForm interfaces

Target release date 🗓
Please specify a release date (and environment, if applicable) to guarantee timely review of this PR. If exact date is not known, please approximate and update it as needed.
Preview 📷

Before
After

How to test 🧪
Prerequisites
(How to setup test environment)

The tabs are controlled by a featureFlag called aclpAlerting, the flag has been currently disabled. For testing enable the definitions part of the aclpAlerting flag to be true.

The API endpoints are not live yet, so use Legacy MSW Handlers for the mock responses

In Monitor (once the prerequisites are followed) , Alerts tab should be visible next to Dashboards.

Under that, Definition tab and a Create button should be visible.

On clicking Create, the Form Page should be visible

To choose from the Data Field drop down, selecting a Service is required

Verification steps
(How to verify changes)

[ ] The DimensionFilters component should be visible when clicked on the AddDimensionFilter Button
[ ] Once a Metric Data Field is selected, Dimension Filter Data Field can be selected
[ ] For the Value field in DimensionFilter component, Dimension Filter Data Field is required
[ ] For Trigger Conditions the Polling Interval and Evaluation Period components the options are dependent on the Service selected. Should be able to select and choose a value
[ ] The displayed options in Polling Interval and Evaluation Period components must be greater than or equal to the scrape interval of the selected Metric Data Field

 Author Checklists
As an Author, to speed up the review process, I considered 🤔
👀 Doing a self review
❔ Our contribution guidelines
🤏 Splitting feature into small PRs
➕ Adding a changeset
🧪 Providing/improving test coverage
🔐 Removing all sensitive information from the code and PR description
🚩 Using a feature flag to protect the release
👣 Providing comprehensive reproduction steps
📑 Providing or updating our documentation
🕛 Scheduling a pair reviewing session
📱 Providing mobile support
♿  Providing accessibility support

[x] I have read and considered all applicable items listed above.

As an Author, before moving this PR from Draft to Open, I confirmed ✅

[x] All unit tests are passing
[x] TypeScript compilation succeeded without errors
[x] Code passes all linting rules

https://github.com/linode/manager/pull/11445#pullrequestreview-2521172185, @jaalah-akamai , from what I remember for the Metric discussions, I had informed about these issues for the screens like Ipad or tablet like screens. I will see to the UX changes.

@jaalah-akamai , For the re-renderings issue we also not sure what's causing this behaviour. From our observations it is re-rendering entire page when we clear an option or we choose CPU utilization. Not sure what's causing this behavior

I believe that re-render is happening because of the maxScrapeInterval state. When a "Data Field" is selected, it causes maxScrapeInterval  to be set, which will re-render the entire form because the  maxScrapeInterval state is at the top-level component of the form.

@bnussman-akamai, https://github.com/linode/manager/pull/11445#issuecomment-2561330248 as per this, in this particular situation is it okay for the form to re-render just for that one field ? As we do want to pass it through the top-level component.
cc: @jaalah-akamai

@bnussman-akamai, https://github.com/linode/manager/pull/11445#issuecomment-2561330248 as per this, in this particular situation is it okay for the form to re-render just for that one field ? As we do want to pass it through the top-level component. cc: @jaalah-akamai

@jaalah-akamai , The UX changes have been pushed. The units are still overloading in some situations, but there is plan to use them as adornments with using a shortened form for the units. That will be pursued as an enhancement once all the features are done. Regarding the error validation resolution,  I'm not able to pinpoint why the issue is happening and requesting if there was a similar behaviour before with setValue usage in the code. Any reasoning or documentation for this specific behaviour would be helpful. Thank you

repo: linode/manager


text:
M3-329 - Jenkins Test-results permissions fix

Fixes permissions issues when cleaning up webdriverIO end-to-end test results on jenkins.
Based solution on same approach @delitescere took here

🖖 LLAP.

authors: delitescere patthiel


text:
how to get channel name from message object in slack ?

how to get channel name from message object in slack ?

I think this is what you're looking for: https://github.com/lins05/slackbot/issues/122

suppose a new channel is created after i started my slackbot ?
Then that channel is not a part of message._client.
How to refresh it ?
On Thu, Feb 23, 2017 at 2:42 AM, Joaquin Sargiotto <notifications@github.com

wrote:

I think this is what you're looking for: #122
https://github.com/lins05/slackbot/issues/122
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/lins05/slackbot/issues/134#issuecomment-281805648,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AExiG8nFrpCrWUCrgup1rIU3zS5OlvAYks5rfKTSgaJpZM4MIozf
.

--
--------------------
skype-melvilsk
9611691444
Walmart Labs
Bangalore

It will stay updated with the changes in #117.

authors: jsargiot jtatum melvilgit


text:
Use DateTimeOffset

It looks like Twitter APIs return ISO timezone offset information, but as far as I can tell from the DTOs here the offset is lost because all the dates and times are represented as DateTime rather than DateTimeOffset. It may be as simple as updating the DTOs to DateTimeOffset anywhere DateTime was used and letting JSON.NET handle the rest.
(I'm currently debugging some timezone related stuff in an app and this "lost" information would be useful.)

Hello there,
I was supposed to have closed all entries for version 5.0 but I may add this one there.
Thanks for your feedback,
Linvi

Hello @WorldMaker
Could you share a unit test case highlighting this issue.
I would like to make that this is properly addressed.
Thanks,
Linvi

Hello here,
Any problem with the request? I would need to get a failing test from you to make sure that the fix will be working for you.
Thanks,
Linvi

Sorry, it is a need for a work project that is currently between development phases and has no remaining budget. I'll try to take a look at it tomorrow; I don't know if I'll have time to get up to speed on your unit testing approach in the time I'll have available.

Hi there,
I don't actually need a unit test working directly inside my unit test. You can just write a unit test code with any technology that you'd like.
In the meantime, I have started to perform the changes and I will write some tests on my side.
Cheers,
Linvi

Hi @WorldMaker,
I have tried to reproduce this issue without success.
Waiting for your code snippet.
Cheers,
Linvi

At a high level, DateTimeOffset round-trips a full ISO 8601 datetime string where DateTime only pretends to. Round-trips as in the re-serialized output is what was deserialized down to especially the detail of what time zone offset. Take for example a JSON document like:
{
  "example_date": "2020-04-10T12:03:55.4525649-04:30"
}

It is useful to use an odd or rare offset like -04:30 in testing here because it should make it more obvious the cases where DateTime's "pretend" (the hack known as DateTimeKind) falls down. DateTime works okay in the cases where the offset matches UTC (Z or +00:00 or -00:00) or the system local time (whatever your timezone is on your machine).
var date = DateTimeOffset.Parse("2020-04-10T12:03:55.4525649-04:30");
Debug.Assert(date.ToString("o") == "2020-04-10T12:03:55.4525649-04:30");
Debug.Assert(date.Offset.Hours == -4);
Debug.Assert(date.Offset.Minutes == -30);

Well, in checking example output from Twitter it is entirely possible that Twitter is just sending UTC for every time field and this is maybe moot because DateTimeKind may be "sufficient" in that case.

@WorldMaker Do you agree that if all the Twitter json dates uses UTC the DateTimeOffset is not useful and that I can close this ticket?

@linvi In terms of my specific debugging need at the time I posted the issue, we solved that elsewhere and it wasn't specifically a Tweetinvi problem.
I'm still worried about addressing the question of "what time offset did the user post this in?" and I'm surprised that information doesn't seem to be easily included in Twitter's API responses as I would have expected given they are returning ISO 8601 dates, but I realize now that is a Twitter API problem and not a Tweetinvi problem in that case.
I think even in the case where Twitter JSON uses UTC everywhere, as they still use ISO 8601 strings it is still useful to know the date was UTC specifically and the ISO 8601 string is represented in .NET exactly as it was parsed. Several years of working with a number of APIs and globally distributed timezone behaviors have led me to believe that DateTimeOffset should be default in .NET applications and libraries and DateTime considered deprecated, but I realize my experience is maybe uncommon still. More libraries using DateTimeOffset by default I think is better for the overall .NET ecosystem, but ideals aren't always "useful".
In the unlikely (?) event that Twitter were to start sending other timestamp offsets in their ISO 8601 dates (for instance, to better represented the time offset in which the user created a tweet), it could be useful preparation to make a switch to DateTimeOffset today rather than after such a Twitter change, but that may still be an unknown hypothetical more than a scenario to prepare for.
I wish Twitter better documented their API specifically with regards to the implicit assumption that they will always return UTC dates. I did find a direct mention of it, but only specifically in regards to the Twitter Ads API Getting Started, where they do state, at least for the Ads API:

Datetime values are always returned in UTC time

It's an easy change to switch all uses of DateTime for DateTimeOffset, but it is a breaking change, so I can understand hesitancy to move forward with the change. My experience says it is a change worth making, even if it won't be "fully useful" today or even hypothetically tomorrow (depending on Twitter's relationship with timezones). I do understand if you want to assume Twitter will continue to only return UTC dates and not make the change because you don't have to.

Thanks @WorldMaker this is very good insight. I will definitely consider this before moving the library to 5.0 beta stage.
Thanks

Thanks for taking the time to provide your knowledge on the topic, I have decided to use DateTimeOffset and you will have access to it in Tweetinvi 5.0-beta1 :)

Hi @linvi
We've decided to use your library for a project. It greatly simplifies twitter api access! Thanks for the great work, keep it up!
With that being said, I suspect the conversion to DateTimeOffset might not be totally complete:
Consider this example in: src\Tweetinvi.Core\Public\Events\AccountActivity\AccountActivityEvent.cs
    public class AccountActivityEvent
    {
        public AccountActivityEvent()
        {
            EventDate = new DateTime();
        }

        public long AccountUserId { get; set; }
        public DateTimeOffset EventDate { get; set; }
        public string Json { get; set; }
    }

The constructor still initializes EventDate to DateTime instead of DateTimeOffset. This causes the following error when events are sent through from a webhook:

Changing it to the following solves the problem:
     public class AccountActivityEvent
    {
        public AccountActivityEvent()
        {
            EventDate = new DateTimeOffset();
        }

        public long AccountUserId { get; set; }
        public DateTimeOffset EventDate { get; set; }
        public string Json { get; set; }
    }

I'm looking forward to your response!
Regards

Thanks for the update and the fix.

authors: TRON-N WorldMaker linvi

repo: linvi/tweetinvi


text:
[Bug] AccessDenied error occurs when clicking on a File block

Symptom
When clicking on a File block in the demo of the rotion project, the following AccessDenied error occurs:
<Error>
  AccessDenied
  <Message>Request has expired</Message>
  <X-Amz-Expires>3600</X-Amz-Expires>
  <Expires>2024-04-12T14:38:16Z</Expires>
  <ServerTime>2024-04-15T00:57:25Z</ServerTime>
  <RequestId>Z44SGQX4W0Z4MN8B</RequestId>
  <HostId>XJL+6lVm7ySEZHrhxxbcxh0xSv7pm5uFJvmpAYNPq+9sUtmZfQuASZOR57gywRDKd7tO5fHIw3u50L/iLRRidQ==</HostId>
</Error>

Steps to reproduce

Access the demo page of the rotion project
Click on a File block

Please investigate and fix the error related to the File block. Let me know if you need more information or have any additional questions. Thank you.

Thank you for the report. It seems to be a 403 error because you have direct access to the content of Notion. Also, not only the File block but also the PDF block was the same. We will respond soon.

authors: linyows ndotcom

repo: linyows/rotion


text:
Add prompts

Hi!
Nice library right here!
I wonder if it is possible to have some text prompting the user to input something.

Not really, there's no mechanism to say "are you sure? (y/n)" or similar - but that's a feature we definitely need!

I didn't mean that, although that would be fantastic as well.
I meant this:

Yes! You can use .set_prompt(), for example like so:
Commandline com;
com.set_prompt("C:\\Users\\santi");

authors: SanPen lionkor

repo: lionkor/commandline


text:
在非全屏模式下点击全屏按钮进入全屏模式如何能直接固定为横屏？

在非全屏模式下点击全屏按钮进入全屏模式如何能直接固定为横屏？不需要通过重力感应来切换横屏状态！

加上下面的代码就可以了：
JZVideoPlayer.FULLSCREEN_ORIENTATION = ActivityInfo.SCREEN_ORIENTATION_LANDSCAPE;
JZVideoPlayer.NORMAL_ORIENTATION = ActivityInfo.SCREEN_ORIENTATION_PORTRAIT;

么么哒

authors: jijinchao2014 lipangit ootypoo

repo: lipangit/JiaoZiVideoPlayer


text:
这是本地的m3u8文件,里边含有网络ts文件，怎么播放改本地m3u8文件

**需求描述
这是本地的m3u8文件,里边含有网络ts文件，怎么播放改本地m3u8文件
**其他app是否实现
**截图或者小视频说明

可以尝试使用其他播放器内核

如果直接指向这个m3u8不能播放的话, 建立个本地server, 然后将本地m3u8地址转成server地址

authors: lipangit oncealong songdehui


text:
Uninstall E2E

Description
This PR adds E2E tests for Liqo uninstall.

Liqo is uninstalled on the cluster1 using the script (2 minutes of timeout)

the timeout will make tests to fail if some finalizers were not correctly removed and resources can not be deleted

Runs e2e tests to assert pods are still running on the cluster2 and that there are no more virtual nodes
Liqo is uninstalled on the cluster1 using the script (2 minutes of timeout)

Pull Request Test Coverage Report for Build 272123574

0 of 0   changed or added relevant lines in 0 files are covered.
23 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.2%) to 49.882%

Files with Coverage Reduction
New Missed Lines
%

internal/liqonet/tunnelEndpointCreator-operator.go
23
65.59%

Totals

Change from base Build 272076700:
-0.2%

Covered Lines:
6773

Relevant Lines:
13578

💛  - Coveralls

/rebase

Hi @aleoli, thanks for this! Maybe in a next PR: Can we add more assertions to assess the state of the cluster? For example, the existence of CRDs and other complementary resources...

Yes, sure, these are very high-level tests

authors: aleoli coveralls palexster

repo: liqotech/liqo


text:
tls-crypt unwrap error: packet too short

I have tls-auth enabled on my ovpn server. I supply the required file (the TLS key from the server, which the script accepts and sends) but the command fails saying CRIT: Not responding.
Checking the ovpn logs I see that it was having trouble reading the tls key.
Tue Dec 18 21:23:01 2018 TCP connection established with [AF_INET]myip
Tue Dec 18 21:23:01 2018 myip TLS: Initial packet from [AF_INET]myip, sid=removed
Tue Dec 18 21:23:01 2018 myip tls-crypt unwrap error: packet too short
Tue Dec 18 21:23:01 2018 myip TLS Error: tls-crypt unwrapping failed from [AF_INET]myip
Tue Dec 18 21:23:01 2018 myip Fatal TLS error (check_tls_errors_co), restarting
Tue Dec 18 21:23:01 2018 myip SIGUSR1[soft,tls-error] received, client-instance restarting

Here us the command being run:
'/usr/lib/nagios/plugins/check_openvpn' '--tls-auth' '/usr/lib/nagios/plugins/ta.key' '-p' '1194' 'myip'

Guys??

Can I get some help???

@Engineer-of-Stuff can you post your openvpn server config?

@andiwand @Engineer-of-Stuff ,
hello guys, I am confirming that tls-crypt does not work at all.
I am getting  the following error:
Sat Feb  9 14:07:47 2019 tls-crypt unwrap error: packet authentication failed
Here is my server.conf:
mode server
tls-server
tls-crypt /etc/openvpn/certs/tlscrypt.key 0
proto udp
dev tun0
port 1194
topology subnet
group openvpn
user openvpn
auth SHA512
cipher AES-256-GCM
tls-version-min 1.2
tls-cipher TLS-ECDHE-RSA-WITH-AES-256-GCM-SHA384
duplicate-cn
reneg-sec 0
persist-key
compress lz4-v2
fast-io
tun-mtu 1200
verb 3
max-clients 250
auth-retry interact
ping-restart 15
ping 5
inactive 1800
management 127.0.0.1 5555
status /var/log/openvpn/status.log
log-append /var/log/openvpn/access.log
tmp-dir /etc/openvpn/tmp
plugin /etc/openvpn/plugins/openvpn-plugin-auth-script.so /etc/openvpn/scripts/authenticate.sh
Can you help me please ?
Thank you very much.

@Engineer-of-Stuff i see "Tue Dec 18 21:23:01 2018 TCP connection established with [AF_INET]myip" but for the check script you use udp.
@drajcan i just tested it for my setup and it work. maybe "tls-cipher TLS-ECDHE-RSA-WITH-AES-256-GCM-SHA384" is the problem here.

How do I specify TCP in the monitor?

you find it in the usage "  -t, --tcp             use tcp instead of udp"

Note: --tls-auth and tls-crypt are different. This tool doesn't yet have a command-line option for --tls-crypt (see the separate issue https://github.com/liquidat/nagios-icinga-openvpn/issues/22).

@connorpower i see, thank you for pointing this out!

As discussed, we currently do not support tls-crypt. Closing the issue for now.

authors: Engineer-of-Stuff andiwand connorpower drajcan liquidat

repo: liquidat/nagios-icinga-openvpn


text:
Inputs and outputs are not being tracked correctly by Network

Description
As the code currently stands, Network relies on two sets input_nodes and output_nodes to keep track of inputs and outputs respectively and make decisions on how to operate on Networks.
It's imperative that we have a way to detect what neurons are actually inputs and neurons to properly mutate, merge, activate, and otherwise do anything with our architecture-free Networks. This is possibly a long-standing bug that can be contributing to https://github.com/liquidcarrot/carrot/issues/51
This bug was (re)discovered when @teh-mICON reported he was getting un-normalized output like @dan-ryan did before
This is the output from Network.toJSON showing the structure of the neurons and connections of @teh-mICON 's network:
{
  "nodes": [
  {
    "bias": 0.09503197925769324,
    "squash": "TANH",
    "mask": 1,
    "index": 0
  },
  {
    "bias": 0.13779783091838294,
    "squash": "LOGISTIC",
    "mask": 1,
    "index": 1
  },
  {
    "bias": 0.10046853249309917,
    "squash": "INVERSE",
    "mask": 1,
    "index": 2
  },
  {
    "bias": 0.24744855279574018,
    "squash": "LOGISTIC",
    "mask": 1,
    "index": 3
  },
  {
    "bias": -0.20052607167794267,
    "squash": "SINUSOID",
    "mask": 1,
    "index": 4
  },
  {
    "bias": -0.09105453041194123,
    "squash": "LOGISTIC",
    "mask": 1,
    "index": 5
  },
  {
    "bias": 0.07804478165427353,
    "squash": "LOGISTIC",
    "mask": 1,
    "index": 6
  },
  {
    "bias": 0.4098613875791224,
    "squash": "LOGISTIC",
    "mask": 1,
    "index": 7
  },
  {
    "bias": -0.10260134476556315,
    "squash": "LOGISTIC",
    "mask": 1,
    "index": 8
  },
  {
    "bias": -0.09105453041194123,
    "squash": "LOGISTIC",
    "mask": 1,
    "index": 9
  },
  {
    "bias": -0.9188545171845655,
    "squash": "SELU",
    "mask": 1,
    "index": 10
  },
  {
    "bias": -0.09105453041194123,
    "squash": "LOGISTIC",
    "mask": 1,
    "index": 11
  }],
  "connections": [
  {
    "weight": 0.20762993440469124,
    "from": 9,
    "to": 11,
    "gater": null
  },
  {
    "weight": -1.6017292711240334,
    "from": 7,
    "to": 11,
    "gater": null
  },
  {
    "weight": 2.1207859110855507,
    "from": 8,
    "to": 9,
    "gater": null
  },
  {
    "weight": 0.9397945993867647,
    "from": 6,
    "to": 11,
    "gater": null
  },
  {
    "weight": -1.6017292711240334,
    "from": 7,
    "to": 9,
    "gater": null
  },
  {
    "weight": -2.062494586539331,
    "from": 5,
    "to": 11,
    "gater": null
  },
  {
    "weight": -0.5624448323743709,
    "from": 6,
    "to": 9,
    "gater": null
  },
  {
    "weight": 0.9220719725967439,
    "from": 4,
    "to": 11,
    "gater": null
  },
  {
    "weight": -2.062494586539331,
    "from": 5,
    "to": 9,
    "gater": null
  },
  {
    "weight": -0.5758182765217281,
    "from": 3,
    "to": 11,
    "gater": null
  },
  {
    "weight": 0.6568345798712394,
    "from": 4,
    "to": 9,
    "gater": null
  },
  {
    "weight": 0.8679286348183202,
    "from": 2,
    "to": 11,
    "gater": null
  },
  {
    "weight": -0.5758182765217281,
    "from": 3,
    "to": 9,
    "gater": null
  },
  {
    "weight": -1.567223021276047,
    "from": 1,
    "to": 11,
    "gater": null
  },
  {
    "weight": 0.8679286348183202,
    "from": 2,
    "to": 9,
    "gater": null
  },
  {
    "weight": 1.2598001286174136,
    "from": 0,
    "to": 11,
    "gater": null
  },
  {
    "weight": -1.567223021276047,
    "from": 1,
    "to": 9,
    "gater": null
  },
  {
    "weight": 1.6194117802506345,
    "from": 0,
    "to": 9,
    "gater": null
  },
  {
    "weight": 0.23318443542656864,
    "from": 8,
    "to": 10,
    "gater": null
  },
  {
    "weight": -0.6619424143505284,
    "from": 10,
    "to": 11,
    "gater": null
  }],
  "input_nodes": [0, 1, 2, 3, 4, 5, 6, 7, 8],
  "output_nodes": [9],
  "input_size": 9,
  "output_size": 1,
  "input": 9,
  "output": 1
}

If you look closely the output_nodes shows that # 9 is an output node, but in one of the connections you can also see that # 9 is a "from" neuron to neuron # 11 which is then the true output
This situation may have come about because of a mutation that added a connection from 9 to 11, something that should not have happened by default which then in turn caused this bug, but even still we should be adaptive enough to update our output node indexes whenever we add connections to former output neurons
Below you'll find a visualization of the network
Screenshots

Files
test/units/architecture/network.1.test.js
src/methods/mutation.js
src/architecture/Network.js
To Reproduce
Build a network, evolve it with methods.mutation.FFW as allowed methods, keep checking the output until it falls outside of the expected range
Tasks

[ ] Write more specific tests for Network.mutate and each mutation method
[ ] Check that the mutateOutput flag also applies to adding connections to output neurons
[ ] Refactor Network and methods that modify connections to update input / output indexes

Interesting idea: a "quick and dirty" way to pinpoint what is causing the bug could be to iteratively restrict the mutation methods to discover if some subset of mutation methods is the culprit

Update:
While writing tests discovered that calling Network.mutate(methods.mutation.ADD_NODE) on a network with no hidden neurons converted an output neuron into a hidden.
Exploring a fix now, will update with more discoveries

Another thing that the tests show is that when neurons are added they're being added to the end of the neurons array which is not in and of itself a bad thing, but I know there are a couple spots where we assume the order of the neurons will be indicative of whether they are inputs, hidden, or outputs so this can also be causing issues.

repo: liquidcarrot/carrot


text:
With due respect, I awaits eagerly. I am struggling for long time now with DA-DDPG repo!

Sir the instructions for the cloning the repo is not that intuitive, that make me feel confuse. And I am stuck here in downloading the data, "Download environment data bash experiments/scripts/download_data.sh"
Please make these instructions, intuitive, as here kept mentioning about the conda envrionment use and reuse, and also mentioned that downlaod again the GA-DDPG?
Installation
git clone https://github.com/liruiw/GA-DDPG.git --recursive
Setup: Ubuntu 16.04 or above, CUDA 10.0 or above, python 2.7 / 3.6
(Required for Training) - Install [OMG](https://github.com/liruiw/OMG-Planner) submodule and **reuse conda environment.**
(Docker) See [OMG Docker](https://github.com/liruiw/OMG-Planner#docker-setup) for details.
(Demo) - **Install GA-DDPG inside a new conda environment**

conda create --name gaddpg python=3.6.9
conda activate gaddpg
pip install -r requirements.txt

Install PointNet++
For me First I download the the recursive repo (git clone https://github.com/liruiw/GA-DDPG.git --recursive) with in anaconda, once downloaded then did this step (conda create --name gaddpg python=3.6.9 conda activate gaddpg pip install -r requirements.txt) and then downloaded this succesfully  (Install [PointNet++])
but the error I am getting here (Download environment data bash experiments/scripts/download_data.sh)
The error is ((gaddpg) siat@siat-Precision-3640-Tower:~/anaconda3/GA-DDPG$ bash experiments/scripts/download_data.sh
WARNING: combining -O with -r or -p will mean that all downloaded content
will be placed in the single file you specified.
--2024-01-16 16:20:17--  https://drive.google.com/uc?export=download&id=136rLjyjFFRMyVxUZT6txB5XR2Ct_LNWC
Connecting to 127.0.0.1:8889... connected.
Proxy request sent, awaiting response... 303 See Other
Location: https://drive.usercontent.google.com/download?id=136rLjyjFFRMyVxUZT6txB5XR2Ct_LNWC&export=download [following]
--2024-01-16 16:20:19--  https://drive.usercontent.google.com/download?id=136rLjyjFFRMyVxUZT6txB5XR2Ct_LNWC&export=download
Connecting to 127.0.0.1:8889... connected.
Proxy request sent, awaiting response... 200 OK
Length: 2427 (2.4K) [text/html]
Saving to: ‘data.zip’
data.zip                                   100%[========================================================================================>]   2.37K  --.-KB/s    in 0s
2024-01-16 16:20:21 (44.9 MB/s) - ‘data.zip’ saved [2427/2427]
FINISHED --2024-01-16 16:20:21--
Total wall clock time: 3.3s
Downloaded: 1 files, 2.4K in 0s (44.9 MB/s)
Data downloaded. Starting to unzip
Archive:  data.zip
End-of-central-directory signature not found.  Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive.  In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
unzip:  cannot find zipfile directory in one of data.zip or
data.zip.zip, and cannot find data.zip.ZIP, period.
)
Thanks for your amazing work, please help me with this if I could contribute and level it up. Thanks in advance.

You can try directly opening the link in the bash script and manually downloading and extracting it.

repo: liruiw/GA-DDPG


text:
Fix phase instantiation in a pipeline

Currently, we call phase() to instantiate one in setup_phases, but the constructor of a Phase requires a positional argument for its name. Make that happen.

This is not an issue any longer.

repo: lisad/phaser


text:
[Fix/Internal] [forecasting] data is shuffled when splitting the data to train/test

Summary
In _RegressorBase (internal class for forecasting), the dataset regarding parmeter values and delayed indicators is shuffled when splitting it to training and test data. This is related to #795.
Codes
import covsirphy as cs
# Dataset preparation
data_loader = cs.DataLoader("input")
jhu_data = data_loader.jhu()
# Scenario analysis
snl = cs.Scenario(country="Country name used")
snl.register(jhu_data)
snl.trend()
snl.estimate(cs.SIRF)
snl.fit()

Outputs
This is an internal error.
Environment

CovsirPhy version: 2.20.2
Python version: 3.9.5
Installation: poetry
System: WSL (Ubuntu)

Datasets for cross validation are also shuffled by K-fold.

With #807, for CV, k-fold will be replaced with TimeSeriesSplit.
https://scikit-learn.org/stable/modules/cross_validation.html#time-series-split
https://scikit-learn.org/stable/modules/generated/sklearn.model_selection.TimeSeriesSplit.html


text:
Edge插件，浏览器标签和底端播放/暂停图标是反的，强迫症有点难受

#957 #956

authors: LuneZ mikelxk


text:
[Feature]: Report failure without throwing and error

Feature Request
I'm not sure if this is already implemented, but seems like task.report doesn't do anything to the result. Would be nice to have task.fail similar to task.skip without having to throw.
Ideally if a task is reported as a fail via task.fail and exitOnError is true, the task runner keeps running and doesn't exit. This allows me to keep exitOnError: true and reserve it for fatal errors. Maybe exitOnFail might make sense as an option.
Use Case
No response
Contribution

[ ] I can implement this feature without anything else required, when specification finalizes.
[ ] I can implement this feature with guidence.
[X] It is just a request.

Preflight

[X] Read/Search existing issues and the provided documentation.
[X] Be sure to not open an issue in the looking for contributions section.
[X] Checking the latest version of the software to confirm it has not been added already.

Dear @masad-frost,
I do not think I got the idea correctly.
Let us assume that we have called this task.fail and it will just continue on running, how will we give visual feedback on how the task has failed?
Do you think that the current way of setting exitOnError on the task level is not enough to handle this case?
Looking forward to your idea about it because I think I am missing the point.

Hey, sorry, yeah i can see how it's not clear.
Essentially, I'd like to report test failures on my task
{
  task: async (ctx, task) => {
    // if something throws here i want that to lead to an exit
    // since it's an uncaught error.
    // but the only way to report a failure is to throw, so I'm forced
    // to set `exitOnError: false`
  }
}

In an ideal world, task failing because of an uncaught error is different from a task failing because some known condition is not met. Does that make sense?


text:
Error in documentation (Typescript) for inheriting-styles-from-a-superclass

https://lit.dev/docs/components/styles/#inheriting-styles-from-a-superclass
super.styles,
gives the following error
'super' property access is permitted only in a constructor, member function, or member accessor of a derived class.

Thanks for the issue, transferred to the lit.dev documentation site repository.
The preview is currently broken:
https://user-images.githubusercontent.com/15080861/134965647-cb8b9b6f-6168-45d7-9245-3be538495d6f.mp4

thanks

authors: AndrewJakubowicz davie-robertson


text:
hiding attribute from superclass

I have a base class
import { html, css, LitElement, ComplexAttributeConverter } from 'lit';
import { customElement, property } from 'lit/decorators';

export enum frameType {
  one = 'one',
  two = 'two',
  three = 'three',
  none = 'none',
}

export const validType = (type: frameType): boolean => {
  switch (type) {
    case frameType.one:
    case frameType.two:
    case frameType.three:
      return true;
    default:
      return false;
  }
};

export const frameTypeConverter: ComplexAttributeConverter = {
  fromAttribute: (value: string): frameType => {
    let v = value as frameType;
    if (v === undefined) {
      v = frameType.none;
    }
    return v;
  },
  toAttribute: (value: frameType): string => {
    return `${value}`;
  }
};

@customElement('my-base')
export class base extends LitElement {
  static styles = css`
    :host {
      background-color: transparent;
      height: auto;
      width: 100%;
    }

    .frame{
      background-color: transparent;
      border: 0px;
      padding: 0px;
      width: 100%;
    }
  `;

  constructor() {
    super();
  }

  @property({
    type: frameType,
    attribute: 'type',
    converter: frameTypeConverter,
    reflect: true,
  })
  type: frameType = frameType.none;

  connectedCallback() {
    super.connectedCallback();
  }

  disconnectedCallback() {
    super.disconnectedCallback();
  }

  render() {
    let src = 'about:blank';
    if (validType(this.type)) {
      const host = 'ENV_APP_HOST';
      src = `${host}content/${this.type}`;
    }
    return html`
      <iframe src="${src}" part="frame" class="frame">
      </iframe>
    `;
  }
}

And a subclass that inherits from it:
import { customElement } from 'lit/decorators';
import { base } from './base.frame';

@customElement('my-child')
export class child extends base {

  constructor() {
    super();
  }
}

How do I fix the value of and hide the type attribute on the subclass. I've tried both of the following but the type attribute still renders:
import { customElement, property } from 'lit/decorators';
import { base, frameType, frameTypeConverter } from './base.frame';

@customElement('my-child')
export class child extends base {

  @property({
    type: frameType,
    attribute: false,
    converter: frameTypeConverter,
    noAccessor: true,
  })
  type: frameType = frameType.one;

  constructor() {
    super();
  }
}

import { customElement } from 'lit/decorators';
import { base, frameType, frameTypeConverter } from './base.frame';

@customElement('my-child')
export class child extends base {
  static get properties() {
    return {
      type: {
        type: frameType,
        attribute: false,
        converter: frameTypeConverter,
        noAccessor: true,
      }
    };
  }

  constructor() {
    super();
    this.type = frameType.one;
  }
}

I have managed to half solve this problem by decorating the type property with @state()
import { customElement, state } from 'lit/decorators';
import { base, frameType } from './base.frame';

@customElement('my-child')
export class child extends base {

  @state()
  type: frameType = frameType.one;

  constructor() {
    super();
  }
}

However the type property is still accessible on the class and can be changed using javascript. I cannot set the type property to private because then child doesn't correctly extend base.

In general in OOP subclasses can add or override superclass members, but can't remove them. Removing members would violate assignability / the Liskov substitution principle.
You may need one base class without the type attribute, and two subclasses: one with type and one without.

Thanks for the suggestion

authors: justinfagnani tmstn

repo: lit/lit


text:
[labs/react] Add back the reserved React property warning

Should this be an RFC?

[X] This is not a substantial change

Which package is this a feature request for?
React (@lit-labs/react)
Description
https://github.com/lit/lit/pull/2800 removed our warning for reserved React property names because it changed how we detect custom element properties. We should add this back, but only in a dev build, which we'll need to set up for the react package.
Alternatives and Workarounds
n/a

Curious if we can close this issue.
We don't iterate over the element like we didn't with #2800 which doesn't give us the opportunity to warn users about properties except for on component updates.

authors: justinfagnani taylor-vann


text:
[lit-html] Choose directive doesn't check types correctly

Which package(s) are affected?
Lit Core (lit / lit-html / lit-element / reactive-element)
Description
When I use choose directive like this, I would expect typescript to throw error since 'test' and 'random' can't be assigned to CheckoutStep type
type CheckoutStep = 'register' | 'delivery' | 'payment';

function render(step: CheckoutStep) {
    return choose(step, [
        ['test', () => 1],
        ['random', () => 2],
        ['register', () => 3],
    ]);
}

Reproduction
There should be a type error but there isn't: Typescript gist
Workaround
It's seems like it's because T is inferred as string since it's used for both value and cases params
export declare const choose: <T, V>(value: T, cases: [T, () => V][]) => V;

It works as expected when I update the signature like this
export declare const choose: <T, V, K extends T>(value: T, cases: [K, () => V][]) => V;

Is this a regression?
No or unsure. This never worked, or I haven't tried before.
Affected versions
This never worked
Browser/OS/Node environment
OS: Windows 10
Node version: 18.12.1
npm version: 8.19.2

Interesting! Yeah, looks like the type inference for T becomes broader so you'd need to manually provide the types like choose<CheckoutStep, number> to get it to type check in its current state.
The suggestion of adding the third type parameter extending T does indeed fix this. It would be good to make it default to T to make it non-breaking for anyone who actually did specify only 2 type arguments before like
export declare const choose: <T, V, K extends T = T>(value: T, cases: [K, () => V][]) => V;

authors: augustjk remziatay


text:
Upgrade 99designs gqlgen and golang to the latest stable version

We aren't able to upgrade the golang version from 1.16 to the latest/stable version due to the direct dependency with the gqlgen version.
Request to upgrade gqlgen version, then go version to the latest one.

ETA- Release 2.11

repo: litmuschaos/litmus


text:
List workflow pagination

Proposed changes

Updated ListWorkflow API to fetch only requested data from the DB.
Added Pagination, Filtering, Sorting, and Searching at DB level for ListWorkflow API.
Updated frontend according to the API's.
Removed deprecated API's from backend and frontend.
Minor style changes due to litmus-ui version 1.1.7

Types of changes
What types of changes does your code introduce to Litmus? Put an x in the boxes that apply

[x] New feature (non-breaking change which adds functionality)
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices applies)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING doc
[x] I have signed the commit for DCO to be passed.
[x] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works (if appropriate)
[ ] I have added necessary documentation (if appropriate)

Dependency

Please add the links to the dependent PR need to be merged before this (if any).

Special notes for your reviewer:
Please ignore translation changes if not important

There was some issue with this branch, so created a new branch for the same PR: https://github.com/litmuschaos/litmus/pull/2882


text:
ValueError:  Character [-] in not allowed in identifier (for existing users)

Describe the bug
I tried SnowDDL today and it looks very promising. 😊
However, I have a problem with existing users on our Snwoflake account.
The Snowflake users in our company are synchronised to Snowflake via Azure Entra ID and AAD groups.
These users then have the following form for their login_name, for example: ADMIN-D0123456.
With a snowddl plan, SnowDDL apparently cannot find these users and does not even list them in the plan. When I try to add the users manually via a user.yaml file, for example to assign roles to them, I get the following error:
ValueError: Character [-] in not allowed in identifier [ADMIN-D0123456], only ASCII letters, digits and single underscores are accepted

Expected behavior
SnowDDL should correctly recognise the existing USers so that they can be used for further role assignments by SnowDDL.
Attach log
$ snowddl -c config/ -a ${ACCOUNT} -r ACCOUNTADMIN -u ${SNOWFLAKE_USER} -k ${PRIVAT_KEY_FILE} --passphrase ${PRIVAT_KEY_PASSWORD} -w XS --show-sql plan
2024-09-13 14:51:13.243 - WARNING - [/builds/customer-data-empowerment/sandbox/test-repos/snowddl-playground/config/user.yaml]: Traceback (most recent call last):
  File "/builds/customer-data-empowerment/sandbox/test-repos/snowddl-playground/venv/lib[64](https://gitlab.dm-drogeriemarkt.com/customer-data-empowerment/sandbox/test-repos/snowddl-playground/-/jobs/42460443#L64)/python3.9/site-packages/snowddl/parser/abc_parser.py", line 38, in parse_single_file
    return callback(file)
  File "/builds/customer-data-empowerment/sandbox/test-repos/snowddl-playground/venv/lib64/python3.9/site-packages/snowddl/parser/user.py", line 84, in process_user
    full_user_name = AccountObjectIdent(self.env_prefix, user_name)
  File "/builds/customer-data-empowerment/sandbox/test-repos/snowddl-playground/venv/lib64/python3.9/site-packages/snowddl/blueprint/ident.py", line 94, in __init__
    self.name = self._validate_part(name)
  File "/builds/customer-data-empowerment/sandbox/test-repos/snowddl-playground/venv/lib64/python3.9/site-packages/snowddl/blueprint/ident.py", line 47, in _validate_part
    raise ValueError(
ValueError: Character [-] in not allowed in identifier [ADMIN-D0123456], only ASCII letters, digits and single underscores are accepted
Cleaning up project directory and file based variables

Attach YAML config (if applicable)
users.yaml
ADMIN-D0123456:
  login_name: ADMIN-D0123456
  display_name: Some, Name- Admin-D0123456
  email: Some.Name@email.de
  default_warehouse: XSMALL
  comment: AAD provisioned account

Ok, you have two options here.
(1) Connect to Azure in Python, get info about users and create blueprints dynamically in the code
Here is the documentation page: https://docs.snowddl.com/advanced/programmatic-config
Here is the structure of UserBlueprint: https://github.com/littleK0i/SnowDDL/blob/master/snowddl/blueprint/blueprint.py#L385-L399
Basically, instead of YAML config you may generate a small part of config dynamically.
This is the best option, since you will have full control over user object generation. You will be able to tweak any settings and adjust any names. Including replacement of hyphens with underscores.
(2) Let Azure manage users and SnowDDL manage everything else
Create SnowDDL config up to business roles, but do not create users. Let Azure create users and own them.
Azure probably can assign roles to newly created users. Point it to business roles created by SnowDDL.
This comes with a lot of limitations. You won't have full control over every parameter of user. You will be able to assign only one business role per users, since user roles do not exist. But things should work, more or less.

SnowDDL does not touch objects which are "owned" by other tools. That's why it does not touch users currently created by Azure.
Login name should accept any string. But user name is an identifier and is subject to strict naming policy introduced in SnowDDL. It helps to prevent account becoming a mess over time, and it helps to keep identifiers useable without double-quotes in most cases. Hyphen - is restricted on purpose.

Just for the sake of interest: How does SnowDDL identify entities that "belong" to other tools? Entities (schemas, tables, etc.) that have been created by other users within snowflake, for example, are also recognized by SnowDDL and dropped or changed if necessary.

@CM000n , it uses "ownership" concept.
Each object in Snowflake is "owned" by some role. All account-level objects owned by SnowDDL role are managed by SnowDDL. All other account-level objects are ignored.
Schema-level objects in databases created by SnowDDL are managed by SnowDDL regardless of ownership. The idea is that databases created by SnowDDL should be fully managed by SnowDDL.
Also, you may set parameter is_sandbox: true for schemas. Other application (e.g. DBT) can create objects in these schemas, and objects won't be dropped if not listed in SnowDDL config.


text:
这2天机器人总是掉线，错误日志都一样，说是BrokenPipeError: [Errno 32] Broken pipe？

在提交前，请确保您已经检查了以下内容!

[ ] 您可以在浏览器中登陆微信账号，但不能使用itchat登陆
[ ] 我已经阅读并按文档 中的指引进行了操作
[ ] 您的问题没有在issues报告，否则请在原有issue下报告
[ ] 本问题确实关于itchat, 而不是其他项目.
[ ] 如果你的问题关于稳定性，建议尝试对网络稳定性要求极低的itchatmp项目

请使用itchat.run(debug=True)运行，并将输出粘贴在下面:
itchat==1.3.10
[在这里粘贴完整日志]
send message:
Traceback (most recent call last):
  File "/home/python/venv/lib/python3.6/site-packages/urllib3/connectionpool.py", line 600, in urlopen
    chunked=chunked)
  File "/home/python/venv/lib/python3.6/site-packages/urllib3/connectionpool.py", line 354, in _make_request
    conn.request(method, url, **httplib_request_kw)
  File "/usr/lib64/python3.6/http/client.py", line 1239, in request
    self._send_request(method, url, body, headers, encode_chunked)
  File "/usr/lib64/python3.6/http/client.py", line 1285, in _send_request
    self.endheaders(body, encode_chunked=encode_chunked)
  File "/usr/lib64/python3.6/http/client.py", line 1234, in endheaders
    self._send_output(message_body, encode_chunked=encode_chunked)
  File "/usr/lib64/python3.6/http/client.py", line 1065, in _send_output
    self.send(chunk)
  File "/usr/lib64/python3.6/http/client.py", line 986, in send
    self.sock.sendall(data)
  File "/usr/lib64/python3.6/ssl.py", line 972, in sendall
    v = self.send(byte_view[count:])
  File "/usr/lib64/python3.6/ssl.py", line 941, in send
    return self._sslobj.write(data)
  File "/usr/lib64/python3.6/ssl.py", line 642, in write
    return self._sslobj.write(data)
BrokenPipeError: [Errno 32] Broken pipe

您的itchat版本为：[在这里填写版本号]。（可通过python -c "import itchat;print(itchat.__version__)"获取）
其他的内容或者问题更详细的描述都可以添加在下面：

[您的内容]

我手机上显示web登录都没了。

repo: littlecodersh/ItChat


text:
update minimum ruby to reflect actual support

As noted on #38, commit a885a778b1afb9694f15939763cb1fd3d461ce2d includes code that will not work with ruby-1.8.7.  Updated the gemspec to reflect this so it doesn't get forgotten.

Thanks a lot @lostapathy , LGTM.

authors: liufengyun lostapathy

repo: liufengyun/hashdiff


text:
GsonUtil.buildGson().toJson出现int变成double的问题

https://wenku.baidu.com/view/7bdaa4dbfa0f76c66137ee06eff9aef8941e4866.html

{"id":20,"name":"test"}反序列化为Map<String,Object>，此时20就是double类型，此时序列化map对象，自然就得到了{"id":20.0,"name":"test"}，这是正常的，你应该在反序列化时规避这个问题，譬如反序列化为以下对象
public class Bean {
     int id;
     String name;
}

此时，再将Bean对象序列化，就得到和原来一样的json字符串

为了通用接手一般都写的string，所以才出现这个问题，不是很大的问题，就是觉得这样会不会更好一点

这个就看个人，你可以自定义Gson对象，传入到GsonConverter对象中，详情设置Converter

repo: liujingxing/rxhttp


text:
C&CPP

cmake使用教程

clion cmake

文件转换为数组


text:
batch_get_group_members 入参gruop数和web不一样

contact['UserName'].find('@@') != -1
我发现还有群聊只有一个@

群聊是两个@@吧

authors: CZJCC yarnping

repo: liuwons/wxBot


text:
After install all the package in a conda env, got the error message!

hi, I got an error after install all the packages and run your code.
Traceback (most recent call last):
File "/home/ubuntu/OSRL/examples/train/train_bc.py", line 15, in
from fsrl.utils import WandbLogger
File "/home/ubuntu/anaconda3/envs/OSRL/lib/python3.9/site-packages/fsrl/utils/init.py", line 3, in
from fsrl.utils.logger import BaseLogger, DummyLogger, TensorboardLogger, WandbLogger
File "/home/ubuntu/anaconda3/envs/OSRL/lib/python3.9/site-packages/fsrl/utils/logger/init.py", line 4, in
from fsrl.utils.logger.tb_logger import TensorboardLogger
File "/home/ubuntu/anaconda3/envs/OSRL/lib/python3.9/site-packages/fsrl/utils/logger/tb_logger.py", line 5, in
from torch.utils.tensorboard import SummaryWriter
File "/home/ubuntu/anaconda3/envs/OSRL/lib/python3.9/site-packages/torch/utils/init.py", line 4, in
from .throughput_benchmark import ThroughputBenchmark
File "/home/ubuntu/anaconda3/envs/OSRL/lib/python3.9/site-packages/torch/utils/throughput_benchmark.py", line 2, in
import torch._C
ModuleNotFoundError: No module named 'torch._C'

It seems that the PyTorch version doesn't support the tensorboard SummaryWriter. Could you show me your PyTorch version?
You can also try to update your PyTorch version to 1.13.1 since this version works for us well.

Your understanding is correct. The bolded $\mathbf{R}$ and $\mathbf{C}$ represent all the reward returns and cost returns in the trajectory, while $R(\tau_i^*)$ denotes the scalar return of the entire trajectory.

repo: liuzuxin/OSRL


text:
Kino.Tree does not render 0.10.0

Environment

Erlang/OTP 25 [erts-13.2.2.2] [source] [64-bit] [smp:10:10] [ds:10:10:10] [async-threads:1] [jit] [aarch64-apple-darwin22.4.0]
kino: 0.10.0

Elixir & Erlang/OTP versions (elixir --version): 1.14.5
Operating system: MacOS Ventura 13.2.1
How have you started Livebook (mix phx.server, livebook CLI, Docker, etc): used 'livebook server'
Livebook version (use git rev-parse HEAD if running with mix): 0.10.0
Browsers that reproduce this bug (the more the merrier):  Chrome: Version 115.0.5790.102 (Official Build) (arm64)
Include what is logged in the browser console:

phx-F3ngfc5bKvgVUwDD update:  -  {1: {…}}
:8080/sessions/7nsq3cvukltodlqqld5o7p54pqhyie24b7yqjaph:1 Access to fetch at 'http://localhost:8081/iframe/v4.html' from origin 'http://localhost:8080' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
app.js:570     GET http://localhost:8081/iframe/v4.html net::ERR_FAILED 200 (OK)
kse @ app.js:570
dW @ app.js:570
loadIframe @ app.js:570
(anonymous) @ app.js:570
Promise.then (async)
mounted @ app.js:570
__mounted @ app.js:18
maybeAddNewHook @ app.js:18
(anonymous) @ app.js:18
(anonymous) @ app.js:12
trackAfter @ app.js:12
(anonymous) @ app.js:12
perform @ app.js:12
performPatch @ app.js:18
(anonymous) @ app.js:18
time @ app.js:24
update @ app.js:18
(anonymous) @ app.js:18
applyDiff @ app.js:18
(anonymous) @ app.js:18
after @ app.js:24
requestDOMUpdate @ app.js:24
(anonymous) @ app.js:18
(anonymous) @ app.js:24
trigger @ app.js:5
(anonymous) @ app.js:6
decode @ app.js:6
onConnMessage @ app.js:6
conn.conn.onmessage @ app.js:6
app.js:570        Uncaught (in promise) TypeError: Failed to fetch
at kse (app.js:570:10984)
at dW (app.js:570:10426)
at D1.loadIframe (app.js:570:15139)
at app.js:570:11856
kse @ app.js:570
dW @ app.js:570
loadIframe @ app.js:570
(anonymous) @ app.js:570
Promise.then (async)
loadIframe @ app.js:570
(anonymous) @ app.js:570
Promise.then (async)
mounted @ app.js:570
__mounted @ app.js:18
maybeAddNewHook @ app.js:18
(anonymous) @ app.js:18
(anonymous) @ app.js:12
trackAfter @ app.js:12
(anonymous) @ app.js:12
perform @ app.js:12
performPatch @ app.js:18
(anonymous) @ app.js:18
time @ app.js:24
update @ app.js:18
(anonymous) @ app.js:18
applyDiff @ app.js:18
(anonymous) @ app.js:18
after @ app.js:24
requestDOMUpdate @ app.js:24
(anonymous) @ app.js:18
(anonymous) @ app.js:24
trigger @ app.js:5
(anonymous) @ app.js:6
decode @ app.js:6
onConnMessage @ app.js:6
conn.conn.onmessage @ app.js:6
app.js:6 phx-F3ngfc5bKvgVUwDD update:  -  {1: {…}}

Include what is logged to the server console: Nothing logged in server console

Current behavior
See screenshots - nothing renders for Kino.Tree, even in the example copied from the docs.
Expected behavior
A tree should render.

Are you running anything else on port 8081? What do you see if you go to http://localhost:8081/iframe/v4.html?

Aha. I was running another process  ( a separate webserver ) on 8081.  When I killed that process, the tree renders fine. I'll close this ticket.

repo: livebook-dev/livebook


text:
Fix IntelliJ markdown dependency issue

This PR updates the cache keys to clear the cache, which was previously causing build issues on JDK <11 due to
https://github.com/JetBrains/markdown/issues/70

@weisers Ah yep! I meant to have that PR based off of this one.

repo: livefront/sealed-enum


text:
Failed to transform '/Users/admin/.gradle/caches/modules-2/files-2.1/io.github.webrtc-sdk/android-prefixed/125.6422.05/df29fc7d002a11d35571bc723f0550b9abcf7697/android-prefixed-125.6422.05.aar' using Jetifier. Reason: IllegalArgumentException, message: Unsupported class file major version 61. (Run with --stacktrace for more details.)

when i build the project,build failed with this log
*envirment:
androidstudio version : 2024.1.2
android_gradle_plugin version:4.1.0
gradle version :gradle-6.7.1
compileOptions {
sourceCompatibility JavaVersion.VERSION_1_8
targetCompatibility JavaVersion.VERSION_1_8
}
thanks

Use a Java version 17 or up. The JDK already included in your Android Studio should be compatible with this.

authors: davidliu nodzhang

repo: livekit/client-sdk-android


text:
Update rust sdk and add dtmf support

depends on https://github.com/livekit/rust-sdks/pull/371
and pulls in latest changes on main of rust sdk, which comes with a couple of necessary ffi protocol changes.
~~the submodule currently points to the lukas/add-publish-dtmf branch. Should update that after that PR got merged to point to main instead. ~~ ✅

@nbsp also added support for retrieving attribute events (which I think wasn't yet part of #240 ?)

repo: livekit/node-sdks


text:
fix: don't overwrite the url path in twirp-client

The twirp client overwrites the URL path, which can lead to unexpected behavior. This was already fixed for other parts of the code base (https://github.com/livekit/rust-sdks/issues/217).

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

authors: CLAassistant weichweich

repo: livekit/rust-sdks


text:
高亮时的样式可以默认用非高亮的样式吗？

用的textView，点击后默认的样式是文字变蓝并有下划线。可以改成默认使用非高亮时的样式吗？
我想着把高亮样式设置成和非高亮样式一样就可以了，然后试了好久好久……才写出来😭。
因为框架隐去了大部分参数的标签，书写方式也不太适应，xcode提示基本瘫了。
但是，一旦underline的Style设置为none，就会报错
'none' is unavailable: use [] to construct an empty option set 和 'none' has been explicitly marked unavailable here
代码如下：
"\("需要点击的文字", .foreground(.red), .action([.underline(.none)], someClick))

你可以试一下 "\("需要点击的文字", .foreground(.red), .action([], someClick))

你可以试一下 "\("需要点击的文字", .foreground(.red), .action([], someClick))

可以了，感谢

然后我又发现了个问题，action会持有界面导致界面无法释放，但是换一下写法就能释放了。

直接用函数名会无法释放： "\("需要点击的文字", .action([], someClickFunc))"
用闭包就可以：
"\("需要点击的文字", .action([], {  [weak self] result in
               // do something...
}))"

https://github.com/lixiang1994/AttributedString/issues/44
是的 会有这个问题, 我也很无奈


text:
Ghc 8.8.1

Takes commit from #19, add bounds + stuff

Does it make it work with GHC 8.8.1? If so, what prevents us from merging this in?

@mrkkrp see https://github.com/haskell-infra/hackage-trustees/issues/236

NMU was done. Commit can be found in https://github.com/hackage-trustees/vector-th-unbox

authors: mrkkrp phadej

repo: liyang/vector-th-unbox


text:
🛑 Movie is down

In d8e8f78, Movie (http://h.liyaodong.com:8096) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Movie is back up in 05e0cb6.

repo: liyaodong/uptime