Password Validation improvements

WHY
BEFORE - What was wrong? What was happening before this PR?
Backpack\CRUD\app\Http\Controllers\Auth\RegisterController has a min password length of 6
Backpack\CRUD\app\Library\Auth\ResetsPasswords.php has a min password length of 8
NIST recommends a min password length of 8. laravel also use a min password length of 8 now by default
As an admin, we should also have stronger password requirements, like disallowing compromised passwords
https://laravel-news.com/password-validation-rule-object-in-laravel-8
AFTER - What is happening after this PR?
min password length to be 8 on RegisterController
bump min laravel to 8.39
Use the uncompromised() rule.
HOW
How did you achieve that, in technical terms?
See the changes in the code
Is it a breaking change?
There might be a tiny chance the user cannot upgrade from laravel 8.26 to 8.39
the uncompromised rule also makes a network call and might be inconvenient in local development if you are on a plane testing registration and resetting password. It is also common to use easy to guess passwords during local development. However that would be so unlikely.
https://haveibeenpwned.com/API/v3#PwnedPasswords
How can we test the before & after?
Just use the register and reset password feature in backpack
Side Thoughts?
Instead of doing Password::min(8)->uncompromised() we might want to use Password::defaults() to use the user password rules they defined in AuthServiceProvider boot method if they defined it. The ->rules() u see in the code example below requires laravel 8.87 however. While Password::defaults() exist since laravel 8.42
https://laravel.com/docs/8.x/validation#defining-default-password-rules
https://github.com/laravel/framework/commits/8.x/src/Illuminate/Validation/Rules/Password.php
// AuthServiceProvider
public function boot(): void
{
        Password::defaults(function () {
            $rule = Password::min(8);

            return $this->app->isProduction()
                ? $rule
                    ->uncompromised()
                : $rule;
        });
}

Then in our validation rules. (Note that the ->rules() method is only added in 8.78)
[
    'required',
    'confirmed',
    'min:8',
    Password::defaults()->rules([ // The extra ->rules() method is added in laravel 8.78
        'additional-rules-we-might-want-to-enforce-for-the-password-field-like-uncompromised'
        'or it might be a bad idea',
    ]),
]

After giving it some thoughts I decide to change the rules to
['required', 'confirmed', 'min:8', Password::defaults()]
I also bumped the min laravel to 8.78 even though Password::defaults is added in 8.42
Reason for that is so that people can use the ->rules() method too like the example below
public function boot(): void
{
    Password::defaults(function () {
            $rule = Password::min(8);

            return $this->app->isProduction()
                ? $rule
                    ->uncompromised()
                    ->rules([
                       new ZxcvbnRule([
                           request('email'),
                           request('name'),
                      ]),
                   ])
                : $rule;
        });
}

I agree with this, but it's kind of a breaking change, so we can only do it in v6, I'm afraid (end-of-year). I'll move it there.
Until then, I'll ask @pxpm to double-check this.
Thanks @ziming !

could it be included if we do some if check on laravel/framework version?
see:
https://getcomposer.org/doc/07-runtime.md

@ziming yes, we can add checks for Laravel version and get this. I am not much in favor of version constrains in code unless is something that completely breaks the app if not done.
I am also holding to bump laravel version to fix spatie/laravel-tags conflict.
I 100% agree with this, but not sure we should add version constrains in code for this scenario at this time.

laravel 8.75 has a security patch for blade. would that be enough incentive to bump the minimum?
https://github.com/laravel/framework/security/advisories/GHSA-66hf-2p6w-jqfw

Totally. But let's do that as a separate PR please - that's a non-breaking change, while this PR is not.

About the PR here: I don't think this change (stronger password) is worth polluting the code and documentation with conditionals. It's a breaking change, we treat it as such and push it on the next major version.
This also forces you to ask yourself: is this important enough to launch a new version right away? And the answer is no, no it's not 😀 Kinda neat, right?

I'm a little confused here. If the minimum laravel is bumped, then conditionals are not necessary anymore.

If we bump the version and only account for the password rule it will be non-breaking I guess.

Pedro expressed this much better than I could, sorry 😀

Hmm I don't really see it as a breaking change since existing users won't feel it while new users who register will never know the password min length used to be 6 and is now 8
But okay I changed the min password length for RegisterController back to 6. 👍🏻

Hey @ziming!
Thank you for the PR, in my opinion this is a MUST 👌
In the between, I added a commit because there was a PHP error, Password class was being imported twice, from different sources. So I renamed the new one, here: https://github.com/Laravel-Backpack/CRUD/pull/4442/commits/2c71a479be2993934abdb3414422de70471ff970

@tabacitu, idea;
Should backpack help on it? Maybe it would be a nice thing to have it on configs.
configs/backpack/base.php
'password_validation' => [
    // 'min:8',
    // 'mixedCase',
    // 'uncompromised',
],

If devs uncommented the rules (if array length > 0) we would automatically assign this rules to the password defaults. (prod env only) They would be able to do it them self anyway.
Making it easy for devs to secure their backends is a super nice thing to have, I think 🤷♂

Let's do this:

[ ] let's add a new config option to base.php like Antonio suggested here; but for ALL env, not only prod; notice the Password::defaults() are commented out; that's in order for this to be a non-breaking change in 100% use cases;
[ ] let's fix the inconsistency and have both files use min:8 (that will get fixed automatically when we use the config above);

That way, we have the best of both worlds:

if the dev wants to customize the password rules for the admin only, they can, by changing the config;
if the dev wants to customize the password rules for both admin and user, they can, by changing the config;
if the dev wants nothing, they get nothing 😀 by default;

Hi,
I added the password_validation_rules config to base.php under Authentication Section
in RegisterController and ResetsPassword I changed to use ...config('backpack.base. password_validation_rules')
This is PHP 7.4 syntax but if you all want to support the EOL PHP 7.3 then feel free to change to use array_merge()
I did not test this but 1 thing I'm wondering is, can you use request() inside config files? Since some people might want to do Zxcvbn or other kinds of password validation that takes into account the value of other inputs like email or name to ensure the password is not too similar to it.

Okay pushed, it's almost 2 am here now.
Here is an explanation of how it works
1st change: config('backpack.base.password_validation_rules') is no longer an array
This is because most password rules on the Password class are not static methods. They need to be chained after min(), required(), sometimes(). If people still need to tag on new rules, they can do something like Password::min(8)->rules([])
2nd change: Creation of a Backpack class to configure the backpack default password rules.
If we look at official laravel packages like Telescope, Horizon, Passport. you would see that configurations are not only done in the config files. But also through static methods you can call on Telescope class, Horizon class and Passport class in your own ServiceProviders boot() method.
https://laravel.com/docs/9.x/passport#main-content
https://laravel.com/docs/9.x/horizon#main-content
https://laravel.com/docs/9.x/telescope#main-content
So if a backpack user want to do more granular customizations, she can do something like this
class MyOwnBackpackServiceProvider
{
    public function boot()
    {

        // Laravel runs the the core and packages service providers first.

        // Backpack::passwordRulesDefaults(
              // Password::min(8)
              //    ->uncompromised()
              //    ->when($this->app->isProduction()
        // );

        Backpack::passwordRulesDefaults(function () {
            $rule = Password::min(8);

            return $this->app->isProduction()
                ? $rule
                    ->uncompromised()
                : $rule;
        });
    }
}

But if the user do not define Backpack::passwordRulesDefaults() in their own service provider, then backpack loads the one from config, as seen in BackpackServiceProvider boot() method. The code in passwordRulesDefaults() and passwordRulesDefault() are pretty much the same as Laravel Password::defaults() and Password::default() with some slight modifications.
I think in the future more things could be move to this new Backpack class too, such as license check as can be seen here
https://github.com/spatie/laravel-medialibrary/blob/main/src/Support/MediaLibraryPro.php

Sorry guys, but I have to shut this down.
@ziming , very sorry for all the time you spent on this, but... I think we should stop searching for a solution for this. This current implementation is by far the cleanest (great job 👏👏👏) but it introduces a new level of configuration, that

is unlike anything we have currently, so it won't be intuitive;
is not scalable, since every new configuration at the boot level will require us to have a new call in our ServiceProvider;

We might introduce something like that in the future (good idea), but not as a side-effect of this minor problem we're solving here. We don't make architecture changes to solve minor bugs... that's a sure way to get to bloat. IF that solution has value, we should talk about it in a different thread, think cost vs benefits, and do then maybe do it. With this fix being a sideeffect. But not the other way around.
In the context of:

Authentication most likely becoming a separate package in v6 or v14;
This being a COULD DO (not a SHOULD, not a MUST);
Us having spent hours and hours on this already;
All solutions we found so far being either too intrusive or overengineered;
The benefit for this feature being minimal, for very very few Backpack devs;

I have to put an end to this, sorry. Don't get me wrong. I'm sympathetic to those who want to customize their password rules. We can create a tutorial for them on how to do that, by extending the classes - please do create that tutorial. And create a separate PR that makes both validations min:8. But going through all this trouble... for such a small feature that so few developers need... this is not worth it, sorry. Let's KISS.
I'm sorry I haven't seen this before, or said anything of this nature before, and have let you spend all this time on it. I should have put a stop to this earlier, or tell you in clear words - "be careful, this is not KISS, it looks like a slippery slope and we've already spent too much time on this". That's my failure, as the decision-maker here, to warn you about that.... I'm sorry, I know this must be frustrating. In the future, let's follow a new rule: If it's a COULD-DO... and it takes more than 1-2h to do... we don't do it. It becomes a WON'T DO. That should stop us from working on problems that aren't worth fixing. Again, I'm sorry for this mistake of mine, for letting you guys work on it for so long just to result in a "won't merge" 🙏
Let's move our focus to more important issues, please 🙏 Keep in mind that... our time is limited. Working on this prevents us from working on something more important.
Feel free to make your case if you think I'm wrong - I often am. Happy to reevaluate its importance. But the way I see it, this is a COULD, and we've already spent too much time on this. I'd rather we quit working on this and solve actual problems, that actual users face. The priority is fixing problems that >80% developers face, not 1%. Those are the problems that are worth our time.
Sorry and thank you 🙏


New Release?

There are some exciting changes that have recently been merged (multi-chain reads, typed contract calls for example). Are there any plans to cut a new release version sometime soon?

Yes, under testing now, should be as soon as this week.


Certora/specs

Testing: Certora Specs
Specific Changes
Certora spec for whitelist module, margin vault and privileged access added. Added certora to circle CI
Code

[x] Unit test 100% coverage
[x] Does your code follow the naming and code documentation guidelines?

Documentation

[x] Is your code up to date with the spec?
[x] Have you added your tests to the testing doc?

Can we use master branch for now? I don't feel like we have figured out a clear definition of master vs dev yet. (The things we discuss yesterday was just for v1 audit fix)


CNF-7347: add sriov parallel drain to RDS

Can you add a reference to the Jira epic for this update in the commit message (and this PR since it didn't get copied).
Thanks!

Hi @imiller0 sure done! :)

Hi @imiller0 let me know if we can merge this or we are waiting for something.
Thanks!

@SchSeba Why didn't you place the file into the https://github.com/openshift-kni/telco-reference/tree/main/telco-core/configuration/reference-crs/required/networking/sriov directory?


When using appcenter CLI in scripts, CLI's errors are not reported to stderr

Description
When using appcenter CLI in scripts, CLI's errors are not reported to stderr
This causes error stream logs to be missed out.
The script reports all errors to stdout
Repro Steps
Please list the steps used to reproduce your issue.

run an invalid command e.g.
appcenter distribute releases list --app <invalid-app-identifier>    1>out.txt    2>err.txt
when command complete, check the out.txt and err.txt files

Actual behavior
err.txt is empty
out.txt has the error log
Expected behavior
err.txt should have the actual error message
Details

Is there a particular beacon/command that you are having trouble with?

No, happening with all commands upon error

Which version of the App Center CLI are you using?

2.10.7

Which OS version did you experience the issue on?

Mac

What command line/shell are you using?

Shell 5.8 /bin/zsh

What version of Node.js and NPM/Yarn are you using?

node v12.22.8 (npm v6.14.15)

Additionally, you can provide verbose logs of a CLI command by using DEBUG="appcenter-cli:*" before the command, for example, DEBUG="appcenter-cli:*" appcenter apps list. Include the logs here, don't forget to omit any personal/sensitive data.

Hello @sameeragrawal and thank you for your contribution!
I've tested and merged your PR.


Notifications Page

We have a link for All Notifications, but the page is empty.  We should probably have some basic list of placeholder notifications displayed on that page.

I want to be assigned to the task.
I'm getting started


camera = picamera.PiCamera issue

When I run the command "camera = picamera.PiCamera()" in either Python, Python3, or as part of a program, I keep getting this message:
Traceback (most recent call last):
  File "<pyshell#3>", line 1, in <module>
    camera = picamera.PiCamera()
  File "/usr/lib/python3/dist-packages/picamera/camera.py", line 489, in __init__
    self._init_defaults()
  File "/usr/lib/python3/dist-packages/picamera/camera.py", line 647, in _init_defaults
    prefix="Failed to get annotation test")
  File "/usr/lib/python3/dist-packages/picamera/exc.py", line 191, in mmal_check
    raise PiCameraMMALError(status, prefix)
picamera.exc.PiCameraMMALError: Failed to get annotation test: Function not implemented

"python3" is "python" when running that version. I have the latest updates and everything as far as I can tell. Camera is also enabled. Can't get past this error. Hope you can help. Thanks.

Is raspivid/raspistill working ? Also, are you using raspbian ?
If you could post the output of uname -a (You can take a look at Firmware Upgrade Section

This sounds like you're running a very old firmware - as André mentioned, upgrading firmware ought to fix it.

Closing old issues; feel free to re-open if you have any further queries about this!


Add NextAuth support to ssx-react

Description
This PR adds support for NextAuth to ssx-react and a corresponding example (ssx-test-nextauth). This PR touches a lot of things! Changes include creating new packages, refactoring ssx-server, and updating ssx-react. Some of the changes were made while debugging next stuff, but were not the eventual solution. I left them in for refactor purposes. I'll highlight them! Please comment on any refactor changes as well as new packages.
Updated packages:

ssx-core
ssx-server
ssx-react

New Packages

ssx-server-middleware

Type

[x] New feature (non-breaking change which adds functionality)

Diligence Checklist

[x] This change requires a documentation update
[ ] I have included unit tests
[ ] I have updated and/or included new integration tests
[ ] I have updated and/or included new end-to-end tests
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

Codecov Report
Base: 71.78% // Head: 72.03% // Increases project coverage by +0.24% :tada:

Coverage data is based on head (b17cdd8) compared to base (24a7220).
Patch coverage: 71.78% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #49      +/-   ##
==========================================
+ Coverage   71.78%   72.03%   +0.24%
==========================================
  Files          24       25       +1
  Lines        3190     3325     +135
  Branches      191      194       +3
==========================================
+ Hits         2290     2395     +105
- Misses        900      930      +30

Impacted Files
Coverage Δ

packages/ssx-sdk/src/core.ts
24.15% <0.00%> (-2.23%)
:arrow_down:

packages/ssx-server-middleware/src/index.ts
100.00% <ø> (ø)

packages/ssx-core/src/types.ts
99.64% <93.33%> (+0.01%)
:arrow_up:

packages/ssx-core/src/index.ts
100.00% <100.00%> (ø)

packages/ssx-core/src/server/types.ts
100.00% <100.00%> (ø)

packages/ssx-sdk/src/ssx.ts
55.30% <100.00%> (ø)

...ges/ssx-server-middleware/src/express/endpoints.ts
89.34% <100.00%> (ø)

...ackages/ssx-server-middleware/src/express/index.ts
100.00% <100.00%> (ø)

...es/ssx-server-middleware/src/express/middleware.ts
71.54% <100.00%> (ø)

packages/ssx-server-middleware/src/http/index.ts
62.58% <100.00%> (ø)

... and 2 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Since this is an implementation for NextAuth, not Next in general, shouldn't we switch references to NextAuth? Example: ssx-react/next/frontend -> ssx-react/next-auth/frontend


Add randomPath utility function to SoundEntriesRecord

This adds a useful utility function to SoundEntriesRecord that handles randomising the path used to for a sound

Closed as I accidentally created the branch off of the M2Camera branch. I've created #111 to properly split the commits up


Timeout searching for location on Android (Nativescript 3.0.3)

I saw issues reported on forum and this repository about issues on reading location on Android on NS3.0. I just want to report that it also not working on Nativescript Sample application.
Steps to reproduce:

Clone the NS sample app repo (https://github.com/NativeScript/nativescript-sdk-examples-ng)
run tns install
run tns run android --emulator
go to the location sample and click read current location

The plugin runs fine on iOS.
Attached please found the screenshot for your reference.
Versions:
│ Component        │ Current version │ Latest version │ Information │
│ nativescript     │ 3.0.3           │ 3.0.3          │ Up to date  │
│ tns-core-modules │ 3.0.1           │ 3.0.1          │ Up to date  │
│ tns-android      │ 3.0.1           │ 3.0.1          │ Up to date  │
│ tns-ios          │ 3.0.1           │ 3.0.1          │ Up to date  │
Hope this can help and let me know if need any further information.
Regards
Clarence

same thing happening with me. any help ?

I noticed that sometimes the internet connection type may cause this problem so try to change internet provider.

Hi @clarenceh, looking at the sceenshots I see that you are running the app on emulator. You might check the Location options/settings/controls of the emulator if you can "Send" location to the device like the Android emulator for Mac:

Do you guys get the same exception when running the app on a physical device?

Got the same problem. I don't think it has anything to do with emulator tho 😕

I get the same error. iOS is working but Android unfortunately not.

Has anybody found a solution for this issue on Android? I am still getting the following "JS: Error: Timeout while searching for location!"

@tbozhikov Sorry for my late reply. Yes I can send location to the emulator. I opened Google Map, and then in emulator's location setting, change the value for latitude and longitude, and the location on the map was updated successfully. Have you had a chance to check out the NS Angular examples and test it out as I mentioned in my message? I believe you will be able to re-produce this. Many thanks, Clarence

Got the same issue here. Tested on many emulators and many real devices.
Last one is on Android 7.0, wifi - network - gps enabled. Timeout on location almost anytime.
Using version 3.0 of the plugin
As for my dependencies:
┌──────────────────┬─────────────────┬────────────────┬─────────────┐
│ Component        │ Current version │ Latest version │ Information │
│ nativescript     │ 3.1.3           │ 3.1.3          │ Up to date  │
│ tns-core-modules │ 3.1.0           │ 3.1.0          │ Up to date  │
│ tns-android      │ 3.1.1           │ 3.1.1          │ Up to date  │
│ tns-ios          │ 3.1.0           │ 3.1.0          │ Up to date  │
└──────────────────┴─────────────────┴────────────────┴─────────────┘

Hi @jeremypele , i have error same thing, i fix with open Location( or GPS ) of device choose Location Mode is a Hight accuracy. A reason is your device auto turn on Battery saving move or Device only mode. it is slow in get location from GPS. that plugin working with android and ios with me, i think it not a prolem.
Hope this will help...

@LeCaoPhuc Regarding the different tests I've done this weekend: on a real device it works well when data is active. If gps + wifi are active then it's not working well - event if accuracy is set to the highest on device settings

@jeremypele  your mean is in real device, if you use data (3g,4g) and turn on gps then you always get location. but if use wifi to connect internet, location will slow and time out if accuracy not in highest .

same thing happening with me. any help ?

Same problem for me on real Galaxy S7 with Android 7.

Hi have this problem on my Samsung A5

Hi guys, please try to set the "desiredAccuracy" option to "Accuracy.high" (see https://docs.nativescript.org/hardware/location#getcurrentlocation).
That solved the problem for me 👍

I have tried it and nothing changed
On Aug 19, 2017 1:16 PM, "Fabian F."<EMAIL_ADDRESS>wrote:

Hi guys, please try to set the "desiredAccuracy" option to "Accuracy.high"
(see https://docs.nativescript.org/hardware/location#getcurrentlocation).
That solved the problem for me 👍
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/NativeScript/nativescript-geolocation/issues/62#issuecomment-323514598,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACGJaNBxmjg5KFaN1oJcCpTIUryDUyQoks5sZrYWgaJpZM4Nw1CF
.

I had the same problem as described. Apparently first you have to call .watchLocation();
I am using my device (XiaoMi 5S) directly without emulator.
So here is what I did (I practically called .getCurrentLocation(...); and .clearWatch(watchId); after .watchLocation();:
function buttonGetLocationTap(args) {
    if (!geolocation.isEnabled()) {
        geolocation.enableLocationRequest();
    }

    watchId = geolocation.watchLocation();

    var location = geolocation.getCurrentLocation({desiredAccuracy: 3, updateDistance: 5, timeout: 2000}).
    then(function(loc) {
        if (loc) {
            console.log("Latitude " + loc.latitude);
            console.log("Longitude " + loc.longitude);
            console.log("Altitude " + loc.altitude);
            console.log("Horizontal Accuracy " + loc.horizontalAccuracy);
            console.log("Vertical Accuracy " + loc.verticalAccuracy);
            console.log("Speed " + loc.speed);
            console.log("Direction " + loc.direction);
            console.log("Timestamp " + loc.timestamp);

            if (watchId) {
                geolocation.clearWatch(watchId);
            }
        }
    }, function(e){
        console.log("Error: " + e.message);
        if (watchId) {
            geolocation.clearWatch(watchId);
        }
    });
}
exports.buttonGetLocationTap = buttonGetLocationTap;

Hope it helps.
Regards!

Per TinoN's suggestion, I added this before my call to getCurrentLocation and it works.  Note, this is the typescript version:
let watchId = watchLocation(x => this.lastLocation = x, x => console.log(x), null);

@toeknee581 I checked it again with my phone. It worked in the office where I have WiFi. As soon as I left the building and had only access to mobile network it didn't work. On my mobile phone I switched the phone location settings from "High accuracy" to "Device only" to force GPS only usage. The data was then most of the time retrieved reliably (sometimes the phone GPS couldn't be accessed...). But when I came back to my office I switched back the phone settings to "High accuracy" to make sure that GPS, WiFi or Mobile can be used to determine location. From then on it stopped working in the office.
So I agree with you, it is not working reliably and I also can't reproduce when it is working and when not...

Hello,
I still was not able to get it to work. And I also couldn't figure out, what the actual problem in the nativescript-geolocation code might be. (too many callbacks for me :))
Therefore based on the nativescript-geolocation code I tried figuring out how to actually trigger the GeoLocation update for my android phone.
You can see the result here.
You can see the usage of the Android API directly and trigger requestSingleUpdate(...) and requestLocationUpdates(...).
Any comments, suggestions and/or questions are very welcome.
Regards!

@TinoN1e unfortunately your code doesn't work on my phone Android 5.1 (I changed your permission function to fit my API level).
to clarify more about this issue: actually everything works fine with nativescript-geolocation in emulator when "Send" button inside emulator pressed. but I tried the same code on real devices with different android versions but no result with COARSE or FINE, watch or single update... I traced nativescript-geolocation completely and nothing is wrong here. also I wrote an example app like @TinoN1e to work directly with android APIs but it doesn't work neither. so I think maybe something is wrong with nativescript code or android runtime. I didn't try Fused Location API on android. maybe this works rather than using location manager. I will try it tomorrow and share the results.

I am also having the Timeout issue. I am using "nativescript-geolocation": "^3.0.1",

And on a real device too..

Same thing here, either with emulator (x86 with Google APIs) or using a real device (tested with Huawei TAG-L21 and Samsung J3). Regardless of the accuracy or using data vs wifi, never works and always have timeout errors as below. Send option on emulator has the same result.
"tns-core-modules": "3.1.1",
"nativescript-geolocation": "^3.0.1",
"tns-android": {
"version": "3.2.0"
}
{
	"originalStack": "Error: Timeout while searching for location!\n    at ZoneAwareError (file:///data/data/org.nativescript.GeoLocationApp/files/app/tns_modules/nativescript-angular/zone-js/dist/zone-nativescript.js:993:33)\n    at file:///data/data/org.nativescript.GeoLocationApp/files/app/tns_modules/nativescript-geolocation/geolocation.js:232:31\n    at invoke (file:///data/data/org.nativescript.GeoLocationApp/files/app/tns_modules/tns-core-modules/timer/timer.js:19:48)\n    at ZoneDelegate.invoke (file:///data/data/org.nativescript.GeoLocationApp/files/app/tns_modules/nativescript-angular/zone-js/dist/zone-nativescript.js:365:26)\n    at Object.onInvoke (file:///data/data/org.nativescript.GeoLocationApp/files/app/tns_modules/@angular/core/bundles/core.umd.js:3965:37)\n    at ZoneDelegate.invoke (file:///data/data/org.nativescript.GeoLocationApp/files/app/tns_modules/nativescript-angular/zone-js/dist/zone-nativescript.js:364:32)\n    at Zone.runGuarded (file:///data/data/org.nativescript.GeoLocationApp/files/app/tns_modules/nativescript-angular/zone-js/dist/zone-nativescript.js:138:47)\n    at file:///data/data/org.nativescript.GeoLocationApp/files/app/tns_modules/nativescript-angular/zone-js/dist/zone-nativescript.js:116:29\n    at Object.run (file:///data/data/org.nativescript.GeoLocationApp/files/app/tns_modules/tns-core-modules/timer/timer.js:23:13)",
	"zoneAwareStack": "Error: Timeout while searching for location!\n    at file:///data/data/org.nativescript.GeoLocationApp/files/app/tns_modules/nativescript-geolocation/geolocation.js:232:31 [angular]\n    at invoke (file:///data/data/org.nativescript.GeoLocationApp/files/app/tns_modules/tns-core-modules/timer/timer.js:19:48) [angular]\n    at Object.onInvoke (file:///data/data/org.nativescript.GeoLocationApp/files/app/tns_modules/@angular/core/bundles/core.umd.js:3965:37) [angular]\n    at file:///data/data/org.nativescript.GeoLocationApp/files/app/tns_modules/nativescript-angular/zone-js/dist/zone-nativescript.js:116:29 [<root>]\n    at Object.run (file:///data/data/org.nativescript.GeoLocationApp/files/app/tns_modules/tns-core-modules/timer/timer.js:23:13) [<root>]",
	"__zone_symbol__currentTask": {
		"type": "microTask",
		"state": "notScheduled",
		"source": "Promise.then",
		"zone": "angular",
		"cancelFn": null,
		"runCount": 0
	}
}

I finally succeeded to get the GPS work
I took Tino's code and made some improvements on it, because it was not locating me correctly.
I also noticed, that if you move a little bit in the offices, the location change event can be triggered, which will then give you the correct geolocation data.

As there are a lot of issues with the Android Location Manager and it's not the recommended approach for getting a location on Android, we fully replaced the Android implementation with the Google Play Location Service one (used by Google Maps).
The change is currently on a pull request and we are still testing some edge cases. However, you could check if your issues are resolved using the tachev/location-manager-to-google-play-services branch.

@DimitarTachev I tried your branch and still I get timeout.

today I tested the same app on iOS 11 and I get timeout there too. so the problem is not related to Android side. maybe a Nativescript runtime issue?

@DimitarTachev @mohammadrafigh  Using your branch and the corresponding demo on Lenovo A6010 Android 5.0.2 I was able to get location using gps service.

@mohammadrafigh Regarding iOS, be sure you have wifi on. This seems to fix it on my side but I guess this should be a separate discussion for another issue related to iOS.

We closed the issues as the Android implementation is fully replaced by a new one and we are not able to reproduce the timeouts anymore.
You could take a look at the 4.0.0 release notes here.

ah nice. I can now confirm that the issue is fixed on Android. I don't know why in previous try I got timeout. but now everything works fine. thanks @DimitarTachev .

I'm also getting this.
Tried everything, including the watchLocation trick, but it doesn't solve the issue.
Any idea?

Bump. I get the same issue even in latest version 4.2.1

I am getting the same error with version 4.2.2.  I also tried the watchLocation trick.

Hi @guestisp, @scottmcmu,
Thank you for contacting us.
We reviewed your case, however, we were unable to recreate an issue with the getCurrentLocation method, while using the latest version of the plugin 4.2.2.
Regarding that, it would help if you could open a new issue, where you could provide the following info:

NativeScript CLI versions
tns-core-modules versions
tns-android versions
tns-ios versions
node versions
npm versions
sample project, which could be used for debugging
exact steps which you are using while building the project

This info will help us to recreate the issue and to verify if there is a real problem.
Thank you in advance for your cooperation.

@tsonevn i've opened a new issue

I figured out that if you follow the tutorial it is actually incorrect. At least now it currently says to use:
const Geolocation = require("nativescript-geolocation");
const Accuracy = require("tns-core-modules/ui/enums");
...
Geolocation.getCurrentLocation({
            desiredAccuracy: Accuracy.high,
            updateDistance: 0.1,
            timeout: 20000,
          })

However I realized that Accuracy should be imported as:
const { Accuracy } = require("tns-core-modules/ui/enums");

if you want to use it that way. Or if you don't change your import statement you can use: Accuracy.Accuracy.high on the desiredAccuracy.

I have this error, i add timeout 0 for resolve the problem
Geolocation.getCurrentLocation({desiredAccuracy: Accuracy.high,  timeout: 0 })

@youtpout answer worked for me,
On android emulator the only configuration for geolocations actions (watch and get) is setting
{
desiredAccuracy:3
}
If you use anything else will throw an exception for timeout, putting timeout:0 works for another desiredAccuracy value,,,

I try on real device


Predetory Journals

I think for predatory Journals, we are not creating a new list, many already exist. We can just point them to these lists:

https://predatoryjournals.com/journals/
https://beallslist.net/

They are regularly updated. We can just include a short paragraph on what they are and how to spot them.

I will work on this task


can not install 2.2.1

1  ~/download/Mancy-2.2.1
npm i
npm WARN deprecated<EMAIL_ADDRESS>react-tools is deprecated. For more information, visit https://fb.me/react-tools-deprecated
npm WARN deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained. Upgrade to<EMAIL_ADDRESS>npm WARN deprecated<EMAIL_ADDRESS>this package has been reintegrated into npm and is now out of date with respect to npm
npm WARN deprecated<EMAIL_ADDRESS>This package has been renamed. Use<EMAIL_ADDRESS>npm WARN prefer global<EMAIL_ADDRESS>should be installed with -g
npm WARN prefer global<EMAIL_ADDRESS>should be installed with -g
npm WARN prefer global<EMAIL_ADDRESS>should be installed with -g

<EMAIL_ADDRESS>install /home/xyh/download/Mancy-2.2.1/node_modules/nslog
node-gyp rebuild

make: Entering directory '/home/xyh/download/Mancy-2.2.1/node_modules/nslog/build'
CXX(target) Release/obj.target/nslog/src/main.o
CXX(target) Release/obj.target/nslog/src/nslog_linux.o
SOLINK_MODULE(target) Release/obj.target/nslog.node
COPY Release/nslog.node
make: Leaving directory '/home/xyh/download/Mancy-2.2.1/node_modules/nslog/build'

<EMAIL_ADDRESS>install /home/xyh/download/Mancy-2.2.1/node_modules/node-sass
node scripts/install.js

Binary downloaded and installed at /home/xyh/download/Mancy-2.2.1/node_modules/node-sass/vendor/linux-x64-47/binding.node

<EMAIL_ADDRESS>install /home/xyh/download/Mancy-2.2.1/node_modules/font-manager
node-gyp rebuild

make: Entering directory '/home/xyh/download/Mancy-2.2.1/node_modules/font-manager/build'
CXX(target) Release/obj.target/fontmanager/src/FontManager.o
CXX(target) Release/obj.target/fontmanager/src/FontManagerLinux.o
SOLINK_MODULE(target) Release/obj.target/fontmanager.node
COPY Release/fontmanager.node
make: Leaving directory '/home/xyh/download/Mancy-2.2.1/node_modules/font-manager/build'

<EMAIL_ADDRESS>postinstall /home/xyh/download/Mancy-2.2.1/node_modules/spawn-sync
node postinstall

<EMAIL_ADDRESS>postinstall /home/xyh/download/Mancy-2.2.1/node_modules/node-sass
node scripts/build.js

/home/xyh/download/Mancy-2.2.1/node_modules/node-sass/vendor/linux-x64-47/binding.node exists.
testing binary.
Binary is fine; exiting.

<EMAIL_ADDRESS>postinstall /home/xyh/download/Mancy-2.2.1/node_modules/electron-prebuilt
node install.js

<EMAIL_ADDRESS>preinstall /home/xyh/download/Mancy-2.2.1
npm prune

<EMAIL_ADDRESS>postinstall /home/xyh/download/Mancy-2.2.1
electron-rebuild && gulp clean && gulp copy

[02:01:54] Requiring external module babel-register
/home/xyh/download/Mancy-2.2.1/gulpfile.babel.js:4
var ref = _asyncToGenerator(regeneratorRuntime.mark(function _callee(api) {
^
ReferenceError: regeneratorRuntime is not defined
at /home/xyh/download/Mancy-2.2.1/gulpfile.babel.js:4:31
at Object. (gulpfile.babel.js:65:16)
at Module._compile (module.js:413:34)
at loader (/home/xyh/download/Mancy-2.2.1/node_modules/babel-register/lib/node.js:128:5)
at Object.require.extensions.(anonymous function) [as .js] (/home/xyh/download/Mancy-2.2.1/node_modules/babel-register/lib/node.js:138:7)
at Module.load (module.js:357:32)
at Function.Module._load (module.js:314:12)
at Module.require (module.js:367:17)
at require (internal/module.js:16:19)
at Liftoff.handleArguments (/home/xyh/download/Mancy-2.2.1/node_modules/gulp/bin/gulp.js:116:3)
npm ERR! Linux 4.4.1-2-ARCH
npm ERR! argv "/usr/bin/node" "/home/xyh/.npm-installed/bin/npm" "i"
npm ERR! node v5.6.0
npm ERR! npm  v3.5.3
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>postinstall: electron-rebuild && gulp clean && gulp copy
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script 'electron-rebuild && gulp clean && gulp copy'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the mancy package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     electron-rebuild && gulp clean && gulp copy
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs mancy
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls mancy
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/xyh/download/Mancy-2.2.1/npm-debug.log
1  ~/download/Mancy-2.2.1

@xieyuheng can you confirm the below npm packages are installed successfully ?
    "babel-preset-es2015": "^6.3.13",
    "babel-preset-react": "^6.3.13",
    "babel-preset-stage-0": "^6.3.13",
    "babel-plugin-add-module-exports": "^0.1.1",
    "babel-plugin-transform-runtime": "^6.3.13",
    "babel-core": "^6.3.13",
    "babel-polyfill": "^6.3.14",
    "babel-runtime": "^6.3.13",

I tryed it with another version of npm it stoped here as following ::
~/download/kkkk/Mancy-2.2.1
cnpm i

<EMAIL_ADDRESS>preinstall /home/xyh/download/kkkk/Mancy-2.2.1
npm prune

npm WARN deprecated<EMAIL_ADDRESS>react-tools is deprecated. For more information, visit https://fb.me/react-tools-deprecated

<EMAIL_ADDRESS>install /home/xyh/download/kkkk/Mancy-2.2.1/node_modules/font-manager
node-gyp rebuild

make: Entering directory '/home/xyh/download/kkkk/Mancy-2.2.1/node_modules/font-manager/build'
CXX(target) Release/obj.target/fontmanager/src/FontManager.o
CXX(target) Release/obj.target/fontmanager/src/FontManagerLinux.o
SOLINK_MODULE(target) Release/obj.target/fontmanager.node
COPY Release/fontmanager.node
make: Leaving directory '/home/xyh/download/kkkk/Mancy-2.2.1/node_modules/font-manager/build'
npm WARN deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained. Upgrade to<EMAIL_ADDRESS>
<EMAIL_ADDRESS>install /home/xyh/download/kkkk/Mancy-2.2.1/node_modules/electron-rebuild/node_modules/nslog
node-gyp rebuild

make: Entering directory '/home/xyh/download/kkkk/Mancy-2.2.1/node_modules/electron-rebuild/node_modules/nslog/build'
CXX(target) Release/obj.target/nslog/src/main.o
CXX(target) Release/obj.target/nslog/src/nslog_linux.o
SOLINK_MODULE(target) Release/obj.target/nslog.node
COPY Release/nslog.node
make: Leaving directory '/home/xyh/download/kkkk/Mancy-2.2.1/node_modules/electron-rebuild/node_modules/nslog/build'

<EMAIL_ADDRESS>postinstall /home/xyh/download/kkkk/Mancy-2.2.1/node_modules/electron-prebuilt
node install.js

<EMAIL_ADDRESS>postinstall /home/xyh/download/kkkk/Mancy-2.2.1/node_modules/node-sass/node_modules/cross-spawn/node_modules/spawn-sync
node postinstall

|

<EMAIL_ADDRESS>install /home/xyh/download/kkkk/Mancy-2.2.1/node_modules/node-sass
node scripts/install.js

Binary downloaded and installed at /home/xyh/download/kkkk/Mancy-2.2.1/node_modules/node-sass/vendor/linux-x64-47/binding.node

<EMAIL_ADDRESS>postinstall /home/xyh/download/kkkk/Mancy-2.2.1/node_modules/node-sass
node scripts/build.js

/home/xyh/download/kkkk/Mancy-2.2.1/node_modules/node-sass/vendor/linux-x64-47/binding.node exists.
testing binary.
Binary is fine; exiting.

<EMAIL_ADDRESS>postinstall /home/xyh/download/kkkk/Mancy-2.2.1
electron-rebuild && gulp clean && gulp copy

[02:32:08] Requiring external module babel-core/register
[02:32:44] Using gulpfile ~/download/kkkk/Mancy-2.2.1/gulpfile.babel.js
[02:32:44] Starting 'clean'...
[02:32:44] Finished 'clean' after 124 ms
[02:32:46] Requiring external module babel-core/register
[02:33:19] Using gulpfile ~/download/kkkk/Mancy-2.2.1/gulpfile.babel.js
[02:33:19] Starting 'watchableCopy'...
[02:33:20] Finished 'watchableCopy' after 787 ms
[02:33:20] Starting 'copy'...

I also tryed Mancy-linux-x64.zip here :: https://github.com/princejwesley/Mancy/releases/tag/v2.2.1
but nothing happened when I open ./Mancy

@xieyuheng Yes, run npm run package after npm install and run from dist directory
If you don't want to build from source, try npm install -g mancy

I also tryed npm install -g mancy
but after I open mancy
I can not see the window (even after a long time)
my friend is meeting the same problem as me
thanks for your reply
I am trying to test more

@xieyuheng let me check from my linux box.

thanks :)
I really wish to be able to use mancy

@xieyuheng prebuilt exe has issues. Try npm install and wait till Starting 'copy'... task is completed. Run npm run package and run ./dist/Mancy-linux-x64/Mancyfrom/home/xyh/download/Mancy-2.2.1/`
I'll fix the executable and upload it.

oh I will try the previous version first

I can run 2.1.0
but in 2.2.0 I meet the same problem
I will use 2.1.0 for now
thanks

@xieyuheng Updated executable for linux 64bit.

thanks again


Running on Raspberry Pi

Description
Attempting to run nvidia-snatcher on Raspberry Pi (raspbian buster) results in this error,
(node:10149) UnhandledPromiseRejectionWarning: Error: Failed to launch the browser process!
/home/pi/nvidia-snatcher/node_modules/puppeteer/.local-chromium/linux-800071/chrome-linux/chrome: 26: /home/pi/nvidia-snatcher/node_modules/puppeteer/.local-chromium/linux-800071/chrome-linux/chrome: Syntax error: Unterminated quoted string

TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

    at onClose (/home/pi/nvidia-snatcher/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:193:20)
    at Interface.<anonymous> (/home/pi/nvidia-snatcher/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:183:68)
    at Interface.emit (events.js:327:22)
    at Interface.close (readline.js:416:8)
    at Socket.onend (readline.js:194:10)
    at Socket.emit (events.js:327:22)
    at endReadableNT (_stream_readable.js:1220:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:21)
(node:10149) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:10149) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Possible solution
In https://github.com/jef/nvidia-snatcher/blob/0aa7ab596c907ce72c188eb4b1acdee088307437/src/index.ts#L39-L45 insert executablePath: 'chromium-browser' (based on https://github.com/puppeteer/puppeteer/issues/550#issuecomment-635718872) and re-run npm install.

Would be great if this could be configured via an optional environment variable. That would make it simpler to run on NixOS as well.

Puppeteer has an env var for this: PUPPETEER_EXECUTABLE_PATH. If using an existing Chromium installation, may also want to set PUPPETEER_SKIP_CHROMIUM_DOWNLOAD to 1 to skip Puppeteer downloading its own Chromium, wasting space.

Would be great if this could be configured via an optional environment variable. That would make it simpler to run on NixOS as well.

Puppeteer has an env var for this: PUPPETEER_EXECUTABLE_PATH. If using an existing Chromium installation, may also want to set PUPPETEER_SKIP_CHROMIUM_DOWNLOAD to 1 to skip Puppeteer downloading its own Chromium, wasting space.

Exactly this! Thanks @amarshall.


Document requirement of opening ETCD ports

Although ETCD ports are automatically opened on Ubuntu nodes, they are by default rejected on photon OS.
Need to document the requirement to use iptables to open ETCD ports if users faced cannot create etcd client error.

mustfix for vFile beta release

Closed by #1971


Can't reproduce some results of GrIPS paper.

Hi Archiki Prasad,
I want to reproduce the results of GrIPS initializing with task-agnostic instructions with Instruction-Only prompts in your paper.
With the hyperparameters in the paper which is l = 1, m = 5, n = 10, and P = 2, I have achieved the accuracy of model InstructGPT babbage in table 3, which is 54.41. However, I cannot achieve the accuracy of model GPT-2 XL in table 3, which is 54.29. My result is about 53.00.
I have tried several train seeds and different hyperparameters, but still failed to achieve the accuracy 54.29.
I need your help to reproduce the result. Could you give me some suggestions.

Can you tell me what dataset this repo uses please? I can't get the file directory 'data'


refactor: Introduce a TaskDate class

This was a suggestion from @sytone:

how about making a TaskDate class and have that deal with all the date management across the plugin.

Originally posted by @sytone in https://github.com/obsidian-tasks-group/obsidian-tasks/pull/696#discussion_r884173142
There is so much repetition in the code and tests around parsing and formatting of dates: it would be really, really good to hide all that away in a class and simplify the code.

I'm leaving this open until Task uses TasksDate for all date and time operations...
This is needed to:

Add support for times
Safety - Prevent accidental mutation of dates
See #2866


Update active-directory-aadconnect-version-history.md

Added release note for upcoming hotfix. Do not publish before 12/12/2017!

pulled this in to the private repo.  Once this is staged I will tag this to be closed.


Footer and Styles Alignment

Related Issue
None
Fixes:  #4330
Description
The Alignment of the footer contents in the footer is not aligned properly and also the changed some styles too.
Isuue Number - #4330
Type of PR

[x] Bug fix

Screenshots / videos (if applicable)
Before!!

After!!

Checklist:

[x] I have made this change from my own.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] My changes generate no new warnings.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers and screenshots after making the changes.

not looking good improve it more since it look like before footer  only @Molza01

@sailaja-adapa Ok ma'am.

I have made changes into the footer. I have done adjustment and alignment and given style to it also.
Screenshot!!
Before

After

remove the backgrd color from quick links

aisa karo . chk community spotlight page.

I have done the changes and generated an another pr #4371 .
@abhi03ruchi


Difference in using float or Function(FunctionSpace(mesh, "R", 0))?

In the newly-added bubble shear demo, I noticed that we get different solutions if I set variables  dt and theta to be floats, rather than Function(FunctionSpace(mesh, "R", 0)). That is, the uniform resolution results don't appear to change, but the adapted ones do (both classical and metric advection). Any idea why this is the case?

This commit https://github.com/mesh-adaptation/animate/commit/bfed2c2409378cdcf4069d6142403365b9feb09f also changed the solutions, where time t was changed from being a float to Function(R)

Very interesting... Even logging affects adaptive results:
(firedrake) firedrake@0241f81993fe:~/firedrake/src/animate/demos$ python bubble_shear.py
Relative L2 error on the coarse mesh: 56.52%
Relative L2 error on the fine mesh: 32.29%.
Classical mesh adaptation.
   Avg. number of vertices: 2299.5
   Relative L2 error: 30.43%
Metric advection mesh adaptation.
   Avg. number of vertices: 2008.3
   Relative L2 error: 30.58%

(firedrake) firedrake@0241f81993fe:~/firedrake/src/animate/demos$ python bubble_shear.py -log_view :foo.txt:ascii_flamegraph
Relative L2 error on the coarse mesh: 56.52%
Relative L2 error on the fine mesh: 32.29%.
Classical mesh adaptation.
   Avg. number of vertices: 2308.1
   Relative L2 error: 30.32%
Metric advection mesh adaptation.
   Avg. number of vertices: 2014.3
   Relative L2 error: 30.79%

Very interesting... Even logging affects adaptive results:

Is this with float or R-space?

Very interesting... Even logging affects adaptive results:

Is this with float or R-space?

This is on the 153_improve_bubble branch, so with R-space.

Hm, are there any other floats that might be causing an issue?

Not sure, but I'll try to make minimal examples for each of these before the next meeting so we can discuss :)

Classical adaptation results without and with logging:
(firedrake) firedrake@0241f81993fe:~/firedrake/src/animate/demos$ python bubble_shear.py
Adapted mesh 0 with 1905 vertices.
Adapted mesh 1 with 2062 vertices.
Adapted mesh 2 with 2127 vertices.
Adapted mesh 3 with 2312 vertices.
Adapted mesh 4 with 2343 vertices.
Adapted mesh 5 with 2446 vertices.
Adapted mesh 6 with 2493 vertices.
Adapted mesh 7 with 2539 vertices.
Adapted mesh 8 with 2542 vertices.
Adapted mesh 9 with 2525 vertices.
Adapted mesh 10 with 2431 vertices.
Adapted mesh 11 with 2370 vertices.
Adapted mesh 12 with 2224 vertices.
Adapted mesh 13 with 2103 vertices.
Adapted mesh 14 with 2070 vertices.

(firedrake) firedrake@0241f81993fe:~/firedrake/src/animate/demos$ python bubble_shear.py -log_view :foo.txt:ascii_flamegraph
Relative L2 error on the coarse mesh: 56.52%
Relative L2 error on the fine mesh: 32.29%.
Adapted mesh 0 with 1905 vertices.
Adapted mesh 1 with 2062 vertices.
Adapted mesh 2 with 2127 vertices.
Adapted mesh 3 with 2312 vertices.
Adapted mesh 4 with 2343 vertices.
Adapted mesh 5 with 2453 vertices.
Adapted mesh 6 with 2498 vertices.
Adapted mesh 7 with 2540 vertices.
Adapted mesh 8 with 2539 vertices.
Adapted mesh 9 with 2530 vertices.
Adapted mesh 10 with 2436 vertices.
Adapted mesh 11 with 2322 vertices.
Adapted mesh 12 with 2262 vertices.
Adapted mesh 13 with 2159 vertices.
Adapted mesh 14 with 2134 vertices.

when I compare different variables and how they change in time (e.g. mean of concentration c before and after projecting, velocity u), they all change very very slowly at the beginning, like 12th decimal point at start. So I guess this accumulates over time. I wasn't able to find the very first thing that is different and that might cause everything else to change (or maybe they all change)


New package: AlickolliSoftware.RandomNumberGenerator(UWP) version 1.0…

….0.0

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.2 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

/azp run

Hi @licon4812,
Validation failed due to a certificate error:

800B0109 A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.

I'm not sure, but I believe the certificate in the error is the msixbundle signing certificate. This is probably something that the package's developer has to fix.

Hi @licon4812,
Validation failed due to a certificate error:

800B0109 A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.

I'm not sure, but I believe the certificate in the error is the msixbundle signing certificate. This is probably something that the package's developer has to fix.

I am the developer of this application. I signed the msixbundle with a certificate generated by visual studio. Any tips on how to fix this?

Hi @stephengillie I am the developer of this application. I signed the msixbundle with a certificate generated by visual studio. Any tips on how to fix this?

Unfortunately I haven't packaged an msixbundle before. Do you have the certificate it was signed with? What other certs are on the chain, including the root?

Hi @stephengillie I am the developer of this application. I signed the msixbundle with a certificate generated by visual studio. Any tips on how to fix this?

Unfortunately I haven't packaged an msixbundle before. Do you have the certificate it was signed with? What other certs are on the chain, including the root?

I Have the certificate it was signed with

I did a quick search:
Sign a Windows 10 app package - MSIX | Microsoft Learn
App package signing is a required step in the process of creating a Windows 10 app package that can be deployed. Windows 10 requires all applications to be signed with a valid code signing certificate.
To successfully install a Windows 10 application, the package doesn't just have to be signed but also trusted on the device. This means that the certificate has to chain to one of the trusted roots on the device. By default, Windows 10 trusts certificates from most of the certificate authorities that provide code signing certificates.

I did a quick search:
Sign a Windows 10 app package - MSIX | Microsoft Learn
App package signing is a required step in the process of creating a Windows 10 app package that can be deployed. Windows 10 requires all applications to be signed with a valid code signing certificate.
To successfully install a Windows 10 application, the package doesn't just have to be signed but also trusted on the device. This means that the certificate has to chain to one of the trusted roots on the device. By default, Windows 10 trusts certificates from most of the certificate authorities that provide code signing certificates.

It looks like I need to purchase a certificate not self-sign for it to be classed as trustworthy. I will do so over the next couple of weeks

@licon4812,
I believe it's possible to use the App Installer to "side-load" packages with self-signed certificates. I know that may be a bit confusing, but it allows ISVs to develop and test their applications without needing to purchase a certificate. There may also be scenarios for line of business applications where the certificate is self-signed, and the machines are configured with that "private" trusted root.


Resolved Cropped text issue in Gamification Board which fixes #389

Issue Number
fixes #389

Describe the changes you've made

Describe if there is any unusual behavior (Any Warning) of your code(Write NA if there isn't)

Additional context (OPTIONAL)

Test plan (OPTIONAL)
A good test plan should give instructions that someone else can easily follow.

Checklist

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[ ] The title of my pull request is a short description of the requested changes.

Provide a Deployed link of route/page that needs to review
Preview: Deploy preview link here with the appropriate route
<!-- Please add deployed link to here text >
![image](https://user-images.githubusercontent.com/53976003/127752744-5f92ea36-7715-4704-b4c0-78cc977965d7.png)

Hey, I have removed the hardcoded breakpoints, instead, I've used flex property to display the cards.
Screenshots of the same are attached below:
1444px

875px

555 px

Please let me know in case any changes or modifications are required :)

Thanks @abhishek2x


Added second EBS drive to agents and public agents (1.10 backport).

High-level description
Without this, agent nodes do not re-join the cluster after reboot.
This is due to our coreos-aws cloud-config where we expect a /dev/xvdb.
The time service is able to start before the cloud-config.yaml adds
the var-lib.mount unit. After reboot the problem shows up as the
units are on the disk at that point.
Corresponding DC/OS tickets (obligatory)
These DC/OS JIRA ticket(s) must be updated (ideally closed) in the moment this PR lands:

DCOS_OSS-3683 Agent node does not re-join the cluster after reboot for a standard CF template based cluster.

Related tickets (optional)
Other tickets related to this change:

DCOS_OSS- Foo the Bar so it stops Bazzing.

Checklist for all PRs

[ ] Added a comprehensible changelog entry to CHANGES.md or explain why this is not a user-facing change:
[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[X] Read the DC/OS contributing guidelines
[X] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

PLEASE FILL IN THE TEMPLATE ABOVE / DO NOT REMOVE ANY SECTIONS ABOVE THIS LINE
Instructions and review process
What is the review process and when will my changes land?
All PRs require 2 approvals using GitHub's pull request reviews.
Reviewers should be:

Developers who understand the code being modified.
Developers responsible for code that interacts with or depends on the code being modified.

It is best to proactively ask for 2 reviews by @mentioning the candidate reviewers in the PR comments area. The responsibility is on the developer submitting the PR to follow-up with reviewers and make sure a PR is reviewed in a timely manner. Once a PR has 2 ship-it's, no red reviews, and all tests are green it will be included in the next train.

This repo has @mesosphere-mergebot integration. You can interact with the following commands.
@mesosphere-mergebot bump-ee
@mesosphere-mergebot merge-it
@mesosphere-mergebot override-status
@mesosphere-mergebot label [Ship It |Holding |Work In Progress |Ready For Review |Request For Comment]

PR creators can apply one of  [Ready For Review |Work In Progress]. Owners can apply any label.

@mesosphere-mergebot label Ready For Review

@mesosphere-mergebot bump-ee

azure failures was test_vip https://jira.mesosphere.com/browse/DCOS_OSS-2115

@mesosphere-mergebot override-status teamcity/dcos/test/azure/arm https://jira.mesosphere.com/browse/DCOS_OSS-2115

I forced the Ship It label onto the EE PR, I couldn't figure out why it wasn't being applied.

@mesosphere-mergebot label Ship It


Bags order: shuffle for train, do not shuffle for test

Training: give bags (one slide = one bag) in a different order every epoch

Shuffling was present but unused (line 35)

Testing: remove shuffling since it does not make any difference for testing.

closing pull request - already implemented by @binli123


How To specify 32 vs 64 bit of the app built

How To specify 32 vs 64 bit of the app built

As per the docs, you can use the "args" configuration to set the flag: --ia32
Source: https://github.com/marketplace/actions/electron-builder-action#user-content-configuration

anyway to build and publish both?

hello, I have the same question on how to use it in this case

@supertiger1234 I just went hunting here and found this issue: https://github.com/samuelmeuli/action-electron-builder/issues/25.
This issue links to another issue that solves our problem; the issue that is linked is this: https://github.com/electron-userland/electron-builder/issues/1897.


Proposal: Random color for new category

When adding a new category or when importing from Conferance-Hall, it would be great to have different colors.
Current behavior seem to be :

new category from "+" button in "Event settings" : color is back
all categories from Conferall-Hall : color is DEFAULT_SESSION_CARD_BACKGROUND_COLOR

Proposal
When creating a new category, generate and assign a color to the category

Done and deployed!


Dependencies Icon

Folder Category: Containers that are required to run other containers
Animation Suggestion: ?
File: dependencies.zip

Perhaps this icon should get the second option I outline on the network icon. The icon for Network then does the first option.

If you'd like me to do a line animation, then the svg needs an update as it's not currently using strokes but fill.

Please let me know if this works. Thank you.

dependencies.zip

Hmm, so it looks like line animations are done in css by adjusting width. Since this is curved it doesn't work. I'd like to avoid using smil since it's been almost deprecated several times and is likely to be at some point and then these will stop working. If you figure out a way to do this with css, let me know, but I think I'm going to do something a little different for this one.

The end result is a bit different than originally intended, but I think it's still pretty nice. Add in fa9f7bf5abeb8bd88737241ab27b2cc2314c3fc0


Static files broken

The following code should just copy files from source to destination:
gulp.src(folder + '/**')
            .pipe(gulp.dest(dstFolder))

However, the copied images are broken i.e. finder and VSC no longer shows them as valid image files. Same happens to font files.
Please provide the following information:

OS & version [e.g. MacOS Catalina 10.15.4]: macOS Sonoma 14.4.1
node version (run node -v): v20.11.1
npm version (run npm -v): 10.2.4
gulp version (run gulp -v): 5.0.0

Duplicate of many other issues - see the changelog, you have to specify encoding: false as an option to gulp.src for binary files.

@yocontra thanks, it works now.
The documentation just mentions "Default stream encoding to UTF-8" as breaking change but does not list any side effects or migration paths.
For others, the solution is:
gulp.src(folder + '/**', {
    encoding: false
})
    .pipe(gulp.dest(dstFolder));

This is needed for all binary files, such as images or fonts.


Adding norm parameter to smooth, and allowing for smoothing in the decode1d and 2d functions

The Gaussian window used in smooth can either be normalized (norm=True), or not (norm=False).
decode1d and decode2d now take the arguments of smooth as optional arguments, which allow for smoothing of the group before decoding. The default values of the call for smooth do no smoothing.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

3 of 7 (42.86%)  changed or added relevant lines in 2 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.3%) to 84.33%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pynapple/core/time_series.py
1
3
33.33%

pynapple/process/decoding.py
2
4
50.0%

Files with Coverage Reduction
New Missed Lines
%

pynapple/core/time_series.py
1
47.95%

Totals

Change from base Build<PHONE_NUMBER>:
-0.3%

Covered Lines:
2190

Relevant Lines:
2522

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

3 of 7 (42.86%)  changed or added relevant lines in 2 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.02%) to 84.68%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pynapple/core/time_series.py
1
3
33.33%

pynapple/process/decoding.py
2
4
50.0%

Files with Coverage Reduction
New Missed Lines
%

pynapple/core/time_series.py
1
48.61%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
2190

Relevant Lines:
2522

💛  - Coveralls


Added shaname.

Please add shaname to packages.json.

@Yardanico Will do. Thanks for your time.

@Torro hmm, maybe there's a way to do that in Nimble, I don't really know

@Yardanico I think it should. IMO not every package deserves its own repo.

@Yardanico I'm running the package scanner right now to see if I can figure what's the problem.
Thanks for the downvote btw. Guess I'll look into creating my own repo if the community doesn't appreciate my contributions.

@Torro we appreciate all contributions, but we don't want to make nimble a clone of npm (in terms of package count and dependencies) :P

You should probably create an issue in nimble repo about multiple packages in one repository but in different branches...

@Yardanico I understand. I don't want to make nimble an npm clone either.
Still waiting on the package_scanner results, will open an issue soon.

You can have a different package in each directory of your repo, but not in each different branch. Can you use directories instead? :)

@dom96 Sure! I made shaname a subtree/branch because I didn't know subdirectories would work tbh.
I'll get started on a new pull request in a few hours.
Thanks :)


add per page setting

This address #131
The list of options may need adjusting.
existing users will have the default option of 5 as is the case now, new user will have the default options of 5,15,25.

It appears that sqlite cannot use expression for the default value, I will close the pr and think of a way to handle the default value for existing users.


Anti-Screenshake

When the camera shakes randomly (most notably this occurs on the very last stage of Olm, in the volcanic mine and after looting a barrows chest (probably more places have this but i could only think of these right now)) it is really tiring for my eyes and after a few short seconds I will start blinking more often and involuntarily start shifting my focus away from the screen. I would love if there was a way to disable this sort of camera behavior.

The fishing trawler mini-game has a vanilla in-game toggle to switch from moving to static camera. Maybe this could be a starting point when investigating how to implement this. Just throwing it out here.

I don't think we should be doing this, something which effectively prevents a certain game mechanic from doing anything could be considered OP.

Yeah


Create removing-a-file.md

Addresses #980

@PavSidhu, from what I understand, you should do git rm --cached to achieve this
https://stackoverflow.com/questions/7434449/why-use-git-rm-to-remove-a-file-instead-of-rm
Also we haven and index of addtional tutorials https://github.com/Roshanjossey/first-contributions/blob/master/additional-material/additional-material.md
Can you add a link to this tutorial there?

@PavSidhu, I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added Facebook share and tweet feature to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.
We also have a slack team to help/mentor people trying to contribute to open source projects.
You can join the team by going to https://firstcontributions.herokuapp.com


research hotswap for frontend files

does installing a grunt watcher work?

If this is what I think it is , you might want to integrate browserSync within the watch. I managed to integrate it with gulp and it worked perfectly fine.

thx for the tip but i think this got done, at least to the satisfaction of kuba.  i don't use it myself:
https://github.com/twosigma/beaker-notebook/commit/0e43699bf2a77fc670a8aabe3b704f69728c3ac5


ignite-kafka not found in the optional/modules

Is ignite Kafka still supporting? I can't find this module from the docs

Does anyone have idea ?

@Taymindis , ignite-kafka was moved to Apache Ignite Extensions repository: https://github.com/apache/ignite-extensions/tree/master/modules/kafka-ext. Currently, there are no new releases of this extensions.

@shishkovilja Noted, i will use latest ignite-kafka-ext with latest ignite libs to make it work. Thanks


Error when trying to get Roomba PW

I ran the following command on my raspberry pi (Ubuntu powered):
sudo npm run getrobotpwd 192.168.x.xxx
I get to the part where the instructions tell me to hold the "home" button until I hear a tone and the WiFi lights turn on.
When I hit  key, that's when the following error occurs:
events.js:291
      throw er; // Unhandled 'error' event
      ^

Error: getaddrinfo EAI_AGAIN 192.168.x.xxx
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:66:26)
Emitted 'error' event on TLSSocket instance at:
    at emitErrorNT (internal/streams/destroy.js:92:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
    at processTicksAndRejections (internal/process/task_queues.js:84:21) {
  errno: 'EAI_AGAIN',
  code: 'EAI_AGAIN',
  syscall: 'getaddrinfo',
  hostname: '192.168.x.xxx'
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>getrobotpwd: `cd node_modules/dorita980 && npm install && node ./bin/getpassword.js "192.168.x.xxx"`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>getrobotpwd script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-10-31T16_13_54_944Z-debug.log

Apologies in advance if this is a known error.
Side Note 1: Location of my plugin folder
My plug-in folder was located here: /usr/lib/node_modules/homebridge-roomba2

So I got this to work with a "work around".
First, I cloned this repo: Nick Waterton - Roomba980
In that repo, there is a file called "getpassword.py".
Once cloned, I navigated (using my Mac's Terminal) to the cloned folder, then to another folder called "roomba" and typed in the following command:
python getpassword.py
The output was similar to the one below:
paho mqtt client not found
CV or numpy module not found, falling back to PIL
PIL module not found, maps are disabled
waiting on port: 5678 for data
supplied address <IP_ADDRESS> does not match discovered address <IP_ADDRESS>, using discovered address...
found 1 Roomba(s)
Make sure your robot (Roomba) at IP <IP_ADDRESS> is on the Home Base and powered on (green lights on). Then press and hold the HOME button on your robot until it plays a series of tones (about 2 seconds). Release the button and your robot will flash WIFI light.
Press Enter to continue...
Received: {
  "ver": "3",
  "hostname": "<HOSTNAME>",
  "robotname": "Roomba",
  "ip": "192.168.X.X",
  "mac": "<MAC ADDRESS>",
  "sw": "v2.4.6-3",
  "sku": "R960020",
  "nc": 0,
  "proto": "mqtt",
  "cap": {
    "pose": 1,
    "ota": 2,
    "multiPass": 2,
    "pp": 1,
    "binFullDetect": 1,
    "langOta": 1,
    "maps": 1,
    "edge": 1,
    "eco": 1,
    "svcConf": 1
  }
}
Roomba (Roomba) IP address is: 192.168.X.X
blid is: <BLID>
Password=> <PASSWORD> <= Yes, all this string.
Use these credentials in roomba.py

I removed the BLID & Password from the output above for privacy. Replace the strings (starting with < and ending with >) with your respective output. Also, I've edited the IP address by removing the last 2 numbers (note the X.X) - replace with your correct output. The rest of the text is what I had on my terminal output.

Thank you for the work around! I will post an updated guide soon.

This workaround worked for me as well.

Just wanted to note location for those running on Mac mini rather than Pi : /usr/local/lib/node_modules/homebridge-roomba2

Just wanted to note location for those running on Mac mini rather than Pi : /usr/local/lib/node_modules/homebridge-roomba2

i have a R890 version and had to use a similar method to @nikdata but with this repo:
https://github.com/koalazak/dorita980
however after getting my info the plugin made Homebridge Crash

i have a R890 version and had to use a similar method to @nikdata but with this repo:
https://github.com/koalazak/dorita980
however after getting my info the plugin made Homebridge Crash

I'm getting all the way to where it gives me my blid, then it just sits there and doesn't give me my password. It finally times out.  I have had this robot setup before, so I think I know the password. Does it change each time?

I was testing this out while I still had a Roomba, and it seems like the library needs to be updated. I no longer own a Roomba, so I am currently going to transfer this plugin to the homebridge org so they may find someone to maintain this repo.

Hi,
I had the same problem - shutting down the iRobot app on the iOS device and deactivating the Roomba2 plugin temporarily (restart homebridge afte) solved the issue. There must be no other device connected to the Roomba, then getpassword normally works fine.
BR, C

I'm going to close this issue as I think it's either the Roomba was busy connected to another client, or the IP address was entered incorrect due to the instructions not being clear.


Distorted iplt.points with circular coordinate

iplt.points() distorts the output when longitude coordinate is circular.  The second plot below shows the correct behaviour by setting circular to false: cube.coord('longitude').circular = False
Also, the current API documentation suggests that points() requires a list of coords as arguments, but the current implementation expects a cube.

import iris.tests as tests
import iris
import iris.plot as iplt
import matplotlib.pyplot as plt

plt.switch_backend('tkagg')
pp_file = tests.get_data_path(('PP', 'globClim1', 'u_wind.pp'))
cube = iris.load(pp_file)[0][0]

plt.subplot(211)
iplt.pcolormesh(cube, vmax=50)
iplt.points(cube, s=cube.data)
plt.gca().coastlines()
ax1 = plt.gca()

plt.subplot(212)
cube.coord('longitude').circular = False
iplt.pcolormesh(cube, vmax=50)
iplt.points(cube, s=cube.data)
plt.gca().coastlines()
ax2 = plt.gca()

plt.show()

Hi @isedwards, is this still something that affects you / can be replicated? I realise things have moved on a long way since you first raised this

I just tried the example from the OP with a recent environment (Iris 3.1.0, Matplotlib 3.4.2) and got an exception
ValueError: s must be a scalar, or float array-like with the same size as x and y

which seems to match @pelson's diagnosis

The problem is that cube.data is the wrong shape for the points being plotted when you have a circular coordinate

I think here we add an extra column to the cube.data to be plotted.  I guess to make it work we would need to do the same for s.

I think we could check every kwarg for being an array with the right length for dimension 1 and extending any that that's the case for - does that seem reasonable @rcomer? I've not done much in plotting code so don't know if we'd want to do that, or maybe just extend any dimension that's the right length regardless of which one it is?

I think we could check every kwarg for being an array with the right length for dimension 1 and extending any that that's the case for - does that seem reasonable @rcomer?

I was thinking similarly, though I'm not particularly familiar with this module either.  Maybe it's enough to check whether val.shape == cube.shape, though I note that cube.data will be transposed if necessary to enforce that "X" is dimension 1.  I also just noticed that c does get auto-transposed to match, but only for the non-map case, which seems odd to me.
https://github.com/SciTools/iris/blob/0852e1ebe7481f0e2a8bcf7665d5179d3496dce7/lib/iris/plot.py#L511-L516
If you do cube.transpose() before plotting the second (working) example from the OP, you get a mess!  I think this is because scatter doesn't check the shape of the s array, only its size.

I think it seems reasonable to generally assume that the user provided bonus data in the same shape as the original data and to expect that debugging to be on them if they haven't (not sure if we can spot it and warn politely, though possibly it's best to pass it to matplotlib to deal with regardless). Based on the comment in your example lines, I'd guess that the automatic transposition of c was implemented to hide that matplotlib had stopped being so helpful.


fix broken tab component

'Check the logs' tabs weren't displaying.
Fixes  https://github.com/docker/docker.github.io/issues/15187

Looks stellar!


Auto-import issue on client side during Liveshare

An issue has been encountered with the auto-import feature during a Liveshare session on the client side. The autocompletion popup appears, but upon selection of one of the suggestions, the import is not being added, and a silent error is being triggered. The feature is working properly on the host side.
The issue has been encountered on JavaScript projects and it appears to also be the case with Java, as reported in issue #3108.
Below is a comparison of the local session versus the remote one :
Local

Product and Version : VSCode 1.74.3
OS Version : Windows 10
Live Share Extension Version : 1.0.5803

Remote

Product and Version : VSCode 1.74.3
OS Version : Windows 11
Live Share Extension Version : 1.0.5803

In both sessions, suggestions are correctly identified.
However, an error is being triggered on the remote session when suggestion selected :

Could I help to investigate this issue ?

Also happening in a Typescript project on vscode version:
Version: 1.75.1 (Universal)
Commit: 441438abd1ac652551dbe4d408dfcec8a499b8bf
Date: 2023-02-08T21:34:59.000Z (2 wks ago)
Electron: 19.1.9
Chromium: 102.0.5005.194
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 21.3.0
Sandboxed: No```

Same here.

Same problem

anyone can link to a solution ?

I don't have a direct solution, but I found a way to make it less painful. After selecting one of the suggestions you can use the "quick fix..." function (  ⌘  +  .  ) to complete the auto-import.


Undo?

Is your feature request related to a problem? Please describe.
I'm new to this plugin (and ignorant to shell programming) and, for some reason, I often find myself hitting the forward-char key and having a big long auto-suggestion I didn't want. Is there a way to undo such a mistake? Could I remove the forward-char binding? (When I hit End it's purposeful.) Or perhaps map forward-char to "forward word"?

Answer is here.


Documented "Getting Started" dapr commands are incorrect in Windows 11

Describe the issue
Many of the commands specified do not work on Windows 11.
Specifically,
(1) The command: dapr -h should be the following: .\dapr -h
(2) The command: dapr int should be the following: .\dapr init
(3) Many other commands which expect the dapr.exe need the .\ preceding the dapr command call, i.e. .\dapr --version
URL of the docs
https://docs.dapr.io/getting-started/install-dapr-cli/
and
https://docs.dapr.io/getting-started/install-dapr-selfhost/
Expected content
I expected the Listed Commands to Work as Written, which is not the case.
Screenshots
(1)
(2)
Additional context

@BillEisenman - When you say Windows 11 you are running this with WSL correct? This is a Linux command prompt rather than a Windows command prompt correct?

@BillEisenman friendly bump

closing for now. let me know if we should reopen.


Generate artifact doesn't seem to do anything

I have Shifter-local running on my MacBookPro.  When I go into the WordPress dashboard, I see that a Shifter menu is available. So I choose "Generate artifact".  It then gives me the warnings as it does in regular Shifter that generating the artifact will cause me not to be able to work in WordPress.  So I click on the OK button and I get the message that an artifact is being generated and to check the Shifter dashboard:

However...

I don't have any Shifter dashboard to check (that I can find).
After I dismiss the dialog box, I can continue using WordPress.
I can't find any sign on my disk that an "artifact" was created.

Is this functionality supposed to work on Shifter-local?   If so, it didn't work for me.
If NOT supposed to work, then I would recommend documenting that in the Github documentation so that people don't expect it to work (yet, anyway).

Generate artifact Shifter-local is to check the operation of WordPress in almost the same environment as Shifter. Generate artifact button works only on Shifter platform.

If NOT supposed to work, then I would recommend documenting that in the Github documentation so that people don't expect it to work (yet, anyway).

Thanks for the feedback, we will update the README.

https://github.com/getshifter/shifter-local/commit/fbf85c84c37bf72b8d6490ad306265545ca0a184
I've updated README. Thanks 😃


Keys Detective shouldn't mark comments as extra keys

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[x] Feature request
[ ] Documentation issue or request
[ ] Support request
[ ] Other... Please describe:

Current behavior
The Keys Detective marks all of our comments for translators (i.e. all entries that are something.comment in our en.json file) as extra keys. It becomes a bit cumbersome to search for real extra keys in the output of the script.
Expected behavior
All comment entries shouldn't be marked as extra keys.
Minimal reproduction of the problem with instructions
Have the following content in an en.json file:
{
  "a": "this is content",
  "a.comment": "a comment about a"
}

Have the following content in a .ts file:
import {} from '@ngneat/transloco'

/**
 * t(a)
 */

What is the motivation / use case for changing the behavior?
With lots of comments, it becomes a bit hard to find all actual extra keys in the list that the Keys Detective provides.
Environment

Angular version: 9.1.12
Keys manager version: 2.2.1

For Tooling issues:
- Node version: 12.0.0
- Platform:  Linux

@potray released in v2.5.0, LMK if it works for you 🙂

@shaharkazaz It does work, thanks! But I think this introduces a bug: an entry with the key "comment" is not processed as an extra key. I think the problem is the following two entries for "comment" are equivalent when reading JSON:
{
  "page": "something",
  "page.comment": "something is the opposite of nothing" ⬅ comment about the page entry, should be ignored by keys extractor
}

{
  "page": {
    "comment": "Write your comment below" ⬅ actual entry with a "comment" key
  }
}

Probably this isn't possible to implement by reading and interpreting json. The easiest solution I can think about would be to change the recommendation about writing comments to use something like a hashtag instead of a dot, so it doesn't get converted into a inner entry of the comment's key, but a genuine entry that ends with #comment.


CreateSessionAppFromApp does not return qSessionAppId

Hi!
According to the documentation "CreateSessionAppFromApp" returns a "qSessionAppID". I wasn't able to grap this property with qsocks, as currently only msg.qReturn is used.
I fixed this for me by changing the code to:
Global.prototype.createSessionAppFromApp = function(qSrcAppId) {     var connection = this.connection;     return this.connection.ask(this.handle, 'CreateSessionAppFromApp', arguments).then(function(msg)  {         return [ msg.qSessionAppId, connection.create(msg.qReturn)];     }); };
Currently I'm not able the Qlik Sense Application with the 'qSessionAppID', but that's probably something that I need to discuss with Qlik support...
Thx,
Roland

Ye I don't return the ID since (I believe) you won't be able to connect to it from an outside session.
You can get the ID (which is the same as qTitle for session apps) by calling getAppProperties() on the app handle.

Thx for the fast response.
Exactly, I want to "change script+reload" the sessionapp, and then redirect the user to:
https://qliksenseserver/sense/app/
Therefore I need the qSessionAppId; unfortunately I dont't get it to work anyway. I thought the redirect would stay in the same session, but it seems it behaves differently..


⚠ SceneTime has degraded performance

In c64d993, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 2108 ms

Resolved: SceneTime performance has improved in 38d7eeb after 6 minutes.


Fixes #435 - Apps using DRM via Widevine

The plugin is stored in appdata, so the user should only ever need to download it once for all nativefier apps they create.

@brianblakely over at https://github.com/jiahaog/nativefier/issues/68#issuecomment-328440151 , @xdgc notes that this PR didn't work for them, but offers a few proposals. Could the two of you discuss what didn't work for @xdgc and maybe improve this PR? Thanks 🙂.

I'm not sure how to determine what failed. If I understand the PR it's trying to download the plugin in runtime, which sounds wise, but I can't see that it's happening. And I don't know enough about electron to find why.

I've just glanced through the source code for https://github.com/webcatalog/electron-widevinecdm briefly. I could be wrong, but it seems like it is downloading a prepackaged widevine binary and we are dependent on the upstream for versioning. Would it be easier to instead assume that the user has Chrome installed, and hence read from that directory?
Something like https://github.com/jiahaog/nativefier/commit/6ca4e794cdbc5b4884cd2c05b9a56f1c4e139cd1 (for flash but the same idea)? Sorry if I'm a little out of touch with things, feel free to correct me if it should/should not work 😄

I think relying on upstream for version is exactly what's attractive. There can be a substantial gap between the Chrome runtime version used by Electron and that in the user's local Chrome installation (if any). If the widevine plugin is not compatible (as between nativefier's Chrome 56 and my Chrome 61) then the plugin just appears unavailable — no diagnostics to help. That's what my comment in #68 addresses.

Agreed @xdgc -- not needing Chrome installed is ideal.
As for the bug report, I grabbed a random MacBook from someone to test.  I knew nothing about its existing setup, I just installed Node and my fork of nativefier, added the Spotify Web Player, and it worked as expected.
My own machine runs Windows, and has the latest Chrome 61 running.  I've tested various scenarios on that environment, and have not been able to break it yet.

Any response to my previous comment?

@brianblakely   Next week I will try your fork since I want to have Spotify and some other apps that require DRM.
Regards :octocat:

@mikhoul Great! Afterwards, please kindly report back in as much detail as you can.

@xdgc @brianblakely Ah yes, you're right about the incompatibility issue between the chrome version drift and Electron Chrome version.
Could we then have some form of pop up to inform the user when the plugin has completed the download?

Has this been fixed?
I see the code in the main.js file in the source, pulling widevine plugin from Chrome<PHONE_NUMBER>
const WIDEVINE_PATH = '/Applications/Google Chrome.app/Contents/Versions/61.0.3163.100/Google Chrome Framework.framework/Libraries/WidevineCdm/_platform_specific/mac_x64/widevinecdmadapter.plugin';
const WIDEVINECDM_VERSION = '<IP_ADDRESS>8';

But it is not working. I manage to find that specific version of Chrome, and put it in /Applications. The widevine plugin inside is <IP_ADDRESS>8 (ref. in the main.js source file)
Not working here. I have Nativefier v. 7.5.4
Has this been implemented?

Is nativefier widevine compatible now? What steps are necessary to implement?

"Is nativefier widevine compatible now? What steps are necessary to implement?"

@ryanmusante there are unaddressed comments above that prevent merging, and I haven't paid attention to it as I have no subscription to DRM-using webapps letting me test it.
@brianblakely can you sum up remaining TODOs?

Closing. @brianblakely @ryanmusante (or anyone else able to test&finish this patch), feel free to chime in anytime with answers to the remaining questions, and I'll re-open 🙂.

Hi everyone. Did someone solve this? I'm still unable to watch Netflix due to Netflix error code M7701-1003. Would be great to have this since Netflix, Amazon Video etc. should be an important use case for nativefier.
@ronjouch @jiahaog <3

Hi everyone,
Still the same error for me too, do you have some solutions please ? :)
Thanks !

Closing. @brianblakely @ryanmusante (or anyone else able to test&finish this patch), feel free to chime in anytime with answers to the remaining questions, and I'll re-open slightly_smiling_face.

I know this has been closed for a long time, but is there anything that can be done with DRM protected content not working? I can't write any code, so most I can do is just test changes, unfortunately :(

And yeah, I can install and use Flatpak version of Spotify, but I don't want to, and I think there are other services out there that have same issue when it comes to using them with nativefier.


Use latest Teku libraries to enable support for Bellatrix fork

Should address https://github.com/ConsenSys/web3signer/issues/494

Error parsing parameters: Failed to load network /path/to/e2e_config.yaml due to Unable to load configuration for network "/path/to/e2e
_config.yaml": Found duplicate declarations for spec constant 'SLOTS_PER_EPOCH' with divergent values: '6' and '8'

I tried this with my test file in #494 where I override SLOTS_PER_EPOCH and it does not work as expected.

Error parsing parameters: Failed to load network /path/to/e2e_config.yaml due to Unable to load configuration for network "/path/to/e2e
_config.yaml": Found duplicate declarations for spec constant 'SLOTS_PER_EPOCH' with divergent values: '6' and '8'

I tried this with my test file in #494 where I override SLOTS_PER_EPOCH and it does not work as expected.

I filed https://github.com/ConsenSys/teku/issues/4905 based on this issue. Thanks


Active Pedometer: Distance calc and display

Thanks! By the way you can do require("locale").distance(dist_in_m) to get a nice, formatted, internationalised distance (eg for europe <1km is in m, and > is in km)


Cannot play Fallout New Vegas in Desktop Mode

Whenever I try to load Fallout New Vegas in Desktop mode (so I can screen share on discord), I get an error about display resolution (image attached).
I’ve tried altering some ini files and opening the original launcher in proton tricks, but neither made any difference. Not sure if I’m doing something wrong there though.

Managed to fix this by reinstalling the game, and making sure the first time I opened it was in desktop mode, not game mode.


Integration of new Zotero annotations capabilities

Hi @retorquere
Thanks for this great great tool !
Zotero has launched a new integrated PDF reader that allows very interesting work on tags. It offers the possibility to put tags to highlighted text excerpts. Currently, the export of the bibliography in .bib integrates all the text extracts but not the tags. It would be very useful to be able to retrieve them somehow to integrate them in other uses (here org-mode).
Would you be interested in this idea?

Sure, but Zotero would have to provide a way to read those tags; when the page says "they're not yet searchable" that likely means they're not handled as regular tags inside Zotero.

Hi @retorquere
Yes you're right, it's a little early, but it was also to document it and not forget it. It will be possible normally.

Also, I'm wondering in what type of field of a .bib entry these tags could fit. :thinking:

Please remind me when activity happens on this front. I don't follow all discussions on the Zotero forums, and new features need an advocate to provide input.

ok, I will try to follow the news ;-)

Slightly related; when running automatic exports these fail with an error "translation failed". Two lines which stand out in the debug log;
(3)(+0000012): {better-bibtex true} +214 worker translation failed, error: <Error: Unexpected Zotero Item type "annotation" in chrome://zotero/content/xpcom/utilities.js itemToCSLJSON@chrome://zotero/content/xpcom/utilities.js:1529:13 exportItemsByWorker@chrome://zotero-better-bibtex/content/common.js:63527:48 >

and later;
(3)(+0000002): {better-bibtex true} +1 auto-export library 1 failed: {"$loki":1,"DOIandURL":"both","asciiBibLaTeX":false,"asciiBibTeX":true,"biblatexExtendedNameFormat":false,"bibtexParticleNoOp":false,"bibtexURL":"off","error":"translation failed","exportNotes":false,"id":1,"meta":{"created":1601883827108,"revision":240,"updated":1616430093103,"version":0},"path":"C:\\Users\\...\\Library.json","recursive":false,"status":"running","translatorID":"f4b52ab0-f878-4556-85a0-c7aeedd09dfc","type":"library","useJournalAbbreviation":false} translation failed

@corstian would you be OK with opening a separate issue for this?

@retorquere Done: https://github.com/retorquere/zotero-better-bibtex/issues/1770

I'll be tracking work on this in issue #2126 -- I've requested the change from zotero, no idea when it will happen.


fix: Update README.md by adding installation commands

Issue Template
Prerequisites
Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.

[x] I am running the latest version
[x] I checked the documentation and found no answer
[x] I checked to make sure that this issue has not already been filed
[x] I'm reporting the issue to the correct repository (for multi-repository projects)

Context

The existing README.md file does not contain any script that installs all the dependencies of the project while setting up the project locally.
Further the command npm install is not working properly, which can cause errors to new contributors while setting up the project locally.

Expected Behavior

The README.md file should be updated with the command which should be used to install the dependencies of the project.

Current Behavior

The README.md file does not have any command that helps contributors to install the dependencies while setting up the project locally.

Failure Information (for bugs)
Please help provide information about the failure if this is a bug. If it is not a bug, please remove the rest of this template.
Steps to Reproduce
Please provide detailed steps for reproducing the issue.

Fork the repo.
Clone the repo on your local machine.
Run the command npm install

Failure Logs
Please include any relevant failure logs.

Error after running npm install

-Error after running npm start

@aceta-minophen I would like to fix this issue!


wheel problem

The python version is python3.10.
And the ERROR: Could not build wheels for qml, which is required to install pyproject.toml-based projects

Please note that further development for the QML package is now happening on the qmlcode/qmllib repository. qmllib is a port of the QML's Fortran core functionality with fewer dependencies and numpy 2.0 compatibility. You are encouraged to open any future issues or pull requests there.


better command call in config.json

user shouldnt have to write ruby code in config.json. This would also allow jane to use system instead of evil eval.
edit config values for a button maybe like this:
{
  "name": "tv_power",
  "icon": "off",
  "btn_class": "btn-info",

  "fn_args": [
    "tv",
    "power"
  ],

  "commands": [
    {
      "type" : "irsend",
      "sleep_after_command" : 0,
      "command_parameter":
        {
          "receiving_device": "tv",
          "command": "KEY_POWER"
        }
    }
  ]
},
{
  "name": "powerdown",
  "icon": "off",
  "btn_class": "btn-info",

  "fn_args": [
    "action",
    "power"
  ],

  "commands": [
    {
      "type" : "irsend",
      "sleep_after_command" : 2,
      "command_parameter":
        {
          "receiving_device": "tv",
          "command": "KEY_POWER"
        }
    },
    {
      "type" : "powerpi",
      "sleep_after_command" : 0,
      "command_parameter":
        {
          "receiving_device": "desklamp",
          "command": "off"
        }
    },
  ]
}

@Lyr3x what do you think?

json
"command" : "off"

command is a bad naming, but I couldn't come up with anything better at this moment.

You're right, i thin its better to write the config without ruby code too.
And what about "command" : "<device>off/on"

I think "device on/off" after the command tag is harder to parse.

What do you think about
"command" : "power_on"
you dont have the device name twice but obviously the user should see what the command do

I think two values like device and command are easier to parse and since powerpi controls radio switches only two states are possible, on or off.
We should discuss better naming for the command tag rather than the value that follows.

done with merge #49


[Postgres/postgis] Cant display geometry_dump columns

System information:

Ubuntu 18.04
DBeaver 5.3.5
Java version 1.8.0_201

Connection specification:

Postgres 9.6

Describe the problem you're observing:
Can't display columns of type geometry_dump.
Steps to reproduce, if exist:
When executing a query that returns a column of geometry_dump like the following:
select st_dump(the_geom)
from (
    values ('MultiPoint((1 2))'::geometry)
) q (the_geom)

it shows <NULL> in both resulting columns and a warning: Can't read column 'st_dump' value - For input string: "{1}"
Changing the query like the following works:
select (st_dump(the_geom)).geom -- or .path also works
from (
    values ('MultiPoint((1 2))'::geometry)
) q (the_geom)

This is actuall a bug in PG structs with nested array parser.
Thanks for the bug report


Osmosis Proto

New PR to merge the osmosis-proto crate into the main branch. (for reference #239)
Best regards,
Philipp

Looking mostly good aside from test failures and rustfmt.
What's up with the empty osmosis-proto/src/prost/osmosisd/cosmos_proto.rs?

@tony-iqlusion I can't test the workflows as first-time contributor. So far locally everything works.

Closing this PR. I need to refactor the osmosis-proto branch first.