Search  listeners on 0.2.0

Hello,
from changelog of 0.2.0 version
Added support for Search and Refresh listeners

but when I'm looking on the implementation we throw UnimplementedError
  @override
  void initState() {
    _scrollController = widget.scrollController ?? ScrollController();
    if (widget.listeners != null) {
      for (var listener in widget.listeners) {
        if (listener is PaginateRefreshedChangeListener) {
          listener.addListener(() {
            if (listener.refreshed) {
              refresh();
            }
          });
        } else if (listener is PaginateSearchChangeListener) {
          listener.addListener(() {
            throw UnimplementedError();
          });
        }
      }
    }

so should we implement SearchChangeListener ? if yes can you please provide sample
Thanks

Hey @azazadev , I apologize for that mistake. It is now fixed in v0.2.1 and you can find the usage in this pr #34

Many Thanks !!! will try to test it today


Flickering After closing window

Describe the bug
Basically whenever I close a window that isn't pinned to the taskbar, all my windows (on the taskbar) "move around back and forth quickly" for lack of a better word
Expected behavior
Not flicker and just align normally I suppose
Desktop (please complete the following information):
Windows 10 Home

Same problem here.

To be able to focus on major/current bugs I had to close all issues. The issues section has gotten very messy to a point that I couldn't follow it anymore. Most issues are duplicates, very old or are already fixed/solved. Feel free to reopen this issue if you still have this issue on the latest version of TaskbarX to get my attention. All feature requests have been put in a list here: 💡| Feature requests #870
I hope you understand ❤


[Enhancement] Release shield for stable releases only

Description
Currently, the release shield for docker hub shows the development releases. As a product owner, I want to promote stable releases and request to adjust the shield to show only the newest stable release versions (ex. v1.0.0).
Criteria

release shield shows only stable version numbers (starting with vxxx and not ending in pre-release tags) according to semver

Additional information

https://semver.org/

non issue -> already implemented


Confusing Tutorial Section

I'm brand new to React-Router and have been using React for about a week now. I tried to go through the tutorial and got hung up when I couldn't figure out why my Message view was not rendering. I didn't even realize that the router had nested UI rendering.
Re-reading several times I noticed a subtle hint that these UI's might nest like the App did after reading "First we'll make a new Message component and then we'll add the route under inbox so that the UI will nest.".
Searching on Google pulled up this SO post that confirmed that and shed some light that I needed to use RouterHandler.
It would be nice if something was added to let you know that the UI is nested and needs that RouterHandler to work.
I just wanted to let you know since I realize it can be tough to catch when you're so deep in the code.

I wonder why @ryanflorence or @mjackson don't add a link to http://rackt.github.io/react-router/ in the project description. That's the docs for the current version on NPM. It mentions RouteHandler many times.
The docs in the master are referring to 1.0 which doesn't have RouteHandler. That's why you didn't see it.

Ah that makes sense. Also I read the the master readme first and then started reading the docs linked above. However I didn't fully read through the docs before writing a hello world app. I realize that's my fault, but if a user is going through step by step, adding in RouterHandler to Inbox is skipped. Not a huge deal but perhaps it should be fixed to have the best onboarding experience.

Adding more UI

Alright, now we're ready to nest the inbox messages inside the inbox UI. First we'll make a new Message component and then we'll add the route under inbox so that the UI will nest.

var Message = React.createClass({
  render () {
    return
Message
;
  }
});

var routes = (
  <Route handler={App}>
    <Route path="about" handler={About}/>
    <Route path="inbox" handler={Inbox}>
      <Route path="messages/:id" handler={Message}/>
    </Route>
  </Route>
);

Now visits to urls like inbox/messages/Jkei3c32 will match the new route and nest the UI branch of App -> Inbox -> Message.

However it only matches the router and doesn't update the UI. It only shows the Inbox heading unless you change Inbox to:
var Inbox = React.createClass({
  render: function () {
    return

Inbox

      <RouteHandler/>

  }
});

I just added a link to http://rackt.github.io/react-router/ to the project description on GitHub.
@AdamBrodzinski Anything more we can do to help people in the future not be confused?

Looks good to me.
In general I thought the guide was a really great start to get it going.
The first guide/tutorial still assumes that you change/use <RouteHandler/> for the nested UI in the inbox  template but I think if you read the guide all the way through before doing it than it's pretty apparent.

I'm going through the docs today and I had the same question as @AdamBrodzinski. I assumed that I had to add <RouteHandler/> to the parent UI to render the child UI, but it never actually showed that in the docs (except at the root level for the main <App /> route handler), which left me questioning whether my assumption was correct or if I was missing something.
I think it would make it clearer if you take @AdamBrodzinski's suggestion in his comment above (https://github.com/rackt/react-router/issues/1440#issuecomment-116361984) and show the updated parent UI that clearly shows that you have to embed a <RouteHandler/> to the UI for the child to render.
After confirming that that is how it works, reading the description of that makes more sense. Seeing an example of it would have been much more clear for me, however.

this should be resolved now. also the new awesome docs are coming soon


Multiple calls to setDiff when triggering refresh

When triggering refresh manually four times DoubleTreeWidget::setDiff will be called.

Drawio diagram
GittyupRefresh.drawio

GittyupRefresh.txt
@exactly-one-kas I updated the image. We have to get rid of 1-4 somehow or do you think we have any issues with it?

Couldn't we just check if the diff given to setDiff() is the same as the current one and do nothing in that case?

I can try. what happens then. I would like to fix the root cause, it makes it then also much clearer

The problem is that a few times the diff is invalid and then valid again, so it is not easy to find out when to update and when not. Lucily we are using refresh quite often in the unittests. Therefore it will be tested quite well :) (Currently in my branch a few tests are failing, I have to check)


enable-remote-node-identity applies to KNP / k8s (CNI neutral) NetworkPolicy

Bug report

In Cilium 1.7, the enable-remote-node-identity option was created, and, when true, this requires that remote-node connectivity be explicitly allowed in NetworkPolicy.
Somewhat problematically, the CNI neutral k8s NetworkPolicy cannot specify remote-node as it is a CiliumNetworkPolicy-specific entity. Reading the k8s NetworkPolicy docs, it sounds like this behavior is unsupported with plain, CNI neutral NetworkPolicy as node identities are currently unsupported.
Maybe I'm misreading the k8s docs, but as such, I was somewhat surprised that enable-remote-node-identity actually affected NetworkPolicy and not just CiliumNetworkPolicy, particularly given that remote-node and node identities in general can't be specified there.
I'd thought that enable-remote-node-identity would have no impact on KNP and that the KNP -> CNP translation code would handle adding fromEntities: - remote-node automatically, but it didn't.
Specific Details
When I set enable-remote-node-identity to true, some of my pods, primarily those that used hostNetwork: true, started dropping connections as our NetworkPolicy only has podSelectors and so ended up denying remote-node.
Some specific examples include KIAM agents accessing the KIAM server via hostNetwork and metrics-server and KEDA receiving requests from the host's kupe-apiserver to serve metrics in the appropriate APIs. Or DNS as the example below.
I was only able to resolve this using CNP, despite starting out with only KNPs.
This is very related to https://github.com/kubernetes/kops/issues/10836, as the recently released kOps 1.19 seems to accidentally enable this option by default (and therefore accidentally created a breaking change during upgrade from kOps 1.18 to kOps 1.19), but I was still surprised it impacted KNP, not solely CNP
I'm not 100% sure that this is a "bug"/incorrect behavior, as it's not entirely clear to me what the behavior should be based on the k8s spec. This case seems like it might be undefined -- perhaps the appropriate resolution to this is better docs on the spec for k8s and Cilium. In any case, if this is incorrect behavior, it's a "spec interpretation issue" as opposed to an actual code bug per se.
General Information

Cilium version (run cilium version)

This affects all versions since introduction of enable-remote-node-identity, so 1.7+

Kernel version (run uname -a)

Amazon Linux 2, so kernel version 4.14

Orchestration system version in use (e.g. kubectl version, Mesos, ...)

k8s 1.19.7
kOps 1.19.0

Link to relevant artifacts (policies, deployments scripts, ...)

see steps to reproduce below

Generate and upload a system zip:

curl -sLO https://git.io/cilium-sysdump-latest.zip && python cilium-sysdump-latest.zip

N/A as this is a spec issue, not a bug in some code

How to reproduce the issue
Per https://github.com/kubernetes/kops/issues/10836, the simplest reproduction is:

Install Cilium with enable-remote-node-identity set to true (e.g. use kOps 1.19.0 with kops create-cluster --networking cilium)
In a cluster with kube-dns in the kube-system namespace, add a simple KNP:

# Allow traffic from other namespaces to kube-dns (CoreDNS)
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: kube-dns
  namespace: kube-system
spec:
  podSelector:
    matchLabels:
      k8s-app: kube-dns
  ingress:
  - from:
    - namespaceSelector: {}

Send some request from a host (e.g. hostNetwork: true pod or SSH'ed into a host) to kube-dns, e.g. curl kube-dns.kube-system.cluster.service.local or an nslookup to something. This request will fail and timeout

This is just a simple example using a service that already exists in a default cluster; any other service works too. I'm not totally sure exactly how host DNS works, this was just one service we had issues with.

This issue can then be resolved by replacing with an equivalent CNP that also includes remote-node (or, in this case, cluster, which includes remote-node):

apiVersion: "cilium.io/v2"
kind: CiliumNetworkPolicy
metadata:
  name: kube-dns-from-host
  namespace: kube-system
spec:
  endpointSelector:
    matchLabels:
      k8s-app: kube-dns
  ingress:
    - fromEntities:
      - cluster

A more complex reproduction would be to:

Deploy KIAM, metrics-server, or KEDA, or another service that uses hostNetwork: true, as mentioned above.
Then one can add a different, simple KNP:

---
# Default network policy to deny all traffic from outside the namespace
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: default
  namespace: test-namespace-where-service-was-deployed
spec:
  podSelector:
    matchLabels:
  ingress:
  - from:
    - podSelector: {}

KIAM agents or metrics-server requests or KEDA requests etc will fail as they are made from the host, not from a pod.

This issue can then be resolved by adding a CNP that includes remote-node:

apiVersion: "cilium.io/v2"
kind: CiliumNetworkPolicy
metadata:
  name: from-hosts
  namespace: test-namespace-where-service-was-deployed
spec:
  endpointSelector:
    matchLabels:
      app: kiam-server
  ingress:
    - fromEntities:
      - host
      - remote-node

As you can see from these examples, although I started with just KNPs, I required CNPs to resolve the denials caused by enable-remote-node-identity. Other than specifying the IP addresses or CIDR of the cluster's nodes, I'm not sure there's a simple way of achieving this in KNP as it does not currently have support for node identities. I'm also not sure that other CNIs behave the same way with respect to remote nodes and KNP.
Can try to make a PR
If this behavior is indeed incorrect, I can try to make a PR to change the KNP -> CNP translation. I believe the code for this is located in this block, though may need a bit more direction on which cases would be appropriate to add fromEntities: - remote-node, or if it should just be added to all to be backward-compatible with the previous behavior.

Hi @agilgur5 , firstly thanks for the great writeup. This is indeed a known limitation with respect to the enable-remote-node-identity option. For a bit more context, there's another variation on this issue where I had posted some thoughts, those notes might also help you to reason about Cilium's behaviour here and maybe see about next steps: https://github.com/cilium/cilium/issues/12277
I'm not sure I fully understand the proposal for KNP -> CNP translation. As far as I can tell, KNP is ambiguous on the point of how node traffic should be handled by the policy. The danger here is that if we are overly broad in our interpretation, we may end up opening up more traffic than the user really intends, particularly if you may have one view on how the policy should react and other users have a different view. The "nice" thing today about the fromEntities: remote-node approach in CNP is that the semantics are well-defined, and if the user wants pod->node traffic to be allowed, then it's very explicit in the policy so Cilium is definitely doing what they intend.  I think that what you're suggesting is to automatically inject an "allow to host/remote-node" rule based on certain KNP rule inputs, particularly podSelector. The thing is, if the pod selected by that pod selector has hostNetwork: true, then does that mean that any application directly running on that node should be accessible, even if not otherwise explicitly allowed by the policy? That's the behaviour it will have. Doing so from a podSelector: {} rule does not make this very obvious to users, and the nature of security issues is that they lurk in areas of implicit behaviour. Furthermore, I don't think we should encourage podSelector: {} rules either, as they are overly broad and not in line with the "least privilege" principle.
An alternative solution to the problem is to resolve #12277 and say that if KNP users want to allow traffic towards remote nodes, they must specify node IPs explicitly. I'm not the biggest fan of this approach either because I don't think that IP addressing really has a place in Kubernetes policies given that there are better higher-level constructs (and CNP provides these!), but that approach would at least provide a path for users who are not willing to use CNP, and in a way that would be a bit more explicit to the policy writer.

Thanks for the detailed response @joestringer . My apologies for not getting back to you in a more timely fashion; we ended up working around it by just completely porting over to CNP usage and then I got pulled into lots of things and left this at the wayside.

As far as I can tell, KNP is ambiguous on the point of how node traffic should be handled by the policy.

Yea, KNP still doesn't seem to support node traffic outside of using CIDRs. In my opening comment, I also thought that this case was likely "undefined" in the KNP spec

I'm not sure I fully understand the proposal for KNP -> CNP translation

Given that, my proposal was either to add more docs around this edge-case when using KNPs, or, given the ambiguity, to always allow remote-node traffic for KNPs as it can't be specified. Basically just for KNPs to be backward-compatible prior to the introduction of enable-remote-node-identity.
Now that this is like a year out though, changing that setting would likely be even more breaking, so that's probably not a viable option. Would have to check if any docs would still be useful a year out.

The danger here is that if we are overly broad in our interpretation, we may end up opening up more traffic than the user really intends

Totally agreed, one of the reasons I'm a Cilium stan is because of lots of great security, least-privilege, and explicitness decisions and implementations like this!
Unfortunately KNPs and other implementations tend to lag behind, which can create some compatibility issues due to non-existent features such as this.

I think that what you're suggesting is to automatically inject an "allow to host/remote-node" rule based on certain KNP rule inputs

I actually didn't mean something as complex as that, and meant the very simple backward-compatibility default I mentioned above 😅  (but I'll take that as a compliment haha).
It would be super cool if there were a way to automatically figure that out, though. I tried wrapping my head around it for a bit after you first replied and couldn't come up with a good strategy that wouldn't be confusing, as you mentioned

I'm not the biggest fan of this approach either because I don't think that IP addressing really has a place in Kubernetes policies given that there are better higher-level constructs (and CNP provides these!), but that approach would at least provide a path for users who are not willing to use CNP, and in a way that would be a bit more explicit to the policy writer.

Also agreed. At least in my case, we probably couldn't use that solution as we don't generally rely on sticky IPs. But may be useful to others as a stop-gap 🤷


Error when running ./syn_yosys.sh

Observed Behavior

Hello,
I am new to Ibex and try to experiment with it.
I have an issue when running the ./syn_yosys.sh script.
More precisely, I have such error:
Executing Verilog-2005 frontend: syn_out/ibex_22_09_2021_14_37_02/generated/ibex_top_tracing.v syn_out/ibex_22_09_2021_14_37_02/generated/ibex_top_tracing.v:99: ERROR: FATAL: Fatal error: RVFI needs to be defined globally.. Failed to synthesize RTL with Yosys
I did define the syn_setup.sh script with the Nangate45 lib.
Do you have an idea of why I get such error ?
Thanks for your help.
My Environment
Operating system:

I am working on Ubuntu 20.04.3 amd64.
Version of the Ibex source code:

I am using the ibex source code version ac8934459b028220ce9fd20683bb018244b59756.

@GregAC: I think you know most about our synthesis flow?

Hello,
Do you have some updates for my problem ?
Thanks a lot!

Can you let us know what versions of yosys and sv2v you are using? The script works locally for me using yosys v0.9 and sv2v v0.0.5-21-g6d907e0

Here are the versions I use:

Yosys 0.9+4081 (git sha1 UNKNOWN, gcc 8.4.1 -O2 -fexceptions -fstack-protector-strong -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fPIC -Os)
sv2v v0.0.8-42-g814f965

I tried on another machine on Rocky Linux 8.4. I have the same error.
Here are my steps:

git clone https://github.com/lowRISC/ibex.
I installed the requirements in https://github.com/lowRISC/ibex/tree/master/syn.
I downloaded the nangate45.lib (https://github.com/The-OpenROAD-Project/OpenROAD-flow-scripts/tree/master/flow/platforms/nangate45/lib)
I uncommented and modified the two last lines of the syn_setup.sh file such as:

export LR_SYNTH_CELL_LIBRARY_PATH=/test/x/Nangate45/NangateOpenCellLibrary_typical.lib
export LR_SYNTH_CELL_LIBRARY_NAME=nangate

I go to the the syn directory and run syn_yosys.sh

here is the full output:
******  o p e n   t o   t h e   c o r e  *******

       +---------------------------------+
       |  _   _   ___   ___  _   _  ___  |
       | | | | | / _ \ / __|| | | |/ __| |
       | | |_| || (_) |\__ \| |_| |\__ \ |
       |  \__, | \___/ |___/ \__, ||___/ |
       |   __/ |              __/ |      |
       |  |___/              |___/       |
       +---------------------------------+

=================== Flow Vars ===================
Path to cell library: /XX/Nangate45/NangateOpenCellLibrary_typical.lib
top module: ibex_top (default)
Output directory for synthesis: syn_out/ibex_27_09_2021_16_54_01
Pre-mapping netlist out: ./syn_out/ibex_27_09_2021_16_54_01/generated/ibex_top.pre_map.v (default)
netlist out: ./syn_out/ibex_27_09_2021_16_54_01/generated/ibex_top_netlist.v (default)
Synth config file: ibex_top_lr_synth_conf.tcl (default)
Report output directory: ./syn_out/ibex_27_09_2021_16_54_01/reports (default)
flatten: Enabled
timing run: Enabled
Enable branch target ALU in Ibex: Disabled
Enable writeback stage in Ibex: Disabled
Bitmanip extenion setting for Ibex (see ibex_pkg::rv32b_e for permitted values. Enum names are not supported in Yosys.): 0 (default)
Multiplier extension setting for Ibex (see ibex_pkg::rv32m_e for permitted values. Enum names are not supported in Yosys.): 2 (default)
Register file implementation selection for Ibex (see ibex_pkg::regfile_e for permitted values. Enum names are not supported in Yosys.): 2 (default)
Name of cell library: nangate
Input SDC file: ibex_top.nangate.sdc (default)
Input SDC file for ABC: ibex_top_abc.nangate.sdc (default)
Output SDC file: ./syn_out/ibex_27_09_2021_16_54_01/generated/ibex_top.nangate.out.sdc (default)
STA netlist out: ./syn_out/ibex_27_09_2021_16_54_01/generated/ibex_top_netlist.sta.v (default)
STA paths reported per group: 1000 (default)
STA paths reported in overall report: 1000 (default)
clock period: 4000.0 ps
=================================================

 /----------------------------------------------------------------------------\
 |                                                                            |
 |  yosys -- Yosys Open SYnthesis Suite                                       |
 |                                                                            |
 |  Copyright (C) 2012 - 2020  Claire Wolf<EMAIL_ADDRESS>        |
 |                                                                            |
 |  Permission to use, copy, modify, and/or distribute this software for any  |
 |  purpose with or without fee is hereby granted, provided that the above    |
 |  copyright notice and this permission notice appear in all copies.         |
 |                                                                            |
 |  THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES  |
 |  WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF          |
 |  MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR   |
 |  ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES    |
 |  WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN     |
 |  ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF   |
 |  OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.            |
 |                                                                            |
 \----------------------------------------------------------------------------/

 Yosys 0.9+4081 (git sha1 UNKNOWN, gcc 8.4.1 -O2 -fexceptions -fstack-protector-strong -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fPIC -Os)

1. Executing Liberty frontend.
Imported 135 cell types from liberty file.

2. Executing Verilog-2005 frontend: ./rtl/prim_clock_gating.v
Parsing SystemVerilog input from `./rtl/prim_clock_gating.v' to AST representation.
Generating RTLIL representation for module `\prim_clock_gating'.
Successfully finished Verilog frontend.

3. Executing Verilog-2005 frontend: syn_out/ibex_27_09_2021_16_54_01/generated/ibex_alu.v
Parsing SystemVerilog input from `syn_out/ibex_27_09_2021_16_54_01/generated/ibex_alu.v' to AST representation.
Generating RTLIL representation for module `\ibex_alu'.
Successfully finished Verilog frontend.

4. Executing Verilog-2005 frontend: syn_out/ibex_27_09_2021_16_54_01/generated/ibex_branch_predict.v
Parsing SystemVerilog input from `syn_out/ibex_27_09_2021_16_54_01/generated/ibex_branch_predict.v' to AST representation.
Generating RTLIL representation for module `\ibex_branch_predict'.
Successfully finished Verilog frontend.

5. Executing Verilog-2005 frontend: syn_out/ibex_27_09_2021_16_54_01/generated/ibex_compressed_decoder.v
Parsing SystemVerilog input from `syn_out/ibex_27_09_2021_16_54_01/generated/ibex_compressed_decoder.v' to AST representation.
Generating RTLIL representation for module `\ibex_compressed_decoder'.
Successfully finished Verilog frontend.

6. Executing Verilog-2005 frontend: syn_out/ibex_27_09_2021_16_54_01/generated/ibex_controller.v
Parsing SystemVerilog input from `syn_out/ibex_27_09_2021_16_54_01/generated/ibex_controller.v' to AST representation.
Generating RTLIL representation for module `\ibex_controller'.
Successfully finished Verilog frontend.

7. Executing Verilog-2005 frontend: syn_out/ibex_27_09_2021_16_54_01/generated/ibex_core.v
Parsing SystemVerilog input from `syn_out/ibex_27_09_2021_16_54_01/generated/ibex_core.v' to AST representation.
Generating RTLIL representation for module `\ibex_core'.
Successfully finished Verilog frontend.

8. Executing Verilog-2005 frontend: syn_out/ibex_27_09_2021_16_54_01/generated/ibex_counter.v
Parsing SystemVerilog input from `syn_out/ibex_27_09_2021_16_54_01/generated/ibex_counter.v' to AST representation.
Generating RTLIL representation for module `\ibex_counter'.
Successfully finished Verilog frontend.

9. Executing Verilog-2005 frontend: syn_out/ibex_27_09_2021_16_54_01/generated/ibex_cs_registers.v
Parsing SystemVerilog input from `syn_out/ibex_27_09_2021_16_54_01/generated/ibex_cs_registers.v' to AST representation.
Generating RTLIL representation for module `\ibex_cs_registers'.
Warning: Replacing memory \pmp_addr_rdata with list of registers. See syn_out/ibex_27_09_2021_16_54_01/generated/ibex_cs_registers.v:852
Warning: Replacing memory \mhpmevent with list of registers. See syn_out/ibex_27_09_2021_16_54_01/generated/ibex_cs_registers.v:897
Successfully finished Verilog frontend.

10. Executing Verilog-2005 frontend: syn_out/ibex_27_09_2021_16_54_01/generated/ibex_csr.v
Parsing SystemVerilog input from `syn_out/ibex_27_09_2021_16_54_01/generated/ibex_csr.v' to AST representation.
Generating RTLIL representation for module `\ibex_csr'.
Successfully finished Verilog frontend.

11. Executing Verilog-2005 frontend: syn_out/ibex_27_09_2021_16_54_01/generated/ibex_decoder.v
Parsing SystemVerilog input from `syn_out/ibex_27_09_2021_16_54_01/generated/ibex_decoder.v' to AST representation.
Generating RTLIL representation for module `\ibex_decoder'.
Successfully finished Verilog frontend.

12. Executing Verilog-2005 frontend: syn_out/ibex_27_09_2021_16_54_01/generated/ibex_dummy_instr.v
Parsing SystemVerilog input from `syn_out/ibex_27_09_2021_16_54_01/generated/ibex_dummy_instr.v' to AST representation.
Generating RTLIL representation for module `\ibex_dummy_instr'.
Successfully finished Verilog frontend.

13. Executing Verilog-2005 frontend: syn_out/ibex_27_09_2021_16_54_01/generated/ibex_ex_block.v
Parsing SystemVerilog input from `syn_out/ibex_27_09_2021_16_54_01/generated/ibex_ex_block.v' to AST representation.
Generating RTLIL representation for module `\ibex_ex_block'.
Successfully finished Verilog frontend.

14. Executing Verilog-2005 frontend: syn_out/ibex_27_09_2021_16_54_01/generated/ibex_fetch_fifo.v
Parsing SystemVerilog input from `syn_out/ibex_27_09_2021_16_54_01/generated/ibex_fetch_fifo.v' to AST representation.
Generating RTLIL representation for module `\ibex_fetch_fifo'.
Successfully finished Verilog frontend.

15. Executing Verilog-2005 frontend: syn_out/ibex_27_09_2021_16_54_01/generated/ibex_icache.v
Parsing SystemVerilog input from `syn_out/ibex_27_09_2021_16_54_01/generated/ibex_icache.v' to AST representation.
Generating RTLIL representation for module `\ibex_icache'.
Warning: Replacing memory \fill_data_q with list of registers. See syn_out/ibex_27_09_2021_16_54_01/generated/ibex_icache.v:630
Warning: Replacing memory \fill_way_q with list of registers. See syn_out/ibex_27_09_2021_16_54_01/generated/ibex_icache.v:608
Warning: Replacing memory \fill_addr_q with list of registers. See syn_out/ibex_27_09_2021_16_54_01/generated/ibex_icache.v:596
Successfully finished Verilog frontend.

16. Executing Verilog-2005 frontend: syn_out/ibex_27_09_2021_16_54_01/generated/ibex_id_stage.v
Parsing SystemVerilog input from `syn_out/ibex_27_09_2021_16_54_01/generated/ibex_id_stage.v' to AST representation.
Generating RTLIL representation for module `\ibex_id_stage'.
Successfully finished Verilog frontend.

17. Executing Verilog-2005 frontend: syn_out/ibex_27_09_2021_16_54_01/generated/ibex_if_stage.v
Parsing SystemVerilog input from `syn_out/ibex_27_09_2021_16_54_01/generated/ibex_if_stage.v' to AST representation.
Generating RTLIL representation for module `\ibex_if_stage'.
Successfully finished Verilog frontend.

18. Executing Verilog-2005 frontend: syn_out/ibex_27_09_2021_16_54_01/generated/ibex_load_store_unit.v
Parsing SystemVerilog input from `syn_out/ibex_27_09_2021_16_54_01/generated/ibex_load_store_unit.v' to AST representation.
Generating RTLIL representation for module `\ibex_load_store_unit'.
Successfully finished Verilog frontend.

19. Executing Verilog-2005 frontend: syn_out/ibex_27_09_2021_16_54_01/generated/ibex_lockstep.v
Parsing SystemVerilog input from `syn_out/ibex_27_09_2021_16_54_01/generated/ibex_lockstep.v' to AST representation.
Generating RTLIL representation for module `\ibex_lockstep'.
Warning: Replacing memory \shadow_data_rdata_q with list of registers. See syn_out/ibex_27_09_2021_16_54_01/generated/ibex_lockstep.v:227
Warning: Replacing memory \shadow_tag_rdata_q with list of registers. See syn_out/ibex_27_09_2021_16_54_01/generated/ibex_lockstep.v:226
Successfully finished Verilog frontend.

20. Executing Verilog-2005 frontend: syn_out/ibex_27_09_2021_16_54_01/generated/ibex_multdiv_fast.v
Parsing SystemVerilog input from `syn_out/ibex_27_09_2021_16_54_01/generated/ibex_multdiv_fast.v' to AST representation.
Generating RTLIL representation for module `\ibex_multdiv_fast'.
Successfully finished Verilog frontend.

21. Executing Verilog-2005 frontend: syn_out/ibex_27_09_2021_16_54_01/generated/ibex_multdiv_slow.v
Parsing SystemVerilog input from `syn_out/ibex_27_09_2021_16_54_01/generated/ibex_multdiv_slow.v' to AST representation.
Generating RTLIL representation for module `\ibex_multdiv_slow'.
Successfully finished Verilog frontend.

22. Executing Verilog-2005 frontend: syn_out/ibex_27_09_2021_16_54_01/generated/ibex_pmp.v
Parsing SystemVerilog input from `syn_out/ibex_27_09_2021_16_54_01/generated/ibex_pmp.v' to AST representation.
Generating RTLIL representation for module `\ibex_pmp'.
Successfully finished Verilog frontend.

23. Executing Verilog-2005 frontend: syn_out/ibex_27_09_2021_16_54_01/generated/ibex_prefetch_buffer.v
Parsing SystemVerilog input from `syn_out/ibex_27_09_2021_16_54_01/generated/ibex_prefetch_buffer.v' to AST representation.
Generating RTLIL representation for module `\ibex_prefetch_buffer'.
Successfully finished Verilog frontend.

24. Executing Verilog-2005 frontend: syn_out/ibex_27_09_2021_16_54_01/generated/ibex_register_file_latch.v
Parsing SystemVerilog input from `syn_out/ibex_27_09_2021_16_54_01/generated/ibex_register_file_latch.v' to AST representation.
Generating RTLIL representation for module `\ibex_register_file_latch'.
Warning: Replacing memory \mem with list of registers. See syn_out/ibex_27_09_2021_16_54_01/generated/ibex_register_file_latch.v:113, syn_out/ibex_27_09_2021_16_54_01/generated/ibex_register_file_latch.v:87
Successfully finished Verilog frontend.

25. Executing Verilog-2005 frontend: syn_out/ibex_27_09_2021_16_54_01/generated/ibex_top.v
Parsing SystemVerilog input from `syn_out/ibex_27_09_2021_16_54_01/generated/ibex_top.v' to AST representation.
Generating RTLIL representation for module `\ibex_top'.
Successfully finished Verilog frontend.

26. Executing Verilog-2005 frontend: syn_out/ibex_27_09_2021_16_54_01/generated/ibex_top_tracing.v
syn_out/ibex_27_09_2021_16_54_01/generated/ibex_top_tracing.v:99: ERROR: FATAL: Fatal error: RVFI needs to be defined globally..
Failed to synthesize RTL with Yosys

Hi,
Any help on this error would be greatly appreciated.
Thanks.

Please try using the exact same versions of yosys and sv2v as @tomroberts-lowrisc mentioned above; the syn_yosys.sh scripting is highly fragile (and unsupported), so if you'd like to use other versions you'll probably need to do some digging yourself.

I can also run syn_yosys.sh without issue. I'm using an older version of sv2v and yosys (sv2v v0.0.5-18-ga170536 and Yosys 0.9+1706 (git sha1 968956ba, clang 6.0.0-1ubuntu2 -fPIC -Os). It looks like either the newer sv2v is translating things a bit differently and yosys doesn't like it or sv2v is emitting some slightly broken verilog that previously yosys didn't care about but now does.


Hello, I'm in trouble with RPPanalyzer tutorial

Hello, I'm beginning user with github.
Also I'm beginning user with R.
And  I'm bad at English.
And I'm in trouble with RPPanalyzer tutorial
I am following the tutorial RPPanalyzer for practice.
RPPanalyzer (Version 1.0.3)
Analyze reverse phase protein array data
User‘s Guide
Heiko Mannsperger and Stephan Gade
German Cancer Research Center
Heidelberg, Germany
October 1, 2012
below is What I done at R
BiocManager::install("RPPanalyzer")
library(RPPanalyzer)
##define path to example files
dataDir <- system.file("extdata",package = "RPPanalyzer")
change working directory
setwd(dataDir)
##store example sample description in a variable
sampledescription <- read.delim("sampledescription.txt")
s## show sample description header
head(sampledescription)
dataDir <- system.file("extdata", package = "RPPanalyzer")
setwd(dataDir)
store example sample description in a variable
slidedescription <- read.delim("slidedescription.txt")
show sample description header
head(slidedescription)
and here is what i'm trouble with
rawdata <- read.Data(blocksperarray = 4, spotter = "arrayjet",printFlags = FALSE)
when if i run , i got error like this  ; Error in dimnames(x) <- dn : length of 'dimnames' [2] not equal to array extent.
How can I handle with this...?

And if you know about RPPanalyzer pipeline with example data, please teach me.


Add simple supervisor service module

This is a very naive module for checking if supervisor managed processes are running or not. It currently just executes on a host to check if something is running.

Hi, thanks.
Beside my comments, consider adding a test (install supervisor in debian_jessie docker image and put some dummy services inside the config).

@philpep thanks for the comments, the PR was a first attempt at a supervisor module. I'll address the issues and submit more commits to this PR.

@philpep I've addressed the issues above, all except the test part related to docker.

I've added a dumb nc listener service and supervisord to the debian jessie docker image

@philpep I've made the suggested changes

Merged in 3a5f4571141bd7a7c0bbd0a5c1b3a1b1d9df3b80 thanks !


Cannot download posts by shortcode

Describe the bug
Cannot download posts by shortcode
To Reproduce
Steps to reproduce the behavior:
instaloader --load-cookies Firefox --no-metadata-json --abort-on=302,400,429,401 -- -XXXXXXXX
Error messages and tracebacks
Cookies loaded successfully from firefox
myaccount has been successfully logged in.
Next time use --login=myaccount to reuse the same session.
Download aborted: Query to https://www.instagram.com/graphql/query responded with "302 Found" redirect to https://www.instagram.com/.
Saved session to xxxxxxxxxx
HTTP redirect from https://www.instagram.com/graphql/query to https://www.instagram.com/
JSON Query to graphql/query: Expecting value: line 1 column 1 (char 0) [retrying; skip with ^C]
HTTP redirect from https://www.instagram.com/graphql/query to https://www.instagram.com/
JSON Query to graphql/query: Expecting value: line 1 column 1 (char 0) [retrying; skip with ^C]
HTTP redirect from https://www.instagram.com/graphql/query to https://www.instagram.com/
-XXXXXXXX: JSON Query to graphql/query: Expecting value: line 1 column 1 (char 0)
Saved session to xxxxxxxxxx
Errors or warnings occurred:
-XXXXXXXX: JSON Query to graphql/query: Expecting value: line 1 column 1 (char 0)
Instaloader version
4.13.1

'query_hash': '2b0673e0dc4580674a88d426fe00ea90',  has wrong

I think a number of issues these few days are due to some API changes: https://developers.facebook.com/docs/instagram-platform/changelog/

That'd make sense. I also started having issues now and not earlier, and the changelog checks it. When downloading I get:
`instaloader --login= -- -<post_id>
Loaded session from /home/user/.config/instaloader/session-.
Logged in as .
-<post_id>: 400 Bad Request - "fail" status, message "feedback_required" when accessing https://www.instagram.com/graphql/query?<query_hash>,,<short_code>
Saved session to /home/user/.config/instaloader/session-.
Errors or warnings occurred:
-<post_id>: 400 Bad Request - "fail" status, message "feedback_required" when accessing https://www.instagram.com/graphql/query?<query_hash>,,<short_code>
`

I cannot download the reels. Here is what I'm get, I'm end up successfully downloaded the profile picture only.
instaloader --login=username profile [profile]
Session is loaded and account is logged in.
**JSON Query to api/v1/users/web_profile_info/?username=profile: 404 Not Found when accessing https://i.instagram.com/api/v1/users/web_profile_info/?username=profile [retrying; skip with ^C]
JSON Query to api/v1/users/web_profile_info/?username=profile: 404 Not Found when accessing https://i.instagram.com/api/v1/users/web_profile_info/?username=profile [retrying; skip with ^C]
Profile profile does not exist.
The most similar profiles are: photo__.profile., profile_pictures_rating
Trying again anonymously, helps in case you are just blocked.
HTTP redirect from https://i.instagram.com/api/v1/users/web_profile_info/?username=profile to https://i.instagram.com/accounts/login/?next=/api/v1/users/web_profile_info/
Redirected to login page. Use --login or --load-cookies.
[1/1] Downloading profile [profile]
Retrieving posts from profile [profile].
Saved session to path.**

Profile profile does not exist.
The most similar profiles are: photo__.profile., profile_pictures_rating
Trying again anonymously, helps in case you are just blocked.

It seems that you are downloading posts from an empty account? Maybe you should check the profile name again

Any account would prompt these output. Not an empty account for sure. I usually ignore such output cause previously i can download the posts and reels

On running this code:
import instaloader
L = instaloader.Instaloader()
post = instaloader.Post.from_shortcode(L.context, "C_ztYi6gvKZ")

Getting this error:
JSON Query to graphql/query: 401 Unauthorized - "fail" status, message "Please wait a few minutes before you try again." when accessing https://www.instagram.com/graphql/query?query_hash=2b0673e0dc4580674a88d426fe00ea90&variables={"shortcode"%3A"C_ztYi6gvKZ"} [retrying; skip with ^C]

Found the new url for graphql
Can this be fixed?
https://www.instagram.com/graphql/query/?doc_id=17867389474812335&variables={"include_logged_out"%3Atrue%2C"include_reel"%3Afalse%2C"shortcode"%3A"C_ztYi6gvKZ"}

I am having the same issue.
JSON Query to graphql/query: Expecting value: line 1 column 1 (char 0)

Fixed in Version 4.13.2.


No way to access ResourceUid class in C#

Godot version
4.0.rc4.mono
System information
Windows 10
Issue description
In C#, I can't find anywhere to get the instance of the ResourceUid singleton. I believe this class is supposed to be static, but it currently isn't.
Steps to reproduce
ResourceUid.IdToText(text); <- Cannot access non-static method 'IdToText' in static contex.
var tmp = new ResourceUid(); <- Cannot access internal constructor 'ResourceUid()' here.
var tmp = GD.ResourceUid; <- No such property/method as far as I can tell, on GD and elsewhere.
Minimal reproduction project
N/A

This class is indeed registered as a singleton so it should be generated as static, but it currently doesn't because it tries to find it in Engine with the C# name (ResourceUid) instead of the C++ name (ResourceUID). A regression from https://github.com/godotengine/godot/pull/69547.


License Code Implementation

Dear @jharrison42 and @jwilles ,
I have read your recent paper with great interest since VBBL is both elegant and practical.  We recently released the first version of a Pytorch domain library for UQ called Lightning-UQ-Box, where we try to implement various UQ methods from different theoretical underpinnings, with the goal of making these methods more accessible to practitioners. Our research domain is Earth Observation data, where we are looking for exactly those kind of methods. Therefore, I wanted to ask what license your code is released under, since I would be interested to include it in the library.
Cheers, and thank you for the cool work.

Thanks for the interest! We have released it under an MIT license. Looking forward to the integration.


Does Atlantis have to run as a privileged container?

Right now, the Atlantis container runs as privileged, but it is unclear why we need to have that set. If we can get it to run as non-privileged, that would be optimal -- otherwise, we should document exactly why it needs to run as privileged so that users understand that need more thoroughly.

Thanks for raising this issue @cblkwell, I'm going to test a non-privileged release as soon as possible.


Fix Issue: If keep_temp is True, Needn't re-clone

Hi, nice to meet you! I found a issue when I typing the following commands:
[root@containerd pycontainerd]# pwd
/root/pycontainerd
[root@containerd pycontainerd]# rm -rf api_1.4/ && ./script/genpb2.sh -k -a 1.4

The containerd git repo was re-cloned. In my point, I think the -k parameter need't re-clone the repo:)

@englandbaron you're right, thanks for the fix!


Style how errors are highlighted

It should be possible to use css or some other option to style the way errors are highlighted. (This was discussed in a call on 9/30 and it was suggested that an issue be added.)

Showing all errors in the editor is now available in the development branch as an experimental feature.
Implemented for text boxes and layout boxes, does not yet refresh when model changes and does not auto-revalidate at changes in the model.

You can style it with CSS, happy to understand whether this is enough or otherwise how we can improve this.


Release notes

Deleted the previous PR in other to create separate branch for this

@chipzoller please review the changes made so far. If its what's expected I will proceed and add the former release notes.


[Feature]: Support asynchronous createTransformer

🚀 Feature Proposal
Support asynchronous functions for createTransformer  in the transformer API.
Motivation
Support asynchronous operations in createTransformer. In my case, I need to perform some pre/post processing around an existing transformer which is an esm modules.
Example
export const createTransformer = async (options) => {
  const { process } = await import(options.path);
  return {
    process: (content, path, options) => {
      console.log("pre-processing here");
      const result = process(content, path, options);
      console.log("post-processing here");
      return result;
    },
  };
};

Pitch
Currently there is now way to perform asynchronous operations in createTransformer which is needlessly restrictive. Indeed, it seems this would only require but minimal code changes because the createTransformer is already called inside an asynchronous function.
packages/jest-transform/src/ScriptTransformer.ts#L272
transformer = transformer.createTransformer(transformerConfig);

transformer = await transformer.createTransformer(transformerConfig);

PR very much welcome! As you mention, support should be fairly trivial

Hi @SimenB thanks for the swift reply.
I will try to get that done today.
Cheers

https://github.com/facebook/jest/releases/tag/v29.4.0


Have Dgeni auto extract @Inputs and @Outputs

It's working in https://github.com/driftyco/ionic/tree/ins_n_outs
Now the docs needs to be updated accordingly.

we're live!


Some extensions/files that could be added for the code preview.

Hi, I just bought your extensions, and of course, I have a request :)
Could you please add those standard Go files to be previewed?

go.mod
go.sum
go.work

And probably (which actually is YAML though):

Dockerfile (yam)
Earthfile (YAML / that would be great, as I use them a lot)

NOTE: I have no idea if it is possible to add those, especially the later ones.

I can look into adding those. Dockerfiles are already on the roadmap.

Most common file extension for TypeScript is .ts. Also, need support for .vue extension

As it says in the Read Me, PreviewCode doesn’t support TypeScript .ts files because the .ts file extension is a standard for transport stream video files. The workaround is to use .tsx for TypeScript files.
But I can look at adding .vue support. I take it you mean .vue for View.js?

But I can look at adding .vue support. I take it you mean .vue for View.js?

Actually, it means Vue.js https://vuejs.org/. For reference, you can have a look at following packages:

https://www.npmjs.com/package/vue-code-highlight
https://github.com/vuejs/language-tools

As it says in the Read Me, PreviewCode doesn’t support TypeScript .ts files because the .ts file extension is a standard for transport stream video files. The workaround is to use .tsx for TypeScript files.
But I can look at adding .vue support. I take it you mean .vue for View.js?

Can't this behavior for .ts be overridden?

I’m considering doing that since I guess most folks using PreviewCode (including me) will be using .ts for TypeScript files rather that transport stream video files.

Even if they have both, can't you open it and if it is not text, show a message, explaining what happened?

Update: preliminary .vue support coming in the next release, along with .gml (GameMaker Language) and some Xcode-specific file types.
Support for the Go .mod, .sum and .work files will appear in the next release of PreviewText, which is free.
Actively researching solutions to the .ts issue, but a solution may not make it to the next release.


create a plan with PnP to PR changes from OCW

work with PnP to capture changes to ASB from OCW prep, delivery and feedback

Completed. A few changes have been merged to the upstream repo.


Showing completions when entering a string value

Description:
$title

Issue is not reproducible in the latest language server based VScode plugin. Hence, closing the issue.


Error installing opendistro-index-management plugin due to missing dependency

I've followed the instruction for installing the opendistro standalone plugins here but I get the following error

[root@c09c2b709732 elasticsearch]# bin/elasticsearch-plugin install https://d3g5vo6xdbdb9a.cloudfront.net/downloads/elasticsearch-plugins/opendistro-index-management/opendistro_index_management-<IP_ADDRESS>.zip
-> Installing https://d3g5vo6xdbdb9a.cloudfront.net/downloads/elasticsearch-plugins/opendistro-index-management/opendistro_index_management-<IP_ADDRESS>.zip
-> Downloading https://d3g5vo6xdbdb9a.cloudfront.net/downloads/elasticsearch-plugins/opendistro-index-management/opendistro_index_management-<IP_ADDRESS>.zip
[=================================================] 100%??
-> Failed installing https://d3g5vo6xdbdb9a.cloudfront.net/downloads/elasticsearch-plugins/opendistro-index-management/opendistro_index_management-<IP_ADDRESS>.zip
-> Rolling back https://d3g5vo6xdbdb9a.cloudfront.net/downloads/elasticsearch-plugins/opendistro-index-management/opendistro_index_management-<IP_ADDRESS>.zip
-> Rolled back https://d3g5vo6xdbdb9a.cloudfront.net/downloads/elasticsearch-plugins/opendistro-index-management/opendistro_index_management-<IP_ADDRESS>.zip
Exception in thread "main" java.lang.IllegalArgumentException: Missing plugin [opendistro-job-scheduler], dependency of [opendistro_index_management]
        at org.elasticsearch.plugins.PluginsService.addSortedBundle(PluginsService.java:452)
        at org.elasticsearch.plugins.PluginsService.sortBundles(PluginsService.java:424)
        at org.elasticsearch.plugins.InstallPluginCommand.jarHellCheck(InstallPluginCommand.java:847)
        at org.elasticsearch.plugins.InstallPluginCommand.loadPluginInfo(InstallPluginCommand.java:821)
        at org.elasticsearch.plugins.InstallPluginCommand.installPlugin(InstallPluginCommand.java:866)
        at org.elasticsearch.plugins.InstallPluginCommand.execute(InstallPluginCommand.java:254)
        at org.elasticsearch.plugins.InstallPluginCommand.execute(InstallPluginCommand.java:224)
        at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86)
        at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:125)
        at org.elasticsearch.cli.MultiCommand.execute(MultiCommand.java:91)
        at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:125)
        at org.elasticsearch.cli.Command.main(Command.java:90)
        at org.elasticsearch.plugins.PluginCli.main(PluginCli.java:47)

Is this normal? I don't see any instructions on that page for how to install the missing opendistro-job-scheduler plugin. I have seen that I can go to the github page and build it from source and install it that way, but that does not seem a very efficient way if I have to do it every time I want to upgrade to a newer version.
Is there a link directly to the zip file similar to the other ones (i.e. https://d3g5vo6xdbdb9a.cloudfront.net/downloads/elasticsearch-plugins/opendistro-index-management/opendistro_index_management-<IP_ADDRESS>.zip) that I can download instead?

Hi @eoinreilly93,
Yes, the Index Management plugin needs the Job Scheduler plugin to be installed first.
The Job Scheduler plugin could be downloaded from here:
https://d3g5vo6xdbdb9a.cloudfront.net/downloads/elasticsearch-plugins/opendistro-job-scheduler/opendistro-job-scheduler-<IP_ADDRESS>.zip
Seems like the _ vs - probably throws people off and this page should have direct links to downloads rather than making people put it together.
https://opendistro.github.io/for-elasticsearch-docs/docs/install/plugins/


Reuse hardware build for multiple software tests?

It dawned on me but I wonder if we can re-use the same sw-snax-mac-cluster-vlt and just build a new SW so we don't need to do multiple HW builds?
So the idea is, build SW for the original one then build for the generic one. Test them differently since we already have the yamls separated? :)
Originally posted by @rgantonio in https://github.com/KULeuven-MICAS/snitch_cluster/pull/57#discussion_r1432444324

This is being implemented already!


Heltec ESP32 doesn't work with ESP-IDF

Hi all,
I have 2 ESP32 boards:

Heltec Automation ESP32 Development Board With 0.96inch OLED

WEMOS WiFi & Bluetooth Battery ESP32

here is my simple code:
#include <stdio.h>
#include "freertos/FreeRTOS.h"
#include "freertos/task.h"
#include "esp_system.h"

void app_main()
{
    printf("hello world\n");
}

it works as expected for the second board, but not the first one.
I have following console output for Heltec board:
Flashing binaries to serial port COM5 (app at offset 0x10000)...
esptool.py v2.1
Connecting......
Chip is ESP32D0WDQ6 (revision 1)
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Auto-detected Flash size: 4MB
Flash params set to 0x0220
Compressed 17568 bytes to 10507...
Wrote 17568 bytes (10507 compressed) at 0x00001000 in 0.9 seconds (effective 150.0 kbit/s)...
Hash of data verified.
Compressed 143088 bytes to 68405...
Wrote 143088 bytes (68405 compressed) at 0x00010000 in 6.1 seconds (effective 188.7 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 82...
Wrote 3072 bytes (82 compressed) at 0x00008000 in 0.0 seconds (effective 1521.9 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting...
MONITOR
--- idf_monitor on COM5 115200 ---
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
ets Jun  8 2016 00:22:57

rst:0x1 (POWERON__RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:4480
ho 0 tail 12 room 4
load:0x40078000,len:0
load:0x40078000,len:12988
entry 0x40078d8c

Traceback (most recent call last):
  File "C:/msys32/home/chu/esp/esp-idf/tools/idf_monitor.py", line 575, in <module>
    main()
  File "C:/msys32/home/chu/esp/esp-idf/tools/idf_monitor.py", line 504, in main
    monitor.main_loop()
  File "C:/msys32/home/chu/esp/esp-idf/tools/idf_monitor.py", line 269, in main_loop
    self.handle_serial_input(data)
  File "C:/msys32/home/chu/esp/esp-idf/tools/idf_monitor.py", line 302, in handle_serial_input
    self.console.write_bytes(b)
  File "C:/msys32/mingw32/lib/python2.7/site-packages/serial/tools/miniterm.py", line 63, in write_bytes
    self.byte_output.write(byte_string)
  File "C:/msys32/home/chu/esp/esp-idf/tools/idf_monitor.py", line 567, in write
    self.output.write(b)
IOError: [Errno 22] Invalid argument
make: *** [/home/chu/esp/esp-idf/components/esptool_py/Makefile.projbuild:96: monitor] Error 1

Any ideas why and how to solve it?
PS Heltec board works perfect from arduino IDE, so it's not broken.
BR, Igor

just found the reason... (as usually after issue described)
printf sends data on different speed. Looks like on 74880...

That board probably uses 26mhz crystal so you need to select it in menuconfig

No, this is not the root.
When I used another console at 115200 a can see loading logs and then noice,
at 74880 I can see noice insead of loading logs and than my output.
So it starts at 115200 and then swith to 74880 somehow. The same code for different boards works different - this is what I didn't expect.
Looking now how to change baudrate for output...

Did you try it?
https://github.com/espressif/arduino-esp32/blob/79e5d4c40da01306bfc03aa7150440d1fcb65f41/tools/sdk/sdkconfig#L236
https://github.com/espressif/esp-idf/blob/f32fa0c1e9843565f95a632baf27df04e8b636fd/components/esp32/Kconfig#L716

@chebukin as @negativekelvin has hinted above, you need to modify your project configuration, setting XTAL frequency from the default value of 40MHz to either "Autodetect" or 26MHz.
You can change this setting by running make menuconfig, navigating into Component config > ESP32-specific, and changing "Main XTAL frequency" option. This option is documented here:
http://esp-idf.readthedocs.io/en/latest/api-reference/kconfig.html#esp32-xtal-freq-sel
The same board works in Arduino because, unlike IDF, in Arduino "Autodetect" option is used as a default.

Yes, that really helps. Thanks a lot!


Initial independent watchdog implementation

Not sure why it didn't compile in the first place, but let's try it again :o
bors r+


The configuration file should still be hooked up after injection is prohibited.

Could you consider still hooking up the configuration file path in Dopamine while disabling injection plugins? Because Sileo or Filza would write to /private/var/mobile/Library/Preferences at this time.
Additionally, if plugins are already disabled, it should also cancel the subsequent restart of the user space. This is because a problem with the daemon process may result in repeated logouts or restarts of the user space. Alternatively, could you consider adding a button in the Dopamine settings menu for users to confirm before restarting the user space? This button can be manually triggered by the user.

I tried that before but couldn't get it working :/ I think the /private/preboot path might be too long for the weird cfprefsd api.
I don't see how a daemon problem would prevent userspace reboots from working.

I tried that before but couldn't get it working :/ I think the /private/preboot path might be too long for the weird cfprefsd api.
I don't see how a daemon problem would prevent userspace reboots from working.

I'm sorry, I misunderstood yesterday. (yesterday, i wrote a faulty shell daemon process, and an incorrect file judgment caused 'launchctl reboot userspace' to execute after the daemon process started.)
So now I'm revising my previous statement, suggesting that we should follow Taurine's approach of starting only the OpenSSH daemon process and not other daemon processes when preventing plug-in injection.

I don't get what's the problem here - When tweaks are disabled Dopamine will already not do a userspace reboot.


Blueapi should not be a valid target for checking out to the scratch repository

Blueapi should be a robust, tested and stable platform for developing beamline code. It should be running a known, versioned, release, for reasons including security (reduce attack surface to only what can be run as a plan, not executing all arbitrary code), debugging.
Acceptance Criteria

Specific criteria that will be used to judge if the issue is fixed

I think this is a fairly simple addition to the scratch code, when pip installing we can fail if the package is called blueapi and display a sensible error message to the user.


Data node spec improvements

The spec should clarify:

how does data node get its data, how it restarts, how it catches up
how does it communicate liveness / up-to-dateness / readiness to serve clients to clients
how does it handle core restarts, core going down, ingesting data slower than core produces them (forever / for a long period of time)

Copied over from duplicate issue:
Update the data-node spec with ACs around testing, to include (pending review/re-writing) but not exhaustive:
Datanode:

[ ] APIs
[ ] datanode snapshots
[ ] post protocol upgrade

Data comparison:

[ ] Diff core snapshots against datanode state
[ ] Using PG Dump tools to compare data across datanodes on the network

Closing as conversations / reviews to happen against:
https://github.com/vegaprotocol/specs/pull/1239


Metadata import

As a cataloguer I would like to import metadata from other sources (csv, xlsx, xml, the cat, archivesspace) to eliminate the need for multiple data entry points.

Needs more information.

this is represented in other user stories with further information.


C++11

Hi,
on the website it is stated that the library can be easily adapted to be usable with C++11. I would like to use the library in a project in which I am unfortunately restricted to C++11 for now. How much effort would it be to compile the library with the v140 toolset on windows? In a first attempt there were quite a few errors. Or would you recommend using Clipper1 for that usecase?
Thanks

https://github.com/AngusJohnson/Clipper2/discussions/796#discussioncomment-8913472


I dont understand the memory sensor

I have setup several systems and the default value of the memory eludes me.
what is this representing? See Doorman low value mem.
see screenshots.

The default memory sensor value represents "MemFree", see https://github.com/tobias-kuendig/hacompanion/blob/2fa3f436226a0b640184bfcc9bb6193d233f449d/sensor/memory.go#L47-L48
For what this actually means, this might be helpful: https://superuser.com/a/980821


Ukrainian

It doesn’t appear that the apostrophe (which functions, I believe, like the hard sign in Russian) is differentiated from the soft sign in ScriptShifter transliteration

This was discussed on 02/24/23. The problem seems to lie in the fact that an apostrophe is sometimes used instead of a soft sign in the source, and the former does not get transliterated.
This can either be left as is to highlight the error in the source, or if we want to be more lenient, add transliteration rules to map the apostrophe to the same characters that the soft sign does. This only applies to script that don't have an apostrophe sign.

The apostrophe should NOT be used in Latin transliteration to represent the Cyrillic soft sign. Ukrainian also uses the apostrophe, so the two must have different characters in Latin strings. That is why the character "prime" is used for the soft sign, to differentiate it from the apostophe.

We're good then. Thanks.


Update docker-compose.yml: open ports 20k-30k for deeplinks container

It is neccessary for port handler in production.

This pull request status depends on https://github.com/deep-foundation/deeplinks/issues/249


On GPU, TestTreeRecombination is failing

What's the problem?
On NVIDIA GPU, TestTreeRecombination::test_reduce is failing.
How can we reproduce the issue?
Run  tests/unit/test_solvers.py::TestTreeRecombination::test_reduce
Python version
3.12
Package version
0.3.1
Operating system
Ubuntu 24.04 with NVIDIA GPU
Other packages
jax[cuda12]
Relevant log output
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[with_jit-random-implicit-explicit-context0-False] - assert Array(False, dtype=bool)
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[with_jit-random-implicit-explicit-context0-True] - assert Array(False, dtype=bool)
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[with_jit-partial-null-implicit-explicit-context0-False] - assert Array(False, dtype=bool)
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[with_jit-partial-null-implicit-explicit-context0-True] - assert Array(False, dtype=bool)
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[without_jit-partial-null-implicit-explicit-context0-False] - assert Array(False, dtype=bool)
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[without_jit-partial-null-implicit-explicit-context0-True] - assert Array(False, dtype=bool)
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[without_jit-partial-null-explicit-context2-False] - assert 16 <= Array(11, dtype=int32)
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[without_jit-partial-null-explicit-context2-True] - assert 16 <= Array(11, dtype=int32)
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[without_jit-random-implicit-explicit-context0-False] - assert Array(False, dtype=bool)
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[without_jit-random-implicit-explicit-context0-True] - assert Array(False, dtype=bool)
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[without_jit-random-explicit-context2-False] - assert 16 <= Array(11, dtype=int32)
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[without_jit-random-explicit-context2-True] - assert 16 <= Array(11, dtype=int32)
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[without_jit-null-implicit-explicit-context0-False] - assert 11 <= (11 - (11 - Array(1, dtype=int32)))
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[without_jit-null-implicit-explicit-context0-True] - assert 11 <= (11 - (11 - Array(1, dtype=int32)))
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[without_jit-null-explicit-context2-False] - assert 14 <= Array(1, dtype=int32)
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[without_jit-null-explicit-context2-True] - assert 14 <= Array(1, dtype=int32)
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[with_jit-null-implicit-explicit-context0-False] - assert 11 <= (11 - (11 - Array(1, dtype=int32)))
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[with_jit-null-implicit-explicit-context0-True] - assert 11 <= (11 - (11 - Array(1, dtype=int32)))
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[without_jit-full_rank-implicit-explicit-context0-False] - assert Array(False, dtype=bool)
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[without_jit-full_rank-implicit-explicit-context0-True] - assert Array(False, dtype=bool)
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[without_jit-full_rank-explicit-context2-False] - assert 6 <= Array(4, dtype=int32)
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[without_jit-full_rank-explicit-context2-True] - assert 6 <= Array(4, dtype=int32)
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[with_jit-full_rank-implicit-explicit-context0-False] - assert Array(False, dtype=bool)
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[with_jit-full_rank-implicit-explicit-context0-True] - assert Array(False, dtype=bool)
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[without_jit-rank_deficient-implicit-explicit-context0-False] - assert 3 <= (4 - (4 - Array(2, dtype=int32)))
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[without_jit-rank_deficient-implicit-explicit-context0-True] - assert 3 <= (4 - (4 - Array(2, dtype=int32)))
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[without_jit-rank_deficient-explicit-context2-False] - assert 3 <= Array(2, dtype=int32)
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[without_jit-rank_deficient-explicit-context2-True] - assert 3 <= Array(2, dtype=int32)
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[with_jit-rank_deficient-implicit-explicit-context0-False] - assert 3 <= (4 - (4 - Array(2, dtype=int32)))
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[with_jit-rank_deficient-implicit-explicit-context0-True] - assert 3 <= (4 - (4 - Array(2, dtype=int32)))
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[without_jit-excessive_test_functions-implicit-explicit-context0-False] - assert 84 <= (128 - (128 - Array(1, dtype=int32)))
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[without_jit-excessive_test_functions-implicit-explicit-context0-True] - assert 84 <= (128 - (128 - Array(1, dtype=int32)))
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[without_jit-excessive_test_functions-implicit-context1-False] - assert 84 <= (128 - (128 - Array(1, dtype=int32)))
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[without_jit-excessive_test_functions-implicit-context1-True] - assert 84 <= (128 - (128 - Array(1, dtype=int32)))
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[without_jit-excessive_test_functions-explicit-context2-False] - assert 84 <= Array(1, dtype=int32)
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[without_jit-excessive_test_functions-explicit-context2-True] - assert 84 <= Array(1, dtype=int32)
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[with_jit-excessive_test_functions-implicit-explicit-context0-False] - assert 84 <= (128 - (128 - Array(1, dtype=int32)))
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[with_jit-excessive_test_functions-implicit-explicit-context0-True] - assert 84 <= (128 - (128 - Array(1, dtype=int32)))
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[with_jit-excessive_test_functions-implicit-context1-False] - assert 84 <= (128 - (128 - Array(1, dtype=int32)))
FAILED tests/unit/test_solvers.py::TestTreeRecombination::test_reduce[with_jit-excessive_test_functions-implicit-context1-True] - assert 84 <= (128 - (128 - Array(1, dtype=int32)))

@tc85324 For visibility, we are seeing test failures on this (also see #853 ) - do you have any thoughts on the cause?

I think this is the result of numerical precision loss. I would guess that the GPU in question does not support double precision compute, or it is not used by default (jax_enable_x64=False)? I've anecdotally seen a similar issue on CPU devices, but in those cases we could simply enable jax_enable_x64=True without too much issue.
I have worried before about being a bit relaxed in the handling of precision loss in the recombination solvers. For this specific case, I am not sure where exactly the precision loss is accumulated in the algorithm, but considering the very similar issue #853 for the simpler CaratheodoryRecombination solver, I would expect the loss to occur in the SVD computation.
However, with that said, #874 appears to address the issue by modifying the elimination procedure -- I will spend some time to identify the root cause in reviewing #874.

I can confirm that setting JAX_ENABLE_X64=True makes the tests pass.


 In this case, do I simply need to run rehash?
I'm new to Python and just trying to get up and running.

Install the latest version and add its alias to .zshrc.

 What is happening, I guess, is that there's some command containing source .zshrc and involving the editor in the shell's history, which makes the history rule suggest that as a fix. IOW, that's expected behavior.
How is source .zshrc not working for you? How would you expect TheFuck to fix it?
TheFuck is intended to act on failed commands.

Install the latest version and add its alias to .zshrc.

 What is happening, I guess, is that there's some command containing source .zshrc and involving the editor in the shell's history, which makes the history rule suggest that as a fix. IOW, that's expected behavior.
How is source .zshrc not working for you? How would you expect TheFuck to fix it?
TheFuck is intended to act on failed commands.

I hadn't realized it until you mentioned it, but this does seem to be a quirk of my own .zsh_history.
My intention here was just to ensure that TheFuck worked correctly in the context of pyenv, pyenv-virtualenv and Python 3.9.1, which I had just installed. I suspect sourcing .zshrc caused the issue, but the README suggests doing just that.

Changes are only available in a new shell session. To make changes immediately available, run source ~/.bashrc (or your shell config file like .zshrc).

Aside from quitting and relaunching Terminal, is there a better way to deal with this?

I hadn't realized it until you mentioned it, but this does seem to be a quirk of my own .zsh_history.
My intention here was just to ensure that TheFuck worked correctly in the context of pyenv, pyenv-virtualenv and Python 3.9.1, which I had just installed. I suspect sourcing .zshrc caused the issue, but the README suggests doing just that.

Changes are only available in a new shell session. To make changes immediately available, run source ~/.bashrc (or your shell config file like .zshrc).

Aside from quitting and relaunching Terminal, is there a better way to deal with this?

There are other ways, such as exec zsh which would spawn a new shell process, replacing the current. To ensure it is working correctly, try a failed command after making changed vailable.  If everything is setup correctly, it should suggest a fixed echo working.

There are other ways, such as exec zsh which would spawn a new shell process, replacing the current. To ensure it is working correctly, try a failed command after making changed vailable.  If everything is setup correctly, it should suggest a fixed echo working.


[1.16.3] Astromine causes fire from touching lava to last for 17 minutes

Having Astromine installed causes the player to stay on fire after touching lava for 1024 seconds, or 17 minutes.
Steps to reproduce:

Install astromine-1.11.4+fabric-1.16.3 on an instance of Minecraft 1.16.3 with Fabric
Create a new creative mode, commands-enabled world to test with (I used a superflat world and disabled mob spawning)
Place lava in the world and switch to survival mode
Run /effect give @p minecraft:fire_resistance 1084 0 to give yourself 18:04 of fire resistance
Step in the lava and back out
Wait for 17:04. The fire should extinguish at approximately 1 minute of fire resistance remaining

I got the number 1024 from here. It appears to be the root cause of this.
Mods used in this test:

astromine-1.11.4+fabric-1.16.3.jar
Cardinal-Components-API-2.7.4.jar
fabric-api-0.25.4+1.16.jar
fabric-carpet-1.16.3-1.4.12+v201001.jar
libblockattributes-all-0.8.2.jar
TechReborn-1.16-3.7.1+build.162.jar

Solved.

I am still getting this error on astromine-1.11.5+fabric-1.16.5.jar.
This issue was posted in November, the most recent update was posted in January, which does not cite this issue in its changelog.
Prior updates were in October, before this issue was posted in Github.

Fixed in development build - this time, apparently, for real.

Closed, since this been been fixed.


fix: output @next/next/ instead of nextjs for plugin-name

https://nextjs.org/docs/app/building-your-application/configuring/eslint#eslint-plugin
Don't know if it changed long time ago, version 13 has the namespace too

@Boshen I think that should be like that for the eslint plugin. Let check please too.
Does oxlint not support @next/next/ prefix? Should It?
If not I can add a fix for the tests.


UWP fails Windows Store App Certification

Operating system or device - Godot version: UWP, Godot 2.2
Issue description:
After packaging my app for windows store (using Visual Studio because I'm still not able to do it from Godot export), I ran the windows store app certification program. Everything seems to work except for this one API call:

I was able to pass the Cert Kit. I wonder if something changed.

@vnen did you try with 2.2 or 2.1?

Both, actually. Maybe it's something on the game?

I tried now with a simple demo, it fails in the same way.

in case it matters:
target platform: 10.0.10240.0

It passes for me with 2.2.

Strange... It fails with both on my side :/

Are you using any extra modules? That function sounds like it's
thread-related, I remember using the STL stuff for the threads originally,
that should be standard..
On 16 June 2017 at 15:31, Nuno Donato<EMAIL_ADDRESS>wrote:

Strange... It fails with both on my side :/
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/9213#issuecomment-309101297,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGVmPdrdT7b2tGDiFO9EUiO0czmDx-0pks5sEsobgaJpZM4N8fwD
.

@punto- no, like I said, I tried a simple demo project and it also failed

Could be either a difference in your ANGLE versions, or in the way you export to UWP?

tried now with my own ANGLE build, still failed :(

Can we expect to have official export templates for WinRT in the next 2.1.4? In that case there's no need to worry as the official one will pass certification... I guess... unless the problem is not in the godot executable, but should be, right?

tried now with the beta 2.1.4 templates, still fail validation on my side. Does it pass with you  @vnen ?

@nunodonato I got a pass here with a simple project. I'll try later with your project. Note that I'm using the debug exports because the release still don't run (haven't figured out the solution yet).

 This is caused by libpng use of ExitProcess() and I added a workaround to it but mistakenly put it under the x86 conditional. It was passing for me because I was building for x86, but now that I tested with x64 I got the same result.

Fixed in master (f55fff3) and 2.1 (55a3e07).


Migrate BuildChildren to impl IntoIterator<Item = Entity>

Fixes https://github.com/bevyengine/bevy/issues/7229
This PR picks up where https://github.com/bevyengine/bevy/pull/7244 leaves off.  In this PR we migrate the remaining methods on the BuildChildren trait to use children: impl IntoIterator<Item = Entity> instead of children: &[Entity].  In the process we change the move semantics.  (I only created this PR when I saw that the earlier one had been dormant for several weeks.)
cc @LamequeFernandes, @adam-shih, @XaurDesu
Questions:

[x] Should other traits in this file should be migrated as well?
[ ] Should some of the methods use impl Iterator<Item = &'e Entity> instead, in order to avoid consuming the input?
[ ] What if anything should go in the Migration Guide section?

@devil-ira sounds good.  Just so I don't go off on a tangent, can you link to an example or two of methods you want to modify?  I looked in crates/bevy_ecs/src/world/entity_ref.rs, and the only function I found there with a slice argument was sorted_remove.  But perhaps you have something more general in mind.
@devil-ira, @james7132 any thoughts on the questions I added to the description?

Ah, sorry I should have been more clear. I was referring to the BuildWorldChildren impl for EntityMut in the same file (child_builder.rs)

Seems there's some errors that are being picked up in CI that I don't see in my smoke tests when running things locally.  This evening or tomorrow I'll try to reproduce what CI is doing.

I was able to mostly repro what CI is doing by updating to the latest stable version using rustup and then running this command:
$ cargo run -p ci -- lints

I say "mostly" because the linter wanted me to fix a linting issue in crates/bevy_reflect/src/enums/dynamic_enum.rs, which wasn't touched in this PR, so I suspect that my local run isn't quite the same as CI on GitHub.

@devil-ira is this good to go, or is there something else that will be needed?

Should some of the methods use impl Iterator<Item = &'e Entity> instead, in order to avoid consuming the input?

What you could use is impl IntoIterator<Item = impl Borrow<Entity>> which accepts both owned values and references. That should avoid this being breaking change as well.
This does mean you have to do SmallVec::from_iter(children.into_iter().map(|e| *e.borrow())) instead.

What you could use is impl IntoIterator<Item = impl Borrow> which accepts both owned values and references.

Done.

Might be good to move this function over as well.

As I work through this PR, I'm beginning to wonder whether it improves upon the existing ergonomics, or whether it makes it harder to work with the children argument than when it was passed as a &[Entity] slice.

Closing per this discussion: https://github.com/bevyengine/bevy/issues/7229#issuecomment-1465434249


[Request] useMaximumSize based height option

Problem
Right now useMaximumSize param is based on width, this is not worked for long images..
Wonder if we can add a option based on the height for useMaximumSize
Solution
A option to make use naturalHeight
Further suggestions
No response

Could you tell me the exact size of the image?
It might be very helpful to resolve this issue.

@marshallku  Thanks for you reply. Here is an example: https://mirror.xyz/zoroo.eth/pfen9oHGGaq09fUbsS1LQRXw3Gl2AkxToUufaIQL_oU
In this article, there is a long image:  https://images.mirror-media.xyz/publication-images/0yDketZhapYnyypIuU4fW.png?height=4518&width=780

@0xhaole I tested in almost every screen size with that image, and it does work fine.
You might think that it's not working becuase it's shrinked, but fitting the image to the screen is the most important goal for this package.


chore: fix windows buildspec

Description of changes

Issue #, if available

Description of how you validated changes
Checklist

[ ] PR description included
[ ] yarn test passes
[ ] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)
[ ] New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies
[ ] Pull request labels are added

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

:exclamation: No coverage uploaded for pull request base (cb@545dcc4). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@          Coverage Diff          @@
##             cb   #12743   +/-   ##
=====================================
  Coverage      ?   47.61%
=====================================
  Files         ?      842
  Lines         ?    38302
  Branches      ?     7833
=====================================
  Hits          ?    18239
  Misses        ?    18441
  Partials      ?     1622

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Webhook: ClusterSecretStore does not pass the provided Secret namespace when using type Secret

Describe the bug
I am unable to upgrade past v0.9.12 due to what appears to be a bug with the caProvider Secret type for the webhook provider. After upgrading, the ClusterSecretStore becomes unready with status 'InvalidProviderConfig' and error message failed to get cert from secret: failed to resolve secret key ref: cannot get Kubernetes secret "my-certificate": an empty namespace may not be set when a resource name is provided
However, I am providing a namespace for the secret:
spec:
  provider:
    webhook:
      caProvider:
        key: ca.crt
        name: my-certificate
        namespace: secret-system
        type: Secret

After tracing this through with a debugger the issue seems to be caused because a StoreKind is not provided to the wh Webhook in NewClient().
line 65 webhook.go
wh := webhook.Webhook{
	Kube:      kube,
	Namespace: namespace,
}

When whClient.wh.GetHTTPClient(ctx, provider) is called on line 85 it gets called with StoreKind unset on wh.
Once we reach SecretKeyRef() in secret_ref.go, the conditional fails because storeKind is empty and therefor key.Namespace does not get assigned the value of ref.Namespace
if (storeKind == esv1beta1.ClusterSecretStoreKind) && (ref.Namespace != nil) {
        key.Namespace = *ref.Namespace
}

When the key is passed to c.Get(), the namespace of the secret is missing, resulting in the error.
Proposed Fix
A simple fix would be to add StoreKind on creation of wh
wh := webhook.Webhook{
	Kube: kube,
	Namespace: namespace,
	StoreKind: store.GetObjectKind().GroupVersionKind().Kind,
}

Running this fix through the debugger results in the namespace being properly added to key.Namespace and a successful call to c.Get(ctx, key, secret).
To Reproduce
Observed this bug on k8s v1.28 and all versions of external-secrets above v0.9.12
Create a ClusterSecretStore that uses caProvider Secret type, resulting in InvalidProviderConfig  2s (x13 over 23s)  cluster-secret-store  failed to get cert from secret: failed to resolve secret key ref: cannot get Kubernetes secret "my-certificate": an empty namespace may not be set when a resource name is provided
apiVersion: external-secrets.io/v1beta1
kind: ClusterSecretStore
metadata:
  name: my-secret-store
spec:
  provider:
    webhook:
      caProvider:
        key: ca.crt
        name: my-certificate
        namespace: secret-system
        type: Secret
      headers:
        Authorization: Basic {{ print .auth.USER ":" .auth.PASS | b64enc }}
        Content-Type: application/json
      method: GET
      result:
        jsonPath: $
      secrets:
      - name: auth
        secretRef:
          name: auth-secret
          namespace: secret-system
      url: https://myservice.secret-system.svc.cluster.local:8000/secrets/{{
        .remoteRef.key | replace "%2F" "/" | replace "%3F" "?" | replace "%3D" "="
        | replace "%26" "&" }}

Expected behavior
I expect the provided namespace to be used when retrieving the caProvider Secret type.

Pull request with the proposed fix: https://github.com/external-secrets/external-secrets/pull/3960


FileHelper::createDirectory can throw an unexpected Exception

FileHelper::createDirectory is more complicated than it should be to catch all failures.
What steps will reproduce the problem?
If you do something like this
if(FileHelper::createDirectory($someFolder) === false) {
    return false;
}

It is possible you may not hit all error scenarios because it can throw an exception, so the proper way is to do something like this.
try {
    if(FileHelper::createDirectory($someFolder) === false) {
        return false;
    }
} catch(\Exception $e) {
    return false;
}

What is the expected result?
I would expect most people will write code in the first sample not the second sample, which can lead to unexpected errors.

But it is a implementation issue, not a FileHelper fault.

It is catch-able but I believe throwing an exception is kind of unnecessary. If you compare it to the php rmdir which doesn't throw an exception.

Yii converts all errors into exceptions so that's expected.

So you expect people to write code in Sample 2?
Yes Yii2 handles exceptions at a higher level, which you could still do in places you use it.
I just think diverting how core php handles mkdir and how Yii2 handles it are at odds with each other.
Anyway I can deal with it, but fundamentally having two ways to produce failures in a function just seems inconsistent and unknowingly not good. My two cents.

@scottix Catching all exception blindly will only make code harder to debug. If you have specific case when createDirectory() should not throw a exception, you should share it with us. Without it, it is only a theoretical conversation without any chance for practical changes.

@rob006 No problem I can be more clear about it in an example.
function doImportantStuff() {

    doSomeStuff1();

    $someDir = '/somepath';
    if(FileHelper::createDirectory($someDir) === false) {
        undoSomeStuff1();
        return false;
    }

    return true;
}

There are instances where undoSomeStuff1() would not get run because an exception was thrown.
 Good thing for inheritance.

because an exception was thrown

What exception was thrown and why?

There are two
When supposed path is not a directory
https://github.com/yiisoft/yii2/blob/master/framework/helpers/BaseFileHelper.php#L629
And
When chmod fails
https://github.com/yiisoft/yii2/blob/master/framework/helpers/BaseFileHelper.php#L635
Since it is recursive it could lead to other directories not being created.
To be honest the only reason I found this, when I was writing a different function using the createDirectory, it documented that it might throw an exception and that raised red flags for me.

@scottix That is expected - usually you really need create this directory and further processing does not make any sense if this fails (for example you can't upload a file when there is no directory for uploads). And usually this is result of app misconfiguration so throwing exception is more practical than checking method result and throwing exception manually.

@rob006 I think we will have to agree to disagree, I can handle it on my own, if you want to leave it as is. Just a note mis-configuration can be a problem, but also a corrupted file system can be a reason. Really it doesn't matter what the problem is, the main point I am making is, in my use case I need to handle the fallout if it does error out. I know Yii will catch the error at the top level but that is not what I want.


Alert words settings UI styling is broken

This screenshot is pretty self-explanatory:

This seems to be a very recent regression.

Hi, @timabbott I would like to work on this.
Are you referring to the "waadsf" text in the screenshot? I don't seem to have that when I open settings and select custom alert words. Can you please tell me how to reproduce this?

@pranjaypatil yes Tim is referring to the "waadsf" text in the screenshot. The way to reproduce this is to add alert words. When you add an alert word, you get the above screenshot, which shows an off format.

@lonerz got it. Apparently it lists the words that were added and clicking the delete button removes them in LIFO order. Wouldn't it be great to have a delete button with each custom alert word? Let me know your thoughts on this. Thanks!

@pranjaypatil you can open up another issue for that.

Awesome thanks.

@pranjaypatil I don't have zulip setup on my machine right now, but when i worked on #1075 I had implemented the UI as you described:

Maybe the issue you're describing is related to this one.

@phansen01 @pranjaypatil this UI was probably accidentally dropped in the new frontend push.

Yeah that's what I was wondering, it looks great the way it was implemented. So how is this going to be fixed considering that it was already implemented. I am new to this project so please help me understand the process.

@pranjaypatil I don't know a ton about CommonJS but unless I'm mistaken all of the javascript and CSS for your desired UI is still there, I don't imagine it'll be too difficult to re-implement/fix.

@pranjaypatil first thing first, you probably want to read this: http://zulip.readthedocs.io/en/latest/readme-symlink.html to start off on how to develop for Zulip. Then, as @phansen01 said, this is a regression, so most of the code is actually there and should be not too difficult to debug and fix.

Great, thank you @lonerz @phansen01 for the information.

@zulipbot claim

Hi @timabbott,
I have figured out what was causing this issue. Here's how it looks like when fixed.

Apparently the code was using a non-existent css property. I found a property that I guess was designed to apply a coherent design to all UI elements and updated it in the template (handlebars).
Moreover, the casper tests for this UI element are commented out and might need updating.
Please let me know what should be the next step to take.
Thank You!

@pranjaypatil You should create a PR with [WIP] in the title, so it is easier to look at what you have already.

@pranjaypatil I think you should submit a pull request fixing the CSS.
I think it'd also be good to uncomment the Casper tests and update them to match the other org-admin tests; I think we recently fixed the bug (in an earlier test in the file!) that had caused them to need to be commented in the first place.

I think it'd be reasonable to do a quick PR fixing the feature right now and then work on the casper test at your leisure, if it's not easy to get the casper tests working.

Okay, I will read through the docs to figure out how to submit the PR request. Also, if it is easy to fix the tests right now, then I feel its better they are fixed in this issue. But again, let me know if fixing them later would be better.
Thanks!


not getting

Challenge Create a Bootstrap Button has an issue.
User Agent is: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

<link href="https://fonts.googleapis.com/css?family=Lobster" rel="stylesheet" type="text/css">

CatPhotoApp

Click here for cat photos.

  <input type = "button" class="btn">Like</input>

Things cats love:

cat nip

laser pointers

lasagna

Top 3 things cats hate:

flea treatment

thunder

other cats

  <form action="/submit-cat-photo">
    <input type="radio" name="indoor-outdoor"> Indoor
    <input type="radio" name="indoor-outdoor"> Outdoor
    <input type="checkbox" name="personality"> Loving
    <input type="checkbox" name="personality"> Lazy
    <input type="checkbox" name="personality"> Crazy
    <input type="text" placeholder="cat photo URL" required>
    <button type="submit">Submit</button>
  </form>

I'm guessing this is the code you have added...
<input type = "button" class="btn">Like</input>

Looking at the instructions of that challenge, it is asking you to create a button element, but you have created an input element. I would also remove the spaces around the = just for good practice.
Don't forget to ask in chat or the forum first if you have any problems with challenges, as you will often get help quicker 👍

Thank you, yes, I got confused. :-) I made necessary changes.
Working fine.


Add support for groups

it would be very helpful if you could great a group of hosts that can then be deployed at once.
Nix code example:
nixinate = {
  group.production.hosts = [ "hetznix" "swordfish" ];
  group.production.buildOn = "remote"; # available options are "remote", "local" or a specific host
};

I use parallel to run deployments in parallel
parallel --tag nix run ".#apps.nixinate.{1}" ::: machine1 machine2 machine3

and created aliases like alias deploy-prodction= ...

Currently I use makefiles for "group" deployments like so:
deploy-nemesis: ## Deploy - Remote deploy to Nemesis
	nix run .#apps.nixinate.nemesis

deploy-hesperides: ## Deploy - Remote deploy to Hesperides
	nix run .#apps.nixinate.hesperides

deploy-all: ## Deploy - 'Parallel' remote deploy to Hesperides & Nemesis
	make deploy-hesperides &\
	make deploy-nemesis

deploy-all-slow: ## Deploy - Remote deploy in order: Hesperides & Nemesis. Good for debugging
	make deploy-hesperides
	make deploy-nemesis

Though I think I might make use of parallel instead of calls to the make file itself. Thanks @mrVanDalo !


Benchmarks

Would be great to see some performance benchmarks on standard datasets with some comparison to known compression algorithms.

There was this post last month, running the Compression library on an iPhone 7.
https://artandlogic.com/2017/02/save-time-energy-libcompression/

That is interesting. What kind of data was this working with (binary, text, etc.)? Is it publicly available for one to test with? Would be interesting to also compare performance on desktops with some range of processors (e.g. different SSE and AVX instruction sets).
To give an idea of what I'm getting at, please take a look at these benchmarks. I'm sure there are strengths and weaknesses of the lzfse approach. In order to get a clear idea of what they are compared to other algorithms, it would be great to see where lzfse sits on similar graphs. This way one can more easily determine when lzfse is the right choice for a problem or another compression algorithm is better suited.

FWICT I think squash, the library/benchmarking suite used to generate those results, can build a copy of lzfse. So I think it should be possible to include lzfse in the results. Have asked the project about including lzfse in the results.
xref: https://github.com/quixdb/squash/issues/226

Squash had a beta version with LZFSE from the public repository. The compression library in macOS and iOS is finely tuned for the hardware, and will be faster.


enable very short runs with scipy

Types of changes

[ ] Docs change / refactoring / dependency upgrade
[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)

Motivation and Context / Related issue
Corner case: some scipy optimizers are not ok with very small budgets.
How Has This Been Tested (if it applies)

Checklist

[x] The documentation is up-to-date with the changes I made.
[x] I have read the CONTRIBUTING document and completed the CLA (see CONTRIBUTING).
[x] All tests passed, and additional code has been covered with new tests.

Closing this in favor of #448


Changed wording to be more concise in README.md

:loudspeaker: Type of change

[ ] Bugfix
[ ] New feature
[ ] Enhancement
[ ] Refactoring

:scroll: Description

:bulb: Motivation and Context

:green_heart: How did you test it?
:pencil: Checklist

[ ] I ran ./gradlew spotlessApply before submitting the PR
[ ] I reviewed submitted code
[ ] I added tests to verify changes
[ ] All tests passing

:crystal_ball: Next steps
:camera_flash: Screenshots / GIFs

would you mind accepting the CLA, please? Without that we can't merge your PR


Direct method async listner execut twice

Hi
I was testing API by playing arrount with:
azure-iot-sdk-python-preview/azure-iot-device/samples/advanced-hub-scenarios/receive_direct_method.py
I have notice that when I push direct method from azure IOT hub or my web app function defines as callback for async listner execute it's own twice (i see it by dupilcated print messages). I am using also API for C# and there in that case callback execute only once.
Is that expected behaviour?

Thank you for raising this issue. We have successfully replicated the problem and are looking into solutions now.

The solution has been identified and we are currently implementing a fix.

This has been fixed in #115 . It will be included in the next pip release at the end of the month.


Material.css: Override opblock h4 span:after color

I'll review here soon - just haven't had time to pull down and test it out. Do you know if this change needs to be added for the other themes, or is this specific to the material theme?

@ostranme specific to the material theme 😄

Any update on this?

@heldersepu @gracefullight Sorry for the delay I've been busy after the new year. I'll merge this in this week. I'm going to have to add the same overrides to the rest of the themes as well. Thanks!

Thanks @ostranme

@ostranme  I just incorporated all your themes into Swagger-Net:

http://swagger-net-test.azurewebsites.net/swagger/ui/index?cssTheme=theme-feeling-blue-css
http://swagger-net-test.azurewebsites.net/swagger/ui/index?cssTheme=theme-flattop-css
http://swagger-net-test.azurewebsites.net/swagger/ui/index?cssTheme=theme-material-css

Looks great! 😄


fix executor file perm mode fixes #9651

fixes #9651 file permissions for directories created by executor

Replaced by #10664


Bug fix data pre-processing of embeddings demo

Fixes bug in script provided to produce the hymenoptera data in the embeddings demo.

Yes, that should do the trick!


Blocklist for instances

There's an allowlist already, I'd like an instance blocklist instead.

It already checks defederations and Fediseer censures. Are those not fitting to your case?

It does. Any chance you could mention it somewhere in the settings when I inevitably forget in half a year?

I didn't quite understand. You need this feature, right? I can implement it since it's a little if check, but I'm busy these days. I can add it in a week or two.


EndBlocker subspaces checks

With the addition of the subspaces module, profiles (and maybe posts) could need some specific checks that runs automatically in their EndBlockers to ensure if users involved in operations like relationships or blocks
are still registered in those subspaces where the operations are performed and, in case they're not, manage it.
The implementation shouldn't be difficult and I will take care of post here a proposal in the following days.
Thoughts on this? @RiccardoM @dadamu

I think this is worth exploring. However, we should try to implement this as efficiently as possible. For this reason, I think we should only consider the users that have unregistered from a subspace. We should not delete relationships or other things related to banned users, since they might always be unbanned in the future.
I think the most efficient implementation would then be to:

When a user unregisters from a subspace, store the (user + suspace) pair in a list.
At each EndBlock, run through the list of unregistered users and delete everything related to them.

Since we are going to have queries that allow us to get the information of a user for a given subspace in O(1) time, this should be pretty easy to do. Also, it should avoid having to iterate over all the users to see if they are unregistered. We simply store the unregistered ones and use that information to clear the store.

Closing this as it will be discussed better when we implement the ADR for the x/posts module