text:
fixed images height

Fixed images height (stretching problem)

Hey @mahakmakharia I've fixed the image stretching problem in events page.


text:
DSC_Disk: Add dev drive creation support to disk resource

Pull Request (PR) description
This PR adds Dev Drive creation support and the ability to explicitly use unallocated space to create a new partition even when there is a partition with the same size as the one the user enters in.
This Pull Request (PR) fixes the following issues

Fixes #276

Task list

[ x] Added an entry to the change log under the Unreleased section of the
file CHANGELOG.md. Entry should say what was changed and how that
affects users (if applicable), and reference the issue being resolved
(if applicable).
[ x] Resource documentation added/updated in README.md.
[ x] Resource parameter descriptions added/updated in README.md, schema.mof
and comment-based help.
[ x] Comment-based help added/updated.
[x ] Localization strings added/updated in all localization files as appropriate.
[ ] Examples appropriately added/updated.
[x ] Unit tests added/updated. See DSC Community Testing Guidelines.
[ ] Integration tests added/updated (where possible). See DSC Community Testing Guidelines.
[x ] New/changed code adheres to DSC Community Style Guidelines.

This change is

@PlagueHO any update on this and #279 ?

Thanks @PlagueHO  I'll update the PR based on your suggestions

Sorry about the delay @bbonaby - I'll get back to your comments in the weekend.

Hey @PlagueHO  I plan on updating this PR today. If possible would you be able to hold off until I update it? I've gotten rid of the 'UseUnallocatedSpace' and would like you to take a look at a different approach I did without needing that flag. Thanks

@PlagueHO any update on this? Thanks

Hi @bbonaby - apologies, day job has been taking up all my bandwidth. Planning to have time for this tomorrow night.

Thanks @PlagueHO  I updated the PR and addressed your comments.

source/DSCResources/DSC_Disk/DSC_Disk.psm1 line 1099 at r4 (raw file):
Previously, PlagueHO (Daniel Scott-Raynsford) wrote…
Should we separate this out into a common function? E.g., a "Compare-PartitionSizeUsingGB" - or something? This is also because the same functionality is used in Set as well.

I created a generic function called Compare-SizeUsingGB so we could reuse the same functionality here. Thanks

source/DSCResources/DSC_Disk/DSC_Disk.psm1 line 402 at r4 (raw file):
Previously, PlagueHO (Daniel Scott-Raynsford) wrote…
Can this be?

Done.

@PlagueHO Thanks for the help with this, if you're all good with these latest changes, would it be possible to get this merged in today or tomorrow?

source: gharchive/pull-request

authors: PlagueHO bbonaby

repo: dsccommunity/StorageDsc

license: MIT

license_type: permissive

license_source: github-api


text:
Verify windows binaries

I have not verified that the windows binaries (from travis-ci) actually work, since I don't have a windows machine.

Tried out the windows release with a Falcon 8 v1.  It runs fine and says it wrote bytes, but nothing appears to have changed after resetting.

Does not even run for me.

source: gharchive/issue

authors: 10011 atom-sgt dshahbaz

repo: dshahbaz/myfalcon


text:
Update default configuration value for PAUSE_WHEN_EMPTY

I created a server with caves and noticed that the game ran when paused.  I needed to explicitly set PAUSE_WHEN_EMPTY to true to disable this.

Thanks a lot for your contribution! :)

authors: CaptEmulation thasmo

repo: dst-academy/docker-dontstarvetogether

license: mit

license_source: bigquery


text:
Mods are not installed properly

When starting the server, the console shows some error:
Download server mod 492173795
Could not open directory [../mods/workshop-492173795] 2 (/var/lib/steam/DoNotStarveTogether/data)
Failed to create mod folder [../mods/workshop-492173795]. Sleep and try again...

Mods can't be written to disk.

ARG! We need a test suit >_<! To fix this issue we just need to add dsta user to the steam group, I think.

Does this problem indicate that using two users is not ideal, or not?

Yes, I think that too. Work with groups seems a bit too much.

So, I propose to keep the steam user for doing all the stuff. We could migrate all files to /var/lib/steam/.

authors: BraisGabin thasmo

repo: dst-academy/server


text:
Fixes #301 and some other issues

in pygam.GAM._modelmat added selection of features, edge_knots and dtypes by term so only the necessary features are checked and features for factor terms can be set to 0 or 1 if another term is being checked
in pygam.GAM._flatten_mesh added two lines that set by feature to 1 if not None. This fixes issue of partial dependence of tensor terms being 0 everywhere if by feature is present
in pygam.GAM.partial_dependence removed check_X as right after it is checked in self._modelmat
updated docstring of pygam.GAM._linear_predictor
removed line that does nothing in terms.SplineTerm.build_column

This should fix the problem in #301 and some others that #302 might not, e.g. I believe it might break due to factor feature being set to 1.0 if it is a by feature in another term. Along the way found that by feature in tensor term is not set to 1 anywhere so partial dependence returns all 0. As _meshgrid seems to be written specifically for partial_dependence and generate_X_grid made it set by feature to 1 if not None.

looks good to me

authors: kdergachev nickcorona

repo: dswah/pyGAM


text:
Design Homepage

https://projects.invisionapp.com/d/main#/console/10281573/226534524/preview

On va dire que c'est bon. Pour la suite : #157

authors: DavidBruant reunono

repo: dtc-innovation/dataviz-finances-gironde


text:
Rework docs to work with demo data

Current docs makes assumptions about non-existing demo data. Should work with the data provided by dtcc-download-demo-data.

@jensoolsson Is this done now? Does the viewing work out of the box with the demo data?
I noticed one thing which is that the path is set to
../data/helsingborg-residential-2022

In the rest of the docs it's simply
data/helsingborg-residential-2022

repo: dtcc-platform/dtcc-viewer


text:
Connection timed out

started librespot with sudo /usr/bin/librespot --cache /tmp/ -n "raspotify" --verbose --username *** --password ***
INFO:librespot: librespot (raspotify) 8e0d758 (2018-02-26). Built on 2018-02-26. Build ID: U2Bp36G1
DEBUG:librespot_connect::discovery: Zeroconf server listening on 0.0.0.0:0
INFO:librespot_core::session: Connecting to AP "guc3-accesspoint-b-5xpp.ap.spotify.com:4070"
thread 'main' panicked at 'called Result::unwrap() on an Err value: Error { repr: Os { code: 110, message: "Connection timed out" } }', /checkout/src/libcore/result.rs:916:5
stack backtrace:
0:   0x86f057 -
1:   0x8792bb -
2:   0x8678d7 -
3:   0x8673b3 -
4:   0x867d83 -
5:   0x867bcb -
6:   0x867b53 -
7:   0x867afb -
8:   0x8d0bcf -
9:   0x449007 -
10:   0x453fd3 -
11:   0x44c4ef -
12:   0x464e5b -
13:   0x455973 -
14:   0x4658e3 -
15:   0x867a2b -
16:   0x88e65b -
17:   0x86ece3 -
18:   0x456453 - main
19: 0x76c95677 - __libc_start_main
any one else had this problem?!

I had the same issue, but after an upgrade to 0.10.4~librespot.20180226T171341Z.8e0d758 everything was working as normal again.

Upgrade and let me know if it works, @zamanisaja

authors: dtcooper ulijh zamanisaja

repo: dtcooper/raspotify


text:
Issue with [serde(untagged)], parsing for KaiTai crate

I'm a bit new to using the serde as well as the serde-yaml crates, but asking for some help with a small part of the https://doc.kaitai.io/user_guide.html parsing from yaml.
Example (rust playground link)
use serde::*;
use serde_yaml::*;
use std::collections::HashMap;

#[derive(Debug, PartialEq, Serialize, Deserialize)]
pub struct KaiTai {
    #[serde(rename = "type")]
    t: T,
}

#[derive(Debug, PartialEq, Serialize, Deserialize)]
#[serde(untagged)]
pub enum T {
    Type(String),
    Switch(Switch),
}

#[derive(Debug, PartialEq, Serialize, Deserialize)]
pub struct Switch {
    #[serde(rename = "switch-on")]
    switch_on: String,

    cases: HashMap<String, String>,
}

#[cfg(test)]
mod tests {
    use super::*;

    #[test]
    fn test_fails() {
        let s = r#"type:
    switch-on: rec_type
    cases:
        1: rec_type_1
"#;

        let kaitai: KaiTai = serde_yaml::from_str(&s).unwrap();

        let expected = KaiTai {
            t: T::Switch(Switch {
                switch_on: String::from("rec_type"),
                cases: HashMap::from([(String::from("1"), String::from("rec_type_1"))]),
            }),
        };
        assert_eq!(kaitai, expected);
    }

    #[test]
    fn test_passes() {
        let s = "type: u4";

        let kaitai: KaiTai = serde_yaml::from_str(&s).unwrap();

        let expected = KaiTai {
            t: T::Type(String::from("u4")),
        };
        assert_eq!(kaitai, expected);
    }
}

Test output
running 2 tests
test tests::test_passes ... ok
test tests::test_fails ... FAILED

failures:

---- tests::test_fails stdout ----
thread 'tests::test_fails' panicked at 'called `Result::unwrap()` on an `Err` value: Message("data did not match any variant of untagged enum T", Some(Pos { marker: Marker { index: 4, line: 1, col: 4 }, path: "." }))', src/lib.rs:38:55
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

failures:
    tests::test_fails

test result: FAILED. 1 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

Thanks for any help, I can't figure out how to do untagged parsers for these two different states. If there is a better place to ask this question lmk. Thanks.

The 1: in your yaml is deserialized as a number, so the deserialization fails when it tries to deserialize it into the cases: HashMap<String, String>,, since a number is not a String. Your example passes the tests when using a HashMap<i32, String>. The code work without the untagged, so this looks like another variants of serde-rs/serde#1183.
You could change the key type of the HashMap to something which works in both cases, for example an enum with a number and a string variant. Another option to solve this is to write custom deserialization code and use the with attribute of serde to call it.

The 1: in your yaml is deserialized as a number, so the deserialization fails when it tries to deserialize it into the cases: HashMap<String, String>,, since a number is not a String. Your example passes the tests when using a HashMap<i32, String>. The code work without the untagged, so this looks like another variants of serde-rs/serde#1183.

Thanks! I actually now just use the serde_yaml::Value, which correctly parses.

You could change the key type of the HashMap to something which works in both cases, for example an enum with a number and a string variant. Another option to solve this is to write custom deserialization code and use the with attribute of serde to call it.

I actually need the HashMap, since the real stuff actually has the following:
    fn test_fails() {
        let s = r#"type:
    switch-on: rec_type
    cases:
        1: rec_type_1
        2: rec_type_2
"#;

Thanks for the help!

repo: dtolnay/serde-yaml


text:
feature request: mode to not assert error messages

Inverse of https://github.com/dtolnay/trybuild/issues/55. Context: https://github.com/exercism/rust/pull/932.
For our use case, we want to test that arbitrary student macro implementations either successfully compile or fail to compile for a given input, but we really don't care about the particular error message. We don't want to require that students set an environment variable, and don't want to confuse them by generating the wip directory.
I'm willing to put some time into implementing this, if it seems like a plausible feature. My approach: add a new method to TestCases: assert_compile_fail. This function checks compilation status and succeeds or fails as a test case, but does not look for a *.stderr file.

Closing as per https://github.com/dtolnay/trybuild/pull/57#pullrequestreview-383342617.

authors: coriolinus dtolnay

repo: dtolnay/trybuild


text:
Fix remote staking bugs

We found three issues with remote staking when testing on the testnet.

Transaction picking might fail because of invalid coinbase transaction which sends remote-staking coins to non-remote staking script. That happened because transaction picking was via invoking BlockAssembler::CreateNewBlock. BlockAssembler::CreateNewBlock generates a coinbase transaction which sends the stake to the provided script and when it picks a remote-staking output it results in invalid coinbase transaction.
A node can generate invalid coinbase transaction which tries to combine remote-staking and non-remote-staking outputs and send them to a non-remote-staking script.
A node which has its own funds and remote staking funds can send its funds to remote staking script because of stake combining.

The first bug is fixed by introducing BlockAssembler::PickTransactions which only picks transactions and does not do an unnecessary job.
The second and the third bugs are fixed by disabling stake combination in BlockBuilder when staking a remote-staking coin and by skipping remote-staking coins in stake combination.

Should #998 be closed now?

authors: Nizametdinov cmihai

repo: dtr-org/unit-e


text:
results to stdin

as it is now, the results get saved to output.md.
there could be an option/flag to simply print the results/findings to stdin.
formatted or not (charmbracelet's glamour could be used if markdown pretty-printing was important), the output could then be piped to other tools easily.

Do you have a suggestion for the format to print? Is the way the output.md currently looks fine or would you optimize things so that it's easier to pipe to another program?

Do you have a suggestion for the format to print? Is the way the output.md currently looks fine or would you optimize things so that it's easier to pipe to another program?

Not really at the moment, it's just the fact that it'd be simply printed out. Did you have a specific use case for the file?
The correct output type (pretty or simple) could be auto-discerned by checking whether the output is a pipe or stdin (things like eza and bat do that).

I didn't have a specific use case for the file other than it being human-readable. I suppose I didn't anticipate that people might pipe the output to other tools because the process of verifying if the suggested domains are actually takeoverable is entirely manual at this point.

repo: dub-flow/subsnipe


text:
Check if output directory exists and is writable before starting

This is a small improvement request, but I've noticed that (on Windows at least) if the directory specified in the -output-dir parameter does not exist, a write error is printed (I guess) when trying to dump the first message:
Save message: open tmp/msg-0000: Cannot find the specified path

It would be better if a check of directory existence / writeability be done before even starting to process queue messages.

I see that standard Linux comands (cp) behave like this:
$ cp file1 file2 file3 /tmp/non-existing-dir/
cp: target '/tmp/non-existing-dir/' is not a directory

$ cp file1 file2 file3 /tmp/read-only-dir/
cp: cannot create regular file '/tmp/read-only-dir/file1': Permission denied
cp: cannot create regular file '/tmp/read-only-dir/file2': Permission denied
cp: cannot create regular file '/tmp/read-only-dir/file3': Permission denied

So the tool does check that the target is a directory, but doesn't check for permissions in it (which makes sense to me).
Do you expect a clearer error message when the output directory doesn't exist?

(inactive issue; closing.)

authors: dubek watery

repo: dubek/rabbitmq-dump-queue


text:
Add a polling option to have the ability to change the status manually

I'd like to be able to change the status of the pin from outside of homekit/homebridge but this plugin won't read that change. I know the wp2 plugin has a polling option, but it does not support lock type.
thanks!

plugin is based on wiringPi library - so you can read manual for it and can do what you need.

For what purpose do you use this plugin ? You would like to change the status of an output pin ?

I’m sorry... after giving it a little more thought changing what I was thinking wouldn’t work.
I have a smart lock which comes with a fob for locking/unlocking. One button only for both actions. I manage to wire it to the Pi and get it to work: when changing from HIGH (locked) to LOW (unlocked) it opens the door. When changing from LOW to HIGH it does nothing.
For mantaining the status consistently with the door: when the door closes I have an automation in homekit to lock the accesory (since it doesn’t do anything is ok).
The thing is when the door is opened manually: I can’t have it change in home kit since that would trigger the smart lock and actually lock it.
What I need is to change the status of the accesory without triggering any change to the pin....

Hi,
May my response not appropriate if my understanding not good but I try :-) :
As you are using the Pi as output, you can't expect to read the pin state as it is normaly driven by the Pi. More than that you can create a short-circuit if you fob is forcing LOW while Pi is forcing HIGH state.
But what you can do is configuring 2 devices in the plugin :

One for driving the Lock (LockMechanism)
One for sensing your fob (ContactSensor)
Then create a homekit automation to unlock when the fob switch and lock when the door closes.

The only "danger" with this option is in case of Pi issue. If not responding, you can't unlock.
What do you mean by "opened manually", is it with the fob or really with the hand ?

authors: Partizan7676 dubocr iandronowicz

repo: dubocr/homebridge-gpio-device


text:
DuckDB postgres scanner connecting to clickhouse

Can it support Clickhouse (which supports psql)?
CALL postgres_attach('postgresql://default:password#@ipaddress:9005/default')
I am happy to share some connection details if anyone is interested. In any case the response was very Clickhouse specific, per below. If I had to guess, DuckDB probes information_schema that Clickhouse in some peculiar way is not compatible with.
Any hope of debugging?
DB::Exception: Cannot convert string BASE TABLE to type UInt8: while executing 'FUNCTION equals(multiIf(is_temporary, 4, like(engine, '%View'), 2, like(engine, 'System%'), 5, equals(has_own_data, 0), 3, 1) : 19, 'BASE TABLE' : 13) -> equals(multiIf(is_temporary, 4, like(engine, '%View'), 2, like(engine, 'System%'), 5, equals(has_own_data, 0), 3, 1), 'BASE TABLE') UInt8 : 20'
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
ERROR:  Query execution failed.
DB::Exception: Cannot convert string BASE TABLE to type UInt8: while executing 'FUNCTION equals(multiIf(is_temporary, 4, like(engine, '%View'), 2, like(engine, 'System%'), 5, equals(has_own_data, 0), 3, 1) : 19, 'BASE TABLE' : 13) -> equals(multiIf(is_temporary, 4, like(engine, '%View'), 2, like(engine, 'System%'), 5, equals(has_own_data, 0), 3, 1), 'BASE TABLE') UInt8 : 20'
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.

Not sure what's going on there, but for now we depend on some postgres internals like the TID scan, I doubt ClickHouse has this too. Going forward, we may consider adding a single-threaded scan for anything that does not look like a Postgres base table (e.g. views)

authors: alanpaulkwan hannes


text:
When user tries to edit query by using the edit icon, modify the quer…

…y rather than do a new search.

Task/Issue URL: https://app.asana.com/0/1125189844152671/1185449784809161
Tech Design URL:
CC:
Description:
This PR changes the behaviour of the edit search icon in the system search. Right now when a user clicks on the icon it triggers a new search and the query input doesn't change . The purpose of the icon is to edit the query so the user can further edit it (as the app's omnibar behaves).
Steps to test this PR:

Add the app widget and open it.
Do a search
Click on the icon with an arrow in the right side of a search result.
It should change the query in the omnibar to the result selected and move the caret to the end.

Internal references:
Software Engineering Expectations
Technical Design Template

@malmstein, @subsymbolic I've put you both down for reviewing this small PR, there is no rush though. I think @subsymbolic is probably the best reviewer for this but I've added @malmstein as well in case you get a chance to have a look at it. Again, no rush, is just a small fix that was bothering me while on vacation :D.

@marcosholgado thanks for submitting this, I will review tomorrow.

@malmstein want me to reassign this PR review to you? Looks like you're already in there.

Yes @subsymbolic, happy to help!

Love the improvement @marcosholgado. Could we add a android:background="?selectableItemBackground" to the view? It's not clear that it's a clickable icon.

Nice improvement! I've added that change and updated the description to test that change as well 👍

authors: malmstein marcosholgado subsymbolic

repo: duckduckgo/Android


text:
Increase redirect loop detection timeout

Reviewer: @jdorweiler

Description:
Increases the redirect loop detection threshold to 3 seconds.
Steps to test this PR:

Open http://xe.com
Redirect loop shouldn't happen

Automated tests:

[ ] Unit tests
[ ] Integration tests

Reviewer Checklist:

[ ] Ensure the PR solves the problem
[ ] Review every line of code
[ ] Ensure the PR does no harm by testing the changes thoroughly
[ ] Get help if you're uncomfortable with any of the above!
[ ] Determine if there are any quick wins that improve the implementation

PR Author Checklist:

[ ] Get advice or leverage existing code
[ ] Agree on technical approach with reviewer (if the changes are nuanced)
[ ] Ensure that there is a testing strategy (and documented non-automated tests)
[ ] Ensure there is a documented monitoring strategy (if necessary)
[ ] Consider systems implications

👍

authors: andrey-p jdorweiler

repo: duckduckgo/duckduckgo-privacy-extension


text:
Add upgradeToSecure support for Firefox 59+

Reviewer: @jdorweiler

Description:

Mozilla released a fix in Firefox 59 for the http -> https upgrade cors errors we've been seeing. This PR implements the fix for Firefox 59+ users. Unfortunately, there doesn't appear to be a way to fix this issue in older versions of Firefox.
Steps to test this PR:

With privacy protection on, visit a site in Firefox 59+ that has been breaking due to cors error. That is, check an http site where we are upgrading child requests to https. I've been using http://www.thrashermagazine.com/ and http://www.balaodainformatica.com.br/ to test. The site should no longer be broken.
Repeat 1, using chrome. Site should be ok.
npm run test

Automated tests:

[ ] Unit tests
[ ] Integration tests

Reviewer Checklist:

[ ] Ensure the PR solves the problem
[ ] Review every line of code
[ ] Ensure the PR does no harm by testing the changes thoroughly
[ ] Get help if you're uncomfortable with any of the above!
[ ] Determine if there are any quick wins that improve the implementation

PR Author Checklist:

[ ] Get advice or leverage existing code
[ ] Agree on technical approach with reviewer (if the changes are nuanced)
[ ] Ensure that there is a testing strategy (and documented non-automated tests)
[ ] Ensure there is a documented monitoring strategy (if necessary)
[ ] Consider systems implications

👍

authors: dharb jdorweiler


text:
Fix styling

Feature/Change Description
Ran npm run style:fix
Developer Checklist

[ ] Updated documentation or README.md
[ ] If adding new feature(s), added and ran unit tests
[ ] If create new release, bumped version number
[ ] Ran npm run style:fix for code style enforcement
[ ] Ran npm run lint:fix for linting
[ ] Ran npm audit to discover vulnerabilities

Did this on master. Thanks @brendoncaulkins

authors: brendoncaulkins duluca

repo: duluca/local-weather-app


text:
Feature: Add flag for showing sizes as bytes

Hey really awesome work, gdu has been one of my go-to system info tools for a while now!
I often use gdu in non-interactive mode to quickly get file/dir sizes using gdu -nps, and it is super useful that gdu automatically converts sizes to the most appropriate prefix (KiB/MiB/GiB or kB/MB/GB using --si flag). But especially when scripting, I wish I could also have the option to output raw bytes to make it easier to do math/compare size values.
At present I have been using pretty hacky shell function to use gdu's --out-file flag combined with a weird and complicated jq statement on the output json but it would be really useful to be able to print raw byte sizes to the console with gdu itself. Admittedly it seems less useful in interactive mode, but I think still worth the effort for non-interactive use.
Any thoughts?

Hi, yes, it makes sense to add it to non-interactive mode. I will try to push it into the next release.

Hey thanks for the response glad you agree with the use case. I don't think I'm fluent enough in go to take a stab at it myself, but out of curiosity I might give it an hour of my best effort over the weekend and see how it goes. Certiainly looks like a pretty well-organized codebase so maybe implementing for stdout only won't be too complicated.
How would you prefer the usage design of a show raw bytes flag? It could be added as another boolean flag, but I'm not sure if that would then require some arg validation against coexisting with --si flag considering they would technically conflict in principle (but validation might be unnecessary for first implementation).
Another idea could be to introduce a --size-format <format> flag with possible values like binary|decimal|raw which would then consolidate this feature with the --si option. Seems like it would be a more significant change to gdu usage (would break scripts that use --si) but that might not a big deal to most users.

Nevermind, I guess a --size-format <format>  flag could still coexist with --si I'm probably overthinking it 🙃

I think we can just go with -b | --bytes to show the raw number of bytes it consumes. I would check if both --si and --bytes are given and print an error if so. What do you think?

Hi @dundee ,
I'm using v5.23.0, but I can't find -b or --bytes option.
Version:         v5.23.0
Built time:      Sat Apr  8 11:40:43 PM CEST 2023
Built user:      dundee

Pretty fast disk usage analyzer written in Go.

Gdu is intended primarily for SSD disks where it can fully utilize parallel processing.
However HDDs work as well, but the performance gain is not so huge.

Usage:
  gdu [directory_to_scan] [flags]

Flags:
      --config-file string            Read config from file (default is $HOME/.gdu.yaml)
  -g, --const-gc                      Enable memory garbage collection during analysis with constant level set by GOGC
      --enable-profiling              Enable collection of profiling data and provide it on http://localhost:6060/debug/pprof/
  -L, --follow-symlinks               Follow symlinks for files, i.e. show the size of the file to which symlink points to (symlinks to directories are not followed)
  -h, --help                          help for gdu
  -i, --ignore-dirs strings           Absolute paths to ignore (separated by comma) (default [/proc,/dev,/sys,/run])
  -I, --ignore-dirs-pattern strings   Absolute path patterns to ignore (separated by comma)
  -X, --ignore-from string            Read absolute path patterns to ignore from file
  -f, --input-file string             Import analysis from JSON file
  -l, --log-file string               Path to a logfile (default "/dev/null")
  -m, --max-cores int                 Set max cores that GDU will use. 48 cores available (default 48)
  -c, --no-color                      Do not use colorized output
  -x, --no-cross                      Do not cross filesystem boundaries
  -H, --no-hidden                     Ignore hidden directories (beginning with dot)
      --no-mouse                      Do not use mouse
      --no-prefix                     Show sizes as raw numbers without any prefixes (SI or binary) in non-interactive mode
  -p, --no-progress                   Do not show progress in non-interactive mode
  -n, --non-interactive               Do not run in interactive mode
  -o, --output-file string            Export all info into file as JSON
  -a, --show-apparent-size            Show apparent size
  -d, --show-disks                    Show all mounted disks
  -B, --show-relative-size            Show relative size
      --si                            Show sizes with decimal SI prefixes (kB, MB, GB) instead of binary prefixes (KiB, MiB, GiB)
  -s, --summarize                     Show only a total in non-interactive mode
  -v, --version                       Print version
      --write-config                  Write current configuration to file (default is $HOME/.gdu.yaml)

Hi @shanghungshih,
the option is called --no-prefix.

Thanks for the quick response! It works like a charm.

authors: dundee ev-dev shanghungshih

repo: dundee/gdu


text:
希望能同步更新autojs的版本

感谢开发者的付出！

看到已经更新了，谢谢！

看到已经更新了，谢谢！


text:
note import: make regex for parsing/replacing head more strict

Random usages of --------- somewhere inside the node can truncate the note body that is actually imported and stored inside the database.
The regex for replacing the metadata should be changed from
/^(---\n[^]*\n---)/
to
/^(---\n[^]*\n---\n)/
Reference code:
https://github.com/dungeon-revealer/dungeon-revealer/blob/677f4d3e54e10ec64fe2e6f27527311e8f80bc99/server/note-import.ts#L134-L139

As @maxb2 mentioned on discord it might even be better to use /^(---\n[^]*\n---\ *\n)/ to be a bit more forgiving with trailing whitespace.

repo: dungeon-revealer/dungeon-revealer

license: ISC


text:
ADR implementation, JSON-LD decoupling and content negociation support

Now uses a variation of the ADR pattern done with Symfony (I'll make a blog post about that soon)
There is no more coupling to JSON-LD and Hydra: the bundle can now output any format including but not limited to raw JSON, XML or HAL (I'll add an exemple of a custom XML serializer in the tests).
To complete the previous feature, I've added content negotiation capabilities using @willdurand's Negotiation library. (I'll add an exemple in tests too). It means that you can request various representations of the same resource using the Accept header (of course the requested format must be supported by one of the registered normalizer).

@pmjones do you think you can find some time to review this ADR implementation and tell me if it is in scope with the pattern you designed?

It looks great !
The ADR pattern is cool, but I'm glad you let the possibility to use Controllers classes outside (in a big application, ADR might be heavy, and has some drawbacks).

@dunglas, by implementing the ADR pattern you got rid of Controllers. I don't see the the big gain is this, can you explain plz ?

@dupuchba take a look at the link I mentioned in the description: https://github.com/pmjones/adr
General gains are:

Easier to unit test
Explicit dependencies
Better respect of the Single Responsibility Principle / smaller code units

Here, it comes with a bigger immediate gain: it makes it easy to decouple from JSON-LD and Hydra. Now you can return as format as you want with ApiBundle such as XML or Protobuf without touching the core.
And as @ogizanagi pointed, you can still use standard Symfony controllers for your userland code if you like.

Hi @dunglas -- looking at it now!

@pmjones thank you!
@ogizanagi thanks for the review, issues fixed.

Hi again @dunglas -- I gave it a quick 5-minute scan, and the only obvious "wrong" thing I saw was that a couple of actions do validation. My opinion is that validatiing/sanitizing of inputs is more properly a domain concern, not an action concern.
I was not able to see where the response actually gets built, but my guess is that it's part of the event dispatching system. As long as the action, domain, and responder portions are separated from each other, your work fits the pattern. As far as I can tell, this looks good!
p.s. Eventually, you're going to realize later that your actions all look the same: collect input (extract Request attributes to a ResourceType), retrieve a Domain result (get an Item from a DataProvider using the ResourceType), and pass the Domain result to a Responder (pass the Item to the EventDispatcher). At that point you'll be able to collect all the differences to a properties and/or injected dependencies, and the number of action classes will become greatly reduced (maybe even down to just 1 generic action class).

I was not able to see where the response actually gets built, but my guess is that it's part of the event dispatching system.

@pmjones : The response is indeed built in the ResponderViewListener

Thank you very much for the review and advices @pmjones!
I've trouble seing how to merge all actions in a single generic one. The process for all actions of the CRUD is a bit different. We can achieve this in a single class but it will lead to a large number of if/else  in the action (collection or item? read or write operation?...). In the end having separate classes for each using dependencies and traits for everything that can be factorized sounds better to me what do you think?

I've trouble seing how to merge all actions in a single generic one.

Right -- it's not an immediate goal to seek, it's something I think you are likely to notice over time, especially as you move more activity down into the domain layer, or over into the responder layer.

For those interested in content negotiation, I've just just a demo / test to the PR: https://github.com/dunglas/DunglasApiBundle/pull/191/files#diff-af37d9fff8b64adda0485128ebf627c1R1. It could be interesting to move the XML responder to the core or at least in a dedicated doc entry. What do you think?

@dunglas : Great ! I think it should go to a dedicated doc entry, but I don't feel it's needed in the core due to the bundle purpose at first (which is using JsonLd and Hydra).

The bundle has been renamed some times ago to reflect that it can support other formats (any format). Maybe that this XML support is too limited to be included in core but I don't exclude to add Turtle, RDF-XML, HAL, SIREN or Protobuf support for instance in the core. This not a problem because both can be used together thanks to content negotiation.

@dunglas I think it can be a huge success :-)

Right, but one step after another ;)
I think it is a very nice aim nonetheless. "ApiPlatform" would already a perfect name for this.

I am trying to be positive !!!

Two steps further:

Externalized the validation an event listener (allow to use another validator than the Symfony one and to validate data in the domain layer as suggested by @pmjones)
Consequence of 1: the custom event system is not necessary anymore. Everything can now be handled using standard Symfony kernel events (code simplification and more powerful than before). Only one drawback: the name of the Symfony event used (kernel.view) sounds a bit strange for that use but I can live with it.

ping @sroze @theofidry

Great work. For the even system it's not much so no problem, a little mention in the changelog is welcomed. I'll take a deeper look tomorrow to see what's going to change.

Nicely done. The Post and Put actions still look a little clunky to me, but whatever -- it's still an improvement. (I think you are starting to see what I meant earlier about "all your actions looking the same" -- Delete, GetCollection, and GetItem are very similar now. :-)

I don't like so much not having custom events dispatched directly in concerned actions:

We loose "accuracy". It's not as easy to identify the event and which action triggered it.
A newcomer will not easily understand that the controllerResponse is the resource item(s) where a getData method is simpler. Same with $event->getRequest()->attributes->get('_resource_type') and getResource.
ManagerViewListener and ValidationViewListener will always be called for userland actions (if we use the ADR pattern instead of controller classes). It might not always be wished. I think it also brings some kind of "magic" at this point.

I actually like the ManagerViewListener and ValidationViewListener idea, but if it relies on dunglas_api dedicated events. :/

@ogizanagi for point 1, a new comer can still php app/console debug:event-dispatcher which has been specifically dedicated for that.
Concerning the "magic" part of this, it's indeed a drawback of using listeners this way. We could always write a doc about "how things work" internally :-).

for point 1, a new comer can still php app/console debug:event-dispatcher which has been specifically dedicated for that.

Yes, but something like app/console debug:event-dispatcher api.pre_update is more accurate and obvious than app/console debug:event-dispatcher kernel.view.
However, we don't need as much events as before. A simple dunglas_api event might be sufficient.

I understand your concerns about readability but the custom event system as other drawbacks:

more code to maintain and test for no real reason
more chances to have bugs in that subsystem
performance decrease (more events dispatched and handled for no real reason)
native events are more powerful (they give access to the request and the response)

Validation and Doctrine are called every time but they return very early if they are not applicable (not the good HTTP method). It doesn't impact performance (at least less than dispatching a new event IMO).
For the readability / convenience issue I think that a doc with a pretty graphic will be better than a good name. We need the doc anyway even if we keep custom events.

:+1: with @dunglas on this, IMO, pros are quite thin to use a custom event system. Besides, as we said, if a user wants to see how things work internally we should help him with a nice doc on internals.

@pmjones: I got your point now and I tried to create an unique generic action. I just pushed it. Indeed it allows to avoid some code duplication. What do you think about it?

@dunglas:

I got your point now and I tried to create an unique generic action. I just pushed it. Indeed it allows to avoid some code duplication. What do you think about it?

This is a bit of a step backwards. The __invoke() method now does routing based on the request, and combines what should be separate actions. The rule-of-thumb in actions is that if you have a conditional (if or switch/case) the action is doing too much.
Remember the specific duties of the action: collect input, send input to a Domain layer, get back a Domain result, send the result to a Responder. Essentially, every action should look something like this:
$resourceType = $request->attributes->get('_resource_type');
$method = $this->domainMethod; // getCollection, getItem, etc
$result = $this->dataProvider->$method($resourceType);
return $result;

That really is all. Leave validation, exception-throwing, and everything else to the Domain layer; leave anything related to formatting to the Responder layer. Each action should be so simple, so dumb, that practically nothing interesting happens in it.

It makes sense I'll revert the last commit but I fail to understand what you was thinking about with the one-class action.

@dunglas IMO, @pmjones was more talking about natural refactoring while adding more action in a parent class for example. Right ?

I fail to understand what you was thinking about with the one-class action.

(/me nods) That's OK -- it will reveal itself to you in time.
Essentially what will happen is that, because each different action has exactly the same steps, but uses only (1) a different set of inputs for the the domain, and (2) a different domain method or domain object, you will end up seeing a way to have only one class, maybe a base class that you end up extending, and inject different input-collection objects and domain objects when you instantiate it. You might see what I mean if you look at Arbiter.
But really, all of that is for later. For now, concentrate on getting a good separation of layers.

@dupuchba Correct. :-)

Thanks for the feedback @pmjones. I understand better now.

authors: dunglas dupuchba ogizanagi pmjones theofidry

repo: dunglas/DunglasApiBundle


text:
Tons of docker tags, little explanation

Is your feature request related to a problem? Please describe.
The documentation for the docker images points you at https://hub.docker.com/r/dunglas/frankenphp/tags, with... quite a few images (360+ pages worth at time of writing). Figuring out which ones are relevant for you can be a bit tricky, as tons of images has SHA-hashes in their names.
Describe the solution you'd like
Adding some basic instructions for which image to pick would be great, basically something like what's available on https://hub.docker.com/_/php (under Image Variants).
The pattern for packages that are relevant to users seem to be {FrankenPHPVersion}-php{Major.Minor}-{Distro}.

This is a "bug". We need to cleanup the SHA tags as they are now uploaded to a specific repository (dunglas/frankenphp-dev).

Part of it is/was a bug, but adding some short guidance on the summary page about picking a good tag should be useful for new users. Either as detailed as what PHP does, or simply "Use 1-php8.3 unless you have specific needs"

@pontus-mp I'm working on fixing the bug (it remains). I already added some more docs: https://github.com/dunglas/frankenphp/pull/781/files#diff-ae5611658dcd443d7a30575bebcdf15a71b7a0f5abebb18b62d00aa0373cae74R5

authors: dunglas pontus-mp

repo: dunglas/frankenphp


text:
Improve handling of Keyboard Interrupts

This improves handling of keyboard interrupts in the C extension by explicitly checking for any queued signals. It also changes the text output to indicate the simulation was cancelled.

Forgot to add that this closes #47


text:
SyntaxError: invalid syntax common.py - common.py

I am getting a below syntex error either with demo or my account settings.
$ sudo python cloudmapper.py prepare --config config.json.demo --account demo
Traceback (most recent call last):
File "cloudmapper.py", line 70, in
main()
File "cloudmapper.py", line 54, in main
module = importlib.import_module(full_package_name)
File "/usr/lib64/python2.7/importlib/init.py", line 37, in import_module
import(name)
File "/home/vkumar/cloudmapper-master/commands/amis.py", line 10, in
from shared.common import parse_arguments, query_aws, make_list, get_regions
File "/home/vkumar/cloudmapper-master/shared/common.py", line 240
for principal_auth in [*json_account_auth_details['UserDetailList'], *json_account_auth_details['RoleDetailList']]:
^
SyntaxError: invalid syntax
$

My guess is you might not be running in the pipenv shell which would force use of Python 3.

Thanks for the quick solution.

repo: duo-labs/cloudmapper


text:
HttpClientHandler.ServerCertificateCustomValidationCallback requires .NET Framework 4.7.1

The repo states the library requires .NET 4.6.1, but this property did not exist until .NET Framework 4.7.1:
https://github.com/duosecurity/duo_universal_csharp/blob/4a8d878454d298917ed97b0c7cb10e883402523d/DuoUniversal/Client.cs#L417
https://docs.microsoft.com/en-us/dotnet/api/system.net.http.httpclienthandler.servercertificatecustomvalidationcallback?view=netframework-4.7.1
Trying to use the client on a Windows machine that does not have at least .NET Framework 4.7.1 would most likely cause a runtime error. It would be really nice to use this with my .NET 4.6.2 web app, but I foresee this being a reason I can't.

I just ran across this myself and hadn't updated the repo yet.  I think it is very likely I'll have to change the minimum .NET framework requirement to 4.7.1 because of this.  I looked around but 4.6 doesn't seem to have anything that can accomplish the same task.

What about using System.Net.Http.WinHttpHandler instead?
        /// <summary>
        /// Get the appropriate HttpMessageHandler based on the builder settings:
        ///   If a custom handler was specified, return that one (TESTS ONLY)
        ///   Otherwise, return a Handler with the appropriate settings
        /// </summary>
        /// <returns>An HttpMessageHandler for use in a client</returns>
        private HttpMessageHandler GetMessageHandler()
        {
            // Custom handler takes precedence
            if (_httpMessageHandler != null)
            {
                return _httpMessageHandler;
            }

            var certPinner = GetCertificatePinner();
            return new WinHttpHandler()
            {
                ServerCertificateValidationCallback = certPinner
            };

            //return new HttpClientHandler
            //{
            //    ServerCertificateCustomValidationCallback = certPinner
            //};
        }

@tloveland1 My biggest concern there is that, per the docs at https://docs.microsoft.com/en-us/dotnet/api/system.net.http.winhttphandler?view=dotnet-plat-ext-6.0

WinHttpHandler is implemented as a thin wrapper on the WinHTTP interface of Windows and is only supported on Windows systems.

I think this may be a deal-breaker, as we want to support Linux and Mac .NET applications as well.

Ah, I did not see that. What about using it conditionally just for Windows platforms?
            if (RuntimeInformation.IsOSPlatform(OSPlatform.Windows))
            {
                return new WinHttpHandler()
                {
                    ServerCertificateValidationCallback = certPinner
                };
            }
            else
            {
                return new HttpClientHandler
                {
                    ServerCertificateCustomValidationCallback = certPinner
                };
            }

I'll look into it.  The docs were not very clear on whether using the ServerCertificateValidationCallback shifted the entire responsibility of certificate validation onto the implementer, so I'll need to test that.
(As opposed to ServerCertificateCustomValidationCallback, which I confirmed does some initial checking - signatures, etc. - and sends the delegate that information in SslPolicyErrors to use in making the decision.)

@tloveland1 I'm taking a look at this again, and the documentation at https://docs.microsoft.com/en-us/dotnet/api/system.net.http.winhttphandler.servercertificatevalidationcallback indicates this property is available in .NET core 1.0 and 1.1, some .NET platform extensions, and some Xamarin stuff.  I'm not very familiar with .NET environments, but doesn't this mean that it's not guaranteed to be available in .NET Framework applications?

I believe that refers to the compatibility of System.Net.Http.WinHttpHandler.dll, which provides the WinHttpHandler class. You would pull in System.Net.Http.WinHttpHandler.dll as a package in this library to use it (https://www.nuget.org/packages/System.Net.Http.WinHttpHandler/)


text:
Introduce yourself (by commenting on this issue)

Leave a comment below to say hello and let us know about your interests. (This is a good place to find collaborators!)
Use this example to help write your own introduction:

Your Name: Bill Branan
Your Employer/Affiliation (if applicable): DuraSpace
What brings you to the DuraCloud project: To make cloud storage more accessible (simpler to understand and use) and more suited to long-term data preservation
What would you like to work on for DuraCloud: I want to help make the software solve real preservation challenges and help to build a community where we can all work together towards common goals

Remember that this issue is public, so please be careful when sharing personal information

hii,
my name is Mayank jain
i am a computer science student
I like the functioning and motive to develop duracloud
i will like to contribute to this project as a java developer

Your Name: Erin Tripp
Your Employer/Affiliation (if applicable): DuraSpace (hey Bill!!)
What brings you to the DuraCloud project: I'm excited to participate in a sprint, meet new people and I'll use it as an opportunity to work on a privacy and data protection policy for DuraCloud and help with other documentation/engagement tasks.

authors: bbranan erintripp mayankjn34

repo: duracloud/duracloud


text:
🛑 Mention Robot is down

In 96344b6, Mention Robot (https://backend.isbotdown.com/bots/mentionrobot) was down:

HTTP code: 200
Response time: 119 ms

Resolved: Mention Robot is back up in b65c790.

repo: durof/status


text:
🛑 Mention Test Bot is down

In df20c3c, Mention Test Bot (https://backend.isbotdown.com/bots/mentiontestbot) was down:

HTTP code: 200
Response time: 85 ms

Resolved: Mention Test Bot is back up in bbbdef9 after 55 minutes.


text:
🛑 Mention Test Bot is down

In 6a17c92, Mention Test Bot (https://backend.isbotdown.com/bots/mentiontestbot) was down:

HTTP code: 200
Response time: 117 ms

Resolved: Mention Test Bot is back up in cea7f19.


text:
🛑 Mention Test Bot is down

In f01e056, Mention Test Bot (https://backend.isbotdown.com/bots/mentiontestbot) was down:

HTTP code: 200
Response time: 106 ms

Resolved: Mention Test Bot is back up in fbd84e8 after 1 hour, 46 minutes.


text:
add devnet.sh support for master branch, upgrade lint and test consensus with multiple bidders #580

This PR addresses having the devnet.sh scrips usable with dusk blindbid. I also does bid on all nodes of the network.

Codecov Report

Merging #581 into master will increase coverage by 4.40%.
The diff coverage is 53.30%.

@@            Coverage Diff             @@
##           master     #581      +/-   ##
==========================================
+ Coverage   52.34%   56.74%   +4.40%
==========================================
  Files         132      169      +37
  Lines        7499     9249    +1750
==========================================
+ Hits         3925     5248    +1323
- Misses       3063     3325     +262
- Partials      511      676     +165

Impacted Files
Coverage Δ

pkg/config/consts.go
0.00% <0.00%> (ø)

pkg/config/loader.go
61.03% <ø> (ø)

pkg/core/candidate/validator.go
65.21% <ø> (ø)

pkg/core/chain/collectors.go
57.14% <ø> (ø)

pkg/core/consensus/agreement/accumulator.go
90.90% <ø> (ø)

pkg/core/consensus/agreement/store.go
59.30% <0.00%> (ø)

pkg/core/consensus/candidate/factory.go
100.00% <ø> (ø)

pkg/core/consensus/candidate/genesis.go
71.42% <ø> (ø)

pkg/core/consensus/collector.go
0.00% <ø> (ø)

pkg/core/consensus/component.go
72.41% <ø> (ø)

... and 194 more

Continue to review full report at Codecov.

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

authors: codecov-commenter devtomnl

repo: dusk-network/dusk-blockchain


text:
fix: dont filter on active configs in conversation or agent view

Description
fixes https://github.com/dust-tt/tasks/issues/405
In agent view, inactive global agents should still be returned
Risk

Deploy Plan

Do we have the same issue for an assistant that would have been deleted?

No it's done properly there

repo: dust-tt/dust


text:
python: added detectnet-video.py and imagenet-video.py

Added two new examples that add support for using detectnet and imagenet on
video files.

This PR depends on https://github.com/dusty-nv/jetson-utils/pull/10

updated the two example so closing the renderer window (if --render) also stops the example.

Thanks @aconchillo , appreciate it.   I will merge these and your PR's for jetson-utils as soon as I finish making a few other modifications.

@dusty-nv absolutely. i have also updated the jetson-utils PR to use mapped memory instead. i assume it's hopefully the same instead of performance. the reason to not copy the frame to GPU-only memory is because of jetson.utils.saveImageRGBA only works with mapped memory. see https://github.com/aconchillo/jetson-utils/commit/a557a8598a41366e73077b6ddcb1d374bb742d8b#commitcomment-34771648

An error occurs at cmake ../
What is the problem?
jetson@jetson-nano:~/jetson/acon/jetson-inference/build$ cmake ../
Note:  this project uses git submodules in the source tree.
if you haven't already, run the following command from
the project's root directory:
       git submodule update --init

-- using patched FindCUDA.cmake
-- CUDA version: 10.0
-- CUDA 10 detected, enabling SM_72
CMake Error at CMakeLists.txt:74 (find_package):
Could not find a configuration file for package "OpenCV" that is compatible
with requested version "3.0.0".
The following configuration files were considered but not accepted:
/usr/lib/aarch64-linux-gnu/cmake/opencv4/OpenCVConfig.cmake, version: 4.1.1

-- Configuring incomplete, errors occurred!

I wonder if your repo is out-of-date, because this issue was fixed for JetPack 4.3 here:
https://github.com/dusty-nv/jetson-inference/blob/8846dcb274ff812880ef7bf9d42eb1dd75c9e7b7/CMakeLists.txt#L74

I wonder if your repo is out-of-date, because this issue was fixed for JetPack 4.3 here:
https://github.com/dusty-nv/jetson-inference/blob/8846dcb274ff812880ef7bf9d42eb1dd75c9e7b7/CMakeLists.txt#L74
I got it~
Thank you!

@aconchillo Thank you for your contribution!  It is exactly what I am looking for.
But I am having difficulties to checkout your commit, and can you please help!
I cloned the repo by $git clone https://github.com/dusty-nv/jetson-inference.git
then I ran $git checkout 3cd88fcd074671690ea8cabf5138c5e7e2dc1730
but it complained that fatal: reference is not a tree: 3cd88fcd074671690ea8cabf5138c5e7e2dc1730
Thanks!

hi @aconchillo sorry for my bad english, i'm very beginner in jetson inference. I was completely clone your forks repo which contain detecnet-video, but when im running in my jetson inference, error saying 'module' object has no attribute 'VideoSource'. How to solve this problem? is that the opencv must version 3? or rebuild the jetson inference? thanks for your advice.

Not sure why you chose to use the aconchillo's version instead of main repo.  I am guessing you want to use gstreamer.  As to the cv version, I am using 4.1.1 and it seems working for me.  BTW, I tried aconchillo's version before, and found that there was a memory leak at that time, then switched back to the main repo.

I haven't played with this for a long time. I will try to revive it and get it up to date. @bl6594 does the main repo support detection non video files? if so there might not be not need to update this.

@aconchillo the jetson-inference dev branch now supports video files, RTP/RTSP streams, ect from both C++ and Python.  So you may not need to update it.  I will be merging it into master as soon as I am done with documentation.   For now, see here:
https://github.com/dusty-nv/jetson-inference/blob/dev/docs/aux-streaming.md

@dusty-nv awesome! thanks!

authors: aconchillo bl6594 dusty-nv fauziacharuna maponarooo

repo: dusty-nv/jetson-inference


text:
Deprecated Nvbuf_utils is removed from JetPack 5.1.2

I build jetson-utils on JetPack 5.1.2.
As a result, CMake could not find nvbuf_utils.
-- distro ID:       Ubuntu
-- distro version:  20.04
-- distro codename: focal
-- nvbuf_utils:  NVBUF_UTILS-NOTFOUND
-- NVMM zero-copy memory:  ENABLE_NVMM=OFF

I found the following information in https://docs.nvidia.com/jetson/archives/jetpack-archived/jetpack-512/release-notes/index.html.

Deprecated Nvbuf_utils is removed. Refer to migration guide to migrate from Nvbuf_utils to NvUtils.

@dusty-nv Yes. I was able to build it without error.

@dusty-nv wouldn't this decrease the performance with nvarguscamerasrc on Jetpack >= 5.0? It seems like gstBufferManager.cpp already has the changes needed for Jetpack 5, is the only missing step an update of CMakeLists.txt according to Nvbuf_utils to NvUtils Migration guide?

@poett1 I believe there are API changes, it wasn't just the name of the header.  I haven't really dug into it, but if you wanted to investigate it further and make a working PR that would be much appreciated 👍

@dusty-nv i just created a PR. Feel free to check this out @atinfinity.

authors: atinfinity dusty-nv poett1

repo: dusty-nv/jetson-utils


text:
Saves content as " b'Test\r\n' " instead of "Test"

Dude this issue persists after the PR.

Sorry for creating a confusion by referencing it.

Sorry for creating a confusion by referencing it.

license: Unlicense


text:
关于dispatch（） .then用法的疑惑

dispatch().then（），then的参数当中是否可以直接返回请求的结果，或者具体想知道then中是不是有默认返回的参数呢，还是直接是空的。

then中是不是有默认返回的参数呢

会返回 effect 的返回值。

这是我调用的地方

打印的是response 是后台的数据，已获取到数据，resp  是我打印的.then返回的数据，没有值

这是我的effect

这是我调用的api

按着@sorrycc陈大你说的，应该有返回值的啊   是我哪里用的不对吗？

return response

@sorrycc dispatch触发之后可以在dipatch({}).then中获取全局state的最新状态吗？

我也想知道dispatch触发之后可以在dipatch({}).then中获取全局state的最新状态吗？ @LPink777 @Gzbox @amelonsamy @

@LPink777 @ChanseaCem 不行的。dispatch().then 推荐用来做比较 "轻量" 的操作，比如说通知 UI 层某个 effect 调用的结束，可以关闭 xx，可以提示 xx。
对于异步逻辑的组织应该尽量在 effect 中完成

你的意思是
effects: {
*getProList({ payload }, { call, put }) {
const res = yield call(getProList);
if (res && res.code === 200) {
yield put({
type: 'setPro',
payload: {
data: res.data
}
})
}
},
}
then的意义表示这个yield call(getProList);的请求结束，而并不是
yield put({
type: 'setPro',
payload: {
data: res.data
}
})
到reducers进行更新赋值结束。如果要拿最新的state就要使用userSelector。
比如：
@connect(({ yieldrate_group, loading }) => ({
...yieldrate_group
}))
class YieldRateGroup extends Component {
constructor(props) {
super(props);
}
componentDidMount() {
this.initData();
}
saveData = (dispatch, data, fn) => {
dispatch({
type: 'yieldrate_group/setState',
payload: {
data: data
}
}).then(() => {
if (fn) {
fn(dispatch);
}
})
}
initData = () => {
const { dispatch } = this.props;
this.getProList(dispatch);
}
// 获取产品列表
getProList = (dispatch) => {
dispatch({
type: 'yieldrate_group/getProList',
payload: {}
}).then(() => {
this.getGrouptList(dispatch)
})
}
//分组
getGrouptList = (dispatch) => {
const { pro_code, start_time, end_time, hours } = this.props;
dispatch({
type: 'yieldrate_group/getYieldAllList',
payload: {
values: {
pro_code: pro_code,
start_time: start_time,
end_time: end_time,
hours: hours,
sort: type == 'ok' ? 'desc' : 'asc',
type: type
}
}
}).then(() => {
......
})
}
......
}
这里的获取产品列表的then后面调用的getGrouptList 方法里，
const { pro_code, start_time, end_time, hours } = this.props 这句代码，不应该直接调用，而是换成userSelector获取。
我这样的理解对吗？
顺便问下，之前我都用这个方式进行获取，都啥问题，就是偶尔会遇见获取最新state的时候是旧数据。我的理解是，这个时候的this.props里面包含的是redecers完结后的数据，所以我怕对then的理解，和this.props这个的理解是不是哪里冲突了或者哪里搞错了

你的意思是
effects: {
*getProList({ payload }, { call, put }) {
const res = yield call(getProList);
if (res && res.code === 200) {
yield put({
type: 'setPro',
payload: {
data: res.data
}
})
}
},
}
then的意义表示这个yield call(getProList);的请求结束，而并不是
yield put({
type: 'setPro',
payload: {
data: res.data
}
})
到reducers进行更新赋值结束。如果要拿最新的state就要使用userSelector。
比如：
@connect(({ yieldrate_group, loading }) => ({
...yieldrate_group
}))
class YieldRateGroup extends Component {
constructor(props) {
super(props);
}
componentDidMount() {
this.initData();
}
saveData = (dispatch, data, fn) => {
dispatch({
type: 'yieldrate_group/setState',
payload: {
data: data
}
}).then(() => {
if (fn) {
fn(dispatch);
}
})
}
initData = () => {
const { dispatch } = this.props;
this.getProList(dispatch);
}
// 获取产品列表
getProList = (dispatch) => {
dispatch({
type: 'yieldrate_group/getProList',
payload: {}
}).then(() => {
this.getGrouptList(dispatch)
})
}
//分组
getGrouptList = (dispatch) => {
const { pro_code, start_time, end_time, hours } = this.props;
dispatch({
type: 'yieldrate_group/getYieldAllList',
payload: {
values: {
pro_code: pro_code,
start_time: start_time,
end_time: end_time,
hours: hours,
sort: type == 'ok' ? 'desc' : 'asc',
type: type
}
}
}).then(() => {
......
})
}
......
}
这里的获取产品列表的then后面调用的getGrouptList 方法里，
const { pro_code, start_time, end_time, hours } = this.props 这句代码，不应该直接调用，而是换成userSelector获取。
我这样的理解对吗？
顺便问下，之前我都用这个方式进行获取，都啥问题，就是偶尔会遇见获取最新state的时候是旧数据。我的理解是，这个时候的this.props里面包含的是redecers完结后的数据，所以我怕对then的理解，和this.props这个的理解是不是哪里冲突了或者哪里搞错了  @xc1427

authors: ChanseaCem Gzbox LPink777 amelonsamy johanazhu sorrycc xc1427

repo: dvajs/dva


text:
186: Remove Cygwin specific ifdefs, check for TIOCSTI definition.

Fix for https://github.com/dvorka/hstr/issues/186. Identical to #164, just check for TIOCSTI directly instead of checking for __CYGWIN__ define. Works on Cygwin, may also work on Windows 10 Linux Subsystem.
Needs testing on Windows 10! (I don't have a Win 10 machine):
git clone https://github.com/jmiserez/hstr
cd hstr
git checkout windows-fix
cd dist
./1-dist.sh
cd ..
./configure
make
make install
hh --show-configuration >> ~/.bashrc

Then open a new Bash and test it with CTRL-R.

Closing this, just saw that TIOCSTI is in fact defined on Win10, it just doesn't work. So this PR won't work.

repo: dvorka/hstr


text:
Update BQM.add_linear_equality_constraint() to take into account the minimal activation of the constraint

For linear equality constraints like $\sum_i x_i a_i = 0$ such that $a_i >= 0$ $\forall i$, I think we can just do $E(x) = objective(x) + \alpha (\sum_i x_i a_i )$ rather than $E(x) = objective(x) + \alpha (\sum_i x_i a_i ) ^2 $. This obviously results in far fewer quadratic terms, although the penalty is applied linearly rather than quadratically. It would be nice to handle this case, either automatically or via a keyword argument.

Though, thinking more about that, $\sum_i x_i a_i = 0$ is trivially satisfied when $x_i = 0$. Closing...

repo: dwavesystems/dimod


text:
Inconsistent handling of invalid variable values in SampleSet

>>> import dimod
>>> dimod.__version__
'0.8.15'
>>>
>>> bqm = dimod.BQM.from_ising({}, {'ab': 1})
>>> ss = dimod.SampleSet.from_samples_bqm([{'a': 1, 'b': 1}, {'a': -1, 'b': -20}], bqm)
>>> print(ss)
   a  b energy num_oc.
0 +1 +1    1.0       1
1 -1 -1   20.0       1
['SPIN', 2 rows, 2 samples, 2 variables]

Note how -20 for b in the second sample is out of allowed {1, -1} set, yet when printed it's rounded down to -1. Energy stays incorrect though (calculated for b = -20).

The energy is correct, it's calculated from a*b*J_ab so -1*-20*1. The problem is that the sampleset does not check that the input samples are actually correct so sampleset.record.sample in this case would be [[1, 1], [-1, 20]]. It is the print function, not the construction that is rounding b down.
We can change it so that the sample set enforces the samples to be the correct vartype, would you prefer an exception or rounding? There is a performance hit that comes with that, so maybe I can add a permissive=True flag or something.

Yes, I'm aware of that. I guess I forgot to write my expected behaviour:

if invalid variable values are accepted in constructor, and actually stored in the SampleSet, then print function should not round them down - it should stay as close to actual sample set data as possible.
but I don't think invalid values should ever be stored in the SS (since vartype is a non-optional parameter!). I like the idea of permissive flag, and I would expect that permissive=False raises an exception (default), and permissive=True rounds values.

authors: arcondello randomir


text:
Failed to import dwave.inspector because the file _minorminer.cp313-win_amd64.pyd from the minorminer package is flagged as a virus.

Description
Failed to import dwave.inspector because the file _minorminer.cp313-win_amd64.pyd from the minorminer package is flagged as a virus.
To Reproduce
Run the following command: import dwave.inspector
Expected behavior
The import should work without any issues.
Environment:

OS: [window 11]
Python version: [3.13.1]
Ocean SDK version: [8.1.0]

Additional context

I have same issue: ImportError: DLL load failed while importing _minorminer

@darkmatter2000, what error message are you getting? I see you're using Python 3.13. Would it be possible to check if it also happens with 3.12? And if so, does this happen with only minorminer==0.2.16 or also with minorminer==0.2.15?
@Jacck , I suspect the DLL load fail might be different. But similar question, can you post the full traceback? And does it happen only with one version of minorminer or with all? What version of Python are you using?

authors: Jacck arcondello darkmatter2000

repo: dwavesystems/dwave-ocean-sdk


text:
Extensions whitelist are case sensitive only

It should be fixed to ignore case. Example: "JPG" is a valid extension.
This plugin should call the method check_whitelist from carrierwave instead of creating its own, because in carrierwave fixes it 2 years ago.
https://github.com/jnicklas/carrierwave/pull/174

Wow, still an open issue. Just started using carrierwave_direct, and low and behold, customers are now having problems with uploading images due to this.

authors: domness luccasmaso


text:
请教一下命名pca/pcaa

不明白两个文件为何叫这个名字，初次见到，有点费解。
私下猜测：
p => province
c => city
a => area
所以pca是 province city area 的缩写？

是的 @levy9527

那pcaa何解？

repo: dwqs/area-data


text:
📢 Deprecating org:destruct

As sfdx source:delete and mdapi:deploy now supports deletion of metadata with pre/post as well as individual components. This command can be deprecated

Hi @hassanalamibmx  you can supply a pre or post destructive change xml file with the force:source:deploy command:

Thanks!

Hi @hassanalamibmx I understand the problem, since there are other avenues, such as creating an empty manifest in your repo, we will still be deprecating this command in the September release. You can still use the command in version 5.0.0 and below.
Caitlyn

authors: Caitlyn-Mills azlam-abdulsalam

repo: dxatscale/sfpowerkit


text:
orchestrator:build job removes too many packages from queue after single failure

Describe the bug
When a package is failing during build job, it removes all childs from queue. Unfortunately it not only removes its own childs, but also others in queue.
To Reproduce
Following Setup:
Package1

no deps

Package2

dep on package1

Package3

no deps

Package4

dep on package3

Build jobs starts: Package(s) currently processed: Package1, Package3. Packages in queue: Package2, Package4.

Package 1 fails: "Error XYZ. Removing childs from queue"

Package3 successfully builds: "Version X.Y.Z successfully created"

Job ends with message: 1 package created. 1 Package failed: package2.

-> Package 4 disappeared!
Expected behavior
If a package fails only child packages of that package must be removed from queue, not child packages of other packages.
Platform Details (please complete the following information):

Version 20.2.11
Salesforce CLI(sfdx cli) Version: 7.179.0
CI Platform: Gitlab CI

Looks like this happens for any errors in the first parent nodes, investigating..

repo: dxatscale/sfpowerscripts


text:
(fix) add aria-label to sort links

this is a more elegant solution than that implemented in https://github.com/dxw/teacher-vacancy-service/pull/303

 Job list sort links need more descriptive text

repo: dxw/teacher-vacancy-service


text:
Do not publish bytecode in build

Should reduce the size of the npm package

Pull Request Test Coverage Report for Build 8443

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 8429:
0.0%

Covered Lines:
1474

Relevant Lines:
1474

💛  - Coveralls

authors: AntonioJuliano coveralls

repo: dydxprotocol/protocol


text:
Workspace improvements...

Currently the following file hierarchy is assumed:
my-workspace/workspace.json
my-workspace/_build
my-workspace/registry
my-workspace/active-package-1
my-workspace/active-package-1/dylan-package.json
my-workspace/active-package-2
my-workspace/active-package-2/dylan-package.json
...

It shouldn't be necessary to have that extra level of directory structure for my-workspace when working on a single package, which, I think it's safe to assume, will be a very common case.
Instead all the dylan subcommands should work inside a bare package checkout. All that's needed to make this work is to first look for a workspace (workspace.json) and then fall back to looking for a package (dylan-package.json). (Then fall back to looking for "registry".)
In order to keep the workspace.json functionality (which is currently only a "default-library" setting), dylan-package.json could have a "workspace" attribute that is treated exactly the same as the contents of workspace.json.
(And workspace.json should probably be called dylan-workspace.json).
How exactly would these settings work when a workspace contains multiple packages with multiple "workspace" configs...not sure. Combine and override?  just use dylan-workspace.json and ignore the package-level settings? Dunno!

This is done, in these commits:

16f51f41b51b5ca36fcc0b84b91cd8d22fe6d2c6
4700c6c36bcc3845e1a3f553fbb3f3efe0dc09db
9f77a1e6abdb13bbc8d8c9f08267f6d85c565da5
See docs for description.

repo: dylan-lang/dylan-tool


text:
chrome os not recognized

using chromebrew to install and run neofetch results in a generic Linux image (ascii tux) being displayed

Open a new issue following the template.

authors: dylanaraps firebadnofire

repo: dylanaraps/neofetch


text:
General: Remove another awk call

Found another one.

LGTM

authors: konimex mstraube


text:
Colorscheme not working on rofi

After updating rofi to the newest version the color scheme doesn't apply to it anymore.
I'm not really sure what I should provide for it to be reproducable tho, so far I tried:

rebooting
reinstalling both pywal and rofi
pacman -Syu

1.5.0-dirty

Got the same issue occurring on Rofi version 1.2.0

It now requires some manual configuration(providing more customizability):
https://github.com/dylanaraps/pywal/wiki/Customization#rofi

works great, thanks

authors: AUTplayed Clyybber ltgouvea

repo: dylanaraps/pywal


text:
[Snyk] Security upgrade @backstage/types from 0.0.0-use.local to 0.1.1

Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.
Snyk changed the following file(s):

packages/config/package.json

Note for zero-installs users
If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠ Warning
Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Regular Expression Denial of Service (ReDoS) SNYK-JS-PATHTOREGEXP-7925106
  67

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Regular Expression Denial of Service (ReDoS)

🎉 Snyk hasn't found any issues so far.
✅ code/snyk check is completed. No issues were found. (View Details)

repo: dylansnyk/backstage


text:
[Snyk] Fix for 4 vulnerabilities

Snyk has created this PR to fix 4 vulnerabilities in the yarn dependencies of this project.
Snyk changed the following file(s):

plugins/events-backend-module-gitlab/package.json

Note for zero-installs users
If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠ Warning
Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Asymmetric Resource Consumption (Amplification) SNYK-JS-BODYPARSER-7926860
  112

Cross-site Scripting SNYK-JS-EXPRESS-7926867
  80

Cross-site Scripting SNYK-JS-SEND-7926862
  80

Cross-site Scripting SNYK-JS-SERVESTATIC-7926865
  80

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Cross-site Scripting

🎉 Snyk hasn't found any issues so far.
✅ code/snyk check is completed. No issues were found. (View Details)


text:
unpack_by_nested_dict_transformer  in customer_gauge

Trymzet: What are this params for? I didn't get this neither from this docstring nor from the unpacking function. I mean I know what it does, but why is it needed in the first place? Can you maybe provide an example of usage?
possibly param can be skipped in the final flow and defined within the task

linked PR - https://github.com/dyvenia/viadot/pull/1040/files

@gwieloch FYI you can link the comment directly like this

authors: gwieloch trymzet

repo: dyvenia/viadot


text:
Missing ⇐

Glyph ⇐ has been added to BQN since the last update to BQN386, I guess.

It's been in paste's copy of the font for a while, but i managed to never update it here (not even in my todo lists!); nevertheless, it's updated now.

authors: dzaima mlochbaum


text:
Favicon/logo background color

Very minor but irritating issue - I have Dark Reader (dark mode everywhere extension) installed, so I'm not sure if this is just a me problem.
The favicon is perfect, but the black background looks odd in the a) bookmark bar, b) against the menu (black on dark grey, very subtle), and c) tab.
idk what the solution looks like - perhaps just drop the background? mail logo only?

navbar logo has been updated in 4f51a88723fdc7562cb94d2b9a749066ff75423d; still need to update favicon

favicon fixed in https://github.com/eAbsentee/eAbsentee/commit/d6735bd7f8896a182b938b5601c23774cd959d85 and https://github.com/eAbsentee/eAbsentee/commit/5bc0e983cf81e9f0f768b040aaf7f4a41f5a78af

authors: rau sumanthratna

repo: eAbsentee/eAbsentee


text:
pnpm workspaces support

Hi :upside_down_face:
I like this tool and I plan to use it at Verdaccio, we have an increasing number of modules and update references manually is though, but we uses pnpm and this requires some sort of refactoring to your tooling.  Would you be interested?
https://pnpm.js.org/en/pnpm-workspace_yaml
https://github.com/verdaccio/verdaccio/blob/5.x/pnpm-workspace.yaml
It might be required to add some extra deps, as yaml to js and add some new CLI argument like --strategy or --support so users can choose and even add support for others tooling.
I'd like to work on this but first know your thoughts.

Hey Juan,
hehe I actually was thinking about that as well after checking your repo 😄.
To add some new dependency to read yaml files would be ok and I think we can autodetect pnpm by searching for the pnpm workspace file or? If yes we don't need an extra cli input.
Interesting tho is that you can add exclude pattern there as well.
Additionally I was also thinking about the referencing-workspace-packages-through-relative-path . It is also used by yarn2 I don't know yet how flexible that path linking is, but we can start without considering it.

Let me dive into pnpm packages and see whether they have some we can use easily.

Hello guys, any news about that feature?

Hello guys, any news about that feature?

No from my side, I am still willing to do it but when I have some extra time.

Hey Juan,
I thought on spending some time for general improvements. If it is fine for you I will just grab this one as my first task.

@gbouteiller Just released the new version 2.1.1. If you rely on pnpm aliases and this needs to supported as well, please let us know via the issue #13

authors: MKruschke gbouteiller juanpicado


text:
code improvement

Firstly
The code makes it possible to avoid certain typing errors, ie lowercase and uppercase letters (if the developer puts one of the letters of the code in uppercase there will not be an error message).
Secondly
Comments are in English

Cheers :rocket:


text:
Update large_data.rst [14088]

Added information about txqueuelen modification.

As a suggestion (but not blocking the merging of this PR), just before this new section the is another which is also platform-dependent. In this case the configuration of both Windows and Linux is explained. I think the Windows configuration should be included at some point. Maybe the same structure can be followed: a subsection for Windows and another for Linux, leaving a note in the Windows section that it is under development.

Or even better, we could use tabs, as it is done here

@xander-m2k Would you mind doing a git rebase -i so your commits are the only ones on this PR ?

@xander-m2k Would you mind doing a git rebase -i so your commits are the only ones on this PR ?

I rebased, but I notice I signed-off all of the commits, how do I undo that?

@xander-m2k Would you mind doing a git rebase -i so your commits are the only ones on this PR ?

I rebased, but I noticed I signed-off all of the commits, how do I undo that?

First do git fetch eProsima
Then git rebase -i eProsima/master
An editor will open with several pick commands. Leave only the pick commands for your commits.
Then save and close the editor.
Then do git push -f

@xander-m2k Would you mind doing a git rebase -i so your commits are the only ones on this PR ?

I rebased, but I noticed I signed-off all of the commits, how do I undo that?

First do git fetch eProsima Then git rebase -i eProsima/master An editor will open with several pick commands. Leave only the pick commands for your commits. Then save and close the editor. Then do git push -f

Finally got it working with:
git fetch https://github.com/eProsima/Fast-DDS-docs.git
git rebase -i FETCH_HEAD
git push -f

@xander-m2k Great!
@JLBuenoLopez-eProsima Would you mind reviewing this?

Hi @xander-m2k,
I have added a couple of commits fixing our CI tests and doing some modifications to conform with our documentation style. I have also generalized using both the ifconfig and the ip command. I have removed the modification of the rc.local file because there is no standard way to run scripts at boot time (rc.local has been removed in the latest Ubuntu releases) so I think we should explain how to set the value but leave to the user the way to ensure that the value is kept after rebooting.
If you have any comment, please let me know!

repo: eProsima/Fast-DDS-docs


text:
WizardUI not working after updating to 19.1.4

After updating an existing project from 19.1.3 to 19.1.4 i can't use the WizardUI anymore, since it returns a error message.

Dieser Vorgang kann die Laufzeit destabilisieren.

bei CreateWindow_Patch1(XafApplication context, TemplateContext controllers, ICollection`1 createAllControllers, Boolean isMain, Boolean view, View )
bei DevExpress.ExpressApp.Win.WinShowViewStrategyBase.ShowViewInModalWindow(ShowViewParameters parameters, ShowViewSource showViewSource)
bei DevExpress.ExpressApp.ShowViewStrategyBase.ShowViewCore(ShowViewParameters parameters, ShowViewSource showViewSource)
bei DevExpress.ExpressApp.ShowViewStrategyBase.ShowView(ShowViewParameters parameters, ShowViewSource showViewSource)
bei DevExpress.ExpressApp.Frame.ProcessActionCreatedView(ActionBaseEventArgs e)
bei DevExpress.ExpressApp.Win.WinWindow.ProcessActionCreatedView(ActionBaseEventArgs e)
bei DevExpress.ExpressApp.Frame.ShowViewAction_ProcessCreatedView(Object sender, ActionBaseEventArgs e)
bei DevExpress.ExpressApp.Actions.ActionBase.OnProcessCreatedView(ActionBaseEventArgs e)
bei DevExpress.ExpressApp.Actions.ActionBase.ExecuteCore(Delegate handler, ActionBaseEventArgs eventArgs)

I tried to reproduce this in a new project and there i get another exception:

Das Objekt des Typs "System.String" kann nicht in Typ "System.Drawing.Bitmap" umgewandelt werden.

bei Xpand.ExpressApp.WizardUI.Win.Properties.Resources.get_wizard_image()
bei Xpand.ExpressApp.WizardUI.Win.Templates.WizardDetailViewForm.InitializeComponent()
bei Xpand.ExpressApp.WizardUI.Win.Templates.WizardDetailViewForm..ctor()
bei Xpand.ExpressApp.WizardUI.Win.WizardUIWindowsFormsModule.Application_CreateCustomTemplate(Object sender, CreateCustomTemplateEventArgs e)
bei DevExpress.ExpressApp.XafApplication.RaiseCreateCustomTemplate(CreateCustomTemplateEventArgs args)
bei DevExpress.ExpressApp.XafApplication.OnCreateCustomTemplate(String name)
bei DevExpress.ExpressApp.XafApplication.CreateTemplate(String templateContextName)
bei DevExpress.ExpressApp.Frame.CreateTemplate()
bei DevExpress.ExpressApp.Win.WinWindow..ctor(XafApplication application, TemplateContext context, ICollection1 controllers, Boolean isMain, Boolean activateControllersImmediately)    bei DevExpress.ExpressApp.Win.WinApplication.CreateWindowCore(TemplateContext context, ICollection1 controllers, Boolean isMain, Boolean activateControllersImmediately)
bei DevExpress.ExpressApp.XafApplication.CreateWindow(TemplateContext context, ICollection`1 controllers, Boolean createAllControllers, Boolean isMain, View view)
bei DevExpress.ExpressApp.Win.WinShowViewStrategyBase.ShowViewInModalWindow(ShowViewParameters parameters, ShowViewSource showViewSource)
bei DevExpress.ExpressApp.Win.MdiShowViewStrategy.ShowViewInModalWindow(ShowViewParameters parameters, ShowViewSource showViewSource)
bei DevExpress.ExpressApp.ShowViewStrategyBase.ShowViewCore(ShowViewParameters parameters, ShowViewSource showViewSource)
bei DevExpress.ExpressApp.Win.MdiShowViewStrategy.ShowViewCore(ShowViewParameters parameters, ShowViewSource showViewSource)
bei DevExpress.ExpressApp.ShowViewStrategyBase.ShowView(ShowViewParameters parameters, ShowViewSource showViewSource)
bei DevExpress.ExpressApp.Frame.ProcessActionCreatedView(ActionBaseEventArgs e)
bei DevExpress.ExpressApp.Win.WinWindow.ProcessActionCreatedView(ActionBaseEventArgs e)
bei DevExpress.ExpressApp.Frame.ShowViewAction_ProcessCreatedView(Object sender, ActionBaseEventArgs e)
bei DevExpress.ExpressApp.Actions.ActionBase.OnProcessCreatedView(ActionBaseEventArgs e)
bei DevExpress.ExpressApp.Actions.ActionBase.ExecuteCore(Delegate handler, ActionBaseEventArgs eventArgs)

Steps to reproduce the behavior:

Create new XAF Project with Version 19.1.4
Add WizardUI via the WinModul.cs
Create a Business Object and specify a Wizard Page
Start the program and try to create a new object

Expected behavior
Wizard Page should just open
Desktop (please complete the following information):

OS: Windows 10 Version 1903
Visual Studio Update 16.1.6
XAF 19.1.4
eXpandFramework 19.1.4

Additional context
I uploaded my test application, which only shows the 2nd Bug
expandframeworktest.zip

eXpand.lab release 19.1.501.2 includes commit that relate to this task:

WizardUI throws on error after 19.1.4 #468

Please test if it addresses the problem. If you use nuget add our LAB NugetServer as a nuget package source in VS.
Thanks a lot for your contribution.

it works now. Thanks a lot

It works now. Thanks a lot

authors: Lukas-lab expand

repo: eXpandFramework/eXpand

license: MS-PL


text:
linux 下 通过 env=test php easyswoole start --d 启动后的进程没法 通过 php easyswoole stop 掉

linux 下 通过 env=test php easyswoole start --d 启动后的进程没法 通过 php easyswoole stop 掉，只能 手动 kill 进程

要修改下pid_file配置，然后env=test php easyswoole stop 才可以

repo: easy-swoole/easyswoole