text:
Travis - prevent FAIL during integration test

As can Currently when running integration test without tag=debug (race = false), 3 tests fails . (as can be seen here on Travis by searching "--- fail"):
--- FAIL: TestChannelLinkTrimCircuitsNoCommit (0.76s)
link_test.go:3806: line: 2741: wrong number of open circuits: want 0, got 2
--- FAIL: TestChannelLinkBandwidthConsistency (3.89s)
link_test.go:1534: line 1939: alice's link bandwidth is incorrect: expected 399994624000 mSAT, got 499995656000 mSAT
--- FAIL: TestMask (0.00s)
mask_test.go:91: htlcswitch tests must be run with '-tags debug'
Avoid that by skipping these tests.
Note that while 3 tests failed, the travis job is still marked green. This is handled by #1593

All the tests should be run with the debug flag activated.

Instead of skipping, we should change the Makefile to run the coverage tests with -tags="debug". This is the change made in #1712

@cfromknecht @Roasbeef @halseth
If this is your decision I suggest you also consider how to handle the case of someone running a test of the htlcswitch package  directly from the command line by:
go test github.com/lightningnetwork/lnd/htlcswitch
This will yield that following errors:
--- FAIL: TestChannelLinkTrimCircuitsNoCommit (0.75s)
link_test.go:3812: line: 2747: wrong number of open circuits: want 0, got 2
--- FAIL: TestChannelLinkBandwidthConsistency (3.76s)
link_test.go:1540: line 1945: alice's link bandwidth is incorrect: expected 399994624000 mSAT, got 499995656000 mSAT
FAIL
FAIL	github.com/lightningnetwork/lnd/htlcswitch	16.037s
Suggest you add t.Fatalf for these two tests and fail them with the proper error (need "debug" tag).

I see your point, if you'd like to amend the PR to make the fatals I would support that

Now that the tests are run w/ the proper tags, we can do so w/o breaking the builds!

Actually, we'll need to wait for #1716 to land, which properly reinstates #1712

@cfromknecht can you please reopen this PR? I will make the changes as you suggested.

@halseth @cfromknecht Updated.
For some reason, all checks fail
Thanks

@offerm You are not passing make lint and make fmt.

@halseth make fmt is good now.
make lint still shows error. These errors, however, have nothing to do with this PR and exist also in the master branch.....
Travis is still crazy.
Hope you can merge it now

authors: Roasbeef cfromknecht halseth offerm


text:
Fix build failures on docker-compose.

This PR is not for any Golang code. So I omited Pull Request Checklist
docker/lnd/Dockerfile haven't been updated even though lnd was moved to Golang 1.11.
This will fix it.

you could also use alpine-sdk instead of musl-dev: https://github.com/lightningnetwork/lnd/pull/2259/files.  Any reason for preferring musl-dev?

source: gharchive/pull-request

authors: cryptcoin-junkey yancyribbens

repo: lightningnetwork/lnd

license: MIT

license_type: permissive

license_source: github-api


text:
Multi-node receive [PoC]

This PR is an exploration of the design space for multi-node receive.
The idea is to run a standalone process (working title: invoice coordinator) that connects to a cluster of lnd nodes via the htlc interceptor API. The coordinator is backed by a replicated database that contains all invoices. It has its own node key and every invoice is generated by the coordinator. Invoices contain a hop hint for each node in the cluster with a dummy scid.
When an htlc comes in on one of the cluster nodes, it is intercepted by the coordinator. The coordinator matches the hash with the invoice database and if there is one, it signals the lnd node to settle the htlc.
This allows invoices to be paid through any of the cluster nodes. When one node goes down, senders will retry with one of the other nodes listed in the route hints. Also shards of a multi-part payment may use multiple nodes.
Current implementation is an adaptation to LND. It allows LND to be run in a mode where it acts as the coordinator. To do that, the gateway node needs to be specified (only one supported atm):
lnd --gateway.pubkey=0314aaf9b2547682b81977b3ac0c5585c3521a0a5430fb410cb572d5c72364edf3 --gateway.tls=~/.lnd/tls.cert --gateway.mac=~/.lnd-bob/data/chain/bitcoin/regtest/admin.macaroon --gateway.host=localhost:10002
What you can do with this is set up Alice and Bob with a channel between them and then connect the coordinator to Bob. This allows Alice to pay invoices created by the coordinator.
For production, it seems unlikely that we want to run a customized lnd as the coordinator. Instead the coordinator code can live in a fresh stand-alone repo. This also allows the database backend (channeldb/invoices.go) to be re-implemented using structured sql.
Dependencies:

https://github.com/lightningnetwork/lnd/issues/6161
https://github.com/lightningnetwork/lnd/issues/6040
https://github.com/lightningnetwork/lnd/pull/6177

Closing as this is now implemented externally in https://github.com/bottlepay/lnmux


text:
Linter checks go versions in Dockerfile and YAML files

Change Description
This PR adds two checks to the linter. These checks ensure that the Go version used in Dockerfile files and YAML files are consistent and as expected.
This PR also ensures that Go version 1.22.5 is used throughout the project.
(Note that I couldn't re-open https://github.com/lightningnetwork/lnd/pull/8211 I think it's because I forced pushed to the branch before re-opening?)
Steps to Test
Steps for reviewers to follow to test the change.
Pull Request Checklist
Testing

[ ] Your PR passes all CI checks.
[ ] Tests covering the positive and negative (error paths) are included.
[ ] Bug fixes contain tests triggering the bug to prevent regressions.

Code Style and Documentation

[ ] The change obeys the Code Documentation and Commenting guidelines, and lines wrap at 80.
[ ] Commits follow the Ideal Git Commit Structure.
[ ] Any new logging statements use an appropriate subsystem and logging level.
[ ] Any new lncli commands have appropriate tags in the comments for the rpc in the proto file.
[ ] There is a change description in the release notes, or [skip ci] in the commit message for small changes.

📝 Please see our Contribution Guidelines for further guidance.

got this failure on my local machine,
make check-go-version

 Checking for target Go version (v1.22.5) in Dockerfile files (*Dockerfile)
./scripts/check-go-version-dockerfile.sh 1.22.5
Skipping ./tools/Dockerfile
./docker/btcd/Dockerfile is using Go version 1.22.5.
./Dockerfile is using Go version 1.22.5.
./dev.Dockerfile is using Go version 1.22.5.
./make/builder.Dockerfile is using Go version 1.22.5.
./lnrpc/Dockerfile is using Go version 1.22.5.
All Dockerfiles pass the Go version check for Go version 1.22.5.
 Checking for target Go version (v1.22.5) in YAML files (*.yaml, *.yml)
./scripts/check-go-version-yaml.sh 1.22.5
Error: ./.github/workflows/release.yaml specifies Go version '', but not version '1.22.5'.
make: *** [check-go-version-yaml] Error 1

@yyforyongyu thanks for the review! I think this might be a difference in sed between linux and mac. I've updated the use of sed in the latest commits, please let me know if that works on your computer.

Thanks for the mac fix @yyforyongyu !


text:
Minor: Remove deprecated chrome.loadTimes() code

This code predates the window.performance API, so it makes sense to remove it given that the window.performance API has broad adoption.
The chrome.loadTimes() code produces console warnings for most Chrome users, since it's deprecated; this PR eliminates that.

nvm forgot i can just merge from the PR

authors: austinlparker tedpennings

repo: lightstep/lightstep-tracer-javascript

license: mit

license_source: bigquery


text:
Use performance on window object

I am seeing an exception ReferenceError: Can't find variable: performance in our CI tests. Everything works fine for us except in the CI environment. I suppose some headless browsers might not implement the Web Performance API? Anyways, accessing performance from window fixes it for us.

Yikes! That actually looks to be a regression - I could have sworn there was a preceding check for window.performance in the code at some point! Thanks again, @luk3thomas .
(Also, FYI, I'm planning on looking into #3 as soon as I can carve out the time.)

@bcronin awesome! I saw several places that used window.performance and this was the only place I saw that didn't have it.
Yeah, #3 seems like a tough one. I started in on a PR but its a non trivial change, with the way everything is initialized. I didn't see a way to access the main Tracer class from within the lightstep instance.


text:
Prometheus Summary conversion is incorrect

The OTLP output for a Prometheus Summary is not properly combining the _sum, _count, and assorted quantiles into a single data point.

(This didn't make the release.)

source: gharchive/issue


text:
update 20220506

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Updated

repo: ligzy/aws-iot-device-sdk-embedded-C


text:
Fix Scala Native for testing libraries

Add missing test-runner in Scala Native tools

Last PR I did, I broke the Scala Native build for testing libraries.. That's because Scala Native, starting from version 0.3.8, has a separate artifact for running tests, test-runner. Upgrading I didn't add it.
Made also a cleanup in the build.sc file.

Thanks!

Thanks!

Thanks to you for having reviewed this so fast! :)
You are a great maintainer!

authors: lefou lolgab

repo: lihaoyi/mill


text:
Reading unquoted numbers as longs

https://github.com/lihaoyi/upickle/issues/66

I'm gonna not-merge this since it's trivial to set this up in your own project. It introduces an asymmetry between reading and writing I'm not comfortable with including in mainline by default

Just C&P that exact snippet into your own object and import it where you want this behavior =)

@lihaoyi, you already have this kind of asymmetry in all NumericReadWriter: read Str and Num, write Num.

AFAICT that writes Nums and Strs too because Infinity and -Infinity cannot be represented as JSON numbers

authors: lihaoyi senia-psm

repo: lihaoyi/upickle-pprint


text:
Dark theme always loaded even if set to light

Version
4.11.2
Description
I have the component setup like the following:
import ReactJkMusicPlayer from 'react-jinke-music-player';
import 'react-jinke-music-player/assets/index.css';

<ReactJkMusicPlayer
        audioLists={[]}
        mode="full"
        toggleMode={false}
        drag={false}
        remove={false}
        theme="light"
        autoHiddenCover={true}
        showDownload={false} showPlayMode={false} showReload={false} showThemeSwitch={false} showLyric={false}  />

However the music player is still using the dark theme.
I digged a bit further and it looks like the <div class="react-jinke-music-player-main"> element does not have light-theme or dark-theme as a class.

Fixed. thank your feedback. please upgrade 4.12.0


text:
Update the docs

Minor updates!

⭐

authors: arbarlow mattvagni

repo: lileio/lile


text:
WebSocket client

@minwoox's PR #3904 adds the server-side WebSocket support. It'd be awesome if we can also add the client-side WebSocket support, which could be useful for those who implements a WebSocket gateway.
Hypothetical API:
WebSocketClient client = WebSocketClient.of(); // or WebSocketClient.of("https://example.com/ws")

// Perhaps we could introduce an event driven API instead of this?
StreamMessageWriter<WebSocketFrame> out = StreamMessage.streaming();
StreamMessage<WebSocketFrame> in = client.connect(out);

let me try

Thanks for volunteering for this issue. 👍
I'm working on implementing WebSocket service and there are common classes
used both for the WebSocket client and service. Let me finish the service first and ping you so that you can work with those classes. 😄

ok

Hi, @i1619khz! I'm so sorry for taking away your joy but I had to implement this by myself.
https://github.com/line/armeria/pull/4972
After implementing WebSocketService, I need to also implement the client in order to check if they work correctly and modify both sides of APIs if needed. 🙏
Please, let me know if you are interested in implementing another feature. I might give you some help to find it.

Closed by #4972

authors: i1619khz ikhoon minwoox trustin

repo: line/armeria


text:
Get as close as possible to full no_std support

To really get no-std support in parley, we need to land dfrg/swash#63. But I believe I've done everything else that's necessary, in both parley and fontique. One can test the build by patching Cargo.toml to use the working branch for that swash PR, and modifying parley/Cargo.toml to specify swash/std or swash/libm as appropriate. If we decide to land dfrg/swash#63 before landing this one, then I can make the latter modification to parley/Cargo.toml before merging this PR.
Some of my changes, e.g. unconditionally using alloc::vec::Vec, are designed to minimize the amount of noise when searching the whole source tree for "std".

I saw @xorgy's approval. The only reason I'm not merging this immediately is that I wonder if we should land dfrg/swash#63 first, and publish a new version of swash (presumably a semver-breaking release), so we can go all the way with this PR. If people think it would be better to merge this PR immediately, that's fine.

https://github.com/dfrg/swash/pull/63 and https://github.com/dfrg/swash/pull/61 have both landed now. I have submitted a couple of additional PRs for swash and I don't know what his plans are for doing a new release.

I think it's fine to land this and when swash gets released do those steps in a separate PR.
Merged PRs are better than lingering PRs. When work can be split, it should. Helps reduce merge conflicts for yourself and others. Keeps the ball rolling.

authors: mwcampbell waywardmonkeys xStrom

repo: linebender/parley


text:
关于主线程卡顿的问题

你好，请教一下，我最初使用的版本是 0.3.3版本，最近更新到1.5.8,同时执行3个下载任务，然后做其他的操作，发现整个应用非常卡，但是在用0.3.3版本的时候没有这种情况。是我继承的问题嘛？

你可以试试demo project，如果你的主线程的卡顿相关，与demo project点击启动与暂停的时候的反应的情况类似，那么这个问题已经在okdownload中修复。如果是其他问题你这么说我不是很理解，不过FileDownloader中很多点在okdownload中已经得到了大量的优化。

repo: lingochamp/FileDownloader


text:
Implement first version of GraphQL server

3975 RUB reward can be claimed by anyone who completes this task.
This task is continuation of https://github.com/Konard/LinksPlatform/issues/571

i took this task

https://hasura.io/docs/latest/graphql/core/guides/export-graphql-schema.html - tools for schema export

Rewards are:
6000 RUB for @FirstAfterGod2501
4000 RUB for @FreePhoenix888

license: Unlicense


text:
🛑 LinkWave Portal / Accounts is down

In ac208b8, LinkWave Portal / Accounts (https://web.linkwaveconnect.com.br) was down:

HTTP code: 500
Response time: 1679 ms

Resolved: LinkWave Portal / Accounts is back up in b8766ab after 13 hours, 23 minutes.

repo: linkwaveconnect/status


text:
new: update pyenv to use environment name

📝 Description
What does this PR do and why is this change necessary?
Updates pyenv to point to local environment setup by devenv.

LGTM.
Could we reformat /home/runner/work/ansible-specdoc/ansible-specdoc/ansible_specdoc/objects.py as part of this change? Just to fix the lint error.

@yec-akamai Coincidentally I just put up a PR to address this lol. A review would definitely be appreciated! https://github.com/linode/ansible-specdoc/pull/36

authors: jriddle-linode lgarber-akamai

repo: linode/ansible-specdoc


text:
Fix warnings raised during test runs

Closes #381

Coverage increased (+0.1%) to 92.769% when pulling 154dda2d145ba3e8fa9a1dbef6fe9cafef60ce2a on SirCmpwn:test-warnings into 4b0aeedd923a3ebe3d55f5e527ef5182017514df on linode:master.

Nice. There is less change here than I expected there would be.

Nice. There is less change here than I expected there would be.

Ditto.

Thanks!

authors: SirCmpwn coveralls eatonphil

repo: linode/manager


text:
feat: [M3-6535, M3-6537] - Add design tokens for akamai, cloudmanager, and dark/light themes

Major Changes 🔄

Replace light theme values with tokens
Can toggle package w/ /cloudmanager, /akamai, /cloudmanager/dark, and /akamai/dark (dark themes are fake for now)
Condensed our color palette with new mappings according to our design spec

Please add a chageset to your PR 🥺🚨

authors: bnussman jaalah-akamai


text:
fix: [M3-7155] - Link Accessibility & Markup on Billing Detail page

Description 📝
Small PR to improve accessibility and markup on the Billing Detail page since those were bothering me and throwing warnings in the console.

Major Changes 🔄

Provide accessibility to the back button link
Improve markup of the Download CVS Link
Update imports/exports

Preview 📷
This PR should contain no visual regression and should be tested against any.
How to test 🧪
Local Setup:
Pull and run code locally
Steps:

Navigate to /account/billing/invoices/{invoiceId}
Confirm there's no warning in the console about Link Accessibility
Confirm there's no visual regression (no difference from the production page)
Confirm the Download CSV link works as expected

Thanks for tackling this, @abailly-akamai !
Interestingly, even with the accessibleAriaLabel prop, when I use VoiceOver and focus on the "Back to Billing" link, it still gets announced generically as "visited link, billing, main". Navigating and activating the link via keyboard is also touchy; you can still focus the inner button, and when "click" it via the enter key, it triggers the visual click animation but doesn't actually navigate you back to the billing page.
I'll attach screen recordings to M3-7155 momentarily which can probably do a better job explaining what I'm seeing

@jdamore-linode thanks for that! the accessibleAriaLabel was not applied to the react-router-dom RouterLink. It is now, and i addressed the focusing issue. should be better now

authors: abailly-akamai jdamore-linode


text:
Fix adminServerAddr flag usage

admin server addr flag  should be "" by default.
Signed-off-by: Mohamed Abokammer mahmednabil109@gmail.com

Codecov Report

Merging #116 (bc9337c) into main (240ce54) will decrease coverage by 16.18%.
The diff coverage is n/a.

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

@@             Coverage Diff             @@
##             main     #116       +/-   ##
===========================================
- Coverage   65.10%   48.92%   -16.19%
===========================================
  Files         161       92       -69
  Lines       10034     5000     -5034
===========================================
- Hits         6533     2446     -4087
+ Misses       2807     2333      -474
+ Partials      694      221      -473

Flag
Coverage Δ

e2e
?

integration
?

unittests
48.92% <ø> (-0.04%)
:arrow_down:

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

Impacted Files
Coverage Δ

pkg/job/reporting.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/target/locker.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/jobmanager/options.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/pluginregistry/errors.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/xcontext/logger/log_level.go
0.00% <0.00%> (-100.00%)
:arrow_down:

...ext/logger/internal/wrap_minimal_logger_compact.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/job/tags.go
0.00% <0.00%> (-92.00%)
:arrow_down:

pkg/jobmanager/stop.go
0.00% <0.00%> (-83.34%)
:arrow_down:

pkg/xcontext/bundles/logrusctx/new_context.go
0.00% <0.00%> (-82.00%)
:arrow_down:

pkg/jobmanager/jobmanager.go
0.00% <0.00%> (-76.93%)
:arrow_down:

... and 114 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 240ce54...2381f3c. Read the comment docs.

repo: linuxboot/contest


text:
Write basic comms plan

Enabler

So that we can keep users and stakeholder informed, we want to write a basic comms plan
Acceptance Criteria

[ ] We have a basic comms plan that makes sure we cover all teh users and stakeholders captured in the customer onion.

Additional context

Customer Onion and other user analysis is here: https://confluence.linz.govt.nz/display/LGDL/Customer+Onion
Tasks

[ ] Draft a basic comms plan, maybe a simplified version of the Basemaps one
[ ] Review with @vlindsay and team
[ ] Make any changes

Definition of Ready

[ ] This story is ready to work on, according to the
team's definition

Definition of Done

[ ] This story is done, according to the
team's definition

Created a template with headings here:
https://confluence.linz.govt.nz/display/LGDL/Comms+Plan

Closing. Well reviewed and followup stories created.

repo: linz/geostore


text:
django-admin inspectdb

Not sure if this is realy implemeted and tested. Got the following exception:
django-admin inspectdb --database=mymssqlserver

# This is an auto-generated Django model module.
# You'll have to do the following manually to clean this up:
#   * Rearrange models' order
#   * Make sure each model has one field with primary_key=True
#   * Remove `managed = False` lines if you wish to allow Django to create, modify, and delete the table
# Feel free to rename the models, but don't rename db_table values or field names.
#
# Also note: You'll have to insert the output of 'django-admin sqlcustom [app_label]'
# into your database.
from __future__ import unicode_literals

from django.db import models
Traceback (most recent call last):
  File "/opt/deep-python-lib/bin/django-admin", line 11, in <module>
    sys.exit(execute_from_command_line())
  File "/opt/deep-python-lib/lib/python2.7/site-packages/django/core/management/__init__.py", line 338, in execute_from_command_line
    utility.execute()
  File "/opt/deep-python-lib/lib/python2.7/site-packages/django/core/management/__init__.py", line 330, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/opt/deep-python-lib/lib/python2.7/site-packages/django/core/management/base.py", line 393, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/opt/deep-python-lib/lib/python2.7/site-packages/django/core/management/base.py", line 444, in execute
    output = self.handle(*args, **options)
  File "/opt/deep-python-lib/lib/python2.7/site-packages/django/core/management/commands/inspectdb.py", line 25, in handle
    for line in self.handle_inspection(options):
  File "/opt/deep-python-lib/lib/python2.7/site-packages/django/core/management/commands/inspectdb.py", line 55, in handle_inspection
    for table_name in connection.introspection.table_names(cursor):
  File "/opt/deep-python-lib/lib/python2.7/site-packages/django/db/backends/base/introspection.py", line 58, in table_names
    return get_names(cursor)
  File "/opt/deep-python-lib/lib/python2.7/site-packages/django/db/backends/base/introspection.py", line 53, in get_names
    return sorted(ti.name for ti in self.get_table_list(cursor)
  File "/opt/deep-python-lib/lib/python2.7/site-packages/django/db/backends/base/introspection.py", line 54, in <genexpr>
    if include_views or ti.type == 't')
AttributeError: 'unicode' object has no attribute 'type'

A short look into django/db/backends/base/introspection.py pointed out that get_table_list()
should return a list of objects with attributes like name and type, but django-pyodbc's get_table_list() returns a list of table name unicodes.

I am getting very similar error when just trying to do a runserver:
python manage.py runserver
File "/usr/lib/python2.7/site-packages/django/utils/autoreload.py", line 225, in wrapper
fn(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/django/core/management/commands/runserver.py", line 112, in inner_run
self.check_migrations()
File "/usr/lib/python2.7/site-packages/django/core/management/commands/runserver.py", line 164, in check_migrations
executor = MigrationExecutor(connections[DEFAULT_DB_ALIAS])
File "/usr/lib/python2.7/site-packages/django/db/migrations/executor.py", line 19, in init
self.loader = MigrationLoader(self.connection)
File "/usr/lib/python2.7/site-packages/django/db/migrations/loader.py", line 47, in init
self.build_graph()
File "/usr/lib/python2.7/site-packages/django/db/migrations/loader.py", line 182, in build_graph
self.applied_migrations = recorder.applied_migrations()
File "/usr/lib/python2.7/site-packages/django/db/migrations/recorder.py", line 59, in applied_migrations
self.ensure_schema()
File "/usr/lib/python2.7/site-packages/django/db/migrations/recorder.py", line 49, in ensure_schema
if self.Migration._meta.db_table in self.connection.introspection.table_names(self.connection.cursor()):
File "/usr/lib/python2.7/site-packages/django/db/backends/base/introspection.py", line 58, in table_names
return get_names(cursor)
File "/usr/lib/python2.7/site-packages/django/db/backends/base/introspection.py", line 53, in get_names
return sorted(ti.name for ti in self.get_table_list(cursor)
File "/usr/lib/python2.7/site-packages/django/db/backends/base/introspection.py", line 54, in
if include_views or ti.type == 't')
AttributeError: 'unicode' object has no attribute 'type'

Can you guys post SSCCEs, specify the versions of all your packages with pip freeze, and specify the vendor and version of the database you're connecting to?

Python 2.7.6
Microsoft SQL Server 2014 - 12.0.4213.0 (X64)

# pip freeze
alabaster==0.7.6
ansible==1.9.3
apt-xapian-index==0.45
apturl===0.4.1ubuntu4
Babel==1.3
BeautifulSoup==3.2.1
chardet==2.0.1
colorama==0.2.5
command-not-found==0.3
configglue==1.1.2
configobj==4.7.2
debtagshw==0.1
defer==1.0.6
defusedxml==0.4.1
deluge==1.3.6
dirspec==13.10
distro-info==0.12
Django==1.8.4
django-autocomplete-light==2.2.6
django-cors-headers==1.1.0
django-countries==3.3
django-filter==0.11.0
django-grappelli==2.7.1
django-model-utils==2.3.1
django-pyodbc==0.3.0
django-reversion==1.9.3
django-taggit==0.17.1
djangorestframework==2.4.6
djangorestframework-jsonp==1.0.2
djangorestframework-xml==1.2.0
djangorestframework-yaml==1.0.2
dnspython==1.11.1
docutils==0.11
docx==0.2.4
docx-xslt==1.0.4
dulwich==0.9.4
duplicity==0.6.23
ecdsa==0.13
enum==0.4.4
Fabric==1.10.2
feedparser==5.1.3
gevent==1.0.2
greenlet==0.4.9
grequests==0.2.0
hg-git==0.8.0
html5lib==0.999
httplib2==0.8
ida===2.2.10-20-g3077
IPy==0.83
jdcal==1.0
Jinja2==2.7.2
keyring==3.5
launchpadlib==1.10.2
lazr.restfulclient==0.13.3
lazr.uri==1.0.3
lockfile==0.8
lxml==3.4.4
Mako==0.9.1
Markdown==2.6.2
MarkupSafe==0.18
mechanize==0.2.5
mercurial==2.8.2
MySQL-python==1.2.3
nemo-emblems==0.0.1
numpy==1.8.2
oauth==1.0.1
oauthlib==0.6.1
oneconf==0.3.7.14.4.1
openpyxl==2.2.3
PAM==0.4.2
paramiko==1.15.2
pathlib==1.0.1
pexpect==3.1
Pillow==2.9.0
piston-mini-client==0.7.5
protobuf==2.5.0
pycrypto==2.6.1
pycups==1.9.66
pycurl==7.19.3
Pygments==2.0.2
pygobject==3.12.0
pyinotify==0.9.4
pyodbc==3.0.10
pyOpenSSL==0.13
pyserial==2.6
pysmbc==1.0.14.1
python-apt===0.9.3.5ubuntu1
python-dateutil==2.4.2
python-debian===0.1.21-nmu2ubuntu2
python-libtorrent==0.16.13
python-money==0.3.3
pytz==2015.6
pyxdg==0.25
PyYAML==3.11
reportlab==3.0
requests==2.7.0
roman==2.0.0
sessioninstaller==0.0.0
simplejson==3.8.0
six==1.9.0
snowballstemmer==1.2.0
South==1.0.2
Sphinx==1.3.1
sphinx-rtd-theme==0.1.8
sqlparse==0.1.10
system-service==0.1.6
tortoisehg==2.10
Twisted-Core==13.2.0
Twisted-Names==13.2.0
Twisted-Web==13.2.0
ubuntu-dev-tools==0.153
Unidecode==0.4.18
urllib3==1.7.1
uTidylib==0.2
uWSGI===2.1-dev-abac960
uwsgitop==0.8
vboxapi==1.0
wadllib==1.3.2
wheel==0.26.0
XlsxWriter==0.7.3
zope.interface==4.0.5

Python 2.7.5, Microsoft SQL server 2012
ansible==1.7.1
appdirs==1.4.0
astroid==1.3.8
Babel==2.1.1
backports.ssl-match-hostname==3.4.0.2
bash8==0.1.1
bzt==0.4.2
certifi==2015.9.6.2
chardet==2.0.1
click==5.1
cliff==1.15.0
cliff-tablib==1.1
cmd2==0.6.8
colorama==0.3.3
colorlog==2.6.0
configobj==4.7.2
cookies==2.2.1
coverage==3.7.1
cssselect==0.9.1
debtcollector==0.8.0
decorator==4.0.4
Django==1.8.4
django-pyodbc==0.3.0
djangorestframework==3.1.1
ethtool==0.8
flake8==2.4.0
freezegun==0.3.4
functools32==3.2.3.post2
gitlint==0.4.1
heighliner==0.5.1
httpie==0.9.2
httplib2==0.7.7
iniparse==0.4
ipdb==0.8.1
ipython==4.0.0
ipython-genutils==0.1.0
iso8601==0.1.10
javapackages==1.0.0
Jinja2==2.7.2
jsonpatch==1.11
jsonpointer==1.9
jsonschema==2.5.1
keystoneauth1==1.1.0
kitchen==1.1.1
livereload==2.4.0
logilab-common==1.0.2
lxml==3.4.4
M2Crypto==0.21.1
mando==0.3.3
Markdown==2.6.2
MarkupSafe==0.11
mccabe==0.3.1
mkdocs==0.14.0
mock==1.0.1
monotonic==0.3
msgpack-python==0.4.6
MySQL-python==1.2.3
netaddr==0.7.18
netifaces==0.10.4
newdawn-qa==2015.2.0.dev203
nose==1.3.7
os-client-config==1.7.5
oslo.config==2.4.0
oslo.i18n==2.6.0
oslo.serialization==1.9.0
oslo.utils==2.5.0
paramiko==1.11.3
path.py==8.1.1
pbr==1.8.0
pciutils==1.7.3
pep8==1.5.7
pexpect==3.3
pickleshare==0.5
prettytable==0.7.2
progressbar33==2.4
psutil==3.2.1
pyasn1==0.1.6
pycrypto==2.6.1
pycurl==7.19.0
pyflakes==0.8.1
Pygments==2.0.2
pygobject==3.8.2
pygpgme==0.3
pygraphviz==1.2
pyliblzma==0.5.3
pylint==1.4.4
pyodbc==3.0.10
pyOpenSSL==0.13.1
pyparsing==2.0.3
python-cinderclient==1.4.0
python-dateutil==2.4.2
python-dmidecode==3.10.13
python-glanceclient==1.1.0
python-keyczar==0.71rc0
python-keystoneclient==1.7.1
python-neutronclient==3.1.0
python-novaclient==2.30.0
python-openstackclient==1.7.0
pytz==2015.6
pyudev==0.15
pyxattr==0.5.1
PyYAML==3.11
radon==1.2.1
requests==2.7.0
responses==0.4.0
rhnlib==2.5.65
rhsm==1.10.12
selenium==2.47.3
sh==1.11
simplegeneric==0.8.1
simplejson==3.8.0
six==1.9.0
slip==0.4.0
slip.dbus==0.4.0
stevedore==1.8.0
tablib==0.10.0
tornado==4.2.1
traitlets==4.0.0
unicodecsv==0.14.1
urlgrabber==3.10
urwid==1.3.0
warlock==1.1.0
wrapt==1.10.5
yum-metadata-parser==1.1.4
I looked a bit into the introspection.py as well, get_table_list needs to return a list of TableInfo(), it does require an adjustment to the SQL Queries to get the TABLE_INFO to include with the TableInfo().  Then a SchemaEditor also needs to be included: https://docs.djangoproject.com/en/1.8/ref/schema-editor/

Same issue with
Python 2.7.11
Microsoft SQL Server 2012
broke in the same place as above

I am having the same issue with manage.py runserver.
Platform: Mac OS X 10.11.5
Python 2.7.12
installed via macports:
unixODBC @2.3.2_0
freetds @1.00.9_0+odbc (active)
pip freeze output:
Django==1.8.14
django-pyodbc==0.3.0
pyodbc==3.0.10
DB Server: Microsoft SQL Server 2012
changes to settings.py:
DATABASES = {
'default': {
'ENGINE': "django_pyodbc",
'HOST': "myhostname,1433",
'USER': "myusername",
'PASSWORD': "mypassword",
'NAME': "mydbname",
'OPTIONS': {
'host_is_server': True,
},
}
}
Connections have been checked successfully with tsql and isql.
Stack trace:
Unhandled exception in thread started by <function wrapper at 0x108608d70>
Traceback (most recent call last):
File "/Users/aron/DEV/VENVS/higgins-venv/lib/python2.7/site-packages/django/utils/autoreload.py", line 229, in wrapper
fn(*args, **kwargs)
File "/Users/aron/DEV/VENVS/higgins-venv/lib/python2.7/site-packages/django/core/management/commands/runserver.py", line 116, in inner_run
self.check_migrations()
File "/Users/aron/DEV/VENVS/higgins-venv/lib/python2.7/site-packages/django/core/management/commands/runserver.py", line 168, in check_migrations
executor = MigrationExecutor(connections[DEFAULT_DB_ALIAS])
File "/Users/aron/DEV/VENVS/higgins-venv/lib/python2.7/site-packages/django/db/migrations/executor.py", line 19, in init
self.loader = MigrationLoader(self.connection)
File "/Users/aron/DEV/VENVS/higgins-venv/lib/python2.7/site-packages/django/db/migrations/loader.py", line 47, in init
self.build_graph()
File "/Users/aron/DEV/VENVS/higgins-venv/lib/python2.7/site-packages/django/db/migrations/loader.py", line 191, in build_graph
self.applied_migrations = recorder.applied_migrations()
File "/Users/aron/DEV/VENVS/higgins-venv/lib/python2.7/site-packages/django/db/migrations/recorder.py", line 59, in applied_migrations
self.ensure_schema()
File "/Users/aron/DEV/VENVS/higgins-venv/lib/python2.7/site-packages/django/db/migrations/recorder.py", line 49, in ensure_schema
if self.Migration._meta.db_table in self.connection.introspection.table_names(self.connection.cursor()):
File "/Users/aron/DEV/VENVS/higgins-venv/lib/python2.7/site-packages/django/db/backends/base/introspection.py", line 58, in table_names
return get_names(cursor)
File "/Users/aron/DEV/VENVS/higgins-venv/lib/python2.7/site-packages/django/db/backends/base/introspection.py", line 53, in get_names
return sorted(ti.name for ti in self.get_table_list(cursor)
File "/Users/aron/DEV/VENVS/higgins-venv/lib/python2.7/site-packages/django/db/backends/base/introspection.py", line 54, in
if include_views or ti.type == 't')
AttributeError: 'unicode' object has no attribute 'type'

authors: RossRogers aronroberts backbohne moird stanep

repo: lionheart/django-pyodbc


text:
预览画面显示gif  取出视频的一些帧 生成一个GIF  显示出来

**需求描述
**其他app是否实现
**截图或者小视频说明

**需求描述
**其他app是否实现
小红书 实现了的
**截图或者小视频说明

么么哒，生成gif能解决吗

repo: lipangit/JiaoZiVideoPlayer


text:
Postgres: deleteCascade="true" works when inlined in , but not in

Environment
Liquibase Version: 4.4.1
Liquibase Integration & Version: Usage from code
Database Vendor & Version: PostgreSQL 13
Operating System Type & Version: Ubuntu 21.04 (irrelevant)
Description
At least in case of PostgreSQL:
<addForeignKeyConstraint baseTableName="payments" baseColumnNames="cardId" constraintName="payments_card_fk"
                             referencedTableName="payment_cards" referencedColumnNames="id" deleteCascade="true"/>

This code doesn't add on delete cascade to the foreign key constraint.
However, this one adds:
    <addForeignKeyConstraint baseTableName="payments" baseColumnNames="cardId" constraintName="payments_card_fk"
                             referencedTableName="payment_cards" referencedColumnNames="id" onDelete="CASCADE"/>

Both are valid in terms of XSD.
We are checking the created constraint using:
SELECT pg_get_constraintdef(oid) AS constraint_def
FROM   pg_constraint
WHERE  conname = 'payments_receivable_fk';

However, the former syntax works as part of , e.g.
<column name="orderId" type="uuid"><constraints nullable="false" foreignKeyName="decisions_order_fk" referencedTableName="orders" referencedColumnNames="id" deleteCascade="true"/></column>

Steps To Reproduce
Just run both changesets and check the created constraints.
Actual Behavior
See above
Expected/Desired Behavior
Both versions (provided they are valid by XSD) should add "on delete cascade" to the created constraint, or the former version should be deprecated and removed from XSD.

Hi @cbxp Thanks for alerting us to this issue.  We will add it to the list of issues we are processing.

authors: cbxp molivasdat

repo: liquibase/liquibase


text:
Aliasing error during eigen decomposition

Hey there,
I found your library really useful so far and I am really surprised by its efficiency. However, I am experiencing some aliasing issues. The following code fails during embedding. Note that I have defined TAPKEE_CUSTOM_INTERNAL_NUMTYPE as float. 1
// Create a matrix with 512x512 32-dim features.
tapkee::DenseMatrix descriptors(32, 262144);

// Randomly fill the matrix.
for (int i(0); i < 32; ++i)
for (int j(0); j < 262144; ++j)
	descriptors(i, j) = static_cast<float>(std::rand()) / static_cast<float>(RAND_MAX);

// Reduce to dim 8 using PCA.
tapkee::ParametersSet parameters = tapkee::kwargs[
	tapkee::method = tapkee::PCA,
	tapkee::target_dimension = 8
];

// Perform PCA
tapkee::TapkeeOutput result = tapkee::initialize()
	.withParameters(parameters)
	.embedUsing(descriptors);

Basically I want to reduce a set of 512x512 32 dimensional features to 8D, which I randomly initialize for demonstration purposes. When ran in debug-mode (under Win64), Eigen detects aliasing:

aliasing detected during transposition, use transposeInPlace() or evaluate the rhs into a temporary using .eval()

The error is raised during eigen decomposition (eigendecomposition.hpp):
//! Eigen library dense implementation of eigendecomposition-based embedding
template <class MatrixType, class MatrixOperationType>
EigendecompositionResult eigendecomposition_impl_dense(const MatrixType& wm, IndexType target_dimension, unsigned int skip)
{
	timed_context context("Eigen library dense eigendecomposition");

	DenseSymmetricMatrix dense_wm = wm;
	dense_wm += dense_wm.transpose();	// Invalid.
	dense_wm /= 2.0;
	DenseSelfAdjointEigenSolver solver(dense_wm);

	// ...
}

It relates to the issues described here. Changing this line to dense_wm += dense_wm.transpose().eval(); resolves the issue. I think transposeInPlace() should also work, however I was not able to get it to compile that way.
Did I miss something or is this an actual bug?!
1 Also note that the documentation says TAPKEE_CUSTOM_NUMTYPE, which is actually incorrect.

Hey, thanks for the report.
It seems to be an actual bug. The eval thing resolves that indeed but it would bump the memory usage 2x for a moment. Let me check if there is a memory-efficient solution.

It seems that eval should be here.
I just added it in ec3514033c036795ca819d3ac68b61a58d24ac53

Thank you for the fast fix!

authors: Aschratt lisitsyn

repo: lisitsyn/tapkee


text:
[labs] Adds initial implementation of @lit-labs/context

This is the very first draft of an initial implementation of lit reactive controllers for the Context API. There's still a lot to do for this to be complete, but hopefully can be used as a good basis for moving forward with the propose API.
This version is implemented against the 'react-like' version of the context API outlined here.
I set this up by cloning one of the other packages, so hopefully its mostly in line with coding style. Would love to hear feedback on this, and I'm sure we'll continue discussion on the Context API over in the community protocols group.

This is great. It may be a bit until we can review this thoroughly but the core proposal seems really good.

This is great. It may be a bit until we can review this thoroughly but the core proposal seems really good.

No problem. I am away until next Tuesday now anyway. I will likely get the work done to align the proposal with this implementation then too.

Hey :D No intention to intrude, but any news about @lit-labs/context being merged? We are waiting for it with enthusiasm!

Hey :D No intention to intrude, but any news about @lit-labs/context being merged? We are waiting for it with enthusiasm!

Good call out, I have let this stagnate as I've been caught up at work with many other things. I'll try and take another look at this asap. @justinfagnani I assume pushing ahead with this as labs release is still ok with the team?

@renoirb thanks for the notes, please be aware I am currently tied up in product launch issues and won't get to update lit-context until sometime in the next couple of weeks. At which point I'm going to make a complete laser focus on getting this finalized.
This PR has also fallen well behind main now so I am likely to close it and reopen after a rebase to the head to bring in lit2 support and cleanup a number of issues and changes which have come out of CG discussion.

I've made some major changes to the implementation, but I think where its at now is probably stable and would love if folks could find some time to re-review.
Most major change is a shift towards controllers and decorators:
ContextConsumer is a controller which emits context-request and executes a given callback when the request is satisfied, as per community protocol for these events.
ContextProvider is a controller which stores a value using a ContextContainer and handles the provider side of the protocol. The provider controller also emits a context-provider event to advertise the providers availability when connected to the dom this is used by ContextRoot described below.
@contextRequest is a property decorator for requesting a context and binding its value to a property.
@contextProvider the associated provider decorator, which shims the property setter it decorates and updates the ContextProvider controller on property change.
I've also added a ContextRoot implementation which can track context-request and context-provider events to resolve unsatisfied requests when providers advertise their availabiilty. This provides a simple mechanism for resolving late-upgraded context providers without leaning too much into event pathing which on investigation has proven to be somewhat unreliable once you trace out all behaviors of slotted elements and portalling components used in various libraries.
Would love any feedback on this, and advise from the lit team on how to get this PR over the hurdle and committed.

Hey @benjamind I really love this PR and am looking forward to it very much :) Thank you so much :)
Just a small thing I noticed:
We have the classes ContextProvider and ContextConsumer
Also we have the decorators @contextProvide and @contextRequest
Now I am wondering, why not name @contextRequest => @contextConsumer?
This would make it more consistent with the class names and also improve the general ease of use, as people would expect to have a consumer when there is a provider. :)

Agreed I think some naming consistency tweaks are in order. I wasn't sure which way to go specifically, Requestor / Provider or Consumer / Provider? I left it as is hoping someone would comment one preference over the other so thank you for bringing it up!

prefer consumer/provider. it's more current IMO

by-the-way i'm looking to implement context protocol in patternfly elements. so far i just copy-pasted from the protocol proposal but this is looking PHAT

Actually is there any eta, when this will be available it @lit-labs?

Think this is ready for another pass @sorvell, can someone also approve the CI workflows so we can get a test run going?

Now I am wondering, why not name @contextRequest => @contextConsumer?
This would make it more consistent with the class names and also improve the general ease of use, as people would expect to have a consumer when there is a provider. :)

@sorvell  what do you think of this suggestion?

Hi Benjamin!, I've noticed when you open the project in VSCode only in packages/labs/context/ and see many import typing errors. Tests runs, but development and type checking doesn't work.
Here is what I changed to solve.
From 272f1a5699462dea53e192c620ab4f8450bd4008 Mon Sep 17 00:00:00 2001
From: Renoir Boulanger <contribs@renoirboulanger.com>
Date: Wed, 23 Mar 2022 19:52:35 -0400
Subject: [PATCH] local development typing errors

---
 packages/labs/context/tsconfig.json | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/packages/labs/context/tsconfig.json b/packages/labs/context/tsconfig.json
index 19e97352..74105763 100644
--- a/packages/labs/context/tsconfig.json
+++ b/packages/labs/context/tsconfig.json
@@ -22 +22,6 @@
-    "experimentalDecorators": true
+    "experimentalDecorators": true,
+    "paths": {
+      "lit/decorators": ["../../lit/decorators"],
+      "lit": ["../../lit"],
+      "@lit/*": ["../../"],
+    }
--
2.30.1 (Apple Git-130)

Hi Benjamin!, I've noticed when you open the project in VSCode only in packages/labs/context/ and see many import typing errors. Tests runs, but development and type checking doesn't work.
Here is what I changed to solve....

@sorvell can you comment on if this change is correct, I'm not sure the repo supports working in a single package like this in VSCode?

@sorvell can you comment on if this change is correct, I'm not sure the repo supports working in a single package like this in VSCode?

That's what I'm doing at the moment, it works well.

VSCode opened in packages/labs/context/
In terminal below, run ./scripts/dev.sh

And notice the lack of distracting red underlined text.

@benjamind

Agreed I think some naming consistency tweaks are in order. I wasn't sure which way to go specifically, Requestor / Provider or Consumer / Provider?

Just wanted to kindly ask if you made a decision as to where to go, as it seems like those inconsistencies are still present, but also I feel like most people prefer the provider - consumer approach judging by the comments

@benjamind

Agreed I think some naming consistency tweaks are in order. I wasn't sure which way to go specifically, Requestor / Provider or Consumer / Provider?

Just wanted to kindly ask if you made a decision as to where to go, as it seems like those inconsistencies are still present, but also I feel like most people prefer the provider - consumer approach judging by the comments

The controllers are called ContextConsumer and ContextProvider, we still have a context-request event which aligns with the community protocol. So I think this is all resolved now?

@LasseRosenow The controllers are called ContextConsumer and ContextProvider, we still have a context-request event which aligns with the community protocol. So I think this is all resolved now?

We still have the inconsistency with the decorator being called contextRequest while the class is called 'contextConsumer'

@LasseRosenow The controllers are called ContextConsumer and ContextProvider, we still have a context-request event which aligns with the community protocol. So I think this is all resolved now?

We still have the inconsistency with the decorator being called contextRequest while the class is called contextConsumer
Of course the event should keep it's name ;)

@LasseRosenow yes but I think @contextConsumer doesn't really describe what it does? Compare these two snippets:
@contextRequest({ context: loggerContext })
@property({attribute: false}
public logger?: Logger;

with
@contextConsumer({ context: loggerContext })
@property({attribute: false}
public logger?: Logger;

I might be willing to rename to contextProvided perhaps? This would align with some Adobe internal approaches to this.
@contextProvided({ context: loggerContext })
@property({attribute: false}
public logger?: Logger;

Regarding the decorator name: I could see something like @contextValue() as well.

Regarding the decorator name: I could see something like @contextValue() as well.

I renamed to @contextProvided in 79da874. I didn't like the overlap with the value of the context that @contextValue implies and @contextProvided does to me seem to state more what the intention is of the decorated property? We can revise in future if needs be.

Phew! All issues addressed, I think this is ready to merge after CI passes?

Can we merge https://github.com/lit/lit/commit/79da87440b53a67aac74514962b9cad1e6243462 with this?

Can we merge 79da874 with this?

Confused what do you mean?

@benjamind https://github.com/lit/lit/commit/79da87440b53a67aac74514962b9cad1e6243462 didn't make it into this PR somehow. I see that it's not a branch in the repo even, but it is a branch in your fork.

Well that's just weird. Will fix this morning.

I'm struggling to see the issue, the commit is showing for me in the commits associated with this PR: https://github.com/lit/lit/pull/1955/commits
Second from the bottom?

@benjamind huh... you're right seems fine. Maybe GitHub is just confusing us with the warning it puts at the top of a commit link from a PR from a work. It's warning that the commit is not part of this repository.

Success! Thanks everyone for the help and input on this one, it was a long time coming together but looking forward to this getting usage in the wild!

authors: LasseRosenow benjamind bennypowers guillemcordoba justinfagnani renoirb sorvell

repo: lit/lit


text:
Error while using literallycanvas with React 17 TypeScript Template

I have a React project with TypeScript template and i'm using literallycanvas library in this project.
I tested this library in Javascript React project, and it's OK, but when i change to TypeScript Project, it have UI error.
How can i fix this?

Is any solution available to work with typescript

authors: ViNguyenHoang aryanisml

repo: literallycanvas/literallycanvas


text:
Q: Where to get the document of Google-QUIC standard?

Not IETF-QUIC standard.
I want to know the details of Q046 or Q050. Where can I get the document?

There is no documentation: you'll have to read the source code -- either lsquic or Chromium.

I take it back: there is also this:
https://tools.ietf.org/html/draft-hamilton-quic-transport-protocol-01

authors: cang-mang dtikhonov

repo: litespeedtech/lsquic


text:
feat: psycopg asyncio support, BigInteger PK option, and binary GUIDs

Pull Request Checklist

[ ] New code has 100% test coverage
[ ] (If applicable) The prose documentation has been updated to reflect the changes introduced by this PR
[ ] (If applicable) The reference documentation has been updated to reflect the changes introduced by this PR

Description
Introduces the BigIntPK mixin for SQLAlchemy 2 contrib.
Adds psycopg tests for the sqlalchemy repository
Store GUIDs as binary on databases that don't have a native GUID type.
Close Issue(s)

Hey, overall, I think this is the way to go.  Based on some conversation today, I think we need to provide a non-uuid based PK as well.
There are a few places in the documentations and examples where we are building a new Base from DeclarativeBase.  We don't want to update these examples.

I've broken the docs, somehow.
But this now adds in a custom BigIntIdentity SQL Alchemy data type.  sqlite only support auto-incrementing primary keys with an Integer type.  This type will use BigInteger where possible and fail back to Integer for sqlite.

@cofin

I've broken the docs, somehow.

Fixed it! The classes were missing from __all__ and there were some indentation issues with a list

@cofin I think you broke it again with your force push :grimacing:

You weren't supposed to see that!

Closing this and re-opening it.

authors: JacobCoffee cofin provinzkraut

repo: litestar-org/litestar


text:
conf/ecpix5.dts: fix typo

The o in the address should be an 0.

Thanks @tretter, that's merged.

authors: enjoy-digital tretter

repo: litex-hub/linux-on-litex-rocket


text:
[AWS Lambda] Pin urllib3 version

According to this, as of today botocore is not yet compatible with urllib3 2.0
#1121
#1104
Developer's Certificate of Origin 1.1
   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

@JosepSampe Hi, did pinning solve the issue? I also tried this before but didn't work and I gave up :sweat:

@aitorarjona For me with python 3.10 yes

authors: JosepSampe aitorarjona

repo: lithops-cloud/lithops


text:
chore(litmus-portal): Added unique attributes in frontend for E2E testing and minor CSS changes

Proposed changes
This PR adds:

Unique attributes required for E2E tests
Refactored the LinearProgressBar Component
Minor CSS fixes

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

[ ] New feature (non-breaking change which adds functionality)
[x] 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:

@amityt Can you add the key property to the two divisions! deepscan is complaining about the same

@S-ayanide DeepScan issues fixed :heavy_check_mark:

/run-unit

authors: Jonsy13 S-ayanide amityt

repo: litmuschaos/litmus


text:
(chore)license: add license notice

Signed-off-by: ksatchit ksatchit@mayadata.io

What this PR does / why we need it:

Adds license notice files for test tools

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:

There are no modified subcomponents, though they are pulled as dependencies (vendor) https://app.fossa.com/attribution/a8a6a1e8-164c-4803-a1b3-84a794765f3c

repo: litmuschaos/test-tools


text:
feat: add support for other platforms than linux and improved, reading, sending

towards #1

Added getIPCPath which returns IPC-pipe path based on OS.
Added findIPC which returns path that is currently active.
Added reworked packet reading in form of new #read method.

Had a few questions before I could start working on support for more commands, for which I've made NOTE comments.
Pretty much WIP, haven't tested as I use Windows and there's no unix socket support.. I'll try on a VM.
There's cool things like editing voice setting, creating game lobbies, selecting text channels, etc. which discord-ipc can do 😉

Should I be using unique Symbols instead of #private fields (like _ipcHandle)?

Should I be using unique Symbols instead of #private fields (like _ipcHandle)?

private fields are fine. _ipcHandle is a symbol because I didn't want users to use DiscordIPC's constructor directly

Private properties seem to have some problem with the way DiscordIPC object is being created

Hmm yeah downside of using private properties. Let's just use Symbols for now - I really don't want users to be able to use the constructor as its not part of the public API

Changed it to use symbols. However, now whenever I try to read from Conn am getting this error 🤔

Tested on Ubuntu VM, seems to work

How would events work? Should it extend a EventEmitter (std or x/event), EventTarget + on* or a just Async Iterator?

How should events work? Should it extend a EventEmitter (std or x/event), EventTarget + on* or a just Async Iterator?

Preferably async iterators

authors: DjDeveloperr littledivy


text:
Using LittleFS for Winbond W25Q16JW

Hello,
I am currently working on implementing LittleFS on the Winbond W25Q16JW through SPI. I have verified that I am able to interface with the chip manually, being able to read and write to it.
The W25Q16JW array is organized into 8192programmable pages of 256-bytes each. Up to 256 bytes can be programmed at a time. Pages can be erased in groups of 16 (4KB sector erase), groups of 128 (32KB block erase), groups of 256 (64KB block erase) or the entire chip (chip erase). The W25Q16JWhas 512 erasable sectors and 32 erasable blocks respectively.
After tuning my config to fit the specs of the chip, I am having issues being able to format the chip. After commenting out the LFS_DEBUG printf functions from lfs.c (as they were causing hard faults), lfs_format() is returning an error code of -28 in main.
Is there anything I am doing explicitly wrong? Thanks!
Here is what my code look like:
Declaring structs:
// variables used by the filesystem
lfs_t lfs;
lfs_file_t file;
struct lfs_config cfg;

uint8_t lfs_read_buf[256];
uint8_t lfs_prog_buf[256];
uint8_t lfs_lookahead_buf[128];	// 128/8=16
uint8_t lfs_file_buf[256];

Linking I/O funtions:
int block_device_read(const struct lfs_config *c, lfs_block_t block,
	lfs_off_t off, void *buffer, lfs_size_t size)
{
	w25->readData((uint32_t)(block*c->block_size + off), (char*)buffer, size);
	return 0;
}

int block_device_prog(const struct lfs_config *c, lfs_block_t block,
	lfs_off_t off, const void *buffer, lfs_size_t size)
{
	w25->pageWrite((uint32_t)(block*c->block_size + off), (char*)buffer, size);

	return 0;
}

int block_device_erase(const struct lfs_config *c, lfs_block_t block)
{
	w25->sectorErase(block*c->block_size);
	return 0;
}

int block_device_sync(const struct lfs_config *c)
{
	return 0;
}

Config function:

// configuration of the filesystem is provided by this struct
void LFS_Config(void)
{
	// block device operations
	cfg.read  = block_device_read;
	cfg.prog  = block_device_prog;
	cfg.erase = block_device_erase;
	cfg.sync  = block_device_sync;

	// block device configuration
	cfg.read_size = 256;
	cfg.prog_size = 256;
	cfg.block_size = 4096;
	cfg.block_count = 4096;
	cfg.cache_size = 512;
	cfg.lookahead_size = 128;
	cfg.block_cycles = 500;

	cfg.read_buffer = lfs_read_buf;
	cfg.prog_buffer = lfs_prog_buf;
	cfg.lookahead_buffer = lfs_lookahead_buf;
//	cfg.file_buffer = lfs_file_buf;
}

I/O I am having issues with in main.cpp
  int res = 0;
  LFS_Config();
  res = lfs_format(&lfs, &cfg);
  res = lfs_mount(&lfs, &cfg);
  res = lfs_file_open(&lfs, &file, "", LFS_O_CREAT | LFS_O_RDWR);
  res = lfs_file_write(&lfs, &file, "abcedfghijklmn", 14);
  res = lfs_file_read(&lfs, &file, readBuffer, 14);

Functions that explicitly handle the i/o on the chip:
void SPIFlash::readData(uint32_t addr, char* data, uint32_t len) {
	//Reads a length of data from a given address
	  cs_set();
	  outBuffer[0] = W25_READ_DATA;
	  outBuffer[1] = (addr >> 16) & 0xFF;
	  outBuffer[2] = (addr >> 8) & 0xFF;
	  outBuffer[3] = addr & 0xFF;
	  sendSPI(outBuffer, 4);
	  recvSPI(data, len);
	  cs_reset();
	  usDelay(1);
}

void SPIFlash::pageWrite(uint32_t addr, char* data, uint32_t len) {
	/* [Public Method]
	 *  Writes to a given page in memory.
	 *
	 *  len defaults to the page size. If len is less than the page size,
	 *  the function will only write to a page however much data is specified.
	 */

	if (len > PAGE_SIZE) len = PAGE_SIZE;

	enableWrite(true);
	cs_set();
	outBuffer[0] = W25_PAGE_PROGRAM;
	outBuffer[1] = (addr >> 16) & 0xFF;
	outBuffer[2] = (addr >> 8) & 0xFF;
	outBuffer[3] = addr & 0xFF;
	for (int i = 0; i < len; i++) outBuffer[i+4] = data[i];
	sendSPI(outBuffer, len + 4);
	cs_reset();
	enableWrite(false);
	usDelay(1);
}

void SPIFlash::sectorErase(uint32_t addr) {
	/* [Public Method]
	 * Wipes a given sector from memory
	 */
	  cs_set();
	  outBuffer[0] = W25_SECTOR_ERASE;
	  outBuffer[1] = (addr >> 16) & 0xFF;
	  outBuffer[2] = (addr >> 8) & 0xFF;
	  outBuffer[3] = addr & 0xFF;
	  sendSPI(outBuffer, 4);
	  cs_reset();
}

Here's something I encountered with a similar Winbond device (a *JV variant). Given that you say that you can already read & write to the device this may not be the problem, but I thought it was worth checking, none-the-less.
You don't show what enableWrite() does. This could either be playing with the Write Protect (WP) line, and/or sending a WriteEnable SPI instruction. The fact that you don't have the chip select line asserted before enableWrite() makes me think that you might only be toggling the WP line. (And you don't seem to be doing anything in sectorErase() to enable writes)
You need to make sure that both the WP line is deasserted, as well as sending a WriteEnable (06h) SPI instruction before every PageProgram, or Sector/Block/Chip erase SPI transaction.
I got caught out on this, and thought it was only required once per page program. Because I have to split my page programs up into multiple SPI transactions, only the first partial page program operation would succeed.

Hi! I appreciate the response but I don't think thats the issue. I have two macros in use to handle the CS pin, and my enableWrite() sends the command. Did you ever get a file system working on the similar chip? Thanks!
#define cs_set() HAL_GPIO_WritePin(WIN_FLASH_CS_PIN,GPIO_PIN_RESET)
#define cs_reset() HAL_GPIO_WritePin(WIN_FLASH_CS_PIN,GPIO_PIN_SET) // NEED TO CHANGE DEPENDING ON LAYOUT OF BOARD

void SPIFlash::enableWrite(bool state) {
	/* [Public Method]
	 * Sends a sequence to the chip to enable
	 * writing. This MUST be done right before
	 * attempting to write to the chip, else
	 * the chip won't write.
	 */
	if (state) outBuffer[0] = W25_WRITE_ENABLE;
	else outBuffer[0] = W25_Write_DISABLE;
	cs_set();
	sendSPI(outBuffer, 1);
	cs_reset();
}

Yes, I got it working on a W25Q32JV (16J/32J is the memory density, W/V is the operating voltage).
Unless I am missing something, you don't appear to be enabling writes when you erase.
Also, in your configuration you have:

cfg.block_size = 4096;
cfg.block_count = 4096;

This would be 4096 * 4k = 16MBytes, however your part is 16Mbit.
BTW, according to the datasheet, the Write Disable (04h) is not needed after the operation:

Note that the WEL bit is automatically reset after Power-up and upon completion of the Write Status Register, Erase/Program Security Registers, Page Program, Quad Page Program, Sector Erase, Block Erase, Chip Erase and Reset instructions.

I notice in retrospect that the documentation refers to as sectors as 4096 bytes and blocks as 32Kbytes in size for the erase feature. I am treating the 4Kbyte sectors as blocks when implementing into lfs. That shouldn't be a problem, should it?

No, that shouldn't cause a problem - you just need to make sure you use the correct erase operation - SectorErase (20h) or BlockErase (52h for 32kB block, D8h for 64kB block).
Your approach for determining when a write/erase operation has completed probably isn't the best. Rather than using a fixed delay, you should read the status register and check for the ERASE/WRITE IN PROGRESS flag. A page program has a typical write time of 0.8ms and a max time of 3ms. A 1us delay isn't going to be much use. (And you don't seem to check if/when erases complete)
Finally, I don't know how the device will respond if you assert the write protect line before a write/erase has completed.

I implemented a function to wait for the register to clear as well as de-asserting the CS line after the write is complete, and the issue persisted.... To simplify I swapped it out for a broad 5ms delay between writes to no dice.... Are you at liberty to share what your read/write/erase functions look like?
Thank you so much for your assistance

Unfortunately, I am not in a position to share the company's work product, however have you considered looking at using other existing W25qxx drivers? For example here, a driver for STM devices?
Having a known-good implementation for the W25Qxx device would then narrow down the problem space to either the littlefs configuration, or an implementation issue.
At the very least, it would be good to contrast & compare your driver.

Gave this a shot, got the library implemented and working but still getting a -28....
int block_device_read(const struct lfs_config *c, lfs_block_t block,
	lfs_off_t off, void *buffer, lfs_size_t size)
{
	W25qxx_ReadPage((uint8_t*)buffer, block*c->block_size, off, size);
	return 0;
}

int block_device_prog(const struct lfs_config *c, lfs_block_t block,
	lfs_off_t off, const void *buffer, lfs_size_t size)
{
	W25qxx_WritePage((uint8_t*)buffer, block*c->block_size, off, size);
	return 0;
}

int block_device_erase(const struct lfs_config *c, lfs_block_t block)
{
	W25qxx_EraseSector(block*c->block_size);
	return 0;
}

// configuration of the filesystem is provided by this struct
void LFS_Config(void)
{
	// block device operations
	cfg.read  = block_device_read;
	cfg.prog  = block_device_prog;
	cfg.erase = block_device_erase;
	cfg.sync  = block_device_sync;

	// block device configuration
	cfg.read_size = 256;
	cfg.prog_size = 256;
//	cfg.block_size = 32678;
//	cfg.block_count = 128;
	cfg.block_size = 4096;
	cfg.block_count = 512;
	cfg.cache_size = 512;
	cfg.lookahead_size = 128;
	cfg.block_cycles = 500;

	cfg.read_buffer = lfs_read_buf;
	cfg.prog_buffer = lfs_prog_buf;
	cfg.lookahead_buffer = lfs_lookahead_buf;
//	cfg.file_buffer = lfs_file_buf;
}

Update: I figured out what was causing the formatting issues! The size of my read and program buffers were not equal to the cache_size value I provided in the initialization. I am going to close this for now, hopefully this will be helpful to someone.

Great to hear. My next step was to point out that you are dropping any data over a page-length in size in the write function. If your write function can automatically split a longer write (or read for that matter) up, then you don't need to have the constraint that page size == cache size.

Hi @JonJust @gtaska
I have the same issue with the same flash. @JonJust do you remember you config lfs struct for W25Q16 flash ?
here is what I've tried
struct lfs_config cfg_lfs = {
        .read = lfs_read,
        .prog = lfs_prog,
        .erase = lfs_erase,
        .sync = lfs_sync,

        .read_size = 256,
        .prog_size = 256,
        .block_size = 4096,
        .block_count = 512,
        .cache_size = 256,
        .lookahead_size = 128,
        .block_cycles = 500,

        .read_buffer = read_buffer,
        .prog_buffer = prog_buffer,
        .lookahead_buffer = lookahead_buffer
};

Thanks a lot

`
#define BUF_SZ 256
#define SECTOR_SIZE 4096
#define PAGE_SIZE 256
#define SECTOR_COUNT 512
// configuration of the filesystem is provided by this struct
void lfs_configure(void) {
// block device operations
// cfg is a global variable held in main.cpp.
// It would probably be better to set this up without global variables, but
// hey if it aint broke don't fix it.
cfg.read  = block_device_read;
cfg.prog  = block_device_prog;
cfg.erase = block_device_erase;
cfg.sync  = block_device_sync;

cfg.read_size = BUF_SZ;
cfg.prog_size = BUF_SZ; // read and prog need to be identical
cfg.block_size = SECTOR_SIZE;
cfg.block_count = 512; // Found in the documentation of the flash chip
cfg.cache_size = BUF_SZ; // Need to be identical size to read and prog
cfg.lookahead_size = 256;
cfg.block_cycles = 1500; // Number of cycles one can write to a block before lfs engages wear leveling.

cfg.read_buffer = lfs_read_buf;
cfg.prog_buffer = lfs_prog_buf;
cfg.lookahead_buffer = lfs_lookahead_buf; // Link the buffers

cfg.name_max = 64;
cfg.file_max = LFS_FILE_MAX;
cfg.attr_max = LFS_ATTR_MAX;
cfg.metadata_max = SECTOR_SIZE;

}`
My Init Function looked something like this

authors: JonJust gtaska simon88

repo: littlefs-project/littlefs


text:
🛑 USTC Mirrors (Unicom) is down

In b897e1a, USTC Mirrors (Unicom) (https://unicom.mirrors.ustc.edu.cn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: USTC Mirrors (Unicom) is back up in b933737.

repo: littlekud/sites-status


text:
🛑 USTC Mirrors (IPv4) is down

In 3cf9f2c, USTC Mirrors (IPv4) (https://ipv4.mirrors.ustc.edu.cn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: USTC Mirrors (IPv4) is back up in 1128b86 after 7 minutes.


text:
🛑 USTC is down

In 61e66d8, USTC (https://www.ustc.edu.cn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: USTC is back up in ea40d9f.


text:
页面多个泄漏问题

请问是不是一次只能检测到一条泄漏的引用链

看原理是这样的，一次只会添加一次到检测map里面


text:
请问要怎样才能自由添加分类里的链接呢？

想自己添加点网址进去~

apk反编译，把JavaScript里的URL换成你想要的，记得改名字，不然会显示错误

authors: Waterkuiiiiii muabl

repo: liumingye/quarkHomePage


text:
如何不使用TuSimple数据集呢，也就是使用预训练模型来测试自己的图片

我在准备TuSimple数据集json结构时遇到些问题，而且数据量太大

我也想先测试一下自己的数据，请问你成功了么？

Sorry for being late, tough months about lots of deadlines.
I think my codes about testing on other images are not well written, the 'db' object is not necessary when testing on other images, you can replace corresponding constants by directly assigning their values rather than get from the 'db' object attributes.
No training and directly use pre-trained models
1-1 TuSimple
Make sure the aspect ratio of your image is 360 to 640, then our test protocol resizes your input image to 360 x 640.
1-2 CULane
Make sure the aspect ratio of your image is 295 to 820, then our test protocol resizes your input image to 295 x 820.
1-3 Why not good?
Currently, images in TuSimple contain only highway scenes, and the quantity is small. Another CULane contains urban scenes a lot but still suffers the lack of lane shape pattern (curved, closely curved, remotely curved, ...).
1-4 How to improve?
Crop (or any other transformations) your images to make them have similar shape patterns like CULane (or TuSimple) since we treat each lane as a whole object.

Sorry for being late, tough months about lots of deadlines.
I think my codes about testing on other images are not well written, the 'db' object is not necessary when testing on other images, you can replace corresponding constants by directly assigning their values rather than get from the 'db' object attributes.
No training and directly use pre-trained models
1-1 TuSimple
Make sure the aspect ratio of your image is 360 to 640, then our test protocol resizes your input image to 360 x 640.
1-2 CULane
Make sure the aspect ratio of your image is 295 to 820, then our test protocol resizes your input image to 295 x 820.
1-3 Why not good?
Currently, images in TuSimple contain only highway scenes, and the quantity is small. Another CULane contains urban scenes a lot but still suffers the lack of lane shape pattern (curved, closely curved, remotely curved, ...).
1-4 How to improve?
Crop (or any other transformations) your images to make them have similar shape patterns like CULane (or TuSimple) since we treat each lane as a whole object.


text:
What's your Django and Python version?

Hi there, what's your Python and Django version of this project? THX.

django 1.4
python 2.7

@liuyug thanks for your reply, however, your readme.md said it passed 1.10 test which made me regard it as python 3 and django 1.10.

authors: NoraGithub Weiming-Hu liuyug

repo: liuyug/django-alipay


text:
🛑 clans.wowsgame.cn is down

In 08341d0, clans.wowsgame.cn (https://clans.wowsgame.cn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: clans.wowsgame.cn is back up in 5aca52b.


text:
Improve auth manager for Comments & Notifications

Description
Auth Manager
This PR improves the Auth Manager for usage in Comments & Notifications (see commit):

The Auth manager will verify that the issued Access Token grants enough access for the requested usage. If not, it will throw an error.
For Access Tokens, if a token without a roomId is requested, the Auth Manager will only accept tokens with a wildcard.
The scope comments:read is enough to get inbox notifications.

Liveblocks-node (Session)

This PR verifies that the resource (roomId or pattern) of an Access Token permissions is a string.
Allows * as a pattern for Access token permissions.

Related issues
https://github.com/liveblocks/liveblocks.io/issues/1934

Should we cherry-pick the error page into main after this PR is merged? Otherwise the link won't be real until beta is merged.

@marcbouchenoire Chris is going to redo this error page later, we can cherry pick it into main when it's done.

repo: liveblocks/liveblocks


text:
Support for pandoc integration

In order to support pandoc integration, and eventual conversion to latex and other documents, we need to:

[ ] Do not discard front matter from Markdown
[ ] Allow metadata on Kino.render/2. This will be stored as part of the HTML comments
[ ] Persist tables as part of the output

Then someone can write a tool that preprocess the .livemd into a markdown document with tables, images, etc and passes that to pandoc.
We don’t plan to tackle this at the moment but if someone plans to use Livebook to write papers, they are welcome to explore these ideas and tools!

Then someone can write a tool that preprocess the .livemd into a markdown document with tables, images, etc and passes that to pandoc.

In my opinion, the best course of action is actually to implement a pandoc reader upstream. Here's the markdown one for comparison: https://github.com/jgm/pandoc/blob/master/src/Text/Pandoc/Readers/Markdown.hs
This has the following benefits:

It's natively supported by pandoc (so no installing external tools or pandoc filters in required)
Information will not get lost in the livemd to md transpilation (no examples come to mind however)
It probably will be more perfomant than any Elixir equivalent.
It probably will be better maintained than any community tool.

But has the following disadvantages:

Less freedom to change the format
We may need to work with pandoc community to make changes
A PR for support may not be even accepted, with the reason being that Livebook is not popular enough.

If we do implement a reader, we should also implement a writer.
Jupyter Notebook has gone this route, with a reader and a writer.

That's good to know. I think for now the ability to iterate is more important and once the format is stable enough we can reach out to pandoc.

I think for now the ability to iterate is more important and once the format is stable enough we can reach out to pandoc.

I agree. I think the first course of action is to start standardising and writing specifications for the format.

Is there something defined or someone working on these specifications?

There are no plans for now. But Livebook is a subset of Markdown so there is not much to specify. We do add HTML comments, but I don't think they would matter for the Pandoc integration. And we also use "triple-backtick", such as ```output and ```` mermaid , but that's regular Markdown behaviour and GitHub, for example, supports its own backticks (including mermaid).
Anyway, I disagree that the first course of action is "to start standardizing and writing specifications" because that assumes the best course of action is by adding a reader/writer to Pandoc. We already have all of the tooling written in Elixir, I would rather write the .livemd to .md layer in Elixir first and play with ideas, then assume the starting point is rewriting the existing still-in-flux stack in another language.

Hello there !
For educational purposes, I've had to share the work I've done on Livebook in an offline HTML static file.
Because I only had little success improving Livemarkdown to exports outputs with embedded VegaLite charts (keeping them interactive) + data tables, I ended up doing the work upside-down, with an escript which drives a whole serverless Livebook otp app instance for cells evaluation.
For its part, a silly dep to add to livemd overrides some Kinos (meant to be interactive/js live/server-driven), to generate static HTML outputs.
While this does the job I needed, I keep in mind the roadmap presented in the issue is the way to go (and was, to some degree, an initial intention for me).
I will try to investigate further back this way, with the knowledge I've earned achieving my little own goal.
(That journey was awesome, but I'm pretty sure that nothing I've done for my lib has value in achieving that roadmap)
I may first start trying to write a paper with some flowcharts on how Livebook / Notebook / Kinos / evaluations / client-js work altogether in my (pretty limited) understanding.
That said, the silly lib/tool is here, for reference: ripmd
Cheers !

Oops, I should have taken a look at this earlier (and understand better what is going on in the upstream) https://github.com/livebook-dev/kino/pull/321 :)

authors: Benjamin-Philip clm-a josevalim viniciusalonso

repo: livebook-dev/livebook


text:
stronger/fix tests & python3.9 compatibility

also print serverside errors of 11labs
add word tokenizer to 11labs (default to the basic one)
stt maximum 0.2 WER
try_trigger_generation in 11labs set to false (bad practice)

added chunk_length_schedule instead
allow multiple concurrent ws connections when multiple segments are pushed

check stt events order
google stt, fix unordered events & accuracy (now competitive with other stt)
fix stt StreamAdapter & test with OAI
fix lot of issues related to python 3.9 compatibility
test_process.py is removed and going to reintroduce it on the next PR adding warmup features
fix tokenizers tests (TokenStream & BufferedTokenStream have STARTED/FINISHED events)

https://docs.livekit.io/agents/plugins/#VAD-and-StreamAdapter and README.md not update with this new feature.
agents.tts.StreamAdapter(openai_tts, silero.VAD().stream(min_silence_duration=1.0)), ** silero.VAD().stream(min_silence_duration=1.0) ** : Expect type Sentence Tokenizer, got VADStream instead;

authors: JARVISMindEngineer theomonnom

repo: livekit/agents


text:
1.5.3 release was not completed

👋 looks like 1.5.3 release was not completed, ie the release did not published, raise this issue for some awareness. Thanks! cc @davidzhao
relates to https://github.com/Homebrew/homebrew-core/pull/163188

Thanks for the heads up @chenrui333! Just released it now.

Thanks @davidzhao!

repo: livekit/livekit


text:
Player should error when content is token gated or inactive

Currently, when the player is using an HLS URL that contains either content that has not begun yet or the user is not using a signed URL for token-gated content, the player will display an infinite spinner. This gives the impression that the content will begin shortly; when it doesn't, the user assumes that something has gone wrong.
An ideal solution looks like:

When a stream has not started yet or is inactive, the player does not display the spinner -- just an empty player.
When a stream has started, but it isn't displayed yet or is pending, the spinner is shown.
If the viewer is not using a signed URL when a stream has a playback policy of signed, "It looks like you don't have permission to view this content"

Future iterations might include:

Allowing users to configure their own error messages

The problem is, we can't distinguish between "started" and "inactive" from the Player with only the playbackId. Unless we add additional info to the playback info endpoint, we will not be able to implement this cc @victorges

Related, here is the approach api.video takes

@0xcadams Added a note above -- we should report via telemetry when users receive errors and what kind of errors they get.

Yes, we get a response including "live" | "vod" | "recording" from the backend, so we can distinguish

Here's are the "Offline" and "Private" view designs by Vadym.
https://www.figma.com/file/dgNNV2zARuwL0hizYqdJxl/UI?node-id=410%3A234&t=pUf3uCp9Gpfnw9t9-1

authors: 0xcadams adamsoffer pglowacky


text:
EXC_BAD_ACCESS when attempting to access Phoenix server on same network

Phoenix allows you to bind to 0.0.0.0 which makes your app accessible to other devices on the same network but when I try to do this from my LVN app, it crashes with a EXC_BAD_ACCESS error. I tried to capture a video of this behavior on my iPhone…
https://user-images.githubusercontent.com/5893007/232146533-05c720b3-868e-491a-9ed1-afb43c90c285.mov

So the underlying issue seems to be that we're hitting the 1MB stack limit on iOS devices (the limit is higher on Macs, which is why it's fine in the Simulator). You run do reg read sp in the debugger to read the stack pointer at the point of the exception and compare it to the stack pointer in start and observe that the difference is always about a megabyte.
Something about this switch is causing the stack to grow by about a 450KB—putting us over the limit—between the fromNodes(_:coordinator:url:) call and the exception.

authors: shadowfacts supernintendo

repo: liveview-native/liveview-client-swiftui


text:
为什么引入找不到cmp

➜  zset go get -u github.com/liyiheng/zset
package cmp: unrecognized import path "cmp": import path does not begin with hostname

cmp 包是 go1.21 新增的，最新版本依赖了它。
旧版  go get github.com/liyiheng/zset@v0.1.0  没依赖它但是不支持泛型。
也许可以把依赖 cmp 的部分实现摘出来，从而支持 go1.18 ~ go1.20 这几个版本

Fixed by #18

repo: liyiheng/zset


text:
有坑否

有在维护吗？没有我就自己拉出来了...

中文输入法有办法处理掉吗


text:
Add support for Concat Operation

Added lit_tests for concat op.

Otherwise, LGTM.

Hi siboehm,
We are looking at this.

Hi @siboehm ,
We have added two more test cases where concatenation is happening with different shaped tensors.

repo: ljfitz/onnx-mlir


text:
Error when starting training on custom dataset

When using a custom coco formatted dataset, after processing with process.sh, this error gets thrown:
[06/27 11:14:57 d2.engine.train_loop]: Starting training from iteration 0
[06/27 11:15:01 d2.engine.hooks]: Total training time: 0:00:04 (0:00:00 on hooks)
---------------------------------------------------------------------------
KeyError                                  Traceback (most recent call last)
Input In [23], in <module>
      3 trainer = Trainer(cfg)
      4 trainer.resume_or_load(resume=False)
----> 5 trainer.train()

File c:\users\user\BCNet\detectron2\engine\defaults.py:373, in DefaultTrainer.train(self)
    366 def train(self):
    367     """
    368     Run training.
    369
    370     Returns:
    371         OrderedDict of results, if evaluation is enabled. Otherwise None.
    372     """
--> 373     super().train(self.start_iter, self.max_iter)
    374     if hasattr(self, "_last_eval_results") and comm.is_main_process():
    375         verify_results(self.cfg, self._last_eval_results)

File c:\users\user\BCNet\detectron2\engine\train_loop.py:131, in TrainerBase.train(self, start_iter, max_iter)
    129     for self.iter in range(start_iter, max_iter):
    130         self.before_step()
--> 131         self.run_step()
    132         self.after_step()
    133 finally:

File c:\users\user\BCNet\detectron2\engine\train_loop.py:205, in SimpleTrainer.run_step(self)
    201 start = time.perf_counter()
    202 """
    203 If your want to do something with the data, you can wrap the dataloader.
    204 """
--> 205 data = next(self._data_loader_iter)
    206 data_time = time.perf_counter() - start
    208 """
    209 If your want to do something with the losses, you can wrap the model.
    210 """

File c:\users\user\BCNet\detectron2\data\common.py:139, in AspectRatioGroupedDataset.__iter__(self)
    138 def __iter__(self):
--> 139     for d in self.dataset:
    140         w, h = d["width"], d["height"]
    141         bucket_id = 0 if w > h else 1

File c:\pyenvs\bcenv\lib\site-packages\torch\utils\data\dataloader.py:521, in _BaseDataLoaderIter.__next__(self)
    519 if self._sampler_iter is None:
    520     self._reset()
--> 521 data = self._next_data()
    522 self._num_yielded += 1
    523 if self._dataset_kind == _DatasetKind.Iterable and \
    524         self._IterableDataset_len_called is not None and \
    525         self._num_yielded > self._IterableDataset_len_called:

File c:\pyenvs\bcenv\lib\site-packages\torch\utils\data\dataloader.py:1203, in _MultiProcessingDataLoaderIter._next_data(self)
   1201 else:
   1202     del self._task_info[idx]
-> 1203     return self._process_data(data)

File c:\pyenvs\bcenv\lib\site-packages\torch\utils\data\dataloader.py:1229, in _MultiProcessingDataLoaderIter._process_data(self, data)
   1227 self._try_put_index()
   1228 if isinstance(data, ExceptionWrapper):
-> 1229     data.reraise()
   1230 return data

File c:\pyenvs\bcenv\lib\site-packages\torch\_utils.py:434, in ExceptionWrapper.reraise(self)
    430 except TypeError:
    431     # If the exception takes multiple arguments, don't try to
    432     # instantiate since we don't know how to
    433     raise RuntimeError(msg) from None
--> 434 raise exception

KeyError: Caught KeyError in DataLoader worker process 0.
Original Traceback (most recent call last):
  File "c:\pyenvs\bcenv\lib\site-packages\torch\utils\data\_utils\worker.py", line 287, in _worker_loop
    data = fetcher.fetch(index)
  File "c:\pyenvs\bcenv\lib\site-packages\torch\utils\data\_utils\fetch.py", line 49, in fetch
    data = [self.dataset[idx] for idx in possibly_batched_index]
  File "c:\pyenvs\bcenv\lib\site-packages\torch\utils\data\_utils\fetch.py", line 49, in <listcomp>
    data = [self.dataset[idx] for idx in possibly_batched_index]
  File "c:\users\user\BCNet\detectron2\data\common.py", line 40, in __getitem__
    data = self._map_func(self._dataset[cur_idx])
  File "c:\users\user\BCNet\detectron2\data\dataset_mapper.py", line 133, in __call__
    instances = utils.annotations_to_instances(
  File "c:\users\user\BCNet\detectron2\data\detection_utils.py", line 277, in annotations_to_instances
    bo_segms = [obj["bg_object_segmentation"] for obj in annos]
  File "c:\users\user\BCNet\detectron2\data\detection_utils.py", line 277, in <listcomp>
    bo_segms = [obj["bg_object_segmentation"] for obj in annos]
KeyError: 'bg_object_segmentation'

Are there any additional steps needed to train this on a custom dataset? I verified that the processing went correct and each instance seems to have the bg_object_segmentation added, although some are empty.
Some examples of the bg_object_segmentation:
"bg_object_segmentation": []
"bg_object_segmentation": [[735.0, 837.0, 734.0, 827.0, 734.0, 817.0, 734.0, 807.0...

This could maybe related to the register_coco_instances I use to register the dataset?
from detectron2.data.datasets import register_coco_instances

This error indicates that some annotation doesnot have the "bg_object_segmentation'" mask annotation. Even it's empty we need such key name in the annotation.

I checked the dataset, every annotation has the bg_object_segmentation. Replacing the coco json with my own annotation file and using the train_net.py works without any errors.
I think registering new datasets just doesn't load in the bg_object_segmentation (even though it is 100% there for all annotations), but that might be out of scope for this repo and has to be added in detectron2.

authors: MathijsNL lkeab

repo: lkeab/BCNet