Support alternative distributed communication

Is your feature request related to a problem? Please describe.
I am working on a cluster that forbids opening sockets on a compute node that anyone can connect to, unauthenticated. This means I can't use the 'env://' initialization method for torch.distributed.  Furthermore, I may want to train on systems that do not have CUDA, and therefore would like the option of using an mpi backend for torch.distributed.
Describe the solution you'd like

Options to change the distributed backend for torch.dist
Options to change the default bootstrapping to include things like shared filesystem support.

Describe alternatives you've considered

I've debated coding up everything myself using horovod, but I don't like how it locks me down into MPI and won't let me use nccl afterwards.  Using horovod also breaks pytorch-lightning's abstraction of handling such parallelism for you, and conflicts with the pytorch default of using the 'dp' backend when possible.

@rblake-llnl
That's great. Would love a PR for this.
Is the best UX here to add a:
# default
Trainer(distributed_backend_options = None)

# allow dict for people to customize any parameter in the distributed init
Trainer(distributed_backend_options = {})

?

so, your PR is great, but i wonder if we should make it a flag instead to access your implementation of that. the reason is that it will allow others to access it who may not know how to implement it.
second, perhaps a hook in the init_ddp method can make it even more customizable?

Would allowing the user to specify backend and init_method args that get passed to init_process_group be sufficient to accomplish everything we need? The trouble with passing through *args, **kwargs is that now users have to dig through multiple layers of documentation to figure out what values are allowed.
I'd propose adding a couple new args to Trainer that default to the current values.
Trainer(
    ...
    torch_dist_backend="nccl",
    torch_dist_init_method="env://",
)

Note that I don't love these names, so feel free to chime in with suggestions. distributed_backend is already taken.
I think there's another issue open asking for distributed CPU training. There are some other changes needed for that, but being able to set torch_dist_backend="gloo" is, I think, a necessary step.

I like this suggestion, it might help to enumerate possible future support cases:

nccl
gloo
whatever new one comes up?

Non-slurm cluster or other ddp implementations wouldn't fall under this new flag (i think). This flag in particular is about configuring ddp?
Maybe it makes sense to do it as a hook then?

As far as I can tell, the only way to use DDP right now without SLURM is to manually construct and set the relevant SLURM environment variables (SLURM_NODEID and SLURM_NODELIST.. maybe more?). Otherwise, it looks like the current code overwrites whatever is set in the MASTER_ADDR environment variable with <IP_ADDRESS> and assumes that the current node is node 0.
While I'd love to have "set one flag and it works" support for things like Horovod, I think that #357 at least makes it possible to use DDP in the same enviornment as one would without Lightning, which would be great for kubernetes/sagemaker/databricks/etc. users.
I'd also like to see "set one flag and it works" support for things like Horovod. I'll probably make it work for my use case, but would be happy to turn that into a PR if given a little guidance on API

@capdevc lightning does not overwrite MASTER_ADDR. If it is not passed it uses the default, otherwise it uses the user provided version.
Lightning always assumes the current node is 0 unless an environment var is present to change that.
Non SLURM systems would need a way to set this.
@capdevc if you want to go for it, i think horovod support would be great.
@rblake-llnl , @capdevc can you guys propose an API alternative which does the following:

support variations on DDP backend (nccl, etc...)
supports other ddp implementations.
final case is where the user still wants to do something on their own.

Currently i'm thinking:
Option 1
# default
Trainer(distributed_backend = 'ddp_nccl')
Trainer(distributed_backend = 'ddp_something_else')

Option 2
# default
Trainer(distributed_backend_config = {...}, distributed_backend='ddp')
Trainer(distributed_backend_config = {...}, distributed_backend='horovod')

And to support custom ddp add a hook:
def setup_distributed_backend():
   port = ...
   ...
   init_process_group(...)

Adding in something like horovod is more invasive-- it requires a wrapper around the optimizers and requires separate DistributedSampler calls that are horovod-aware.
Maybe we should think about having some sort of interface that all these models inherit from? Users could implement that interface to use their own distributed interface for things like Horovod.  We could allow distributed_backend to remain as it is, but also allow it to be an object that implements the prescribed interface.
That way, people who want to use more exotic distributed_backend options could create and initialize objects themselves.
The resulting changes could also clean up the use_dp, use_ddp, and so on flags that are scattered throughout the source code and bleed out into userspace.  Code like this in userspace:
        if self.use_ddp:
            train_sampler = DistributedSampler(dataset)

        should_shuffle = train_sampler is None
        loader = DataLoader(
            dataset=dataset,
            batch_size=batch_size,
            shuffle=should_shuffle,
            sampler=train_sampler,
            num_workers=0
        )

could become
        train_sampler = self.sampler(dataset)
        should_shuffle = train_sampler is None
        loader = DataLoader(
            dataset=dataset,
            batch_size=batch_size,
            shuffle=should_shuffle,
            sampler=train_sampler,
            num_workers=0
        )

Great suggestion. I like the idea of a wrapper users can implement for more esoteric versions.
Could you draft a proposal for something like that? (quick, simple and at a high-level so we can modify it quickly before making it super robust)?
@jeffling
This code is like this because users need the option to use DDP WITHOUT using distributedSampler. That came up a while back so we added support for it.
        if self.use_ddp:
            train_sampler = DistributedSampler(dataset)

@rblake-llnl @williamFalcon are we going to any further steps in this one?


Same file + extension in directory names breaks relative image assets

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[X] I have tried the npm run clear or yarn clear command.
[X] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[X] I have tried creating a repro with https://new.docusaurus.io.
[X] I have read the console error message carefully (if applicable).

Description
When referencing static images that are colocated with alongside the Markdown file, if the directory name has <filename>.md in it, the image can't be found.
For example, a file like file.md, with a nearby directory called file.md__static_image_assets__, will break. It attempts to find the file in the global /static folder, even if the path in file.md is like:
[some image](./file.md__static_image_assets/image.png)

This is a legal directory name, so this should work.
Reproducible demo
https://stackblitz.com/edit/github-znyym6?file=docs/file.md
Steps to reproduce

See the reproduction:
Have a folder in docs/ called file.md__static_image__assets with an image.png image in it.
Have a file.md in docs/ with content of something like

![my image](./file.md__static_image_assets__/image.png)

Verify it won't compile.

Expected behavior
Should compile.
Actual behavior
Doesn't compile, looks for the image in /static.
Your environment
Public source code: https://stackblitz.com/edit/github-znyym6?file=docs/file.md
Self-service

[ ] I'd be willing to fix this bug myself.

There is a fault with our link replacement logic. I will refactor this part of the code since it's getting really dense. Thanks for reporting!


How many days a QR code/URL is valid?

Hi,
If I run ./googleauthenticator and generate a new URL/QR code. How many days/weeks this QR code will be valid to be insert on Google Authenticator mobile app? I
Regards,
Marcus Papa.

Forever.


Feature Request: prevent access to component methods unless declared in .cmp markup

Currently the following code is possible:
in my_componentController.js:

 //example 1
  var another_component = cmp.find("my_other_component");
  another_component.helper.private_method(my_variable);

 //example 2
  var another_func = another.get("c.action");
  another_func();

Which makes component encapsulation difficult. I would like 1) to always fail, and 2) to succeed only if the action is marked as exportable in the .cmp file.

Locker Service addresses this encapsulation breakage.


Increment version for keyvault releases

Increment version for keyvault releases

Can one of the admins verify this patch?


InputText is written wrongly

As stated in the screenshot below, instead of writing<EMAIL_ADDRESS>the driver does not write the @ symbol but adds the quotes instead

I suspect this might be related to the locale set on your device. Could you try setting it to English / US to see if that solves the problem?

I tried with both English (USA) and English (UK), but it still writes the quotes instead of @

What is a locale that is set on your Mac? Also, what is the language of an input method?
I am wondering if that could have an effect.

My Mac's locale is Italian, on the emulator I've tried English and Italian keyboard but in both cases it still writes " instead of @.
I've noticed that by running the exact same flow on an Android emulator, the virtual keyboard is shown and the drivers simulates the taps, while on iOS the virtual keyboard is not shown. Is it an intended behaviour?

Yes, we interact with the device via Facebook's IDB that in turn talks directly to Apple frameworks.
Thanks for the context, I was able to reproduce the issue 👍

without actually opening a different issue, I've noticed maestro has issues properly parsing multi-worded input on inputText. I've tried several test cases:

[x] - inputText<EMAIL_ADDRESS>[x] - inputText<EMAIL_ADDRESS>[ ] - inputText<EMAIL_ADDRESS>and something
[ ] - inputText<EMAIL_ADDRESS>and something"

All of these were tested on Android with the emulator and the behavior is consistent. also went through the code but it seems as if the YAML parses defaults to null when it fails to parse the inputText String. thoughts?

without actually opening a different issue, I've noticed maestro has issues properly parsing multi-worded input on inputText. I've tried several test cases:

[x]  - inputText<EMAIL_ADDRESS>[x]  - inputText<EMAIL_ADDRESS>[ ]  - inputText<EMAIL_ADDRESS>and something
[ ]  - inputText<EMAIL_ADDRESS>and something"

All of these were tested on Android with the emulator and the behavior is consistent. also went through the code but it seems as if the YAML parses defaults to null when it fails to parse the inputText String. thoughts?
edit: test cases that fail produce an empty string hence the suspicion towards the parses defaulting to null (or empty)

I am also running into the same issue as I was just about to create an issue. Glad to see someone already mentioned it

Hey folks, just wanted to call out that this is a high priority for us, we are going to look into it early next week

@MenilV thanks for reporting and the test cases. The issue is different from what @smsimone mentioned, but is nonetheless valid. I have addressed it in #122 (going to be released today/tomorrow).
@smsimone I have confirmed that the issue you are facing is related to the system input method (aka keyboard language). The simplest way to fix it is to switch to a US English keyboard layout. In the meantime, I am looking for a smarter way to resolve it.

Android part of the bug was addressed in #122

Lets merge everything into #146


AWS disovery via proxy

This is a breaking change and rightly increments the minor version 👍 . Should there be migration documentation for users who currently do NOT use the external ID in their auth setup? Those users will be broken by this change. Alternatively, you could preserve Optional/do null checks guarding setting the external id in the downstream client. Absolutely correct to require the external id on the net new config for the proxy role arn.

@oferrigni While this does change the API (Optionals are no longer used) the behavior hasn't changed, externalID can still be null (as can the new proxyRoleConfig parameter). I've gone ahead and added Javadoc annotations and comments to the method to make it clear for anyone who may be using Magpie as a library.


Used date picker lib in slim mode

Pull requests into Flux require the following. Submitter and reviewer should :white_check_mark: when done. For items that are not-applicable, note it's not-applicable (N/A) and :white_check_mark:.
Originally, slim mode was using an html date picker for selecting dates in slim mode (specifically for reference date in disease status form, enrollment date and end date for clinical enrollment form, and date of death on the deceased form). The date picker component does not render in IE. To fix this, replaced the html date picker component with the react-day-picker component (https://github.com/gpbl/react-day-picker)
Submitter:
Documentation

[x] This pull request describes why these changes were made
[x] Recognizes any potential shortcomings/bugs in the description
[x] N/A Cheat sheet is updated
[x] N/A Demo script is updated
[x] Documentation on Wiki has been updated
[x] Additional technical components and libraries are documented and added to wiki as needed

NoteParser

[x] N/A Note parser has been updated if structured phrases change

Code Quality

[x] 4-space indents - convert any tabs to spaces
[x] Use public class field syntax for binding functions - ex. handleChange = () => { ... };
[x] Code is commented

Tests

[x] Existing tests passed
[x] N/A Added UI tests for slim mode
[x] N/A Added UI tests for full mode
[x] N/A Added backend tests for fluxNotes code
[x] N/A Added note parser examples to test new functionality

Reviewer 1: Name

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Reviewer 2: Name

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

LC1- When you select a Enrollment Date in IE it populates the End Date with that date as well and vice versa.

We should add testing on Chrome and IE to the definition of done although that's difficult for Julia so she may be exempt and her reviewers need to make sure to try it on IE on Windows.

@laclark22 Yikes! Nice catch. I know what I did wrong so I can fix that right away. It's also happening in Chrome too. @gregquinn2001 That is a good suggestion. We do have IE and Chrome in our automated tests but we can definitely add that to our manual tests as well.

@laclark22 [LC1] has been fixed

@gregquinn2001 Updated the template for pull requests to include manual testing in IE and in chrome so future pull requests will have that check. I also updated the Developer Definition of Done in the project wiki to include manual testing in IE and Chrome

thanks @nicoleng12  and thanks to everyone for reviewing so quickly!


Always split response type

Partially based on discussion https://github.com/RobinTail/express-zod-api/discussions/2219
Needed for #2226
But generally should simplify the flow and enable further improvements of the Integration class

✅ QA passed


Statistical Counters

The current profile implementation requires synchronization of kernels to be accurate. This is very bad. We should use cudaEvent or similar.
However, these things are not supported by AnyDSL yet. A kernel aware annotation (for debug & profiling) and query system for AnyDSL needs to be implemented in the runtime.

Done in the features/runtime2 branch


Is "_collapsible" property for the node, still available in v2? If not, what will be the alternative?

Thank you for taking the time to report an issue with react-d3-tree!
Feel free to delete any questions that do not apply.
Are you reporting a bug, or opening a feature request?
[Replace with your answer]
What is the actual behavior/output?
[Replace with your answer if relevant]
What is the behavior/output you expect?
[Replace with your answer if relevant]
Can you consistently reproduce the issue/create a reproduction case (e.g. on https://codesandbox.io)?
[Replace with your answer if relevant]
What version of react-d3-tree are you using?
[Replace with your answer]
If react-d3-tree crashed with a traceback, please paste the full traceback below.
[Replace with your traceback]

got it working this way
  componentDidUpdate() {
    let nodeDatum = this.props.nodeDatum
    if (nodeDatum.collapsed && !nodeDatum.__rd3t.collapsed && !this.state.updated) {
      this.props.toggleNode()
    }
  }

  onClick = () => {
    this.setState({ updated: true})
    this.props.toggleNode()
  }

Hi Jordan,
I was curious what issue you were having or trying to overcome with the code above?  Also, where is updated set back to false?
Only reason I am asking, is that we are extending on click behavior when rendering a node and update a state variable for currently selected node before calling the default toggleNode().  If I comment out the code to update the state variable the tree properly recognizes the toggleNode and either expands or collapse the branch.  However, if the code to update the state variable is executed then calling toggleNode appears to do nothing.  I wasn't sure if you were seeing some similar type of issue with your question.
`  const renderCustomNodeElement = ({ nodeDatum, toggleNode, onNodeMouseOver, onNodeMouseOut }) => {
const displayID = generateDisplayID(nodeDatum.name);
// Check if the current node is the selected node
const isSelected = selectedNode && selectedNode.attributes.wid === nodeDatum.attributes.wid;
const hasChildren = nodeDatum.children && nodeDatum.children.length > 0;
const strokeColor =getStrokeColor(nodeDatum, isSelected, hasChildren);
const strokeWidth = getStrokeWidth(isSelected, hasChildren);

const handleNodeClick = (event) => {
  if (event.shiftKey) {
   setShiftBtnDown(true);
  } else {
    setShiftBtnDown(false);
  }
  setSelectedNode(nodeDatum);  // state variable, if commented out toggleNode works, as is toggleNode doesn't do anything

  // call default functionality
  toggleNode(event);
};

return (`


[LevelUp] importleveler only imports users who have sent a message since the cog was loaded

I'm using aikaterna's fork of fixator's leveler cog. When I use the importleveler command, it only imports 2 users (my user and another user who sent a message after the cog was loaded) and nothing else. There are no errors in the log while executing the command.

I switched to using fixator's leveler cog, which uses the same mongodb so all the data is the same. I still can only import the users who have sent messages since importing the LevelUp cog.

Ill take a look at it when i get home, it may be only importing users that have an existing config with leveler, ill fix that if so

Alright you can update the cog and try again now. the issue should be resolved, it now creates data for any users that dont exist yet in the levelup config. If this fixes your issue you can close this.


build for android failed due to unable to find library -lpthread

android has no separated libpthread, it is included in libc
reference：https://developer.android.com/ndk/guides/stable_apis#c_library
in android.toolchain.cmake has folloing code which can be used to check if is Android platform
set(CMAKE_SYSTEM_NAME Android)

Note that lpthread is only needed by the CLI, which I wouldn't necessarily expect to build with the NDK? If you do need the CLI, feel free to submit a PR that fixes this.

there are two workaround, I would like to  konow which do fou prefer?
1
if (UNIX)
    find_library(LIBPTHREAD pthread)
    if (LIBPTHREAD)
         target_link_libraries(Luau.Repl.CLI PRIVATE pthread)
    endif()
endif()

2
if (UNIX)
    if (NOT "${CMAKE_SYSTEM_NAME}" STREQUAL Andriod)
         target_link_libraries(Luau.Repl.CLI PRIVATE pthread)
    endif()
endif()

Either of these is probably fine. The first one seems a bit cleaner.

Fixed by #203.


Add title handling.

Adds support for addons/apps to update the document title by using renderer:-dom.

Tested and works very well with<EMAIL_ADDRESS>


Syntax incorrect after upgrade

After upgrading blazor from v0.1 to v0.2 , i get a syntax error on the default project

I don’t think you’ve installed the correct Visual Studio extension. Could you reinstall or update your “Blazor Language Services” VS extension?

@SteveSandersonMS i was working normaly when using blazor v0.1 then after upgrading to v0.2 , the blazor extanction was notifying me to upgrade , after doing that i got this error

I would try removing the extension and reinstalling it


Issues connecting over VPN

Backstory:
my ISP has CGNAT, the main downfall of this is I am unable to forward any ports traditionally. so to get around this I use a vpn that supports port forwarding, I use this for a few services and it works swimmingly.
I have setup uptime kuma, and uptime buddy, and got them connected easy, and got uptime buddy to work fine if I point it at my local IP when connected to my local network, but when I point it at my VPN ip address I get the following error:
" Network Error Occurred: The resource could not be loaded because the App Transport Security Policy requires the use of a secure connection"
I know the port is open successfully and able to leave my network and allow external connections in using a port tester.
This is running using docker on the latest release
I completely understand if my setup is one that is unsupported and you aren't able to assist, but I wanted to reach out!
thank you

Hey,
The resource could not be loaded because the App Transport Security Policy requires the use of a secure connection tells me that your backend is http nor https, right?
There is an option to allow insecure connections on the apps.
Let me do some research about this, how it impacts the security or any guidelines.
I will let you know, if I can implement it.

That makes perfect sense! I’m guessing secure connection is required for any form of connection to a remote network by default? As it did work on local lan onlyI really appreciate you looking into this, and no pressure to lower the security below your comfort level for this request, this might just be the kick in my butt I need to get ssl setup. Thanks for your time! On Oct 26, 2024, at 2:15 PM, schech1 @.***> wrote:
Hey,
The resource could not be loaded because the App Transport Security Policy requires the use of a secure connection tells me that your backend is http not https, right?
There is an option to allow insecure connections on the apps.
Let me do some research about this, how it impacts the security or any guidelines.
I will let you know, if I can implement it.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>


Solving anthropic packaging version issue

Description: Solving, anthropic packaging version issue by clearing the mixup from package.version that is being confused with version from - importlib.metadata.version.

Issue: it fixes the issue #7283

Maintainer: @hwchase17

The following change has been explained in the comment - https://github.com/hwchase17/langchain/issues/7283#issuecomment-1624328978

thanks @dudesparsh!


Do not reuse label in showLabel() method

I have use case where I add custom HTML markup into error label in errorPlacement callback method.
Custom HTML is a fontawesome icon:
HTML generated by default jQuery validation:
ERROR MESSAGE

What I try to achieve is:
ERROR MESSAGE

However, current jQuery validation implementation reuses existing error labels and removes all content from inside the label tag, without calling errorPlacement callback again.
The issue is that my custom HTML is removed from label and there is no way to put it back when error message is replaced.
My suggested solution is to not allow to reuse existing error labels in showLabel() method. Instead it may try to remove existing label just before creating one.
Please see line 4. of the code below.
Here is fixed code for latest release:
showLabel: function( element, message ) {
			var label = this.errorsFor( element );
			if ( label.length ) {
				// do not reuse existing label - just remove one if it already exists (P.Szalko)
				label.remove();
			}
			// create label
			label = $("<" + this.settings.errorElement + ">")
				.attr("for", this.idOrName(element))
				.addClass(this.settings.errorClass)
				.html(message || "");
			if ( this.settings.wrapper ) {
				// make sure the element is visible, even in IE
				// actually showing the wrapped element is handled elsewhere
				label = label.hide().show().wrap("<" + this.settings.wrapper + "/>").parent();
			}
			if ( !this.labelContainer.append(label).length ) {
				if ( this.settings.errorPlacement ) {
					this.settings.errorPlacement(label, $(element) );
				} else {
					label.insertAfter(element);
				}
			}
			if ( !message && this.settings.success ) {
				label.text("");
				if ( typeof this.settings.success === "string" ) {
					label.addClass( this.settings.success );
				} else {
					this.settings.success( label, element );
				}
			}
			this.toShow = this.toShow.add(label);
		},

I'm sorry for the lack of activity on this issue. Instead of leaving it open any longer, I decided to close old issues without trying to address them, to longer give the false impression that it will get addressed eventually, especially after several years with no activity. It doesn't mean I'm abandoning the project, just that I'm unable to work through 200+ open issues with the little time I can afford to spend on this project.
To the reporter (or anyone else interested in this issue): If you're still affected by the same issue, please consider opening a new issue, with a testpage that demonstrates the issue with a current version of the plugin. Even better, make an attempt to fix the issue yourself, and improve the project by sending a pull request. This may seem daunting at first, but you'll likely learn some useful skills that you can apply elsewhere as well. And you can help keep this project alive. We've documented how to do these things, too. A patch is worth a thousand issues!


Suggestions to Improve debug/visualisation in SMT2 backend for SBY

Steps to reproduce the issue
Consider this dummy test, Verilog and SBY files:
`default_nettype none
module fsm (input wire clk, rstn, start, a, b, c, d,
            output reg [1:0] state_val);

        localparam [3:0] s0=0, s1=1, s2=2, s3=3;
        reg [1:0] ps, ns;

        wire jump_s2, jump_s3, return_w;
        assign jump_s2 = &({a,b,c,d});
        assign jump_s3 = (~a & b & c & ~d);
        assign return_w  = (a | d & ~b);

        always @(posedge clk) begin
                if (~rstn) ps <= s0;
                else       ps <= ns;
        end

        always @(*) begin
                ns = ps;
                case (ps)
                        s0: if (start)   ns = s1;
                        s1: if (jump_s2) ns = s2;
                        s2: if (jump_s3) ns = s3;
                        s3: if (return_w)  ns = s0;
                endcase
        end
        assign state_val = ps;

        // Assertion logic
        always @(*) assume (rstn == 1'b1);
        always @(posedge clk) if (ps == s2 && jump_s3) assert (ps == s3);
endmodule

SBY:
[options]
mode bmc

[engines]
smtbmc boolector

[script]
read_verilog -formal fsm.v
prep -top fsm

[files]
fsm.v

Expected behavior
When a formal tool finds a failure, it shows a concise CEX with logic that influences the assertion/cover logic. For this particular example the logic influences are: ps, jump_s3, clk and rstn, as shown in the following VCD. The rest of the tools also shows the exact moment where the assertion failed (see assert_always_i transition from 1 to 0 (falsification)).

Actual behavior
User needs to get signals from the generated VCD file, and correlate it back with the RTL. For trivial modules it may not represent a problem. For big designs, both in size and depth (states), this kind of debuggability may represent a barrier of tool adoption.

A quick workaround is to separate the formal "testbench" into separate file, bind or instantiate it into the top module, and when a CEX or reached cover is found, get the signals from the container, as starting point. But still requires human intervention.
// Assert container
module assert_always (input wire event_m, disable_e, precondition, condition);
`ifndef _SV_
	always @(*) assume (disable_e == 1'b1);
	always @(posedge event_m)
                if (precondition) assert (condition);
`else
	assert_always_i: assert property (@(posedge event_m) disable iff (!disable_e)
					    precondition |-> condition);
`endif

// Assert container instance
wire cause  = (ps == s2 && jump_s3);
wire effect = (ps == s3); // check ns instead, to fix it
assert_always checker_inst (clk, rstn, cause, effect);
endmodule

Maybe a better approach is to add a mechanism in backends/smt2/smt2.cc to add that information in the SMT generated model, as a comment like how it extracts the assertion name, and let smtio.py and smtbmc.py deal with the extra information needed in the generate_vcd function.

This is really more of a SymbiYosys issue than a Yosys issue; but there will probably need to be some handling on the Yosys side to enable it.
A first rough idea would be to select the fan-in cone of the property that was triggered, and create a .gtkw file with the public names from that cone already added to the waveform. Might need something fancier for big designs, as the entire cone might be too big, but a fixed number of levels might lead to odd results because of differing amounts of non-public logic inbetween.

I can move it if that's better. I opened here because AFAICS the smt2 already dumps the private names of the wires, so it will be probably more easy to deal with this in the SMT backed that is hosted in Yosys, but IDK.


ES Modules based ComponentLoader

Currently we have two ComponentLoader options:

CommonJS based loader used normally for Node.js NoFlo programs
"Hardcoded" component loader baked in with noflo-component-loader in Webpack builds

Nowadays browsers generally support Modules including dynamic imports. Node.js is also getting there. So, we should add a Module ComponentLoader option into NoFlo.
Using Modules would be especially interesting on browser, as it could allow loading components from various libraries as needed instead of having to have a "kitchen sink" build. A module loader should be possible to supply with a set of "fbp manifest" files telling where various components are available. It would then use dynamic loading to pull them in.
It would also open the door for making NoFlo available in tools like jsfiddle, as requested in #102 and #101

Once we have this in place, it might make sense to have a CI/CD process for NoFlo component libraries that would publish their component files and a fbp.json on GitHub Pages.


GREET Data Hotfix

Hotfix to correct values and units for iron ore mining and pelletizing emission intensities based on feedback from ANL.
Related issue
https://github.com/NREL/HOPP/pull/380
Impacted areas of the software
resources
Additional supporting information
This work is being completed for the LCA integration, the data pulling and parsing will live in HOPP, the LCA calculations with that data will live in GreenHEART
Test results, if applicable
tests/hopp/test_greet_resource.py ...

Thanks for this, @dakotaramos! The changes you've made look good.
The failing CI appears unrelated to your changes. @RHammond2, could you please take a look and see if a package update or similar has caused these tests to fail?

Thanks for this, @dakotaramos! The changes you've made look good. The failing CI appears unrelated to your changes. @RHammond2, could you please take a look and see if a package update or similar has caused these tests to fail?

The issue is stemming from the KML object having features as a callable, so if we change these lines to use k.features instead of k.features(), then we should be ok in theory.
However, something I noticed is that we'll also be attempting to index an empty list in the tests, so this will raise a new error. Doubly however, this is call was not previously an issue, so I checked out the fastkml changelog, and they had a v1.0 release in mid-November.
tl;dr: Pin fastkml to be < 1, and open an issue to migrate HOPP and GreenHEART to be compatible with fastkml v1.0.

@RHammond2 @johnjasa just pushed the update to the fastkml version in pyproject.toml


Detail pages sidebar #1663

Suggestion: on hold until as we need to focus on the LSP migration + implementation might be easier later.


Stuck on "Downloading CLM"

I am trying to run the PICO W example. I know it worked before with a previous revision of this crate, but now, I get these info prints:
2.857950 INFO  shared: SharedMemData { flags: 00000001, trap_addr: 00000000, assert_exp_addr: 00000000, assert_file_addr: 00000000, assert_line: 00000000, console_addr: 0006debc, msgtrace_addr: 00000000, fwid: 22213098 }
2.858024 INFO  init done
2.858201 INFO  Downloading CLM...

After which nothing anymore happens.

My bad, some bug slipped back in when I tries to split my work into multiple PRs.
The wifi task has to be spawned before issuing ioctls. Downloading the CLM data is the first ioctl that happens, so it will just be stuck there.
You can try the fix and see if it works for you.
The last few commit also switch to an new implementation using a PIO for the SPI bus. It would be interesting, if that works for anyone else but me ;). But if you get to the CTM download it should be fine.


Add support for empty values (Proper)

This is a new pull request for #103, based on comments of #104 .
It now supports primitive types properly, and use the new AbstractRecordMapper class.
It also add a constructor to the AbstractRecordMapper class.

Easy Batch Framework » easybatch-framework #81 UNSTABLE
Looks like there's a problem with this pull request
(what's this?)

Easy Batch Framework » easybatch-framework #82 FAILURE
Looks like there's a problem with this pull request
(what's this?)


Errors with log-sink and log-action Kamelet

I am seeing errors in YAKS tests while using log-action Kamelet:
ERROR [io.qua.run.Application] (main) Failed to start application (with profile prod): org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint: log://log-action?level=INFO&logMask=false&multiline=false&showAllProperties=false&showBody=true&showBodyType=true&showCachedStreams=true&showExchangePattern=true&showHeaders=false&showProperties=false&showStreams=false due to: There are 1 parameters that couldn't be set on the endpoint. Check the uri if the parameters are spelt correctly and that they are properties of the endpoint. Unknown parameters=[{showCachedStreams=true}]

Do we need to remove showCachedStreams property form the Kamelet?

same with log-sink Kamelet

ShowCachedStreams is in 3.20.0-SNAPSHOT. it should be released soon. I think this is the problem. But need to double check

Yes, showCachedStreams is a new addition to 3.20.0 so it should be fixed once Camel is upgraded to 3.20.0.
https://camel.apache.org/components/next/log-component.html#_endpoint_options

This is related to camel k runtime not aligned to 3.20.0, it should be something to report in camel k

I think we already fixed that, making main Camel K to depend on the latest Kamelets tag aligned with the expected Camel version.

@squakez I did rebase the PR on main branch but still the log-action Kamelet is not able to run properly with Camel K as shown in the tests https://github.com/apache/camel-kamelets/actions/runs/3872513218/jobs/6601438316#step:11:817

Camel K main is built against a stable relase of Kamelets 0.10.0: https://github.com/apache/camel-k/blob/main/script/Makefile#L88 - this is because the latest version of Camel K still uses Camel 3.19. If you need a Camel K operator (and runtime) available for Camel 3.20, I guess you'll need to wait for the related update (which is mainly driven by Camel Quarkus).

Unfortunately this is not a good situation for the CI tests in this Kamelet catalog repository. They will keep failing until the Camel K runtime with Camel 3.20 is available.
I see an option to move from Camel K runtime to JBang in the tests in order to align with Camel 3.20. I really would like to keep Camel K runtime in Kamelets tests, too but waiting such a long time is not a good option IMO

Yes. As Kamelets are going to be completely decoupled from Camel K, it makes sense to use some other way of testing it against the latest Camel version.


Add nbinteract stretch features (Sprint 4)

This repo is deprecated now! https://github.com/data-8/nbgitpuller is what is now going to be used.


Spreadshirt links on Shop page are dead

Both mc-stan.spreadshirt.com and mc-stan.spreadshirt.co.uk are dead links on https://mc-stan.org/shop/.
I also could not find Stan at all on the Spreadshirt website to let me update the links on that page via a pull request, so perhaps we can no longer infer in style?

They seem to be working once again


[Feature] how to change the  order of the top menu item ,or hide it .  with @univer/ presets0.5.0

Initial checklist

[X] Is this really a problem?
[X] I have searched the Github Issues for similar issues, but did not find anything.

Problem
how to change the  order of the top menu item ,or hide it .  with @univer/ presets0.5.0


Polyfill glitching out over large areas bug?

Hi all,
I am attempting to use h3 to generate a GeoJSON polygon that I will then overlay on a mapbox map. When I try and polyfill(blue) a large square polygon(red) the resulting output gets really glitchy (see screenshots)

However when I halve the size of the red box, the polyfill works as intended?

const polygon = [
        [minLon, maxLat],
        [maxLon, maxLat],
        [maxLon, minLat],
        [minLon, minLat]
    ];
    const hexagons = h3.polyfill(polygon, 1, true);

    let hexFeatures = []
    for(let h of hexagons){
        let hexFeature = {
            'type': 'Feature',
            'geometry': {
                'type': 'Polygon',
                'coordinates': [h3.h3ToGeoBoundary(h, true)]
            }
        }
        hexFeatures.push(hexFeature)
    }

let hexGroup = {
        "id": "hex",
        "type": "fill",
        "source": {
            "type": "geojson",
            "data": {
                "type": "FeatureCollection",
                "features": hexFeatures
            }
        },
        'layout': {},
        'paint': {
            'fill-color': '#0000ff',
            'fill-opacity': 0.50
        }
    }

    map.addLayer(worldGroup)

Is this a possible bug?
Thanks

There are two issues here, both (unfortunately) expected and somewhat documented:

The current H3 polyfill algorithm can't deal with polygon segments of greater than 180 degrees longitude. Otherwise, we interpret the bounding box of the polygon as crossing the antimeridian. The alternative was to require incoming polygons to follow the Right Hand Rule, and while we obey this in output we didn't want to enforce it in input. So what you're seeing in the first image is the set of hexagons in the bounding box between the western edge of your real bounding box (interpreted as east) and the eastern edge of your bounding box (interpreted as west).

Mapbox doesn't deal well with drawing polygons that cross the antimeridian. So the cross-globe lines you see in the first image are a rendering artifact, not actual H3 output. The fix is to adjust the geometry to go outside the +-180 degree longitude range (i.e. a segment from longitude -179 to longitude 179 would need to be rewritten as going from -179 to -181).

So unfortunately this is "working as expected". You can polyfill the area by using multiple bounding boxes, and you can draw it correctly by adjusting the output geometry to what Mapbox expects.

Many thanks for a fast, clear & consise reply! Can probably close this issue.


raftstore: add a concurrency limiter for receiving snapshots

What is changed and how it works?

Issue Number: Ref #15972

What's Changed:
This commit starts to introduce a snapshot precheck mechanism to reduce
unnecessary snapshot drops and generations. The mechanism functions as follows:

Before a leader sends a snapshot to a follower, it first sends a precheck
message. This message serves as a preliminary inquiry to the follower, seeking
confirmation of its readiness to receive a snapshot. Upon receiving the message,
the follower consults its concurrency limiter and returns a response to the
leader. The leader will only proceed to generate the snapshot after the precheck
is passed.

A passed precheck means the leader has reserved a spot on the follower so the
subsequent snapshot send should succeed. The reservation has a TTL and the
leader is supposed to complete the snapshot generation and transmission within
the TTL timeframe.

Note that this commit implements the concurrency limiter without actually using
it. A follow-up commit will update the snapshot sending process and make use of
this concurrency limiter.

Related changes

[ ] PR to update pingcap/docs/pingcap/docs-cn:
[ ] Need to cherry-pick to the release branch

Check List
Tests

[x] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Release note

None

/cc @overvenus could you help review this?
The approach right now is similar to what we discussed last week except that the follower would not return a string token and would not ask for a token when receiving the snapshot. The follower merely maintains a counter where each counted object has a TTL. I think this is sufficient for slowing down snapshot requests from the leader. Also, the existing concurrent_recv_snap_limit is still in place to protect the receiver from receiving too many snapshots.

/ok-to-test

/test

/test all

/merge


Library entries not sorted by {number}

I just adpated it straight from the IMDB top 250 example, only added my own library names and folders.
# New library details
new_library:
  name: '_Movies - IMDB Top 250'
  folder: 'D:\Main\RClone\python-plexlibrary-master\symlinks\_Movies - IMDB Top 250'
  sort: true
  sort_title:
    format: '{number}. {title}'
    visible: true
    absolute: true  # Skips numbers for missing items
  # Limit the age (in years) of items to be considered
  # * 0 for no limit
  max_age: 0
  # Maximum number of items to keep in the library
  max_count: 250
  # Remove items that no longer exist in the source lists
  remove_from_library: true
So if I understand it correctly it should become something like:

The Shawshank Redemption
The Godfather Part II

However, the sort titles of the Plex items are just the regular titels of the items. So it's just simply sorted alphabetically. Looking at the CMD it does know the actual numbers that belong to the items.

Did you manage to fix this?


Document how to delete all records from all tables

This PR documents how to delete all records from all tables using postgres, sqlite and mysql. It gives an example for doing this with each database. The info is added to the CRUD page. Though this page might get split up into sections by operation later.
Fixes #451

One other option that is already documented - use deleteMany in a particular order, run all queries in a transaction: https://www.prisma.io/docs/guides/prisma-guides/prisma-client-transactions-guide#scenario-privacy-legislation


chore(main): release 1.26.36

:robot: I have created a release beep boop
1.26.36 (2023-10-07)
Bug Fixes

use && windows (5b2e4e0)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/aidanaden/canvas-sync/releases/tag/v1.26.36 :sunflower:


Shader bgcolorchange.shpk

Add support for the shader bgcolorchange.shpk (used by dyeable furniture, such as Riviera Round Table.)

Finished as of ec1627667280492aa55ec4ac755b919a64cc3a80.


Z-Wave "Network is stopped" on OS X

Home Assistant release (hass --version):
0.19.4
Python release (python3 --version):
Python 3.5.1
Component/platform:
Z-Wave on OS X
Description of problem:
I can't get Z-Wave to work on OS X using an Aeotec USB Z-Stick S5 controller. Everything works fine with OpenHAB so it shouldn't be due to a faulty stick.
Problem-relevant configuration.yaml entries and steps to reproduce:
zwave:
  polling_interval: 60000
  usb_path: /dev/tty.usbmodem1421

Traceback (if applicable):
INFO:homeassistant.components.zwave:network state: 0 Network is stopped
INFO:homeassistant.components.zwave:network state: 0 Network is stopped
INFO:homeassistant.components.zwave:network state: 0 Network is stopped
INFO:homeassistant.components.zwave:network state: 0 Network is stopped
INFO:homeassistant.components.zwave:network state: 0 Network is stopped
INFO:homeassistant.components.zwave:network state: 0 Network is stopped
INFO:homeassistant.components.zwave:network state: 0 Network is stopped
INFO:homeassistant.components.zwave:network state: 0 Network is stopped
INFO:homeassistant.components.zwave:network state: 0 Network is stopped
INFO:homeassistant.components.zwave:network state: 0 Network is stopped
INFO:homeassistant.components.zwave:network state: 0 Network is stopped
INFO:homeassistant.components.zwave:network state: 0 Network is stopped
INFO:homeassistant.components.zwave:network state: 0 Network is stopped
INFO:homeassistant.components.zwave:network state: 0 Network is stopped
INFO:homeassistant.components.zwave:network state: 0 Network is stopped
INFO:homeassistant.components.zwave:network state: 0 Network is stopped
INFO:homeassistant.components.zwave:network state: 0 Network is stopped
INFO:homeassistant.components.zwave:network state: 0 Network is stopped
INFO:homeassistant.components.zwave:network state: 0 Network is stopped
INFO:homeassistant.components.zwave:network state: 0 Network is stopped
INFO:homeassistant.components.zwave:network state: 0 Network is stopped
INFO:homeassistant.components.zwave:network state: 0 Network is stopped
INFO:homeassistant.components.zwave:network state: 0 Network is stopped
INFO:homeassistant.components.zwave:network state: 0 Network is stopped
INFO:homeassistant.components.zwave:network state: 0 Network is stopped
INFO:homeassistant.components.zwave:network state: 0 Network is stopped
WARNING:homeassistant.components.zwave:zwave not ready after 30 seconds, continuing anyway
INFO:homeassistant.components.zwave:final network state: 0 Network is stopped
INFO:homeassistant.components.zwave:zwave polling interval set to 60000 ms
INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: domain=zwave, service=add_node>
INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: domain=zwave, service=remove_node>
INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: domain=zwave, service=heal_network>
INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: domain=zwave, service=soft_reset>
INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: domain=zwave, service=test_network>

What if you try a shorter or the default polling_interval? Mine showed this error recently after I was ding some dev work but rebooting the pi seems to have brought it back online.

@Kapeli I'm having the same problem on OS X. Were you able to solve this?
INFO:homeassistant.components.zwave:ZWave network autoheal is enabled.
INFO:homeassistant.core:Bus:Handling <Event component_loaded[L]: component=zwave>
INFO:openzwave:Start Openzwave network.
WARNING:homeassistant.components.zwave:zwave not ready after 30 seconds, continuing anyway
INFO:homeassistant.components.zwave:final network state: 0 Network is stopped

I was not able to solve this. Changing the polling_interval didn't do anything.

Bummer. I'm having the same problem with hass 0.23.1. Also, when I invoke the add_note service, I see in logs:
INFO:homeassistant.core:Bus:Handling <Event call_service[L]: service=add_node, service_data=, domain=zwave, service_call_id=24543180-1>
/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/homeassistant/components/zwave.py:356: DeprecationWarning: Call to deprecated function begin_command_add_device.
  NETWORK.controller.begin_command_add_device()
ERROR:homeassistant.core:BusHandler:Exception doing job
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/homeassistant/core.py", line 835, in job_handler
    func(arg)
  File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/homeassistant/core.py", line 688, in _execute_service
    service(call)
  File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/homeassistant/core.py", line 547, in __call__
    self.func(call)
  File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/homeassistant/components/zwave.py", line 356, in add_node
    NETWORK.controller.begin_command_add_device()
  File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/openzwave-0.3.1-py3.5.egg/openzwave/object.py", line 48, in new_func
    return func(*args, **kwargs)
  File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/openzwave-0.3.1-py3.5.egg/openzwave/controller.py", line 1110, in begin_command_add_device
    self.CMD_ADDDEVICE, self.zwcallback, highPower=high_power)
  File "src-lib/libopenzwave/libopenzwave.pyx", line 4120, in libopenzwave.PyManager.beginControllerCommand (src-lib/libopenzwave/libopenzwave.cpp:28637)
TypeError: an integer is required

@Kapeli I think i've finally got to the bottom of this. I believe OS X sees two devices, the serial-usb interface that we want, and separately a usb modem. I b

@Kapeli I finally got to the bottom of this. You should see two devices when you plug in your USB stick. One is /dev/tty.usbmodem1421. The other is /dev/cu.usbmodem1421. You want to use the cu.usbmodem, not the tty.usbmodem. The reason for this is that TTY devices are for calling into a UNIX system, and will wait for a data-carrier-detect before responding. CU devices are for calling out of UNIX systems, and so will not assert DCD and will respond immediately. This is why the TTY device was hanging for us.
More info here: http://stackoverflow.com/questions/8632586/macos-whats-the-difference-between-dev-tty-and-dev-cu/8632603

That fixed it for me too. Thanks!


Collect more metrics by default

What does this PR do?

Motivation

Additional Notes

Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Changelog entries must be created for modifications to shipped code
[ ] Add the qa/skip-qa label if the PR doesn't need to be tested during QA.

Current dependencies on/for this PR:

master:

PR #16629

PR #16630

PR #16631 👈

This comment was autogenerated by Freephite.


Add changelog docblock

In Rector itself we have this nice little gem to add an @changelog docblock for every rule which is also outputted after running it. This is very helpful in order to understand why the change has to be done

Add custom PHPStan Rule https://github.com/sabbelasichon/typo3-rector/blob/main/utils/phpstan/src/Rules/AddChangelogDocBlockForRectorClassRule.php


edit_post_id in posts.php_ XSS (Cross Site Scripting) exists for the place parameter

After installation, log in to the backend using the default account password tester/1234
select posts

enter payload
?edit_post_id=3);</script><script>alert(1024)</script>

execution results

Use burpsuite to capture packets.

if (isset($_GET['edit_post_id'])) {
    $edit_post_id = $_GET['edit_post_id'];
    echo "<script>loadPostEditForm($edit_post_id);</script>";
}

The vulnerable code location is line 274 in core/tools/posts.php

Thank you for spotting and reporting security holes in the code. Following
your observations, I reviewed the code and implemented the recommended
security improvements. Using the PHP functions filter_input() and
htmlspecialchars(), I sanitized and encoded all the data that comes from
the URL parameters. This should prevent any XSS-type attacks.
I think these changes will increase the security and quality of the
project. If you have any further observations or recommendations, be sure
to let me know.
Thanks again for your help and attention.
2023-10-24, an, 13:36 光头强不会砍树了 @.***> rašė:

After installation, log in to the backend using the default account
password tester/1234
select posts
[image: image]
https://user-images.githubusercontent.com/113713406/277630999-f5b40b5c-fd5b-4b35-99e3-2d5305974934.png
enter payload
?edit_post_id=3);
[image: image]
https://user-images.githubusercontent.com/113713406/277631071-2445c0a4-1cf0-4533-a7bd-bad1f5a9d050.png
execution results
[image: image]
https://user-images.githubusercontent.com/113713406/277631314-33adb1b1-31ee-4e9d-ba6d-13fee97753cf.png
Use burpsuite to capture packets.
[image: image]
https://user-images.githubusercontent.com/113713406/277631397-d096f43e-7b1c-419c-8e20-0fb0781a3a86.png
if (isset($_GET['edit_post_id'])) {
$edit_post_id = $_GET['edit_post_id'];
echo "";
}
The vulnerable code location is line 274 in core/tools/posts.php
—
Reply to this email directly, view it on GitHub
https://github.com/flusity/flusity-CMS/issues/2, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZINVW6OYZ7U36MRA3P4BFDYA6K37AVCNFSM6AAAAAA6NPHKJCVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE2TQOJWG4YTANI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
Pagarbiai,
Darius Jakaitis

To manage this project more efficiently, we recommend creating a version identifier and recording which bugs or vulnerabilities are fixed in each version. This will help ensure continuous improvement and quality control of the project, while also facilitating communication and collaboration among team members. Here are some suggestions to improve this project: 1. Assign a unique number to each version, such as v1.0, v2.0, etc. This will help clearly differentiate between different versions. 2. Detail the new features, improvements, and fixed bugs or vulnerabilities of each version in the version release notes. This will help users understand what each version is about. 3. Conduct code reviews during key stages of the project  to ensure code quality and follow best practices.

Thank you for spotting and reporting security holes in the code. Following your observations, I reviewed the code and implemented the recommended security improvements. Using the PHP functions filter_input() and htmlspecialchars(), I sanitized and encoded all the data that comes from the URL parameters. This should prevent any XSS-type attacks. I think these changes will increase the security and quality of the project. If you have any further observations or recommendations, be sure to let me know. Thanks again for your help and attention. 2023-10-24, an, 13:36 光头强不会砍树了 @.> rašė:
…
After installation, log in to the backend using the default account password tester/1234 select posts [image: image] https://user-images.githubusercontent.com/113713406/277630999-f5b40b5c-fd5b-4b35-99e3-2d5305974934.png enter payload ?edit_post_id=3); [image: image] https://user-images.githubusercontent.com/113713406/277631071-2445c0a4-1cf0-4533-a7bd-bad1f5a9d050.png execution results [image: image] https://user-images.githubusercontent.com/113713406/277631314-33adb1b1-31ee-4e9d-ba6d-13fee97753cf.png Use burpsuite to capture packets. [image: image] https://user-images.githubusercontent.com/113713406/277631397-d096f43e-7b1c-419c-8e20-0fb0781a3a86.png if (isset($_GET['edit_post_id'])) { $edit_post_id = $_GET['edit_post_id']; echo ""; } The vulnerable code location is line 274 in core/tools/posts.php — Reply to this email directly, view it on GitHub <#2>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AZINVW6OYZ7U36MRA3P4BFDYA6K37AVCNFSM6AAAAAA6NPHKJCVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE2TQOJWG4YTANI . You are receiving this because you are subscribed to this thread.Message ID: @.>
-- Pagarbiai, Darius Jakaitis

Bug fixed changed to if (isset($_GET['edit_post_id'])) {
$edit_post_id = filter_input(INPUT_GET, 'edit_post_id', FILTER_SANITIZE_NUMBER_INT);
$safe_edit_post_id = htmlspecialchars($edit_post_id, ENT_QUOTES, 'UTF-8');
echo "";
}

Thank you for your guidance on project version control and quality control.
I think the ideas you have provided are very valuable and will help improve
the efficiency of the project.
2023-10-24, an 14:27, 光头强不会砍树了 @.***> rašė:

To manage this project more efficiently, we recommend creating a version
identifier and recording which bugs or vulnerabilities are fixed in each
version. This will help ensure continuous improvement and quality control
of the project, while also facilitating communication and collaboration
among team members. Here are some suggestions to improve this project: 1.
Assign a unique number to each version, such as v1.0, v2.0, etc. This will
help clearly differentiate between different versions. 2. Detail the new
features, improvements, and fixed bugs or vulnerabilities of each version
in the version release notes. This will help users understand what each
version is about. 3. Conduct code reviews during key stages of the project
to ensure code quality and follow best practices.
Thank you for spotting and reporting security holes in the code. Following
your observations, I reviewed the code and implemented the recommended
security improvements. Using the PHP functions filter_input() and
htmlspecialchars(), I sanitized and encoded all the data that comes from
the URL parameters. This should prevent any XSS-type attacks. I think these
changes will increase the security and quality of the project. If you have
any further observations or recommendations, be sure to let me know. Thanks
again for your help and attention. 2023-10-24, an, 13:36 光头强不会砍树了 @.
> rašė: … <#m_-7535338137665724930_m_-3618805998345497968_> After
installation, log in to the backend using the default account password
tester/1234 select posts [image: image]
https://user-images.githubusercontent.com/113713406/277630999-f5b40b5c-fd5b-4b35-99e3-2d5305974934.png
https://user-images.githubusercontent.com/113713406/277630999-f5b40b5c-fd5b-4b35-99e3-2d5305974934.png
enter payload ?edit_post_id=3);
[image: image]
https://user-images.githubusercontent.com/113713406/277631071-2445c0a4-1cf0-4533-a7bd-bad1f5a9d050.png
https://user-images.githubusercontent.com/113713406/277631071-2445c0a4-1cf0-4533-a7bd-bad1f5a9d050.png
execution results [image: image]
https://user-images.githubusercontent.com/113713406/277631314-33adb1b1-31ee-4e9d-ba6d-13fee97753cf.png
https://user-images.githubusercontent.com/113713406/277631314-33adb1b1-31ee-4e9d-ba6d-13fee97753cf.png
Use burpsuite to capture packets. [image: image]
https://user-images.githubusercontent.com/113713406/277631397-d096f43e-7b1c-419c-8e20-0fb0781a3a86.png
https://user-images.githubusercontent.com/113713406/277631397-d096f43e-7b1c-419c-8e20-0fb0781a3a86.png
if (isset($_GET['edit_post_id'])) { $edit_post_id = $_GET['edit_post_id'];
echo ""; } The vulnerable
code location is line 274 in core/tools/posts.php — Reply to this email
directly, view it on GitHub <#2
https://github.com/flusity/flusity-CMS/issues/2>, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZINVW6OYZ7U36MRA3P4BFDYA6K37AVCNFSM6AAAAAA6NPHKJCVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE2TQOJWG4YTANI
https://github.com/notifications/unsubscribe-auth/AZINVW6OYZ7U36MRA3P4BFDYA6K37AVCNFSM6AAAAAA6NPHKJCVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE2TQOJWG4YTANI
. You are receiving this because you are subscribed to this thread.Message
ID: @.>
-- Pagarbiai, Darius Jakaitis
—
Reply to this email directly, view it on GitHub
https://github.com/flusity/flusity-CMS/issues/2#issuecomment-1777023383,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZINVW5EJTG5XFP6A26I7VDYA6Q23AVCNFSM6AAAAAA6NPHKJCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZXGAZDGMZYGM
.
You are receiving this because you commented.Message ID:
@.***>


Offset in screeenshot

Puppeteer version:     "puppeteer": "^1.1.0",

Platform / OS version: window 7

URLs (if applicable):

Node.js version: v8.9.3

What steps will reproduce the problem?
I have a simple express app using to experiment with gathering screenshot just like this:
app.get('/window', (req, res) => {
  let browser
  let page
  console.time('scrrenshot')
  puppeteer.launch({headless: false})
    .then((b) => {
      browser = b
      console.log('browser is', b.version())
      return b.newPage()
    }).then(p => {
      console.time('scrrenshot')
      page = p
      return page.goto('localhost:8080/anzeigeApp.html?device=ZA1_TYP5&nc=BRm', {waitUntil: 'load'})
    }).then((response) => {
      return page.waitForSelector('.anzeige', {visible: true})
        .then((element) => {
          return element.boundingBox()
        }).then((bbox) => {
          page.screenshot({
            clip: bbox,
            omitBackground: false
          }).then((buffer) => {
            console.timeEnd('scrrenshot')
            res.set('Content-Type', 'image/png')
            res.write(buffer, 'binary')
            res.end(null, 'binary')
            browser.close()
          })
        })
    })
})

What is the expected result?
I would expect an image which contains the selected element only.
What happens instead?
The created image contains the selected element but it has an offset in x ynd y  direction.

Whats wrong with my doing?
Can you help me?
Thanx
Lutz

Can you try element.screenshot() and the puppeteer@next version? We recently changed the logic around element screenshots.

Sorry, but it didn´t changed anything. In between I have already updated the puppeteer version  to 1.1.1 and the change to element.screenshot didn´t changed anything.
The local chromium version from its manifest file is : 66.0.3347.0.
I will try if it is a "genuine" windows problem

I tried it on a linux machine. It seems to be a problem using puppeteer on windows 7.
Next try will be on windows 10.

Not sure.
Currently, i have the vwersion 1.5.0 of puppeteer installed and I dont have that offset in the snapshot generated.


chore: use pnpm

Let’s use pnpm as the package manager.

Funny. Somehow it all works locally. So probably pnpm is still too much experimental for this project (;


Update docs to show aud derivation from scope when there's multiple dots

Eg scope zones.12345.admin results in aud zones.12345

Reopen for develop please. This way we don't run into conflicts


Unable to start Kestrel: path base can only be configured using IApplicationBuilder.UsePathBase

My application runs fine in Visual Studio 2017 using the built-in IIS Express. However, when I deploy my code to IIS, suddenly I get the attached error.
I have found a couple of articles saying that I need to set my application URL to
"applicationUrl": "http://localhost/"
rather than
"applicationUrl": "http://localhost/{my application name}/"
But when I do that, my application tries to deploy to the webroot, and my application is stored in a folder elsewhere, so that doesn't work.
In all this, I am so confused as to what Microsoft's approach is. Why - if IIS Express works great at the press of a button - doesn't Microsoft just copy that exactly and apply it to IIS? I understand there may be more in-depth configuration a user may need to do, but that should be optional for users who need something more complex. Deploying something in IIS is almost always a complete living nightmare involving a million random undocumented settings. It is needlessly difficult and seems to default to the most random edge-case setup, rather than the most simple.
Anyway... Can someone please tell me how to make my application just deploy to IIS and work the same as it already does on other Microsoft products?
----------THIS IS THE ERROR MESSAGE --------------------
System.InvalidOperationException: 'A path base can only be configured using IApplicationBuilder.UsePathBase().'
info: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[0]
User profile is available. Using 'C:\Users\JohnDunn\AppData\Local\ASP.NET\DataProtection-Keys' as key repository and Windows DPAPI to encrypt keys at rest.
crit: Microsoft.AspNetCore.Server.Kestrel[0]
Unable to start Kestrel.
System.InvalidOperationException: A path base can only be configured using IApplicationBuilder.UsePathBase().
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.ParseAddress(String address, Boolean& https)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.AddressesStrategy.BindAsync(AddressBindContext context)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindAsync(IServerAddressesFeature addresses, KestrelServerOptions serverOptions, ILogger logger, Func2 createBinding)    at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServer.StartAsync[TContext](IHttpApplication1 application, CancellationToken cancellationToken)

This issue was moved to aspnet/Home#3495


Generic way to configure what's bug using config options for the github exporter

More generic way to configure what's bug using config options would be nice to have as not all of the users may follow standard github labeling to measure issues with Pelorus
Originally posted by @mpryc in https://github.com/konveyor/pelorus/issues/546#issuecomment-1180412452

ah.. thanks for opening a new issue :)

@mpryc ah dang I was thinking about the k8s app label and github label
https://pelorus.readthedocs.io/en/latest/Configuration/
An example may be to override the APP_LABEL for the failure exporter to indicate a production bug or issue. The APP_LABEL with the value production_issue/name may give more context than app.kubernetes.io/name In this case the Github issue would be labeled with production_issue/name=todolist
So this bug is NOT resolved.  I would have to update..
https://github.com/konveyor/pelorus/blob/master/exporters/failure/collector_github.py#L125
and create a variable for what key word needs to be in the bug label.
I suppose in jira .. you have an issue w/ type bug so it's not a problem there.
I'm inclined to push this OUT of MVR.  WDYT?  I think we can create that change later.


User Request: Debugging instructions

Is your feature request related to a problem? Please describe.
It would be nice to provide instructions on how to debug the controller vs an existing cluster.
Running this locally, in an IDE, requires some effort but is feasible.
Describe the solution you'd like
Any required files and documentation on how to run the controller -in an IDE- vs an existing cluster.
Describe alternatives you've considered
Deploying the controller to a cluster and relying on logs/metrics.
Additional context
Quick overview of running it locally:

Generate the webhook certificates; one can get these from the cluster as long as the controller has been installed there before. Or we can provide dummy ones?
Create the config.yaml file

This is similar to the one provided as a ConfigMap
Leader election and safeguards should be disabled
Provide the directory with the certificates

Set the --config argument, and the CONTROLLER_NODE_NAME environment variable when running the controller.

Would it help if we introduce a local folder with a sample config.yaml and dummy certificates?

I don't ever run the controller in an IDE, though I do know  requires some effort but is feasible. to be true. Is this something you have working?

I don't ever run the controller in an IDE, though I do know  requires some effort but is feasible. to be true. Is this something you have working?

Hey Philip. Yes, I got a working setup so happy to document it.

#515 is merged, I'm closing this one, thanks!


Main User Story -

AS A marketing agency
I WANT a codebase that follows accessibility standards
SO THAT our own site is optimized for search engines

Adding demo photo

main adjusted and still produces a functional website matching the example.


Show each config's devices in the list

Add a column in the HTML list in between the config name and the timestamp that states which devices the config uses. Omit keyboard and mouse.

Fixed in 1.0.5


temporal events triples

Produce decade by decade tables for temporal events and the triples from the same sentence. The output should be according to Jo's ranking scheme:

(decade by decade) ranked by top 10 triple count
(decade by decade) ranked by top 10 event count

Jo is not using these tables, so i am closing the issue


[BUG] vfkit: Use --device virtio-net,unixSocketPath

User-mode networking on macos uses gvforwarder running in the guest + a vsock socket to forward the networking data between the guest and the host.
vfkit has had support for --device virtio-net,unixSocketPath for a while. This allows to pass the networking data directly from the hypervisor to gvisor-tap-vsock without the need for a process running in the guest. This is similar to vpnkit which was used with hyperkit (see commit cf173bc033e7ae)

I'm not sure if this requires bundle changes or not, possibly not as gvforwarder will exit if a 'real' network interface exists.


Client minor fix

Compatible with openssl 1.1.1 (sha256)
Allows more theads when using interactive input

Minor chnages, directly merge  into main.


Run pytest in CI only in PRs that update either sources or tests

Since running pytest is pretty slow (~1h), let's mitigate our contribution on global warming by preventing to run the corresponding CI step when not needed.
I used https://github.com/dorny/paths-filter that seems quite popular.
Note that this change only targets PRs, not CI pipelines on branches. We just need green CI on PRs for merging.

📚 Documentation preview 📚: https://jaxsim--80.org.readthedocs.build//80/

I'll squash merge this PR, ignore the dirty commit names.


请问先运行完FCN.py成功,再运行FCN_plus.py报错，怎么解决？I can run the FCN.py successfully,but I have a problem in running the FCN_plus.py.Asking for help,thanks

E:\anaconda3\python.exe "G:/Document/Graduation_ project/AutoPortraitMatting-master/AutoPortraitMatting-master/FCN_plus.py"
WARNING:tensorflow:From G:/Document/Graduation_ project/AutoPortraitMatting-master/AutoPortraitMatting-master/FCN_plus.py:237: The name tf.placeholder is deprecated. Please use tf.compat.v1.placeholder instead.
setting up vgg initialized conv layers ...
WARNING:tensorflow:From G:/Document/Graduation_ project/AutoPortraitMatting-master/AutoPortraitMatting-master/FCN_plus.py:88: The name tf.variable_scope is deprecated. Please use tf.compat.v1.variable_scope instead.
WARNING:tensorflow:From G:\Document\Graduation_ project\AutoPortraitMatting-master\AutoPortraitMatting-master\TensorflowUtils_plus.py:65: calling Constant.init (from tensorflow.python.ops.init_ops) with dtype is deprecated and will be removed in a future version.
Instructions for updating:
Call initializer instance with the dtype argument instead of passing it to the constructor
WARNING:tensorflow:From G:\Document\Graduation_ project\AutoPortraitMatting-master\AutoPortraitMatting-master\TensorflowUtils_plus.py:66: The name tf.get_variable is deprecated. Please use tf.compat.v1.get_variable instead.
WARNING:tensorflow:From G:\Document\Graduation_ project\AutoPortraitMatting-master\AutoPortraitMatting-master\TensorflowUtils_plus.py:127: The name tf.nn.avg_pool is deprecated. Please use tf.nn.avg_pool2d instead.
OMP: Info #204: KMP_AFFINITY: decoding x2APIC ids.
OMP: Info #202: KMP_AFFINITY: Affinity capable, using global cpuid leaf 11 info
OMP: Info #154: KMP_AFFINITY: Initial OS proc set respected: {0,1,2,3,4,5,6,7}
OMP: Info #156: KMP_AFFINITY: 8 available OS procs
OMP: Info #157: KMP_AFFINITY: Uniform topology
OMP: Info #179: KMP_AFFINITY: 1 packages x 4 cores/pkg x 2 threads/core (4 total cores)
OMP: Info #206: KMP_AFFINITY: OS proc to physical thread map:
OMP: Info #171: KMP_AFFINITY: OS proc 0 maps to package 0 core 0 thread 0
OMP: Info #171: KMP_AFFINITY: OS proc 1 maps to package 0 core 0 thread 1
OMP: Info #171: KMP_AFFINITY: OS proc 2 maps to package 0 core 1 thread 0
OMP: Info #171: KMP_AFFINITY: OS proc 3 maps to package 0 core 1 thread 1
OMP: Info #171: KMP_AFFINITY: OS proc 4 maps to package 0 core 2 thread 0
OMP: Info #171: KMP_AFFINITY: OS proc 5 maps to package 0 core 2 thread 1
OMP: Info #171: KMP_AFFINITY: OS proc 6 maps to package 0 core 3 thread 0
OMP: Info #171: KMP_AFFINITY: OS proc 7 maps to package 0 core 3 thread 1
OMP: Info #242: KMP_AFFINITY: pid 3784 thread 0 bound to OS proc set {0}
OMP: Info #242: KMP_AFFINITY: pid 3784 thread 3 bound to OS proc set {6}
OMP: Info #242: KMP_AFFINITY: pid 3784 thread 1 bound to OS proc set {2}
OMP: Info #242: KMP_AFFINITY: pid 3784 thread 2 bound to OS proc set {4}
WARNING:tensorflow:From G:\Document\Graduation_ project\AutoPortraitMatting-master\AutoPortraitMatting-master\TensorflowUtils_plus.py:123: The name tf.nn.max_pool is deprecated. Please use tf.nn.max_pool2d instead.
WARNING:tensorflow:From G:\Document\Graduation_ project\AutoPortraitMatting-master\AutoPortraitMatting-master\TensorflowUtils_plus.py:75: The name tf.truncated_normal is deprecated. Please use tf.random.truncated_normal instead.
WARNING:tensorflow:From G:/Document/Graduation_ project/AutoPortraitMatting-master/AutoPortraitMatting-master/FCN_plus.py:100: calling dropout (from tensorflow.python.ops.nn_ops) with keep_prob is deprecated and will be removed in a future version.
Instructions for updating:
Please use rate instead of keep_prob. Rate should be set to rate = 1 - keep_prob.
WARNING:tensorflow:From G:/Document/Graduation_ project/AutoPortraitMatting-master/AutoPortraitMatting-master/FCN_plus.py:134: calling argmax (from tensorflow.python.ops.math_ops) with dimension is deprecated and will be removed in a future version.
Instructions for updating:
Use the axis argument instead
WARNING:tensorflow:From E:\anaconda3\lib\site-packages\tensorflow\python\util\dispatch.py:180: calling expand_dims (from tensorflow.python.ops.array_ops) with dim is deprecated and will be removed in a future version.
Instructions for updating:
Use the axis argument instead
WARNING:tensorflow:From G:/Document/Graduation_ project/AutoPortraitMatting-master/AutoPortraitMatting-master/FCN_plus.py:244: The name tf.Session is deprecated. Please use tf.compat.v1.Session instead.
2021-02-25 00:05:06.079382: I tensorflow/core/platform/cpu_feature_guard.cc:145] This TensorFlow binary is optimized with Intel(R) MKL-DNN to use the following CPU instructions in performance critical operations:  AVX AVX2
To enable them in non-MKL-DNN operations, rebuild TensorFlow with the appropriate compiler flags.
2021-02-25 00:05:06.081405: I tensorflow/core/common_runtime/process_util.cc:115] Creating new thread pool with default inter op setting: 8. Tune using inter_op_parallelism_threads for best performance.
WARNING:tensorflow:From G:/Document/Graduation_ project/AutoPortraitMatting-master/AutoPortraitMatting-master/FCN_plus.py:247: The name tf.train.Saver is deprecated. Please use tf.compat.v1.train.Saver instead.
WARNING:tensorflow:From E:\anaconda3\lib\site-packages\tensorflow\python\training\saver.py:1276: checkpoint_exists (from tensorflow.python.training.checkpoint_management) is deprecated and will be removed in a future version.
Instructions for updating:
Use standard file APIs to check for files with this prefix.
Traceback (most recent call last):
File "E:\anaconda3\lib\site-packages\tensorflow\python\client\session.py", line 1356, in _do_call
return fn(*args)
File "E:\anaconda3\lib\site-packages\tensorflow\python\client\session.py", line 1341, in _run_fn
options, feed_dict, fetch_list, target_list, run_metadata)
File "E:\anaconda3\lib\site-packages\tensorflow\python\client\session.py", line 1429, in _call_tf_sessionrun
run_metadata)
tensorflow.python.framework.errors_impl.InvalidArgumentError: Assign requires shapes of both tensors to match. lhs shape= [3,3,6,64] rhs shape= [3,3,3,64]
[[{{node save/Assign_13}}]]
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "E:\anaconda3\lib\site-packages\tensorflow\python\training\saver.py", line 1286, in restore
{self.saver_def.filename_tensor_name: save_path})
File "E:\anaconda3\lib\site-packages\tensorflow\python\client\session.py", line 950, in run
run_metadata_ptr)
File "E:\anaconda3\lib\site-packages\tensorflow\python\client\session.py", line 1173, in _run
feed_dict_tensor, options, run_metadata)
File "E:\anaconda3\lib\site-packages\tensorflow\python\client\session.py", line 1350, in _do_run
run_metadata)
File "E:\anaconda3\lib\site-packages\tensorflow\python\client\session.py", line 1370, in do_call
raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.InvalidArgumentError: Assign requires shapes of both tensors to match. lhs shape= [3,3,6,64] rhs shape= [3,3,3,64]
[[node save/Assign_13 (defined at G:/Document/Graduation project/AutoPortraitMatting-master/AutoPortraitMatting-master/FCN_plus.py:247) ]]
Errors may have originated from an input operation.
Input Source operations connected to node save/Assign_13:
inference/conv1_1_w (defined at G:\Document\Graduation_ project\AutoPortraitMatting-master\AutoPortraitMatting-master\TensorflowUtils_plus.py:66)
Original stack trace for 'save/Assign_13':
File "G:/Document/Graduation_ project/AutoPortraitMatting-master/AutoPortraitMatting-master/FCN_plus.py", line 296, in
pred()
File "G:/Document/Graduation_ project/AutoPortraitMatting-master/AutoPortraitMatting-master/FCN_plus.py", line 247, in pred
saver = tf.train.Saver()
File "E:\anaconda3\lib\site-packages\tensorflow\python\training\saver.py", line 825, in init
self.build()
File "E:\anaconda3\lib\site-packages\tensorflow\python\training\saver.py", line 837, in build
self._build(self._filename, build_save=True, build_restore=True)
File "E:\anaconda3\lib\site-packages\tensorflow\python\training\saver.py", line 875, in _build
build_restore=build_restore)
File "E:\anaconda3\lib\site-packages\tensorflow\python\training\saver.py", line 508, in _build_internal
restore_sequentially, reshape)
File "E:\anaconda3\lib\site-packages\tensorflow\python\training\saver.py", line 350, in _AddRestoreOps
assign_ops.append(saveable.restore(saveable_tensors, shapes))
File "E:\anaconda3\lib\site-packages\tensorflow\python\training\saving\saveable_object_util.py", line 72, in restore
self.op.get_shape().is_fully_defined())
File "E:\anaconda3\lib\site-packages\tensorflow\python\ops\state_ops.py", line 227, in assign
validate_shape=validate_shape)
File "E:\anaconda3\lib\site-packages\tensorflow\python\ops\gen_state_ops.py", line 65, in assign
use_locking=use_locking, name=name)
File "E:\anaconda3\lib\site-packages\tensorflow\python\framework\op_def_library.py", line 788, in _apply_op_helper
op_def=op_def)
File "E:\anaconda3\lib\site-packages\tensorflow\python\util\deprecation.py", line 507, in new_func
return func(*args, **kwargs)
File "E:\anaconda3\lib\site-packages\tensorflow\python\framework\ops.py", line 3616, in create_op
op_def=op_def)
File "E:\anaconda3\lib\site-packages\tensorflow\python\framework\ops.py", line 2005, in init
self._traceback = tf_stack.extract_stack()
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "G:/Document/Graduation_ project/AutoPortraitMatting-master/AutoPortraitMatting-master/FCN_plus.py", line 296, in
pred()
File "G:/Document/Graduation_ project/AutoPortraitMatting-master/AutoPortraitMatting-master/FCN_plus.py", line 249, in pred
saver.restore(sess, ckpt.model_checkpoint_path)
File "E:\anaconda3\lib\site-packages\tensorflow\python\training\saver.py", line 1322, in restore
err, "a mismatch between the current graph and the graph")
tensorflow.python.framework.errors_impl.InvalidArgumentError: Restoring from checkpoint failed. This is most likely due to a mismatch between the current graph and the graph from the checkpoint. Please ensure that you have not altered the graph expected based on the checkpoint. Original error:
Assign requires shapes of both tensors to match. lhs shape= [3,3,6,64] rhs shape= [3,3,3,64]
[[node save/Assign_13 (defined at G:/Document/Graduation_ project/AutoPortraitMatting-master/AutoPortraitMatting-master/FCN_plus.py:247) ]]
Errors may have originated from an input operation.
Input Source operations connected to node save/Assign_13:
inference/conv1_1_w (defined at G:\Document\Graduation_ project\AutoPortraitMatting-master\AutoPortraitMatting-master\TensorflowUtils_plus.py:66)
Original stack trace for 'save/Assign_13':
File "G:/Document/Graduation_ project/AutoPortraitMatting-master/AutoPortraitMatting-master/FCN_plus.py", line 296, in
pred()
File "G:/Document/Graduation_ project/AutoPortraitMatting-master/AutoPortraitMatting-master/FCN_plus.py", line 247, in pred
saver = tf.train.Saver()
File "E:\anaconda3\lib\site-packages\tensorflow\python\training\saver.py", line 825, in init
self.build()
File "E:\anaconda3\lib\site-packages\tensorflow\python\training\saver.py", line 837, in build
self._build(self._filename, build_save=True, build_restore=True)
File "E:\anaconda3\lib\site-packages\tensorflow\python\training\saver.py", line 875, in _build
build_restore=build_restore)
File "E:\anaconda3\lib\site-packages\tensorflow\python\training\saver.py", line 508, in _build_internal
restore_sequentially, reshape)
File "E:\anaconda3\lib\site-packages\tensorflow\python\training\saver.py", line 350, in _AddRestoreOps
assign_ops.append(saveable.restore(saveable_tensors, shapes))
File "E:\anaconda3\lib\site-packages\tensorflow\python\training\saving\saveable_object_util.py", line 72, in restore
self.op.get_shape().is_fully_defined())
File "E:\anaconda3\lib\site-packages\tensorflow\python\ops\state_ops.py", line 227, in assign
validate_shape=validate_shape)
File "E:\anaconda3\lib\site-packages\tensorflow\python\ops\gen_state_ops.py", line 65, in assign
use_locking=use_locking, name=name)
File "E:\anaconda3\lib\site-packages\tensorflow\python\framework\op_def_library.py", line 788, in _apply_op_helper
op_def=op_def)
File "E:\anaconda3\lib\site-packages\tensorflow\python\util\deprecation.py", line 507, in new_func
return func(*args, **kwargs)
File "E:\anaconda3\lib\site-packages\tensorflow\python\framework\ops.py", line 3616, in create_op
op_def=op_def)
File "E:\anaconda3\lib\site-packages\tensorflow\python\framework\ops.py", line 2005, in init
self._traceback = tf_stack.extract_stack()
进程已结束，退出代码 1

是tf的版本问题吗，但看起来报错是model不匹配

May I ask if you have downloaded the data set of your data folder successfully? I cannot download it through Matlab, could you share it？


Doing some cleanup of all the Warnings that litter the build

Doing some cleanup of all the Warnings that litter the build and create TODOs (and Issues) to at least silence all these many many Warnings.
I also fix some small stuff that are very obvious to fix or there are "just" some hints needed for the compiler.

The local runner is not staying connected to GitHub.  I've switched back to the ubuntu-latest running in dotnet.yml and recommend you do the same

I should follow more my own advice ... 🤔 This PR is getting way to big and issues from Rebase creeps in.
I will break this PR down in smaller chunks and open separate PRs for them.

I have now splitt out all the commits that make sense for now. I will open additional PRs when the time allows it to me.


Fixed image resize that was not keeping the aspect.

The image were distorted and in my case this resulted in having people recognized as "bananas from a tree" :)

:) You're welcome :)


(tasks or server?) torch import error for gpu task

While running a cellpose_segmentation task with server 1.0.0b1 and tasks 0.4.6, we observe this error
$ cat 4_par_20200812-CardiomyocyteDifferentiation14-Cycle1_mip_zarr_B_03_0_.err
/data/homes/fractal/fractal-demos/examples-v1/server/FRACTAL_ROOT/.fractal/fractal-tasks-core0.4.6/venv/lib/python3.8/site-packages/anndata/experimental/pytorch/_annloader.py:18: UserWarning: Сould not load pytorch.
  warnings.warn("Сould not load pytorch.")
Traceback (most recent call last):
  File "/net/nfs4/pelkmanslab-fileserver-common/data/homes/fractal/fractal-demos/examples-v1/server/FRACTAL_ROOT/.fractal/fractal-tasks-core0.4.6/venv/lib/python3.8/site-packages/fractal_tasks_core/cellpose_segmentation.py", line 35, in <module>
    from cellpose import models
  File "/data/homes/fractal/fractal-demos/examples-v1/server/FRACTAL_ROOT/.fractal/fractal-tasks-core0.4.6/venv/lib/python3.8/site-packages/cellpose/models.py", line 6, in <module>
    import torch
  File "/data/homes/fractal/fractal-demos/examples-v1/server/FRACTAL_ROOT/.fractal/fractal-tasks-core0.4.6/venv/lib/python3.8/site-packages/torch/__init__.py", line 202, in <module>
    from torch._C import *  # noqa: F403
ImportError: libtorch_cuda.so: failed to map segment from shared object

EDIT
Note that running the appropriate python interpreter (i.e. the one defined in the venv in FRACTAL_ROOT), the situation is as follows
Python 3.8.13 (default, Oct 21 2022, 23:50:54)
[GCC 11.2.0] :: Anaconda, Inc. on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import torch
>>> torch.__version__
'1.12.1+cu102'

most likely task

Possibly related to wrong configuration of SLURM, since I was assigning a very small memory requirement (1G) -- see https://github.com/pytorch/pytorch/issues/16558.
I will try to reproduce with larger memory requirement.

Fixed by assigning larger memory, notably with this script:
#!/bin/sh
#SBATCH --output=/net/nfs4/pelkmanslab-fileserver-common/data/homes/fractal/fractal-demos/examples-v1/server/artifacts/workflow_000001_job_000001/slurmpy.stdout.%j.log
#SBATCH --partition=gpu
#SBATCH --mem=61g
#SBATCH --nodes=1
#SBATCH --job-name Cellpose_Segmentation
export CFUT_DIR=/net/nfs4/pelkmanslab-fileserver-common/data/homes/fractal/fractal-demos/examples-v1/server/artifacts/workflow_000001_job_000001
srun /data/homes/fractal/.conda/envs/fractal-server-v1/bin/python -m cfut.remote nt5Ym9PSu6NfeMp5CyT1Mw3wQG4awueC


Escape key in the accelerator makes some systems fail

Describe the bug
Escape key in the accelerator makes some systems fail

Will be fixed with #110


Yarn 3: @mui/core tried to access @mui/system, but it isn't declared in its dependencies

While using Yarn 3.1 and PnP I get this error. @mui/core tried to access @mui/system, but it isn't declared in its dependencies. This does not allow our app to build.
./.yarn/__virtual__/@mui-core-virtual-2bf19239de/0/cache/<EMAIL_ADDRESS>Module not found: @mui/core tried to access @mui/system, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.`

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
Error is shown
Expected Behavior 🤔
Error not shown, dependencies listed as expected
Context 🔦
Use material UI with Yarn 3
Your Environment 🌎

`npx @mui/envinfo`
  System:
    OS: Windows 10 10.0.19043
  Binaries:
    Node: 16.13.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 3.1.0 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 8.1.3 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Spartan (44.19041.1266.0), Chromium (95.0.1020.44)

Duplicate of https://github.com/mui-org/material-ui/issues/29341


local foopath disabled

To get rid of the error that "/home/scp1/bin/foopath" wouldn't exist.

Closable, this was already fixed.


Renaming master to main

The default branch was renamed from master to main so updating the CI files to point to the new branch.

Codecov Report

Merging #59 (9dbc287) into main (3d53242) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #59   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         1    -1
  Lines          184       181    -3
=========================================
- Hits           184       181    -3

Impacted Files
Coverage Δ

sas7bdat_converter/__init__.py

Continue to review full report at Codecov.

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

Codecov Report

Merging #59 (9dbc287) into main (3d53242) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #59   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         1    -1
  Lines          184       181    -3
=========================================
- Hits           184       181    -3

Impacted Files
Coverage Δ

sas7bdat_converter/__init__.py

Continue to review full report at Codecov.

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


NEXUS dataset, avoid gene in charset if is not included in the dataset

due to missing reading frame for example.

fixed in 75115c8a695d7668ae7a03bfb2b1c54ab7bfa2a8


Terraforming multiple AWS regions

Hello,
I work on several AWS regions.
When I want to terraform actual stacks with a non-default account, terraforming fails.
It seem to be since region is taken from default  account.
Regards,

I tried with multiple IAM users and multiple regions, it worked fine.
Terraforming v0.15.0
[default]
aws_access_key_id = ...
aws_secret_access_key = ...

[dtan4]
aws_access_key_id = ...
aws_secret_access_key = ...

# with default user
terraforming kmsa --region us-west-1
terraforming kmsa --region ap-northeast-1

# with non-default user
terraforming kmsa --profile dtan4 --region us-west-1
terraforming kmsa --profile dtan4 --region ap-northeast-1

It seems that we have nothing to do about this now.
Could you show me the error message?


Demo scripts seperate and fix navigation

Description

Seperating demos script to certain page not use combined one.
Correcting docs homepage <title> from "Index" to jsdoc config's "conf.meta.title".
make cdn page as jsdoc static file named "cdn-iframe.html" and generate cdn.html which contains a iframe reference to "cdn-iframe.html" .
combined jsdoc generated api pages to API,flatten the API navigation.
include to all chart type demo script to kitchen-sink page.

Motivation and Context

fix issue https://github.com/eventbrite/britecharts/issues/270
How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Merged in #273 with some other details.
Thanks a lot for the work!!
I wanted to remove the 'CDN' link on the header, as I added some references on the docs. I couldn't figure out how, could you do it for me?
We are preparing a rework of the home page, more info and designs soon!

@miglesiasEB I'd remove the cdn link , since docs generateing logic mainly in publish.js so I modify it, you can check these changes https://github.com/eventbrite/britecharts/pull/272/commits/127c373571048003e94e9eb4808e1a0e015ecb8f ,this will help you to modification the main navigation.


Mass search replace 'github.com/bytecodealliance/wasm-tools-go' -> 'g…

…o.bytecodealliance.org'

I think it might be worth doing a first pass of replacing https://github.com/bytecodealliance/wasm-tools-go with https://github.com/bytecodealliance/go-modules before finding and replacing github.com/bytecodealliance/wasm-tools-go with go.bytecodealliance.org.

Do we want to replace all the https://github.com/bytecodealliance/wasm-tools-go in CHANGELOG.md too?

Do we want to replace all the https://github.com/bytecodealliance/wasm-tools-go in CHANGELOG.md too?

Yes, this will pick up tags, releases, issues, PRs.


fix(MockBuilder): better detection of provided dependencies #3635

closes #3635

v14.2.3 has been released and contains a fix for the issue. Feel free to reopen the issue or to submit a new one if you meet any problems.


I2C for LCD not working after phoniebox script installer runs and reboots

System
Rasberry Pi 3A+
Raspbian Buster Lite
Bug
I2C for LCD not working after phoniebox script installer and reboot
What I did
On a fresh rasbian buster the i2c can be enabled and the display is detected by 'sudo i2cdetect -y 1' with ID 27
After reboot, display still found with 'sudo i2cdetect -y 1'
I can write text on the display with python code too.
No I am installing phoniebox with the script installer
After script is finished, I reboot the system.
What happened
After system is rebooted, 'sudo i2cdetect -y 1' can't detect the display again.  'sudo i2cdetect -y 1' runs slow
If I disable and enable I2C again, 'sudo i2cdetect -y 1' can detect the display again.
I tried this many times, always the same problem occures.
Can someone else confirm this bug?
Thank you and regards
Dominik
And sorry for the bad english. :-)

@DSteg you may want to check out issue #656

Thank you very much.
Yes, it is the same issue.
I have not recognized it myself, because I have the buttons still not connected.
If the GPIO3 (PIN5,SCL) is set to high, i2c is not working any longer.
So it is not possible to use the GPIO3 for shutdown + wake-up and any device with i2c at the same time.
In my opinion, this is a design failure of the Raspberry Pi constructors to set two functions on the same GPIO.
It would be better if the wake up function would be available on a free GPIO without a special function.
I have now set the shutdown GPIO to GPIO17 PIN11 and will try to create a switch function with a relay to use GPIO3 to wake up and GPIO 17 to shutdown.
Thank you again for the hint on issue #656


Update Post “termite-inspection-who-to-call-on-the-gold-coast”

Automatically generated by Netlify CMS

👷 Deploy Preview for chic-shortbread-66a66b processing.

Name
Link

🔨 Latest commit
643694d7bfb34d4bdd0fad4f136ba0f0c2989dad

🔍 Latest deploy log
https://app.netlify.com/sites/chic-shortbread-66a66b/deploys/654abdb18fa80300083c0317


Support for Chinese(simplified) language

This merge request includes:

Chinese(simplified) translation file for the zod error messages.
Chinese(simplified) section has been appended to the examples page.

Thank you for your contribution.
I will release this immediately.


error  in tf2.1

in tensorflow_binding/warprnnt_tensorflow/init.py, there is a line @ops.RegisterShape("WarpRNNT")
when using tf 2.1.0, there is an error
'tensorflow.python.framework.ops' has no attribute 'RegisterShape'

I got the same error with tf2.1

Try to remove python 'RegisterShape', then add a SetShapeFn after warprnnt_op.cc:13.

Hi,
I am getting the same issue. Did this work? Can anyone explain what changes are need to be done?

Hello bhaswa!
I was having the same issue and i found this solution:
https://github.com/noahchalifour/warp-transducer/commit/45a4a10ae9af14b7d9b25bd558be95f43ee1ba9a