text:
Broker loads max 50 workitems

Bug Report
Describe the Bug
The broker loads max of 50 workitems to crawl
Expected Behavior
The broker should load all known nodes as workitems to be crawled
Observed Behavior
The broker only loads max 50 workitems to be crawled
Steps to Reproduce

Setup Broker
Register 50+ connectors
Wait for crawler to start

Context Information

Used version ghcr.io/truzzt/federated-catalog:image-v0.0.4

Detailed Description

Possible Implementation
You already know the root cause of the erroneous state and how to fix it? Feel free to share your thoughts.

The problem is related to the query of FederatedCacheNode used to load the work items to be processed by the crawler.
The number of created crawler instances will equal the number of work items and the SQL implementation of the FederatedCacheNode interface is returning no more than 50 records.
The SQL query built on SqlFederatedNodeDirectory.getAll() method is not defining the query limit property and the QuerySpec class is using its default limit value of 50:
https://github.com/truzzt/FederatedCatalog/blob/f3bb0da194441d70677d982908dc2cbee4eec34c/extensions/store/fcc-node-directory-sql/src/main/java/de/truzzt/edc/extension/catalog/directory/sql/SqlFederatedNodeDirectory.java#L54
https://github.com/eclipse-edc/Connector/blob/a6fdb2a0b4360629ec562e11ae19d077162200b7/spi/common/core-spi/src/main/java/org/eclipse/edc/spi/query/QuerySpec.java#L36
To solve the problem we have three possible solutions:
1 - Create an environment variable to configure the max number of 'FederatedCacheNode' returns in the getAll() method and use this variable value as the query limit.
2 - Define a fixed value to the query limit. We can choose a value high enough to support the max number of registered connectors in all known scenarios.
3 - Create a new FederatedNodeDirectory.getAll() method in our FederatedNodeDirectory interface, receiving as a parameter the max number of items to return. After that, we can use the value of the environment variable EDC_CATALOG_CACHE_PARTITION_NUM_CRAWLERS  as the method parameter, returning always a number of work items less of equals the allowed max number of crawlers to be created:
https://github.com/truzzt/FederatedCatalog/blob/f3bb0da194441d70677d982908dc2cbee4eec34c/spi/federated-catalog-spi/src/main/java/org/eclipse/edc/catalog/spi/directory/FederatedCacheNodeDirectory.java#L5
Please let me know the solution to implement.

Very nice description of the issue 👍
As discussed in the Daily please fix it for now with the solution 2 and please set it to 5000. When we switch to a newer version of the EDC, we can think about making it configurable similar to this: https://github.com/eclipse-edc/Connector/issues/3044

authors: dhommen jannotti-glaucio schoenenberg

repo: truzzt/FederatedCatalog


text:
how to insert a new line break at data-caption.

I'm making website , using wordpress (make original-template) , bootstrap and this lightbox system.
Please tell me , how to insert a new line break at "data-caption".
Only HTML file ,  is working.
but, remake wordpress original template , its not working.

@yu-jp are you trying to use PHP in the caption?

@yu-jp are you trying to use PHP in the caption?

yes. Is it incorrect way to use?

source: gharchive/issue

authors: trvswgnr yu-jp

license: MIT

license_type: permissive

license_source: github-api


text:
Aggregation on nullable fields lead to a wrong type error

Describe the bug
Type suggestion is wrong, we get a lint error which we shouldn't.
To Reproduce
I guess it happens when we use max(X) as aggregate, on a nullable field.
Expected behavior
lastExecutedAt is a nullable field, so max(lastExecutedAt) may be null as well, but safeql forces me to declare this field as Date, while I would expect it to be Date | null.
Screenshots

Desktop (please complete the following information):

OS: macOS
PostgreSQL version: irrelevant
Version: eslint-plugin 1.1.4

That's interesting.
Currently, the plugin assumes each row is non-nullable until proven otherwise (either by looking at the table column definition or by a join type if exists).
Assuming the opposite (nullable until proven otherwise) will solve that problem, but will introduce odd cases
// ex1 - we know for a fact that num is non-nullable here
sql<{ num: number | null }>`select 1 as num`

// ex2 - we know for a fact that count never returns null.
sql<{ num: number | null }>`select count(1)`

The only solution I could do is to assume the opposite (nullable until proven otherwise) and then add another layer of checks to determine whether a column is non-nullable based on the parsed query.
Since it'll take time to implement, in the meanwhile, I can add a flag called expirmentalStrictNull which assumes every column is nullable until proven otherwise. The only false-negative cases will be the examples I've written above. Will it temporarily solve your issue?

repo: ts-safeql/safeql


text:
fix: import manual edits

This is the better approach as we are moving to the "pure snippets", I think we shouldn't be throwing error on importing empty file for manual-edits

@imrishabh18 the playwright test failure might be legitimate here because it involves manual edits

@seveibar Checked the manual-edits file, can't see any difference it's just the pcb-viewer lines

I think we are good to merge.

Can you add a network idle check in the playwright test for that file? This is going to keep happening if we dont fox these tests- ansh recently pr’d what that fix may look like

source: gharchive/pull-request

repo: tscircuit/snippets


text:
Latest version giving lots of extra debug

Updated to latest git and suddenly im getting these messages

Error: hls: unsupported HLS tag: EXT-X-CUE-OUT-CONT
Error: hls: unsupported HLS tag: EXT-X-CUE-OUT-CONT
Error: hls: unsupported HLS tag: EXT-X-CUE-OUT-CONT
Error: hls: unsupported HLS tag: EXT-X-CUE-OUT-CONT
Error: hls: unsupported HLS tag: EXT-OATCLS-SCTE35

Any way of turning them off as they are polluting the log.

The HLS plugin did not change. Your input must have changed.
I will downgrade those messages to debug level. You are right, they do not bring any valuable information outside debugging.

Thanks

authors: joolzg lelegard

repo: tsduck/tsduck


text:
Plot two different vegeta reports

Hi guys,
I'd like to plot in a combination two *.bin files. Do you know if there is any tool to do it? I know I can get a html file out of each file, but I'd like to plot into a single graph the result of two files.
How can I consume the .bin to get the metrics and then create a graph combining different results ?
Thanks in advance

I found a way of getting the values via the dump command.

repo: tsenart/vegeta


text:
Configuration fails to save after 4.6.0 update

Just updated to the latest version and the addon won't start.
Reverted the config to default values and it still won't start with the same error message.
Failed to save add-on configuration, expected int. Got {'enable_cameras': False, 'snapshot_mode': 'disabled', 'enable_modes': False, 'enable_panic': False, 'beam_duration': 0, 'disarm_code': '', 'mqtt_host': '<auto_detect>', 'mqtt_port': '<auto_detect>', 'mqtt_user': '<auto_detect>', 'mqtt_password': '<auto_detect>', 'branch': 'addon', 'ring_token': '', 'location_ids': ['']}
LE:
enable_cameras: false
snapshot_mode: disabled
enable_modes: false
enable_panic: false
beam_duration: 0
disarm_code: 'xxxx'
mqtt_host: <auto_detect>
mqtt_port: <auto_detect>
mqtt_user: <auto_detect>
mqtt_password: <auto_detect>
branch: addon
ring_token: ''
location_ids:
  - ''

Thanks

@tsightler Looks like there is something wrong with beam_duration as that is the only one with a schema for "int"

You must have snuck in super fast as the version of config.json that had this bug was only in the main branch for maybe 5 minutes.  Easiest thing to do is to copy the config, then uninstall and reinstall and it should be fine.

Yeah, well, Home Assistant isn't exactly great at errors messages on their parsing logic, it would be nice if they actually said what field was wrong wouldn't it.  But it's actually the mqtt_port.  Somehow I accidentally pushed a change that included port as the type for the "mqtt_port" field, which sounds OK in theory, but it's actually not since the default is "<auto_detect>" which is clearly not a valid port.  If you don't want to re-install you can just put your MQTT port in there for now and it will work.

I reinstalled and still get the same error -- FWIW

Before you reinstall you should perform a reload in the addon store or it will probably just install the broken one again.

Out of curiosity, I don't understand how you get notifications of these things so fast.  It's been over an hour and my production system doesn't even show the update yet.  Do you have some setting to check for updates super often?

@tsightler Sorry just had dinner.
After submitting the issue I have reverted the module to the snapshot. Now i came and reloaded the addon store and updated and everything is fine :)

Out of curiosity, I don't understand how you get notifications of these things so fast. It's been over an hour and my production system doesn't even show the update yet. Do you have some setting to check for updates super often or is it just luck? I'm trying to understand how often Home Assistant refreshes addon updates.

Yes I have a package that monitors all sorts of updates :) but with my own notification settings. Simply put, I get notifications on my phone, i read the change log, get very excited, update and then be one of the first to suffer if things are wrong haha :)
The link is here
https://community.home-assistant.io/t/update-notifications-core-hacs-supervisor-and-addons/182295
Offtopic 1:
Shouldn't the volume related entities be different now? Mine are still brightness?

Please don't suggest uninstalling and reinstalling cause my entities have custom names :)
Offtopic 2:
Any news on the support for the Chime as discussed https://github.com/tsightler/ring-mqtt/issues/168
Thanks a lot
Rob

OK, cool, thanks for the information on updates.  I'm hopeful most people aren't quite that aggressive with updating.  My usual process is that, as soon as I push the update, I upgrade my dev instances (I have two a VM and a RPi) and, if I find anything wrong, I try to fix it super fast.  In this case I think it was about 5 minutes between pushing the updating and finding that this bug with port had slipped in and fixing it so I expected that nobody would have managed to get the by then.  But maybe that expectation is unrealistic and I need to do something better.
Regarding volume, the addon does not attempt to remove the old light based entities but you should see new number sensor entities in the device.  You'll have to manually remove the old ones.  Technically the slider on the old one might still work since the MQTT topic is the same and the device will be online, but I've never bothered to try.  I think I could remove the entity by sending an empty discovery string to the discovery topic, but I haven't tried that.  I really didn't think very many people used volume control previously.
Chime support will have to wait for some time in the future, I'm not sure when.  Chimes behave more like cameras than alarm devices but they are also quite different from cameras so it basically has to be coded from scratch as a new device type.  Alarm and smart lighting devices are all extensions of the generic alarm-device type, so adding those is relatively easy.  I'll may end up having to buy a chime to build support for it but I've been reviewing the Homebridge code to see how it works.

Closing this issue since the existing repo is working at this point.  If there are issues, reload the repos on the add-in store and retry.  If you have issue with volume controls feel free to open a separate issue for that.

Regarding volume, the addon does not attempt to remove the old light based entities but you should see new number sensor entities in the device. You'll have to manually remove the old ones. Technically the slider on the old one might still work since the MQTT topic is the same and the device will be online, but I've never bothered to try. I think I could remove the entity by sending an empty discovery string to the discovery topic, but I haven't tried that. I really didn't think very many people used volume control previously.

@tsightler I am not 100% about the underlying functionality, but I have seen for example in zigbee2mqtt that if an entity is "re-writen" in terms of its type during the autodiscovery stage, the HA entity updates to the new type, without duplication or orphans. Might be something to consider?

Chime support will have to wait for some time in the future, I'm not sure when. Chimes behave more like cameras than alarm devices but they are also quite different from cameras so it basically has to be coded from scratch as a new device type. Alarm and smart lighting devices are all extensions of the generic alarm-device type, so adding those is relatively easy. I'll may end up having to buy a chime to build support for it but I've been reviewing the Homebridge code to see how it works.

I am willing to contribute so you can buy a Chime on me, for your implementation. TBH i am unsure if I will stick with Ring as a permanent solution but I feel that is the least I can do to reward your work. Just let me know how and I will look into it

It may be a side effect of the fact that I changed the device ID suffix from "_audio" to "_volume".  I'm expecting that the percentage of people using that feature is too low to worry about at this point, but we'll see.  It's pretty easy to just delete the old entity I think.
Time is by far bigger issue vs the cost of buying a Chime.  If I ever get to the point where I have the time to work on it I'm sure I'll just buy one as I even have a use for it.  If someone else purchased it I'd feel more obligated to supporting it quickly!  :)
I managed to scrape together a little time over the last few days to get this backlog of things out the door, but there is so much that needs to be done with this project that I still don't have time mess with at this point.

authors: jmacul2 robertalexa tsightler

repo: tsightler/ring-mqtt-ha-addon


text:
file(1) maintainer deems magic marker "really weak" for 2021

The maintainer of file(1) command has accepted a patch to support the Birtual Machine.
However, he states

I added it, but the magic is really weak. It is 2021 and we are making 2 byte magic entries? Please let the developers know that they should have at least a 4 byte magic. If there are conflicts/complaints in the future it will be removed.

Perhaps the magic marker should be "bomb", for  Born Of Mighty Birtualization.
I checked, "bomb" is not taken yet.

We could use 0xa4 0x01 0x6d 0x62, which deserialised is 420 bm.

diff --git a/src/bm.h b/src/bm.h
index 91b59f1..b4eae3b 100644
--- a/src/bm.h
+++ b/src/bm.h
@@ -197,11 +197,11 @@ void bm_push_native(Bm *bm, Bm_Native native);
 void bm_dump_stack(FILE *stream, const Bm *bm);
 void bm_load_program_from_file(Bm *bm, const char *file_path);

-#define BM_FILE_MAGIC 0x6D62
-#define BM_FILE_VERSION 5
+#define BM_FILE_MAGIC 0xa4016d62
+#define BM_FILE_VERSION 6

 PACK(struct Bm_File_Meta {
-    uint16_t magic;
+    uint32_t magic;
     uint16_t version;
     uint64_t program_size;
     uint64_t entry;

If you read the resulting .bm file into an hex editor, with your suggestion @aodhneine, you can squint a naught, it reads
"bm" 1 $ - so we have a 1 dollar BM.
I am okay with this change.

authors: aodhneine catull

repo: tsoding/bm


text:
Investigate live trace runs

Doing in process traces using ts lib would allow us to provide more information in an on-demand manner.  For example, types.json only includes the display field when it is cheap to generate.  With a live trace we could generate the displays as needed.
As a side benefit, in memory fs should reduce skew due to IO overhead during tracing.

partially implemented with the ability to run a command to do traces and automatically send them to the viewer.
live via ts lib still should be investigated but is low priority

this is higher priority now as it enables much more functionality.  It can't be done in process without blocking the event loop and freezing the vscode UI, so I'm working on a server we can spawn and communicate with via web sockets

repo: tsperf/tracer


text:
Rename panel improvements

I've made a few improvements to the rename panel:

When the panel is shown, the word under the cursor in the active code editor is set as the contents of the new name field. Useful if the user only wants to make small changes to the existing name.

The name field is focused so you don't need to use the mouse.

The name in the field is automatically fully selected so it can also be easily replaced with something new.

Instead of clicking on the Rename button, you can also press enter on the name field.

:+1:

authors: mjomble tststs

repo: tststs/atom-ternjs

license: mit

license_source: bigquery


text:
Feature description
requirements.txt あるいは poetry.lock を削除し，残りの一方に統合する．
requirements.txt を削除する方針で進める．（理由は後述）
Motivation
現在，このリポジトリのルートには requirements.txt と poetry.lock の2つのlockファイル（requirements.txt がlockファイルか否かは諸説あり）が存在する．つまり，ライブラリの依存関係の解決が pip, poetry の両方によって行われうる状態になっている．これにより環境の差異や，「特定のツールを使うと動かない」といったことが起こってしまうかもしれない．（現在はpoetryは使えない）
なので，requirements.txt を削除し，今後，依存解決は poetry.lock （poetry）によってのみ行うように案内したい．
Additional context
[背景] requirements.txt を削除する方針で進める理由
現在のこのリポジトリの大まかな構成は以下のようになっている．
.
├── data
│   ├── ...
│   └── twitter.csv
├── ga
│   └── ...
├── lib
│   ├── ...
│   └── run_model.py
├── qd
│   └── ...
...

これは，/lib にqdとgaの共通モジュールを切り出し，それを各々（qd, ga）のスクリプトから呼び出している．が，これを行う上でPythonのimport周りの仕様が面倒なため，poetryのtools.packageに丸投げすることで解決している．ref. #12
上記理由により，poetryへの依存は簡単に解決できないので，requirements.txtを削除する方向にする

@krmr73
qdで使っているサードパーティ製のライブラリ（いわゆる pip installするやつ）を poetry add で追加し，プルリクを開いておいてもらえませんか？？それか，その一覧を教えてください．
開いてくれれば，あとはこっちで巻き取ります．
参考:

Poetry documentation コマンド#add
Poetryをサクッと使い始めてみる #依存パッケージの追加

repo: tsukuba-websci/MPS-TOM-Urnmodel


text:
Import statements does no work well on typescript

When importing on typescript like this import * as Fireworks from 'fireworks-canvas'
when creating the instance it throws this error

Interesting.  I have this running in one of my typescript projects:
https://github.com/tswaters/klondike/blob/master/src/components/Fireworks.tsx#L3
It doesn't actually work at the moment, ( one of the things I need to fix ) -- but I don't get any typescript errors trying to use it and can build the project OK.
Can you share your project code?  What version of typescript are you using ?

I just used another library, I couldn't figure how to solve the error

OK, thanks.  Closing the ticket.

Hello,
I have exactly the same problem. The code is the following :
import * as Fireworks from 'fireworks-canvas'; const fw = new Fireworks(document.querySelector('body'));
Error:
This expression is not constructable.   Type 'typeof Fireworks' has no construct signatures.
Typescript version : 4.9.5
Vite version : 4.2.0
If you have any idea on how to solve this, I'm interested ! Thanks in advance !

Yikes, this package.json has some old dependencies.
I think I might do a major bump, update all the things and change to a named export instead of default export.

This should be better now.
Must have been an artifact of old typescript versions... I remember I spent ages trying to get that right.
I've updated the tsconfig to include "module": "ESNext", and the latest rollup-typescript plugin does the right thing with it.
Either way, I've published v3.0.0, major change is new build tooling versions & updated to use named export,  Fireworks

Thank you ! It's perfect !

authors: manip-syntax mikews93 tswaters

repo: tswaters/fireworks

license: WTFPL


text:
网站接口挂掉了，所有内容不显示

请开发这个网站的码农，今晚加班把它修改好

你是哪来的傻逼，给了多少钱还是咋的，在这叽叽歪歪的

你是哪来的傻逼，给了多少钱还是咋的，在这叽叽歪歪的

你他妈才是傻逼呢，网站挂了不修复，看你妈的动画，狗子

@wubuzhi  为啥要给你这种傻逼用，除了做个伸手巨婴和bb还会点啥，自己写去啊nt玩意！


text:
French translation

I took my time to translate all of this, taking the time to choose the official words that you can read in the google apps menus and official google documentation when I could.

Just did
pnpm exec prettier ./src --write
It worked. I can see some of the text were re-indented.

repo: ttsukagoshi/mail-merge-for-gmail


text:
Remove warnings

Two simple changes to avoid boring warnings:
Running tests with RUBYOPT=-w before the changes:
Ruby Warnings found:

  20 lib/nightcrawler_swift/connection.rb:20: warning: instance variable @auth_response not initialized
  20 lib/nightcrawler_swift/connection.rb:19: warning: instance variable @auth_response not initialized
   1 lib/nightcrawler_swift.rb:32: warning: method redefined; discarding old logger

Thanks! The build was failing but the problem was not related to your pull request.

:+1:


text:
Update scalafmt-core to 3.7.9

About this PR
📦 Updates org.scalameta:scalafmt-core from 3.7.7 to 3.7.9
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

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

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

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

Superseded by #188.

repo: tulz-app/laminext


text:
A, B Files: Contrail -> Tungsten Fabric

Contrail -> Tungsten Fabric for a*.rst and b*.rst files.

Sorry, I don't seem to have write access to this repo :(
"This branch has no conflicts with the base branch"
"Only those with write access to this repository can merge pull requests."
Hopefully, pono or swill will review and merge them ..

I've sent an invite for you to be a collaborator on this repo. Apologies for forgetting to do that earlier, @tnaganawa!

I've sent an invite for you to be a collaborator on this repo. Apologies for forgetting to do that earlier, @tnaganawa!

authors: tnaganawa vmbrasseur


text:
Latency grows substantially as batch size increases, even with small batch sizes

Thanks for the wonderful repo, @turboderp!
I'm benchmarking latency on an A100 and I've observed latency increasing substantially as I increase batch size–to much larger degree than I'm used to (logs included below):

bs=1 vs bs=2: ~30% increase in latency
bs=2 vs bs=4: ~30% increase in latency

I'd love to know if I'm missing something or if this is expected!
Setup
I'm benchmarking with The Bloke's gptq_model-4bit-128g llama-2-13B-chat-GPTQ checkpoint.
I'm using test_benchmark_generation.py with some minimal modifications to run these benchmarks.
I'm instantiating cache with batch size and I'm warming up with a batch of ids.
I'm generating tokens like:
ids = torch.randint(0, 31999, (1, max_seq_len - gen_tokens)).repeat(batch_size, 1).cuda()

...

for i in range(gen_tokens):

    logits = logits[:, -1, :]
    id_per_batch = torch.argmax(logits, dim=-1)
    assert id_per_batch.shape == (batch_size,), f"{id_per_batch.shape} != {(batch_size,)}"
    next_id_per_batch = id_per_batch.unsqueeze(-1)
    sequence = torch.cat((sequence, next_id_per_batch), dim = -1)
    logits = next_logits(next_id_per_batch, lora)

bs=1
 ** Batch size: 1
         ** Latency: 46.10 tokens/second
         ** Throughput: 46.10 tokens/second
         ** Total time: 2.776369094848633
 -- Generating 128 tokens, 4 token prompt...
 ** Batch size: 1
         ** Latency: 54.13 tokens/second
         ** Throughput: 54.13 tokens/second
         ** Total time: 2.364816427230835

bs=2
-- Generating 128 tokens, 1920 token prompt...
 ** Batch size: 2
         ** Latency: 33.04 tokens/second
         ** Throughput: 66.08 tokens/second
         ** Total time: 3.87422776222229
 -- Generating 128 tokens, 4 token prompt...
 ** Batch size: 2
         ** Latency: 41.16 tokens/second
         ** Throughput: 82.31 tokens/second
         ** Total time: 3.1100616455078125

bs=4
 -- Generating 128 tokens, 1920 token prompt...
 ** Batch size: 4
         ** Latency: 23.13 tokens/second
         ** Throughput: 92.50 tokens/second
         ** Total time: 5.535064220428467
 -- Generating 128 tokens, 4 token prompt...
 ** Batch size: 4
         ** Latency: 28.07 tokens/second
         ** Throughput: 112.26 tokens/second
         ** Total time: 4.560673952102661

The kernels are very specifically optimized for matrix-vector operations (batch size = 1). It also does well on matrix-matrix by reconstructing full-precision matrices on the fly and relying on cuBLAS. The in-between territory is problematic, but I guess the question is what sort of throughput you would expect. (?)

The kernels from NVIDIA folks at https://github.com/tlc-pack/cutlass_fpA_intB_gemm are probably interesting in the batched scenario.

authors: fxmarty joehoover turboderp

repo: turboderp/exllama


text:
Batched generations are very similar

Hey @turboderp!
I'm facing an unusual problem while performing batched generation to obtain 2 sequences from the same prompt.
Previously, in exllamaV1, to obtain two distinct responses from a single prompt, I would pass the same prompt twice in a list and would then receive two very different sequences. ["x", "x"] -> ["y", "z"]
However, in exllamaV2, using the same approach results in the generated responses being extremely similar to each other. Despite this, each separate invocation of the function gives me a different response. ["x", "x"] -> ["y", " ≈y"]
Is there a way to ensure that each prompt in the list generates a unique response, perhaps by creating a new seed for each prompt?

This happens because sampling is done in the extension but randomness for the sampler is provided by Python (to make seeds easier to work with), and I only thought to carry one random number over because your use case hadn't really occurred to me at the time.
But I've fixed it with the latest commit, so you'll get different random samplings from multiple instances of the same prompt in a batch.

@turboderp Wow! Dude you are amazing.
I continue to be absolutely astounded about how well maintained this project is.


text:
Explain that NCBI's XML is chunked because there's a cap on the number of nodes in a BaseX database.

max nodes/database ~ 2 billion
https://docs.basex.org/wiki/Statistics

We currently split into ~ 35 chunks/databases with ~ 150 million nodes/database

repo: turbomam/biosample-xmldb-sqldb


text:
2.2 Ensure that sinks are configured for all log entries - problem with multiple projects in an aggregator

Describe the bug
When using this dashboard against an aggregator returning a set of GCP projects, only the last project will return a correctly configured log sink although every other one is configured the same (using terraform)

I will post a MR to update the query so that it successfully works for all projects with a correctly configured sink.

Steampipe version (steampipe -v)
steampipe 0.20.9
Plugin version (steampipe plugin list)
gcp: 0.41.0
To reproduce
Use this dashboard against an aggregator or put multiple gcp project in the search-path
Expected behavior
For every project in the search-path (or aggregator), all projects with correctly configured log sinks should return as OK

Here is the PR : https://github.com/turbot/steampipe-mod-gcp-compliance/pull/111

@M0nsieurChat, Thanks for using Steampipe!
Nice catch on this; I appreciate raising PR for this as well 👍
Just adding this image to track and explain how the query behaved differently. Not sure even why we might have used this string_agg. Anyways, we will go ahead and approve the PR

After the fix

Addressed in https://github.com/turbot/steampipe-mod-gcp-compliance/pull/111 !!
Thanks @M0nsieurChat for the fix 👍.

repo: turbot/steampipe-mod-gcp-compliance


text:
Update the GitHub reference from docs with hub url.

Need to change the below link to point Steampipe hub links.
Default Thresholds

Long running instance threshold (90 Days)
Volume backup age threshold (90 Days)
Volumes that are large (> 100 GB)

Already part of the main.

repo: turbot/steampipe-mod-oci-thrifty


text:
Not work with latest version of drizzle-orm

#205 reappear, following docs from Drizzle

This might be drizzle related it works with 0.34.1 but breaks with 0.35.0

Drizzle informed me that there is an issue they're working on in regards to the connection property of drizzle in 0.35.
I did actually manage to get 0.35 working for me, but only if I pass the client instance to drizzle(client) myself.

authors: 1qh notrab thibaultleouay

repo: tursodatabase/libsql-client-ts


text:
Feature: per-connection memory allocator configuration

I have a use case where I want to specify a custom allocator per connection. (The general form of the use case is to specify an arena allocator for an object that opens its own connection. This occurs in a process that is long lived [an application in my case] and that may spawn multiple concurrent instances/connections.)
In SQLite you can configure a custom allocator at the process level, but not per connection.

That AI-generated solution looks like the kind of path to take! Of course, we should also switch to allocator-api2 which gives Zig-style explicit allocators.

I'm a mega fan of this feature. I would love to implement it myself but if someone comes with something nice then I'm all for it.

allocator-api2 is the way! I tried to use bump allocator (bumpalo) and that was a fool's errand due to lifetime annotations polluting many structs.
@penberg is it possible to statically allocate all the memory needed at the startup similar to TigerBeetle in the case of limbo?
I'm not yet that well versed in the workings of SQLite memory allocator but it seems like it tries to do static memory allocation where ever possible using lookaside memory allocator, more about this here

allocator-api2 is the way! I tried to use bump allocator (bumpalo) and that was a fool's errand due to lifetime annotations polluting many structs.

I've never done allocators in rust and once I tried bumpalo. It is 100% true that lifetimes get in the way and I hate it so much with passion.

@penberg is it possible to statically allocate all the memory needed at the startup similar to TigerBeetle in the case of limbo?

I believe this is hard in our case as there could be multiple big blobs being pushed or things like that. Maybe possible but it requires a lot of thinking of a bunch of edge cases. I believe good choice of allocators per stage + giving control to the user is the goal.

authors: krishvishal penberg pereman2 ubirdio

repo: tursodatabase/limbo


text:
Missing Location Header

I am trying to make uploads to the vimeo platform using the tus library here . Below is a code snippet of how i initiate this upload process:
document.getElementById('browse').addEventListener("input", function(e) {

            // Get the selected file from the input element
            var file = e.target.files[0]
            var myToken = document.getElementById('accessToken')
            var url = 'https://api.vimeo.com/me/videos'
            var xhr = new XMLHttpRequest()
            xhr.open('POST', 'https://api.vimeo.com/me/videos', true)
            xhr.setRequestHeader('Authorization', 'Bearer ' + myToken.value)
            xhr.setRequestHeader('Content-Type', 'application/json')
            xhr.setRequestHeader('Accept', 'application/vnd.vimeo.*+json;version=3.4')
            xhr.onload = function(e) {
                if (e.target.status < 400) {
                    console.log(e.target.status) //this returns status 200
                    var response = JSON.parse(e.target.responseText)
                    // Create a new tus upload
                    var upload = new tus.Upload(file, {
                        endpoint: response.upload.upload_link,   //this looks like vimeo.api.tus... something like that
                        retryDelays: [0, 1000, 3000, 5000],
                        metadata: {
                            filename: file.name,
                            filetype: file.type
                        },
                        onError: function(error) {
                            console.log("Failed because: " + error)
                        },
                        onProgress: function(bytesUploaded, bytesTotal) {
                            var percentage = (bytesUploaded / bytesTotal * 100).toFixed(2)
                            console.log(bytesUploaded, bytesTotal, percentage + "%")
                        },
                        onSuccess: function() {
                            console.log("Download %s from %s", upload.file.name, upload.url)
                        }
                    })
                    // Start the upload
                    upload.start()
                } else {
                    console.log("This is a developer error: " + e)
                    console.log(e.target.status)
                }
            }.bind(this)
            xhr.send(JSON.stringify({
                upload:{
                    approach: 'tus',
                    size: file.size
                }
            }));
        })

Then when that new tus upload is intiated it calls the Upload method in the Tus library which has http variables as below:
var xhr = (0, _request.newRequest)();
xhr.open("PATCH", this.options.endpoint, true);
xhr.setRequestHeader("Upload-Length", this._size);
xhr.setRequestHeader("Tus-Resumable", "1.0.0");
xhr.setRequestHeader("Upload-Offset", 0);
xhr.setRequestHeader("Content-Type", "application/offset+octet-stream")

  xhr.onload = function () {
    if (!inStatusCategory(xhr.status, 200)) {
      _this2._emitXhrError(xhr, new Error("tus: unexpected response while creating upload"));
      return;
    }

    var location = xhr.getResponseHeader("Location");
    if (location == null) {
      _this2._emitXhrError(xhr, new Error("tus: invalid or missing Location header"));
      return;
    }

xhr.send();

Now the issue is that this procedure is returning me an error as below:
Failed because: Error: tus: invalid or missing Location header, originated from request (response code: 204, response text: )

From the way i see it, this Location Header is supposed to be in the response from the request made. How do i go around this???

You're welcome :+1:

authors: Acconut Daniel-Mutsawashe

repo: tus/tus-js-client


text:
How to cancel compression

At present, there is a requirement that no compression will be carried out after transmission. What kind of data will be transmitted. Is there an option to configure the option to cancel compression

What compression are you referring to? tusd does not compress incoming data, so I am not sure what you exactly mean.

你指的是什么压缩？tusd 不压缩传入的数据，所以我不确定你的确切意思。

Hello, I sent in 700m data and received only 300m from the service

Closing this issue due to inactivity. Feel free to leave a comment if you want to continue the discussion :)

authors: Acconut milelu-y

repo: tus/tusd


text:
tusd converts Upload-Metadata headers to lowercase

Question
Hi, I'm using tusd in a system where users can upload files into S3-compatible cloud storage. Then, a user may want to download file back in the browser by the signed URL to the file on S3. So, in the browser's save dialog I want a file name and file extension to be set as in the original file. It can be done, if I set the following file metadata in the cloud storage:

Name
Value

ContentDisposition
attachment; filename="myFile.mov"

However, when I try to pass ContentDisposition metadata in the Upload-Metadata request header, it gets converted to lowercase, i.e. contentdisposition, and this is how it is saved in the file metadata on S3. And it does not work to provide a file name and file extension on download then.
This is not a tus-js-client problem, because I can see that the Upload-Metadata header of the request to tusd is set correctly with ContentDisposition, not contentdisposition.
Is it possible to configure tusd not to do lowercase conversion of Upload-Metadata request header? Is it the expected behaviour?
Setup details

Operating System: running tusd in a docker, from official image: https://hub.docker.com/layers/tusproject/tusd/v1.11.0/images/sha256-db463b74ebb57a7bc959d8ac364dd007bf8fd49d50ede93c0dde885800e74602?context=explore
Used tusd version: v1.11.0
Used tusd data storage: AWS S3 compatible
Used tusd configuration: -s3-endpoint $BUCKET_ADDRESS -s3-bucket $BUCKET_NAME -metrics-path /admin/prometheus -port=8080 --hooks-http $HOOK_ADDRESS -base-path $BASE_PATH -behind-proxy
Used tus client library: tus-js-client 2.3.1

I don't see any code that would lower case the metadata keys in tusd, so I would assume that this is maybe even done by S3 itself. However, this should also not matter in this case because header values are usually treated case insensitively.
What might be the problem is that you are using ContentDisposition instead of Content-Disposition. I am not entirely sure if that is the root cause, but at least the HTTP header is written with a dash.

Okay, I'll try to check what S3 does on that, thanks.
I know that the correct HTTP header name is with the dash (Content-Disposition), however, when I try to pass it within Upload-Metadata it is not saved as a metadata to S3.
On the other hand, when I manually add ContentDisposition (CamelCase, no dash) metadata to the file on S3, it gets downloaded with file name and extension info as I want it to. So, it actually works, I just cannot find the way to set this metadata correctly from tusd yet.

So, it seems that setting metadata only is not working for Content-Disposition.
I had a look at the CreateMultipartUploadInput of the AWS S3 go SDK here and it has a separate field ContentDisposition. So, I think when the multipart upload is created in s3store.go
	// Create the actual multipart upload
	res, err := store.Service.CreateMultipartUploadWithContext(ctx, &s3.CreateMultipartUploadInput{
		Bucket:   aws.String(store.Bucket),
		Key:      store.keyWithPrefix(uploadId),
		Metadata: metadata,
	})

it should also set ContentDisposition field separately here:
	// Create the actual multipart upload
	res, err := store.Service.CreateMultipartUploadWithContext(ctx, &s3.CreateMultipartUploadInput{
		Bucket:   aws.String(store.Bucket),
		Key:      store.keyWithPrefix(uploadId),
		Metadata: metadata,
		ContentDisposition: ...,
	})

I tested setting metadata from AWS S3 java SDK, it also has the separate field for ContentDisposition and it works correctly when I set it.
So, I would love if you guys could fix this.
I believe the same applies to ContentLanguage metadata/header, and maybe some others.

That makes sense. Then we would have to populate these properties. I think we could fill Content-Disposition and Content-Type from the metadata keys filename and filetype, like we already do when we respond to GET requests: https://github.com/tus/tusd/blob/b4ffdf43f034099ee46437271de2ff98c1f52397/pkg/handler/unrouted_handler.go#L763-L765
Feel free to open a PR for this! I am not sure when I could work on this.

Closing in favor of https://github.com/tus/tusd/issues/1016.


text:
Question about generating KITTI range view images

Thanks for your great work. Could you please tell me the meaning of height and incl in the function get_range_image [code] ?

height means the vertical height of each laser beam.
incl means the inclination of each laser beam.
Note that the 64 laser beams of  LiDAR are not emitted from a single point.

height means the vertical height of each laser beam. incl means the inclination of each laser beam. Note that the 64 laser beams of LiDAR are not emitted from a single point.

Thanks for your great work. Could you please tell me how to calculate the height and zenith? Can the nuscenes data be converted into range view data format? What should I do for it?

@HuangDihe The heights and zeniths we used in KITTI are provided by the authors of RCD, which is obtained via Hough Transformation. You need to estimate height and zenith for each beam, which is somewhat similar  to line detection with Hough Transformation. I believe you can do it in NuScenes but I cannot provide you the source code.

@Abyssaledge Thanks for your great work! I run the code ：
python ./datasets/create_range_image_in_kitti.py --source-dir data/kitti --target-dir output
but there is no results in --target-dir(only have npz_test,npz_trainval folder with no files and have .roidb files（5 Byte）)，and report：
Error: 'lidar_idx'
the kitti data organized as follow,and generated .pkl files
data
│   ├── kitti
│   │   │── ImageSets
│   │   │── training
│   │   │   ├──calib & velodyne & label_2 & image_2 & (optional: planes) & (optional: depth_2)
│   │   │── testing
│   │   │   ├──calib & velodyne & image_2

@Abyssaledge Thanks for your great work! I run the code ： python ./datasets/create_range_image_in_kitti.py --source-dir data/kitti --target-dir output but there is no results in --target-dir(only have npz_test,npz_trainval folder with no files and have .roidb files（5 Byte）)，and report：
Error: 'lidar_idx'
the kitti data organized as follow,and generated .pkl files data │ ├── kitti │ │ │── ImageSets │ │ │── training │ │ │ ├──calib & velodyne & label_2 & image_2 & (optional: planes) & (optional: depth_2) │ │ │── testing │ │ │ ├──calib & velodyne & image_2

hello,i encoutered the same question that you have met,have you solved it?

@Abyssaledge Thanks for your great work! I run the code ： python ./datasets/create_range_image_in_kitti.py --source-dir data/kitti --target-dir output but there is no results in --target-dir(only have npz_test,npz_trainval folder with no files and have .roidb files（5 Byte）)，and report：
Error: 'lidar_idx'
the kitti data organized as follow,and generated .pkl files data │ ├── kitti │ │ │── ImageSets │ │ │── training │ │ │ ├──calib & velodyne & label_2 & image_2 & (optional: planes) & (optional: depth_2) │ │ │── testing │ │ │ ├──calib & velodyne & image_2

You may encounter error: lidar-idx because you named the storage differently from the author when generating the kitti_infos_trainval.pkl file for the kitti dataset. You can open your pkl file and look up the two memory names in 'point_cloud' to find the one that corresponds to 'lidar-idx', Then change the 'lidar-idx' in the process_single_frame function of create_range_image_in_kitti.py to the corresponding name

@Abyssaledge What is the version of mmdet3d? The kitti pkl file changed in different version.

authors: Abyssaledge HuangDihe Myszz248 QYChan qrzeffort tengteng95

repo: tusen-ai/RangeDet


text:
nuxt 3 dark mode refresh page broken

TuSimple/naive-ui version (版本)
2.33.3
Vue version (Vue 版本)
3.2.39
Browser and its version (浏览器及其版本)
Version 105.0.5195.125 (Official Build) (64-bit)
System and its version (系统及其版本)
ubuntu 22
Node version (Node 版本)
16
Reappearance link (重现链接)
https://github.com/productdevbook/oku-nuxt3-template
Reappearance steps (重现步骤)
yarn install
yarn dev
open -> http://localhost:3000/naive
dark mode select
refresh page
Expected results (期望的结果)
dark mode working
Actual results (实际的结果)
half dark half white mode
Remarks (补充说明)

and white this problem

In SSR Mode. color.preference is always white. It results in the SSR output using light theme variables & causes the style glitch.
If you want SSR page output correct result. You need to make theme a param of URL.

I don't really care if the SSR output respects the client's color scheme, but I'd at least like it to hydrate properly once rendered client side. This doesn't always seem to work as expected for some naive-ui components.

As you can see here, the SSR NButton is rendered with the light theme, while the Client Only NButton is rendered with dark (wrapped in ClientOnly tag). In my experience, the only naive-ui components that are hydrated correctly are those that are forced to load/reload client side (e.g. relying on async data or wrapped in ClientOnly tag).
I'm sure there's a far better method for getting around this, but my simple hack was adding a plugin to hook into the page:finish lifecycle hook, and then simply toggle dark mode off and on (only if already enabled):
// plugins/setTheme.client.ts

export default defineNuxtPlugin((nuxtApp) => {

    const isDark = useDark()

    // SSR is causing dark mode hydration issues with naive-ui
    // This fix quickly toggles dark mode on 'page:finish' hook
    nuxtApp.hook('page:finish', () => {
        setTimeout(() => {
            const prefersDark = usePreferredDark()
            isDark.value = false

            setTimeout(() => {
                isDark.value = prefersDark.value
            }, 0)
        }, 0)
    })

    return {
        provide: {
            isDark
        }
    }

})

<!-- app.vue -->

<template>
<div>
    <nuxt-layout>
        <n-config-provider :theme="$isDark ? darkTheme : lightTheme">
            <n-message-provider>
                <n-dialog-provider>
                    <nuxt-page />
                </n-dialog-provider>
            </n-message-provider>
        </n-config-provider>
    </nuxt-layout>
</div>
</template>

<script lang="ts" setup>
import { NMessageProvider, NConfigProvider, NDialogProvider } from 'naive-ui';
import { darkTheme, lightTheme } from 'naive-ui';

const { $isDark } = useNuxtApp()

</script>

I think this is still a bug. When the server renders, and then sends it to the client to render as well, the client actually gets the color pattern responsively and passes the prop to the NConfigProvider component accordingly, but the components don't respond to the change correctly.

Alternative workaround:
<NConfigProvider :theme>
  <!-- your code here -->
</NConfigProvider>

import { darkTheme } from "naive-ui"

const theme = ref(null)
watchPostEffect(
  () => theme.value = colorMode.value === "dark" ? darkTheme : null
)

The trick is the delayed theme change by watchPostEffect.

repo: tusen-ai/naive-ui


text:
🛑 Hasteserver is down

In d8c6021, Hasteserver (https://paste.eighty-three.me) was down:

HTTP code: 523
Response time: 1282 ms

Resolved: Hasteserver is back up in 06553db.

repo: tuxpeople/monitoring


text:
german Aldi Süd casalux Wifi LED RGB Light Strip Dump (Tuya CBU, BK7231N,RGB PWM and IR receiver)

Edited, due to false offsets in this posting text (thanks kuba2k2) that I wrongfully read using TextWrangler on Mac OS which did obviously change/insert values on the screen while watching the .bin files probably due to wrongfully using coding like UTF-8 on the bin files (the actual files were always correct, only had problem with displaying data)
Edit2: Update of PWM-Pins (wrong RGB color, additional pin info, Hint for OpenBeken Pin Settings)
Here is the (german) no name brand casalux with the “Wifi LED RGB Light Strip”, vendor is german Aldi Süd.
I bought it in 2022-10 for ca. 17 €. Seems to be it was sold also in early 2022 for 10€, but I don’t know if it had the same controller back then, seems to be identical.
Early 2022 info: https://www.aldi-sued.de/de/p.casalux-wifi-led-rgb-light-strip.490000000000711151.html
Youtube Video/Review about early 2022 (packing is still looking the same): https://www.youtube.com/watch?v=W_QRa3aQdN4
2022-10 info: https://www.aldi-sued.de/de/p.casalux-wifi-led-rgb-light-strip.490000000000818507.html
Packing states: Imported by Horstmann GmbH & Co KG, Hopfens. 1d, 24114 Kiel, Germany www.horstmann-kiel.com
Markings on the packing: 818507, Modell 9A22044,   X/17/2022
Technical specs on the packing:

9 W
0,5 W standby
5 m LED strip
150 LEDs

The LED strip only has 4 connections (12 V, R-PWM,G-PWM,B-PWM), it only has RGB, so no extra white LEDs
The “Smart Wi-Fi controller" in the white plastic box has the following information on the sticker:
Model: DW-RGB-WI01
Input: 12 V DC
Output: 3x2A (Max)
2.4 GHz ISM band
protection class III
Dongguan D-win Light ing Co., Ltd
Room 101, No.17,Dongkeng West Yanhe
Road 3. Dongkeng Town, Dongguan City. Guangdong Province China
Besides this controller there is the LED strip, a simple IR remote and a wall wart power plug (12 V DC / 1 A) in the box.
I opened the controller and found a Tuya CBU module (or CBU IPEX?): https://developer.tuya.com/en/docs/iot/cbu-module-datasheet?id=Ka07pykl5dk4u which wasn’t a surprise because the handbook tells you to download one of the Tuya apps.
The CBU module (which has Beken BK7231N chip) has only 7 connections soldered to the PCB:
3.3 V: CBU Pin 14
GND: CBU Pin 13
PWM Red:     CBU Pin  8 = Symbol "P8" = BK7231N Pin 24
PWM Green: CBU Pin  9 = Symbol "P7" = BK7231N Pin 23
PWM Blue:    CBU Pin 10 = Symbol "P6" = BK7231N Pin 22
IR Receiver: CBU Pin 1 = Symbol "P14" = BKN7231N Pin 11
?:                    CBU Pin 21  = Symbol "P15" = BKN7231N Pin 13 (maybe for mechanical stability reasons because the right edge of the module has no solder connection, seems to be not connected to anything else on the PCB)
Hint for using OpenBeken FW: The "Pin Settings" in OpenBeken V1.14.86 (and others I guess) refer to the "Symbol Px" Pins, not the CBU or BK7231N Pins.
I set up my old Android smartphone, changed MAC address for safety reasons and set up a test access point with SSID “test1234” and used the “Smart Life”  android app to connect the device to the tuya cloud, but i didn’t create a user profile (skipped profile creation in the app). I could then use the LED strip with the smart life app, so i suppose the readout dump should contain a Datapoint ID (DPID).
I found the access point SSID and PSK in cleartext in the dump.bin (see below) at offset 0x33CAA70x1D1000 to 0x33CB580x1D10AA. Didn’t findI also found my access point MAC (BSSID) in the dump.bin @ offset 0x1D1021 after kuba2k2 showed it to me. The MAC address isn't ASCII coded but raw.
For readout I connected my Raspi 3B to UART (CBU Pins 15 and 16) (redirected the Raspi UART /dev/ttyAMA0 to the Raspi Pins and therefore deactivated Bluetooth on the Raspi to get a “real” UART, checked if /dev/serial0 now points to /dev/ttyAMA0) and used python script:
bk7231tools read_flash -d /dev/serial0 -s 0 -l 0x200000 ./dump.bin
Further attempts (dump2.bin and all further attempts) gave a slightly changed readout (changed 1 time, stayed then this way), but looking into the dump file reveal that the change doesn’t affect the boot loader or the main program but maybe is some sort of boot counter. (change between dump.bin and dump2.bin starts at offset 0x36A1E3 0x1EB034, ends at offset
0x36A1FF 0x1EB045).
At 0x1EF000 there seems to be no DPID data. (it is all blank there) but at 0x1EEA8C to 0x1EEB07 there is something, maybe it is it? If yes: This could be for BK7231N devices other than BK7231T The DPID data is all there @0x1EF000, see kuba2k2s comment below.
I am also curious why free areas in the flash have the data 0x87CB in it instead of 0x00 or 0xFF Free spaces in the flash are 0xFF, see kuba2k2s comment below.
Because I couldn’t write my CBU module with bk7231tools (see my issue https://github.com/tuya-cloudcutter/bk7231tools/issues/7) i successfully wrote my flash with https://github.com/OpenBekenIOT/hid_download_py with the OpenBeken FW. Still trying that out, but seems to work so far, boots up, WLAN works, everything seems fine, haven’t tried to configure PWM/LEDs or IR receiver yet.
Aldi_casalux_Wifi_RGB_LED.zip
Have fun!

Further attempts (dump2.bin and all further attempts) gave a slightly changed readout (changed 1 time, stayed then this way), but looking into the dump file reveal that the change doesn’t affect the boot loader or the main program but maybe is some sort of boot counter

That's normal, the firmware writes to upper flash areas frequently, so it's usual to get different data after the device boots.
I'm not sure why are you referring to the offsets like 0x33CB58; the flash is 2 MiB in size, which is 0x200000 so there's no data at that offset. It's true that bk7231tools prints larger offsets - that's to trick the bootloader to allow reading the entire flash. If you do 0x33CB58 % 0x200000 it will show the correct offset, which would be 0x13CB58 in this case.

I found the access point SSID and PSK in cleartext in the dump.bin (see below) at offset 0x33CAA7 to 0x33CB58. Didn’t find my access point MAC (BSSID) in the dump.bin.

It's at offset 0x1D1000 - not sure where do the offsets you mention come from. The MAC is also there - at offset 0x1D1021 - C0:EE:FB:C2:D9:C5.

At 0x1EF000 there seems to be no DPID data. (it is all blank there) but at 0x1EEA8C to 0x1EEB07 there is something, maybe it is it? If yes: This could be for BK7231N devices other than BK7231T.

The data starts at 0x1EE000 and goes all the way to 0x200000. It's an encrypted block that contains DPIDs, network SSID, pinouts and other things like that.

I am also curious why free areas in the flash have the data 0x87CB in it instead of 0x00 or 0xFF.

I don't see that in the dump. All empty flash data is filled with 0xFF, some blocks (which are used) are filled with 0x00 if the data takes less space.

I'll look into the issue with bk7231tools. Meanwhile, I think you're using some kind of a weird hex viewer - the offsets at which you find the data are wrong. On Linux, you may simply use:
cat dump.bin | hexdump -C | less

For the record, here's your encrypted block data, but decrypted and put into JSON. I believe there are the DPIDs you're looking for.
gh-171-9927782-aldi-casalux-wifi-rgb-led-dump.json

I used Textwrangler on mac os to view the .bin files and used File -> Hex Dump Front Document, so all the offsets come from there. Don't know why all the offsets would be completely off.
Will look into it later, also why i obviously wrote some offset out of 2MB area which doesn't make sense...
Thanks for your reply !

I edited my original post to correct my wrong offsets and wrong assumptions based on the bad hexdump i saw. Thanks kuba2k2 :-)

An update has been pushed that should include a profile for this device.  Please update your repo and give it a try.  Please see the instructions page ( https://github.com/tuya-cloudcutter/tuya-cloudcutter/blob/main/INSTRUCTIONS.md ) for any command or input changes.
If the new profile does not work, please re-open this ticket with details (including logs) of the failure.
Any feedback is appreciated.

authors: Cossid kuba2k2 twobeseen

repo: tuya-cloudcutter/tuya-cloudcutter


text:
Maually esiting profile / understanding profile

Hi,
Referring the picture below. Can you tell me how to retrieve key from tuya clud api?

What is address finish, address ssid, ssid padding and how to retrive the same?

This is outside the scope of CloudCutter.
CloudCutter includes the list of DPIDs in the schema (the id fields), but doesn't determine how to use them.  Beyond that you'll need to use external tools such as LTChipTool's UPK2ESPHome Schema Download using the key from the CloudCutter profile as either the firmware key or product key.

Okay.
What about the adrress finish, address ssid, ssid padding?
Trying to understand it to find a workaround for devices using esp based tuya ic.
I myself happen to have lots of them.
Tuya convert is able to detect them but unable to exploit.

What about the adrress finish, address ssid, ssid padding?

Those are for CloudCutter exploiting, and are not a part of device configuration.

authors: Cossid hackintoshlover


text:
New device Smart Energy Meter support

Device normal info

Zemismart
ZMAi-90

Device info
"result": [
{
"active_time": 1622728475,
"biz_type": 0,
"category": "zndb",
"create_time": 1617444785,
"icon": "smart/icon/ay1536897190133VVeLx/b9439bd86d7954663fe187f367c5a54b.jpg",
"id": "xxxxx",
"ip": "xxxxx",
"lat": "xxxxx",
"local_key": "xxxxxx",
"lon": "xxxxxx",
"model": "ZM-wi-Fi -电表",
"name": "WiFi Smart Meter",
"online": true,
"owner_id": "xxxxxx",
"product_id": "nzexeqam9qulajbf",
"product_name": "",
"status": [
{
"code": "forward_energy_total",
"value": 58155
},
{
"code": "phase_a",
"value": "{"electricCurrent":0.786,"power":0.165,"voltage":233.0}"
},
{
"code": "switch",
"value": true
},
{
"code": "alarm_set_2",
"value": "[{"alarmCode":"overcurrent","doAction":false,"threshold":"60"},{"alarmCode":"ammeter_overvoltage","doAction":false,"threshold":"264"},{"alarmCode":"under_voltage","doAction":false,"threshold":"150"}]"
},
{
"code": "meter_id",
"value": "111111111111"
}
**Device specifications **
"result": {
"category": "zndb",
"functions": [
{
"code": "switch",
"type": "Boolean",
"values": "{}"
},
{
"code": "alarm_set_2",
"type": "Json",
"values": "{}"
}
],
"status": [
{
"code": "forward_energy_total",
"type": "Integer",
"values": "{"unit":"kW·h","min":0,"max":99999999,"scale":2,"step":1}"
},
{
"code": "phase_a",
"type": "Json",
"values": "{}"
},
{
"code": "switch",
"type": "Boolean",
"values": "{}"
},
{
"code": "alarm_set_2",
"type": "Json",
"values": "{}"
},
{
"code": "meter_id",
"type": "String",
"values": "{"maxlen":255}"
}
]
},

I'm working on contributing this and almost everything is done. I need suggestion for the following thing - device reports current, power and voltage as a single json string for each phase, like: "value": "{"electricCurrent":0.786,"power":0.165,"voltage":233.0}"
Is it better to parse values and split them for each separate sensor or leave it as is in single one?

I think it is better to split them for each separate sensor.

authors: skynetua tsutsuku

repo: tuya/tuya-home-assistant


text:
Login error 1114

Describe the bug
Setting up the new integration, received this error when trying to setup. I don't have any IP allowlist settings enabled.
Expected behavior
login details saved and integration enabled.
Screenshots

Home Assistant Version
2021.10.6
Device info (please complete the following information, which can be found in log):
All devices appear in the Cloud Project
Additional context
When linking my Smartlife app, I initially had the project setup as the Western Europe Data Centre however the app failed to link telling me it was for a different region (or words to that effect). I then changed the project to Central Europe and the app linked. My SmartLife account appears to be set to Isle of Man/United Kingdom.

I've opened a ticket with Tuya via the IoT website, I'll update this ticket once we find the solution. At they have just been repeatedly asking me to set the data centre to Central Europe, which I have done, as that's the only way to assign my SmartLife account to the IoT platform.
I'm pretty sure it's a mistake their end. I think they have assigned some UK IP addresses to the Western Europe datacentre but the UK accounts are registered in the Central Europe data centre. With most other platforms, the UK falls under Western Europe (unless there is a specific UK data centre). They have only recently been enforcing their rules around cross-data centre data transfer so I think it's only just started happening.

OK they have found the issue.
The Tuya IoT Access ID is not the login email you use for logging into the IoT platform, it's the ID found on the overvirew tab.

One I added that the integration worked.

Here. When doing the final step of adding + installing and configuring the TuyaV2 Integration into Home Assistant.

Until a few days ago Tuya devices just worked with little or no fuss......

That's a different login box to mine. That's weird.
The country code is 44.
Have you updated Home Assistant?

Olá, estava com esse mesmo problema, identifiquei que na plataforma Tuya Iot estava marcado uma opção de Lista de permissões de IP de autorização na nuvem desmarquei essa opção e voltou a funcionar normal!


text:
antela f1s202-eu don't report power/voltage/current

power monitor doens't work for device antela smart plug f1s202-eu.
none of current/power/voltage are reported
home assistant log
{   "home_assistant": {     "installation_type": "Home Assistant Container",     "version": "2022.9.7",     "dev": false,     "hassio": false,     "virtualenv": false,     "python_version": "3.10.5",     "docker": true,     "arch": "x86_64",     "timezone": "Europe/Rome",     "os_name": "Linux",     "os_version": "3.10.105",     "run_as_root": true   },   "custom_components": {     "localtuya": {       "version": "4.1.0",       "requirements": []     }   },   "integration_manifest": {     "domain": "tuya",     "name": "Tuya",     "documentation": "https://www.home-assistant.io/integrations/tuya",     "requirements": [       "tuya-iot-py-sdk==0.6.6"     ],     "dependencies": [       "ffmpeg"     ],     "codeowners": [       "@Tuya",       "@zlinoliver",       "@frenck"     ],     "config_flow": true,     "iot_class": "cloud_push",     "dhcp": [       {         "macaddress": "105A17*"       },       {         "macaddress": "10D561*"       },       {         "macaddress": "1869D8*"       },       {         "macaddress": "381F8D*"       },       {         "macaddress": "508A06*"       },       {         "macaddress": "68572D*"       },       {         "macaddress": "708976*"       },       {         "macaddress": "7CF666*"       },       {         "macaddress": "84E342*"       },       {         "macaddress": "D4A651*"       },       {         "macaddress": "D81F12*"       }     ],     "loggers": [       "tuya_iot"     ],     "is_built_in": true   },   "data": {     "endpoint": "https://openapi.tuyaeu.com",     "auth_type": 0,     "country_code": "39",     "app_type": "smartlife",     "mqtt_connected": true,     "disabled_by": null,     "disabled_polling": false,     "name": "Riscaldatore",     "model": "F1s202-EU",     "category": "cz",     "product_id": "bhqkxecq6o5qkc52",     "product_name": "",     "online": true,     "sub": false,     "time_zone": "+02:00",     "active_time": "2022-10-05T13:32:03+00:00",     "create_time": "2022-10-05T13:32:03+00:00",     "update_time": "2022-10-05T13:48:07+00:00",     "function": {       "switch_1": {         "type": "Boolean",         "value": {}       }     },     "status_range": {       "switch_1": {         "type": "Boolean",         "value": {}       }     },     "status": {       "switch_1": true     },     "home_assistant": {       "name": "Riscaldatore",       "name_by_user": null,       "disabled": false,       "disabled_by": null,       "entities": [         {           "disabled": false,           "disabled_by": null,           "entity_category": null,           "device_class": null,           "original_device_class": "outlet",           "icon": null,           "original_icon": null,           "unit_of_measurement": null,           "state": {             "entity_id": "switch.riscaldatore_socket_1",             "state": "on",             "attributes": {               "device_class": "outlet",               "friendly_name": "Riscaldatore Socket 1"             },             "last_changed": "2022-10-05T15:42:36.102148+00:00",             "last_updated": "2022-10-05T15:42:36.102148+00:00"           }         }       ]     }   } }
device info
{   "result": {     "active_time": 1664976723,     "category": "cz",     "category_name": "Socket",     "create_time": 1664976723,     "gateway_id": "",     "icon": "smart/icon/bay1603247053327gtRW/f0615f7985374fe0bb0504e3f34bfb42.png",     "id": "xxx",     "ip": "xxx",     "lat": "45.5707",     "local_key": "xxx",     "lon": "8.0538",     "model": "F1s202-EU",     "name": "Riscaldatore",     "online": true,     "owner_id": "67485276",     "product_id": "bhqkxecq6o5qkc52",     "product_name": "Antela Smart Plug",     "sub": false,     "time_zone": "+02:00",     "update_time": 1664977687,     "uuid": "72774fcb10540742"   },   "success": true,   "t": 1664988918480,   "tid": "7ddfafd744ce11edb88bca0f69d78a9e" }

the only things that i was able to get from IOT platform was this log, but i dont' understand what json call make them pop out :)
2022-10-05 18:59:19 | Report | Current | 1428mA | device itself |
-- | -- | -- | -- | -- | --
2022-10-05 18:59:19 | Report | Power | 335.60W | device itself |
2022-10-05 18:59:19 | Report | Voltage | 234.30V | device itself |
2022-10-05 18:46:34 | Report | Add Electricity | 0.10kwh | device itself |
2022-10-05 18:33:45 | Device semaphore | Device semaphore | signal intensity:-57||Remaining memory:54176||UTC:1664987625||DST:1664991225

I have the same

i got it fixed i raise a ticket on iot.tuya specifying the device id and model and they added the missing params.
i think they did for all device family as all my plugs started to work,you should check on your side

Lol i was playing all day with my homeassistant en yaml files en custom integration and it just started working. I think i know the reason now ;-)
I think it is solved by the ticket you raised.


text:
🛑 Recruit Connect - Website is down

In f6a3234, Recruit Connect - Website (https://recruitconnect.vn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Recruit Connect - Website is back up in e856ee6 after 7 minutes.

repo: tuyencaovn/recruituptime


text:
🛑 KKK is down

In f5cf630, KKK (https://www.kkk.tsk.tr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: KKK is back up in da55e58 after 8 minutes.

repo: tuz-z/upp


text:
【v1.0.0】无法删除文件

刚开始使用这款App，各方面都很吸引我，感谢开发者的努力！
刚想删除文件的时候，不管是单个文件还是多选文件，右键删除或者Cmd + ←，都没有任何反应，iCloud文件夹里的那些文件也没有被移到Trash里，不知道是不是Bug呢？谢谢！

我测试了一下是可以的，可能有一个情况，是你打开了预览模式，在预览模式下防止用户误触，将删除给过滤了
可以command+3到编辑模式，然后试试

我测试了一下是可以的，可能有一个情况，是你打开了预览模式，在预览模式下防止用户误触，将删除给过滤了 可以command+3到编辑模式，然后试试

谢谢！用cmd + 3切换后确实可以删除了，但是我第一次也切换到了编辑模式，只不过是点的眼睛图标切换的，那一次就无法删除。不知道是不是眼睛图标的某些判断有Bug呢？我好像复现不出来了，有空的话希望复查一下哦。
无论如何，感谢开发这么优秀的一款编辑器，期待今后的更新！

好勒 谢谢反馈我优化一下

正式版本已经发布，🐶解决了预览不能删除掉的特性，可去更新1.1.0 ~
https://github.com/tw93/MiaoYan/releases/tag/V1.1.0

正式版本已经发布，🐶解决了预览不能删除掉的特性，可去更新1.1.0 ~ https://github.com/tw93/MiaoYan/releases/tag/V1.1.0

好的！感谢开发大大的努力~


text:
关于窗口拖动

发现有部分网站是没法拖动的如reddit,还有部分网页打开链接是打开新页面的也没法使用

第一个问题可以打开dev调试模式，记的是pull最新代码 有这个逻辑 不过需要看一下问题在哪儿
第二个也是 你可以调试看错误在哪儿


text:
打包到Windows

是否有Windows平台打包方案

开个pr先

欢迎直接 pr


text:
no GurobiJni75 in java.library.path

Not sure if this is related to #1 , but I'm trying to run optimize on a profile in chordatlas and I get the following error:
java.lang.UnsatisfiedLinkError: no GurobiJni75 in java.library.path
	at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1867)
	at java.lang.Runtime.loadLibrary0(Runtime.java:870)
	at java.lang.System.loadLibrary(System.java:1122)
	at gurobi.GurobiJni.<clinit>(GurobiJni.java:243)
	at gurobi.GRBEnv.<init>(GRBEnv.java:41)
	at org.twak.tweed.gen.GurobiSkelSolver.buildProblem(GurobiSkelSolver.java:262)
	at org.twak.tweed.gen.GurobiSkelSolver.solve(GurobiSkelSolver.java:118)
	at org.twak.tweed.gen.SkelFootprint.solve(SkelFootprint.java:288)
	at org.twak.tweed.gen.SkelFootprint.buildAndSolve(SkelFootprint.java:154)
	at org.twak.tweed.gen.skel.SkelGen.optimize(SkelGen.java:150)
	at org.twak.tweed.gen.skel.SkelGen.lambda$new$1(SkelGen.java:135)
	at java.lang.Thread.run(Thread.java:745)

I'm currently running on MacOS 10.13.6. Also, this problem doesn't happen when I run on Ubuntu LTS 14.04. I have to temporarily move off of my Ubuntu machine so I'm trying to run this on my personal MacOS, but this is causing the optimized profile to not be able to be generated. Any clue how to fix this?

#1 is something different - I want to get rid of gurobi entirely and write my own replacement (since it's only a search through binary choices).
Are you running the latest jar (of from src)? Have you installed and licensed Gurobi? Which version? If you have run the optimiser on ubuntu, it should be the same procedure (if I remember OS X correctly...?) - you have to set the library environment variable when running:
LD_LIBRARY_PATH=/wherever/you/installed/gurobi/lib java -jar chordatlas.jar

Yep - setting the library path solved the problem exactly! I didn't have Gurobi installed on my local MacOS machine, and I guess it must have been installed on my Ubuntu machine by someone else. It would be helpful to list Gurobi as a prerequisite for installation (assuming that #1 is still there, haha).

great!
the details are there (but hidden) on the "bigSUR" page. I clarified a little.

authors: leekkww twak

repo: twak/chordatlas


text:
Remove similar colors

I have recently used yellowlab.tools to rate a website that is using Bootstrap 4.1.3/css/bootstrap.min.css.
It has flagged up 12 similar colors in that file. They are:
#badaff and #b8daff
#ffffff and #fdfdfe
#ffffff and #fefefe
#e2e6ea and #dee2e6
#eeeeee and #f1f1f1
#eeeeee and #ebebeb
#23272b and #212529
#f8f9fa and #f7f7f7
#343a40 and #32383e
#000000 and #040505
#fdfdfe and #fefefe
#171a1d and #16181b
Are they all necessary?

I doubt anyone is going to look into such stuff.

repo: twbs/bootstrap


text:
Spinner-border-reverese: A spinner that rotates in a reverse direction

Prerequisites

[X] I have searched for duplicate or closed feature requests
[X] I have read the contributing guidelines

Proposal
The feature proposal is to add a new class "spinner-border-reverse" to the existing spinner-border component in the Bootstrap framework. This class would allow the spinner-border to rotate in the other direction, providing a visual cue of activity in the opposite direction.
Motivation and context
The spinner-border component is widely used in Bootstrap applications to indicate activity or loading. However, in some cases, a user may want to indicate activity in the reverse direction. For example, when we are talking about two different types of spinners, to establish the contrast between them, we may give them different colors, and different rotating directions as well. It may also be useful to differentiate between the loading state of a component. For instance, if changes are uploading (loading) a spinner can be shown. Yet, it will be very useful to change the spinner with a reversed one once the changes fail to commit and we go to the rolling back state.
These are cases in which having a spinner that rotates in the reverse direction provides a clear visual cue and helps to improve the user experience. It also allows developers to be more creative and provide unique experiences for their users.
More importantly, having a separate class for reverse rotation reduces the complexity of using custom CSS to achieve the desired effect. It also provides a consistent and well-documented approach, making it easier for other developers to understand and maintain the code.

Closing for now per #37990.

@mdo  Thank you for your review, and for your comment.
I can work on a modifier class that if we add to any spinner, it makes it rotate in the other direction. Same thing for the spinner-grow, it makes it shrink instead of grow. Should I start working on it, or let it go as it is considered not planned?

authors: ChellyAhmed mdo


text:
Collect all Plutus dependencies in one module

This also shows how much we depend on plutus-apps.

Is this change still relevant now that we no longer intend on relying on cardano-ledger directly ? It might be, let's discuss about it here.

authors: carlhammann mmontin

repo: tweag/plutus-libs


text:
Bash formatting support

Is your feature request related to a problem? Please describe.
AFAIK, there is no de facto Bash/shell script formatter. It is very common to come across horrendously formatted shell scripts!
Describe the solution you'd like
Bash support in Topiary. (Bash, for now; perhaps POSIX sh, zsh, etc. in the future.)
Describe alternatives you've considered
n/a
Additional context
Having Bash support, alongside OCaml, JSON and TOML, in the first -- or an early -- release would be a good demonstration of both the general-ness of the engine and the potential for the project.
(Grammar: https://github.com/tree-sitter/tree-sitter-bash)

[x] Update Rust code
[x] Commands, command lists and command pipelines
[x] Conditionals
[x] Switch statements
[x] Loops
[x] Redirection and heredocs
[x] Compound statements
[x] Variables (declaration and expansion)
[x] Command and process substitution
[x] Subshells
[x] Functions

I'm not sure what you mean by “de facto” Bash formatters, but there do exist some Shell formatters, including for instance shfmt. Don't get me wrong, I'm super excited to see it included in Topiary, I just wouldn't want someone somewhere to claim there were no other Shell formatters!

I'm not sure what you mean by “de facto” Bash formatters, but there do exist some Shell formatters, including for instance shfmt.

Good point. What I mean is that -- in my experience, at least -- it's not common for formatters to be applied to Bash scripts and no particular formatter has a significant mindshare, not that they don't exist. (Compared with, e.g., linters, where many would immediately jump to Shellcheck.)

That makes sense and I completely agree. Hopefully, that is something Topiary could bring to the table: if it's already a dependency of your project, why not make it format your Shell files as well?

n.b., Line spacing is a bit messed up, but it's "good enough"; see #203.

authors: Niols Xophmeister

repo: tweag/topiary


text:
serdes : dataflow

need to be able to serialize and deserialize dataflow graphs

done.
https://github.com/tweakoz/orkid/commit/40b0950b9312e5e91ec2828f25c617e0fd8d6978

repo: tweakoz/orkid


text:
NotificationExtension Readme update

Ticket

[#####]

Github Issue

ISSUE-

Description

NotificationExtension Readme update

Commit message

Screenshot

Testing

[ ] Added unit tests
[ ] Ran unit tests successfully
[x] Added documentation for public APIs and/or Wiki

Code coverage
Total coverage: 93.61%

Powered by Slather

  Generated by :no_entry_sign: Danger

Code coverage
Total coverage: 93.74%

Powered by Slather

  Generated by :no_entry_sign: Danger

authors: AlejandroOrozco AuthyApps

repo: twilio/twilio-verify-ios


text:
PKPushRegisteryDelegate methods never called in swift 3

Description
I downloaded voice-quickstart-swift repository and followed all steps provided to get the app running. When app launches PKPushRegisteryDelegate method is not invoked in swift 3. The same code works fine with swift 4
Versions
All relevant version information for the issue.
Voice iOS SDK
4.1.0 via CocoaPods
Xcode
10.1
iOS Version
12.4
iOS Device
iPhone 6, 6s

Hi @ankitpansuria
While I cannot try Swift 3 compiler on Xcode 11, I remember when we updated the quickstart to use Swift 4 we needed to change the method signatures of PKPushRegisteryDelegate. Did you see any warnings when building with Swift 3?

Build succeeds without any errors or warning. But delegate methods are not invoked when app is opened.

Hi @ankitpansuria
Couple of questions:

Did you receive the pushRegistry:didUpdatePushCredentials:forType: callback with the device token when you initialize the PkPushRegistry instance?
The delegate methods of the PKPushRegistryDelegate protocol were updated in the Swift 4 version iOS SDK like the updates in this PR. This was a breaking change from Swift 3 to Swift 4 so I am asking if the method signature works for you in your Swift 3 environment.

@ankitpansuria Closing the ticket assuming the problem is resolved at your end. Feel to reopen the ticket if you are still running into the issue or have questions.

authors: ankitpansuria bchen-twilio piyushtank

repo: twilio/voice-quickstart-ios


text:
Crash when receiving a Twilio Call while you are in native call

Description
When you are in a standard pstn call and you receive a Twilio call, the call gets terminated and a dialog saying "Call Failed" appears. First, I thought this was some issue in my app but it's reproducible with the quickstart repository.
Steps to Reproduce

Make a PSTN call to a PSTN number
Call the placeCall endpoint to initiate a call to the device while in call

Code
No code apart from the Quickstart code is necessary to reproduce this issue
Expected Behavior
The PSTN call should continue, a dialog should appear to let you choose between calls
Actual Behavior
The active PSTN call gets ended, and the Twilio call is not displayed
Reproduces How Often
100%
Logs
A callservicesd crash is generated:
callservicesd  10-24-19, 4-08 PM.log
Versions
All relevant version information for the issue.
Voice iOS SDK
5.0.0
Xcode
11.1
iOS Version
13.1.2
iOS Device
iPhone SE
iPhone 11 Pro

@MarcoCanalcar Are you still running into the crash? We haven't seen the crash in our validation.

Hi @MarcoCanalcar
Hope things are well. I am closing this ticket assuming the original issue has been resolved by the iOS updates. Please feel free to reach out to us.
Cheers,
bobie

authors: MarcoCanalcar bchen-twilio piyushtank


text:
Enabling the clang-runtime feature does not seem to solve the known issue in #troubleshooting

I am hitting the " thread 'main' panicked at 'a libclang shared library is not loaded on this thread' " error, yet I believe I have enabled the clang-runtime feature, as suggested in the help. Is there anything else to try?

MacOS Catalina 10.15.7 on MacBook Pro 16" 2019
OpenCV from homebrew
OpenCV 4.5.2_4
rustc 1.52.1 (9bc8c42bb 2021-05-09)

Here is the complete log that I get when running:
env METAL_DEVICE_WRAPPER_TYPE=1 RUST_BACKTRACE=full DYLD_FALLBACK_LIBRARY_PATH="/Library/Developer/CommandLineTools/usr/lib" cargo -vv run --release

(I'm using fish so that's how I set the env vars for that run)
log.txt
Here is my Cargo.toml:
[package]
name = "svsclock"
version = "0.1.0"
authors = ["AA"]
edition = "2018"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[features]
clang-runtime = []

[dependencies]
nannou = { git = "https://github.com/nannou-org/nannou" }
nannou_audio = { git = "https://github.com/nannou-org/nannou" }
rand_xorshift = "0.2"
opencv = "0.53"

I'm surely doing something wrong, but I would appreciate another pair of eyes!
I am able to build and run as long as I don't add nannou-audio to my project.

The way you use clang-runtime feature makes it an optional feature of your crate, it doesn’t get passed on to dependencies. To fix this declare the opencv dependency like this:
opencv = { version = “0.53”, features = [“clang-runtime”] }

And of course it works! Sorry for the newb mistake.

authors: MacTuitui twistedfall

repo: twistedfall/opencv-rust


text:
different users

I would like  to create different users as roles in RBAC. For example, user1 can access container1  while user2 in docker groups like Bob cannot access container1.
as I know Docker daemon only see network requests sent from sockets and no username on the request.
therefore, Is twistlock provide that technique or not ?
Many thanks
Ibrahim

This is not relevant to this plugin. The docker auth subsystem only works with certificates. You can read more about it in the official docker GitHub repo
https://docs.docker.com/engine/extend/plugins_authorization/

authors: alobaidan liron-l

repo: twistlock/authz


text:
Add Errorf function

Hi there, it would be handy to have an Errorf function to make it easy to parameterize errors, alternatively we could have NewError and InternalError take args ...interface{} and then pass that to Sprintf in the function.
If you're open to this I can make a PR.

Thanks for the suggestion. That helper would be handy.
However, the errors package tries to be minimal by design. This ensures simplicity and performance.
Projects are encouraged to build their own error utils with their own constructors and wrappers. For example:
package errorutil

func TwirpErrorf(code twirp.ErrorCode, format string, a ...interface{}) {
    return twirp.NewError(code, fmt.Sprintf(format, a...))
}

authors: bouk marioizquierdo

repo: twitchtv/twirp


text:
looking for special traces or scripts

I want to do some research about caching with low locality(means large reuse distance), but I don't find such nice traces.
So I want to ask is there such kind of traces in this project?
Or any scripts to get L2 traces by doing a L1 filtering?
Thank you for your time.

answered here https://groups.google.com/g/cache-trace/c/ct8MqEvKRhg

Thank you very much!!!
------------------ 原始邮件 ------------------
发件人:                                                                                "twitter/cache-trace"                                                                                @.>;
发送时间: 2021年3月22日(星期一) 上午10:50
@.>;
@.@.>;
主题: Re: [twitter/cache-trace] looking for special traces or scripts (#2)
answered here https://groups.google.com/g/cache-trace/c/ct8MqEvKRhg
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

repo: twitter/cache-trace


text:
Cannot build package

Or it might just be me you cannot figure out how.
Steps to reproduce:
First, start with a clean Ubuntu 14.04 x64 server (e.g. from digitalocean.com)
Then, run these commands:
# ===========
# Follow instructions from https://docs.mesosphere.com/getting-started/datacenter/install/
# Setup
apt-key adv --keyserver keyserver.ubuntu.com --recv E56151BF
DISTRO=$(lsb_release -is | tr '[:upper:]' '[:lower:]')
CODENAME=$(lsb_release -cs)

# Add the repository
echo "deb http://repos.mesosphere.io/${DISTRO} ${CODENAME} main" | \
  sudo tee /etc/apt/sources.list.d/mesosphere.list
apt-get update

apt-get install mesos marathon
# ===========

apt-get install git
git clone https://github.com/twitter/mysos.git
cd mysos
apt-get install python-pip
pip install virtualenv
virtualenv venv
source venv/bin/activate
cd 3rdparty
wget http://downloads.mesosphere.io/master/ubuntu/14.04/mesos-0.22.1-py2.7-linux-x86_64.egg
wheel convert mesos-0.22.1-py2.7-linux-x86_64.egg
cd ..

python setup.py install
mysos_scheduler

Expected: The scheduler should start?
Actual:
Traceback (most recent call last):
  File "/root/mysos/venv/bin/mysos_scheduler", line 9, in <module>
    load_entry_point('mysos==0.1.0.dev0', 'console_scripts', 'mysos_scheduler')()
  File "/root/mysos/venv/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 552, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/root/mysos/venv/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2672, in load_entry_point
    return ep.load()
  File "/root/mysos/venv/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2344, in load
    self.require(*args, **kwargs)
  File "/root/mysos/venv/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2361, in require
    items = working_set.resolve(reqs, env, installer)
  File "/root/mysos/venv/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 833, in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'pynacl<1,>=0.3.0' distribution was not found and is required by the application

I am sorry that documentation on this is lacking but basically the scheduler requires extra dependencies which can be installed via pip install mysos[scheduler].
https://github.com/twitter/mysos/blob/master/vagrant/bin/mysos_scheduler.sh has the example for installing mysos scheduler.
In this example, /home/vagrant/mysos/dist has the mysos package and /home/vagrant/mysos/deps contains the mesos.native package.
BTW mysos currently requires Mesos native egg version to be 0.20.1 (there's a ticket for upgrading it) and the egg being named mesos.native-*. See how https://github.com/twitter/mysos/blob/master/vagrant/provision-dev-cluster.sh#L55 downloads the native egg.

Ok, I downloaded native binaries for 0.20.1. I get a little further, now there's another error...
I ran
apt-get upgrade # get python version 2.7.6
cp -r 3rdparty dist
python setup.py install
pip install mysos[scheduler]

and this is the error that pip shows:
Collecting mesos.native==0.20.1 (from mysos[scheduler])
/root/mysos/venv/local/lib/python2.7/site-packages/pip/_vendor/requests/packages/urllib3/util/ssl_.py:90: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning.
  InsecurePlatformWarning
  Could not find a version that satisfies the requirement mesos.native==0.20.1 (from mysos[scheduler]) (from versions: )
  Some externally hosted files were ignored as access to them may be unreliable (use --allow-external mesos.native to allow).
No matching distribution found for mesos.native==0.20.1 (from mysos[scheduler])

I'm not sure if it's the urllib3/SSLContext error that is causing problems, I've never seen that error before. But it looks like it cannot find the native package...

I also had difficulties getting mysos to connect [Mysos scheduler is still connecting...].
I'm using the playa-mesos vagrant box as a start point. Single node master/slave on same server.
Question how is mysos-0.1.0-dev0.zip built?
Here is my startup script
#!/bin/sh
#10.0.2.15
ZK_HOST=10.141.141.10
API_PORT=55001
#NOTE: In --executor_environ we are pointing MYSOS_DEFAULTS_FILE to an empty MySQL defaults file.
#The file 'my5.6.cnf' is pre-installed by the 'mysql-server-5.6' package on the VM.
mysos_scheduler
--verbose=on
--port=$API_PORT
--framework_user=vagrant
--mesos_master=zk://$ZK_HOST:2181/mesos/master
--admin_keypath=/home/vagrant/mysos/vagrant/etc/admin_keyfile.yml
--scheduler_keypath=/home/vagrant/mysos/vagrant/etc/scheduler_keyfile.txt
--executor_uri=/home/vagrant/mysos/dist/mysos-0.1.0-dev0.zip
--executor_cmd=/home/vagrant/mysos/vagrant/bin/mysos_executor.sh
--zk_url=zk://$ZK_HOST:2181/mysos
--framework_failover_timeout=1m
--executor_environ='[{"name": "MYSOS_DEFAULTS_FILE", "value": "/etc/mysql/conf.d/my5.6.cnf"}]'
Which outputs...
/usr/lib/python2.7/dist-packages/pkg_resources.py:1031: UserWarning: /home/vagrant/.python-eggs is writable by group/others and vulnerable to attack when used with get_resource_filename. Consider a more secure location (set with .set_extraction_path or the PYTHON_EGG_CACHE environment variable).
warnings.warn(msg, UserWarning)
I0619 12:07:27.604989 4360 mysos_scheduler.py:177] Options in use: {'framework_failover_timeout': '1m', 'twitter_common_log_simple': False, 'verbose': 'on', 'twitter_common_app_daemon_stdout': '/dev/null', 'twitter_common_log_scribe_category': 'python_default', 'api_port': 55001, 'twitter_common_log_log_dir': '/var/tmp', 'twitter_common_app_daemonize': False, 'twitter_common_app_ignore_rc_file': False, 'twitter_common_app_profiling': False, 'work_dir': '/tmp/mysos', 'twitter_common_app_pidfile': None, 'twitter_common_log_scribe_buffer': False, 'executor_source_prefix': None, 'election_timeout': '60s', 'twitter_common_app_rc_filename': False, 'framework_role': '*', 'executor_environ': '[{"name": "MYSOS_DEFAULTS_FILE", "value": "/etc/mysql/conf.d/my5.6.cnf"}]', 'twitter_common_log_scribe_log_level': 'NONE', 'executor_uri': '/home/vagrant/mysos/dist/mysos-0.1.0-dev0-py2.7.egg', 'twitter_common_log_disk_log_level': 'NONE', 'twitter_common_log_stderr_log_level': 'ERROR', 'framework_authentication_file': None, 'state_storage': 'zk', 'executor_cmd': '/home/vagrant/mysos/vagrant/bin/mysos_executor.sh', 'twitter_common_app_profile_output': None, 'framework_user': 'vagrant', 'zk_url': 'zk://10.141.141.10:2181/mysos', 'twitter_common_app_debug': False, 'twitter_common_log_scribe_port': 1463, 'twitter_common_log_scribe_host': 'localhost', 'scheduler_keypath': '/home/vagrant/mysos/vagrant/etc/scheduler_keyfile.txt', 'installer_args': None, 'backup_store_args': None, 'mesos_master': 'zk://10.141.141.10:2181/mesos/master', 'admin_keypath': '/home/vagrant/mysos/vagrant/etc/admin_keyfile.yml', 'twitter_common_app_daemon_stderr': '/dev/null'}
I0619 12:07:27.631294 4360 mysos_scheduler.py:219] Extracted web assets into /tmp/mysos
I0619 12:07:27.631490 4360 mysos_scheduler.py:244] Starting Mysos scheduler
D0619 12:07:27.635765 4360 connection.py:456] ZK loop started
D0619 12:07:27.636231 4360 client.py:374] Skipping state change
I0619 12:07:27.636354 4360 connection.py:566] Connecting to 10.141.141.10:2181
D0619 12:07:27.636468 4360 connection.py:570]     Using session_id: None session_passwd: 00000000000000000000000000000000
I0619 12:07:27.637034 4360 connection.py:276] Sending request(xid=None): Connect(protocol_version=0, last_zxid_seen=0, time_out=10000, session_id=0, passwd='\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00', read_only=None)
D0619 12:07:27.640809 4360 connection.py:261] Read response Connect(protocol_version=0, last_zxid_seen=0, time_out=10000, session_id=94019154140135465, passwd='V\x9e6Lf vmD\xd1\x88\xaa6\xb7R\x0b', read_only=False)
D0619 12:07:27.640971 4360 connection.py:603] Session created, session_id: 94019154140135465 session_passwd: 569e364c6620766d44d188aa36b7520b
negotiated session timeout: 10000
connect timeout: 10000
read timeout: 6666.66666667
I0619 12:07:27.641103 4360 client.py:378] Zookeeper connection established, state: CONNECTED
I0619 12:07:27.644429 4360 mysos_scheduler.py:250] Using ZooKeeper (path: /mysos) for state storage
I0619 12:07:27.645031 4360 connection.py:276] Sending request(xid=1): GetData(path='/mysos/state/scheduler', watcher=None)
D0619 12:07:27.646624 4360 connection.py:401] Reading for header ReplyHeader(xid=1, zxid=486, err=0)
I0619 12:07:27.646917 4360 connection.py:360] Received response(xid=1): ("ccopy_reg\n_reconstructor\np1\n(cmysos.scheduler.state\nScheduler\np2\nc__builtin__\nobject\np3\nNtRp4\n(dp5\nS'framework_info'\np6\ncmesos.interface.mesos_pb2\nFrameworkInfo\np7\n(tRp8\n(dp9\nS'serialized'\np10\nS'\n\x07vagrant\x12\x05mysos!\x00\x00\x00\x00\x00\x00N@(\x012\x05mysosB\x05mysos'\np11\nsbsS'clusters'\np12\ng1\n(ctwitter.common.collections.orderedset\nOrderedSet\np13\ng3\nNtRp14\n(dp15\nS'map'\np16\n(dp17\nsS'end'\np18\n(lp19\nNag19\nag19\nasbsb.", ZnodeStat(czxid=118, mzxid=118, ctime=1434628707473, mtime=1434628707473, version=0, cversion=0, aversion=0, ephemeralOwner=0, dataLength=424, numChildren=0, pzxid=118))
I0619 12:07:27.647811 4360 mysos_scheduler.py:262] Successfully restored scheduler state
I0619 12:07:27.660214  4360 sched.cpp:139] Version: 0.20.1
2015-06-19 12:07:27,660:4360(0x7fdaa3fff700):ZOO_INFO@log_env@712: Client environment:zookeeper.version=zookeeper C client 3.4.5
2015-06-19 12:07:27,660:4360(0x7fdaa3fff700):ZOO_INFO@log_env@716: Client environment:host.name=mesos
2015-06-19 12:07:27,660:4360(0x7fdaa3fff700):ZOO_INFO@log_env@723: Client environment:os.name=Linux
2015-06-19 12:07:27,660:4360(0x7fdaa3fff700):ZOO_INFO@log_env@724: Client environment:os.arch=3.13.0-55-generic
2015-06-19 12:07:27,660:4360(0x7fdaa3fff700):ZOO_INFO@log_env@725: Client environment:os.version=#92-Ubuntu SMP Sun Jun 14 18:32:20 UTC 2015
2015-06-19 12:07:27,672:4360(0x7fdaa3fff700):ZOO_INFO@log_env@733: Client environment:user.name=vagrant
2015-06-19 12:07:27,672:4360(0x7fdaa3fff700):ZOO_INFO@log_env@741: Client environment:user.home=/home/vagrant
2015-06-19 12:07:27,672:4360(0x7fdaa3fff700):ZOO_INFO@log_env@753: Client environment:user.dir=/home/vagrant/mysos
2015-06-19 12:07:27,672:4360(0x7fdaa3fff700):ZOO_INFO@zookeeper_init@786: Initiating client connection, host=10.141.141.10:2181 sessionTimeout=10000 watcher=0x7fdab498acc0 sessionId=0 sessionPasswd= context=0x7fda8c0010d0 flags=0
2015-06-19 12:07:27,675:4360(0x7fda9bfff700):ZOO_INFO@check_events@1703: initiated connection to server [10.141.141.10:2181]
2015-06-19 12:07:27,682:4360(0x7fda9bfff700):ZOO_INFO@check_events@1750: session establishment complete on server [10.141.141.10:2181], sessionId=0x14e05ec2c9b002a, negotiated timeout=10000
I0619 12:07:27.683342  4369 group.cpp:313] Group process (group(1)@127.0.1.1:56730) connected to ZooKeeper
I0619 12:07:27.683377  4369 group.cpp:787] Syncing group operations: queue size (joins, cancels, datas) = (0, 0, 0)
I0619 12:07:27.683393  4369 group.cpp:385] Trying to create path '/mesos/master' in ZooKeeper
Bottle v0.11.6 server starting up (using CherryPyServer())...
Listening on http://0.0.0.0:55001/
Hit Ctrl-C to quit.
D0619 12:07:30.685837 4360 connection.py:276] Sending request(xid=-2): Ping()
D0619 12:07:30.687498 4360 connection.py:386] Received Ping
D0619 12:07:34.005599 4360 connection.py:276] Sending request(xid=-2): Ping()
D0619 12:07:34.007508 4360 connection.py:386] Received Ping
D0619 12:07:37.255810 4360 connection.py:276] Sending request(xid=-2): Ping()
D0619 12:07:37.258078 4360 connection.py:386] Received Ping
D0619 12:07:40.526374 4360 connection.py:276] Sending request(xid=-2): Ping()
D0619 12:07:40.528445 4360 connection.py:386] Received Ping
I0619 12:07:41.477478 4360 mysos_scheduler.py:331] Interrupted, exiting.
2015-06-19 12:07:41,482:4360(0x7fdab9edf740):ZOO_INFO@zookeeper_close@2505: Closing zookeeper sessionId=0x14e05ec2c9b002a to [10.141.141.10:2181]
I have this in ZK under /mysos/state/scheduler
ccopy_reg
reconstructor
p1
(cmysos.scheduler.state
Scheduler
p2
c__builtin_
object
p3
NtRp4
(dp5
S'framework_info'
p6
cmesos.interface.mesos_pb2
FrameworkInfo
p7
(tRp8
(dp9
S'serialized'
p10
S'\n\x07vagrant\x12\x05mysos!\x00\x00\x00\x00\x00\x00N@(\x012\x05mysosB\x05mysos'
p11
sbsS'clusters'
p12
g1
(ctwitter.common.collections.orderedset
OrderedSet
p13
g3
NtRp14
(dp15
S'map'
p16
(dp17
sS'end'
p18
(lp19
Nag19
ag19
asbsb.

authors: eirslett xujyan yuriksan

repo: twitter/mysos


text:
getTweetLength not working

If text has link without http  google.com/contact  . getTweetLength is not returning correct value.

A url without protocol should count as 23 characters. See our test here:
https://github.com/twitter/twitter-text/blob/master/conformance/validate.yml#L230

140 - 117 = 23 characters.
@sridharkalaibala, please reopen this ticket if you're getting something else and we'll debug.

repo: twitter/twitter-text


text:
Adding A Bull Bear Power indicator

Added the Bull Bear Power (BBP) indicator to the pandas_ta library.
The indicator helps to gauge the strength of bulls and bears by calculating the difference between the highest and lowest prices relative to the close price.
The function accepts high, low, and close price data as inputs.
Returns a  pd.series with the calculated BBP values.
The default parameters used for the length is 13.

Hello @SharifDer,
Please checkout the development branch, make adjustments, check your tests, and resubmit.
Kind Regards,
KJ

@SharifDer
Also I thought I recognized this indicator. It already exists under Elder Ray Index (ERI).
KJ

authors: SharifDer twopirllc

repo: twopirllc/pandas-ta


text:
Change cook executor to be more container-friendly

Changes proposed in this PR

Report MESOS_DIRECTORY to cook as the sandbox location instead of MESOS_SANDBOX. This is the root filesystem path instead of the path in the container
Explicitly write executor.log in the MESOS_SANDBOX, not the current working directory

Why are we making these changes?
These make cook executor behave better when in a container.

Awaiting green build.

authors: pschorf shamsimam

repo: twosigma/Cook


text:
Makes test_progress_update_submit more reliable

Changes proposed in this PR
We need to wait for the job to complete in this test.
Why are we making these changes?
If we only wait until Running, the job might start running, then the instance might fail with e.g. "Agent removed", and then we'd have to wait for it to get scheduled again but we'd already have moved past this wait, which can cause the test to flake.

I don't think this is the right fix for this test, but it's better to apply this patch now, and I'll remove all of the unnecessary assertions (e.g., wait for sandbox) later.

authors: DaoWen dposada