Generate mipmaps of desktop texture

I'm doing duplication of a 4K desktop texture and the aliasing is super-intense. Is it possible to generate mipmaps of the duplicated texture to cut down on artifacts?
I've done a bit of looking into it and it seems that this needs to be done at the native level, which I have precisely zero understanding of 😭
That said, if it's possible to do within Unity, or within the pixel shader , that would be swell (and probably doable on my end!)

Update: If I understand correctly, just changing the MipLevels parameters of the Cursor and Monitor D3D11_Texture2D_DESC to zero should generate a full set of mip levels, that I could access in Unity by setting the MipMap input parameter of the Texture2D constructor to true?
But because I have never written a line of C++ in my life, I can't for the life of me get the plugin to recompile after making those changes. I get
'errorno_t strcpy_s(char *, std:rsize_t, cosnt char *)': cannot convert argument 3 from 'const WCHAR [32]' to 'const char *'
which, after about 2 hours of googling I can confidently say that I totally do not understand hehe

I'm very sorry for the late reply...
uDD cannot generate mipmap of the desktop texture because the MipLevels of the texture provided from Windows Desktop Duplication API is 1 sadly.


run_cifar.sh

experiments/run_cifar.sh: 5: experiments/run_cifar.sh: Syntax error: "(" unexpected

you can try to  use the command "$ bash experiments/run_cifar.sh" rather than the command"$ sh .."

Closing this due to inactivity, please reopen if you still encounter this issue


Add SBOM

[!warning]
This is a public repository, ensure not to disclose:

[x] personal data beyond what is necessary for interacting with this pull request, nor
[x] business confidential information, such as customer names.

What kind of PR is this?
Required: Mark one of the following that is applicable:

[ ] kind/feature
[ ] kind/improvement
[ ] kind/deprecation
[x] kind/documentation
[ ] kind/clean-up
[ ] kind/bug
[ ] kind/other

Optional: Mark one or more of the following that are applicable:

[!important]
Breaking changes should be marked kind/admin-change or kind/dev-change depending on type
Critical security fixes should be marked with kind/security

[ ] kind/admin-change
[ ] kind/dev-change
[ ] kind/security
[ ] kind/adr

What does this PR do / why do we need this PR?
Add an initial SBOM based on v0.37.0
Information to reviewers

Checklist

[ ] Proper commit message prefix on all commits

Change checks:

[ ] The change is transparent
[ ] The change is disruptive
[ ] The change requires no migration steps
[ ] The change requires migration steps
[ ] The change upgrades CRDs

Metrics checks:

[ ] The metrics are still exposed and present in Grafana after the change
[ ] The metrics names didn't change (Grafana dashboards and Prometheus alerts are not affected)
[ ] The metrics names did change (Grafana dashboards and Prometheus alerts were fixed)

Logs checks:

[ ] The logs do not show any errors after the change

Pod Security Policy checks:

[ ] Any changed pod is covered by Pod Security Admission
[ ] Any changed pod is covered by Gatekeeper Pod Security Policies
[ ] The change does not cause any pods to be blocked by Pod Security Admission or Policies

Network Policy checks:

[ ] Any changed pod is covered by Network Policies
[ ] The change does not cause any dropped packets in the NetworkPolicy Dashboard

Audit checks:

[ ] The change does not cause any unnecessary Kubernetes audit events
[ ] The change requires changes to Kubernetes audit policy

Falco checks:

[ ] The change does not cause any alerts to be generated by Falco

Bug checks:

[ ] The bug fix is covered by regression tests

Config checks:

[ ] The schema was updated

Is there a reason why we want to keep multiple versions of this at all times?
Else we could move it to docs/sbom.md and state in the document for which version it has been validated for.
Please add a top level heading "Compliant Kubernetes Apps - SBOM" or something.

I was thinking the same, that the SBOM would reflect the current repository, so if you checked out an old tag the SBOM would reflect that version. Although if it wasn't automatically updated when the repository changed that could become confusing so maybe it's something we could add later on.

I have pushed the new sbom,  ptal :)

LGTM! Just wondering why it isn't in the docs folder?

Sure, I don't see any problem moving it under docs/sbom

Also do we want to write a comment in the document for which commit of the repository it was generated for with date?

I'm fine with adding a note in the document saying that it was based of off v0.37.0.

I'll merge this now. It's not perfect and there are things that need to be sorted out (like how to properly handle multiple helm charts with the same name etc) and there's probably some error in this one, but this is a start and it can only get better from here :)


How to get cloth textures

Thanks for the sharing of your data synthesis toolkit. Could you please show me how to generate the black_patches subfolder in your clothes textures folder? I am trying to extract white patches using custom data. It seems that ccp_patches and df_patches also require additional annotations. Where can I find them? Thanks for your help.

You may use simple rules to classify the color type of a texture image. For instance, if you require black textures, just select those with average pixel values lower than 20 or some other thresholds.

Thanks!


3D printed case?

Has anyone made a 3d printed case for this project along with Raptordemon's PCB's (big and small versions).?

IrControllerCase.zip

Here's one for the v1.5 small board.
ir_blaster_v1.5_small.zip


Lab02 - Compare results to maps

Hello,
I was wondering if we should get exactly the same maps as in the lab instructions? I mean for example in Question 3 while calculating the proportion, whenever I put the yearbuilt >1980 , i get the same maps but if I put yearbulit>=1980, I get slightly different maps. Knowing that the comments in Rmardown mention that we need to count commercial properties with buildings constructed during or later than 1980. I am not sure which instructions I should follow. Please find attached.
Thank you

Hi @gzbib, I think it's okay to do either, as long as you're demonstrating that you grasp the intent and give it your best shot.  This was my fault - I updated the lab template to be more helpful but I used the wrong relational operator here.  We updated the assignment last semester to use only Downtown data, rather than the whole city, so thanks for helping us understand how to improve this particular assignment.
> or >= works either way.  Is that helpful?

Yes Sir, thank you for your prompt reply

Sure thing, @gzbib!


Install reduced pom for dist module

Fixes #6433
This PR

disables default install in favor of install-file similar
how rapids-4-spark is deploy-file'd to Maven central

disables default deploy in favor of deploy-file similar
how rapids-4-spark is deploy-file'd to Maven central in deploy.sh

After this, the dependency reduced pom is correctly placed after mvn deploy -pl dist -PnoSnapshots -Ddist.jar.compress=false

~/.m2/repository/com/nvidia/rapids-4-spark_2.12/22.10.0-SNAPSHOT/rapids-4-spark_2.12-22.10.0-SNAPSHOT.pom
/tmp/m2-repo/com/nvidia/rapids-4-spark_2.12/22.10.0-SNAPSHOT/rapids-4-spark_2.12-22.10.0*pom

Other fixes:

dist.jar.compress is ignored when updating the dist jar

Signed-off-by: Gera Shegalov<EMAIL_ADDRESS>

build

build

build

build

build


Feature: Add (daily/weekly/...) summary of mailserver by parsing logs

More of a feature really,
It would be nice if there was a summary (daily, weekly etc) of the server.
What I mean is including something like Pflogsumm and running it at a schedule defined in a config.
Currently I'm exec'ing into the container and manually running it to get summary information about my mail server, but if this could be included, and even send its output to a defined email address, that would be mighty handy.

Hi @chrisella, we also released a bridge to ELK which could give long term stats and allow to debug a lot of things.
The implementation is partial but works, this could be a better option, no?

https://github.com/tomav/docker-mailserver/pull/331


Events not received on consumer during Too much pending tasks error in Azure Event hub sdk

Package Name:  @azure/event-hubs
Package Version:  5.4.0
Operating system:
[x] nodejs

version:  v14.15.4

[ ] browser

name/version:

[x] typescript

version: 4.1.5

Is the bug related to documentation in

[ ] README.md
[ ] source code documentation
[ ] SDK API docs on https://docs.microsoft.com

Describe the bug
Some events not received by the consumer. Possibly it is related to this ticket 14606.
We received some errors in processError method on 13thMay. The log  message said MessagingError: The request with message_id \"5db3cdec-6b8b-46f0-b333-f7cf3f00c7aa\" timed out. Please try again later. We also print the partiton Id in the log but it was not present in the error message thrown by Azure sdk.
Detail log is below:-
{"level":"error", "time":"2021-05-12T23:33:10.991Z","msg":"Error in listening on eventHub: iot-prd01-evh and partitionId : MessagingError: The request with message_id \"5db3cdec-6b8b-46f0-b333-f7cf3f00c7aa\" timed out. Please try again later.}"}

We received another log message Error: Too much pending tasks in processError method on 20th May.
Detail log is below:-
{"level":"error", "time":"2021-05-25T22:50:53.372Z","msg":"Error in listening on eventHub: iot-prd01-evh and partitionId : Error: Too much pending tasks}"}

Point to note:-

From 13th to 19th May we constantly received timeout out error messages after which no events were received.

As soon as we received too much pending tasks on 20th may and still no events were received and at last when we restarted our machines the events started coming in most probably the ones that were in event hub queue also came.

Once everything was settled after the restart we thought all the events that were missed must have been processed by now. But after further analysis we found around 50 events were missing from 20thMay till 26th May.
Now as per our analysis we suspect the issue for missing events might be:-

The error came in below method in our code:-

processError: (error, context): Promise<void> => {
	AppLogger.error(
	`Error in listening on eventHub: ${context.eventHubName} and partitionId ${context.partitionId}: ${error}}`,
					EventHubService.name
	);
	return Promise.resolve();
},

We catch the error and go ahead with processing other messages in below method:-
processEvents: async (events, context): Promise<void> => {
	AppLogger.info(
		`Received events array length is: ${events?.length}`,
		EventHubService.name
	);
	await Promise.all(events.map(async (event) => {
		await this.handleEvent(event);
		if (config.has('env.MODE') && config.get('env.MODE') === config.get('env.PROD_MODE')) {
						// update checkpoint as per checkpoint frequency
						await this.updateEventCheckpoint(context, events[events.length - 1]);
		}
	}));
},

So when the Timeout message error came in Azure sdk we didn't received any messages and our services was not processing anything.
EDIT:- I gathered some more insights.
We have 2 consumer groups mapped to 2 different consumer services listening to a single event hub. So, as one of the service never received the event which is the issue I raised while the other service received the event as below:-
{"level":"info", "time":"2021-05-25T08:47:45.412Z","context":"DevicesService","msg":"Received event: device created, device id: w3phoenix-61808291846052781-prod"}

I noticed the same time logs [when the other service received the event  2021-05-25T08:47:45.412Z] in my service which stopped receiving events too. The observations were:-

processEvents was called at frequent intervals between [+5:30 IST on above time]14:16:00 to 14:18:00  and the array length was 0 i.e. the array had no events in it.
Between 14:16:00 to 14:18:00 there were Too much pending tasks error exists. Log is below:-
{"level":"error", "time":"2021-05-25T08:46:11.966Z","msg":"Error in listening on eventHub: iot-prd01-evh and partitionId : Error: Too much pending tasks}"}

So on 26th May when we got the information that events are not received, then we restarted the service and thought the events would be in EventHub pipeline and we will receive those. But the event in question above was never received.
Now the question is:-

The events which were not received during the time sdk was in error state i.e. Timed out will those events be present in Event hub queue? If so, we never received those when we restarted our service.  So, Is it the events are still in event hub queue? If so, how can we confirm that, can you suggest a metrics or log somewhere would help.

Below Screenshot  I took on 1st May which shows Captured Backlog as 0.
As per my understanding, it should have shown some events in backlog that were enqueued till 7 days back from 1st of May.
Also it shows User Errors to be 6. I'm still not sure exactly what this User Error means.
Incoming vs Outgoing message is somewhat making sense as my service restarted on 26th evening and there is one more service listening to the same hub. So outgoing is ahead of incoming.

If point 1) stand true, how we can replay those events in our service? Since we never came to know the offset of those events barring one event out 50 which we received the error other than that none of the other 49 events were received by our service.

We never faced this type of issue before of missing events, only correlation we see in missing events is that it happened at the time when the Azure sdk started giving too much pending tasks error i.e. from 20th May. Is it some what really related?

To Reproduce
Steps to reproduce the behavior:

2 Container running in AWS listening on event hub using EventHub consumer client. There are 32 partitions in Event hub.

Expected behavior
Events should never be missed by consumer

@amit12cool
First, with regards to the too much pending tasks issue, this was previously reported in #14606 and fixed in @azure/event-hubs version 5.5.1: changelog
We also fixed a couple race conditions that led to too much pending tasks to occur that are also included in version 5.5.1.

The events which were not received during the time sdk was in error state i.e. Timed out will those events be present in Event hub queue?

I want to be clear, are you talking about events which were not received by your client using the SDK, or events not received by the service (events you would have sent?)
If you're asking about events that were not received by your client, then those will still be in your event hub. When the SDK reads an event from the Event Hubs service, it doesn't delete the event, so you can reread your events as long as they haven't been removed as part of your Event Hubs lifecycle policy.

If point 1) stand true, how we can replay those events in our service? Since we never came to know the offset of those events barring one event out 50 which we received the error other than that none of the other 49 events were received by our service.

Is your application making use of checkpointing? If you're using checkpointing in your application (e.g. via the @azure/eventhubs-checkpointstore-blob package then anytime you restart your application, it will begin reading events from the last event you 'checkpointed'.

@chradek Thanks for your response.
Is the times out error also fixed? Because as soon as we got that error our service stopped consuming messages. Also is it something connection was broken between event hub and consumer when times out error came?
Regarding checkpoint, I will check that on my end. But I'm curious to know what happens when I start the consumer and let's say I consume 100 events and my checkpointing is done at every 150 events. Now, after 100 events received by consumer I restart the consumer. Will the consumer read those 100 events again? Since there is no checkpoint yet done in blob that was to be done at 150th event, I observed those 100 events never came in my consumer.

@chradek any update on this?

@amit12cool

Is the timed out error also fixed?

Yes, there was a race condition that caused the connection to be in a bad state leading to the timeout errors and the too many pending tasks errors. Both were fixed in version 5.5.1.
With regards to checkpointing, if you checkpoint every 150 events and your consumer is closed after 100 events, then the next time you start reading you'll reread those 100 events. The checkpoint defines the starting point in the event you have to restart reading.

Now, when I restart my consumer let's say after 7 days from timed out error occurance day, will the consumer receive the events from 6 day onwards or the last checkpoint saved in blob storage that is 150?

In this scenario, you'd start reading from either the checkpoint location or the earliest event still in the event hub, whichever is latest. If the last few days of events were already deleted, then the checkpoint is really setting the lower bound of where to start.

With regards to checkpointing, if you checkpoint every 150 events and your consumer is closed after 100 events, then the next time you start reading you'll reread those 100 events. The checkpoint defines the starting point in the event you have to restart reading.

I couldn't reproduce this behaviour i.e for the first time the app was launch and after consuming 100 events stopped the app. Then again ran the app those 100 events never came. Should I share the repro code for it?

@amit12cool Are you setting a startPosition when you start your subscribe call? By default, if no checkpoint exists the consumer will start reading new events that come in after subscribe is called. You can configure it to start from the beginning of the event stream instead like this:
const { EventHubConsumerClient, earliestEventPosition } = require('@azure/event-hubs');
const client = new EventHubConsumerClient(
    EventHubConsumerClient.defaultConsumerGroupName,
    connectionString,
    eventHubName
);

client.subscribe({
    processEvents(events, {partitionId}) {
        if (events.length) {
            console.log(events[0].sequenceNumber)
            console.log(`Received ${events.length} events on partition "${partitionId}"`);
        }
    },
    processError(err, {partitionId}) {
        console.error(`Error received on partition "${partitionId}"`);
        console.error(err);
    }
}, {startPosition: earliestEventPosition}) // If no checkpoint exists, the start of the partition will be used.

@chradek Thanks for the solution, that helps. And we were able to do the RCA of this issue on our side and found we had set message retention of 1 days i.e. default set when we create a event hub. We need it to be set max to 7 days.


Build issue on Windows due to white spaces on OpenSSL path

Hi,
I'm having issues compiling OpenSSL (for FIPS compliance), on Windows 11 x64. I've seen other people compiling and not having escape issues but, nonetheless, I had and I can't pinpoint the exact reason for it, aside that my version is different from what people use in their videos/tutorials.

OpenSSL Source version: 3.0.8
x64 Native Tools Command Prompt VS2022 in Admin Mode
Configuration data:

perl configdata.pm --dump

Command line (with current working directory = .):

    C:\Strawberry\perl\bin\perl.exe Configure enable-fips

Perl information:

    C:\Strawberry\perl\bin\perl.exe
    5.38.0 for MSWin32-x64-multi-thread

Enabled features:

    acvp-tests
    aria
    asm
    async
    autoalginit
    autoerrinit
    autoload-config
    bf
    blake2
    bulk
    cached-fetch
    camellia
    capieng
    cast
    chacha
    cmac
    cmp
    cms
    comp
    ct
    deprecated
    des
    dgram
    dh
    dsa
    dso
    dtls
    dynamic-engine
    ec
    ec2m
    ecdh
    ecdsa
    engine
    err
    filenames
    fips
    fips-securitychecks
    gost
    idea
    legacy
    loadereng
    makedepend
    md4
    mdc2
    module
    multiblock
    nextprotoneg
    ocb
    ocsp
    padlockeng
    pic
    pinshared
    poly1305
    posix-io
    psk
    rc2
    rc4
    rdrand
    rfc3779
    rmd160
    scrypt
    secure-memory
    seed
    shared
    siphash
    siv
    sm2
    sm3
    sm4
    sock
    srp
    srtp
    sse2
    ssl
    ssl-trace
    static-engine
    stdio
    tests
    threads
    tls
    ts
    ui-console
    uplink
    whirlpool
    tls1
    tls1-method
    tls1_1
    tls1_1-method
    tls1_2
    tls1_2-method
    tls1_3
    dtls1
    dtls1-method
    dtls1_2
    dtls1_2-method

Disabled features:

    afalgeng            [not-linux] OPENSSL_NO_AFALGENG
    asan                [default]   OPENSSL_NO_ASAN
    buildtest-c++       [default]
    crypto-mdebug       [default]   OPENSSL_NO_CRYPTO_MDEBUG
    devcryptoeng        [default]   OPENSSL_NO_DEVCRYPTOENG
    ec_nistp_64_gcc_128 [default]   OPENSSL_NO_EC_NISTP_64_GCC_128
    egd                 [default]   OPENSSL_NO_EGD
    external-tests      [default]   OPENSSL_NO_EXTERNAL_TESTS
    fuzz-afl            [default]   OPENSSL_NO_FUZZ_AFL
    fuzz-libfuzzer      [default]   OPENSSL_NO_FUZZ_LIBFUZZER
    ktls                [default]   OPENSSL_NO_KTLS
    md2                 [default]   OPENSSL_NO_MD2 (skip crypto\md2)
    msan                [default]   OPENSSL_NO_MSAN
    rc5                 [default]   OPENSSL_NO_RC5 (skip crypto\rc5)
    sctp                [default]   OPENSSL_NO_SCTP
    trace               [default]   OPENSSL_NO_TRACE
    ubsan               [default]   OPENSSL_NO_UBSAN
    unit-test           [default]   OPENSSL_NO_UNIT_TEST
    weak-ssl-ciphers    [default]   OPENSSL_NO_WEAK_SSL_CIPHERS
    zlib                [default]
    zlib-dynamic        [default]
    ssl3                [default]   OPENSSL_NO_SSL3
    ssl3-method         [default]   OPENSSL_NO_SSL3_METHOD

Config target attributes:

    AR => "lib",
    ARFLAGS => "/nologo",
    AS => "nasm",
    ASFLAGS => "-g",
    CC => "cl",
    CFLAGS => "/W3 /wd4090 /nologo /O2",
    CPP => "\$(CC) /EP /C",
    HASHBANGPERL => "/usr/bin/env perl",
    LD => "link",
    LDFLAGS => "/nologo /debug",
    MT => "mt",
    MTFLAGS => "-nologo",
    RANLIB => "CODE(0x1a271c2b3d0)",
    RC => "rc",
    ar_resp_delim => "
",
    aroutflag => "/out:",
    asflags => "-Ox -f win64 -DNEAR",
    asm_arch => "x86_64",
    asoutflag => "-o ",
    bin_cflags => "/Zi /Fdapp.pdb",
    bin_lflags => "setargv.obj /subsystem:console /opt:ref",
    bn_ops => "SIXTY_FOUR_BIT",
    build_file => "makefile",
    build_scheme => [ "unified", "windows", "VC-common" ],
    cflags => "/Gs0 /GF /Gy /MD",
    coutflag => "/Fo",
    cppflags => "",
    defines => [ "OPENSSL_BUILDING_OPENSSL", "OPENSSL_SYS_WIN32", "WIN32_LEAN_AND_MEAN", "UNICODE", "_UNICODE", "_CRT_SECURE_NO_DEPRECATE", "_WINSOCK_DEPRECATED_NO_WARNINGS" ],
    disable => [  ],
    dso_cflags => "/Zi /Fddso.pdb",
    dso_scheme => "win32",
    enable => [  ],
    ex_libs => "ws2_32.lib gdi32.lib advapi32.lib crypt32.lib user32.lib",
    includes => [  ],
    ld_implib_flag => "/implib:",
    ld_resp_delim => "
",
    lddefflag => "/def:",
    ldoutflag => "/out:",
    ldpostoutflag => "",
    ldresflag => " ",
    lflags => "",
    lib_cflags => "/Zi /Fdossl_static.pdb",
    lib_cppflags => "",
    lib_defines => [ "L_ENDIAN" ],
    makedep_scheme => "VC",
    makedepcmd => "\$(CC) /Zs /showIncludes",
    module_cflags => "",
    module_cxxflags => undef,
    module_ldflags => "/dll",
    mtinflag => "-manifest ",
    mtoutflag => "-outputresource:",
    multilib => "-x64",
    perl_platform => "Windows::MSVC",
    perlasm_scheme => "auto",
    rcoutflag => "/fo",
    shared_cflag => "",
    shared_defflag => "",
    shared_defines => [  ],
    shared_ldflag => "/dll",
    shared_rcflag => "",
    shared_target => "win-shared",
    sys_id => "WIN64A",
    thread_defines => [  ],
    thread_scheme => "winthreads",
    unistd => "<unistd.h>",
    uplink_arch => "x86_64",

Recorded environment:

    AR =
    ARFLAGS =
    AS =
    ASFLAGS =
    BUILDFILE =
    CC =
    CFLAGS =
    CPP =
    CPPDEFINES =
    CPPFLAGS = C:\Program Files\OpenSSL\include
    CPPINCLUDES =
    CROSS_COMPILE =
    CXX =
    CXXFLAGS =
    HASHBANGPERL =
    LD =
    LDFLAGS = C:\Program Files\OpenSSL\lib
    LDLIBS =
    MT =
    MTFLAGS =
    OPENSSL_LOCAL_CONFIG_DIR =
    PERL =
    RANLIB =
    RC =
    RCFLAGS =
    RM =
    WINDRES =
    __CNF_CFLAGS =
    __CNF_CPPDEFINES =
    __CNF_CPPFLAGS =
    __CNF_CPPINCLUDES =
    __CNF_CXXFLAGS =
    __CNF_LDFLAGS =
    __CNF_LDLIBS =

Makevars:

    AR              = lib
    ARFLAGS         = /nologo
    AS              = nasm
    ASFLAGS         = -g
    CC              = cl
    CFLAGS          = /W3 /wd4090 /nologo /O2
    CPP             = $(CC) /EP /C
    CPPDEFINES      =
    CPPFLAGS        = C:\Program Files\OpenSSL\include
    CPPINCLUDES     =
    CXXFLAGS        =
    HASHBANGPERL    = /usr/bin/env perl
    LD              = link
    LDFLAGS         = C:\Program Files\OpenSSL\lib
    LDLIBS          =
    MT              = mt
    MTFLAGS         = -nologo
    PERL            = C:\Strawberry\perl\bin\perl.exe
    RANLIB          = ranlib
    RC              = rc
    RCFLAGS         =

NOTE: These variables only represent the configuration view.  The build file
template may have processed these variables further, please have a look at the
build file for more exact data:
    makefile

build file:

    makefile

build file templates:

    Configurations\common0.tmpl
    Configurations\windows-makefile.tmpl

Windows 11 x64
Compiler Details: MSVC v143
Problem Description:

Running the build process, using the guide from install.md or openssl-3.0.8-security-policy-2023-05-05.pdf:
> perl Configure enable-fips
Configuring OpenSSL version 3.0.8 for target VC-WIN64A
Using os-specific seed configuration
Created configdata.pm
Running configdata.pm
Created makefile.in
Created makefile

**********************************************************************
***                                                                ***
***   OpenSSL has been successfully configured                     ***
***                                                                ***
***   If you encounter a problem while building, please open an    ***
***   issue on GitHub <https://github.com/openssl/openssl/issues>  ***
***   and include the output from the following command:           ***
***                                                                ***
***       perl configdata.pm --dump                                ***
***                                                                ***
***   (If you are new to OpenSSL, you might want to consult the    ***
***   'Troubleshooting' section in the INSTALL.md file first)      ***
***                                                                ***
**********************************************************************

Then I get the following output because of incorrectly escaped paths with spaces (partial output):
nmake

Microsoft (R) Program Maintenance Utility Version 14.38.33130.0
Copyright (C) Microsoft Corporation.  All rights reserved.

        "C:\Strawberry\perl\bin\perl.exe" "-I." -Mconfigdata "util\dofile.pl" "-omakefile" "include\crypto\bn_conf.h.in" > include\crypto\bn_conf.h
        "C:\Strawberry\perl\bin\perl.exe" "-I." -Mconfigdata "util\dofile.pl" "-omakefile" "include\crypto\dso_conf.h.in" > include\crypto\dso_conf.h
        "C:\Strawberry\perl\bin\perl.exe" "-I." -Mconfigdata "util\dofile.pl" "-omakefile" "include\openssl\asn1.h.in" > include\openssl\asn1.h
        "C:\Strawberry\perl\bin\perl.exe" "-I." -Mconfigdata "util\dofile.pl" "-omakefile" "include\openssl\asn1t.h.in" > include\openssl\asn1t.h
        "C:\Strawberry\perl\bin\perl.exe" "-I." -Mconfigdata "util\dofile.pl" "-omakefile" "include\openssl\bio.h.in" > include\openssl\bio.h
        "C:\Strawberry\perl\bin\perl.exe" "-I." -Mconfigdata "util\dofile.pl" "-omakefile" "include\openssl\cmp.h.in" > include\openssl\cmp.h
        "C:\Strawberry\perl\bin\perl.exe" "-I." -Mconfigdata "util\dofile.pl" "-omakefile" "include\openssl\cms.h.in" > include\openssl\cms.h
        "C:\Strawberry\perl\bin\perl.exe" "-I." -Mconfigdata "util\dofile.pl" "-omakefile" "include\openssl\conf.h.in" > include\openssl\conf.h
        "C:\Strawberry\perl\bin\perl.exe" "-I." -Mconfigdata "util\dofile.pl" "-omakefile" "include\openssl\crmf.h.in" > include\openssl\crmf.h
        "C:\Strawberry\perl\bin\perl.exe" "-I." -Mconfigdata "util\dofile.pl" "-omakefile" "include\openssl\crypto.h.in" > include\openssl\crypto.h
        "C:\Strawberry\perl\bin\perl.exe" "-I." -Mconfigdata "util\dofile.pl" "-omakefile" "include\openssl\ct.h.in" > include\openssl\ct.h
        "C:\Strawberry\perl\bin\perl.exe" "-I." -Mconfigdata "util\dofile.pl" "-omakefile" "include\openssl\err.h.in" > include\openssl\err.h
        "C:\Strawberry\perl\bin\perl.exe" "-I." -Mconfigdata "util\dofile.pl" "-omakefile" "include\openssl\ess.h.in" > include\openssl\ess.h
        "C:\Strawberry\perl\bin\perl.exe" "-I." -Mconfigdata "util\dofile.pl" "-omakefile" "include\openssl\fipskey.h.in" > include\openssl\fipskey.h
        "C:\Strawberry\perl\bin\perl.exe" "-I." -Mconfigdata "util\dofile.pl" "-omakefile" "include\openssl\lhash.h.in" > include\openssl\lhash.h
        "C:\Strawberry\perl\bin\perl.exe" "-I." -Mconfigdata "util\dofile.pl" "-omakefile" "include\openssl\ocsp.h.in" > include\openssl\ocsp.h
        "C:\Strawberry\perl\bin\perl.exe" "-I." -Mconfigdata "util\dofile.pl" "-omakefile" "include\openssl\opensslv.h.in" > include\openssl\opensslv.h
        "C:\Strawberry\perl\bin\perl.exe" "-I." -Mconfigdata "util\dofile.pl" "-omakefile" "include\openssl\pkcs12.h.in" > include\openssl\pkcs12.h
        "C:\Strawberry\perl\bin\perl.exe" "-I." -Mconfigdata "util\dofile.pl" "-omakefile" "include\openssl\pkcs7.h.in" > include\openssl\pkcs7.h
        "C:\Strawberry\perl\bin\perl.exe" "-I." -Mconfigdata "util\dofile.pl" "-omakefile" "include\openssl\safestack.h.in" > include\openssl\safestack.h
        "C:\Strawberry\perl\bin\perl.exe" "-I." -Mconfigdata "util\dofile.pl" "-omakefile" "include\openssl\srp.h.in" > include\openssl\srp.h
        "C:\Strawberry\perl\bin\perl.exe" "-I." -Mconfigdata "util\dofile.pl" "-omakefile" "include\openssl\ssl.h.in" > include\openssl\ssl.h
        "C:\Strawberry\perl\bin\perl.exe" "-I." -Mconfigdata "util\dofile.pl" "-omakefile" "include\openssl\ui.h.in" > include\openssl\ui.h
        "C:\Strawberry\perl\bin\perl.exe" "-I." -Mconfigdata "util\dofile.pl" "-omakefile" "include\openssl\x509.h.in" > include\openssl\x509.h
        "C:\Strawberry\perl\bin\perl.exe" "-I." -Mconfigdata "util\dofile.pl" "-omakefile" "include\openssl\x509_vfy.h.in" > include\openssl\x509_vfy.h
        "C:\Strawberry\perl\bin\perl.exe" "-I." -Mconfigdata "util\dofile.pl" "-omakefile" "include\openssl\x509v3.h.in" > include\openssl\x509v3.h
        "C:\Strawberry\perl\bin\perl.exe" "-I." -Mconfigdata "util\dofile.pl" "-omakefile" "test\provider_internal_test.cnf.in" > test\provider_internal_test.cnf
        "C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.38.33130\bin\HostX64\x64\nmake.exe" /                   depend

Microsoft (R) Program Maintenance Utility Version 14.38.33130.0
Copyright (C) Microsoft Corporation.  All rights reserved.

        "C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.38.33130\bin\HostX64\x64\nmake.exe" /                   _build_sw

Microsoft (R) Program Maintenance Utility Version 14.38.33130.0
Copyright (C) Microsoft Corporation.  All rights reserved.

        "cl"  /Zi /Fdossl_static.pdb /Gs0 /GF /Gy /MD /W3 /wd4090 /nologo /O2 -I"." -I"include" -I"apps\include" -D"L_ENDIAN" -D"OPENSSL_PIC" -D"OPENSSLDIR=\"C:\\Program Files\\Common Files\\SSL\"" -D"ENGINESDIR=\"C:\\Program Files\\OpenSSL\\lib\\engines-3\"" -D"MODULESDIR=\"C:\\Program Files\\OpenSSL\\lib\\ossl-modules\"" -D"OPENSSL_BUILDING_OPENSSL" -D"OPENSSL_SYS_WIN32" -D"WIN32_LEAN_AND_MEAN" -D"UNICODE" -D"_UNICODE" -D"_CRT_SECURE_NO_DEPRECATE" -D"_WINSOCK_DEPRECATED_NO_WARNINGS" -D"NDEBUG" C:\Program Files\OpenSSL\include  -c /Foapps\lib\libapps-lib-app_libctx.obj "apps\lib\app_libctx.c"
cl : Command line warning D9024 : unrecognized source file type 'C:\Program', object file assumed
cl : Command line warning D9027 : source file 'C:\Program' ignored
cl : Command line warning D9024 : unrecognized source file type 'Files\OpenSSL\include', object file assumed
cl : Command line warning D9027 : source file 'Files\OpenSSL\include' ignored
app_libctx.c
        cmd /C ""cl" /Zs /showIncludes  /Zi /Fdossl_static.pdb /Gs0 /GF /Gy /MD /W3 /wd4090 /nologo /O2 -I"." -I"include" -I"apps\include" -D"L_ENDIAN" -D"OPENSSL_PIC" -D"OPENSSLDIR=\"C:\\Program Files\\Common Files\\SSL\"" -D"ENGINESDIR=\"C:\\Program Files\\OpenSSL\\lib\\engines-3\"" -D"MODULESDIR=\"C:\\Program Files\\OpenSSL\\lib\\ossl-modules\"" -D"OPENSSL_BUILDING_OPENSSL" -D"OPENSSL_SYS_WIN32" -D"WIN32_LEAN_AND_MEAN" -D"UNICODE" -D"_UNICODE" -D"_CRT_SECURE_NO_DEPRECATE" -D"_WINSOCK_DEPRECATED_NO_WARNINGS" -D"NDEBUG" C:\Program Files\OpenSSL\include  "apps\lib\app_libctx.c" > apps\lib\libapps-lib-app_libctx.d 2>&1"
        "cl"  /Zi /Fdossl_static.pdb /Gs0 /GF /Gy /MD /W3 /wd4090 /nologo /O2 -I"." -I"include" -I"apps\include" -D"L_ENDIAN" -D"OPENSSL_PIC" -D"OPENSSLDIR=\"C:\\Program Files\\Common Files\\SSL\"" -D"ENGINESDIR=\"C:\\Program Files\\OpenSSL\\lib\\engines-3\"" -D"MODULESDIR=\"C:\\Program Files\\OpenSSL\\lib\\ossl-modules\"" -D"OPENSSL_BUILDING_OPENSSL" -D"OPENSSL_SYS_WIN32" -D"WIN32_LEAN_AND_MEAN" -D"UNICODE" -D"_UNICODE" -D"_CRT_SECURE_NO_DEPRECATE" -D"_WINSOCK_DEPRECATED_NO_WARNINGS" -D"NDEBUG" C:\Program Files\OpenSSL\include  -c /Foapps\lib\libapps-lib-app_params.obj "apps\lib\app_params.c"
cl : Command line warning D9024 : unrecognized source file type 'C:\Program', object file assumed
cl : Command line warning D9027 : source file 'C:\Program' ignored
cl : Command line warning D9024 : unrecognized source file type 'Files\OpenSSL\include', object file assumed
cl : Command line warning D9027 : source file 'Files\OpenSSL\include' ignored
app_params.c

The issue seems to be that CPPFLAGS (LDFLAGS explained next) is not escaped:
CPPFLAGS        = C:\Program Files\OpenSSL\include
LDFLAGS         = C:\Program Files\OpenSSL\lib

LDFLAGS also gives me issues, if I only change CPPFLAGS. I changed CPPFLAGS and LDFLAGS to the following, on the makefile:
CPPFLAGS=-I"C:\Program Files\OpenSSL\include"
LDFLAGS=/LIBPATH:"C:\Program Files\OpenSSL\lib"

After this change, I also had to make some adjustments to util/copy.pl due to paths (line 68), but doesn't seem related. Aside from that, I was able to run nmake install after introducing the escaping and so on, with the expected output:
perl util/wrap.pl -fips apps/openssl list -provider-path providers -provider fips -providers
Providers:
  base
    name: OpenSSL Base Provider
    version: 3.0.8
    status: active
  fips
    name: OpenSSL FIPS Provider
    version: 3.0.8
    status: active

I've seen other people compiling and not having escape issues but, nonetheless, I had and I can't pinpoint the exact reason for it, aside that my version is different from what people use in their videos/tutorials.

There have been issues and fixes for Windows builds with spaces in the path (although I can't find them in the short time I've got right now) so this is quite possible.
Note that as long as you are correctly using the FIPS provider from 3.0.8, you can use it with any 3.0.x version of OpenSSL and be FIPS compliant

There have been issues and fixes for Windows builds with spaces in the path (although I can't find them in the short time I've got right now) so this is quite possible.

I'll try to get back with a PR, once I get some more time, as this FIPS certification is giving us some work atm. I've added a temp solution to the bug report just in case someone has issues.

Note that as long as you are correctly using the FIPS provider from 3.0.8, you can use it with any 3.0.x version of OpenSSL and be FIPS compliant

This is good to know, thank you for pointing that info as I completely missed it in the docs. This means we can keep things up to date with the latest, while still enforcing the FIPS certified crypto ops. I wonder if that takes care of most, if not all CVEs that eventually are fixed with newer versions. I'm not sure how compatible it will be with PHP though. I'm still trying to build PHP from source, with this version of OpenSSL, and I'm not being able to do so due to linking issues/missing symbols.

fyi -- some changes went in to handle paths with spaces on unix-like platforms:
https://github.com/openssl/openssl/pull/21821
I did some testing on Windows to confirm that paths-with-spaces were not a problem there.  However, I may have only tested "master" (which then became part of our 3.2 release).

some of my initial missteps with Windows builds are documented in the following discussion:
https://github.com/openssl/openssl/discussions/22385

fyi -- some changes went in to handle paths with spaces on unix-like platforms:

It could be, thank you. I'll take that into account when doing further testing.
I'm having some issues building PHP, cURL and OpenSSL 3.0.8, on my work laptop machine though. As this is troublesome there, I'm just at this exact moment doing this on my personal desktop with Windows 11 and with the same VS tooling, Strawberry Perl, etc. Might be my work laptop with some weird envs set.
Some clues on the problem on my personal desktop: after executing perl Configure enable-fips on my personal desktop, the makefile CPPFLAGS is empty and LDFLAGS is set to ´LDFLAGS=/nologo /debug´ instead of the values I described in the first post. The nmake runs successfully and so does nmake test and nmake install. The issue on my work laptop show up for these two. I wonder if there could have been any "leftover" from a previous OpenSSL build, or related. Hopefully this points in some direction as to some use case where CPPFLAGS and/or LDFLAGS get populated in the makefile generation.

some of my initial missteps with Windows builds are documented in the following discussion:
#22385

Classical Windows building experience. 😄

FWIW I remember fixing this 4 years ago, but the PR was never merged (IIRC some parts of it was merged separately later on, but can't find it):
https://github.com/openssl/openssl/pull/9864
https://github.com/openssl/openssl/pull/9903
BSD vs GNU make was also discussed, and it seems that BSD make cannot support spaces no matter what, so these PRs also focused on GNU Make with an option to add support for other flavours as they come by.

It looks like you defined some environment variables, which Configure looks at:
CPPFLAGS = C:\Program Files\OpenSSL\include
LDFLAGS = C:\Program Files\OpenSSL\lib

Their values are meaningless as they are.
They aren't formatted for their use (the values are used as is on the command line)

Considering your environment, I think that the best thing you can do is to make sure these are unset (have the empty string as value) before calling Configure.


Performance: running test for the whole assembly should not be using the same code path as a single test

Hi,
Is anyone else noticing a performance drop when using this? We changed our local and server builds to use this VS plugin, over separate mspec and msbuild runners so we have a consistent output and one trx file - which is great; really, really useful.
However, from a performance perspective we are now really struggling, and I believe it is because the the 'Establish', and 'Because' are being run for each and every 'It'. Whereas our old mspec runner ran Establish', and 'Because' once and then all the 'It's to check the assertions.
Is this something that could be configured?
Is anyone else experiencing this problem...
Sadly if I can't find a resolution to this my boss is gonna roll us back to separate runners :(
Thank you.

Unfortunately there is no workaround currently for this. Have a look at my last comment on issue #8 for why this is currently the case. I agree - it's really not optimal at all.

Hi, I don't believe this is entirely the case - for us at least.
We are using your test adapter with vstest directly and are specify the /TestAdapterPath:
Because of the way we are using your test adapter our code entry point is RunTests sources. I can see from your code base there is a temporary 'hack' whereby you are taking the assemblies, discovering the individual tests and calling mspec for each and every one rather than just passing on the assembly name and letting the mspec runner do the magic.
I have reinstated the 'RunAssembly' call and it works fine for us... and massively improves performance, we also have about 15,000 tests of which about 8,000 are mspec and it works fine.
Does this change your understanding of our problem?
Thanks.

Thanks for the clarification. I see what you mean. There is still a performance issue when using the adapter in Visual Studio, but for the CI scenario we can look to improve the code path as per your comment. I will try to have a look when I get a chance to improve that for this scenario. Meanwhile I am also working on solving the issue once and for all for all scenarios.

Awesome!
I have just finished making changes to the method myself for testing in our usage.. it is crude... but it has literally halved from 6 to 3 mins our test run times..
Total tests: 15585. Passed: 15585. Failed: 0. Skipped: 0.
Total MSTest Time: 00:03:15.8153955
 public void RunTests(IEnumerable<string> sources, IRunContext runContext, IFrameworkHandle frameworkHandle)
        {
            string currentAsssembly = string.Empty;

            try
            {
                ISpecificationExecutor specificationExecutor = this.adapterFactory.CreateExecutor();
                int count = sources.Count();

                foreach (var source in sources)
                {
                    currentAsssembly = source;

                    frameworkHandle.SendMessage(TestMessageLevel.Informational,
                        string.Format(Strings.EXECUTOR_EXECUTINGIN, currentAsssembly));

                    specificationExecutor.RunAssembly(currentAsssembly, MSpecTestAdapter.uri, runContext,
                        frameworkHandle);
                }

                frameworkHandle.SendMessage(TestMessageLevel.Informational, string.Format("Complete on {0} assemblies ", count));
            }
            catch (Exception ex)
            {
                frameworkHandle.SendMessage(TestMessageLevel.Error,
                    string.Format(Strings.EXECUTOR_ERROR, currentAsssembly, ex.Message));
            }
        }

In that case - how do you feel about creating pull request for review to avoid duplication of effort? :)

I had a feeling you'd say that..... TBH I think it is worth someone who is closer to the understanding looking at what I've done above.
It is almost certainly NOT correct....

It's actually fine :) :+1: I did some tiny cosmetic changes in my own pull request and will merged it.


Ensure k8s views are correctly hidden.

Filter unconnected psuedo nodes from the Pods view
Don't report these filtered nodes in stats
Fix typo in logic for hiding views

Fixes #1214

@paulbellamy PTAL

The number of nodes filtered still seem odd.

what 32 nodes are being filtered?

Also, I still think the SilentFilter thing seems overcomplicated and error-prone. e.g. It will still count the internet node being filtered out as part of the container renderer.

The number of nodes filtered still seem odd.

I think the stats in the bottom left lag slightly; when I do this I get 39 NODES (7 FILTERED) (which is still wrong).

Mine's been showing 12 nodes (34 filtered) for 28 minutes. When there are 39 nodes visible...

Try refreshing?  Otherwise its a UI bug.

Ah yeah. Now I get 39 nodes (6 filtered), which is still wrong. It occurs to me that maybe any filters used in render/topologies.go should be silent, and only the ones applied (at the end) by the UI widget should count towards the (X filtered) statistic.

@paulbellamy yup, I agree.  Have made them all silent now; which also means we need to silently filter some non-pseudo nodes.  WDYT?

Probably also want SilentFilterNonProcspied

LGTM. I take back what I said about SilentFilter not being the right abstraction. When applied to all the internal filters, it's great.


Implement LoopModeOverride to AnimationNodeAnimation to properly manage the loop state for each AnimationTree

Closes #79208.
Implement the LoopModeOverride parameter to the AnimationNodeAnimation.
Context: https://github.com/godotengine/godot/issues/79208#issuecomment-1633283541
AutoAdvance should not be executed for looping animations, since it is undecided where the animation will end. However, there are cases where AutoAdvance is executed at the appropriate time after looping several times.
The straightforward way to solve this is to disable the Animation's Loop at any intended timing. However, changing the Loop property of an Animation resource will affect all the multiple AnimationTrees and AnimationPlayers that reference it.
Therefore, by implementing LoopModeOverride as a parameter of AnimationNodeAnimation, the loop state of the animation can be managed for each AnimationTree as a node.
This makes it easy to manage the looping state of animations for multiple characters.

@lyuma How should I do?

I'm a little bit nervous about this workaround for a few reasons. While I'm not against introducing an AnimationTree specific overwrite of looping state for animation, I feel that implementing it in the parameter list feels quite janky. I'm also unsure if this solves the underlying issues with the AtEnd transition. While there may be some ambiguity on what constitution an AtEnd transition, I would like to investigate a more explicit fix. I could still be in favour of looping overrides in a more general sense, but I am unsure of this specific implementation.

The cause of this problem is clear.
The progress of a StateMachine is taken from the remaining time of its child animation nodes. However, child nodes can be nested, and in that case it is not clear which node's remaining time should be prioritized.
Currently, the node with the longest remaining time is selected, but this may cause unintended transitions (e.g., firing AtEnd in favor of End of an animation with a short remaining time).
Therefore, currently, for such cases where the remaining time is ambiguous, we have no choice but to set the time to infinite, and the only way to do so is to manually break the loop.
Even in such a case, the StateMachine does not know the progress at the time of the transition command, so it must choose between a forced transition or an interruption of the nested child animation loop.

Instead of a progress bar, it might be better to have a notation telling people that the length is infinite. Like ♾ or infinit?

Superseded by https://github.com/godotengine/godot/pull/87171


First-person voice in the docs are a pain read

The first-person Valibot voice seems cute but has been a terrible experience when you just want to get work done and some random sentence is written in first person. I'm often broken out of flow often to translate into third person to understand what it means.

In addition, I can help you to perform more detailed validations and transformations with the pipe method.

😒

It is harder to read. It is likely often 0 value for developers and in my case almost always negative value.
It probably harder to write for you (and contributors). Writing in first-person likely needs you to mentally translate from a "regular" voice only for us readers to mentally translate it back.

Please write docs normally. No first-person please.

Thank you for your feedback. I will consider it in the long run.

For what it's worth, I love the personality this brings to the docs but can understand it's not for everyone

I agree. Up until now, the current approach has had many benefits for the project. It has helped us tell a story and differentiate ourselves from other projects.

Oh wow, I also wanted to create same issue long time ago.
Reading the docs always felt so weird, happy to see I'm not the only one 😅
Never had such issue with other libraries docs though.

Thank you for your feedback!

This is something that annoys and confuse me too when reading the documentation. I really can't follow the storytelling style, to the point that I try to completely avoid reading it. That being said, I still use Valibot as the main validation library in my project and I'll continue to use it.
BTW, here's a HN discussion about someone not wanting to consider Valibot just for that:
https://news.ycombinator.com/item?id=41790418

Thank you for your feedback! I will probably change this before our v1 release.

Too bad. I found it refreshing and fun.

😢

Too bad. I found it refreshing and fun.

I'm with you, mate. It made the docs enjoyable to read.

Sorry 😌

There's no way you're going to please everybody. 😄

I believe that:

People who tolerate the story telling style could still use the docs easily without it.
People who don't tolerate the story telling style would have a very hard time using the docs.

So it's a wise decision to drop it and this will make the docs usage experience decent for both categories.

I kept the first-person voice in the README and the introduction guide. I think it is a good mix.


Feature request: Stream the video to an external device, wirelessly

I've seen/heard this feature request before, but could not find it mentioned here, so here goes:
Using the the WiFi module to stream the video seen on the goggle screen, to an external device would be awesome.
Perhaps create an rstp endpoint, so that smartphone or computers or the same WiFi network could access the live streaming?
This would allow the live stream to be processed and recorded directly in an external device, and could be used to add effects to the video stream live.

personally i was thinking we go a little more modern with HLS and/or DASH, a raw MPEG-TS stream might be another option.

Couldn't this issue be closed? Video streaming over the external module already works for some time now 😉

Solved.


ERROR: tools/python/transform/onnx_converter.py:571: Mace does not support onnx op type Tdnn yet

Mace does not support onnx op type  Kaldi Tdnn yet?

@beyondych11 Yes, it's not supported yet. I saw a developer use an alternative method: in Kaldi's model definition file（ final.config ）, transformed the definition of Tdnn into an equivalent Affine, and then use Kaldi to train the network(the Affine is supported in MACE).

@beyondych11 Yes, it's not supported yet. I saw a developer use an alternative method: in Kaldi's model definition file（ final.config ）, transformed the definition of Tdnn into an equivalent Affine, and then use Kaldi to train the network(the Affine is supported in MACE).
OK！thank for your reply!

@lu229 Hi！In my opinion, MACE is used to accelerate the inference of kaldi AM. But how to deploy the kaldi decode part on the mobile(android or ios) based on MACE? Are there some reference documents?

@beyondych11 Sorry for the late reply. MACE is a deep-learning framework on mobile devices and micro-controllers. Kaldi-ONNX is a tool for porting Kaldi Speech Recognition Toolkit neural network models to ONNX models for inference. The decoding part of Kaldi does not involve deep learning model, so you may need to deploy it yourself.


test presubmit

looks like the tests is flaky. I'm encountering the same issue: sometimes it passes, sometimes not. I suspect it's due to env variables set and not unset properly.

Yeah, I was testing linters and it looks like the yamllint one is broken since it passes though it finds issues. #283


Show participant detail and profile picture

Profile picture and name of participants in edit page and detail page
Show number of participant in edit page
minor fix for long detail that will go out the box in detail page
minor fix for card box in edit page when activity has many details, it will unable to scroll up to the top

@TeerapatTrepopsakulsin at least it should tell something that better than undefined. Edit activity restricted to host problem.


Offload policies support cross multiple clusters

Master Issue: #13444
Motivation
Offload policies support cross multiple clusters
Documentation

[x] no-need-doc

/pulsarbot rerun-failure-checks

/pulsarbot rerun-failure-checks

/pulsarbot rerun-failure-checks

@315157973  @eolivelli
PTAL :)

/pulsarbot rerun-failure-checks

/pulsarbot rerun-failure-checks

/pulsarbot rerun-failure-checks

@codelipenghui  @BewareMyPower @315157973  @eolivelli  @Technoboy-
PTAL :)

+1
We should figure out a way to not pass secrets from the cli, but this is something to do in a follow up patch probably

Thanks to you @eolivelli , i will do that in a follow up patch.

@315157973
PTAL : )

@mattisonchao Could you please help resolve the conflicts?

@mattisonchao Could you please help resolve the conflicts?

Conflict has been fixed. PTAL

/pulsarbot rerun-failure-checks


chore: adding code space configuration

Add a codespace configuration that makes it easy to open the project and run the unit tests.
Also adding a set of EXTRA_DEPS in setup to easily install additional requirements needed for testing.
Though, still have some work to do to get the tests working, this config loads them into VSCode test browser.

Closing this for now, since we're going to stick closely to the developer setup with azdev and a python virtual environment.


Detecting caner driver genes

Hi,
I am new to analyze somatic mutation variants. So I followed the process in maftools manual.
My data is breast cancer samples, and the clinical data contains three phenotypes ER, PR and HER-2.
I want to detect the cancer driver genes. I followed the manual. The code was showed below:
##Detecting cancer driver genes based on positional clustering
mf.sig = oncodrive(maf=mf, AACol="Proein_Change", minMut =5, pvalMethod='zscore')
I got the error:
Estimating background scores from synonymous variants..
Error in eval(jsub, SDenv, parent.frame()) : object 'AAChange' not found
Could you tell me how to detect cancer driver genes?
Many thanks.

Hi,
Please accept my apologies for late reply.
Did you figure out the issue ? Argument AACol takes the column name under which protein change information is stored. Use function getFields() to see available columns in the maf.

@Jwang412 See if this helps: https://github.com/PoisonAlien/maftools/issues/16#issuecomment-401152757


Suggested syntax in Dockerfile for $PORT?

Perhaps the documentation can show an example of how to create a new image allowing for a $PORT environment var using this one.

Just curious, what's this?
    <init-param>
      <param-name>expires</param-name>
      <param-value>666</param-value>
    </init-param>

https://github.com/docker-library/tomcat/issues/169#issuecomment-512101112

it requires modification of XML configuration to change the port -- we currently do not do anything to the default XML configuration provided by Tomcat upstream, and we don't have any plans to do so.

And that snippet looks like an ssl expiry parameter

Thank you for responding and helping support the Tomcat image.
Am trying to figure out how to set the port by Env variable.  Are you aware of a tutorial or discussion you can point me to?
Also, the expiry parm just happens to be the Mark of The Beast (666)!
Regards,
C

On May 26, 2021, at 1:31 PM, wglambert @.***> wrote:
#169 (comment) https://github.com/docker-library/tomcat/issues/169#issuecomment-512101112
it requires modification of XML configuration to change the port -- we currently do not do anything to the default XML configuration provided by Tomcat upstream, and we don't have any plans to do so.
And that snippet looks like an ssl expiry parameter
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/docker-library/tomcat/issues/228#issuecomment-848973073, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARAJCFCRB7ZKVEWA4RZ6KV3TPUV5VANCNFSM45R5ECSQ.

You would need to provide a modified server.xml that can substitute the value for the environment variable
https://stackoverflow.com/a/15556920
It seems unnecessary when you can just have Docker forward whichever port you want to the container (which is listening on port 8080 by default)
https://docs.docker.com/config/containers/container-networking/#published-ports
https://github.com/docker-library/docs/tree/master/tomcat#how-to-use-this-image
You could also try asking over at the Docker Community Forums, Docker Community Slack, or Stack Overflow. Since these repos aren't really a user-help forum

Agree it does seem unnecessary. But it’s an issue for Heroku which assigns a port at runtime.
There are workarounds, (ie web runner) but I think solving it will help my  understanding of Docker.
Thank you again and Regards…
C

On May 26, 2021, at 2:06 PM, wglambert @.***> wrote:
You would need to provide a modified server.xml that can substitute the value for the environment variable
https://stackoverflow.com/a/15556920 https://stackoverflow.com/a/15556920
It seems unnecessary when you can just have Docker forward whichever port you want to the container (which is listening on port 8080 by default)
https://docs.docker.com/config/containers/container-networking/#published-ports https://docs.docker.com/config/containers/container-networking/#published-ports
https://github.com/docker-library/docs/tree/master/tomcat#how-to-use-this-image https://github.com/docker-library/docs/tree/master/tomcat#how-to-use-this-image
You could also try asking over at the Docker Community Forums https://forums.docker.com/, Docker Community Slack https://dockr.ly/slack, or Stack Overflow https://stackoverflow.com/search?tab=newest&q=docker. Since these repos aren't really a user-help forum
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/docker-library/tomcat/issues/228#issuecomment-849004325, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARAJCFGLJQDRICHGP7SDQ7TTPU2BTANCNFSM45R5ECSQ.

这是来自QQ邮箱的假期自动回复邮件。

您好，我最近正在休假中，无法亲自回复您的邮件。我将在假期结束后，尽快给您回复。


Suggestions for ouliner in markdown to html

Hi, so glad to find this project! I use Dynalist.io/ quite a bit and used to use Fargo and Workflowy (or LoqSeq). I want this same functionality in my own static website (the reader part). I see you use a Details HTML Element in the readme for the collapsed text section. I've been looking at ways to integrate this with markdown (link below). Do you have any suggestions?
Somehow the converter needs to translate Markdown nested lists (with maybe a + to designate the open state) into HTML Details with Blockquote. Most converters (https://markdowntohtml.com/) convert to nesting of HTML lists.
I read your note about Pandoc lists but need to look more closely at the hangups it has.
https://gist.github.com/pierrejoubert73/902cc94d79424356a8d20be2b382e1ab?permalink_comment_id=4320038#gistcomment-4320038

If youre interested, I plan to use Dave Winer's @scripting (of Fargo and Little Outliner fame) Concord for editing and notetaking, and this tool which exports the markdown/opml files to HTML and has some wiki backlink functionality like LogSeq but without the large application.
https://github.com/interstar/owl-electron/issues/1


add experimental FROST/EdDSA signature combination

Description
Adds support to combining FROST-type signature shares to the crypto package.
Relies on https://github.com/LIT-Protocol/lit-ecdsa-wasm-combine/pull/5.
NOTE: the way this functionality is exposed in the api is not ideal, and only temporary. (Namely, it was added to the combineEcdsaShares method, despite we are not dealing with ECDSA, and the input/output types do not conform to the signature of that method.)
Type of change

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

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Checklist:

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

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

@cairomassimo
Can we start a feature branch for this work on https://linear.app/litprotocol/issue/LIT-2262/eddsa-and-schnorr
since this is being tracked as a project we can make a feature branch and merge it into that.

Closing in favor of #341


The section for adding a workitem using a template says to copy the url...

... but not what to do with that URL

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

ID: 1debd814-eb48-c984-a4f9-7606093e9617
Version Independent ID: f48ef796-c2e3-8fa3-6c41-326a5b252a3d
Content: Add and use work item templates to update user stories, tasks, issues, and other work items - Azure Boards
Content Source: docs/boards/backlogs/work-item-template.md
Product: devops
Technology: devops-agile
GitHub Login: @KathrynEE
Microsoft Alias: kaelli

@StingyJack - Thank you for your feedback. I've updated the article to indicate that the URL is used to open the template in a browser.


Using a variable to define a color ramp does not work

Related with https://github.com/CartoDB/carto-vl/issues/555#issuecomment-411888652
Description
When we define a variable as a color array and pass it to a ramp expression, it does not work.
Examples:
    const viz = new carto.Viz(`
        @category_colors: [#FF0066, #0055AA, #99BB99]
        color: ramp(linear($popCount, 0, 200), @category_colors)
    `);

    const viz = new carto.Viz(`
        @category_colors: [pink, red, darkRed]
        color: ramp(linear($popCount, 0, 200), @category_colors)
    `);

Expected behaviour
Above examples should work without errors.

Fixed by #917


Full example

H
Is there a full example which shows how to upload objects? list the objects? list the buckets?
Can you please also add more details how to set the configuration from the service credentials?

How to map from here:
const cred = {
  "apikey": "xV.......",
  "endpoints": "https://cos-service.bluemix.net/endpoints",
  "iam_apikey_description": "Auto generated apikey ......",
  "iam_apikey_name": "auto-generated-apikey-......",
  "iam_role_crn": "crn:v1:....",
  "iam_serviceid_crn": "crn:v1:bluemix:.....",
  "resource_instance_id": "crn:v1:bluemix:public.......::"
}

To here:
{
  endpoint: '',
  apiKeyId: '',
  ibmAuthEndpoint: '',
  serviceInstanceId: ''
}

The example code in the readme shows the mapping of the values:
    endpoint: '<endpoint>',
    apiKeyId: '<api-key>',
    ibmAuthEndpoint: 'https://iam.ng.bluemix.net/oidc/token',
    serviceInstanceId: '<resource-instance-id>'

For more information on service credentials, check out the docs.
For more information on selecting endpoints, check out the docs.
For more details on how to upload objects using the package, see the API docs.

In addition to the info provided above, here is a full list objects for a bucket example if it helps:
const AWS = require('ibm-cos-sdk');
const s3 = new AWS.S3({
	apiKeyId: "apikey",
	endpoint: "s3-api.us-geo.objectstorage.softlayer.net",
	ibmAuthEndpoint: "https://iam.ng.bluemix.net/oidc/token",
	serviceInstanceId: "resource_instance_id"
});
var params = {
	Bucket : "bucketName",
	MaxKeys: 5000
};

s3.listObjects(params, function(err, data) {
	if (err) {
		console.log('listObjects Error',err, err.stack); // an error occurred
	} else {
		console.log('listObjects Returned',data);        // successful response
	}
});

Sufficient information provided in the earlier comments, closing this issue.


[Bug] The White screen is displayed on the opened app after collapsing the app by double tapping on the device Back button

Description

fixed build config
adjusted stores containers initialization

About #3259
How Has This Been Tested?
Please describe the tests that you ran to verify your changes.
Checklist:

[x] PR title matches follow: (Feature|Bug|Chore) Task Name
[x] My code follows the style guidelines of this project
[x] I have followed all the instructions described in the initial task (check Definitions of Done)
[x] I have performed a self-review of my own code
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[x] I have added reference to a related issue in the repository
[x] I have added a detailed description of the changes proposed in the pull request. I am as descriptive as possible, assisting reviewers as much as possible.
[ ] I have added screenshots related to my pull request (for frontend tasks)
[ ] I have pasted a gif showing the feature.
[x] @mentions of the person or team responsible for reviewing proposed changes

What was the source of the bug?

Component "n" does not seem to be nested in an Undux <Container>.
Store failed with exception: Cannot read property \'get\' of null', [TypeError: Cannot read property 'get' of null]
GD store's container is removing from the JSX in some cases, the store also destroys. App is trying to render something / access store and crashes
This happens because GDStore.Container is located under Router component which is lazy loaded.
I moved it to the app holder with the SimpleStore's container


ISPN-15503 Protostream 5.0.0.Dev01

https://issues.redhat.com/browse/ISPN-15503
Won't compile since this PR depends on Protostream 5.0.0-SNAPSHOT

Failures are unrelated


Pass entire int array to picosat_add_lits once per clause, in AddClauses()

This improves performance when passing a bunch of clauses, by reducing the number of times we need to call into C. Instead of once per literal, it is once per clause.

Your code is faster, but I'm wondering if the API is now a little confused. You can end a clause in the middle of a slice by using a zero instead of a literal. Or you can end a clause by having the slice end.
One approach: the only way to end a clause is at the end of a slice, and zeros caused errors. Pro: more idiomatic for Go authors. Con: slower (since it would require keeping my old code [with modifications] that uses C.picosat_add()).
Another approach: the only way to end a clause is with a zero. Pro: faster since we can use C.picosat_add_lits() directly without scanning the contents. Con: Confusing? Like, why allow slices if the slice doesn't mean anything.
I'm leaning toward the first one. Thoughts?

Ah you are right. I didn't realize I was actually changing the behavior until you pointed it out. I can think of a possible 3rd approach that is a mixture of yours...
The real costly aspect of the call is the C.picosat_add(), so what if we make it so that we still loop over each value in the given clause, looking for 0, and then call C.picosat_add_lits() on slices of the clause around the zero values? That is, if your clause was: [1,0,2,0,3], then it would call C.picosat_add_lits() 3 times, with:
C.picosat_add_lits(p.p, (*C.int)(&(clause[0:1)][0]))
C.picosat_add_lits(p.p, (*C.int)(&(clause[2:3)][0]))
C.picosat_add_lits(p.p, (*C.int)(&(clause[4:5)][0]))

That way you still get only one call to add all of the literals if you are actually passing a large single clause. What do you think?

Decided the documentation was clear and the speed up was important. Thanks for your help.

Awesome! Happy to contribute.
On Sun, 15 Feb 2015 6:27 PM William Schwartz<EMAIL_ADDRESS>wrote:

Decided the documentation was clear and the speed up was important. Thanks
for your help.
—
Reply to this email directly or view it on GitHub
https://github.com/wkschwartz/pigosat/pull/3#issuecomment-74404802.


Permissions error with chmod

Hello,
I am having issues getting my docker containers up and running without restarting. The first two containers are running without any issues but the postgres one (tried on 10.11 and 10.12) is thowing the error:
chmod: changing permissions of '/var/lib/postgresql/data': Operation not permitted

I am running from an elevated powershell window if that matters. Would it be as simple as setting the user to a different value than the default? I am afraid that I can't get into the container itself to see what is going wrong beyond the message above as that is all that:
docker-compose logs db

is supplying to me. I recognise that it may be something that I have done but in the off chance that it is not wanted to make you aware. Thank you.
version: '3'
services:
  nginx:
    restart: always
    image: nginx:latest
    container_name: ng01
    networks:
      - default
    ports:
      - "80:80"
    volumes:
      - .:/src
      - ./config/nginx:/etc/nginx/conf.d
    depends_on:
      - web
  web:
    restart: on-failure:5
    build:
      context: .
      dockerfile: Dockerfile
    container_name: dg01
    env_file:
      - .env
    command: bash -c "python pmv3/manage.py runserver <IP_ADDRESS>:8000" # Do this after makemigrations && python pmv3/manage.py migrate && cd pmv3 &&  gunicorn --config=gunicorn_config.py pmv3.wsgi:application"
    depends_on:
      - db
    volumes:
      - .:/src
    expose:
      - "8000"
    networks:
      - default
  db:
    image: postgres:10.12
    container_name: pg01
    restart: always
    environment:
      POSTGRES_DB: a
      POSTGRES_USER: b
      POSTGRES_PASSWORD: c
    ports:
      - "5432:5432"
    volumes:
    - ./sql_backups:/home
    - pg_data:/var/lib/postgresql/data

volumes:
  pg_data:

Docker version 17.10.0-ee-preview-3, build 1649af8
docker-compose version 1.25.4, build 8d51620a
Windows Server 2019 Datacenter
The suggestion in a suggested thread to try:
pg_data:/var/lib/postgresql/data:z

did not work either
Trying to add the environmental variable
PG_DATA: /var/lib/postgresql/data/pgdata

doesn't work nor does adding
user: root
I do recall in Docker desktop there is an option to give permission to the c:drive but I don't know if that is required with this version of docker.
Cheers
Edit: Ended up just switching from a windows server to an ubuntu one and it worked instantly.

Since you were on Windows Server, this was probably via LCOW, right?
I think https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/linux-containers#work-in-progress is probably relevant, even that section about bind mounts.  I'm not 100% sure how it handles local named volumes, but I think they're technically Windows volumes which then get shared to the Linux container, which would cause exactly the permissions errors described (as noted in that linked documentation).

Brilliant cheers for finding that, thankfully I was able to switch the server os so worked around it but useful to know for the future.


[DO NOT MERGE] Auto PR to update dependencies of istio

This PR will be merged automatically once checks are successful.
none

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
48219bff621cdca465961d2ab28a9496dbbf4c27
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
48219bff621cdca465961d2ab28a9496dbbf4c27
link
/test istio-pilot-e2e

prow/istio-presubmit.sh
48219bff621cdca465961d2ab28a9496dbbf4c27
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Update Dokka to 1.4.30

Dokka 1.4.30 now supports multimodule project natively, so a custom documentation index is not required.

Performance regression in Dokka significantly slowed down snapshot upload pipeline.


chore(carbon-accounting): fix CVE-2022-25881 CVE-2021-39167

Commit to be reviewed

examples(carbon-accounting):fix CVE-2022-25881 CVE-2021-39167
Primary Changes
----------------
1. Modified the Dockerfile to use the updated versions
   of the packages being used
2. Modified the supervisord.conf to use the correct path
   because it has changed after updating the versions

Fixes #2062
Pull Request Requirements

[x] Rebased onto upstream/main branch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.
[x] Have git sign off at the end of commit message to avoid being marked red. You can add -s flag when using git commit command. You may refer to this link for more information.
[x] Follow the Commit Linting specification. You may refer to this link for more information.

Character Limit

[x] Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
[x] Commit Message per line must not exceed 80 characters (including spaces and special characters).

A Must Read for Beginners
For rebasing and squashing, here's a must read guide for beginners.

@aldousalvarez Please specify in the commit subject and the PR title the top 1 or 2 CVEs that are being addressed by the pull request so that it is as unique as possible within the 72 characters limit.

Already updated it with the top 2 CVEs that are being addressed by this pull request. With this fix we can also close the issue #2718 because all the vulnerabilities are now fixed by this PR

@aldousalvarez Run yarn install to update the lock file to fix the CI

@petermetz already fixed it, PR lint check is now passing and is up to date with the upstream/main


Fixed issue #7674

This fix allows to configure a command class to be used by the connection component.
Also it uses the DI container instead of creating the object on its own.

Then I think it's ready for merge!

merged https://github.com/yiisoft/yii2/commit/f1e8a8f25802af7a1403cbf5e3baf73e4a677761

reopening for discussion of my comment https://github.com/yiisoft/yii2/pull/10740#discussion_r51864144

thats a good point. CreateCommand is used many, many times in a Request. Every extension will slow down the request.
Within this case, Yii::createObject should be replaced by:
$commandClass = $this->commandClass;
$command = new commandClass()

Why do we need a separated variable commandClass?

That is something I considered as well @SilverFire, we could also go with pure DI but Yii historically uses  a configuration variable for this purpose..
That way I can configure the class to use in the configuration (as I do for most of my components).

I propose to change it like this, any objections?
diff --git a/framework/db/Connection.php b/framework/db/Connection.php
index 9adc2ad..c1af541 100644
--- a/framework/db/Connection.php
+++ b/framework/db/Connection.php
@@ -626,10 +626,10 @@ class Connection extends Component
      */
     public function createCommand($sql = null, $params = [])
     {
-        $command = Yii::createObject([
-            'class' => $this->commandClass,
+        /** @var $command Command */
+        $command = new $this->commandClass([
             'db' => $this,
-            'sql' => $sql
+            'sql' => $sql,
         ]);

         return $command->bindValues($params);

I object but my objection is mostly from a theoretical standpoint since for my specific use cases it won't matter ;-)

Why do we need a separated variable commandClass

Because I thought PHP didnt accept it at all times. Perhabs this is because I (still) have a server with a very old PHP version.

https://github.com/yiisoft/yii2/commit/b43ebcc368e5da2caed418a2a976cf847051780c

@dynasource seems to work on PHP >= 5
https://3v4l.org/v8O41
How old PHP version do you have on your server? O_o

its not that old ;). I I was confusing:

not allowed: $this->class::method()
allowed: new $this->class()

Okay :D


Add PR instructions to README

Add instructions on how to use GitHub forks to make a PR to this repository, as there have been a few questions around that. Should probably go in CONTRIBUTING.md and can be a resource to point to as the question comes up.

Hi, noticed there is a PR section in the contributing.md file now, do you want this updated/made more clear for people or should this issue now be closed?

Good call, thanks @AndyMc629 !


KAFKA-13746: Attempt to fix flaky test by waiting to fetch 2 topics f…

…rom describe topics command
More detailed description of your change,
if necessary. The PR title and PR message become
the squashed commit message, so use a separate
comment to ping reviewers.
Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@guozhangwang , I added a fix for this test.. Plz review

Thank you for this PR, in fact, I haven't seen this flaky test happen, however, it's worth fixing it, left a minor comment.

@dengziming , thanks for the review. Actually I saw a couple of instance of this one failing. Like this one failed 2 days back => https://ci-builds.apache.org/blue/organizations/jenkins/Kafka%2Fkafka-pr/detail/PR-11438/2/tests

Thanks @vamossagar12 , the failed tests still contains testDescribeUnderMinIsrPartitionsMixed(String).quorum=zk](https://ci-builds.apache.org/job/Kafka/job/kafka-pr/job/PR-12104/4/testReport/junit/kafka.admin/TopicCommandIntegrationTest/Build___JDK_17_and_Scala_2_13___testDescribeUnderMinIsrPartitionsMixed_String__quorum_zk_2) which seems relevant. Do you want to take a look into them before I re-trigger the build?

Details

@guozhangwang , Thanks for pointing it out. I will take a look at this and make another commit which should re-trigger the build.

Hello @vamossagar12, sorry for changing around, we added a TestUtils.ensureConsistentKRaftMetadata in #12108 to fix this kind of flakiness, which waits until the brokers have caught up to the controller metadata topic end offset, instead of waiting for something really specific, you can just use this method for KRaft mode, and keep it was for zk mode.

Thanks @vamossagar12 , the failed tests still contains testDescribeUnderMinIsrPartitionsMixed(String).quorum=zk](https://ci-builds.apache.org/job/Kafka/job/kafka-pr/job/PR-12104/4/testReport/junit/kafka.admin/TopicCommandIntegrationTest/Build___JDK_17_and_Scala_2_13___testDescribeUnderMinIsrPartitionsMixed_String__quorum_zk_2) which seems relevant. Do you want to take a look into them before I re-trigger the build?

@guozhangwang , looks like the tests passed this time after the latest fixes.


Avoid using numpy.nonzero in _make_decorator

See the description of #2387.

Jenkins, test this please

Jenkins CI test (for commit c5e13662a7228642430d36018fd8c8f1655216de, target branch master) failed with status FAILURE.

LGTM


EF Tools 1.1.0-preview4 Unrecognized option '--config'

Notes by @rowanmiller
This affects just the 1.1.0-preview4 tools on apps that target full .NET (rather than .NET Core). I have not been able to find a way to workaround this with the latest tools preview.
The best option right now is to roll back to the 1.0.0-preview3 version of the Microsoft.EntityFrameworkCore.Tools.DotNet package. Fortunately, because of the way things are factored, you can keep using the 1.1 versions of all the other packages.
  "tools": {
    "Microsoft.EntityFrameworkCore.Tools.DotNet": "1.0.0-preview3-final"
  },

Steps to reproduce

Upgrade nuget packages from v1.0.1 to v1.1.0.
Use 'dotnet ef' to generate migrations
Error: Unrecognized option '--config'

I've tried to delete the older SDK and runtime, but it doesn't solve the problem.
The issue
It's not possible to generate migrations with v1.1.0.
The website is building and running successfully.
Further technical details
EF Core version: 1.1.0
Operating system: Windows 10
Visual Studio version: VS2015
My project.json:
{
  "dependencies": {
    "TinyMapper": "2.0.8",
    "Hangfire.Dashboard.Authorization": "2.1.0",
    "Hangfire": "1.6.6",
    "Hangfire.SqlServer": "1.6.6",
    "Microsoft.AspNetCore.Authentication.JwtBearer": "1.1.0",
    "Microsoft.AspNetCore.Diagnostics": "1.1.0",
    "Microsoft.AspNetCore.Mvc": "1.1.0",
    "Microsoft.AspNetCore.Owin": "1.1.0",
    "Microsoft.AspNetCore.Server.IISIntegration": "1.1.0",
    "Microsoft.AspNetCore.Server.Kestrel": "1.1.0",
    "Microsoft.AspNetCore.StaticFiles": "1.1.0",
    "Microsoft.Extensions.Configuration.EnvironmentVariables": "1.1.0",
    "Microsoft.Extensions.Configuration.FileExtensions": "1.1.0",
    "Microsoft.Extensions.Configuration.Json": "1.1.0",
    "Microsoft.Extensions.DependencyInjection": "1.1.0",
    "Microsoft.Extensions.DependencyInjection.Abstractions": "1.1.0",
    "Microsoft.Extensions.Logging": "1.1.0",
    "Microsoft.Extensions.Logging.Console": "1.1.0",
    "Microsoft.Extensions.Logging.Debug": "1.1.0",
    "Microsoft.EntityFrameworkCore.SqlServer": "1.1.0",
    "Microsoft.EntityFrameworkCore.SqlServer.Design": "1.1.0",
    "Microsoft.EntityFrameworkCore.Tools": {
      "version": "1.1.0-preview4-final",
      "type": "build"
    }
  },

  "tools": {
    "Microsoft.EntityFrameworkCore.Tools.DotNet": "1.1.0-preview4-final"
  },

  "frameworks": {
    "net461": {}
  },

  "buildOptions": {
    "emitEntryPoint": true,
    "preserveCompilationContext": true
  },

  "publishOptions": {
    "include": [
      "wwwroot",
      "Views",
      "Areas/**/Views",
      "appsettings.json",
      "web.config"
    ]
  },

  "scripts": {
    "postpublish": [ "dotnet publish-iis --publish-folder %publish:OutputPath% --framework %publish:FullTargetFramework%" ]
  }
}

If you want to use package manager console to run the migrations, Microsoft.EntityFrameworkCore.Tools is necessary, because this package only contains .ps1 files, located at:
%UserProfile%\.nuget\packages\Microsoft.EntityFrameworkCore.Tools\1.1.0-preview4-final\tools
```
Also ensure `Microsoft.EntityFrameworkCore.Tools` is referenced in the `dependencies` section of your `project.json` file. NuGet won't load the Package Manager Commands from the tools section.

If you want to use `dotnet ef` commands, you will need these packages too:
```
PM> Install-Package Microsoft.EntityFrameworkCore.Tools.DotNet –Pre
PM> Install-Package Microsoft.EntityFrameworkCore.Design
```
```json
    "dependencies": {
        "Microsoft.EntityFrameworkCore": "1.1.0",
        "Microsoft.EntityFrameworkCore.Design": "1.1.0",
        "Microsoft.EntityFrameworkCore.SqlServer": "1.1.0",
        "Microsoft.EntityFrameworkCore.SqlServer.Design": "1.1.0",
        "Microsoft.EntityFrameworkCore.Tools": {
            "version": "1.1.0-preview4-final",
            "imports": [
                "portable-net45+win8"
            ],
            "type": "build"
        }
    },

    "tools": {
        "Microsoft.EntityFrameworkCore.Tools.DotNet": {
            "version": "1.1.0-preview4-final",
            "imports": [
                "portable-net45+win8"
            ]
        },
        "Microsoft.EntityFrameworkCore.Tools": {
            "version": "1.1.0-preview4-final",
            "imports": [
                "portable-net45+win8"
            ]
        }
    },
```

More on the topic #7076
I have a similar problem Unrecognized option '--config'

Confirmed what we speculated in triage: this affects just the 1.1.0-preview4 tools on apps that target full .NET (rather than .NET Core). I couldn't find a way to workaround this with the latest tools preview.
The best option right now is to roll back to the 1.0.0-preview3 version of the Microsoft.EntityFrameworkCore.Tools.DotNet package. Fortunately, because of the way things are factored, you can keep using the 1.1 versions of all the other packages.
  "tools": {
    "Microsoft.EntityFrameworkCore.Tools.DotNet": "1.0.0-preview3-final"
  },

Clearing to re-discuss in triage. To me, this would probably be patch worthy, but I'm not sure that we are planning to patch the preview tooling.

This is fixed in dev (could become preview5) and dev2 (will become msbuild2).

@bricelam does just using preview3 for full .NET projects seem like the best workaround to you?

Yes, but it depends on Microsoft.NETCore.App 1.0  which is the problem we were trying to solve with the 1.1.0-preview4 release.

Using the nightly builds would solve both problems 😉

@bricelam - If CI passes. 😜

I have the same problem, and would love to try out the nightly build. Is it available on a feed?
Any idea when 1.1.0-preview5 might come out?

Just edit project.json and change the tools back to 1.0.0-preview3.
It works with the latest EntityFrameWorkCore (v1.1.0).

Nightly feed: https://dotnet.myget.org/gallery/aspnetcore-dev

@microef Thanks, I does work. But it also requires me (and all my devs) to install platform 1.0.0 (we're on 1.1.0), which I'd rather avoid.
@bricelam Thanks, I'll try it out!

@bricelam Working excellently. Thanks.

Any new on this? In my case the proposed workarounds don't work, neither using the nightly builds nor downgrading the tools to 1.0.0-preview3. I'm really desesperated. I've lost two days with this and I always hit an end with an error, like this (unrecognized option --config) or this:
Could not load assembly 'Sales'. Ensure it is referenced by the startup project 'Sales'

That is absurd, as my app has only one project and is not a dll (it has also emitEntryPoint:true set).
This is my favourite one:
error: Package Microsoft.EntityFrameworkCore.Tools.DotNet 1.0.0-preview3-final is not compatible with netcoreapp1.0 (.NETCoreApp,Version=v1.0). Package Microsoft.EntityFrameworkCore.Tools.DotNet 1.0.0-preview3-final supports: netcoreapp1.0 (.NETCoreApp,Version=v1.0)
I've read it five times to get sure that in the second sentence is telling just the opposite of the first one.
Is this a joke? I'm getting crazy with so many versions of everything and I only want to create a migration, it doesn't matter wich version of the tools I have to use... Is there a valid option nowadays? Is very far the next release of the tools? This seems a rabbit hole I can't scape... Please tell me what is the maximum version I can target to get this work

@SocVi100, it looks like you got to the bottom it. Well done! x86 will be supported in the new MSBuild-based tooling (for best results, wait for version 1.0.0-msbuild3-final or use the feature work nightly feed).

@bricelam, thanks! It has been a hard way though...
I don't know yet where the "platform": "x86" setting came from. I didn't want to target any platform specifically but in some moment it "slipped in".
Anyway, I pity you all in the team, there has been too many changes on key aspects since the "vnext" started its road and that burns anybody a lot. I supose it may be hard to work with so many changing  premises.

@bricelam
Package Microsoft.EntityFrameworkCore.Tools.DotNet 1.2.0-preview4-22878 is not compatible with net461

@AR1ES - Are you using project.json based project? If yes then you need to put Tools.DotNet package under "tools" node instead of "dependencies".

@smitpatel , thanks. Tools.DotNet was under tools section and under dependencies.

Hey,
After reading all this above I can still not figure out the problem or solution. We have this project.json file content:
{
"dependencies": {
"Microsoft.AspNetCore.Hosting": "1.1.0",
"Microsoft.AspNetCore.Server.IISIntegration": "1.1.0",
"Microsoft.AspNetCore.Server.Kestrel": "1.1.0",
"Microsoft.EntityFrameworkCore": "1.1.0",
"Microsoft.EntityFrameworkCore.Design": "1.1.0",
"Microsoft.EntityFrameworkCore.SqlServer": "1.1.0",
"Microsoft.EntityFrameworkCore.SqlServer.Design": "1.1.0"

},
"tools": {
"Microsoft.EntityFrameworkCore.Tools.DotNet": "1.1.0-preview4-final"
},
"buildOptions": {
"emitEntryPoint": true
},
"frameworks": {
"net462": {}
},
"configurations": {
"TestDebug": {},
"TestRelease": {}
}
}
We get the error "Unrecognized option '--config' when we run the following CLI cmd from the cmd line console:
dotnet ef dbcontext scaffold "Server=;Initial Catalog=;Persist Security Info=False;User ID=;Password=;Pooling=False;Encrypt=True;TrustServerCertificate=False;" Microsoft.EntityFrameworkCore.SqlServer --output-dir models --force
We are on Windows 10 (latest patches). VS 2015 (latest patches). We also have installed on the dev machine VS 2017 to play with it (Not clear if that somehow messed us up).
We tried rolling back to "Microsoft.EntityFrameworkCore.Tools.DotNet": "1.0.0-preview3-final" but get a message we do not have the 1.0.0 framework installed.
We looked for Microsoft.EntityFrameworkCore.Tools.DotNet 1.2.0-preview4-22878 but cannot find it in the nuget pkg list. Is it a daily build?
Any definitive ideas or help will be greatly appreciated.
P.S. Sorry to say, because we love .NET Core so far but this just feels like a mess that we cannot seem to get clarification on. We just cannot be expected to work our way through all these various versions, etc when we are supposedly doing an upgrade to a stable release. I know you guys are working hard and it is appreciated but sometimes it feels like we are back in dll hell from years ago, except now its packages, sdks and platforms with all different versions and endless possible combinations. Sorry just needed to get that out. I know it will get better.

@chassq, my working solution was to use 1.1.0-preview3-final.
I had a lot of different errors. Initially 1.1.0-preview3-finals did not work.
Try the following steps:

Set "Microsoft.EntityFrameworkCore.Tools.DotNet": "1.0.0-preview3-final" under tools section in the project.json.
Execute dotnet restore
3!!!. Delete bin/obj from project directory
Execute dotnet build
Execute ef command dotnet ef dbcontext scaffold  .......

Thanks for the quick reply. Here is what we get now:
project.json
{
"dependencies": {
"Microsoft.AspNetCore.Hosting": "1.1.0",
"Microsoft.AspNetCore.Server.IISIntegration": "1.1.0",
"Microsoft.AspNetCore.Server.Kestrel": "1.1.0",
"Microsoft.EntityFrameworkCore": "1.1.0",
"Microsoft.EntityFrameworkCore.Design": "1.1.0",
"Microsoft.EntityFrameworkCore.SqlServer": "1.1.0",
"Microsoft.EntityFrameworkCore.SqlServer.Design": "1.1.0"
},
"tools": {
"Microsoft.EntityFrameworkCore.Tools.DotNet": "1.0.0-preview3-final"
},
"buildOptions": {
"emitEntryPoint": true
},
"frameworks": {
"net462": {}
},
"configurations": {
"TestDebug": {},
"TestRelease": {}
}
}
Restored, cleaned and deleted bin/obj per above.
Ran the CLI cmd and get this:
The specified framework 'Microsoft.NETCore.App', version '1.0.0' was not found.

Check application dependencies and target a framework version installed at:
C:\Program Files (x86)\dotnet\shared\Microsoft.NETCore.App
The following versions are installed:
1.1.0
Alternatively, install the framework version '1.0.0'.

How should we go about installing the 1.0.0 version as specified in the message?
Thanks!

@chassq Install the LTS Runtime from the .NET Core Downloads page.

Thank you very much. That did the trick. Working again.

I got this error with "Microsoft.EntityFrameworkCore.Tools.DotNet": "1.1.0-preview4-final" but it went away if I used "Microsoft.EntityFrameworkCore.Tools.DotNet": "1.1.0-preview4"

@cda-1 That's interesting. Maybe because that version doesn't exist (doesn't show up in nuget package mgr) it's actually using the previous version 1.0.0-preview3-final?

I can no longer find 1.2.0-preview4-22817 anywhere, including on the dev-feed. Luckily I had i cached, so now I'm commiting it to my repo and adding a local nuget feed for this package only.
The version numbers are a bit confusing. Has this "fix" been released in some other version that I should switch to?

If anyone here is interested in trying out the latest (MSBuild/VS2017) tools, see #7358 for details.

We cannot roll back to '1.1.0-preview3-final' because it seems to be incompatible with current version of NuGet.
Help! Blocked on critical migration
Error: "The schema version of 'Microsoft.EntityFrameworkCore.Tools.DotNet' is incompatible with version <IP_ADDRESS>5 of NuGet"

@marchy Have you tried using a more recent version of NuGet? 2.12 seems very old, as 3.5 was recently released. (Or are you stuck with VS 2013?)

Same problem here ... I tried with 1.1.0-preview4-final, 1.1.0-preview3-final and 1.1.0-preview4 and the problem still occurs with VS 2015 Update 3.
Part of my project.json :

 "dependencies": {
    "Remotion.Linq": "2.1.1",
    "Serilog.Sinks.RollingFile": "3.2.0",
    "Serilog.Extensions.Logging": "1.4.0-dev-10136",
    "System.Interactive.Async": "3.0.0",
    "Microsoft.AspNetCore.Diagnostics": "1.1.2",
    "Microsoft.AspNetCore.Mvc": "1.1.3",
    "Microsoft.AspNetCore.Server.Kestrel": "1.1.2",
    "Microsoft.AspNetCore.StaticFiles": "1.1.2",
    "Microsoft.Extensions.DependencyInjection.Abstractions": "1.1.1",
    "Microsoft.Extensions.Configuration.Binder": "1.1.2",
    "Microsoft.AspNetCore.Server.IISIntegration": "1.1.2",
    "Microsoft.Extensions.Configuration.EnvironmentVariables": "1.1.2",
    "Microsoft.Extensions.Logging.Console": "1.1.2",
    "Microsoft.Extensions.Logging": "1.1.2",
    "Microsoft.EntityFrameworkCore.SqlServer.Design": "1.1.2",
    "Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore": "1.1.2",
    "Microsoft.AspNetCore.Identity.EntityFrameworkCore": "1.1.2",
    "Microsoft.AspNetCore.Authentication.Cookies": "1.1.2",
    "Microsoft.EntityFrameworkCore": "1.1.2",
    "Microsoft.Extensions.Logging.Debug": "1.1.2",
    "Microsoft.Extensions.Configuration.UserSecrets": "1.1.2",
    "Microsoft.Extensions.Configuration.Json": "1.1.2",
    "Microsoft.EntityFrameworkCore.Tools": "1.1.1",
    "Microsoft.EntityFrameworkCore.SqlServer": "1.1.2"
  },
  "tools": {
    "Microsoft.Extensions.SecretManager.Tools": "1.1.0-preview4-final",
    "Microsoft.VisualStudio.Web.CodeGeneration.Tools": "1.1.0-preview4-final",
    "Microsoft.EntityFrameworkCore.Tools": "1.1.1",
    "Microsoft.EntityFrameworkCore.Tools.DotNet": "1.1.0-preview3-final"
  },
  "frameworks": {
    "net461": {
      "dependencies": {
        [...]
      }
    }
  },

After some tests I had to use the old version 1.0.0-preview3 and it did the job.


No "Show Derived Types" in Class View settings

Is it removed or need some conditions to active it?

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

ID: b960c4e0-ac54-9e65-6397-44d7a5750764
Version Independent ID: 224d2c57-b542-8030-6b77-ce8a7889b466
Content: View code structure using class view, call hierarchy, object browser, and code definition window - Visual Studio
Content Source: docs/ide/viewing-the-structure-of-code.md
Product: visual-studio-dev15
GitHub Login: @gewarren
Microsoft Alias: gewarren

@fairjm -- Thanks for your question. It looks like you're having an issue with the product itself, rather than an issue with the documentation. Here are a few options where you might consider asking your question:
https://social.msdn.microsoft.com/Forums/vstudio
https://www.stackoverflow.com
https://www.reddit.com/r/VisualStudio/
As well, you might also consider using the Report a Problem tool to report the issue.


[PoC] dns: implement parseLabelSequence in wasm

This patch removes the implementation of parseLabelSequence from the dns tracer package and instead implements it in an external wasm module. In this PoC, the wasm module was compiled from Golang with tinygo but it could be from other languages.
The wasm module could be moved to the containerized gadget.
Compile the wasm module:
sudo dnf install tinygo binaryen
make -C gadgets/dns-label-sequence/

$ go run -exec sudo ./cmd/ig/... trace dns
RUNTIME.CONTAINERNAME    PID    TID    COMM  QR TYPE      QTYPE NAME              RCODE  NUMANSW…
keen_stonebraker         32910  32910  wget  Q  OUTGOING  A     wikipedia.org.           0

Event generated with:
docker run -ti --rm busybox wget wikipedia.org

xref https://github.com/inspektor-gadget/inspektor-gadget/issues/1929
cc @mauriciovasquezbernal

@alban can we close it in favor of https://github.com/inspektor-gadget/inspektor-gadget/pull/2204?

Closing in favor of #2204