dustjs custom helpers

Hi
first of all, thanks for the webpack loader
it's possibile to insert into the flow a custom dustjs helpers before the loader compile the template?
My configuration is:
webpack config
{ test: /\.dust$/, loader: 'dust-loader-complete', exclude: /node_modules/, query: { verbose: true } },

in my module file i have
const tmpl = require('template.dust');

but in my template i have a custom dustjs helper formatDate that is defined in a separate file
dustjs-custom-helpers.js
const dust = require('dustjs-linkedin');
dust.helpers.formatDate = function formatDate(chunk, context, bodies, params) {
....
}

Hi Killanaca,
Thanks for checking out the loader!
We don't currently have a mechanism for automatically inserting a helpers file into the bundle. What you can do is simply require('dustjs-custom-helpers') from your main entry point. Webpack is smart enough to only include one dustjs-linkedin module, and because DustJS is global in the browser, your helpers will work in your templates. Give it a shot and let me know if it works out for you.
I think it would be cleaner to have a way of specifying helper modules, so I think we will consider that for a future enhancement.

Hi
i tried to add the require('dustjs-helpers'); to my main entry point, but webpack tells me
ERROR in ./~/dustjs-helpers/lib/dust-helpers.js Module not found: Error: Cannot resolve module 'dust.core' in E:\P\14\DW\...  @ ./~/dustjs-helpers/lib/dust-helpers.js 3:4-34

I didn't need UMD support so I just removed AMD from the module factory
(function(root, factory) {   if (typeof exports === 'object') {     module.exports = factory(require('dustjs-linkedin'));   } else {     factory(root.dust);   } }(this, function(dust) {
vs.
(function(root, factory) {   if (typeof define === 'function' && define.amd && define.amd.dust === true) {     define(['dust.core'], factory);   } else if (typeof exports === 'object') {     module.exports = factory(require('dustjs-linkedin'));   } else {     factory(root.dust);   } }(this, function(dust) {

@killfish i make the same workaround but the problem is that i must do the same workaround every time someone download our project and make npm install on it

@killanaca & @killfish, I'm fixing that by adding dust.core to the alias section of the webpack.config:
alias: {
  ....
  "dust.core": "dustjs-linkedin"
}

That lets webpack find dustjs-linkedin by aliasing it to dust.core. I'll add a note to the README for any others who might need it.

it's works. thanks a lot

No problem!


Hows show private permission image on blade

Hows show private permission images on view i am getting current url but its not show even public file shows.

This seems to be related to Laravel, not Flysystem.


Handle inline proposal

A fix for https://github.com/paritytech/rfc-action/blob/2bd29c129299537321369cebea403d741d5edddf/src/find-referendum.ts#L27
It's gonna require testing with a local chain with sped-up referendum, because the real ones do not have a proposal like that.

This will probably be a one-line change, but requires a setup to test this.


fix: sidebar file

:tada: This PR is included in version 1.2.8 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Unable to import scipy.ftt

So, I am not sure if I am doing something completely wrong, since this report seems quite basic, and I cannot believe that I am the first reporting this problem.
Anyway, in a quite fresh mac, I try to install scipy to get access to the fourier transform.
Reproducing code example:

import scipy.ftt

Traceback (most recent call last):
  File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'scipy.ftt'

Error message:
➜  $ pip3 install scipy
Requirement already satisfied: scipy in /usr/local/lib/python3.9/site-packages (1.6.3)
Requirement already satisfied: numpy<1.23.0,>=1.16.5 in /usr/local/lib/python3.9/site-packages (from scipy) (1.20.3)
WARNING: You are using pip version 21.1.1; however, version 21.1.2 is available.
You should consider upgrading via the<EMAIL_ADDRESS>-m pip install --upgrade pip' command.
➜  $ python3 -c 'import scipy.ftt'
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'scipy.ftt'

Scipy/Numpy/Python version information:
$ python3 -c 'import sys, scipy, numpy; print(scipy.__version__, numpy.__version__, sys.version_info)'
1.6.3 1.20.3 sys.version_info(major=3, minor=9, micro=5, releaselevel='final', serial=0)

Installation log
➜  $ pip3 install scipy
Collecting scipy
  Downloading scipy-1.6.3-cp39-cp39-macosx_10_9_x86_64.whl (30.9 MB)
     |████████████████████████████████| 30.9 MB 8.5 MB/s
Collecting numpy<1.23.0,>=1.16.5
  Downloading numpy-1.20.3-cp39-cp39-macosx_10_9_x86_64.whl (16.1 MB)
     |████████████████████████████████| 16.1 MB 9.3 MB/s
Installing collected packages: numpy, scipy
Successfully installed numpy-1.20.3 scipy-1.6.3
WARNING: You are using pip version 21.1.1; however, version 21.1.2 is available.
You should consider upgrading via the<EMAIL_ADDRESS>-m pip install --upgrade pip' command.

Mac OS
macOS Big Sur
11.3.1 (20E241)
2 GHz Quad-Core Intel Core i5

I think you meant to import scipy.fft.  Is that correct?

We can close!
Sorry sorry!


More fine-grained file-lines

Currently rustfmt ignores file lines check for items.
Closes #1835.

Rebased with the change to use macro.

I was super-excited to try this with bindgen, but this causes a bunch of undesired effects.
Current STR (will try to find something more reduced later today):

Clone https://github.com/rust-lang-nursery/rust-bindgen.
Apply this diff (for example):

diff --git a/src/lib.rs b/src/lib.rs
index 3a85382..1b68a0a 100644
--- a/src/lib.rs
+++ b/src/lib.rs
@@ -1268,7 +1268,7 @@ fn filter_builtins(ctx: &BindgenContext, cursor: &clang::Cursor) -> bool {

 /// Parse one `Item` from the Clang cursor.
 pub fn parse_one(ctx: &mut BindgenContext,
-                 cursor: clang::Cursor,
+             cursor: clang::Cursor,
                  parent: Option<ItemId>)
                  -> clang_sys::CXChildVisitResult {
     if !filter_builtins(ctx, &cursor) {

Run rustfmt-format-diff.py, which as of right now it does:

rustfmt --file-lines '[{"range": [1268, 1274], "file": "src/lib.rs"}]' src/lib.rs

Expected: Only the parse_one signature is modified.
Actual: A lot of use statements and whitespace is missing, and also lines with comments misindented.

This helps not to get them skipped, but the use statements still get reformatted / reordered:
diff --git a/src/utils.rs b/src/utils.rs
index 9c1717e..47ce5e7 100644
--- a/src/utils.rs
+++ b/src/utils.rs
@@ -343,6 +343,7 @@ macro_rules! skip_out_of_file_lines_range {
 macro_rules! skip_out_of_file_lines_range_visitor {
     ($self:ident, $span:expr) => {
         if out_of_file_lines_range!($self, $span) {
+            $self.push_rewrite($span, None);
             return;
         }
     }

Disclaimer, no clue about whether it's the right fix :-)

Ok, I also got a patch for the other issue, I'll try to add some tests :-)

I opened #1841 with my fixes on top of this.
Also, thanks @topecongiro! I was about to report too much stuff being formated with file-lines, and you already had a fix up for review, that's awesome! :)

Thanks for the changes!


test out cap'n proto vs grpc support

Initial grpc support is in https://github.com/pkgcraft/pkgcraft/commit/3a4a2bbed8161b9ac6c8de8c18af5df5a4c0a8e9. We should check out how well cap'n proto works with rust these days since it looks like it can support a number of features beyond grpc that could be helpful down the road, but those might not all be implemented yet for the rust version.

I had a look at https://github.com/capnproto/capnproto-rust it seems usable, what features are you considering?

I'm not sure without playing around with it like I said. :smile:
My current feeling is that gRPC is the better choice at this point since it has a bigger community behind it leading to better docs/examples and easier integration via tonic.


Upload latest binary to cdr.sh

Makes for easy grabbing within dockerfiles.

This might seem stupid, but what exactly is cdr.sh? Google can't seem to find it.

it's just a domain that we use to host files

Ah ok - thanks for the info


GPS Track Logs jump around in Foreflight

Stratux version:1.4r4-872839fccc

Stratux config:
SDR

[ ] single
[x ] dual

GPS

[ x] yes
[ ] no
type:

AHRS

[x ] yes
[ ] no

power source: Portable battery
usb cable: Micro USB

EFB app and version: ForeFlight 9.6 (21535)
EFB platform: iOS 11.2.6 (15D100)
EFB hardware: iPad

Description of your issue:

I've gone on a few flights recently where I open the track log and it shows my location randomly going back to my home airports FBO. I've tried opening the KML in Google Earth and in the ForeFlight browser, and both show these random jumps. In the screenshot I am attaching I was just flying the pattern, but you can see my flight path would stop going in the direction I was going, then back to the FBO. Almost as if my tablet was switching to the wifi at the FBO and getting the location based on google's wifi location database, but I know it's not connecting to the wifi, as I went on some cross country flights and it jumped back to the same FBO.
Any idea of what's going on or how I can help troubleshoot? I'm a Java developer myself.

Does the KML reflect the exact same coordinates for the FBO? Also, are you using automatic start/stop with the track logs?

So, this is strange,

I opened the KML first in the Google Earth app straight from my iPad and saw all the extra lines as shown above.
Uploaded to ForeFlight.com and saw all the same lines.
Downloaded the KML to my desktop and opened it in the Google Earth desktop app...No Lines!

I'm not a KML expert and I'm not sure how to convert the decimals for the Long and Lat, but it all looks pretty close for a 10-15 second period I narrowed down to a problem area. The only thing I did notice, is that the pulling time seems to be about every 1 second on the dot, however during the time period where we are having problems, there's missing data points. There's a 2-3 second gap in location data points.
This makes me think that ForeFlight and the Google Earth app are filling in with their own data points that go back to the start location.
To answer your question, yes I was using the auto start/stop in ForeFlight. I'm going up for some solo time tomorrow, so I'll try turning off the auto start and manually start the track logs.
Here is a snippet of the KML. Right after 13:49:44 is where I noticed a jump back to start.
<when>2018-03-19T13:49:36.929Z</when>         <gx:coord>-85.8916711807251 39.2665958404541<PHONE_NUMBER>907653</gx:coord>         <when>2018-03-19T13:49:37.928Z</when>         <gx:coord>-85.89173555374146 39.26696062088013<PHONE_NUMBER>8149945</gx:coord>         <when>2018-03-19T13:49:38.920Z</when>         <gx:coord>-85.89186429977417 39.26730394363403<PHONE_NUMBER>7454995</gx:coord>         <when>2018-03-19T13:49:39.924Z</when>         <gx:coord>-85.89203596115112 39.26764726638794<PHONE_NUMBER>652841</gx:coord>         <when>2018-03-19T13:49:40.926Z</when>         <gx:coord>-85.89231491088867 39.268012046813965<PHONE_NUMBER>5601815</gx:coord>         <when>2018-03-19T13:49:42.926Z</when>         <gx:coord>-85.89282989501953 39.26863431930542<PHONE_NUMBER>305368</gx:coord>         <when>2018-03-19T13:49:44.943Z</when>         <gx:coord>-85.89345216751099 39.269256591796875<PHONE_NUMBER>1895443</gx:coord>         <when>2018-03-19T13:49:45.939Z</when>         <gx:coord>-85.89379549026489 39.26955699920654<PHONE_NUMBER>096885</gx:coord>         <when>2018-03-19T13:49:48.939Z</when>         <gx:coord>-85.89491128921509 39.27045822143555<PHONE_NUMBER>957896</gx:coord>         <when>2018-03-19T13:49:49.923Z</when>         <gx:coord>-85.89529752731323 39.270737171173096<PHONE_NUMBER>679918</gx:coord>         <when>2018-03-19T13:49:50.939Z</when>         <gx:coord>-85.89568376541138 39.271037578582764<PHONE_NUMBER>5409294</gx:coord>         <when>2018-03-19T13:49:51.920Z</when>         <gx:coord>-85.89609146118164 39.27131652832031<PHONE_NUMBER>4019404</gx:coord>         <when>2018-03-19T13:49:52.924Z</when>         <gx:coord>-85.8964991569519 39.27159547805786<PHONE_NUMBER>309281</gx:coord>         <when>2018-03-19T13:49:53.921Z</when>         <gx:coord>-85.89692831039429 39.27187442779541<PHONE_NUMBER>170293</gx:coord>         <when>2018-03-19T13:49:54.939Z</when>         <gx:coord>-85.89737892150879 39.27213191986084<PHONE_NUMBER>031304</gx:coord>         <when>2018-03-19T13:49:55.921Z</when>         <gx:coord>-85.89782953262329 39.27236795425415<PHONE_NUMBER>961808</gx:coord>         <when>2018-03-19T13:49:56.924Z</when>

Update: I went flying again and did not use the auto start/stop. I did not have any issues with the track logs when I manually started recording my flight.

Awesome. So my line of thinking is that auto-start works by detecting proximity to an airport and GPS movement. My guess is a default starting airport location is used if GPS connection is lost rather than interpolating your position or omitting that data. I've seen similar results with Foreflight when you run a tracklog on a flight sim and pause the flight.
All this being said, I do not know Foreflight's business logic and I've never had a problem with the internal GPS on my iPad.

Well, based on what we've found, and the conclusion that it's probably ForeFlight. I'm going to close this ticket and try to open one with ForeFlight.


feat: allow full script syntax in event section

This upgrades the current "list of services" restriction to allow the full syntax of HA scripts.
fixes #65
As a side-effect this also requires to generate a context for the script to run.
see #96
This can also be seen as a preparatory step to allow defining HASPObject-wide variables.
see #63
I believe, this should be even backwards-compatible, because a list of services is also a valid script.

This is nice... but it moves from services to scripts
Don't think this is the best path...

Isn't a "list of services" also a valid "script"? If it is, this should not break anything. Instead, it should make possible a whole range of new things, such as requested in the referenced issues.
But I might miss something not so obvious?
(As a side-effect, we would get in line with most of the other integrations. At least I am not aware of a single integration, that allows only a subset of the script syntax as actions. Again, I might miss something.)

This custom integration was based on https://www.home-assistant.io/integrations/universal/ which supports services only.
How to deal with the breaking change ?

This custom integration was based on https://www.home-assistant.io/integrations/universal/ which supports services only.

Ah, I see. It even only admits a single service, which is not supported here, as far as I can see. (A list is required.)

How to deal with the breaking change ?

Not sure, if this question goes to me. If it does: I still don't see anything that could break. But I still might be mistaken. Just in case, a notice could be added in the release page as was done for 0.6.0. (If it does not: Never mind my answer. 😉)

@nagyrobi since you have a big setup, can you test this PR :) ?

Hey, any news on this? I still don't see any breaking change here. Also, I have this running on my instance for half a year now, with no problems so far. The opposite: it allows me to do a whole range of things which wouldn't be possible with services alone. I'll give examples, if you like.
In my opinion: even if this were a breaking change, the opportunities outweigh the risks, by far. But that would be up to you too judge.
For curiosity, I also checked the history, and the actual breaking change was in this commit: https://github.com/HASwitchPlate/openHASP-custom-component/commit/e31fd76e8ab452ff72af89a29975c07267749cad
Bottom line: I really think this is a useful contribution, which I would rather like to see in the upstream codebase than in my personal fork, which noone uses but me. Especially, since 0.7.0 seems to be approaching (the documentation started to prompt my to switch to it's most current version 0.7.0 lately).

Checking back... Any news here?

@nagyrobi since you have a big setup, can you test this PR :) ?

I'm sorry not anymore. I moved to ESPHome with all my displays meanwhile.

@dgomes LVGL is still work in progress but I was able to migrate almost all functionality I previously had.

like the fact that logic can be handled on the device, but coding the everything in through yaml... not the best option IMHO. JSONL approach seams more sensible to me.

I always looked for a way to ditch MQTT from the system, now this is finally possible. Also, for our needs I need zero templates and customizations on HA side, I can do HA service calls directly from the device, no middleware required. HA seems to be faster without the ~200 templates I prevoiusly had to maintain for 6 displays.
I can have any degree of flexibility I want, from C++ lambdas even back to templates.
Conceptually ESPHome is brilliantly thought out. Compilation is very flexible, it generates smaller binaries with only the desired functionality and no Tasmota-ish data losses threatening.

Oh and moodlight color is restored every time regardless of HA or device state as it's being stored on the device itself.

🤔  Makes me wonder if I should abandon this  PR altogether and switch as well. 😉
Jokes aside: Before I find the time for such an adventure, I would still highly appreciate the script feature to become part of this project. And be it only for those who follow...

Oh and moodlight color is restored across reboots every time regardless of HA or device state as it's being stored on the device itself.

This could be easily added to the current firmware...
!Back_to_topic
the breaking change would be changing from single service to list of services... but if we are releasing 0.7 I guess we can accept some breaking changes @fvanroie

Just to remind: the breaking change from single service to list of services has been done way back in the past. From my I understanding, we're discussing a pure extension of functionality here, without breaking changes.

I'm worried with the EVENT_SCHEMA validation change

Ah, ok. I'll check more thoroughly:

The script schema checks for a list of script_actions:
https://github.com/home-assistant/core/blob/3c960b7d4e7a23cedb765226a98e35d1b4ab52e8/homeassistant/helpers/config_validation.py#L1294

Where a script_action is a dictionary of any action_type_schema:
https://github.com/home-assistant/core/blob/3c960b7d4e7a23cedb765226a98e35d1b4ab52e8/homeassistant/helpers/config_validation.py#L1281

And one of these action types is a service schema:
https://github.com/home-assistant/core/blob/3c960b7d4e7a23cedb765226a98e35d1b4ab52e8/homeassistant/helpers/config_validation.py#L1863

So, I'm confident that the current [SERVICE_SCHEMA] check is actually a special case of the SCRIPT_SCHEMA check.
Which makes sense, because a list of service calls is a perfectly valid script.

This could be easily added to the current firmware...

Doesn't seem so, waiting for it for almost 3 years now: https://github.com/HASwitchPlate/openHASP/issues/99#issuecomment-851626353

This could be easily added to the current firmware...

Doesn't seem so, waiting for it for almost 3 years now: HASwitchPlate/openHASP#99 (comment)

That issue is closed now... it doesn't seem anyone missed that feature in the past 3 years.

Is this still active?

Yes. It's running on my system since I started the PR (more or less). Without any problems.

I rebased onto main to test #122. No further changes.

Is this still active?

I was wondering: is there anything else you need from me to proceed on this?

I have no knowledge of the HA inner workings to decide one way or the other. I will let you guys figure it out.
I was just curious since this issue has been open for some time now.

Ok, thanks for clarifying! To my understanding, Diogo had approved the changes on March 3. So, I assumed this had handed it over to you somehow.
@dgomes, anything missing from me? Please let me know!

I think this is good to go


playground extract method to class creates instance side method instead of class side

If you extract a method from a playground snippet to a class, it puts the method on the instance side instead of the class side. For example, if you extract the following code: Object new printString, it will create a method on Object instead of Object class.


Update S3 files collection after image deleted

How is it possible to update the S3 files collection when delete method is called?
Since I tried to delete an image that S3 shown was removed, S3 files collection still has the file exist.
Please help.

Hey! After calling S3.delete(path,cb), you should be able to use the cb function to do something like S3.collection.findOne({relative_url:path}). This should be more intuitive though, I've been wanting to rewrite this package for a while now. I have a project where I know I will use it so an update is on it's way to simplify these things.

yes, this solved. Thanks very much.
I got another problem. I am using Meteor 1.3.1, React 0.15 right now.
Before I was successfully delete the image , but after I installed the webpack:webpack. Then, when I delete the image on the client slide, I got this error:
  S3.delete(selectedImage,function(error, result) {
    console.log("remove result: ", result);
  });

Browser
Uncaught TypeError: Cannot read property 'delete' of undefined
Thanks very much

I just solved the problem. It is because of the s3.config have not setting correctly in the right file.
Thanks.


Expose assumeDotNetFramework in FSharpChecker.GetProjectOptionsFromScript

See https://github.com/fable-compiler/Fable/pull/709#issuecomment-279735384

Will need to change service.fsi as well

Ok, this what happens when you let the CI server to do all the job :) I fixed it, hopefully it'll be fine this time.


Test execution fails even if exception is caught using Protractor helper's grabTextFrom()

I am trying to grab text from a toast, clearly from time to time the test doesn't sync up with the toast and cannot grab the toast's content. I want to be able to catch such situations and to NOT fail test execution.
I am therefore enclosing my call to grabTextFrom() with a try / catch block, but even if the exception is encountered, the test ends.
Here is my code to read the text from the toast:
async getToastMessage() {
try {
const msg = await I.grabTextFrom(this.toastMessage);
return msg;
} catch(err) {
}
return '';
}
I have also tried the following:
async getToastMessage() {
try {
const msg = await I.grabTextFrom(this.toastMessage);
return msg;
} catch(err) {
return '';
}
}
Both examples end my test, I don't want test execution to be terminated. Please advise!

Any news here, it would be useful to be able to catch execptions within codeceptjs, please advise how to do this, particularly in asynchronous calls.

@lepadellec why don't you just do I.grabNumberOfVisibleElements and check if toast is there, do something, this won't cause the test execution to be terminated.

This did the job (code added to a Helper class):
async readToastMessage(){
let ph = this.helpers['Protractor'];
return new Promise(function(resolve, reject) {
// Do async job
ph.grabTextFrom('.toast-message')
.then(function(toastMsg) {
resolve(toastMsg);
}).catch(function(err) {
reject('');
})
});
}
async getToastMessage () {
let results = '';
for (let i = 0; i < 10; i++) {
await new Promise((resolve) => setTimeout(resolve, 1000));
this.readToastMessage()
.then(function(str){
if (!results.includes(str))
results = results.concat(str);
})
.catch((err) => {
});
}
return results;
}


Change node hooks to take in HamiltonNode

Is your feature request related to a problem? Please describe.
StaticValidator does, but the rest don't. We should fix this. We just need to keep it backwards compatible, and we can do this with **future_kwargs. Possibly log a warning as well.
Describe alternatives you've considered
Keeping it the way it is
Additional context
API consistency

I believe this can be closed?


rtorrent disregards port directive and starts on 6980 only

First of all thank you for this AWESOME set of script.
I have rtorrent 0.9.6 on a Raspbian box and just discovered that despite the .rtorrent.rc has the following lines:
network.port_range.set = 51001-51250
network.port_random.set = yes
dht.mode.set = disable
protocol.pex.set = no
trackers.use_udp.set = yes
but when I check on which ports it's listening:
bob@rpi2b:~ $ ss -tulp | grep torrent
tcp LISTEN 0 100 ::ffff:<IP_ADDRESS>:5000 :::* users("rtorrent main",pid=800,fd=13))
tcp LISTEN 0 128 :::6980 :::* users("rtorrent main",pid=800,fd=12))
which I think shows the rtorrent process is opening the standard 6980 and not the 51001-51250 ports, right?
Thank you very much
Additional info:
bob@rpi2b:/usr/local/bin $ lsb_release -sd
Raspbian GNU/Linux 9.1 (stretch)
bob@rpi2b:~ $ uname -a
Linux rpi2b 4.9.41-v7+ #1023 SMP Tue Aug 8 16:00:15 BST 2017 armv7l GNU/Linux
bob@rpi2b:~ $ pwd
/home/bob
bob@rpi2b:~ $ ls -la .rtorrent.rc
-rw-r--r-- 1 bob bob 2706 Oct 27 14:41 .rtorrent.rc

This was an issue with rtorrent, which I thought had been fixed. When did you install rtorrent?
May need to reinstall the latest version.

This should have been fixed. You should be able to install latest version 0.9.7


[opencascade] Fix OpenCASCADE_INSTALL_PREFIX path in config

Describe the pull request

What does your PR fix? Fixes #14636

Currently,  OpenCASCADE_INSTALL_PREFIX path is like this:
OpenCASCADE_INSTALL_PREFIX=D:/vcpkg/installed/x64-windows/share
This causes OpenCASCADE_INCLUDE_DIR and OpenCASCADE_LIBRARY_DIR are wrong.
OpenCASCADE_INCLUDE_DIR =D:/vcpkg/installed/x64-windows/share/include/opencascade

OpenCASCADE_LIBRARY_DIR=D:/vcpkg/installed/x64-windows/share/lib

So need to fix OpenCASCADE_INSTALL_PREFIX path.
Note: All features are not needed to test.

Thank you!

This issue is back again after upgrade to OCC 7.5.0,
https://github.com/microsoft/vcpkg/pull/15997

Thanks for reporting this issue @socuwn.
I found that the patch was removed in PR #15997. I think we can add it back to PR #16513.


Windows 10 Mobile support

I am curious to know why the docs suggest to only check the "Windows 10 Desktop" checkbox. Why is the generated package not supported on Windows 10 mobile, for instance, even though the submission site seems to suggest it is supported. Here is how I left my submission, before I found these helpful docs.

The Chromium-based Edge won't be backported to Windows 10 Mobile, which is not supported anymore. That's why you shouldn't try to target something else than Windows 10 Desktop for now as the other platform simply won't work.


rkt: enter without executing process

I would like to be able to run rkt enter without executing a new process inside the container itself. I routinely have minimal containers with no /bin/bash that I need to get in and debug manually, but I cannot if rkt enter wants to execute a shell.

are you talking about #602 ?

yep, dupe

@bcwaldon I'm confused, what is it you want rkt enter to do upon entering the namespaces of the container if not execute something from within those namespaces?
It's not as if rkt enter can hand execution back to the calling process once it has been executed, it must either provide you with a shell itself if that's what you expect or run something provided by the container.
Your description sounds like expectations differing from what #602 is discussing, can you please clarify your expectations?


Adding Admin Log for Background checks

With the changes made to the Background check statuses (Submitted, Passed, and Failed), the way we are creating the admin logs no longer works since it is based off of a bool value.

 Adding Admin Log for Background checks #686


SlugService::createSlug() isn't creating unique slugs

I'm using SlugService::createSlug() in one part of my code because I want to override my default configuration and use a specific string "new post" for creating new models, instead of the normal source field "title" which is used elsewhere. But when I do this the string generated isn't unique with respect to existing instances of my model. I tried adding ['unique' => true] but it didn't help. I want the slug to be incremented normally, i.e. "new-post-1", "new-post-2", etc.
Relevant section of model:
class Page extends Model
{
	use Sluggable, NodeTrait
	{
		NodeTrait::replicate as replicateNode;
		Sluggable::replicate as replicateSlug;
	}
	// handle trait collision between NodeTrait and Sluggable
	public function replicate(array $except = null)
	{
		$instance = $this->replicateNode($except);
		(new SlugService())->slug($instance, true);
		return $instance;
	}
	public function sluggable()
	{
		return [
			'slug' => [
				'source' => 'title',
				'maxLength' => 50,
			]
		];
	}
	protected function getScopeAttributes()
	{
		return [ 'site_id' ];
	}
	// ...
}

My code:
$page = Page::create([
	'site_id' => $this->site->id,
	'parent_id' => $this->page->id,
	'title' => 'Headline',
	'slug' => SlugService::createSlug(Page::class, 'slug', 'new post', ['unique' => true]),
]);

The slug created is always "new-post" even if that instance already exists. I can see that the problem is that SlugService::createSlug() isn't aware of site_id—how can I do this?

I guess I can just do this, but it requires two database calls:
$page = Page::create([
	'site_id' => $this->site->id,
	'parent_id' => $this->page->id,
	'title' => 'New post',
]);
$page->title = 'Headline';
$page->save();

I'm not sure if this would work, but what about something like:
<?php
public function sluggable()
{
    return [
        'slug' => [
            'source' => 'slug_title',
            'unique' => true,
        ]
    ];
}

public function getSlugTitleAttribute()
{
    return $this->exists ? $this->getAttribute('title') : 'new post';
}

Closing due to no response.  Feel free to re-open or comment if you are still having issues.

In my case I don't want to mess with my model, which is more general than the thing I am working on. (And now I'm hitting this roadblock in a different part of my code).
I just want SlugService::createSlug() to do what it says on the tin—create unique slugs.

For anyone else reading this, the solution is to pass an instance instead of a class identifier:
Instead of SlugService::createSlug(Page::class, 'slug', 'new post')
You do SlugService::createSlug($page, 'slug', 'new post')

For my case I had 'static' keyword in model event callback like following.
static::saving(static function(Post $post) {}
When I removed 'static' keyword then SlugService::createSlug() was able to generate and save unique slug.
Thanks


Cann't listen to mousedown event

[ ] I'm reporting a bug, not asking for help
[ ] I've looked at the documentation to make sure the behaviour is documented and expected
[x] I'm sure this is a Leaflet code issue, not an issue with my own code nor with the framework I'm using (Cordova, Ionic, Angular, React…)
[ ] I've searched through the issues to make sure it's not yet reported

How to reproduce

Leaflet version I'm using: 0.7.7
Browser (with version) I'm using: Chrome 55.0.2883.87 m (64-bit)
OS/Platform (with version) I'm using: Window 10
step 1

document.addEventListener('mousedown', function() {
  console.log('mousedown')
})

step 2
Click the map area, see console in debug tool

ps:
map.on('mousedown') works well. But that's not I want.
What behaviour I'm expecting and which behaviour I'm seeing
It should print 'mousedown' when I click the map area.
Minimal example reproducing the issue

[x] this example is as simple as possible
[x] this example does not rely on any third party code

Using http://playground-leaflet.rhcloud.com/ or any other jsfiddle like site.

Cannot reproduce with https://playground-leaflet.rhcloud.com/xapi/edit?html,output with Leaflet 1.0.2.
It's possible that the 0.7.x series are preventing propagation of events on the map container, but I don't think it's worth it to backport a fix.


jwt.verify() not truly async.

Despite the verify action is in fact synchronize, the callback API does not.
It is specifically this line that released Zalgo.
https://github.com/auth0/node-jsonwebtoken/blob/5a7fa23c0b4ac6c25304dab8767ef840b43a0eca/verify.js#L24
Which can be fixed by wrapping it as such
    done = function(err, data) {
      setImmediate(callback, err, data);
    };

That behavior (with process.nextTick() though) was removed in this PR: https://github.com/auth0/node-jsonwebtoken/pull/302
I will leave the issue open in case the community has strong opinions about re-adding it or keep it as is. I understand the reasons, however, the pain to the event loop was already done while performing the verification synchronously, even doing that is "lying" to the consumer.
There was another discussion to remove the callback-ish style to that function, we didn't do it and now we support to get the secret/key asynchronously which gives sense to the callback now.

Forgive my words if the opinions is too strong, but to the best of my knowledge the consensus is already there for decades.
The nature of an asynchronous API should behave like it means, implementation should be hidden behind the API even if it is a so-called lie.
The API is the contract of behavior between the library and its users, and should be followed the moment it goes public as (Asynchronous) ....
IMO #302 should in fact use the (Synchronous) ... version without API for the desired performance gain, and such performance differences should be documented instead of breaking the API.

@MitMaro thanks.
I don't have much on the callback/promise/async controversy because of the disproportionate gain of productivity, the difference in performance is tiny; I like the inline error catching in async/await though.
But the breaking of the current API should be a hotfix instead of next major, there are potential risks for people using them in production.

Hey, I just want to point out that if you ever re-add code to make this async (which you should do), you should also really switch from process.nextTick to setImmediate. You can read about the differences here: https://nodejs.org/en/docs/guides/event-loop-timers-and-nexttick/
TL;DR process.nextTick doesn't allow the event loop time to handle things like I/O buffering before you run the verification function. Since cryptographic functions can take more than a few processor cycles to execute, you really do want to allow node to give itself a chance to handle its I/O before starting on your big chunk of work. Otherwise this library will negatively impact I/O perf much more than is necessary.

But, is there a reason such a heavy processing is done synchronously in the first place ?
The fact you remove the fake-callback-still-synchronous strategy is not really addressing that issue.

@cyrilchapon Everything in javascript is inherently single-threaded. Doing it "asynchronously" won't allow any other code to execute simultaneously. It'll just return after at least 1 tick of the event loop (process.nextTick) and it might also give the event loop time to handle I/O streams (setImmediate)

We might be able to use something like threads.js to do this in a real multi-threaded manner, which would be fun and sexy for everyone. But it also might reduce compatibility and/or require pseudo-polyfills like webworker-fallback

I believe the verify method is synchronous in nature and if we considered it a computationally expensive process we may use the node.js worker threads module to run it in parallel out of the main thread from the performance point of view.


idea recenter button

When calibration is done if i change the camera orientation or height i don't want to do the calibration again, i would like a quick button on the calibration tool to tell "this is the new height and center point" putting my PS move in front of my helmet for example.

I'm actually working on this right now. I plan to get this in for the next release I want to put out on Sunday.

Awesome :)

Glad to hear the turn around on this issue from  #59
@HyppoNymous  if you have a kinect at hand you can also try this OSVR plugin for positional tracking albeit at 30hz.
https://github.com/simlrh/OSVR-fusion

Scratch that. I took a stab at getting it to work, but it turns out that it's not immediately apparent how to the HMD pose from inside the psmove steamvr driver plugin (you can only get the poses of the devices your plugin provides). Getting the HMD pose will take a bit more work, which I'm going to do on Monday. In the meantime, there is a new release: https://github.com/cboulay/PSMoveService/releases/tag/v0.9-alpha4.6


Add support for github.com/common-fate/granted

https://github.com/common-fate/granted
https://docs.commonfate.io/granted/getting-started/#installing-the-cli

Thank you.

https://github.com/aquaproj/aqua-registry/pull/16085

v4.59.0 is out 🎉
https://github.com/aquaproj/aqua-registry/releases/tag/v4.59.0


Allow empty folders for known v3 folders

Allow nuget v3 folders to contain empty folders at pack file.
https://github.com/NuGet/Home/issues/1104
//cc @feiling @deepakaravindr @zhili1208 @yishaigalatzer

:shipit:

:shipit:

:shipit:


⚠ Bofrost.fr has degraded performance

In 7436cc5, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 947 ms

Resolved: Bofrost.fr performance has improved in 386bdee after 6 minutes.


mstsc.exe which under wslhost.exe keep crashing and causes every window refreshing

Environment
Windows build number: Microsoft Windows [Version 10.0.22000.527]
Your Distribution version: Ubuntu 20.04
Your WSLg version: 1.0.26

Steps to reproduce

Not always can reproducing this problem.
WSL logs:

Attach WSLg logs from  /mnt/wslg

I've checked these logs, the really interesting parts listed here:
stderr.log:
weston: ../libweston/backend-rdp/rdpclip.c:525: clipboard_process_bmp: Assertion `bits == (DWORD*)(&bmi->bmiColors[color_table_size/sizeof(RGBQUAD)])' failed.
<4>WSLGd: /usr/bin/weston terminated with signal 6.
<4>WSLGd: /mnt/c/Windows/System32/mstsc.exe exited with status 5.

weston.log
pulseaudio.log
and one more important thing here which from Windows Logs:
Faulting application name: mstsc.exe, version: 10.0.22000.282, time stamp: 0x4f2ad43b
Faulting module name: WSLDVCPlugin.dll_unloaded, version: <IP_ADDRESS>, time stamp: 0x60f0bddd
Exception code: 0xc0000005
Fault offset: 0x000000000000239d
Faulting process id: 0x424c
Faulting application start time: 0x01d83363eaa62081
Faulting application path: C:\Windows\System32\mstsc.exe
Faulting module path: WSLDVCPlugin.dll
Report Id: eee57cbf-9db5-4abf-b6fc-5617a3d07429
Faulting package full name:
Faulting package-relative application ID:

Fault bucket<PHONE_NUMBER>122348732, type 5
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: mstsc.exe
P2: 10.0.22000.282
P3: 4f2ad43b
P4: WSLDVCPlugin.dll_unloaded
P5: <IP_ADDRESS>
P6: 60f0bddd
P7:<PHONE_NUMBER>00239d
P8: c0000005
P9:<PHONE_NUMBER>000008
P10:

Attached files:
<omitted>

These files may be available here:
<omitted>

Analysis symbol:
Rechecking for solution: 0
Report Id: 4f31498d-3aa1-4a03-9edc-8bb6c7513fe0
Report Status: 268435456
Hashed bucket: b56f467c88760cb78ef60ef45e1bccbc
Cab Guid: 0

Expected behavior

don't crash
Actual behavior

Today I noticed my whole Windows keep refreshing everything per second, including almost every window, especially for the "Notification Area", which previously Windows 11 keeps buggy refreshing and flickering。
So, I'm trying to figure out which naughty process causes this and with procexp.exe which from Windows SysInternal Suite, I've noticed this:

The rdp client process keeps crashing, and WerFault.exe came out. This happens every second.
Tried shutting down WSL by wsl --shutdown, they calm down. but once WSL restarted, turns to that situation again.
but minutes after, it's fine and stable again, and during that time, I have not making any noticeable action.

would you please update to the latest WSL from aka.ms/wslstorepage
OK, I've done that now, I will see if this would happen again.

[Version 10.0.22000.527]

Maybe try updating to Windows 11?

Maybe try updating to Windows 11?

That is Windows 11, see wiki here

@epiciskandar, thanks for trying out the latest WSL, and let us know if this happens again. Just to be clear for the crash in mstsc.exe, which is known and reported at https://github.com/microsoft/wslg/issues/287 and this issue still exists, but since this crash is secondary which only happens when it's forcibly disconnected by weston crash, thus given the latest WSL has the fix for that weston crash, the secondary crash from mstsc.exe should not happen either. Thanks!

The latest WSL kernel(<IP_ADDRESS>-microsoft-standard-WSL2) works stable for days, so I'm going to close this issue for now.

I am currently experiencing this exact issue.
This is my wsl version
wsl --update Checking for updates... No updates are available. Kernel version: <IP_ADDRESS>
This is my Windows version
Version 21H2 (OS Build 22000.556)

@ryanhinton, have you updated WSL from aka.ms/wslstorepage?

No. I intentionally and originally did not install WSL through the Microsoft store and I prefer not to use the store to install, if it is not necessary.  The CLI command wsl --update should offer the same update, is that not correct?

@ryanhinton, may I ask you share the output from wsl --version?

Hi @hideyukn88, you are correct.  it is not available.  I have to use wsl -l -v to retrieve the version.  OK, I will have to wait for the release to older Windows 11 release.  What version of Windows 11 currently allows for the newest wsl release that does not require the using the store installation?
`$ wsl -l -v
NAME                   STATE           VERSION

Ubuntu                 Running         2
docker-desktop-data    Stopped         2`

Is there any reason why wsl is not yet updatable using wsl --update command?

As I noted above comments, current wsl.exe in Windows 11 does not support updating WSL from Store. The newer version of wsl.exe will be available from Windows Update for public release soon. While I can't not say when that will be but it's already insider version of Windows 11, so it should be within a month or two. Thanks!

Linux NOPE <IP_ADDRESS>-microsoft-standard-WSL2 #1 SMP Wed Mar 2 00:30:59 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
still crash

@RimuruChan, would you please share the output of wsl --version on Windows's command prompt? thanks!

@RimuruChan, would you please share the output of wsl --version on Windows's command prompt? thanks!

Thanks for your reply, I have solved the problem by updating the latest version

Hi seem to have this problem with my:
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>
WSLg version: 1.0.49
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19044.2604


windows server support needed!

for some reason,we must stay windows platform.
compiling  pulsar-cpp always give errors.
any plan offering support for windows? thanks!

@guzuomuse thank you for reporting.  we'd love to support windows, however most of the committers are more familiar with linux/macos. if you can share some of your build errors, we might have some ideas on how to help you better.

@sijie ,thanks your reply,here is error log when i compile the c++ client with cmake gui:
`
BUILD_TESTS:  ON
LINK_STATIC:  OFF
USE_LOG4CXX:  OFF
CMAKE_BUILD_TYPE:
Found ZLIB: F:/en_folder_for_testing/zlib-1.2.11/cmake/Release (found version "1.2.11")
Could NOT find Protobuf (missing: Protobuf_LIBRARIES Protobuf_INCLUDE_DIR)
PYTHON: 3.7.0
DETECTED Python 3
CMake Warning at D:/Program Files/CMake/share/cmake-3.12/Modules/FindBoost.cmake:1723 (message):
No header defined for python3-mt; skipping header check
Call Stack (most recent call first):
CMakeLists.txt:120 (find_package)
CMake Warning at D:/Program Files/CMake/share/cmake-3.12/Modules/FindBoost.cmake:1723 (message):
No header defined for python-py37; skipping header check
Call Stack (most recent call first):
CMakeLists.txt:120 (find_package)
CMake Warning at D:/Program Files/CMake/share/cmake-3.12/Modules/FindBoost.cmake:1723 (message):
No header defined for python37-mt; skipping header check
Call Stack (most recent call first):
CMakeLists.txt:120 (find_package)
Boost version: 1.68.0
Found the following Boost libraries:
program_options
filesystem
regex
thread
system
python37
chrono
date_time
atomic
CMake Error at lib/CMakeLists.txt:42 (set_target_properties):
set_target_properties called with incorrect number of arguments.
CMake Error at lib/CMakeLists.txt:43 (set_target_properties):
set_target_properties called with incorrect number of arguments.
CMake Warning (dev) at python/CMakeLists.txt:34 (if):
Policy CMP0054 is not set: Only interpret if() arguments as variables or
keywords when unquoted.  Run "cmake --help-policy CMP0054" for policy
details.  Use the cmake_policy command to set the policy and suppress this
warning.
Quoted variables like "MSVC" will no longer be dereferenced when the policy
is set to NEW.  Since the policy is not set the OLD behavior will be used.
This warning is for project developers.  Use -Wno-dev to suppress it.
Using Boost Python libs: optimized;D:/programs/boost_1_68_0/lib64-msvc-14.1/boost_python37-vc141-mt-x64-1_68.lib;debug;D:/programs/boost_1_68_0/lib64-msvc-14.1/boost_python37-vc141-mt-gd-x64-1_68.lib
clang-tidy not found
clang-format not found
CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
CURL_LIBRARY_PATH
linked by target "pulsarStatic" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/lib
linked by target "pulsarShared" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/lib
linked by target "perfProducer" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/perf
linked by target "perfConsumer" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/perf
linked by target "SampleReaderCApi" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
linked by target "SampleAsyncProducer" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
linked by target "SampleConsumerListener" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
linked by target "SampleConsumer" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
linked by target "SampleProducer" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
linked by target "SampleProducerCApi" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
linked by target "SampleConsumerListenerCApi" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
linked by target "SampleConsumerCApi" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
linked by target "main" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/tests
GMOCK_INCLUDE_PATH
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/lib
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/lib
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/perf
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/perf
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/tests
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/python
GMOCK_LIBRARY_PATH
linked by target "main" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/tests
GTEST_INCLUDE_PATH
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/lib
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/lib
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/perf
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/perf
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/tests
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/python
JSON_INCLUDE_PATH
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/lib
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/lib
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/perf
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/perf
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/tests
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/python
LIB_JSON
linked by target "pulsarStatic" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/lib
linked by target "pulsarShared" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/lib
linked by target "perfProducer" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/perf
linked by target "perfConsumer" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/perf
linked by target "SampleReaderCApi" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
linked by target "SampleAsyncProducer" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
linked by target "SampleConsumerListener" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
linked by target "SampleConsumer" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
linked by target "SampleProducer" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
linked by target "SampleProducerCApi" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
linked by target "SampleConsumerListenerCApi" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
linked by target "SampleConsumerCApi" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
linked by target "main" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/tests
PROTOBUF_LIBRARIES
linked by target "pulsarStatic" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/lib
linked by target "pulsarShared" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/lib
linked by target "perfProducer" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/perf
linked by target "perfConsumer" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/perf
linked by target "SampleReaderCApi" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
linked by target "SampleAsyncProducer" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
linked by target "SampleConsumerListener" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
linked by target "SampleConsumer" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
linked by target "SampleProducer" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
linked by target "SampleProducerCApi" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
linked by target "SampleConsumerListenerCApi" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
linked by target "SampleConsumerCApi" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
linked by target "main" in directory F:/en_folder_for_testing/pulsar-client-cpp/source/tests
Protobuf_INCLUDE_DIR (ADVANCED)
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/lib
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/lib
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/perf
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/perf
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/examples
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/tests
used as include directory in directory F:/en_folder_for_testing/pulsar-client-cpp/source/python
Configuring incomplete, errors occurred!
See also "F:/en_folder_for_testing/pulsar-client-cpp/cmake/CMakeFiles/CMakeOutput.log".
See also "F:/en_folder_for_testing/pulsar-client-cpp/cmake/CMakeFiles/CMakeError.log".
`

@guzuomuse
You're missing some of the dependencies. For tests, you can disable by passing -DBUILD_TESTS=OFF to cmake.
For the rest, you need to install:

Libcurl : https://github.com/curl/curl
JsonCpp : https://github.com/open-source-parsers/jsoncpp
Protocol buffer: https://developers.google.com/protocol-buffers/

Anyway, the deps for tests are :

GTest : https://github.com/google/googletest
Google Mock: https://github.com/google/googlemock

@merlimat ,thank you very much ,i will try and then give my feedback

@merlimat @sijie
unfortunately. cause too many dependencies drive me crazy.
i will look back.but i have to give up for now.

A conan.io support would make all this much simpler

A vcpkg support would make all this much simpler :)


No events sent when a service replica change in global replica mode

I'm using it with docker-flow-monitor and flexible labeling. When I create a new node on the swarm, an event is correctly sent to DF_NOTIFY_CREATE_NODE_URL. However, as I have some exporters configured as global, no event is sent to DF_NOTIFY_CREATE_SERVICE_URL. It's a problem as these new replicas do not appears in targets and thus do not scrape metrics.
Steps to reproduce the issue:

Setup the stack and node-exporter as replica mode global
Add a new node to the stack

Describe the results you received:
I only see this event but no event for services that add new instances.
monitor_monitor-swarm-listener.1.q8vu6fuqdr8z@swarm-manager-2    | 2018/05/25 12:33:19 Sending node created notification to http://monitor:8080/v1/docker-flow-monitor/node/reconfigure?address=<IP_ADDRESS>&availability=active&hostname=swarm-worker-3&id=hxzf579q0guyqsz722iixpj7q&role=worker&state=ready&versionIndex=795`

Describe the results you expected:
I expected an event to be fired for each services that add a replica.
Additional information you deem important (e.g. issue happens only occasionally):
I believe targets are updated properly on docker-flow-monitor if used with dns_sd_config instead of file_sd_config
Additional environment details (AWS, VirtualBox, physical, etc.):
I'm testing it on VirtualBox

Note that a docker-service update actually resolve the issue. So I imagine that I would need to add this in the pipeline if I handle scaling with Jenkins. Do Docker Flow Scaler actually handle this use-case?

Can you test out thomasjpfan/docker-flow-swarm-listener:6f2ff36 for your use case?

@thomasjpfan thanks for your prompt response. I'll test it next Monday and keep you informed.

My fix does not work. I will take another look at this.

I have updated DFSL to send service notifications after sending node notifications. You can test this feature out in dockerflow/docker-flow-swarm-listener:18.05.27-13.

@thomasjpfan I tested and it works perfectly! 👍
As a side note, and it's related to docker and not to docker-flow-swarm-listener, when a node is put down, services in replica mode global also scale down. This means that if we rely on prometheus targets "up" status to detect unavailable nodes it never works.

@Munchery-DavidMichon When a node is drained or goes down, DFSL will notify DFM on the updated list of running exporters. That means the exporter on the drained/down node will be removed from the target list.
Theoretically, if DFM was setup to keep metrics from downed nodes, that target list will become larger through time. What would be a good indicator to remove the metric from the list?

I strongly believe that DFM and DFSL works exactly the way we expect them to work because it reflect exactly what docker API gives.
In my opinion the issue is more on docker. When you set a service as global and a node is down, the service replicas should be in a state 5/6 (in my case), and not 5/5.  My cluster count effectively 6 nodes, not all in Ready state but 6 are Active in their availability.
The problem here is that DFM remove metrics (correctly) because it understands that he has 5 targets to track to, so all are up. I would not change anything to DFM to keep metrics for downed nodes. It's correct in its design and implementation.
I need to detect in another way that a node is down. Perhaps another exporter that do just that, export nodes status and availability as metrics.

@Munchery-DavidMichon I'm following this now, since we're interested in this problem as well. I'm curious if you can get docker-socat running in your stack, and if the Docker metrics it presents contain the right info to solve for this use-case. We have not been able to successfully deploy docker-socat in our stack, but if others are able to do so successfully, we would love to be able to learn from them ...

@Munchery-DavidMichon thanks for the write-up! I will be sure to pass this along to our team for feedback.

We can consider this issue resolved.


How to design training data for a model which only needs to synthesis single English words?

Hi all, I'm building my own TTS system which I hope can synthesis both Mandarin and English. Usually the text contains only a few English words such as 'Sorry', 'Micheal Jackson', 'NBA','WIFI' etc, and the rest of it are all Chinese. What I need is to train an English model which is able to clearly pronounce single English words base on the audios recorded by the same speaker to guarantee the consistency. The problem is that this speaker can offer me very limited amount of English audios.
So, What text shall I give her to record? A list of English words? The goal is to provide text with amount of words just enough to cover all English phoneme pronunciation rules. Any suggestion?
Thanks in advance!

If you want phonetic balance, the CMU ARCTIC database sentences were put
together for this purpose:
http://www.festvox.org/cmu_arctic/
http://www.festvox.org/cmu_arctic/cmuarctic.data
it's 1132 sentences or about an hour of speech, so maybe others have
recommendations for smaller sets as well.
Best,
Erica
On Wed, Oct 17, 2018 at 4:33 AM, MinuitYang<EMAIL_ADDRESS>wrote:

Hi all, I'm building my own TTS system which I hope can synthesis both
Mandarin and English. Usually the text contains only a few English words
such as 'Sorry', 'Micheal Jackson', 'NBA','WIFI' etc, and the rest of it
are all Chinese. What I need is to train an English model which is able to
clearly pronounce single English words base on the audios recorded by the
same speaker to guarantee the consistency. The problem is that this speaker
can offer me very limited amount of English audios.
So, What text shall I give her to record? A list of English words? The
goal is to provide text with amount of words just enough to cover all
English phoneme pronunciation rules. Any suggestion?
Thanks in advance!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/CSTR-Edinburgh/merlin/issues/404, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABReNtCozWeeilk1tbP5p0m-Dgkv1hupks5ulutcgaJpZM4XjZhl
.

If the announcer naturally sounds very similar to slt_arctic then there may be nothing to change.
Otherwise, the most likely reason is accidentally training on the slt_arctic data. Make sure you are certain which data is being used in training model.


Bump github.com/docker/docker to v20.10.18

To fix CVE-2022-36109
Signed-off-by: Hui Yu<EMAIL_ADDRESS>

All checks have passed


feat(animator-lifecycle)

Resolves issue from #28
Also Please see notes from #28

@joelcoxokc I think you will need to rebase this on the latest version in master.

@joelcoxokc Can you rebase this on master? We can't merge it as is.

@EisenbergEffect Yes I will

Just to clear up something from the description of this issue, #28 is already solved in the most recent release. Glad the code is being cleaned up whether the fix is still needed or not.

I'm going to close this for now. We've had some big changes and a couple more fixes have come in. We would like to rework the innards. It's probably better to do it as a new PR.

@EisenbergEffect Might any of those changes fix the super serious repeat bug: https://github.com/aurelia/templating-resources/issues/183
I've had to stop demoing my project to people because the first thing they raise is how badly the lists become out of order :( Our team is worried we made the wrong choice with Aurelia :(

@Ohjames one of the greatest things about Aurelia, is that it's pluggable and extensible. The CSS animator is obviously not as extensive a something like GreenSock. I personally dont think the animator should determine whether you made the right decision on a framework.
Let chat some time this coming weekend, and maybe we can nail down the bug.

@joelcoxokc The issue isn't with the animator but to do with the way the framework interacts with the animator leading to a desync. I spent about 30 hours trying to fix the various desync issues in aurelia leading to three PRs that are now part of Aurelia... but this last desync issue really worries me. I think it might involve some really significant changes.

What exactly do you mean by desync, I think I have an idea...
Or do you have a reference where you recently discussed?
On Mon, Feb 29, 2016 at 9:07 AM Mr Friend<EMAIL_ADDRESS>wrote:

@joelcoxokc https://github.com/joelcoxokc The issue isn't with the
animator but to do with the way the framework interacts with the animator
leading to a desync. I spent about 30 hours trying to fix the various
desync issues in aurelia leading to three PRs that are now part of
Aurelia... but this last desync issue really worries me. I think it might
involve some really significant changes.
—
Reply to this email directly or view it on GitHub
https://github.com/aurelia/animator-css/pull/37#issuecomment-190292590.

@joelcoxokc Here is the issue for the bug @ohjames referring to https://github.com/aurelia/templating-resources/issues/183


Feature/test workflows

This allows tooltester to test workflows.  Additionally it can also grab files from an s3 repository whose name is passed in as a parameter of any PipelineTest job.

Coverage increased (+29.4%) to 79.772% when pulling 183b2b0c149d8976462f6851d87cf8bf4121b8ec on feature/testWorkflows into 11414d22892788559e3d00c1f6c130d4dff3c34a on develop.

Coverage increased (+29.4%) to 79.772% when pulling 021e3c1e3134548818855804e4b9c27e34ec8977 on feature/testWorkflows into 11414d22892788559e3d00c1f6c130d4dff3c34a on develop.

Coverage increased (+29.3%) to 79.714% when pulling cbbaed91302383c3bb505c2a068c58933d20615a on feature/testWorkflows into 11414d22892788559e3d00c1f6c130d4dff3c34a on develop.


Is there a plan for task flow to support forking and aggregation?

bi seems to have a strong need to support both forking and aggregation. xxl currently supports forking and Azkaban supports aggregation, neither of which is ideal.
bi似乎很需要同时支持分叉和聚合，目前xxl支持分叉，阿兹卡班支持聚合，都不太理想。

bi seems to have a strong need to support both forking and aggregation. xxl currently supports forking and Azkaban supports aggregation, neither of which is ideal.
bi似乎很需要同时支持分叉和聚合，目前xxl支持分叉，阿兹卡班支持聚合，都不太理想。

Dear friend, I translated your question into English because of the internationalization of the project, thank you for your understanding.
There are plans for forking and aggregation of task flows, but currently, it will be scheduled for the 2022 roadmap, and there are 6 main features in development for the 2021 roadmap.
The future will already be in the form of interactive drawings (expressing the forking and aggregation of task flows), giving the user an interface to freely organize the processing flow of tasks!

use bpmn.js?

bpmn.js

Thank you for your valuable advice on the front-end.
At the moment it is mainly being developed according to the Roadmap, and the task flow will be implemented in a later opportunity.


Previous track can be played while the current track is initially loading

Describe the Bug
From https://discord.com/channels/567636850513018880/600714011318681610/974596964912070666

In iOS if any track of the queue has wrong track  url (like no track found) then track change action does change the current track info and payback track change event also trigger. But previously playing track still continue to play.. actual track does not change..

Steps To Reproduce
Code To Reproduce
Environment Info:

@AshrafulAfruz I tested this against the work that's been done on this PR (which addresses a bunch of track changed issues), and I wasn't able to reproduce it. For that reason, I'm going to consider this effectively a "duplicate" issue of the issues that were identified there and close it.
If you can, please pull down my branch and verify that it's fixed from your perspective too. If not, I'm happy to reopen.

https://user-images.githubusercontent.com/38793029/170449168-cac43c92-3a8e-4ad1-83f3-757bd49c7bc8.mp4
@jspizziri  I don't know how could I test by your change. What   did was cloning your repository and run example project from there. But I think it's using version 2.2.0-rc3. Here i'm providing a screencast ( on example project showing it's behavior) so that it might help. Please can you check if your changes actually address this issue.?

@AshrafulAfruz When you cloned my fork did you make sure to checkout my branch?

@jspizziri  I have tested in your branch. The problem still exists. But your new refactored example code bypasses that scenario as it remain in connecting state. If there is errored track it remain in connecting state but invoking trackplayer.play() at that time causes the last correct track to start playing (though playback progress show current track index).

@AshrafulAfruz Can you share a reproducible example based off of my branch? Please also include steps to reproduce. I can't reproduce it so we must be missing each other on some point.

For reproducing the problem I have made following changes,
In  file example/src/components/PlayPauseButton.tsx  changed
if (isLoading) {
    return (
      <View style={styles.statusContainer}>
        {isLoading && <ActivityIndicator />}
      </View>
    );
  }

to
if (isLoading) {
    return (
      <>
        <Button
          title={isPlaying ? 'Pause' : 'Play'}
          onPress={onTogglePlayback}
          type="primary"
        />
        <View style={styles.statusContainer}>
          {isLoading && <ActivityIndicator />}
        </View>
      </>
    );
  }

so that play button can show at state connecting time.
And modified  example/src/assets/data/playlist.json as follow
[
  {
    "url": "https://react-native-track-player.js.org/example/Longing.mp3",
    "title": "Longing",
    "artist": "David Chavez",
    "artwork": "https://react-native-track-player.js.org/example/Longing.jpeg",
    "duration": 143
  },
  {
    "url": "https://react-native-track-player.js.org/example/Soul%20Searching.mp3",
    "title": "Soul Searching (Demo)",
    "artist": "David Chavez",
    "artwork": "https://react-native-track-player.js.org/example/Soul%20Searching.jpeg",
    "duration": 77
  },
  {
    "url": "http://<IP_ADDRESS>:8028/stream",
    "title": "Radio Amar",
    "artwork": "https://d2h2ofqh3tbq9r.cloudfront.net/station_image/logo_2.png",
  },
  {
    "url": "http://google.com",
    "title": "Google",
    "artwork": "https://react-native-track-player.js.org/example/Soul%20Searching.jpeg",
  },
  {
    "url": "https://react-native-track-player.js.org/example/Lullaby%20(Demo).mp3",
    "title": "Lullaby (Demo)",
    "artist": "David Chavez",
    "artwork": "https://react-native-track-player.js.org/example/Lullaby%20(Demo).jpeg",
    "duration": 71
  },
  {
    "url": "https://react-native-track-player.js.org/example/Rhythm%20City%20(Demo).mp3",
    "title": "Rhythm City (Demo)",
    "artist": "David Chavez",
    "artwork": "https://react-native-track-player.js.org/example/Rhythm%20City%20(Demo).jpeg",
    "duration": 106
  }
]

Adding invalid track in 3rd and 4th position.
Reproducible steps:

run the app after modifying above 2 files.
play first/second track
click next
(Observe in 3rd track it continue to loading state.)
click on the play button. (Previously running track start to resume). Also observe the log.

Optional extra steps:
5) toggle between play pause.
6) click next. (it will exibit the same behavior of from 3 step for 4th track also.
Let me know if you could reproduce this problem.

@AshrafulAfruz alright. I've followed your steps and I can reproduce your behavior.
In this scenario it is correct that the track-changed is fired, as the app has transitioned to the next track, but because it's broken it sits there in a loading state and eventually fails with the following exception:
*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Error when sending event: playback-error with body: {
    error = "The request timed out.";
}

The only issues I see here are the following:

It is strange that if you hit the "play" button again it will briefly play the previous track (which is perhaps your initial report). I agree that this shouldn't happen, but I do think it's fairly edge-case, as a good design pattern would be to not allow users to hit the play button when a track is attempting to load. Regardless, I do think it's a bug, and I think the expected behavior would effectively for play to do nothing in this scenario. I'm going to reopen this issue.
A request timeout error should not be causing a fatal exception and should instead be bubbling up through the PlaybackError event. This I think can be considered a separate issue, and I'm opening a new ticket for it.

@jspizziri Running previous track is a problem when programmatically control the playing of track. It limits the functionality. For example, one of my requirements is that when hitting next button, track should start playing irrespective of currently it was playing or not. So what i do is after skipping to the next track manually start the playback. I have another usecase where need to manually start the playback where i have to manage shuffling.

@jspizziri I've just found that android also have problem regarding errored tracks. Now in android playback error is not fired and playback state become 0 (State.none) and further operation can not be performed. like changing to a good track then trackplayer.play() does not change the state anymore.

Looking at the source code I can see the fail case for the initial load of the item happening here:
https://github.com/doublesymmetry/SwiftAudioEx/blob/main/SwiftAudioEx/Classes/AVPlayerWrapper/AVPlayerWrapper.swift#L228
But indeed, nothing is done to the current item at this point – which means it just continues playing. We probably want to call AVPlayerWrapper.swift at that point, which will set replace the current avplayer item with nil:
https://github.com/doublesymmetry/SwiftAudioEx/blob/main/SwiftAudioEx/Classes/AVPlayerWrapper/AVPlayerWrapper.swift#L255

Opened a pull request to solve this here: https://github.com/doublesymmetry/SwiftAudioEx/pull/25

This issue will be fixed when v3.2 is released.


Initial refactoring/implementation of expanded tests and support for npm

Differences from the original:

added bin file for execution with npx
removed code that was async vs sync
expanded tests to cover more cases
added support for npm detection

📦 Published PR as canary version: 1.0.1--canary.1.a8aca37.0

:sparkles: Test out this PR locally via:
npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>

:rocket: PR was released in v1.0.1 :rocket:


break the summary tests into separate tests for nodes, reports and controls

Signed-off-by: Rick Marry<EMAIL_ADDRESS>:nut_and_bolt: Description
In order to improve test readability and, in case of test failures, to more easily see failure origin, the stats summary tests are being separated into three distinct sections:
1 - reports
2 - nodes
3 - controls
:+1: Definition of Done
:athletic_shoe: Demo Script / Repro Steps
:chains: Related Resources
:white_check_mark: Checklist

[x] Necessary tests added/updated?
[ ] Necessary docs added/updated?
[ ] Code actually executed?
[ ] Vetting performed (unit tests, lint, etc.)?

Sorry if I wasn't clear in my other comment, but I think it'd be ok to keep the test setup shared but have a different test for each of the code paths. For the suggestions tests, the test setup and results were the same for each suggestion type but they take different ways of getting the data, so I split those into multiple tests for each test case: https://github.com/chef/automate/pull/322#discussion_r283510492

Sorry if I wasn't clear in my other comment, but I think it'd be ok to keep the test setup shared but have a different test for each of the code paths. For the suggestions tests, the test setup and results were the same for each suggestion type but they take different ways of getting the data, so I split those into multiple tests for each test case: #322 (comment)

Thanks @phiggins.  I've refactored a bit. I moved some of the boilerplate stuff into a setup func and call it from each test now.  This cuts down on the the duplicate code and makes things more readable.


[BUG] ListStore::find_with_equal_func segfaults

Bug description
fn main() {
    gio::ListStore::new(glib::Type::OBJECT).find_with_equal_func(|_| todo!());
}

Cargo.toml:
[package]
name = "x"
version = "0.1.0"
edition = "2021"
[dependencies]
gio = { version = "0.17.0", features = ["v2_74"] }
glib = "0.17.1"

Backtrace
Segmentation fault (core dumped)

Valgrind output:
$ valgrind target/debug/x
==2927== Memcheck, a memory error detector
==2927== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==2927== Using Valgrind-3.19.0 and LibVEX; rerun with -h for copyright info
==2927== Command: target/debug/x
==2927==
==2927== Invalid read of size 8
==2927==    at 0x4993321: g_list_store_find_with_equal_func_full (gliststore.c:585)
==2927==    by 0x1104C7: gio::list_store::<impl gio::auto::list_store::ListStore>::find_with_equal_func (list_store.rs:97)
==2927==    by 0x1105CD: x::main (main.rs:2)
==2927==    by 0x11077A: core::ops::function::FnOnce::call_once (function.rs:250)
==2927==    by 0x11036D: std::sys_common::backtrace::__rust_begin_short_backtrace (backtrace.rs:121)
==2927==    by 0x1106A0: std::rt::lang_start::{{closure}} (rt.rs:166)
==2927==    by 0x12418B: call_once<(), (dyn core::ops::function::Fn<(), Output=i32> + core::marker::Sync + core::panic::unwind_safe::RefUnwindSafe)> (function.rs:287)
==2927==    by 0x12418B: do_call<&(dyn core::ops::function::Fn<(), Output=i32> + core::marker::Sync + core::panic::unwind_safe::RefUnwindSafe), i32> (panicking.rs:483)
==2927==    by 0x12418B: try<i32, &(dyn core::ops::function::Fn<(), Output=i32> + core::marker::Sync + core::panic::unwind_safe::RefUnwindSafe)> (panicking.rs:447)
==2927==    by 0x12418B: catch_unwind<&(dyn core::ops::function::Fn<(), Output=i32> + core::marker::Sync + core::panic::unwind_safe::RefUnwindSafe), i32> (panic.rs:140)
==2927==    by 0x12418B: {closure#2} (rt.rs:148)
==2927==    by 0x12418B: do_call<std::rt::lang_start_internal::{closure_env#2}, isize> (panicking.rs:483)
==2927==    by 0x12418B: try<isize, std::rt::lang_start_internal::{closure_env#2}> (panicking.rs:447)
==2927==    by 0x12418B: catch_unwind<std::rt::lang_start_internal::{closure_env#2}, isize> (panic.rs:140)
==2927==    by 0x12418B: std::rt::lang_start_internal (rt.rs:148)
==2927==    by 0x110679: std::rt::lang_start (rt.rs:165)
==2927==    by 0x11063D: main (in /home/USERNAME/miniproj/list-store-find-with-equal-busted/target/debug/x)
==2927==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==2927==
==2927==
==2927== Process terminating with default action of signal 11 (SIGSEGV): dumping core
==2927==  Access not within mapped region at address 0x0
==2927==    at 0x4993321: g_list_store_find_with_equal_func_full (gliststore.c:585)
==2927==    by 0x1104C7: gio::list_store::<impl gio::auto::list_store::ListStore>::find_with_equal_func (list_store.rs:97)
==2927==    by 0x1105CD: x::main (main.rs:2)
==2927==    by 0x11077A: core::ops::function::FnOnce::call_once (function.rs:250)
==2927==    by 0x11036D: std::sys_common::backtrace::__rust_begin_short_backtrace (backtrace.rs:121)
==2927==    by 0x1106A0: std::rt::lang_start::{{closure}} (rt.rs:166)
==2927==    by 0x12418B: call_once<(), (dyn core::ops::function::Fn<(), Output=i32> + core::marker::Sync + core::panic::unwind_safe::RefUnwindSafe)> (function.rs:287)
==2927==    by 0x12418B: do_call<&(dyn core::ops::function::Fn<(), Output=i32> + core::marker::Sync + core::panic::unwind_safe::RefUnwindSafe), i32> (panicking.rs:483)
==2927==    by 0x12418B: try<i32, &(dyn core::ops::function::Fn<(), Output=i32> + core::marker::Sync + core::panic::unwind_safe::RefUnwindSafe)> (panicking.rs:447)
==2927==    by 0x12418B: catch_unwind<&(dyn core::ops::function::Fn<(), Output=i32> + core::marker::Sync + core::panic::unwind_safe::RefUnwindSafe), i32> (panic.rs:140)
==2927==    by 0x12418B: {closure#2} (rt.rs:148)
==2927==    by 0x12418B: do_call<std::rt::lang_start_internal::{closure_env#2}, isize> (panicking.rs:483)
==2927==    by 0x12418B: try<isize, std::rt::lang_start_internal::{closure_env#2}> (panicking.rs:447)
==2927==    by 0x12418B: catch_unwind<std::rt::lang_start_internal::{closure_env#2}, isize> (panic.rs:140)
==2927==    by 0x12418B: std::rt::lang_start_internal (rt.rs:148)
==2927==    by 0x110679: std::rt::lang_start (rt.rs:165)
==2927==    by 0x11063D: main (in /home/USERNAME/miniproj/list-store-find-with-equal-busted/target/debug/x)
==2927==  If you believe this happened as a result of a stack
==2927==  overflow in your program's main thread (unlikely but
==2927==  possible), you can try to increase the size of the
==2927==  main thread stack using the --main-stacksize= flag.
==2927==  The main thread stack size used in this run was 8388608.
==2927==
==2927== HEAP SUMMARY:
==2927==     in use at exit: 43,521 bytes in 305 blocks
==2927==   total heap usage: 427 allocs, 122 frees, 56,681 bytes allocated
==2927==
==2927== LEAK SUMMARY:
==2927==    definitely lost: 0 bytes in 0 blocks
==2927==    indirectly lost: 0 bytes in 0 blocks
==2927==      possibly lost: 0 bytes in 0 blocks
==2927==    still reachable: 41,089 bytes in 279 blocks
==2927==         suppressed: 0 bytes in 0 blocks
==2927== Rerun with --leak-check=full to see details of leaked memory
==2927==
==2927== For lists of detected and suppressed errors, rerun with: -s
==2927== ERROR SUMMARY: 2 errors from 1 contexts (suppressed: 0 from 0)
Segmentation fault (core dumped)

(Disclaimer: I know nothing about GTK/GIO/etc; this is just from clicking around.)
Seems like gio's g_list_store_find_with_equal_func_full expects an item as its second argument, but the Rust code passes a null instead:
https://github.com/gtk-rs/gtk-rs-core/blob/5d37089882c7d8765e0d6b16445954f99dd4bcc7/gio/src/list_store.rs#L99
This triggers a segfault on line 585 of gliststore.c, as seen above in the valgrind output, because it contains G_OBJECT_TYPE (item). G_OBJECT_TYPE is #define'd to G_TYPE_FROM_INSTANCE, which seems to dereference item.

Yes that analysis looks correct. IMHO line 585 should be changed in glib too (allowing NULL seems useful) but we'll also have to fix this on our side somehow.
As calling the function right now is impossible, changing the API would be fine. Do you want to provide a PR?
CC @pbor

Also reporting this to GLib so that NULL is allowed would seem useful. And also CC @jf2048 who actually added this function to GLib 10 months ago so we can use it here :)

Writing the PR sounds like fun, although I'm a bit busy. I'll try doing it, but if I don't post it in the next 24 hours or so, assume real life caught up to me :p

We could construct a value on the stack before calling the C function that looks close enough to a GObject of the correct type. Then the current intended behaviour and API could  be kept.

Part 1: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3284

Part 2: https://github.com/gtk-rs/gtk-rs-core/pull/1015


Apply windowrule to specific window

Description
Exec with window rules is not always workingcan not handle some usecases. It would be convenient if something like "apply windowrule dispatcher" or hyprctl apply rule window and someway of undone is available.
My specific usecase is to toggle nofocus rule.

exec rule itself is working as expected. It does not handle my usecase (dynamically apply and clear windowrule to existent window) .

elaborate?

what about hyprctl keyword "windowrulev2 [rule], [window]"

what about hyprctl keyword "windowrulev2 [rule], [window]"
windowrulev2 does not support specifying window id.

what's a window id? Never heard of such a thing.

Ah, I mean, address

it's dynamic and always changes, though.

Does address change during window is open?
Then pid is ok?
hyprctl apply [rule] [pid]

no, once it's open it doesn't...
have you checked hyprctl setprop?

Yes but setprop does not support nofocus...

ok I finally understand what you want from me, tho xD

Yes but setprop does not support nofocus...

it does now


fixed unix timestamp for schedule start in Pavia

I am afraid you need to fix the other timestamps as well, no?

ehm.. why?
the other ones are displayed correctly, they're the same as MPi-EVA and
1679904000 = Mon Mar 27 2023 10:00:00 GMT+0200 (Central European Summer Time)
1679907600 = Mon Mar 27 2023 11:00:00 GMT+0200 (Central European Summer Time)
1679911200 = Mon Mar 27 2023 12:00:00 GMT+0200 (Central European Summer Time)
1679914800 = Mon Mar 27 2023 13:00:00 GMT+0200 (Central European Summer Time)
1679918400 = Mon Mar 27 2023 14:00:00 GMT+0200 (Central European Summer Time)
1679922000 = Mon Mar 27 2023 15:00:00 GMT+0200 (Central European Summer Time)
1679925600 = Mon Mar 27 2023 16:00:00 GMT+0200 (Central European Summer Time)
and they correspond to what's displayed on the main event page. I just used MPi-EVA as a template, and changed the first timestamp
1679902200 = Mon Mar 27 2023 09:30:00 GMT+0200 (Central European Summer Time)
because we'll start at that time.
what am I missing?

Ah, sorry, didn't see it rendered and just guessed from the code. 😬😞
It's good to go then.


bn_mul.h: require at least ARMv6 to enable the ARM DSP code

Description
Commit 16b1bd89326e "bn_mul.h: add ARM DSP optimized MULADDC code"
added some ARM DSP instructions that was assumed to always be available
when __ARM_FEATURE_DSP is defined to 1. Unfortunately it appears that
the ARMv5TE architecture (GCC flag -march=armv5te) supports the DSP
instructions, but only in Thumb mode and not in ARM mode, despite
defining __ARM_FEATURE_DSP in both cases.
This patch fixes the build issue by requiring at least ARMv6 in addition
to the DSP feature.
Status
READY
Requires Backporting
NO, this is a bug fix for the development branch only, introduced by PR #1618.
Steps to test or reproduce
Build mbedTLS with -march=armv5te -marm

Please can this be merged. I currently have to carry this patch in the Debian package because mbedTLS won't build on armel without it.

Unfortunately, the has been released in Mbed TLS 2.14. So this needs a changelog entry and a backport to Mbed TLS 2.16. I'll make those.

I made separate PRs for development and mbedtls-2.16 to facilitate testing: https://github.com/ARMmbed/mbedtls/pull/2777, https://github.com/ARMmbed/mbedtls/pull/2778. So this PR is now superseded.

I made separate PRs for development and mbedtls-2.16 to facilitate testing: https://github.com/ARMmbed/mbedtls/pull/2777, https://github.com/ARMmbed/mbedtls/pull/2778. So this PR is now superseded.

@jcowgill It's cheap for us to add a build to our CI if it uses tools that are already available in our CI environment, but more work to add a new tool. We have arm-none-eabi-gcc but not arm-linux-*. I added a build with -march=armv5te, but I can tweak that. Would you suggest different flags to try not to break Debian?

I think -march=armv5te matches Debian's armel port, so just using that option will be fine.

@jcowgill The fix to bn_mul.h has been merged to Mbed TLS's development branch, as well as to the mbedtls-2.16 LTS branch. Thank you for your patience and cooperation!


Support with only ADB

Would it run with only adb and not using USB at all. Is there any support for that?

Hello, yes, it is possible.
I think you need to root your phone. What are you trying to do?

I am trying to use it for testing purpose.

But you want to run the code from an app or directly from a terminal in the phone?
According to this, you can install the terminal and run it directly.
Still, I think you would need a USB in the beginning to record the instructions.

I've tried it, recording events from the terminal or via Tasker works fine.
Unfortunately, replaying doesnt work at all.

I have replayed it in the past through an app but I had to root my phone for it to work.


Test if container blob is accessible before mounting

related #16865
This PR adds an accessibility check before mounting container blobs.

Is this PR alive?

Is this PR alive?

We need this for 1.19.1

bump

I was unable to create a backport for 1.20. @KN4CK3R, please send one manually. :tea:
go run ./contrib/backport 22759
...  // fix git conflicts if any
go run ./contrib/backport --continue


Clipboard cache feature request

Hey, love this one as moved from PhraseExpress that is buggy and charges money. Would pay if no bugs though. Anywy, it had cool feature - pressing alt+ENTER opened my last items in clipboad in menu and with arrow down and enter I quickly got the item pasted.

Hi @e-stonia,
Thank you for your support. At the moment Beeftext will remain a tool focused on managing text snippet, so there will be no such thing as advanced clipboard management in the foreseeable future.
I guess you can find many clipboard managers out there. A quick google search led me to ArsClip, which I have not tested, but seem to be doing what you are looking for.


Please add a screenshot and spec requirements (minimum: FC version, Qt version etc....)

The FC version was specified in the .FCMacro file as  "FreeCAD >= v0.20" which what I had tested it with. Due to your 'issue' I tried some other versions and I cannot seem to make it work in versions in older than v0.19. I had to make a small change to make it work in v0.19 but that's covered now :)
Initially it was just a quick script for MisterMakerNL as I didn't quite understand what he wanted and just made something to have a starting point to iterate from.
I'll add a proper README.md to the github either today or tomorrow along with a screenshot as requested. Is there any reason in particular you need to know the Qt version? (it just uses PySide2 which seems to be Qt 5.12+)

Thanks so much for all your work. You experimentations will help propel more refinements in FreeCAD UI/UX for sure!:pray:

Is there any reason in particular you need to know the Qt version? (it just uses PySide2 which seems to be Qt 5.12+)

Indeed. There is work toward migrating FC to Qt6 (https://github.com/FreeCAD/FreeCAD/issues/6992). In conjunction,  certain Qt5 versions are problematic so knowing what Qt specs have been tested is helpful.


Real signal noise issue?

Is it rng.normal(size=trials, scale=np.sqrt(n0 / 2)) or rng.normal(size=trials, scale=np.sqrt(n0))?

For real signals, the noise variance is n0/2. There's probably a bug somewhere, then.


Long double tests fail on big-endian 64-bit architectures

The tests in test-complex involving rotdist_complexld fail on big-endian 64-bit architectures, for example s390x:
[...]
running test-complex
FFF
==============================================================================
Error: Complex number tests:2:basic operations on complex numbers passed by value(stubs).

File "/<<PKGBUILDDIR>>/_build/oUnit-Complex number tests-zandonai#00.log", line 36, characters 1-1:
Error: Complex number tests:2:basic operations on complex numbers passed by value(stubs) (in the log).

File "tests/test-complex/test_complex.ml", line 163, characters 1-1:
Error: Complex number tests:2:basic operations on complex numbers passed by value(stubs) (in the code).

rotdist
------------------------------------------------------------------------------
==============================================================================
Error: Complex number tests:1:basic operations on complex numbers (stubs).

File "/<<PKGBUILDDIR>>/_build/oUnit-Complex number tests-zandonai#00.log", line 28, characters 1-1:
Error: Complex number tests:1:basic operations on complex numbers (stubs) (in the log).

File "tests/test-complex/test_complex.ml", line 93, characters 1-1:
Error: Complex number tests:1:basic operations on complex numbers (stubs) (in the code).

rotdist
------------------------------------------------------------------------------
==============================================================================
Error: Complex number tests:0:basic operations on complex numbers (foreign).

File "/<<PKGBUILDDIR>>/_build/oUnit-Complex number tests-zandonai#00.log", line 20, characters 1-1:
Error: Complex number tests:0:basic operations on complex numbers (foreign) (in the log).

File "tests/test-complex/test_complex.ml", line 93, characters 1-1:
Error: Complex number tests:0:basic operations on complex numbers (foreign) (in the code).

rotdist
------------------------------------------------------------------------------
Ran: 3 tests in: 0.00 seconds.
FAILED: Cases: 3 Tried: 3 Errors: 0 Failures: 3 Skip:  0 Todo: 0 Timeouts: 0.

It turns out this is due to libm not being linked into the test library. This patch fixes that.

Thanks for tracking that down, @glondu.  I've submitted your patch as a PR in #656.


update activation list format to show additional activation details

Expected Behaviour
This is an enhancement/feature request. When listing activations using wsk the activation list is now more richly formatted and shows the activation date/time, status, cold/warm start etc. The aio cli output is the older activation list which only contains the activation ids and their corresponding function names.
Sample output from wsk:
Datetime            Activation ID                    Kind      Start Duration   Status  Entity
2019-10-24 07:38:18 e2f86469271745f3b86469271745f3ec nodejs:10 cold  52ms       success guest/textToSpeech:0.0.4
2019-10-24 06:30:59 8d2e11ea689244cdae11ea689234cd9f nodejs:10 warm  2ms        success guest/hello:0.0.1

Actual Behaviour
activations
f652a5f5a7d14e0c92a5f5a7d16e0cf1 imageToText
76dfe44d904149369fe44d9041d93651 hello

Reproduce Scenario (including but not limited to)
Steps to Reproduce
Platform and Version
Sample Code that illustrates the problem
Logs taken while reproducing problem

I believe this has been implemented in https://github.com/adobe/aio-cli-plugin-runtime/commit/7c11e7ffee955156d0c4637c7eceaf9c63489336#diff-22b60df1df1cb6e7c1cccf8cb357aa61
.. and should be in 1.1.0 of the Runtime plugin. This version of the Runtime plugin should be in the aio-cli v2.1.0. Can you verify with --version what version you have? Thanks!

Hmm. I see "@adobe/aio-cli": "^2.1.0". I’ll check further.

> aio version
@adobe/aio-cli/2.1.1 darwin-x64 node-v10.16.3

but i'm not seeing the --full flag:
> aio runtime:activation:list --help
Lists all the Activations

USAGE
  $ aio runtime:activation:list [ACTIVATIONID]

OPTIONS
  -i, --insecure           bypass certificate check
  -l, --limit=limit        only return LIMIT number of activations from the collection with a maximum LIMIT of 200 activations (default
                           30)
  -s, --skip=skip          exclude the first SKIP number of activations from the result
  -u, --auth=auth          whisk auth
  -v, --verbose            Verbose output
  --apihost=apihost        whisk API host
  --apiversion=apiversion  whisk API version
  --cert=cert              client cert
  --debug=debug            Debug level output
  --help                   Show help
  --json                   output raw json
  --key=key                client key
  --since=since            return activations with timestamps later than SINCE; measured in milliseconds since Th, 01, Jan 1970
  --upto=upto              return activations with timestamps earlier than UPTO; measured in milliseconds since Th, 01, Jan 1970
  --version                Show version

In a separate aio build, I do see --full but unable to use it:
> aio runtime:activation:list --full
 ›   Error: failed to list the activations: GET https://.../api/v1/namespaces/_/activations?name=--full Returned
 ›   HTTP 400 (Bad Request) --> "The query parameter 'name' was malformed:
 ›   Parameter may be a 'simple' name or 'package-name/simple' name: --full"

@shazron the --full flag emits the activation list in json and not as a summary table (shown in my first comment). In any case, the correct place for this feature request is the plugin repo and I can open a corresponding issue there.

@shazron you are correct, if I run directly with aio-cli-plugin-runtime> ./bin/run runtime:activation:list I am getting the updated table format.


Load balancing strategy based on active connections count

According to router/README.md the Flynn router "acts as a standard reverse proxy with random load balancing". In some scenarios this is suboptimal. For example, assume we have several processes running which serve persistent Websocket connections. The load spikes, we add some new hosts to the cluster, and scale additional processes on them. Ideally, the routers should point new connections to the new processes, until their load (number of connections) reaches the same level as the old ones. A purely random strategy cannot achieve that.
It would be great if each router maintains a table with the number of active connections to each process, and uses that table to decide which process should handle a new connection. Note that such a table does not need to be cluster-global, it's enough to have separate tables per router (which is a much easier task).

FYI see #966 for a discussion on approaches (and difficulties) for the router keeping track of active connections.

Flynn is unmaintained and our infrastructure will shut down on June 1, 2021. See the README for details.


[CVP-1897] Generate mock prow artifacts when running external Operator Bundle Tests

When operator bundle deployment tests are run through DPTP, two files are generated that the upstream optional-operators-subscribe role does not generate.
We will need to generate these files as a part of the optional-operators-subscribe role.
The finished.json file should contain the following fields:
timestamp: use the already-existing start_time field
passed: boolean true or false
result: Omit. The result field has been deprecated in favor of passed
revision: Omit. The revision field is deprecated
The build-log.txt file is the stdout of the optional-operators-subscribe shell script. We should collect the stdout and save it to the file.
Both files should be saved inside the ARTIFACT_DIR for the role.

lgtm

/retest

@14rcole bump

@14rcole bump

lgtm

LGTM