Update model with relation

Hi,
I,m updating model with hasMany relation.
mysql query update relation example (id is AIPK)
DELETE FROM bibliography WHERE (item_id=13)  AND (id<>NULL)
INSERT INTO bibliography (name, item_id, lock, created_at, updated_at, created_by, updated_by) VALUES ('anywhat', 13, 0, NOW(), NOW(), 1, 1)
But operator delete don't work correctly
explain DELETE FROM bibliography WHERE (item_id=13) AND (id<>NULL)
"id"	"select_type"	"table"	"type"	"possible_keys"	"key"	"key_len"	"ref"	"rows"	"Extra"
"1"	"SIMPLE"           \N	         \N	           \N	                         \N	         \N	         \N	  \N	          "Impossible WHERE"
row don't delete and insert duplicate entry with new PK
How to fix it?
Tnx

@VnukA take a look at
https://github.com/mootensai/yii2-enhanced-gii/issues/138


typings issues in angular-cli 1.0.0-beta.11-webpack.2

1. OS?  Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
El Capitan 10.11.6
2. Versions. Please run ng --version. If there's nothing outputted, please run
in a Terminal: node --version and paste the result here:
(node:69005) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
angular-cli: 1.0.0-beta.11-webpack.2
node: 6.3.1
os: darwin x64

3. Repro steps. Was this an app that wasn't created using the CLI? What change did you
do on your code? etc.
It is a whole new project, just did
npm install -g angular-cli@webpack
ng new my-project
npm install --save-dev angular-cli@webpack

4. The log given by the failure. Normally this include a stack trace and some
more information.
The app runs well, but seems having some typings issues (red parts, my IDE is WebStorm 2016.2.2). And seems only happening with RC5 new things:
app.module.ts

main.ts

Looks like an ide glitch. I use idea (same as WS) and types work fine. Did you try reimporting your project. Look like it did not index the RC5 dependencies

Thanks, @mmrath.
This morning I got an update from WebStorm.
After updating from 162.1628.21 to 162.1628.41. The issue seems gone!

I have the same issue when i installed<EMAIL_ADDRESS>my output of ng--version:
ng --version
(node:4132) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
angular-cli: 1.0.0-beta.11-webpack.2
node: 6.2.1
os: darwin x64

my output of of ng new emptyApp:
ng new emptyApp
(node:4087) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
installing ng2
create .editorconfig
create README.md
create src/app/app.component.css
....
this is the output of my global npm packages installed:
npm list -g -depth=0
/usr/local/lib
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>npm ERR! peer dep missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! peer dep missing<EMAIL_ADDRESS>|| ^1.9.0-dev, required by<EMAIL_ADDRESS>

@stefanaerts I don't see how what you posted is related to this issue. Please open a new issue if you're experiencing problems

???  The issue is that the deploy does not work
Op 23 aug. 2016 17:12 schreef "Filipe Silva"<EMAIL_ADDRESS>
@stefanaerts https://github.com/stefanaerts I don't see how what you
posted is related to this issue. Please open a new issue if you're
experiencing problems
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/angular/angular-cli/issues/1745#issuecomment-241764334,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADg49_jZHBBGLpcAqTX-NyNUYQK39s-vks5qiw3SgaJpZM4Jnxum
.

@stefanaerts there is nothing about deploy in your comment on this issue. I have to reiterate: please open a new issue if you are still having problems, this issue is already closed with a resolution.

Sry, i dont know how i got on this tread. But the issue was indeed closed and "they say with a solution" but the solution didnt work.


Change Go logging library

Ref: https://github.com/equinor/radix-platform/issues/1048

closed since this is user facing and we dont want structured logging here(or colored output)


tweak top level invoker flow for error handling

Several bug fixes and some code refactoring - organized as 3 independent commits.

remove unnecessary vars and simplify types
when activation fails (for docker actions in particular), set annotations correctly (previous was null)
reorganize invoke action flow to avoid unintended recovery attempts.
added some tests to checks proper annotations on failed docker actions
while at it, added duration for activations

pg2/526 approved.

Some changes with respect to timing and # of Futures in flight but LGTM.

Got some conflicts.  Can you resolve the rebase?

merged


Watches pane - "Rename expression" -> "Edit expression"

'Rename' doesn't feel right here. I was going to make the change but don't know whether the localize ID, action name, and everything else should change to be consistent.

+1 for the change.
Yeah everything should change except the ID if it is exposed in the keybindings.json. I believe this one is not so feel free to change everything.
Good old full text search should do the trick here :)


AdGuard Home memory issue

Originally posted by trinib May 21, 2022
AdGuard Home has a memory issue at the moment. So when using the url python script with block list that have 100k+ URLs it can cause a memory lockup. So I advise for now use script with limited blocklist at a time and reboot everytime adding a set. 😔
Edited
Even after reboot memory does not get freed. So until AGH gets this fixed use limited blockist

I’ve just suffered this issue on a Pi 3B, I would suggest you remove or add a warning to the Black Mirror blocklist about this problem.

I’ve just suffered this issue on a Pi 3B, I would suggest you remove or add a warning to the Black Mirror blocklist about this problem.

@jaytay79 It is not the fault of urls in blocklist.. It's AdGuard!
I really hope they fix that issue asap.. pi hole had a memory leak issue as well in the past for a couple of versions until it was fixed
AGH is its early stages of development, so bare with them for now 🙏


503 Error

Hello, thanks again for maintaining this! Wanted to let you know that the hosted API is returning 503s for all requests.

Closing as the issue has resolved itself. :tada:

Reopening b/c it looks like the error is back.

Yep can cofirm

Looks all good again, I'll go check out the Azure logs.


Added Right-To-Left text direction support.

When the HTML attribute dir="rtl" is set on the page, the input value does not get aligned properly with the knob.  Use jquery.knob({ rtl: true }) to adjust the alignment appropriately.
Fixes #205

Hi,
the problem with RTL language exists yet. I tried the following but the value shows outside1
$(".dial").knob({
width : 300,
fgColor: "red",
font: "iranyekan",
rtl: true
});
Any Idea?


cdc/codec: fix string for unsigned value in canal-json.

What problem does this PR solve?

Issue Number: close #4635
What is changed and how it works?
handle the case when unsigned in string
Check List
Tests

No code

Code changes
Side effects
Related changes

Need to cherry-pick to the release branch

Release note
fix `Canal-JSON` meet `unsigned` SQL typed in `string`, which cause CDC server panic.

Codecov Report

Merging #4629 (21a8e42) into master (9607554) will increase coverage by 0.0124%.
The diff coverage is 57.3092%.

Flag
Coverage Δ

cdc
60.1600% <54.2105%> (+0.2378%)
:arrow_up:

dm
51.8582% <58.8491%> (-0.1707%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
@@               Coverage Diff                @@
##             master      #4629        +/-   ##
================================================
+ Coverage   55.6402%   55.6527%   +0.0124%
================================================
  Files           494        507        +13
  Lines         61283      63138      +1855
================================================
+ Hits          34098      35138      +1040
- Misses        23750      24497       +747
- Partials       3435       3503        +68

/run-all-tests

/merge

/run-integration-test /tidb=pr/32434
/run-leak-test /tidb=pr/32434


Pull Makefile-initiated linting checks or move to a monthly schedule

The recent bug with the v2.17.0 release of the gosec linter (bundled with golangci-lint v1.54.2) triggered false-positive linting failures across several projects using the workflows from this repo.
The go-ci based containers were updated to rollback golangci-lint to v1.54.1 which resolved the container based linting false-positives.
The linting jobs using project Makefiles however continue to fail. This is because of two reasons:

The project Makefiles install the latest stable release of golangci-lint
The upstream project does not appear to (quickly?) rollback bundled linters when a confirmed problem exists

the project appears to primarily wait on their upstream sources to resolve the problem before generating a new release

I originally intended for the Makefiles to serve two purposes:

allow me to easily orchestrate common development tasks (linting, building)
allow others to (somewhat easily) generate builds

I still use project Makefiles to generate assets (mostly using containers now), but no longer use Makefiles for local linting tasks.
As noted in the GH issue title, it's probably worth first dropping the Makefile linting checks as regular CI jobs. To begin with I'd add them the monthly scheduled tasks, but might end up dropping them entirely, leaving them in the Makefile but generally disused.

Looking over the current setup the easiest path forward is to mark the job as optional just like the Makefile / Build codebase using Makefile all recipe has been marked. That job is then explicitly enabled for the monthly scheduled workflow.

Consider removing CI Makefile-initiated linting tasks

I'm thinking that by keeping this limited to a monthly schedule it remains useful as a proof against Makefiles "degrading" and no longer properly running the linting tasks.

might be worth dropping project-specific linting configuration?

This is worth considering. Since we're using the go-ci project images which bundle a standardized golangci-lint config file we don't necessarily need project-specific config files unless those config files apply stricter linting standards than the standardized linter config.
Said another way, if we remove the linter config file from each project we should probably also remove the Makefile-initiated linting tasks from CI (currently a monthly schedule).
For now, it's probably worth leaving everything as it is until I think on this further.


Vector Drawable as Menu icon

It doesn't show vector drawable as menu icon on API 19 with below err:
   Caused by: org.xmlpull.v1.XmlPullParserException: Binary XML file line #1: invalid drawable tag vector
                                                                        at android.graphics.drawable.Drawable.createFromXmlInner(Drawable.java:933)
                                                                        at android.graphics.drawable.Drawable.createFromXml(Drawable.java:877)

Hi, @pooyanmajd! Currently this lib doesn't support vector-drawables. Can you use just ordinary drawable?

Hi @warko-san, I fixed the issue by adding this support for vector-drawable
AppCompatDelegate.setCompatVectorFromResourcesEnabled(true);


Add 'Save as new' on filters

I'm submitting a feature request
Brief Description
Currently if the user loads, then modifies a saved filter and finally save it, the filter will be overwritten. I listened from a user that it would be very useful to have the possibility to Save as New.
What  is the current behaviour, (attach relevant screenshots) ?
The user can apply and then save to generate a new filter, but it should have a way to directly Save as new.

Will this be happening any time soon?


Hi, some questions about the model!

Hi, Thanks for this nice work. Recently, I am trying to modify this excellent model to make it suit for my work. As you see, why the "average" operation is required here, the shape of the tensor changes from 6464 to 88 after the "average" operation.  However, the shape of the tensor should be the 64*64 just like the description" fusion at (B,64,64,64)".

The fusion can also be done at 64x64 resolution but that would be too computationally expensive since a transformer is used (quadratic complexity due to attention), so reduce the size to 8x8 at each resolution of the intermediate feature maps.

Thanks for your quick reply. I guess that the input feature map of the transformer of each layer will be downsampled to 8*8 according to what you mean?

that's correct, now there are several variants of transformer which address the quadratic complexity issue of the transformer (eg. Linformer) so maybe it's possible to use the transformer without downsampling.

that's correct, now there are several variants of transformer which address the quadratic complexity issue of the transformer (eg. Linformer) so maybe it's possible to use the transformer without downsampling.

Ok, Another interesting question is that can this fusion fashion based on the transformer be replaced with other transformers, such as swim or PVT. Because I notice that this transformer is developed based on the GPT suited for the NLP area.

I agree, architecture design can be improved quite a bit.

Ok, Nice work, Thanks for your reply.

But it may require more resources to train...

I agree, architecture design can be improved quite a bit.


Multi @init execution order

As shown in my snippet below, I have several @init for each type of build (dev, external..) and one for common initialization (classifiers, requirements,..). I would like the common initializer to be executed first, before the specific environment initializer but it is always the last one. I tried using @depends and @after on the environment specific initializers but it does not work (@depends and @after seems to only work for tasks).
Is there a way to specify the execution order of initializers?
@init
def common(project):
    # Common initialization
    pass

@init(environments="dev")
def init_dev(project):
    # dev build initialization
    pass

@init(environments="external")
def init_ext(project):
    # external release build initialization
    pass

Alternatively, is there a way to execute an initializer only if no environment is specified

Hi, @MarvBob.
As I know initializers are sortered by name (result of calling Python dir() method). For example:
[DEBUG] Registering initializer 'add_resources'
[DEBUG] Registering initializer 'common'
[DEBUG] Registering initializer 'filter_config'
[DEBUG] Registering initializer 'init_dev'
[DEBUG] Registering initializer 'init_ext'
[DEBUG] Registering initializer 'set_properties'

In this case if we change name for common to post_common_init we will get:
[DEBUG] Registering initializer 'add_resources'
[DEBUG] Registering initializer 'filter_config'
[DEBUG] Registering initializer 'init_dev'
[DEBUG] Registering initializer 'init_ext'
[DEBUG] Registering initializer 'post_common_init'
[DEBUG] Registering initializer 'set_properties'

And for execution:
[DEBUG] Executing initializer 'add_resources' from 'build'
[DEBUG] Executing initializer 'filter_config' from 'build'
[DEBUG] Not going to execute initializer 'init_dev' from 'build' as environments do not match.
[DEBUG] Not going to execute initializer 'init_ext' from 'build' as environments do not match.
[DEBUG] Executing initializer 'post_common_init' from 'build'

Ok thanks !
I think this issue can be closed then?
It should be a good thing to add this to the documentation.

Yes, could be closed. I created ticket for documentation.
Thanks.


Unable to make AtomVM

I am very new to AtomVM and must be doing something incorrectly.  I am trying to build AtomVM on a Linux machine and am following the Getting Started guide.  I can successfully use cmake to build the various makefiles in the different subdirectories, but when I run the make command, it works for a while and then generates this error:
[  6%] Linking C executable ../../AtomVM
lib/liblibAtomVMLinux-i686.a(platform_nifs.c.o): In function nif_crypto_hash': /home/bruce/Projects/AtomVM/src/platforms/generic_unix/lib/platform_nifs.c:133: undefined reference to EVP_MD_CTX_new'
/home/bruce/Projects/AtomVM/src/platforms/generic_unix/lib/platform_nifs.c:141: undefined reference to EVP_MD_CTX_free' /home/bruce/Projects/AtomVM/src/platforms/generic_unix/lib/platform_nifs.c:155: undefined reference to EVP_MD_CTX_free'
/home/bruce/Projects/AtomVM/src/platforms/generic_unix/lib/platform_nifs.c:159: undefined reference to `EVP_MD_CTX_free'
collect2: error: ld returned 1 exit status
src/platforms/generic_unix/CMakeFiles/AtomVM.dir/build.make:89: recipe for target 'src/AtomVM' failed
If anyone has any advice it would be greatly appreciated.

You need to point cmake to OpenSSL3 headers and libraries on your platform.
E.g.,
cmake -DOPENSSL_ROOT_DIR=/usr/local/opt/openssl -DOPENSSL_LIBRARIES=/usr/local/opt/openssl/lib ...`

We will need to make this more clear in the build instructions.  I think we also need to conditionally compile the offending code you hit, so I will file a ticket on that, as well.
Just out of curiosity, why are you trying to build AtomVM?

Thanks for the suggestion.
I was under the impression that I needed to build AtomVM in order to get an executable version of the PackBEAM application.  Here is what I have done so far.

Downloaded the ESP32 release image of AtomVM and flashed it to the chip.
Started following the steps listed in the AtomVM Development guide.
Wrote a hello_world.erl Erlang program
Need to use the PackBEAM app to package the compiled Erlang program

I see a packbeam.c file in the AtomVM/tools/packbeam folder and assumed that I needed to compile it somehow.
Am I understanding this correctly?

We have a stand-alone version of packbeam available here:
https://github.com/atomvm/atomvm_packbeam
It looks like this should be made more clear in the documentation...
For compiling and flashing your own app there is a rebar3 plugin that can create an AtomVM application template, and flash your compiled app to ether an ESP32 or an STM32, available here:
https://github.com/atomvm/atomvm_rebar3_plugin
Hope this helps. Please follow up if you still run into problems.

I forgot to mention that the rebar3 plugin has packbeam included, so if you are using that the standalone packbeam application is not necessary.

Just to be clear, the atomvm_rebar3_plugin and the atomvm_packbeam code is all pure Erlang, so there is no need to build any C code out of the AtomVM repo.  The PackBEAM C program is used internally by AtomVM for packing the core libraries.

@brucekissinger did @fadushin suggestion worked for you?
Also, can you tell us which Linux distribution are you using? Which version?
I think there is something we should improve on our side for sure.

I am using Ubuntu 18.04.06.
It sort of worked.  I was able to download the rebar3 plugin and build everything correctly.  I followed the instructions and created an AVM file named mylib.avm.  I was able to flash the AVM file but when I connect to the port, I get lots of messages that look like this:
Build:Mar 27 2021
rst:0x7 (TG0WDT_SYS_RST),boot:0x8 (SPI_FAST_FLASH_BOOT)
Saved PC:0x40048839
invalid header: 0xffffffff
....

Have you flashed the AtomVM VM image?  This sounds like an issue with not having an IDF application (in our case, the VM) flashed to the device.  Make sure to follow the instructions at https://www.atomvm.net/doc/master/getting-started-guide.html#deploying-the-atomvm-virtual-machine
Short of that, please feel free to contact us at any of the links on https://www.atomvm.net/contact/  We are most active on Telegram

@brucekissinger Can you give us an update on this ticket?  Thanks!

I think the issue here is not relevant anymore (we even don't support OpenSSL anymore). Closing it.


Direct Share URL

HI,
it is possible to add a direct share URL instead of https://www.example.com/#/?r=/download&path=L2FyY2hpdmUuemlw I want to like this https://www.example.com/#/foldername/filesname.zip
the reason why I need this.
I am uploading files to my website and other people come and copy the link and share on their own website. I want to protect my files to my domains only via hotlink protection.
it is not possible to publicly share the URL but it is possible with an actual share path with file extension.
I am also requesting a remote upload option for uploading large files from direct URLs.
thanks

would love this but i think it would get into a few problems, from how it looks like it's done rn is it just encoding it with Base64, like "L2FyY2hpdmUuemlw" is "/archive.zip" that in itself don't i think would be an issue, i think the issues with starts when there's spaces in the folder or file
for an example if i wanna download a file that looks like this "https://www.example.com/#/?r=/download&path=foldername/filesname.zip" that would be no issue, but if it looked like this "https://www.example.com/#/?r=/download&path=folder name/filesname.zip" would it not be able to download the filesname.zip file
one way to maybe prevent this could be to make it Base64 encode the url you put in, so if you put "https://www.example.com/#/?r=/download&path=folder name/filesname.zip" would it give the server the url called "https://www.example.com/#/?r=/download&path=Zm9sZGVyIG5hbWUvZmlsZXNuYW1lLnppcA=="
not sure how else you would go about it tbh, spaces are kinda annoying when it comes to urls


Add contributors

@all-contributors please add @fraxken for code, bug, maintenance, security, review


CSS Consistency

Lunar has built in support for CSS-in-JS which is preferable for its local name space and theming, but Vercel supports a version of CSS Modules that are pretty nice too:
https://nextjs.org/docs/basic-features/built-in-css-support
Either one is fine, but we should align on one system.

Closed by https://github.com/philihp/skyfall/pull/22


demo.html is not match to the fonts last update

Hello,
I have a problem with the demo.html file, which are included in the custom zip archives you can download from the web service at fontello.com.
I have notice that the demo.html code does not match the icons shown in the fonts - so even when i'm updating the font icons, and downloading the zip file from the fontello site, the demo.html file is not getting the update - and the new icons is not shown.
Are you familiar with this issue?
Thanks!

Closed due no activity


Example for posting a body for AsyncRead?

reqwest::blocking::Body can be easily built from any Read object. I'm working on trying to convert some of this code to async, but can't for the life of me figure out how to do something similar in async land. I assume you have to use reqwest::Body::wrap_stream, but how to create a proper stream from an tokio::fs::AsyncRead appears to be beyond me as I've been banging my head against this all day. It's easy enough to read the entire AsyncRead into memory and provide it directly, but when uploading a file, that requires loading the entire file into memory. Any tips would be greatly appreciated, and since I doubt I'm the only one attempting this, perhaps adding an example of posting a file with the new async API would help a lot.
Thanks!

For now I found that the best way is to use BytesCodec type from tokio-util crate. Internally it minimizes memory allocations, see an investigation here.
So, full code will be:
use reqwest::Body;
use tokio::fs::File;
use tokio_util::codec::{BytesCodec, FramedRead};

fn file_to_body(file: File) -> Body {
  let stream = FramedRead::new(file, BytesCodec::new());
  Body::wrap_stream(stream)
}

@nickkuk Thanks for the example, any idea how to integrate indicatif? I want to display the current progress.
Is there a way to "do something" (bar.inc(1);) in every chunk from the  stream or maybe from Body?
Thanks in advance :-)

Hi, @nbari, if you mean file uploading, here I've just tried to create Stream that consumes stream from
FramedRead::new(file, BytesCodec::new())

and calls inc inside. But it works not smoothly, maybe there is some buffering between reqwest and the system. At now I don't know better way.
If you mean file downloading, just call inc inside this loop, but you need to know total file size somehow, not every server gives you content length.

Thanks, I am using this approach, inspect_ok does the trick:
use futures::stream::TryStreamExt;
use tokio_util::codec::{BytesCodec, FramedRead};

let stream = FramedRead::new(file, BytesCodec::new())
    .inspect_ok(|chunk| {
        // do X with chunk...
    });

let body = Body::wrap_stream(stream);

@nbari, I'm tried both approaches, but eventually decided that it is better to call inc for previous chunk, i.e., when reqwest reads just another chunk, we believe that it sends all previous. But it is not the case, probably due to some buffering.
Did you get smoothly increasing progress bar?

Hi @nickkuk, I am currently working on it, indeed I am stuck with this,  https://stackoverflow.com/q/63374041/1135424, any helps is pretty much appreciated.
let stream = if let Some(mut tx) = sender {
    FramedRead::new(file, BytesCodec::new()).inspect_ok(move |chunk|
         tx.send(chunk.len())
    )
} else {
    FramedRead::new(file, BytesCodec::new())
};

// reqwest
let body = Body::wrap_stream(stream);
client.put(url).body(body)
let body = Body::wrap_stream(stream);

I am getting:
`if` and `else` have incompatible types

But for other similar cases (multipart upload), I do get a nice progress bar: https://github.com/s3m/s3m/blob/develop/src/s3m/upload.rs#L55
(currently working/learning so any feedback is more than welcome)

I think you can use async-stream crate, that I've already mentioned here. It allows you to write sync-like code with yield instead of using combinators (as map or inspect_ok):
  async_stream::stream! {
    if let Some(mut sender) = sender {
      while let Some(bytes) = stream.next().await {
        if let Ok(bytes) = &bytes {
          sender.send(bytes.len()).await;
        }
        yield bytes;
      }
    } else {
      while let Some(bytes) = stream.next().await {
        yield bytes;
      }
    }
  }

@nickkuk many thanks for the examples, I was indeed dealing with the if/ else until found I could do:
let stream  =  async_stream::stream! {
...
};

Hi @nickkuk I found interesting this example:
use tokio::sync::mpsc;
use futures::future::Either;

fn upload(file: String, sender: Option<mpsc::Sender<usize>) {
    let stream = FramedRead::new(file, BytesCodec::new());

    let stream = if let Some(mut tx) = sender {
        Either::Left(stream
            .inspect_ok(move |chunk| tx.send(chunk.len()))
        )
    } else {
        Either::Right(stream)
    };

    let body = Body::wrap_stream(stream);

}

Is not clear for me why It won't compile if I don't add a println!("{}", 0):
Either::Left(stream
    .inspect_ok(move |chunk| {
        tx.send(chunk.len());
        println!("{}",0);
     }))

Also, I think it requires a .await: tx.send(chunk.len()).await;  but if I add it I get this error:
 await` is only allowed inside `async` functions and blocks

Just asking to understand & learn more, I indeed became curios because code for me looks cleaner when using Either but would like to know what could be some pros cons against the async-stream create.
Thanks in advance.

From documentation of inspect_ok you can see that it expects F: FnOnce(&Self::Ok), which means that a closure must returns ().
But tx.send(chunk.len()) returns impl Future<Output = Result<(), SendError<T>>, so it is not magic of println, but magic of semicolon.
About .await for send - you are right, and I use it in my example. It is needed because your Sender is bounded, so it will be blocked if capacity not enough. You have the following possibilities:

use UnboundedSender, which have send that returns just Result<(), SendError<T>> (i.e., without Future);
use async-stream crate that allows to use .await and yield inside stream! macro;
use another combinator of Stream, e.g., and_then, that expects F: FnOnce(Self::Ok) -> Future.

I suggest to use async-stream because

it is more idiomatic for rust;
it unsugars to something like Either;
it maybe become standard in future: see about activity from rust lang team here.

Hi @nickkuk many thanks for the explanation and your time on this,  taking advantage of the thread, I have one last question regarding this topic, probably too basic but hope you don't mind since I am trying to grasp the concepts of async/await
To increase the progress bar bar.inc(1);  or read from the Receiver I am found that I have to call tokio::spawn to do the request and then that will allow me to read  from the channel, otherwise, since there is no reader I get locked, I thought that by using already .await I could skip the "spawn", my bad probably since I was thinking that await is like go ( Gorouting from Golang. I end up doing something like this:
let bar = ProgressBar::new(1000);
let (tx, mut rx): (mpsc::Sender<usize>, mpsc::Receiver<usize>) = mpsc::channel(100);

tokio::spawn(async move {
    my_upload(file, Some(tx)).await; // <-- method using `async-stream` uploading the file and returning in the chunks.len()
 });
while let Some(i) = rx.recv().await {
       bar.inc(1);
 }
...

Is think is the way to go, but now with too many new options that I just learn about how to do the same task but with different methods, I wonder if there is something more idiomatic to achieve the same.

At first I want to clarify that in my last reply I suggested to use async-stream not against UnboundedSender (actually UnboundedSender is more suitable for your task), but against Stream combinators (and even this not always true, sometimes combinators are smaller).
Actually you don't need any tokio::spawn for single file uploading by using tokio::try_join!; see an example here. Even more, you can upload two, three, or more files by this approach (maybe with the same UnboundedReceiver for all files and cloned UnboundedSender). And even unknown number of files can be uploaded without tokio::spawn by using e.g. futures::stream::FuturesUnordered.
tokio::spawn

should be used to reduce memory size of Future - every rust Future (i.e., every async fn including async fn main, every bunch of combinators, tokio::try_join!, tokio::select!, futures::stream::FuturesUnordered) is state machine - it consumes more memory if it is bigger;
must be used to introduce task parallelism - every spawned rust Future (so called task) is executed on zero (waiting among all tasks or on .await) or one system thread; tokio::spawn creates new task that can be executed on another thread.

For example, tokio::spawn is used in hyper server for every new connection and every new request of connection.
Main drawback of tokio::spawn is that consumed Future must be 'static. There was an attempt to handle this constraint, but it failed.

@nickkuk many thanks for the examples and sharing the knowledge, I highly appreciate it :-)

Example for save a response body to file for async, and display download total progress?
I don't know how to use buff to read and write
let rsp = reqwest::Client::new().get("http://aabbcc.com/1.mp4").send().await;
let file = std::fs::File::create(file).unwrap();
let mut buf = [0; 8192];
let mut reader = StreamReader::new(rsp.bytes_stream());
loop {
  // do  read buff , write buff, print r/w size, util eof
}

Hi people!
I have the below code and I'm stucked because I don't know how to post() the AsyncRead, can you help me understand?
#[async_trait::async_trait]
impl Trait for UploadClient {
    async fn put_file(
        &self,
        filename: &str,
        mut reader: Pin<&mut (dyn AsyncRead + Send + Sync)>,
    ) -> Result<u64> {
        // let url = ...;

        let client = reqwest::Client::new();

        let resp = client
            .post(url)
            // Nothing of these works!
            // .body(reader)
            // .body(reqwest::Body::wrap_stream(reader))
            // .body(ReaderStream::new(reader))
            .body(StreamReader::new(reader))
            .send()
            .await?
            .error_for_status()?;

        Ok(123)
    }
}

Hey @frederikhors, I think that the current standard approach is to use tokio-util helper crate with BytesCodec and FramedRead structures. See an example here.

@frederikhors your example would not set the upload length though right ?
There are a number of implementations of From<File> for Body etc and even a function for streamwithlength which is helpful when uploading an async tokio file stream.
I am interested in this because i have a ProgressReader (reporting on upload progress) which is AsyncReader which can wrap a file stream etc, but i need it converted to a body to send it.
With some of the other examples above I am worried about backpressure and whether this is correctly handled. Based on the way async reads are handled I am pretty sure AsyncRead will always be pull based and thus handle pressure automatically.
In general, tracking progress (optionally) for sending a request should be something built in.


[V2] Crash on iPhone 15 Pro + iOS 17 (AVCaptureDeviceFormat.toDictionary()) 🐛

What's happening?
I have reported and simulated crashes on iOS 17, only on iPhone 15 Pro affected (i've tested iphone 15, 12 and it works ok).
It looks similiar like https://github.com/mrousavy/react-native-vision-camera/issues/1840, but crash is on different place and it is not problem of iphone 15 (non-Pro version)
I'm using Xcode14 (i had reverted back when V2 build was not possible on xcode 15 due to some errors) and RNVC V2.
Sadly, i don't have device available for debugging, i have just production crash reports and crash on BrowserStack real device cloud.
Reproduceable Code
const devices = useCameraDevices();
	const device = devices.back;

// ....

	return (
		<>
			{device && hasPermission && (
				<View style={styles.container}>
					{isForeground && (
						<Camera
							style={StyleSheet.absoluteFill}
							device={device}
							isActive={!disabled}
							frameProcessor={boundFrameProcessor}
							frameProcessorFps={frameProcessorFps}
							preset="medium"
							onLayout={handleLayoutChange}
						/>
					)}

....

Relevant log output
Incident Identifier: A67BE188-5BF8-4B0B-979F-3378000178E4
Hardware Model:      iPhone16,1
Process:             MyRNVCApp [82017]
AppVariant:          1:iPhone15,2:16
Code Type:           ARM-64 (Native)
Role:                Foreground
Parent Process:      launchd [1]
Coalition:           com.MyRNVCApp [3039]

OS Version:          iPhone OS 17.0.3 (21A360)
Baseband Version:    1.00.03
Report Version:      104

Exception Type:  EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000001, 0x000000019472f86c
Termination Reason: SIGNAL 5 Trace/BPT trap: 5
Terminating Process: exc handler [82017]

Triggered by Thread:  0

Thread 0 name:
Thread 0 Crashed:
0   libswiftCore.dylib            	0x000000019472f86c _assertionFailure(_:_:file:line:flags:) + 264 (AssertCommon.swift:144)
1   MyRNVCApp                   	0x0000000104aea884 AVCaptureDeviceFormat.toDictionary() + 3016 (AVCaptureDevice.Format+toDictionary.swift:0)
2   MyRNVCApp                   	0x0000000104aff2ec closure #1 in closure #2 in closure #1 in CameraViewManager.getAvailableCameraDevices(_:reject:) + 4 (CameraViewManager.swift:136)
3   MyRNVCApp                   	0x0000000104aff2ec specialized Collection.map<A>(_:) + 112 (<compiler-generated>:0)
4   MyRNVCApp                   	0x0000000104aff2ec closure #2 in closure #1 in CameraViewManager.getAvailableCameraDevices(_:reject:) + 1816 (CameraViewManager.swift:135)
5   MyRNVCApp                   	0x0000000104afea48 specialized Collection.map<A>(_:) + 128 (<compiler-generated>:0)
6   MyRNVCApp                   	0x0000000104afea48 closure #1 in CameraViewManager.getAvailableCameraDevices(_:reject:) + 968
7   MyRNVCApp                   	0x0000000104afea48 0x10470c000 + 4139592 (CameraViewManager.swift:118)
8   MyRNVCApp                   	0x0000000104b0483c specialized withPromise(_:_:) + 48 (Promise.swift:52)
9   MyRNVCApp                   	0x0000000104aff560 specialized withPromise(_:_:) + 12 (CameraViewManager.swift:68)
10  MyRNVCApp                   	0x0000000104aff560 CameraViewManager.getAvailableCameraDevices(_:reject:) + 12 (<compiler-generated>:0)
11  MyRNVCApp                   	0x0000000104aff560 @objc CameraViewManager.getAvailableCameraDevices(_:reject:) + 196
12  CoreFoundation                	0x000000019b2b7134 __invoking___ + 148 (:-1)

Camera Device
{}

Device
iPhone 15 Pro
VisionCamera Version
2.16.1
Can you reproduce this issue in the VisionCamera Example app?
I didn't try (⚠ your issue might get ignored & closed if you don't try this)
Additional information

[ ] I am using Expo
[X] I have enabled Frame Processors (react-native-worklets-core)
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

I have got the same issue. react-native-vision-camera version: 3.6.16

same

Same issue logged in 1840

same problem

i also got an issue with this it's crashing on 15 pro/max version @mrousavy any solutions to this?

same issue for me, crash on iPhone 15 ProMax
using react-native-vision-camera: 2.16.6

same issue here, i'm using v2.15.2

same issue ;/

Same issue here, please help someone. :)

Same issue here, please help someone. :)

same issue ;/

same issue for me, crash on iPhone 15 ProMax

i also got an issue with this it's crashing on 15 pro/max version @mrousavy any solutions to this?

same

I have got the same issue. react-native-vision-camera version: 3.6.16

please stop spamming - if an issue is that important for you to get it fixed, consider sponsoring me on GitHub to pay me for fixing an issue for you.

Thanks @Ardazafer for the sponsorship on GitHub!
I've gone ahead and ran the Example app on my iPhone 15 Pro on the current v2 branch, and it starts perfectly fine. Are there any ways to reproduce this issue?

Did this fix the issue for you guys? https://github.com/mrousavy/react-native-vision-camera/commit/503114b9d1c61d60fa3c69b3bd4cb084758fbf5b

I'm pretty sure that fixed the issue in 2.16.7, if not we can still re-open the issue @Ardazafer.

@mrousavy Yeap that fixed the issue, thanks for the good work man!

Any update on this issue?

Happing til now


General: Make exam mode feature overview page viewable on mobile

Checklist
General

[x] This is a small issue that I tested locally and was confirmed by another developer on a test server.
[x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[x] I chose a title conforming to the naming conventions for pull requests.

Client

[x] I followed the coding and design guidelines and ensured that the layout is responsive.
[x] Following the theming guidelines, I specified colors only in the theming variable files and checked that the changes look consistent in both the light and the dark theme.

Motivation and Context

The feature overview page is currently not viewable on small screen widths. Additionally, the description texts in the cards are sometimes too long and can't be read entirely

Description

Adjust styling and responsiveness to make the page at least readable on mobile widths
Change hover styles of feature boxes to be more simple and provide enough space for the entire short feature description text

Steps for Testing

Prerequisites:

1 User

Navigate to /features/instructors and /features/students and make sure everything looks okay on desktop and mobile sizes
Make sure that you can read the short description texts when hovering over feature boxes
Make sure that it looks okay in both themes (I won't do anything about the white background of images for now)

Review Progress

Code Review

[ ] Review 1
[ ] Review 2

Manual Tests

[ ] Test 1
[ ] Test 2

Screenshots

https://user-images.githubusercontent.com/23171488/185759244-ba7a4100-3e48-4266-b8c2-e360c25877c5.mp4

@ge65cer Could you recheck all 3 issues?


use DBOS cloud v1alpha1 API

As the title says

It feels like a lot of work to change them all.

When users send requests to their deployed apps, do they also need to add v1alpha1 to their url?

Looks like it - seems like a lot of churn - all the URLs get new (additional?) names even when the API doesn't change at all...  Hardcoding in several places is unappealing, given that circumstance.  (In 20+ years, the S3 API is on v3 ... aim for that.)

When users send requests to their deployed apps, do they also need to add v1alpha1 to their url?

They don't, user routes are unaffected by this.


Cannot install plugin

Obsidian 0.12.5 on macOS 11.4
Kindle Highlights plugin has been installed for awhile.  Today I checked for updates (from within the Community Plugins section of Obsidian Settings).    An update for Kindle Highlights was available according to Obsidian.   Clicked to install.  "Failed to Install..." message.  I deleted the plugin and restarted Obsidian.  Now, from the Community Plugins list, I cannot install the plugin.
  Failed.
Attached shows the installed plugins.

I've just released a new version 0.2.16. Can you try getting latest and see if this version works for you please?

Thank you.  I am able to succeed and install it.  I'll have to monitor it to determine if it is actually syncing again.


Separate C# GUI initialization logic from the rest of the entry point

This simple PR is intended to allow another program to act as a wrapper for the GUI runner. Currently, one can invoke the runner via reflection, but if one uses C# forms BEFORE invoking the runner, the GUI initialization logic in Main throws an exception. In my case, for instance, I was initializing a C# form for easy configuration of the args passed to the NUnit GUI runner, and the following exception would get thrown upon using reflection to call Main:
Unhandled Exception: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: SetCompatibleTextRenderingDefault must be called before the first IWin32Window object is created in the application.
   at System.Windows.Forms.Application.SetCompatibleTextRenderingDefault(Boolean defaultValue)
   at NUnit.Gui.Program.Main(String[] args)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
// ...

With this change, clients can now invoke the
var guiRunnerAssembly = Assembly.LoadFile("...\\nunit-gui.exe");
guiRunnerAssembly.EntryPoint.DeclaringType.GetMethod("Run").Invoke(null, new object[] { args });

I don't see any particular harm in this PR, but it supports a usage that we don't have any plans to continue to support. That is, it could continue to work, or not, depending on future changes.
@NUnitSoftware/gui-team What do you think?

Well, if it's not something that the team plans on supporting, I definitely don't want to give a false start that makes it seem like it's supported. :) I hope that the GUI team likes it!
For me as a user, the motivation behind this example is to avoid shelling out using Process.Start, if possible. It's nice to avoid that overhead, but that doesn't change the fact that it adds another concern to the GUI runner's code: maintaining the entry point as I've modified it here.

For the V2 gui, we made the exe a one-liner and put the actual code in an eye that others could reference. Of course, you can reference the exe as well.
I wonder if a more robust fix would be possible by bypassing initialization if it's already done by a caller.

I don't mind the change. Wrt. to making the code more robust I'm unsure about the consequences of SetCompatibleTextRenderingDefault. What if the caller has set Application.SetCompatibleTextRenderingDefault(true) before calling into our code. How will this affect our code/GUI?

That part wasn't changed, and it would be up to the user who is bypassing to deal with the consequences of setting Application.SetCompatibleTextRenderingDefault(true).  I think the change is small enough and fine as is.

Also, another thing I might add for the benefit of anyone who's following this: being able to call the executable via assembly loading instead of shelling out also facilitates a debugging flow from Visual Studio. I just ran into this myself today -- I'd forgotten that this was one of the ramifications!


Upstream a bunch of additions and changes to unistd

The Zeek project recently had a port to Windows contributed by a team at Microsoft. Included in the port was a number of changes to libunistd to add needed methods and fix a few bugs. This is the first in a set of PRs that I'm putting together to upstream as many of these changes back to the main repo as possible. This is the easy set, where it's just additional files and such.
I have other changes that will take a bit of massaging to get ready to PR back to upstream. Those will come later.

Alright I think I've caught up with everything you added to the contributor notes. Let me know if there's anything else, or if I should squash everything back into the original commit set again.

Great, thanks. I'll get started on the next set 😃


error while building

When trying to compile for windows following the guide i get the following error message for all files
fatal error C1083: Cannot open include file: 'gs/gs.h': No such file or directory
I dont understand how to fix it or what gs.h is or where to get that dependency

Try pulling again - the third party dependency on gs wasn't included correctly with the last update.


Startup probe is in beta since 1.18

Startup probe is in beta since 1.18
See https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.18.md#features-graduated-to-beta

@alex-slynko if you can sign the CLA, this sounds like it's going to be a useful PR to review and then merge!

@sftim I have changed the company and now have trouble in changing the Linux Foundation email.
I will sign the CLA as soon as possible.

/status

done @sftim

Relevant to issue #19405


Update build dependency versions

I need to update bigdataviewer-omezarr dependency version, so I'll try to harmonize more or less with the Fiji released versions the other packages in the pom.

https://github.com/JaneliaSciComp/BigStitcher-Spark/pull/28
I reverted back the other packages due to new error in creating groups by N5Writer in aws. We'll address this later.
The problem is, I think, that setup0/timepoint0/s0 does not exist while setDatasetAttributes tries to read it in already before setting them.
org.janelia.saalfeldlab.n5.N5Exception$N5IOException: setup0/timepoint0/s0 is not a group or dataset.
	at org.janelia.saalfeldlab.n5.GsonKeyValueN5Writer.setAttributes(GsonKeyValueN5Writer.java:154)
	at org.janelia.saalfeldlab.n5.N5Writer.setDatasetAttributes(N5Writer.java:138)
	at org.janelia.saalfeldlab.n5.N5Writer.createDataset(N5Writer.java:206)
	at org.janelia.saalfeldlab.n5.N5Writer.createDataset(N5Writer.java:228)
	at net.preibisch.bigstitcher.spark.AffineFusion.call(AffineFusion.java:361)


hero

Template request
Describe the template you need
Additional information
Optional: Add screenshots, or Figma/Sketch files

Please provide a proper description. We already have some hero templates: https://chakra-templates.dev/page-sections/hero


Support Inline Comments for Styled Components

Styled Component supports both line comments //as well as regular css comments /* */.
In this package when you use the atom comment shortcut you get the following.
${'' /* display: block; */}

Expected Result:
// display: block;

In an addition if you manually type out line comments the syntax highlighting doesn't identify line comments as a comment.
See comment below for more information
https://github.com/styled-components/styled-components/issues/1098#issuecomment-324404085

Hi @mattmischuk I was able to make this happen by updating my config.cson file.  Open the command pallete and search for "Application: Open Your Config".  At the bottom, I added:
".source.inside-js.css.styled":
  "editor":
    "commentStart": "/* ",
    "commentEnd": " */"

Hope this helps!


OCPEDGE-927: Introduce Static discovery of devices that allows immutable storage configurations

DeviceDiscoveryPolicy is a flag to indicate whether the device should be discovered at install time or at runtime (static or dynamic configuration of devices):

If set to DeviceDiscoveryPolicyInstallStatic, the devices will not be added to the VG if they are not present at setup time.
If set to DeviceDiscoveryPolicyRuntimeDynamic, the devices will be added to the VG if they are present at runtime. By default, the value is set to RuntimeDynamic.
This field cannot be updated once the LVMCluster is created.

All existing LVMClusters will work in Dynamic Mode and will not be able to be reconfigured to Static Mode. Any new LVMClusters will be able to be changed to Static Mode.
A new LVMCluster with 2 devices (/dev/loop0 available when LVMCluster was created and /dev/loop1 added afterwards) would look like this:
apiVersion: lvm.topolvm.io/v1alpha1
kind: LVMCluster
metadata:
  finalizers:
  - lvmcluster.topolvm.io
  generation: 1
  name: my-lvmcluster
  namespace: openshift-storage
spec:
  storage:
    deviceClasses:
    - default: true
      deviceDiscoveryPolicy: InstallStatic
      fstype: xfs
      name: vg1
      thinPoolConfig:
        name: thin-pool-1
        overprovisionRatio: 10
        sizePercent: 90
status:
  deviceClassStatuses:
  - name: vg1
    nodeStatus:
    - deviceDiscoveryPolicy: InstallStatic
      devices:
      - /dev/loop0
      excluded:
      - name: /dev/loop1
        reasons:
        - /dev/loop1 was not part of vg1 at creation (static device discovery enabled)
      - name: /dev/vda
        reasons:
        - /dev/vda has children block devices and could not be considered
        - /dev/vda was not part of vg1 at creation (static device discovery enabled)
      - name: /dev/vda1
        reasons:
        - /dev/vda1 has an invalid partition label "BIOS-BOOT"
        - /dev/vda1 was not part of vg1 at creation (static device discovery enabled)
      - name: /dev/vda2
        reasons:
        - /dev/vda2 has an invalid filesystem signature (vfat) and cannot be used
        - /dev/vda2 was not part of vg1 at creation (static device discovery enabled)
      - name: /dev/vda3
        reasons:
        - /dev/vda3 has an invalid filesystem signature (ext4) and cannot be used
        - /dev/vda3 has an invalid partition label "boot"
        - /dev/vda3 was not part of vg1 at creation (static device discovery enabled)
        reasons:
        - /dev/vda4 has an invalid filesystem signature (xfs) and cannot be used
        - /dev/vda4 was not part of vg1 at creation (static device discovery enabled)
      name: vg1
      node: crc-vlf7c-master-0
      status: Ready
  ready: true
  state: Ready

We can later on think about introudcing switching between RuntimeDynamic and InstallStatic (in case we want people to be able to switch between dynamic allocation and "pinning" their configuration) but this has been out of scope for this PR.

/jira-refresh

Codecov Report
Attention: Patch coverage is 77.77778% with 14 lines in your changes are missing coverage. Please review.

Project coverage is 77.80%. Comparing base (fd45f00) to head (8e81cfd).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #599      +/-   ##
==========================================
- Coverage   77.92%   77.80%   -0.13%
==========================================
  Files          27       27
  Lines        1948     1987      +39
==========================================
+ Hits         1518     1546      +28
- Misses        316      323       +7
- Partials      114      118       +4

Files
Coverage Δ

api/v1alpha1/lvmcluster_types.go
100.00% <ø> (ø)

api/v1alpha1/lvmvolumegroup_types.go
100.00% <ø> (ø)

api/v1alpha1/lvmvolumegroupnodestatus_types.go
100.00% <ø> (ø)

internal/controllers/vgmanager/controller.go
73.60% <100.00%> (ø)

internal/controllers/vgmanager/status.go
82.30% <100.00%> (+0.48%)
:arrow_up:

internal/controllers/vgmanager/filter/filter.go
83.78% <88.23%> (+1.02%)
:arrow_up:

internal/controllers/vgmanager/devices.go
77.41% <73.68%> (-2.59%)
:arrow_down:

api/v1alpha1/lvmcluster_webhook.go
81.53% <56.25%> (-1.89%)
:arrow_down:

... and 1 file with indirect coverage changes

This depends on how the disk was added to LVMCluster, e.g. which path/symlink is used.
If using a device path such as /dev/xda, then one would need to make sure the device appears under this path again.
You are right in that it is impossible to switch to a new device path like this, however removing device Paths is already not supported today from what I know. Meaning once you enter a device path it cannot be removed (maybe a design / product oversight?)
When using the usual symlinks we have to differentiate:

/dev/disk/by-path: This is okay to be used as long as the replaced device is slotted into the same PCIe Slot and the Host OS has persistent PCIe Controller mapping
/dev/disk/by-id: The Disk ID has to match the hardware serial number, this is impossible to replace because there is no way the new disk can match to the old disk

the by-path will already change when the device is plugged into a different port of the controller, the by-id will change when the device is plugged into a port of a hardware controller subject to another subsystem. For example, The /dev/disk/by-path/pci-* paths for NVMe devices may change if a PCIe device is added or removed from the system or if the system firmware does not enumerate them deterministically

/dev/disk/by-label: to be preferred, the Disk has to use the same label as the broken disk and will be picked up again in its stead, but the old disk has to be unmounted
/dev/disk/by-partlabel: equivalent to by-label, but to be used when using a prepartitioned layout with GPT entries.
/dev/disk/by-uuid: We should not use this one as it uses filesystem UUIDs and we potentially have only block storage to rely on
/dev/disk/by-partuuid: We should not reference this one as it uses GPT partition UUIDs or MBR pseudo UUIDs and thus make them irreplaceable device paths.

This depends on how the disk was added to LVMCluster, e.g. which path/symlink is used.
I was under the impression that the DeviceDiscoveryPolicy is only applied when no devicePath is used?

You are right in that it is impossible to switch to a new device path like this, however removing device Paths is already not supported today from what I know. Meaning once you enter a device path it cannot be removed (maybe a design / product oversight?)

We should make sure this is documented.

When using the usual symlinks we have to differentiate:
Thanks for the excellent enumeration and explanation. We should add this to the docs.

Overall: This needs a FEATURE, as it also needs docs. We should use the opprtunity to add a "Guide to use disk devices with LVMS". (e.g. recommend HW RAID, make sure the restrictions on device removal are clearly stated,  etc). (I will create that feature)

I think those are good Action Items. Also started looking into https://issues.redhat.com/browse/OCPEDGE-1007 based on your previous comment now to get clear understanding from engineering side. We can use that to fill the docs and give us a better idea on what we need to fix.

This depends on how the disk was added to LVMCluster, e.g. which path/symlink is used.

I was under the impression that the DeviceDiscoveryPolicy is only applied when no devicePath is used?

/hold
putting on hold until we have some more clarity on the approach

Closing until we have a way forward since it doesnt seem likely this goes in


Added some help text to odenc

Don't know if I'll have time or energy to add any real functionality, but here is an implementation of
odenc help
I might have misread how things work, so please check the text.

Thanks! I'll do some updates to it later but it looks good. :)


add tests for multiline reprs

Type of changes

[x] Bug fix
[ ] New feature
[ ] Documentation / docstrings
[ ] Tests
[ ] Other

Checklist

[x] I've run the latest black with default args on new code.
[ ] I've updated CHANGELOG.md and CONTRIBUTORS.md where appropriate.
[x] I've added tests for new code.
[x] I accept that @willmcgugan may be pedantic in the code review.

Description
This pull request will fix #2073 . Reasoning and thought process described in excruciating detail in this article about contributing to Open Source.

Codecov Report

Merging #2267 (cd7070f) into master (14d47c9) will decrease coverage by 3.02%.
The diff coverage is 96.89%.

@@            Coverage Diff             @@
##           master    #2267      +/-   ##
==========================================
- Coverage   98.88%   95.85%   -3.03%
==========================================
  Files          73       73
  Lines        7629     7681      +52
==========================================
- Hits         7544     7363     -181
- Misses         85      318     +233

Flag
Coverage Δ

unittests
95.85% <96.89%> (-3.03%)
:arrow_down:

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

Impacted Files
Coverage Δ

rich/_export_format.py
100.00% <ø> (ø)

rich/console.py
96.68% <95.91%> (-2.11%)
:arrow_down:

rich/pretty.py
99.24% <100.00%> (+0.02%)
:arrow_up:

rich/syntax.py
99.30% <100.00%> (+0.02%)
:arrow_up:

rich/terminal_theme.py
100.00% <100.00%> (ø)

rich/_windows_renderer.py
0.00% <0.00%> (-100.00%)
:arrow_down:

rich/_win32_console.py
3.19% <0.00%> (-88.30%)
:arrow_down:

rich/traceback.py
98.68% <0.00%> (-0.88%)
:arrow_down:

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 1772458...cd7070f. Read the comment docs.

@willmcgugan I have some questions.
There's 2 main things to solving #2073. Making sure pretty_repr understands that some objects might have multiline reprs and pprint not adding vertical guidelines to those. So far, this draft takes care of pretty_repr.
I will study pprint better to see how I can take care of not adding vertical guidelines.
Meanwhile, question: do I add unit tests that comprehensively check that the pretty_repr function does the proper job of indenting objects with multiline reprs when inside all the containers that pretty_repr knows about? So far, the tests only cover a couple of containers like sets, dictionaries, and lists.

It's probably not necessary to test every container, as long as the system is well-tests.
The coverage calculation is quite flakey. It always seems to be off!

Right.
There is another fundamental issue with what I've done. I changed _Line.__str__ so that, sometimes, it returns a multi-line string. I know how careful you are with naming, so what should happen now?

_Line gets renamed because it doesn't represent a line of input, but more like a unit block or something.
I create multiple _Line instances for nodes with multi-line reprs.
My changes are actually OK because _Line says it represents some node output that starts on its own line, which is still true.

I think _Line being private, I can relax my pedantry a bit. But equally open to a better name if you can think of one!

@rodrigogiraoserrao Is this stale?

Nah, I'm just overwhelmed with life. I'll finish this ASAP.
If you want, close this PR draft and I'll open a new one with all the changes when they're done.

No hurry


Make MediaInfoLib on Mac throws error

"_curl_slist_free_all", referenced from:
MediaInfoLib::Amazon_AWS_GetRegion(std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > const&, std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > const&, MediaInfoLib::Http::Url const&, void*, ZenLib::ZtringList const&) in Reader_libcurl.o
MediaInfoLib::Reader_libcurl::~Reader_libcurl() in Reader_libcurl.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[1]: *** [libmediainfo.la] Error 1
make: *** [all-recursive] Error 1

We build also on macOS, so weird.
Which package (name, version)? which macOS version?

We build also on macOS, so weird.
Which package (name, version)? which macOS version?

tried to build from current master on macOS Mojave 10.14.6.
Followed direction as per the READ.ME

Please try with our "all in one" package so we can see if issue is in the use of the raw source or also in our "all in one" package with a single command line.

E: Libcurl support is disabled due to compilation options

Did you check that libcurl development package is detected from the result of ./configure of libmediainfo?
Something weird here is that libcurl support seems configured but the libcurl library location is not in the linker.

Please try with our "all in one" package so we can see if issue is in the use of the raw source or also in our "all in one" package with a single command line.

E: Libcurl support is disabled due to compilation options

Did you check that libcurl development package is detected from the result of ./configure of libmediainfo?
Something weird here is that libcurl support seems configured but the libcurl library location is not in the linker.

libcurl was pointing to the system. correctly. Trying all in one package

Please try with our "all in one" package so we can see if issue is in the use of the raw source or also in our "all in one" package with a single command line.

E: Libcurl support is disabled due to compilation options

Did you check that libcurl development package is detected from the result of ./configure of libmediainfo?
Something weird here is that libcurl support seems configured but the libcurl library location is not in the linker.

libcurl was pointing to the system. correctly. Trying all in one package

@JeromeMartinez "all in one package" failed with the same error for me.

Anyone has success to build mediainfo with libcurl on macOS?

Anyone else have success building mediainfo with libcurl on macOS?

The "All in one" package don't enables libcurl by default. Please tries ./CLI_Compile.sh --with-libcurl or ./CLI_Compile.sh --with-libcurl=runtime


replace communities leaderboards with a table

Partially addresses #3222, and sets us up for #3127.
TODO

[ ] paging (cf. #3185)
[ ] clean up formatting a bit

This is about #3222, not #3127. I assume you're planning to make the table sortable, so it doesn't really fix #1928 either.

This is about #3222, not #3127.

The UI will need to change at least a little bit as part of #3127. For one, the sidebar doesn't make sense in the context of tags: one doesn't generally "organize" or "join" a tag; one isn't a "member" of a tag; the avatar no longer fits. We could simply drop the sidebar as on other pages (Search, Explore > Teams), but we also need to get the word "Member" out of "New Members."
However, I think #3127 actually requires a strong visual break from the current communities page. The point of #3127 isn't just to change communities to tags in our codebase, the point is to change the user's expectation from one of strongly identifying with others in the same community to weakly identifying with others using the same tag.
Since I've put #3222 out there as a general goal, I do see a chance to move us forward on both #3222 and #3127 at the same time by adopting a table layout for tags. Implementing #3222 for tags gives us a significant break from the current communities implementation.
It could make sense to do them as two separate PRs, but once the #3222 portion of this PR is done, the remaining work will largely be under the hood, and I think it won't bloat this PR too much to do it here.

it doesn't really fix #1928 either.

Addressed on #1928.

I've narrowed the scope of this to be about #3222.

Turned off communities in #3706.


500 error getting network info from API: Network interface "tap4eb1e6f0" not found

Required information

Distribution: Ubuntu
Distribution version: 21.04
The output of "lxc info" or if that fails: https://paste.ubuntu.com/p/KcYN5X4P9m/

Issue description
In MAAS, we have code like this, using pylxd:
networks = [net.state() for net in client.networks.all()]
If that runs while a VM is stopped, a 500 error is returned from the LXD API:
Network interface "tap4eb1e6f0" not found

While it's understandable that network interface can go away, shouldn't it return a 404 instead of a general 500 error? I couldn't find anything, except looking at the error message, to determine that the error is that the interface doesn't exist. I would at least expect something in the response to be able to see that it's not found, apart from having to search the error message, which is a bit fragile.
Steps to reproduce

Request /1.0/networks/foo/state, where foo doesn't exist.

Information to attach

[ ] Any relevant kernel output (dmesg)
[ ] Container log (lxc info NAME --show-log)
[ ] Container configuration (lxc config show NAME --expanded)
[ ] Main daemon log (at /var/log/lxd/lxd.log or /var/snap/lxd/common/lxd/logs/lxd.log)
[ ] Output of the client with --debug
[ ] Output of the daemon with --debug (alternatively output of lxc monitor while reproducing the issue)

Yeah, we'll likely need to make our SmartError wrapper or something turn this into a Missing error instead of InternalError.

@stgraber @masnax now that we have api.StatusError() and response.SmartError() is already configured to recognise it by type, you can use api.StatusErrorf() to return an api.StatusError() with a particular HTTP status code and custom message that will then be returned to the requester with the correct HTTP status code.
E.g.
https://github.com/lxc/lxd/blob/f9ce1c2d3191b4c88973dc2141841c2685498e68/lxd/db/network_forwards.go#L124

This should be a small change to https://github.com/lxc/lxd/blob/fc743968e05d941e796643b7558a991a2f62d1f6/lxd/resources/network.go#L437 to replace:
return nil, fmt.Errorf("Network interface %q not found", name)

with
return api.StatusErrorf(http.StatusNotFound, "Network interface %q not found", name)


Added the moving border to centermost div

I added the moving border to the centermost div.
Fixed issue #180
BEFORE

AFTER
https://github.com/sk66641/Random-Disco-Light-Simulator/assets/135015856/9a83e35f-cf70-4be2-9b37-3ab6ca39d96f

@Riddhi162
I have assigned level2 in your PR #212 as it contains solutions for both the issues #178  & #180 . So, i'm closing this PR.


clickhouse: add support for multiple and remote disks

The first thing is to support the disk prefix at the beginning of the file
path (anything before the store or shadow folder).
Some disks have metadata files instead of actual files in their store
folder, like object storage disks.
Even when the content is the same between replicas, the file
in object storage can be different, which makes the metadata files
different.
Because of that, we can't distribute parts among replicas and
we can't use a replicated ATTACH to exchange the data.
Even if we did, that wouldn't work great with all replication modes that
can be used in ClickHouse.
To fix that, stop doing parts distribution entirely and download all
parts from all nodes. To avoid the replication induced by ATTACH, replace
that with a SYSTEM RECOVER REPLICA: we remove the information in
ZooKeeper about the table replica, then force the disk content to be the
source of truth to recreate the ZooKeeper state.
When restoring a backup, we need to know if it's an old one that needs
to be restored with ATTACH/SYNC, or a new one that needs RESTART/RECOVER.
To detect that, introduce a version in the ClickHouse part of the manifest.
DDB-498

Reviewing this tomorrow


make sure first $_SERVER is an array. fixes zf2-194

Hi!
This is a fix for http://framework.zend.com/issues/browse/ZF2-194 just wrapped it in a is_array check.

Why not combine the ifs?

Readability. See https://github.com/robertbasic/zf2/blob/c5509c3346fdfa3f0b9c4e0fcd69e469fa65b7e2/library/Zend/Locale/Locale.php#L904 https://github.com/robertbasic/zf2/blob/c5509c3346fdfa3f0b9c4e0fcd69e469fa65b7e2/library/Zend/Locale/Locale.php#L914 https://github.com/robertbasic/zf2/blob/c5509c3346fdfa3f0b9c4e0fcd69e469fa65b7e2/library/Zend/Locale/Locale.php#L655 for examples.


Add support for Kinesis

This Pull Request is based on the awesome work done by @autometa101 in  #33. It introduces support for a subset of the AWS Kinesis API.
All the credit goes to @autometa101 for this, as we only refactor, slightly changed a few APIs, document and reorganize the code in this PR.
@autometa101 if you have the time, I would appreciate if you could take it for a spin and let us know if it works as intended 🙇🏻

✋🏻 We will need to have a documentation branch ready before we merge this ✋🏻

Hi @oleiade! I was looking precisely for this support and run into your PR. Thank you! Decided to give it a try but run into some issues I've been unable to fix. Sharing here in case it helps! The tests fail with the following error
 █ 04. publish to kinesis Stream

       ✗ Exception raised "GoError: Error: Either streamName or streamARN must be provided"
        ↳  0% — ✓ 0 / ✗ 1

     █ 05. Gets an Amazon Kinesis read all data

       ✗ Exception raised "GoError: KinesisServiceError: Invalid message body: Could not decode JSON: {
  "ShardIterator" : {
    "ShardIterator" : "AAAAAAAAAAFmqwhoAfhE8MD13BXmQX1Ih9VZi4y1LyauMGHHn7dAS6mus1maw43HnDAqCWJBITfLCVFU5Hlc2I5/bBVx/ztxgE+ql5aZ+e4bb0P7XMBe93AZdQtOznPAvjkna2+Zp1IomJ2qLEHM3y+BwbUJDGx0vxSHAKTEldoEPxTQJ+iIlXBy5yRe1ZS4vhgMXhbaMEOLIu3/h9/oO/h4iSPuGf75"
  }
}"
        ↳  0% — ✓ 0 / ✗ 1

     █ 06. Delete kinesis Stream

       ✗ Exception raised "GoError: KinesisServiceError: Invalid message body: Could not decode JSON: {
  "StreamName" : {
    "StreamName" : "kinesis-test-stream-dummy"
  }
}"
        ↳  0% — ✓ 0 / ✗ 1

I'm using Node.js v19.9.0 on an M1 MacBook. I see the tests are failing in the build system with the same message too (although the check is green?), so I'm guessing this is not something privy to my box. Can I help you debug this somehow?

Hey @igracia 👋🏻
Thanks for taking this code out for a spin 🚗 Much appreciated! 👏🏻
We are actively looking into the errors you've reported, and I'll let you know if we could use some further support from you 🙇🏻

@immavalls @igracia I have pushed some changes to the branch which address the issues related to the tests failing. It should at least work as intended on that front now 👍🏻 Could you please take it out for a spin and let me know if it works for you? 🙏🏻 🙇🏻

Thanks for the quick response! Gave it another go and got a somewhat different error
DEBU[0001] Starting executor run...                      executor=per-vu-iterations iterations=1 maxDuration=10m0s scenario=default type=per-vu-iterations vus=1
ERRO[0003] Exception raised in test "03. publish to kinesis Stream". Failing the test and continuing.
GoError: Error: Either streamName or streamARN must be provided  source=console
ERRO[0003] Exception raised in test "05. Gets an Amazon Kinesis read all data ". Failing the test and continuing.
GoError: KinesisServiceError: Invalid message body: Could not decode JSON: {
  "StreamName" : "traces",
  "ShardId" : null,
  "ShardIteratorType" : "TRIM_HORIZON"
}  source=console
DEBU[0003] Regular duration is done, waiting for iterations to gracefully finish  executor=per-vu-iterations gracefulStop=30s scenario=default
DEBU[0003] Executor finished successfully                executor=default startTime=0s type=per-vu-iterations
DEBU[0003] teardown() is not defined or not exported, skipping!
DEBU[0003] Test finished cleanly
DEBU[0003] Stopping vus and vux_max metrics emission...  phase=execution-scheduler-init
DEBU[0003] Metrics emission of VUs and VUsMax metrics stopped
DEBU[0003] Releasing signal trap...
DEBU[0003] Sending usage report...
DEBU[0003] Waiting for metric processing to finish...
DEBU[0003] Metrics processing finished!
DEBU[0003] Stopping outputs...
DEBU[0003] Stopping 1 outputs...                         component=output-manager
DEBU[0003] Stopping...                                   component=metrics-engine-ingester
DEBU[0003] Stopped!                                      component=metrics-engine-ingester
DEBU[0003] Generating the end-of-test summary...

     █ 01. List Kinesis streams

       ✓ expected number of streams to equal 1

     █ 02. List kinesis stream with arguments

       ✓ expected number of streams to equal 1

     █ 03. publish to kinesis Stream

       ✗ Exception raised "GoError: Error: Either streamName or streamARN must be provided"
        ↳  0% — ✓ 0 / ✗ 1

     █ 05. Gets an Amazon Kinesis read all data

       ✗ Exception raised "GoError: KinesisServiceError: Invalid message body: Could not decode JSON: {
  "StreamName" : "traces",
  "ShardId" : null,
  "ShardIteratorType" : "TRIM_HORIZON"
}"
        ↳  0% — ✓ 0 / ✗ 1

I'm running the tests against a localstack dokcer container, which is where I guess the Invalid message body: Could not decode JSON comes from. However, it's reporting a GoError: Error: Either streamName or streamARN must be provided that I can see there. Thoughts?

LGTM! I'm having some issues with base64 encoding of protobuf data, but t's not related to this PR.


Notion's "Timeline - Inline" cannot be presented correctly here

Hey @JankinShaw, welcome 👋
This is a feature request for https://github.com/NotionX/react-notion-x which doesn't support timeline views at the moment.
Please create a separate issue over there to track support.
Thanks!


1.14.7 dev torv3 70 13191

https://github.com/dogecoin/dogecoin/pull/3162/commits/7b37aac9c16f471741205ec3f5b06b664c2913e3

Hi. This is not intended to be opened up against 1.14.7-dev in it's totality if at all. May I ask what your prerogative is with this?


rcc: Correct apb1_freq and apb2_freq calculations.

As per the Reference Manual Clock Tree (figure 17), these frequencies are divided from ahb_freq (HCLK) not sys_clk (SYSCLK).

Thanks for all your work maintaining this crate!

Wow, nice find! Thank you :)

From what I can tell, the affected peripherals are:

All TIMx, LPTIMx, and HRTIM1 timers
All UARTs and I2Cx depending on clock source

@usbalbin Thanks for the quick review and merge!
FDCAN is affected as well (that's how I ran into it.) FDCAN can select its clock from multiple sources, but currently the HAL sets it to PCLK1.


Fix #456

Fixes #456 by introducing a clone function that also copies select values instead of using cloneNode(true).

@NickolasBoyer - I have checked this out and it looks like it works very well. Can you add radio inputs as well?


Allow creating layers at a given position

This PR changes things so that map.createCartoDBLayer, map.createTorqueLayer, etc. accept at option to specify where the position where the layer should be inserted. Orders are automatically re-assigned here. Also refactored the method that assign indexes a bit.
@viddo would you please take a look? thx!

Looks legit 👍

Thanks!


Datagrid iterator updates

Now keys(), LinearIndices(), CartesianIndices(), and eachindex() have been defined for RealSpaceDataGrid.

Gonna need to force push because I started this branch on next instead of dev


WSL2 adb push large file cause BSOD

Version
Microsoft Windows [Version 10.0.19044.2006]
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>-microsoft-standard-WSL2
Distro Version
Ubuntu 20.04
Other Software
usbipd version in Windows: 2.4.0
usbip version in WSL2: usbip (usbip-utils 2.0)
VirtualBox in Windows: 6.1.36
Repro Steps
1.connect device to windows USB port
2.switch device to adb mode
3.usbipd wsl list can show the adb device in windows
4.usbipd wsl attach -b x-x to attach adb device to WSL2
5.in WSL lsusb can show newly attached  adb device
6.try to adb push files to device

one single large file (e.g. 1G), windows BSOD with code SYSTEM_PTE_MISUSE
multiple small files (e.g. 20M), when pushing the 16th file, windows BSOD with code SYSTEM_PTE_MISUSE

Expected Behavior
No BSOD happened when using adb push in WSL
Actual Behavior
windows BSOD with code SYSTEM_PTE_MISUSE
Diagnostic Logs
No response

Assuming you have Watson enabled dumps will go there and in the hands of the kernel team for them to investigate.


get-all not working with compound indexes

Hi,
I can create a compound index, but the get-all is not returning the correct values.   the get-all via a python command on the server works. Am I doing something wrong with how I pass in the key value list?
;
; CREATE INDEX
;
(...(:index-create (:table "cities")
"citiesndx2"
:function (r:fn (profile) (list (:attr profile "Region") (:attr profile "City"))))))
;
; TEST VIA PYTHON ON SERVER
;  This works

con = r.connect("localhost", 28015).repl()

t = r.rb("crunchbase").table("cities")
t.get_all(["05","copainala"],index="citiesndx2").count().run(con)
1

;
; TEST VIA LISP
; No Results
(..... (:get-all (:table "cities") (list "05" "copainala") :index "citiesndx2")))

get-all takes a list of index values (in an actual list, not in &rest form). It's set up this way because it's really hard for CL to support both &rest and &key (which get-all uses), so it replaces the &rest part with an actual list.
I think doing
(..... (:get-all (:table "cities") (list (list "05" "copainala")) :index "citiesndx2")))

may solve your problem.
Can you confirm?

Thanks. That worked.  Issue solved.


AssertionError: HappyPack[1]: Loader must have a @path property or be a string.

var path = require('path');
var HappyPack = require('happypack')

module.exports = {
  entry: path.resolve(__dirname, 'a.js'),

  output: {
    path: path.resolve(__dirname, 'dist'),
    filename: '[name].js'
  },

  plugins: [
    new HappyPack({
      cache: process.env.HAPPY_CACHE === '1',
      loaders: [
          {
            test: /\.js$/,
            loader: 'babel',
            exclude: [/node_modules/]
          },
          {
            test: /\.json$/,
            loader: 'json-loader'
          }
      ],
      threads: 2
    })
  ],

  module: {
    loaders: [
      {
        test: /\.js$/,
        loader: 'happypack/loader',
      }
    ]
  }
}

Hi, so like the error says and the documentation states, what you have to specify inside HappyPack's loaders array is not the same as what you pass to webpack's loaders array. So your config has to be tuned as such:

  plugins: [
    new HappyPack({
      cache: process.env.HAPPY_CACHE === '1',
      loaders: ['babel'],
      threads: 2
    }),
    // and another for JSON
    new HappyPack({
      id: 'json',
      cache: process.env.HAPPY_CACHE === '1',
      loaders: ['json'],
      threads: 2
    })
  ],

  module: {
    loaders: [
      {
        test: /\.js$/,
        loader: 'happypack/loader?id=js',
        exclude: [ /node_modules/ ],
      }
    ]
  }

Please feel free to re-open if this still does not work for you.


possible to detect the type of defect?

Hi
possible to detect the type of defect? with anomaly detection
Thank you!

The models in the repo are more Out of Distribution models than classifiers, so no.


WHY ARE YOU NOT HONEST?? WHY?

You said wait 20 minutes and use port 39, Why ??? To finish injecting Backdoor scripts
NOT GOOD!!!!!  WHY???
PEOPLE! BE CAREFUL WITH THIS SCRIPT!!
Jul  3 21:08:41 localhost sshd[859]: pam_unix(sshd:session): session opened for user root by (uid=0)
Jul  3 21:08:41 localhost systemd-logind[545]: New session 3 of user root.
Jul  3 21:08:41 localhost systemd: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Jul  3 21:09:09 localhost useradd[1028]: new group: name=vps, GID=1000
Jul  3 21:09:09 localhost useradd[1028]: new user: name=vps, UID=1000, GID=1000, home=/home/vps, shell=/bin/sh, from=/dev/pts/1
Jul  3 21:09:10 localhost usermod[1094]: change user 'vps' password
Jul  3 21:09:10 localhost chage[1108]: changed password expiry for vps
Jul  3 21:09:10 localhost usermod[1129]: add 'vps' to group 'sudo'
Jul  3 21:09:10 localhost usermod[1129]: add 'vps' to shadow group 'sudo'
Jul  3 21:09:10 localhost useradd[1150]: new group: name=cendrawasih, GID=1001
Jul  3 21:09:10 localhost useradd[1150]: new user: name=cendrawasih, UID=1001, GID=1001, home=/home/cendrawasih, shell=/bin/sh, from=/dev/pts/1
Jul  3 21:09:10 localhost usermod[1158]: add 'cendrawasih' to group 'sudo'
Jul  3 21:09:10 localhost usermod[1158]: add 'cendrawasih' to group 'cendrawasih'
Jul  3 21:09:10 localhost usermod[1158]: add 'cendrawasih' to shadow group 'sudo'
Jul  3 21:09:10 localhost usermod[1158]: add 'cendrawasih' to shadow group 'cendrawasih'
Jul  3 21:12:02 localhost sudo: pam_unix(sudo:session): session opened for user root by root(uid=0)
Jul  3 21:12:02 localhost sudo: pam_unix(sudo:session): session closed for user root
Jul  3 21:12:18 localhost sudo:     root : TTY=pts/1 ; PWD=/tmp ; USER=root ; COMMAND=/usr/bin/apt update
Jul  3 21:12:18 localhost sudo: pam_unix(sudo:session): session opened for user root by root(uid=0)
Jul  3 21:12:20 localhost sudo: pam_unix(sudo:session): session closed for user root
Jul  3 21:12:20 localhost sudo: pam_unix(sudo:session): session opened for user root by root(uid=0)
Jul  3 21:13:01 localhost groupadd[4486]: group added to /etc/group: name=stunnel4, GID=117
Jul  3 21:13:01 localhost groupadd[4486]: group added to /etc/gshadow: name=stunnel4
Jul  3 21:13:01 localhost groupadd[4486]: new group: name=stunnel4, GID=117
Jul  3 21:13:01 localhost useradd[4492]: new user: name=stunnel4, UID=114, GID=117, home=/var/run/stunnel4, shell=/usr/sbin/nologin, from=/dev/pts/2
Jul  3 21:13:01 localhost chage[4500]: changed password expiry for stunnel4
Jul  3 21:13:02 localhost groupadd[4600]: group added to /etc/group: name=_chrony, GID=118
Jul  3 21:13:02 localhost groupadd[4600]: group added to /etc/gshadow: name=_chrony
Jul  3 21:13:02 localhost groupadd[4600]: new group: name=_chrony, GID=118
Jul  3 21:13:02 localhost useradd[4606]: new user: name=_chrony, UID=115, GID=118, home=/var/lib/chrony, shell=/usr/sbin/nologin, from=/dev/pts/2
Jul  3 21:13:02 localhost usermod[4614]: change user '_chrony' password
Jul  3 21:13:02 localhost chage[4621]: changed password expiry for _chrony
Jul  3 21:13:02 localhost chfn[4625]: changed user '_chrony' information
Jul  3 21:13:08 localhost groupadd[5492]: group added to /etc/group: name=ssl-cert, GID=119
Jul  3 21:13:08 localhost groupadd[5492]: group added to /etc/gshadow: name=ssl-cert
Jul  3 21:13:08 localhost groupadd[5492]: new group: name=ssl-cert, GID=119
Jul  3 21:13:12 localhost groupadd[5785]: group added to /etc/group: name=vnstat, GID=120
Jul  3 21:13:12 localhost groupadd[5785]: group added to /etc/gshadow: name=vnstat
Jul  3 21:13:12 localhost groupadd[5785]: new group: name=vnstat, GID=120
Jul  3 21:13:12 localhost useradd[5791]: new user: name=vnstat, UID=116, GID=120, home=/var/lib/vnstat, shell=/usr/sbin/nologin, from=/dev/pts/2
Jul  3 21:13:12 localhost usermod[5799]: change user 'vnstat' password
Jul  3 21:13:12 localhost chage[5806]: changed password expiry for vnstat
Jul  3 21:13:12 localhost chfn[5810]: changed user 'vnstat' information
Jul  3 21:13:21 localhost groupadd[6955]: group added to /etc/group: name=msmtp, GID=121
Jul  3 21:13:21 localhost groupadd[6955]: group added to /etc/gshadow: name=msmtp
Jul  3 21:13:21 localhost groupadd[6955]: new group: name=msmtp, GID=121
Jul  3 21:13:21 localhost useradd[6961]: new user: name=msmtp, UID=117, GID=121, home=/var/lib/msmtp, shell=/usr/sbin/nologin, from=none
Jul  3 21:13:21 localhost usermod[6969]: change user 'msmtp' password
Jul  3 21:13:21 localhost chage[6976]: changed password expiry for msmtp
Jul  3 21:13:40 localhost sudo: pam_unix(sudo:session): session closed for user root
Jul  3 21:13:40 localhost sudo:     root : TTY=pts/1 ; PWD=/tmp ; USER=root ; COMMAND=/usr/bin/apt-get autoremove -y
Jul  3 21:13:40 localhost sudo: pam_unix(sudo:session): session opened for user root by root(uid=0)
Jul  3 21:13:42 localhost sudo: pam_unix(sudo:session): session closed for user root
Jul  3 21:15:01 localhost CRON[27924]: pam_unix(cron:session): session opened for user root by (uid=0)
Jul  3 21:15:01 localhost CRON[27924]: pam_unix(cron:session): session closed for user root
Jul  3 21:15:11 localhost useradd[28036]: new group: name=rclone, GID=1002
Jul  3 21:15:11 localhost useradd[28036]: new user: name=rclone, UID=1002, GID=1002, home=/home/rclone, shell=/bin/sh, from=none
Jul  3 21:15:11 localhost usermod[28047]: change user 'rclone' password
Jul  3 21:15:11 localhost usermod[28054]: add 'rclone' to group 'sudo'
Jul  3 21:15:11 localhost usermod[28054]: add 'rclone' to shadow group 'sudo'
Jul  3 21:15:11 localhost chage[28061]: changed password expiry for rclone
Jul  3 21:15:13 localhost useradd[28129]: new group: name=taibabi, GID=1003
Jul  3 21:15:13 localhost useradd[28129]: new user: name=taibabi, UID=1003, GID=1003, home=/home/taibabi, shell=/bin/sh, from=none
Jul  3 21:15:13 localhost usermod[28140]: change user 'taibabi' password
Jul  3 21:15:13 localhost usermod[28147]: add 'taibabi' to group 'sudo'
Jul  3 21:15:13 localhost usermod[28147]: add 'taibabi' to shadow group 'sudo'
Jul  3 21:15:13 localhost chage[28154]: changed password expiry for taibabi
Jul  4 04:17:11 localhost dropbear[710]: Running in background
Jul  4 04:17:11 localhost systemd-logind[642]: New seat seat0.
Jul  4 04:17:11 localhost systemd-logind[642]: Watching system buttons on /dev/input/event0 (Power Button)
Jul  4 04:17:11 localhost systemd-logind[642]: Watching system buttons on /dev/input/event1 (AT Translated Set 2 keyboard)
Jul  4 04:17:12 localhost sshd[833]: Server listening on <IP_ADDRESS> port 3939.
Jul  4 04:17:12 localhost sshd[833]: Server listening on :: port 3939.
Jul  4 04:17:12 localhost sshd[833]: Server listening on <IP_ADDRESS> port 39.
Jul  4 04:17:12 localhost sshd[833]: Server listening on :: port 39.
Jul  4 04:25:01 localhost CRON[914]: pam_unix(cron:session): session opened for user root by (uid=0)
Jul  4 04:25:01 localhost CRON[914]: pam_unix(cron:session): session closed for user root
Jul  4 04:25:16 localhost sshd[925]:
WHY???? WHY??? WHY????
VERY BAD!!!

lmao. thanks for checking this script.
i just editing from someone else and add some tweaking. preferred rclone script, i not and never touch rclone script.
if you got some another backdoor, you can pull request or i will patch another time

@ollyt3st fixed. you can check it. if any backdoor or anything like this. tell me.

Hi there,
do you have telegram we can chat and i show you some errors, like all xray shows offline. and the backdoors are still there..
thanks


JS Interop exception (Blazor server app)

Bug type
Component
Component name
MudDrawer, MudHidden
What happened?
We are seeing a lot of java script errors and we are not sure what is causing them however I think it is related to this issue: https://github.com/MudBlazor/MudBlazor/issues/3327.
MudDrawer error:
Unhandled exception rendering component: JavaScript interop calls cannot be issued at this time. This is because the circuit has disconnected and is being disposed.
 Microsoft.JSInterop.JSDisconnectedException: JavaScript interop calls cannot be issued at this time. This is because the circuit has disconnected and is being disposed.
   at Microsoft.AspNetCore.Components.Server.Circuits.RemoteJSRuntime.BeginInvokeJS(Int64 asyncHandle, String identifier, String argsJson, JSCallResultType resultType, Int64 targetInstanceId)
   at Microsoft.JSInterop.JSRuntime.InvokeAsync[TValue](Int64 targetInstanceId, String identifier, CancellationToken cancellationToken, Object[] args)
   at Microsoft.JSInterop.JSRuntime.InvokeAsync[TValue](Int64 targetInstanceId, String identifier, Object[] args)
   at MudBlazor.BrowserViewportService.GetCurrentBrowserWindowSizeAsync()
   at MudBlazor.BrowserViewportService.SubscribeAsync(IBrowserViewportObserver observer, Boolean fireImmediately)
   at MudBlazor.MudDrawer.OnAfterRenderAsync(Boolean firstRender)
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task taskToHandle, ComponentState owningComponentState)

MudHidden error:
Microsoft.JSInterop.JSDisconnectedException: JavaScript interop calls cannot be issued at this time. This is because the circuit has disconnected and is being disposed.
   at Microsoft.AspNetCore.Components.Server.Circuits.RemoteJSRuntime.BeginInvokeJS(Int64 asyncHandle, String identifier, String argsJson, JSCallResultType resultType, Int64 targetInstanceId)
   at Microsoft.JSInterop.JSRuntime.InvokeAsync[TValue](Int64 targetInstanceId, String identifier, CancellationToken cancellationToken, Object[] args)
   at Microsoft.JSInterop.JSRuntime.InvokeAsync[TValue](Int64 targetInstanceId, String identifier, Object[] args)
   at MudBlazor.BrowserViewportService.GetCurrentBrowserWindowSizeAsync()
   at MudBlazor.BrowserViewportService.SubscribeAsync(IBrowserViewportObserver observer, Boolean fireImmediately)
   at MudBlazor.MudHidden.OnAfterRenderAsync(Boolean firstRender)
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task taskToHandle, ComponentState owningComponentState)

Expected behavior
There would be no errors
Reproduction link
https://github.com/MudBlazor/MudBlazor/issues/3327
Reproduction steps

...
Relevant log output
No response
Version (bug)
6.12.0
Version (working)
No response
What browsers are you seeing the problem on?
Chrome
On what operating system are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi.
Please, add a reproduction, either a trymudblazor or if it's not possible to replicate it there, then make a reproduction repository with your project and link it, or upload a .zip.
You linking https://github.com/MudBlazor/MudBlazor/issues/3327 as reproduction, but first of all this is an very old issue with an very old version and it doesn't have any reproduction either.

I'll try and see if i can put something together soon

Also. What type of project is this? Is this a new net8 webapp with the prerendering enabled? This can explain the error

Also. What type of project is this? Is this a new net8 webapp with the prerendering enabled? This can explain the error

.net 7, server pre rendered.  I had issues getting mudblazor working with .net 8 so i gave up on that for now.

is there a way to get notified when this is released?

You can watch the repository and configure (via arrow) to get release notification, also via discord in the #news-feed channel.

is there a way to get notified when this is released?

You can watch the repository and configure (via arrow) to get release notification, also via discord in the #news-feed channel.

Thanks so much, you have been incredibly helpful.


Fixing Acceptable  Prop Type in Docs

<Route> does not currently accept an array of paths, only a single one.
Also acknowledged by a @pshrmn: https://github.com/ReactTraining/react-router/issues/6270#issuecomment-408534917
cc @mjackson

This is correct. It was added in #5889. This is in the 4.4 betas.


Ability to run multiple sockets with multiple apps

Hi team 👋
I'm attempting to run two different slack bots in the same container. This is an example of how I'm doing so:
# creating an instance of the Slack app
app1 = App(token=TOKEN_1, signing_secret=SIGNING_SECRET_1)

# creating an instance of MyBot1 and registering its event handlers
my_bot_1 = MyBot1(app1)
my_bot_1.register_event_handlers()

# creating an instance of the other Slack app
app2 = App(token=TOKEN_2, signing_secret=SIGNING_SECRET_2)

# creating an instance of MyBot1 and registering its event handlers
my_bot_2 = MyBot2(app2)
my_bot_2.register_event_handlers()

# Starting the apps
handler1 = SocketModeHandler(app1, APP_TOKEN_1)
handler1.start()
logging.info("started bot1!")

handler2 = SocketModeHandler(app2, APP_TOKEN_2)
handler2.start()
logging.info("started bot2!")

The idea is that I would be able to have both apps running simultaneously, on the same container. However, when I try this, it looks like app number 2 is not connecting at all. It looks like app number 1 is connecting.
Weirdly, I looked in logs and am seeing only 1 log of "Bolt app is running", but neither message for "started bot1!" nor "started bot2!".
Is this a possible functionality, or do I need to have these apps start separately?

Nevermind, I solved this by doing something like this:
handler1 = SocketModeHandler(app1, APP_TOKEN_1)
handler1.connect()
logging.info("started bot1!")

handler2 = SocketModeHandler(app2, APP_TOKEN_2)
handler2.connect()
logging.info("started bot2!")

Event().wait()

^ it is crucial to do an Event().wait() or even a while(true) sleep, to keep the bots running


Fixes #5 updating _f5.py to b9019679a94d69821f6fe4b1f4c6594ca7fbf418

Problem:
marathon's 1.0-stable's _f5.py file was not committed in its current
version in a master branch commit
Analysis:
This incorporates the current version of _f5.py for marathon's
1.0-stable
Tests:
None

@andrewjjenkins @richbrowne @michaeldayreads
The tasks performed:

git reset to e0c0fcb89ac76a50ca2c6138fd591b1b27523e95
Created separate branch for marthon-k8s-1.0 and pushed to f5-cccl as a new branch
Created this pull request with the change for marathon/k8s's _f5.py file

I show these _f5.py and common.py as exactly matching what's in the 1.0-stable branch of marathon-bigp-ctlr
0 ajenkins@BLD-ML-JENKINS:~/velcro/f5-cccl$ git show upstream/pr/16:f5_cccl/_f5.py | shasum
0321296abcd6b254bb44ab0e50d3135ff33f6145  -
0 ajenkins@BLD-ML-JENKINS:~/velcro/f5-cccl$ git show upstream/pr/16:f5_cccl/common.py | shasum
6c1024f355c68ebaf9a94f8322ea2b1eca1ade33  -

0 ajenkins@BLD-ML-JENKINS:~/velcro/marathon-bigip-ctlr$ git show upstream/1.0-stable:_f5.py | shasum
0321296abcd6b254bb44ab0e50d3135ff33f6145  -
0 ajenkins@BLD-ML-JENKINS:~/velcro/marathon-bigip-ctlr$ git show upstream/1.0-stable:common.py | shasum
6c1024f355c68ebaf9a94f8322ea2b1eca1ade33  -

Looks good to me!


模板

In what area(s)?

/area runtime
/area operator
/area placement
/area docs
/area test-and-release

What version of Dapr?

0.1.x
0.2.x
Output of git describe --dirty

Expected Behavior

Actual Behavior

Steps to Reproduce the Problem

Release Note

RELEASE NOTE:

@viv718918 Can you elaborate on this issue?

In what area(s)?

/area runtime
/area operator
/area placement
/area docs
/area test-and-release

What version of Dapr?

0.1.x
0.2.x
Output of git describe --dirty

Expected Behavior

Actual Behavior

Steps to Reproduce the Problem

Release Note

RELEASE NOTE:


Improve spec helpers, prepare for compiler specs on Windows

I extracted self-contained parts of #9348 so that this is easier to review

the compiler-specific parts of spec/spec_helper.cr should be moved to spec/compiler/spec_helper.cr.
This PR as-is makes the stdlib spec suite require the compiler source.

It's not compiler-specific, it's for pending_win32. Gotta come up with something else then.

Yeah this is better. Instead of moving it to the top level spec_helper and switching files to use it, I move it to a file that is then required by both spec_helpers

Please review

@oprypin this PR is in conflict with master now. Other than that LGTM.

third merge is the charm?


Need to help

I'm Vietnam Student's .How can i contact you ?

yeah you can cotact me on gmail : my gmail is<EMAIL_ADDRESS>What is your issue... Please mention.. I will try to solve your issue as soon as possible.


fix: Content set hold rendering until upgrade, prefixed attribute support for overflow property in cards

1.3.2 patch

Content set cascading attributes patch from issue found on dotcom
Added back fallback styles for pfe-overflow prefixed attributes (not a property on host so needs to be backwards compatible on the scss level)

Preview
Link(s) to demo page(s) where this element can be viewed:

Content-set demo
Card demo
(If you have Red Hat VPN access): https://web-dev-drupal-carobert.dev.a1.vary.redhat.com/en/demo-accordions-and-tabs-pattern

Testing instructions

Check that the attributes on the demo page cascade to the rendered component: demo page

vertical (tabs)
selected-index (tabs)
align (tabs)
variant (tabs)
tab-history (tabs)
disclosure (accordion)

Check that the overflow images fill the card: Card demo

Browser requirements
Your component should work in all of the following environments:

[x] Latest 2 versions of Edge
[x] Internet Explorer 11 (should be useable, not pixel perfect)
[x] Latest 2 versions of Firefox (one on Mac OS, one of Windows OS)
[x] Firefox 68 (or latest version for Red Hat Enterprise Linux distribution)
[x] Latest 2 versions of Chrome (one on Mac OS, one of Windows OS)
[x] Latest 2 versions of Safari
[x] Android mobile device (such as the Galaxy S9)
[x] Apple mobile device (such as the iPhone X)
[x] Apple tablet device (such as the iPhone Pro)

Ready-for-merge Checklist

[x] Expected files: all files in this pull request are related to one request or issue (no stragglers or scope-creep).
[ ] Tests have been updated to cover these changes.
[x] Browser testing passed.
[x] Repository compiles and tests pass.
[x] Changelog updated.

Merging
Please squash when merging and ensure your commit message uses conventional commit formatting.
Be sure to share your updates with the<EMAIL_ADDRESS>mailing list!

Re: Do we still need the default slot in the shadowdom now that we are copying items from the lightdom into the "_view" slot?
We definitely do.  The default slot is how we're hiding the light DOM content being passed into the component and the _view slot is how we're showing only the rendered upgrade.  We need to maintain our default slot so you can dynamically add components to pfe-content-set on the fly and they will be reflected into the rendered component.

Yep that makes sense.  LGTM!!!


Rename all test files to the style: '***.test.js'

jest & ava supports __tests__/**/*.(spec|test).js style.
I think its way is more common style for today's JS code.

This change is

bors r+