The addon dex can't be installed .

Describe the bug
There are some error when I install the addon of dex.
[root@xy-5-server14 velaux]# vela status addon-dex -n vela-system
About:

  Name:         addon-dex
  Namespace:    vela-system
  Created at:   2023-07-05 16:13:04 +0800 CST
  Status:       runningWorkflow

Workflow:

  mode: DAG-DAG
  finished: false
  Suspend: false
  Terminated: false
  Steps
  - id: dqppe1n3go
    name: dex
    type: apply-component
    phase: running
    message: wait healthy
  - id: zg6esfki4h
    name: dex-resources
    type: apply-component
    phase: succeeded

Services:

  - Name: dex
    Cluster: local  Namespace: vela-system
    Type: helm
    Unhealthy Fetch repository successfully, Delivery helm release in progress, message: HelmChart 'vela-system/vela-system-dex' is not ready
    No trait applied

  - Name: dex-resources
    Cluster: local  Namespace: vela-system
    Type: k8s-objects
    Healthy
    No trait applied

I check the the HelmChart and found that:
[root@xy-5-server14 velaux]# kubectl get HelmChart -A
NAMESPACE     NAME              CHART   VERSION   SOURCE KIND      SOURCE NAME   AGE   READY   STATUS
vela-system   vela-system-dex   dex     0.6.5     HelmRepository   dex           13m   False   invalid chart reference: failed to get chart version for remote reference: no 'dex' chart with version matching '0.6.5' found

I find addon source address:,it is a wrong version:

It is should be 0.6.6 like velaux page:

Thanks for reporting, maybe it's a network issue, I can see the 0.6.5 version exist in dex charts repo: https://charts.dexidp.io/index.yaml

Thanks for reporting, maybe it's a network issue, I can see the 0.6.5 version exist in dex charts repo: https://charts.dexidp.io/index.yaml

Yes,there are 0.6.5 version dex charts.
But in fact  the version of the dex addon that I need to install is 0.6.6 .

Could you check the connection between you cluster and charts.dexidp.io/? Since version 0.6.5 exists, it may be a network issue.
Version in dex addon page means the version of addon (0.6.6). It's possible that the addon version is not exactly the same with chart version(0.6.5).

You can help update the dex addon's chart version if you're willing to.

@chivalryq can I work on this issue?

@chivalryq I create  PR could you please review it !! I am new to community.

/assign

Hey @chivalryq, could you please assign me this issue ?

Hey!
Is this issue still open?


[Wagtail] Update versions info to include 2.16

Add the 2.16 release, and updates info on previous releases

Thank you for the PR with the updates. I saw that you are a Wagtail developer :+1: and I have tried to verify the data. It seems there are different details from different sources:
https://github.com/wagtail/wagtail/wiki/Release-schedule

Version
Release date
Supported until

2.16
1 February 2022
1 May 2022

But from https://github.com/wagtail/wagtail/releases/tag/v2.16 it is released on 2022-02-07.
Based on your change the data seems calculated from the final date not from the planed one. Can you confirm?
https://docs.wagtail.org/en/stable/contributing/security.html#supported-versions

Upon the release of Wagtail 2.6, Wagtail 2.4’s security support will end.
Version 2.4 is EoL (no more security support) since 2022-02-07, do you agree?

I think we should also update the description at the end to have the same wording as in https://docs.wagtail.org/en/stable/contributing/security.html#supported-versions.

Hey @BiNZGi, thank you very much for taking the time to cross-reference the dates!
The https://github.com/wagtail/wagtail/wiki/Release-schedule wiki page is indicative and previous dates are updated on a new release. I've now updated it (e.g. 2.16 was released on 7 Feb - https://github.com/wagtail/wagtail/releases/tag/v2.16)
You are very right about 2.14, not sure what I was thinking there 🤦♂


Update to 2018 edition and some QoL improvements; generate 2018 code

r? @danburkert

As an alternative to a cargo feature flag, this could also be configured as a flag on the Config struct.  That may be the safer option, since it avoids conflicts between multiple dependent crates which do prost code generation.  For example, you have crates A and B in your dependency tree, A uses edition-2015, and B uses edition-2018.  By configuring this as a feature flag, you unavoidably force A into edition-2018, and will probably get compile errors as a result.

@nrc not related to this PR, but I figure I'll ask since you are the person who would know.  prost-build goes to annoying lengths to output more-or-less pretty-printed code.  This was originally done because rustfmt wasn't as baked, and it helped in debugging to have formatted code.  Nowadays it seems pretty antiquated.  Is there a way to call rustfmt as a library, or otherwise pipe the generated code through rustfmt?

... Is there a way to call rustfmt as a library, or otherwise pipe the generated code through rustfmt?

I agree, I think it would be best to avoid trying to format code in Prost. My preference would be to not format at all - since the code is not intended to be kept around, there doesn't seem to be a need to format it. If users want to format it, then it is very easy to run it through rustfmt as part of the build script (and I would use the binary rather than using rustfmt as a library since users might already have the binary on the system and thus can save downloading all the rustfmt source and deps).
If you do want to generate formatted code, then rustfmt can easily be used as a library.

As a user I would much prefer fewer dependencies over pretty-printed Output, for what it's worth :)

@danburkert rebased and addressed all your comments (sorry for the delay, have been on vacation).

@nrc Thanks for the update.  I've split this into two halves, with the first being the cargo fmt changes which I pushed to master.  The second is the edition 2018 changes which I'm iterating on in the edition-2018 branch.  In particular I want to add 2015 tests so we don't regress 2015 support in the future, and I think @lorkki is right that there are a few additional 2018 keywords.

So I'm planning to land it in the next day or two, I'll handle the additions I mentioned myself.

Merged in #159, thanks!


meta(sync): tracing

Codecov Report

Merging #455 (93e1cc2) into main (ae2fc49) will decrease coverage by 0.41%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #455      +/-   ##
==========================================
- Coverage   74.44%   74.03%   -0.42%
==========================================
  Files         238      240       +2
  Lines       22933    23129     +196
==========================================
+ Hits        17073    17124      +51
- Misses       5860     6005     +145

Impacted Files
Coverage Δ

crates/stages/src/stages/bodies.rs
95.59% <100.00%> (+0.01%)
:arrow_up:

crates/stages/src/stages/headers.rs
96.88% <100.00%> (+0.17%)
:arrow_up:

crates/transaction-pool/src/test_util/mock.rs
53.70% <0.00%> (-6.67%)
:arrow_down:

crates/net/network/src/discovery.rs
60.00% <0.00%> (-5.63%)
:arrow_down:

crates/net/network/src/network.rs
48.80% <0.00%> (-4.44%)
:arrow_down:

crates/net/discv4/src/lib.rs
62.00% <0.00%> (-4.16%)
:arrow_down:

crates/net/network/src/peers/manager.rs
70.94% <0.00%> (-1.64%)
:arrow_down:

crates/net/network/src/state.rs
52.36% <0.00%> (-1.39%)
:arrow_down:

crates/net/network/src/session/mod.rs
69.50% <0.00%> (-1.06%)
:arrow_down:

crates/transaction-pool/src/pool/txpool.rs
58.21% <0.00%> (-0.53%)
:arrow_down:

... and 13 more

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


[FIX] css styles for pos_mobile

@GabbasovDinar fix remaining lint

@ilmir-k DONE, you can merge it

@yelizariev please make review to be able to merge it


DUOS-560 Structured research purpose

Technically still a work in progress. Currently, the SRP and DUSL require different logic to format the content, but they will turn into an abstract component when we have the backend returning the JSON object.

@mackenziekerwin FYI, the ontology endpoint for getting a structured translation is here: https://consent-ontology.dsde-dev.broadinstitute.org/#/Translate/post_translate_summary
To generate a request to this endpoint, we'll need to format the relevant elements of the data access request into a properly formed data use schema. We don't have any code to do that in the UI now so we'll need to make that happen to utilize the ontology endpoint.


INK2-764-library-changes

It's likely that we can keep these changes within the fork, without a PR back to the main repo for now

From the comments above it sounds like this was an accidentally raised PR containing some code to set a number of default record headers based on a private company project?
Will go ahead and close this PR for now but feel free to come back if you think I'm mistaken :)


Squad Changes

Change verbiage and defaults on configurations
Change regexes for join and leave
Disable writable console

Has the regex been tested with multiple players connected? I suspect that given there is no identifier for individual players, AMP will treat one player leaving as providing a match for all players - so the player count will drop immediately to 0

Either way, this PR has conflicts that will prevent merge anyway. It needs to be rebased


Update existing hooks for Foundry VTT V9.220

For a lot of hooks, documentation has been added.

We should probably replace unknown return types with void.


[EXTRACTOR ERROR] Bone Index out of range of Remap List

Description
runtime error during normal usage.
System info:

Filediver version: 0.3.3
OS: Windows

Error output
Only include errors that actually pertain to the described type of file.
STATUS File 617/27607: 0x0991016be957eb39.unitpanic: runtime error: index out of range [198] with length 1
...

Additional context
full log:
./filediver -c "model:format=glb"
INFO Using game found at: "C:\Program Files (x86)\Steam\steamapps\common\Helldivers 2"
INFO Output directory: "extracted"
INFO Known hashes: names 23.47%, types 95.45%
INFO Extracting files...
ERROR extract 0x003d21b411d799d4.unit: expected bone index item to have format [4]float16 or [4]uint8, but got: float32
ERROR extract 0x004865a7e5da5b2c.unit: expected bone index item to have format [4]float16 or [4]uint8, but got: float32
ERROR extract 0x005c2262f672caf4.unit: expected bone index item to have format [4]float16 or [4]uint8, but got: float32
ERROR extract 0x00bcf8247a544cdc.unit: expected bone index item to have format [4]float16 or [4]uint8, but got: [2]float16
ERROR extract 0x00f84088090c623c.unit: expected bone index item to have format [4]uint8, but got: 20
ERROR extract 0x01144a44b65471bd.unit: expected bone index item to have format [4]float16 or [4]uint8, but got: float32
ERROR extract 0x01b741a724fd9bb3.unit: expected bone index item to have format [4]uint8, but got: 20
ERROR extract 0x01d8f262f56227fb.unit: expected bone index item to have format [4]float16 or [4]uint8, but got: float32
ERROR extract 0x029cfc4c193211c3.unit: expected bone index item to have format [4]float16 or [4]uint8, but got: float32
ERROR extract 0x02c978264cdcccad.unit: expected bone index item to have format [4]uint8, but got: 20
ERROR extract 0x02ca1c5210037cae.unit: expected bone index item to have format [4]uint8, but got: 20
ERROR extract 0x02ecb3e7587540bb.unit: expected bone index item to have format [4]float16 or [4]uint8, but got: [2]float16
ERROR extract 0x0332aa9db9f3471f.unit: expected bone index item to have format [4]float16 or [4]uint8, but got: float32
ERROR extract 0x0364ca45cf3fb606.unit: expected bone index item to have format [4]uint8, but got: 20
ERROR extract 0x0377ea04bcbd7319.unit: expected bone index item to have format [4]float16 or [4]uint8, but got: float32
ERROR extract 0x0387a158d04848f4.unit: expected bone index item to have format [4]float16 or [4]uint8, but got: float32
ERROR extract 0x03e67a19b07c6523.unit: expected bone index item to have format [4]float16 or [4]uint8, but got: float32
ERROR extract 0x0416984f4922757b.unit: expected bone index item to have format [4]float16 or [4]uint8, but got: float32
ERROR extract 0x042592e43d4d977d.unit: expected bone index item to have format [4]float16 or [4]uint8, but got: float32
ERROR extract 0x046ef8f635d3b937.unit: expected bone index item to have format [4]float16 or [4]uint8, but got: float32
ERROR extract 0x0591971af87d0cba.unit: expected bone index item to have format [4]uint8, but got: 20
ERROR extract 0x068cc25ab414bb1c.unit: expected bone index item to have format [4]uint8, but got: 20
ERROR extract 0x070bc8d3e18bb8f9.unit: expected bone index item to have format [4]float16 or [4]uint8, but got: float32
ERROR extract 0x070df80412814549.unit: expected bone index item to have format [4]float16 or [4]uint8, but got: float32
ERROR extract 0x072837478929b018.unit: expected bone index item to have format [4]uint8, but got: 20
ERROR extract 0x079c966ee10536f9.unit: expected bone index item to have format [4]float16 or [4]uint8, but got: float32
ERROR extract 0x07b2590feb74c102.unit: expected bone index item to have format [4]float16 or [4]uint8, but got: float32
ERROR extract 0x07d605bd50c98461.unit: expected bone index item to have format [4]float16 or [4]uint8, but got: float32
ERROR extract 0x07d9c4b2824dcc3d.unit: expected bone index item to have format [4]float16 or [4]uint8, but got: float32
ERROR extract 0x07db4515d78027b6.unit: expected bone index item to have format [4]uint8, but got: 20
ERROR extract 0x07fe9ad17429dc6b.unit: expected bone index item to have format [4]float16 or [4]uint8, but got: [2]float16
ERROR extract 0x080694e77eb97e77.unit: expected bone index item to have format [4]float16 or [4]uint8, but got: float32
ERROR extract 0x08886d27a6f6db8c.unit: expected bone index item to have format [4]float16 or [4]uint8, but got: [2]float16
ERROR extract 0x089159bcfcbfc957.unit: expected bone index item to have format [4]float16 or [4]uint8, but got: float32
ERROR extract 0x08d91172be0a96ee.unit: expected bone index item to have format [4]float16 or [4]uint8, but got: float32
ERROR extract 0x08f6089289c83d22.unit: expected bone index item to have format [4]float16 or [4]uint8, but got: [2]float16
STATUS File 617/27607: 0x0991016be957eb39.unitpanic: runtime error: index out of range [198] with length 1
goroutine 1 [running]:
github.com/xypwn/filediver/extractor/unit.remapMeshBones(...)
/github/workspace/extractor/unit/extractor.go:185
github.com/xypwn/filediver/extractor/unit.ConvertOpts({0xf4cea0, 0xc0022f8540}, 0xc000027118)
/github/workspace/extractor/unit/extractor.go:453 +0x21f0
github.com/xypwn/filediver/extractor/unit.Convert({0xf4cea0, 0xc0022f8540})
/github/workspace/extractor/unit/extractor.go:557 +0x165
github.com/xypwn/filediver/app.(*App).ExtractFile(0xc00008a890, {0xf4bd30, 0xc000066050}, {{0x991016be957eb39}, {0xe0a48d0be9a7453f}}, {0xda0fa5, 0x9}, 0xc000088810, 0xc00008c078)
/github/workspace/app/app.go:431 +0x156f
main.main()
/github/workspace/cmd/filediver-cli/main.go:206 +0x1a45

It seems like the bone indices are being used without bounds checking. I'll look into it once I'm at my home computer. Thanks for the report!

@ryanjsims maybe you can immediately recognize what exactly went wrong here, since you wrote the code. If not, that's also fine and I'll figure it out myself :)

Alright, I hope everything works for you now!
I turned the panic into a regular error so the program doesn't completely fail and only skips the erroneously read file. I still don't know what exactly happened (because I didn't actually write the skeleton/bone stuff, but also because we had to reverse engineer everything), but this is something that may be looked at a bit closer, along with fixing a lot more error messages, especially in model extraction.
(The additional research that has to be done is also why I'm reopening this issue)

@xypwn Sorry, I was working on other stuff but I've gotten back to looking at the code again: it looks like the reason for the panic boils down to simply not correctly loading all the data in the unit file and making incorrect assumptions about how bones and components work.
I've been doing some more research on how the format is loaded and I've got a branch that implements a more correct unit format on my fork. It isn't perfect yet, but it resolves several incorrect assumptions I made when initially writing the skeleton export code

@ryanjsims Absolutely no need to apologize! I haven't had much time recently either to work on almost anything. After all, this is voluntary work and I really appreciate you sharing your amazing contributions :)
Seems like you made some really good progress with unit files. I'll definitely check it out later and am super excited about the improvements!


Deployment with rsync

rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: remote command not found (code 127) at io.c(226) [sender=3.1.3]

Все новое - хорошо забытое старое
https://github.com/trikset/trik-studio/pull/98/files

Download:
Environment: QT=5.12, ARCH=32, CONFIGURATION=release, QTIFW=C:\Qt\Tools\QtInstallerFramework\3.1

Download:
Environment: QT=5.12, ARCH=32, CONFIGURATION=release, QTIFW=C:\Qt\Tools\QtInstallerFramework\3.1


Stream-based Extractor

Currently, ExtractorData stores all data of the rar file in memory, and when extract() is called, each files inside are also kept in memory as Uint8Array extraction property.
This works fine for small rar file, but would run out of memory for big file.
Would you consider adding another Extractor that supports ReadableStream, both for the rar file, and the files inside it?

It's hard since the Extractor is just a simple wrapper for the file writing API for unrarLib. So technically the unrarlib may not write the file sequentially is hard to rewrite to a streaming class.


VSCode memleaks. Hard.

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.62.0 and above
OS Version: Artix Linux 20210726 (plasma-openrc) [x86_64] Kernel 5.15.5-artix1-1

Steps to Reproduce:

Open VSCode
RAM usage grows indefinitely until the system is brought to its knees (and I have 48 friggin GIGABYTES of RAM, just FYI)

It all happened after I updated vscode to 1.62.2 today. Tried downgrading it back to 1.62.0 to no avail. It's absurd: this tool is supposed to help developers get work done and it's making it impossible for me to use it.
Note: Don't even try to close this issue as "out of scope". I will come for your head. With torches and a pitchfork. Jokes aside though: this has to be fixed

/needsMoreInfo
Please use this guide to provide more information: https://github.com/Microsoft/vscode/wiki/Performance-Issues. Thanks.

Hi, thanks for the swift reply. I'll update this issue ASAP with the requested profiler information, although I'd like to reiterate that VSCode memleaks even with all extensions disabled and after a cold reboot (I haven't checked CPU usage, but my fan spin up real hard so I'll have to inspect that too)

@nocturn9x ping for actionable info

@nocturn9x ping for actionable info

I have switched to using an older version of VSCode for now, as I need to get work done. I'll try to submit logs/dumps by the end of the week, sorry for the wait

Apparently, uninstalling and reinstalling vscode entirely fixed the issue. No idea what caused it, probably a bad global config carried over from a previous version. Closing


fix: document typo

Description
This pull request changes the following:

Fix some typos in documentation

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


2da inconsistency fixes

Some 2da files (found xpbaseconst.2da, cloakmodel.2da) are inconsistent in header's file version and number of empty rows.

Thanks for the PR. I'm holding off on merging this for a bit. I need to consult the spec and decide if I'm okay supporting ill-formed files. I probably will be; I just need some time to consult the broken 2das and the 2da spec.


Disallow both single- and multi-signing in RPC (RIPD-1713)

This pull request is composed of two related commits.
The first commit adds some checking in the signing RPC commands (like submit and sign_for) to return an error when a transaction being multisigned is already single-signed and vice versa.  The transaction layer already protected against this problem.  So the commit just improves the error message for the user and stops processing earlier on this kind of error.  It also adds a couple of new error codes to ErrorCodes.h.  More on that in a bit.
In the process of making this change a bug was uncovered in the RPCCall unit test.  The first commit fixes that bug as well.
Also during the work on the first commit it was discovered that there was at least one code in ErrorCode.h that is currently unused anywhere in the current code base.  That led to an audit.  The audit in turn led to the second commit.
The second commit removes all of the codes in ErrorCodes.h that are unused.  The corresponding support code is also removed from ErrorCodes.cpp.
This leads me to my last question.  The source code in ErrorCodes.h notes that the numeric values below a certain point are unstable: https://github.com/ripple/rippled/blob/develop/src/ripple/protocol/ErrorCodes.h#L40-L41  And they certainly will be unstable after these two commits.
However the online documentation does not seem to spell out that the numeric codes are not stable.  Here's where I would expect to see that indication: https://developers.ripple.com/error-formatting.html  It doesn't assert that the numeric codes are stable.  But it also doesn't say they can't be relied on.  There is documentation to say that TER codes are unstable: https://developers.ripple.com/transaction-results.html#immediate-response  Still, TER codes are a different matter from RPC error codes.
One additional data point is that the numeric values in ErrorCodes.h have been changing over time.  So it seems like users must not be relying on the stability of these values; we probably would have heard.  The last change was in version 1.1.0.  Before that there were changes in versions 0.80.0 and 0.33.0.  And there were lots of changes before 0.33.0.
So my feeling is that we can probably continue to get away with changing these codes.  But if we do we should probably add a warning regarding their stability in https://developers.ripple.com/error-formatting.html
Alternatively, if we decide that the codes should be treated as stable, then I should rework the first commit and throw out the second commit.  I'd be good with that too.
Thanks for your thoughts.

At prompting from @thejohnfreeman I investigated what it would take to do error checking of the ErrorCode lookup table at compile time.  It turned out not to be that hard.  But it does take a recent enough compiler to swallow the constexpr code.
So I've added two commits to this pull request.  One, from @mellery451 (thanks very much to him), pushes our Travis CI ahead to a more recent gcc version.  The gcc version that Travis was previously at could not handle the for loop in constexpr evaluation.  The last commit takes an unordered list of ErrorInfo which is sorted and validated at compile time.  The sorted list is used in place of what was previously a hash map.
These most recent commits are optional.  They add nothing to the functionality of the original pull request.  But I think that validating the ErrorInfo to this extent at compile time is the sort of thing we should be doing when we can.
I encourage people to make a local branch and mess around by re-ordering, adding, or commenting out various entries in the unorderedErrorInfos toward the top of ErrorCodes.cpp and then re-building.  That will give you a sense for the kinds of compile-time errors we can see from constexpr error checking.

Squashed and rebased.


chore: Add Support Django 5.1

Django 5.1 was released
https://www.djangoproject.com/weblog/2024/aug/07/django-51-released/

Pull Request Test Coverage Report for Build<PHONE_NUMBER>7
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 89.683%

Totals

Change from base Build<PHONE_NUMBER>0:
0.0%

Covered Lines:
3364

Relevant Lines:
3751

💛  - Coveralls


Bug in 'render' function of 'ForeignKeySearchInput' class in 'admin/widgets.py' file

Hello,
I believe there is a bug in 'render' function of 'ForeignKeySearchInput' class in admin/widgets.py file. When it creates the url for 'search_path', it should look at the other side of the relationship, because of the way new 'foreignkey_autocomplete' url resolver is added to the admin site in 'get_urls' function of 'ForeignKeyAutocompleteAdmin' class in admin/__init__.py file.
So, in 'render' function of 'ForeignKeySearchInput' class, the code should look something like this:
        opts = self.rel.to._meta
        app_label = opts.app_label
        model_name = opts.object_name.lower()
        related_url = reverse('admin:%s_%s_changelist' % (app_label, model_name))

        if not self.search_path:
            opts_1 = self.rel.related_model._meta
            app_label_1 = opts_1.app_label
            model_name_1 = opts_1.object_name.lower()
            related_url_1 = reverse('admin:%s_%s_changelist' % (app_label_1, model_name_1))
            self.search_path = urllib.parse.urljoin(related_url_1, 'foreignkey_autocomplete/')

The way it is now, the inline lookup will not work in general case. It will only work if the model corresponding to the 'to' side of relationship is independently registered on admin site by using ForeignKeyAutocompleteAdmin, too. The bug probably dates back to version 1.6.0.
P.S.: While writing this post, I realized that the workaround would probably be to just derive all the required models on the admin site using 'ForeignKeyAutocompleteAdmin' rather than 'ModelAdmin'. :)

Any chance of writing some unittests and maybe a PR for this ?

closing due to inactivity


No module named gsplat.distributed

I am trying to run the simple_trainer on a cloud provider container. I installed gsplat using git(git clone && pip install -e .)
When i try to run the simple_trainer.py file i get this error
Traceback (most recent call last):
  File "/gsplat/./examples/simple_trainer.py", line 25, in <module>
    from gsplat.distributed import cli
ModuleNotFoundError: No module named 'gsplat.distributed'

For some reason it wasn't picking up the current directory in PYTHONPATH, I had to manually edit the PYTHONPATH env variable


Is it possible to provide RecursiveComparisonConfiguration for usingRecursiveFieldByFieldElementComparator()

I can pass a RecursiveComparisonConfiguration  to usingRecursiveComparison() for ignoring certain fields, but it's not possible when asserting collection types  with usingRecursiveFieldByFieldElementComparator().

Indeed it is not possible, that's why we added usingRecursiveComparison() and the new recursive comparison API.
There is no plan to to retrofit but in 3.15.0 at the moment.

ok, will check out the new recursive comparison API 👍
I have been doing this with v3.14.0
assertThat(list)
        .anySatisfy(actual -> assertThat(actual).usingRecursiveComparison(config)
            .isEqualTo(expected));


Not working on XCode 9 ios11

Swift compiler error in TuningFork.swift
Module compiled with Swift 3.1 cannot be imported in Swift 3.2

A workaround is to download the latest AudioKit framework, embed it into source code. Ensure you remove references to AudioKit in the pods file. Also bring in TuningFork into your own project.

@TheDarkRoom created pull request with update to Swift 4.2


Spotify for Doom Emacs

I cannot accept this PR because it's not enough to warrant a module. A user could trivially set it up themselves. It also only caters to helm users and does not accommodate ivy.
I don't mind a spotify module, but there has to be more to it.
Side notes:

Modules should not define their own leader keybinds (leader keybinds should be bound in :config default)
(featurep! helm) should be (featurep! :completion helm)
The helm-spotify-plus isn't lazy loaded


pass down exception message if we are missing any explicit constraint violations

@ewencp

Refer to this link for build results (access rights to CI server needed):
http://jenkins.confluent.io/job/rest-utils-pr/15/
Test PASSed.

LGTM


Add Support for Hive Contraints

Starting with Hive 2.x non-enforced constraints are supported. These should be supported in the ER Diagrams since the data is available from the default jdbc metadata calls.

will be implemented in #10330


Gracefully skip loading when Vim version is below a minimum

See #370.
We're using a few parts of the Vim Python API that were added in Vim 7.4 (e.g. vim.vars). We either need to find these and change them to use methods that are compatible with older Vim (e.g. #370), or declare supported compatibility and skip loading on older versions.
I'm in favor of the latter, ensime-vim is the type of plugin people use for concentrated Scala work in an environment setup optimized for day-to-day development. Most such users will run a fairly recent (Neo)vim, and IMO this is in keeping with ENSIME's overall tinkerer philosophy. Installs of 7.3 are becoming increasingly obsolete in OS packages, and we have better things to do than wrestle with compatibility for a minority.
FWIW UltiSnips is precedent of a high-value Python-based plugin that supports only 7.4+.
The work to do here is, I think:

Add a simple if version < 704 check to finish with a friendly message to the user.
Document the requirement where appropriate.

I totally agree whit everything you just said, adding modern-IDEs-like features to Vim is hard enough already without supporting every single version out there. So I should not focus on this kind of compatibility issues. But I would be keen to consider merging a PR if someone interested in such support come up with any. Obviously if it doesn't complicates the codebase too much.


'jupyter-book upgrade' deletes new references

Hi!
When running the command jupyter-book upgrade using the latest version of jupyter-book directly downloaded from the github repo, I noticed that in the upgraded book all my references (stored in the folder _bibliography) were deleted and replaced with the default ones.
When tracking down the error, I realized that the script create.py is not copying the references folder from the old book to the upgraded book, but it’s actually copying the references folder from the template book (thus erasing newly added information).
To find a possible solution, I added a few lines of code to create.py to:

Ignore the _bibliography folder when copying the template book:

    ignore_folders = ['_build', 'content', '_bibliography']

Add an argument called ‘bib_folder’ to the new_book function and inside it copy the references from the old book to the upgraded book:

    _check_file_exists(bib_folder)
    print("Copying over your bibliography folder...")
    sh.copytree(bib_folder, op.join(path_out, '_bibliography'))

With these changes added, I re-ran the upgrade process and the references didn’t get deleted.
If you can replicate this problem and you think this could be a possible solution (with improvements), I could submit a PR with the changes.

Hey! 👋  good catch - this is definitely something we should fix.
I think that sounds like a reasonable approach. Another way we could accomplish the same thing is to modify the upgrade_book function so that it includes bib_folder in its call to new_book here: https://github.com/jupyter/jupyter-book/blob/master/jupyter_book/create.py#L271 .
I'm happy to review a PR if you'd like to give it a shot!

Do you mean adding the bibliography folder to the extra_files list inside the upgrade_book function? I tried only adding this line to the code (instead of all the other lines I added in the original post):
extra_files_to_check = ['requirements.txt', 'environment.yml', '_bibliography']

... and it works perfectly, no references get deleted. So this might be a more efficient solution. The only thing I'm bothered about this approach is that the description of that block of code says:  "Double check for pre-existing environment files as special cases", and in this case we are not talking about environmental files anymore right? But if this is an issue I can change the description or I could add a separate block:
# Add bibliography folder to extra files
bib_folder = op.join(path_book, '_bibliography'),
extra_files.append(bib_folder)

Let me know which approach sounds more reasonable and I submit a PR for a more detailed examination of the code :rocket:

Good catch - your second approach looks good to me!


Add support for binary evidence

Overview
We should add support for gathering binary evidence.  A need arose for fetching excel spreadsheets.
Requirements

Add BinaryEvidence

To be used with fetching evidence only
Add appropriate decorator
Add appropriate context manager

Update locker to write binary content

Approach
TBD
Security and Privacy
N/A
Test Plan
TBD

We have excel (both .xls and .xlsx) files that we need to dynamically fetch from a remote source and eventually parse into a harvest report. It would be helpful to be able to do the following (or similar):
# source is a pathlib.Path to an excel file
content = source.read_bytes()
...
with raw_evidence(...) as raw:
  raw.set_content(content)

This would help in maintaining the file as excel-readable in the locker without extra encoding / lossiness.
At the moment the above gives the following error:
Traceback (most recent call last):
  File ".../fetch_excel.py", line 80, in fetch_excel
    logging.error('Raw evidence error. Evidence is empty')
  File "/usr/local/lib/python3.9/site-packages/compliance/evidence.py", line 259, in __exit__
    self.locker.add_evidence(self.evidence)
  File "/usr/local/lib/python3.9/site-packages/compliance/locker.py", line 226, in add_evidence
    f.write(evidence.content)
TypeError: write() argument must be str, not bytes


Onboard not resolving initial ENS domain

Description
This is related to the migration to Onboard's subscriptions for provider 'watching'.
Onboard's ENS subscription is not always triggering and the ensDomain in the providers store therefore not being populated. The issue definitely revolves around ENS domain compatability cross-chain. There is a function already implemented: hasENSSupport() in onboard.ts but the issue is the the chainId of the UI can differ to that of the web3 object: the user can switch the UI whilst remaining connected to another network.
We need to find a solution that retains the currently connected network upon Onboard init so that the current implementation doesn't block resolution.
Steps to reproduce

Connect to a chain that doesn't support ENS resolution.
Switch to a chain that does and refresh the Safe.
The ensDomain will not be populated.

I am closing this in favour of working on it in the original branch that we have decided to reopen.


Sidebar UX

Summary

Ticket Link

Checklist

[ ] Added or updated unit tests (required for all new features)
[ ] Has UI changes
[ ] Includes text changes and localization file updates
[ ] Have tested against the 5 core themes to ensure consistency between them.

Device Information
This PR was tested on:
Screenshots

Release Note

@shazm tests are failing and you have conflicts to resolve
/home/circleci/mattermost-mobile/app/components/channel_list/categories/categories.tsx
4:9   error  'sortBy' is defined but never used  @typescript-eslint/no-unused-vars
6:31  error  'Text' is defined but never used    @typescript-eslint/no-unused-vars
/home/circleci/mattermost-mobile/app/utils/mattermost_managed.ts
27:5  error  Unexpected console statement  no-console
✖ 3 problems (3 errors, 0 warnings)

@shazm tests are failing and you have conflicts to resolve
/home/circleci/mattermost-mobile/app/components/channel_list/categories/categories.tsx 4:9 error 'sortBy' is defined but never used @typescript-eslint/no-unused-vars 6:31 error 'Text' is defined but never used @typescript-eslint/no-unused-vars
/home/circleci/mattermost-mobile/app/utils/mattermost_managed.ts 27:5 error Unexpected console statement no-console
✖ 3 problems (3 errors, 0 warnings)

I merged in the latest Gekidou, resolved some errors with the Podfile and just working through some of the TSC/ESLint errors.

@shazm can you please help update this PR as you mentioned https://github.com/mattermost/mattermost-mobile/pull/5928#issuecomment-1031146653

@shazm can you please help update this PR as you mentioned https://github.com/mattermost/mattermost-mobile/pull/5928#issuecomment-1031146653

Yup almost there; will push fixes in the next hour or so!


[flatiron] jitsu config set colors false doesn't turn off colors

I would expect the effect to be the same as --no-colors, which does work.

Two things going on here:

jitsu config set colors false sets "colors" to "true" (as in a string), not true (as in a boolean). So, either jitsu config set needs to be smart enough to convert "true" and "false" into booleans, or any code that checks it needs to be smart enough to interpret "false" as false. This is a regression from the current stable version.

Even when .jitsuconfig is fixed manually, some strings still show color.

Fixed the second case (afaict), now we just need to fix the first case.

For #1, see https://github.com/flatiron/cli-config/pull/2 . There might be other ways to fix it.
For #2: The "usage" module requires colors and defines the text before jitsu.config runs. I tried adding the jitsu.config.get step for colors, but I think it occurs too soon.

See: https://github.com/nodejitsu/jitsu/pull/167


Remove obsolete files related to rdkit-js + write a rescoped README for MinimalLib

Reference Issue
https://github.com/rdkit/rdkit-js/issues/130
What does this implement/fix? Explain your changes.
Wrote a rescoped readme in the minimallib source code post release of the official rdkit-js repository
Any other comments?
cc @ptosco @greglandrum, let me know if you think this makes sense :+1:

Will wait for @ptosco's comments before merging.

while @ptosco finds the time to check this, I made further replacement of rdkit-js links in the rdkit docs here
a bit out of scope, but I added the UGM 2021 link in the main README here

that's my dream @ptosco , see a related comment in your repository here https://github.com/rdkit/rdkit-structure-renderer/pull/2#issuecomment-1179290487
maybe we should open an official discussion topic to establish a plan on how to centralize all rdkit-js efforts?

https://github.com/rdkit/rdkit/pull/5432#issuecomment-1190397594

No rush @ptosco but yes we should continue the conversation whenever we find the time


11/22 OOB Publish

Docs Build status updates of commit a986271:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:bulb:Suggestion

Details

DocsLegal/GDPR.md
:white_check_mark:Succeeded

DocsLegal/TOC.md
:white_check_mark:Succeeded

DocsLegal/index.md
:white_check_mark:Succeeded

DocsLegal/termsofuse.md
:white_check_mark:Succeeded

.openpublishing.redirection.json

Line 5, Column 48: [Suggestion: redirect-url-invalid - See documentation] Can't redirect document ID for redirected file 'marketplace/general-policies.md' because redirect URL 'certification-policies' is invalid or is in a different docset. Specify a redirect_url in the same docset, or set redirect_document_id to false in .openpublishing.redirection.json.
Line 25, Column 90: [Suggestion: redirect-url-invalid - See documentation] Can't redirect document ID for redirected file 'cognitive-services/text-analytics/transparency-note.md' because redirect URL '/legal/cognitive-services/language-service/transparency-note' is invalid or is in a different docset. Specify a redirect_url in the same docset, or set redirect_document_id to false in .openpublishing.redirection.json.
Line 30, Column 85: [Suggestion: redirect-url-invalid - See documentation] Can't redirect document ID for redirected file 'cognitive-services/text-analytics/data-privacy.md' because redirect URL '/legal/cognitive-services/language-service/data-privacy' is invalid or is in a different docset. Specify a redirect_url in the same docset, or set redirect_document_id to false in .openpublishing.redirection.json.
Line 35, Column 109: [Suggestion: redirect-url-invalid - See documentation] Can't redirect document ID for redirected file 'cognitive-services/text-analytics/guidance-integration-responsible-use.md' because redirect URL '/legal/cognitive-services/language-service/guidance-integration-responsible-use' is invalid or is in a different docset. Specify a redirect_url in the same docset, or set redirect_document_id to false in .openpublishing.redirection.json.
Line 40, Column 115: [Suggestion: redirect-url-invalid - See documentation] Can't redirect document ID for redirected file 'cognitive-services/text-analytics/transparency-note-executive-summarization.md' because redirect URL '/legal/cognitive-services/language-service/transparency-note-extractive-summarization' is invalid or is in a different docset. Specify a redirect_url in the same docset, or set redirect_document_id to false in .openpublishing.redirection.json.
Line 45, Column 97: [Suggestion: redirect-url-invalid - See documentation] Can't redirect document ID for redirected file 'cognitive-services/text-analytics/transparency-note-health.md' because redirect URL '/legal/cognitive-services/language-service/transparency-note-health' is invalid or is in a different docset. Specify a redirect_url in the same docset, or set redirect_document_id to false in .openpublishing.redirection.json.
Line 50, Column 112: [Suggestion: redirect-url-invalid - See documentation] Can't redirect document ID for redirected file 'cognitive-services/text-analytics/transparency-note-key-phrase-extraction.md' because redirect URL '/legal/cognitive-services/language-service/transparency-note-key-phrase-extraction' is invalid or is in a different docset. Specify a redirect_url in the same docset, or set redirect_document_id to false in .openpublishing.redirection.json.
Line 55, Column 109: [Suggestion: redirect-url-invalid - See documentation] Can't redirect document ID for redirected file 'cognitive-services/text-analytics/transparency-note-language-detection.md' because redirect URL '/legal/cognitive-services/language-service/transparency-note-language-detection' is invalid or is in a different docset. Specify a redirect_url in the same docset, or set redirect_document_id to false in .openpublishing.redirection.json.
Line 60, Column 115: [Suggestion: redirect-url-invalid - See documentation] Can't redirect document ID for redirected file 'cognitive-services/text-analytics/transparency-note-named-entity-recognition.md' because redirect URL '/legal/cognitive-services/language-service/transparency-note-named-entity-recognition' is invalid or is in a different docset. Specify a redirect_url in the same docset, or set redirect_document_id to false in .openpublishing.redirection.json.
Line 65, Column 126: [Suggestion: redirect-url-invalid - See documentation] Can't redirect document ID for redirected file 'cognitive-services/text-analytics/transparency-note-personally-identifiable-information.md' because redirect URL '/legal/cognitive-services/language-service/transparency-note-personally-identifiable-information' is invalid or is in a different docset. Specify a redirect_url in the same docset, or set redirect_document_id to false in .openpublishing.redirection.json.
Line 70, Column 109: [Suggestion: redirect-url-invalid - See documentation] Can't redirect document ID for redirected file 'cognitive-services/text-analytics/transparency-note-sentiment-analysis.md' because redirect URL '/legal/cognitive-services/language-service/transparency-note-sentiment-analysis' is invalid or is in a different docset. Specify a redirect_url in the same docset, or set redirect_document_id to false in .openpublishing.redirection.json.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Explain the need to update PCB after adding rotation/position offset

I was having the same problem as presented in #41 and realized that I needed to update the PCB after entering a rotation offset in the Schematic Editor. This PR adds documentation to point this out and help others avoid the same frustration.

Also relevant for #57
Thanks!


what is the parameter_file ?

what dose that file include?

You can see it right here:
https://github.com/jiegzhan/time-series-forecasting-rnn-tensorflow/blob/master/training_config.json
It contains model and training parameters.


gpu_wrapper does not honor selected GPU

Hi,
when, for example, using pics -G1 -g ..., the following wrapping code will still try to initilize CUDA on other GPUs, not honoring my selected GPU:
https://github.com/mrirecon/bart/blob/dca1cd4c2a2d00cd33a59d5e2b7381d358db05a2/src/num/ops.c#L1140-L1143
This is unfortunate because it makes pics unusable on the GPU when CUDA is configured to only allow a single process per GPU.

yes, this broke at some point (and letting the driver select was broken before). Here is the plan to fix it:

In gpuops.c: introduce a global bitmask gpu_allowed.
In src/num/gpuops.c: make 'cuda_init' fail if gpu is not allowed and 'cuda_init_memopt' select from allowed GPus
in src/num/ops.c: move gpu selection into a new function to src/num/gpuops.c which respect the bitmask (e.g. selects according to allowed gpus) and does nothing if bitmask is zero.
in src/num/init.c: add a new function num_init_multigpu: which takes a bitmask as argument and selects the first allowed GPU.
in src/pics.c: change command-line argument to take the bitmask and pass it on. default should be a bitmask of zero and a call to num_init_gpu which let's the driver decide.

GPU selection is now implemented by the driver. Use the CUDA_VISIBLE_DEVICES variable to the selected GPUs. BART will the use the first available selected GPU.


Nuget package needed

To get this program to build and run, had to install the Nuget package: Microsoft.Windows.CppWinRT, v2.0.210122.3
So you might want to add something about the C++/WinRT support needed.
Thanks.

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

ID: 7ae018a1-a3ab-037a-2df7-354677971ff9
Version Independent ID: 95ff0a4f-48c7-4962-93b3-538ab5ec458f
Content: Get started with C++/WinRT - UWP applications
Content Source: windows-apps-src/cpp-and-winrt-apis/get-started.md
Product: uwp
Technology: platform
GitHub Login: @stevewhims
Microsoft Alias: stwhi

Hi, @rcohn, and thanks for filing this issue. To confirm, I just created a new Windows Console Application (C++/WinRT) project, as per the topic, and the version that you mention of that NuGet package is added automatically. It wouldn't be added for a non-C++/WinRT project type, for example the regular Console App. And the second Note in the topic links to the info for setting up Visual Studio for C++/WinRT development.
Everything looks good, so I'll close the issue, but you can still reply in case I'm overlooking something.
Thanks!
Steve

Hi, @rcohn, and thanks for filing this issue. To confirm, I just created a new Windows Console Application (C++/WinRT) project, as per the topic, and the version that you mention of that NuGet package is added automatically. It wouldn't be added for a non-C++/WinRT project type, for example the regular Console App. And the second Note in the topic links to the info for setting up Visual Studio for C++/WinRT development.
Everything looks good, so I'll close the issue, but you can still reply in case I'm overlooking something.
Thanks!
Steve


Sensu 0.27 should be the default version

Expected Behavior
The cookbook should install the latest version of Sensu Core (0.27 as of this writing).
Current Behavior
Because installing Sensu Core 0.27 requires changes to the package repository configuration, the cookbook currently cannot install versions newer than 0.26.5.
Possible Solution

Update default version to 0.27.0-2 or newer
Remove support for init_style on sensu_service resources (see #530 , breaking change).

Your Environment

Version of this cookbook used: 3.2.0

Hi,
I try to update the sensu package on CentOS 7, but I received this error:
   Recipe: sensu::client_service
     * sensu_service[sensu-client] action enable
       * service[sensu-client] action enable
         * service[sensu-client]: Service is not known to chkconfig.
         * service[sensu-client]: Service is not known to chkconfig.
         * service[sensu-client]: Service is not known to chkconfig.
         * service[sensu-client]: Service is not known to chkconfig.
         ================================================================================
         Error executing action enable on resource 'service[sensu-client]'
         ================================================================================

         Chef::Exceptions::Service
         -------------------------
         service[sensu-client]: Service is not known to chkconfig.

         Cookbook Trace:
         ---------------
         /tmp/kitchen/cache/cookbooks/sensu/providers/service.rb:73:in block in class_from_file'
         /tmp/kitchen/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:78:in run_action'
         /tmp/kitchen/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:106:in block (2 levels) in converge'
         /tmp/kitchen/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:106:in each'
         /tmp/kitchen/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:106:in block in converge'
         /tmp/kitchen/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:105:in converge'

         Resource Declaration:
         ---------------------
         # In /tmp/kitchen/cache/cookbooks/sensu/providers/service.rb

   47:     service new_resource.service do
   48:       provider service_provider
   49:       supports :status => true, :restart => true
   50:       retries 3
   51:       retry_delay 5
   52:       action :nothing
   53:       subscribes :restart, resources("ruby_block[sensu_service_trigger]"), :delayed
   54:     end
   55:   when "runit"

         Compiled Resource:
         ------------------
         # Declared in /tmp/kitchen/cache/cookbooks/sensu/providers/service.rb:47:in load_current_resource'

         service("sensu-client") do
    provider Chef::Provider::Service::Redhat
    action [:nothing]
    supports {:status=>true, :restart=>true}
    retries 3
    retry_delay 5
    default_guard_interpreter :default
    service_name "sensu-client"
    pattern "sensu-client"
    declared_type :service
    cookbook_name "sensu"
         end

         Platform:
         ---------
         x86_64-linux

       ================================================================================
       Error executing action enable on resource 'sensu_service[sensu-client]'
       ================================================================================

       Chef::Exceptions::Service
       -------------------------
       service[sensu-client] (/tmp/kitchen/cache/cookbooks/sensu/providers/service.rb line 47) had an error: Chef::Exceptions::Service: service[sensu-client]: Service is not known to chkconfig.

       Cookbook Trace:
       ---------------
       /tmp/kitchen/cache/cookbooks/sensu/providers/service.rb:73:in block in class_from_file'
       /tmp/kitchen/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:78:in run_action'
       /tmp/kitchen/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:106:in block (2 levels) in converge'
       /tmp/kitchen/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:106:in each'
       /tmp/kitchen/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:106:in block in converge'
       /tmp/kitchen/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:105:in converge'

       Resource Declaration:
       ---------------------
       # In /tmp/kitchen/cache/cookbooks/sensu/recipes/client_service.rb

        20: sensu_service "sensu-client" do
        21:   init_style node["sensu"]["init_style"]
        22:   action [:enable, :start]
        23: end

       Compiled Resource:
       ------------------
       # Declared in /tmp/kitchen/cache/cookbooks/sensu/recipes/client_service.rb:20:in from_file'

       sensu_service("sensu-client") do
         action [:enable, :start]
         retries 0
         retry_delay 2
         default_guard_interpreter :default
         declared_type :sensu_service
         cookbook_name "sensu"
         recipe_name "client_service"
         init_style "sysv"
         service "sensu-client"
       end

       Platform:
       ---------
       x86_64-linux

In CentOS 6 it's ok. Any idea how to solve this problem?

Hi @betorvs,
I think you're encountering this because we now ship systemd unit files in the packages for Centos 7, but the cookbook is still trying to use the Chef::Provider::Service::Redhat provider to manage the service.
We've merged a change in #534 which addresses this condition, and we're planning to include that change in the upcoming 4.0 release of this cookbook.


#16327 Update kubelet.md to remove GA variables

Remove PodPriority, PodReadinessGates and PersistentLocalVolumes variable from description as these are in GA state

hello @SupriyaSirbi . Thanks for this PR. Would you check if your changes are valid for v1.16?
Page preview:
https://deploy-preview-16346--kubernetes-io-master-staging.netlify.com/docs/reference/command-line-tools-reference/kubelet/

Closing this issue as the kubelet page has been updated as part of the recent 1.16 release.
You can reopen this issue if needed.

/close


Provide wrappers for popular ML libraries

It'd be convenient to provide support for use of Keras or PyTorch models in model selection. There are two issues:

Keras/PyTorch models don't conform to the Scikit-learn API.
Keras models are not pickle-able.

I'm imaging this interface:
from torchvision.models import resnet18
import torch.optim as optim
from dask_ml.wrappers import PyTorchClassifier

pytorch_model = resnet18()
sklearn_model = SkorchClassifier(
    model=pytorch_model,
    model__alpha=1e-2,  # if resnet18 had a kwarg `alpha`
    optimizer=optim.SGD,
    optimizer__lr=0.1,
)

Related issues/PRs
Same complaint in dask/distributed: https://github.com/dask/distributed/issues/3873

I think this is possible with these wrappers:

skorch, a library that brings the Scikit-learn API to PyTorch. This is what's used in the "Better and faster hyperparameter optimization with Dask ."
There's an implementation of __reduce_ex__ for  Keras models in https://github.com/tensorflow/tensorflow/pull/39609/

If you're looking for a way to make Keras models conform to the scikit-learn API, check out SciKeras (full disclosure: I'm the author)

Thanks for the link Adrian. To minimize our maintenance burden, I'd aim for the goal that our model_selection estimators work with any model implementing the scikit-learn interface, and encourage the development / use of wrappers like skorch and SciKeras.
On top of that, we have the additional burden of these models needing to work well with distributed's serialization. To the extent possible, that functionality should be in the projects themselves (making Keras models picklable) or in distributed.

How hard is it to support PyTorch/Keras fit/predict APIs?  If this is as simple as making a function like the following, then I would be in favor
def fit(estimator, X, y=None):
    if hasattr(estimator, "fit"):
        return estimator.fit(X, y)
    elif hasattr(estimator, ...): #  pytorch-like
        return ...
    elif hasattr(estimator, ...): # keras-like
        return ...

For serialization I think that we have a decent Pytorch serializer in distributed (early work from @stsievert if I recall correctly).  I don't think that we have anything for Keras today.

Serialization is also maybe something that we could ask for help from the RAPIDS folks like @quasiben @jakirkham @pentschev  .  It's not RAPIDS obviously, but these are often GPU related and that team is familiar with these sorts of issues.

I'm not 100% sure what the goal is here (I just came from the discussion in tensorflow/tensorflow#39609) but SciKeras adds serialization support to the Keras models it wraps.

Serialization is definitely something RAPIDS cares about.  scikeras looks interesting -- @adriangb do you know if it forces a host to device transfer ?  Does it support the __cuda_array_interface__ ?  If so, I believe things are a lot easier for us.
cc @JohnZed maybe pytorch serialization is something cuML would also care about

Current pytorch serialization is here:
https://github.com/dask/distributed/blob/master/distributed/protocol/torch.py
It looks like it forces things to numpy though, and so may not be
GPU-optimized.
Rather than scikeras I'm still curious if we can make things more
torch/tf/keras-native cheaply
On Mon, Jul 13, 2020 at 8:35 AM Benjamin Zaitlen<EMAIL_ADDRESS>wrote:

Serialization is definitely something RAPIDS cares about. scikeras looks
interesting -- @adriangb https://github.com/adriangb do you know if it
forces a host to device transfer ? Does it support the
cuda_array_interface ? If so, I believe things are a lot easier for
us.
cc @JohnZed https://github.com/JohnZed maybe pytorch serialization is
something cuML would also care about
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask-ml/issues/696#issuecomment-657631883, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACKZTBFNULDR66W3MEA6XDR3MSVHANCNFSM4OX6CD2Q
.

So I guess you could just tell your users to wrap their Keras models before using them with dask-ml?

That's the plan. To do that, models need to support serialization and implement partial_fit (see https://github.com/adriangb/scikeras/pull/17).

pytorch serialization is something cuML would also care about

may not be GPU-optimized.

PyTorch has serialization support, even though they recently tried to remove it! https://github.com/pytorch/pytorch/issues/38597 Skorch wraps the PyTorch, and it looks like the support GPUs: skorch/net.py#L1608.

do you know if it forces a host to device transfer ? Does it support the __cuda_array_interface__ ? If so, I believe things are a lot easier for us.

To be honest, I am not familiar with these terms. All SciKeras does is implement copy.deepcopy and pickle compatible serialization. It does not have a __cuda_array_interface__ method, so I think the answer is no.

How difficult would it be to implement pickling (like Matt did for PyTorch ( https://github.com/pytorch/pytorch/pull/9184 )) for Keras as well? There's a lot of value gained by supporting standard Python protocols. Not to say there may not be additional gains with Dask serialization. Just that having this standard protocol working would make interop with various distributed computing libraries (including Dask) easier.

How difficult would it be to implement pickling ... for Keras as well?

SciKeras has an implementation at scikeras/wrappers.py#L87. There's currently an open PR to merge this into Tensorflow/Keras master: https://github.com/tensorflow/tensorflow/pull/39609

Here's two more PyTorch wrappers:

adadamp, which provides usage of Dask clusters with PyTorch models and presents a Scikit-learn interface
saturncloud/dask-pytorch-ddp, which allows use of a Dask cluster with PyTorch distributed code.


Multiple radis server

how to add Multiple radis server.

To connect to multiple Redis instances, you'll need to create multiple connections.
Please note, for the following example, <IP_ADDRESS> and <IP_ADDRESS> are the redis hosts.
const redisConnection1 = redis.createConnection(6379, "<IP_ADDRESS>");
const redisConnection2 = redis.createConnection(6379, "<IP_ADDRESS>");


fix: compatibility with swup 4.6.0

Description

Fix caching of foreign persisted fragments with swup 4.6.0.
Fix types for matchPath functions

Drive-By

Formatted also the tests, fixtures and readme.md

Checks

[x] The PR is submitted to the master branch
[x] The code was linted before pushing (npm run lint)
[x] All tests are passing (npm run test)
[x] New or updated tests are included

Regarding my comment from above: I've removed the backwards-compatibility code and bumped the swup peer dependency to 4.6.0. I guess that should do it, right? I hope I'll ever wrap my head around these kinds of things...

@hirasso I think it needs both the peer dependency as well as the requires key in the plugin itself. That's how we did that in the body class and head plugins, for example here.

Aaah right, the requires property! Thanks!


Implement the simulation package for lazyledgerapp

Modules in the sdk all have a package called simulation that interfaces with the simapp framework for fuzzing. Implement the simulation package for lazyledgerapp so that proper simulation fuzzing can be done as described here

I'm a little confused by the reference to lazyledgerapp. I infer that lazyledgerapp was renamed to celestia-app but I don't see a celestia-app module in the x/ directory.
Does this issue apply to the payment module and therefore entail creating a x/payment/simulation package?

Every module that implements the Cosmos SDK simulator needs to have a x//simulation package which contains the primary functions required by the fuzz tests: store decoders, randomized genesis state and parameters, weighted operations and proposal contents.

Naive question but can we implement the simulation package for app/test given it doesn't look like a Cosmos SDK module?

Naive question but can we implement the simulation package for app/test given it doesn't look like a Cosmos SDK module?

in the future I think there will definitely be tools that we can use to help fuzz ABCI++ methods, since we're basically the first ones using those methods, those tools don't exist yet though.

Got it. Should we close this issue because we can't implement the simulation package for x/payment/ or app/test? Additionally, should we open a new issue to explore fuzz tooling for ABCI++?

good question, I'm not sure. I think we should at least try, there's almost certainly something of value we can get out of it.
We can open an issue to explore testing ABCI++ methods. Some of the informal team is working on some interesting tools iirc

This is blocked until we either #183 or we use a version of the cosmos-sdk with PrepareProposal and ProcessProposal integrated so we can use the simulation manager to test those. In the meantime, we should continue to flesh out our integration tests for those methods.
taking this off of the goals for incentivized testnet until then.


Simpler compose workflow

Build will always fail until merged into master because import-external container is using cached Docker Hub image.
Users just have to:

docker-compose up postgis
docker-compose run import-external
docker-compose run import-osm
docker-compose run import-sql

And thats it. We had too many compose steps. For full developer control you can still do docker-compose run import-water if you are working on water import.
Integrated the labelrank updating into import-osm (since it has to happen after osm data is imported and I forgot it a lot of times). This makes import-osm dependant on import-external running before. But this makes sense since you import external only once - at the beginning and OSM data multiple times.
Also cleaned up the Natural Earth dataset to make images smaller and schema cleaner.

Great work @lukasmartinelli.

Great work @lukasmartinelli.

Ahh no. Will break the build. Just found a bug. Will fix it in master.
Always bad if you can't trust travis. sorry.


docker-modem depencency  new version breaks tests

Expected Behaviour
Tests work correctly: postgres db runs in docker correctly
Actual Behaviour
Got error: No Docker client strategy found
Testcontainer Logs
testcontainers DEBUG Found applicable Docker client strategy: UnixSocketStrategy +0ms
testcontainers DEBUG Testing Docker client strategy URI: unix:///var/run/docker.sock +1ms
testcontainers WARN  Docker client strategy UnixSocketStrategy is not reachable +59ms
No Docker client strategy found
at node_modules/.pnpm/testcontainers@9.1.3/node_modules/testcontainers/dist/docker/docker-client.js:46:11
at fulfilled (node_modules/.pnpm/testcontainers@9.1.3/node_modules/testcontainers/dist/docker/docker-client.js:5:58)
Environment Information

Operating System: Ubuntu 22.04.2 LTS
Docker Version: Docker version 23.0.1, build a5ee5b1
Node version: v18.12.1
Testcontainers version: 9.1.3 (^9.0.0).

Description
Hello. After i today reinstall node-modules, i face the problem during tests running: No Docker client strategy found. But last week (on friday) everything was normal. I started looking for problem:

Increased testcontainers version from 8.16.0 to 9.1.3 - no changes.
Found that testcontainers's dependency - dockerode relesed a new version these holidays: 3.3.4 -> 3.3.5. I decreased it to 3.3.4 again in package.json in overrides section - no changes.
Found that dockerode's dependency - docker-modem relesed a new version these holidays: 3.0.6 -> 3.0.7. I decreased it to 3.0.6 again in package.json in overrides section. My tests started work correctly. There are the changes: https://github.com/apocas/docker-modem/compare/v3.0.6...v3.0.7.

I use testcontainers to run postges db this common way:
const container = await new GenericContainer('postgres:14-alpine')
      .withEnvironment({
        POSTGRES_DB: 'db_name',
        POSTGRES_USER: 'db_user_name',
        POSTGRES_PASSWORD: 'db_password',
      })
      .withExposedPorts('db_port')
      .withStartupTimeout(300000)
      .start();

Actually i don't know who should care about this problem (testcontainer or docker-modem maintainers)

Thanks for raising @fx-it, I will look into it.

Stepped on it just now

docker-modem has been released with a breaking change as a patch bump v3.0.6 -> v3.0.7.
Suggestion: pin v3.0.6 until resolved.

Hi @fx-it, @Gaen, could you please test<EMAIL_ADDRESS>and confirm it's working for you?

Although I see the author of docker-modem is rolling back the change as another patch release, so I think there's nothing for us to do here.

Tomorrow will try on the lastest version of docker-modem and with stable version of testcontainers. I have to go now.

With the new docker-modem version this is resolved.

confirmed, works


[New] Added phrase for aria-label for the selected day

Added the setting of the CalendarDay aria-label with a dateIsSelected phrase when the day is the selected day.

Coverage increased (+0.08%) to 85.57% when pulling cbafbbde25cf4252cf9fe8e2b65b470c74343a1d on add-aria-label-selected-date into 92cdc04b70cc6cd14b6cc44d7f8e3324e90b76a5 on master.

Coverage increased (+0.02%) to 85.505% when pulling ce272db5071fec102b6af1cdbbf41d15c5f1a02f on add-aria-label-selected-date into 92cdc04b70cc6cd14b6cc44d7f8e3324e90b76a5 on master.


Update/add torch versions to tox.ini

Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Details

3 minutes.
It went from 31 minutes to 34 minutes for this PR.

@tvalentyn PTAL

No comments from me, I'll let @damccorm merge to make sure his comments were addressed.


Use pathlib in conda_vendor.py, fix issue 38

Fixes #38
I believe this fixes the issue that was causing trouble last week. While working through the fix, I took's @kcpevey suggestion and converted path-like objects from str to pathlib.Path objects. This did also require swapping out the tmpdir fixture for tmp_path_factory, the latter of which returns a pathlib.Path object.

Thanks for the review @kcpevey! I believe I've made all of the suggested changes :)


Local-global broken from using the new identity

The compare functionality (know as local-global) is not working anymore. This mainly happened to changes within the app regarding the new identity stuff.
The index page where you pick your scenarios has been fixed in #4075, but the page where the comparison happens will require more work. Basically, the compare functionality now needs to know about the rest of the app (to use the correct authentication protocol), where before it was more of a standalone thing.
For now we put up an maintenance banner.

[ ] Remove links to local-global @noracato
[ ] Add discontinued text to What's New @mabijkerk
[ ] Change mainenance text to discontinued @mabijkerk


Server entries documentation

I'd like to remove entries in the DB servers tables, but I can't find where these settings are saved. Where can I trim these configurations? Documentation around this would be splendid

My extension save data in VS Code Settings. Find key database.connections.


Zip-Ball building for git source

If I understand it correctly, repman extracts the metadata of all versions, but if you use a simple git repository as source (instead of GitHub for example) the Web UI will only show the latest version available (the packages.json contains all versions) and apart from packagist, it will not build dist files itself. (The ComposerPackageSynchronizer skips all versions, which do not have a dist url - which are all for git repositories given by a ssh url)
If this is something you would like to support, I could try to deliver at least a draft
Another thing, I am missing is the "required by", which Satis publishes in Package details.

It is as you wrote. We welcome such a contribution.
As for "required by", you can have a look at: https://github.com/repman-io/repman/pull/426


Add --file CLI option documentation to README.md.

Resolves #384.

Awesome, thanks for contributing the fix! Hopefully that helps the next person get started a little bit quicker ☺


Changed third_body function parameter and added u.kg wherever applicable

Addresses #938

Why are the tests failing now @astrojuanlu?

The tests aren't failing - the coverage check is failing. There is a slightly larger number of lines and no new tests, therefore the coverage decreased. However, I am not very strict with these things, so I am merging strainght away. Thanks @priyanshurohilla!


:sparkles: Integrate documentation to Web UI

Signed-off-by: Mauro Morales<EMAIL_ADDRESS>
What this PR does / why we need it:

Allows users without an internet connection to read the docs in the Web UI
Ensures that the user first sees the documentation related to their release

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Relates to #738

this is super NICE!

Codecov Report

Merging #741 (2a166b4) into master (7b79808) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##           master     #741   +/-   ##
=======================================
  Coverage   19.90%   19.90%
=======================================
  Files          18       18
  Lines        1422     1422
=======================================
  Hits          283      283
  Misses       1091     1091
  Partials       48       48

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


libogg and libvorbis requirement + note for Windows

The readme says

libogg and libvorbis are required to decode ogg samples

What do you mean with "decode"? It sounds like decompressing to PCM format. But probably means reading some format header attributes or verify the file format?
Then it says

If ogg files are not required to be decoded then the libraries are not required.

There is no option to skip "decoding" when using "extract.py". But it seems if the input file contains Ogg Vorbis, then it automatically tries to load the shared libraries and aborts if library loading fails.
Can you add a simple "raw" option without the need for extra libraries to "extract.py"?
Note for Windows:
Working DLL files are available here: http://www.rarewares.org/ogg-libraries.php
When using "extract.py" you may copy the libs into the same directory.
Make sure the name is (rename if needed):
"libvorbis.dll" (just "vorbis.dll" fails)
"libogg.dll"
I've tested on a Unity3D ".resource" file containing hundreds of FSB5 files under Windows and it worked great.

What do you mean with "decode"? It sounds like decompressing to PCM format. But probably means reading some format header attributes or verify the file format?

for PCM sound files fsb just stores the sound, for MPEG it stores the content but cuts off the header but for vorbis it encodes the sound into a stream of vorbis packets.
Currently to decode the packets back to an ogg file I use libogg and libvorbis through ctypes which are only imported when a vorbis sample is requested to be decoded.
If you want the raw vorbis packet stream then you could use the code from the library usage in the example but don't use rebuild_sample which is the function that does the ogg rebuilding.
i.e.
import fsb5

# read the file into a FSB5 object
with open('sample.fsb', 'rb') as f:
  fsb = fsb5.FSB5(f.read())

print(fsb.header)

# iterate over samples
for sample in fsb.samples:
  # print sample properties
  print('''\t{sample.name}.{extension}:
  Frequency: {sample.frequency}
  Channels: {sample.channels}
  Samples: {sample.samples}'''.format(sample=sample, extension=ext))

  # rebuild the sample and save
  with open('{0}.bin'.format(sample.name), 'wb') as f:
    f.write(sample)

Copying the libs to the same directory doesn't work for me :(
Traceback (most recent call last):
  File "D:\Users\Kim\Documents\DuOS-shared\bundles\extractfsb.py", line 131, in <module>
    main()
  File "D:\Users\Kim\Documents\DuOS-shared\bundles\extractfsb.py", line 127, in main
    exit(app.run(sys.argv[1:]))
  File "D:\Users\Kim\Documents\DuOS-shared\bundles\extractfsb.py", line 121, in run
    self.handle_file(f)
  File "D:\Users\Kim\Documents\DuOS-shared\bundles\extractfsb.py", line 110, in handle_file
    for sample_fakepath, sample_name, sample_data in self.read_samples(fakepath_prefix, fsb, ext):
  File "D:\Users\Kim\Documents\DuOS-shared\bundles\extractfsb.py", line 86, in read_samples
    yield sample_fakepath, sample.name, fsb.rebuild_sample(sample)
  File "D:\Python\Python35\lib\site-packages\fsb5\__init__.py", line 212, in rebuild_sample
    from . import vorbis
  File "D:\Python\Python35\lib\site-packages\fsb5\vorbis.py", line 12, in <module>
    vorbis = load_lib('vorbis')
  File "D:\Python\Python35\lib\site-packages\fsb5\utils.py", line 76, in load_lib
    raise LibraryNotFoundException('Could not load the library %r' % (names[0]))
fsb5.utils.LibraryNotFoundException: Could not load the library 'vorbis'

Note for Windows:
...
Make sure the name is (rename if needed):
"libvorbis.dll" (just "vorbis.dll" fails)
"libogg.dll"

I did rename them like that, but it doesn't work.
By "same directory" do you mean the directory in which unityextract.py is stored? If so, that's where I have the libraries.
Also I'm not sure if I got the correct libogg.dll, could that be an issue?
for libvorbis I downloaded "libvorbis.dll using libVorbis v1.3.5"
for libogg I downloaded "ogg vorbis dlls using libVorbis v1.3.5" and renamed ogg.dll to libogg.dll (is it supposed to be vorbis.dll in this case?)

Copy the two DLL files to the same directory as "extract.py". Open a command line window and make sure the current working directory is the one with "extract.py".
I have the directory "fsb5" and "scripts" as subdirectory of "extract.py". Then I run "py extract.py ..."
In general whenever you have a "file not found" error "https://technet.microsoft.com/en-us/sysinternals/processmonitor" can log all IO accesses of a process, also the failed ones.

Those versions should be fine, as @murkymark said just make sure the DLLs are next to extract.py
I've created a release with the correct directory structure and DLLs that work for me on windows
https://github.com/HearthSim/python-fsb5/releases/tag/b7bf605

Okay, it works only with the DLLs bundled with the release zip. It didn't work with the DLLs I grabbed from the Rarewares website for some reason.


nan exception with variational inference

For the following model
data {
    int N;
    vector[N] p;
    int Ngrps;
    int<lower=1, upper=Ngrps> grp_index[N];
}
parameters {
    vector<lower=0.0001, upper=100>[Ngrps] sigmaGrp;
    vector<lower=-100, upper=1000>[Ngrps] muGrp;
}

model {
    int grpi;
    for (i in 1:N){
        grpi <- grp_index[i];
        p[i] ~ logistic(muGrp[grpi], sigmaGrp[grpi]);
    };
}

I'm trying to estimate group level parameters from the following data (I generated with python and saved data file test.R with pystan):
p = 63.1, 108.3, 1.0, 46.0, 22.9, 14.8, 28.8, 52.5, 60.1, 81.3
grp_index = [1, 1, 1, 1, 1, 1, 2, 3, 4, 5]

test_dat = dict(
    N=len(p),
    p=p,
    grp_index=grp_index,
    Ngrps=len(set(grp_index)),
)

When I compile and sample with advi using
$ modeldir/model/test variational data file=modeldir/dat/test.R random seed=3021828106

I get the exception:
Exception: stan::variational::normal_meanfield::set_mu: Input vector[7] is nan, but must not be nan!
Diagnostic information:
Dynamic exception type: std::domain_error
std::exception::what: stan::variational::normal_meanfield::set_mu: Input vector[7] is nan, but must not be nan!

This is a small dataset, and the error can be avoided if I run with most other random seeds, but I originally ran into this every time with a larger data set, that presumably has some groups only represented once in the grp_index array. I could get rid of those groups in the dataset, but wondered if this is a bug with the variational algorithm.

Thanks for filing the issue.  This is a known bug with the way
errors are currently being trapped, which is why it hasn't
been ported to RStan yet --- this would've crashed RStan if
we'd included it.
We should have this fixed (and a version in RStan) by the
next release.

Bob

On Jul 20, 2015, at 3:53 PM, Chris<EMAIL_ADDRESS>wrote:
For the following model
data {
int N;
vector[N] p;
int Ngrps;
int<lower=1, upper=Ngrps> grp_index[N];
}
parameters {
vector<lower=0.0001, upper=100>[Ngrps] sigmaGrp;
vector<lower=-100, upper=1000>[Ngrps] muGrp;
}
model {
int grpi;
for (i in 1:N){
grpi <- grp_index[i];
p[i] ~ logistic(muGrp[grpi], sigmaGrp[grpi]);
};
}
I'm trying to estimate group level parameters from the following data (I generated with python and saved data file test.R with pystan):
p = 63.1, 108.3, 1.0, 46.0, 22.9, 14.8, 28.8, 52.5, 60.1, 81.3
grp_index = [1, 1, 1, 1, 1, 1, 2, 3, 4, 5]
test_dat = dict(
N=len(p),
p=p,
grp_index=grp_index,
Ngrps=len(set(grp_index)),
)
When I compile and sample with advi using
$ modeldir/model/test variational data file=modeldir/dat/test.R random seed=3021828106
I get the exception:
Exception: stan::variational::normal_meanfield::set_mu: Input vector[7] is nan, but must not be nan!
Diagnostic information:
Dynamic exception type: std::domain_error
std::exception::what: stan::variational::normal_meanfield::set_mu: Input vector[7] is nan, but must not be nan!
This is a small dataset, and the error can be avoided if I run with most other random seeds, but I originally ran into this every time with a larger data set, that presumably has some groups only represented once in the grp_index array. I could get rid of those groups in the dataset, but wondered if this is a bug with the variational algorithm.
—
Reply to this email directly or view it on GitHub.

Specifically it is #1544 and there is a pull request (that needs some work) for it. So, I think we can close this issue.

Yup, hopefully when I have time later this week, I can repush some changes to the current pull request as it isn't working at the moment.


Release log after exception so that old log name can be used again.

Hi, here's the fixed line endings version of my previous PR.

Thanks, looks good!


npm build doesn't do anything

While making changes in a fork, npm test works as expected, npm build doesn't seem to run(?)
Probably a user error.

Try npm run build. npm build is used when building from a folder, like npm build angular-addtocalendar run from the parent directory.

Ahh, thanks for the help! That's workin'


Align Flow example with Polymer

Align Flow example to reflect the structure of Polymer example.

Partly done via https://github.com/vaadin/ui-examples/commit/b9dbb160b28004c20f969719e0df201fcd18e832 and https://github.com/vaadin/ui-examples/commit/fc4fdfefe8cf055f3b81be754fb348e24513a1b8
Two tickets need to be completed in order to fully align the examples:
https://github.com/vaadin/vaadin-grid-pro-flow/issues/26
https://github.com/vaadin/vaadin-grid-pro-flow/issues/27


Mobile Navbar cut off by screen size

After #2011 was merged I was checking out the website on mobile and I noticed that the navbar is cut off by the size of the screen. in portrait mode, it is not a big problem unless you try to open some of the dropdowns like the very last one
the big issue comes when in landscape mode.

I tried to fix it myself but I'm not good at mobile CSS and I won't have a good way of testing it on mobile until mid-January. @violetcraze

If you take out the height of the nav, you can see the 'cut off' links again.

fixed by #2027


CosmicTroubleshooting Reduce number of engineInstances in load testing

Currently the engineInstances is set to 4 in bash and PowerShell.
Unfortunately "typical" subscription doesn't allow that, so I propose to reduce it to "1", to avoid:
Azure Load Testing dataplane returned different status code (400, was expecting 200 or 201) for test creation.\n{"statusCode": 400,
"exitCode": 0,
"body": "{\"error\":{\"code\":\"QuotaExceeded\",\"message\":\"Operation could not be completed as it results in exceeding the quota of 1 maxEngineInstancesPerTestRun per subscription in the region East US. Please create a support ticket to increase the limit.\",\"target\":null,\"details\":null}}"}

Thanks goes to Adam Marczak!

The question would be, will 1 instance be enough to show the issue? If not, maybe lowering RU/s on container will?

Piotr, thanks for the update!
@istavrinides As the original author, what do you say?

Making this change would lead to the actual load test to fail (the load test simulates 1000 users and Azure Load Testing requires 1 engine instance per 250 simulate users). I would propose we close this PR without merging, and I will add documentation to either ensure enough quota or guidance on how to lower both deployed # of instances as well as users in the JMeter script.

Thanks again Piotr for your interest in this hack and taking the time to propose an update!  As per @istavrinides guidance, I will close this PR.
-Peter


monitor only shows moon info

This can be fixed by using "StartOfRound.Instance.SwitchMapMonitorPurpose(false);" on the StartOfRound singleton

This bug also appears to occur when new players join, likely without the latecompany mod installed(?)

I have no idea what this issue is referring to


Move rollbar to resque

Asynchronous Rollbar reporting

A quick experiment but it works. Maybe it's worth trying it to avoid slowing the ruis when Rollbar goes down. Opinions from @CartoDB/builder-backend ?

Ping!?

Given that I would like to have some #systems feedback on this, I'd wait a couple of weeks. Archiving the PR for now, I'll revive it when we get the chance.


tests/eas/preliminary: Make TestSchedutilTunables mainline-friendly

I wrote with a version of schedutil in mind that was
hacked by the EAS project to have two separate rate limiting
tunables, up_rate_limit_us and down_rate_limit_us. I forgot that the
mainline version only has rate_limit_us.
Just check each tunable that endswith rate_limit_us to make this
generic across schedutil versions.

Thanks for review, updated. Also fixed a missing conversion to int.

LGTM


ASR rules supported by GPO and PowerShell

[Enter feedback here]
Hi Team,
I have a question for the table under Supported configuration management systems. GPO and PowerShell are actually can configure ASR rules by its GUID and not only one rule is supported. Why this table indicate there is only one ASR rule supported?
Thanks!

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

ID: c664e229-9294-6515-f586-12a1f0348308
Version Independent ID: a97f107c-fd36-143a-ea68-ee2248f11362
Content: Attack surface reduction rules
Content Source: microsoft-365/security/defender-endpoint/attack-surface-reduction-rules.md
Product: m365-security
Technology: mde
GitHub Login: @jweston-1
Microsoft Alias: v-jweston

@jweston-1 Pleas help us in resolving this issue. Thanks

In progress

Fixed. See: https://docs.microsoft.com/microsoft-365/security/defender-endpoint/attack-surface-reduction-rules-reference?view=o365-worldwide#supported-configuration-management-systems


kube-dns does not need port

@Cynerva found that we may not need the dns port in the current code. We should look at removing port from the relation if is not needed or used.

@mbruzek Thanks for opening this, sorry I didn't get to it!
For context, this is a follow-up to https://github.com/juju-solutions/kubernetes/pull/64/files#diff-bdfd6f6b79f7f3171e9f0167164a7c98L164 where we removed the DNS port from --cluster-dns on the worker.
It doesn't look like there is a way to pass in a non-standard port to kubelet. This is a cleanup issue to remove "port" from the kube-dns relation as well.

This is no longer valid as we dont use the kube-dns relationship anymore. This has been fully deprecated in favor of the kube-control relation.


[mongo] - "authSource" is not being utilized in _parse_uri() method.

There is a connection error returned while trying to connect to mongo replica set and database other than "admin".

**Output of the info page **
====================
Collector (v 5.13.2)
====================

  Status date: 2017-08-16 07:25:16 (9s ago)
  Pid: 18
  Platform: Linux-3.13.0-121-generic-x86_64-with-debian-8.8
  Python Version: 2.7.13, 64bit
  Logs: <stderr>, /var/log/datadog/collector.log

  Clocks
  ======

    NTP offset: 0.001 s
    System UTC time: 2017-08-16 07:25:25.681839

  Paths
  =====

    conf.d: /etc/dd-agent/conf.d
    checks.d: /opt/datadog-agent/agent/checks.d

  Hostnames
  =========

    ec2-hostname: ip-10-X-X-X.stage.internal
    local-ipv4: 10.X.X.X
    socket-hostname: e6ea97c7aabb
    hostname: i-0e363669f376df574
    local-hostname: ip-10-X-X-X.stage.internal
    instance-id: i-0e363669f376df574
    socket-fqdn: e6ea97c7aabb

  Checks
  ======

    ntp (5.13.2)
    ------------
      - Collected 0 metrics, 0 events & 0 service checks

    disk (5.13.2)
    -------------
      - instance #0 [OK]
      - Collected 32 metrics, 0 events & 0 service checks

    mongo (5.13.2)
    --------------
      - instance #0 [ERROR]: 'Mongo: cannot connect with config `mongodb://*****@stage-shard-00-00-xxx.mongodb.net:27017,stage-shard-00-01-xyx.mongodb.net:27017,stage-shard-00-02-xzz.mongodb.net:27017/mydb?ssl=true&replicaSet=stage-shard-0&authSource=admin`'
        Traceback (most recent call last):
          File "/opt/datadog-agent/agent/checks/__init__.py", line 788, in run
            self.check(copy.deepcopy(instance))
          File "/opt/datadog-agent/agent/checks.d/mongo.py", line 721, in check
            raise Exception(message)
        Exception: Mongo: cannot connect with config `mongodb://*****@stage-shard-00-00-xxx.mongodb.net:27017,stage-shard-00-01-xyx.mongodb.net:27017,stage-shard-00-02-xzz.mongodb.net:27017/mydb?ssl=true&replicaSet=stage-shard-0&authSource=admin`

      - Collected 0 metrics, 0 events & 1 service check
      - Dependencies:
          - pymongo: 3.2

    docker_daemon (5.13.2)
    ----------------------
      - instance #0 [WARNING]
  Emitters
  ========

    - http_emitter [OK]

====================
Dogstatsd (v 5.13.2)
====================

  Status date: 2017-08-16 07:25:17 (8s ago)
  Pid: 15
  Platform: Linux-3.13.0-121-generic-x86_64-with-debian-8.8
  Python Version: 2.7.13, 64bit
  Logs: <stderr>, /var/log/datadog/dogstatsd.log

  Flush count: 14
  Packet Count: 254
  Packets per second: 1.9
  Metric count: 14
  Event count: 0
  Service check count: 0

====================
Forwarder (v 5.13.2)
====================

  Status date: 2017-08-16 07:25:21 (4s ago)
  Pid: 14
  Platform: Linux-3.13.0-121-generic-x86_64-with-debian-8.8
  Python Version: 2.7.13, 64bit
  Logs: <stderr>, /var/log/datadog/forwarder.log

  Queue Size: 0 bytes
  Queue Length: 0
  Flush Count: 47
  Transactions received: 30
  Transactions flushed: 30
  Transactions rejected: 0
  API Key Status: API Key is valid

======================
Trace Agent (v 5.13.2)
======================

  Pid: 13
  Uptime: 152 seconds
  Mem alloc: 1293544 bytes

  Hostname: i-0e363669f376df574
  Receiver: <IP_ADDRESS>:8126
  API Endpoints: https://trace.agent.datadoghq.com

  Bytes received (1 min): 0
  Traces received (1 min): 0
  Spans received (1 min): 0

  Bytes sent (1 min): 0
  Traces sent (1 min): 0
  Stats sent (1 min): 0

Additional environment details (Operating System, Cloud provider, etc):
Platform: Linux-3.13.0-121-generic-x86_64-with-debian-8.8
Python Version: 2.7.13, 64bit
pymongo: 3.2
Steps to reproduce the issue:

Try to setup mongo replica connection string in mongo.yml to track stats from your database ("mydb") and use "admin" database as an authentication source, like below:

  - server: mongodb://user:pass@stage-shard-00-00-xxx.mongodb.net:27017,stage-shard-00-01-xyx.mongodb.net:27017,stage-shard-00-02-xzz.mongodb.net:27017/mydb?authSource=admin&ssl=true&replicaSet=stage-shard-0

or alternatevily:
  - server: mongodb://user:pass@stage-shard-00-00-xxx.mongodb.net:27017,stage-shard-00-01-xyx.mongodb.net:27017,stage-shard-00-02-xzz.mongodb.net:27017/mydb?ssl=true&replicaSet=stage-shard-0

    auth_source: admin

Restart datadog agent
Check agent status.

Describe the results you received:
Getting authentication error in data dog log:

- instance #0 [ERROR]: 'Mongo: cannot connect with config `mongodb://*****@stage-shard-00-00-xxx.mongodb.net:27017,stage-shard-00-01-xyx.mongodb.net:27017,stage-shard-00-02-xzz.mongodb.net:27017/mydb?ssl=true&replicaSet=stage-shard-0&authSource=admin`'
--
Traceback (most recent call last):
File "/opt/datadog-agent/agent/checks/__init__.py", line 788, in run
self.check(copy.deepcopy(instance))
File "/opt/datadog-agent/agent/checks.d/mongo.py", line 721, in check
raise Exception(message)
Exception: Mongo: cannot connect with config `mongodb://*****@stage-shard-00-00-xxx.mongodb.net:27017,stage-shard-00-01-xyx.mongodb.net:27017,stage-shard-00-02-xzz.mongodb.net:27017/mydb?ssl=true&replicaSet=stage-shard-0&authSource=admin`

Describe the results you expected:
I should be able to get stats for "mydb" database while using "admin" as an authentication source.
Additional information you deem important (e.g. issue happens only occasionally):
I believe that the problem is caused by the _parse_uri() method in integrations-core/mongo/check.py . The method is not utilising the authSource parameter properly, so that it's never returned and passed to the connection establish part, thus "mydb" is mistakly treated as an authentication source.
It's confirmed in the mongo log ("user" tries to authenticate in "mydb" and should be "admin"):
2017-08-11T20:30:00.667+0000 I ACCESS   [conn208423] SCRAM-SHA-1 authentication failed for monitor on cloudwife from client 10.X.X.X ; UserNotFound: Could not find user user@mydb

Hi @michaljrk,
Thanks for opening this issue. We currently don't support the authSource parameter. I just open a PR to fix this.
Would you be able to try it and tell us if it resolves your problem.
Thanks !

The PR has been merged and will be available in the agent version 5.17.
I'm closing this issue, feel free to reopen it if needed.

As soon as 5.17 is released, I will test it.
Thanks a lot for a fast reaction!

Test in 5.17 and it's working like a charm. Cheers !


predictor.model.args defined in InferenceService does not override containers.args in ServingRuntime

/kind bug
What steps did you take and what happened:
When specifying both args field in InferenceService and ServingRuntime, the both args field are combined in a list which is then consumed by the predictor deployment  in the example shown below. In this example, the inference-predictor cannot start because the  text-generation-launcher command can only takes ` port value.
  containers:
  - args:
    - --port=3000
    - --port=3000
    - --grpc-port=8033
    - --num-shard=1
     command:
      - text-generation-launcher

What did you expect to happen:
I'd expect the predictor.model.args defined in InferenceService to override containers.args in ServingRuntime
What's the InferenceService yaml:
[To help us debug please run kubectl get isvc $name -n $namespace -oyaml and paste the output]
See above
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:

Istio Version: N/A
Knative Version: N/A
KServe Version: 0.11
Kubeflow version: N/A
Cloud Environment: ibm
Minikube/Kind version: N/A
Kubernetes version: OCP 4.13 / K8s 1.26
OS (e.g. from /etc/os-release): Linux

/assign

This is a nice to have, found a workaround. Thank you


Creating test case for issue with class-transformer

@pleerock here is the example I have on routing controllers for my issue with the class transformer. If you locally link the change in class-transformer it will fix the test issues this change has caused.

@alexthebuilder actually I was talking to create a test case in the class transformer library, not here. It does not mean that you should install routing-controllers in the class-transformer library. It means that this issue should not specific to routing-controllers and it can be represented in isolation

@pleerock I understand what you are asking but the level of effort to isolate the issue due to the way its used in this the routing-controller is a bit of work. I was hoping this test case would show you the issue. I'll put some effort to try and comb through the code here to isolate why the other module is breaking.


Increasing timeout for CI job of 'che-dockerfiles'

Hi @ibuziuk - @l0rd last PR removed this job entirely, do we need to bring it back ? or are you ok to close this - i noticed he has a higher timeout already in the new job

I believe we can close this one


supportting inline workflow definition within subworkflow?

The releasing v2.27.1 mentioned that supportting inline workflow definition within subworkflow, how to understand it? and do you have instruction documents?

@andyyumiao This feature enables the workflowDefinition to be passed in dynamically into a sub workflow task. Checking the source code, the usage of this feature would look like so,
  "name": "sub_workflow_task",
  "taskReferenceName": "sub1",
  "type": "SUB_WORKFLOW",
  "inputParameters": {
    "subWorkflowParam": {
      "name": "deployment_workflow",
      "version": 1,
      "taskToDomain": {
        "*": "mydomain"
      }
    },
    "anythingelse":  "value"
  },
 "workflowDefinition": {
   "name": "deployment_workflow",
  "description": "Deploys to CDN",
  "version": 1,
  "tasks": [
    {
      "name": "deploy",
      "taskReferenceName": "d1",
      "type": "SIMPLE",
      "inputParameters": {
        "fileLocation": "${workflow.input.encodeLocation}"
      }
    }
  ],
  "outputParameters": {
    "cdn_url": "${d1.output.location}"
  },
  "failureWorkflow": "cleanup_encode_resources",
  "restartable": true,
  "workflowStatusListenerEnabled": true,
  "schemaVersion": 2
 }
}

Please note the inlined workflow definition for the subworkflow in the example above.

hello, I created a workflow which contains a sub_workflow with inline workflow definition mentioned above,  the wrokflow json is:
{ 	"name": "virtual_parent_workflow", 	"workflowDef": { 		"ownerApp": "xiaowei12", 		"ownerEmail"<EMAIL_ADDRESS>		"createdBy": "xiaowei12", 		"name": "virtual_parent_workflow", 		"description": "virtual test", 		"version": 1, 		"tasks": [ 			{ 				"name": "virtual_son_wf_01", 				"type": "SUB_WORKFLOW", 				"taskReferenceName": "virtual_son_wf_01", 				"inputParameters": {}, 				"subWorkflowParam": { 					"name": "myDynamicWf", 					"version": "1", 					"workflowDefinition": { 						"name": "myDynamicWf", 						"description": "xxx", 						"version": 1, 						"tasks": [ 							{ 								"name": "simple_sleep_task", 								"taskReferenceName": "simple_sleep_task01", 								"inputParameters": { 									"simpleTimeout": "1" 								}, 								"type": "SIMPLE" 							} 						], 						"failureWorkflow": "cleanup_encode_resources", 						"restartable": true, 						"workflowStatusListenerEnabled": true, 						"schemaVersion": 2 					} 				} 			} 		] 	}, 	"input": {} }
the workflow can be executed completely , but when I try to look up the details of parent workflow , I got a nerror:

could you help me solve this problem, thank you very much?
@apanicker-nflx

@xiaowei582648206 I believe the UI doesn't support inline subworkflow definitions yet. We're considering revamping the UI, which would have a fix for this, but we're not certain of the timelines yet. If you could get to this before the release of latest UI, please send us a PR.

thanks a lot！