could not find TARGET vtkIGSIOCalibration

Hello,
I try to build IGSIO with vtk 9.1, when did cmake config, got "could not find TARGET vtkIGSIOCalibration".  Any solution for that?
Thank you!
`
CMake Error at C:/Program Files/CMake/share/cmake-3.19/Modules/ExternalProject.cmake:3116 (get_property):
get_property could not find TARGET vtkIGSIOCalibration.  Perhaps it has not
yet been created.
Call Stack (most recent call first):
C:/Program Files/CMake/share/cmake-3.19/Modules/ExternalProject.cmake:3433 (_ep_add_configure_command)
SuperBuild/External_vtkAddon.cmake:40 (ExternalProject_Add)
SuperBuild/Superbuild.cmake:27 (INCLUDE)
CMakeLists.txt:153 (INCLUDE)
CMake Error at C:/Program Files/CMake/share/cmake-3.19/Modules/ExternalProject.cmake:3116 (get_property):
get_property could not find TARGET vtkIGSIOCalibration.  Perhaps it has not
yet been created.
Call Stack (most recent call first):
C:/Program Files/CMake/share/cmake-3.19/Modules/ExternalProject.cmake:3433 (_ep_add_configure_command)
SuperBuild/Superbuild.cmake:67 (ExternalProject_Add)
CMakeLists.txt:153 (INCLUDE)
`

I just tested compiling a standalone IGSIO and haven't been able to reproduce yet.
Is this a standalone build or part of a SuperBuild project?

I have tried both builds. I'm using the latest vtkAddon from the slicer github site. That may be the cause.

The vtkAddon from the slicer github site, after build and install it just has lib and header file.  Can that be a problem.

The Slicer vtkAddon repository is correct. If you build IGSIO with IGSIO_SUPERBUILD enabled, it should automatically checkout and build the vtkAddon repository.

I think the problem might be

When I build and install vtkAddon in its install/cmake folder there is only vtkAddonConfig.cmake file. But IGSIO requires  vtkAddonTargets.cmake. I renamed it, it seems OK for IGSIO camke config and generate.
When build IGSIO, it seems connot find vtkAddonConfigure.h. vtkAddon seems not generate  vtkAddonConfigure.h from  vtkAddonConfigure.h.in

Got it built. vtkAddon installation path related.


[Event Hubs]The process of "Integration test libraries" is not finished until it is out of specified time in pipeline on China cloud

We are running live Tests against other clouds like US Gov and Azure China Cloud. The goal is to check whether new azure sdk package work with other clouds or not.
Error Description:
When we run integration tests in pipeline (os: ubuntu2004_12x_node) on China cloud. All the integration tests passed but the process is not finished until it is out of specified time.
The detailed info is shown here

Expected Behavior:
The process of Integration test libraries is complete with no error.
@benbp, @lilyjma, @ramya-rao-a for notification.

@zzhxiaofeng Based on your last comment, I am assuming we don't have this issue any more. If we do, please re-open this issue


[KAFKA-15117] In TestSslUtils set SubjectAlternativeNames to null if there are no hostnames

We are currently encoding an empty hostNames array to subjectAltName in the keystore. While parsing the certificates in the test this causes the issue - Unparseable SubjectAlternativeName extension due to java.io.IOException: No data available in passed DER encoded value.
Up to Java 17, this parsing error was ignored. This PR assigns subjectAltName to null if hostnames are empty.

I merged a PR that introduced a conflict - I resolved it since it was trivial.


fix: typo in val_state_change.go

Description

typo error fixed in x/staking/keeper/va_state_change.go UnbondingToUnbonded function sanity check error message. This PR changed error message from bad state transition unbondingToBonded to bad state transition unbondingToUnbonded because function name is UnbondingToUnbonded.
Motivation and context

How has this been tested?

Screenshots (if appropriate):
Checklist:

[ ] I followed the contributing guidelines and code of conduct.
[ ] I have added a relevant changelog to CHANGELOG.md
[ ] I have added tests to cover my changes.
[ ] I have updated the documentation accordingly.
[ ] I have updated API documentation client/docs/swagger-ui/swagger.yaml

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.jinseong.cho seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Powershell just hangs after the Start-ChiaHarvesterWatcher command

I've installed followed all the instructions but when i try and start the heat map powershell just hangs with a cursor and doesn't do anything.  Any suggestions?

Same thing here, only on one PC. Was this ever resolved?


First version of separating memory and runtime measurements

Introduces a new Measurer behaviour that can be adopted by Time
and Memory and in the future Reduction. Also switches over to
memory having its own configuration for time. Like how this ended up
in general.
This isn't merge ready yet, it's a first implementation already
up for review and CI.
Fixes #202
Ah yeah, most important proof - it actually fixes the problem - memory measurements don't seem to be impacting runtime measurements anymore:
tobi@speedy ~/github/benchee $ mix run samples/run.exs
Name                  ips        average  deviation         median         99th %
flat_map           2.16 K      463.52 μs    ±10.62%         452 μs         762 μs
map.flatten        1.16 K      863.87 μs    ±16.60%         822 μs     1301.96 μs

Comparison:
flat_map           2.16 K
map.flatten        1.16 K - 1.86x slower
# include memory measurements in the run.exs
tobi@speedy ~/github/benchee $ mix run samples/run.exs
Name                  ips        average  deviation         median         99th %
flat_map           2.30 K      435.69 μs     ±9.88%         429 μs         720 μs
map.flatten        1.19 K      838.40 μs    ±16.38%         803 μs        1223 μs

Comparison:
flat_map           2.30 K
map.flatten        1.19 K - 1.92x slower

Memory usage statistics:

Name           Memory usage
flat_map          625.54 KB
map.flatten       781.85 KB - 1.25x memory usage

**All measurements for memory usage were the same**

TODO:

[x] README/documentation adjustments
[x] respect memory_time during calculation of estimated total runtime
[x] allow measurer to return nil when a a measurement "failed" and handle it appropriately (memory measurement is less than 0 case)

This also sort of sets up putting do_benchmark/3 into its own module as it is responsible for running the benchmarking with a given measurer. The rest of the module deals with setting up the measurements according to our different measurer.

Good idea on the naming too, thanks! I think that was my OOP mindset leaking through as in the thing that measures but just Measure is nicer I think - thanks!

Ok this should be done now from me... but one of the builds failed I'll see real quick what that is about hopefully.
Reviews appreciated :pray:
:rabbit: :rabbit: :rabbit:

Includes a fix for #206 now :)

Assuming that this is good now --> (devon's comments where documentation related I think I fixed those and if not we can always adjust again)


Added @ symbols to attributes

V recently changed to using '@' symbols in front of attributes

Fixed in https://github.com/irishgreencitrus/raylib.v/pull/25 , which also v fmt -w .

Superceded by #25, which is now merged.


Modify behaviour of @assignment.outer so it includes keywords like const, local etc. and semicolon

Goal of PR (For all languages which support either of the first 1-4 text objects):

Change assignment.outer so that it captures extra tokens like const and semicolon

Examples
ecma (js, jsx, ts, tsx):
const x = 5;

@assignment.outer: const x = 5;

c and c++
int x = 5;

@assignment.outer: int x = 5;

bash
x=5

@assignment.outer: x=5

python
x = 5

@assignment.outer: x=5

css and scss:
body {
  margin: 1px 2px 3px 4px;
}

@assignment.outer: margin: 1px 2px 3px 4px;

Languages changed:
a -> b, c means b and c inherit from a, so no changes were made to b or c

[x] apex
[x] go
[x] ecma -> js, ts, jsx, tsx,
[x] lua
[x] julia

Languages not changed since they don't have keywords like const or similar, OR they were already working well:

[x] nim
[x] python
[x] bash
[x] yaml
[x] rust
[x] cuda
[x] fish
[x] css -> sass
[x] hcl -> terraform
[x] c -> fennel, ( cpp -> glsl, ( hlsl -> slang ) )
[x] inko
[x] matlab
[x] odin
[x] r
[x] tact
[x] v
[x] vim

Closes #681

I don't really agree that assignment.inner should be gone.
First, I considered assignment.lhs and rhs to be more of an addition for people who'd like granular control but I expected that with assignment.inner you can still do most things.
I just think that most of the time people expect assignment.outer to include the whole statement. The problem was that I think with languages with more complex syntax it was hard to design such thing (like it can consist of so many different mixture of const, final, variable types etc. in different order) and it ended up having a simple version of the implementation.

I don't really agree that assignment.inner should be gone.
First, I considered assignment.lhs and rhs to be more of an addition for people who'd like granular control but I expected that with assignment.inner you can still do most things.
I just think that most of the time people expect assignment.outer to include the whole statement. The problem was that I think with languages with more complex syntax it was hard to design such thing (like it can consist of so many different mixture of const, final, variable types etc. in different order) and it ended up having a simple version of the implementation.

Fair enough, I'll update the PR to restore behaviour of assignment.inner

Update: I have looked over every single language, and modified all the ones that need modifying. Some languages like Rust and C already have expected behaviour: @assignment.outer selecting the entire assignment.
PR is ready for review


[Global Routing Resizer Timing Optimizations] Stage does not fix hold violation, when a input has setup and hold violation in different end point

Description
Global Routing Resizer Timing Optimizations - Stage does not fix hold violation, when a input has both setup and hold violation in different end point.
Below example: core_dmem_req_ack => 7275/D has Hold Violation: -0.34  & core_dmem_req_ack => core2_dmem_req_ack has setup violation: -3.10 .

Environment
dinesha@lenovo-i3-10100-07IMB05:~/workarea/efabless/MPW-7/OpenLane$ python3 ./env.py issue-survey
Kernel: Linux v5.15.0-46-generic
Distribution: ubuntu 20.04
Python: v3.8.10 (OK)
Container Engine: docker v20.10.17 (OK)
OpenLane Git Version: b6bacc9d1ab469917fda7ceea61ea3a18984b818
pip: INSTALLED
python-venv: INSTALLED
---
PDK Version Verification Status: OK
---
Git Log (Last 3 Commits)

b6bacc9 2022-08-24T21:21:29+02:00 Build Script Fixes (#1283) - Mohamed Gaber -  (HEAD -> master)
f0f6055 2022-08-24T19:36:18+02:00 Remove `-echo` flags from `read_sdc` (#1284) - Anton Blanchard -  ()
9452129 2022-08-20T13:41:59+02:00 Fix 'run_yosys' invocation during -synth_explore (#1278) - meta -  ()
---
Git Remotes

origin	https://github.com/efabless/OpenLane.git (fetch)
origin	https://github.com/efabless/OpenLane.git (push)

Reproduction Material
issue_reproducible.tar.gz
Logs
[INFO RSZ-0046] Found 5 endpoints with hold violations.
[WARNING RSZ-0064] Unable to repair all hold checks within margin.
16-resizer.log

The resizer is unable to resolve all the setup violations, and hold fixup is being told not to create setup violations and so can't make progress. Increasing the clock period from 10 to 16 so setup repair can pass fixes the issue.
To get the resizer to ignore setup issues when doing hold repair, you can set:
set ::env(GLB_RESIZER_ALLOW_SETUP_VIOS) 1

Even with that option, hold repair gives up after a couple of passes. It's not obvious to me why it gave up though.

Even with that option, hold repair gives up after a couple of passes. It's not obvious to me why it gave up though.

I see why, because the path doesn't have any place where we have enough setup margin to resolve the hold issues. This fixes it, but I'm not sure it's the best solution. I moved the allow_setup_violations checks to ignore all the checks:
diff --git a/src/rsz/src/RepairHold.cc b/src/rsz/src/RepairHold.cc
index b52ce9909..9800ed331 100644
--- a/src/rsz/src/RepairHold.cc
+++ b/src/rsz/src/RepairHold.cc
@@ -391,18 +391,18 @@ RepairHold::repairEndHold(Vertex *end_vertex,
             Slew buffer_slews[RiseFall::index_count];
             resizer_->bufferDelays(buffer_cell, load_cap, dcalc_ap,
                                    buffer_delays, buffer_slews);
-            // setup_slack > -hold_slack
-            if (slacks[rise_index_][max_index_] - setup_margin
-                > -(slacks[rise_index_][min_index_] - hold_margin)
-                && slacks[fall_index_][max_index_] - setup_margin
-                > -(slacks[fall_index_][min_index_] - hold_margin)
-                // enough slack to insert the buffer
-                // setup_slack > buffer_delay
-                && (allow_setup_violations
-                    || ((slacks[rise_index_][max_index_] - setup_margin)
-                        > buffer_delays[rise_index_]
-                        && (slacks[fall_index_][max_index_] - setup_margin)
-                        > buffer_delays[fall_index_]))) {
+            if (allow_setup_violations
+                // setup_slack > -hold_slack
+                || ((((slacks[rise_index_][max_index_] - setup_margin)
+                    > (-(slacks[rise_index_][min_index_] - hold_margin)))
+                   && ((slacks[fall_index_][max_index_] - setup_margin)
+                    > (-(slacks[fall_index_][min_index_] - hold_margin))))
+                    // enough slack to insert the buffer
+                    // setup_slack > buffer_delay
+                   && (((slacks[rise_index_][max_index_] - setup_margin)
+                        > buffer_delays[rise_index_])
+                        && ((slacks[fall_index_][max_index_] - setup_margin)
+                        > buffer_delays[fall_index_])))) {
               Vertex *path_load = expanded.path(i + 1)->vertex(sta_);
               Point path_load_loc = db_network_->location(path_load->pin());
               Point drvr_loc = db_network_->location(path_vertex->pin());

If this isn't acceptable, perhaps a better solution is to do two passes. The first pass looking for a place to resolve the hold issue without impacting any setup issues, then if allow_setup_violations is set, a second pass that just finds a place to insert the hold buffer without any regard to setup violations it might cause.
@jjchery56 any thoughts? To summarize, this test case is unable to resolve all the setup violations but also fails to resolve hold violations even when -allow_setup_violations is set. Ideally the SDC should be fixed so that setup fixup can pass, but it seems like we should try harder to resolve the hold violations.

I feel issue is script is trying to fix hold based on margin in output of the cell. If the output of cell has two path, One have Hold violation and Other path as setup violation. Then better to fix hold at input of the end point.
In My case
Hold violation:  input687/X  => 7275/D  : -0.34
Setup violation: input687/X  => core2_dmem_req_ack :  -3.10
Better fix is to add Hold buffer at 7275/D, which will not create any additional setup violation in the other branch.

I think its similar to this issue: https://github.com/The-OpenROAD-Project/OpenLane/issues/1366
Updating DONT_USE_CELLS will fix timing violations.

@dineshannayya
Can you please share timing logs for placement resizer stage?
Possible attach test case for placement stage to confirm the same.

@vijayank88 My Don't cell list is
set ::env(DONT_USE_CELLS) {sky130_fd_sc_hd__a2111oi_0 sky130_fd_sc_hd__a21boi_0 sky130_fd_sc_hd__and2_0 sky130_fd_sc_hd__buf_16 sky130_fd_sc_hd__clkdlybuf4s15_1 sky130_fd_sc_hd__clkdlybuf4s18_1 sky130_fd_sc_hd__fa_4 sky130_fd_sc_hd__lpflow_bleeder_1 sky130_fd_sc_hd__lpflow_clkbufkapwr_1 sky130_fd_sc_hd__lpflow_clkbufkapwr_16 sky130_fd_sc_hd__lpflow_clkbufkapwr_2 sky130_fd_sc_hd__lpflow_clkbufkapwr_4 sky130_fd_sc_hd__lpflow_clkbufkapwr_8 sky130_fd_sc_hd__lpflow_clkinvkapwr_1 sky130_fd_sc_hd__lpflow_clkinvkapwr_16 sky130_fd_sc_hd__lpflow_clkinvkapwr_2 sky130_fd_sc_hd__lpflow_clkinvkapwr_4 sky130_fd_sc_hd__lpflow_clkinvkapwr_8 sky130_fd_sc_hd__lpflow_decapkapwr_12 sky130_fd_sc_hd__lpflow_decapkapwr_3 sky130_fd_sc_hd__lpflow_decapkapwr_4 sky130_fd_sc_hd__lpflow_decapkapwr_6 sky130_fd_sc_hd__lpflow_decapkapwr_8 sky130_fd_sc_hd__lpflow_inputiso0n_1 sky130_fd_sc_hd__lpflow_inputiso0p_1 sky130_fd_sc_hd__lpflow_inputiso1n_1 sky130_fd_sc_hd__lpflow_inputiso1p_1 sky130_fd_sc_hd__lpflow_inputisolatch_1 sky130_fd_sc_hd__lpflow_isobufsrc_1 sky130_fd_sc_hd__lpflow_isobufsrc_16 sky130_fd_sc_hd__lpflow_isobufsrc_2 sky130_fd_sc_hd__lpflow_isobufsrc_4 sky130_fd_sc_hd__lpflow_isobufsrc_8 sky130_fd_sc_hd__lpflow_isobufsrckapwr_16 sky130_fd_sc_hd__lpflow_lsbuf_lh_hl_isowell_tap_1 sky130_fd_sc_hd__lpflow_lsbuf_lh_hl_isowell_tap_2 sky130_fd_sc_hd__lpflow_lsbuf_lh_hl_isowell_tap_4 sky130_fd_sc_hd__lpflow_lsbuf_lh_isowell_4 sky130_fd_sc_hd__lpflow_lsbuf_lh_isowell_tap_1 sky130_fd_sc_hd__lpflow_lsbuf_lh_isowell_tap_2 sky130_fd_sc_hd__lpflow_lsbuf_lh_isowell_tap_4 sky130_fd_sc_hd__mux4_4 sky130_fd_sc_hd__o21ai_0 sky130_fd_sc_hd__o311ai_0 sky130_fd_sc_hd__or2_0 sky130_fd_sc_hd__probe_p_8 sky130_fd_sc_hd__probec_p_8 sky130_fd_sc_hd__xor3_1 sky130_fd_sc_hd__xor3_2 sky130_fd_sc_hd__xor3_4 sky130_fd_sc_hd__xnor3_1 sky130_fd_sc_hd__xnor3_2 sky130_fd_sc_hd__xnor3_4  }

@dineshannayya
Sorry., I've misunderstood the OpenLane tags. this is not same as mine.

@dineshannayya is correct. There is a better strategy that fixes the hold violation without affecting the setup violation. Setup repair splits non-violating loads from violating loads and hold repair could do the same.
@antonblanchard you are correct that the allow_setup_violations needs to move up but you don't need all those extra parens around && clauses.

fixed in openroad 79313e90d


Javascript fails when markdown input contains titles with {}

Background: I have swagger (2) JSON, which is converted to Slate format using widdershins, and then I try to display it using Shins.
But it seems that if markdown file has headings containing { or }, _toc.js fails with following error in browser, which then renders page somewhat non-usable.
_jquery.js:1463 Uncaught Error: Syntax error, unrecognized expression: #account-exists__get_accounts_{id}_exists
    at Function.Sizzle.error (_jquery.js:1463)
    at Sizzle.tokenize (_jquery.js:2120)
    at Sizzle.select (_jquery.js:2541)
    at Function.Sizzle [as find] (_jquery.js:864)
    at jQuery.fn.init.find (_jquery.js:2787)
    at jQuery.fn.init (_jquery.js:2904)
    at jQuery (_jquery.js:75)
    at HTMLAnchorElement.<anonymous> (_toc.js:40)
    at Function.each (_jquery.js:360)
    at jQuery.fn.init.each (_jquery.js:137)

(Tested with latest Chrome):
Similar error does not happen when using Slate
Source markdown:
    ## Account.exists__get_accounts_{id}_exists

Shins renders it as:
   Account.exists__get_accounts_{id}_exists

Slate renders it as:
  Account.exists_get_accounts{id}_exists

I did not (yet) further investigate what Sizzle tries to do with that string, but I presume those '{}'-characters can cause other problems too, so perhaps they should be converted to something else ?
Slate seems to just rip them out when rendering html.
Example markdown file:
https://gist.githubusercontent.com/TomiTakussaari/8cbfeab272d53e9d07ca44a4c744e9a8/raw/17ed9c0b5290513ea1863d7c045a973173bd6c27/index.html.md

Could you let me know which version (if from npm) or HEAD commit (if from git) you're using?

I had a local commit ready which fixes this issue. Can you let me know if you're using shins from npm or from a git clone?

I am using npm

v2.0.1-1 published. Please let me know if it fixes the issue for you.

That fixes it, thanks!
Also thanks for great libraries, saved me from lot's of Ruby trouble.


about accuracy

I use res50-C5
when I don't use the pre-training model, the accuracy is only 59%. After using the pre-training model, the accuracy reaches 80%.
However, my experiment on YOLOv5s is only 75%.
Should I use the pre-training model? What may be the reason for my situation?

Yes, it is better to use the pre-trained model given performance and training time. We suggest you to read this paper for a deeper understanding.


Effect on Recycle bin on URL change outdated

In my recent tests, the content of the recycle bin was moved and I was able to restore files from it, so the documentation is outdated.
Is there any special content of the recycle bin that is not moved?

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

ID: 5475fd83-52fa-6d49-d08f-fc75fabee09c
Version Independent ID: 19ede247-e62c-9f1a-700c-4c878fec7f78
Content: Change a site address - SharePoint Online
Content Source: SharePoint/SharePointOnline/change-site-address.md
Service: sharepoint-online
GitHub Login: @kaarins
Microsoft Alias: kaarins

@ChristianGalla thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.

I don't think this is a problem with the tenant and therefore does not need a service ticket. I have seen the same thing too

According to the support, the documentation can not be entirely correct. Primary aim of the documentation is to prevent data loss. If data is lost, the 3rd level support is able to restore data within 14 days.


updater: Change tests not to set StopGracePeriod

The updater used to use StopGracePeriod to figure out how long to wait for stopping a task to timeout. In 47ddece4c66bcafc0563bedcc2d5db77033da003, this was changed to use an updater-level parameter instead. So there is no reason for tests to set StopGracePeriod or refer to it.

Current coverage is 55.01% (diff: 100%)

Merging #1745 into master will decrease coverage by 0.15%

@@             master      #1745   diff @@
==========================================
  Files           101        101
  Lines         16500      16500
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           9103       9078    -25
- Misses         6262       6288    +26
+ Partials       1135       1134     -1

Powered by Codecov. Last update efd44df...f0c5702


Add support for progn-equivalent for sequencing

It would be nice to have some equivalent to Common Lisp’s progn / Scheme’s begin / Clojure’s do to sequence side-effecting forms in an expression. Except not named progn 😄:
(if (< x 5)
  (do
    (begin-tx)
    (print "in tx")
    (commit-tx))
  (print "not running tx"))

At the moment, the only option is to create a separate function wherein these side effecting expressions are sequenced:
(defun helper ()
  "Runs tx"
  (begin-tx)
  (print "in tx")
  (commit-tx))

(if (< x 5)
  (helper)
  (print "not running tx"))

As much as I resist introducing Clojure-isms into Pact, do is by far the best one. begin: well, where does it end? progn: barf.

Brian do you want to take a crack at this sometime?


Class library exception issue

Hi
I used the package in a normal WPF application. And It worked fine.
Now I 'm trying to set up the package inside a class library. But I m getting the following exception.
System.Windows.Markup.XamlParseException
HResult=0x80131501
Message=The invocation of the constructor on type 'SourceChord.FluentWPF.ResourceDictionaryEx' that matches the specified binding constraints threw an exception.
Source=PresentationFramework
StackTrace:
at System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
at System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri)
at System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream)
at System.Windows.Application.LoadComponent(Object component, Uri resourceLocator)
at V4.WPF.GUI.MainWindow.InitializeComponent() in D:\Vitrox\V4_x64\V4.WPF.GUI\MainWindow.xaml:line 1
Inner Exception 1:
TypeInitializationException: The type initializer for 'SourceChord.FluentWPF.SystemTheme' threw an exception.
Inner Exception 2:
NullReferenceException: Object reference not set to an instance of an object.
"   at SourceChord.FluentWPF.ThemeHandler..ctor()\r\n   at SourceChord.FluentWPF.SystemTheme..ctor()\r\n   at SourceChord.FluentWPF.SystemTheme..cctor()"
The exception is being occurred at SystemTheme. The inner exception is
"Object reference not set to an instance of an object."

Does anyone have any idea on how to resolve this problem?
Thanks and have a great day.

Hi, @nima70
Sorry for responding so late.
I couldn't reproduce it.
Please tell me more information.
By the way, FluentWPF needs some ResourceDictionaries.
(See also preparation)
If you use FluentWPF in class library, you have to load the ResourceDictionary manualy.
For example, like this in class library.
var dict = new ResourceDictionary();
dict.Source = new Uri("pack://application:,,,/FluentWPF;component/Styles/Controls.xaml");
Application.Current.Resources.MergedDictionaries.Add(dict);

Please try it.

Hi
I added the mentioned code inside my Window code behind .

Here is the exception I get


Fixes failing workflow

Resolves test workflow for deployment
Missing yaml key added for yarn

@IanShelanskey can you approve this PR first - This should fix the failing tests. I realized that I missed some commands in the test build action.


Hittest not working after 2.2?

I've used 'hitTest' code to auto-center on items in collections. And it works with 2.2.0, but nothing later.  Could someone point me in the right direction to enable it in newer versions?
Example of working using 2.2.0 ->
https://chattanoogahistory.com/marr-field
Example of same page using 2.4.1 (not working / not throwing errors): -> https://chattanoogahistory.com/marr
hitTest code:
var hitTest = function(position) {
            var box;
            var count = viewer.world.getItemCount();
            for (var i = 0; i < count; i++) {
              box = viewer.world.getItemAt(i).getBounds();
              if (position.x > box.x &&
                  position.y > box.y &&
                  position.x < box.x + box.width &&
                  position.y < box.y + box.height) {
                return i;
              }
            }
            return -1;
          };
          var $viewerElement = $('#openseadragon-canvas')
          .on('mousemove', function(event) {
            var pixel = new OpenSeadragon.Point(event.clientX, event.clientY);
            pixel.y -= $viewerElement.position().top;
            var index = hitTest(viewer.viewport.pointFromPixel(pixel));
            $('.output').text(index === -1 ? '' : 'Image ' + index);
          }
             );
          viewer.addHandler('canvas-click', function(event) {
            if (!event.quick) {
              return;
            }
            var index = hitTest(viewer.viewport.pointFromPixel(event.position));
            if (index !== -1) {
              viewer.viewport.fitBounds(viewer.world.getItemAt(index).getBounds());
            }
          }
                           );

After some test, I conclude that this is caused by the click to zoom setting. If disable the clickToZoom option in gestureSettingsMouse, it works well. So you have to disable the default click to zoom handler when you just need fit the selected item bounds, which you can disable preventDefaultAction of event to realize.

That works! Thank you.

Now that I need the current version to do 'other stuff', I'd like to see HitTest working without disabling clickToZoom
in gestureSettingsMouse.
Any help in doing that?
FYI - the hitTest failure occurs only on desktop after version 2.2.0.

Seems like it should work... in what way is it failing? What are you hoping that it'll do that it's not doing? Do you have an example to share?

Specifically,  to make it work after 2.2.0 you have to disable the clickToZoom option in gestureSettingsMouse.
Not terrible, but removes the option for a user to click outside tiles and zoom (normal expected behavior). At least this is the only fix I'm aware of.
Working example here in a modal:  https://chattanoogahistory.com/hittest

I still don't understand what you mean by it not working. If you don't disable clickToZoom, the hit detection doesn't happen at all? Or the hit detection happens, but in response it doesn't zoom correctly? If it's the latter, that makes sense, because the click to zoom behavior would override any additional navigation you might be adding.
If you want to override the click to zoom behavior dynamically, you can use event.preventDefaultAction = true like so:
viewer.addHandler('canvas-click', function(event) {
  if (!event.quick) {
    return;
  }

  var index = hitTest(viewer.viewport.pointFromPixel(event.position));
  if (index !== -1) {
    event.preventDefaultAction = true;
    viewer.viewport.fitBounds(viewer.world.getItemAt(index).getBounds());
  }
});

The 'fix' requires that click to zoom is disabled for all areas around the tiles (shown in red in example), but does work for the tiles themselves. Both worked for v 2.2.0.
Again, not a huge deal, but would be ideal if Hittest worked without disabling the zoom.
Without the 'fix' - Hittest won't zoom to fill/contain per tile after 2.2.0.

Cool, makes sense. My suggestion above should work for that. Have you given it a try?

I misread that suggestion.
Tested and confirmed. It works!
Thank you.

Excellent :)


docs(guides): add how to create custom form field.

What kind of change does this PR introduce? docs update

This change is

Codecov Report

Merging #795 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #795   +/-   ##
=======================================
  Coverage   91.69%   91.69%
=======================================
  Files          22       22
  Lines         915      915
  Branches      254      254
=======================================
  Hits          839      839
  Misses         76       76

Continue to review full report at Codecov.

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


Pip install tenosorboardX

tensorboardX isn't installed by default.

Hello, https://github.com/NVIDIA/retinanet-examples/commit/d03b68b8969f155e19b2a54b018ccf9672153572 switches to torch.utils.tensorboard and removes tensorboardX dependency.


Build a toggltrackreceiver to collect timers as logs

Now reading https://opentelemetry.io/docs/collector/building/receiver/

Designing receiver settings:
receivers:
  tailtracer: # this line represents the ID of your receiver
    interval: 1m


ESCI evaluation label2relevance mapping

Hi! Thanks for this great resource!
Following the evaluation guidelines, the labels E, S, C, and I are associated respectively to the relevance scores of  1.0, 0.1, 0.01, and 0.0.
This is reflected in two places in the code:
in esci-data/ranking/launch-predictions-task1.sh
$1/terrier trec_eval "${TREC_EVAL_DATA_PATH}/test.qrels" "${TREC_EVAL_DATA_PATH}/hypothesis.results" -c -J -m 'ndcg.1=0,2=0.01,3=0.1,4=1'

and in esci-data/ranking/prepare_trec_eval_files.py
esci_label2relevance_pos = {
        "E" : 4,
        "S" : 2,
        "C" : 3,
        "I" : 1,
 }

The label2relevance mappings of S and C seem to be interchanged, given that S is supposed to be associated with relevant score 0.1 and C with relevance score 0.01.

Just saw this related issue, but not sure it answers this specific question

Hi @marieiag,
The relevance scores have the right value from the relevance position, but as you said S and C must be 2 and 3, respectively, instead of  3 and 2.
As this has been a popular question I will changed in a coming commit.
Thanks for asking.

Sounds good, thanks for the answer!


Adjusted backend run command in cypress workflow.

Description
Adjusted backend run command in cypress workflow to align with the backend developer guide.
https://github.com/opensearch-project/alerting/blob/main/DEVELOPER_GUIDE.md#building-from-the-command-line
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Closing in favor of https://github.com/opensearch-project/alerting-dashboards-plugin/pull/1056/files#diff-182180634aa77cafcb5b44f6b95b6b1cc243dae5d31cb1bc402b0050ce01fd6bR37


[discover] Fix SO branch discovery and remove update action SO special casing

Fix SO branch discovery by adding "future branches" when the non-existing configured one is created/available
Remove Update action specifial casing for SO and skip non existing branches
Run make discover-branches
Add image overrides for SO main

This will also enable more special casing removal in the future.

@creydr @mgencur can you take a look?


adds switch for base models based on etl

Fivetran Compatibility

create fivetran macros
update models to pull from macros specific to the ETL specified at the project level

updated adapter models to use the router pattern. Also renamed fields to be unioned with other ad packages. @eogilvy12 @jthandy These changes are ready for review


Add MySQL database storage support

[ ] Username to UUID
[ ] Save home

[ ] Figure out best table structure

[ ] Get home
[ ] Ensure thread safety

But for small servers, this shouldn't be of an absolute necessity.

Scrapped


Shibe.Online CORS is NO

Thanks for looking to open an issue for this project.
If you are opening an issue to suggest adding a new entry, please consider opening a pull request instead!
please check it and change.

Hi @puddinggggg
Thanks for your contribution ;)
We have some problems with public APIs, so we won't be able to review/add this improvement right now.
Read this issue for more information, please: https://github.com/public-apis/public-apis/issues/3104


Command line usage

After typing WTFJS from the command line, how do you type to view the javascript weird specification

Use arrows to move around and q to quit

@SharakPL Hi, you know how to run it from the command line (WTFJS), but I wonder how to get the weird javascript specification

You dont't. This simply loads content of README.md in your terminal. You need to scroll through it. You can try https://github.com/ttscoff/mdless for more

@SharakPL thank you


Extending with custom manual instrumentation

Fixes https://github.com/open-telemetry/opentelemetry.io/issues/5713

@svrnm can you check?

@svrnm please check again

@svrnm can you check?

@svrnm can you check?

I did, but I'd like to get some feedback from @open-telemetry/java-approvers or @open-telemetry/java-instrumentation-approvers as well

@jack-berg can you check?


How can I throw the http.request.on('timeout') with Nock?

This is the .js code that I want to test.
Get(incomingUrl) {
        const url = url.parse(incomingUrl);
        const httpSendOptions = {
          protocol: url.protocol,
          host: cUrlPurlarse.hostname,
          port: (url.port ? url.port : 80),
          path: url.path,
          method: httpMethod.get,
          timeout: 200
        };
        const req = http.request(httpSendOptions);

        req.on('response', response =>
        {
          // do stuff
        });
        req.on('timeout', () =>
        {
          console.log('time out is throwed');
          req.destroy();
        });
        req.on('error', error => this.requestFailureHandler(client, `error ${error.message}`));

        req.end();
      }
}

Now this is my test that I have atm:
it.only('should timeout', done =>
    {
      nock('http://localhost').get('/api/v1/keepMeAlive').socketDelay(100).reply(200);
      sut.Get(incomingUrl);

      setTimeout(() =>
      {
        // expect log line with 'time out is throwed'
        done();
      });
    });

Versions:
"nock": "^9.2.3",
"node": 8.11.1,
"npm": 5.8.0

Hey I’m out vacationing right now, I’ll be back end of April. I think there are tests in nock that test for both request & response timeouts, can you look trough the current nock tests and see if you find something?

Hello,
I have seen al tests, but still can't throw that timeout.
Greetings,
LittleGnome


[Release-1.28] - k3s crashes if I do not start the cloud-provider

Backport fix for k3s crashes if I do not start the cloud-provider

#10068

Validated on Version:
-$   k3s version v1.28.10+k3s-7de7adb2 (7de7adb2)

Environment Details
Infrastructure
Cloud EC2 instance
Node(s) CPU architecture, OS, and Version:
Ubuntu
AMD
Cluster Configuration:
-1 nodes
config;

 sudo bash -c 'cat <<EOF>>/etc/rancher/k3s/config.yaml
write-kubeconfig-mode: 644
secrets-encryption: true
cluster-init: true
selinux: true
kubelet-arg:
 - cloud-provider=external
disable-cloud-controller: true
disable: servicelb
EOF'

Steps to validate the fix

start k3s with config above
Validate that it not crashes
Validate nodes and pods

Reproduction Issue:

 k3s version v1.29.5+k3s1 (4e53a323)

  journalctl -xeu k3s.service | grep "timed"
May 31 12:01:41 ip-  k3s[4434]: time="2024-05-31T12:01:41Z" level=fatal msg="network policy controller timed out waiting for node.cloudprovider.kubernetes.io/uninitialized taint to be removed from Node  : timed out waiting for the condition"

 :~$ systemctl status k3s  server.service
Unit server.service could not be found.
● k3s.service - Lightweight Kubernetes
     Loaded: loaded (/etc/systemd/system/k3s.service; enabled; vendor preset: enabled)
     Active: activating (auto-restart) (Result: exit-code) since Fri 2024-05-31 12:04:28 UTC; 5s ago
       Docs: https://k3s.io
    Process: 4934 ExecStartPre=/bin/sh -xc ! /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service 2>/dev/null (code=exited, status=0/SUCCESS)
    Process: 4936 ExecStartPre=/sbin/modprobe br_netfilter (code=exited, status=0/SUCCESS)
    Process: 4937 ExecStartPre=/sbin/modprobe overlay (code=exited, status=0/SUCCESS)
    Process: 4938 ExecStart=/usr/local/bin/k3s server --cluster-init --token secret --write-kubeconfig-mode=644 (code=exited, status=1/FAILURE)
   Main PID: 4938 (code=exited, status=1/FAILURE)
        CPU: 29.239s

Validation Results:

$ journalctl -xeu k3s.service | grep "timed"
<no logs>

  $ systemctl status k3s  server.service
Unit server.service could not be found.
● k3s.service - Lightweight Kubernetes
     Loaded: loaded (/etc/systemd/system/k3s.service; enabled; vendor preset: enabled)
     Active: active (running)
       Docs: https://k3s.io

:~$ systemctl status k3s  server.service
Unit server.service could not be found.
● k3s.service - Lightweight Kubernetes
     Loaded: loaded (/etc/systemd/system/k3s.service; enabled; vendor preset: enabled)
     Active: active (running)

 k get nodes,pods -A
NAME                    STATUS   ROLES                       AGE   VERSION
node/ip   Ready    control-plane,etcd,master   89s   v1.28.10+k3s-7de7adb2

NAMESPACE     NAME                                         READY   STATUS    RESTARTS   AGE
kube-system   pod/coredns-6799fbcd5-q92l6                  0/1     Pending   0          73s
kube-system   pod/helm-install-traefik-crd-v597m           0/1     Pending   0          73s
kube-system   pod/helm-install-traefik-vn459               0/1     Pending   0          73s
kube-system   pod/local-path-provisioner-6f5d79df6-s844t   0/1     Pending   0          73s
kube-system   pod/metrics-server-54fd9b65b-4s6gr           0/1     Pending   0          73s


Enhance daterange control in Ensemble

please see the attached video
https://github.com/EnsembleUI/ensemble/assets/10066434/47eedf91-d36f-4a48-bf7b-1c3aa1047a3f
Basically we need the following for the DateRange component -
custom widget in EDL for each date block. The actual date number is passed to this widget as an input
@vusters @evshi @vinothvino42  what do you think?
This is needed for a customer

The design requirements have changed a bit, talk to me before starting

@sharjeelyunus can you please share the latest design for this widget as the video I posted is out of dat

There are 2 UIs for that:

Calendar Widget
DatePicker Widget

Here is the Calendar UIs, Calendar widget should be able to select the date range (startDate - endDate), On load it will show calendar on the whole screen with a bottomModal that shows seleted dates. If there is already data i.e from API we get blocked/booked dates, it should show that as well.

DatePicker Widget, we can show bottomModal with DatePicker, This date picker should be able to select the date range (startDate - endDate) and give us the selectedDate on change or save

@vinothvino42 if you have any confusion, feel free to reach out, we can have a call, and will let you know exactly how we need it

@vinothvino42 assigning to you. This is ready, please prioritize highly as a customer is waiting for it. Get in touch with @sharjeelyunus if you need more info.

@kmahmood74 Okay I'll work on this issue from tomorrow

@vusters will be taking care of it

@snehmehta Sending this to you. I looked at a few packages and table_calendar fits most of the requirements (also looked at calendar_date_picker2). The only one that may require us to extend the package is column and row spans (to overlay our own widget over several cells). I didn't get far and won't get to this for a while. Please pick this up this high priority item.

@snehmehta @vusters I think this would be best if we provide two actions -
selectDate
selectDateRange
This will allow dev to invoke this action from anywhere and set its properties. @sharjeelyunus already have a use case where the calendar icon appears without the input field to put the date.
Can we please get to this right away, this is BLOCKING a customer for weeks now.


[Enhancement] (compaction) support parallel compaction for single replica

Search before asking

[X] I had searched in the issues and found no similar issues.

Description
Currently only one thread can do compaction for a tablet, but some case compaction may cost
a lot of time and we may able to start other thread do compaction.
Solution
multi-thread compaction for one tablet, modify meta in lock
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi, I’m new to Doris, but I’m really interested in this issue. Would it be possible for me to take on the task of implementing this feature? I would greatly appreciate the opportunity to contribute to the project.

I'm so sorry that this issue has already been assigned to @gitccl and you can choose another one if it is convenient for you

Hi, I’m new to Doris, but I’m really interested in this issue. Would it be possible for me to take on the task of implementing this feature? I would greatly appreciate the opportunity to contribute to the project.

I'm sorry that I picked this issue yesterday, There are still some issues in #17176.

Hi, I’m new to Doris, but I’m really interested in this issue. Would it be possible for me to take on the task of implementing this feature? I would greatly appreciate the opportunity to contribute to the project.

I'm so sorry that I picked this issue yesterday, there are still some issues in #17176, feel free to pick another one in #17176 if you're interested.

No problem at all. Thank you for letting me know. I’ll take a look at #17176 and choose another issue to work on.


When song from autoplaylist is unavailable - bot hangs

https://gist.github.com/DaFri-Nochiterov/8189c799453184beddd44c354e8f3f7b

3431252

Another error :new_moon_with_face:
https://gist.github.com/DaFri-Nochiterov/bbc53cbe6396d252cab305b5b3a9ce02

:ok:


Separate the Engine integration tests

Currently all tests in tfengine_test.go are non-hermetic and closer to integration tests, since they aren't Go-only tests. They expect the "terraform" binary to be installed and access GitHub Releases.
Rename this file so that if unit tests are added in the future, there's a clear separation.

Is there supposed to be a renamed file?

Is there supposed to be a renamed file?

Yes. I just added it, it was ignored by .gitignore before.

I think just calling it integration_test.go for now is fine. We might have a 'full' integration test later on though that actually applies things too, so we may need a way to separate this 'semi' integration test from that.

I think just calling it integration_test.go for now is fine. We might have a 'full' integration test later on though that actually applies things too, so we may need a way to separate this 'semi' integration test from that.

Done.


Obsolete javax.xml.bind:jaxb-api dependency

I don't know from where but liquibase-core contains javax.xml.bind:jaxb-api as a direct compile dependency. Looking in the liquibase-core/pom.xml I cannot see the dependency being set. On top of that Liquibase core uses the java SAXParser.
I have tried the latest release (4.3.5) in this repository. That repository was an example repository that showcased the problem that existed in 3.8.x Liquibase when run under Java 11 without the jaxb-api. However, it seems like the problem has been resolved and Liquibase (at least core) runs correctly on Java 11 without the need of the jaxb-api.
Is it possible for you to remove this dependency from liquibase-core?

I did some more analysis on this and it seems like the dependency is needed by Liquibase Pro. More precisely by DaticalTrueLicenseService. If the dependency is exclude then there won't be a LicenseService and there might be a NullPointerException at some point.
e.g.
Caused by: liquibase.exception.DatabaseException: liquibase.exception.LiquibaseException: java.lang.NullPointerException
	at liquibase.Liquibase.dropAll(Liquibase.java:1804)
	at liquibase.Liquibase.dropAll(Liquibase.java:1767)
	at org.flowable.common.engine.impl.db.LiquibaseBasedSchemaManager.schemaDrop(LiquibaseBasedSchemaManager.java:116)
	... 40 more
Caused by: liquibase.exception.LiquibaseException: java.lang.NullPointerException
	at liquibase.Liquibase.runInScope(Liquibase.java:2374)
	at liquibase.Liquibase.dropAll(Liquibase.java:1783)
	... 42 more
Caused by: java.lang.NullPointerException
	at com.datical.liquibase.ext.command.RollbackOneChangeSetCommand.getPriority(Unknown Source)
	at liquibase.command.CommandFactory$1.compare(CommandFactory.java:49)
	at liquibase.command.CommandFactory$1.compare(CommandFactory.java:46)
	at java.base/java.util.TimSort.binarySort(TimSort.java:296)
	at java.base/java.util.TimSort.sort(TimSort.java:221)
	at java.base/java.util.Arrays.sort(Arrays.java:1515)
	at java.base/java.util.ArrayList.sort(ArrayList.java:1750)
	at java.base/java.util.Collections.sort(Collections.java:179)
	at liquibase.command.CommandFactory.getCommand(CommandFactory.java:55)
	at liquibase.Liquibase$15.run(Liquibase.java:1787)
	at liquibase.Scope.lambda$child$0(Scope.java:160)
	at liquibase.Scope.child(Scope.java:169)
	at liquibase.Scope.child(Scope.java:159)
	at liquibase.Scope.child(Scope.java:138)
	at liquibase.Liquibase.runInScope(Liquibase.java:2369)
	... 43 more

We have been working on our 3rd party dependency setup a bit, and with the latest code in master I'm finding that everything works without the jaxb dependencies anymore. Even the pro code.
I created #1882 for additional testing to make sure I didn't miss anything.

That is great to hear @nvoxland.

I thought maybe I'd need to shade them or something, but when I created #1882 for additional testing everything worked.

It would be good if we can avoid shading as the liquibase-core jar is big enough as it is already (3.2 MB currently).

With further testing, we are still needing the jaxb dependencies for the pro license management. I did find a problem where the missing jaxb libraries produce an unhelpful null pointer exception that will be fixed in #1931, but beyond that I'll have to close this as "won't do" for now.
We have plans to re-evaluate our license management at some point and reducing dependencies are part of those requirements. But that is a larger/later project.


DOC: Add pybind11 requirment to HACKING.rst.txt

The addition of the scipy.fft module (#10238) adds pybind11 as an additional
build time dependency. This has already been documented in
INSTALL.rst.txt (#10348) but not in HACKING.rst.txt. This commit adds
pybind11 to the required dependencies.

@larsoner if this seems OK would you merge this?
I'm not sure if you're the correct person to ask but it's a straight forward one-line change and you merged the INSTALL.rst.txt.

@mdhaber okay with you to add this? It will require more work on your part to sort out in #10286.
Alternatively, if #10286 is 99% ready to go, you could just add this there, or @Kai-Striega could make a PR into your branch.

@larsmans sorry I haven't kept up with #10286. I'll be happy to follow @mdhaber's lead on this one.

Thanks for catching this @larsoner. Yes I can work that into the rest of the documentation. @Kai-Striega I'll keep you posted.

Adding wontfix label as it will be added in #10286. I'll defer closing the PR until that PR has been merged.

It probably should say what version of pybind11 is required.
It doesn't seem to build on pybind11 2.0.1 (the version on Debian stable).

@peterbell10 do you know what the minimum requires version for pybind11 is? Any released version is fine I think; for Cython we regularly require the latest version too. But if 2.1 or 2.2.x works, that'd be better given that 2.3.0 is less than a month old.

I've had a look at the changelog and I think the minimum is 2.2.0 because it uses PYBIND11_MODULE. However, I've been listing the minimum as 2.2.4 (September 2018) since that was the version used for development:
https://github.com/scipy/scipy/blob/1238d2d52eaf988cdd43b2173dd527c433d1818c/pyproject.toml#L9
https://github.com/scipy/scipy/blob/1238d2d52eaf988cdd43b2173dd527c433d1818c/setup.py#L474
Do these not actually change the setup behaviour?

Thanks, 2.2.4 sounds good. Requiring the latest bugfix release of 2.2 (or any minor release) sounds like a healthy idea.
The pyproject.toml one is only involved when you'd do pip install . or pip install -e .
The setup.py one is correct and also helps when using pip, but doesn't actually do anything for python setup.py build_ext -i. If I uninstall pybind11 and run that, the failure shows up later:
scipy/fft/_pocketfft/pypocketfft.cxx:13:10: fatal error: 'pybind11/pybind11.h' file not found
#include <pybind11/pybind11.h>
         ^~~~~~~~~~~~~~~~~~~~~
1 error generated.
error: Command "g++ -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -g -fwrapv -O3 -Wall -I/Users/rgommers/anaconda3/include -arch x86_64 -I/Users/rgommers/anaconda3/include -arch x86_64 -I/Users/rgommers/.local/include/python3.6m -I/Users/rgommers/anaconda3/include/python3.6m -I/Users/rgommers/anaconda3/lib/python3.6/site-packages/numpy/core/include -I/Users/rgommers/anaconda3/include/python3.6m -c scipy/fft/_pocketfft/pypocketfft.cxx -o build/temp.macosx-10.7-x86_64-3.6/scipy/fft/_pocketfft/pypocketfft.o -MMD -MF build/temp.macosx-10.7-x86_64-3.6/scipy/fft/_pocketfft/pypocketfft.o.d --std=c++14 -fvisibility=hidden -mmacosx-version-min=10.7 -stdlib=libc++" failed with exit status 1

Anyway, the code is fine, so if the docs say 2.2.4 we've done all we can do here I think - the rest is just Python build system annoyances


Depict Network discovery and Routing state maintenance flows

Output: sequence diagrams for both flows in https://miro.com/app/board/o9J_lSPb2vk=/

Obsoleted by #1210


nixosTests: Reraise exceptions in subtests so they stop the test

Motivation for this change
#72828
While porting the printing test i realized that if an assert triggers within a subtest, then this is logged but does not lead to test abort. This was bad because without successful assertions the rest of the test didn't make any sense.
I changed this passage of the test driver so that it gives extra-info in which subtest the problem occured and then leave it to the global exception handling to fail the whole test.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This basically depends on whether we want to use subtests to describe individual independent things / testcases on machines that don't necessarily depend on each other (A), or just use them as a way to group / give a heading to a bunch of statements (B).
The current behaviour (both in python and perl) is to add the an error message to failed_tests, but keep going with the next one if I'm not mistaken (cc @globin https://github.com/NixOS/nixpkgs/pull/74089), which assumes (A)
However, I think we mostly do B in many tests, even though we probably shouldn't. WDYT?
I don't think we should change semantics here with the perl driver still around.

This basically depends on whether we want to use subtests to describe individual independent things / testcases on machines that don't necessarily depend on each other (A), or just use them as a way to group / give a heading to a bunch of statements (B).

It generally makes sense to enable the user to decide which things should make tests fail and which should not.

The current behaviour (both in python and perl) is to add the an error message to failed_tests, but keep going with the next one if I'm not mistaken (cc @globin #74089), which assumes (A)

True, but i observed this behavior to do no good in the many many tests that i have ported.

However, I think we mostly do B in many tests, even though we probably shouldn't. WDYT?

The vast majority of tests that i have seen assumes behavior B. Behavior B is also a good default setting in my opinion.
We could longterm give users some wrapper that is similar to subtest but that is explicit in isolating exceptions from the code outside so users can kind of add diagnostic output. This however with the current situation does not make much sense at the time because what kind of test should succeed if something in it failed?

I agree that a lot of tests currenly assume B.
I'm just hesitant introducing semantic changes with both python and perl driver around, so would really feel better if we pick this up when the perl driver isn't around anymore.

I'm just hesitant introducing semantic changes with both python and perl driver around, so would really feel better if we pick this up when the perl driver isn't around anymore.

I agree that it is not cool to have different semantics in different implementations that share the same names.
But we have a lot of things in subtests that are necessary prerequisites to their next steps, but won't blow up visibly, leading to tests that time out (e.g. something must be done, but that fails, and then a test loops on wait_until_x which then can never happen) and are hard to debug.
Regarding the minority of still existing perl tests that remain untouched and working until they are ported (and people will see that they get more fails instead of less then, which is always better than the other way around), i suggest putting this in.

Just want to mention if there's any decision on this please merge after branch off.

Sure.

I stumbled more than once into python tests failing in a previous subtests, while I was staring at the later (still running) output.
As this only affects the behaviour of tests ultimately failing anyway, and tests run isolated too, I don't have any strong objections against this.

I pushed some cleanups, PTAL.

@flokli looks good!


@singleton

Very nice and simple framework! Would you consider adding a @singleton shortcut decorator to mark such classes? This would allow to avoid the use of container register in many cases (with tests where mocks are used the most common exception).
Since there is a global container this should not be a problem. The docs do not mention singleton, but I see it is implemented.
Here a quick and dirty proof of concept, that works in the simple case:
import {container, decorators} from "tsyringe";

export const {injectable} = decorators;

export function singleton(constructor: any) {
    container.register(
        constructor,
        {useClass: constructor},
        {singleton: true}
    );

Thanks! I would definitely accept that decorator. If you want to create a PR I'd be happy to review, otherwise I can add the feature in the not too distant future.

ok, I'm playing with it with a concrete use case. When I'll have written the tests for the code I'll submit a push request.
I've seen in code that mostly the framework works with metadata and I'm not sure if in this case it is possible, too. My worry while working directly with container.register is what happens if you register the class a second time and this happens before the class is actually first instantiated. It could result in quite unpredictable behavior.
Or would you also try to go with metadata?

I'm not entirely sure what you mean? The @singleton decorator is guaranteed to register the class before the first instantiation.

Not sure that this would fit your use case but this is what I am currently using from my main entrypoint class.
@autoInjectable()
@registry([{
  token: Analytics,
  useClass: Analytics,
  options: {singleton: true}
}])
export class main{
  constructor(private analytics?: Analytics,
                       private storage?: Storage,
                       private api?: Api){}
}

@autoInjectable()
export class Storage{
  constructor(private analytics?: Analytics){}
}

@autoInjectable()
export class Api{
  constructor(private analytics?: Analytics){}
}

I think the desired usage scenario is something like this:
// Foo.ts

@singleton()
export class Foo {}

// Bar.ts

import {Foo} from "./Foo.ts";

@injectable()
export class Bar {
  constructor(private foo: Foo) {}
}

No matter where you reference Foo from, it'll be a global singleton when resolved.


Write script logs to a log screen

Instead of waiting until program termination to dump all logs, we could instead have a screen for this. Better yet if we can have this in a screen tab of some sort. When in the main view, we could signal to the user that a new log has been made by making the log tab bold or something.
We should be able to write a sink for spdlog for this.

[ ] ground work (link the logger screen to the spdlog sink)
[ ] write update()

[ ] wrap entries if too long
[ ] indent succeeding lines so the log level stands out
[ ] give the log level a colour

[ ] implement movement (j/k/d/u)
[ ] implement attaching/detaching from new entries (so we don't scroll past something important)
[ ] notify the user of new entries if the log isn't the focused screen

When it comes to scrolling, while the user switches to the log (and thus marking all logs as read) there might be a big amount "outside" of the screen that requires scolling to see. If the user then switches away from the log, these actually unread messages will still be considered read.

Scrolling has been implemented, but when we have reached the top of the entries, we will need to scroll an appropriate amount of times down again to actually "scroll the whole screen" down. We can probably fix this by just changing what we consider the top-most entry.

We'll scrap log indention for now. If we indent by some arbitrary amount, the capacity() function will be off. Perhaps this can be done by using some lambda trickery — passing a void function from capacity() and non-void when actually drawing (ugly) — but nevertheless, I'm laying that feature on ice until post-release.

The log screen is done for now. An emulation of a "screen-scroll" is yet to be implemented, but I have the feeling that I'll stumble upon a problem alike is later in development. I'm branching that to a new issue and closing this.


fix(cli): prevent accidental bootstrapping of an older package-operat…

Closes #304
Fixes #304
📑 Description

This PR fixes the accidental bootstrapping of an older package-operator version.
✅ Checks

[ ] My code requires changes to the documentation
[ ] I have updated the documentation as required

ℹ Additional Information

Is this what we are expecting?

Here I have installed the glasskube releases v0.2.1:

And this is a wrong url google.com

Here I have made the necessary changes, but when I bootstrap from v0.3.0 to v0.2.1 via --url it doesn't show the YesNo Prompt.

Rebased && Pushed

I hope this looks good!


How to implement this project in React Native?

Thanks for this wonderful package. I have a react native project and I couldn't find any readme for integrating with React Native. Could you point me to tutorial to implement this in React native.

To implement this in React Native, you will need to create a native module to bridge the code between React Native and Android, please see this resource on this topic. Furthermore, if you are implementing the detection code in C/C++ like in this project, you will also need to create a native JNI (Java Native Interface) library that can be loaded from the Android SDK, here is a good starting guide. You could alternatively implement the detection code in Java/Kotlin and bypass the JNI step but that would leave your application at risk of hooking from Frida.

@pradsirwt , I'm also looking for react native logic to detect Frida. Were you able to use this repo to create a native module for Frida detection ?

@vinithreddy3  and @pradsirwt Please use below library to detect Frida and avoid frida to bypass root checks
react-native-detect-frida


Error during login

Hello, im using the example code that comes with the flutter_facebook_login.
It builds fine on Windows using Visual Studio Code, running on ANDROID
It displays the Login button, when i press it then it gives error that something went wrong, .... error performing query while running on my android phone device
I didnt even get a chance to log in, soon as i click the button it gives that error right away.
Do i need some code from facebook, maybe app ID or something else?
Any idea what can cause that?

Fixed it, i created an app ID on facebook and it logged me in..... sort of, it logged me in, displayed my photo, then when i clicked continue, it then gave a SERVER_ERROR 1349195 The key hash does not match any stored key hashes

I have the same problem. They solved it?

same here!

Solved! check this #32
Get the key hash and save it in your facebook developer console

I had a lot of headache about this,
this is how I solved:

Get your SHA-1 fingerprint, from Android Studio the easiest way is to create a new project with a Google Maps Activity. Once created it will start with a opened file "google_maps_api.xml" where you can find your SHA-1 certificate fingerprint (comment block).
source: https://stackoverflow.com/questions/27609442/how-to-get-the-sha-1-fingerprint-certificate-in-android-studio-for-debug-mode

Copy the SHA1 value and and open http://tomeko.net/online_tools/hex_to_base64.php to convert your SHA1 value to base64. This is what Facebook requires get the generated hash " ********************= " and copy the key hash to the facebook app.
source: https://stackoverflow.com/questions/54680955/sign-in-with-facebook-error-code-1349195-ionic

Hope it helps.

@Mapk26 Work for me! Thx


ShowDisplayStrings = DisplayStringsState.ForVisualizedItems

HI
is there a reason Natvis.ShowDisplayStrings is not DisplayStringsState.On ?
it seems to prevent DisplayStrings from showing up

I think the answer is that we found that GDB was too slow at evaluating the display strings, so for visualized items we instead added a child node to show the visualized value instead. @paulmaybee do I have this right?

Can I make a PR that makes this a LaunchOption (bool ShowDisplayString, default=false) ?
I think having DisplayStrings show up immediately in datatips or watchwindow is pretty helpful, even when gdb isn't super fast.

That is fine with me. @paulmaybee, @chuckries can you think of any gotchas that would make that undesirable?

Seems ok.
From: Gregg Miskelly<EMAIL_ADDRESS>Sent: Monday, December 7, 2015 12:47 PM
To: Microsoft/MIEngine<EMAIL_ADDRESS>Cc: Paul Maybee<EMAIL_ADDRESS>Subject: Re: [MIEngine] ShowDisplayStrings = DisplayStringsState.ForVisualizedItems (#128)
That is fine with me. @paulmaybeehttps://github.com/paulmaybee, @chuckrieshttps://github.com/chuckries can you think of any gotchas that would make that undesirable?
—
Reply to this email directly or view it on GitHubhttps://github.com/Microsoft/MIEngine/issues/128#issuecomment-162656915.

This would be inaccessible in the current Android/iOS project system scenarios since we would not be able to adjust the LaunchOptions to include this. We would have to expose it through the project system UI or make it also enabled through an environment variable or registry setting.

Right, but we don't have any UI now (except for the command window) where we could stick this option in a user-exposed way. So adding it to the launch options XML will at least allow RYDB3RG to use it in his scenario (I am assuming you aren't doing iOS/Android development?).

Yes, PC only (x64), no iOS/Android. I wasn't aware that IOS/Android launcher work differently, I agree that it would be strange to not have this option in those platforms. I don't mind using a patched version myself, so I don't persist on a PR

So on Android and iOS the launch options XML is something dynamically generated by the Visual C++ project system. So in order for this setting to be tweaked in that case, the Visual C++ project system would need to expose some UI and add in to the launch options XML that they created. So the new feature that you are creating will not be exposed to folks using our Android/iOS C++ tooling. But that is okay, you have still added support for this so we could add it to those project systems if we want. I would just recommend adding it to the 'common attributes' inside the XSD so that we can trivial get this support in any scenario that wants it.

I made a pullrequest: https://github.com/Microsoft/MIEngine/pull/133


Add shortcut to run a query

In the workbench, we should have a shortcut to run a query. This shortcut should only work when the user has the workbench editor on focus.

Suggest shortcut: Ctrl + Enter or Cmd + Enter (for macOS):

@azaddhirajkumar please do not close isses.


Broken coverage report

Looks like it's an issue with the gcrov action
https://github.com/actions-rs/grcov/issues/142
Making an issue so if it takes very long to resolve on the gcrov side, we can track progress on however we decide to address it.

LOL that repo hasn't been touched in 3 years, I'll wager it's something that'll take a while if we don't tackle it 😂

It looks like cargo-tarpaulin is still going strong, might start in on what it looks like to go back to it for coverage. It was a while ago, but I remember there were a pile of lines reported as uncovered that gcrov saw were covered... i do feel like checking in on the state of that, maybe it's been resolved 😄 If not though, a pile of lines reported as uncovered is better than a broken build!

woah @CrockAgile I really like the looks of that PR (#132) to use LLVM coverage to replace gcrov. I'll vote for that for sure


Uber Scheduling Rides using Android SDK

I would like to schedule Uber rides using Android SDK. Is there any API for this?
On a button click, i should be able to schedule the ride. (Done using Uber SDK Integration).

Hey @imprashanthguru, Github is only for bug reports. Please use Stackoverflow with the uber-api tag for product help.


ci: Set alias in tasks with artifacts in cirrus.yml

This change simplifies artifact links by using the task alias. It also allows changing the task name without breaking artifact links.

@MarcoFalke wdyt?

Looks good and the links seem to work.


Testing request: Running CLI using exe generated by Pyinstaller

Instructions
Rough timeline:

@carmen-chau will test whether CLI -B fix as mentioned in #29 works using the exe setup on her computer.

Update on this: The CLI -B fix works, however, there is a minor visual bug where after the script terminates, due to the print("") statement, the terminal prompt would be in a new line. I honestly think this is OK to leave, but something worth noting

@carmen-chau will then test the same fix but with @moonsdust 's exported EXE

Currently facing the following issue:

Perhaps this might contain a fix?  Unsure, likely need to consult @moonsdust for advice + do further reading/testing

@carmen-chau would then detail the exe generation instructions that she took. @moonsdust would do the same

Eventually, @carmen-chau would need to share her exe with @moonsdust for testing.

https://github.com/pyinstaller/pyinstaller/issues/5434

I have now packaged the exe file into a dmg file for MacOS and it gets rid of all the popups!


getAuthor() function not working correctly for RSS feed.

I have been using the Drupal 8 Feeds module and encountered an issue when interacting with zend-feed. I am using an XML feed that has a <author> field and it is not being handled correctly by the getAuthor() function.
I have made an alteration to /vendor/zendframework/zend-feed/src/Reader/Entry/Rss.php
/**
     * Get an author entry
     *
     * @param int $index
     * @return string
     */
    public function getAuthor($index = 0)
    {
        $author = $this->xpath->evaluate('string(' . $this->xpathQueryRss . '/author)');
        return $author;
    }

The changes above fixed my problem and the <author> field is now importing correctly.

@k-cogswell

The changes above fixed my problem and the  field is now importing correctly.

With your changes you ignore the index and break the unit tests. Have a look at all these tests: https://github.com/zendframework/zend-feed/blob/master/test/Reader/Feed/RssTest.php#L758

I am using an XML feed that has a  field and it is not being handled correctly by the getAuthor() function.

Can you provide the original RSS feed with the author field?

@froschdesign
I have attached an example item from the RSS feed I am using.
I think the issue was my feed does not have any nested values inside the <author> tag while it seems the getAuthor() function is looking for <name> and <email>.
RSS_Example.txt

@k-cogswell

The feed is wrong, because the value of author is not an email address. (see at the RSS 2.0 specification)
zend-feed checks for an email address.


replace deprecated failure with Display trait implementation

failure crate is marked as deprecated: https://github.com/rust-lang-nursery/failure/pull/347
This change removes the failure usage and replace with fmt::Display trait implementation.

looks good to me, thanks :+1:


Do any functions fire on maxFileSize over limit?

I am trying to have some custom wording / events happen when a user tries to upload over the max file size. Currently as far as I can tell you can only edit the string that gets sent back when this happens. Is there a function that fires this event? If so which one

No callback for maxFile reach

Is there any way to trigger an error when file size exceeded the limit


White space after filter is applied.

Describe the bug
White space appear on the Datagrid component after applying filter to recude the items.
How to reproduce
Code sample:
        <clr-dg-column [clrDgField]="'domainType'">
          <ng-container *clrDgHideableColumn="{ hidden: false }">
            Domain Type
          </ng-container>
        </clr-dg-column>
        <clr-dg-column [clrDgField]="'productType'">
          <ng-container *clrDgHideableColumn="{ hidden: false }">
            Product Type
          </ng-container>
        </clr-dg-column>
        <clr-dg-column [clrDgField]="'productAddress'">
          <ng-container *clrDgHideableColumn="{ hidden: false }">
            Product Address
          </ng-container>
        </clr-dg-column>
        <clr-dg-column [clrDgField]="'productVersion'">
          <ng-container *clrDgHideableColumn="{ hidden: false }">
            Product Version
          </ng-container>
        </clr-dg-column>

        <clr-dg-row
          *clrDgItems="let domain of wld.domains.data"
          [clrDgItem]="domain"
        >
          <clr-dg-cell>{{ domain.domainType }}</clr-dg-cell>
          <clr-dg-cell>{{ domain.productType }}</clr-dg-cell>
          <clr-dg-cell>{{ domain.productAddress }}</clr-dg-cell>
          <clr-dg-cell>{{ domain.productVersion }}</clr-dg-cell>
        </clr-dg-row>

        <clr-dg-footer>
          <clr-dg-pagination #pagination [clrDgPageSize]="10">
            <clr-dg-page-size [clrPageSizeOptions]="[10, 20, 50]"
              >Items per page</clr-dg-page-size
            >
            {{ pagination.firstItem + 1 }} - {{ pagination.lastItem + 1 }} of
            {{ pagination.totalItems }} items
          </clr-dg-pagination>
        </clr-dg-footer>
      </clr-datagrid>

Steps to reproduce the behavior:

Load Datagrid component with 20 items. Example from test env:

Apply filter which will reduce the number of displayed items. Example after filter:

White space will appear on the bottom.

Expected behavior:
Datagrid to compact white space and do not appear.
Versions
Clarity project:

[ ] Clarity Core
[X] Clarity Angular/UI

Clarity version:

[ ] v3.x
[ ] v4.x
[X] v5.x

Framework:

[X] Angular
[ ] React
[ ] Vue
[ ] Other:

Framework version:
Angular 13
Device:

Type: MacBook
OS: iOS
Browser Chrome, Firefox
Version 98.0.4758.102

Additional notes
Add any other notes about the problem here.

Hello @Tzvetelin88 - If I understand correctly the concern here is that when there are fewer rows than the height of the datagrid there is white space below the rows. Please let me know if I am mistaken.
This is working as intended. When a datagrid has pagination declared we can't know how many rows there will be on the last page. A UX choice was made to fix the height of the datagrid so that UI's avoided a vertical jumping effect on the page content when the number of rows was less than the rows / page value. In the case above, this also applies when a user filters the data set.
I'm going to close this as no fix needed b/c I believe the datagrid is working as intended.

Hello @hippee-lee , yes this is right - when there are fewer rows than the height of the datagrid there is white space below the rows.
Is there a way to by-pass fixed height and eliminate white space - based on the rows(like the example above), even if we sacrifice jumping effect?

I also notice another issue with this. If we have 250+ items for example, and I do items per page to be 50,

and go thru the pages, again white space is appearing, even that we have more pages with items. Will try to make sandbox demo for it


[RFC] Randomized names next to mouse pointers.

Based on #953.
A few example names it generates:

lively deer
thankful rat
polite cow
witty rabbit
calm bee

Don't know if we want this or to ask the user for their name. If we want this for now, click the merge button. If not no worries :)

Is it possible to show the name to the user somehow so they can know who’s who?

I feel like we want both, a default generated name and the ability to change. I was thinking of putting the name setting in the giant modal where there’s the stop session button.


chroma reload new data support?

If my data has changed and I need to reload the new data, does chroma have a method similar to hot reload, or do I need to create a new object to get a new chroma?

@stoneLee81 hi there - what do you mean by "reload the new data"?


Update CNI plugins

CNI 0.9.0 added support to automatically select the master NIC - this is very useful when running microk8s & multus in clusters with different NIC names.
It also avoids having to either manually rename the NICs or creating bridges.
Fixes: https://github.com/ubuntu/microk8s/issues/2019
Also verify you have:

[x] Read the contributions page.
[x] Submitted the CLA form, if you are a first time contributor.

Thank you for this PR @angelnu .
Would you be fine if we update to v0.8.7 [1] instead of v0.9.1? The reason is that Kubernetes has currently v0.8.7 as its build dependency [2].
[1] https://github.com/containernetworking/plugins/releases/tag/v0.8.7
[2] https://github.com/kubernetes/kubernetes/blob/master/build/dependencies.yaml#L46

@angelnu would cni pluging v0.8.7 [1] be fine for your case?
[1] https://github.com/containernetworking/plugins/releases/tag/v0.8.7

Sorry, I missed you first reply...
Yes, 0.8.7 should work since it supports optional masters: https://v0-8-7.cni.dev/plugins/main/macvlan/


Add UnitarySynthesis page

Add page on UnitarySynthesis, with an explanation of the Quantum Shannon Decomposition and the multiplexor formalism.

Superseded by #1078 to keep track in the larger issue: #1046


[Markdown]  Failing specs before doing anything

The exercise mentioned all tests should be passing initially. When I run the specs, four specs are failing:
crystal spec spec/markdown_spec.cr:93 # Markdown unordered lists
crystal spec spec/markdown_spec.cr:102 # Markdown With a little bit of everything
crystal spec spec/markdown_spec.cr:120 # Markdown with markdown symbols in the list item text that should not be interpreted
crystal spec spec/markdown_spec.cr:137 # Markdown unordered lists close properly with preceding and following lines

After modifying 2 places, all specs had passed:

At last line of Markdown#to_html, change lines.join("\n") to lines.join. Because it seems like html output in specs does not contains '\n'.
At second condition of Markdown#parse_list, change !previous_line.starts_with?('*') to !previous_line.starts_with?(/<(ul|li)>/). Old condition failed because it checks previous line in markdown format. If there is previous line, it is already transformed into html format.

Hey @ls1955, good catch. Would you mind creating a PR with your suggested changes?

Good catch, I will look into making the ci able to test against the normal solution for this exercise as well.


client never returns

this code
var Keen = require("keen-js")
var fs = require("fs")
var client = new Keen({
    projectId: "myprojectid",   // String (required always)
    writeKey: "mywritekey",     // String (required for sending data)
    readKey: "myreadkey",       // String (required for querying data)
    protocol: "https",              // String (optional: https | http | auto)
    host: "api.keen.io/3.0",        // String (optional)
    requestType: "jsonp"            // String (optional: jsonp, xhr, beacon)
  });

 fs.readFile("jls.json",function(err,data) {
 	client.addEvents(data, function(err, res){
  		if (err) {
    		console.log("tihs")
  		} else {
    		console.log("done")
  		}
	});
})

just hangs when trying to send the data. The jls.json file contains an array of 1000 items, and is only 244974 bytes in size
am I doing something wrong ? Or is there a problem / bug ?
thanks

Hey @jmls, can you send me the JSON file (or a structural sample) that you're running? I'm guessing there's something awry with that format<EMAIL_ADDRESS>

hey, sorry, yes - it was my data structure. sorry for not letting you know earlier

@jmls whew! happy to hear that :) also glad to hear you're cruising along again. Please hit me up if you have any other questions or recommendations for the lib.


fix(plugin-chart-pivot-table): color weight of Conditional formatting metrics not work

SUMMARY

Since our color scheme uses hex values, the previous way of RGB is not working, so we fix it here.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

before

after

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[x] Has associated issue: https://github.com/apache/superset/issues/20391
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

@stephenLYZ this overlaps (and now conflicts) with #20353 so I'm trying to figure out the best way to fix my conflicts.
So is everything moving toward 8 digit hex colors for alpha, rather than 'rgba(R,G,B,A)' strings? Looks like it is so I'll assume so for now.
If so, there may be future issues in https://github.com/apache/superset/blob/master/superset-frontend/packages/superset-ui-core/src/color/utils.ts since it expects hex codes to be 3 or 6 digits.

@stevetracvc hi, thanks for your work! At the moment I think color schemes are hex colors, so here I still use 8 digit hex colors for consistency, but we can't completely avoid using rgba, like linear-gradient property. so if you need to introduce rgba in your PR it's also acceptable. BTW,  there is an emotion-rgba library that adds alpha channels to rgb. Not sure if we can use this directly.


Add support for nested classes

Build and tests passed.

Build and tests passed.

Yah the conflicts are next, wanted to get it working with the updates first

Rebased to fix the merge conflicts

Build and tests passed.


Missing covariant check on type param

The following gives no strong mode errors and prints 'hello1' in DDC - adding a string and int without error.
Where is the missing runtime check?  :-)  @leafpetersen @jmesserly
typedef T Callback<T>(T val);

class Foo<T> {
  T x;

  Callback<T> _callback;

  Callback<T> get callback => _callback;
  void set callback(Callback<T> f) { _callback = f; }
}

void main() {
  Foo<int> f = new Foo<int>();
  f.callback = (x) => x + 1;

  Foo<Object> f2 = f;
  var result = f2.callback('hello');
  print(result);
}

I believe this is a dupe of https://github.com/dart-lang/sdk/issues/27259


scrublet ignores threshold

[x] I have checked that this issue has not already been reported.
[x] I have confirmed this bug exists on the latest version of scanpy.
[] (optional) I have confirmed this bug exists on the master branch of scanpy.

Minimal code sample (that we can copy&paste without having any data)
import scanpy as sc
adata = sc.datasets.pbmc3k()
sc.external.pp.scrublet(adata, threshold='I am ignored')

/opt/conda/lib/python3.7/site-packages/scanpy/preprocessing/_normalization.py:138: UserWarning: Revieved a view of an AnnData. Making a copy.
  view_to_actual(adata)

Automatically set threshold at doublet score = 0.27
Detected doublet rate = 1.5%
Estimated detectable doublet fraction = 44.3%
Overall doublet rate:
	Expected   = 5.0%
	Estimated  = 3.4%

Versions

scanpy==1.7.0 anndata==0.7.5 umap==0.5.1 numpy==1.20.0 scipy==1.6.0 pandas==1.2.1 scikit-learn==0.24.1 statsmodels==0.12.2 python-igraph==0.8.3 louvain==0.7.0 leidenalg==0.8.3

@pinin4fjords, could you look into this? Also, there may be some other arguments which are not being passed correctly. For example, n_prin_comps and use_approx_neighbors are not passed from scrublet to scrublet_call_doublets.

@ivirshup Honestly don't know what I was thinking here- the parameters are clearly not passed through. Perhaps I broke things when rearranging logic in the PR. In in any case I'll submit a fix soon.

PR with fix submitted, thanks @fabianrost84 for the report.


BAU: add CI using Github Actions

Should help ensure that we don't accidentally break the repo.
Replaces https://github.com/alphagov/dcs-python-client/pull/5, which was trying to do the same thing with Travis.

And the CI works - it correctly identified that pylint was failing. I've added a commit to fix the pylint failures, so it should be green now.


Review report scheduling logic

Two weeks ago I got two reports the same day and today I got the same one as last Friday sent again.

Couldn't reproduce or find any clues, instead added more verbose logging. Closing this until it pops up again.


node-sass needs to be upgraded to work with Ubuntu 18.04

Issue
It looks like node-sass needs to be upgraded in order to work with Ubuntu 18.04.
Steps to reproduce

On an Ubuntu 18.04 machine, clone the shingkgs repository.
Run yarn
Run yarn start.
You should now get output that looks like this:

yarn run v1.6.0
$ yarn run build-sass
$ node-sass --include-path='node_modules' src/css/index.scss src/index.css
/home/brian/Projects/shinkgs/node_modules/node-sass/lib/binding.js:13
      throw new Error(errors.unsupportedEnvironment());
      ^

Error: Node Sass does not yet support your current environment: Linux 64-bit with Unsupported runtime (57)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v4.5.2
    at module.exports (/home/brian/Projects/shinkgs/node_modules/node-sass/lib/binding.js:13:13)
    at Object.<anonymous> (/home/brian/Projects/shinkgs/node_modules/node-sass/lib/index.js:14:35)
    at Module._compile (module.js:652:30)
    at Object.Module._extensions..js (module.js:663:10)
    at Module.load (module.js:565:32)
    at tryModuleLoad (module.js:505:12)
    at Function.Module._load (module.js:497:3)
    at Module.require (module.js:596:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/home/brian/Projects/shinkgs/node_modules/node-sass/bin/node-sass:11:10)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Solution
Upgrading node-sass to to versoin 4.9.0 solves this problems.

hey @beejunk! Pull down the latest master; I pushed a fix for this in commit d920202

Hah, I just saw that you did this! Okay, closing down this issue...

no worries, thanks for the detailed report! 🙂


[Bug]Delete form widget fails intermittently

Steps:

As a part of the form widget spec we see tests related to delete widget failing intermittently.
Delete from properties / Delete from the keyboard is failing intermittently, this is after we optimized the test

@NandanAnantharamu what is expected here, Looks like this should be assigned to the owner of the test optimization

@somangshu as discussed, this is an intermittent issue, not a cypress issue.

@vivekverma2312 @YogeshJayaseelan can you verify this, if possible we will need some reproducible steps.
@NandanAnantharamu in case you know how to better debug this, Please let us know, Right now on cypress the only error i see is CypressError: Timed out retrying, I suspect something to do with eval here

@somangshu CypressError: Timed out retrying, this is seen because after delete the @updateLayout call happens. Since the Delete action hasn't worked the call hasn't happened and the test failed.

Is this still happening @NandanAnantharamu?


[Enhancement] Add more test coverage for QueryMessageProcessor

Before Creating the Enhancement Request

[X] I have confirmed that this should be classified as an enhancement rather than a bug/feature.

Summary
add more tests
Motivation
add more tests
Describe the Solution You'd Like
add more tests
Describe Alternatives You've Considered
no
Additional Context
No response

link #8262


adding imp leetcode questions

would like to add container with most water question

Great !
Go ahead and do more contributions :)


Not compatible with JupyterLab 3.0.15

There is an issue with the build system right now. You can also try a dev build: https://github.com/deshaw/jupyterlab-execute-time#development-install
https://github.com/deshaw/jupyterlab-execute-time/pull/37 is an attempt to fix it, but something is still not working.

Can you try 2.0.3 with<EMAIL_ADDRESS>While mybinder does not seem to work yet, that combo did work for me.

Even in 3.0.14 looks that it's not working =(

As a workaround, you can build from dev. See https://github.com/deshaw/jupyterlab-execute-time#contributing (this seems to be the same as https://github.com/deshaw/jupyterlab-execute-time/issues/32)

It works for me in lab Version 2.3.1

This should work with the new release. Be sure for 3.x you are installing from python and not npm (e.g. pip install jupyterlab_execute_time).
Closing, but feel free to reopen if you still have an issue!


Problem with intersection types

I have seen some wierd behaviour with the flow type checker. It seems that accessing fields that does not exist on an intersection type, incorrectly passes flow type checking.
type A = {
  x: string
}
type B = {
  y: string
}
type C = A & B
const cObj: C =  ....
console.log(cObj.fieldThatDoesNotExist); // Passes flow checking, why??
const aObj:  A  = c
console.log(aObj.fieldThatDoesNotExist); // Correctly fails flow checking! Because field is not defined in A

I couldn't reproduce this:
type A = {
  x: string
}
type B = {
  y: string
}
type C = A & B
const cObj: C = {x: "foo", y: "bar"}
console.log(cObj.fieldThatDoesNotExist);
const aObj:  A  = {x: "foo"}
console.log(aObj.fieldThatDoesNotExist);

On the first console.log line, I get property `fieldThatDoesNotExist`. Property cannot be accessed on any member of intersection type.

i had 0.46. was fixed in 0.47
0.47.0
Likely to cause new Flow errors:
We are now sealing the object type that is passed to a React component's props. This means Flow will start complaining if you try and access unknown React props.


set secureview flag based on addr

OCIS config for https://github.com/cs3org/reva/pull/4706
requires the reva bump

bumping reva as well, now


Expands info on config with kustomize

Fixes https://github.com/kubeflow/website/issues/1092
Goals:

Give people more guidance on how to manage their Kubeflow config.
Move the kustomize info into the section containing other config guides, because kustomize isn't really a component of Kubeflow, but rather the configuration manager. The guide therefore doesn't belong in the "components" section.

This change is

Preview:

https://deploy-preview-1093--competent-brattain-de2d6d.netlify.com/docs/other-guides/kustomize/
REDIRECT: https://deploy-preview-1093--competent-brattain-de2d6d.netlify.com/docs/components/misc/kustomize/
LINK FIXED: /docs/gke/deploy/deploy-cli.md
LINK FIXED: https://deploy-preview-1093--competent-brattain-de2d6d.netlify.com/docs/started/getting-started/#installing-command-line-tools

This PR is now ready for review. I'm applying a hold to allow for multiple reviewers.
/hold

/assign @richardsliu

/assign @yanniszark

@yanniszark @richardsliu Please would you take a look at this doc. The goal is to provide a platform-agnostic introduction to customizing Kubeflow with kustomize. If you have an examples to add or any corrections to make, they'd be very welcome!

/cc @aarondietz234
@aarondietz234 for tech writing review.

Thanks for the review @aarondietz234!

Thanks @richardsliu PTAL. I think this is ready to go now. Note that I've added an instruction to tear down the cluster before generate/apply, due to https://github.com/kubeflow/kubeflow/issues/3810

/hold cancel


What kind of programs can we submit to the repo?

I'm seeing a lot of programs here, and was hoping to contribute some code, but I'm not sure what exactly is the criteria for pushing files to this repository.
If possible, can you add a CONTRIBUTING.MD as a guide for others who may want to contribute?

Nice and simple really, write your code and submit it, no real criteria if you think it can help others then push it up here
Cheers

On 17 Nov 2018, at 09:45, Vinay Deshmukh<EMAIL_ADDRESS>wrote:
I'm seeing a lot of programs here, and was hoping to contribute some code, but I'm not sure what exactly is the criteria for pushing files to this repository.
If possible, can you add a CONTRIBUTING.MD as a guide for others who may want to contribute?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/geekcomputers/Python/issues/431, or mute the thread https://github.com/notifications/unsubscribe-auth/ABHa0uhy76BRG2g5CCOy60xX7KwcJa_Dks5uv9qxgaJpZM4YnXsD.

I think it's a very good policy.

Sure

@vinay-deshmukh Can this issue be closed?


Fix endlessly increasing memory consumption with the '-W' option

build_layout appends the current layouts to the vector syms, without clearing them beforehand. With the -W option, this code path is executed everytime the layout changes. Therefore, this leads to a huge, unnecessary memory consumption.

Thanks, indeed!