Signage points out of order are considered skips

Describe the bug
If signage points are logged out of order, skip alerts are triggered.
Chia debug log:
2021-05-19T13:14:51.592 full_node chia.full_node.full_node: INFO     ⏲  Finished signage point 9/64: 99dc2878cd36e748f35caf8b48fc3e048dc1d2306c6e5675a51f5a6beaaf8826
2021-05-19T13:14:52.165 full_node chia.full_node.full_node: INFO     ⏲  Finished signage point 10/64: fbd8a6cbfd9ceb973842b998f9e221791495bb0b95bb594078ff9022dd0c64c4
2021-05-19T13:15:24.908 full_node chia.full_node.full_node: INFO     ⏲  Finished signage point 12/64: 3e0f1d609eef221f21a5bb8f5c5290380563d265da219f49fca47c4cb1b8392d
2021-05-19T13:15:24.912 full_node chia.full_node.full_node: INFO     ⏲  Finished signage point 11/64:<PHONE_NUMBER>e581b98e22e8776b41e61495751a7b2a9da27976120fef39c65e5a
2021-05-19T13:15:24.914 full_node chia.full_node.full_node: INFO     ⏲  Finished signage point 13/64: a5b4b7c0456eea6711776dd7781a828bac626e49f8f5f3083e031e456ffea0c7
2021-05-19T13:15:25.875 full_node chia.full_node.full_node: INFO     ⏲  Finished signage point 14/64: 2971d057ac883958a8e873d06d507ff66c13b58b30bc7a20e08014e2fb4dce10
2021-05-19T13:15:34.107 full_node chia.full_node.full_node: INFO     ⏲  Finished signage point 15/64: 520b8c1cc85449fc82351528e63e232f8d6bd85dc58a6a1abb11d486ea3b3f8f
2021-05-19T13:15:43.902 full_node chia.full_node.full_node: INFO     ⏲  Finished signage point 16/64: a0aa4580f66ee139c222297acd04f618bc1f5cfaa7aab75d76f63237a2ecdb7f

Chiadog log from same time:
[2021-05-19 13:15:24] [    INFO] --- Detected 1 skipped signage point. (non_skipped_signage_points.py:46)
[2021-05-19 13:15:24] [ WARNING] --- Experiencing networking issues? Skipped 2+ signage points in the last hour (non_skipped_signage_points.py:53)
[2021-05-19 13:15:25] [    INFO] --- Last farming event was 32 seconds ago. This is unusual (time_since_last_farm_event.py:47)

Notice signage point 12 that is logged before 11 completes.
Environment:

OS: Ubuntu 20.04
Python version: 3.8.5
PIP version: 20.0.2 for Chia, latest for chiadog (installed via install.sh)
Chia version: 1.1.5
Chiadog revision: 67328d7960

I cannot reproduce this on 0.5.1.
The logs posted in the issue description above are not triggering a skipped signage point detection.
That can be quickly verified by anyone, if you replace the content of the scrambled.txt test case and re-run the unit tests.
For your reference, the test is checking that none of the debug log events in that log are generating any events:
https://github.com/martomi/chiadog/blob/67328d7960608179f8a4d9858a70955de29932f9/tests/chia_log/handlers/test_finished_signage_point_handler.py#L59
I've gotten many of these notifications today, but when checking the logs, I can find actual skips - not false alarms from chiadog. Most recent one being:
2021-05-20T19:53:28.925 full_node chia.full_node.full_node: INFO     ⏲  Finished signage point 62/64:
2021-05-20T19:53:38.107 full_node chia.full_node.full_node: INFO     ⏲  Finished signage point 63/64:
2021-05-20T19:53:59.905 full_node chia.full_node.full_node: INFO     ⏲  Finished signage point 1/64:
2021-05-20T19:54:08.305 full_node chia.full_node.full_node: INFO     ⏲  Finished signage point 2/64:

I found a case from earlier today when I got notification and also reproduces the issue with the test:
2021-05-20T18:43:34.798 full_node chia.full_node.full_node: INFO     ⏲  Finished signage point 8/64:
2021-05-20T18:43:42.919 full_node chia.full_node.full_node: INFO     ⏲  Finished signage point 9/64:
2021-05-20T18:43:51.653 full_node chia.full_node.full_node: INFO     ⏲  Finished signage point 10/64:
2021-05-20T18:44:10.151 full_node chia.full_node.full_node: INFO     ⏲  Finished signage point 12/64:
2021-05-20T18:44:11.085 full_node chia.full_node.full_node: INFO     ⏲  Finished signage point 11/64:
2021-05-20T18:44:19.641 full_node chia.full_node.full_node: INFO     ⏲  Finished signage point 13/64:

Not sure this should be classified as a bug however. Signage points should arrive every ~9 seconds. Signage point #11 was supposed to arrive by 18:44:01. It didn't arrive. It was skipped and #12 arrived as expected 9 seconds later.
The fact that we also got #11 together (or even after #12) doesn't mean it wasn't skipped. Question: does the consensus allow processing and responding to signage point challenges out of order? Even if the farmer responds to a challenge for signage point 11, it'll be already at least 10 seconds late. So from my point of view it's as good as skipped.
What we can certainly do is to further throttle down the notifications for these occasional events however.

I am also getting a lot of warnings about skipped SP, but I can't find them in the log, so I guess I got the same problem.
Where can I find the exact mentioned SP and timestamps for those?
Imho skipped and late SPs are two different things.
What's annoying is, that I get multiple messages via telegram about this issue.
The warning says "Experiencing networking issues? Skipped 2+ signage points in the last hour. (non_skipped_signage_points.py:53)", but I get it several times per hour, every hour.
Monitoring should inform about wrong things you can and should fix, not spam you with things that seem to be normal in the current chia network status. ;)
I propose warning thresholds this should be configurable.
And btw Chia 1.1.6 was released today, which fixes some signate point stuff. (But I still get multiple warnings per hour.)
Further: great tool, thanks a lot for this!

The fact that we also got SP-11 together (or even after SP-12) doesn't mean it wasn't skipped. Question: does the consensus allow processing and responding to signage point challenges out of order? Even if the farmer responds to a challenge for SP-11, it'll be already at least 10 seconds late. So from my point of view it's as good as skipped.

To my understanding there is nothing that would forbid signing points out of order, since the P2P-Network is not reliable in this way. Also i don't think those have references to the previous SPs, so signing SP 5/64 first and then SP 4/64 should not be a problem consensus-wise. As far as the time you have for the SP goes, to my knowledge you have like 30sec, and since SPs come in around 8-10sec, you should be able to sign them out of order in the appropriate timeslot, but it's less likely that you will make it in time, yeah.

I'm considering removing these checks from chiadog at least for the time being.
The harvester monitoring already does 99% of the important checks.
Maybe will add a configuration with default state disabled.

I'm considering removing these checks from chiadog at least for the time being.
The harvester monitoring already does 99% of the important checks.
Maybe will add a configuration with default state disabled.

I would keep the checks and still count the number of SPs missed, but stop notifying if you miss some. This will happen regardless of how good the checks are implemented, since...well...it's the internet and P2P on top of that :) What i think is valuable to keep is the % of missed SPs on the daily report. I hope that stays.

Yes, I totally agree on that approach. Maybe also keep the alert notifications but only for >1% of skips over the past hour and not for individual occurrences 😄

Yes, I totally agree on that approach. Maybe also keep the alert notifications but only for >5% of skips over the past hour and not for individual occurrences

I'd love to see that % value configurable, with the default set to lets say something between 2-5%

Thanks for this not being a warning event anymore!
This just triggered a "skipped" log info in v0.6.0 in my farmer log:
2021-05-26T02:53:41.229 full_node chia.full_node.full_node: INFO     ⏲  Finished signage point 34/64:
2021-05-26T02:54:00.457 full_node chia.full_node.full_node: INFO     ⏲  Finished signage point 36/64:
2021-05-26T02:54:00.631 full_node chia.full_node.full_node: INFO     ⏲  Finished signage point 35/64:
2021-05-26T02:54:09.634 full_node chia.full_node.full_node: INFO     ⏲  Finished signage point 37/64:

Detected 1 skipped signage point.This is expected to happen occasionally and not a reason for concern. (non_skipped_signage_points.py:39)
(A missing space btw. ;))
But why is a cached and instantly catched up signage point still a "skipped" signage point?
You could log a more precise info like "Finished (cached) signage point out of order, but nothing missed"?
Great work!

I agree this is not worth the additional effort.


Makefile: Add deps-ubuntu target

Add target for installing the system dependencies listed in the README on a Debian/Ubuntu system.
Follows the same naming format of other ocrd modules (e.g. core), and could be used by ocrd-all when installing this module (I had to install openjdk manually after installing this with ocrd-all).

I will also open a pull request on ocrd-all for this

I will also open a pull request on ocrd-all for this

Splendid. If you do, just add a line…
deps-ubuntu: ocrd_pagetopdf

…above the existing rules for ocrd-pagetopdf.

@kba, can I merge with my changes?

@sulzbals, thank you for your contribution.


Add documentation for :preview_port

Changing the preview port is not mentioned in any of the swoosh documentation here or on hex. This took me a while to dig up. Hopefully it will save others time in the future.

Thanks @dweremeichik


iOS version requirement

I couldn't find iOS version requirements in the readme or in the release description. Would be useful. Did I miss it?

@anohren It's minimum iOS 13. Will add it to the README - thanks!


Remove redundant test, top level export

@jwong-nd it looks like this redundant test for convert_video is not needed if it's not re-exported in __init__.py. I don't think it needs to be exported by itself.

Coverage is at 96% though.


NOISSUE - fix building problems for things service

Signed-off-by: mteodor<EMAIL_ADDRESS>Pull request title should be MF-XXX - description or NOISSUE - description where XXX is ID of issue that this PR relate to.
Please review the CONTRIBUTING.md file for detailed contributing guidelines.
What does this do?
Which issue(s) does this PR fix/relate to?
Put here Resolves #XXX to auto-close the issue that your PR fixes (if such)
List any changes that modify/break current functionality
Have you included tests for your changes?
Did you document any new/modified functionality?
Notes

Codecov Report

Merging #741 into master will increase coverage by 1.02%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master    #741      +/-   ##
=========================================
+ Coverage   84.28%   85.3%   +1.02%
=========================================
  Files          68      66       -2
  Lines        4313    4220      -93
=========================================
- Hits         3635    3600      -35
+ Misses        472     416      -56
+ Partials      206     204       -2

Impacted Files
Coverage Δ

readers/postgres/messages.go

readers/postgres/init.go

Continue to review full report at Codecov.

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


Typdef; Found undefined, required object

Version Info
Closure Compiler (http://github.com/google/closure-compiler)
Version: v20161201
Built on: 2016-12-02 14:56

Command line arguments
  --compilation_level ADVANCED ./ --language_in ECMASCRIPT5_STRICT

Source Code
goog.provide('Gram.Injectable.Entity');

/**
 * @summary  Represents an injectable entity.
 * @typedef  {(Object|Function)} Entity
 * @name     Entity
 * @memberof Gram.Injectable
 */
Gram.Injectable.Entity;

Expected behavior
Recognize Gram.Injectable.Entity as a defined type which can either be an Object or a Function.
Actual behavior
./Gram/Injectable/Entity.js:8: WARNING - No properties on this expression
found   : undefined
required: Object
Gram.Injectable.Entity;
^^^^^^^^^^^^^^^

Is Gram.Injectable defined anywhere in your code or externs?

@Dominator008 Yes. Part of the code follows:
goog.provide('Gram.Injectable');
goog.require('Gram.Injectable.Exception.NotFound');
goog.require('Gram.Injectable.Exception.Collision');

/**
 * @class
 * @constructor
 * @memberof    Gram
 * @classdesc   — Content removed since it's insiginificant
 * @description — Content removed since it's insiginificant
 */
Gram.Injectable = function () {
};

Did you require Gram.Injectable in Entity.js?

@Dominator008 No, since by my understanding goog.provide is expected to take care of it. Please correct me if I'm wrong and if possible point me to a documentation of the goog.provide/goog.require API.
My interpretation is, that the error message
./Gram/Injectable/Entity.js:8: WARNING - No properties on this expression
found   : undefined
required: Object
Gram.Injectable.Entity;
^^^^^^^^^^^^^^^

is about expecting Gram.Injectable.Entity; to be of object type, while it is an undefined. However based on this documentation it seems like this is the way to go.

@adam-rocska I can't seem to reproduce this:
https://closure-compiler-debugger.appspot.com/#input0%3Dgoog.provide('Gram.Injectable')%253B%250A%250A%252F**%250A%2520*%2520%2540class%250A%2520*%2520%2540constructor%250A%2520*%2520%2540memberof%2520%2520%2520%2520Gram%250A%2520*%2520%2540classdesc%2520%2520%2520%25E2%2580%2594%2520Content%2520removed%2520since%2520it's%2520insiginificant%250A%2520*%2520%2540description%2520%25E2%2580%2594%2520Content%2520removed%2520since%2520it's%2520insiginificant%250A%2520*%252F%250AGram.Injectable%2520%253D%2520function%2520()%2520%257B%250A%257D%253B%250A%26input1%3Dgoog.provide('Gram.Injectable.Entity')%253B%250A%250A%252F**%250A%2520*%2520%2540summary%2520%2520Represents%2520an%2520injectable%2520entity.%250A%2520*%2520%2540typedef%2520%2520%257B(Object%257CFunction)%257D%2520Entity%250A%2520*%2520%2540name%2520%2520%2520%2520%2520Entity%250A%2520*%2520%2540memberof%2520Gram.Injectable%250A%2520*%252F%250AGram.Injectable.Entity%253B%26conformanceConfig%26externs%26refasterjs-template%26includeDefaultExterns%3D1%26CHECK_SYMBOLS%3D1%26MISSING_PROPERTIES%3D1%26TRANSPILE%3D1%26CHECK_TYPES%3D1%26CLOSURE_PASS%3D1%26PRESERVE_TYPE_ANNOTATIONS%3D1%26PRETTY_PRINT%3D1

@Dominator008 I'll do my best to put together a sharable codebase this weekend and push it to github to share. Still facing the same issue :(


Test ssl in all test

Provide one option enable_ssl in all test executable.

Need pass arguments from ctest to test executable.


Initial prototype for JWTCallerPrincipal and associated reference implementation

Signed-off-by: Scott Stark<EMAIL_ADDRESS>

Emily, ok, I'll move the ri module to its own repository.

I'm going to merge this to unblock anything, but it still needs work.  I'll raise follow up issues.


EthStorage Devs Meeting #106 Agenda

Meeting Info

Dec 03, 2024, 11:00 UTC+8
Duration: 60 minutes
Meeting link
Anyone can comment on the agenda where they would like this to be discussed.

Agenda

Protocol/App/Research progress
BD/Marketing progress

Goal:

EthStorage Mainnet Ready

Updates:

CircleCI

https://github.com/ethstorage/optimism/pull/97
https://github.com/ethstorage/optimism/pull/98
op-program make verify-compat failed: https://github.com/ethstorage/chain-test-data

Investigate supporting blob tx in L2

TODO:

Continue to fix circle ci issues

Goal:

Prepare WSC L2 testnet launch

Updates:

Created an issue to layout the work required for e2e test of new features.
report the batcher liveness issue to OP and discuss
review:

https://github.com/ethstorage/optimism/pull/98
https://github.com/ethstorage/optimism/pull/105

reading the e2e tests for batcher:

action tests uses a Mocked L2Batcher
system tests uses the real batcher, but things are asynchronous so it's hard to manually trigger the corner cases.
difference between action tests and system tests from George

TODO:

follow the batcher liveness issue and continue reading the  e2e tests for batcher.
Continue to deploy a new testnet after https://github.com/ethstorage/op-geth/pull/19 is merged.
Prepare a tool to handle scalar: https://github.com/ethstorage/optimism/issues/93
Investigate https://github.com/ethstorage/optimism/issues/82

Walrus: https://docs.google.com/document/d/18h3-s_j9c7Zg1ybU92EdsvX3hwxPkxnE/edit

Read the white paper, run walrus site builder, join co-learn group, summarize and prepare PPT.
Answer for questions (node准入机制，费用分配方法，存储证明等)

EthStorage Bug fix: https://github.com/ethstorage/es-node/pull/336

EthStorage x Taiko:

[x] investigation: read docs and go through the taiko codes (Merge the latest code)
[x] integration test
[ ] Run on Holesky chain (Under test)

Sync OP testnet node on Sepolia
https://github.com/ethstorage/es-node/pull/337
Archiver test doc

https://github.com/ethstorage/es-node/pull/338
https://github.com/ethstorage/es-node/pull/325

TODO

A doc to explain OP-ES integration with BatchInbox contract

Goal:
E2E test of 4-ary dispute game
Updates:

Review and fix Bill's code --Done
Alphabet E2E test  https://github.com/ethstorage/optimism/pull/105 -- Done

TODO:

cannon e2e test

Conduct airdrop test on 4,156,332 addresses:
Total time: 12 hours.
Gas Used:<PHONE_NUMBER>4.
Gas: 0.054 QKC.
https://explorer.testnet.l2.quarkchain.io/tx/0x84f8a527b308c2f6d768b8a18dd630523e675372b5ea6779c6456a996b0c136a

Study how the odyssey testnet implements session key:
the user signs the key data of the transaction, then uses a specific rpc to send the transaction, and the Sequencer signs the transaction and submits it to the chain

1 discuss with design team about quarkchain new website update
2 coordinate with pr agency about journalist pitch
3 working on kol marketing proposal
4 ethdenver, prepare the topic pitch and follow up on booth selection
5 taipei blockchain week, just got the visa confirming the speaker topic.


History doesn't work correctly

If undo or redo is called only one times more, the history will broke.
Reproduce steps:

draw a line,
push Undo button - first time,
push Undo button - second time,
history is gone.

Above steps same on redoing.
Codepen example

object:skewing is triggered after draw a line. It was missing I have added on this commit https://github.com/lyzerk/fabric-history/commit/155a17d8100bf557907a0ab60b132ff56d773f12.


[NFC][Breakpoint] Remove unused include

I didn't remove this when I was factoring out the swift bits from Breakpoint, but this is the last reference to swift inside of Breakpoint.

cc @JDevlieghere @dcci  @compnerd

@swift-ci please test and merge


datasets/ needs cleaning

The datasets directory in the code base has mostly outdated files. We need to migrate them to the new configuration system, or to delete (move to somewhere like 'old') those directories about no-longer used datasets.
First, we need if to automate that or not, ie,

how many are to be migrated?
Which one needs to be grouped into multi-specie configs?
Which one can be deleted (or parked somewhere like 'old')

@KeywanHP, @jparsons2222 are the best to answer this.

@jparsons2222 This has been in review for some time. I don't see any old datasets in the directory anymore. If this is done please close.


Determined release order in workspace is not working

I am publishing https://github.com/n0-computer/iroh using<EMAIL_ADDRESS>but unfortunately it determines an incorrect order and aborts half way through: iroh-resolver is attempted to be published before iroh-store, which fails due to their dependency.

I'm not seeing why iroh-resolver being published before iroh-store is a problem.  For me, the publish order looks correct.
I ran
$ cargo release publish --all -v
warning: disabled due to previous publish (0.1.3), skipping iroh-car
warning: disabled due to previous publish (0.1.3), skipping iroh-util
warning: disabled due to previous publish (0.1.3), skipping iroh-metrics
warning: disabled due to previous publish (0.1.3), skipping iroh-rpc-types
warning: disabled due to previous publish (0.1.3), skipping iroh-rpc-client
warning: disabled due to previous publish (0.1.3), skipping iroh-resolver
warning: disabled due to previous publish (0.1.3), skipping iroh-store
warning: disabled due to previous publish (0.1.3), skipping iroh-api
warning: disabled due to previous publish (0.1.3), skipping iroh-localops
warning: disabled due to previous publish (0.1.3), skipping iroh
warning: disabled due to previous publish (0.1.3), skipping iroh-bitswap
warning: disabled due to previous publish (0.1.3), skipping iroh-gateway
warning: disabled due to previous publish (0.1.3), skipping iroh-p2p
warning: disabled due to previous publish (0.1.3), skipping iroh-one
warning: disabled due to previous publish (0.1.3), skipping iroh-share

Those warnings should represent the publish order.
I then compared it with the output from cargo depgraph:

and the ordering seems correct.

Thank you for the detailed response! Looks like this is my own fault
https://github.com/n0-computer/iroh/blob/main/iroh-store/benches/store.rs#L7 uses iroh-store, but it is not listed in dev-dependencies
Will try to add, which should fix the issue hopefully.

Ah, yes.  This case broke in #422.
From the comment in the change
                // Ignore dev dependencies. This breaks dev dependency cyles and allows for
                // correct publishing order when a workspace package depends on the root package.

                // It would be more correct to ignore only dev dependencies without a version
                // field specified. However, cargo_metadata exposes only the resolved version of
                // a package, and not what semver range (if any) is requested in Cargo.toml.

A workaround is to leave out the version field in you dev-dependency.  The only downside is that people won't be able to run tests on your crate from crates.io, which really only affects crater.  This is the default behavior if you ran cargo add iroh-store --dev.


assigning categories to artworks (admin panel)

category and subcategory are select-able while adding a new artwork, but they do not get saved, and it leads to receiving error during saving the artwork.
admin panel/adding artwork

@aghpr it works already please be more specific maybe I am missing your point

I sent the error video file in Telegram @ehsan-g

@aghpr Done


I try to use kotlin to add an extension method to it. Why is the index out of bounds?

Observed vs. expected behavior

Steps to reproduce

Environment

Querydsl version:
Querydsl module:
Database:
JDK:
Additional details

Needs more info


Use es6 load syntax in documentation example

require() otherwise demands the module to be exported as module.exports

Unfortunately this doesn't currently work well with jest.dontMock etc. because imports are hoisted. I'm hoping to solve this in the future but for now I can't merge this.


can I Inference with 2 nvidia-4090?

Hi,
Thanks for opensora! I am trying Inference on my workstation (with 2 nvidia-4090) as the following:
(my cli-command):
torchrun --standalone --nproc_per_node 1 scripts/inference.py configs/opensora/inference/16x256x256.py --ckpt-path ./checkpoint/OpenSora-v1-HQ-16x256x256.pth
(my testing):

if I keep the current config(in 16x256x256.py: samples = 16) then I got "GPU no-enough-memory" error-message.
if I change config to sample = 4 then I could generate the output sample.mp4 successfully: but the image-quality is not good (I am using the same prompt "A serene night scene in a forested area..." and I can see some buildings and cars in my output-sample, but the video-quality is much lower than your sample).

my questions are:

can I run Inference on nvidia-4090? if 1 nvidia-4090(24GB) memory is not enough can I run Inference on 2 nvidia-4090?
how can I get the high output-sample quality (same as your samples)? can I get the high-quality output-video by your Model Weights (OpenSora-v1-HQ-16x256x256.pth)? or I need to continue to train it?

Thanks!
(my output sample with OpenSora-v1-HQ-16x256x256.pth and samples = 4):
https://github.com/hpcaitech/Open-Sora/assets/163908077/43b368b9-328f-4518-9b78-585ebdca16d5

hey @minounou this is unrelated to you question, but would you mind sharing your torch, torchvision, and nvidia-drivers versions? I also have a 4090 but am having trouble getting my install to work.
thanks

@jstmn
OK sure here is my config (my cuda is 12.2, I have 2 nvidia-4090, but it seems I only can use 1 of them now):
...
conda create -n opensora20240317 python=3.10
conda activate opensora20240317
conda install pytorch torchvision torchaudio pytorch-cuda=12.1 -c pytorch -c nvidia
...
(apex: for this I need to comment setup.py line-39, so 12.2-cuda and my pytorch coould work together)
git clone https://github.com/NVIDIA/apex.git
cd apex
(update setup.py line-39)
pip install -v --disable-pip-version-check --no-cache-dir --no-build-isolation --config-settings "--build-option=--cpp_ext" --config-settings "--build-option=--cuda_ext" ./
...
download T5 and OpenSora Model Weights (in girhub-page)
(Inference)
(update sample from 16 to 4: otherwise got GPU not-enough-mem error):
torchrun --standalone --nproc_per_node 1 scripts/inference.py configs/opensora/inference/16x256x256.py --ckpt-path pretrained_models/OpenSora-v1-16x256x256.pth

Same question for one NVIDIA RTX 4090, as this might be the configuration for most casual user and some universities.

我用一块3090，可以跑16x256x256的

我用一块3090，可以跑16x256x256和16x512x512的，batchsize设成1

只是infer么，finetune的话是不是不太够了

我用一块3090，可以跑16x256x256和16x512x512的，batchsize设成1

只是infer么，finetune的话是不是不太够了

是的呢

@tanghaom
batchsize设成1后、现在可以生成16x256x256、谢谢！
https://github.com/hpcaitech/Open-Sora/assets/163908077/d64c1465-362d-4c9e-9c55-1bfb22dd39a4

https://github.com/hpcaitech/Open-Sora/assets/13972782/9c48b0f0-1f25-4f89-afdb-5a28aefca982
Prompt: A soaring drone footage captures the majestic beauty of a coastal cliff, its red and yellow stratified rock faces rich in color and against the vibrant turquoise of the sea. Seabirds can be seen taking flight around the cliff's precipices. As the drone slowly moves from different angles, the changing sunlight casts shifting shadows that highlight the rugged textures of the cliff and the surrounding calm sea. The water gently laps at the rock base and the greenery that clings to the top of the cliff, and the scene gives a sense of peaceful isolation at the fringes of the ocean.


Makefile: simplify make rpm

Prior to this patch, make rpm would produce rpms that have the latest
tag as their versions. This was confusing, because one could never know
which contents are in a locally built rpm.
Change this so that the is version always based on the commit hash of
HEAD. This is easy: the golang macros read a %commit macro when it
exists and do this for us.
To simplify more, only define %_topdir to ./rpmbuild and use
rpmbuild's known directory structure (SPEC, SOURCES, RPMS, ...)
otherwise, to make it easier to find build results.
Build the specfile, tarball, source rpms, and rpms with make rpm,
without separate sub-targets. We can reintroduce them if they're needed
somewhere.
Also remove the check-working-directory target. It should be clear
from the output that only the currently-committed files are included,
because the resulting tarball and rpms contain the commit hash. Without
the check, one can work on the Makefile without having to commit all the
time, for example ;)

Please don't remove Makefile targets without prior notice. I use them. This commit broke my workflow because the checkout directory lives on NFS drive and I cannot execute make rpm there. That's why I use make srpm && rpmbuild --rebuild <srpm> because the rebuild takes place in ~/rpmbuild which is not NFS drive.
I also consider removing the check-working-directory an unfortunate choice because it prevents me from errors when testing new features. I don't think it was necessary to remove it.

I think we should have some common understanding of what kind of make targets we have and why. Splitting make rpm back into two seems reasonable to me. But most of the other make targets I'd like to drop (exactly because we don't know how and why they are used, so updating them becomes cumbersome, at least the usecases should be documented). My take is that private helpers should not live in the repo, but we should write this up and get consensus on what we want.

I am for bringing back the srpm target as well. All out other repos have it as well (lorax, cockpit-composer) and it makes sense because sometimes you just need a srpm. Especially, when building go packages takes a while.

I think we should have some common understanding of what kind of make targets we have and why. Splitting make rpm back into two seems reasonable to me. But most of the other make targets I'd like to drop (exactly because we don't know how and why they are used, so updating them becomes cumbersome, at least the usecases should be documented). My take is that private helpers should not live in the repo, but we should write this up and get consensus on what we want.

That's what I tried to address with the common development environment, because these issues are a result of the fact that each of us have a completely different workflow. In general osbuild-composer, when compared to other open source software projects, is very unfriendly to get started with. The development process in cumbersome because we remove all private/convenience make targets, helper scripts etc.
I agree that we need to keep the repo and code organized and, if possible, small but we shouldn't sacrifice pleasant development for few lines of code because unpleasant and cumbersome development process will result in less/worse contributions.

@msehnout Sorry for breaking your workflow. I should have requested a review from everyone.
I'll add the srpm target back today.

That's what I tried to address with the common development environment, because these issues are a result of the fact that each of us have a completely different workflow.

We will always have different workflows. For example, the check-working-directory target was breaking mine. Is there a different way we can support preventing you "from errors when testing new features."?

In general osbuild-composer, when compared to other open source software projects, is very unfriendly to get started with. The development process in cumbersome because we remove all private/convenience make targets, helper scripts etc.

Which convenience targets have we removed? I still see make build, make install (which is questionable, because it might get out of sync with the package), make ca and friends, which are purely convenience. Also, which helper scripts do you mean?
It is very hard to respond to such a general comment. What exactly do you think is cumbersome?

We will always have different workflows. For example, the check-working-directory target was breaking mine. Is there a different way we can support preventing you "from errors when testing new features."?

I thought we agreed on this one pretty long time ago. More specifically it was introduced to osbuild on Jul 25, 2019.  I introduced the same so that I can keep the same workflow for both.
Yes, there is a different way, I think we should agree on a development process, write it down to CONTRIBUTING.md and maintain it. Nobody is forced to use it, but it would be the single "official" development workflow.

Which convenience targets have we removed? I still see make build, make install (which is questionable, because it might get out of sync with the package), make ca and friends, which are purely convenience. Also, which helper scripts do you mean?

hmm, I didn't even know we have these because we agreed it would get out of sync with the package. I probably confused osbuild-composer with osbuild.

Also, which helper scripts do you mean?

For example make run-socket, here:
$ git log -p Makefile | tail -3
+
+run-socket:
+	systemd-socket-activate -l /run/weldr/api.socket -l /run/osbuild-composer/job.socket ./osbuild-composer

It is very hard to respond to such a general comment. What exactly do you think is cumbersome?

I always think about the workflow this way: If I was completely new to this project what would I need to do to build, run, and debug this project?
In case of osbuild-composer I always did checkout => rpm build (because I didn't know we still have make install) => systemctl start, then you need to attach gdb. In my opinion, this workflow is cumbersome. Ideal workflow (again mine, not necessarily for others) is to open an IDE, such as GoLand or VSCode, set up a target like go run osbuild-composer or go run osbuild-composer-dev * and click the green button (run or debug).
* I proposed to create alternative to osbuild-composer executable which wouldn't use the systemd socket activation so that I could easily use graphical debugger.

I'll add the srpm target back today.

Opened a PR: https://github.com/osbuild/osbuild-composer/pull/283

Yes, there is a different way, I think we should agree on a development process, write it down to CONTRIBUTING.md and maintain it. Nobody is forced to use it, but it would be the single "official" development workflow.

Sorry, I meant if there's a different way to support both your and my workflow. They seem to be in conflict with each other.

For example make run-socket, here:

Its removal has a good explanation: https://github.com/osbuild/osbuild-composer/commit/029dd0a81bdc405225b6e00b55e74a74eabbd42d. systemd-socket-activate isn't enough when using more advanced systemd features, like setting up /var/lib, /var/cache, and temporary directories. It's really not beginner-friendly to keep a target that doesn't work.

I always think about the workflow this way: If I was completely new to this project what would I need to do to build, run, and debug this project? [...]

Right, I'm happy to improve on the workflow, especially via documentation, but also through things like Tom's test-vm effort, which aims to streamline this.
I don't see the point in reimplementing systemd features only for development, though. There are probably other solutions that are less error-prone (running it in a container?).


too many block arguments (given 1, expected maximum 0)

minimized example from msgpack-crystal:
def bla(x = 1)
  if x == 1
    x + yield 10
  else
    x + yield
  end
end

p bla(1) { |y| 11 }
p bla(2) { 5 }

too many block arguments (given 1, expected maximum 0)

but this works in 0.17.4

Yes, this is a breaking change, it's listed in the changelog. you must do yield nil to fix this. Now all yield must yield exactly the same number of elements. We decided that slipping hidden nils isn't good.


[T3A3][T11-A3]Shailesh Nahata

Ready for review

@nahata-shailesh Some comments added. Please close the PR after reading comments.
Avoid accumulating unrelated changes into a single PR.
Tip: If you are currently on branch1 and want to create a new branch2, you need to switch back to master branch before creating branch2. If not, changes in branch1 will appear in the PR created from branch2 later.
Note also that commit messages should be in imperative mood (i.e. ‘fix’ rather than ‘fixed’).


CUDA 12 Conda Packages

Pushing for CUDA 12 Conda package builds of libraries for RAPIDS 23.04. This issue is for tracking that work.
Requirements (please recheck):
### Developer tasks
- [ ] I've confirmed the list below is correct (or updated if not)

### Toolkit dependencies from Conda
- [x] cuda-cudart
- [x] cuda-nvcc
- [x] libcufile

### Other dependencies from Conda using CUDA
- [ ] nvcomp (is this needed?)
- [x] pynvml (optional for benchmarks)

Thanks @jakirkham. For building, both libcufile and nvcomp are required. At runtime, KvikIO will dlopen libcufile and if it isn't found, it will use its fallback compatibility mode. If nvcomp isn't available at runtime, the IO still works.


Fix ScrollView. Simplify and improve message components

Automated message from Dropbox CLA bot
@borisyankov, it looks like you've already signed the Dropbox CLA. Thanks!


alignment support

Problem

While working on a project with salomon_bottom_bar package, I had to change the alignment of the elements. I made ad-hoc changes locally.

Solution

Let the user pass the mainAxisAlignment.

The given value will affect only if the length > 2
If not given, the default value will affect, i.e. spaceBetween

Though I'm not sure if it comes under the planned features of the package, I submit a PR.

Hi. Thank you for the PR. Promise 3 is that we will mimic BottomNavigationBar semantics. I do not see an alignment property on it. Can you please tell me if you have the same issue with BNB and how you use the existing BNB API to solve it? If we can get that answered, we can determine if there is a code change to be made here. Thank you.


Using the next branch cause errors with server side rendering

Getting the following error on the next branch:
[Vue warn]: The client-side rendered virtual DOM tree is not matching server-rendered content. This is likely caused by incorrect HTML markup, for example nesting block-level elements inside <p>, or missing <tbody>. Bailing hydration and performing full client-side render.

code looks like:
        <div class="overflow" >
            <v-touch class="inner"
                 :style="innerStyle"
                 v-on:swipeleft="next"
                 v-on:swiperight="prev" >
                <slot></slot>
            </v-touch>
        </div>

I know it's the v-touch component causing the error, since when I delete the component, the error goes away.

It seems even just requiring Hammer on the server is creating trouble during server-side rendering, so I will have to see what I can do about that at all.

I think a possible solution would be to provide a stubbed version of v-touch with the package. This stub would basically be a functionless component expect for the tag prop, and it would not not require Hammer (there's no use for it on the server anyway).
The user can then use a webpack alias in his SSR webpack config to load this in place of the normal module:
'vue-touch$': 'vue-touch/stub.js'

Yeah the issue might be that I stubbed out all of vue touch on the server. I'm use webpack aliases to have separate server and client side versions. Now that I think about it, that would make sense as to the cause of the problem.
I will try and send you a repo to show what I'm doing, but might take a while, since this is gonna be a busy work week.
Thanks for starting to look into it.

@pajtai I don't think the repo is nessessary anymore, already working on the solution.

Now available in v2.0.0-beta.2

Hello,
I have embeded with the ssr workaround to the vue next.js. The stuff is working however it brokes the DOM and I am getting 'the client-side rendered virtual DOM tree is not matching server-rendered content...'
using beta-4

Please open an issue and provide a reproduction.


chore: fix 404 status URL

PR description
The previous link has expired and has been replaced with the latest address.
Thanks for sending a pull request! Have you done the following?

[x] Checked out our contribution guidelines?
[x] Considered documentation and added the doc-change-required label to this PR if updates are required.
[x] Considered the changelog and included an update if required.
[x] For database changes (e.g. KeyValueSegmentIdentifier) considered compatibility and performed forwards and backwards compatibility tests

Locally, you can run these tests to catch failures early:

[ ] unit tests: ./gradlew build
[ ] acceptance tests: ./gradlew acceptanceTest
[ ] integration tests: ./gradlew integrationTest
[ ] reference tests: ./gradlew ethereum:referenceTests:referenceTests

Hi, thanks for your interest in our project. We'd love for you to contribute code, however we don't accept trivial contributions such as this. Have a look at good first issues and please read our contributing guidelines https://github.com/hyperledger/besu/blob/main/CONTRIBUTING.md#guidelines-for-non-code-and-other-trivial-contributions


Update Excel.Workbook.CheckInWithVersion.md example to follow proper indentation standards

Updated example to use proper indentation standards

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

Docs Build status updates of commit 21d679f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

api/Excel.Workbook.CheckInWithVersion.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@sancarn Thanks for the fix!


Filter Tracers before adding LogObject and converting to Traces

Issue Number
~Relates to #2005, I think.~
edit by @KtorZ: relates to #1997
Overview
Changes the tracer minimum severity so that it filters logs before adding LogObject and converting to Trace.
Users noticed that setting --trace-db=off improved performance, especially when restoring many wallets in parallel.
Comments
Benchmarks not fixed yet.

bors r+


publish to maven repo

would like to give it a spin without having to build it myself...

👋 forgot to close this issue, this is complete
https://search.maven.org/artifact/com.mailersend/java-sdk


Beep and red line

hi
1)Is there any way to beep when the barcode is scanned?
2) Have red line in the middle of the scanning part ?

Not currently, though both could potentially be implemented. The first seems like a more worthy feature than the second, as getting a buzz/beep when the scan is complete could be a convenient feature.


[question] Libcamera-vid capture

With libcamera-vid, Is it possible to capture frame by frame with a signal working as a trigger?
You could answer RTFM😀
Thanks

Hi, do you mean that you would send a signal and it would capture just a single frame, and then the camera would keep on running while it waits for the next signal?
It doesn't have that behaviour at the moment, I think if you send a signal it starts recording permanently until another signal pauses it again. I don't think there's any way you can time these so as to guarantee a single frame.
libcamera-still has this behaviour already (though the version in apt implements this incorrectly; we fixed it in the sources and will be rolling that out "shortly"). It also performs a camera mode switch to full-resolution readout for the capture before switching back to the preview mode again, so capturing a frame takes a bit longer, and maybe this isn't what you want.
If you have some familiarity with C/C++ it might be worth editing libcamera_vid.cpp yourself to get the behaviour you want, the code is not at all difficult. With h.264 you might need to set the GOP size to 1 so that every frame is an I-frame, with MJPEG obviously there are no such problems.
If you wanted to try that, certainly feel free to ask questions (perhaps over on the Camera forum) and we'll try to help.

yes , this is exactly what i wish to do .
i have rebuilt libcamera and the last sources, it works well with libcamera-still -s but i need a process as fast as possible.
thank you for your complete answer, i will try to edit libcamera_vid.cpp and also with MJPEG codec, wich is perfect for me.
and i'll fall over to the forum . thanks again

i try libcamera-vid with -s option .
it seems to work just one time if i want to switch pause/resume mode.
libcamera-vid --version
libcamera-apps build: 9d89e1e858b3-intree 11-12-2021 (14:21:06)
libcamera build: v0.0.0+3346-f16acb27

Hmm, just off the top of my head I wonder if this fix needs applying to libcamera_vid (are you in a position to try that?). Otherwise I'll have to investigate.

yes it works just by adding the same fix
signal_received = 0;
thanks

Thanks for letting me know. I'll get that merged into the code.

Closing this now, as the relevant patch has been merged.


Fixed equalizer preAmp handling

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Jax decompiler

A jax decompiler would take jaxpr code and produce a more readable Python code. Even if some information about the original function is lost (obfuscated code) like variable names being lost. Decompilers are important tool for reverse-engineering.
Here the illustration of the usefulness of a decompiler.
(step a)  f(x) is my function:
from jax import numpy as jnp
f=lambda x: jnp.log(1+jnp.exp(x)

(step b)  The derivative does not give the right answer:
print(grad(f)(100.)) # nan <- expected 1
(step c)  The JAXPR code of the derivative (along x axis) is:
from jax import make_jaxpr
make_jaxpr(grad(f))(100.)

output:
{ lambda ; a:f32[]. let
b:f32[] = exp a
c:f32[] = add 1.0 b
_:f32[] = log c
d:f32[] = div 1.0 c
e:f32[] = mul d b
in (e,) }
(step d) The Python equivalent (manually written) is:
df=lambda a: (1 / (1 + jnp.exp(a))) * jnp.exp(a)
print(df(100.)) # nan <- expected 1

(step e) We can easily understand the problem. I refactored a little bit the code and improved the arithmetic stability:
df=lambda x: 1 if x>10 else (jnp.exp(x) / (1 + jnp.exp(x)))
print(df(100.)) # 1. <- expected answer

A decompiler would automate step d.

Thanks for the suggestion! It's an interesting idea. There would be some complexity involved for a full solution; off the top of my head:

how to decide if expressions are inlined or assigned to variables?
how to deal with call primitives?
how to deal with primitives whose API is quite different from the typical Python API, e.g. scatter_p, gather_p, conv_general_dilated_p, etc.?

It could be a fun challenge though 😁

I will release a first version working for simple code samples in next days.

Cool - if you haven't seen it already, this might be a useful resource for crawling/interpreting jaxprs: https://jax.readthedocs.io/en/latest/notebooks/Writing_custom_interpreters_in_Jax.html

I implemented a first version: https://github.com/PierrickPochelu/JaxDecompiler
For instance, it supports 23 common jaxpr operators such as "add, mul, neg, cos, sin,...". It supports also partially pmap.


Links from Getting Started Tutorial are broken

https://allegro.ai/blog/setting-up-allegro-ai-platform/
It seems that examples are moved and some links became broken. See:

Trains has got you covered (https://github.com/allegroai/trains/blob/master/examples/hyper_parameters_example.py)

as well as storing general purpose artifacts (https://github.com/allegroai/trains/blob/master/examples/artifacts_toy.py)

Thanks for pointing it out @elimohl - Seems like some housecleaning is order post refactor :)
The relevant code is now under:
https://github.com/allegroai/trains/blob/master/examples/reporting/hyper_parameters.py
and
https://github.com/allegroai/trains/blob/master/examples/reporting/artifacts.py

@elimohl Updated the blog with the correct links - Thanks again!


The information for 'stabilityai/stable-code-3b' has not been added to the config.py file.

I wrote it like this:
##########################
Stability AI Stable-Code-3b
##########################
stable_code_3b = [
# https://huggingface.co/stabilityai/stable-code-3b/blob/main/config.json
dict(
name="stable-code-3b",
hf_config=dict(org="stabilityai", name="stable-code-3b"),
block_size=16384,
vocab_size=50304,
n_layer=32,
n_embd=2560,
)
]
configs.extend(stable_code_3b)

The weights I downloaded from Hugging Face are in the form of safetensors, and the current convert_hf_checkpoint.py file does not support this format, always resulting in errors.

Hello @ARROGANT666
If the model seems to be properly working, you can submit a PR.
Here you can find an example of how it was done before.


BIGTOP-3650: Improve Hive's Debian packaging

Raised compat to '12' and followed some suggestions from Lintian.

thanks @iwasakims!


L4m2quicksight

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Updaye from main


node-pg-migrate erroneously shown as "out of date"

The image says "dependencies out of date" yet the detailed list says 6 are up to date.
https://david-dm.org/theoephraim/node-pg-migrate

I have the same for my project: https://david-dm.org/cyclejs-community/cyclejs-sortable

Same with here:
https://github.com/alanshaw/david-www/issues/367

Thanks for your patients. I believe this bug has been resolved in by https://github.com/alanshaw/david-www/commit/6436f07bec18384d0d83a8e89b7fb40286da5bc8. Please comment if you notice this issue again.


Reddit Stream

Stream Reddit posts to a manageable data structure.
A local file should suffice for now. Later the stream could be directed to cloud-based storage.
See PRAW: The Python Reddit API Wrapper.

Work complete.
No PR linked as work developed as initial repository branch.
wp-1-reddit-stream renamed to main.
Closing issue.

Work complete.
No PR linked as work developed as initial repository branch.
wp-1-reddit-stream renamed to main.
Closing issue.


Accessing Client inside different types of interactions

👋 Hey and thanks for Tempest!
I've noticed that some of the interaction structs have a Client key that isn't set during the interaction callbacks.
For example, for ComponentInteraction, the Client is attached to the interaction here:
https://github.com/amatsagu/tempest/blob/c097fa4fc3c577e77fe58d15bf7da69af7c97be3/client-handler.go#L83
Compare to CommandInteraction and ModalInteraction where itx.Client is nil in the corresponding handlers.
I'm not sure whether this is by design, but it looks like it would be possible to provide the client for the other interaction types by setting itx.Client in the other switch cases too. Would you accept a PR for that?
My current workaround inside my modal submit handler is just to create a brand new client with NewClient so that I can send multiple messages in response to the modal submission.

Sure thing! I don't really remember why I've done it the way it is but your suggestion sounds logical so let's go with that. I'm currently short on time so if you want to make a PR, I would appreciate it.
This lib was first project I've made from A to Z using Go, back then I was still new to idea of goroutines, channels, etc. so some parts of code are made to just work but I understand they may look weird as they do not follow any "good patterns".

This lib was first project I've made from A to Z using Go, back then I was still new to idea of goroutines, channels, etc. so some parts of code are made to just work but I understand they may look weird as they do not follow any "good patterns".

😄 Been there myself many times! Thanks for the super quick response. PR is over at #34.


openssl build problem on android

I am using tauri to create a mobile android app using tapo as a depenendy.
Tapo has a depenency on openssl which gives me cross compile problems.
Is this a known issue?
Did you consider switching to rustls to avoid native openssl issues during compilation?

Yes, OpenSSL is known for compatibility issues, even on the platforms on which it's supposed to be supported.
I'd definitely welcome switching to rustls.
I think someone started doing it on a fork, but I'm not sure what happened to the effort or where it is exactly.
If someone wants to have a go at it, please shout in the next couple of days.
Otherwise, I'll try to find some time myself now that there's clear interest expressed.

Hi Mihai,
I made local changes to tapo to remove openssl and replace it with sha1 and sha2 and I commented the rsa stuff out as it was to complicated for the moment.
Also Claude and ChatGpt were not really giving consistent solutions. But the dummy tapo was finally building with tauri and I could install the android native app with tapo.
Of course the requests were not working because of the commented out stuff.
I am a Rust Newbee. I have some experience with Golang and Python and I found a lot of crypto crates and I am not sure which to go for ... Also the question is how trustworthy they are. I figured that openssl is a pretty solid battle proofed solution. Not sure what the security requirements for your project are ...
But I will try again today evening to see if I can get the rsa stuff also working ...

I've started having a quick look, and there seem to be three areas that openssl covers and could be replaced with lower-level crates.

hashing: sha1 and sha2 crates should cover this
asymmetric encryption (RSA): the rsa crate looks like a good choice
symmetric encryption (AES):  I haven't had a chance to look into this yet

Working :-)
I tried yesterdayh ChatGpt4 and Claude3.5 until my free tokens were over. I did not really succeed but got some inspirations.
The problem with the AI is that there are many crate versions of rsa and cipher and cbc and the guys are changing the API frequently. The AI gets confused und mixes different versions. So it becomes worse after some time.
I started today fresh and limited the changes and used an older crate version for rsa which is 0.7 instead of 0.9 and with some manual fixing now it works for me.
You can see it in the picture :-)

I am a big fan of your tapo library ... Only in case I did not mention this before.
I guess the refactoring would need a look from an expierienced guy and the upgrade to rsa 0.9 I would also think is necessary. But I am putting the stuff I have as a pull request so you can see where this is going and you can fine tune it. Or give me some comments and I try to fine tune it.
I am also not sure if you have some test cases which I can run and validate the changes ...

I now also upgraded to crate version 0.9.6 for rsa so this should be fixed.

This is great! #275.
I need to understand what's going on and figure out how to test it, but this should serve as a very good starting point while also unblocking your use case.

Yes. That is the scary part :-) I only understand have of it. Cryptography sucks and Cryptography with Rust sucks even more :-)
It works for me with Android and Linux Desktop so I am fine with the fork for now, but I can see a big plus for the tapo lib as you get rid of the native libs that are difficult to ensure that they work on all platforms.
But take your time. I can live with the fork for now :-) In case I find problems I let you know ...

Ok, I think I've got it. https://github.com/mihai-dinculescu/tapo/pull/281
Your PR has been a great source of inspiration, and I've ended up writing the same thing, which is just a tad more optimised (e.g., the padding is done through the library rather than manually).
Mind giving it a try?

I will today night. Let you know as Sohn as I have results
Mihai Dinculescu @.***> schrieb am Fr., 18. Okt. 2024,
17:02:

Ok, I think I've got it. #281
https://github.com/mihai-dinculescu/tapo/pull/281
Your PR has been a great source of inspiration, and I've ended up writing
the same thing, which is just a tad more optimised (e.g., the padding is
done through the library rather than manually).
Mind giving it a try?
—
Reply to this email directly, view it on GitHub
https://github.com/mihai-dinculescu/tapo/issues/274#issuecomment-2422680103,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACZPKPEE5S3DOFIH66XQCF3Z4EPIHAVCNFSM6AAAAABPTD3RUCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRSGY4DAMJQGM
.
You are receiving this because you authored the thread.Message ID:
@.***>


Use NoCommentsYamlLine

The NoCommentsYamlLine is implemented but never actually used when reading the yaml. Let's use it.

done. Ticket #100 was opened in this task.


Somesh - app with two buttons and Daq LEDdisplay

Stopwatch app counting seconds (daq.LEDDisplay), with a start and stop button

[ ] Layout- 1row:1col;  1row:2col;  2row:1col;  3row:1col;  multiple row and col
[ ] Callback- 1input:1output;  2input:1output;  1input:2output;  Multiple output input
[ ] Components - dropdown, checklist, DataTable, RadioItem, etc.
[ ] Data set - sports, geology, manufacturing, finance, general
[ ] Graph- Bar, Line, Histogram, Scatter, Pie, Candle, etc

I've submitted PR for this
It's working as expected 😄


Horizontal scroll bar appears on the menu when the window is narrow 🐛

URL of the Page
https://www.researchequals.com/
What happened?
When the window is narrow, the menu area shows a horizontal scroll bar:

(when viewing with the width of ~800 px)
Steps to reproduce

Go to https://www.researchequals.com/
Log in
Adjust the window width to 800px

What browser(s) did you use?
Chrome
Anything else?
No response

What do you think should happen instead? From my point of view this is expected behavior at the moment, because it's scrollable. Happy to explore adjustments as this menu is getting a bit cluttered (collections will also be added...)

Chris and I talked and we decided to set the breakpoint identical to the nav bar. 👍  I will try implementing


Use XDG_CONFIG_HOME on MacOS

I don't have data on this but I am pretty sure that most people place scripts in unix style directories rather than /Library. As such, quite a few people probably use XDG_CONFIG_HOME even on MacOS. Yet this library doesn't support that, which means every CLI app relying on this library also doesn't (https://github.com/jesseduffield/lazygit/issues/641)

Yeah, I am just looking at this library now and trying to figure out how to override that. I think there should be the option for override for OSX apps. Definitely CLI apps want to be going in the XDG_CONFIG_HOME.

/Library/Application Support doesn't appear standard at all for CLI tools. I don't have a single CLI tool with configuration there.


Add support for ON CONFLICT DO UPDATE SET with EXCLUDED table

This adds support for insert queries containing ON CONFLICT DO UPDATE SET
expressions with EXCLUDED table references. Tests verify identical semantics as
the ON DUPLICATE KEY statement.
Examples:
CREATE TABLE t1 (id int primary key, other string);
INSERT INTO t1 (id, other) values (id, 'str');

-- Set other to 'backing up' on duplicate key 1
INSERT into t1 (id, other) VALUES (1, 'test')
  ON CONFLICT DO UPDATE SET other = 'backing up';

-- which is identical to
INSERT into t1 (id, other) VALUES (1, 'test')
  ON DUPLICATE KEY UPDATE other = 'backing up';

-- Overwrite other with 'test'
INSERT into t1 (id, other) VALUES (1, 'test')
  ON CONFLICT DO UPDATE SET other = excluded.other;

-- which is identical to
INSERT into t1 (id, other) VALUES (1, 'test')
  ON DUPLICATE KEY SET other = values(other);

@mfussenegger @matriv @chaudum Thanks for your review. I've addressed your comments.
@matriv Considering the expectedException, I think it is ok to use try/catch/fail here because otherwise we have to duplicate a lot of code in extra test methods.


Add Sorting Function for Projects in Dataset Layout Page

Description
backend branch: sum_addLastModifiedMeta
Able to sort project based on created date, last modified date and project name.
Fixes # (issue)
https://user-images.githubusercontent.com/81958029/123570819-99adcf00-d7fb-11eb-9fd0-205c26799059.mp4
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Tested on?

[x] Windows
[ ] Linux Ubuntu
[ ] Centos
[ ] Mac
[ ] Others  (State here -> xxx )

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged

Added created and last modified timestamp

hover to see the timestamp
https://user-images.githubusercontent.com/81958029/123733853-de566a80-d8ce-11eb-803a-ec0e6e26c366.mp4


Made it so the folders only get ingored in the root

With the current setup these folders are ignored in the whole repo, but they're only automatically generated in the project root so it makes sense to only ignore the ones in the root.
I made this change because one of the assets in my project uses a folder called 'Library', and I was wondering why it never uploaded that folder.
It might also make sense to extend this 'root only' change to VS/MD and crash report lines, as I believe those can only be placed in the root.

Thanks!


Add dupe check passing two fingerprints

In my scenario, I save the fingerprints and check for dupes sometime in the future.
I thought that a module method for that would do the trick.

I really appreciated the addition you made to the gem, @gallois; I hope it gets pulled in.

This is also a feature that I can use.

Hey @gallois. Sorry I've left this hanging for so long. Thanks for the PR 👍.
I can understand the desire to add the module method. I'l take a look at it this weekend and work on moving it into the gem.

@gallois thanks for the pull request!


gRPC Integration Test Exception

When I try to debug the integration test for the gRPC that is  SayHelloUnaryTest in class GreeterServiceTests i am getting the following exception

Grpc.Core.RpcException: 'Status(StatusCode="Internal", Detail="Error starting gRPC call. ArgumentOutOfRangeException:  (Parameter 'count')
Actual value was 0.", DebugException="System.ArgumentOutOfRangeException:  (Parameter 'count')
Actual value was 0.")'
Inner Exception
ArgumentOutOfRangeException:  (Parameter 'count')
Actual value was 0.
how can i fix that issue i spent a lot of time on it

Hi @farooqahmad1989,
This question for troubleshooting your app would be best handled on a forum dedicated for that rather than this issue form specifically for docs.
We recommend posting to a community support group like Stack Overflow with the asp.net-core and grpc tags.

Stack Overflow
ASP.NET Core Slack
ASP.NET Gitter

Potential bugs in the ASP.NET Core framework and product feedback can be reported at dotnet/aspnetcore issues (include full repro steps and cross-link to a repro project in GH when appropriate).
That said, The error you’re encountering is a Grpc.Core.RpcException with an ArgumentOutOfRangeException for the parameter ‘count’. This exception is thrown when the value of an argument is outside the allowable range of values as defined by the invoked method.
Some places to start as a guess, knowing little about your specific app:

Check the ‘count’ parameter: Ensure that the ‘count’ parameter in your code is being assigned a valid value. If it’s an index for an array or collection, make sure it’s within the valid range.

Check the gRPC call: The error message suggests there’s an issue starting the gRPC call. Make sure the server is running and accessible, and the client is correctly configured to communicate with the server.

Check for race conditions: If ‘count’ is being modified in multiple threads, it could lead to a race condition where one thread is reading the value while another is modifying it.

Check the server logs: If the server is throwing an exception, it might provide more details about what’s going wrong.

I will close this doc issue, but if you feel I am missing something and have specific changes you want in a doc, please feel free to re-open.  Thanks.


Is it possible to hide DebugDrawer layout at runtime?

I want to hide DebugDrawer at runtime - it means no UI of DebugDrawer, user cannot swipe from right to left to show it. Is it possible?

You mean that DebugDrawer should be available only for debug builds but not for release builds?

Not related to debug or release build, but I want to hide DebugDrawer layout. Only show its UI by touch on secret region. For examle when send build to QA, I don't want to let them know there is DebugDrawer, however I can activate it anytime I need.

You can set lock mode via debugDrawer.setDrawerLockMode(DrawerLayout.LOCK_MODE_LOCKED_CLOSED);
and then call debugDrawer.openDrawer();

I'm closing this issue. If it is still necessary we could open it later.


devpkg: better flake references and installable parsing

In anticipation of adding support for non-default package outputs, I wanted to clean up some of the flakeref parsing in devpkg. This will make it easier to handle Nix's flakeref#attrpath^outputs installable syntax. This PR is broken up into two commits: one that handles flakeref parsing and one that handles installable parsing.
The ParseFlakeRef function is able to parse the more common flakerefs that devbox currently supports ("path", "flake", "indirect", etc.). It doesn't support mercurial, gitlab, and sourcehuthut for now. The ParseFlakeInstallable function parses Nix flake installables, which are a superset of the flake reference syntax. It allows an attribute path and/or outputs to be specified using the flake#attrpath^outputs syntax. The tests were validated using the nix expression builtins.parseFlakeRef "ref" and the nix flake metadata <ref> CLI.
The goal isn't to perfectly replicate Nix's parsing of flake references (which itself is sometimes inconsistent), but to make it good enough to handle flakerefs in devbox.json.

It's the second one. For handling the flake-like syntax supported in devbox.json (which users have to add manually).


message view: Render formal date string as tooltip on recipient row

A formal date string will be assigned to the title attribute of the
recipient_row_date and date_row elements.
e.g. "Wednesday, April 5, 2017"
Fixes #4663.

Automated message from Dropbox CLA bot
@dhcrzf, it looks like you've already signed the Dropbox CLA. Thanks!

The timerender module's heavy use of tuples is not the best programming style, and it doesn't have tests, which made this not the most fun to review.  But your changes look good.  Merged, thanks @dhcrzf!
If you're interested, adding node tests to this module (http://zulip.readthedocs.io/en/latest/testing-with-node.html) and then refactoring timerender to pass around objects would be a good adjacent projects :).
Thanks for fixing this @dhcrzf!

@dhcrzf a quick follow-up project that would probably be useful: the date rows currently don't show the year when it is different from the current year, which I think they definitely should.
Are you interested in fixing that, while you've got the timerender.js system figured out?

Sure. And I do agree about refactoring the timerender.js module and adding test coverage. What is the protocol for creating new GitHub issues for Zulip? Am I allowed to do that myself?

Yep, feel free to open issue(s) for these follow-up tasks!  You don't have permission to add labels (blame GitHub for that limitation), but someone will usually be by to add labels pretty quickly.

@timabbott he should be able to add labels with @zulipbot label name1 name2

true, that's an option :)

@timabbott Would you please clarify the issue with the date rows not showing the year for me? I'm not sure I follow.

If you look at messages from a year ago, the date in the recipient bar (not using the hover to get the title) will be "June 05".  It should be "June 05, 2016".


fix(#25): Mark certain structs as !Sync

Some objects in dlib are not Thread Safe, thus they should be marked as !Sync to do this in stable Rust, you add a field with UnsafeCell.
If you don't need UnsafeCell, then just put it inside a PhantomData, this tells the type system that your type should act as if it held an UnsafeCell, but it doesn't actually have it.
When negative_impls is stabilized, we can use that instead.
I would suggest applying this patch then bumping the crate version to 0.3.1 and yanking 0.3.0 to prevent people from downloading the previous version.
Closes #25

Confirmed as your issue https://github.com/ulagbulag/dlib-face-recognition/issues/25#issuecomment-1700358845!
Thanks :)


Cleanup

Please update (branch is out of date with base).

This is cleanup for custommetrics which will not be available in v0.16


Updating removal of edgecontroller logs and some nits

Updating steps to remove edgecontroller logs and some UI related improvements

cc @sids-b

lgtm


login problame

otp not korking,,, how to fix it,, pls suport me,,, pls reply me

I am having the same issue. I am not receiving OTP, I only get a call from a number and the call hangs up as soon I pick.


MDEPLOY-245: Remove the remnants of the obsolete updateReleaseInfo parameter.

Jira: MDEPLOY-240 - trivial follow-up fix.

[X] I hereby declare this contribution to be licensed under the Apache License Version 2.0, January 2004

Can you please create a new JIRA with a reference to the old one and describe that information has not been removed completely.

Sure, https://issues.apache.org/jira/browse/MDEPLOY-245

Thanks for your contribution.


Grammar module build process

Should the Grammar module be built automatically?
There is no mention of it in the README.md and it's impossible to build the plugin without its generated sources. Thanks!

I added a step in the README to build the grammar module. Since it can break things, I think it's a good idea to build it when needed, i.e. when we know the grammar has changed and we are in the mood to fix compilation errors :)

Thanks! That was precisely my experience :)


Elasticsearch shield plugin

Provide a shield plugin to backup/restore/store/retrieve/purge elasticsearch snapshots to/from s3. Should backup elasticsearch data directly, as if it's a stand-alone (non-service-broker-based) system.

Current implementation involves communication between target + store, which is going to be impossible when we add the encryption layer in.
For now, the elasticsearch plugins are on hold, until needed, at which time possibly https://github.com/taskrabbit/elasticsearch-dump can be used, to alleviate the need for modifying shield to support a target-only style backup. Might also need to implement incremental backups for this, as dataset sizes are going to get rather large.


Attack Indicators Plugin Displays Removed Styles

Upon hopping worlds, it seems that that the "Attack Indicators" plugin fails to remove blocked attack styles. Once the unwanted combat styles are present, they do not disappear until the player's weapon is changed, the plugin is reset, or client is restarted.
Edit: Setting a spell to autocast also breaks the plugin. To restore functionality, one of the procedures noted above must be followed.

Is this fixed as of #639 ?

Yes, this is fixed.


Fixes

preserve original entry order (for easier diffs)
never replace "inproceedings" with an arXiv link (better an obscure conference that's not on DBLP than just arXiv)
fix some crashes

OK looks like I need to update from upstream and then try again


Creating Octomap from PointCloud

I found that using moveit-RViz, octomaps can be generated with a robot fitted with depth camera publishing its pointcloud.
I am trying to generate the same scenario but instead of using the pointcloud from depth camera, I want to use the pointcloud published by ply_publisher (.ply is generated using LSD_SLAM algorithm). But unlike the depth camera which has a transform, the sensor_frame of ply_publisher does not have a transform.
So, is it possible to publish the ply_publisher pointcloud as though the depth camera in the robot is publishing the pointcloud? Is my method of generating octomaps correct?

You can use the _frame:=/sensor_frame parameter to publish the point clouds in a given frame. Now you only need the publish the corresponding TF, and your setup should work.


Exception: not find lib assign_box_cuda

What are the requirements to run this because I am getting this error
`
python setup.py install
running install
running bdist_egg
running egg_info
writing nms_cuda.egg-info/PKG-INFO
writing dependency_links to nms_cuda.egg-info/dependency_links.txt
writing top-level names to nms_cuda.egg-info/top_level.txt
reading manifest file 'nms_cuda.egg-info/SOURCES.txt'
writing manifest file 'nms_cuda.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_ext
building 'nms_cuda' extension
creating /home/mahmood/fcos/libs/nms_cuda/build/temp.linux-x86_64-3.6
Emitting ninja build file /home/mahmood/fcos/libs/nms_cuda/build/temp.linux-x86_64-3.6/build.ninja...
Compiling objects...
Allowing ninja to set a default number of workers... (overridable by setting the environment variable MAX_JOBS=N)
[1/2] /usr/local/cuda-11.2/bin/nvcc --generate-dependencies-with-compile --dependency-output /home/mahmood/fcos/libs/nms_cuda/build/temp.linux-x86_64-3.6/nms_kernel.o.d -I/home/mahmood/.local/lib/python3.6/site-packages/torch/include -I/home/mahmood/.local/lib/python3.6/site-packages/torch/include/torch/csrc/api/include -I/home/mahmood/.local/lib/python3.6/site-packages/torch/include/TH -I/home/mahmood/.local/lib/python3.6/site-packages/torch/include/THC -I/usr/local/cuda-11.2/include -I/home/mahmood/anaconda3/envs/cu10/include/python3.6m -c -c /home/mahmood/fcos/libs/nms_cuda/nms_kernel.cu -o /home/mahmood/fcos/libs/nms_cuda/build/temp.linux-x86_64-3.6/nms_kernel.o -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr --compiler-options ''"'"'-fPIC'"'"'' -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1011"' -DTORCH_EXTENSION_NAME=nms_cuda -D_GLIBCXX_USE_CXX11_ABI=0 -gencode=arch=compute_61,code=compute_61 -gencode=arch=compute_61,code=sm_61 -std=c++14
/home/mahmood/fcos/libs/nms_cuda/nms_kernel.cu: In function ‘at::Tensor nms_cuda(at::Tensor, float)’:
/home/mahmood/fcos/libs/nms_cuda/nms_kernel.cu:72:62: warning: ‘at::DeprecatedTypeProperties& at::Tensor::type() const’ is deprecated: Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a drop-in replacement. If you were using data from type(), that is now available from Tensor itself, so instead of tensor.type().scalar_type(), use tensor.scalar_type() instead and instead of tensor.type().backend() use tensor.device(). [-Wdeprecated-declarations]
AT_ASSERTM(boxes.type().is_cuda(), "boxes must be a CUDA tensor");
^
/home/mahmood/.local/lib/python3.6/site-packages/torch/include/ATen/core/TensorBody.h:303:1: note: declared here
DeprecatedTypeProperties & type() const {
^ ~~
/home/mahmood/fcos/libs/nms_cuda/nms_kernel.cu:81:50: warning: ‘T* at::Tensor::data() const [with T = float]’ is deprecated: Tensor.data() is deprecated. Please use Tensor.data_ptr() instead. [-Wdeprecated-declarations]
scalar_t* boxes_dev = boxes_sorted.data<scalar_t>();
^
/home/mahmood/.local/lib/python3.6/site-packages/torch/include/ATen/core/TensorBody.h:398:1: note: declared here
T * data() const {
^ ~~
/home/mahmood/fcos/libs/nms_cuda/nms_kernel.cu:109:46: warning: ‘T* at::Tensor::data() const [with T = long int]’ is deprecated: Tensor.data() is deprecated. Please use Tensor.data_ptr() instead. [-Wdeprecated-declarations]
int64_t* keep_out = keep.data<int64_t>();
^
/home/mahmood/.local/lib/python3.6/site-packages/torch/include/ATen/core/TensorBody.h:398:1: note: declared here
T * data() const {
^ ~~
[2/2] c++ -MMD -MF /home/mahmood/fcos/libs/nms_cuda/build/temp.linux-x86_64-3.6/nms_cuda.o.d -pthread -B /home/mahmood/anaconda3/envs/cu10/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/home/mahmood/.local/lib/python3.6/site-packages/torch/include -I/home/mahmood/.local/lib/python3.6/site-packages/torch/include/torch/csrc/api/include -I/home/mahmood/.local/lib/python3.6/site-packages/torch/include/TH -I/home/mahmood/.local/lib/python3.6/site-packages/torch/include/THC -I/usr/local/cuda-11.2/include -I/home/mahmood/anaconda3/envs/cu10/include/python3.6m -c -c /home/mahmood/fcos/libs/nms_cuda/nms_cuda.cpp -o /home/mahmood/fcos/libs/nms_cuda/build/temp.linux-x86_64-3.6/nms_cuda.o -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1011"' -DTORCH_EXTENSION_NAME=nms_cuda -D_GLIBCXX_USE_CXX11_ABI=0 -std=c++14
FAILED: /home/mahmood/fcos/libs/nms_cuda/build/temp.linux-x86_64-3.6/nms_cuda.o
c++ -MMD -MF /home/mahmood/fcos/libs/nms_cuda/build/temp.linux-x86_64-3.6/nms_cuda.o.d -pthread -B /home/mahmood/anaconda3/envs/cu10/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/home/mahmood/.local/lib/python3.6/site-packages/torch/include -I/home/mahmood/.local/lib/python3.6/site-packages/torch/include/torch/csrc/api/include -I/home/mahmood/.local/lib/python3.6/site-packages/torch/include/TH -I/home/mahmood/.local/lib/python3.6/site-packages/torch/include/THC -I/usr/local/cuda-11.2/include -I/home/mahmood/anaconda3/envs/cu10/include/python3.6m -c -c /home/mahmood/fcos/libs/nms_cuda/nms_cuda.cpp -o /home/mahmood/fcos/libs/nms_cuda/build/temp.linux-x86_64-3.6/nms_cuda.o -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1011"' -DTORCH_EXTENSION_NAME=nms_cuda -D_GLIBCXX_USE_CXX11_ABI=0 -std=c++14
cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++
In file included from /home/mahmood/.local/lib/python3.6/site-packages/torch/include/ATen/Parallel.h:140:0,
from /home/mahmood/.local/lib/python3.6/site-packages/torch/include/torch/csrc/api/include/torch/utils.h:3,
from /home/mahmood/.local/lib/python3.6/site-packages/torch/include/torch/csrc/api/include/torch/nn/cloneable.h:5,
from /home/mahmood/.local/lib/python3.6/site-packages/torch/include/torch/csrc/api/include/torch/nn.h:3,
from /home/mahmood/.local/lib/python3.6/site-packages/torch/include/torch/csrc/api/include/torch/all.h:13,
from /home/mahmood/.local/lib/python3.6/site-packages/torch/include/torch/extension.h:4,
from /home/mahmood/fcos/libs/nms_cuda/nms_cuda.cpp:2:
/home/mahmood/.local/lib/python3.6/site-packages/torch/include/ATen/ParallelOpenMP.h:83:0: warning: ignoring #pragma omp parallel [-Wunknown-pragmas]
#pragma omp parallel for if ((end - begin) >= grain_size)
/home/mahmood/fcos/libs/nms_cuda/nms_cuda.cpp: In function ‘at::Tensor nms(const at::Tensor&, float)’:
/home/mahmood/fcos/libs/nms_cuda/nms_cuda.cpp:4:39: warning: ‘at::DeprecatedTypeProperties& at::Tensor::type() const’ is deprecated: Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a drop-in replacement. If you were using data from type(), that is now available from Tensor itself, so instead of tensor.type().scalar_type(), use tensor.scalar_type() instead and instead of tensor.type().backend() use tensor.device(). [-Wdeprecated-declarations]
#define CHECK_CUDA(x) AT_CHECK(x.type().is_cuda(), #x, " must be a CUDAtensor ")
^
/home/mahmood/fcos/libs/nms_cuda/nms_cuda.cpp:9:3: note: in expansion of macro ‘CHECK_CUDA’
CHECK_CUDA(dets);
^~~~~~~~~~
In file included from /home/mahmood/.local/lib/python3.6/site-packages/torch/include/ATen/Tensor.h:3:0,
from /home/mahmood/.local/lib/python3.6/site-packages/torch/include/ATen/Context.h:4,
from /home/mahmood/.local/lib/python3.6/site-packages/torch/include/ATen/ATen.h:9,
from /home/mahmood/.local/lib/python3.6/site-packages/torch/include/torch/csrc/api/include/torch/types.h:3,
from /home/mahmood/.local/lib/python3.6/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader_options.h:4,
from /home/mahmood/.local/lib/python3.6/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader/base.h:3,
from /home/mahmood/.local/lib/python3.6/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader/stateful.h:3,
from /home/mahmood/.local/lib/python3.6/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader.h:3,
from /home/mahmood/.local/lib/python3.6/site-packages/torch/include/torch/csrc/api/include/torch/data.h:3,
from /home/mahmood/.local/lib/python3.6/site-packages/torch/include/torch/csrc/api/include/torch/all.h:8,
from /home/mahmood/.local/lib/python3.6/site-packages/torch/include/torch/extension.h:4,
from /home/mahmood/fcos/libs/nms_cuda/nms_cuda.cpp:2:
/home/mahmood/.local/lib/python3.6/site-packages/torch/include/ATen/core/TensorBody.h:303:30: note: declared here
DeprecatedTypeProperties & type() const {
^~~~
/home/mahmood/fcos/libs/nms_cuda/nms_cuda.cpp:4:23: error: ‘AT_CHECK’ was not declared in this scope
#define CHECK_CUDA(x) AT_CHECK(x.type().is_cuda(), #x, " must be a CUDAtensor ")
^
/home/mahmood/fcos/libs/nms_cuda/nms_cuda.cpp:9:3: note: in expansion of macro ‘CHECK_CUDA’
CHECK_CUDA(dets);
^~~~~~~~~~
/home/mahmood/fcos/libs/nms_cuda/nms_cuda.cpp:4:23: note: suggested alternative: ‘DCHECK’
#define CHECK_CUDA(x) AT_CHECK(x.type().is_cuda(), #x, " must be a CUDAtensor ")
^
/home/mahmood/fcos/libs/nms_cuda/nms_cuda.cpp:9:3: note: in expansion of macro ‘CHECK_CUDA’
CHECK_CUDA(dets);
^~~~~~~~~~
ninja: build stopped: subcommand failed.
Traceback (most recent call last):
File "/home/mahmood/.local/lib/python3.6/site-packages/torch/utils/cpp_extension.py", line 1673, in _run_ninja_build
env=env)
File "/home/mahmood/anaconda3/envs/cu10/lib/python3.6/subprocess.py", line 438, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['ninja', '-v']' returned non-zero exit status 1.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "setup.py", line 15, in
'build_ext': BuildExtension
File "/home/mahmood/anaconda3/envs/cu10/lib/python3.6/site-packages/setuptools/init.py", line 153, in setup
return distutils.core.setup(**attrs)
File "/home/mahmood/anaconda3/envs/cu10/lib/python3.6/distutils/core.py", line 148, in setup
dist.run_commands()
File "/home/mahmood/anaconda3/envs/cu10/lib/python3.6/distutils/dist.py", line 955, in run_commands
self.run_command(cmd)
File "/home/mahmood/anaconda3/envs/cu10/lib/python3.6/distutils/dist.py", line 974, in run_command
cmd_obj.run()
File "/home/mahmood/anaconda3/envs/cu10/lib/python3.6/site-packages/setuptools/command/install.py", line 67, in run
self.do_egg_install()
File "/home/mahmood/anaconda3/envs/cu10/lib/python3.6/site-packages/setuptools/command/install.py", line 109, in do_egg_install
self.run_command('bdist_egg')
File "/home/mahmood/anaconda3/envs/cu10/lib/python3.6/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/home/mahmood/anaconda3/envs/cu10/lib/python3.6/distutils/dist.py", line 974, in run_command
cmd_obj.run()
File "/home/mahmood/anaconda3/envs/cu10/lib/python3.6/site-packages/setuptools/command/bdist_egg.py", line 164, in run
cmd = self.call_command('install_lib', warn_dir=0)
File "/home/mahmood/anaconda3/envs/cu10/lib/python3.6/site-packages/setuptools/command/bdist_egg.py", line 150, in call_command
self.run_command(cmdname)
File "/home/mahmood/anaconda3/envs/cu10/lib/python3.6/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/home/mahmood/anaconda3/envs/cu10/lib/python3.6/distutils/dist.py", line 974, in run_command
cmd_obj.run()
File "/home/mahmood/anaconda3/envs/cu10/lib/python3.6/site-packages/setuptools/command/install_lib.py", line 11, in run
self.build()
File "/home/mahmood/anaconda3/envs/cu10/lib/python3.6/distutils/command/install_lib.py", line 107, in build
self.run_command('build_ext')
File "/home/mahmood/anaconda3/envs/cu10/lib/python3.6/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/home/mahmood/anaconda3/envs/cu10/lib/python3.6/distutils/dist.py", line 974, in run_command
cmd_obj.run()
File "/home/mahmood/anaconda3/envs/cu10/lib/python3.6/site-packages/setuptools/command/build_ext.py", line 79, in run
_build_ext.run(self)
File "/home/mahmood/anaconda3/envs/cu10/lib/python3.6/distutils/command/build_ext.py", line 339, in run
self.build_extensions()
File "/home/mahmood/.local/lib/python3.6/site-packages/torch/utils/cpp_extension.py", line 708, in build_extensions
build_ext.build_extensions(self)
File "/home/mahmood/anaconda3/envs/cu10/lib/python3.6/distutils/command/build_ext.py", line 448, in build_extensions
self._build_extensions_serial()
File "/home/mahmood/anaconda3/envs/cu10/lib/python3.6/distutils/command/build_ext.py", line 473, in _build_extensions_serial
self.build_extension(ext)
File "/home/mahmood/anaconda3/envs/cu10/lib/python3.6/site-packages/setuptools/command/build_ext.py", line 196, in build_extension
_build_ext.build_extension(self, ext)
File "/home/mahmood/anaconda3/envs/cu10/lib/python3.6/distutils/command/build_ext.py", line 533, in build_extension
depends=ext.depends)
File "/home/mahmood/.local/lib/python3.6/site-packages/torch/utils/cpp_extension.py", line 538, in unix_wrap_ninja_compile
with_cuda=with_cuda)
File "/home/mahmood/.local/lib/python3.6/site-packages/torch/utils/cpp_extension.py", line 1359, in _write_ninja_file_and_compile_objects
error_prefix='Error compiling objects for extension')
File "/home/mahmood/.local/lib/python3.6/site-packages/torch/utils/cpp_extension.py", line 1683, in _run_ninja_build
raise RuntimeError(message) from e
RuntimeError: Error compiling objects for extension
`


feat: Add documentation for krt v2

Why
As development for krt v2 is coming to an end, we need documentation that explains and depicts new changes and features.
What

Fixed some lint markers
Added documentation for krt V2
Separated user functionality for runners old V2 and new V3

Great job @alexrodfe!
I will leave here another pair of things to update on the documentation:
On the versions documentation under Home/Kai Servier/User Documentation/Versions:

The image on the top of the page showing an example of the workflows should be updated to one showing the new charts with multi-branching.

The image on the Node section showing the methods to be overwritten by each node should be updated, the new runners have different methods.

Behind the above Node section, the Workflow section contains some references to the old versions. For example, it references sequential field on the Workflow configuration.

On the KRT (V1) documentation there is a Version 3 section which is confusing to me, as this same documentation is also included on the KAI Server Runner SDK documentation for each version, so I would probably remove the mentions to the handler methods on the KRT (V1) documentation and reference the KAI Server Runner SDK instead.
We are doing a reference to the KAI-Server-Training repository on the documentation, but that repository is archived, we should update the documentation to reference the active sample project (demo-email-classificator)
And one last question, why are the features of each KRT version on a separate Features page, and not as another section under the KAI Server Runner SDK page?


Update README.md - fixed broken links.

The links on the README are broken. I have created an issue for reference.

+1 to this PR as I was trying to get started and hit some 404s trying to navigate to the docs and tutorials.

Thanks for the pull request @akon-dey


Connection Pooling

Does the CqlDatabaseConnector support connection pooling and transient recovery or should I create a new connection and open it for each database request?
Currently each of my db calls is wrapped with a new connection being OpenAsync-ed.
@pabloordonez @lbrugnara @bgrainger

I've done and it seems like the Cassandra Connector reconnects automatically without having to explicitly call OpenAsync

@turowicz I made an update a couple of weeks ago, because there was an issue with the ADO.NET implementation of the datastax connector we use internally. Basically, Datastax requries to have one global connection for the same cluster/session pair. You can have multiple connections if you want to connect to a different cluster, but should reuse the same for the same cluster.
Their ADO.NET implementation wraps the cluster session pair with a DbConnection. If you are using the connection for a web scenario, you're probably opening and closing and disposing the connection expecting the inner connector to handle the pool, but that was not what was happening with the driver.
So I took a different approach and added a static cache for cassandra connections. Diposing the connections won't actually dispose the connection. If you want to dispose the connection you'll need to target CqlConnectionManager.ClearConnections().
Disposing connections frequently seemed to also produce a leak inside datastax driver. A lot of pool objects ended up in gen2 and never freed and the application was taking more and more memory.
So far we're seeing much better times and memory management running against a Scylla cluster. Sorry for the delay on this.


Jasper mpdclient improvements and UTF-8 fix

password protected mpd connection now possible
improved keyword recognition in mpdcontrol by using all keywords found by the stt engine, instead of only the one with highest confidence. "SCHLIESSEN" for example could never be found, as the first hit is always u'SCHLIE\xdfEN'.
improved recognition for playlist names

unicode fix:

no errors any more when non-ascii characters as in 'LAUTSTÄRKE' or 'NÄCHSTES LIED' are encountered thanks to utf-8 decoding in i18n.py

Coverage remained the same at 50.35% when pulling 6e92a9d0638df66dcae4d79451f81a1a56d531ae on KrawallKurt:jasper-mpd-improvements into f26ee30ae80f6e4e9c73be551af39bbd31d9b562 on jasperproject:jasper-dev.

Coverage remained the same at 50.35% when pulling 466aa77e10259bb087c5d6d96cad3e501be5bc43 on KrawallKurt:jasper-mpd-improvements into f26ee30ae80f6e4e9c73be551af39bbd31d9b562 on jasperproject:jasper-dev.

Thanks for your contribution! Merged.


Adding IOO

Added variables list, logic and notebook example for IOO data ( https://erddap-uncabled.oceanobservatories.org/uncabled/erddap)
This ticks one more off the list

Thanks for the suggestions @ocefpaf. Hopefully the two extra commits address these adequately. My commits are still failing the github checks, but I can't figure out the errors :/

Thanks for the suggestions @ocefpaf. Hopefully the two extra commits address these adequately. My commits are still failing the github checks, but I can't figure out the errors :/

The GitHub Actions is outdated. I'll fix it in a moment. Travis-CI is missing matplotlib, which should be an optional dependency. Looking into it...

One day I will remember to run the pre-commit before pushing. It was not this day.

One day I will remember to run the pre-commit before pushing. It was not this day.

conda create --name GLIDERPY python=3.9 --file requirements.txt --file requirements-dev.txt --yes
pre-commit install

Then it will "remind" you every time you try to commit ;-p


Provide a way to download the agent and document that in getting started

Options:

https://unpkg.com/elastic-apm-js-base
Adding dist folder to the github repo
Releases feature in github

We should look into github release page and emphasise downloading from there.


New PAGINATION_DEFAULT_LIMIT pagination setting isn't used

Describe the Bug
The recent release that included PR #642 introduced a new setting, PAGINATION_DEFAULT_LIMIT, which is mentioned in the settings and pagination documentation sections.
However, upon reviewing the PR and the codebase, it appears that PAGINATION_DEFAULT_LIMIT is not actually currently referenced or used anywhere! This suggests that the setting is currently non-functional and does not affect pagination behavior.
Suggested Approach
We should either remove the PAGINATION_DEFAULT_LIMIT setting and its documentation, or implement its expected behaviour. Once the issue with is addressed, it would also be helpful to update the documentation to clarify that Relay pagination limits are controlled separately by the relay_max_results setting from the upstream strawberry package (if still applicable). This setting is documented in the Relay configuration guide.
System Information

Operating system: MacOS
Strawberry version (if applicable): 0.248.1

Upvote & Fund

We're using Polar.sh so you can upvote and help fund this issue.
We receive the funding once the issue is completed & confirmed by you.
Thank you in advance for helping prioritize & fund our backlog.

OMG such an oversight on my end 🤦
Thanks for the report, I'm going to fix this


Enroll and validate the user certificate - not working

GPResult shows the GPO is effective, but no certificate is generated.  I have also tried "All Tasks" -> "Request New Certificate" -> "Next" -> "Next" and the template is not listed.  I check the "Show all templates", scroll down to "VPN User Authentication"  and see the template status is "Unavailable".  The details states "The requested certificate template is not supported by this CA.  A valid certification authority (CA) configured to issue certificates based on this template cannot be located, or the CA does not support this operation, or the CA is not trusted."
The one and only server on this network is a Windows Server 2016 DC, which should be a valid and trusted CA.  The workstation I am attempting this from is a domain-joined Windows 10 PC and I am logged-in as a domain user who is a member of the VPN Users group.  What am I missing?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0e886cf2-b2cc-1942-2e93-b83ba3f5c81a
Version Independent ID: 14185f76-c920-66a5-9d3b-51ddc4845ee8
Content: Configure the Server Infrastructure
Content Source: WindowsServerDocs/remote/remote-access/vpn/always-on-vpn/deploy/vpn-deploy-server-infrastructure.md
Product: windows-server-threshold
GitHub Login: @shortpatti
Microsoft Alias: pashort

I resolved #1422:
I had to do the "Certificate Template for Issue" step again - for whatever reason.  It's possible that I missed that step to start with.


V11

This PR will update all packages to support angular and NX version 11. I think in our previous v11 upgrade we've used ng update. With NX we should use nx migrate and run the migrations for the changes. This is the way we should upgrade our applications, by using ng update we will break the monorepo setup.  At least we could break it in the future.

I'm facing some issues will update this in the upcoming days.


⚠ ClamAV has degraded performance

In 39ef964, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 438 ms

Resolved: ClamAV performance has improved in da90c67.


Nav hover and browse all category position

Describe the bug
Remove the hover effect of navbar and fix the position of browse all category

@MAVRICK-1 can you please assign this to me


EV3-G API: Gyro sensor

Need to get screenshots of the gyro sensor blocks

Implementation note on Reset block:
This block puts the sensor into GYRO-ANGLE mode, plus sends a command to the sensor (I'll have to look it up later). Sending the command would have to be done with the direct attribute in ev3dev.

Newer versions of these sensors also have an additional second axis accessible via the TILT-ANGLE and TILT-RATE modes that is not usable using the official EV3-G blocks.
https://www.youtube.com/watch?v=KjlT0BUJr-w


Can't locate Config/Properties.pm in @INC

i've tried to run this files in perl getting below error.
"Can't locate Config/Properties.pm in @INC (you may need to install the Config::Properties module) (@INC contains: C:/Perl64/site/lib C:/Perl64/lib) at generate-activity-gadget-xml.pl line 8.
BEGIN failed--compilation aborted at generate-activity-gadget-xml.pl line 8."

In the install page (https://github.com/zenoss/testrail-jira-gadgets/blob/master/INSTALL.md) there is a list of Perl modules that must be installed for those scripts to work. They are:

Config::Properties
MIME::Base64
JSON
REST::Client
HTML::Parser


[AKS] update mgmt-containerservice to 9.4.0 and enable 09-01 API

Description

Update to the latest SDK and switch to using September API.
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

@arrownj please help review this PR.


Graphs is not active

I get this error in the log.
2020-05-19 10:10:01:036+0100 [temperature-rrd-writing-thread-1] ERROR Unable to write temperature for 'raspberrypi' to RRD: host not setup as an archive

Also seeing this, started around the same time.
2020-05-31 22:56:18:536-0300 [temperature-rrd-writing-thread-1] ERROR Unable to write temperature for 'Templogpi' to RRD: host not setup as an archive

I am also experiencing this error.
Temperatures are not stored and graphs are not displayed.
2020-08-13 09:32:43:262+0100 [temperature-rrd-writing-thread-1] ERROR Unable to write temperature for 'raspberrypi' to RRD: host not setup as an archive
Is it possible to provide a solution?

Same problem here. This is what I see after few hours

Ok, seems that I found solution. I deleted ~/.temperature/temperature.rrd (this will remove all history). After that I restarted service. Now I see some movement.

Day two: