rex2nc does not work with all rex files

Rex2nc works correctly when I use one of the rex files included in the test directory Rich committed.
When I use one of the rex files included in the SLOSH package or one that I created using SLOSH, in the ReadRexHeader function the code stops with Abort (signal 6).
I am working  on a MacBook Pro with Intel Core processor. The version of SLOSH I am using is dated 1/20/2012.   Any idea?
Thank you

Can you confirm that SLOSH was compiled using a 32-bit compiler?
something like the following should tell you that:
file (slosh exec name)

I used 64 bit gcc with the option -DSIZEOF_LONG_INT=4.

... and I compiled rex2nc with gcc -m32

I compiled slosh with -m32, same problem ...

Just to be sure its not a Mac issue, I'd probably try compiling it on a Linux machine.  If that still fails, then perhaps something might have changed in the rex header.  The date I have on the last version of the converter (aka when it was originally developed) is Aug 2, 2011 which is a bit before your SLOSH code.  I'd recommend talking with AT and see if he has updated his rexout porgram.  This converter code was based on 1.3 of that.  If he has a new version, then the header may have changed and the converter may need updating.  However, in general AT was good about keeping backward compatible...so I'm still leaning toward a compiling, O/S, hardward-related issue...the rex stuff was very particular...

I opened and animated without errors my rex file (created with SLOSH compiled under OSX with -m32) using the SLOSH display on a Windows machine.  That makes me think that the problem I have in running rex2nc is not  related to OS X.  I emailed AT asking about updated rex headers. I haven't heard from him yet.

@donatellapasqualini has there been any progress on getting rex2nc to work?

@JRDavisUF, is this the most recent version of the code https://github.com/rsignell-usgs/rex2nc?

The key here is to build in 32 bit.  The current code is completely incompatible if compiled in 64 bit.  The netcdf library http://www.gfd-dennou.org/library/netcdf/unidata-mirror/netcdf-<IP_ADDRESS>.tar.gz used must also be compiled in 32-bit too and then linked to the code in order for the whole tool-chain to work properly.
I'll make a note on the readme that the code must be compiled in 32-bit mode.

Yes, 32 bit compilation is required.  Someone asked about this several years ago, but I guess this piece of info never made it into the documenation.  Specially, this is what I advised someone:
“Keep in mind that the rex format is a custom written "gif"-like compression.  As such, so you have to be very careful with the byte sizes of your variables.  I'm guessing it won't work, for example, if you try to use a 64-bit compiled version...at least in the sense of reading a rex file generated by a 32 bit executable.  So make sure you are doing a 32-bit compile...”
jrd
From: Phillip Wolfram<EMAIL_ADDRESS>Sent: Thursday, June 29, 2017 3:29 PM
To: ioos/comt<EMAIL_ADDRESS>Cc: Justin R. Davis<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [ioos/comt] rex2nc does not work with all rex files (#37)
The key here is to build in 32 bit. The current code is completely incompatible if compiled in 64 bit. The netcdf library http://www.gfd-dennou.org/library/netcdf/unidata-mirror/netcdf-<IP_ADDRESS>.tar.gz used must also be compiled in 32-bit too and then linked to the code in order for the whole tool-chain to work properly.
I'll make a note on the readme that the code must be compiled in 32-bit mode.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/ioos/comt/issues/37#issuecomment-312074950, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AGlJy6L-ZkkCph_pU2Ry-TCXJNXD8c8Gks5sI_rlgaJpZM4FS3MF.

Thanks a bunch for the confirmation @JRDavisUF!  Your help is much appreciated and has been key to good progress over the last week.

Hi there good folks. So it appears that if I build SLOSH with BIT=64, that rex2nc cannot read it, correct? Or, perhaps, some compiler flag could do the trick?

@briane678, I think you only can really work in 32-bit mode.  I wasn't able to get 64-bit to work.

Arthur Taylor (developer of the rex gif-like compression) was pretty adamant about 32-bit compilation.  I'd stick with that.


Missing Data elements

We should consider adding multiple Data elements for the Create, Delete, Network and View 'action' elements. All other 'actions' allow for multiple Data elements to carry additional information. These four are the only ones that don't. The only alternative is to place the 'action information' in Data elements of the 'subject of the action' (e.g. Object, Document, File, etc) which is NOT appropriate.

Noted that the Network element can only have one of Bind, Connect, Open, Close, Send, Recieve, Listen, Permit or Deny and all are of type NetworkComplexType which already holds unbounded Data sub-elements.
So no need to change this element, only the ObjectOutcomeComplexType element type.

Fixed in v3.1.0


migrate integration_test to flutter sdk

Description
Update integration_test to Flutter SDK.
Related Issues
#465
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

This is blocking #442, and also preventing the CI pipeline from upgrading from flutter-version: "2.2.1" to a recent version like 2.5.1. Can this be merged?

@alexbatalov great PR. thank you. Can you just add a changelog and bump a patch version on all of these plugins? I'll merge and release right away.


Add support for Dynamic Type to reload the table

Add shouldMonitorContentSize property.
This property allows for the observation of the UIContentSizeCategoryDidChangeNotification notification to reload the table when the user changes their preferences for Dynamic Text.

Thanks for the PR. I'm not sure about this though. It doesn't fee like "part" of the features for this component. This commit seems to be for more like a general table view functionality. We had something like this and more but we put them on a subclass of a SKStatefulTableViewController.


Cache

How can I use cache?
Cache Data
Key:
message:ISPXNB32R82Y766F
Value:
{
"message:ISPXNB32R82Y766F": {
"amount": 0,
"due_date": 44197,
"fiscal_code": "ISPXNB32R82Y766F",
"invalid_after_due_date": false,
"markdown": "# Welcome, Giovanni Rossi\\nYour fiscal code is ISPXNB32R82Y766F\\nI hope you will enjoy IO.",
"notice_number": 1,
"subject": "Welcome to IO, Giovanni"
}
}

just shown for debugging purposes


Update to the build file to modernize the docs

This commit throws out Docbook and gives us the modern look and feel for the docs. It uses Asciidoctor to generate the PDF.

Merged as https://github.com/spring-projects/spring-kafka/commit/f6caf5bb1efc13273dfa0f01179115462a580dca.
@Buzzardo ,
thank you for you contribution!


Propagating shown.bs.tab event into nested tabs

Prerequisites

[X] I have searched for duplicate or closed feature requests
[X] I have read the contributing guidelines

Proposal
Thanks again for making Bootstrap!
I am using Bootstrap 5.2 in a web-app with large input-forms, some of which have more than 200 input-fields and about 40 plots. These are organized in nested tabs. Because the backend plotting is a bit slow, and it is unlikely the user is going to look at all 40 plots, I want to lazy-load the plots. But as they need to use data from the input-fields, this is apparently not supported by typical lazy-load features in HTML and Bootstrap.
Solution 1
My first solution was to catch the Javascript event onFocus in the tab-button, but this does not work for nested tabs, because the event only fires in the outer tab and does not propagate into the inner nested tabs that become visible. Similarly the Bootstrap event shown.bs.tab also does not propagate into the nested tabs that become visible.
So I had to render the plots in each of the first nested tabs, but the other plots could be lazy-loaded using the onFocus event, as the user would have to click those nested tab-buttons so the event would fire.
Solution 2
My second solution was to catch the shown.bs.tab event in the tab-button, and recursively follow the active tab-buttons into the nested tabs, until we get to the inner-most tab-pane where there are no more nested tabs, at which point we find a div element with a certain class such as lazy, and then call the lazy-load function with that element's ID.
Load-Time
The load-time was around 30 seconds without any lazy-loading. With the 1st solution above the load-time was around 3 seconds, and with the 2nd solution it was only around 0.1 second! So this makes a huge difference in user-experience!
Of course, the plots still have to be rendered when the user clicks a tab-button, but it is fast enough when it is just one plot at a time.
Bootstrap Solution?
My solution is probably too specific for inclusion into Bootstrap, but perhaps you could make a more elegant and general solution, e.g. by having a class propagate-shown which would propagate shown.bs.tab events into the active nested tabs?
Code
Even if you don't want to make support for this in Bootstrap, I thought I would share my solution, because I have spent a long time trying to figure out how to do this best. So this may save someone else a lot of time, especially people like myself who are not really web-developers.
The following script should go in your Javascript-file or at the bottom of your HTML-file.
<script>
/** Setup event-handler to lazy-load HTML elements, also inside nested tabs.
  * This is necessary because the `onFocus` and `shown.bs.tab` events that fire
  * when the user switches tabs, do not propagate into the nested tabs. So this
  * catches the Bootstrap event 'shown.bs.tab' in 'nav-link' tab-buttons, and
  * then recursively follows the *active* nested tab-buttons to the bottom,
  * where it then finds the element <div class='lazy' id='XYZ'> and
  * then calls `ajaxLazy(id='XYZ')`
  */
function setupHandlerLazy() {
  // Catch the Bootstrap event 'shown.bs.tab' on all tab-buttons.
  // We could make a specific class to only catch the event for nested tabs,
  // but that would make the HTML templates more complicated, and this is so
  // fast to execute even for tab-buttons that don't have nested tabs.
  $('button.nav-link').on('shown.bs.tab', function (event) {
    // Get the tab-button that was activated.
    var button = $(event.target);

    // Tab-pane that the tab-button targets. This will be found below.
    var tab_pane = null;

    // Find the inner-most nested and *active* tab-pane.
    while (button) {
      // Get the HTML ID for the button's target tab-pane.
      var tab_id = button.attr("data-bs-target");

      // Terminate the iteration unless we find a nested active button below.
      button = null;

      // Does the tab-ID exist?
      if (tab_id) {
        // Get the tab-pane.
        tab_pane = $(tab_id);

        // Does the tab-pane exist?
        if (tab_pane) {
          // Find the first nested and *active* tab-button.
          // This will continue the while-loop into the nested tab.
          button = tab_pane.find('button.nav-link.active:first');
        }
      }
    }

    // If we found a tab-pane, it must be the inner-most / bottom nested tab.
    if (tab_pane) {
      // Find the "lazy" <div> element inside this tab-pane.
      var lazy = tab_pane.find('div.lazy:first');

      // Does the lazy element exist?
      if (lazy) {
        // Get the HTML ID for the lazy element.
        var lazy_id = lazy.attr('id');

        // Does the HTML ID exist?
        if (lazy_id) {
          // AJAX lazy-loading of the element. (Function not shown here.)
          ajaxLazy(id=lazy_id);
        }
      }
    }
  })
}
</script>

You should then call the function setupHandlerLazy() in a script at the bottom of your HTML-file to enable it.
Motivation and context

@Hvass-Labs don't bother too much, it's just much easier to use intersection observer. it will trigger as soon as the tab is active and you can setup relevant init code there
you can find an example here https://bs-companion.vercel.app/bs-tabs.html (where i have a custom lazy-loader custom element that does exactly just that)

@lekoala Thanks very much! I came across the IntersectionObserver API when trying to find a solution for lazy-loading, but it looked very complicated as I am not a web-developer. But you're right that it was fairly easy to implement and it works great!
Here's my solution that may perhaps help others in the future:
<script>
/** Setup event-handler to lazy-load HTML elements, also inside nested tabs.
  * This registers all the HTML elements with an IntersectionObserver, which
  * triggers an event whenever the element becomes visible to the user,
  * so the element's contents can be lazy-loaded.
  */
function setupHandlerLazy() {
  // Create a new observer object that triggers when elements become visible.
  const observer = new IntersectionObserver((entries) => {
    entries.forEach((entry) => {
      if (entry.intersectionRatio > 0) {
        // Element became visible to the user.

        // Get the HTML ID for the lazy element.
        var lazy_id = entry.target.id;

        // Does the HTML ID exist?
        if (lazy_id) {
          // AJAX lazy-loading of the element. (Function not shown here.)
          ajaxLazy(id=lazy_id);
        }
      }
    });
  });

  // Register the HTML elements that need lazy-loading.
  document.querySelectorAll("div.lazy").forEach((element) => {
    observer.observe(element);
  });
}
</script>

As this solves my problem, I currently don't have any need for propagating shown.bs.tab events anymore, so I have closed this issue.


Some package, class name, and autowire improvements

Moved enricher instances under enricher package
Renamed some services for consistency
Improved @Autowired fields: Field injection is not recommended, using constructor based injecting instead: https://stackoverflow.com/questions/39890849/what-exactly-is-field-injection-and-how-to-avoid-it

Codecov Report

Merging #99 into rc will decrease coverage by 0.06%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##                rc     #99      +/-   ##
==========================================
- Coverage     6.09%   6.02%   -0.07%
  Complexity      10      10
==========================================
  Files           44      44
  Lines          607     614       +7
  Branches        71      71
==========================================
  Hits            37      37
- Misses         562     569       +7
  Partials         8       8

Impacted Files
Coverage Δ
Complexity Δ

...us/service/enricher/HotspotAnnotationEnricher.java
0% <ø> (ø)
0 <0> (?)

...us/service/enricher/IsoformAnnotationEnricher.java
0% <ø> (ø)
0 <0> (?)

...e/enricher/MutationAssessorAnnotationEnricher.java
0% <ø> (ø)
0 <0> (?)

...xus/service/internal/CancerHotspotServiceImpl.java
0% <ø> (ø)
0 <0> (?)

...s/service/internal/IsoformOverrideServiceImpl.java
0% <ø> (ø)
0 <0> (?)

...service/internal/VariantAnnotationServiceImpl.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...ome_nexus/service/internal/PdbDataServiceImpl.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

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 dd973fd...dc84472. Read the comment docs.


tsc: Unable to calibrate against PIT

I can't see any good logging in any of the campaigns that include VIRTIO:
$ pwd
/home/bill/data/test1/BPH_VIRTIO_PCI_PROBE
(.venv) $ fuzz.sh run build -p1 --debug

When I run fuzz.sh, the output to the console is:
Worker-00 RedQ-Dict: Have performed 0 itersvs pending, findings: <0, 0, 0>
Worker-00 Input validation failed! Target funky?..

See the full logs:
kafl.log
(.venv) $ pwd
/var/run/shm/kafl_bill
(.venv) $ tail -f hprintf_00.log

tail: hprintf_00.log: file truncated
tsc: Unable to calibrate against PIT
tail: hprintf_00.log: file truncated
tsc: Unable to calibrate against PIT
tail: hprintf_00.log: file truncated
tsc: Unable to calibrate against PIT
tail: hprintf_00.log: file truncated
tsc: Unable to calibrate against PIT
tail: hprintf_00.log: file truncated
tsc: Unable to calibrate against PIT
tail: hprintf_00.log: file truncated
tsc: Unable to calibrate against PIT
tail: hprintf_00.log: file truncated

I have some local changes with a bunch of printk's to see what's going on, and I don't even see my printk from the kernel's
entry point at the KAFL ifdef.
diff --git a/init/main.c b/init/main.c
index c652266dc548..4c2c86e9d623 100644
--- a/init/main.c
+++ b/init/main.c
@@ -1677,7 +1677,7 @@ static int __ref kernel_init(void *unused)
        rcu_end_inkernel_boot();

        do_sysctl_args();
-
+       printk("BILL KERNEL INIT\n");
 #if defined CONFIG_TDX_FUZZ_HARNESS_FULL_BOOT || defined CONFIG_TDX_FUZZ_HARNESS_REST_INIT
        // End fuzzing before dropping to userspace
        kafl_fuzz_event(KAFL_DONE);

But their in the vmlinux is both build and shm location:
(.venv) bill@fang:/var/run/shm/kafl_bill$ strings target/vmlinux | grep BILL
BILL KERNEL INIT
BILL getting cached u64.
BILL updating cache.
BILL is NOT VIRTIO DEVICE REFRESH SKIPPING...
BILL is VIRTIO DEVICE, REFRESHING!
BILL __virtio16_to_cpu
BILL __virtio32_to_cpu
BILL __virtio64_to_cpu
BILL __virtio16_to_cpu
BILL __virtio32_to_cpu
BILL __virtio64_to_cpu
BILL __virtio16_to_cpu
BILL __virtio32_to_cpu
BILL __virtio32_to_cpu
BILL __virtio16_to_cpu
BILL __virtio16_to_cpu
BILL __virtio16_to_cpu
BILL __virtio16_to_cpu
BILL __virtio16_to_cpu

In order to see detailed logs from the guest you need the ensure following (will file an issue to update the docs, it is not mentioned there):

change qemu_append line to select the one with more debug (it is commented out by default) in bkc/kafl/kafl_config.yaml

modify kafl.yaml in your local "data/test1/harness_name" to comment out "#log_crashes: True"  and add
"log_hprintf: True" .

run with "fuzz.sh run build -p 2 --log-hprintf"

The you will better boot log from the guest.

Filed issue to update the docs on verbose input: https://github.com/intel/ccc-linux-guest-hardening/issues/105

Yep, that got me better logs, why wouldn't we just make that the default?
I tried applying the patch below, but still getting tsc: Unable to calibrate against PIT
diff --git a/arch/x86/kernel/kafl-agent.c b/arch/x86/kernel/kafl-agent.c
index 79a97655a2e1..0639f1acf1ac 100644
--- a/arch/x86/kernel/kafl-agent.c
+++ b/arch/x86/kernel/kafl-agent.c
@@ -403,6 +403,8 @@ static bool kafl_fuzz_filter(uintptr_t addr, enum tdx_fuzz_loc type)
                                case 0xc000 ... 0xcfff:
                                        return 0;
 #endif
+                               case 0x70 ... 0x71:
+                                       return 0;
                                default:
                                        return 1;
                        }

"tsc: Unable to calibrate against PIT", yes, this message seems to be ok actually (I forgot that our emulation VM is not a real TD and in such TD this can happen) actually I saw that output in a good campaign also, so smth else is wrong. How do I reproduce your setup?

why wouldn't we just make that the default?
I guess because it is not good default if you actually want to fuzz (which ideally what people would like to do), not to debug why it is not fuzzing...

"tsc: Unable to calibrate against PIT", yes, this message seems to be ok actually (I forgot that our emulation VM is not a real TD and in such TD this can happen) actually I saw that output in a good campaign also, so smth else is wrong. How do I reproduce your setup?

why wouldn't we just make that the default?
I guess because it is not good default if you actually want to fuzz (which ideally what people would like to do), not to debug why it is not fuzzing...

All I am doing is following the setup:

Make changes to linux-guest under the ccc-linux-guest-hardening
make env from cc-linux-guest-hardening repo
iniit_harness.py ~/data/test1 BPH_P9_VIRTIO_PROBE
cd ~/data/test1/BPH_P9_VIRTIO_PROBE
fuzz.sh build ./build
cd build
cp the KConfig from my last known good one over (https://github.com/intel/ccc-linux-guest-hardening/files/10946069/config.bak.txt): cp ~/config.bak .config
make -j4 to rebuild the kernel
cd .. back to parent directory BPH_P9_VIRTIO_PROBE.
run the campaign fuzz.sh run build -p 2 --debug --log-hprintf

@williamcroberts when you overwrite the config in the above step 7, you are enabling only CONFIG_TDX_FUZZ_HARNESS_POST_TRAP harness from the guest point of view, so virtio inputs are not being injected.
Could you please try the following default sequence instead:

Make changes to linux-guest under the ccc-linux-guest-hardening
make env from cc-linux-guest-hardening repo
iniit_harness.py ~/data/test1 BPH_P9_VIRTIO_PROBE
cd ~/data/test1/BPH_P9_VIRTIO_PROBE
fuzz.sh build ./build
run the campaign fuzz.sh run build -p 2 --debug --log-hprintf

@williamcroberts when you overwrite the config in the above step 7, you are enabling only CONFIG_TDX_FUZZ_HARNESS_POST_TRAP harness from the guest point of view, so virtio inputs are not being injected.

Oh duh :-p

Could you please try the following default sequence instead:

Make changes to linux-guest under the ccc-linux-guest-hardening
make env from cc-linux-guest-hardening repo
iniit_harness.py ~/data/test1 BPH_P9_VIRTIO_PROBE
cd ~/data/test1/BPH_P9_VIRTIO_PROBE
fuzz.sh build ./build
run the campaign fuzz.sh run build -p 2 --debug --log-hprintf

@williamcroberts  Great! Thank you! Is it ok to close this issue?


GPU error on x86_64 with Tesla V100

I am running a docker container with the following details:
OS:     Ubuntu 16.04.5 LTS
GPU:    Tesla V100-SXM2
CUDA:   10.0.130
PYTHON: 3.5.2

The GPU works fine when I use it with Keras, Numba, etc.  I downloaded LightGBM and compiled (with GPU flags).  There are no errors that I see at any step.  I can run from python the CPU version with num_thread = 28 and that works perfectly.  However, when I add  device='gpu' and gpu_device_id=0, I get the following error:   LightGBMError: No OpenCL device found.  Details of the output from the compilation steps, and the stack trace for the error are given below.  I would appreciate any suggestions for how I could get this to work.  Thx.
Also note that the container did not originally have lightgbm.  So, it is not that there are two versions and I am seeing the wrong one.  When I run import lightgbm as lgb and then lgb.__file__ I do get the correct location.
$ cmake -DUSE_GPU=1 -DOpenCL_LIBRARY=/usr/local/cuda/lib64/libOpenCL.so -DOpenCL_INCLUDE_DIR=/usr/local/cuda/include ..
-- The C compiler identification is GNU 5.4.0
-- The CXX compiler identification is GNU 5.4.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Try OpenMP C flag = [-fopenmp]
-- Performing Test OpenMP_FLAG_DETECTED
-- Performing Test OpenMP_FLAG_DETECTED - Success
-- Try OpenMP CXX flag = [-fopenmp]
-- Performing Test OpenMP_FLAG_DETECTED
-- Performing Test OpenMP_FLAG_DETECTED - Success
-- Found OpenMP: -fopenmp
-- Looking for CL_VERSION_2_0
-- Looking for CL_VERSION_2_0 - not found
-- Looking for CL_VERSION_1_2
-- Looking for CL_VERSION_1_2 - found
-- Found OpenCL: /usr/local/cuda/lib64/libOpenCL.so (found version "1.2")
-- OpenCL include directory:/usr/local/cuda/include
-- Boost version: 1.58.0
-- Found the following Boost libraries:
--   filesystem
--   system
-- Configuring done
-- Generating done
-- Build files have been written to: /notebooks/libs/LightGBM/build

$ make -j8
Scanning dependencies of target _lightgbm
Scanning dependencies of target lightgbm
[ 11%] Building CXX object CMakeFiles/lightgbm.dir/src/main.cpp.o
[ 12%] Building CXX object CMakeFiles/_lightgbm.dir/src/boosting/boosting.cpp.o
[ 12%] Building CXX object CMakeFiles/_lightgbm.dir/src/c_api.cpp.o
[ 12%] Building CXX object CMakeFiles/_lightgbm.dir/src/application/application.cpp.o
[ 12%] Building CXX object CMakeFiles/lightgbm.dir/src/application/application.cpp.o
[ 12%] Building CXX object CMakeFiles/_lightgbm.dir/src/lightgbm_R.cpp.o
[ 12%] Building CXX object CMakeFiles/lightgbm.dir/src/boosting/prediction_early_stop.cpp.o
[ 12%] Building CXX object CMakeFiles/lightgbm.dir/src/boosting/boosting.cpp.o
[ 14%] Building CXX object CMakeFiles/lightgbm.dir/src/boosting/gbdt_prediction.cpp.o
[ 15%] Building CXX object CMakeFiles/lightgbm.dir/src/boosting/gbdt_model_text.cpp.o
[ 17%] Building CXX object CMakeFiles/lightgbm.dir/src/boosting/gbdt.cpp.o
[ 19%] Building CXX object CMakeFiles/_lightgbm.dir/src/boosting/prediction_early_stop.cpp.o
[ 20%] Building CXX object CMakeFiles/lightgbm.dir/src/io/json11.cpp.o
[ 23%] Building CXX object CMakeFiles/lightgbm.dir/src/io/metadata.cpp.o
[ 23%] Building CXX object CMakeFiles/_lightgbm.dir/src/boosting/gbdt_prediction.cpp.o
[ 25%] Building CXX object CMakeFiles/_lightgbm.dir/src/boosting/gbdt_model_text.cpp.o
[ 26%] Building CXX object CMakeFiles/_lightgbm.dir/src/boosting/gbdt.cpp.o
[ 28%] Building CXX object CMakeFiles/lightgbm.dir/src/io/file_io.cpp.o
[ 30%] Building CXX object CMakeFiles/_lightgbm.dir/src/io/json11.cpp.o
[ 31%] Building CXX object CMakeFiles/lightgbm.dir/src/io/config.cpp.o
[ 33%] Building CXX object CMakeFiles/lightgbm.dir/src/io/bin.cpp.o
[ 36%] Building CXX object CMakeFiles/lightgbm.dir/src/io/dataset.cpp.o
[ 36%] Building CXX object CMakeFiles/lightgbm.dir/src/io/dataset_loader.cpp.o
[ 38%] Building CXX object CMakeFiles/_lightgbm.dir/src/io/metadata.cpp.o
[ 39%] Building CXX object CMakeFiles/_lightgbm.dir/src/io/file_io.cpp.o
[ 41%] Building CXX object CMakeFiles/lightgbm.dir/src/io/tree.cpp.o
[ 42%] Building CXX object CMakeFiles/lightgbm.dir/src/io/parser.cpp.o
[ 44%] Building CXX object CMakeFiles/lightgbm.dir/src/io/config_auto.cpp.o
[ 46%] Building CXX object CMakeFiles/lightgbm.dir/src/metric/metric.cpp.o
[ 47%] Building CXX object CMakeFiles/_lightgbm.dir/src/io/config.cpp.o
[ 49%] Building CXX object CMakeFiles/lightgbm.dir/src/metric/dcg_calculator.cpp.o
[ 50%] Building CXX object CMakeFiles/lightgbm.dir/src/objective/objective_function.cpp.o
[ 52%] Building CXX object CMakeFiles/lightgbm.dir/src/network/linker_topo.cpp.o
[ 53%] Building CXX object CMakeFiles/lightgbm.dir/src/network/linkers_mpi.cpp.o
[ 55%] Building CXX object CMakeFiles/lightgbm.dir/src/network/network.cpp.o
[ 57%] Building CXX object CMakeFiles/_lightgbm.dir/src/io/bin.cpp.o
[ 58%] Building CXX object CMakeFiles/lightgbm.dir/src/network/linkers_socket.cpp.o
[ 60%] Building CXX object CMakeFiles/_lightgbm.dir/src/io/dataset.cpp.o
[ 61%] Building CXX object CMakeFiles/_lightgbm.dir/src/io/dataset_loader.cpp.o
[ 63%] Building CXX object CMakeFiles/_lightgbm.dir/src/io/tree.cpp.o
[ 65%] Building CXX object CMakeFiles/lightgbm.dir/src/treelearner/serial_tree_learner.cpp.o
[ 66%] Building CXX object CMakeFiles/lightgbm.dir/src/treelearner/tree_learner.cpp.o
[ 68%] Building CXX object CMakeFiles/lightgbm.dir/src/treelearner/data_parallel_tree_learner.cpp.o
[ 69%] Building CXX object CMakeFiles/lightgbm.dir/src/treelearner/voting_parallel_tree_learner.cpp.o
[ 71%] Building CXX object CMakeFiles/lightgbm.dir/src/treelearner/gpu_tree_learner.cpp.o
[ 73%] Building CXX object CMakeFiles/_lightgbm.dir/src/io/parser.cpp.o
[ 74%] Building CXX object CMakeFiles/lightgbm.dir/src/treelearner/feature_parallel_tree_learner.cpp.o
[ 76%] Building CXX object CMakeFiles/_lightgbm.dir/src/io/config_auto.cpp.o
[ 77%] Building CXX object CMakeFiles/_lightgbm.dir/src/metric/metric.cpp.o
[ 79%] Building CXX object CMakeFiles/_lightgbm.dir/src/metric/dcg_calculator.cpp.o
[ 80%] Building CXX object CMakeFiles/_lightgbm.dir/src/objective/objective_function.cpp.o
[ 82%] Building CXX object CMakeFiles/_lightgbm.dir/src/network/linker_topo.cpp.o
[ 84%] Building CXX object CMakeFiles/_lightgbm.dir/src/network/linkers_mpi.cpp.o
[ 85%] Building CXX object CMakeFiles/_lightgbm.dir/src/network/network.cpp.o
[ 87%] Building CXX object CMakeFiles/_lightgbm.dir/src/network/linkers_socket.cpp.o
[ 88%] Building CXX object CMakeFiles/_lightgbm.dir/src/treelearner/serial_tree_learner.cpp.o
[ 90%] Building CXX object CMakeFiles/_lightgbm.dir/src/treelearner/tree_learner.cpp.o
[ 92%] Building CXX object CMakeFiles/_lightgbm.dir/src/treelearner/data_parallel_tree_learner.cpp.o
[ 93%] Building CXX object CMakeFiles/_lightgbm.dir/src/treelearner/voting_parallel_tree_learner.cpp.o
[ 95%] Building CXX object CMakeFiles/_lightgbm.dir/src/treelearner/gpu_tree_learner.cpp.o
[ 96%] Building CXX object CMakeFiles/_lightgbm.dir/src/treelearner/feature_parallel_tree_learner.cpp.o
[ 98%] Linking CXX executable ../lightgbm
[ 98%] Built target lightgbm
[100%] Linking CXX shared library ../lib_lightgbm.so
[100%] Built target _lightgbm

$ ldd lib_lightgbm.so
linux-vdso.so.1 =>  (0x00007ffff7ffa000)
libOpenCL.so.1 => /usr/local/cuda/lib64/libOpenCL.so.1 (0x00007ffff76ba000)
libboost_filesystem.so.1.58.0 => /usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.58.0 (0x00007ffff74a2000)
libboost_system.so.1.58.0 => /usr/lib/x86_64-linux-gnu/libboost_system.so.1.58.0 (0x00007ffff729e000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007ffff6f1c000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007ffff6c13000)
libgomp.so.1 => /usr/lib/x86_64-linux-gnu/libgomp.so.1 (0x00007ffff69f1000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007ffff67db000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007ffff65be000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007ffff61f4000)
/lib64/ld-linux-x86-64.so.2 (0x00007ffff7dd7000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007ffff5ff0000)

$ python setup.py install --user --precompile
running install
running build
running build_py
INFO:root:Generating grammar tables from /usr/lib/python3.5/lib2to3/Grammar.txt
INFO:root:Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
creating build
creating build/lib
creating build/lib/lightgbm
copying lightgbm/plotting.py -> build/lib/lightgbm
copying lightgbm/basic.py -> build/lib/lightgbm
copying lightgbm/libpath.py -> build/lib/lightgbm
copying lightgbm/callback.py -> build/lib/lightgbm
copying lightgbm/compat.py -> build/lib/lightgbm
copying lightgbm/__init__.py -> build/lib/lightgbm
copying lightgbm/sklearn.py -> build/lib/lightgbm
copying lightgbm/engine.py -> build/lib/lightgbm
running egg_info
creating lightgbm.egg-info
writing lightgbm.egg-info/PKG-INFO
writing requirements to lightgbm.egg-info/requires.txt
writing dependency_links to lightgbm.egg-info/dependency_links.txt
writing top-level names to lightgbm.egg-info/top_level.txt
writing manifest file 'lightgbm.egg-info/SOURCES.txt'
reading manifest file 'lightgbm.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
no previously-included directories found matching 'build'
warning: no files found matching 'LICENSE'
warning: no files found matching '*.txt'
warning: no files found matching '*.so' under directory 'lightgbm'
warning: no files found matching '*.txt' under directory 'compile'
warning: no files found matching '*.so' under directory 'compile'
warning: no files found matching '*.dll' under directory 'compile/Release'
warning: no files found matching '*' under directory 'compile/compute'
warning: no files found matching '*' under directory 'compile/include'
warning: no files found matching '*' under directory 'compile/src'
warning: no files found matching 'LightGBM.sln' under directory 'compile/windows'
warning: no files found matching 'LightGBM.vcxproj' under directory 'compile/windows'
warning: no files found matching '*.dll' under directory 'compile/windows/x64/DLL'
warning: no previously-included files matching '*.py[co]' found anywhere in distribution
writing manifest file 'lightgbm.egg-info/SOURCES.txt'
copying lightgbm/VERSION.txt -> build/lib/lightgbm
running install_lib
creating /jupyter/.local/lib/python3.5/site-packages/lightgbm
copying build/lib/lightgbm/VERSION.txt -> /jupyter/.local/lib/python3.5/site-packages/lightgbm
copying build/lib/lightgbm/plotting.py -> /jupyter/.local/lib/python3.5/site-packages/lightgbm
copying build/lib/lightgbm/basic.py -> /jupyter/.local/lib/python3.5/site-packages/lightgbm
copying build/lib/lightgbm/libpath.py -> /jupyter/.local/lib/python3.5/site-packages/lightgbm
copying build/lib/lightgbm/callback.py -> /jupyter/.local/lib/python3.5/site-packages/lightgbm
copying build/lib/lightgbm/compat.py -> /jupyter/.local/lib/python3.5/site-packages/lightgbm
copying build/lib/lightgbm/__init__.py -> /jupyter/.local/lib/python3.5/site-packages/lightgbm
copying build/lib/lightgbm/sklearn.py -> /jupyter/.local/lib/python3.5/site-packages/lightgbm
copying build/lib/lightgbm/engine.py -> /jupyter/.local/lib/python3.5/site-packages/lightgbm
INFO:LightGBM:Installing lib_lightgbm from: ['../lib_lightgbm.so']
copying ../lib_lightgbm.so -> /jupyter/.local/lib/python3.5/site-packages/lightgbm
byte-compiling /jupyter/.local/lib/python3.5/site-packages/lightgbm/plotting.py to plotting.cpython-35.pyc
byte-compiling /jupyter/.local/lib/python3.5/site-packages/lightgbm/basic.py to basic.cpython-35.pyc
byte-compiling /jupyter/.local/lib/python3.5/site-packages/lightgbm/libpath.py to libpath.cpython-35.pyc
byte-compiling /jupyter/.local/lib/python3.5/site-packages/lightgbm/callback.py to callback.cpython-35.pyc
byte-compiling /jupyter/.local/lib/python3.5/site-packages/lightgbm/compat.py to compat.cpython-35.pyc
byte-compiling /jupyter/.local/lib/python3.5/site-packages/lightgbm/__init__.py to __init__.cpython-35.pyc
byte-compiling /jupyter/.local/lib/python3.5/site-packages/lightgbm/sklearn.py to sklearn.cpython-35.pyc
byte-compiling /jupyter/.local/lib/python3.5/site-packages/lightgbm/engine.py to engine.cpython-35.pyc
running install_egg_info
Copying lightgbm.egg-info to /jupyter/.local/lib/python3.5/site-packages/lightgbm-2.2.4-py3.5.egg-info
running install_scripts

Stack trace
---------------------------------------------------------------------------
LightGBMError                             Traceback (most recent call last)
<ipython-input-6-0721398586f8> in <module>
     22 for n,x in enumerate(param_cart,1):
     23     print(n, end=' '); sys.stdout.flush()
---> 24     result.append(lgb_cv(x))
     25     if n%10==0 or n==len(param_cart):
     26         print(' ({0:.1f}min)'.format((time()-st)/60.)); st = time()

<ipython-input-6-0721398586f8> in lgb_cv(vals)
     15 def lgb_cv(vals):
     16     prm = {**param_fixed, **dict(zip(param_grid.keys(),vals))}
---> 17     out = lgb.cv(prm, train_lgb, nfold=4, verbose_eval=0, show_stdv=False)
     18     return(list(vals)+[out[metric+'-mean'][-1],len(out[metric+'-mean'])])
     19

~/.local/lib/python3.5/site-packages/lightgbm/engine.py in cv(params, train_set, num_boost_round, folds, nfold, stratified, shuffle, metrics, fobj, feval, init_model, feature_name, categorical_feature, early_stopping_rounds, fpreproc, verbose_eval, show_stdv, seed, callbacks)
    456     cvfolds = _make_n_folds(train_set, folds=folds, nfold=nfold,
    457                             params=params, seed=seed, fpreproc=fpreproc,
--> 458                             stratified=stratified, shuffle=shuffle)
    459
    460     # setup callbacks

~/.local/lib/python3.5/site-packages/lightgbm/engine.py in _make_n_folds(full_data, folds, nfold, params, seed, fpreproc, stratified, shuffle)
    315         else:
    316             tparam = params
--> 317         cvbooster = Booster(tparam, train_set)
    318         cvbooster.add_valid(valid_set, 'valid')
    319         ret.append(cvbooster)

~/.local/lib/python3.5/site-packages/lightgbm/basic.py in __init__(self, params, train_set, model_file, silent)
   1552                 train_set.construct().handle,
   1553                 c_str(params_str),
-> 1554                 ctypes.byref(self.handle)))
   1555             # save reference to data
   1556             self.train_set = train_set

~/.local/lib/python3.5/site-packages/lightgbm/basic.py in _safe_call(ret)
     44     """
     45     if ret != 0:
---> 46         raise LightGBMError(decode_string(_LIB.LGBM_GetLastError()))
     47
     48

LightGBMError: No OpenCL device found

Looking at an older post, it appears that running the following helped  mkdir -p /etc/OpenCL/vendors && \ echo "libnvidia-opencl.so.1" > /etc/OpenCL/vendors/nvidia.icd.  Is this required even if OpenCL_LIBRARY and OpenCL_INCLUDE_DIR are mentioned in the cmake step above? Thx.

@ironv: did you run a clean session after changing max_bin?

@mayer79 I have been running clean sessions every time.  So, in my Jupyter notebook I always run with "Restart and Run All".
I went back to the examples provided here to see if that would work.  My code is shown below and I am happy to report that example is working and the GPU is giving me a 3x speedup.
Unfortunately, my instance is still not working and I get the error reported above.  Working perfectly with CPU but still giving the error above with GPU.  I thought a difference was lgb.cv versus lgb.train but higgs works perfectly with lgb.cv using GPU.  One key difference is that my input matrix is a lot wider (9000+ columns).  Could that be an issue?  And because of that would I need to set some other param?
import lightgbm as lgb
import numpy as np
from sklearn.metrics import roc_auc_score

with open('higgs.train') as f:
    y_train = np.array([x[0] for x in f])
with open('higgs.test') as f:
    y_test = np.array([x[0] for x in f])

train_lgb = lgb.Dataset('higgs.train').construct()
print('#row in train_lgb: {:,}'.format(train_lgb.num_data()))

##########GPU

param_final = dict(max_bin=63, num_leaves=255, num_iterations=500, learning_rate=.1, tree_learner='serial',
                  min_data_in_leaf=100, num_threads=16, device='gpu')

model_gbm = lgb.train(param_final, train_lgb, verbose_eval=False)

    #CPU times: user 17min 33s, sys: 28.8 s, total: 18min 2s
    #Wall time: 1min 12s

print('train: {}'.format(roc_auc_score(y_train, model_gbm.predict('higgs.train', SVMLight=True))))
print('test: {}'.format(roc_auc_score(y_test, model_gbm.predict('higgs.test', SVMLight=True))))

    #AUC train: 0.8498480556891181
    #AUC test: 0.8421583671697879

##########CPU (run as a clean session after commenting out GPU part)

param_final = dict(num_leaves=255, num_iterations=500, learning_rate=.1, tree_learner='serial',
                  min_data_in_leaf=100, num_threads=16)

model_gbm = lgb.train(param_final, train_lgb, verbose_eval=False)

    #CPU times: user 54min 8s, sys: 19.4 s, total: 54min 28s
    #Wall time: 3min 27s

print('train: {}'.format(roc_auc_score(y_train, model_gbm.predict('higgs.train', SVMLight=True))))
print('test: {}'.format(roc_auc_score(y_test, model_gbm.predict('higgs.test', SVMLight=True))))

    #AUC train: 0.8498480563639954
    #AUC test: 0.8421585516951305

I can confirm that the issue is the number of features in the input matrix.  I tried the following train_lgb = lgb.Dataset(train_csc[:,:5800], train_pd['is_case'].values).construct(), and that works fine.  When that number is changed to 5900  I get and exception LightGBMError: bin size 272 cannot run on GPU

Closing issue since the originally reported issue has been addressed.  Moving the wide matrix problem to another issue.

Closing issue since the originally reported issue has been addressed. Moving the wide matrix problem to another issue.

How do you fix this? I have exactly same issue error LightGBMError: No OpenCL device found although I have successfully compile LightGBM with --gpu param

Looking at an older post, it appears that running the following helped mkdir -p /etc/OpenCL/vendors && \ echo "libnvidia-opencl.so.1" > /etc/OpenCL/vendors/nvidia.icd. Is this required even if OpenCL_LIBRARY and OpenCL_INCLUDE_DIR are mentioned in the cmake step above? Thx.

And this one does not fix my issue.


Spring Bank Holiday 2022 (UK)

UK Spring Bank Holiday is moved to 2nd June in 2022 for the Platinum Jubilee. An additional bank holiday is added the day after. #270

@dch-dev Thank you very much for the PR! It has a few errors, so would be great if you could have a look at them.
I am planning to make a new release the coming week and can include this PR if you have fixed the issues.
Cheers!

Sorry about that! Added the correct return types and should be good to go!


[lighthouse] add reference for "title" audit

What's changed, or what was fixed?

updated the reference template
created reference for "doesn't have title element" audit

Fixes: N/A
Target Live Date: 2018-03-09

[x] This has been reviewed and approved by @kaycebasques
[x] I have run gulp test locally and all tests pass.
[x] I have added the appropriate type-something label.
[x] I've staged the site and manually verified that my content displays correctly.

CC: @petele

:+1:

:+1:

:tada: This has been pushed live to https://developers.google.com/web/


logging: https://github.com/metanorma/metanorma-plugin-glossarist/iss…

…ues/27
Metanorma PR checklist

[ ] Breaking changes (list related PRs)
[ ] Documentation update required (create task for this)
[ ] External dependency introduced (documentation update need)
[ ] Gem with native library introduced

@HassanAkbar Reminder to approve this PR.


ISSUE-6  master fails build with tests

There is an extra space trailing in the test with missing headers test line.
I have resolved it by removing the space from the tests.  You may want to think about trim() with fields like this.

@trixpan ping


PLT-7798 Support new mattermost-redux action returns

Summary
Support new mattermost-redux action returns.
@lindalumitchell could I get your help just running a smoke test on this? I did one myself already but another set of eyes would be awesome. It touches a bunch of different parts of the app, anything broken by this should be obvious and have a JS error.
Ticket Link
https://mattermost.atlassian.net/browse/PLT-7798

Setup Test Server label detected. Spinmint test server created if build succeeds (checks pass and no conflicts with base branch).

Spinmint test server created at: http://i-0af5eeb807e6f3adf.spinmint.com:8065/pr147
Test Account 1: Email<EMAIL_ADDRESS>| Password: passwd
Test Account 2: Email<EMAIL_ADDRESS>| Password: passwd
Instance ID: i-0af5eeb807e6f3adf

Spinmint test server destroyed

Setup Test Server label detected. Spinmint test server created if build succeeds (checks pass and no conflicts with base branch).

Spinmint test server created at: http://i-07ea550e6e677ec12.spinmint.com:8065/pr147
Test Account 1: Email<EMAIL_ADDRESS>| Password: passwd
Test Account 2: Email<EMAIL_ADDRESS>| Password: passwd
Instance ID: i-07ea550e6e677ec12

Setup Test Server label detected. Spinmint test server created if build succeeds (checks pass and no conflicts with base branch).

Spinmint test server created at: http://i-0938accd989776b53.spinmint.com:8065/pr147
Test Account 1: Email<EMAIL_ADDRESS>| Password: passwd
Test Account 2: Email<EMAIL_ADDRESS>| Password: passwd
Instance ID: i-0938accd989776b53

Setup Test Server label detected. Spinmint test server created if build succeeds (checks pass and no conflicts with base branch).

Spinmint test server created at: http://i-06e357bb979b460ff.spinmint.com:8065/pr147
Test Account 1: Email<EMAIL_ADDRESS>| Password: passwd
Test Account 2: Email<EMAIL_ADDRESS>| Password: passwd
Instance ID: i-06e357bb979b460ff

@jwilander I'm still working through some more smoke testing, but may have found one issue so far.

In a public channel, click channel name > Leave Channel

Observed: Appears to leave channel visually (disappears from LHS and Town Square briefly displays), but then the page auto-refreshes, and channel is still there in LHS and center. Still part of the channel after refresh and logout/login. Can repeat selecting Leave Channel with same behavior.
Expected: User leaves channel. Channel name removed from LHS, and center displays Town Square.

Saw slightly different behavior only once (no refresh, but channel still stayed. Channel top nav appeared blank):

I'm pretty sure it's caused by the bug that was fixed in the RC but I'll take a look to confirm that's it not anything in this PR

Right here https://github.com/mattermost/mattermost-webapp/blob/master/actions/websocket_actions.jsx#L382, you need to add:
dispatch({
    type: ChannelTypes.RECEIVED_PROFILE_NOT_IN_CHANNEL,
    data: {user_id: msg.broadcast.user_id},
    id: channelId
});

Essentially the redux store was not getting the information that user was removed from the channel. Dispatching this event should cover that

@lindalumitchell I just rebased onto latest and did another little smoke test myself. The leaving channel issue seems to be fixed now that 4.3 was merged into master.
If you can take another look that would be much appreciated

Spinmint test server destroyed

Setup Test Server label detected. Spinmint test server created if build succeeds (checks pass and no conflicts with base branch).

Spinmint test server created at: http://i-0d627a59eb72f9dd3.spinmint.com:8065/pr147
Test Account 1: Email<EMAIL_ADDRESS>| Password: passwd
Test Account 2: Email<EMAIL_ADDRESS>| Password: passwd
Instance ID: i-0d627a59eb72f9dd3

First one is definitely this PR, I'll fix it. Nice catch!
For the second one yeah, that's likely just a result of the PDF dependency we're using but I'll take a look at it just to be sure

Pushed a fix for adding commands and looked into the second one which is indeed a non-issue

Spinmint test server destroyed

Setup Test Server label detected. Spinmint test server created if build succeeds (checks pass and no conflicts with base branch).

Spinmint test server created at: http://i-09da0eb9c91070ba6.spinmint.com:8065/pr147
Test Account 1: Email<EMAIL_ADDRESS>| Password: passwd
Test Account 2: Email<EMAIL_ADDRESS>| Password: passwd
Instance ID: i-09da0eb9c91070ba6

@jwilander I verified that the slash command issue is fixed on the new spinmint, and did some more smoke testing, and it all looks great! No new issues found. 👍

Awesome, thanks @lindalumitchell really appreciate your help on this


git tags is not updated

The v2.0.0 refers to the old commit, which's not merged with #35 .
This causes package on https://pkg.go.dev/ didn't synchronized

This issue has been fixed in PR #35.


basis function details from the prediction ?

Hello,
Since MARs build a model which is weighted sum of basis functions..of the form
f(x) = c1B1 + c2B2 + c3B3 + ...+ ciBi
where Bi is a Basis function and ci is a constant coefficient.
is it possible to get the individual value of ciBi for each prediction from the PyEarth implementation ?

Hello,
yes it is possible through  the transform method. You can look here : http://contrib.scikit-learn.org/py-earth/content.html#pyearth.Earth.transform

@adumudaliar Yes.  Adding to what @mehdidc wrote, the transform method gives your Bi's and your ci's are in the  coef_ attribute.  Closing, but please post if you find this doesn't work for you.


iPhone 12 playing back on earpiece speaker and therefore is very quiet.

When running on the iPhone 12 the playback volume is very low.
        _audioPlayer = AudioManager.Current.CreatePlayer(filePath);
        _audioPlayer.Play();

Even if I try manually setting the volume to 1 it is still the same low volume.
        _audioPlayer = AudioManager.Current.CreatePlayer(filePath);
        _audioPlayer.Volume = 1;
        _audioPlayer.Play();

If I save the wav file and then play it it is loud.
On further investigation it appears that this is due to the fact that it is using the earpiece speaker at the top of the iPhone rather than the loudspeakers.  Is there any way I can configure the audio player to use the loudspeakers?

Didn't hear this before (no pun intended), I think the iPhone automatically switches between those devices depending on how you hold the device? Or some other configuration maybe?
Just tried the sample app here and that plays very loud from the regular speakers. Could you maybe try the sample app and see how that behaves?

Yes this is really frustrating and by default the plugin does NOT stream to AirPods, bluetooth devices ect, they also cant be used to record.
There is a simple fix, it seems you need to set the audio category on the audio session.  I do this before recording and before playback as I want slightly different settings, but equally it can be done in the iOS AppDelegate once on start-up.
var audioSession = AVAudioSession.SharedInstance(); var err = audioSession.SetCategory(AVAudioSessionCategory.PlayAndRecord, AVAudioSessionCategoryOptions.AllowBluetooth | AVAudioSessionCategoryOptions.AllowBluetooth | AVAudioSessionCategoryOptions.AllowAirPlay | AVAudioSessionCategoryOptions.DefaultToSpeaker); if (err != null)     return false; err = audioSession.SetActive(true); if (err != null)     return false; return false;
Hope this helps others, would be great to see the library updated to provide more functionality.

Perhaps we could include this information into documentation at the bare minimum

@nathanjeynes Is the final return in your code supposed to be false?
Also, I'm having a hard time getting this into the appdelegate for ios.  Do you have anything to show for doing that?


Updates TP-Link dependency

Description:
This should fix the issues with TP-Link HS200 switches not appearing
Internal changes in dependent module should resolve issues with HS100/110/200 switches returning chunked responses.
Related issue (if applicable): fixes #4045  fixes #4601
Checklist:
If the code communicates with devices, web services, or third-party tools:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] New dependencies have been added to the REQUIREMENTS variable ([example][ex-requir]).
[x] New dependencies are only imported inside functions that use them ([example][ex-import]).
[x] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.

https://github.com/kirichkov/home-assistant/blob/a127d52581f7b39928d0ebb846c801b6abdddf8b/homeassistant/components/switch/tplink.py#L67
Use SmartPlug.is_on property here.
https://github.com/kirichkov/home-assistant/blob/a127d52581f7b39928d0ebb846c801b6abdddf8b/homeassistant/components/switch/tplink.py#L69-L75
Use SmartPlug.turn_on(), SmartPlug.turn_off() calls, they hide the 'ON', 'OFF' string encoding.

Also we can now default the plugs name to SmartPlug.alias, or store the name given by HASS into the Plug.

I'll add functionality to import the name from the switch, if name is not present, but I'm a bit reluctant setting the switch's name to match the one in home assistant. This might be confusing to users who use both hass and the TP-Link mobile app.

I'd think the name should be unified in both the Kasa app (if used) and in home-assistant.

I agree that they should be the same, but setting a name in hass in no way implies changing it on the device itself.
I haven't come across a device that gets its settings changed from hass but I haven't looked at many implementations either.

Also update the very top comment to reflect HS200 support.

Comment updated.
Perhaps I can beg @balloob to try and squeeze this in for 0.35 so we can restore functionality for HS200?

Made it 👍

HS200 state does not get updated when switched on or off from the switch itself or from the Kasa app. Had to downgrade to 30.2.

@linodavid: Are you seeing any traceback?

@mweinelt
`16-12-19 00:43:00 netdisco.ssdp: Error fetching description at http://<IP_ADDRESS>:8200/rootDesc.xml
16-12-19 00:43:00 pynetgear: Error talking to API
Traceback (most recent call last):
File "/srv/hass/lib/python3.5/site-packages/requests/models.py", line 358, in prepare_url
scheme, auth, host, port, path, query, fragment = parse_url(url)
File "/srv/hass/lib/python3.5/site-packages/requests/packages/urllib3/util/url.py", line 195, in parse_url
raise LocationParseError(url)
requests.packages.urllib3.exceptions.LocationParseError: Failed to parse: None:None
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/hass/.homeassistant/deps/pynetgear/init.py", line 113, in _make_request
self.soap_url, headers=headers, data=message, timeout=10)
File "/srv/hass/lib/python3.5/site-packages/requests/api.py", line 110, in post
return request('post', url, data=data, json=json, **kwargs)
File "/srv/hass/lib/python3.5/site-packages/requests/api.py", line 56, in request
return session.request(method=method, url=url, **kwargs)
File "/srv/hass/lib/python3.5/site-packages/requests/sessions.py", line 474, in request
prep = self.prepare_request(req)
File "/srv/hass/lib/python3.5/site-packages/requests/sessions.py", line 407, in prepare_request
hooks=merge_hooks(request.hooks, self.hooks),
File "/srv/hass/lib/python3.5/site-packages/requests/models.py", line 302, in prepare
self.prepare_url(url, params)
File "/srv/hass/lib/python3.5/site-packages/requests/models.py", line 360, in prepare_url
raise InvalidURL(*e.args)
requests.exceptions.InvalidURL: Failed to parse: None:None
16-12-19 00:43:00 homeassistant.components.device_tracker.netgear: Failed to Login
16-12-19 00:43:00 homeassistant.components.device_tracker: Error setting up platform netgear`

This is not related to the tp-link switch. It's an issue with the Netgear device tracker. Perhaps you have another traceback in the logs, or for some reason the failed initialization is breaking your switch, which is highly unlikely in my experience.

Unfortunately, I don't have anything else in the log. The proper current state of the switches are reflected only after restarting HA 0.35.2. Any state change after that does not reflect until the next restart. Please note that the state gets updated in the Kasa app immediately and in HA 0.30.2 after 15-10 seconds.

One thing you could check is to enable debug logging for this component, maybe the logs will have some clue why it isn't working.

@rytilahti, thanks for your suggestion. Below is the log output.
At the very end of the logs at 19:27:46, I turned on the Front Door Lights from HA. A minute after, I turned it off from the Kasa app.  I manually typed the backticks and use the insert code button. Both gave me the same format as above.

Hi again,
I should've said that you'll need to enable the logger for the pyHS100 instead of homeassistant, then you'll see the raw communication between the device and hass. I thought adding homeassistant.components.switch.tplink: debug to logs in logger would help, but doesn't seem to do it. In worst case you have to go to the pyHS100 sources and set the logger to have level logging.DEBUG manually.

  So there is some propagation issue between pyHS100.state and home-assistant.

The last message visible is about it being turned, calls for state will just use the value the device has at that point, but as component makes no queries on the device it stays stale. I'm not sure, but maybe the component should refetch system_info if specific amount of time (like a second or few) has elapsed since the last update?
@linodavid for temporary fix you can add the following line into tplink.py's update() before self._state = self.smartplug.state:
self.smartplug._fetch_sysinfo()

The switches disappear from the UI and I see the following traceback:
Traceback (most recent call last):
  File "/srv/hass/lib/python3.5/site-packages/homeassistant/helpers/entity_component.py", line 150, in _async_setup_platform
    entity_platform.add_entities, discovery_info
  File "/usr/lib/python3.5/asyncio/futures.py", line 361, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.5/asyncio/tasks.py", line 296, in _wakeup
    future.result()
  File "/usr/lib/python3.5/asyncio/futures.py", line 274, in result
    raise self._exception
  File "/usr/lib/python3.5/concurrent/futures/thread.py", line 55, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/hass/lib/python3.5/site-packages/homeassistant/components/switch/tplink.py", line 41, in setup_platform
    add_devices([SmartPlugSwitch(SmartPlug(host), name)], True)
  File "/srv/hass/lib/python3.5/site-packages/homeassistant/helpers/entity_component.py", line 299, in add_entities
    entity.update()
  File "/srv/hass/lib/python3.5/site-packages/homeassistant/components/switch/tplink.py", line 88, in update
    self.smartplug._fetch_sysinfo()
AttributeError: 'SmartPlug' object has no attribute '_fetch_sysinfo'

@linodavid This looks like you have an old version of the pyHS100 module.

Shouldn't upgrading HA also update all the modules? If not, how do I upgrade pyHS100?

It should update the dependent modules, so I'm wondering why are yours not updated.
You can "update" it by removing the old version from the "deps" directory. This will force hass to install the required version on next start

I've remove the old version from the deps directory as well as created a completely new VM and installed HA from scratch. Have the same error still. In the deps folder, I have both the pyHS100 and pyHS100-0.2.2-py3.5.egg-info folders but still looks like I'm still pulling the old pyHS100.

Have you installed before hass without virtualenv in the past? Perhaps hass is using an existing version that is old? Can you check the lib directory in your virtualenv root whether it has any version of pyHS100?
If you still can't figure it out can you please open a new bug or perhaps a new topic on community.home-assistant.io, to avoid notifying the participants in this pull request.


fix: Allow forcing dark or light mode on all users regardless of system theme

🙋 Feature Request
If Mode on FluentDesignTheme is explicitly set to a value, force that value regardless of user system theme.
🤔 Expected Behavior
When <FluentDesignTheme StorageName="theme" Mode="DesignThemeModes.Dark" /> is added to App.cs the theme selected by FluentUI will always be dark regardless of what the user's system UI theme is.
😯 Current Behavior
Explicit setting of Mode on FluentDesignTheme will be ignored and use the user's system theme.
💁 Possible Solution
Do what is stated in expected behavior assuming this is a bug and not intended.
🔦 Context
I have a website that is stylistically intended to work only in dark mode, when the user uses a light UI theme, it just defaults to the system theme regardless of my explicit set in FluentDesignTheme.
I've tried clearing cache, cookies, and the obj + bin folders in my local environment.
 Set the default theme -->
    <script src="_content/Microsoft.FluentUI.AspNetCore.Components/js/loading-theme.js" type="text/javascript"></script>
    <loading-theme storage-name="theme"></loading-theme>
</body>
</html>

Mode="DesignThemeModes.Dark" gets ignored by FluentUI and just uses the user's system theme.

Sorry it appears I used the wrong issue template, this is a bug report.

Hi,
We will take a look at that. In the meantime, do not put the below line in your index.html the library will automatically load it for you and i have observed some weird things happen when it is loaded twice
<script src="_content/Microsoft.FluentUI.AspNetCore.Components/Microsoft.FluentUI.AspNetCore.Components.lib.module.js" type="module" async></script>

in

Hi,
We will take a look at that. In the meantime, do not put the below line in your index.html the library will automatically load it for you and i have observed some weird things happen when it is loaded twice
<script src="_content/Microsoft.FluentUI.AspNetCore.Components/Microsoft.FluentUI.AspNetCore.Components.lib.module.js" type="module" async></script>

in

Thanks for the tip and prompt response, it didn't solve the problem here, but did fix some other quirks I was experiencing. Hopefully the fix will be easy.

Here's a code project to show the issue, changing system theme changes the site theme when it should stay in dark mode due to the explicit setting of Mode on FluentDesignTheme in App.cs
Some info about my environment:
I tested on iOS and MacOS, extensions disabled, and the project uses the WASM stand-alone app variant of the FluentUI-Blazor template.
https://github.com/HunterAhlquist/ForceThemeModeBug

Hi,
I can't reproduce your issue. Using you reproduction code (which does not contain any code wrt FluentDesignTheme) and adding the line
<FluentDesignTheme CustomColor="#ffff00" StorageName="theme" Mode="DesignThemeModes.Dark" />

to App.razor just works. First time I see a script error because the local storage does not exist yet but the site shows with dark theme nevertheless

Hi,
I can't reproduce your issue. Using you reproduction code (which does not contain any code wrt FluentDesignTheme) and adding the line
<FluentDesignTheme CustomColor="#ffff00" StorageName="theme" Mode="DesignThemeModes.Dark" />

to App.razor just works. First time I see a script error because the local storage does not exist yet but the site shows with dark theme nevertheless

Could it be specific to Safari on MacOS, or did you only try on windows/Chrome?

I only have a Windows machine

I only have a Windows machine

I mean can we really call this closed then? Safari is the second most popular browser today. Perhaps someone else can use my test project on their mac.

I'm pretty sure we would have received more reports if this was not working on Safari.
Your test project does not contain any theme specific code. Please make sure it is a an actual reproduction of the issue.


Panel function 74 implementation

The function on execution triggers a timer for a given
duration and sets Dbus property to mark window to upload
ACF certificate as active.
This property should be looked upon by Bmcweb to detect
if the window has been enabled.
Upon timer expiration the window is set as disabled.
Change-Id: I51a890b48c38fc52d94ff336a469f89c95f26160
Signed-off-by: Sunny Srivastava<EMAIL_ADDRESS>

How can I activate this function for testing?   What is the D-bus API to invoke OpPanel function74?  Or can I use a D-Bus API to directly set ACFWindowActive=true or false?

I am not familiar with ibm-panel code, boost::asio timers, or sdbusplus coding, but this seems okay to me. As far as I can tell, when the BMC reboots or the application restarts: ACFWindowActive=false. That behavior seems correct. When function74 is invoked or re-invoked: it sets or resets the 30 minute window with ACFWindowActive=true, and then after the timeout it goers back to ACFWindowActive=false. That behavior seems correct.

Sounds good.

How can I activate this function for testing? What is the D-bus API to invoke OpPanel function74? Or can I use a D-Bus API to directly set ACFWindowActive=true or false?

You need to have panel hardware, using which you need to traverse to function 74 and press an execute on that.

How can I activate this function for testing? What is the D-bus API to invoke OpPanel function74? Or can I use a D-Bus API to directly set ACFWindowActive=true or false?

You need to have panel hardware, using which you need to traverse to function 74 and press an execute on that.

Sorry I phrased my question wrong.  I am familiar with the operation of the physical panel, but that was not my question.
My question is: For unit testing, I will not have access to the OpPanel; I want a software solution to simulate pressing function 74 and I though I heard there was a way to do that (given BMC shell access as root).  How can I simulate pressing function 74?


Assignment 9

Hi Professor,
I would keep this page for all concerns in assignment 9 if you do not mind.
One concern is that there is two declarations of a single variable of loop in mutate() which could result conflict, kindly see the code below:
         for **i,** x in enumerate(self.generation):             new_x = list(x)             for **i** in range(len(x)):
" i " variable was declared two times; please let me know whether or not this would result an issue.

@salmassari Thanks for pointing this out! The two "i" should definitely be different.
I have updated the hint file.
@everyone Please also update it

Thank you Professor @azhe825

Hi Professor and All,
I got two iterated issues over and over. I am still not sure what they are. It seems not from my code, so I want to make sure. The issues are below:
   clf = self.model(*decision) TypeError: type object argument after * must be an iterable, not int
The second one
    predictions = clf.predict(X_test)   File "../assignment2/my_DT_hint.py", line 114, in predict     if type(self.tree[node])==Counter: KeyError: 2
Could anyone confirm whether the assignment is done or not? This helps me to know if the issue is from my code or not.

A useful way for debugging is to add a try and except to catch the error:
try:
  clf = self.model(*decision)
except:
  set_trace()

A useful way for debugging is to add a try and except to catch the error:
try:
  clf = self.model(*decision)
except:
  set_trace()

This is what I get
> /Users/XX/DSCI-633/assignments/assignment9/test.py(73)evaluate()
-> indices = [i for i in range(len(self.data_y))]
(Pdb)

Then you can debug what happened. E.g. check what decision is

@salmassari @azhe825
I get the same issue with my_DT file ( in predict if type(self.tree[node])==Counter).
I have used the TA's assignment 2 code but still the same error .
Is anyone else have the same error please let us know ?

Yes, I'm also having the same problem
On Sun, Oct 25, 2020, 16:24 AbdullahA93<EMAIL_ADDRESS>wrote:

@salmassari https://github.com/salmassari @azhe825
https://github.com/azhe825
I get the same issue with my_DT file ( in predict if
type(self.tree[node])==Counter).
I have used the TA's assignment 2 code but still the same error .
Is anyone else have the same error please let us know ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/hil-se/fds/issues/45#issuecomment-716206436, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AKTRMLA4AZ3DSKL4OKPF53LSMSCQTANCNFSM4SUTGSDA
.

I found that the TA's reference answer to my_DT.py was not updated. It did not convert the node to leaf node when max_depth was reached.
It has been fixed now. Please update.
https://github.com/ketakisbarde/DSCI-633/blob/master/assignments/assignment2/my_DT.py

I found that the TA's reference answer to my_DT.py was not updated. It did not convert the node to leaf node when max_depth was reached.
It has been fixed now. Please update.
https://github.com/ketakisbarde/DSCI-633/blob/master/assignments/assignment2/my_DT.py

@azhe825 Thanks Professor, it works well now.

Hi Professor, @azhe825
I am tending to use TA's solution in assignment 2, so do I need to update my assignment 2 ? and replace my solution with TA's solution?

Yes. You can do that.

Sir, do we need to change it in our repo too?

You can choose whether to use the reference answer to finish A9. If you choose so, you need to overwrite your repo with the reference answer


Cilium 1.11 fails the kubernetes e2e test "[sig-network] Services should create endpoints for unready pods"

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Cilium 1.11 fails the kubernetes e2e test [sig-network] Services should create endpoints for unready pods
https://github.com/kubernetes/kops/pull/12919 is a PR that only changes the default cilium version to 1.11.
The test log can be found at https://storage.googleapis.com/kubernetes-jenkins/pr-logs/pull/kops/12919/pull-kops-e2e-cni-cilium/1469638304646303744/build-log.txt
The pod logs and config maps can be found at https://gcsweb.k8s.io/gcs/kubernetes-jenkins/pr-logs/pull/kops/12919/pull-kops-e2e-cni-cilium/1469638304646303744/artifacts/cluster-info/kube-system/
Cilium Version
1.11.0
Kernel Version
Linux ip-172-20-33-11 5.10.0-9-cloud-amd64 #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64 GNU/Linux
Kubernetes Version
1.23.0
Sysdump
No response
Relevant log output
No response
Anything else?
No response
Code of Conduct

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

Just to let you know that this failure still persists on cilium 1.11

We skip non-ready endpoints in Cilium while parsing endpoint slice resources.  Do you have a use case for considering non-ready pods for load-balancing service traffic? Or is this bug filed to mainly track the k8s sig-network test failure?

Services should create endpoints for unready pods

Do you know how the test validates this behavior? Does it send traffic to the non-ready pods?

I have not looked very closely at exactly how k/k implemented the test. I would assume it only checks that there is a service endpoint. I don't see how it could be a requirement that the non-ready endpoint actually accepts traffic.
That being said, I would also assume that cilium is not responsible for populating these endpoints, but that KCM did this. So it could be the case it actually tries to send traffic.

The test is at https://github.com/kubernetes/kubernetes/blob/9c3a0e63a71c0890a5ab1aa0a267e91a81e5c441/test/e2e/network/service.go#L1648
It creates a Service with the spec.publishNotReadyAddresses field set to true and appears to send traffic to the service cluster ip and verify it is received by the non-ready pod. It then turns off publishNotReadyAddresses and verifies the non-ready pod is no longer reachable.

Another related test failing: Services should be able to connect to terminating and unready endpoints if PublishNotReadyAddresses is true

@aanm what Endpoint/EndpointSlices uses Cilium to map the Service to the Pods? this CRD ?
https://github.com/cilium/cilium/blob/01f7d9a4a51735afdd1d0b8288cd34e539eaa8a2/Documentation/network/kubernetes/ciliumendpointslice.rst#L16
because the EndpointSlices present those pods in the ready addresses when the Service PublishNotReadyAddresses is true

@aojea It uses the one available in the cluster, either k8s endpoints or k8s endpointslices.

I'm trying to figure out why it omits these Pods, if the Service sets PublishNotReadyAddresses the Endpoints and EndpointSlices controller sets their state to read on the corresponding object
https://gist.github.com/aojea/30ee9ff53022d6b3e6156c4d2e570852
is there any other source of readiness for the Pods in cilium?

in this test, the Pod has a graceful timeout of 600 seconds, it gets deleted and after that, the Pod will become unready but will still be able to serve traffic, and since the Service has PublishNotReadyAddresses it will be available on the endpoints

Jan 27 12:58:12.082: INFO: At 2023-01-27 12:52:56 +0000 UTC - event for slow-terminating-unready-pod: {replication-controller } SuccessfulDelete: Deleted pod: slow-terminating-unready-pod-nk64j

It seems that there is a pod controller that
https://github.com/cilium/cilium/blob/e4889d72f9a8f86bee47327dbab7b46773607a7e/pkg/k8s/watchers/pod.go#L61-L126
if this controller sees the Delete and removes the pod from the cilium endpoints, then it may explain why the test fails, since it is not sending traffic to it ... but I'm not familiar with the code, so just throwing ideas
@squeed we went through this together in our previous gig ;) , the edge vs trigger thing, it is better if you reconcile instead of processing the events directly ...

I was wrong, the problem is simpler, it seems that cilium does not implement this kubernetes feature service.Spec. PublishNotReadyAddresses at all, at least I could not find any place that checks for that field in the codebase
grep -r PublishNotReadyAddresses | grep -v vendor
aojea@aojea:~/src/cilium$

/cc @thockin

another false assumption it seems I did, that information is set on the EndpointSlice
ready := service.Spec.PublishNotReadyAddresses || (serving && !terminating)
pkg/controller/endpointslice/utils.go

unless there is a check in cilium on the pod status in addition to the endpointslice status ...

ok, I verified that service.Spec.PublishNotReadyAddresses works correctly in Cilium
apiVersion: apps/v1
kind: Deployment
metadata:
  name: server-deployment
  labels:
    app: MyApp
spec:
  replicas: 2
  selector:
    matchLabels:
      app: MyApp
  template:
    metadata:
      labels:
        app: MyApp
    spec:
      containers:
      - name: agnhost
        image: k8s.gcr.io/e2e-test-images/agnhost:2.39
        args:
          - netexec
          - --http-port=80
        ports:
        - containerPort: 80
        readinessProbe:
          exec:
            command:
            - cat
            - /tmp/healthy
---
apiVersion: v1
kind: Service
metadata:
  name: notready-service
spec:
  type: ClusterIP
  selector:
    app: MyApp
  publishNotReadyAddresses: true
  ports:
    - protocol: TCP
      port: 80
      targetPort: 80

pods are not ready
kubectl get pods
NAME                                 READY   STATUS    RESTARTS   AGE
server-deployment-58bc78d657-kz6vv   0/1     Running   0          11s
server-deployment-58bc78d657-q7mlz   0/1     Running   0          11s

Service is created
kubectl get service
NAME               TYPE        CLUSTER-IP    EXTERNAL-IP   PORT(S)   AGE
kubernetes         ClusterIP   <IP_ADDRESS>     <none>        443/TCP   20m
notready-service   ClusterIP   <IP_ADDRESS>   <none>        80/TCP    11m

curl to the service works, ciliums forwards traffic correctly
curl <IP_ADDRESS>/hostname
server-deployment-58bc78d657-kz6vvroot@kind-worker:/# curl <IP_ADDRESS>/hostname
server-deployment-58bc78d657-q7mlzroot@kind-worker:/# curl <IP_ADDRESS>/hostname
server-deployment-58bc78d657-q7mlzroot@kind-worker:/# curl <IP_ADDRESS>/hostname

it has to be here then
		ginkgo.By("Check if terminating pod is available through service")

the handling of terminating 👀

ok, confirmed , the bugs is on how the terminating is being handled
apiVersion: v1
kind: Pod
metadata:
  name: terminating
  labels:
    app: MyApp
spec:
  terminationGracePeriodSeconds: 300
  containers:
  - name: agnhost
    image: k8s.gcr.io/e2e-test-images/agnhost:2.39
    args:
      - netexec
      - --http-port=80
      - --delay-shutdown=300
    ports:
    - containerPort: 80
---
apiVersion: v1
kind: Service
metadata:
  name: terminating-service
spec:
  type: ClusterIP
  selector:
    app: MyApp
  ports:
    - protocol: TCP
      port: 80
      targetPort: 80

 kubectl get service
NAME                  TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)   AGE
kubernetes            ClusterIP   <IP_ADDRESS>       <none>        443/TCP   33m
terminating-service   ClusterIP   <IP_ADDRESS>   <none>        80/TCP    2m57s

once you delete the pod, the traffic to the service stops
kubectl delete pod terminating
pod "terminating" deleted

but the connectivity to the pod works
 curl  <IP_ADDRESS>/hostname
curl: (7) Couldn't connect to server
root@kind-worker:/# curl <IP_ADDRESS>/hostname
terminatingroot@kind-worker:/#

however, I still see the service in cilium
6    <IP_ADDRESS>:80   ClusterIP      1 => <IP_ADDRESS>:80 (terminating)

/assign
I've found the issue and have it working locally, will send a PR to fix this once I polish it and test it better


Error. unfortunately the demo colab does not work

You should go to the lag-llama folder before you call LagLlamaEstimator. For instance,
cd /content/lag-llama.

You should go to the lag-llama folder before you call LagLlamaEstimator. For instance, cd /content/lag-llama.

Thank you for your response. However, changing the directory to the lag-llama folder before calling LagLlamaEstimator does not seem to resolve the issue. The problem might be related to recent changes in the repository (around March 2nd or 3rd, or even earlier).
Regardless, the demo Colab notebook should work without any issues. The error "No module named 'lightning'" appears on any machine, not just in Colab.
I would greatly appreciate if you could provide further guidance on how to properly set up the environment and resolve this error. Please let me know if there are any additional steps I should take or if you have any other suggestions.
Thank you for your time and assistance in this matter.

Sorry, this is related to recent changes in the repository and we are fixing it right now.

Hi @m6129 we have fixed the issue and the colab should work fine now.
Please check it and let us know.

Hi @m6129 we have fixed the issue and the colab should work fine now.
Please check it and let us know.
Thank You. Now Colab works correctly.


onMouseUp issue when clicked on draggable

The following line prevents handling onMouseUp when draggable element is clicked: https://github.com/jasonslyvia/react-anything-sortable/blob/master/Sortable.jsx#L143
For example we have a button on a draggable element. When button is pressed, pop-up appears. With that line, handleMouseUp returns on click (because mouse is not moving). So dragging is never cancelled.
I am not sure whether it's a bug or a feature. But if you consider this a feature, maybe you could make it a preference?

I believe that is a design on purpose to prevent some browser fire redundant mouse events, but I will inversigate it with next release.

Since I've refactored the code the aforementioned line should be https://github.com/jasonslyvia/react-anything-sortable/blob/master/src/index.js#L152.
Back to your scenario, if there's a button on a draggable element, how can you click it during dragging the element?
So I believe this is the correct behaviour to make handleMouseUp respond only if handleMouseDown and handleMouseMove  have been called.
Please notice this return would cancel the event bubbling because 1) It ain't jQuery and 2) I didn't return false.
Let me know if there is anything I'm missing.

Back to your scenario, if there's a button on a draggable element, how can you click it during dragging the element?

My draggable elements are looking as follows:
[ Sortable A | x ]  [ Sortable B | x ]  [ Sortable C | x ]  [ Sortable D | x ]

User can push the x button (it's an actual x) when item is not dragging. This will trigger a bootstrap modal where user can set the reason why this item is being deleted.
Problem is: when I push the x button, it triggers onMouseDown / handleMouseDown(), which binds the drag event.
When I release the mouse button onMouseUp / handleMouseUp() is called which is correct.
But because the mouse did not move between onMouseDown and onMouseUp, handleMouseUp() returns immediately and thus never releases the drag event. So when I click x and move the mouse to a button on the modal, draggable element will move along with the mouse cursor.
The same behaviour still exists when I click the draggable element outside the x button. Latest Safari, Chrome, Firefox and IE8 on WinXP show the same behaviour.

I get your point, it turns out I add this return to prevent unnecessary setState. I'll fix in next release.

Thanks!

Fixed in 529ee0d0af3b6d1ad139777db7a3a29482dc8a82

Since I've refactored the code the aforementioned line should be https://github.com/jasonslyvia/react-anything-sortable/blob/master/src/index.js#L152.

btw, canonical url you can get by pressing y


[!-VIRAL~4k!*] Filipina Teen xxx video Original Xvideo Link On Social Media X Trending Now

37 seconds ago.....
[🌐 𝖢𝖫𝖨𝖢𝖪 𝖧𝖤𝖱𝖤 🟢==►► 𝖶𝖠𝖳𝖢𝖧 𝖭𝖮𝖶]
[🔴 𝖢𝖫𝖨𝖢𝖪 𝖧𝖤𝖱𝖤 🌐==►► 𝖣𝗈𝗐𝗇𝗅𝗈𝖺𝖽 𝖭𝗈𝗐]
L𝚎aked Video pinay teen video Original Video Viral Video L𝚎aked on X Twitter Telegram
[-wATCH-]—pinay teenvideo Video Original Video Linkpinay teenvideo Video Viral On Social Media X Trending Now
[-wATCH-]—pinay teenvideo ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]—pinay teenvideo ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]—pinay teenvideo Video Original Video Linkpinay teenvideo Video Viral On Social Media X Trending Now
pinay teenvideo Original Video video took the internet by storm and amazed viewers on various social media platforms.pinay teenvideo, a young and talented digital creator, recently became famous thanks to this interesting video.
L𝚎aked Videopinay teenvideo Original Video Viral Video L𝚎aked on X Twitter
pinay teenvideo Original Video video oficial twitter
L𝚎aked Videopinay teenvideo Original Video Viral Video L𝚎aked on X Twitter..
.
.
.
.
.
.
.
.
.
.
.
.
37 seconds ago.....
[🌐 𝖢𝖫𝖨𝖢𝖪 𝖧𝖤𝖱𝖤 🟢==►► 𝖶𝖠𝖳𝖢𝖧 𝖭𝖮𝖶]
[🔴 𝖢𝖫𝖨𝖢𝖪 𝖧𝖤𝖱𝖤 🌐==►► 𝖣𝗈𝗐𝗇𝗅𝗈𝖺𝖽 𝖭𝗈𝗐]
L𝚎aked Video pinay teenvideo Original Video Viral Video L𝚎aked on X Twitter Telegram
[-wATCH-]—pinay teenvideo Video Original Video Linkpinay teenvideo Video Viral On Social Media X Trending Now
[-wATCH-]—pinay teenvideo ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]—pinay teenvideo ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]—pinay teenvideo Video Original Video Linkpinay teenvideo Video Viral On Social Media X Trending Now
pinay teenvideo Original Video video took the internet by storm and amazed viewers on various social media platforms.pinay teenvideo, a young and talented digital creator, recently became famous thanks to this interesting video.
L𝚎aked Videopinay teenvideo Original Video Viral Video L𝚎aked on X Twitter
pinay teenvideo Original Video video oficial twitter
L𝚎aked Videopinay teenvideo Original Video Viral Video L𝚎aked on X Twitter..
.
.
.
.
.
.
.
.37 seconds ago.....
[🌐 𝖢𝖫𝖨𝖢𝖪 𝖧𝖤𝖱𝖤 🟢==►► 𝖶𝖠𝖳𝖢𝖧 𝖭𝖮𝖶]
[🔴 𝖢𝖫𝖨𝖢𝖪 𝖧𝖤𝖱𝖤 🌐==►► 𝖣𝗈𝗐𝗇𝗅𝗈𝖺𝖽 𝖭𝗈𝗐]
L𝚎aked Video pinay teenvideo Original Video Viral Video L𝚎aked on X Twitter Telegram
[-wATCH-]—pinay teenvideo Video Original Video Linkpinay teenvideo Video Viral On Social Media X Trending Now
[-wATCH-]—pinay teenvideo ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]—pinay teenvideo ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]—pinay teenvideo Video Original Video Linkpinay teenvideo Video Viral On Social Media X Trending Now
pinay teenvideo Original Video video took the internet by storm and amazed viewers on various social media platforms.pinay teenvideo, a young and talented digital creator, recently became famous thanks to this interesting video.
L𝚎aked Videopinay teenvideo Original Video Viral Video L𝚎aked on X Twitter
pinay teenvideo Original Video video oficial twitter
L𝚎aked Videopinay teenvideo Original Video Viral Video L𝚎aked on X Twitter..
.
.

37 seconds ago.....
[🌐 𝖢𝖫𝖨𝖢𝖪 𝖧𝖤𝖱𝖤 🟢==►► 𝖶𝖠𝖳𝖢𝖧 𝖭𝖮𝖶]
[🔴 𝖢𝖫𝖨𝖢𝖪 𝖧𝖤𝖱𝖤 🌐==►► 𝖣𝗈𝗐𝗇𝗅𝗈𝖺𝖽 𝖭𝗈𝗐]
L𝚎aked Video pinay teen video Original Video Viral Video L𝚎aked on X Twitter Telegram
[-wATCH-]—pinay teenvideo Video Original Video Linkpinay teenvideo Video Viral On Social Media X Trending Now
[-wATCH-]—pinay teenvideo ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]—pinay teenvideo ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]—pinay teenvideo Video Original Video Linkpinay teenvideo Video Viral On Social Media X Trending Now
pinay teenvideo Original Video video took the internet by storm and amazed viewers on various social media platforms.pinay teenvideo, a young and talented digital creator, recently became famous thanks to this interesting video.
L𝚎aked Videopinay teenvideo Original Video Viral Video L𝚎aked on X Twitter
pinay teenvideo Original Video video oficial twitter
L𝚎aked Videopinay teenvideo Original Video Viral Video L𝚎aked on X Twitter..
.
.
.
.
.
.
.
.
.
.
.
.
37 seconds ago.....
[🌐 𝖢𝖫𝖨𝖢𝖪 𝖧𝖤𝖱𝖤 🟢==►► 𝖶𝖠𝖳𝖢𝖧 𝖭𝖮𝖶]
[🔴 𝖢𝖫𝖨𝖢𝖪 𝖧𝖤𝖱𝖤 🌐==►► 𝖣𝗈𝗐𝗇𝗅𝗈𝖺𝖽 𝖭𝗈𝗐]
L𝚎aked Video pinay teenvideo Original Video Viral Video L𝚎aked on X Twitter Telegram
[-wATCH-]—pinay teenvideo Video Original Video Linkpinay teenvideo Video Viral On Social Media X Trending Now
[-wATCH-]—pinay teenvideo ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]—pinay teenvideo ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]—pinay teenvideo Video Original Video Linkpinay teenvideo Video Viral On Social Media X Trending Now
pinay teenvideo Original Video video took the internet by storm and amazed viewers on various social media platforms.pinay teenvideo, a young and talented digital creator, recently became famous thanks to this interesting video.
L𝚎aked Videopinay teenvideo Original Video Viral Video L𝚎aked on X Twitter
pinay teenvideo Original Video video oficial twitter
L𝚎aked Videopinay teenvideo Original Video Viral Video L𝚎aked on X Twitter..
.
.
.
.
.
.
.
.37 seconds ago.....
[🌐 𝖢𝖫𝖨𝖢𝖪 𝖧𝖤𝖱𝖤 🟢==►► 𝖶𝖠𝖳𝖢𝖧 𝖭𝖮𝖶]
[🔴 𝖢𝖫𝖨𝖢𝖪 𝖧𝖤𝖱𝖤 🌐==►► 𝖣𝗈𝗐𝗇𝗅𝗈𝖺𝖽 𝖭𝗈𝗐]
L𝚎aked Video pinay teenvideo Original Video Viral Video L𝚎aked on X Twitter Telegram
[-wATCH-]—pinay teenvideo Video Original Video Linkpinay teenvideo Video Viral On Social Media X Trending Now
[-wATCH-]—pinay teenvideo ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]—pinay teenvideo ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]—pinay teenvideo Video Original Video Linkpinay teenvideo Video Viral On Social Media X Trending Now
pinay teenvideo Original Video video took the internet by storm and amazed viewers on various social media platforms.pinay teenvideo, a young and talented digital creator, recently became famous thanks to this interesting video.
L𝚎aked Videopinay teenvideo Original Video Viral Video L𝚎aked on X Twitter
pinay teenvideo Original Video video oficial twitter
L𝚎aked Videopinay teenvideo Original Video Viral Video L𝚎aked on X Twitter..
.
.


Double jsonencoded

https://github.com/humanitec-architecture/example-library/blob/2da269e0f98dd44f361294b1dfa7e5f27df11858/resource-definitions/ingress/ingress/ingress-alb.tf#L15
This should not have the 2nd Jsonencode

That's right, well spotted! Working on a fix,

@bobbydeveaux  Please see this PR: https://github.com/humanitec-architecture/example-library/pull/65

Closing with https://github.com/humanitec-architecture/example-library/pull/65 merged.


Vmchatserver

Thanks for your PR, but what's the point of this?

Closied due to inactivity. Feel free to reopen.


Answer to a comment question in apca.js

In apca.js:

	// why is this a delta, when Y is not perceptually uniform?
	if (Math.abs(Ybg - Ytxt) < deltaYmin) {
		C = 0;
	}

Answer: This is just a noise gate, and it is not strictly necessary for the W3 version, which has an output clamp of 0.1.
In some "full range" versions it's needed to clean up very small Y differences that are essentially "noise" (such as 8bit noise), that can cause issues with some of the full range extensions.
But as color.js is using loClip = 0.1; this if statement can be safely discarded.

Thanks for the clarification!
I prefer to stick to the published algorithm, so if you remove this from apca-w3 I will too; but if you don't, I won't. As you say the computed result is the same either way.

I prefer to stick to the published algorithm, so if you remove this from apca-w3 I will too; but if you don't, I won't. As you say the computed result is the same either way.

Hi Chris @svgeesus
I should probably remove it fromt eh W3 version in the interest of simplicity... on my todo list...


httpRetryEnabled feature (2409) is inaccessible as it has not been exposed as a valid key in the configure function

I am trying to use this recent feature: https://github.com/karatelabs/karate/pull/2409
However "httpRetryEnabled" has not been exposed as a valid key in the configure function.
So when I add karate.configure('httpRetryEnabled', true) to my karate-config.js I get the following error...
org.graalvm.polyglot.PolyglotException: unexpected 'configure' key: 'httpRetryEnabled'

com.intuit.karate.core.Config.configure(Config.java:334)
com.intuit.karate.core.ScenarioEngine.configure(ScenarioEngine.java:348)
com.intuit.karate.core.ScenarioBridge.configure(ScenarioBridge.java:300)
.fn(Unnamed:18)

Minimal project attached.
Thanks.
karate-template-main.zip

tagging @ksola since it may take me some time to get to this.

can i send you a PR to fix it @ptrthomas? should just be a few lines

@neeeeeel sure please use develop: https://github.com/karatelabs/karate/blob/master/.github/CONTRIBUTING.md

Hi @ptrthomas @neeeeeel I found out that indeed I made this bug because I wrongly tested the app. Didn't noticed that the config have to be adjusted also in the Config class. I am sorry for inconvenience.

Hi @ptrthomas @neeeeeel I fix that and this time tested it correctly: https://github.com/karatelabs/karate/pull/2433

great ! merged with thanks


Nil Pointer Dereference on EVSE Disconnected

Description
When cemd is connected to an EVSE and the EVSE disconnects the following function is called.
https://github.com/enbility/cemd/blob/e18d4265b5ec281a65ed664bec2c67f593cf5a29/ucevsecc/events.go#L57-L59
Here the entity is accessed to get the Device however the enitity is nil causing the exception.

What is the expectation during disconnect? If https://github.com/enbility/cemd/issues/23 gets implemented the disconnecting entity would still be needed at this point.

Yes, that is a bug. The entity is no longer associated to the Device, as it is disconnected. I will fix it.

Would it make sense to change the order? I.e. in case of disconnect invoke the callback first and the disassociate the entity from the device? Disclaimer would be that you can‘t use is for any spine messaging but you‘d still have access to the relevant information for just that callback.

This should now be fixed via https://github.com/enbility/cemd/commit/d46d7436de874166307557b28fa7a8968fb18a74

I tried it out but there seems to still be a bug. At the moment e.g. UCEVSECC uses the payload to get the entity:
https://github.com/enbility/cemd/blob/f4fdd6b27e473863bf498234e93b7c45d125a31f/ucevsecc/events.go#L57-L59
however in an disconnect situation. This is not populated as can be seen below.
https://github.com/enbility/spine-go/blob/7fea429a63c1ac23055637265b4c21ddf9c2ad26/spine/device_local.go#L144-L157
I think there the entity needs to be added.

Right, I forgot to remove this device disconnect check from the EVSE, as device level is handled on the CEM and the use cases only care about entity changes. See https://github.com/enbility/cemd/commit/6ce38e7775b877e2a219b381e839ea59b8cb1f6a

Thanks works like a charm now.


[Vue warn] linkCurrentClasses -> upon Table render

When rendering the table component, I receive a vue warning.
Vue 3.1.0-beta.7 / vite / oruga 4.1
[Vue warn]: Property "linkCurrentClasses" was accessed during render but is not defined on instance.    at <OPaginationButton key=1 class="pagination-previous" linkClass= (2) ["pagination-link", {…}]  ... >    at <OPagination icon-pack=undefined total=204 per-page=25  ... >    at <OTablePagination class="is-fullwidth" per-page=25 paginated=true  ... >    at <OTable class="is-fullwidth" data= (25) [{…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}] loading=false  ... >    at <ProjectsCntrl onVnodeUnmounted=fn<onVnodeUnmounted> ref=Ref< Proxy {_pStores: {…}, …} > >    at <RouterView key=1 name="default" >    at <App>

Already fixed! It's relative to pagination component.
Available in the next release


tempo: expands the module

Description of changes
Expands on the tempo module.
Expanded module options are compatible with and tested against Tempo 1.5.0 in nixpkgs master.
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

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

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

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

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

[X] Fits CONTRIBUTING.md.

cc: @K900

This is a lot of changes that largely go against the RFC 42 style of configuration. What's your intended use case for this?


[DEVOPS-643] Fix nix-shell dependencies

This adds the full list of build dependencies required for building to the nix-shell.
There is also a change to make the buildkite-agent program available when running on nix-darwin.
I'm not sure I like the nix-shell.sh script. Perhaps if all build agents are configured with nix available and the pipelines specify NIX_PATH, then it wouldn't be required?

@rvl I don't like it too much as well :) buildkit starts with fresh env, so we need to come up with a way to setup Nix env in pure way.


connection close event is fired shortly after connection

Hello ,
I tried the same server side code and client side with this package and default event source . i see that server is getting close event as soon as connection is established . Just to make sure that my Server side code is not the issue I changed the client code to native event source and i cam seeing that it works as expected . i am interested to send header and other good things that this Package has . Can any one help me
My client side code (removed all other codes just to keep simple ) wrapped in useEffect reactHook
const fetchData = async () => {
      await fetchEventSource(`${serverBaseURL}`, {
        method: "POST",
        body: JSON.stringify({ userName, uniqueUserIdentifier }),
        headers: {
          Accept: "text/event-stream",
        },

        openWhenHidden: true,
        onclose() {
          console.log("Connection closed by the server");
        },
      });
    };
    fetchData();
  }, []);

any update for this issue? i have the same prob

same prob too


Refactor config.json into sku model and cleanup error messages

Change InternalError errors to BadRequest when the issue arises due to
bad data in the skupack file that is posted.
Move the config.json properties into the model

*** BUILD #1065 ***
Test Name: test_node_workflows_del_active
Error Details: (400)
Reason: Bad Request
HTTP response headers: HTTPHeaderDict({'Content-Length': '78', 'X-Powered-By': 'Express', 'Connection': 'keep-alive', 'ETag': 'W/"4e-tH4CnLwPLeuXLp/LX6OdsQ"', 'Date': 'Wed, 27 Apr 2016 16:27:52 GMT', 'Access-Control-Allow-Origin': '*', 'Content-Type': 'application/json; charset=utf-8'})
HTTP response body: {"message":"TaskCancellationError: Failed to cancel 5720e885e20c9fdd33bdf5d6"}

Stack Trace: Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/on-http/RackHD/test/tests/api/v2_0/nodes_tests.py", line 340, in test_node_workflows_del_active
    raise e
ApiException: (400)
Reason: Bad Request
HTTP response headers: HTTPHeaderDict({'Content-Length': '78', 'X-Powered-By': 'Express', 'Connection': 'keep-alive', 'ETag': 'W/"4e-tH4CnLwPLeuXLp/LX6OdsQ"', 'Date': 'Wed, 27 Apr 2016 16:27:52 GMT', 'Access-Control-Allow-Origin': '*', 'Content-Type': 'application/json; charset=utf-8'})
HTTP response body: {"message":"TaskCancellationError: Failed to cancel 5720e885e20c9fdd33bdf5d6"}

test this please

*** BUILD #1083 ***

test this please


Entering the meeting notes and making the actual changes about yesterday's meeting

Irem if you don't have the time I can do it, just let me know :)

Actually I think Narin was going to do the changes, can you just write the meeting notes on the wiki page? Thanks

I will write the meeting notes, no problem.

Changes from yesterday's meeting have been made to the requirements page as well.


Move "SignalR connection lifetime handling" section to the SignalR docs

The section about Improved SignalR connection lifetime handling doesn't belong in this doc (my bad!) and should move to the SignalR docs.

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

ID: 542f38c4-1502-f739-372a-80c86c377491
Version Independent ID: 72c2a844-ffb2-4799-2c7a-a7a73d3b6833
Content: Blazor hosting models
Content Source: aspnetcore/blazor/hosting-models.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

oops ... https://github.com/aspnet/AspNetCore.Docs/issues/12715
Beat you by 10 seconds. 🏃
I'll close that.

Looks like we only need to delete it in Blazor ...
https://docs.microsoft.com/aspnet/core/signalr/javascript-client?view=aspnetcore-3.0#automatically-reconnect