Feature request: Support saving and checking hash or signature of dependency in report

dependency-guard does an awesome job of protecting projects from unwanted dependency changes.
But this way we know nothing about the actual dependency content and cannot protect against malicious supply chain attacks like the ones mentioned here:

https://blog.oversecured.com/Introducing-MavenGate-a-supply-chain-attack-method-for-Java-and-Android-applications/
https://blog.sonatype.com/malware-removed-from-maven-central
https://www.csoonline.com/article/654560/why-open-source-software-supply-chain-attacks-have-tripled-in-a-year.html

Of course, we can use Gradle's support for package signatures.  But it's hard to use properly and not supported by many Gradle plugins and library providers (including many Google and JetBrains packages).
By simply saving and checking the dependency package hash along with the package, name, and version, we can verify that this dependency has not been unexpectedly replaced!  Using a hashing algorithm like xxHash this would be very fast and provide an order of magnitude higher level of security for any Gradle build with a super simple setup.
Additionally, we can store and check the signature hash for packages that provide one.  Using truncated hashes (like for git commits) it will not bloat the dependency reports too much.
All of this can be optional and opt-in, disabled by default.
If this idea is welcome, I would be happy to provide a prototype/mvp pull request.

@handstandsam I think this functionality fits well within the scope of the plugin, but I understand your concerns.  I'll make an MVP pull request to show that it shouldn't significantly increase complexity and usability.  Would you consider it?

I'd consider as this is something I'd find valuable as well in a tool.  Before you spend a ton of time doing it, I've got a bunch of questions/comments to discuss so we can make sure this is something that could be implemented, and something that makes sense in this tool.   (What if you have a bad artifact to begin with?)
Will you hash local artifacts to verify they do compute to the correct hash?  Do you have that algorithm?  Will that come from the Gradle OSS plugin?
What type of hashes would it support?  SHA256? SHA512? SHA1? MD5?
In the baseline file, how do you represent the hash+algorithm used?  What is an example of what the baseline would look like?
Example - Kotlin 1.9.22  https://repo1.maven.org/maven2/org/jetbrains/kotlin/kotlin-stdlib/1.9.22/

This could be a format (just an example).
org.jetbrains.kotlin:kotlin-stdlib:1.9.22 8c1a267 SHA1

How would this work with modules = true?  (Probably just not do anything for those, which makes sense to me)
Requirement: We have a baselineMap config parameter that allows you to map (transform) what is stored in your baseline file (see readme for example https://github.com/dropbox/dependency-guard/tree/main).  How would it work for items that are filtered out with null?  How would it work for items that are transformed in general, because we have no way of guaranteeing what those look like. (Example: Some people like to trim off versions when they release a lot of versions internally).  Another Example: some dependencies a team may not desire to baseline/track.
How will this work with -SNAPSHOT versions?
Extra Feature Request - Could you somehow note which repository (if more than one, example: mavenCentral(), google()) it came from?  I think that's almost as important as the hash (in terms of the plugin's goal of "guard against detecting unintentional dependency changes")

org.jetbrains.kotlin:kotlin-stdlib:1.9.22 8c1a267 SHA1 https://repo1.maven.org/maven2

Future Questions:

What is the performance overhead?
Requirement: It needs to have a hard toggle in the plugin configuration and off by default (for consistent usage) - Unless it's a new major version. (Which this might be with this big of a change)


Add ryan-brocklesby's file

created a branch, created a file and made a commit, and opened a pull request


Get-Team: does not retrieve Team Settings

In the documentation for Get-TeamMemberSettings, Get-TeamFunSettings, Get-TeamGuestSettings, Get-TeamMessagingSettings is mentioned, that those cmdlets are deprecated and the Get-Team should be used instead. However, the Get-Team cmdlet does not retrieve any of those setting details. The respective Set-Team and New-Team cmd-lets provide parameters to set those details, why the Get-Team is not able to retrieve them?

Hi @BChaloupka, thank you again for your comment.
Not all properties/settings are displayed by default in PowerShell. You can use Format-List for example to retrieve all the properties for one team:


[DB] onwer's db is too big

try —unsafe-pruning => more testing => change crust-node => add wiki

testing


Question: How do I specify which factor/role to use by default in credential_process?

At my org, I have a few roles that are in various AWS accounts. Each of these AWS accounts represents a different environment within our CICD process: dev/stage/prod.
If I create multiple aws profiles so I can switch between multiple accounts/roles quickly like this:
$ crowbar profiles add my-org-dev -u paul.baker -p okta --url https://my-org.okta.com/home/amazon_aws/....
$ crowbar profiles add my-org-stage -u paul.baker -p okta --url https://my-org.okta.com/home/amazon_aws/....
$ crowbar profiles add my-org-prod -u paul.baker -p okta --url https://my-org.okta.com/home/amazon_aws/....

It gets a little difficult to manage, because when the token expires it'll ask you to select which factor to use (I have multiple options, but I only ever want push) and it'll ask me which role I wish to assume. I can't swap roles until the token expires so if my intent was to target a development environment but I specify production by accident, I can't fix it until the token expires and I re-select the correct account.
Is there a way to tell crowbar which factor method and role I want to assume by default within the credential_process command?

Hey @paul-nelson-baker, terribly sorry for the delay, I was on vacation the past two weeks.
Just so that I understand: you wish to specify the factor and the role to use when running crowbar with credential_process, right?
Both of these functionalities are planned (in fact, there's a stub for the role selection already) but not implemented. I'm going to try to get around it soon.

(Along with fixing the removal of invalid/broken AWS credentials)

I've added a crude implementation of the role selection in #7, and I'm happy to accept feedback.

Apologies for not responding, when I submitted this initially the organization I was working for underwent an acquisition and I never had a chance to return my focus. Thank you for addressing it regardless, it is appreciated :)


started to document krop

You (challenger) can claim the throne by reversing our hack (HENkaku) and explaining it.

Not sure if explaining (in public) is a good thing to do: first it spoils the challenge for others, second it makes the kernel vulnerabilities accessible/usable -- also for possibly attacking/bricking/... 3.60 Vitas via simple website access.

Once we have been knocked off, we will post all our source code, build scripts,

Thanks, but no need ;) Writing the tools to analyze/understand is - at least to me - half the fun.

and a special bonus… [..]

If this depends on a detailed, public explanation -- I'll pass for now.. Anyway, thanks for the challenge and congrats for hacking the Vita in the first place + providing such a homebrew enabler; a truly remarkable feat!

Oh, seems like 'the time was right'; congrats to the others!
http://st4rk.net/2016/10/21/henkaku-ps-vita-ctf-the-end/
http://hexkyz.blogspot.com/2016/10/henkaku-exploit-teardown-stage-3.html
https://yifan.lu/2016/10/20/henkaku-koth-solved/


Plex with google drive

Hi, i'm trying to stream files from my google drive account to plex media server (PMS) on linux ubuntu 16.04. Currently PMS doesn't show me any file that is in my movies folder from google drive using google drive ocamlfuse, here are the steps i'm following:
install plex using snap
sudo snap install plexmediaserver
install google Drive Ocamlfuse
sudo add-apt-repository ppa:alessandro-strada/ppa
sudo apt-get update
sudo apt-get install google-drive-ocamlfuse

link to my google drive account
google-drive-ocamlfuse
create folder and mount it allowing other
mkdir ~/miguel-google-drive
sudo google-drive-ocamlfuse -o allow_other ~/miguel-google-drive

Any suggestion? Thanks.

@meszape  Thanks, Wich command i must use to configure the drive mount with the plex user? Do you have plex installed with snap?

Hi
I installed via apt. You have to run the command as the plex user (the
config and the mount)
Br
On Thu, 27 Jun 2019, 16:55 Miguel Alberto Plazas<EMAIL_ADDRESS>wrote:

@meszape https://github.com/meszape Thanks, Wich command i must use to configure
the drive mount with the plex user? Do you have plex installed with
snap?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/astrada/google-drive-ocamlfuse/issues/554?email_source=notifications&email_token=AK22HZ62ANVRIX5ZDREWHPTP4TIHLA5CNFSM4HUJQMPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYXMHTQ#issuecomment-506381262,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AK22HZ6VGVB7HDRE7GPXZB3P4TIHLANCNFSM4HUJQMPA
.

Thanks, that's the problem. Installing using apt works perfect! But by snap I must access data in /media/ folder.

I am not familiar how plex works when you install with snap. But if media
needs to be in /media, than you should mount with /media path
Br
Peter
On Thu, 27 Jun 2019, 17:27 Miguel Alberto Plazas<EMAIL_ADDRESS>wrote:

Thanks, that's the problem. Installing using apt works perfect! But by
snap I must access data in /media/ folder.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/astrada/google-drive-ocamlfuse/issues/554?email_source=notifications&email_token=AK22HZY5IUTARKGEGZKSGULP4TL57A5CNFSM4HUJQMPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYXPLGY#issuecomment-506394011,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AK22HZ54ZOKMV6R2K6UC3VTP4TL57ANCNFSM4HUJQMPA
.

thanks
El jue., 27 jun. 2019 a las 10:47, meszape<EMAIL_ADDRESS>escribió:

I am not familiar how plex works when you install with snap. But if media
needs to be in /media, than you should mount with /media path
Br
Peter
On Thu, 27 Jun 2019, 17:27 Miguel Alberto Plazas, <
<EMAIL_ADDRESS>wrote:

Thanks, that's the problem. Installing using apt works perfect! But by
snap I must access data in /media/ folder.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/astrada/google-drive-ocamlfuse/issues/554?email_source=notifications&email_token=AK22HZY5IUTARKGEGZKSGULP4TL57A5CNFSM4HUJQMPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYXPLGY#issuecomment-506394011
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AK22HZ54ZOKMV6R2K6UC3VTP4TL57ANCNFSM4HUJQMPA
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/astrada/google-drive-ocamlfuse/issues/554?email_source=notifications&email_token=AD6P2EDOTJZAWF7EPFQLWXTP4TOKRA5CNFSM4HUJQMPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYXRMXQ#issuecomment-506402398,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD6P2EFTP7PO4ZDCORBQKQDP4TOKRANCNFSM4HUJQMPA
.


Fixed the type of the make method of the Attribute class

[ ] Added or updated tests
[ ] Documented user facing changes

Changes
The argument type of the make method of the Attribute class has been modified to match the Laravel documentation.
https://laravel.com/docs/11.x/eloquent-mutators#building-value-objects-from-multiple-attributes
I wrote the following code according to the Laravel documentation, but when I ran it on Larastan (Level 9), I noticed the following error, which led me to create a PR:
If there doesn't seem to be any problems, I'd like to ask you to merge it.
    /**
     * @return Attribute<Period, Period>
     */
    protected function publishPeriod(): Attribute
    {
        return Attribute::make(
            get: fn(mixed $value, array $attributes) => new Period(
                $attributes['publish_from'],
                $attributes['publish_to'],
            ),
            set: fn(Period $value) => [
                'publish_from' => $value->from,
                'publish_to' => $value->to,
            ],
        );
    }

 ------ ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
  Line   Models/Recruitment.php
 ------ ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
  24     Parameter $get of static method Illuminate\Database\Eloquent\Casts\Attribute<mixed,mixed>::make() expects (callable(mixed, mixed): App\ValueObjects\Period)|null, Closure(mixed,
         array): App\ValueObjects\Period given.
         🪪  argument.type
         💡 Type #1 from the union: Type array of parameter #2 $attributes of passed callable needs to be same or wider than parameter type mixed of accepting callable.
 ------ ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Breaking changes

Hi,
Can you add some integration test for this? The code snippet you shared should be fine.

@canvural

Hi,
Can you add some integration test for this? The code snippet you shared should be fine.

I added tests in 7d1faa603ad2585b5097e9f8775050e65a8579eb. Please let me know if it doesn't match your intention.
The code I referred to for the tests: https://laravel.com/docs/11.x/eloquent-mutators#mutating-multiple-attributes

Can you remove the merge commit and rebase instead?

Thank you!


Force gl context loss, Fixes #3039

For #3039

Background
A partial fix was published in 7.0.4, however garbage collector is still not able to release all the memory used.

Since being able of mounting and unmounting Deckgl components without any memory leakage was a must, I just implemented a simple context lose at the time of finalization achieving the following results:

This may seem unnecesary for a simple app like the example web but it was critical for my App, where I'm rendering huge amounts of data while mounting/unmounting different instances
I'd like to know what do you think about this approach.
Change List

Reference the gl context at component level
Make sure we force the loss of such context

Thanks

I'd like to know what do you think about this approach.

Using the .gl.getExtension('WEBGL_lose_context').loseContext() approach has been discussed in the past. The idea was to implement it in luma.gl here.
The main concern was that upon careful reading of the spec this WebGL extension is a debug extension for testing application response to context loss, and it is not clearly specified to work for this use case.
But if it really helps we should consider it again, and also do some cross-browser testing.
@tsherif

This is interesting, @Lowhearth. I'm actually surprised that you saw that significant a result.
I would prefer not to go with this approach for a few reasons:

Per the extension spec, This extension exposes new functions which simulate losing and restoring the WebGL context. So while recommended, it isn't guaranteed that the underlying context is actually destroyed
Overhead of the loseContext function across platforms is unknown
Not supported in some browsers (IE and older Edge)

I'd recommend we think about what's happening on context loss that we aren't currently doing when we clean up. Assuming our finalize methods are working correctly, I suspect it's just that textures and buffers are still bound to various binding points in the GL. OpenGL specs are clear that glDelete* functions will mark names as unused, but the underlying resource isn't actually deleted until it's no longer bound anywhere. So perhaps a robust solution would be to create a cleanupGLContext function (I'm thinking in luma.gl) that simply binds all texture, buffer and attribute pointer binding points to null to release GPU resources as quickly as possible.

I suspect it's just that textures and buffers are still bound to various binding points in the GL.

I'm pretty sure that's the main problem. Just didn't have the time yet to get familiarized with the luma.gl source code and make the changes.
I think we all agree that the creation of a cleanupGLContext in luma will be the correct solution. Let's close this PR and take @tsherif 's approach.
Thanks for the responses


Add linter for the JavaScript port

Summary

Added a linter for the JS port to enforce code style and code consistency.
Added scripts to check and fix linter issues.

Closes #16.

I chose the option to inspect the actual file to detect the code style, however, we can definitely keep the configuration minimal by removing the rules key. I'll make the changes.


Qiskit 0.11.1 micro release

Summary
Micro release fixing compatibility issues with the new IBM Q API v2.
Details and comments

The version history was already changed.  I did miss the doc version number though, so good find there.  I have also bumped aqua to its latest minor.


Example fails to build on windows for target x86_64-pc-windows-gnu

Example used.
error.txt

I found the culprit https://github.com/rust-lang/rust/issues/47048
Sorry for the noise.

No problem, glad you found the issue!
I probably should set up some windows-based CI just to be sure...

This is from my appveyor.yml for a cmdline tool
environment:
  matrix:
    - TARGET: x86_64-pc-windows-gnu
      CHANNEL: stable
      MINGW_PATH: "C:\\mingw-w64\\x86_64-7.2.0-posix-seh-rt_v5-rev1\\mingw64"
    - TARGET: x86_64-pc-windows-msvc
      CHANNEL: stable
    - TARGET: i686-pc-windows-gnu
      CHANNEL: stable
      MINGW_PATH: "C:\\mingw-w64\\i686-6.3.0-posix-dwarf-rt_v5-rev1\\mingw32"
    - TARGET: i686-pc-windows-msvc
      CHANNEL: stable

install:
  - if defined MINGW_PATH set PATH=%MINGW_PATH%\bin;%PATH%

Build fails with 7.3 and msys2


Need to add stack trace as an optional param in print functions

Description:
$Subject
Describe your problem(s)
Describe your solution(s)
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

Closing since fixed in https://github.com/ballerina-platform/module-ballerina-log/pull/421


Invalid pattern of replacement

    def test_path_should_not_resolve_case_insensative():
        resolvers = []
        toc = ',a/b/C,'
        path = 'a/B/c'
        (path, pattern) = _resolve_path(toc, path, resolvers)
        assert path == 'a/b/C'
>       assert pattern == ('a/B/', 'a/b/')
E       assert ('', 'a/b/C/') == ('a/B/', 'a/b/')

Hey @naglalakk found a bug in the pattern output. It should not return the filename in the pattern resolving.

Is this resolved in your latest refactor?

This is handled in the latest refactor.  It will be included in the next enhance/performance PR I will commit soon


Update tokens to 5.0.0

This PR is to

Update the Material Design tokens to 5.0.0
4 color roles in Light mode have different default values
onPrimaryContainer: Primary10  -> Primary30
onSecondaryContainer: Secondary10 -> Secondary30
onTertiaryContainer: Tertiary10 -> Tertiary30
onErrorContainer: Error10 -> Error30

new tokens added in list.json
md.comp.menu.list-item.* tokens are deprecated and should be replaced by tokens in list.json and we've done the migration last year:)!(#122388)

Pre-launch Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I signed the [CLA].
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is [test-exempt].
[x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported.
[x] All existing and new tests are passing.

Will there be an accompanying doc for this breaking change?

Should I send an email to flutter-announce@? It seems there's no failures in customer_testing and Google testing, so probably not counted as breaking changes, but we do have some golden test failures:) Looks like based on this doc, we should just send an announcement. Any suggestions:)?


Create Periodical references page

[ ] Create page
[ ] Add description of what is being covered
[ ] Add description of checks required on this content, compiled from current protocol documents
[ ] Add examples covering correct and incorrect scenarios, as required to support checks
[ ] Populate with schematron messages
[ ] Provide explanations for how to fix schematron errors and warnings
[ ] Review house style document to ensure all requirements are covered by GitBook and schematron
[ ] Review schematron messages related to this topic to ensure they are user friendly
[ ] Becky approved page
[ ] Melissa approved page
[ ] Fred approved page
[ ] James approved page
[ ] Naushin approved page
[ ] Claudia approved page
[ ] Share page with Exeter and invite feedback
[ ] Revise with Exeter's suggestions

Definition of done

[ ] Page completed
[ ] Team reviewed and approved page?
[ ] Assign Fred to update the Schematron

With Peter to check it's OK to ditch this reference type.
If it is, the following tests will need to be amended:
err-elem-cit-high-6-2
The following removed:
err-elem-cit-periodical-2-1 to err-elem-cit-periodical-14-7

If Ok to remove will need to ask Editorial to remove periodical from the reference table in author guide https://reviewer.elifesciences.org/author-guide/initial

@FAtherden-eLife Peter has agreed we can remove this ref type.
Actions:

Delete the page on the Gitbook
Delete the reference to it in the author guide
delete the related schematron rules
delete any references to it anywhere else on the GitBook.

Would you like me to take any of these actions?

Many thanks @Melissa37. Please could you delete the page? I am unable to do that (I don't have permission to merge in GitBook atm). I'll take on the rest.

I've deleted the page :-)


Write an aspect implementation for shellcheck rule

This needs upstream support via https://github.com/bazelbuild/rules_shell/issues/16

Note that https://github.com/aspect-build/rules_lint supports shellcheck. Do you still want to maintain this one?


[proposal] sound/buf: rename to sndbuf, sbuf or something more specific than buf

Based on the Code Review Comments suggestions for Package Names and the Package names blog post.

Packages named util, common, or misc provide clients with no sense of what the package contains. This makes it harder for clients to use the package and makes it harder for maintainers to keep the package focused.

One option would be to rename the buf package to sndbuf, sbuf (sbuf would be similarly named as sio) or something along those lines. This also lets clients use buf as a variable name without having to rename the buf package locally.

Yes in general the package naming suggestions are good.
However, for this one I was unable to come up with a reason to decide between the alternatives such as you mention).   Also sio took a good deal of thought -- but I really didn't like sound/io and soundio seemed too long to me for something which I anticipate may be used frequently.
Since its early, we can still change the names.  But I'd like to see if others have preferences before changing names:
Any opinions out there?

sndbuf
sbuf
others?

Seems unlikely we'll get other opinions, so I just renamed it.  For whatever reason, I chose sndbuf.


Add support for SendGrid's unique arguments

SendGrid's unique arguments allow attaching a unique identifier to each email which can be used for tracking:
https://sendgrid.com/docs/for-developers/sending-email/unique-arguments/
SendGrid's Event API emits events that also contain these identifiers, allowing emails and events to be linked:
https://sendgrid.com/docs/for-developers/tracking-events/event/
Support for unique arguments would be a great addition to the SendGridHelper, which already supports a similar feature - adding categories to emails using the with_categories/2 function:
https://hexdocs.pm/bamboo/Bamboo.SendGridHelper.html#with_categories/2

Thanks for opening this issue @jason-pather. I'd be happy to review a PR for this, if you or others feel up for it. I imagine having a function like SendGridHelper.with_unique_args(email, args) would be good.

I create a PR to support this one. Please kindly review my PR.
Thank you.


Update README.md in build your own docker section

Update build your own docker section in README.md

Hey @versus,
Thanks for making this contribution. But we do have a make docker-build command which would directly create a docker image for a user.
Do you think, this should suffice? May be we can document the make docker-build command

I don't mind

Hi @versus , I've acommodated your commits into an updated pr #555 . PTAL and verify the instructions if they work for you. closing this.


Docker network / socket issues

Two issues here.

Docker networking doesn't work after boot (before I upgraded to unstable, restarting docker fixed that. --net host works too)
systemctl restart docker doesn't recreate the socket /var/run/docker.sock

So here is bascially what happens:
$ docker run ...
Error response from daemon: 404 page not found

$ sudo systemctl restart docker

$ docker run ...
Cannot connect to the Docker daemon. Is the docker daemon running on this host?

$ sudo file /var/run/docker.sock
/var/run/docker.sock: cannot open `/var/run/docker.sock' (No such file or directory)

Journal logs:
level=warning msg="Usage of loopback devices is strongly discouraged for production use. Please use `--storage-opt dm.thinpooldev` or use `man docker` to refer to dm.thinpooldev section."
level=warning msg="Running modprobe bridge br_netfilter failed with message: , error: exec: \"modprobe\": executable file not found in $PATH"
level=warning msg="Running modprobe nf_nat failed with message: ``, error: exec: \"modprobe\": executable file not found in $PATH"
level=info msg="Firewalld running: false"
level=info msg="Default bridge (docker0) is assigned with an IP address <IP_ADDRESS>/16. Daemon option --bip can be used to set a preferred IP address"
level=warning msg="Your kernel does not support kernel memory limit."
level=warning msg="Your kernel does not support cgroup cfs period"
level=warning msg="Your kernel does not support cgroup cfs quotas"
level=info msg="Loading containers: start."
level=info msg="Loading containers: done."
level=info msg="Daemon has completed initialization"
level=info msg="Docker daemon" commit=76d6bc9a execdriver=native-0.2 graphdriver=devicemapper version=1.9.0
level=info msg="Processing signal 'terminated'"
level=info msg="API listen on /var/run/docker.sock"
level=warning msg="Usage of loopback devices is strongly discouraged for production use. Please use `--storage-opt dm.thinpooldev` or use `man docker` to refer to dm.thinpooldev section."
level=warning msg="Running modprobe bridge br_netfilter failed with message: , error: exec: \"modprobe\": executable file not found in $PATH"
level=warning msg="Running modprobe nf_nat failed with message: ``, error: exec: \"modprobe\": executable file not found in $PATH"
level=info msg="Firewalld running: false"
level=info msg="Default bridge (docker0) is assigned with an IP address <IP_ADDRESS>/16. Daemon option --bip can be used to set a preferred IP address"
level=warning msg="Your kernel does not support kernel memory limit."
level=warning msg="Your kernel does not support cgroup cfs period"
level=warning msg="Your kernel does not support cgroup cfs quotas"
level=info msg="Loading containers: start."
level=info msg="Loading containers: done."
level=info msg="Daemon has completed initialization"
level=info msg="Docker daemon" commit=76d6bc9a execdriver=native-0.2 graphdriver=devicemapper version=1.9.0

The networking issue on boot seems to be fixed now, but still no socket after restart.

Setting socketActivation = false fixes it. With it enabled, I get this in the logs:
Dec 07 18:02:44 thinkpad docker[4948]: time="2015-12-07T18:02:44.275389920+01:00" level=warning msg="Your kernel does not support kernel memory limit."
Dec 07 18:02:44 thinkpad docker[4948]: time="2015-12-07T18:02:44.275565255+01:00" level=warning msg="Your kernel does not support cgroup cfs period"
Dec 07 18:02:44 thinkpad docker[4948]: time="2015-12-07T18:02:44.275603085+01:00" level=warning msg="Your kernel does not support cgroup cfs quotas"
Dec 07 18:02:44 thinkpad systemd[1]: libcontainer-4948-systemd-test-default-dependencies.scope: Scope has no PIDs. Refusing.
Dec 07 18:02:44 thinkpad docker[4948]: time="2015-12-07T18:02:44.281643862+01:00" level=info msg="Loading containers: start."
Dec 07 18:02:44 thinkpad docker[4948]: ..........................................................................................................................................................................
Dec 07 18:02:44 thinkpad docker[4948]: time="2015-12-07T18:02:44.324232824+01:00" level=info msg="Loading containers: done."
Dec 07 18:02:44 thinkpad docker[4948]: time="2015-12-07T18:02:44.324258519+01:00" level=info msg="Daemon has completed initialization"

Wondering if the Scope has no PIDs. Refusing. error is related.
@lethalman

@jgillich you mean socketActivation = true? That helped me.

@domenkozar It's true by default, I had to set it to false.

Disabling socketActivation fixes the issue for me too

Likewise, I just moved from 15.09 to unstable, and had to set virtualisation.docker.socketActivation = false; to get Docker working again.

Well, in my case it just takes a few moments(~20seconds) to start-up, you
can just wait a bit and it will start.
On Sun, Feb 14, 2016 at 1:11 PM Christopher Martin<EMAIL_ADDRESS>wrote:

Likewise, I just moved from 15.09 to unstable, and had to set virtualisation.docker.socketActivation
= false; to get Docker working again.
—
Reply to this email directly or view it on GitHub
https://github.com/NixOS/nixpkgs/issues/11478#issuecomment-183880642.

@offlinehacker even after five minutes socketActivation = true doesn't work for me

@jgillich any updates?

No, I'm not even using NixOS currently. But feel free to look into it yourself.

i've solved this by systemctl restart docker.socket. we can close this issue then.

No, that's no a solution. FWIW, there's a similar issue with socket activation o n Ubuntu Xenial: https://github.com/docker/docker/issues/23793

docker is also missing the modprobe binary - usually such firewall modules are automatically loaded by iptables but maybe we could add the binary to the paths to silence the warning.


Improve testing, add manual (slow) test of many packages

[ ] I have added an entry to docs/changelog.md

Summary of changes
This was originally part of a branch converting venv_metadata_inspector.py to use modern libraries.  To verify I had the new venv_metadata_inspector.py working I wanted to test it across MANY packages.  After everything was working I split this new testing capability into its own branch and PR to make it easier to parse.
Notable changes:

Add package_info.py to tests/ which contains dict PKG with "package name" keys, and containing data on each package, which can be used by tests

'spec' sub-key contains a standard pipx testing version for each package for more deterministic tests
other sub-keys contain information about the package such as apps, and apps of dependencies

Add test_install_all_packages.py which is only run manually (nox -s test_all_packages), and tests pipx installation of 86 different packages, both with and without dependencies.

Output is not the usual pytest PASS or FAIL, but text files reporting on which packages: installed with the pipx tests' cleared system PATH, installed with the original PATH, or didn't install successfully with either.

Add another Github workflow triggered via workflow_dispatch to exercise the above testing of 86 packages.  This can be activated only through the Github web UI, and does not run automatically.

All separate OS's reports are combined into a master report and provided as an Artifact for download.

Modified the prebuild_wheels function in noxfile.py to hopefully be cleaner.  It also now expects a list of each end package to build all dependency wheels for, not specific dependency wheels.  This should make specifying wheels easier as you don't have to track down each specific dependency that is problematic.


Consider adding Firebase performance monitoring

https://firebase.google.com/docs/perf-mon/get-started-web
This could monitor outgoing network requests to spot HTTP errors on the client-side.

Added this in 2795d1bb630f1078bf319755e1df50ca3821ac5e
I need to give Firebase some time to do some analysis of the logs.


Update for R 3.5.1

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Re-rendered with the latest conda-smithy
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@bgruening This is ready to merge


[EmbeddingAPI-autocase] Add autocase for XWalkView API loadExtension

-Add autocase for XWalkView API loadExtension
-Cover the XWalkActivity and XWalkInitializer two ways
Impacted tests(approved): new 2, update 0, delete 0
Unit test platform: [Android]
Unit test result summary: pass 2, fail 0, block 0
BUG=https://crosswalk-project.org/jira/browse/XWALK-6017

@Shao-Feng please help to review.


Refactor backend

User story

As a backend developer
I want the backend to be refactored
So that it is easier to work on it afterwards

Acceptance criteria

everything which is in the API is fulfilled
front and backend allignment in advance

Definition of done

Approved by product owner
Tests have been written (e.g. Unit test, integration test etc..)
Code has been peer reviewed and approved
No syntax or runtime errors emerged
Code has to be included in the release candidate

TODOs

refactor according to Project.yaml Part 1 (import endpoints)

[ ] GET, POST /projects

[ ] GET, PUT /projects/{projectID}

[ ] GET /productareas

refactor according to Project.yaml Part 2 (currently not import endpoints)

[ ] POST, PUT, DELETE /projects/{projectID}/users

refactor according to Product.yaml

[ ] GET, PUT /products/{productID}

[ ] GET, POST /projects/{projectID}/products

refactor according to Rating.yaml

[ ] GET /ratings

[ ] GET, POST, PUT /projects/{projectID}/ratings


Increase size of Name.author to 255 [Delivers #147238161]

The limit needed to be increased for a recent Name. See Pivotal #147238161.

Write migration.
Hand-test migration by migrating up and down, checking resulting schema.
Migrate

Coverage remained the same at 88.323% when pulling a331a7f155c9b3dd0f35833ea248bb1bc3c2b3ed on JoeCohen:increase-author-size into 0937ec978716008b0489fba40e1dcea28a521e14 on MushroomObserver:master.

Forgot to see if there was a limit in Rails (in addition to the DB).  There is, so I have to fix this.


Adding sample for commercetools GraphQL binding

Signed-off-by: Harry Kimpel<EMAIL_ADDRESS>This sample creates a microservice with an output binding to commercetools.

@harrykimpel - Can you update the top level ReadMe file, to include this sample in the table of samples with a description?
Otherwise looks great!

@harrykimpel - Can you update the top level ReadMe file, to include this sample in the table of samples with a description? Otherwise looks great!

@msfussell done


Can't use LLDB to attach to wasmtime 16 anymore

Attaching to wasmtime with LLDB to step through Rust code in the WebAssembly module stopped working after switching to wasmtime 16. It still worked perfectly fine on wasmtime 15.0.1. These are all the changes on my side (i.e. only version bumps):
https://github.com/LiveSplit/livesplit-core/commit/23e31b3b7edb2badaa01050e9e946404e2e98610
I don't see anything in the changelog indicating that something changed regarding the DWARF support.

Do you perhaps depend on Wasmtime with default-features = false? If that's the case the support for this was moved behind a debug-builtins feature which will need to be enabled.

Yeah that seems to fix it. However it seems like that this is not documented at all:

The changelog doesn't mention it.
The crate features section doesn't mention it: https://docs.rs/wasmtime/16.0.0/wasmtime/index.html#crate-features
The debug_info function on the Config isn't feature gated by it, nor mentions it: https://docs.rs/wasmtime/16.0.0/wasmtime/struct.Config.html#method.debug_info

Good point! I've pushed https://github.com/bytecodealliance/wasmtime/pull/7736 to add some docs.


How to make this work with crud?

Im trying the field examples on
https://laravel-backpack.readme.io/docs/crud-fields
to create something like this:
https://camo2.githubusercontent.com/e442e4819b19e196ee37e53331bac52d5a4f7a8d/68747470733a2f2f646c2e64726f70626f7875736572636f6e74656e742e636f6d2f752f323433313335322f6261636b7061636b5f7065726d697373696f6e6d616e616765725f757365722e706e67

I'm sorry, I don't understand. What's not working?

Oooh, I understand now. You're saying there's no documentation for that the checklist and checklist_dependency field types.
You're right, thank you for the issue, the documentation has been updated with the basic field attributes. Check out https://laravel-backpack.readme.io/docs/crud-fields#checklist_dependency


[REVIEW] Fixes #81: remove Python 2.7 builds, add CUDA 9.2 builds, default to CUDA 9.2

It looks like Python 3.7 builds aren't really available via conda / pip yet so I'm going to remove Python 3.7 and stick to just 3.5 and 3.6.

@mike-wendt Can you review before merge?


Prepare S2N CI for branch name change

Description of changes:
Remove any specific reference to S2N's branch name in preparation to change our default branch name.
The documentation for source_version says: "If not specified, the default branch's HEAD commit ID is used." We leave source_version empty in other CodeBuild configs: https://github.com/awslabs/s2n/blob/master/codebuild/integ_codebuild.config#L29
Testing:
Example entry in changeset:
INFO:root:Summary of changes:
	Action                   Modify
	LogicalResourceId    s2nstufferpemfuzztestRule
	PhysicalResourceId   s2nstufferpemfuzztestEvernt
	ResourceType         AWS::Events::Rule
	Replacement               False
	Scope                ['Properties']
	Details              [{'Target': {'Attribute': 'Properties', 'Name': 'Targets', 'RequiresRecreation': 'Never'}, 'Evaluation': 'Dynamic', 'ChangeSource': 'ResourceAttribute', 'CausingEntity': 's2nFuzzScheduled.Arn'}]

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Do we plan on removing other references in a different PR?
https://github.com/awslabs/s2n/search?q=master&unscoped_q=master

Not sure we were going to rename variables with master in them?

Codecov Report

Merging #2145 into master will decrease coverage by 0.06%.
The diff coverage is 74.28%.

@@            Coverage Diff             @@
##           master    #2145      +/-   ##
==========================================
- Coverage   81.07%   81.00%   -0.07%
==========================================
  Files         247      247
  Lines       18390    18398       +8
==========================================
- Hits        14909    14904       -5
- Misses       3481     3494      +13

Do we plan on removing other references in a different PR?
https://github.com/awslabs/s2n/search?q=master&unscoped_q=master

Eventually we'll likely want to change everything named "master" that we can control, but for now the goal of this PR is to prepare S2N for the branch name change.


posm

Related Issue
Which issue does this pull request resolve?
Description of changes

closing in favor of #295


patch windows lld-link error

This should fix the failure in #4453.

Yeah, I'm sorry, I've been getting strange errors and windows CI currently takes very long.


[BUG] Access Dictionary from multiple thread cause the app to crash sometimes

Currently when we open a vault , it load crypto balance for all the coins at the same time ,  however a lot places we use dictionary to cache data , and dictionary is not threadsafe , and not safe to be accessed from multiple thread

This has been fixed


Protorev smarter logic and more testing

What is the purpose of the change
This PR adds more testing to x/protorev and improves the arb calculation logic to be more efficient.
Brief Changelog

Given a route, we now calculate if the minAmountIn is profitable as a pre-check. If minAmountIn is not profitable, then the route is not profitable and we don't run the full binary search algo. This will make Protorev take much less compute time in production compared to its previous design (which would run the full binary search even when a route has no-arb). We only increment the pool point counter if the trade is profitable, thereby saving us compute for swaps that create no backrunning opportunity.
Given a route, we now calculate if the maxAmountIn and maxAmountIn + 1 profit is increasing as a pre-check and increase the range if so. If the profit from maxInputIn is still increasing, this means that we need to increase the range to capture the max profit.
Adds tests that verifies the limit/point system works properly, >3 pool routes work, and other denom besides osmo/atom work.
Deprecate hot routes from being included in genesis state for simplicity.
Add E2E testing that

Checks that the module is correctly init on start
Checks that the module can correctly spot a back running opportunity after a swap
Checks that the module executes a profitable cyclic arbitrage trade
Checks that the module did not mint or alter the supplies from the bank

Add support for gamm swap msgs
Deprecate atom from the list of base denoms that are used on genesis for route creation

Testing and Verifying

All previous tests pass with new changes
Added a test to ensure range extension works properly
Added a test for swapExactAmountOut
Added benchmark testing
Added doomsday testing to ensure point system works properly and doesn't allow protorev to keep running
Adds tests for generalized denoms
Adds a test to ensure panic catching is handled properly. This currently FAILS. This is on purpose, this PR is not to be merged until https://github.com/osmosis-labs/osmosis/issues/4180 is resolved
Add test for gamm msg swaps
Add tests for E2E (as described above)

Another thing I noticed is that we still have a hardcoded denom for atom: https://github.com/osmosis-labs/osmosis/blob/e6c1ba6006a3ed2a414e14e1ad3e53b814d83f81/x/protorev/types/constants.go#L8
This is no longer used in protorev itself, but used throughout our test suite. Is there a way for us to move this easily to only be for test suite and not in any of the core module files (to avoid changing all the tests that reference it, but not have any unnecessary code in core module files)

Another thing I noticed is that we still have a hardcoded denom for atom:
https://github.com/osmosis-labs/osmosis/blob/e6c1ba6006a3ed2a414e14e1ad3e53b814d83f81/x/protorev/types/constants.go#L8
This is no longer used in protorev itself, but used throughout our test suite. Is there a way for us to move this easily to only be for test suite and not in any of the core module files (to avoid changing all the tests that reference it, but not have any unnecessary code in core module files).
I think this is a non-issue though

Update, I deprecated it from the module.


Historical Data Loading

Add a system for choosing the period in which to launch the Backtest directly with API Request.
Utility:
If we do x4 but for 2 years we do x1.05, this can help to understand the stability of our algorithm and therefore to understand if over a "calm" period it is profitable or not.
Good example:

Important feature that has to be made soon

Done with the -start_ts and -end_ts parameters in plotly and api.


Figure out why QGIS Vector Tiles Reader compatibility plugin is not able to read our tilejson url.

Add the following end point:
/capabilities/$map/metadata.json
Where the json returned follows the follow spec:
https://github.com/geometalab/Vector-Tiles-Reader-QGIS-Plugin/wiki/Help#metadatajson
This will allow QGIS to access tiles from Tegola directly.

Would this be in the cache directory? Or at a particular URL? I guess how do you envision this being used?

This might not be an answer, but here's what I was trying to do:

After clicking save, then connect, it shows this:

I have also tried with this url: https://osm.tegola.io/maps/osm/{z}/{x}/{y}.pbf.
Eventually, if we could get the plugin to work with our tiles and styles then it will help us transform our styles for qgis much more quickly. I imagine there will be some things that will still need to be hand-styled in qgis but not as many as if we started from scratch.

From the spec, it's my understanding that the endpoint should be /maps/:map/metadata.json for the metadata since the tiles are being served from /maps/:map/:z/:x/:y.pbf and the plugin assumes a specific file structure.

@PetersonGIS After looking into this, I believe the endpoint you should use is /capabilities/:map without the trailing metadata.json. Let me know if this still doesn't work.

I just checked this against https://osm.tegola.io/capabilities/osm and it gave a Loading error: SSL handshake failed. So that is something new to look into...

Thanks for the tips @ear7h . I finally got the QGIS Vector Tile Plugin to load up some of our vector tiles with the following URL: https://osm.tegola.io/capabilities/osm. I wonder if the server was down when you tried it before. Can you double-check that it is working for you at this time?

@PetersonGIS can you send over a screen shot of your settings? I still get an error message "None" when trying to connect.

This one is a better screenshot. It is connecting to the TileJSON URL here and providing all the layers. (Note that with this plugin it is best to load a layer such as ne_10m_admin_0 first so you can zoom way in first.)
Interestingly it is not loading up the style.json at all, except for the background color. I still haven't figured out that piece of the puzzle. So the colors shown here are definitely not the camo style.

strange.  You're using windows, right?

Yes

Try removing the tile layers and reloading after using Vector > Vector Tiles Reader > Clear Cache. Or create a new connection and see if that works.

@PetersonGIS, I've (re)installed QGIS 2.18.15 along with the Vector Tiles Reader QGIS Plugin on OS X. I'm using http://localhost:7070/capabilities/osm.json as the TileJSON URL and http://localhost:8080/nautical_active.json as the GL Style JSON URL and the combo looks promising.
What kills the load is
2018-04-01T13:53:18	0	Creating styles from: http://localhost:8080/nautical_active.json
2018-04-01T13:53:18	0	Styles will be written to: /var/folders/q2/3wp7snyh8xn46j008k8wdqr80000gn/T/vector_tiles_reader/styles/tegola-openseamap local
2018-04-01T13:53:18	2	Style generation failed: (<type 'exceptions.ValueError'>, ValueError("invalid literal for int() with base 10: 'wetland'",), <traceback object at 0x129830cb0>), Traceback (most recent call last):
			  File "/Users/erictheise/.qgis2/python/plugins/vector_tiles_reader/vtr_plugin.py", line 409, in _create_styles
			    core.generate_styles(data, output_directory, web_request_executor=self._load_style_data)
			  File "/Users/erictheise/.qgis2/python/plugins/vector_tiles_reader/ext-libs/mapboxstyle2qgis/core/__init__.py", line 53, in generate_styles
			    styles = process(style_json)
			  File "/Users/erictheise/.qgis2/python/plugins/vector_tiles_reader/ext-libs/mapboxstyle2qgis/core/__init__.py", line 89, in process
			    qgis_styles = get_styles(l)
			  File "/Users/erictheise/.qgis2/python/plugins/vector_tiles_reader/ext-libs/mapboxstyle2qgis/core/__init__.py", line 277, in get_styles
			    all_values.extend(get_properties_by_zoom(layer, "paint/fill-color", is_color=True, default="rgba(0,0,0,0)"))
			  File "/Users/erictheise/.qgis2/python/plugins/vector_tiles_reader/ext-libs/mapboxstyle2qgis/core/__init__.py", line 498, in get_properties_by_zoom
			    "zoom_level": int(lower_zoom),
			ValueError: invalid literal for int() with base 10: 'wetland'

and indeed the hunk of JSON style for 'wetland' looks suspicious.
    {
      "id": "landuse_areas_z13",
      "type": "fill",
      "source": "osm",
      "source-layer": "landuse_areas",
      "minzoom": 13,
      "maxzoom": 24,
      "layout": {
        "visibility": "visible"
      },
      "paint": {
        "fill-color": {
          "property": "type",
          "type": "categorical",
          "default": "transparent",
          "stops": [
            [
              "wetland",
              "rgba(227, 233, 226, 1)"
            ],

Is this right? Every occurrence of stops I've come across has a numerical first value corresponding to a zoom level and the QGIS/Python error suggests it's expecting an integer.

After more digging, our use of "type": "categorical"should allow for strings as stops. I opened an issue at the plugin repo.

I am concerned about the comment that this plugin "was a semester student project which actually came to an end".

Yes, was just coming around to this idea of the plugin not being very stable right now and perhaps not being as useful as I originally thought. For example, I got one stylesheet to work with the plugin and then it promptly minidumped and shutdown when zoomed out. Thinking we may want to stop working on this for now. Thoughts?

Well, something's going to evolve to fill this niche and I could submit a pull request to cover this case. Can't tell if that's the only thing blocking us or just the tip of the iceberg.

I agree with @erictheise, something is going to need to fill this niche. I also foresee an issue with parsing the new Mapbox GL expressions. The stops syntax is being deprecated.

Just checking in, and hoping to help out.  I found about this QGIS plugin because of this open issue (so thanks for the discussion)

Is this issue still open because

Tegola's TileJSON?

e.g., http://localhost:8080/capabilities/cities.json
which is seems compliant as "tilejson":"2.1.0",  or,

Mapbox GL expressions?  #issuecomment-377996308

I assume the issue is open due to 2)  — the specific nautical Style with stops that @erictheise refers to.

@roblabs to be honest, I'm not quite sure where the issue is. I would suspect on the style definition as tegola is returning back the correct tileJSON. I have not had much of a chance to dig into it though. Last I recall, the plugin was a student project and may have lost momentum. It would be an amazing addition to the QGIS ecosystem though.

I'm getting similar issues. Thanks to @ear7h 's suggestion I used the following for my connection string:
http://localhost:9091/capabilities/swellendam

(I had initially tried an {x}/{y}/{z} style url which gave the  'none' error as shown above.)
And now I see my test layers:

However when I add these to my project, they show up as empty QGIS layer groups:

Just an update that by tweaking my  id fieldname to use fid as below (I am serving the tiles from a geopackage):
id_fieldname = "fid"

my vector tiles served from tegola now work:

@timlinux nice! is this with QGIS 3.0? It would be nice to have some of these screenshots in a guide under the tegola.io docs. Would you be able to help with that?

I just checked with 3.3-dev and it recognizes them just fine

I just tried this on 3.2 and it's also working great! I'm going to call this issue closed!


[DRAFT] Merge next down to develop

Closes: #4338
What's Changed

TODO

[ ] Explanation of Change(s)
[ ] Added change log fragment(s) (for more information see the documentation)
[ ] Attached Screenshots, Payload Example
[ ] Unit, Integration Tests
[ ] Documentation Updates (when adding/changing features)
[ ] Example Plugin Updates (when adding/changing features)
[ ] Outline Remaining Work, Constraints from Design

This shouldn't need a separate branch. We should be able to go straight from next -> develop


jvector supports filter search

Does jvector supports filter search? I didn't find code related to filter search, such as metadata filtering

JVector is only a vector index.  It's designed to be combined with other indexes if you want to add "metadata filtering".


The current implementation of Iterable::any_of does not allow infinite Iterables

This implementation is more compile-time efficient than the previous one, but it does not allow for infinite Iterables. We could provide this implementation only for Foldables, since Foldables must be finite.

This was introduced by 46b4def732ed13bd9b70ffb1f523f706c1e19dbc.


White screen Issue with MapsUI.forms for Android

In my company project we have setup mapsui in our xamarin forms app. We found the strange behaviour. If you are on the map and then you turn the phone in standby, then you turn it off the map is shown in white screen.
Steps to reproduce:

Create a simple stack layout with mapsui included:

Start the app

Wait for 30-60 seconds phone to go standby

Turn on the phone and get in the app

You will see a white screen.

Has anyone encountered this issue or there is a workaround that I can use ?

Which version do you use?
What happens if you zoom to the full extent after it has gone white?

Closing, outdated, not enough information.


Improved docs

Please mark as invalid and spam, this is an obvious attempt to get a free t-shirt by 'contributing'(hacktoberfest)
This will also ban the user for trying to abuse the system by doing marginal effort

Thanks for flagging. Closed.


Updates for properties 0.4.0

Codecov Report

Merging #24 into master will increase coverage by 0.09%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #24      +/-   ##
==========================================
+ Coverage   85.38%   85.47%   +0.09%
==========================================
  Files          10       10
  Lines         472      475       +3
==========================================
+ Hits          403      406       +3
  Misses         69       69

Impacted Files
Coverage Δ

omf/surface.py
90.74% <ø> (ø)
:arrow_up:

omf/pointset.py
95.23% <ø> (ø)
:arrow_up:

omf/__init__.py
100% <100%> (ø)
:arrow_up:

omf/base.py
88.46% <100%> (+0.14%)
:arrow_up:

omf/data.py
75.58% <100%> (ø)
:arrow_up:

omf/fileio.py
77.02% <100%> (+0.63%)
:arrow_up:

Continue to review full report at Codecov.

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


[Enterprise] Update rebalance doc

Adds context and additional checks to the manual rebalance doc in Enterprise.
TODO:

[ ] Confirm that I'm not lying anywhere (disk space wording and write throughput wording)

@desa - when you have time could you take a look at this rebalance doc? (The diff is useless because I basically rewrote everything.)

@pauldix, thank you!!! I made the requested changes.
There's one last thing: I added a note about how to determine shard sizes (@gunnar gets all the credit for that command) but I wasn't sure if big shards or small shards were ideal for moving and why. Is there a recommendation for this or will it depend on what users want/their setup?

Talked to @desa  and I think this is ready to go! Thanks again, @pauldix, @gunnaraasen, and @desa!


Update The Things Join Server Documentation

Summary
Based on the latest insights, we have identified a point in The Things Join Server documentation that needs to be updated.

Add the--unset version_ids flag to the CLI command in Activating Devices on Cloud section.

Why do we need this?
Currently, the CLI command to update the device configuration does not register the device in the application server resulting in a few issues.
What is already there? What do you see now?
CLI command for Activating Devices on Cloud.
What is missing? What do you want to see?
Update the below command in the Activating Devices on Cloud sub page. Ref: https://github.com/TheThingsIndustries/lorawan-stack-support/issues/743
ttn-lw-cli end-devices set test-app eui-0004a310001ff9e0 \
  --net-id 000013 \
  --lorawan-version 1.0.2 \
  --lorawan-phy-version 1.0.2-b \
  --frequency-plan-id EU_863_870 \
  --supports-join \
  --unset version_ids \
  --touch

How do you propose to document this?
....
Can you do this yourself and submit a Pull Request?
No.

Closed with #805


policy: Fix MapState.Equals()

Compare the entries of 'msA' and 'msB' rather than 'msB' against itself.
Simplify the body of the comparison function for readability.
Fixes: #28352

/test


Kubernetes network policy is not enabled between different nodes.

We are currently creating multiple instances on Oracle Cloud Infrastructure to build a Kubernetes cluster.
We are building it from scratch using kubeadm instead of OKE, assuming that it can be built in any environment such as on-premise.
When I installed Calico as a CNI plugin and configured the network policy for Kubernetes, the network policy setting does not work.
When you install Calico as a CNI plugin and configure the network policy settings for Kubernetes, the network policy settings do not work effectively when communicating between Pods running on different worker nodes, and communication becomes impossible.
I believe I am missing some settings needed to enable network policy settings even across different worker nodes, but I don't know what I am missing. Please help.
Current Behavior

I have confirmed that the network policy setting is enabled for pods running on the same worker node.
Also, with the network policy setting removed, Pods running on different worker nodes can communicate with each other.
The same applies to Calico's network policy and global network policy.
Even if you build multiple nodes on a single instance using minikube, we have confirmed that the network policy setting is enabled for communication between different nodes.
Your Environment

Calico version:  v3.17
Orchestrator version : Kubernetes
Operating System and version: CentOS 7

@kawamoto-taku-13 could you please give a bit more detail about what you're trying to do and what exactly is not working?

the network policy settings do not work effectively when communicating between Pods running on different worker nodes, and communication becomes impossible.

Basically, a bit more detail about the policies you've created, and what you mean by "do not work effectively"

@caseydavenport
There are three different systems a,b,c and two worker nodes, with one of the three systems located in each worker node.
NAME                        READY   STATUS    RESTARTS   AGE    IP               NODE       NOMINATED NODE   READINESS GATES
system-a-66658b869c-572tz   1/1     Running   0          114s   <IP_ADDRESS>   worker-1   <none>           <none>
system-a-66658b869c-dzh44   1/1     Running   0          114s   <IP_ADDRESS>      worker-2   <none>           <none>
system-b-7c89c67bbb-dj7xf   1/1     Running   0          9s     <IP_ADDRESS>   worker-1   <none>           <none>
system-b-7c89c67bbb-2j25m   1/1     Running   0          9s     <IP_ADDRESS>     worker-2   <none>           <none>
system-c-6984589967-kv8fj   1/1     Running   0          9s     <IP_ADDRESS>   worker-1   <none>           <none>
system-c-6984589967-kl2lx   1/1     Running   0          9s     <IP_ADDRESS>     worker-2   <none>           <none>

We want a and b to be able to communicate freely from each system, but c to be able to communicate only from b.
Before setting the network policy, all systems are able to communicate.

Connection sourceSystem:Worker node
Connection destinationSystem:Worker node
Communication enabled

system-a : worker-1
system-b : worker-1
yes

system-a : worker-1
system-b : worker-2
yes

system-a : worker-1
system-c : worker-1
yes

system-a : worker-1
system-c : worker-2
yes

system-a : worker-2
system-b : worker-1
yes

system-a : worker-2
system-b : worker-2
yes

system-a : worker-2
system-c : worker-1
yes

system-a : worker-2
system-c : worker-2
yes

system-b : worker-1
system-a : worker-1
yes

system-b : worker-1
system-a : worker-2
yes

system-b : worker-1
system-c : worker-1
yes

system-b : worker-1
system-c : worker-2
yes

system-b : worker-2
system-a : worker-1
yes

system-b : worker-2
system-a : worker-2
yes

system-b : worker-2
system-c : worker-1
yes

system-b : worker-2
system-c : worker-2
yes

When the network policy is set, the following will happen.
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: network-policy-ingress
spec:
  podSelector:
    matchLabels:
      app: system-c
  ingress:
  - from:
    - podSelector:
        matchLabels:
          app: system-b

Connection sourceSystem:Worker node
Connection destinationSystem:Worker node
Communication enabled
Expected results

system-a : worker-1
system-b : worker-1
yes
yes

system-a : worker-1
system-b : worker-2
yes
yes

system-a : worker-1
system-c : worker-1
no
no

system-a : worker-1
system-c : worker-2
no
no

system-a : worker-2
system-b : worker-1
yes
yes

system-a : worker-2
system-b : worker-2
yes
yes

system-a : worker-2
system-c : worker-1
no
no

system-a : worker-2
system-c : worker-2
no
no

system-b : worker-1
system-a : worker-1
yes
yes

system-b : worker-1
system-a : worker-2
yes
yes

system-b : worker-1
system-c : worker-1
yes
yes

system-b : worker-1
system-c : worker-2
no
yes

system-b : worker-2
system-a : worker-1
yes
yes

system-b : worker-2
system-a : worker-2
yes
yes

system-b : worker-2
system-c : worker-1
no
yes

system-b : worker-2
system-c : worker-2
yes
yes

Communication from system-b:worker-1 to system-c:worker-2 and from system-b:worker-2 to system-c:worker-1 is no longer possible.
The following configuration file works as expected, but since there may be more systems in the future, I would like to solve this problem with an ingress to system-c.
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: network-policy-egress
spec:
  podSelector:
    matchLabels:
      app: system-a
  policyTypes:
  - Egress
  egress:
  - to:
    - podSelector:
        matchLabels:
          app: system-b

Since I have only been working with Kubernetes for a short time, I did not know how to check.
I have built a Kubernetes cluster using kubeadm, and I have confirmed that the configMap of kube-proxy includes the clusterCIDR setting.
I'm sorry, but can you please tell me how to check the details?

Perhaps join us in slack http://slack.projectcalico.org/ and we can talk you through troubleshooting steps?


tests/drivers/counter/counter_basic_api is very long when counter is RTC

Describe the bug
Testing the tests/drivers/counter/counter_basic_api/  with RTC counter is  very very long until it ends.
It takes about 17minutes to complete when RTC counter is enabled.
When timer counter is enabled test PASSED in a few seconds
Note that following commit 51f452bbf005ca81c10916e24e93c4a4524769d5
the test duration increased from about 5 minutes (before commit) to about 17 minutes (after commit)
The timeout: 600 becomes too low
Probably present on any platform where RTC has 1Hz counter unit
--> detected on stm32 nucleo board when counter RTC is enabled,
To Reproduce
Steps to reproduce the behavior:

west build -p auto -b nucleo_f746zg tests/drivers/counter/counter_basic_api/
west flash
wait for test completion

Expected behavior
shorter time to full test execution
Impact
CI and twister fails due to timeout
in the tests/drivers/counter/counter_basic_api/testcase.yaml the timeout: 600  is really not enough
Failure due to timeout with twister on :

stm32f3_disco.overlay
nucleo_wb55rg.overlay
nucleo_l152re.overlay
nucleo_h743zi.overlay
nucleo_g474re.overlay
nucleo_g071rb.overlay
nucleo_f746zg.overlay
nucleo_f429zi.overlay
nucleo_f207zg.overlay
nucleo_f103rb.overlay
nucleo_f091rc.overlay

Logs and console output
*** Booting Zephyr OS build zephyr-v3.3.0-1285-g459935c09d06 ***
Running TESTSUITE counter_basic
===================================================================
START - test_all_channels
Testing rtc@40002800
 PASS - test_all_channels in 3.103 seconds
===================================================================
START - test_cancelled_alarm_does_not_expire
Skipped for rtc@40002800
 PASS - test_cancelled_alarm_does_not_expire in 0.103 seconds
===================================================================
START - test_late_alarm
Skipped for rtc@40002800
 PASS - test_late_alarm in 0.103 seconds
===================================================================
START - test_late_alarm_error
Skipped for rtc@40002800
 PASS - test_late_alarm_error in 0.103 seconds
===================================================================
START - test_multiple_alarms
Skipped for rtc@40002800
 PASS - test_multiple_alarms in 0.103 seconds
===================================================================
START - test_set_top_value_with_alarm
Skipped for rtc@40002800
 PASS - test_set_top_value_with_alarm in 0.103 seconds
===================================================================
START - test_short_relative_alarm
Testing rtc@40002800
 PASS - test_short_relative_alarm in 3.472 seconds
===================================================================
START - test_single_shot_alarm_notop
Testing rtc@40002800
 PASS - test_single_shot_alarm_notop in 7.103 seconds
===================================================================
START - test_single_shot_alarm_top
Skipped for rtc@40002800
 PASS - test_single_shot_alarm_top in 0.103 seconds
===================================================================
TESTSUITE counter_basic succeeded
Running TESTSUITE counter_no_callback
===================================================================
START - test_set_top_value_without_alarm
Skipped for rtc@40002800
 PASS - test_set_top_value_without_alarm in 0.103 seconds
===================================================================
TESTSUITE counter_no_callback succeeded

------ TESTSUITE SUMMARY START ------

SUITE PASS - 100.00% [counter_basic]: pass = 9, fail = 0, skip = 0, total = 9 ds
 - PASS - [counter_basic.test_all_channels] duration = 3.103 seconds
 - PASS - [counter_basic.test_cancelled_alarm_does_not_expire] duration = 0.103s
 - PASS - [counter_basic.test_late_alarm] duration = 0.103 seconds
 - PASS - [counter_basic.test_late_alarm_error] duration = 0.103 seconds
 - PASS - [counter_basic.test_multiple_alarms] duration = 0.103 seconds
 - PASS - [counter_basic.test_set_top_value_with_alarm] duration = 0.103 seconds
 - PASS - [counter_basic.test_short_relative_alarm] duration = 3.472 seconds
 - PASS - [counter_basic.test_single_shot_alarm_notop] duration = 7.103 seconds
 - PASS - [counter_basic.test_single_shot_alarm_top] duration = 0.103 seconds

SUITE PASS - 100.00% [counter_no_callback]: pass = 1, fail = 0, skip = 0, totals
 - PASS - [counter_no_callback.test_set_top_value_without_alarm] duration = 0.1s

------ TESTSUITE SUMMARY END ------

===================================================================
PROJECT EXECUTION SUCCESSFUL

Environment (please complete the following information):

OS: Ubuntu
Toolchain SDK,0.15.2
Commit SHA e35733d2ff62a892cd0a5209820e671a9586e038

general issue as soon as the RTC (counting at 1Hz) is enabled


ipam: various minor cleanups

Noticed while working on #22762.
See commit messages for details.

/test

/test


Fix for perfect scrollbar

Fix for perfect scrollbar that doesnt appear on admin side menu
Reference issue #1744

@davodavodavo3 Thans man!

@tnylea why guys commented file types in media manager

Do you know?

I'am fixing media manager issue when double click on image he think that its an folder,
and I stumbled in this code

@davodavodavo3, that is unrelated to this issue.  Please try to keep the comments relevant

@davodavodavo3, that is unrelated to this issue.  Please try to keep the comments relevant

Where i can ask you questions?

Slack would be a good place to do that


[Feature] Introduce grouping in VMAS

This PR allows VMAS to use the MARL api with grouping.
Users will be able to provide a group_map to VMAS.
By default this will try to group agents named name_n into a group named "name".
In case at least one agent does not follow this convention and not group map is specified, VMAS will try to group all agents under the "agent" group

Ok I made all methods private.
I would like to keep the attributes public so that they can be accessed by libraries like BenchMARL.
I'll document them

ok now there shold be no bc changes and the public attributes should be all doxumented


Triggers isn't working on gamecube

BlueRetro firmware version
1.8.4
BlueRetro firmware specification
HW1
BlueRetro firmware variant
Universal
BlueRetro hardware type
External adapter with detachable cord
Manufacturer
BlueRetro Gaming Store
System used
Nintendo GameCube
Bluetooth controller brand & name
8bitdo Ultimate, Gamesir T4 pro, 8bitdo M30, 8bitdo SN30 Pro
What is problem? (only list ONE problem per report)
When I paired one of this controllers using Switch mode the triggers works fine but when a pair the second one using Switch or Xinput the triggers stop working on both of them, using Visual_Controller_Test https://wiibrew.org/wiki/Visual_Controller_Test, I had the proof of this failure.
What did you expect to happen?
Pair more than one controller and works fine
Attach files like logs or Bluetooth traces here

8bitdo Ultimate (Button pressed order)
Left analog up
Left analog down
Left analog left
Left analog right
dpad up
dpad down
dpad left
dpad right
home
star
+
Y
X
A
B
right analog up
right analog down
right analog left
right analog right
L3
R3
P1
P2
Gamesir T4 PRO
LT
LB
RT
RB
Left analog up
Left analog down
Left analog left
Left analog right
dpad up
dpad down
dpad left
dpad right
home
select
start
turbo
Y
X
A
B
right analog up
right analog down
right analog left
right analog right
L3
R3
M1
M2
M3
M4
trace_files.zip

I noticed l and r were not working on mine (internal blue tooth) to

Try to reload the merge trigger preset:
https://github.com/darthcloud/BlueRetro/wiki/BlueRetro-BLE-Web-Config-User-Manual#33---example-preset-load

reloading 1.8.3 firmware solved the problem. Definitely an issue with 1.8.4 firmware. Even deleted all the 4 files in file manager to test and same issue on 1.8.4.

reloading 1.8.3 firmware solved the problem. Definitely an issue with 1.8.4 firmware. Even deleted all the 4 files in file manager to test and same issue on 1.8.4.

Try to reload the merge trigger preset: https://github.com/darthcloud/BlueRetro/wiki/BlueRetro-BLE-Web-Config-User-Manual#33---example-preset-load

I'd already did and got the same problem.

reloading 1.8.3 firmware solved the problem. Definitely an issue with 1.8.4 firmware. Even deleted all the 4 files in file manager to test and same issue on 1.8.4.

I'll try today

Do let us know if it worked!

Worked !!!!!, after downgrading to 1.8.3. Thank you guys.

Worked !!!!!, after downgrading to 1.8.3. Thank you guys.

Great to hear! Now I hope 1.8.4 can get fixed

Are you sure you got the merged trigger preset loaded as in this example?
https://github.com/darthcloud/BlueRetro/wiki/BlueRetro-BLE-Web-Config-User-Manual#33---example-preset-load
So I tested this myself in v1.8.4 with 8bitdo SF30 and Ultimate controllers. I had the merged trigger preset loaded and in Wario World I was able to dash with R and also Slam the ground with A then R.
Can you guys run homebrew?
If so run this https://github.com/corenting/GC-Controller-Test/releases/tag/v1.2
and take a picture while you hold R to maximum and post here. I want to see the analog value.
Also can you take a screenshot of the mapping in the web configuration ( i need to see the first 32 entries)

Are you sure you got the merged trigger preset loaded as in this example? https://github.com/darthcloud/BlueRetro/wiki/BlueRetro-BLE-Web-Config-User-Manual#33---example-preset-load
So I tested this myself in v1.8.4 with 8bitdo SF30 and Ultimate controllers. I had the merged trigger preset loaded and in Wario World I was able to dash with R and also Slam the ground with A then R.
Can you guys run homebrew?
If so run this https://github.com/corenting/GC-Controller-Test/releases/tag/v1.2
and take a picture while you hold R to maximum and post here. I want to see the analog value.
Also can you take a screenshot of the mapping in the web configuration ( i need to see the first 32 entries)

Yeas I used the exlene gamecube controller pre config. Works perfectly on 1.8.3 but fails on 1.8.4

Well this bug is about the 8bitdo controllers. I'll look at the other bug later.

Well this bug is about the 8bitdo controllers. I'll look at the other bug later.

@darthcloud I think this issue is related to #849.
I just commented there that digital triggers only work if digital and analog triggers are merged. Digital triggers can't be mapped alone.
Is that behavior intentional?

@darthcloud Triggers also stop working when 2 or more DualSense controllers are connected to the same BlueRetro device. Tested on a Wii via the GameCube ports on firmware 1.9.1.

@darthcloud Triggers also stop working when 2 or more DualSense controllers are connected to the same BlueRetro device. Tested on a Wii via the GameCube ports on firmware 1.9.1.

Been having that problem since um I think 2 versions ago. Work around was getting all 4 exelene gamecube controllers connected and pressing l+r at the same time. or 3 holding it down while the last presses it and it normally happens. (can easily test this in mario kart double dash for the randomizer option)

This beta should fix it:
https://github.com/darthcloud/BlueRetro/actions/runs/8680779369

Fixed in v24.04

Issue is still prevalent. Despite me setting the preset correctly, Xbox Series X controller STILL cannot perform slam in Wario World.


Trim trailing / of configured registry

Pipeline and/or Tekton should trim trailing / of configured registry
Setting the registry with a trailing / such as the following causes failure: image-registry.openshift-image-registry.svc:5000/kabanero/
With pipelines release
https://github.com/kabanero-io/kabanero-pipelines/releases/download/0.6.0/default-kabanero-pipelines.tar.gz
{"level":"info","ts":1583432835.921106,"logger":"fallback-logger","caller":"logging/config.go:69","msg":"Fetch GitHub commit ID from kodata failed: \"KO_DATA_PATH\" does not exist or is empty"}
OUTPUTS_RESOURCE_DOCKER_IMAGE_URL_LOWERCASE=image-registry.openshift-image-registry.svc:5000/kabanero//sample-java-microprofile:e923b666fc3dedbfb6f635efbfc8eaf77eaebbf0
invalid reference format

Pull request created with the fix : https://github.com/kabanero-io/kabanero-pipelines/pull/256

Fix is merged.


Logging traces with level below severity logging.WARNING are disregarded

I noticed that my INFO traces weren't showing. Upon further inspection it seems that init_sct() is disregarding traces with severity less than logging.WARNING.
Specific piece of code:
https://github.com/neuropoly/spinalcordtoolbox/blob/d9a8a88fb2e0a6462a46db572ed1e222fe1a4681/spinalcordtoolbox/utils/sys.py#L51-L61
I'm assuming it's a mistake?

Nevermind I'm saying non-sense!


feat: preview data api extended for mysql

Description
This PR extends the /{datasourceId}/schema-preview API for MySQL plugin as well
As per designs We want to show the MySQL schema as well as preview on the datasource review page.

JUnit tests are not added as the feature is experimental, If we finalise on the feature in future, we should add JUnit tests, tracking here https://github.com/appsmithorg/appsmith/issues/26582
PR fixes following issue(s)
Fixes #26574

if no issue exists, please create an issue and ask the maintainers about this first

Media

A video or a GIF is preferred. when using Loom, don’t embed because it looks like it’s a GIF. instead, just link to the video

Type of change

Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
Chore (housekeeping or task changes that don't impact user perception)
This change requires a documentation update

Testing

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration.
Delete anything that is not relevant

[x] Manual
[ ] JUnit
[ ] Jest
[ ] Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own 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
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

/ok-to-test

/ok-to-test

Since this PR updates newly added API on server side, we cannot test it without the frontend, and these changes should not introduce any bugs in existing functionality as its a new API. In this case we can skip the testing and add test-plan-approved label.
CC: @prapullac @rohan-arthur @sumitsum


DataFrame.transform should ensure output has same index as input

I believe a very common application for DataFrame.transform is to compute a new column of a dataframe. This is one of the examples in pandas, see at the bottom https://pandas.pydata.org/docs/reference/api/pandas.DataFrame.transform.html
Effectively, this means that a very typical pattern is something like
ddf["new_col"] = ddf.groupby("<column>").transform(func)

Consider the following example
df = pd.DataFrame({
    'ints': [1, 2, 3],
    'grouper': [0, 1, 0]
})

ddf = dd.from_pandas(df, npartitions=2)
ddf["new"] = ddf.groupby('grouper').transform('first')['ints']

will raise a
ValueError: Not all divisions are known, can't align partitions. Please use `set_index` to set the index.

To make this work as expected, one has to sort the series index manually, e.g.
df = pd.DataFrame({
    'ints': [1, 2, 3],
    'grouper': [0, 1, 0]
})

ddf = dd.from_pandas(df, npartitions=2)
ddf["new"] = (
    ddf.groupby('grouper')
    .transform('first')
    .reset_index()
    .set_index('index')
)['ints']

While the above exception tells you that you should use set_index I believe this is not very intuitive for users since the output of a transform is a series which doesn't have a set_index. At the very least, the series should offer a method sort_index that effective performs reset_index().set_index()[self.name] for the user.
This obviously comes with a performance penalty but is ultimately required to use DataFrame.transform for assignments.
Note: An even less intuitive way to trigger this problem is by using dd.concat which provides a slightly less helpful exception
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
Cell In[173], line 1
----> 1 dask.dataframe.concat([ddf, first_series], axis=1).compute()

File ~/mambaforge/envs/dask-311/lib/python3.11/site-packages/dask/dataframe/multi.py:1295, in concat(dfs, axis, join, interleave_partitions, ignore_unknown_divisions, ignore_order, **kwargs)
   1293         return concat_unindexed_dataframes(dfs, ignore_order=ignore_order, **kwargs)
   1294     else:
-> 1295         raise ValueError(
   1296             "Unable to concatenate DataFrame with unknown "
   1297             "division specifying axis=1"
   1298         )
   1299 else:
   1300     if all(df.known_divisions for df in dasks):
   1301         # each DataFrame's division must be greater than previous one

ValueError: Unable to concatenate DataFrame with unknown division specifying axis=1

Note: whoever picks up the issue should also take a look at the original case, that has a reproduction example of concatenating DataFrames producing an incorrect result:

https://github.com/coiled/support-two-sigma/issues/32

@fjetter

While the above exception tells you that you should use set_index I believe this is not very intuitive for users since the output of a transform is a series which doesn't have a set_index. At the very least, the series should offer a method sort_index that effective performs reset_index().set_index()[self.name] for the user.

The output of the above .transform is a DataFrame:
In [1]: import pandas as pd

In [2]: df = pd.DataFrame({
   ...:     'ints': [1, 2, 3],
   ...:     'grouper': [0, 1, 0]
   ...: })

In [3]: df.groupby('grouper').transform('first').__class__
Out[3]: pandas.core.frame.DataFrame

but you're getting a single item out of it with __getitem__ accessor, and that's Series.
I agree, this is not intuitive that __getitem__ requires you to reset an index first. Looking at the docstring of our Groupby.transform:
https://github.com/dask/dask/blob/fd31b9b67e105f4c63b391f5c24959e39e27a0cc/dask/dataframe/groupby.py#L2489
It says:

This mimics the pandas version except for the following:

If the grouper does not align with the index then this causes a full shuffle.  The order of rows within each group may not be preserved.

It says " if the grouper does not align with the index", in fact it's checking if the grouper contains the index, which seems more restrictive. If your grouper contains the index, the __getitem__ will work fine:
In [22]: df2 = df.set_index('grouper')

In [23]: ddf2 = dd.from_pandas(df2, 2)

In [30]: ddf2['new'] = ddf2.groupby('grouper').transform('first', meta=expected)['ints']

In [31]: ddf2.compute()
Out[31]:
         ints  new
grouper
0           1    1
0           3    1
1           2    2

In our documentation, I don't see a a section for DataFrame.transform and DataFrame.GroupBy.transform. This looks like an omission.
I'm going to look into the issue.

Closed via https://github.com/dask/dask/pull/10184


Refactoring of ssh auth

Removing specific check from the general mixing and rather
overriding authentication_best_fit method. This method now
implements basic inheritance of ssh auth. So we can define
credentials on Provider level for all hosts and override
individual hosts with another credentials.

@jrafanie before you ask, tests are coming as another PR, we have task for writing tests for the whole OpenstackInfra overridden functionality. :-)

@Fryguy @blomquisg @Ladas What is the status of this PR?

@chessbyte also being reviewed

@Ladas is this still work in progress or ready for final review/merge?

@chessbyte it should be ready, I usually mark all non ready PRs as wip :-)

This PR looks good to me!  @blomquisg @Fryguy Please review.

Fine by me.


adding contentthread to sites

👋🏼 howdy, just adding contentthread.com to the sites lists data

Thank you!


RtcEngine.setCameraZoomFactor

I think there is an issue with the RtcEngine.setCameraZoomFactor.
I looked at the doc and some samples and they all expect this to work.
RtcEngine.setCameraZoomFactor(1.0)
When I look at the RtcEngine it says that the setCameraZoomFactor is a promise.
Is his only for IOS or? I am using react native

Never mind, I updated to version 2.3.3-alpha.6 and it worked, but I feel like the camera is still zoomed in even if I enter RtcEngine.setCameraZoomFactor(1)

@CyrusZei same problem for me, it was a bug on iOS, the last version 2.3.3-alpha.7 has fixed that.
But yes the camera is still zoomed.

I feel like the doc could have more examples. I mean how do I publish a stream and get the URL for it? so that I can add that into a video preview for others to watch?

RtcEngine.setCameraZoomFactor(1.0) is work fine for me. It just control the camera zoom ratio. you could find on our docs
I cannot reproduce it. If you means the camera is auto focusing, iOS platform will enable auto focusing as usual, so if you want to fixed that problem, Please wait for the next version, we will support gesture for iOS & android ASAP.
If you can please provider your demo project and paste github link here. I will do work around for you.

@Matrixbirds If you open up your iphone camera you will see that baseline of the zoom, but if you open up the agora camera when you broadcast you will see that it is "Zoomed".
I have got the zoom to work, but I feel like the camera is "zoomed". It feels like the zoom is set to 2.0 instead of 1.0

@CyrusZei @Matrixbirds  yes i agree, the camera is zoomed at the remote side and it is also not mirrored.
I did not try on android, because i don't have a device.

This might be a bug since I talked to Agora on the slack channel

Okej guys,
I got help from Agora and this fixed it for me.
in your
videoEncoderConfig: {         width: 360,         height: 480,         bitrate: 0,         frameRate: FPS15,       },

@CyrusZei thank you man, it's working for me too. But i noticed something, it was zoomed because i had set the orientation_mode with  "FixedLandscape" value in the videoEncoderConfig. Remove that makes it work.
Here's what i had:
         videoEncoderConfig: {
                width: 360,
                height: 480,
                bitrate: 1,
                frameRate: FPS30,
                orientationMode: FixedLandscape,
            },

yes, the Agora team told me to remove the FixedLandscape and then it worked.


Publish 15.7 RTM NuGet packages

We need to publish final release 15.7 packages. Since those bits will ship in both .NET Core SDK 2.1.300 and Visual Studio 2017 Update 7, which may ship at different times, this will be somewhat complicated.
The plan is:

[ ] Accept #3222 to drop the prerelease tag from our output version.
[ ] Insert the output of that build to VS but do not publish packages.
[ ] Allow prodcon builds to flow the final release version of Microsoft.NETCore.App to our build (and the produced NuGet packages).
[ ] Publish the NuGet packages that came out of prodcon and point to RTM .NET Core package versions.
[ ] Immediately check in a change to our vs15.7 branch that freezes our $(MicrosoftNETCoreAppVersion) to the RTM version.
[ ] Update CLI's reference to MSBuild to point to the release packages.
[ ] Disconnect CLI's uptake dependency on MSBuild in prodcon so it depends on the checked-in package version.

@mmitche FYI. Looks like we can't produce a package outside of prodcon that has the correct dependencies. This is our plan for this release.

@livarcocc : This is our plan for unifying MSBuild versions and packages between the 15.7 and 2.1.300 releases. Unfortunately, it requires an insertion to CLI to prep for (theoretical) future 3xx releases, but it's the best we could come up with.

Seems feasible.

Given that we won't know the final reference until the very end, and msbuild has dependency uptake, I think this should look a little more like:

[ ] Accept #3222 to drop the prerelease tag from our output version.
[ ] Insert the output of that build to VS but do not publish packages.
[ ] Msbuild stays in prodcon until the end, but fixes on a single hash or unchanging branch (the final hash inserted into VS)
[ ] Wait until 2.1 final shipping bits are produced
[ ] Publish the NuGet packages that came out of prodcon and point to RTM .NET Core package versions.
[ ] Immediately check in a change to our vs15.7 branch that freezes our $(MicrosoftNETCoreAppVersion) to the RTM version.
[ ] Update CLI's reference to MSBuild to point to the release packages.
[ ] Disconnect CLI's uptake dependency on MSBuild in prodcon so it depends on the checked-in package version for servicing.

The plan changed somewhat, because we had to take an urgent fix for 15.7.2 that we were able to get into .NET Core SDK 2.1.300 as well.
https://www.nuget.org/packages/Microsoft.Build/15.7.179


Ignore files when exporting package

This commit is part of a campaign to reduce the amount of data transferred to save global bandwidth and reduce the amount of CO2. See https://github.com/Codeception/Codeception/pull/5527 for more info.
Please make sure I didn't accidentally exclude too much.

The failing tests have nothing to do with my PR.

@stof ping


Deleting a tree without deleting it's children

Is it somehow possible to delete a node without (optionally) deleting its children? That means...
if a node looks like this:
1
-1.1
-1.1.1
-1.1.2
-1.1.3
-1.2
... and you delete 1.1, the tree should look like this:
1
-1.1.1
-1.1.2
-1.1.3
-1.2

No specific method for that but this should work:
nodeToDrop.children.forEach(child => nodeToDrop.parent.addChildAtIndex(child, nodeToDrop.getIndex() + child.getIndex()))
nodeToDrop.drop()

Thank you!!!!!


componentWillMount and componentWillReceiveProps warnings

Hi,
I use the last version of the lib (4.10.3) and there are these warnings which appear in the console.

Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.

Move code with side effects to componentDidMount, and set initial state in the constructor.
Rename componentWillMount to UNSAFE_componentWillMount to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run npx react-codemod rename-unsafe-lifecycles in your project source folder.

Please update the following components: %s AlgoliaConfigure(UnknownComponent), AlgoliaInfiniteHits(InfiniteHits), AlgoliaSearchBox(SearchBox)

Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.

Move data fetching code or side effects to componentDidUpdate.
If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run npx react-codemod rename-unsafe-lifecycles in your project source folder.

Please update the following components: %s AlgoliaConfigure(UnknownComponent), AlgoliaInfiniteHits(InfiniteHits), AlgoliaSearchBox(SearchBox), CreateInstantSearch, InstantSearch

The lib doesn't seem to use state hooks from the latest React versions, is it possible to fix this please?

This library doesn't use react at all, do you use the 4.10.3 of React InstantSearch instead of the latest (6.12.0) by chance?

@Haroenv
I use theses libs on React Native:
"algoliasearch": "^4.10.3",
"react-instantsearch-native": "5.7.0",

It's bad?

Oops.. Sorry I use a very old version, I updated and my problem is solved

No problem!


.htmlhintrc parsing issue (strict JSON)

It seems like parsing of .htmlhintrc is broken to some degree:
Issue:
{
  "doctype-first": false
}

With this, htmlhint stops reporting any issues, eg. no warning about < h2 >Whoops< h2 >.
(I'm using this to lint AngularJS templates)
{
  "doctype-first": false,
}

Using this works just fine BUT this config can't be used by gulp-htmlhint (for deployment linting as cordova-hook) because .htmlhintrc can't be parsed.
Obviously the later is not valid (strict) JSON, so I guess there is an issue with htmlhint when parsing/loading this file, since the first config should be valid. (htmlhint: 0.9.12)

https://www.npmjs.com/package/strip-json-comments
May be is issue from strip-json-comments?

Tested you idea:
I removed strip-json-comments in /usr/lib/node_modules/htmlhint/gin/htmlhint (where the config JSON is parsed), but still the same problem.
Maybe there is a misconception on my part:

When I don't use a htmlhintrc config-file, htmlhint will use its default set of rules
When I use a htmlhintrc config-file, htmlhint will ...

My assumption was: ... use its default ruleset with options from given config applied
What seems more likely: ... only use the options from given config and ignore its default ruleset

Which one is true?

Your are useing gulp-htmlhint ?

TL;DR: Yes, I'm using htmlhint with gulp-html and also via atom-linter-htmlhint. (See Addendum)
Longer Version:
Yes, I'm using htmlhint together with gulp (via gulp-htmlhint), so a bit more background details here.
The following code works with gulp-htmlhint AND only disables the doctype-first rule:
{
  "doctype-first": false
}

However this does not (seem to) work with atom-linter-htmlhint, since I don't get any warning/errors in Atom anymore. I confirmed this is not a atom-linter-htmlhint issue, since manually running htmlhint on files with intentional errors also does not report any warning/error.
On the otherhand with the following code atom-linter-htmlhint continues to display all warnings/errors, but gulp-htmlhint fails, because it can't parse the JSON.
{
  "doctype-first": false,
}

Addendum:
My bad, this actually 'works', because atom-linter-htmlhint (unlike gulp-htlmhint) fails silently when loading the above htmlhintrc, which causes it to be ignored...
This only leaves me with one question then:
Is it the intended behavior that htmlhint ignores it default ruleset when using a htmlhintrc config-file (aka disabling all rules not explicitly enabled in the config)?

Yes, the default rule will work when the config is undefined.

In that case my issue if resolved, or at least explained, thank you :)


Package search doesn't show the latest version

Version 2.1.2 of aforemny/material-components-web-elm was released a few days ago but Ellie still shows 2.1.0.

I published MartinSStewart/elm-audio a few days ago and haven't seen it either.

I looked into this a bit, and I think it is due to some changes on the package site, in older versions it would return an array of versions, but on the current site, fetching https://package.elm-lang.org/search.json returns an array like
[
    {
        "name": "elm/browser",
        "summary": "Run Elm in browsers, with access to browser history for single-page apps (SPAs)",
        "license": "BSD-3-Clause",
        "version": "1.0.2"
    },
    {
        "name": "elm/bytes",
        "summary": "Work with sequences of bytes (a.k.a. ArrayBuffer, typed arrays, DataView)",
        "license": "BSD-3-Clause",
        "version": "1.0.8"
    },
    {
        "name": "elm/core",
        "summary": "Elm's standard libraries",
        "license": "BSD-3-Clause",
        "version": "1.0.5"
    }
]

The relevant code looks like it is here https://github.com/ellie-app/ellie/blob/b84c3150992713912dd8f3d8f895f12a51377372/lib/elm/platform/parser.ex#L69

I'll see if I can do a PR, maybe learn some Elixir in the process ^_^;

I'm not sure if it's related, but mdgriffith/elm-animator is completely missing from the Ellie search results.


Review Ansys Q3D analysis and HFSS eigenmode analysis and find pain points, missing improvements, things to smooth, revise, features needed

What is the feature being requested?
Review Ansys Q3D analysis and HFSS eigenmode analysis and find paint points, missing improvements, things to smooth, revise, features needed
Document as features in issues.
@marcolincs  you can go over this with Dennis and Thomas and over the tutorial we are making with Dennis now for Thursday.
We need to smooth and automate the flow
Goal of this is to mark issues to do for a next scrum
What are use cases for this feature?

Several issues created. Last but not least #255 . We shall close this case, and just make it a habit for us to loop on this stuff periodically.
Cheers