dont work on linux

sad face

Sorry for the late reply but figured better late than never haha :)
I just posted an update v0.2.0 which should now work on Linux. I tested it on Linux Mint and it's working well for me. Check out the main page here for details: https://github.com/Dteyn/SF2000_BGM_Tool
If you run into any issues just let me know!

Sorry for the late reply but figured better late than never haha :)
I just posted an update v0.2.0 which should now work on Linux. I tested it on Linux Mint and it's working well for me. Check out the main page here for details: https://github.com/Dteyn/SF2000_BGM_Tool
If you run into any issues just let me know!

Wow Thanks!! I tested and it worked !!


Can not use Chinese url?

(Are you asking for help with using Caddy? Please use our forum instead: https://forum.caddyserver.com. If you are filing a bug report, please take a few minutes to carefully answer the following questions. If your issue is not a bug report, you do not need to use this template. Thanks!)
1. What version of Caddy are you running (caddy -version)?
0.9.5
2. What are you trying to do?
like：
https://www.drixn.com/categories/教程/
Can‘t find~

Hi thanks for the issue. Can you provide some more detail? Your full caddy file and the full error you are receiveing

look, my files name is "中文" ,
http://<IP_ADDRESS>:2015/中文
Encode is
http://<IP_ADDRESS>:2015/%E4%B8%AD%E6%96%87
But I can not access it

Nginx is  successful in 80
http://<IP_ADDRESS>/中文
http://<IP_ADDRESS>/中文

Can you please provide

Your full Caddfile
What version of Caddy are you running?
How are you running caddy, what is the command line

Can you access another not chinese character file in the same directory?

I can fine a chinese characgter file
http://chard.kinchik.ie/中文.txt
with no difficulty, so there must be something else going on.

thaks， utf8 is OK


Compose update to 1.0.1

Kotlin update to 1.5.21
Accompanist to 0.16.0
Coil to 1.3.2
More dependencies update
replace deprecated observe from lifecycle

Hey @wiryadev, thanks for your contribution! Can you update your branch with the latest from the compose branch?

Hey @wiryadev, thanks for your contribution! Can you update your branch with the latest from the compose branch?

Hi, i have updated it with the latest compose branch and updated Coil with new rememberAsycnImagePainter they introduced in 2.x.x version.


support for one hot plugin with dynamic axis other than batch_size dim

I read the code of one hot plugin generation. It seems that it only support dynamic axis of batch size dimension. Can tpat support one hot plugin generation with dynamic axises other than batch_size dimension?

@wenqf11  Hi, why adding Transpose before and after one_hot node can avoid issues of dynamic dims? I suppose the transpose node cannot infer the exact tensort shape runtime.

@frankxyy If you have more than one dynamic dimensions, we cannot support currently. If your ONNX model has only one dynamic diemnsion, you can Transoise it  to the first dimension. It may cost more time to run it with Transpose.

@wenqf11 Thank you. Got it.


Create docs for config/default.json

We need to describe each variable - line by line with the reference links to the source code.

Related to #1239


Play plugin

Please fill up those following information before send Pull request

Pull request NO: https://github.com/apache/skywalking/pull/3207
Agent repository URL: https://github.com/aiyanbo/skywalking.git  branch: play-plugin
Testcases repository URL: https://github.com/aiyanbo/agent-auto-integration-testcases.git

Test Report - 2019-08-20 16:01

tests  : 2 passed. 0 failed
branch name : play-plugin
commit id : 88ef44459583a88df39c8cc3e4ab7dcc1b526c10
cases branch: play-plugin
cases commit id: dd3f925293a913dc74a33f2541b8e43b5b2cd2f6

Cases List

Case description
Status
Cases

Play
2 passed. 0 failed
click me

Play

Version
Passed
Failed

2.6.0
:heavy_check_mark:

2.7.0
:heavy_check_mark:


Started a similar list for purescript, with attribution

I started a similar list for companies that use Purescript. It currently uses pretty much the same format and blurb as this list, but I have added an attribution to this project at the top. I hope that this is acceptable. Please let me know if you would like me to change something.
The project is here -
https://github.com/ajnsit/purescript-companies

Nice initiative. That's fine, good luck!

@erkmos I think that people interested in companies using Haskell are likely to be interested in companies using PureScript. Would you accept a PR to add a top reference to this other list?

I guess that would be ok


Create vscode_shortcuts.md

Hi Christian, thanks for creating a youtube video and this repo. Please take a look at those vscode shortcuts. I think those are the defaults.

MacOS vscode shortcuts


Let ReactiveUI RxApp handle multiple windows

On UWP each new window gets its own ui thread and the way WaitForDispatcherScheduler (which is the default scheduler for RxApp.MainThreadScheduler) works it is inherently only going to work on a single window app. As @anaisbetts put it in Slack, UWP UI thread situation is a "tire fire" and to quote "ReactiveUI is not designed to handle multiple window apps" - which essentially means no ProjectionManager, no ShareTarget, no ApplicationViewSwitcher, nothing multi-window. While I agree with the first part (and begrudgingly the second part), I am not so sure that RxUI shouldn't be considering these issues.
This can cause issues with RxApp.MainThreadScheduler, where each one of these windows runs its own dispatcher thread and is an “Application Single Threaded Apartment” (ASTA). Essentially the framework is blocking what it thinks is a potential deadlock. This particular exception is thrown when code running under one STA (1) calls out to another STA (2) and that STA (2) might have to re-enter STA (1) in order to do its work. The framework throws that exception at this point to try and stop you getting into a mess with deadlocks.
I am currently testing a scheduler that can handle multiple windows/dispatchers and will hopefully manage this as well, but we are still testing it and I'm not sure if I'll be able to block this exception yet (which would make my new scheduler useless... 👎).
Originally posted by @hinterlandsupplyco in https://github.com/reactiveui/ReactiveUI/issues/2034#issuecomment-504558031

Fixed by #2100


yosys-abc takes a very long time

Description
I thought I'd try synthesizing something other than the inverter, so I took a VexRiscv verilog file and tried replacing inverter.v. The resulting repo is at https://github.com/xobs/openlane-cpu-synth-test
The build has been running for about seven hours now:
  PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
11209 user      20   0 2010644   1.9g   9516 R  99.7   3.0 411:02.80 yosys-abc

This was reported in #openlane, and I was instructed to open an Issue report.
Expected Behavior
yosys-abc shouldn't take so long, particularly since the synthesis only took a few minutes. It would be very useful to know what's going on.
Environment report
Kernel: Linux v<IP_ADDRESS>-microsoft-standard-WSL2
Distribution: ubuntu 22.04
Python: v3.10.6 (OK)
Container Engine: docker v20.10.21 (OK)
OpenLane Git Version: flow-overview-typo-dev
pip: INSTALLED
python-venv: INSTALLED
---
PDK Version Verification Status: OK
---
Git Log (Last 3 Commits)

dbc0495 2022-11-24T09:47:36+08:00 docs: correct small typo in flow_overview.md - Sean Cross -  (HEAD -> flow-overview-typo, xobs/flow-overview-typo)
ff85171 2022-11-21T11:23:51+02:00 Document Error in JSON Config Files (#1509) - Mohamed Gaber -  (origin/master, origin/HEAD, master)
cb59d1f 2022-11-18T18:42:38+02:00 fix return values in `equally_spaced_sequence` (#1503) - Kareem Farid -  (tag: 2022.11.19)
---
Git Remotes

origin  https://github.com/The-OpenROAD-Project/OpenLane.git (fetch)
origin  https://github.com/The-OpenROAD-Project/OpenLane.git (push)
xobs    git@github.com:xobs/OpenLane.git (fetch)
xobs    git@github.com:xobs/OpenLane.git (push)

Reproduction material
The repo was posted in "Description"
Relevant log output
Running synthesis (run_synthesis).
[STEP 1]
[INFO]: Running Synthesis (log: ../../work/vexriscv-betrusted/runs/RUN_2022.11.24_10.12.11/logs/synthesis/1-synthesis.log)...
Thu Nov 24 10:12:12 +08 2022 - Executing "yosys -c /opt/Si/src/OpenLane/scripts/yosys/synth.tcl |& tee /dev/null /opt/Si/work/vexriscv-betrusted/runs/RUN_2022.11.24_10.12.11/logs/synthesis/1-synthesis.log"

@xobs
Update the config.json as per your design.
{
    "DESIGN_NAME": "VexRiscv",
    "VERILOG_FILES": "dir::VexRiscv_BetrustedSoC_Debug.v",
    "CLOCK_PORT": clk,
    "DIODE_INSERTION_STRATEGY": 3,
    "SYNTHESIS_STRATEGY": "DELAY 0"
}

Refer this setup file

The previous run finished in 7.5 hours, and then complained about [ERROR PPL-0024] Number of pins 361 exceeds max possible 106. A fair gripe. Probably not the best idea to expose a Harvard CPU directly to pins.
Let me create a top.v that reduces the number of pins that are exposed.
Note that I do have config.json configured as you suggested, and yosys-abc has been running for 40 minutes now.
I'm also running flow.tcl -synth_explore as documented in hardening_macros.md and yosys-abc has been running for 21 minutes so far...
I'll try again after putting a debug connector on this and see if that doesn't improve synthesis, but it definitely seems like yosys-abc takes a very, very long time.

I'm not sure it's the problem but you have some pretty big arrays in that design:
  (* ram_style = "block" *) reg [31:0] memory_AesPlugin_rom_storage [0:511];
  (* ram_style = "block" *) reg [21:0] ways_0_tags [0:127];
  (* ram_style = "block" *) reg [7:0] ways_0_data_symbol0 [0:1023];
  (* ram_style = "block" *) reg [7:0] ways_0_data_symbol1 [0:1023];
  (* ram_style = "block" *) reg [7:0] ways_0_data_symbol2 [0:1023];
  (* ram_style = "block" *) reg [7:0] ways_0_data_symbol3 [0:1023];
  (* ram_style = "block" *) reg [21:0] ways_1_tags [0:127];
  (* ram_style = "block" *) reg [7:0] ways_1_data_symbol0 [0:1023];
  (* ram_style = "block" *) reg [7:0] ways_1_data_symbol1 [0:1023];
  (* ram_style = "block" *) reg [7:0] ways_1_data_symbol2 [0:1023];
  (* ram_style = "block" *) reg [7:0] ways_1_data_symbol3 [0:1023];
  (* ram_style = "block" *) reg [21:0] ways_2_tags [0:127];
  (* ram_style = "block" *) reg [7:0] ways_2_data_symbol0 [0:1023];
  (* ram_style = "block" *) reg [7:0] ways_2_data_symbol1 [0:1023];
  (* ram_style = "block" *) reg [7:0] ways_2_data_symbol2 [0:1023];
  (* ram_style = "block" *) reg [7:0] ways_2_data_symbol3 [0:1023];
  (* ram_style = "block" *) reg [21:0] ways_3_tags [0:127];
  (* ram_style = "block" *) reg [7:0] ways_3_data_symbol0 [0:1023];
  (* ram_style = "block" *) reg [7:0] ways_3_data_symbol1 [0:1023];
  (* ram_style = "block" *) reg [7:0] ways_3_data_symbol2 [0:1023];
  (* ram_style = "block" *) reg [7:0] ways_3_data_symbol3 [0:1023];
  (* ram_style = "block" *) reg [31:0] banks_0 [0:1023];
  (* ram_style = "block" *) reg [31:0] banks_1 [0:1023];
  (* ram_style = "block" *) reg [21:0] ways_0_tags [0:127];
  (* ram_style = "block" *) reg [21:0] ways_1_tags [0:127];

Reducing the size of these or using DFFRAM macros should help.

That was one of the theories as to what could be causing the runtime. Is there any way to get Yosys to infer the correct macro? Or will I need to add a step before Yosys is run that replaces these registers with a module? How would I know which DFFRAM macros are available or which one I should use?
Is there any way to see what it's doing? The logfile just ends with 17.1.1. Executing ABC. without any progress as to what ABC is doing.
Is it just a bad idea to directly adapt this design from an FPGA, and instead I should pick a smaller cache with fewer ways?

@antonblanchard That's a good find. It seems as though OpenLane isn't currently inferring RAMs due to a missing memory_libmap pass. I've opened https://github.com/VLSIDA/OpenRAM/issues/163 to get the libmap and techmap files generated, and it may make sense to add a map_ram pass to https://github.com/The-OpenROAD-Project/OpenLane/blob/master/scripts/yosys/synth.tcl

I've opened VLSIDA/OpenRAM#163 to get the libmap and techmap files generated, and it may make sense to add a map_ram pass to https://github.com/The-OpenROAD-Project/OpenLane/blob/master/scripts/yosys/synth.tcl

Great! We could also build and publish a set of https://github.com/AUCOHL/DFFRAM RAMs and add yosys inference for them.
I did take a quick look at your verilog, and it is large, but I have no idea why we got stuck in yosys for so long. There are just under a million standard cells:
=== VexRiscv ===

   Number of wires:             916484
   Number of wire bits:         916809
   Number of public wires:      217117
   Number of public wire bits:  217442
   Number of memories:               0
   Number of memory bits:            0
   Number of processes:              0
   Number of cells:             916630
     sky130_fd_sc_hd__a2111o_1       2
     sky130_fd_sc_hd__a2111oi_0     26
     sky130_fd_sc_hd__a211o_1       16
     sky130_fd_sc_hd__a211oi_1     180
     sky130_fd_sc_hd__a21bo_1        3
     sky130_fd_sc_hd__a21boi_0      27
     sky130_fd_sc_hd__a21o_1        92
     sky130_fd_sc_hd__a21oi_1    44843
     sky130_fd_sc_hd__a221o_1       13
     sky130_fd_sc_hd__a221oi_1   22038
     sky130_fd_sc_hd__a222oi_1     118
     sky130_fd_sc_hd__a22o_1       136
     sky130_fd_sc_hd__a22oi_1      250
     sky130_fd_sc_hd__a2bb2o_1       1
     sky130_fd_sc_hd__a2bb2oi_1      6
     sky130_fd_sc_hd__a311o_1        1
     sky130_fd_sc_hd__a311oi_1      81
     sky130_fd_sc_hd__a31o_1        21
     sky130_fd_sc_hd__a31oi_1     9511
     sky130_fd_sc_hd__a32o_1       137
     sky130_fd_sc_hd__a32oi_1      217
     sky130_fd_sc_hd__a41o_1         4
     sky130_fd_sc_hd__a41oi_1       12
     sky130_fd_sc_hd__and2_0       222
     sky130_fd_sc_hd__and3_1       146
     sky130_fd_sc_hd__and3b_1       10
     sky130_fd_sc_hd__and4_1        19
     sky130_fd_sc_hd__and4b_1        3
     sky130_fd_sc_hd__buf_4        128
     sky130_fd_sc_hd__conb_1         2
     sky130_fd_sc_hd__dfxtp_1   216931
     sky130_fd_sc_hd__inv_1        372
     sky130_fd_sc_hd__maj3_1       729
     sky130_fd_sc_hd__mux2_1     81682
     sky130_fd_sc_hd__mux2i_1      372
     sky130_fd_sc_hd__mux4_2       512
     sky130_fd_sc_hd__nand2_1   197101
     sky130_fd_sc_hd__nand2b_1     249
     sky130_fd_sc_hd__nand3_1    10903
     sky130_fd_sc_hd__nand3b_1      25
     sky130_fd_sc_hd__nand4_1      166
     sky130_fd_sc_hd__nand4b_1       9
     sky130_fd_sc_hd__nand4bb_1      2
     sky130_fd_sc_hd__nor2_1     71297
     sky130_fd_sc_hd__nor2b_1      202
     sky130_fd_sc_hd__nor3_1      6136
     sky130_fd_sc_hd__nor3b_1       33
     sky130_fd_sc_hd__nor4_1       108
     sky130_fd_sc_hd__nor4b_1        6
     sky130_fd_sc_hd__nor4bb_1       8
     sky130_fd_sc_hd__o2111ai_1     25
     sky130_fd_sc_hd__o211a_1        8
     sky130_fd_sc_hd__o211ai_1      64
     sky130_fd_sc_hd__o21a_1        83
     sky130_fd_sc_hd__o21ai_0   212335
     sky130_fd_sc_hd__o21ba_1        4
     sky130_fd_sc_hd__o21bai_1      10
     sky130_fd_sc_hd__o221a_1       19
     sky130_fd_sc_hd__o221ai_1   33248
     sky130_fd_sc_hd__o22a_1       164
     sky130_fd_sc_hd__o22ai_1      759
     sky130_fd_sc_hd__o2bb2ai_1     26
     sky130_fd_sc_hd__o311ai_0     394
     sky130_fd_sc_hd__o31a_1         5
     sky130_fd_sc_hd__o31ai_1     1171
     sky130_fd_sc_hd__o32a_1         3
     sky130_fd_sc_hd__o32ai_1       79
     sky130_fd_sc_hd__o41ai_1       12
     sky130_fd_sc_hd__or2_0        106
     sky130_fd_sc_hd__or3_1         50
     sky130_fd_sc_hd__or3b_1        13
     sky130_fd_sc_hd__or4_1         14
     sky130_fd_sc_hd__or4b_1         3
     sky130_fd_sc_hd__xnor2_1     1531
     sky130_fd_sc_hd__xnor3_1      236
     sky130_fd_sc_hd__xor2_1       967
     sky130_fd_sc_hd__xor3_1       193

   Chip area for module '\VexRiscv': 8284565.555213

It looks to be getting stuck in ABC. Switching to the ORFS synth strategy makes it go much faster for me, it might be worth a try:
set ::env(SYNTH_STRATEGY) {DELAY 4}

I guess what's actionable here is RAM mapping..? I really recommend you just use a RAM macro though instead of just letting Yosys try to infer one...

I'm at the stage where I'm just getting an understanding of the project, and I'm making lots of obvious mistakes. I'm discovering that one of those mistakes is that relying on implicit memories like I do when designing an FPGA is not a good idea because it really blows up synthesis time.
There's a lot of documentation, so perhaps I missed something saying that's a bad thing to do.
I do agree that the lowest-hanging of fruit would be to create a set of DFFRAMs and have Yosys infer them. That would improve routing and layout for caches.
Another thing that I'm having trouble understanding is how to diagnose what the problem is. There doesn't appear to be any sort of log. All I have to go on is seeing yosys-abc at the top of my process table and the log entry "19.1.1. Executing ABC.". I'm not sure how often this is an issue, so I'm not sure how much effort should be put into diagnosing this, but how can I better understand where the bottlenecks are and how to address them? I.e. how could I have identified the caches as being the source of the long synthesis times? And is there any way to add a check for that to alert people about it before they start synthesizing?

Try ./flow.tcl -design VexRiscv -synth_explore will give PPA based on synthesis exploration. Choose the best PPA as per design requirement.
Next important thing is use of OpenRAM macros

I did try -synth_explore, but I want to say it took about eight hours to run. I'll try it again and get an exact number for you, but it'll be a few hours.
Setting SYNTH_STRATEGY to DELAY 4 did allow Yosys to finish in about 25 minutes, which is much improved! I still should find a way to extract the caches to a RAM macro. Is there any documentation on how to select a SYNTH_STRATEGY? What does it mean to prioritize area or delay? And what does the index actually mean?

Refer this: https://openlane.readthedocs.io/en/latest/reference/configuration.html#synthesis

Does a SYNTH_STRATEGY of DELAY mean that it will try to synthesize logic to have the lowest delay, whereas AREA will try to use the fewest number of logic elements? What does the index actually mean? I don't see it defined anywhere.

I asked same question #959

Does a SYNTH_STRATEGY of DELAY mean that it will try to synthesize logic to have the lowest delay, whereas AREA will try to use the fewest number of logic elements? What does the index actually mean? I don't see it defined anywhere.

While that may have been the original intent, it's basically just different ABC scripts, and I'm not convinced a lot of thought has gone into them.
I've found DELAY 4 (the strategy that came from ORFS - OpenROAD-flow-scripts) has produced the best results on a number of my designs. That includes it completing much quicker, hence why I suggested giving it a go.

In general it is hard to predict what script will produce the best results on a given design.  The script names should suggest the common outcome (delay or area minimization) though on any given design it will vary.
I think reporting the problem to abc makes sense.

Try ./flow.tcl -design VexRiscv -synth_explore will give PPA based on synthesis exploration. Choose the best PPA as per design requirement. Next important thing is use of OpenRAM macros

I don't think that -synth_explore is very useful here:
[SUCCESS]: Done with synthesis exploration: See report at 'runs/RUN_2022.12.01_15.25.24/reports/synthesis/0-exploration_analysis.html'.

real    4504m8.770s
user    4260m7.903s
sys     13m23.285s
(pyenv) $

The good news is that DELAY 1 produced the best result. The bad news is that it took 3.1 days to get the result. -synth_explore looks like it actually runs the synthesis 10x, and is therefore not very useful when the thing you want to optimize is the synthesis itself.
As far as actionable things go:

Perhaps a FAQ entry can be added about the synthesis / yosys-abc step taking a long time, asking users to check for memories?
Maybe the default flow.tcl could add a memory_libmap step? I've created https://github.com/VLSIDA/OpenRAM/issues/163 to try and get this.
Related to (2), perhaps a dummy memory_libmap step could be added that does nothing but error out on inferred memories, suggesting users wire up their own RAMs explicitly. I get that it's generally a good idea to do that, but making it explicit (along with an override to use logic for RAM) might be useful for newcomers to let them know that something funny is going on.

Maybe the default flow.tcl could add a memory_libmap step? I've created Create yosys memlib mapping VLSIDA/OpenRAM#163 to try and get this.

While this is a great long term aim, keep in mind that OpenRAM needs to characterised on every new process (via a shuttle) so it would likely be a non default option (even sky130hd at this stage).
We could however work on adding DFFRAM based macros now, since they are just standard cell based. Vendor SRAM macros are another possibility (the GF180 PDK has them for example).

I don't think that -synth_explore is very useful here:

Did the log file show how long DELAY 4 took? If it's much faster then it's another data point for changing the default synth strategy.

It doesn't look like the logfiles include any sort of timestamp, so I can't tell. Furthermore, yosys cleans up its /tmp/yosys-abc-xxxxxx directory, so I can't look at the timestamps for the temp files.
In looking at the generated files, I suspect this means that DELAY 4 is indeed fastest:
$ ls -l results/synthesis/ logs/synthesis/
logs/synthesis/:
total 47568
-rw-r--r-- 1 user user 48707526 Dec  4 18:29 0-synthesis.log

results/synthesis/:
total 1381288
-rw-r--r-- 1 user user 161679010 Dec  3 15:32 VexRiscv.AREA_0.nl.v
-rw-r--r-- 1 user user 156315215 Dec  4 03:38 VexRiscv.AREA_1.nl.v
-rw-r--r-- 1 user user 156328097 Dec  4 18:16 VexRiscv.AREA_2.nl.v
-rw-r--r-- 1 user user 171204295 Dec  4 18:29 VexRiscv.AREA_3.nl.v
-rw-r--r-- 1 user user 159082635 Dec  1 21:07 VexRiscv.DELAY_0.nl.v
-rw-r--r-- 1 user user 141429117 Dec  2 09:14 VexRiscv.DELAY_1.nl.v
-rw-r--r-- 1 user user 156176367 Dec  2 19:27 VexRiscv.DELAY_2.nl.v
-rw-r--r-- 1 user user 163662714 Dec  3 07:53 VexRiscv.DELAY_3.nl.v
-rw-r--r-- 1 user user 148509841 Dec  3 08:12 VexRiscv.DELAY_4.nl.v
$

I think DFFRAM macros could be a great addition, particularly for helping newcomers to avoid pitfalls like the ones I've fallen into.


Health Check for Elastic Search and RabbitMQ

Extension methods for checking health of RabbitMq and ElasticSearch.

        public void ConfigureServices(IServiceCollection services)
        {
            Metrics.HealthChecks.RegisterFromAssembly(services).BuildAndAddTo(services);
            services.AddHealth(Metrics);
            services.AddHealthEndpoints();

            //RabbitMqHealthCheck Usage
            services.AddRabbitMqHealthCheck("RabbitMq", "rabbitmqbaseurl/api/healthchecks/node", 3, "username", "password"); //username and password are optional

            //ElasticSearchHealthCheck Usage
            services.AddElasticSearchHealthCheck("ElasticSearch", "elasticbaseurl/_cluster/health", 3, "username", "password"); //username and password are optional
        }

        public void Configure(IApplicationBuilder app)
        {

            app.UseHealthAllEndpoints();
        }

What do you think?

LGTM 👍


feat: lint on isolated where and leading by

Extend the style linter with two tiny features:

lint on "isolated where": all occurrences were already fixed in #12991 and #13202.
lint on "leading by": if one line starts with by  but the previous line ends with :=, according to the style guide the by should move to the previous line. For now, we only lint if the by fits on the previous line (fixed in #13618 and predecessors): there about other 28 cases in mathlib which don't have an obvious fix.

This looks reasonable to me, thanks! Delegating in case there are any errors introduced since the last update.
bors d+

Thank you for the review! There was one new occurrence, which I have just auto-fixed.
bors r+


Documentation update for jaxon.getFormValues

The documentation for jaxon.getFormValues does not mention the second and third parameters.  The second parameter is a bool, and if set to true includes disabled form fields.  The third parameter is string prefix, and only form fields matching the prefix will be included.  These parameters were carried over from xajax.
I would also like to point out that in xajax and jaxon up through version 3, the syntax jaxon.getFormValues('id', 1) worked for submitting disabled form fields.
In version 4, the above syntax does not submit disabled form fields.  It only submits disabled fields using the syntax jaxon.getFormValues('id', true)
This is not a bug report, just a request to possibly mention this in the "Migration from version 3" documentation.  If the older syntax is being used and you update jaxon from v3 to v4 without knowing about this change, it could result in data loss when disabled form fields that were previously submitted are no longer being submitted.

Hi,
I made a change related to this issue in the 4.0.6 release.
You can now call jaxon.getFormValues('id', 1) as well as jaxon.getFormValues('id', true).


[BUG] Store n_timepoints and n_channels in fit to check in transform

fixes #1712
Stores the length of the first series and number of channe;ls in the metadata in fit, which is then checked against the series length/number of channels  in predict and predict proba. Note

Because of the number of supported data types, best way is to call a method get_n_timepoints/n_timepoints in validation
For variable length data structures it just looks at the length of the first element, and does not do the test if the classifier has unequal_length capability. If the collection is in fact unequal length, then it fails before here. Only case is where it is in an np-list but they are all in fact equal length. This tests if that common length is different to that seen in train
n_channels only checked for multivariate capable classifiers
will move the checking function up to base collection estimator because it is common to all collection estimators

Code LGTM, but wouldn't we need to apply this to other base classes like fitted transformations ? And in such cases shouldn't we consider the axis parameter in the get_n_channels and get_n_timepoints methods ?

yes it should be in other estimators, but I thought I'd get approval for doing it like this before doing the other collection estimators. I will do them when this is in. Axis is not an issue with collection estimators, we always assume (n_cases, n_channels, n_timepoints),


Pretty print JSON files, and terminate with newline

Text files that don't end with a newline can be troublesome or unacceptable in some contexts.
The only down side is a bit of merging hassle for existing pull requests. But that happens anyways, and of course the YAML file is authoritative so JSON conflicts can be ignored in practice.

Looks fine to me.
(It would also be nice to have some kind of human-friendlier printing of the generated JSON, because currently it is painful for implementations that use the JSON to locate the source of a test failure within the big generated one-liner.)

Yes, @gasche, good point. I found how to do that. Its default looks pretty good, I think.

Very nice! Thanks.

I'm a tiny bit hesitant to merge this since all other pull requests would need to be re-run. I'll merge a few and then come back to this one.

I am very much in favor of the quality-of-life and readability improvement this provides! I merged a few active pull requests, can you go ahead and re-generate the json?

I force-pushed an update of the specs/*.json files.

Thanks!


feat: new command for inspecting state-root mismatches

Summary of changes

Changes introduced in this pull request:

forest-tool archive diff replaces forest-cli state diff.
The new command is more ergonomic and doesn't require copy&pasting CIDs.

Example output (with Forest modified to use an incorrect base-fee):
$ forest-tool archive diff forest_snapshot_calibnet_2023-10-11_height_989049.forest.car.zst --epoch 989000
- Expected state hash: bafy2bzaceaujrn4wf72j6ojgnka47lkdxzttxv22brjteaexs76vtgfptebfe
+ Computed state hash: bafy2bzacecgggv4fd27pfs3xzxg764kcaj6otf5sar5ypt7r22qn66xmotb74
Address t099 changed:
 ActorState(ActorState { code: Cid(bafk2bzacebor5mnjnsav34cmm5pcd3dy4wubbv4wtcrvba7depy3sct7ie4sy)
  state: Cid(bafy2bzacedpuk5ggwoq3s2wixsyjjnexpsjstdlyntio76vs2lt2jvy3o6mau)
  sequence: 0
- balance: TokenAmount(13369711.247500476309337237)
+ balance: TokenAmount(13369711.247500461221402237)
  delegated_address: None })
V11(State { address: Address { payload: ID(99) } })
Address t035181 changed:
 {
  "code": {
    "/": "bafk2bzacedrbpvjvyzif2cjxosm4pliyq2m6wzndvrg7r6hzdhixplzvgubbw"
  }
   "sequence": 33965
-  "balance": "165.580950032976185226"
+  "balance": "165.580950048064120226"
   "state": []
}

Reference issue to close (if applicable)

Closes #3586
Other information and links
There is no testing since there are no convenient ways of triggering state-root mismatches.
Change checklist

[x] I have performed a self-review of my own code,
[x] I have made corresponding changes to the documentation,
[x] I have added tests that prove my fix is effective or that my feature works (if possible),
[x] I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

Can you contrive some test cases, or would that be too time-consuming or complex?

I have no idea how to test this. We have tests for pretty-printing diffs but I don't see an easy way of doing end-to-end testing.

Looks good to me. As a follow-up would be great to have this tool more exposed by means of public-facing docs.
There are also no tests, but it's not a blocker.


Updated Swedish translation

Added some new strings and fixed a couple of typos in the previous translation. 😊

@marcusforsberg Sorry for my late response. Thank you for this. Will merge in now for the next release.


iterate on toasts

because i wanted to use toasts in DCOS-UI and was interested in how stuff works, i played around with some code and thought it's worthwhile to share the results.

@pierrebeitz , the lint check is failing.

thanks for having a look, @GeorgiSTodorov!

Not related to this PR, but "with dismiss callback" doesn't seem to do anything.

i think there should be a message in the "actions"-panel when you click dismiss. is that not working?

i think there should be a message in the "actions"-panel when you click dismiss. is that not working?

I don't remember if I checked there, I was expecting either an alert or a console.log.

@mperrotti addressed your feedback. i'd hit the button, but am not sure about what the conventions in ui-kit are. would it be ok to self-merge if there's only been small changes and like 3 people approved before?

@pierrebeitz - it's ok to self-merge :)


Fix krb5 external test

Since commit c3845ceba84aab9ddeb43f043549238fd10de63b ("Build file
templates: don't set OPENSSL_{ENGINES,MODULES}") the krb5 external test
has been failing.  This is because it relied on OPENSSL_MODULES already
being set -- even though it did assign to OPENSSL_MODULES itself (and
thus got skipped by the cleanup pass in that commit), it was doing so
only to canonicalize the existing value to an absolute path, not as a de
novo assignment.
Catch up to the rest of the tree and just set it directly as the
"providers" path from the build top (but still canonicalized to an
absolute path).
[extended tests]
Fixes: 11492

The Travis failure is the usual timeout fixed with #11468.

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

Pushed to master; closing.


Vimeo Videos with Captions show HUGE captions on the Vimeo player "underneath" plyr

Expected behavior
Captions on the Vimeo embed should not be shown in favor of the captions built-in to the plyr.
Actual behavior
Captions are shown on both players and the Vimeo player's captions cannot be disabled and are also gigantic and fill the screen.
Steps to reproduce

Use a Vimeo video that has captions with Plyr.
In both Safari or Chrome, this issue occurs on SOME of the captions but not all. I imagine that some of the shorter lines get hidden, but the longer lines of text become visible?

Environment

Browser: Safari
Version: 13.1.1
Operating System: macOS Catalina
Version: 10.15.5

Link to where the bug is happening
https://jacklink.productions/video/256150842

I think Vimeo doesn't allow playback without their captions. (Not sure if a Pro account allows you to do this??)
I'm working on a partial workaround:
.plyr__video-wrapper.plyr__video-embed {
width: 10px;
transform-origin: 5px 0px;
overflow: visible;
transform: scale(32);
}
... the scale(N) value would need to match your player width / 10px
It basically forces the video to play in the 10px gap at the left of the captions(!), then scales it back up.
Vimeo controls need to be disabled (from Vimeo plugin controls in Plyr options).

Thanks for your help and thanks for pointing out the duplicate. I searched around, but couldn't find one!


Correct Lise Meitner's name, add Euler

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "meitner" git@github.com:janten/docker.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "meitner" git@github.com:janten/docker.git somewhere
$ cd somewhere
$ git rebase -i HEAD~2
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

Actually, looks like "meitner" is now in the list twice; https://github.com/docker/docker/pull/17155/files#diff-a461eecf31e5c471572678b08330893aR329. Possibly a bad rebase somewhere.
Can you fix that, and remove the duplicate? Thanks!
Also, we like this list to be balanced and like to have both a man and woman added in each change, could you come up with one?

I've added Emmy Noether, too.

Thanks, excellent choice! Oh (apologies, I overlooked that); can you squash your commits? We like to have changes grouped in logical commits; for most PR's that means only a single commit.
If you need help with squashing, please refer to the contribution guide, which contains some examples on that; https://docs.docker.com/project/work-issue/#pull-and-rebase-frequently
LGTM after the commits are squashed

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "meitner" git@github.com:janten/docker.git somewhere
$ cd somewhere
$ git rebase -i HEAD~7
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

LGTM


Allow "Required: False" on Response headers - Fix #1261

Fixes #1261
Changes proposed in this pull request:

Allows response headers to have required: False without NonConformingResponseHeaders error

Coverage remained the same at 96.878% when pulling 96bfdb1c1aedcadda7a1472e7bce2041ea63c0e9 on miguelgf:master into 1ed14fbde5be3d144760fec4982e90064f151e88 on zalando:master.

Hello @jmcs
Any change this gets reviewed and merged? I would like to use in a project and we will need to fork the project to support our required: false on our openapi specs
Regards

@Ruwann rebased against main 👍

It seems that your code was correct, but another test failed because, imo, the test itself is incorrect.
For OpenAPI 3, it is clearly in the spec what the expected behaviour for optional and required headers is, but it is not very clear for Swagger 2. This issue (https://github.com/OAI/OpenAPI-Specification/issues/321) and this response (https://github.com/OAI/OpenAPI-Specification/issues/321#issuecomment-89958502) seem to indicate that that the response headers in Swagger 2 are optional.
In OpenAPI 3, when the required field is not present in the header, it should be considered false. So you can revert that last change.
If you are up for it, you can adjust the corresponding test and swagger/openapi. But I'm also happy to do it myself in a PR to your branch or in a follow-up PR.
https://github.com/zalando/connexion/blob/c014299435990ff1d4c20596396ca563f7b266b4/tests/api/test_headers.py#L20-L30
https://github.com/zalando/connexion/blob/c014299435990ff1d4c20596396ca563f7b266b4/tests/fixtures/simple/swagger.yaml#L559-L572
https://github.com/zalando/connexion/blob/c014299435990ff1d4c20596396ca563f7b266b4/tests/fixtures/simple/openapi.yaml#L704-L720

@Ruwann feel free to change the code, I won't be able to make any changes until late today. Thanks!

@Ruwann I've reading what you sent and I see the issue, yes, the test is not testing the proper behaviour, but we can't test it on the Swagger 2, as there is no way to say that a header is required with the Header Object specification (https://swagger.io/specification/v2/#headerObject).
This test can be perform on openapi 3, on swagger 2 this test has no sense (every header is always optional, based on their specification).
We can change the test so it only pass on OpenAPI 3 and we don't pass it on Swagger 2, what do you think?

Thanks @Ruwann and @hjacobs !!


Revert "Revert "cronet wrapper code"", and fix the issue with build.yaml

It looks fine to me.
@ctiller , any objections?

LGTM
On Thu, May 12, 2016 at 8:56 AM Jan Tattermusch<EMAIL_ADDRESS>wrote:

It looks fine to me.
@ctiller https://github.com/ctiller , any objections?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/6553#issuecomment-218802017


Put decorators on the same line

Mobx is the only popular JavaScript library that I know about which uses decorators. They put things on the same line so we should follow their conventions.
The logic implemented here is the following: if there is one decorator, it's on the same line. If there is more than one, they are each on their own line.
Fixes #325

redux connect can also be used with a decorator. But the decorator is placed above the class.

@vramana good call! It seems like redux connect takes arguments. We likely don't want decorators with arguments to be inlined. Let me encode this rule as well!

Done, now it has to be a single decorator AND just an identifier to be inlined.
I also tried to enable flow decorator support but it only supports half of the decorators in the tests and has a different AST structure, so it's not worth using it.

Thanks, looks good!

Is there a possibility to make this configurable? I personally really dislike decorators being in the same line. Makes it very hard to browse the class properties.
  @Entity("Todos")
  export class Todo implements ITodo {
    @PrimaryGeneratedColumn("uuid") public id?: string;
    @Column() public text: string;
    @Column() public completed: boolean;
  }

@jlongster @vjeux @vramana I agree highly with @egeozcan -- would love to see this be a configurable value. If I submit a PR, would the team be up for merging it or is everyone set on keeping things as is?

+1. This is very annoying, especially with Inversify.
public constructor(
    @inject(MyStoreStore) public readonly myStore: MyStore,
    @inject(InjectionTypes.StyleProvider) public readonly styleProvider: IStyleProvider,
) { }

Relevant issue: #1974

@JoshuaKGoldberg Please open a new issue, filling the template


Bye Bye ryd box, OBD adapter will stop working

Repo will be archived on 30.04. as RYD will stop supporting the OBD adapter:
Bye Bye ryd box

Do we have any alternatives?

I'm looking into Traccar. Hesitant because of the costs for two obd dongles


MVCKrazoExtension should report its stability level as 'preview'

The current target stability level of the mvc-krazo extension and subsystem in a WildFly installation is 'preview'. For the 0.x releases the extension did not report this (via Extension.getStability()), but for 1.0 it must.
(For the 0.x releases there were technical issues within the WildFly Galleon Plugin that prevented reporting the stability level.  I was ok with the extension not reporting this, because 1) 0.x releases IMO are typically regarded as lower stability, and 2) the main use of those releases was content incorporated in the wildfly-preview feature pack, which itself is generally regarded as providing tech preview content.)

See also https://issues.redhat.com/browse/WFLY-19062


the alphabetic order in the code influence console_output.

Just compile and run the code,my english is poor ,so please see the attach picture.

What do you mean? The keys of the objects are always sorted.

Can you provide more information?


window + flat_map fails on dataset of tuples

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes.
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10 Home edition
TensorFlow installed from (source or binary): pip install tensorflow-gpu
TensorFlow version (use command below): b'v1.12.0-rc2-3-ga6d8ffae09' 1.12.0
Python version: 3.6.7
CUDA/cuDNN version: Cuda compilation tools, release 9.0, V9.0.176, CuDNN 7.4.1, I believe
GPU model and memory: NVIDIA GTX 1070, 8 GiB memory (maybe 6, as TF is a bit unclear on that point)

Describe the current behavior
On a range dataset, window followed by flat_map works as expected, but on a dataset of tuples (originally encountered using a CSV dataset), flat_map fails, complaining that the input argument to the mapped function has multiple components.
Describe the expected behavior
I expected flat_map to treat the windows as datasets, allowing me to perform dataset operations such as batch on them.
Code to reproduce the issue
#Simple window batch test
import tensorflow as tf
data = tf.data.Dataset.range(0,10)
data = data.map(lambda *x: (x[0],x[0]+1))
#Each entry is now a tuple of (n,n+1)
#Without the mapping to tuple, window+flat_map works.
data = data.window(3)
#Each entry is now a window dataset
#map fails, because the dataset is nested
#data.map(lambda x: print(x))
#flat_map fails because x is a tuple, not a dataset
data = data.flat_map(lambda x: x.batch(3))

Other info / logs

Traceback (most recent call last):
File "window_batch_test.py", line 14, in
data = data.flat_map(lambda x: x.batch(3))
File "C:\Users\elias\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python\data\ops\dataset_ops.py", line 1070, in flat_map
return FlatMapDataset(self, map_func)
File "C:\Users\elias\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python\data\ops\dataset_ops.py", line 2677, in init
experimental_nested_dataset_support=True)
File "C:\Users\elias\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python\data\ops\dataset_ops.py", line 1860, in init
self._function.add_to_graph(ops.get_default_graph())
File "C:\Users\elias\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python\framework\function.py", line 479, in add_to_graph
self._create_definition_if_needed()
File "C:\Users\elias\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python\framework\function.py", line 335, in _create_definition_if_needed
self._create_definition_if_needed_impl()
File "C:\Users\elias\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python\framework\function.py", line 344, in _create_definition_if_needed_impl
self._capture_by_value, self._caller_device)
File "C:\Users\elias\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python\framework\function.py", line 864, in func_graph_from_py_func
outputs = func(*func_graph.inputs)
File "C:\Users\elias\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python\data\ops\dataset_ops.py", line 1794, in tf_data_structured_function_wrapper
ret = func(*nested_args)
TypeError: () takes 1 positional argument but 2 were given

The (regretably) deprecated sliding_window_batch seems to work, though. It is much more convenient for my purposes to just get the windows as batches.

This works as intended. If the input to window, is a dataset of nested elements, then the output of window will be a dataset of nested datasets of (flat) elements.
import tensorflow as tf

tf.enable_v2_behavior()

data = tf.data.Dataset.range(0,10)
data = data.map(lambda *x: (x[0],x[0]+1))
data = data.window(3)
data = data.flat_map(lambda x, y: tf.data.Dataset.zip((x.batch(3), y.batch(3))))

for elem in data:
  print(elem)

produces
(<tf.Tensor: id=35, shape=(3,), dtype=int64, numpy=array([0, 1, 2])>, <tf.Tensor: id=36, shape=(3,), dtype=int64, numpy=array([1, 2, 3])>)
(<tf.Tensor: id=39, shape=(3,), dtype=int64, numpy=array([3, 4, 5])>, <tf.Tensor: id=40, shape=(3,), dtype=int64, numpy=array([4, 5, 6])>)
(<tf.Tensor: id=43, shape=(3,), dtype=int64, numpy=array([6, 7, 8])>, <tf.Tensor: id=44, shape=(3,), dtype=int64, numpy=array([7, 8, 9])>)
(<tf.Tensor: id=47, shape=(1,), dtype=int64, numpy=array([9])>, <tf.Tensor: id=48, shape=(1,), dtype=int64, numpy=array([10])>)

Thank you for answer, and for providing what appears to be a way to solve the problem. I suppose that for a dataset with many columns the expression would be something like:
data.flat_map(lambda *x: tf.data.Dataset.zip((col.batch(batch_size) for col in x)))

which I will test soon. :-)
What I don't get is that x cannot just be batched directly. x is a tuple, but was supposed to be a dataset. (flat_map doc says that it applies the function to every element (dataset), and then flattens the result (packing out the datasets). It should at least be a custom tuple with dataset methods added, as far as I can tell.
The old sliding window batch works well. And, while perhaps being less flexible, it solves a common valid usecase that should not be made less available. The "instructions for updating" that show up in the terminal when I use sliding_window_batch says nothing about the trick you gave me here, and the recommended solution does not work.
To conclude, I think this issue should not be closed yet. But thank you again for providing a workaround.

What about dict, e.g when the input to window() was already a dictionary? flat_map behaves unintuitively here and doesn't get the job done.


Update Beacon endpoint according to specification

Description
Update Beacon endpoint according to the specification: add support to imprecise structural variants (imprecise start and end locations) and an option to search variants in different datasets.
Use case
Beacon specification supports datasets, this update is necessary to support that functionality.
Benefits
More options to query variants.
Possible Drawbacks
The output of old queries is different, this may create a few problems for users.
Testing
Updated old tests according the new output.
Added new tests to make sure new options are available.
Run all tests and no regression detected.
Changelog
Old queries still work however their outputs have some differences.
New input options to search for variants. The new options affect:
ga4gh/beacon (only output affected)
ga4gh/beacon/query

Coverage increased (+0.009%) to 44.299% when pulling c68370b290a3efa2b377cb319bc5edded110ef81 on dglemos:beacon/update_spec into 2b58470f802a3725488246300f2512e550c026c3 on Ensembl:master.


Qubit mapping seems to account only for CNOTs and not other two-qubit gates

As far as I can tell, the SwapShort, aka "swap-shortest-path", IRTransformation considers only CNOTs and not other 2-qubit gates such as CZ. Please see the example cz_repro.cpp below:
__qpu__ void kaboom(qreg q) {
    X(q[0]);
    H(q[2]);
    CZ(q[0], q[2]);
    H(q[2]);
    Measure(q);
}

int main() {
    set_shots(64);
    set_verbose(true);

    auto q = qalloc(5);
    kaboom(q);
    q.print();
}

The CZ there is operating on qubits 0 and 2, which I chose because they are not directly connected in the coupling graph of the IBM backend I am targetting:

If you run this, IBMAccelerator correctly notices that the program has a 2-qubit gate on non-adjacent qubits:
$ qcor -qpu ibm:ibmq_lima cz_repro.cpp -o cz_repro
$ ./cz_repro
0x7f3f7670387d: (xacc::error(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::function<bool ()>)+0x2b)
0x7f3f61d0277c: -- error: unable to obtain symbol name for this frame
0x7f3f61d04876: (xacc::quantum::IBMAccelerator::execute(std::shared_ptr<xacc::AcceleratorBuffer>, std::vector<std::shared_ptr<xacc::CompositeInstruction>, std::allocator<std::shared_ptr<xacc::CompositeInstruction> > >)+0x4be)
0x7f3f61d01f8e: (xacc::quantum::IBMAccelerator::execute(std::shared_ptr<xacc::AcceleratorBuffer>, std::shared_ptr<xacc::CompositeInstruction>)+0xca)
0x7f3f76bab6d4: (xacc::internal_compiler::execute(xacc::AcceleratorBuffer*, std::shared_ptr<xacc::CompositeInstruction>, double*)+0x16c)
0x7f3f6d7a5a2a: (qcor::NISQ::submit(xacc::AcceleratorBuffer*)+0x360)
0x7f3f76bdc131: (quantum::submit(xacc::AcceleratorBuffer*)+0x38)
0x40b3f2: (kaboom::~kaboom()+0x302)
0x40995b: (__internal_call_function_kaboom(xacc::internal_compiler::qreg)+0x4b)
0x4098d1: (kaboom(xacc::internal_compiler::qreg)+0x21)
0x409ab6: (main+0x56)
0x7f3f756e40b3: (__libc_start_main+0xf3)
0x4097de: (_start+0x2e)
terminate called after throwing an instance of 'std::runtime_error'
  what():  Invalid logical program connectivity, no connection between [0,2]
Aborted (core dumped)

If we change that kernel to this instead, swap-shortest-path correctly swaps qubits as needed, and it runs successfully:
__qpu__ void kaboom(qreg q) {
    X(q[0]);
    CNOT(q[0], q[2]);
    Measure(q);
}

My guess is this is because the visitor inside staq itself is looking only for CNOTs and simply ignores the CZ:
https://github.com/eclipse/xacc/blob/f83e1825735c937686c4c04ba71ea37fbdd42b51/tpls/staq/include/mapping/mapping/swap.hpp#L84
Is this expected behavior? If not, how would this be fixed? Decompose two-qubit gates before they reach swap-shortest-path, or make it aware of other two-qubit gates, or something else? (I don't know which is why I'm opening this)

Hey @ausbin this is not expected behavior. Basically we aren't letting staq translate the program to native U and CX gates, the CZ is sticking around, and then the visitor doesn't pick it up. I'll work on a fix.

I think I'm going to have to write a custom staq AST visitor for this I think. In the meantime you can just use the following replacement
__qpu__ void MyCZ(qubit q, qubit r) {
    H(r);
    X::ctrl(q,r);
    H(r);
}

__qpu__ void kaboom(qreg q) {
    X(q[0]);
    H(q[2]);
    MyCZ(q[0], q[2]);
    H(q[2]);
    Measure(q);
}

If you compile this with -opt 1 you'll get rid of the Hadamards.

Nevermind, don't need a visitor, the staq Inliner takes extra config parameters that can fix it. Got a fix coming into XACC for this.

fixed with xacc f1eedf04176b68241f6dc7dddaa5ae7453662da9


Migration to and from filesystem can have issues with underscores

I have vault backed by consul which I am migrating to filesystem for backup purposes.
If my vault kv has a key named foo and a folder named _foo... both want to become _foo on the filesystem so I get a _foo is a directory error when running vault-migrator.
Since vault is okay with foo and _foo, is there some way to configure the consul file backend to make it handle this case?  Do you have any advice that isn't: "don't do that, silly!"  :-)
My config.json for vault-migrator --config config.json:
$ cat backup.json
{
    "to": {
        "name": "file",
        "config": {
            "path": "/Users/jar349/projects/vault-backups/data"
        }
    },
    "from": {
        "name": "consul",
        "config": {
            "address": "localhost:8500",
            "path": "vault/"
        }
    }
}

hi @jar349, not much to say.  my only suggestion is to name differently keys and folders.  is unfortunate that you have that issue, the script only has a job to copy the keys. unfortunately, I have not much time available to fix any incompatibility between backends.

In your opinion, where should a fix for this be made?  Here, or in the consul file backend implementation?


build-source: reorganize to emphasize only on CiV and CiC

Separate sections for CiV and CIC build instructions.
Signed-off-by: Tonny Tzeng<EMAIL_ADDRESS>

@swaroopbalan PTAL on the requested editing.

Please change Build the OS image >> Build the CAAS image

Build the OS image >> Build the CAAS image


Dev/fix delete model

Delete items in registry
Warn users that when deleting a version it will also delete any associated deployments

When all versions deleted for a model, also delete docker registry name space (currently only the tags/containers are removed)


[Internal] [Test] Add Separate CI For Dev Branch

Please Provide a Description of the Testing Request.
Place an :x: in a Box that Best Matches the Test Request's Importance:

[X] 1 - Urgent (absolutely integral and core-functionlaity of the codebase is completely compromised without this test)
[] 2 - Most Important (codebase can be used for some core-functions but the test needs to be executed for some)
[] 3-4 - Moderate (codebase can be used for all core-functions but the test needs to be exexcuted for some other ones)
[] 5 - Least important (would like to see but there are no stringent expectations nor urgency for current/future use-cases)

Any Additional Context or Information? Has There Been Any Progress Made So Far Towards this Request? Any Helpful Resources to Reference? Screenshots or Links?
N/A

Refactoring to the python scripts containing tests and the workflow needs to be changed.
Production (master) = Uses test_main.py to run general end-to-end tests in Nextflow + checking outputs with a full-run (to test across all features associated with an enhancement). These tests are called through a separate workflow .yml file with the merge condition into main (therefore staging into main or hotfixes).
Staging (dev) = Uses a separate python script for calling unit tests, by importing enhancement / bug fix specific tests and running it. These tests are called through a separate workflow.yml file with a merge condition into dev (any time a PR is opened into the dev branch).


no space outside of table causes it to always float (cover first rows)

If there are no pixels (body margin:0px, padding:0px, etc) between the top of the page and the table, setting the table to windowscroll always triggers the floating condition which means the first row(s) are always partially hidden.
I fixed this for my case (window scroll, absolute) by simply changing the > to >= in line
https://github.com/mkoryak/floatThead/blob/5e5f08069835fb214de8174d4e213d8a4e2b0f8b/dist/jquery.floatThead.js#L618
I'm going to guess that the arithmetic is similar for other scrollings.

Thanks for finding the fix. Do you mind throwing up a jsfiddle that demonstrates this bug so I can have something to test against?

http://jsfiddle.net/9eo8gjag/
Change the body css from margin 0 to margin 1.
There exists a second obvious problem in the posted fiddle, however. Even after changing the margin to 1, scrolling at all completely breaks the arrangement.

I see your clever trick to get around the error you would get when you run this plugin on a table which does not have a thead. this is what causes it to fail on reflow, see update:
http://jsfiddle.net/9eo8gjag/1/
I see the bug that you outlined, thanks. Ill have a fix soon

I had a thead, but you are right I accidentally did not have a tbody tag! (oops. that is a mistake that is not present in my project though).
Updated.
http://jsfiddle.net/9eo8gjag/2/
Is it thus necessary to have a tbody defined before calling floatThead?
Compare
http://jsfiddle.net/9eo8gjag/3/

Oops. Actually update 2 is not what I meant to show. I'm doing a terrible job of cutting down the one I have from before...hold on...

Here. (finally, I think?)
Compare http://jsfiddle.net/9eo8gjag/4/ with http://jsfiddle.net/9eo8gjag/3/

yep, that looks like a bug to me. Ill get a fix in for it soon

Reflow after adding tbody doesn't seem to help.
http://jsfiddle.net/9eo8gjag/5/

nice, i see a different bug here that ive been trying to fix for a while but didnt have a good way to reproduce:  http://jsfiddle.net/9eo8gjag/6/
thanks for the reports.

Sorry if this is abusing the issue queue, but is your other bug the different scrolling behavior where the tbody jumps when you start scrolling if it's not created before the first floatThead and scrolls smoothly if declared before?
( scrolling behavior http://jsfiddle.net/9eo8gjag/7/  vs  http://jsfiddle.net/9eo8gjag/6/ )
I can make a new issue if you want. I know the thread is diverging.

my other bug is that floatThead does not init itself properly after you add the body. remove the plugin code and you will see that the table should be much wider after you stick that html into it.

Heh, you are in sommerville, I am in JP. small world :)
your original issue should be fixed on master. I made the change you suggested.
I just noticed the scrolling/jumping bug you pointed out. I think you are the first person add a tbody after plugin init, but I think its a valid usecase and should work. If you want to make a new issue that would be great.
I will probably make a 3rd issue for myself with the size thing, but that one is going to be hard to fix.

I moved both bugs into #186 because they turned out to be related. closing this


[Original, draft] Add Elrond coin

Description
Extended Wallet-core with blockchain & coin Elrond.
Testing instructions

interacting with walletconsole
running the tests

Types of changes

New feature (non-breaking change which adds functionality)

Checklist

[ ] Prefix PR title with [WIP] if necessary.
[x] Add tests to cover changes as needed.
[ ] Update documentation as needed.
[ ] If there is a related Issue, mention it in the description (e.g. 'Fixes #444 ).

New blockchain checklist

[x] Add the coin definition to coins.json.
[x] Add coin dispatcher to src/Coin.cpp
[x] Create tests in tests/Elrond/TWCoinTypeTests.cpp
[x] Implement Entry.cpp
[x] Implement Address.cpp
[ ] Implement Transaction.cpp if necessary. Was not necessary.
[x] Implement Signer.cpp
[x] Write test: mnemonic phrase - > Address derivation test. Put this test in CoinTests.cpp TWHDWalletTests.cpp.
[x] Transaction signing tests, at least one mainnet transaction test.
[ ] Add stake, unstake, get rewards tests if the blockchain is PoS like. Will be added later in time.
[ ] Implement C interface in src/interface Not applicable.
[x] Add tests for TWAnyAddress
[x] Add tests for  TWAnySigner
[x] Add tests in ElrondTests.swift
[x] Validate generated code in Android project. Write integration tests. Maiar Android Wallet.
[x] Validate generated code in iOS project. Write integration tests. Maiar iOS Wallet.
[x] Extend test: CoinAddressDerivationTests.cpp
[x] Extend test: CoinAddressValidationTests.cpp
[x] Extend test: TWHRPTests.cpp
[x] Extend test CoinAddressDerivationTests.kt
[x] Extend test CoinAddressDerivationTests.swift
[ ] Upload coin icon to trustwallet/assets if necessary.

We can close this PR, the official one is against the parent repository.


link swift-nio-extras in docs

@swift-nio-bot test this please

needs a PR like apple/swift-nio-extras#86

All three builds timed out during the build process.

@swift-nio-bot test this please

14:25:57 Running test suite 'tests_02_allocation_counters'
14:25:57 Running test 'test_01_allocation_counts.sh'... Build timed out (after 20 minutes). Marking the build as failed.
14:31:03 $ ssh-agent -k

@swift-nio-bot test this please

@swift-nio-bot test this please


AMWSUP-7 Ansible MW: Update Flange project to use the latest version …

Issue: https://github.com/ansible-middleware/flange-demo/issues/50

@RanabirChakraborty where are we on this? I can see the PR is still failing, but I'm not sure if you are waiting on something or if you are working on it :)

@RanabirChakraborty I took a look and the issue is that keycloak is not starting propery. My advice would be to add a slurp: tasks to print out the content of the keycloak log, see why it's failing to start.

@rpelisse I actually forgot that keycloak is not supported by wildfly 27. Now it's working fine. Can you please review it now?


Auto scale down doesn't work when plan of address is changed

Description:
When new address with broker.resource=2.0 is created and plan of this address is changed (in ConfigMap) to another plan with broker.resource=1.0 then StatefulSet is not scaled down to 1 replicas.
Reproducer:
Reproducible via automated test in issue-1123-manual-scale-down branch (Will be soon disabled and merged with master)
make SKIP_CLEANUP=true MULTITENANT=true systemtests SYSTEMTEST_ARGS="PlansTest#testMessagePersistenceAfterChangePlan"
Output in standard-controller seems to be correct:
018-04-10 10:15:41 INFO  AddressController:107 - Total: 1, Active: 1, Configuring: 0, Pending: 0, Terminating: 0, Failed: 0
2018-04-10 10:15:41 INFO  AddressController:121 - Usage: {broker={distributed-queue={used=2.0, needed=2}}}, Needed: {broker={distributed-queue={used=2.0, needed=2}}}
2018-04-10 10:15:41 INFO  AddressController:153 - total: 160671818 ns, resolvedPlan: 60966 ns, calculatedUsage: 513646 ns, checkedQuota: 278396 ns, listClusters: 36928714 ns, provisionResources: 32433 ns, checkStatuses: 122754527 ns, deprovisionUnused: 74680 ns, replaceAddresses: 10601 ns, gcTerminating: 17855 ns
2018-04-10 10:16:04 INFO  FifoQueue:80 - Processing event Updated with key distributed-queue
2018-04-10 10:16:04 INFO  Reflector:55 - Waiting on event queue for 63818 ms unless notified
2018-04-10 10:16:04 INFO  AddressController:107 - Total: 1, Active: 1, Configuring: 0, Pending: 0, Terminating: 0, Failed: 0
2018-04-10 10:16:04 INFO  AddressController:121 - Usage: {broker={distributed-queue={used=1.0, needed=1}}}, Needed: {broker={distributed-queue={used=1.0, needed=1}}}
2018-04-10 10:16:04 INFO  AddressController:153 - total: 217535410 ns, resolvedPlan: 30964 ns, calculatedUsage: 347755 ns, checkedQuota: 244027 ns, listClusters: 101345708 ns, provisionResources: 32480 ns, checkStatuses: 115475770 ns, deprovisionUnused: 38836 ns, replaceAddresses: 10125 ns, gcTerminating: 9745 ns
2018-04-10 10:16:34 INFO  AddressController:107 - Total: 1, Active: 1, Configuring: 0, Pending: 0, Terminating: 0, Failed: 0
2018-04-10 10:16:34 INFO  AddressController:121 - Usage: {broker={distributed-queue={used=1.0, needed=1}}}, Needed: {broker={distributed-queue={used=1.0, needed=1}}}
2018-04-10 10:16:34 INFO AddressController:153 - total: 178032384 ns, resolvedPlan: 59036 ns, calculatedUsage: 1122613 ns, checkedQuota: 256846 ns, listClusters: 33028309 ns, provisionResources: 33349 ns, checkStatuses: 143277613 ns, deprovisionUnused: 222005 ns, replaceAddresses: 13230 ns, gcTerminating: 19383 ns

The issue here is that the standard-controller only acts on addresses in phase=Pending. This means that it will not attempt to check quota nor provision new resources for the address. I will try to change the REST API to change phase to Pending when an address is changed and see if that fixes it or causes havoc.

I think we might need another phase to handle this. If we set the phase to Pending, the agent will remove the configuration for the address from router and broker.
Another alternative is to keep the Active phase, and find a way to 'detect' that plan has changed. For instance, if we add an annotation on the address called 'actual plan', we can detect that if it doesn't match the plan specified, we need to deal with plan change and then update the 'actual plan' annotation.

This is supported now and we have testd


gh-460: added 'TimestampSeries' in TimedeltaSeries in series.pyi

[x] Closes #460
[x] Tests added: Please use assert_type() to assert the type of any return value

Yeah I'll look into it

Sir I looked into it, it fails because of this  Failed to install /Users/runner/Library/Caches/pypoetry/artifacts/59/74/28/0da99c4265a039049b4cccc0a54b5103991e1d78c7d85b899291d627c5/black-22.10.0-1fixedarch-cp310-cp310-macosx_11_0_x86_64.whl, I think it is not able to install but why?

I think it is not able to install but why?, that is what I am not able to understand

We are not sure.  I Just did a PR and those jobs had no issue, and there is nothing you changed that would cause them to fail.  May have been a momentary hiccup in the CI.

The same tests are failing again

Can you try this?

Can you try this? Modify pyproject.toml on the line about the black version and change it to:
black = ">=22.12.0"

then commit and push.

yeah

All these tests fail but in my local test poe test succeds

That was a separate issue that I did a PR for on Friday, and just merged it.  Do git fetch upstream then git merge upstream/main then push, and I think we'll be good.

That was a separate issue that I did a PR for on Friday, and just merged it. Do git fetch upstream then git merge upstream/main then push, and I think we'll be good.

yes

Done sir, it finishes off nicely

thanks @ramvikrams

Thanks sir


Homebr3w hangs when system fails to validate certificate for https links

Repro: try to download freeShop

@ksanislo shouldn't https certificate check be disabled?

Yeah, the cert check is actually disabled... I've mentioned this to him already, but the author has a problem with the cert he's using on the freeshop.pw site that causes a failure even when the official 3DS check is turned off. There's no solution from this end, as long as he keeps letting release links get posted that have the bad certificate, it will continue to show up from time to time.


searches and show_only_matches are lost after a redraw

For the time being this looks like the better approach (clearing search on modification).


Added Gallery, Thumbnail components

Added the following

Gallery Component
Thumbnail Component
Delete Button fixes

Appreciate the time taken out to test and comment on the code :) Made the necessary changes.

I've got a big work-related project release in 2 weeks, so I'll try to find some time this week-end to test your PR and finish the review.
But you did a really great job here !
Thanks @tjunxiang92 !

@Elhebert Thanks for taking time out to check it. New to contributing in open source and open to feedback on places I can improve in :)
All the best for your big work-related project release in 2 weeks!

@tjunxiang92 Just got some time to test this, and it's working pretty well. Nice job!
I'm merging this.

Sweet! Updated onto develop branch.

I have some update to do in the documentation, then I'm merging all of it onto master, and publish it on npm ;)


Add caching support

Prevent to download the same google fonts URL twice inside a single build run

Download @ build, ...I think this must be what next.js does?

@kerns yeah but I asked the astro team if there's any caching system built in, but there isn't atm. So ideally it wouldn't do the download for every build (when the assets are already in the cache).

I published package that adds in-memory caching for downloaded cache and retrying fetch on failure
https://www.npmjs.com/package/@herob191/astro-google-fonts-optimizer
In case of problem with my  fork, post an issue there
https://github.com/Herob527/astro-google-fonts-optimizer


Change the data structure for saving notifications data

Previously it was saved as
LinkedHashMap<String, Pair<String, Integer>> conversations;

Now it is saved as
LinkedHashMap<String, List<MessageInfo>> conversations;

MessageInfo contains the content and the message id.
This commit does no visual changes, only changes the underlaying data structure and functions related to it.

@gnprice How about we use LinkedList instead of ArrayList?
It has to perform these main operations

Traversing each message to find a certain message id (For deletion)
Deleting a MessageInfo
Inserting message in the end

Deletion is faster in LinkedList but traversing is faster in ArrayList & other reason for LinkedList is after deletion the memory is freed up pretty easily and quickly which is not the case for ArrayList

Merged -- thanks!

LinkedList instead of ArrayList

So actually, one thing that I noticed when working out what the answers were to my questions to put in that doc comment :grin: is: it looks like we're currently sticking each message on the end of the list; but what we should probably actually be doing is keeping them sorted by message ID. That way they're always in the order the sender sent them in. (I'm not sure if GCM promises things will be delivered in order; even if it does, between the Zulip server and the notification bouncer I don't think we have that guarantee.)
That operation feels a lot more natural on an ArrayList than a LinkedList.
Better yet, though: how about a TreeMap, indexed by message ID? That keeps things sorted, and also makes deletion very simple and efficient.

other reason for LinkedList is after deletion the memory is freed up pretty easily and quickly which is not the case for ArrayList

This doesn't sound right to me -- I'd actually expect the opposite to be true, because a LinkedList will contain a separate piece of garbage for each entry in the list. But I don't think this is likely to be a big concern either way; this shouldn't be a lot of data.

Yeah, there is no sorting done according to the ID because currently the messages are being grouped into a separate list for different narrows, so in a particular narrow I don't think there can be a case where we receive a notification of a later message first than an older message, so If we're using a single list or a map (from message id to details) then it could have been a problem.
The main performance increase we can get if we group these into different narrows, a TreeMap would have been a good option, anyways mostly the number of messages would be really low so I don't think we should be worrying so much about the data structure.

so in a particular narrow I don't think there can be a case where we receive a notification of a later message first than an older message

Why are you sure of that?
I don't see a reason to be sure messages will always come in order. If we don't have a good reason to be sure that assumption is true, we should write the code to behave correctly without making the assumption. Which means sorting the messages by ID (or inserting them into an ordered data structure), rather than just putting them on the end.

Just now I happened across this orange warning box in the docs for FCM:

FCM does not guarantee the order of delivery.

That's the behavior I'd expect from a service like this, so it's nice to see it explicit in the docs. I'd be surprised if GCM makes a stronger guarantee here than FCM does.
In any case, I wouldn't want to make that guarantee on behalf of the Zulip app server and the Zulip push notification bouncer. We should assume that messages may come out of order.


nunaliit schemas-for-inreach command ignores form versioning

Currently the nunaliit schemas-for-inreach command outputs JSON containing all the definition objects for schemas related to a inreach_forms.xml file found in the config folder.
In the XML document, forms have an id number, a title, and a prefix. By convention, a best practice for building forms would have the prefix include a version number to uniquely identify a form. The inreach form XML in the example below shows and example of the syntax. The form id which functions as more of an index in the file and cannot be assumed to be consistent over time. The title may well remain consistent despite changes to the form fields. The prefix contains a unique form identifier with an abreviation representing the atlas, the form title, and the version (in this case 1). The schema IDs for each form should be based on the entire prefix to permit versioning of forms and with new versions resulting in new matching schemas.
<form id="9">
<title>Weather Conditions</title>
<EMAIL_ADDRESS><prefix>EX-WC-1-</prefix>
<delimiter>|</delimiter>
<field id="1">
<name>Observed</name>
<type>PickList</type>
<value>Blowing snow</value>
<value>White out</value>
<value>Blizzard</value>
<value>Flat light</value>
<value>Ice fog</value>
<value>Fog</value>
<value>Excellent visibility</value>
<value>Good visibility</value>
<value>Fair visibility</value>
<value>Poor visibility</value>
<value>Bad visibility</value>
<value>Zero visibility</value>
<value>Falling snow</value>
<value>Rain</value>
<value>Freezing rain</value>
<value>Other (put in notes)</value>
<required>Y</required>
</field>
<field id="2">
<name>Notes</name>
<type>Text</type>
<length>140</length>
<required>N</required>
<default></default>
</field>
</form>

The schema IDs for each form should be based on the entire prefix to permit versioning of forms with matching schemas.

Reverted with: https://github.com/GCRC/nunaliit/pull/1174
Versioning of schemas requires that all existing schemas to be updated as well in addition to every reference to affected schemas in the client side code. It would also require references to the old schemas that don't use the versioning be added everywhere as well.
This is because adding the new IDs for schemas with prefix + title needs the inReach processing servlet to also check for that instead of only checking title. The servlet could be changed to query for the existence of a particular schema then check the alternative (check if prefix+title exists, otherwise check if it's title only), but is not ideal to be querying the database for every inReach message processed. Caching them is also difficult because there is no indication if it was updated with the executable.


[Question] How can I create table header in seperate file

<table ng-table="tableParams" template-header="tableHeader">

<script id="tableHeader" type="text/ng-template">
......
</script>

Instead of this I want to create the template header in separate file so that I can re use same for other tables also
can any one suggest how can get this ?

@ravindhar Please refer header cell template demo page.
They used following template:
 <script type="text/ng-template" id="headerCheckbox.html">
    <input type="checkbox" ng-model="demo.checkboxes.checked" class="select-all" value="" />
  </script>

you can pull out this in separate file and then ng-include that file where ever needed.


add axes_reset_user command to the docs

There's not currently a mention of the axes_reset_user command in the docs (besides in CHANGES.txt).
This PR adds a note about the axes_reset_user command to the quick start section of the docs here: https://django-axes.readthedocs.io/en/latest/usage.html#quickstart

Looks good. Thank you!


IIS Web app Manage: cannot detect existing apppool, site and binding if they contains foreign characters

Having a website with matching appool and bindings with names that contains foreign characters (in my case a danish "æ"), causes subsequent deploys to fail as the existing apppool, website and bindings are not detected and so the task tries to create these again.
It works for me by adding  -Encoding ([System.Text.Encoding]::GetEncoding(1252)) to all Invoke-VstsTool calls in AppCmdOnTargetMachines.ps1.
Not sure if that solution is safe world-wide. I guess that depends on how appcmd.exe is constructed.

@AThomsen Feel free to raise PR if you know the solution. We highly encourage community contribution.

@AThomsen Thanks for your contribution. We will review this


Add a name or description for each language icon

This issue is related to the vim-bootstrap website.
Description
When selecting the language, I think it is good to present icons, including the language name they represent. Some icons are not very known. This will improve the accessibility.
For example (in the Vim Boostrap page):

On ohmyz.sh page:

Best regards,
Fernando Pimenta

Maybe we could show the language name when the mouse is hovering the icon or change all the icons completely.


Upgrade some more dev dependencies

Awww, man. This affects the built files in ways I simply don't understand:
--- dist-master/diff.js	2024-03-19 17:54:44.215622691 +0000
+++ dist/diff.js	2024-03-19 17:55:19.022355585 +0000
@@ -1,8 +1,8 @@
 (function (global, factory) {
   typeof exports === 'object' && typeof module !== 'undefined' ? factory(exports) :
   typeof define === 'function' && define.amd ? define(['exports'], factory) :
-  (global = global || self, factory(global.Diff = {}));
-}(this, (function (exports) { 'use strict';
+  (global = typeof globalThis !== 'undefined' ? globalThis : global || self, factory(global.Diff = {}));
+})(this, (function (exports) { 'use strict';

   function Diff() {}
   Diff.prototype = {
@@ -1827,6 +1827,4 @@
   exports.reversePatch = reversePatch;
   exports.structuredPatch = structuredPatch;

-  Object.defineProperty(exports, '__esModule', { value: true });
-
-})));
+}));

I guess I need to get some understanding of JavaScript module systems to evaluate if this breaks stuff. Argh!

I'm just gonna roll forward with this, keep updating stuff, and before doing a release, figure out how to test that jsdiff still works with all module systems.


New msbuild package update on Ubuntu crashes environment

Steps to reproduce
I have an Ubuntu environment for my .NET Core 2.1 project. Today apt reported there are some updates available. After upgrading my environment broke, failing to load projects in the solution.
These packages were updated: mono-llvm-tools msbuild msbuild-sdkresolver
This is the error given:
Project 'MyProject' load failed: The SDK 'Microsoft.NET.Sdk.Razor' specified could not be found.
That SDK is referenced in 2 files:
/usr/lib/mono/msbuild/15.0/bin/Sdks/Microsoft.NET.Sdk.Web/Sdk/Sdk.props
/usr/lib/mono/msbuild/15.0/bin/Sdks/Microsoft.NET.Sdk.Web/Sdk/Sdk.targets
As a workaround I commented out a reference to that SDK in those files and now my environment is working again.
I don't know if it's a mono or msbuild issue. The only thing I know is that it was working before the update of those packages and stopped working afterwards. Nothing else changed.
Version info:
Setting up mono-llvm-tools (3.6.0+mono201805011452-0xamarin1+ubuntu1804b1) ...
Setting up msbuild-sdkresolver (1:15.8+xamarinxplat.2<IP_ADDRESS>.43-0xamarin5+ubuntu1804b1) ...
Setting up msbuild (1:15.8+xamarinxplat.2<IP_ADDRESS>.43-0xamarin5+ubuntu1804b1) ...
Mono JIT compiler version <IP_ADDRESS> (tarball Mon Aug  6 09:07:45 UTC 2018)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
TLS:           __thread
SIGSEGV:       altstack
Notifications: epoll
Architecture:  amd64
Disabled:      none
Misc:          softdebug
Interpreter:   yes
LLVM:          yes(3.6.0svn-mono-/)
GC:            sgen (concurrent by default)
Microsoft (R) Build Engine version <IP_ADDRESS> ( Wed Sep  5 19:27:37 UTC 2018) for Mono

@radical Can you take a look? I'd expect the msbuild-sdkresolver package to include the NuGet SDK resolver, but I don't actually know the Mono distribution details.

It would not be expected to use the NuGet SDK resolver to find Microsoft.NET.Sdk.Razor. It is a depdency of Microsoft.NET.Sdk.Web. What's happening here is that resolution has fallen back to the default Sdk resolver, which found a default web sdk without its razor sdk dependency. If mono msbuild bundles web sdk for use without .NET Core SDK, it needs to also bundle the razor sdk.
See also https://github.com/OmniSharp/omnisharp-vscode/issues/2604#issuecomment-430046231

Hmm I thought we're bundling Razor (https://github.com/mono/msbuild/blob/105cb8a15778bf32efa730b5125d1503e5b44629/mono/build/SdkVersions.txt#L4) but I indeed don't see it in my Mono install.

Does a Mono install normally carry Microsoft.DotNet.MSBuildSdkResolver?
FWIW, we are moving in the opposite direction in VS where we will not be putting any SDKs in the default MSBuildSdksPath.
See https://github.com/dotnet/cli/issues/6795
The problem with the default resolver is that it hides errors with the .NET Core SDK resolver, and it's very hard to diagnose.
I suspect that some of the folks seeing razor failures are first having a hidden failure to resolve from .NET Core SDK, and then seeing that the default location doesn't have Razor as the only error message.

Yes we do ship the Microsoft.DotNet.MSBuildSdkResolver cause afaik it was the only way to get SDK style projects to work.
I'm not really deeply familiar with all of this though, @radical would be the subject matter expert (but he is out till end of this month).

Any updates on this @radical / @akoeplinger?
Would be great to see this resolved, all our web projects are broken due to this.

Closing since @marchy reported it fixed.


Any improvements welcome

Any improvements welcome just document what you have done

what exactly i have to improve coding part or documentation part

Please how do I contribute

I would love to contribute

#4

I would love to contribute

Go for it!!

This is pretty open ended I will review pull request.


Support Sleep - [FEATURE]

Most harmony remote support sleep timer which will turn off all running activities, choice of 15, 30,60, 90 and 120 minutes
Can this be added?
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Hi,
You can use shortcut / automation for that I think, will be far more powerfull . The timer is handled as far as I know by the harmony app, not the hub itself.


User/v jandrew/focus mode breakpoint

Docs Build status updates of commit ed62b88:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: CannotMergeCommit] Cannot merge commit ed62b880d2952dbfab4c2bcf477422dcb799f4ba in branch user/v-jandrew/focus-mode-breakpoint of repository https://github.com/MicrosoftDocs/edge-developer into branch main (commit d22bef394514602e0dfa81ccaf0927cb84154a3e). Please follow this documentation: https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/ to use git.exe to resolve you content conflicts locally and then push to remote.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


GEOMESA-1337 - Add tutorial and example code for GMSpark Shallow Join

Signed-off-by: Atallah Hezbor<EMAIL_ADDRESS>

Alright, looks good to me. Sorry to be so picky, but it wasn't rendering properly when I built the document with Sphinx.

cool. @jnh5y  or @elahrvivaz got anything else?

@jahhulbert-ccri after some discussion with Bob, I plan on expanding the tutorial to talk more about visualization

looks good, my comments were mainly style and picky things


Fix issue caused by nil content or provider position.

[#112380605]

looks good :eyes: and nice spec update.


Gamejs Http ajax  is deprecated

Make sure that you used XMLHttpRequest

thanks, yes. the problem is the sync httprequest which should i shouldn't do. i'm not actively maintaining gamejs but i regularly pull PRs


Resurrect the email.trim()

email trimming was lost when we added partialEmail, thus regressing
the PAN submission for gmail.  Trim in this.partialEmail and let
this.email inherit it.

Tested and works fine for gmail for PAN, EPFO.  Tested on android+chrome as well as firefox+fedora.


Exact settings for example videos?

https://github.com/MooreThreads/Moore-AnimateAnyone#-examples
Also any preconditioning and post editting?

We did not perform any post editing and preconditioning. The default settings (e.g. cfg=3.5, step=30) can yield similar results.

How about the other settings? I tried to replicate the example but it still has flickering
settings -W 512 -H 768 -L 120 (pose video is 30fps and 4 seconds long)   --steps 30
I'm guessing the interpolation is off somewhere. How can I get just the end video the extra width may also be causing issues.
https://github.com/MooreThreads/Moore-AnimateAnyone/assets/114336644/e586890c-a43b-44ba-9c31-cadb2f863769

Could this be the reason for the flickering?
Some weights of the model checkpoint were not used when initializing UNet2DConditionModel:
['conv_norm_out.weight, conv_norm_out.bias, conv_out.weight, conv_out.bias']

It seems the motion module not working. Can you check whether the motion module params are loaded correctly?

Could this be the reason for the flickering?
Some weights of the model checkpoint were not used when initializing UNet2DConditionModel: ['conv_norm_out.weight, conv_norm_out.bias, conv_out.weight, conv_out.bias']

Encountered the same problem, have you solved it?

Unfortunately not, have given up for now.

Any update on this?

Unfortunately not, have given up for now.

Sort of, the error message wasn't solved but the flickering was, I simply had a '.' in front of the motion module path in the json which meant it was not used. However now I get OOM because I use a t4 15gb card on colab.

Yes colab gives a maximum of 12.7 GB system RAM to free users, however, to generate one video of length 2 sec, this module seems to consume an average of 13 GB system RAM and >14GB GPU RAM.


[FR] Display more text data in visualizer tooltip (OCR)

Visualizing more text data on a label in the visualizer tooltip, or generally enabling easy access to all of a label's attributes would be a valuable improvement for users working with OCR datasets

Duplicate of https://github.com/voxel51/fiftyone/issues/3361