Using component with typescript (Ionic) ?

Hello, I am just starting to get into react/typescript etc. so I just thought to ask wether this a problem only on my end on with this component.
When using this component in Ionic I encountered the message:
'ProgressLabel' cannot be used as a JSX component.
Now after some reading I fixed it by changing the following in the "index.d.ts"
export default class ProgressLabel extends Component<ProgressLabelProps,void> {}
to
export default class ProgressLabel extends Component<ProgressLabelProps,object> {}
Not sure why this works as I basically just started trying things out, so would also be nice to get a little explanation if anyone knows...

updated in 3.1.7


Push Notifications doesn't sent on iOS 10+

Hello,
Expected Behaviour
Notifications sent on every mobiles devices on every iOS.
Actual Behaviour
Notifications are just send on mobiles devices using iOS < 10 (9 - 8 ect)
When users use iOS 10 or + notifications are create and (I guess) sent because the code is 201 - CREATED.
Reproduce Scenario (including but not limited to)
Just push notifications from mobile app or website and not receive notificaiton on devices using iOS 10 or +
Steps to Reproduce
Just push notifications from mobile app or website and not receive notificaiton on devices using iOS 10 or +
Platform and Version (eg. Android 5.0 or iOS 9.2.1)
iOS 10 or + => doesn't work
iOS 9 - 8 => it's work
(Android) What device vendor (e.g. Samsung, HTC, Sony...)
I don't test on android devices
Cordova CLI version and cordova platform version
cordova --version                                    : 6.4.0
cordova platform version android           :

Installed platforms:
android 5.2.2
ios 4.2.1
Available platforms:
amazon-fireos ~3.6.3 (deprecated)
blackberry10 ~3.8.0
browser ~4.1.0
firefoxos ~3.6.3
osx ~4.0.1
webos ~3.7.0
Plugin version
phonegap-plugin-push 1.6.0 "PushPlugin"
Sample Push Data Payload
var req = {
method: 'POST',
url: 'https://api.ionic.io/push/notifications',
headers: {
'Content-Type': 'application/json',
'Authorization': 'Bearer *******************************'
},
data: {
"tokens": [token],//[token],//post.people.socialtoken,
"profile":"",
"notification":
{
"message": msg,"badge": 1,
"ios": {"message": msg,"badge": 1},
//"ios": {"message": msg,"badge": 1,"payload": {"link": link,"where":where}},
"android": {"message": msg,"badge": 1,"payload": {"link": link,"where":where}}
}
}
};
// Make the API call
$http(req).success(function(resp){
console.log(resp);
}).error(function(error){
// Handle error
console.log(error);
});
Sample Code that illustrates the problem
var req = {
method: 'POST',
url: 'https://api.ionic.io/push/notifications',
headers: {
'Content-Type': 'application/json',
'Authorization': 'Bearer *******************************'
},
data: {
"tokens": [token],//[token],//post.people.socialtoken,
"profile":"",
"notification":
{
"message": msg,"badge": 1,
"ios": {"message": msg,"badge": 1},
//"ios": {"message": msg,"badge": 1,"payload": {"link": link,"where":where}},
"android": {"message": msg,"badge": 1,"payload": {"link": link,"where":where}}
}
}
};
// Make the API call
$http(req).success(function(resp){
console.log(resp);
}).error(function(error){
// Handle error
console.log(error);
});
Logs taken while reproducing problem
no logs error
So, first question, do you have any ideas to fix this problem?
Then, how can I update my phonegap plugin?
Thanks

You are using the 1.6.0 version of the plugin which was created long before iOS 10 was announced and released, you should update to latest version (1.9.1) as some changes where made to make push work on iOS 10.
As 1.9.1 requires cordova-ios 4.3.0, cordova-android 6.0.0 and cordova CLI 6.4.0 you should update all of them too.
If you can't update them, you can test with latest version of the plugin compatible with your platforms and CLI, 1.8.4

Hi,
Thank you very much,
Can you tell me how can I update phonegap-plugin-push?
Thanks :)
Amaury Leproux
Développement Web - Développement Mobile - Référencement - Community Management
Site web : www.aleproux.com http://www.aleproux.com/

On 5 Dec 2016, at 14:57, jcesarmobile<EMAIL_ADDRESS>wrote:
You are using the 1.6.0 version of the plugin which was created long before iOS 10 was announced and released, you should update to latest version (1.9.1) as some changes where made to make push work on iOS 10.
As 1.9.1 requires cordova-ios 4.3.0, cordova-android 6.0.0 and cordova CLI 6.4.0 you should update all of them too.
If you can't update them, you can test with latest version of the plugin compatible with your platforms and CLI, 1.8.4
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/phonegap/phonegap-plugin-push/issues/1435#issuecomment-264874820, or mute the thread https://github.com/notifications/unsubscribe-auth/AOWVhb0eIgbMi0U1E0MifsrtX55EaGeZks5rFCY8gaJpZM4LEUJ-.

A possible list of steps to upgrade to 1.8.4 would be:
cordova plugin rm phonegap-plugin-push
cordova plugin add --save<EMAIL_ADDRESS>--variable SENDER_ID="XXXXXXX"

Thanks @fredgalvao, I've just tied that but I got this error message :
Uninstalling phonegap-plugin-push from android
Error: ENOENT: no such file or directory, open '/Applications/MAMP/htdocs/usmileapp-v2/platforms/android/assets/www/cordova_plugins.js'

Thanks I could update phonegap-plugin-push, now I will test this new version.

Hi Guys, me again :/
When I try to install phonegap-plugin-push 1.9.1 (cordova plugin add --save<EMAIL_ADDRESS>--variable SENDER_ID="***********")
I get this error message:
Failed to install 'phonegap-plugin-push':Error: pod: Command failed with exit code 1 Error output:
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
100 1085k    0 1085k    0     0  2754k      0 --:--:-- --:--:-- --:--:-- 2950k
dyld: lazy symbol binding failed: Symbol not found: _ERR_remove_thread_state
Referenced from: /usr/local/lib/libcurl.4.dylib
Expected in: flat namespace
dyld: Symbol not found: _ERR_remove_thread_state
Referenced from: /usr/local/lib/libcurl.4.dylib
Expected in: flat namespace
at ChildProcess.whenDone (/Applications/MAMP/htdocs/usmileapp-v2/platforms/ios/cordova/node_modules/cordova-common/src/superspawn.js:169:23)
at emitTwo (events.js:87:13)
at ChildProcess.emit (events.js:172:7)
at maybeClose (internal/child_process.js:829:16)
at Socket. (internal/child_process.js:319:11)
at emitOne (events.js:77:13)
at Socket.emit (events.js:169:7)
at Pipe._onclose (net.js:486:12)
Error: pod: Command failed with exit code 1 Error output:
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
100 1085k    0 1085k    0     0  2754k      0 --:--:-- --:--:-- --:--:-- 2950k
dyld: lazy symbol binding failed: Symbol not found: _ERR_remove_thread_state
Referenced from: /usr/local/lib/libcurl.4.dylib
Expected in: flat namespace
dyld: Symbol not found: _ERR_remove_thread_state
Referenced from: /usr/local/lib/libcurl.4.dylib
Expected in: flat namespace
i alreday try to do : remove this plugin -> pod repo update -> reinstall this plugin but that's not work.
Do you have any ideas please?
Thanks

Did you update your platforms to the 1.9.x requirements stated here? AFAIK you had

android 5.2.2
ios 4.2.1

and we need

android 6.0.0
ios 4.3.0

Specifically, pod suport is available mainly on cordova-ios 4.3.0, and also you might want to try pod repo update when the plugin is installed, instead of doing it right after the plugin was removed.

When i run cordova version platform ios :
Installed platforms:
android 6.0.0
ios 4.3.1
and cordova -v : 6.4.0

I would make sure your certificates and everything is working on. I just used pusher to test this found here https://github.com/noodlewerk/NWPusher From there I realized something else was not setup properly but that was what initially led me to fixing a problem I was having with another library (mixpanel integration with push notifications)

Hi @codeHatcher and thanks for the reply.
So you think I have a wrong setup?
On iOS 9 and 8 and before it's working properly.

I've always the same error message when I try to install phonegap version 1.9.1 :
Failed to install 'phonegap-plugin-push':Error: pod: Command failed with exit code 1 Error output:
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
100 1085k    0 1085k    0     0  2103k      0 --:--:-- --:--:-- --:--:-- 2167k
dyld: lazy symbol binding failed: Symbol not found: _ERR_remove_thread_state
Referenced from: /usr/local/lib/libcurl.4.dylib
Expected in: flat namespace
dyld: Symbol not found: _ERR_remove_thread_state
Referenced from: /usr/local/lib/libcurl.4.dylib
Expected in: flat namespace
at ChildProcess.whenDone (/Applications/MAMP/htdocs/usmileapp-v2/platforms/ios/cordova/node_modules/cordova-common/src/superspawn.js:169:23)
at emitTwo (events.js:87:13)
at ChildProcess.emit (events.js:172:7)
at maybeClose (internal/child_process.js:829:16)
at Socket. (internal/child_process.js:319:11)
at emitOne (events.js:77:13)
at Socket.emit (events.js:169:7)
at Pipe._onclose (net.js:486:12)
:(

Doesn't work for me too in iOS 10.1.1, but works great in iOS 9.

@amauryleproux That smells like a node/cordova/pod bug. Can you try creating a new project and adding the plugin from the start, following the steps on the docs here?

Not able to receive notification using GCM in IOS [works in Android]
Cordova:  6.4.0
Cordova IOS: ios 4.3.1
phonegap-plugin-push 1.9.2 "PushPlugin"
Device: Iphone 6S Plus
IOS version: 10.2
I am able to get notification using NWPusher APN but when I try using GCM it is not working
Logs taken while reproducing problem
2016-12-17 21:38:53.998871 Chordpedia[1815:502181] Apache Cordova native platform version 4.3.1 is starting.
2016-12-17 21:38:53.999478 Chordpedia[1815:502181] Multi-tasking -> Device: YES, App: YES
2016-12-17 21:38:54.039921 Chordpedia[1815:502181] Using UIWebView
2016-12-17 21:38:54.041211 Chordpedia[1815:502181] [CDVTimer][handleopenurl] 0.065982ms
2016-12-17 21:38:54.042379 Chordpedia[1815:502181] Unlimited access to network resources
2016-12-17 21:38:54.042445 Chordpedia[1815:502181] [CDVTimer][intentandnavigationfilter] 1.175046ms
2016-12-17 21:38:54.042536 Chordpedia[1815:502181] [CDVTimer][gesturehandler] 0.050008ms
2016-12-17 21:38:54.059073 Chordpedia[1815:502181] [CDVTimer][splashscreen] 16.489983ms
2016-12-17 21:38:54.065705 Chordpedia[1815:502181] [CDVTimer][statusbar] 6.518960ms
2016-12-17 21:38:54.079125 Chordpedia[1815:502181] [MC] System group container for systemgroup.com.apple.configurationprofiles path is /private/var/containers/Shared/SystemGroup/systemgroup.com.apple.configurationprofiles
2016-12-17 21:38:54.081038 Chordpedia[1815:502181] [MC] Filtering mail sheet accounts for bundle ID: com.dez.chordpedia, source account management: 1
2016-12-17 21:38:54.083101 Chordpedia[1815:502181] [MC] Result: YES
2016-12-17 21:38:54.083255 Chordpedia[1815:502181] [MC] Filtering mail sheet accounts for bundle ID: com.dez.chordpedia, source account management: 1
2016-12-17 21:38:54.083721 Chordpedia[1815:502181] [MC] Result: YES
2016-12-17 21:38:54.096186 Chordpedia[1815:502181] [CDVTimer][socialsharing] 30.387044ms
2016-12-17 21:38:54.097318 Chordpedia[1815:502181] [CDVTimer][localnotification] 1.031995ms
2016-12-17 21:38:54.097384 Chordpedia[1815:502181] [CDVTimer][localnotification] 0.010014ms
2016-12-17 21:38:54.097424 Chordpedia[1815:502181] [CDVTimer][TotalPluginStartup] 56.306005ms
2016-12-17 21:38:54.104624 Chordpedia[1815:502181] createNotificationChecker
2016-12-17 21:38:54.104669 Chordpedia[1815:502181] not coldstart
2016-12-17 21:38:54.105830 Chordpedia[1815:502181] active
2016-12-17 21:38:54.106006 Chordpedia[1815:502181] PushPlugin skip clear badge
2016-12-17 21:38:54.211535 Chordpedia[1815:502181] [MC] Reading from public effective user settings.
2016-12-17 21:38:54.296198 Chordpedia[1815:502181] Resetting plugins due to page load.
2016-12-17 21:38:54.565405 Chordpedia[1815:502181] Finished load of: file:///var/containers/Bundle/Application/BFE7AC84-5839-495A-BD0C-609AC258C34A/Chordpedia.app/www/index.html
2016-12-17 21:38:54.735060 Chordpedia[1815:502210] Push Plugin register called
2016-12-17 21:38:54.735146 Chordpedia[1815:502210] PushPlugin.register: setting badge to false
2016-12-17 21:38:54.735165 Chordpedia[1815:502210] PushPlugin.register: clear badge is set to 0
2016-12-17 21:38:54.735177 Chordpedia[1815:502210] PushPlugin.register: better button setup
2016-12-17 21:38:54.735640 Chordpedia[1815:502210] GCM Sender ID XXXXXX
2016-12-17 21:38:54.735732 Chordpedia[1815:502210] Using GCM Notification
2016-12-17 21:38:54.735790 Chordpedia[1815:502210] Using GCM Sandbox
2016-12-17 21:38:54.742486 Chordpedia[1815:502181] Push Plugin register success:
2016-12-17 21:38:54.765: GCM | GCM library version 1.1.4
2016-12-17 21:38:54.769: GCM | Invalid key in checkin plist: GMSInstanceIDDeviceDataVersion
2016-12-17 21:38:54.771384 Chordpedia[1815:502181] GCM Registration Token: XXXXXX

Same here. Do work on Android and iOS <= 9.
I tried the NWPusher @codeHatcher suggested. I'm not able neither with that tool to send a push notification to one of my iOS10 devices. Got the error:
Connecting to APN...  (my.package sandbox)
Connected  (my.package sandbox)
Pushing..
Notification error: APN invalid token

The msg says invalid token but it works with my other iOS 9 device so I quite not understand.
I use the default test payload of the tools, also tried to change it, doesn't helped:
{"aps":{"alert":"Testing.. (2)","badge":1,"sound":"default"}}

Closing, inactivity. Please comment/re-open if you have more details.


cinder-cfg.py generating invalid config

We hit two issues with the cinder-cfg.py generated config:

the serviceUser is meant to be a string rather than a list.

the cinderVolumes section is invalid.

@karelyatin noticed that the problem with the the cinderVolumes section was incorrect networkAttachments nesting (under cinderVolumes rather than under tripleo-ceph).
After correcting these issues, Cinder seems to deploy but the cinder-volume pod is restarting.

I have fixed those 2 issues in PR#139 and I'm wondering if the restart is related to the missing extraVolumes section.
One of the patches of the PR fixes the extraVolumes sample not getting rendered for RBD backends.


⚠ Bofrost.de has degraded performance

In 6068f43, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1196 ms

Resolved: Bofrost.de performance has improved in 04784b4 after 6 minutes.


Add AffineTransformedDistribution

Issue #, if available: fixes #1050
Description of changes: adds an AffineTransformedDistribution subtype of TransformedDistribution, which allows computing other things like mean and variance (and potentially CRPS and more). Modify distribution output classes to use this when given loc and scale, and expand tests to cover mean and variance. Fix bugs in some distributions along the way (Dirichlet, DirichletMultinomial, MixtureDistribution).
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thanks Lorenzo! Overall seems ok to me.
One general comment that does not apply directly to this pr but touches the concept of transformed distributions is the hard coded restriction we have for affine transformations. We can always default to this but shouldn't we have the option to select or use a custom one? I have in mind a general normalizing flow for example. It would be great if we were able to define the transformation when we define the DistributionOutput. For example, assuming a Gaussian, we can go from this:
distr_out=GaussianOutput()  # implicit AffineTransformedDistribution

to this:
distr_out=GaussianOutput(transform=MyFlow).

Of course any transformation should have a predefined behaviour/api that matches and we can learn its parameters as we learn the parameters of any other projection layer. I am not sure what is the approach that @rshyamsundar followed here for NKF and if this matches...

@benidis that's a valid point, I think we should work on something to allow models to output "more complex" distributions (unless someone has already worked something out there), but maybe wrapping is not the best way to do it. Also, in your example
distr_out=GaussianOutput()  # implicit AffineTransformedDistribution

I think there is nothing implicit about affine transformations here: when affine transformations enter the game is when calling
distr_out.distribution(...)


[Compiler] Methods in object literals

Version
3.0.0-beta.15
Reproduction link
https://vue-next-template-explorer.netlify.app/#%7B%22src%22%3A%22%3Cdiv%20v-x%3D%5C%22%7B%20a%3A%201%2C%20b()%20%7B%20%7D%7D%5C%22%3E%3C%2Fdiv%3E%22%2C%22options%22%3A%7B%22mode%22%3A%22module%22%2C%22prefixIdentifiers%22%3Afalse%2C%22optimizeBindings%22%3Afalse%2C%22hoistStatic%22%3Afalse%2C%22cacheHandlers%22%3Afalse%2C%22scopeId%22%3Anull%7D%7D
Steps to reproduce
The compiler produces invalid content if you create an object literal with the method shorthand syntax, such as this:

What is expected?
v-x compiles to the expression:
{ a: 1, b() { _ctx.hello() } }
What is actually happening?
Compiles to the following, which is invalid:
{ a: 1, _ctx.b() { _ctx.hello() } }

Wow less than 30 min. from open issue to merged fix. You're amazing guys! 🥇


Multiverse - Error (says not up to date)

When I add Multiverse and multiverse inventories I get these errors
I am not sure what else to do
http://pastebin.com/RRtKJ8g8

Update Multiverse from here: http://ci.onarandombox.com/view/Multiverse/
Next time you post an error like this, could you add versions of everything to the post. Thank you :)

They are the latest versions ... and the config shows that too

As I can see in the log your Multiverse plugins are most definitely not the latest versions that are available on the site @TWSSYesterday linked you to. You need to use the dev builds for 1.9. Also, Multiverse-Inventories is no longer supported. Please check out PWI which supports importing your MV-inventories files.


Fixes and updates for the Greek language

I have translated some UI text that hadn’t been translated by @Stelios3g. And I have also changed some translated entries to look and sound more natural for general uses (eg ‘Recent posts’ was translated as ‘Latest Announcements’ before). Finally, I have added ‘RSS’ next to ‘Feed’, because 1) there is no translation (or something that sounds natural) in Greek I’m afraid, 2) the term ‘RSS Feed’ is widely used in Greek websites.

@Stelios3g care to weigh in?
As far as adding RSS, the feed is technically Atom and not RSS. People commonly interchange them but they're two different specs which is why I went with "Feed".

Hi, Michael.
I am Greek myself and I can assure you that the translation is correct.
Please feel free to keep 'Feed' in English, because there is no term in Greek that could describe such thing and isn't related to 'food/eating'.
Many thanks.


Fix Amazon Polly with non English voices

Description:
Fix Amazon Polly TTS service with non English voices.
Related issue (if applicable): fixes #8377
Checklist:
If the code does not interact with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass

The Travis Lint build failed due to Timeout. Can someone restart it ?

Thanks!


Performance issue

$ ./bm/bin/generate-bm-file > bm-file
$ ls -larth bm-file
-rw-r--r-- 1 user user 9.6M Jan 16 13:19 bm-file
$ cat cp.ch
bm-file f<; bm-file-copy swap; f>;
$ time ./target/release/cosh cp.ch

real    0m0.343s
user    0m0.167s
sys     0m0.150s
$ cat cp.pl
#!/usr/bin/perl

use warnings;
use strict;

open my $fh, '<', 'bm-file' or die $!;
open my $fh2, '>', 'bm-file-copy' or die $!;
while (my $line = <$fh>) {
    print $fh2 $line;
}
close $fh;
close $fh2;

1;
$ time perl cp.pl

real    0m0.044s
user    0m0.027s
sys     0m0.008s
$

Try to make this faster.

Some other possible performance improvements:

avoid stack push/pop operations where possible, by dealing with stack element pointers instead; and
avoid get_constant value generation where possible, by using get_constant_int or similar functions.

Buffered output has mostly fixed this problem (56ms vs. 27ms for Perl, when the time taken is averaged over 100 runs).


ci(release): Automatically build release binary on tag push

(waiting for someone to approve macOS binaries)

(waiting for someone to approve macOS binaries)


Why trigger a page_update when an event handler is missing?

According to this comment, JustPy triggers a "page_update" event if an event handler returns None.
But as I noticed right now, it also updates the page if there is no handler for an event: https://github.com/elimintz/justpy/blob/42275e9c6e00373f09affd7d781a278383171807/justpy/justpy.py#L341
This might happen for e.g. QSlider, which triggers "change" and "input" events. So you get page updates even though you implement a change event handler returning False.
What is the reason behind this? Couldn't we remove the page updates in this case?
In this specific case it helps to create the QSlider with disable_input_event=True.

This is the code I'm experimenting with. Omitting one of the event handlers causes page updates after every slider change.
import justpy as jp

def handle_change(sender, msg):
    print('CHANGE', sender, msg, flush=True)
    return False

def handle_input(sender, msg):
    print('INPUT', sender, msg, flush=True)
    return False

def input_test(request):
    wp = jp.QuasarPage()
    jp.QSlider(min=0, max=10, step=1, a=wp, change=handle_change, input=handle_input)
    return wp

jp.justpy(input_test)

One option would be to not update page when event_handler returns None. But that would require an extra variable to signal when should the page be updated? Guess the best thing to do in current setup would be provide an event handler and return a value.
Or one can add an extra qualifier to if event_result is None: to restrict to case only if event_function is defined.

Sure, you can avoid individual page updates by implementing a handler which returns a non-None value. But you need to be aware of every event that can be handled and add those empty handlers. That's why I was wondering why we need the current default behavior in the first place. If there is any event you didn't think about, why should JustPy send a whole page update message?

My initial thinking was to keep event handlers as simple as possible and usually you would like to update the page after an event. Since if there is no return statement, None is returned, that is the value that updates the page.
This design keeps the event handlers more concise but it does cause the problems as described above.

I just don't see why Python should trigger a page update if it didn't subscribe to the JavaScript event in the first place. The information that something happened does not reach the user code, so the event should be no reason for an update.
These updates are problematic for our use cases where we interact with robots over the internet. Sending complex user interfaces again and again is pretty costly, especially for events like key presses or slider movements. That's why I was hunting such implicit updates.

When an input or change type event happens in the browser, the default is for the to be sent to the backend even if the event does not have an event handler because otherwise the value on the server would not be in sync with the value in the browser. Anything the inherits from the Input component has the before event which takes care of that. So basically, Input components come with an event handler that the user does not specify.
Please take a look at https://github.com/elimintz/justpy/blob/master/justpy/htmlcomponents.py#L787
So in some implicit (to the user) way the information reaches the backend.
Right after the Input definition in the code there is the  InputChangeOnly definition. Perhaps we need to extend this concept? Would that solve your problem?
Alternatively, we could change https://github.com/elimintz/justpy/blob/master/justpy/justpy.py#L307 so that the default would be that if there is only a before event and not a user specified handler, the page is not updated. The potential problem with this is that a user defined before event or some background task may cause side effects that do require the page to be updated.

Ok, I see. My tendency was indeed to change this line
https://github.com/elimintz/justpy/blob/42275e9c6e00373f09affd7d781a278383171807/justpy/justpy.py#L341
to = False, i.e. treating a missing event handler as if there was one which returned False.
I wasn't aware of the before- (and after-?) events. That might be something to consider, but I don't know the code well enough to foresee its consequences. Still, if the user didn't subscribe to any event, e.g. just places a slider on a blank page, I wouldn't expect any page updates when moving it. And I'm not sure if possible side effects should drive the default behavior.
But if I had to decide at this point in time, I would tend to leave it as it is, to avoid potentially breaking existing code. If performance is critical, one would need to know about these page updates and how to avoid them. Or use NiceGUI which takes care of those lower-level details. 😉


Supply historical displayVersions

Why
Supply displayVersions for historical modules
What changed
These modules don't have displayVersions. Hardcode them.
NB: Not all module id versions line up with what they actually ship:

Test plan
N/A, this is just informative.
Rollout
Describe any procedures or requirements needed to roll this out safely (or check the box below)

[ ] This is fully backward and forward compatible

NB: Not all module id versions line up with what they actually ship:
that's due to the upgrade map: https://github.com/replit/nixmodules/blob/main/pkgs/upgrade-map/default.nix#L13

Closing this since it's included in the next PR

I didn't realize we were stacking PRs. I'm here for it.


Prepare for 1.7.1.RELEASE

As part of the 1.7.1.RELEASE, we would have to prepare the following.

[x] Bump SCDF core to 1.7.2.RELEASE

Created https://github.com/spring-cloud/spring-cloud-dataflow-server-kubernetes/issues/360 for Helm repo update.


Change Curl\Util for return response from cURL request.

Simply rework Curl\Util::execute() method. So now this method returns HTTP response from the request.
Moreover, because this method returns nothing - these changes do not break anything.

Thanks


Delayed refresh/reload of web page on startup

When I set "open on device boot" and default home app too, two loading happens at startup. It is enough time to the second instance to load the (homeassinstant) web page successfully, but sometimes I have issues when two instances are loaded (eg. motion sensor doesn't work).
When I disable "open on device boot", and tablet is restarted, the home screen is loaded (too quickly), but WIFI is still not connected (yet), so only "web page not available" ("net:: ERR_INTERNET_DISCONNECTED") happens.
Maybe a configurable startup delay would be great, or checking "internet_disconnected" followed by automatic page reload may solve this problem.
If I not set default home app to WallPanel (but OneUI), just "open on device boot", it works, but most updates cause not loading of the default home app, but asks for choosing one of them (and the page will not be loaded until user input). (Yes, I can disable auto update of applications for a workaround.)

I don't think you need to use both open on device boot and home screen, if the app is the home screen it will also load when the device restarts.   I think we have another issue some place about handling errors with WiFi disconnect.   The app does not know if you set it as the home screen, so I recommend not setting restart on boot.
You can add your issue with wifi disconnect to this ticket https://github.com/thanksmister/wallpanel-android/issues/265, that was a bug already filed and seems to fit your issue.   Basically we want to try to handle wifi disconnect issues and reload the page for the user.

I have added a way for the page to detect if there is a network disconnect and reload.  It can do this also for page load errors.  Please try with version https://github.com/thanksmister/wallpanel-android/releases/tag/v<IP_ADDRESS>.


Fix MONAI-ITK orientation. Improve Writer docstrings.

Description
Removed my temp fix for https://github.com/Project-MONAI/MONAI/issues/6985 as it has been fixed.

Related Issue

Type of Change

[ ] 📚 Examples / docs / tutorials / dependencies update
[ ] 🔧 Bug fix (non-breaking change which fixes an issue)
[x] 🥂 Improvement (non-breaking change which improves an existing feature)
[ ] 🚀 New feature (non-breaking change which adds functionality)
[ ] 💥 Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🔐 Security fix

Checklist

[ ] I've read the CODE_OF_CONDUCT.md document.
[ ] I've read the CONTRIBUTING.md guide.
[ ] I've updated the code style using make codestyle.
[ ] I've written tests for all new methods and classes that I created.
[ ] I've written the docstring in Google format for all the methods and classes that I used.

@ibro45 We should also fix the monai version in poetry. Otherwise this fix doesn't work right?

Right now, we have this,
https://github.com/project-lighter/lighter/blob/009e7da49c6ad9dacfd5aa1e795ca2913d0c7f23/pyproject.toml#L54
It will pull the latest one if available, but it's not necessary that it picks up the version with this fix.

Cool will do it thanks

Thanks Suraj!


Development

@xTavi Selection Page is done but I'm not sure about it's responsiveness as of yet. I can put off working on the profile page and work on the responsiveness of that page today.

@Chris-Mugumwa choose whatever you feel comfortable with! There is no hurry ☺


Running fable with -w gives file is being used exception

Description
Running fable -w run the first time. Subsequent times fail with file in use by another process exception
Repro steps
Run fable -w
Expected behavior
Files are compiled and webpack-dev-server runs
Actual behavior
u:\Work\PlayGround\Fable\CreatingVSCodePlugin\test2>fable -w
Start compilation...
Compiled Fable.Helpers.React.fs at 7:36:31 PM
Compiled models.fs at 7:36:31 PM
Compiled reactTest.fsx at 7:36:31 PM
Compiled main.fsx at 7:36:31 PM
Watching u:\Work\PlayGround\Fable\CreatingVSCodePlugin\test2\src
Cannot read project options: The process cannot access the file 'u:\Work\PlayGround\Fable\CreatingVSCodePlugin\test2\src\main.fsx' because it is being used by another process.
Compiled main.fsx at 7:38:01 PM
Cannot read project options: The process cannot access the file 'u:\Work\PlayGround\Fable\CreatingVSCodePlugin\test2\src\main.fsx' because it is being used by another process.
Cannot read project options: The process cannot access the file 'u:\Work\PlayGround\Fable\CreatingVSCodePlugin\test2\src\main.fsx' because it is being used by another process.

Known workarounds
Run fable manually when there is a change
Related information

Operating system: Window 10
Branch: Fable 0.2.14
.NET Runtime, CoreCLR or Mono Version
Performance information, links to performance testing scripts

Thanks for the report. Can you please post the fableconfig.json you're using? Also, if you have the copy in Github or somewhere public a link would be very helpful to reproduce the issue. Cheers!

Hi,
I'm migrating an application from elm to f# so cannot post it online. One observation is that it affects only the projFile. When I edit any other file, it compiles just fine. It is only the main.fsx file that gives that error.
fableconfig.json below
{ "module": "commonjs",
  "sourceMaps": true,
  "projFile": "./src/main.fsx",
  "outDir": "build",
  "scripts":{
  },
  "targets":{
    "watch":{
      "scripts":{
        "postbuild": "webpack-dev-server --content-base public/"
      }
    }
  }
}

This is very helpful, thank you! Yes, I didn't test the --watch option when modifying the the .fsproj file (or the main .fsx file in your case) so probably I didn't get it quite right. I'll fix that. For the moment, you can try using an empty main.fsx that's only loading the other files so you don't need to change it that much. Sorry for the inconvenience!

No problem. main.fsx is indeed loading other components and at such rarely modified.

I've tried to reproduce the error by creating a test script:
// Test1.fsx
printfn "Hello from Test1"

// Test2.fsx
printfn "Hello from Test2"

// Test.fsx
#load "Test1.fsx"
#load "Test2.fsx"

Then I run: fable Test.fsx -w but I could modify without problems any file (including the "main" script, Test.fsx) both in Mac and Windows :/
If you can isolate a minimal project where the problem can be reproduced it will be really helpful to find out the cause. You can also try running the --watch option without the webpack server to check if this is what's blocking the file.
Cheers!

Actually, I was running fable -w  without webpack. I thought that was the case. Will look at a minimal project. Also, watch does not seem to be working with fable -w on the new .fsproj version. Always have to use just fable

@irium's fix has been applied to v0.3.15. @ritcoder, can you please check if this fixed the issue for you? Thanks in advance!

Worked fine with the fsproj. Thanks.

Slight problem. When the code is recompiled, can it recompile all files that depend on it as well?
I had what I thought was a bug. It turned out not to be. I updated a file (SemanticUi.fs) and got an error in TopPanel.fs (blah blah is not a function). Code worked after editing and saving TopPanel.fs (just added a space and it recompiled). The error was because that file had to be recompiled since I had changed the structure of the previous file.
Compile on save is working fine so identifying dependents and recompiling them could be a good addition.

Hmmm, this is going to be complicated because the F# compiler doesn't give you a file dependency graph (or at least I haven't seen it), so I'd have to go through all the files to check if there are references to the modified one and then probably watch compilation won't be that fast anymore.
I'll have a look. At least you have file order in F# so you only have to look at the files coming after the modified one.

There's an event that's fired that lets you know to re-check dependants.

On 5 Jun 2016, at 08:57, Alfonso Garcia-Caro<EMAIL_ADDRESS>wrote:
Hmmm, this is going to be complicated because the F# compiler doesn't give you a file dependency graph (or at least I haven't seen it), so I'd have to go through all the files to check if there are references to the modified one and then probably watch compilation won't be that fast anymore.
I'll have a look. At least you have file order in F# so you only have to look at the files coming after the modified one.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

In the output js files, there are require statements that points to project files. I'm not sure how they are determined during compilation but can't that idea be used to build some kind of dependency graph during the first compilation? If it is possible, then watch compilation will lookup the graph to determine the dependents and recompile them - updating the graph in the process.

Good one! Actually I was thinking of something similar after writing the comment, it should be possible to create a simple dependency graph after the first compilation. I'll work on that.
@7sharp9, do you happen to know the name of the event? Is it one of the events raised by the FSharpChecker type?

Yeah that's right, I'll let you know when I'm next using my computer, currently on phone.

On 5 Jun 2016, at 09:46, Alfonso Garcia-Caro<EMAIL_ADDRESS>wrote:
Good one! Actually I was thinking of something similar after writing the comment, it should be possible to create a simple dependency graph after the first compilation. I'll work on that.
@7sharp9, do you happen to know the name of the event? Is it one of the events raised by the FSharpChecker type?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Had an experience where one of my files had an error and hence first compilation failed. When the file was fixed, got some weird error: Fable.Helpers.React.div is inlined but is not reachable. If it belongs to an external project try removing inline modifier. Everything worked fine after killing the process and executing fable -w again got everything back to normal. I did try but could not replicate it.
Do you suppose that in the event where a complete compilation of the project has not been successful, all subsequent changes will trigger a full compilation until it is successful after which only the modified files are compiled?

Inline expressions are giving me headaches, maybe I shouldn't have added that feature ;)
Inline expressions are stored in a static collection and are never removed. I wonder how Fable.Helpers.React.div got "lost". If you encounter the error again and have any other clue, please write again.
In any case, your idea of forcing a full compilation when there're errors is a good one. I'll try to implement it :)


MAGIC WP4 quantile bias

Namelist to calculate the precipitation quantile bias (following Mehran et al 2014).
First version for ESMValTool v2:
https://github.com/ESMValGroup/ESMValTool/blob/REFACTORING_quantilebias/esmvaltool/diag_scripts/quantilebias/main.r
Namelist
https://github.com/ESMValGroup/ESMValTool/blob/REFACTORING_quantilebias/esmvaltool/namelists/namelist_quantilebias.yml
Current status: First version of the tool implemented for ESMValTool v2.0 starting from branch REFACTORING_backend. To be delivered as alpha version for next demo session.

First version for v2.0 written starting from branch REFACTORING_backend synchronized on 11 May 2018. R wrapper calling CDO commands. Only NetCDF output.

@mattiarighi @bouweandela @valeriupredoi
This recipe heavily rely on cdo commands called from a main R wrapper. The latest version2_development merged for final refinements required an update of the esmvaltool environment, and cdo was not anymore included. How can we have cdo in the environment? The issue is that cdo will look for libraries within the conda environment while running from a local bin.


PPI and ENdmembers: AttributeError

Both PPI and Compute end-members end with
AttributeError: 'SpectralPlotter' object has no attribute 'figure'

In the case of the endmembers, is this the plot that I am supposed to get?

The result of endmembers depends on your sample and the settings/choices of MNF and PPI. For rock samples, this looks reasonable. However, for more explorative work, I would recommend being less restrictive in the MNF correlation or eigenvalues reduction and on the PPI definition. That way, you will have more than one endmember (but potentially more potential noise). We will try to describe this process in the upcoming documentation. At this point, we can discuss this via PM.


Mark env files as sensitive

This suppresses env file logging output in case of sensitive credentials making their way in to that directory. There is a fallback in case this is an older version of Chef that does not support sensitive as a common resource argument.

Thanks for the PR @martinisoft. I tried to add the following test to validate this functionality, but it's not passing:
it 'sets the sensitive attribute on the env file resource' do
  expect(chef_run).to create_file(::File.join(service_svdir, 'env', 'PATH')).with(
    :sensitive => true
   )
end

Failures:

  1) runit_service with environment attributes sets the sensitive attribute on the env file resource
     Failure/Error: expect(chef_run).to create_file(::File.join(service_svdir, 'env', 'PATH')).with(
       expected "file[/etc/sv/env-files/env/PATH]" to have parameters:

         sensitive true, was false
     # ./test/unit/runit_service/step_into_service_spec.rb:256:in `block (3 levels) in <top (required)>'

Also, I'm curious if there's a reason we're querying the instance methods on Chef::Provider::ChefGem rather than Chef::Provider::File ? FWIW I have tried the test both ways with no success.
Any thoughts about how to test for this?

@cwjohnston You're right and I've changed the class accordingly. A way you can test this by hand is to make a bundle with Chef 11.10 and run chef-shell with that code to see if it returns false then upgrade to 11.14 or newer and try again it should be true. The test should pass now with this change and if you'd like I can include it with my PR.

Due to the particulars of our unit test specs, it is proving difficult to actually run the negative case test against Chef < 11.14, but the affirmative test against this latest commit looks good to me! :+1:
@martinisoft, will you please add the affirmative unit test to this PR?

@cwjohnston I've added the test, but I am unable to run the specs locally. I keep seeing argument errors for the shared chef_run let so I don't know if this was a breaking change in ChefSpec that caused that.

@martinisoft any connection to #185 ?

@cwjohnston That patch resolved my testing issue and I was able to correct my test to get it to pass. All ready for review and possible merge 👍

Looks good to me! Thanks!


Visual bug in fullscreen

I'm using this button to control the fullscreen
IconButton(
                  icon: const Icon(PhosphorIcons.frameCornersLight),
                  iconSize: 16,
                  splashRadius: 20,
                  onPressed: () async {
                    var current = await windowManager.isFullScreen();
                    await windowManager.setFullScreen(!current);
                  },
                ),

If I click on it, it looks like this

The appbar seems to be replicated.
If you want to test it on the my app: https://github.com/LinwoodCloud/Butterfly/tree/CodeDoctorDE/issue117/app

Correction: It's not the appbar but the whole app (top, bottom, and the sides). I think this might be caused by the app border not removed properly.

Can you try running window_manager example app.

I thought of a way, set titlebar style to default before entering full screen.

Please update to v0.1.9


add IFSertaoPE domain

Hello, Its levan tsotskolauri from georgia
i'd like to ask you add my school in list ill write information below to prove that im student and my school is real
thanks you!
<EMAIL_ADDRESS>ISANI DISTRICT, PUBLIC SCHOOL #216
https://www.facebook.com/სსიპ-ქთბილისის-N216-საჯარო-სკოლა-473256156339558

@Gabriel-stack Pull request merged. Thank you!


Minor text changes to improve readability

Have removed duplications, changed the formatting in a couple of places to make it easier to understand options, and simplified the text to make it easier to read.

I am the Editor-Writer for the Apache Software Foundation's Infrastructure team. Justin McLean asked if I could review the documentation for your excellent project.


Branch 163490703

@tensorflow-jenkins test this please

@tensorflow-jenkins test this please, wakey wakey

Tensorflow Jenkins, test this please.

Jenkins, test this please.

Jenkins, test this please.

Jenkins, test this please.


Fix interrupt signal handling during shell.RunInteractiveShell()

closes #2612

This also slightly changes Ctrl-C behavior during the "Press enter to continue" prompt:
- Pressing Ctrl-C does not immediately interrupt the process
- The program will close after the user presses enter if Ctrl-C was pressed.
+ Pressing Ctrl-C does not interrupt the process
+ The program returns to the editor as normal after user presses enter.

I do not think this is an issue so I didn't bother with trying to find a workaround. Ctrl-C keybinding still works normally once the editor is restored.

As explained in the issue comments I don't think this approach will work without messing up SIGINT handling :frowning_face:


Trying to fix the watchdog wrapper.

@techman83 - can you take a look at this and see if it fixes the problem you had with the watch dog?


Implement a generator to generate expressions in Kong routes

Is there an existing issue for this?

[X] I have searched the existing issues

Problem Statement
broken from #3730.
For making expressions in kong routes for expression based router, we should implement a generator that constructs matchers including the predicates for matching fields, and logical AND/OR of the predicates. The generator should translate matcher to expressions in string format to fill into Expression field of kong routes, which satisfies Kong's ATC syntax, and have the same semantics as we define the matcher.
Supported fields are:

net.protocol (protocol)
net.port (target port)
tls.sni (SNIs of TLS requests)
http.method (HTTP method)
http.host
http.path
http.header.*

Proposed Solution
No response
Additional information
No response
Acceptance Criteria

[ ] Have a generator that can generate expressions from matchers used in Kong routes
[ ] Have tests to verify that generated expressions in Kong routes will match requests as we expected

fixed by #3780


I need your help creating an example with chainlit and MiniAutoGen: Lightweight and Flexible Agents for Multi-Agent Chats

🌐 Hello, amazing community!
I'm exploring the integration of two powerful libraries: MiniAutoGen and chainlit, and I would greatly appreciate your help and insights!
MiniAutoGen is an innovative open-source library designed to take applications with Large Language Models (LLMs) to the next level. Its differentiators are its lightweight and flexible approach, which allows for a high degree of customization.
Here are some notable features of MiniAutoGen:

Multi-Agent Dialogues: The ability to create complex and nuanced interactions with multiple intelligent agents operating together.
Agent Coordination: A mechanism that ensures harmony and efficient management among the agents.
Customizable Agents: Total freedom to shape agent behaviors according to project needs.
Action Pipeline: Simplifies and automates agent operations, facilitating scalability and maintenance.
Integration with +100 LLMs: Expanding conversational capabilities with over 100 LLMs for intelligent and contextualized responses.

My Challenge: I'm seeking help from the community to develop new integrations and modules.
I Seek Your Help: Do you have examples, tips, or guidance on how I can accomplish this integration? Any insight or shared experience would be extremely valuable!
Check out MiniAutoGen on Google Colab: MiniAutoGen on Google Colab
And here is the GitHub repository for more information: GitHub - brunocapelao/miniAutoGen
I'm looking forward to your ideas and suggestions. Let's shape the future of AI conversations together! 🌟

Hello, I think you should join our discord, it's a better place to chat with the community, and showcase your code!


Alpine.js/Livewire and Power-Grid Authentication redirect hangup

For bug reporting only! If you're posting a feature request or discussion, please ignore.
Expected Behavior
When making a a request via Livewire, after adding the auth header, we expect the requested resource to load.
Current Behavior
When queries are fired, the appropriate header is added. However, the middleware "verify.shopify" is forcing a redirect through responding with HTML and trying to redirect from javascript. This cause the request to end and errors abound.
This does not work...
Steps to Reproduce

Use livewire

I believe I solved my own problem.... Yay! I added the following to token_handler.blade.php
        if (window.Livewire) {
            // livewire
            window.livewire.addHeaders({
                'Authorization': bearer,
                'content-type': 'application/json',
                'X-Requested-With': 'XMLHttpRequest'
            });
        }

Since this package doesn't recognize Liveware, which is identified in the request, we need to add a little finesse to it. This should work for anyone using livewire combined with this package.


[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative-sandbox/networking-wg-leads
/assign knative-sandbox/networking-wg-leads
Produced by: knative-sandbox/knobots/actions/update-deps
Details:
bumping knative.dev/networking 58bc12b...bd21fc9:
  > bd21fc9 add component label to reduce invocations (# 616)
bumping knative.dev/pkg 51be315...fc93ac7:
  > fc93ac7 upgrade to latest dependencies (# 2424)

/lgtm
/approve


Documentation Incomplete?

This doesn't seem to have the same info as the inbox one here: https://docs.microsoft.com/en-us/uwp/api/windows.ui.xaml.controls.textcommandbarflyout
Is that expected?

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

ID: 4438107a-5416-cbe3-e17d-381406b6b01e
Version Independent ID: 8fae7f8a-85db-43c4-2f44-77249b350842
Content: TextCommandBarFlyout Class - Windows UWP applications
Content Source: https://cpubwin.visualstudio.com/DefaultCollection/windows-uwp/_git/winui-api-build?path=%2fwinui-api-build%2fmicrosoft.ui.xaml.controls.textcommandbarflyout.yml&version=GBlive&_a=contents
Product: uwp
Technology: winrt-reference
Git Login: jwmsft
Microsoft Alias: jimwalk

Not expected, but the source is in two places so we need to copy from one to the other. @yulikl?

Hi @michael-hawker - This is expected for the WinUI 2.x docs as the CommandBar classes were still inheriting from the WinRT FlyoutBase, so our docs pipeline wasn't pulling in the inherited members. If you switch the WinUI version to 3 preview 3, the inherited members are displayed in-page as expected as https://docs.microsoft.com/en-us/windows/winui/api/microsoft.ui.xaml.controls.primitives.flyoutbase?view=winui-3.0-preview has been lifted from WinRT.


Docs: being more explicit about why to use api.background.task

Hey! When I was reading the docs and I saw api.background.task, the first thing that popped into my head was "but you can just use asyncio.create_task or loop,.run_in_executor for that without inventing something new!". But then I noticed that it also passes the context vars to the synchronous backround stuff, which is nice. Wonder why that's not the case in the stdlib, cause it would be nice :)
All I'm asking is: would you welcome a docs PR explaining api.background.task to asyncio purists like myself? :)

Yes, we would love to !

Nice. I'll try to write something up in the next few days


[TW#18773] Deadlock in spi_master.c spi_device_transmit

I am experiencing a deadlock in spi_device_transmit(). The deadlock happens while waiting for the transaction response, in this code from spi_master.c:
esp_err_t spi_device_get_trans_result(spi_device_handle_t handle, spi_transaction_t **trans_desc, TickType_t ticks_to_wait)
{
    BaseType_t r;
    spi_trans_priv trans_buf;

    SPI_CHECK(handle!=NULL, "invalid dev handle", ESP_ERR_INVALID_ARG);
    // DEADLOCK HERE
    r=xQueueReceive(handle->ret_queue, (void*)&trans_buf, ticks_to_wait);

This only seems to happen when I am running many transactions on both the HSPI_HOST and VSPI_HOST.
I have previously reported this problem in this thread: https://esp32.com/viewtopic.php?f=2&t=4374 but did not get any further responses.
Initially, I was able to get around this issue by using a mutex on all my SPI access, so I would never use both HSPI_HOST and VSPI_HOST at the same time. Without that mutex the deadlock happens almost immediately. With the added mutex it is much more rare, but I can produce it within about 2 minutes by running thousands of transactions on both busses.
At the most basic, it seems like the issue is that the transaction gets submitted to the controller but then the response is never received. Since I am using SPI master, I'm not sure what the conditions are where this could happen. The master should either successfully receive the response or it should time out.
I'm happy to provide any further detail you need, please just let me know.

Does it only happen when one spi is using dma and one is not? Does it happen in single core mode?

Hi @negativekelvin, thank you for your response. Here's some answers:

Yes, happens when one is using DMA and one is not, or when both are using DMA. My normal use case is the SPI Flash using DMA and the LCD is not. I typically only send commands to the LCD, no data, so I don't use DMA and my transfer length is 0.

I normally run two cores. I tested today with one core and that does indeed seem to fix it.

IDF on a5eb369126e5cef31715d2755931cf933bb98bee

I also tested a few other things this morning, and I noticed that if I add vTaskDelay(2 / portTICK_PERIOD_MS); between calls to spi_device_transmit it improves the issue, but does not completely fix it. Instead of it locking up within a second or two, it takes 10-15 seconds.
I'm very interested to know if any of those points give you any ideas as to what is happening.
Thanks!

Update on this: I converted my LCD code entirely to DMA so that both the SPI Flash and LCD are both using DMA and this seems to have either solved or hidden the problem. I am no longer getting deadlocks even while accessing both busses at the same time.
For what it's worth, the biggest change that this made is that I now send my updates about 4x faster, so I am holding the bus for less time, and I am sending far fewer total transactions. Previously I would send about 532 single byte transactions per frame, and now I send 8.
I'll close this, and reopen it if I start to notice the problem again.

I spoke too soon, a few minutes later it locked again. So, I've switched from spi_device_transmit to calling spi_device_queue_trans and spi_device_get_trans_result myself, so that I can specify a shorter timeout and try to recover. That eventually generated the following error:
. Exception was unhandled.
Core 1 register dump:
PC      : 0x400820be  PS      : 0x00060933  A0      : 0x8013f468  A1      : 0x3ffde9b0
0x400820be: esp_intr_enable at /Users/jason/esp/esp-idf/components/esp32/./intr_alloc.c:768

A2      : 0x3ffdfcd8  A3      : 0x00000000  A4      : 0x3ffcec50  A5      : 0x00000000
A6      : 0x00000000  A7      : 0x00000000  A8      : 0xbed194f7  A9      : 0x3ffde980
A10     : 0x00000001  A11     : 0x3ffdeb4c  A12     : 0x00000001  A13     : 0x00000001
A14     : 0x00060920  A15     : 0x00000000  SAR     : 0x00000005  EXCCAUSE: 0x0000001c
EXCVADDR: 0xbed194f7  LBEG    : 0x40099c64  LEND    : 0x40099c92  LCOUNT  : 0xffffffff
0x40099c64: memcpy at /home/jeroen/esp8266/esp32/newlib_xtensa-2.2.0-bin/newlib_xtensa-2.2.0/xtensa-esp32-elf/newlib/libc/machine/xtensa/../../../../.././newlib/libc/machine/xtensa/memcpy.S:168

0x40099c92: memcpy at /home/jeroen/esp8266/esp32/newlib_xtensa-2.2.0-bin/newlib_xtensa-2.2.0/xtensa-esp32-elf/newlib/libc/machine/xtensa/../../../../.././newlib/libc/machine/xtensa/memcpy.S:201

Backtrace: 0x400820be:0x3ffde9b0 0x4013f465:0x3ffde9d0 0x400dba82:0x3ffdea10 0x400dc89c:0x3ffdea70 0x400dd82d:0x3ffdeaa0 0x400dd8ba:0x3ffdeac0
0x400820be: esp_intr_enable at /Users/jason/esp/esp-idf/components/esp32/./intr_alloc.c:768

0x4013f465: spi_device_queue_trans at /Users/jason/esp/esp-idf/components/driver/./spi_master.c:725

0x400dba82: fb_hal_lcd_send_buffer_unsafe at /Users/jason/Projects/xxx/xxx-esp32-firmware/main/./fb_hal_v1r1.c:1043

0x400dc89c: fb_hal_lcd_flush at /Users/jason/Projects/xxx/xxx-esp32-firmware/main/./fb_hal_v1r1.c:1203

0x400dd82d: draw_screen at /Users/jason/Projects/xxx/xxx-esp32-firmware/main/./fb_lcd.c:294

0x400dd8ba: fb_lcd_refresh_task at /Users/jason/Projects/xxx/xxx-esp32-firmware/main/./fb_lcd.c:461

Rebooting...

My code for sending a transaction to the LCD is below:
static esp_err_t fb_hal_lcd_send_buffer_unsafe(uint8_t* data, size_t data_len, bool command) {
	esp_err_t err = gpio_set_level(LCD_IO_A0, command ? 0 : 1);
	if (err != ESP_OK) {
		return err;
	}

	memcpy(lcd_tx_buffer, data, data_len);

	spi_transaction_ext_t t = {
			.base = {
				.length = data_len * 8,
				.flags = SPI_TRANS_VARIABLE_ADDR
					| SPI_TRANS_VARIABLE_CMD,
				.tx_buffer = lcd_tx_buffer,
				.rx_buffer = lcd_rx_buffer,
			},
			.command_bits = 0,
			.address_bits = 0,
	};

    err = spi_device_queue_trans(lcd_spi_device, (spi_transaction_t*) &t, 1000 / portTICK_PERIOD_MS);
    if (err != ESP_OK) {
    		FB_LOG_ERROR(err, "spi_device_queue_trans");
    		return err;
    }

	spi_transaction_t *ret_trans;
    err = spi_device_get_trans_result(lcd_spi_device, &ret_trans, 1000 / portTICK_PERIOD_MS);
    if (err != ESP_OK) {
    		FB_LOG_ERROR(err, "spi_device_get_trans_result");
    		return err;
    }

//    err = spi_device_transmit(lcd_spi_device, (spi_transaction_t*) &t);
//	if (err != ESP_OK) {
//		return err;
//	}

	return ESP_OK;
}

So now what happens is after a few minutes I get a timeout error on spi_device_get_trans_result and then within a few seconds I get the above core dump.

I added some code to attempt to reinitialize the bus when this timeout happens, and got some interesting errors:
E (58417) FB_HAL_V1R (0107) spi_device_get_trans_result
E (58417) FB_HAL_V1R (0107) LCD bus failure detected, attempting to reinitialize
E (58427) spi_master: spi_bus_remove_device(317): Have unfinished transactions
E (58427) spi_master: spi_bus_free(221): not all CSses freed
E (58437) spi_master: spi_bus_initialize(131): host already in use

and here is the code that produced those errors:
	if (lcd_spi_device) {
		spi_bus_remove_device(lcd_spi_device);
		lcd_spi_device = NULL;
		spi_bus_free(HSPI_HOST);
	}

So it seems the transaction is still in the queue, but it's not completing, and I can't de-init the bus to try again. So how do I handle this situation?

You are still unable to reproduce in single core mode?  What about if all spi threads pinned to same core?

@negativekelvin Correct, it works fine in single core mode. I'll try pinning the threads, but that will take a bit since the SPI Flash access is coming from the VFS layer and I have several threads accessing it.
In the meantime, can you tell me if there is a reason for the questions regarding two core? Is there a known issue, or something you've seen before?
Thanks,
Jason

There have been some SMP issues with dport and interrupts so running related peripheral interrupts on separate cores could trigger something. Will have to ask some experts...
@ginkgm @Spritetm @igrr

@negativekelvin I've confirmed that if I run the app in single core mode, or if I pin all tasks that use SPI to a single core in two core mode it works fine. So, it does seem to relate to SMP and interrupts, as you said.

Hi Jason @vonnieda ,
I've done a simple test: two tasks access the bus (to the same pin but one HSPI and another VSPI) continuously, using the LCD example and it switches between tasks fluently.
So I wonder if the problem is in the spi flash part.
Can you explain the lib/functions you used to access the spi flash more detailedly??

Hi @ginkgm, I will try to put together a self contained example today and post it here. In the meantime, I want to mention that when this happens it has never been the SPI Flash. It's always the LCD. I've checked this both with logging and with JTAG, and it is always the LCD thread locking up.

Hi @vonnieda ,
thanks, that would help us a lot to know the cause.
But as far as i know, ESP-IDF don't have library supporting SPI flash on HSPI or VSPI, the esp_flash_ functions are used to access the ROM flash which holds the code. And sometimes accessing the flash involves a pause to code in a wide-range (iirc all the code except those ISR in the IRAM) since you cannot fetch code from the flash until the flash is ready again.
If you're using your own flash lib, maybe you can check the SPI controller you're using in the flash lib, or paste them here for us to help you.

Hi @ginkgm, I am using my own SPI flash access routines. I will post these as part of the example as soon as I have it ready. Right now I am trying to get it to reproduce on a dev board (WROVER-KIT) so that it will be easy for you to test and reproduce.
In summary, here is what we have:
LCD: ST7565 on HSPI_HOST @ 1 MHz
SPI FLASH: W25Q128 on VSPI_HOST @ 40 MHz
No other devices are on either bus.
The SPI FLASH is used for a LittleFS filesystem via VFS, also using my own routines.
Sorry for the delay in getting the example posted. I'll get it up as soon as I can. If you'd like to close this until I am able to provide a test case, I understand.

Hi @negativekelvin, @ginkgm, @Spritetm, @igrr: I am now experiencing this at a much higher frequency on both SPI busses, and I'm at a loss to understand why. Here is a short summary of the problem:
LCD: ST7565 on HSPI_HOST @ 1 MHz
SPI FLASH: W25Q128 on VSPI_HOST @ 40 MHz
Once in a while, and randomly, spi_device_transmit() will deadlock. It never returns. According to the docs, this should be impossible. The function should either return with success or failure. In debugging this issue, the deadlock happens in spi_device_transmit() in spi_master.c, on this line:
ret=spi_device_get_trans_result(handle, &ret_trans, portMAX_DELAY);

This seems to indicate to me that the interrupt handler that receives the transaction complete notification is never firing.
I also want to reiterate that this only happens in dual core mode - in single core mode it seems to be fine.
Can you tell me if there is any situation in which spi_device_transmit() should fail to return?
If there is any other information I can supply, please let me know. I have tried reproducing this on a dev board, but there is so much software behind it that it will take a long time to write something that accurately reproduces the issue. That being said, I want to reiterate that this deadlock is within the ESP-IDF code.
Thanks,
Jason

Have you tried forcing spi_bus_initialize for both buses to be called on the same core so that both interrupts are enabled on the same cpu?

Hi @negativekelvin, yes, all my init code runs from app_main().
app_main() calls fb_hal_initialize()
Here is that function, somewhat trimmed down:
esp_err_t fb_hal_initialize() {
	FB_ERROR_CHECK_NO_RET(fb_hal_bulk_storage_initialize());
	FB_ERROR_CHECK_NO_RET(fb_hal_lcd_initialize());
	return ESP_OK;
}

And here are those two init functions, also somewhat trimmed down:
static esp_err_t fb_hal_bulk_storage_initialize() {
	bulk_storage_spi_mutex = xSemaphoreCreateMutex();

	bulk_storage_rx_buffer = heap_caps_calloc(
			BULK_STORAGE_SPI_MAX_TRANSFER_BYTES,
			sizeof(uint8_t),
			MALLOC_CAP_DMA);
	bulk_storage_tx_buffer = heap_caps_calloc(
			BULK_STORAGE_SPI_MAX_TRANSFER_BYTES,
			sizeof(uint8_t),
			MALLOC_CAP_DMA);
	spi_bus_config_t bus_config = {
		.mosi_io_num = BULK_STORAGE_IO_SPI_MOSI,
		.miso_io_num = BULK_STORAGE_IO_SPI_MISO,
		.sclk_io_num = BULK_STORAGE_IO_SPI_SCLK,
		.quadwp_io_num = BULK_STORAGE_IO_SPI_QWP,
		.quadhd_io_num = BULK_STORAGE_IO_SPI_QHD,
		.max_transfer_sz = BULK_STORAGE_SPI_MAX_TRANSFER_BYTES,
	};

	FB_ERROR_CHECK_RET(spi_bus_initialize(VSPI_HOST, &bus_config, BULK_STORAGE_SPI_DMA_CHANNEL));

	spi_device_interface_config_t dev_config = {
		.clock_speed_hz = BULK_STORAGE_SPI_SPEED_HZ,
		.mode = 0,
		.spics_io_num = BULK_STORAGE_IO_SPI_CS,
		.queue_size = 7,
		.flags = SPI_DEVICE_HALFDUPLEX,
	};

	FB_ERROR_CHECK_RET(spi_bus_add_device(VSPI_HOST, &dev_config, &bulk_storage_spi_device));

	return ESP_OK;
}

static esp_err_t fb_hal_lcd_initialize() {
	lcd_spi_mutex = xSemaphoreCreateMutex();

	lcd_tx_buffer = heap_caps_calloc(
			LCD_WIDTH * LCD_HEIGHT / 8,
			sizeof(uint8_t),
			MALLOC_CAP_DMA);

	esp_err_t err;

	// Configure the SPI bus
	spi_bus_config_t bus_config = {
			.mosi_io_num = LCD_IO_MOSI,
			.miso_io_num = -1,
			.sclk_io_num = LCD_IO_SCK
	};
	err = spi_bus_initialize(LCD_SPI_BUS, &bus_config, LCD_SPI_DMA_CHANNEL);

	// Configure the LCD SPI device
    spi_device_interface_config_t dev_config = {
        .clock_speed_hz = LCD_SPI_SPEED_HZ,
		.mode = 0,
        .spics_io_num = LCD_IO_CS,
        .queue_size = 7,
    };
	err = spi_bus_add_device(LCD_SPI_BUS, &dev_config, &lcd_spi_device);

	// setup GPIO for A0
	gpio_config_t g = {
		.pin_bit_mask = (1ULL << LCD_IO_A0),
		.mode = GPIO_MODE_OUTPUT
	};
	err = gpio_config(&g);

	return ESP_OK;
}

Ok well then have you tried forcing spi_bus_initialize for each bus to be called on different cores so that both interrupts are not enabled on the same cpu?

Hi @negativekelvin, I've run the test as you described and it looks like it might fix the problem. I've been running now for about 41 minutes without a deadlock, where previously it would lock usually within 3-5 minutes.
Here's how I changed my code:
volatile static bool initialize_cpu_0_done = false;
volatile static bool initialize_cpu_1_done = false;

void initialize_cpu_0(void* pw) {
	FB_LOG_INFO(0, "Initializing Bulk Storage on core %d", xPortGetCoreID());
	FB_ERROR_CHECK_NO_RET(fb_hal_bulk_storage_initialize());
	initialize_cpu_0_done = true;
	FB_LOG_INFO(0, "Initializing Bulk Storage on core %d DONE", xPortGetCoreID());
	vTaskDelete(NULL);
}

void initialize_cpu_1(void* pv) {
	FB_LOG_INFO(0, "Initializing LCD on core %d", xPortGetCoreID());
	FB_ERROR_CHECK_NO_RET(fb_hal_lcd_initialize());
	initialize_cpu_1_done = true;
	FB_LOG_INFO(0, "Initializing LCD on core %d DONE", xPortGetCoreID());
	vTaskDelete(NULL);
}

esp_err_t fb_hal_initialize() {
	xTaskCreatePinnedToCore(initialize_cpu_0,
			"init_0",
			5 * 1024,
			NULL,
			tskIDLE_PRIORITY,
			NULL,
			0);
	while (!initialize_cpu_0_done) {
		vTaskDelay(500 / portTICK_PERIOD_MS);
	}

			xTaskCreatePinnedToCore(initialize_cpu_1,
					"init_1",
					5 * 1024,
					NULL,
					tskIDLE_PRIORITY,
					NULL,
					1);
			while (!initialize_cpu_1_done) {
				vTaskDelay(500 / portTICK_PERIOD_MS);
			}

	return ESP_OK;
}

So, this seems like it might be a workaround, but I'd like to understand why the problem is happening in the first place. Does this give you any clue as to what might be wrong?
Thanks,
Jason

It seems like it happens when there are overlapping interrupts on the same CPU and the other CPU is also active but still unclear exactly why.

Thanks @negativekelvin, would you recommend this workaround for now, then?

Yes because you can see if it really prevent the issue 100%.  Hopefully you can give some minimal code to reproduce it.  Maybe you could also get logic capture to see exactly where it stops in terms of spi outputs.

Hi @negativekelvin, I've just seen this post: https://esp32.com/viewtopic.php?f=2&t=5505&sid=3421566ef8d889acd849d972481fcf87 and then the documentation that it references at https://esp-idf.readthedocs.io/en/latest/api-reference/system/intr_alloc.html#external-peripheral-interrupts.
I looked at spi_master.c and it does indeed call esp_intr_alloc outside of a critical section, so, does this mean that I need to be sure that any task that calls into the spi_master driver is on the same core that allocated it?
This reminds me that when I tried your suggestion a while back of pinning all the SPI tasks to one core it seemed to fix it. Is this a requirement for ESP-IDF, then?
Thanks,
Jason

I just ran into a similar issue and the discussion in this issue seems helped a lot.
I am having multiple thread accessing the same SPI device. The access are guarded by std::mutex and I could confirm no racing condition. However, I still got deadlock after a few hours. I crashed the program when deadlock and collected the coredump. Supurisingly, all blocking threads were stuck at spi_device_acquire_bus, an unexpected indication that a transaction was not ending properly. My SPI bus/locks are managed by C++ RAII pattern so they are guaranteed to be released after use.
After reading through this issue, I realize that even though my bus access is mutually exclusive, the threads are not guaranteed to run on the same core (i.e., not pinned). I refactored my code to ensure all SPI transaction were run on the same core. Now the issue was gone in the short test (a few hours). I will keep it on and see if this really is the root issue.
If this is the case, I would argue that the docs should be improved.

The SPI master driver has the concept of multiple Devices connected to a single bus (sharing a single ESP32 SPI peripheral). As long as each Device is accessed by only one task, the driver is thread safe. However, if multiple tasks try to access the same SPI Device, the driver is not thread-safe. In this case, it is recommended to either:

Refactor your application so that each SPI peripheral is only accessed by a single task at a time. You can use spi_bus_config_t::isr_cpu_id to register the SPI ISR to the same core as SPI peripheral related tasks to ensure thread safety.

Add a mutex lock  around the shared Device using xSemaphoreCreateMutex.

Clearly, the second recommendation is not sufficient to guarantee the bus ISR and the task runs on the same core. Could you please confirm this? @negativekelvin

I was having a problem that looks exactly like this one (#6624) that I gave up digging about it as I deemed it to be above my paygrade, but someone apparently nailed it (#8179) and seems to be solved now.
I suggest you test it again with revisions which include that fix, and provided that there's mutual exclusion at the device level, calling any amount of SPI functions from either core in any way should work, otherwise it's a bug and you should open an issue.

I just ran into a similar issue

What is your esp-idf version? (git describe --tags output)

@AxelLin v5.1-dev-3223-ge1ebda17c4

@AxelLin v5.1-dev-3223-ge1ebda17c4

It already includes 3c8f6dd1cfebaee3860fbc66ff985528ba56b447.
Could you provide more detail about the issue? e.g. sdkconfig, backtrace log.
(Maybe you should create a new issue instead if your issue is not exactly the same as this one.)

@AxelLin The issue might not be exactly the same but pinning task to the same core as ISR did fix the issue. I have left my device running for 24 hrs without issue otherwise it will be stuck in deadlock in couple of hours. I will try to reproduce the error later and start a new issue. Thanks

I will try to reproduce the error later

Please do that.

@wuyuanyi135 Did you do it?

Sorry for not responding. Probably due to environment inconsistent and the randomness I could not reproduce the issue. After updating to v5.2 and sticking to the same core rule I have never run into the same issue.


Circuit metadata is missing from Sampler results on fake backend

Describe the bug
When running a circuit via SamplerV2 on a real QPU, the PubResult corresponding to the circuit contains a metadata attribute that reproduces the original circuit metadata. However, when running that circuit on a fake backend, the metadata attribute is not present in the PubResult.
Steps to reproduce
Run the script below. The script duplicates the example script in the fake backend documentation and simply adds metadata to the circuit. The first print line correctly prints the circuit metadata, which survives transpilation. The second print line prints an empty dictionary, rather than the circuit metadata.
from qiskit.circuit import QuantumCircuit
from qiskit.transpiler.preset_passmanagers import generate_preset_pass_manager
from qiskit_ibm_runtime import SamplerV2 as Sampler
from qiskit_ibm_runtime.fake_provider import FakeManilaV2

# Bell Circuit
qc = QuantumCircuit(2)
qc.h(0)
qc.cx(0, 1)
qc.measure_all()
qc.metadata = {0: 1}

# Run the sampler job locally using FakeManilaV2
fake_manila = FakeManilaV2()
pm = generate_preset_pass_manager(backend=fake_manila, optimization_level=0)
isa_qc = pm.run(qc)
print(f'circuit metadata: {isa_qc.metadata}')

# You can use a fixed seed to get fixed results.
options = {"simulator": {"seed_simulator": 42}}
sampler = Sampler(backend=fake_manila, options=options)
result = sampler.run([isa_qc]).result()
print(f'circuit metadata: {result.metadata}')

Expected behavior
Retain circuit metadata in SamplerV2 when running fake backend, identically to behaviour on real QPU.

qiskit-ibm-runtime version: 0.22.0
Python version: 3.11.6
Operating system: macOS Sonoma 14.4

The same issue occurs when using the AerSimulator migration script here. Happy to file a separate ticket if that is helpful.


Tags need a space after it in order to count as a tag at the end of a memo

Describe the bug
Tags need a space after it in order to count as a tag at the end of a memo
Steps to reproduce
create a memo with "#test"
after that create a memo with "#test "
Screenshots or additional context
No response

This has been discussed here https://github.com/usememos/memos/issues/560

Duplicated with #560


Add remark command

Week 6 Tutorial 2

Codecov Report

Merging #1 (d0cb4f9) into master (08a0727) will decrease coverage by 0.44%.
The diff coverage is 67.74%.

@@             Coverage Diff              @@
##             master       #1      +/-   ##
============================================
- Coverage     72.15%   71.71%   -0.45%
- Complexity      399      409      +10
============================================
  Files            70       73       +3
  Lines          1232     1287      +55
  Branches        125      130       +5
============================================
+ Hits            889      923      +34
- Misses          311      331      +20
- Partials         32       33       +1

Impacted Files
Coverage Δ

.../seedu/address/logic/parser/AddressBookParser.java
88.88% <0.00%> (-11.12%)
:arrow_down:

...eedu/address/logic/parser/RemarkCommandParser.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/ui/PersonCard.java
0.00% <0.00%> (ø)

...c/main/java/seedu/address/model/person/Remark.java
62.50% <62.50%> (ø)

...va/seedu/address/logic/commands/RemarkCommand.java
73.91% <73.91%> (ø)

...java/seedu/address/logic/commands/EditCommand.java
97.05% <100.00%> (+0.04%)
:arrow_up:

...a/seedu/address/logic/parser/AddCommandParser.java
100.00% <100.00%> (ø)

...ain/java/seedu/address/logic/parser/CliSyntax.java
85.71% <100.00%> (+2.38%)
:arrow_up:

...c/main/java/seedu/address/model/person/Person.java
97.82% <100.00%> (+0.20%)
:arrow_up:

.../java/seedu/address/model/util/SampleDataUtil.java
25.00% <100.00%> (+5.00%)
:arrow_up:

... and 5 more

Continue to review full report at Codecov.

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


Set up as GH action

Describe the solution you'd like
I'm looking for a solution to automate testing of a WP plugin in a GitHub action.
Ideally, The repo would be of the plugin files only and it would install WP around it, set up the server, etc.
Has anyone set this up before?

Hi @KevinBatdorf
We've done this before, so definitely achievable and doesn't require too much work if you're using this tool.
First set your configuration in cypress.json to be something similar to below ensuring the path to the plugin you want to test is correct.
{
 "wp": {
    "version": ["5.5"],
    "plugins": ["./"]
  }
}

Then you can use Cypress's GitHub action https://github.com/cypress-io/github-action to get most of the way there. But you need to ensure the test container is running. We've done something similar below in a workflow:
      - name: Yarn Install
        uses: cypress-io/github-action@v1
        with:
          # just perform install
          runTests: false

      - name: WP Cypress Start
        run: yarn run wp-cypress start

      - name: Run Cypress
        uses: cypress-io/github-action@v1
        with:
          browser: chrome
          headless: true
          install: false

We hope to provide some examples of testing on different CI's in the future but hope this helps for now 🤞🏽


Bug: correct commit-analyzer cwd issues

Describe the bug
Depending on a set of unique runner variables the cwd path in @semantic-release/commit-analyzer will not properly load the conventional-changelog-conventionalcommits from the dependency tree and we had to patch it manually.
To Reproduce

Expected behavior
We should somehow make this work out of the box, either by patching upstream or creating our own forks / peerDep configurations expanding commit tooling.
Screenshots

Desktop

OS:
Browser:
Version:

Smartphone

Device:
OS:
Browser:
Version:

Additional context

View the issue in https://github.com/open-sauced/open-sauced/actions/runs/1095686316

.take

This has been resolved in upstream!


Bump version of sc4s in ansible playbooks

:tada: This PR is included in version 3.14.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Running dep ensure -v hangs

UPDATED

Following the instructions in the BUILDING.md file, when I run 'dep ensure -v' it hangs.
It appears to download everything then get as far as shown below, then just hangs.
(106/110) Wrote<EMAIL_ADDRESS>(107/110) Wrote k8s.io/apiextensions-apiserver@master
(108/110) Wrote<EMAIL_ADDRESS>(109/110) Wrote<EMAIL_ADDRESS>(110/110) Wrote<EMAIL_ADDRESS>Attaching strace to the dep process reveals that it is doing nothing but waiting for something:-
strace -p 3443
strace: Process 3443 attached
futex(0xb689b0, FUTEX_WAIT, 0, NULL
The disk usage on the /home filesystem seems to be steadily increasing, although I don't know which process is causing this:-
_Every 1.0s: df |grep -E "/home|/tmp"                                     : Tue May 21 14:56:57 2019
/dev/mapper/sys_vg-tmp_lv       5232640  414948   4817692   8% /tmp
/dev/mapper/data_vg-home_lv   103758336 5992612  97765724   6% /home
Every 1.0s: df |grep -E "/home|/tmp"                                     : Tue May 21 14:57:22 2019
/dev/mapper/sys_vg-tmp_lv       5232640  414948   4817692   8% /tmp
/dev/mapper/data_vg-home_lv   103758336 6000292  97758044   6% /home_
I'm running minikube on the server in question, within a VirtualBox VM.
The server is an ubuntu 18.04 OS which is fully up to date.
All obvious things like disk space, memory and swap are all OK.
What am I missing?

UPDATE

After waiting for over 20 mins, the 'dep ensure -v ' process completed, however when running 'make build' as instructed in the BUILDING.md file, I get the following errors.
There is no mention in BUILDING.md about an "image tag" and I can't find anything in the documentation about it either.
Error: could not set image tag: must specify an image tag, none found for build env vars:
Usage:
build parse-env release [flags]
Flags:
-h, --help   help for release
Global Flags:
--debug   enable verbose debug output
exit status 1
Error: could not set image tag: must specify an image tag, none found for build env vars:
Usage:
build parse-env version [flags]
Flags:
-h, --help   help for version
Global Flags:
--debug   enable verbose debug output
exit status 1
Error: could not set image tag: must specify an image tag, none found for build env vars:
Usage:
build parse-env image-tag [flags]
Flags:
-h, --help   help for image-tag
Global Flags:
--debug   enable verbose debug output
exit status 1
Error: could not set image tag: must specify an image tag, none found for build env vars:
Usage:
build parse-env container-prefix [flags]
Flags:
-h, --help   help for container-prefix
Global Flags:
--debug   enable verbose debug output
exit status 1
go run buildcmd/main.go validate-operating-parameters

\
Error: could not set image tag: must specify an image tag, none found for build env vars:
Usage:
build validate-operating-parameters [flags]
Flags:
-h, --help   help for validate-operating-parameters
Global Flags:
--debug   enable verbose debug output
exit status 1
Makefile:20: recipe for target 'validate-computed-values' failed
make: *** [validate-computed-values] Error 1

We've updated the building docs, thanks for the heads up!
https://github.com/solo-io/squash/blob/master/BUILDING.md


gcForest error

Hi,
When I tried to follow your gcForest Demo, then for "from deepforest.gcForest import GCForest", an error happened since there is no gcForest in the deep forest folder. So, could you lend me a hand, how to fix this problem?

@JenniferCreep The notebook is not up to date with the latest version of the API. I will change the notebooks shortly and will let you know when it's done ! Hope it will help !

great thanks!!


EEBus: Fix Enabled handling, improve Status and connected handling, fix typo

Fix https://github.com/evcc-io/evcc/issues/2938


Sound Issue

Summary:
Sometiems all the units reply at the same time when you are moving them.
Type:

A ()
B ()
C (x)

Priority:

Urgent ()
High ()
Regular ()
Low (x)

Frequency

Always ()
High ()
Regular (x)
Low ()

Steps to reproduce:
Select all units, Maintain pressed right mouse button
Actual result:
Everyone talks saying the their lines
Expected result:
Just one line said.
Build:
0.6.5

When this happended to you, did you press the mouse buttons in any particular order, or were you pressing anything that wasn't the ground?
Thanks!


Readme: extended prerequisites section

demo_socket_listen example
more errorproof enable-bpf-lsm.py
docker container template

CI failures are unrelated to this change. The same thing happens on main branch https://github.com/deepfence/ebpfguard/actions/runs/4859183192/.


Rename Post Action and Add Secrets Tags

ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo.  If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[x] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[x] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

[x] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[x] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

fyi @mentat9

\az run

/azp run

/azp run

@ruowan Hi, can you please approve this PR when you get chance please?

@leni-msft Hi can I please get approval?

@xwang971 Since the integration branch has been merged to main, please rebase your working branch onto main and update the target branch to main.
/cc. @Juliehzl

also changing url will be breaking change, please request breaking change approval

@leni-msft Hi, the authToken API is newly introduced to this version and we havent rolled out release based on this version yet so this would not break anything. Could we please remove the label and get this merged?

@xwang971 - The changes are good from ARM perspective, but the BreakingChangeReviewRequired label needs to be addressed before ARM signoff.

/azp run

/azp run

@leni-msft Hi, the breacking change is approved, also got approval from ARM side, please take a look, thanks


externalize audits so they can be run locally and/or within target library CI/CD

Story
As a GraphQL library maintainer I would like to be able to run HTTP spec audit locally to ensure my client/server remains compliant with the spec.
Acceptance criteria

GraphQL library maintainer is able to run HTTP spec audit locally

Related

https://github.com/graphql/graphql-http/issues/8
Apollo Federation Spec Compliance Tools

You already can, see the "Audit for servers usage in Jest environment" recipe.

Its doable but somewhat clunky -> it implies folks have to write Javascript to run tests (and many libraries are not Javascript based). Ideally they could just run some executable script that gives them the results*.
Looks like we would also need to generate the report matrix manually as well (example auto generated report https://github.com/apollographql/federation-jvm/pull/290#issuecomment-1397915584).

Ah yes, a CLI. Makes sense! I'll see what I can do.


Pass through supported pandas reader parameters in signatures

[X] Tests added / passed
[X] Passes black dask / flake8 dask

This PR makes use of an optional dependency on fastcore to pass through supported parameters of pandas readers (read_csv, etc) in the corresponding dask dataframe function signature.
The optional dependency fastcore is small, smaller than even toolz as a point of reference.
If this PR is acceptable, I will also try to get fastcore on conda-forge.
Hopefully others will find this as awesome as I do:

Thanks for opening up the PR. I personally don't think this justifies dask taking on an additional dependency, but we'll see what the other maintainers think.

This seems like a nice feature, thanks for putting a PR forward @brl0! However, I agree with @TomAugspurger that it may not be worth adding a new optional dependency.
I wonder how difficult it would be to write our own decorator using the inspect module to do something similar

@jrbourbeau, I removed the optional dependency and just copied the decorator over from fastcore along with some tests from their docs.  They are using an Apache 2 license in case there is any concern about that.
At this point, I think this should be ready for further review.  While the MacOS tests are still running, most other tests have passed other than python 3.7 on windows, but from what I can tell, that failure is not related to this PR.

Can one of the admins verify this patch?

For comparison, here is the signature for read_csv currently, without this PR:

Let me know if there are any questions or concerns.


is it possible to make the menu icon bar removable?

just for us guys that like to keep the menu bar clean from third party apps. thank you, great app! it works great for me.
edit: sorry, *menu bar icon

See How to hide Unshaky from status bar


User Settings: Implement setting-provided default values

As an extension developer, I want to be able to get settings' values including defaults like interface language so I can stay in sync whether or not the setting has been set.

On the settings service:

Maintain list of all user settings' default values (hard-coded; we will load from extensions in #719)

Include some real settings - interface language, current Scripture reference

Use the default value from the manifest instead of the parameter default value passed in. No more defaultValue parameter in service or in hook.

Rework settings service's data provider: getSetting(key)

If setting is provided in extensions or built into core (though for now the list is just built into core as mentioned above), returns setting value or its default if it doesn't have a value
If setting is not provided anywhere, returns setting value if it has one or throws if it doesn't have a value

Should we revert this and say defaultValue parameter can be a backup for the extension-provided default? I think it would be nice never to have to worry about if a setting exists
YAGNI. We can do something like this if we need it one day for React stuff. Extensions should define their own settings and depend on extensions whose settings they absolutely need. We can figure something out for optional dependencies if we want. Maybe add a new papi.settings.tryGet or something that returns an object with success and the value

Note: intentionally not adding hasSetting(key) because the use case isn't clear and it could cause race condition issues. Just try/catch getSetting if you're unsure if a setting is available until we find a very good reason to do otherwise.
Depends on #502

Closed - merged into #502 as this is trivially more work, and it would be a waste of time to create the other api then remove it to add this one.


Implement an example with a transition

So does this mean transitions are possible with the current version? If yes, can you please just point to the entry of the API that supports transitions? It would be cool! :)


Chromap read format

Submitting this as a draft
Removing correcting and trimming
Removing "no_align" pipeline mode
Adding get_read_format task prior to Chromap
Not sure if we need to add any additional logic
Not sure if it would make more sense to have the read format task input be fastq_barcode[0] instead of read2[0]
Would appreciate feedback on task name, variable names, structure or anything else

why STARsolo doesn't need to have the parameters updated?

You mean for specifying where the barcodes are? For STARsolo, I used negative indexing to specify the barcode positions; since it's indexing from the end, the R2 read length doesn't matter. But it makes sense that we might want to pass in our own read_format, I'll try to make the STARsolo task accommodate that

Made suggested changes (tee, get_chromap_read_format, fastq = fastq_barcode[0]).
I changed the logic in subwf_atac so that task_chromap_read_format is called if chemistry=='shareseq' AND read_format is not defined, so that we can pass in custom a read_format for SHARE. I set the default value of read_format to "bc:0:-1,r1:0:-1,r2:0:-1" in the chromap task (would be used for 10X).
I added a soloCBposition input for STARsolo and set the default value to be the string we use for specifying the SHARE barcodes. The default should be ok since we don't use soloCBposition when we run STARsolo on 10X.
Tested both chromap and STARsolo, ran successfully


<path> in Svelte is improperly transpiled

I am interested in helping provide a fix!
Yes
Which generators are impacted?

[ ] All
[ ] Angular
[ ] HTML
[ ] Qwik
[ ] React
[ ] React-Native
[ ] Solid
[ ] Stencil
[X] Svelte
[ ] Vue
[ ] Web components

Reproduction case
https://mitosis.builder.io/?outputTab=M4NwpgNgLmQ%3D&code=KYDwDg9gTgLgBAE2AMwIYFcA29noHYDGMAlhHnALICeAwhALaR7B4wAUAlHAN4BQccKMBjoo5NvwFwAPAGcAbgHM4IepjyyAvACIAFjBhgAXAHoTAd0sA6cwGYr0RSYBMABncmFi7XGTFMmDp4ZMA%2B8sTA5gBCECA6rnAJzgAscCk%2BsjBQEADWwAC05sQIMLo6AIxWAKwZWbnAOgSiQqx0mNDaAHySUjJgqKVwmdl5%2BZjEzASoYDrZ%2BAi1IwXjzABWEBOzEPM%2BCDoUzuVwABxWzlUErvnOVsnHVddWrgCcz%2FnJ1e9WAGzHx18PSrPWxVRL5exVZ4AdjglXKzm%2BX1s8LSVihtls%2BTR5UBP1cUMetihBJu6MxH2RmNJGJoVSsR3sUNBtjgdKh32ZJzOFwSULOzjgz1hAqF8Nkbw%2BUOOgvy8IAXj4TN1etJPEplXAOABuXgAXyAA%3D%3D%3D
Expected Behaviour
The output of <path> element should be:
<path
  stroke-linecap="round"
  stroke-linejoin="round"
  d="M21 8.25c0-2.485-2.099-4.5-4.688-4.5-1.935 0-3.597 1.126-4.312 2.733-.715-1.607-2.377-2.733-4.313-2.733C5.1 3.75 3 5.765 3 8.25c0 7.22 9 12 9 12s9-4.78 9-12z"
/>

Actual Behaviour
Mitosis outputted <path> element as <svelte:component this={path}>.
<svelte:component
  this={path}
  stroke-linecap="round"
  stroke-linejoin="round"
  d="M21 8.25c0-2.485-2.099-4.5-4.688-4.5-1.935 0-3.597 1.126-4.312 2.733-.715-1.607-2.377-2.733-4.313-2.733C5.1 3.75 3 5.765 3 8.25c0 7.22 9 12 9 12s9-4.78 9-12z"
/>

Additional Information
No response

Ah, we are checking against a list of valid HTML tags here: https://github.com/BuilderIO/mitosis/blob/2ec674ade37d0e1db19df5ebd4130c9d78fb4fc2/packages/core/src/generators/svelte.ts#L160
However, this list does not include SVG tags! We need to add a hardcoded list of SVG tags (you can get the complete list of SVG tags from here: https://developer.mozilla.org/en-US/docs/Web/SVG/Element#svg_elements_a_to_z), and then add a check that the list does not include the json.name


Move drafts in folders to drafts in user when folder published

Description

Currently the action is to delete drafts but we should keep them for the user
DoD (Definition of Done)

Drafts are move from folders to user drafts when folder publish
Testing

unit and integration tests

this functionality makes more sense in front-end.


Adding StompAMQ interface

Benjamin, can you remind me what's the stomp version you're using? We may need to update this spec (I'll take care of that):
https://github.com/cms-sw/cmsdist/blob/comp_gcc493/py2-stomp.spec
Moreover, can you please squash all these commits in a single one?

I was testing with the latest version (stomp.py 4.1.15).
For squashing, do you want me to open a new PR or force push here? I also just learned that you should actually be able to "squash & merge" directly on Github: https://github.com/blog/2141-squash-your-commits

There is no need for a new PR. You'll basically merge them all together and push only one commit.
See the procedure here: http://blog.steveklabnik.com/posts/2012-11-08-how-to-squash-commits-in-a-github-pull-request
This "squash & merge" from GH is kind of evil because if you (e.g. Eric :)) are tracking this repo with some graphical tools (like sourceTree), then you cannot see when this branch got merged into master.

Ok, done.

@stiegerb can you please add these import statements as suggested above?
I discussed this with Seangchan and even if we're not using it - yet - it's safer to add it now to get used to python3 behavior.

Ok, done.

Thanks Benjamin, I am merging this. If you get a chance, could you created the unit test for it.
Not sure how it would test though without revealing any secrets (user id, etc) or connecting production service. Maybe some kind of emulator? #7473

Thanks Seangchan. I can have a look at the unittest, but it will probably have to wait until January.

For the record, I was trying to build stomp rpms with 4.1.15 but that's failing because the source code cannot be found in pypi. I suggest we use what we have already in the repo (3.1.3) and in case of issues, then we try to update it.
BTW, ASO uses stomp, so we need to ping them in case we update that package.

Ok, this might be an issue.
I tested with stomp.py 3.1.7 (the closest to 3.1.3 I could find on pypi), and the interface changed a bit. I fixed it to run with that version and tested it a bit, see here:
https://github.com/stiegerb/WMCore/commit/ed1a0f7853149063a3705a9f21e084c384f0e763
We'll have to decide which version of stomp.py we want to use.