Proxy broken in the latest beta release

Describe the bug
I've updated recently Franz to the latest release (5.0.0-beta22) and noticed that it messed up the proxy settings.
To be more precise, previously, when setting "use proxy" to a service, without filling the fields, i was able to make the service use "direct connection", bypassing the default proxy of the OS. Not disclosing the reason behind it, though 😬
Right now, doing that doesn't change anything. It would be nice to be fixed, since it's the only reason i'm paying for premium supporter account
To Reproduce
You will need to have a proxy configured. Preferably one that filters certain services (i.e. Whatsapp, or Messenger.com)
Steps to reproduce the behavior:

Go to 'Settings'
Click on 'Your services'
Select any of them and choose "use proxy" (without filling in the fields)
Check if the default OS proxy is overridden

Expected behavior
OS proxy is bypassed and uses direct connection
Desktop:

OS: Windows 10 b1083
Franz Version 5.0.0-b22

For bypassing proxy you need to use direct:// as a proxy host. I'll add an option in the future that explicitly says "Bypass proxy".
The default setting now is to use the system proxy by default.

Thanks for the quick reply. Just tested it and it works.
I filed a bug report, because previously it was working without direct:// set as proxy

Yep, I'm aware. This was the default setting that broke Franz in a few corporate environments (whops)
But using the system proxy by default isn't usually the worst idea ;)


updated P#-specific exceptions

Refactored P#-specific exceptions:

Removed the previous PSharpException (I did not like the previous name because the namespace Microsoft.PSharp implied that its a P# exception).
Introduced the new Microsoft.PSharp.RuntimeException, which is the base exception for P# runtime-related exceptions. The user should never catch these exceptions (future TODO).
Introduced the new Microsoft.PSharp.ExecutionCanceledException, which is thrown when the P# runtime/scheduler decides to cancel the execution of a P# machine. This is now thrown instead of OperationCanceledException to make it clear that the exception was thrown by P# (and not by user code).
Introduced the new Microsoft.PSharp.LoggingException which replaces the Microsoft.PSharp.PSharpIOException (name was weird anyway :-)). This is thrown by the logger.
Replaced PSharpException with Exception in the two places in the compiler and static analyser. We can introduce compiler/static analysis specific exceptions later on.

Btw, I currently do not derive LoggingException from RuntimeException, not sure if its should or not.

Looks good to me. Lets merge it!


Polish SupportView

When navigating from Settings > Support.  The view sometimes displays data as needed and sometimes it hangs.

The current version points to an email address. Sometimes it doesn't load immediately.  I recommend having a embedded static page if the web server is unavailable.  The mobile webpage should allow user to ask FAQs and learn more about usage

This is resolved with a static email address

This is resolved with a static email address


Update MavenAuthenticateV0 task to use AGENT_TEMPDIRECTORY for settings.xml file

Task name: MavenAuthenticateV0
Description: Updated task to utilize AGENT_TEMPDIRECTORY for location of settings.xml file used in task. The MavenV2 and MavenV3 tasks already check the AGENT_TEMPDIRECTORY for the presence of this file and should not impact usage of those tasks.
Documentation changes required: (Y) Yes, location of the settings.xml file directory is now at AGENT_TEMPDIRECTORY\.m2\settings.xml. Relevant documentation reference is here.
Added unit tests: (Y) Yes, Tasks\MavenAuthenticateV0\Tests\L0.ts updated to reflect change to agent temp directory and ran locally on windows to validate
Attached related issue: (Y) #13569
Checklist:

[X] Task version was bumped - please check instruction how to do it
[x] Checked that applied changes work as expected

Bump, any progress?

@Cadacious thanks for the contribution! Could it make more sense to make this path customizable? (for example, by adding additional input for userM2FolderPath, so there will be an ability to override default value)

@aasim Please review this PR

Bump, any progress? We're facing the same race condition and it seems only small step is missing here :D


Component not found: IntesisHome

Hi,
I install this component at custom_components.
When check configuration.yaml, i have this error: Component not found: IntesisHome
Can you tell me how to install fine?
Peter
Thanks

Hi Peter,
So you have a folder called intesishome inside custom_components? You might need to put init.py in there too for it to detect it perhaps.
I've just pushed an update to intesishome.py also.

Hi jnimmo,
I downloaded and copied  files to custom_components.
But i have same error.
Perhaps, is not error of this component, i have other component and don't load too.
Any ideas?
Thank you for your time.
Peter.

Hi Peter,
You'll need three files in the following location:
custom_components/intesishome/init.py
custom_components/intesishome/manifest.json
custom_components/intesishome/climate.py


Feat server inline guidance

There is currently a bug in the compiled build where the help window isn't opening anymore. The current code is not ready for merge until this is fixed.


Create GitHub Releases via a GitHub Action

Twiglet had to be hardcoded unfortunately as there isn't a neat way to find out the Gem name.
Issue: https://github.com/simplybusiness/twiglet-ruby/issues/51

/dobby version minor


Changes not applied to file

Hi, when I use aider, response is printed to the terminal but not applied to the file like described and shown in the screencasts. I don't have GPT-4 access yes, though, so am running with the -3 flag.
Thanks for doing this, eager to use it :) .

Thanks for trying aider!
You are probably correct that the issue is caused by using gpt-3.5-turbo. It doesn't following instructions well, and often fails to  format code in a way that aider expects.
Is it outputting "edit blocks" that look like the example in the prompts?
https://github.com/paul-gauthier/aider/blob/82cc64eb6f4bd1006bf55b94890a76c5db1576b8/aider/prompts.py#L18-L28
If not, then aider won't be able to parse out the edit and apply to the file.

No, it's just outputting the entire file, with its changes. It would be nice if there was a command like /replace or /overwrite that would simply replace the file with that output. Because the answer is good, even though it's gpt-3.5-turbo.

Yes, it would be nice for aider to support some basic functionality with gpt-3.5-turbo. That model is quite limited in what it can do though. With only 4k context window and the need to read and write the entire code that is being modified... you can only work on small pieces of code with it.
I'll definitely think some more about this and try and find a good approach to adding support for 3.5.
Thanks again for the feedback.

I'm going to close this for now. Feel free to reopen or make a new issue if you have problems or questions about gpt-3.5-turbo support.


add console email backend

I'd rather not have it as a default, it can be pretty annoying when mails are printed for everything and you want to debug sth else


a few time measuring and some goimports fixes

Added some time measurements
Description
Just added some debug information regarding how long it takes to invoke CommitTxBatch and ProcessTransactionMsg (to see how fast the other goroutine processes the queue)
Also fixed some goimports because make linter complained.
Signed-off-by<EMAIL_ADDRESS>

Signed-off-by<EMAIL_ADDRESS>

It's better we can provide a util function to handle this performance measurement logs related. I believe we should have a lot of check points regarding how long it taks, the issue #856 is using to trace this.

But, if we do something generic it'll have to be with interface{} and then we lose the compile time type checking, won't we?

Does it exist a metrics library in golang world which like dropwizzard metrics in java?

I've made this point previously. There are plenty of metrics/benchmarking packages for go that can be used for performance measurement. Some of the tests have started to use Ginkgo which includes benchmarking capabilities, and I think it would be preferable to instrument the tests than littering the code with more debug log output.

If we have this metrics in code, we can collect the metrics from a dedicated monitoring system real time. i saw many large scale system have this feature.

we aren't going to run production with DEBUG level logging enabled. Further, you can track things via events that we're already publishing. Further, it would make more sense to have metrics collection that can be periodically published rather than constantly spewing log messages that need to be correlated to yield value. As noted, Google is our friend. There are an abundance of metrics packages we might employ vs rolling and maintaining our own.

@christo4ferris Sure. I totally agree you, my point is not related this PR, I just wonder if we already have a plan to do some instrument for metrics statistic, request tracing,  maybe it is better to create a issue to track.

@yacovm we will be transferring the fabric and fabric-api repository and all the corresponding issues and pull requests to the hyperledger-archives org on GH and replacing this repository with a read-only mirror of our Gerrit source. As a result, any automatic GH redirects will be broken. If you haven't already migrated your PR to Gerrit, and intend to do so, you will need to change your git remote to reference the transferred repository (e.g. git@github.com:hyperledger-archives/fabric) on your local clone.


[Feature]: Reading multiple files without being zipped

Guidelines

[X] I agree to follow this project's Contributing Guidelines.

Description
It could be nice for some users to not have to zip their files together for upload and instead allow for multiple file section as an option. Currently a little tricky to implement because it isn't integrated well into the read_any function.
Problem
Requiring zipped data which creates an extra step for some.
Proposed Solution
Allow multiple file selection.
Alternatives Considered
status quo

This is working now at a basic level but the file names are being lost when the top matches are downloaded.

Should be fixed now and fully working.


Proposed new externs ExactMap and TernaryMap

This was first discussed in a public PNA meeting on 2022-Jun-13.
The original motivation for the new proposed externs is to have constructs that are in some ways similar to P4 tables, but:
(a) their lookup method can be called from inside the body of a P4 action.  The P4_16 language spec explicitly disallows table_name.apply() calls within P4 action calls today, and always has since version 1.0.
(b) they simply "return a value" rather than execute an arbitrary P4 action.
Attached is a P4_16 source file pna_extern_defns.p4.txt that defines the extern objects.  Something like this would be added to the pna.p4 #include file if this proposal goes forward.
Below is an edited version of a file that I used to explain the new extern's behavior in the first meeting discussing it, plus some notes of discussion we had during that meeting.
The originally proposed name of ExactMap was ExactMatchLookupTable.
Not only does this seem too long, but putting "table" anywhere in its
name makes it more confusing to talk about, since it is not a P4
table (despite the similarities).  ExactMap was proposed as a shorter
name that avoids the "table" word confusion.
Here are some examples of how to instantiate and call the originally
proposed extern object originally proposed, as defined in the file
pna_extern_defns.p4:
    // Example of ExactMap with type bit<W> for key type and return
    // value type.

    // instantiation of an instance named `emap1`, in a control before
    // the apply { ... } block

    ExactMap<bit<8>, bit<16>, _>(
            size = 128,
            default_value = 42)  // default value returned for all other keys
        emap1;

    bit<16> v;

    apply {
        // ... other code here ...
        v = emap1.lookup({hdr.ipv4.protocol);

        // A target _might_ support multiple lookup() operations on
        // the same instance per packet, or it might limit the number
        // of lookup() operations to 1 per packet, 2 per packet, etc.
        // That is a target-specific decision.  The most portable P4
        // code would limit itself to 1 lookup operation per instance,
        // per packet, just as P4 developers do today for P4 table
        // apply() calls.

        //w = emap1.lookup(hdr.ipv4.srcAddr[7:0]);

        // ... more other code here ...
    }

For the purposes of understanding the behavior of the code above, it
should be the same as the code below, which does not use the new
extern.
    // Code that behaves the same as the above, and has a very similar
    // control plane API

    bit<16> v;

    action emap1_set_value (bit<16> val) { v = val; }

    table emap1_table {
        key = { hdr.ipv4.protocol : exact; }
        actions = { emap1_set_value; }
        size = 128;
        default_action = emap1_set_value(42);
    }

    apply {
        // ... other code here ...
        emap1_table.apply();
        // ... more other code here ...
    }

The example below is nearly the same as the first one above, but it
uses a struct type for the key type.  This is a straightforward way in
existing P4_16 to have "multiple fields" in such an extern as the
lookup key.
Independently from the key, the return value type could also be a
struct type.  The example below uses a struct type for the return
value, as well as for the key.
    // Example of ExactMap with struct types for key type and return
    // value type.

    struct MyKeyType1_t {
        bit<8> f1;
        bit<16> f2;
    }
    struct MyValType1_t {
        bit<1> valid;
        bit<16> foo;
    }

    MyValType1_t v;
    ExactMap<MyKeyType1_t, MyValType1_t, _>(
            size = 1024,
            default_value = {valid = 0, foo = 0})  // default value returned for all other keys
        emap2;

    apply {
        // ...
        v = emap2.lookup({hdr.ipv4.protocol, hdr.ipv4.srcAddr[15:0]});
    }

One advantage of using struct types for key types is that it gives a
clear choice for what to use for "key field names" in a table-like
control plane API when adding/deleting entries to this extern --
i.e. use the names of the struct members, of the struct that is type
K.
Note that P4Runtime API 1.x does not support struct types as table
keys today.  It could be extended, of course, but not there now.
Proposal here would be to use field names f1, f2 for emap2 as key
fields in control plane API of emap2.
TODO: Would tuples have any advantages over structs for emap2
example?  One potential disadvantage vs struct is that struct
members have names that control plane API could use for emap2,
but tuple members do not have names.
Vlad: Note that for TernaryMap, the type of a key field int should
have a mask with type bit, probably, not int.
Thomas: This seems fairly target-specific.  Why not go to the P4_16
language spec and make a separate method?
e.g. table_name.lookup(key_expr), as shown in sample code snippet
below?
    // Thomas Calvert: Why not make this look more like an existing P4
    // table, but perhaps with different table properties to
    // distinguish it?

    bit<16> v;

    table emap3 {
        key = { hdr.ipv4.protocol : exact; }
        size = 128;
        value_type = bit<16>;  // Andy: I am making up possible syntax here on the fly
        default_value = 42;
        // actions table property is NOT ALLOWED for this variant of
        // table, because value_type table property is defined.
    }

    apply {
        // ...
        v = emap3.lookup();
        // ...
    }

Alan Lo: Is there a way to make the above look more like other
P4 table definitions?
Perhaps using the 'implementation' table property, as shown in
code snippet below.
    table emap4 {
        key = { hdr.ipv4.protocol : exact; }
        size = 128;
        implementation = ValueReturner;   // making up proposed name `ValueReturner` on the fly during discussion here
        // TODO what the other table properties would be, and what the
        // definition of the ValueReturner extern is.
    }

Andy is summarizing in his (Andy's) own words a week after Vlad said
something like the following near the end of the meeting.  Any
differences between this and what Vlad actually said are Andy's
fault.
pna_extern_defns.p4.txt

Partially remembered and new comments regarding going to the P4 language design work group and extending the definitions of P4 tables to enable similar features.

One of the motivations for making these externs is that extern calls can be made within expressions, including within the bodies of P4 actions, and we would like to enable the new extern lookup() calls to be performed within action bodies, among other places in the code.

Note that the P4 language spec has for all 1.x versions released since 2017 disallowed performing table_name.apply() calls within P4 action bodies.  Or at least, it has said that P4 implementations need not support this, and the open source p4c compiler has always so far given an error message if you attempt to do so.  See Appendix F of the P4_16 language specification, the last table, the row labeled "table", and the column labeled "action", where the cell contains the word "no".  That is intended to mean "tables cannot be called (i.e. apply()'d) from within a P4 action".

Another reason is that the P4 language design work group is, fairly reasonably, a conservative bunch, representing developers of multiple P4 target devices.  Extending tables is possible, but is not a quick process.  I certainly do not mind if some day P4 tables are extended with similar capabilities, but one way to convince a conservative group of folks that something is a good, solid, workable idea is to show that multiple targets can implement it, and any issues in its specification have been worked out.  Defining new externs can be done in any P4 architecture, without changes to the P4 language specification, and is one way towards this.

This seems related to this https://github.com/p4lang/p4c/pull/2739

This issue for the P4 language specification is tracking the possible addition of a list type in the P4 language spec, which would be useful in enabling the p4c front end to perform type-checking on the const_entries or entries argument value of these proposed ExactMap / TernaryMap externs.  We can define these externs without that language feature, too, but then the P4 compiler back-ends would need to do all error-checking on the value of those constructor parameters.
Not a big deal to me either way, but if the list type is added to the language spec and p4c relatively soon (e.g. before end of 2022 calendar year), I will update this PR to use that list type for those parameters to these extern constructor calls.


Add HTML validation

We're not checking the validity of HTML for the demo page. This was noticed in #119.
It would be nice to have something added to check for HTML validity - either something that lints the HTML files, or something that makes the build task fail when HTML isn't valid.
I would be looking for recommendations on how to do this and would be open to any pull request that accomplishes the goal!

Hi , I am willing to work on this issue but I need some guidance

In 2.0 we're linting JavaScript inside HTML but not checking the HTML for validity. I'm gonna keep this open, but it isn't important enough to be part of 2.0.

Can I fix this issue?

Closing since 2.0 has a validation script that handles this now.


Set awake param to true by default

Sets the default value of the awake parameter to true in the following Body methods to better match the documentation.
Described in this issue.

applyForce
applyForceToCenter
applyTorque
applyLinearImpulse
applyAngularImpulse

Thanks for the fix!


Allow headless backend to re-use an existing renderer

This would allow things like having a DRM backend with some headless outputs.

Implemented in 6129a6f93e97680dfe7e983db2ee7671edb5ffbe.


Quantum API - Computed Statement Resolution

Have followed this Quantum - Computed Statement Resolution and got it copying the image to the .dist folder and the Quantum bundle warning does not appear.
Not to sure what the issue is but as @nchanged mentioned in gitter it appears FuseBox is complaining that the API is not loading.

My code (Assets.ts)
export function getImageByName(filename: string) {
    return require("../images/" + filename + ".png");
};

App.tsx
const test = getImageByName("icon-tick.png");
//... then down in render i am just trying to console.log(test);

And then here is my Fuse.ts
I did get a similar setup working with the quantum_computed_resolve fuse-box example. Not to sure what the difference is. Both that and my playground that I am testing on are quite simple apps.
Differences obviously can be drawn from looking at my Fuse.ts gist and the fuse.js file in the FuseBox example project.

The issue was icon-tick.png**.png** doe's not exist... silly mistake. Not sure how to delete issues but am closing it now.

Hmm opening as it seems its not fully fixed. Will update shortly.

@pmonty you need to read this section
https://fuse-box.org/page/quantum-configuration#computed-statement-resolution
You are using computed statements, you need mapping ;-)
QuantumPlugin({
    api: (core) => {
        core.solveComputed("default/yourfile.js", {
            mapping: "images/*.png",
            fn: (statement, core) =>
                statement.setExpression(`"default/fromRoot/images/" + name + ".html"`)
        });
    }
})

Yeh read through it and followed the examples. The issue isn;'t the warning just that the api is not loading saying it is not a function.
Really strange, you can see how I have the mapping set up correctly in my gist in the first post. Not sure what the issue might be. It copies the file into the dist folder an everything.

Tested it as is and it worked (dev and production build).
Moment I make changes

change all extensions/references to .png
add an image to views folder
change line to const first = getHTMLContents("test-img");

Then after those it does work on dev build but the production/dist build that uses quantum breaks with the $fsx.p is not a function error.

Hm, could you reproduce this issue in a repository?

Will check it out tomorrow and let you know how it goes.

Hmm so looks like tree-shaking was the issue and it was removing the following
// default/images/EA/images/icontick.png
$fsx.f[29] = function(module,exports){
module.exports = '/assets/7c8a54f-icontick.png';
}

So added this and it worked. I guess it will still treeshake atleast but avoid assets.ts related stuff.
treeshake: {
    shouldRemove: file => {
        if (file.fuseBoxPath === "Assets.js") {
           return false;
        }
   }
},

So hopefully this will be entirely avoidable when dynamic computed import statements are available. Guess treeshaking was just doing it job and causing the issue.


Is this a sample project or a dev tool?

The first couple of lines of README say
https://github.com/webxdc/hello/blob/a42c553ba14045d69e718e11d123d8f3c4a78a2d/README.md?plain=1#L3

the repo is marked as "template"

But for a sample project this looks a little too convoluted, e.g. the "Limitations" section in README looks unnecessary for a sample project, this sounds more like it applies to the webxdc.js stub dev tool. This makes it look like it's required reading to know how this sample project works, which it isn't.
I think sample project must be as short and easy to swallow as possible. We have this in https://docs.webxdc.org/get_started.html#a-simple-example, but I don't know, it looks like we're saying that this is the repo of that simple example.
If it's a dev tool, we shouldn't be regarding it as a sample project in https://docs.webxdc.org/.
I think we need to clearly separate the stub webxdc.js and the sample index.html into different projects (also see "Stop the copy-paste of create-xdc.sh, webxdc.js").

we should separate the emulator and typescript types definition to a node package developers can install as dev dependency without copying files manually, and the package could offer a vite plugin to transparently inject webxdc.js file without needing the file copied manually

we already have https://www.npmjs.com/package/webxdc-types but it is completely different from webxdc.d.ts in the hello repo

the package could offer a vite plugin

Idk, it doesn't sounds like a good reason to add Vite, it's just a matter of cp node_modules/webxdc-js-stub/webxdc.js ..

I think we need to clearly separate the stub webxdc.js and the sample index.html into different projects

well not sure if splitting into two projects help here, that would result in a subproject for hello, with all its troubles. i am not sure that makes things easier.
i think, "hello" it is great as a pattern esp, for ppl that are not familiar with js or git tooling, just having very few files that one can start with. i do not see it as an issue if things are duplicated afterwards, eg. create-xdc.sh needs to be adapted anyways (sure, you can do that with vite and whatnot - but you would have to learn it as well)
so, not against adding other tooling and projects and examples - but we should really keep things simple in hello (as long as we make things simpler in hello, of course, we can adapt here as well)

forcing some packet manager

We can make a separate project for the stub webxdc.js while keeping webxdc.js in this project as a copy-pasted file, stating where the file is coming from (see #52), like it sort of is with webxdc.d.ts (see #53).

this issue is solved by #61 we in the meanwhile have the @webxdc/types package for types and we don't have to maintain a duplicated webxdc.d.ts file here, and the emulator is now available via @webxdc/vite-plugins package


Optional test selector

Make test selector optional. If no test selector is used, just run every test for every mutation. This feature will help us to integrate the mocha test runner, without having to also implement and support the mocha test selector.

Merged master branch into this branch.
Added an option to pass 'null' (as string), has the same result as passing null (as in nill)

Looks good! Nice work!


template useability docs changes

tweaks for revised template
move breaking changes to bottom, clarify instance name usage, reorg DET options

Amplitude Developer Docs PR
Description
Describe your changes.
Deadline
When do these changes need to be live on the site?
Change type

[ ] Doc bug fix. Fixes #[insert issue number]. Amplitude contributors include Jira issue number.
[ ] Doc update.
[ ] New documentation.
[ ] Non-documentation related fix or update.

PR checklist:

[ ] My documentation follows the style guidelines of this project.
[ ] I previewed my documentation on a local server using mkdocs serve.
[ ] Running mkdocs serve didn't generate any failures.
[ ] I have performed a self-review of my own documentation.

@amplitude-dev-docs

It will be better if we also change the types accordingly to the new name.

I'm hesitant to change those because it would require going back into the template and updating the doc links for all of the tag types. Imo the names in parentheses are sufficient.


Add Commitizen config

chore(package.json): add commitizen config
This adds the conventional changelog config for commitizen.
commitizen

Commit:
07ef6ee904ed849b1cd75f38c0338bd44055af59

I feel this is unnecessary, the project is also unmaintained so I don't like the idea of having a lot of node_modules unmaintained, because in the long term we need to keep the packages up to date.

I recently changed in dcos-ui to use: @commitlint/config-conventional https://github.com/dcos/dcos-ui/blob/master/package.json#L77...it makes sense that this repo and dcos-ui would use the same tooling for linting/changelog. No strong opinions either way, just consistency.

"@commitlint/cli": "6.1.3",
"@commitlint/config-conventional": "6.1.3",

its in here already 👍  the tool added by philipp is only about generating commit messages (and i really like this tool, want to have it in dcos-ui also 👍
@Poltergeist can you please add a short gif/video of how it works? I'm alsmost sure that the guys are instantly sold after seeing it :)

@juliangieseke Thank you for explaining, I understood it differently 🙈

I hope this explains more what it does. I think this is adding value because it will generate commits based on a style definition.


ESPNet training

Hello,Thank you for your impressive work!
I know the training is followed by two steps.When I set the  variable 'decoder' to 'True',there is a problem with '

RuntimeError: input and target batch or spatial sizes don't match: target [8 x 96 x 192], input [8 x 20 x 768 x 1536] at /opt/conda/conda-bld/pytorch_1549628766161/work/aten/src/THCUNN/generic/SpatialClassNLLCriterion.cu:23'
Please help me solve doubts.Thank you very much!

What is the value of argument scaleIn ? For encoder, it is 8 and for decoder, it should be 1.

What is the value of argument scaleIn ? For encoder, it is 8 and for decoder, it should be 1.

Thank you for your reply.This problem has been solved.May I ask another question?The epoch in ESPNet-C and  ESPNet  training are both 300.But it takse too many time. Do you have any suggestion to reduce the time? Hope for your reply. Thanks!

Hello!
I am try to retrain the net.Everything follows your advice,but there has a bug.Can you help me to solve it .Please, this is important for me. Thank you !
RuntimeError: Error(s) in loading state_dict for ESPNet:
        size mismatch for conv.conv.weight: copying a param with shape torch.Size([20, 39, 3, 3]) from checkpoint, the shape in current model is torch.Size([20, 36,3, 3]).

Hello!
I am try to retrain the net.Everything follows your advice,but there has a bug.Can you help me to solve it .Please, this is important for me. Thank you !
RuntimeError: Error(s) in loading state_dict for ESPNet:
        size mismatch for conv.conv.weight: copying a param with shape torch.Size([20, 39, 3, 3]) from checkpoint, the shape in current model is torch.Size([20, 36,3, 3]).

I also suffered such a bug, have you solved this error? If it is solved, can you tell me the solution?
please please please

Model file in train and test folders are different. The one in train folder is generic and can be applied to any dataset. The one in test folder is specific to Cityscapes dataset. Which file are you using?

火车和测试文件夹中的模型文件是不同的。列车文件夹中的一个是通用的，可以应用于任何数据集。测试文件夹中的一个特定于Cityscapes数据集。你使用的是哪个文件？

thank.
my training process is like what you said in readme.
first .i train esp-net-C then i train esp-net
so i get two dir. like:

now i want to test my model that i haved train .
how can i do ?

Replace the model file in test folder with the one in train folder and then follow the instructions for testing. It should work

将test文件夹中的模型文件替换为train in train文件夹中的模型文件，然后按照说明进行测试。它应该工作
your meaning is that i used results_enc__dec_2_8/model_300.pth to be the espnet_p_2_q_8.pth and results_enc__enc_2_8/model_300.pth to be the espnet_p_2_q_8.pth ,and i can test my model?

I mean replace Model.py file in test folder with Model.py file in train folder and then use the weights that you trained.

solve it !!!
thank you very much !!!

I mean replace Model.py file in test folder with Model.py file in train folder and then use the weights that you trained.

I just tested it. I trained 300 rounds of models and I feel it may be not the best.
could you tell me what is the best parameter when you train?
How accurate is it?

We used the default parameters for training. See accuracy details in paper or Cityscapes leaderboard.
P.S.: In case you are not aware of, ESPNetv2 is 6-7% more accurate than ESPNet and has about half the number of FLOPs and trains faster too. See below repo for more details.
https://github.com/sacmehta/EdgeNets


compute_ctl: Break up main()

Problem
compute_ctl's main() is "pretty gnarly". This makes changes to control flow quite difficult.
I hit this while working on #7434 and had an idea of how it could be improved, thus this PR.
Summary of changes
First commit: Small changes to reduce the diff of the second commit.
Second commit: Breaks up main() into a handful of component functions, aligned with distinct sections of the existing control flow. Each new function gets the previous one's return values as its arguments. The new functions destructure their args so the names are all the same.
Third commit: Move the tracing startup context guard out of where it was previously used, to make things more simple. Taken from #7600.
Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.
[ ] Do we need to implement analytics? if so did you add the relevant metrics to the dashboard?
[ ] If this PR requires public announcement, mark it with /release-notes label and add several sentences in this section.

Checklist before merging

[ ] Do not forget to reformat commit message to not include the above checklist

Planning to merge in 24h or so, if no objections (cc @tristan957).


Cannot run task of type "process"

Type: Bug
I can see the warning:
"Warning: process tasks are unavailable in the current environment"
I have no doubt that this is some stupid security policy introduced by my organization that is causing this (and if I run VSCode as an Administrator, I no longer get this warning and process tasks run fine).
However, the reason I'm reporting the issue is that I'm finding that if I run another task e.g. a task of type "docker-build", that's sufficient to get VSCode to launch the "tasks" terminal process. And once this is launched, then the tasks of type "process" will run fine (even when I'm not running as an Administrator).
So I wonder if VSCode executed things in a different order or front-loaded the tasks terminal window in some way, could this avoid the issue for Windows users with similar organization security policies in place?
VS Code version: Code 1.75.1 (441438abd1ac652551dbe4d408dfcec8a499b8bf, 2023-02-08T21:32:34.589Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (8 x 1992)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
31.85GB (2.29GB free)

Process Argv
C:\dev\ccace\Microservices --crash-reporter-id 6b6f5016-4aed-4bb2-96fe-2e0bcbbf0bff

Screen Reader
no

VM
0%

Extensions (20)

Extension
Author (truncated)
Version

clipboard-history
Anj
1.0.7

vscode-csharp-snippets
jor
1.1.0

rainbow-csv
mec
3.5.0

dotenv
mik
1.0.1

azure-pipelines
ms-
1.208.0

vscode-azurefunctions
ms-
1.10.2

vscode-azureresourcegroups
ms-
0.5.6

vscode-docker
ms-
1.23.3

csharp
ms-
1.25.4

isort
ms-
2022.8.0

python
ms-
2023.2.0

vscode-pylance
ms-
2023.2.30

vscode-jupyter-cell-tags
ms-
0.1.6

vscode-jupyter-slideshow
ms-
0.1.5

remote-wsl
ms-
0.75.3

azure-account
ms-
0.11.3

powershell
ms-
2023.1.0

vscode-octopusdeploy
Oct
0.1.4

vscode-nuget-gallery
pat
0.0.24

code-spell-checker
str
2.16.0

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
azure-dev_surveyone:30548225
pyindex848:30662994
nodejswelcome1:30587005
282f8724:30602487
pyind779cf:30662993
f6dab269:30613381
pythonsymbol12:30657548
a9j8j154:30646983
vsccsb:30662443
vscodeenable:30660116

I also get "Warning: process tasks are unavailable in the current environment."
Sometimes my User defined tasks are not listed, other times they are. Usually my workspace tasks are not listed.
Commenting and uncommentating tasks inside the workspaces tasks.json will resolve the issue until the next reload of VSCode and listings of both workspace and user tasks are restored.

Commenting and uncommentating tasks inside the workspaces tasks.json will resolve the issue until the next reload of VSCode and listings of both workspace and user tasks are restored.

Thanks, you're a genius. This got me unstuck this morning.

Good to hear @rstackhouse . Unfortunately my technique is a hacky workaround and does not fix things like tasks that you want to run consistently at workspace activation.

Interestingly, I think, the only time I've seen this (on Ubuntu Linux 22.04, Code 1.77.1) was after reopening a workspace after reboot, in which I had previously had a temp file opened (so, of course, the file no longer existed). This would seem likely to match @cathalmchale 's belief that it's their security policy — some file is not openable either because of permissions or just non-existence.

I've reproduced this on Windows:

Have a valid file open,
Confirm User defined tasks are showing up correctly
Ctrl+Shift+P -> Developer: Reload Window

Expected outcome: User defined tasks appear in list when running Ctrl+Shift+P ->Tasks: Run Task
Actual outcome: User defined tasks are missing and the message Warning: process tasks are unavailable in the current environment. appears in the Tasks Output log.
Hacky workaround:

Ctrl+Shift+P -> Tasks: Open User Tasks
Ctrl+A  to select all, Ctrl+/ to comment out all; then Save.
Ctrl+Z to Undo; then Save. Task list is restored

Bit of a mess this one. VSCode becomming a bit of a hindrance to development at the minute.
Other issues that I've notice that appear to be related:
Always getting this warning in Output (Tasks):
"Warning: process tasks are unavailable in the current environment."
When I attempt to Launch a dotnetclr debugger, which has a preLaunchTask that looks like this:
{
"label": "build",
"command": "dotnet",
"type": "process",
"args": [
"build",
"${workspaceFolder}/services/MySolution.sln",
"/property:GenerateFullPaths=true",
"/consoleloggerparameters:NoSummary"
],
"problemMatcher": "$msCompile"
}
I can see the task terminal spit out the command:
Executing task: dotnet build /property:GenerateFullPaths=true /consoleloggerparameters:NoSummary
So clearly it's struggling with the arg "${workspaceFolder}/services/MySolution.sln" and just skips it. So not resolving ${workspaceFolder}?
So I manually execute the build tasks in a terminal myself (dotnet clean, restore, build etc.), then Launch the debugger and choose "Launch anyway" when it reports an error, and I can see the following in the Debug Console:
Unable to submit event Now listening on: {address}
Unable to submit event Application started. Press Ctrl+C to shut down.
Unable to submit event Hosting environment: {envName}
Unable to submit event Content root path: {contentRoot}

@meganrogge is there documentation or additional logging we can enable to interrogate why the message "Warning: process tasks are unavailable in the current environment." is appearing?

Bit of a mess this one. VSCode becomming a bit of a hindrance to development at the minute. Other issues that I've notice that appear to be related:
Always getting this warning in Output (Tasks): "Warning: process tasks are unavailable in the current environment."
When I attempt to Launch a dotnetclr debugger, which has a preLaunchTask that looks like this:
{ "label": "build", "command": "dotnet", "type": "process", "args": [ "build", "${workspaceFolder}/services/MySolution.sln", "/property:GenerateFullPaths=true", "/consoleloggerparameters:NoSummary" ], "problemMatcher": "$msCompile" }
I can see the task terminal spit out the command:
Executing task: dotnet build /property:GenerateFullPaths=true /consoleloggerparameters:NoSummary
So clearly it's struggling with the arg "${workspaceFolder}/services/MySolution.sln" and just skips it. So not resolving ${workspaceFolder}?
So I manually execute the build tasks in a terminal myself (dotnet clean, restore, build etc.), then Launch the debugger and choose "Launch anyway" when it reports an error, and I can see the following in the Debug Console:
Unable to submit event Now listening on: {address} Unable to submit event Application started. Press Ctrl+C to shut down. Unable to submit event Hosting environment: {envName} Unable to submit event Content root path: {contentRoot}

UPDATE so that it doesn't cause confusion. I was wrong about the tasks.json not picking up the ${workspaceFolder}. I was getting caught out by Task auto-detection here. But the rest of it is valid - the debugger is failing to "launch externally" because of the error reported in the debug console:
Unable to submit event Now listening on: {address}
Unable to submit event Application started. Press Ctrl+C to shut down.
Unable to submit event Hosting environment: {envName}
Unable to submit event Content root path: {contentRoot}
I can't say whether the issues are related, but two startements that are true:

This all used to work just fine.
Running VSCode as an administrator removes the warning: "Warning: process tasks are unavailable in the current environment."

/closedWith 440bade

@meganrogge , I've reproduced part of this issue with version 1.80.1
Continuing to see the warning in the Tasks Output:

"Warning: process tasks are unavailable in the current environment"

and process tasks specified in %APPDATA%\Code\User\tasks.json are not appearing when selecting Tasks: Run Task from the "Show All Command" panel until you perform the workaround specified here https://github.com/microsoft/vscode/issues/174674#issuecomment-1520560613

Not surprising that you've reproduced with that version. Pls try insider's, where this issue should be fixed @Spitfire1900

Thanks @meganrogge. Is there docs on how to check whether a commit is in insiders vs GA vs not yet released?


refactors VanillaSoftwareProcessLifecycleModifier

Looks good on the whole. Tests? Would also like the class to be renamed to indicate that it specifically handles TOSCA's standard interface.

@robertgmoss Thanks.


feat(build): add API to update the iOS entitlements file

What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Docs
[ ] New Binding issue #___
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change?

[ ] Yes, and the changes were approved in issue #___
[ ] No

Checklist

[ ] When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
[x] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
[ ] I have added a convincing reason for adding this feature, if necessary

Other information

Needs #7445 and #7446

Example usage together with #7447
// Copyright 2019-2023 Tauri Programme within The Commons Conservancy
// SPDX-License-Identifier: Apache-2.0
// SPDX-License-Identifier: MIT

#[derive(serde::Deserialize)]
struct Config {
    domains: Vec<String>,
}

fn main() {
    if let Some(config) = tauri_build::config::plugin_config::<Config>("deepLink") {
        #[cfg(target_os = "macos")]
        {
            tauri_build::mobile::update_entitlements(|entitlements| {
                entitlements.insert(
                    "com.apple.developer.associated-domains".into(),
                    config
                        .domains
                        .into_iter()
                        .map(Into::into)
                        .collect::<Vec<_>>()
                        .into(),
                );
            })
            .expect("failed to update entitlements");
        }
    }
}


hedgewars: Disable autoupdate on darwin to fix build

On darwin cmake complains about missing Sparkle. Autoupdates don‘t seem important for a nixpkgs package, so we disable it.
See: https://hydra.nixos.org/build/190503204/nixlog/4 for the error.
\cc @fpletz @kragniz
I can‘t test this on darwin, I will only be able to tell after merging.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

@ofborg build hedgewars

As witnessed by ofBorg this just let’s the build proceed to another failure.

Unfortunately, I also can't test or fix this since I don't have Darwin either. I would propose to disable builds for Darwin for now. We should also disable the autoupdate in nixpkgs. :+1:

If have done this in e678b76.


Migrate Pipelines - Phase 1 - Five Pipelines and Templates

Migrate These Pipelines:

.pipelines/android_packaging.yml
.pipelines/java_packaging.yml
.pipelines/nuget.yml
.pipelines/wheels_linux.yml
.pipelines/OneBranch.Official.yml

The files in templates folder are from folder .pipelines/templates.

Do you still keep the .yml files in .pipelines? Can we still use this folder for pipeline files?

@wenbingl , shall we merge this PR?


Link to the OpenGL::GL target, instead of ${OPENGL_LIBRARIES}

This prevents absolute paths from creeping into the output MaterialXConfig.cmake, which makes it not portable.
Also, in general in modern CMake, targets are preferred over baked paths.  Additionally, at least on Linux,
${OPENGL_LIBRARIES} includes libGLU, which is not actually a required dependency

Fixed an issue with requiring OpenGL on iOS builds.  Refactored the way COMMON_LIBRARIES was used to make the iOS library changes clearer / grouped with other target_link_library statements

This looks like a good proposal, @pmolodo, and the one caveat is that we'll need to raise our minimum required version of CMake, which is currently set to 3.5:
https://github.com/AcademySoftwareFoundation/MaterialX/blob/main/CMakeLists.txt#L8
We've been interested in raising this minimum version for quite a while, and one option would be to align with OpenImageIO and raise the minimum version of CMake to 3.15:
https://github.com/AcademySoftwareFoundation/OpenImageIO/blob/master/CMakeLists.txt#L5
Let's bring this up as a topic in the MaterialX channel of the ASWF Slack, so that we can gather consensus on what minimum version we should align with.

Following up on a discussion on the MaterialX channel of the ASWF Slack, we've raised the minimum CMake version to 3.16:
https://github.com/AcademySoftwareFoundation/MaterialX/pull/1607

Great, thanks!


Typo fix in oauth-proxy/README.md

a small typo in oauth-proxy/README.md line 41
There are many such typos in the directory /incubator.

/assign @sameersbn


Scroll input on iOS

I've found when viewing a page on iOS, any attempt to scroll over a live photo will open the mp4 link.
Is there anything that can be done to fix that?

@joshdaws0n Did you manage to find or develop a fix? I'm experiencing the same issue.


Resetting request cookie during a test does not persist

What Ruby, Rails and RSpec versions are you using?
Ruby version: 2.6.3
Rails version: 6 rc2
RSpec version: 3.8.2

Observed behaviour
https://stackoverflow.com/questions/57648988/ror-rspec-request-cookie-change-not-persisting-when-changed-in-test-case
Expected behaviour
Setting a request cookie uses that cookie value in the next request.
Can you provide an example app?
Not easily

There are some oddities with how cookies are set, its all controlled by rails / rack-test and not us though, I'm guessing from the closed issue you got an answer on SO?


Error on init. failed to open stream: phar error: "phinx.yml" is not a file

I tried installing this as a phar using box. I'm getting this error when I try to init a project.
$ phinx init .
PHP Warning:  file_get_contents(phar:///usr/local/bin/phinx/src/Phinx/Console/Command/../../../../phinx.yml): failed to open stream: phar error: "phinx.yml" is not a file in phar "/usr/local/bin/phinx" in phar:///usr/local/bin/phinx/src/Phinx/Console/Command/Init.php on line 92
created ./phinx.yml

I tried rebuilding the phinx.phar with box, then extracting it. There's no .yml files in the resulting phinx.phar-contents directory.
So, I edited the box.json file and added "phinx.yml" to the "files" section:
     "files": [
         "LICENSE",
         "phinx.yml"
     ],

That seemed to fix it. Must be an oversight? I have Phinx version 0.3.0

I encountered this issue also - as you noted Rob, it attempts to look for the yml within the phar as opposed to creating it locally/outside of the phar.


Added recipe for plain function

This fixes issue #481. Adds documentation recipe for functions vs. beforeEach.

I wouldn't focus on "stylistic" side of manually doing setup/teardown. I'd suggest focusing on actual benefits it gives to developers, which you actually mentioned at the end:

Setup functions allow for easier modifications between test runs.

If the recipe focuses on a code style, it's not really a recipe, it's just an opinion/preference. Recipes are meant to be official, ready-to-go solutions for questions/problems, that often occur while using AVA.
Everything else looks good, thanks @jarrettmeyer, looking forward to checking out and merging your updated recipe!

@vdemedes Your recommendation is a change to the supporting text? Are the examples good/bad/necessary?

Yes, the supporting text. I think the code examples are fine. But I'd focus reader's attention to the point, that using manual setup/teardown functions gives you more flexibility.
The point of style, looking better and having straightforward tests is secondary, but also worth mentioning.

And @jamestalmage pointed out another advantage:

The real advantage of the setup function approach is that you could have more than one, and call them based on what you need in a particular test.

I would also at the end mention some of the benefits of using beforeEach. From #481:

Still, there are benefits of beforeEach too. They're not mutually exclusive. beforeEach has benefits like supporting non-promise asynchronicity. Better output when a hook fails. Void hook usage doesn't require a call in each test. And more.

There might be more I haven't thought of.

@jarrettmeyer ping :)

@jarrettmeyer Do you have time to follow up on the feedback? Would like to merge this soon.

Closing for lack of response by OP.


Allow block overrides for eth_call and eth_estimateGas

Support for block overrides as in geth (also see state overrides in #5788)
As a network participant, I would like access to be able to drop in and replace Besu in certain networks/tooling/RPC stacks.
Acceptance Criteria
Whilst it's not specified in the ethereum rpc spec the implementation should be based on the Geth rpc docs to allow a drop in replacement.
https://geth.ethereum.org/docs/interacting-with-geth/rpc/ns-eth#eth-call
Block overrides https://geth.ethereum.org/docs/interacting-with-geth/rpc/objects#block-overrides

This should be considered alongside #6203 cc @Gabriel-Trintinalia


added PDFControllerV2 and associated services

Create a new PDFType file that more clearly defines different possible pdf types
Added new error messages to PdfMessage
Set up new PdfController and service files
Added two Handlers (pdfUpload, pdfDelete) and corresponding helper functions
Added two new services (DeletePDFServiceV2, UploadPDFServiceV2)

DeletePDFService deleting actions may be edited based on how other services are implemented
UploadPDFServiceV2 requires EncryptionController, which in turn requires MongoDatabase

Note: The original ImageToPDFService is reused as it doesn't involve database changes

7/31/23 Update
PDFControllerV2

Finished PDFControllerV2 Handlers
Finished UserParams and FileParams inner classes that are passed into services

Services

All services have completed condition-checking functions
All services require tests

DeletePDFServiceV2

Finished

DownloadPDFServiceV2

Working on download function

Need to look into how to inject answers into PDF

FillPDFServiceV2

Working on fill function

Need to look into form object and figure out how to fill answers
Need to figure out how to get and output filled pdf

GetFileInformationPDFServiceV2

Working on getFileInformation function

Need to look into file/form merging process

GetQuestionsPDFServiceV2

Nearly finished, need to handle 4 formField parameters (fieldName, fieldLinkageType, fieldLinkedTo, fieldStatus)

ImageToPDFService

Reused from V1

UploadAnnotatedPDFServiceV2

Working on upload function

Need to figure out how to pull questions from PDF

UploadPDFServiceV2

Finished

UploadSignedPDFServiceV2

Working on upload function


x/crypto/ssh: handshake failed: ssh: no common algorithms with MACs hmac-sha2-256,hmac-sha2-512

go version go1.4.2 darwin/amd64
With OpenSSH server configured to accept:
MACs hmac-sha2-256,hmac-sha2-512,hmac-ripemd160

Go ssh client fails with:
ssh: handshake failed: ssh: no common algorithms

The server side logs that client simply does not support anything but hmac-sha1 and hmac-sha1-96:
fatal: no matching mac found: client hmac-sha1,hmac-sha1-96
server hmac-sha2-256,hmac-sha2-512,hmac-ripemd160

Which is indeed true: https://github.com/golang/crypto/blob/c57d4a71915a248dbad846d60825145062b4c18e/ssh/mac.go#L46
var macModes = map[string]*macMode{
	"hmac-sha1": {20, func(key []byte) hash.Hash {
		return hmac.New(sha1.New, key)
	}},
	"hmac-sha1-96": {20, func(key []byte) hash.Hash {
		return truncatingMAC{12, hmac.New(sha1.New, key)}
	}},
}

It would be great if the SSH client supported hmac-sha2 family of MACs.

CC @agl

I spent a few minutes looking through the code and don't see any obvious reason this wouldn't work:
var macModes = map[string]*macMode{
	"hmac-sha2-512": {64, func(key []byte) hash.Hash {
		return hmac.New(sha512.New, key)
	}},
	"hmac-sha2-256": {32, func(key []byte) hash.Hash {
		return hmac.New(sha256.New, key)
	}},
	"hmac-ripemd160": {20, func(key []byte) hash.Hash {
		return hmac.New(ripemd160.New, key)
	}},
	"hmac-sha1": {20, func(key []byte) hash.Hash {
		return hmac.New(sha1.New, key)
	}},
	"hmac-sha1-96": {20, func(key []byte) hash.Hash {
		return truncatingMAC{12, hmac.New(sha1.New, key)}
	}}
}

@dluchinienoc @ianlancetaylor  I met this issue too, hope this can be fixed in the repo
Besides @dluchinienoc change. Also need to change on the https://github.com/golang/crypto/blob/master/ssh/common.go#L55
To add corresponding algorithm string, tested and worked
Surprised golang does not do pull request :(
Cheers

We don't do pull requests but we accept contributions through the process described at http://golang.org/doc/contribute.html .

@agl  Can you review?
https://go-review.googlesource.com/#/c/8353/   ^^

While it won't affect our use case specifically, MACs in common.go are specified in order or preference, so it might be best to prefer the new (stronger) MACs by ordering them before the SHA1 MACs:
"hmac-sha2-512", "hmac-sha2-256", "hmac-sha1", "hmac-sha1-96"

I had the same problem with openSSH. To solve it currently, I needed to add hmac-sha1 to MACs in /etc/ssh/sshd_config and restart sshd.

$ go version
go version go1.5rc1 darwin/amd64

panic: Failed to dial: ssh: handshake failed: ssh: no common algorithms

OpenSSH work perfectry:
debug1: kex: server->client aes128-cbc hmac-sha1 none
debug1: kex: client->server aes128-cbc hmac-sha1 none

SSH Client CISCO:
package main

import (
	"flag"
	"fmt"

	//"github.com/ScriptRock/crypto/ssh"
	"golang.org/x/crypto/ssh"
)

var (
	USER = flag.String("user", os.Getenv("USER"), "ssh username")
	HOST = flag.String("host", "cisco86.drekstop.dev", "ssh server hostname")
	PORT = flag.Int("port", 22, "ssh server port")
	PASS = flag.String("pass", os.Getenv("SSH_PWD"), "ssh password")
)

func init() { flag.Parse() }

func main() {
	//ssh.Config
	Ciphers: []string{"aes128-cbc", "hmac-sha1", "none"},

	sshConfig := &ssh.ClientConfig{
		User: *USER,
		Auth: []ssh.AuthMethod{ssh.Password(*PASS)},
		//	HostKeyAlgorithms: []string{ssh.KeyAlgoRSA, ssh.KeyAlgoDSA},
	}

	addr := fmt.Sprintf("%s:%d", *HOST, *PORT)
	client, err := ssh.Dial("tcp", addr, sshConfig)
	if err != nil {
		panic("Failed to dial: " + err.Error())
	}

	session, err := client.NewSession()
	if err != nil {
		client.Close()
		panic("Failed to create session: " + err.Error())
	}

	out, err := session.CombinedOutput("show ssh")
	if err != nil {
		panic("Failed to run: " + err.Error())
	}
	fmt.Println(string(out))

	// Close connection
	client.Close()
}

@denji this issue is closed. Please raise a new issue.


Modified docs and variable names

Signed-off-by: Randy Smith<EMAIL_ADDRESS>For an explanation of how to fill out the fields, please see the relevant section
in PULL_REQUESTS.md
Description: Change name and add documentation for integration coroutines.
Risk Level: Low; just name and comment change.
Testing: //test/integration:integration_test
Docs Changes: No user visible doc change.
Fixes #5686

I think this addition was @htuch so he may be able to vouch for renaming better than I

Please merge master to pick up https://github.com/envoyproxy/envoy/pull/5827.

Hey Randy - I was going to merge this for you this morning but looks like the format build blocks - take a look when you have a few!


Try Rector behavior on error

Bug Report
https://getrector.com/demo
If I provide a wrong PHP code to the editor (by mistake while I copy or change it), it returns "Provide a valid PHP code" error message and reset the whole form to default. I have to start the whole process again.
Expected Behaviour
Provide error message and keep the changes in textareas.

As stated in other repo, feel free to provide a PR with suggested improvement :+1:
The code is fully open-source and any giving back is welcomed.


Use baseline value to get position in next line

Description
This PR simplifies the way the vertical offset of the previous/next line is obtained when traversing text using up/down arrow keys.
As vertical runs start at baseline of the current line, use baseline already provided in the text metrics from the TextPainter instead of translating the offset using ascents/descents. It's much shorter and also allows to support more complex metrics (e.g. a customised TextPainter might add some space between paragraphs which wouldn't be included in ascent/descent values).
Testing
The relevant tests are passing:
% ../../bin/flutter test test/rendering/editable_test.dart
00:04 +39: All tests passed!
% ../../bin/flutter test test/rendering/editable_gesture_test.dart
00:03 +1: All tests passed!
% ../../bin/flutter test test/widgets/editable_text_test.dart
00:19 +209: All tests passed!
% ../../bin/flutter test test/widgets/editable_text_show_on_screen_test.dart
00:06 +17: All tests passed!
% ../../bin/flutter test test/widgets/editable_text_shortcuts_tests.dart
00:26 +366: All tests passed!
% ../../bin/flutter test test/widgets/editable_text_cursor_test.dart
00:09 +25: All tests passed!
% ../../bin/flutter test test/widgets/text_selection_test.dart
00:05 +27: All tests passed!
% ../../bin/flutter test test/widgets/selectable_text_test.dart
00:18 +155 ~2: All tests passed!
% ../../bin/flutter test test/material/text_form_field_test.dart
00:07 +28: All tests passed!
% ../../bin/flutter test test/material/text_field_test.dart
00:37 +329: All tests passed!
% ../../bin/flutter test test/cupertino/text_field_test.dart
00:18 +122: All tests passed!

Pre-launch Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I signed the [CLA].
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is [test-exempt].
[x] All existing and new tests are passing.

cc @LongCatIsLooong @justinmc

Yup, should be catchable when passing e..g textHeight=1.1.
Let me add a test with varying font sizes per line also and I'll update the PR.

LGTM. Thanks for the pull request! Out of curiosity does the new test fail without the editable.dart changes?

Yes, with the values I picked (fontSize: 13.0, height: 1.17), it failed on the 15th iteration (skipped one line on arrow down).


Help: endpoint is deprecated

Hello everyone,
I gently request some help to make possible this ngshare service work with jupyterhub >= 2.0. It has been working fine while I used jupyterhub 1.3, but after upgrading jupyterhub to 2.x I get this error:
/authorizations/cookie endpoint is deprecated in JupyterHub 2.0. Use /api/user with OAuth tokens
This error appears in the kubectl logs of the jupyterhub pod when I try to access
https://mydomain.com/services/ngshare/
(the browser says “too many redirects”).
Please, any help would be very very appreciated.
Thank you.

Hi everyone, we created this project at UC Davis with a group of CS students for their capstone design project. I then stewarded this with a funded project at UC Davis after that, but now all the students and myself have left the university. I don't think anyone at LibreTexts or UCD is using this anymore, so there are no resources to develop it.
If anyone wants to take over maintenance, I'm happy to give commit rights to the repo and access to pypi and such so you can do so. @rubdos are you interested this?

If anyone wants to take over maintenance, I'm happy to give commit rights to the repo and access to pypi and such so you can do so. @rubdos are you interested this?

Yeh, sure, I am! Especially if nobody else would be that has more frequent commits than I do.
If you want to contact me in private, I suggest we take my University email at rubedesm at vub dot be

@joernahlers I'm trying to free some time next week to test your pull request on a test cluster and give some feedback if necessary. You're not being forgotten :-)

The new release now takes care of the issue. Thanks to @joernahlers !


Adding PLOS info, changing schema

Looks like the build failure is from:
ruamel.yaml.scanner.ScannerError: mapping values are not allowed here

Will look into what this is tomorrow.

I've revised the schema, including moving "co-review-field" under a new heading called "peer review form" and see that this causes a conflict -  presumably it would be easier to just keep it where it is?

I've revised the schema, including moving "co-review-field" under a new heading called "peer review form" and see that this causes a conflict - presumably it would be easier to just keep it where it is?

If we are going to update the schema, not is the best time. It could get harder once we have files that are curator populated.

Okay I think took the schema changes from here and applied some additional ones to the URL patterns in https://github.com/transpose-publishing/policies-database/pull/13. Once we merge that, we can create a PR with only the PLOS policy updates.

Looks like the URL pattern could have a bug. I will investigate.

Great, thank you - in addition, are the bool values not evaluating properly? ie

"Value 'yes' is not of type 'bool'.

Are these the valid ones? http://yaml.org/refcard.html  Also I notice that we use "no" without quotes as a possible str value in some of the early fields - should we change that? If any of the above are true, we should probably change the descriptions to prompt users with the proper capitalization etc (and harmonize capitalization of expected responses throughout)

It looks like in YAML v1.2 the only support boolean values are true and false (spec). This is a good change IMO since it can be confusing when things meant to be strings get converted to bools. I believe we are using a 1.2 parser, but I can double check. So our options are:

Keep bool fields and rewrite descriptions to use true/false
Switch bools back to an enum string with yes or no.

@jpolka do you have a preference?

Hmm - I feel like yes/no is a little more natural? Unless there are advantages to booleans maybe we could stick with that?

Sounds good. I've taken the PLOS related commits from this PR and moved them to a new PR in https://github.com/transpose-publishing/policies-database/pull/14


Glassmorphism Card Added

What is the change?
A simple Glassmorphism card created with HTML and CSS.
Related issue?
closes: #271
How was it tested?
In vscode
Checklist:
Before you create this PR, confirm all the requirements listed below by checking the checkboxes [x]:

[x] Have you followed the Contribution Guidelineswhile contributing.
[x] Have you checked there aren't other open Pull Requests for the same update/change?
[x] Have you tested the code before submission?
[x] Have you formatted your code? (You can use any HTML, CSS beautifier)
[x] My changes generates no new warnings.
[x] I'm HSOC22 contributor.

GIF/video of the working component you created:
Add here the GIF you created.

Add demo video or gif in readme

Done

You said you have made the card in middle but the demo shows it on top !

updated video


Allow building for the web

I don't think this is necessary? There's no reason that a crate which takes a dependency must re-export or otherwise control the dependency's features.
If you want to set pki-types/web in your application, just write in your Cargo.toml: pki-types { version = "*", features = ["web"] } -- job done, no need for any other crates to change.
(The version = "*" is only appropriate if you do not use any of the APIs from pki-types yourself.)

I don't think this is necessary? There's no reason that a crate which takes a dependency must re-export or otherwise control the dependency's features.
If you want to set pki-types/web in your application, just write in your Cargo.toml: pki-types = { version = "*", features = ["web"] } -- job done, no need for any other crates to change.
(The version = "*" is only appropriate if you do not use any of the APIs from pki-types yourself.)

This is what I have been doing before but it doesn't feel right having to dig into the dependency tree to fix all compile errors by adding features with no standardized name

I made a similar PR on rustls#1921 btw

I don't think this is necessary? There's no reason that a crate which takes a dependency must re-export or otherwise control the dependency's features.

I agree it's not strictly necessary, but it usually makes things easier for the consumer at little cost to the maintainer?

I agree it's not strictly necessary, but it usually makes things easier for the consumer at little cost to the maintainer?

I think a basic level of testing is that all combinations of a crate's features are tested.  If we have features which do not vary the code or dependencies, that adds new dimensions to that testing for no benefit and eventually makes that style of testing implausible.
I think a crate should only have features that either change its dependencies or behaviour; but not just pass through to some other crate's features. I especially think that webpki-roots is an odd choice to do that.

I think a crate should only have features that either change its dependencies or behaviour; but not just pass through to some other crate's features. I especially think that webpki-roots is an odd choice to do that.

That is fair. And if we add a flag for this in rustls, we probably wouldn't strictly need it here?

Agreed, let's close this for now.


add ai qa bot

What's the purpose of this PR
Integrate an intelligent QA bot capable of providing natural language responses to users' inquiries.
The source code for the backend Apollo QA bot can be accessed at here and is currently deployed in conjunction with the Apollo demo server, which is why the ip is <IP_ADDRESS>.
Screenshots

Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Read the Contributing Guide before making this pull request.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit tests to verify the code.
[x] Run mvn clean test to make sure this pull request doesn't break anything.
[ ] Update the CHANGES log.

work well.

Maybe we can change the logo

in the feature to attract user to click it more frequently.

Add some text to it
Zoom out it to get larger logo

I added the Chat with AI text below the icon.


Support new event named "message" on Room

So we can use
room.on('message', message => console.log(message))

#1897


[Snyk] Security upgrade golang from 1.17.8-alpine to 1.21.6-alpine

This PR was automatically created by Snyk using the credentials of a real user.Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Changes included in this PR

internal/services/formatters/go/deployments/Dockerfile

We recommend upgrading to golang:1.21.6-alpine, as this image has only 0 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Some of the most important vulnerabilities in your base image include:

Severity
Priority Score / 1000
Issue
Exploit Maturity

614
Use After Free SNYK-ALPINE315-OPENSSL-3314621
No Known Exploit

614
Use After Free SNYK-ALPINE315-OPENSSL-3314621
No Known Exploit

614
Access of Resource Using Incompatible Type ('Type Confusion') SNYK-ALPINE315-OPENSSL-3314622
No Known Exploit

614
Access of Resource Using Incompatible Type ('Type Confusion') SNYK-ALPINE315-OPENSSL-3314622
No Known Exploit

714
Out-of-bounds Write SNYK-ALPINE315-ZLIB-2976173
No Known Exploit

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Use After Free
🦉 Access of Resource Using Incompatible Type ('Type Confusion')

Checkmarx One – Scan Summary & Details – 1ab9946e-543d-455d-82f7-9513f036a9f5
New Issues

Severity
Issue
Source File / Package
Checkmarx Insight

CVE-2018-0765
Nuget-System.Security.Cryptography.Xml-4.4.1
Vulnerable Package

CVE-2018-8292
Nuget-System.Net.Http-4.3.0
Vulnerable Package

CVE-2019-0820
Nuget-System.Text.RegularExpressions-4.3.0
Vulnerable Package

CVE-2021-26701
Nuget-System.Text.Encodings.Web-4.5.0
Vulnerable Package

CVE-2023-39325
Go-golang.org/x/net-v0.0.0-20220114011407-0dd24b26b47d
Vulnerable Package

CVE-2023-39325
Go-golang.org/x/net-v0.0.0-20210226172049-e18ecbb05110
Vulnerable Package

CVE-2023-44487
Go-k8s.io/apiserver-v0.20.6
Vulnerable Package

CVE-2023-44487
Go-k8s.io/apimachinery-v0.20.6
Vulnerable Package

CVE-2023-44487
Go-google.golang.org/grpc-v1.44.0
Vulnerable Package

CVE-2023-44487
Go-google.golang.org/grpc-v1.36.0
Vulnerable Package

CVE-2024-21626
Go-github.com/opencontainers/runc-v1.0.2
Vulnerable Package

CVE-2024-21647
Ruby-puma-3.12.1
Vulnerable Package

CVE-2024-21907
Nuget-Newtonsoft.Json-10.0.1
Vulnerable Package

Cx477c10a4-5717
Go-go.etcd.io/etcd-v0.5.0-alpha.5.0.20200910180754-dd1b699fc489
Vulnerable Package

Cxb6dee8d5-b814
Go-gopkg.in/square/go-jose.v2-v2.5.1
Vulnerable Package

CVE-2022-34716
Nuget-System.Security.Cryptography.Xml-4.4.1
Vulnerable Package

CVE-2023-3978
Go-golang.org/x/net-v0.0.0-20220114011407-0dd24b26b47d
Vulnerable Package

CVE-2023-3978
Go-golang.org/x/net-v0.0.0-20210226172049-e18ecbb05110
Vulnerable Package

CVE-2023-44390
Nuget-HtmlSanitizer-4.0.217
Vulnerable Package

CVE-2023-48795
Go-golang.org/x/crypto-v0.0.0-20220214200702-86341886e292
Vulnerable Package

CVE-2023-48795
Go-golang.org/x/crypto-v0.0.0-20190308221718-c2843e01d9a2
Vulnerable Package

CVE-2024-22195
Python-Jinja2-2.7.2
Vulnerable Package

Cx47e4310e-3167
Go-go.etcd.io/etcd-v0.5.0-alpha.5.0.20200910180754-dd1b699fc489
Vulnerable Package

Cx68162182-3f7b
Go-github.com/containerd/containerd-v1.5.10
Vulnerable Package

Cx68162182-3f7b
Go-github.com/containerd/containerd-v1.4.1
Vulnerable Package

Reflected_Absolute_Path_Traversal
/internal/utils/file/file.go: 221
Attack Vector

Missing_Content_Security_Policy
/internal/services/horusec_api/horus_api_test.go: 76
Attack Vector

Fixed Issues

Severity
Issue
Source File / Package

Cx46691637-14e8
Nuget-Newtonsoft.Json-10.0.1

Missing_Content_Security_Policy
/internal/services/horusec_api/horus_api_test.go: 54


Different results on version changes

Firstly, thank you for the library, amazing one.
Coming to issue, today I pulled latest commits and my tests revealed some changes in results, after this commit.
Before above commit with model: Dlib, distance_metric: cosine, enforce_detection=False and detector=opencv I had follownig results:
 {'verified': False, 'distance': 0.07104641720871241, 'max_threshold_to_verify': 0.07, 'model': 'Dlib', 'similarity_metric': 'cosine'}
After:
 {'verified': True, 'distance': 0.05064566577204832, 'max_threshold_to_verify': 0.07, 'model': 'Dlib', 'similarity_metric': 'cosine'}
As for the expected results: the first result one was correct.

default detector is mtccn now, this might cause the results. could you set detector_backend = 'opencv'

In both cases above, I had opencv as detector,  and now i tried different detecots including mtccn.
{'verified': True, 'distance': 0.042281921647302045, 'threshold': 0.07, 'metric': 'cosine', 'model': 'dlib'}

Well, I opened this issue, because I thought this may somehow help you. Otherwise, I can close it.

As I mentioned, it seems detector backend effect. Nothing to worry :) thank you. I'm closing the issue.


Only Listen to a specific channel

Hi,
I wonder if there is any way to listen to messages on a specific channel? Listening to messages event means checking every message that comes into the system and then checking the channel and then performing an action. Isn't there a simpler way in RTM where the bot opens a channel and listens for messages. When the task is complete, it closes the channel.
My real-world usecase is :
My bot will open a DM channel with a specific user and ask a question. When the user responds, it will followup with a second question. When the user answers that, the bot will thank the user and end the conversation.

listen to all messages, and your first line can check which channel that message is coming from. This would essentially be the same code that would be implemented in here.
if message.channel.name == 'my_channel'
   # do stuff

@ghostsquad - thanks for answering this!


support for custom method call

Hey,
could you please open an issue with the problem you try to solve?
This PR fails every test, touches the composer.json which shouldn't be needed and I don't really get what or why you want to achieve. 🤔
If the goal is to log method returns too I don't think that we need this. You can add an accessor for everything you want and you can also log all accessible attributes. Why do you want to log methods?
And the method_exists() checks will let the log silently fail. As the user is the only one configuring what's logged it shouldn't fail silently as the user should know if he's doing something wrong.


move ta-generator to task-generator directory

ta-generator and task-generator are currently on the same directory level.
Move ta-generator so it's a subdirectory of the task-generator leading to a better file organization in the repository.

update .gitignore so it ignores vendor directories and diff
files used in trusted-artifacts task generation testing
reflect the move of the trusted-artifacts
task generator to the task-generator directory
in the README
add a README into every task-generator subdirectory

Thank you for the review!
I would like to avoid using Go workspace if possible. The Go Modules reference mentions It is generally inadvisable to commit go.work files into version control systems and I'm not familiar with Go workspaces enough to understand if our use case warrants it.


Blender closes when trying to render through CUDA

In some projects, BlendLuxCore does not want to render through a video card. I try to render through OpenCL or through CUDA. During the compiling of the kernel, the render just closes. When i trying to render through CPU, everything is ok.
My pc spec:
i7 6700
GTX 1070 (Nvidia Studio Driver 442.92)
SSD 512
32 DDR4
Win10
.blend file:
https://1drv.ms/u/s!AiiAe1SZzhrEk28bmuD3DYUmN7jG?e=3pSnVJ
Steps to reproduce:
Try to render with OpenCL or CUDA
Error message from Blender console:
Not possible to see. The blender just closes during kernel compilation.
OS: Win 10
Blender version: 2.82.7
LuxCore version: 2.4a latest build from 15 may

I'm testing your scene but it lacks the HDR file and I get an endless number of errors out Blender, including:

Traceback (most recent call last):
File "/home/david/.config/blender/2.82/scripts/addons/BlendLuxCore/engine/base.py", line 83, in render_final
final.render(self, depsgraph)
File "/home/david/.config/blender/2.82/scripts/addons/BlendLuxCore/engine/final.py", line 49, in render
_render_layer(engine, depsgraph, statistics, layer)
File "/home/david/.config/blender/2.82/scripts/addons/BlendLuxCore/engine/final.py", line 61, in _render_layer
engine.session = engine.exporter.create_session(depsgraph, engine=engine, view_layer=view_layer)
File "/home/david/.config/blender/2.82/scripts/addons/BlendLuxCore/export/init.py", line 143, in create_session
luxcore_scene.Parse(scene_props)
RuntimeError: Syntax error in texture name: Zamioculcas.001
ERROR: Syntax error in texture name: Zamioculcas.001
Error: Syntax error in texture name: Zamioculcas.001

@Theverat does it work for you ?

Checking it now, this seems to hint to some bug in the addon.

I fixed a regression in the addon, now the scene renders fine here on OpenCL. Can't test CUDA right now.

Here it is another file with crashing when I try to render by cuda or opencl.
https://1drv.ms/u/s!AiiAe1SZzhrEk3CPqCgaAE1TTeOB?e=UAv6wA

I fixed a regression in the addon, now the scene renders fine here on OpenCL. Can't test CUDA right now. Since the HDRI is missing, the background will be pink, not sure if that matters for the original issue.

It can be any 2k resolution.

@Theverat, I get a ton of errors out of that scene too:

WARNING: Material "Terrazzo_Stones_2x2_ud4mfako": Writing to ID classes in this context is not allowed: ud4mfako_2K_AO.jpg, Image datablock, error setting Image.filepath_raw
Traceback (most recent call last):
File "/home/david/.config/blender/2.82/scripts/addons/BlendLuxCore/export/material.py", line 25, in convert
return cycles_node_reader.convert(material, props, luxcore_name, obj_name)
File "/home/david/.config/blender/2.82/scripts/addons/BlendLuxCore/export/cycles_node_reader.py", line 28, in convert
result = _node(link.from_node, link.from_socket, props, material, luxcore_name, obj_name)
File "/home/david/.config/blender/2.82/scripts/addons/BlendLuxCore/export/cycles_node_reader.py", line 69, in _node
base_color = _socket(node.inputs["Base Color"], props, material, obj_name, group_node)
File "/home/david/.config/blender/2.82/scripts/addons/BlendLuxCore/export/cycles_node_reader.py", line 48, in _socket
return _node(link.from_node, link.from_socket, props, material, None, obj_name, group_node)
File "/home/david/.config/blender/2.82/scripts/addons/BlendLuxCore/export/cycles_node_reader.py", line 624, in _node
"texture": _socket(node.inputs["Color"], props, material, obj_name, group_node),
File "/home/david/.config/blender/2.82/scripts/addons/BlendLuxCore/export/cycles_node_reader.py", line 48, in _socket
return _node(link.from_node, link.from_socket, props, material, None, obj_name, group_node)
File "/home/david/.config/blender/2.82/scripts/addons/BlendLuxCore/export/cycles_node_reader.py", line 343, in _node
tex2 = _socket(node.inputs["Color2"], props, material, obj_name, group_node)
File "/home/david/.config/blender/2.82/scripts/addons/BlendLuxCore/export/cycles_node_reader.py", line 48, in _socket
return _node(link.from_node, link.from_socket, props, material, None, obj_name, group_node)
File "/home/david/.config/blender/2.82/scripts/addons/BlendLuxCore/export/cycles_node_reader.py", line 237, in _node
filepath = ImageExporter.export_cycles_node_reader(node.image)
File "/home/david/.config/blender/2.82/scripts/addons/BlendLuxCore/export/image.py", line 94, in export_cycles_node_reader
return cls._save_to_temp_file(image)
File "/home/david/.config/blender/2.82/scripts/addons/BlendLuxCore/export/image.py", line 45, in _save_to_temp_file
image.filepath_raw = orig_filepath
AttributeError: Writing to ID classes in this context is not allowed: ud4mfako_2K_AO.jpg, Image datablock, error setting Image.filepath_raw

Anyway, once exported I get an out of memory error and I assume @maxpiratemax  is what you get too:
CUDA driver API error CUDA_ERROR_OUT_OF_MEMORY (code: 2, file:/home/david/projects/luxcorerender/LuxCore/src/luxrays/devices/cudadevice.cpp, line: 451): out of memory
This isn't really surprising because it is a 45,000,000 triangles scene but I'm checking anyway how the memory is used. I have the feeling it may related to the use of particles.

The exported scene.scn alone is 250MB Oo

The scene has some insane subdivision applied, I'm not sure if it is intended:
[SDL][24.992] Subdividing shape Mesh_dom140593333551624000 at level: 5
[SDL][30.083] Subdivided shape from 13174 to 13490176 faces
[SDL][30.083] Subdividing time: 5.091secs
[SDL][30.083] Shape count: 1
[SDL][30.083] Displacement shape Mesh_dom140593333551624000_140591201969160 with texture<PHONE_NUMBER>68136Color
[SDL][31.229] Displacement time: 1.146secs
[SDL][31.229] Subdividing shape Mesh_dom140593333551624002 at level: 5
[SDL][56.770] Subdivided shape from 68212 to 69849088 faces
[SDL][56.770] Subdividing time: 25.541secs
[SDL][56.770] Shape count: 3
[SDL][56.770] Displacement shape Mesh_dom140593333551624002_140590863160328 with texture<PHONE_NUMBER>62376Color
[SDL][62.687] Displacement time: 5.917secs
[SDL][62.687] Shape count: 4
[SDL][62.687] Displacement shape Mesh_Cylinder__003140593333550088000 with texture<PHONE_NUMBER>78248Color
[SDL][62.688] Displacement time: 0.001secs
[SDL][62.688] Displacement shape Mesh_Cylinder__001140593333548552000 with texture<PHONE_NUMBER>78248Color
[SDL][62.689] Displacement time: 0.001secs
[SDL][62.689] Shape count: 6

"Subdivided shape from 68212 to 69849088 faces" 70,000,000 of faces !

This isn't really surprising because it is a 45,000,000 triangles scene but I'm checking anyway how the memory is used. I have the feeling it may related to the use of particles.

I must correct myself the scene has  450,000,000 of triangles !

So the bug is that it crashes instead of reporting "out of memory" and aborting the render?

It throw the exception "Out of memory" as usual with LuxCoreUI. I'm not even sure if I have enough CPU memory to try a rendering inside Blender ... I tried and Blender crashes inside Embree code while trying to build the BVH for the GPU.
I'm not sincerely that surprised given the over the sky numbers. The scene has 2 meshes that once exported create 2GB .ply file each.
If I try to import back the .ply in Blender to see what they are, Blender just crashes (no LuxCore/BlendLuxCore involved).
The scene works fine on GPU if I enable out of core rendering and use TILEPATHOCL:

but it uses more than 8GB of GPU ram so it clearly can not run with OpenCL and a 8GB card.
If you look at the scene:

I have the feeling the 450,000,000 triangles are more the result of some Cycles to LuxCore automatic conversion gone very wrong (subdivision levels ?).

But Blender says that I have only 479000 triangles. Almost all meshes are instances. Therefore, there are a few triangles. Doesn't Lux support instances and hair? Why are 400,000 turning into 450 million?

So the bug is that it crashes instead of reporting "out of memory" and aborting the render?

At least yes

Subdivision, like I wrote in my previous post you (or some automatic conversion code) are using some huge level of subdivision (probably for than applying displacement).

I checked the scene and did not find subdivision

84m without grass. How then to understand which scene a suite can render on a video card and which one cannot?

But Blender says that I have only 479000 triangles.

The following materials have subdivision nodes in them:

Gray_Brick_Wall_2x2_ucelcacfw
Red_Brick_Wall_2x2_udznaenfw

These will only be evaluated on render startup, so Blender can not show the number of triangles they generate.
These nodes were added manually, the Cycles converter does not do subdivision.

Ok. Thank you! Only one thing remains. That the program crashes instead of showing an error.

The program crashes because of 450,000,000 triangles (not reached trough instancing but objects with 70,000,000 over real triangles). At that point, you are over many limits, for instance, BVH GPU code uses 28 bits for the node index: you can have max 2^28 = 268,435,456 of nodes. It isn't something fixable.


Export-Excel

Having an issue with Export-Excel.  I am doing an AD query and looking to pipe it to Excel.   I am pulling ADGroupMembers (who are Users) and getting the following pieces (These are the headers):
AD_GroupName
AD_GroupNotes
AD_Group_Manager
Name
SamAccountName
Email
Department
I have a text file that I pull AD groups from, but with the issue I am having, I have narrowed it down to a few groups (So I am just setting the $ADGroups to a specific group that is having the issue.  The issue I am running into is in various columns, I am getting erroneous data.  What I have found is that, if that property/parameter is blank, it is not exporting to excel blank; it is pulling eroneous data.  For instance, if the AD_GroupNotes  (Group.info values) is blank/null, it returns the Group.info from another group; if a user's email is blank it is pulling a different person's CN.
Interesting thing is if I run the code in ISE, it returns valid data (with the value being blank, if its truly blank).  If I export the output to CSV, it leaves that cell blank.  However, if I use export-excel, if the value is blank/null, it will put erroneous values in the cell.  Is there a switch/parameter I need to run with Export-Excel, or should I test for blank/null in the code and assign it "No Value" (and if so, how is that done/coded)?
#$ADGroups = Get-Content "C:\Scripts\VDIUSage\VDIGroups.txt"
$ADGroups = "VDI JB Mcleod"

$UserInfo =
Foreach ($ADGroup in $ADGroups) {
    Get-ADGroup -Identity $ADGroup -Properties info, ManagedBy |
          ForEach-Object {
            $Group = $_
            Get-ADGroupMember -Identity $_.objectguid |
                Where {$_.objectclass -eq 'user'} |
                    ForEach-Object {
                        [PSCustomObject]@{
                            AD_GroupName     = $Group.name
                            AD_Group_Notes   = $Group.Info
                            AD_Group_Manager = $(Get-ADUser -Identity $($Group.managedby) -Properties cn).cn
                            Name             = $_.name
                            sAMAccountName   = $_.samaccountname
			                Email			 = $(Get-ADUser -Identity $($_.SamAccountName) -Properties EmailAddress).emailaddress
                            Department       = $(Get-ADUser -Identity $($_.SamAccountName) -Properties Department).Department
                                }
                        }
             }
         }
$Userinfo |  Export-Excel -Path "$DataPath\UserInfo.xlsx"
#$Userinfo |  Export-Csv -Path "c:\scripts\users.csv" -NoTypeInformation

ForEach-Object passes empty objects therefore use checking:
Get-ADGroup -Identity $ADGroup -Properties info, ManagedBy | where-object {$_} | ForEach-Object {}

Hope this will help

@Gtoml data needs to be shaped and scrubbed before exporting it to Excel. Export-Excel is optimized to work with array of data, with fields expanded if needed, or summaries you've applied. Once exported, then you can chart and pivot. Each of these needs the data shaped so visualizations makes sense.