add maxHttpRequestsPerSource to docs

Fixes: https://github.com/NuGet/docs.microsoft.com-nuget/issues/2033

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

File
Status
Preview URL
Details

docs/reference/nuget-config-file.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 1cc998c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/reference/nuget-config-file.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 93fadd3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/reference/nuget-config-file.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 61b58aa:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/reference/nuget-config-file.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 12863a0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/reference/nuget-config-file.md
:white_check_mark:Succeeded
View

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


Nominate button does not work #101

Add a form to fill in the details of a possible new member

Ya envie los nuevos cambios

I already sent the new changes

@robertrm0 send me a DM in WhatsApp


Add help text for drug interaction type in evidence item edit form

Currently there is not explanation of the drug interaction type field in the edit evidence item form.  It just says: "Drug Interaction Type Help text"

I replaced that with the text: 'Please indicate whether the drugs specified above are subtitutes, or act as sequential or combination treatments.'


Can't disable typescriptMismatch warning

Bug Report or Feature Request (mark with an x)
- [x ] bug report -> please search issues before submitting
- [ ] feature request

When want to disable the typescriptMismatch warning on a project-basis so it only affects a particular project and the warning is automatically disabled for other developers. Hence, I want to disable it from within the angular-cli config file.
Versions.
@angular/cli: 1.4.1
node: 7.7.1
os: win32 x64
@angular/common: 4.3.6
@angular/compiler: 4.3.6
@angular/core: 4.3.6
@angular/forms: 4.3.6
@angular/http: 4.3.6
@angular/platform-browser: 4.3.6
@angular/platform-browser-dynamic: 4.3.6
@angular/router: 4.3.6
@angular/cli: 1.4.1
@angular/compiler-cli: 4.3.6
typescript: 2.5.2
Repro steps.
Setup angular project to use latest typescript.
Add this to .angular-cli.json:
    "warnings": {
        "typescriptMismatch": false
    }

run "ng build"
The output given by the failure.
<EMAIL_ADDRESS>requires<EMAIL_ADDRESS><2.4.0' but 2.5.2 was found instead.
Using this version can result in undefined behaviour and difficult to debug problems.
Please run the following command to install a compatible version of TypeScript.
npm install<EMAIL_ADDRESS><2.4.0'

To disable this warning run "ng set --global warnings.typescriptMismatch=false".
Desired functionality.
When I disable the typescriptMismatch warning in  .angular-cli.json I expect the warning to disappear when running ng build.
Mention any other details that might be useful.
It might be possible to disable the warning instead by setting a global flag but I want something that only affects a single project yet is shared with other developers automatically. Setting a global flag won't do that.

Currently we only support disabling it globally, but I agree it would be good to work locally as well. Will implement.


AWS, AZURE: Switch DE templates to use temporaryStorage: EPHEMERAL or…

… temporaryStorage: COMBINED/EPHEMERAL_OR_ATTACHED for 7.2.16 and 7.2.17

This commit changes the instance type for compute and worker nodes of Data engineering cluster templates for AWS of 7.2.16 and 7.2.17.
Compute nodes are updated to use "r5d.2xlarge" and "r5d.4xlarge" for non-ha and ha templates respectively with ephemeral volume.
Worker nodes are updated to use "r5d.2xlarge" and "r5d.4xlarge" for non-ha and ha templates respectively with gp2/ebs volume.

See detailed description in the commit message.

Jira ticket missing in commit message


python3Packages.rtb-data: init at 1.0.1

Description of changes
Adds rtb-data to Python packages.
One part of many to add roboticstoolbox to Python packages.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 321911 run on x86_64-linux 1

4 packages built:

python311Packages.rtb-data
python311Packages.rtb-data.dist
python312Packages.rtb-data
python312Packages.rtb-data.dist

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4136

Result of nixpkgs-review pr 321911 run on x86_64-linux 1

4 packages built:

python311Packages.rtb-data
python311Packages.rtb-data.dist
python312Packages.rtb-data
python312Packages.rtb-data.dist

Result of nixpkgs-review pr 321911 run on x86_64-linux 1

4 packages built:

python311Packages.rtb-data
python311Packages.rtb-data.dist
python312Packages.rtb-data
python312Packages.rtb-data.dist


derive(Diffus) "leaks" serialize-impl feature

remedy by using feature serde instead to be conformant?
any other solution?


Fix color future warning

This is a small PR that addresses #307 and fixes a couple minor bugs

If anyone can please give this an OK, I would merge it afterwards, no high-impact changes here

so in general everything LGTM but this only works for environments with napari >= 0.4.19 so there is a backward compatibility breaking change I guess we should mention?

True, we would then have to update dependencies as well. I think we are moving in that direction for the next release, right?

That is true but maybe that would create issues with the devbio-napari system... @haesleinhuepf: do you know if relying on a specific napari version would cause issues for the devbio napari install?

Let's wait for @haesleinhuepf feedback on this, it can be halted since it is not a major fix.
I would like to eventually have it implemented (maybe it can wait a couple months or so), because it does impact a little my usage of the current plotter by the napari-flim-phasor-plotter plugin

I will break this PR into 2.

here, only changes needed to fix the FutureWarning will be kept
the other minor changes were moved to #313

This PR should remain open until we are sure we do not break devbio-napari installation.

As of napari 0.5.0 this is now an error:
TypeError: _add_layer_from_data received an unexpected keyword argument ('color') for layer type labels

It would be great if this fix gets into a release soon.

OK now this is a bug with napari>=0.5.0.
The workaround until this is fixed is to use a lower napari version...

this only works for environments with napari >= 0.4.19 so there is a backward compatibility breaking change

You can check the napari installed version and pass one key or the other based on that, which is what we did with napari-ome-zarr, here:
https://github.com/ome/napari-ome-zarr/pull/112/files#diff-3ac23664593f6255d26806df61d2364f3d3f0b66c53a4fad561a70877093239aR134-R139
Let us know if you have any questions about the new API!

You can check the napari installed version and pass one key or the other based on that, which is what we did with napari-ome-zarr, here:
https://github.com/ome/napari-ome-zarr/pull/112/files#diff-3ac23664593f6255d26806df61d2364f3d3f0b66c53a4fad561a70877093239aR134-R139

Oh nice @jni ! I will give this a try! Thanks!

With the current state of this PR, there is no need to check for the napari version, it should work whether the Labels layer has the .color attribute or not because the colors dictionary is always converted with DirectLabelColormap (only available with napari>=0.4.18 TMK) into a colormap and assigned to the .colormap attribute.
I tried to install this version on top of the latest devbio-napari version (0.10.1) but I could not make it work when installing with pip becasue it brings npe>=0.7.0,
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
devbio-napari 0.10.1 requires npe2<0.7.0, but you have npe2 0.7.7 which is incompatible.

This seems to be a requirement of napari>=0.5.1. For example, if I try to downgrade npe2 to 0.6.2, I get:
- package napari-base-0.5.1-pyh9208f05_0 requires npe2 >=0.7.6
So, napari-clusters-plotter may still work if installed with mamba/conda along with devbio-napari, but we can only test that after generating a new recipe in conda-forge (TMK).
I suggest we merge changes here regardless of the problems above because otherwise this is a bug of this plugin when napari>=0.5.0.
If this new version impacts devbio-napari installation, we should create an issue there and work on a solution from the outside, but not here.
@jo-mueller, if you agree, could you merge this?

Agreed @zoccoler, thanks for the fix!

the colors dictionary is always converted with DirectLabelColormap (only available with napari>=0.4.18 TMK) into a colormap

It became available in 0.4.19. We should probably start adding .. versionadded:: directives to docstrings when we add new things... 😅🙏

the colors dictionary is always converted with DirectLabelColormap (only available with napari>=0.4.18 TMK) into a colormap

It became available in 0.4.19. We should probably start adding .. versionadded:: directives to docstrings when we add new things... 😅🙏

You are right, my mistake! I had looked into napari API for other versions to check that. DirectLabelColormap only "shows up" in 0.4.19 (https://napari.org/0.4.19/api/index.html), thanks for the correction!
We have 0.4.19 as a requirement here (https://github.com/BiAPoL/napari-clusters-plotter/blob/44a658789fc119e339e320e4cab10238d67781eb/setup.cfg#L52C5-L52C19) so it should all be fine 😌


Fix dockerhub promote action

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 39.00%. Comparing base (23880a7) to head (eda376e).

Additional details and impacted files
@@           Coverage Diff           @@
##               v2     #232   +/-   ##
=======================================
  Coverage   39.00%   39.00%
=======================================
  Files          30       30
  Lines        1564     1564
=======================================
  Hits          610      610
  Misses        876      876
  Partials       78       78

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Update screenshot after diagnostics UI changed

Signed-off-by: Stephen Turner<EMAIL_ADDRESS>Proposed changes
Update screenshot after diagnostics UI changed
Unreleased project version (optional)
Applies to next version of Docker for Windows
Related issues (optional)
docker/pinata#9175

Thanks, Gwen. Not in 18.03.1. It will be in the next edge release (18.05) and the next stable (18.06, I guess).


errors for new dev environment

After creating a new dev environment the exposecontroller is in a crash loop:
I0828 00:48:32.736226       1 exposecontroller.go:60] Using build: '2.3.70'
I0828 00:48:32.785312       1 config.go:22] No /etc/exposecontroller/config.yml file found.  Will try to figure out defaults
W0828 00:48:32.785366       1 exposecontroller.go:81] %!s(<nil>)
W0828 00:48:32.787346       1 exposecontroller.go:98] Could not find ConfigMap exposecontroller in namespace jx-edit-mattmor2
I0828 00:48:32.787606       1 exposecontroller.go:103] Config file before overrides exposer: ""
path-mode: ""
apiserver-protocol: ""
watch-namespaces: ""
watch-current-namespace: false
http: false
tls-acme: false
I0828 00:48:32.787763       1 exposecontroller.go:133] Config file after overrides exposer: ""
path-mode: ""
apiserver-protocol: ""
watch-namespaces: ""
watch-current-namespace: true
http: false
tls-acme: false
I0828 00:48:32.787781       1 exposecontroller.go:165] Watching services in namespaces: `jx-edit-mattmor2`
I0828 00:48:32.787933       1 controller.go:78] NewController false
I0828 00:48:32.809603       1 auto.go:32] Using exposer strategy: ingress
F0828 00:48:32.834721       1 exposecontroller.go:169] failed to create new strategy: failed to create auto expose strategy: failed to get a domain: failed to find any nodes: nodes is forbidden: User "system:serviceaccount:jx-edit-mattmor2:exposecontroller-service" cannot list nodes at the cluster scope: Unknown user "system:serviceaccount:jx-edit-mattmor2:exposecontroller-service"

Does it need a ClusterRoleBinding instead of RoleBinding?
helm list --namespace jx-edit-mattmor2
NAME               	REVISION	UPDATED                 	STATUS  	CHART                         	APP VERSION	NAMESPACE
jx-edit-mattmor2-es	4       	Tue Aug 28 12:42:35 2018	DEPLOYED	exposecontroller-service-1.0.4	           	jx-edit-mattmor2

hitting this as well when setting custom expose.config.urltemplate


fix(region): network brand

What this PR does / why we need it:

[ ] Smoke testing completed

If yes, write the release branches name in the below format and submit the related cherry-pick PR:

release/3.8

/cc @swordqiu
/area region

/lgtm
/approve


Fix panic when meminfo couldn't be read

Fixes panic reported by @abronan in https://github.com/docker/docker/pull/24516#issuecomment-232125090

LGTM
On 12 Jul 2016 8:31 p.m., "Brian Goff"<EMAIL_ADDRESS>wrote:

Fixes panic reported by @abronan https://github.com/abronan in #24516
(comment)
https://github.com/docker/docker/pull/24516#issuecomment-232125090
You can view, comment on, or merge this pull request online at:
https://github.com/docker/docker/pull/24549
Commit Summary

Fix panic when meminfo couldn't be read

File Changes

M daemon/info.go
https://github.com/docker/docker/pull/24549/files#diff-0 (1)

Patch Links:

https://github.com/docker/docker/pull/24549.patch
https://github.com/docker/docker/pull/24549.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker/pull/24549, or mute the thread
https://github.com/notifications/unsubscribe/AAdcPHvh0MthOXu53_D0py2d1iw7XVEmks5qU-uDgaJpZM4JKvW5
.

LGTM

LGTM

Ah experimental hitting https://github.com/docker/docker/issues/23401
Merging anyway…


Fix CMake build of TFLite C Library

Following the guide on how to build the TensorFlow Lite C library from source, I ran into an issue where the build was failing due to missing file common.c:
CMake Error at CMakeLists.txt:63 (add_library):
  Cannot find source file:

    common.c

  Tried extensions .c .C .c++ .cc .cpp .cxx .cu .mpp .m .M .mm .ixx .cppm .h
  .hh .h++ .hm .hpp .hxx .in .txx .f .F .for .f77 .f90 .f95 .f03 .hip .ispc

CMake Error at CMakeLists.txt:63 (add_library):
  No SOURCES given to target: tensorflowlite_c

I noticed that the file seems to have been renamed.
This PR updates the entry in CMakeLists.txt and fixes the issue with the build.

Hi @Ameobea  This PR is the duplicate of PR#54566. Hence closing this PR.  Thank you!


Alias --shell pwsh to --shell powershell

The newer binaries are called pwsh.exe

Whoops, got confused.


Reload/Refresh model from database.

I would like to be able to call
modelInstance.reload()
To build a select query using the instance's ID and reload the data from the database into the model.  I am aware of fetch but it forms a query from all of the attributes, meaning that if some attributes were changed in memory, the query will not find the model.
For now I have been manually passing the ID of the instance into a new query, but this feels kind of silly.

Hi @light24bulbs. You'll be happy to know that I actually wrote this change yesterday.
I can't see any problem with changing the behaviour of fetch for this. As was pointed out in a couple of other issues, having fetch match on columns other than idAttribute has unexpected behaviour such as using non-indexed columns and sometimes attempting to fetch with JSON attributes (which have no equality operator).
I just haven't merged the changes in because of the problems with the new JSON tests in Travis CI.
Semantically I like the idea of refresh,reload or renew, but since fetch currently updates the model on which it's called, it makes sense to just change its behaviour.
Ultimately I think it would be nice to have a distinction between fetch and refresh. refresh would update the model itself, and fetch gets a nice model. I think it's too soon for such a dramatic API break though.

Hi, @rhys-vdw
Updating fetch to use only the ID seems far more breaking to me.  For instance, my code frequently does
Model.forge(anAttribute: 'aValue').fetch()
as a way to query by parameters.  I think fetch works well and that it's behavior isn't so unexpected.  I would rather have a separate method refresh or reload to handle this.  I don't consider it to be API breaking to introduce a new method.  I think it is more breaking to change the behavior of an existing method.

Oh, sorry, I probably wasn't clear enough. It checks for the presence of idAttribute and fetches by that. If not it uses its current behaviour.

Oh.
Hmm, well, In my opinion, that is a more unexpected behavior than it was before, because before it was constant.  You've taken two logically separate functions and combined them into one method which magically switches between them.
And believe it or not, it actually does break some of my code and possibly other's code as well.  Some of my code does:
Model.forge(id: 21, anAttribute: 'aValue').fetch()
Though this could obviously be rewritten, I would still argue for introducing a new method refresh as it is more clear and gives the user a choice of which functionality they want. Could you explain how a new method would be API breaking where changing an existing method is not?
If you're tied to this functionality, maybe checking isNew when deciding to use the id or not would work well.
But hey, I love the lib otherwise.  You guys are doing something right :)
Thank you for all the hard work which makes my life easier!

Okay, good to hear feedback on this. I wasn't sure whether to go ahead with it. Personally I was surprised by the behaviour of fetch (as were others #550, #778). It is inconsistent with the behaviour of save which assumes that an object exists if it has an idAttribute.
But you've raised a valid point. Perhaps refresh would be more appropriate. Ultimately I think this API would be cleaner:
// deprecated
Model.forge({id: 4}).fetch()

// preferred
Model.where({id: 4, other: 'value'}).fetch();
Model.forge({id: 4}).refresh();

Yeah sometimes I also use the ability to fetch by a given attribute but never when combined with an id attribute as well. @light24bulbs Why would you want to fetch with non-id attributes and the id attribute at the same time? It doesn't make sense to me since the id attribute is already specifying a single row, so you can't be more specific than that, and considering that the result would be the same in both cases. Is it some kind of security concern? That is, you want the possibility of returning nothing if the id and the otherAttribute don't match a row that exists?
That said, the Model.where({ ... }).fetch() form does look like the preferred way to fetch by random attributes.
If we were to change this behaviour it should be preceded by deprecation messages first to give users time to migrate to the preferred way of fetching. Seems like the only change would be to replace forge with where right?

Well, at the moment I think just adding refresh is enough. I agree that the current behaviour of fetch on a Model instance doesn't make sense. You'd expect it to update the model, but it doesn't, in fact it will fail if the row has changed.

@light24bulbs Hey mate, this is now in master. I took your advice and left fetch as it is. refresh will default to fetch's behaviour if no idAttribute is present. If you're keen you can point your project dependency the current head commit to get the change. Thanks for the feedback.

Awesome!  Just what I needed.  Thank you!

This is super useful, thanks!


CreateEvent Function

Hi! Does this package support CreateEvent Function?
I try to implement some function like Monitoring Communications Events. But I can't find CreateEvent Funtion in win32 package.
Here is CreateEvent doc:
https://docs.microsoft.com/en-us/windows/win32/devio/monitoring-communications-events

As a temporary solution, I suggest using this fork.
environment:
  sdk: '>=2.13.0 <3.0.0'

dependencies:
  win32:
    git:
      url: https://github.com/ilopX/win32
      ref: create_event

As a temporary solution, I suggest using this fork.
dependencies:
  win32:
    git:
      url: https://github.com/ilopX/win32
      ref: create_event

Thanks! I will using this fork to implement my function. Hope the PR can be merged soon.


ISPN-7574 Upgrade Management Console to 9.0.0.CR3

https://issues.jboss.org/browse/ISPN-7574

Integrated, thanks @ryanemerson !


Buildings have no health

Hi, what dou you mean when you say that the buildings have no health?
Thanks!


Need typescript support. Need pnpm support

I've checked this project.
It's useless for me until Typescript + pnpm support will be implemented.
Also, it would be great to have options as create-next-app
Is that supposed to add?

Hi @rxqd,
Thank you for your feedback. I agree with you. I should offer Typescript and phpm support.
It is good to know that we have people interested in this project. I am not a fan of Typescript, but I need to admit that it has a huge community.
Currently situation:

I am using a separate repository to manage the template files
There is an issue there to work on https://github.com/raphox/next-rails-scaffold/issues/5
The idea is to generate a new folder with the Typescript and Tailwind codes

Your suggestion and interest have encouraged me to continue the development. I hope to have news soon.
Best regards.


Added tzdata package to get timezones

Mac-Users are not able to get timezone information with timedatectl list-timezones, because of that I added a general solution for getting a list of timezones by adding the hex package tzdata

A nice fix, thank you!


dont work on windows 10.0.19041.1348

Listener state: Not listening [not suported]
Do you have a solution?
Thanks

Duplicate of https://github.com/stascorp/rdpwrap/issues/1595


forceFallback & scaled container produce continuously multiplied scale

Problem:
When a container element wrapping the SortableJS interaction is being scaled with a CSS transform and forceFallback: true is being used, there appears to be an error in the calculation of scaling for the .sortable-fallback element, causing it to continually rescale ever smaller/larger on each drag position update.
With a scale of less than 1 on the ancestor element, the dragged item vanishes to oblivion and over-corrects X/Y position. With a scale of greater than 1, the dragged item grows to encompass the whole screen.
It seems that a calculation that should be happening once to correct for the scale is instead happening continuously and cumulatively.
This behaviour does not appear to exist in 1.9.0.
JSBin/JSFiddle demonstrating the problem:
Demonstration of draggable item shrinking exponentially:
http://jsfiddle.net/GBorreson/m549v1t0/6/

I encountered the same problem.

Fixed in aae2c97180e2096aaa539ba3357080612469d000

+1 Same problem here for Chrome


Add an option to the angular builder to not emit initReflector

If you are using the runApp bootstrapping, then this code shouldn't be necessary.
Note that in my experiments this has no effect on dart2js size, but it does have a significant effect on the amount of code that dartdevc will ship to the browser.
As an example, for the angular_components package this reduces the cost of importing package:angular_components/angular_components.dart significantly, by only shipping the modules for the components you actually use, even if you use the general import.
As an example, the actual difference when only using MaterialButton:

with initReflector:

browser stats: 553 requests, 13.9MB, Finish: 2.62s
build stats:  44.6s with  3899 outputs (8285 actions)

without initReflector:

browser stats: 48 requests, 6.6MB, Finish: 448ms
build stats:  28.9s with 1838 outputs (5030 actions)

All I did to reproduce the above was actually remove this line https://github.com/dart-lang/angular/blob/master/angular_compiler/lib/src/emitter/reflector.dart#L200. So that's not even completely eliminating the entire initReflector method.

Yes, but then I'm not sure of the value (I don't really want to add features that only work in 1 place)

Allows us to start collecting metrics as a carrot for internal teams?

I was actually envisioning a global blaze flag to toggle this (we already have that ability). That way if your app uses runApp you can just use this flag. However, I don't know how much benefit you would get internally because the modules are not structured the same way, there is already no general angular components import at all.

Ah I see. That sounds reasonable.

The plan right now, if it is OK with you, is actually to have 2 flags. If you specify
--no-emit-component-factories --no-emit-injectable-factories

... we will emit a no-op void initReflector() {} (with no transitive imports). Will that do?
I could add a --no-init-reflector that turns both of these off, but not sure if worth it, especially if we want to make the default externally "--no" sooner rather than later.

The plan right now, if it is OK with you, is actually to have 2 flags. If you specify
--no-emit-component-factories --no-emit-injectable-factories

Yep should be fine, we need to make sure its supported via the BuilderOptions config which will look a little different than the blaze args but will actually go through the same codepath I believe?

... we will emit a no-op void initReflector() {} (with no transitive imports). Will that do?

Yes, this is effectively what I did when validating this approach. You can get a lot of value by just not referencing all the initReflector methods from all direct imports/exports.

I could add a --no-init-reflector that turns both of these off, but not sure if worth it, especially if we want to make the default externally "--no" sooner rather than later.

I don't have a strong opinion here.

Yep should be fine, we need to make sure its supported via the BuilderOptions config.

I believe it should "for free". Only Bazel requires a bit of additional hookup.

Ok this is now done (at MASTER), but not yet documented:
builders:
  angular:
    options:
      emit-component-factories: false
      emit-injectable-factories: false

... I'll sanity check.

OK. Landed at MASTER for real now. Here is an example output when specified:
// **************************************************************************
// Generator: Instance of 'Compiler'
// **************************************************************************

// ignore_for_file: cancel_subscriptions,constant_identifier_names,duplicate_import,non_constant_identifier_names,library_prefixes,UNUSED_IMPORT,UNUSED_SHOWN_NAME
import 'main.dart';
export 'main.dart';
import 'dart:async';
import 'dart:html';
import 'package:angular/angular.dart';
import 'package:angular_router/angular_router.dart';
import 'package:pwa/client.dart' as pwa;
import 'package:examples.hacker_news_pwa/app_component.template.dart' as app;
import 'package:examples.hacker_news_pwa/hacker_news_service.dart';
import 'main.template.dart' as ng;

import 'package:angular/src/di/injector/injector.dart' as _i1;
import 'package:angular/src/di/injector/hierarchical.dart' as _i2;
import 'package:angular_router/src/location/path_location_strategy.dart' as _i3;
import 'package:angular_router/src/location/browser_platform_location.dart' as _i4;
import 'package:angular_router/src/location/location.dart' as _i5;
import 'package:angular_router/src/router/router_impl.dart' as _i6;
import 'main.dart' as _i7;
import 'package:angular_router/src/location/platform_location.dart' as _i8;
import 'package:angular/src/core/di/opaque_token.dart' as _i9;
import 'package:angular_router/src/location/location_strategy.dart' as _i10;
import 'package:angular_router/src/router_hook.dart' as _i11;
import 'package:examples.hacker_news_pwa/hacker_news_service.dart' as _i12;
import 'package:angular_router/src/router/router.dart' as _i13;

_i1.Injector hackerNewsApp$Injector([_i1.Injector parent]) => new _Injector$hackerNewsApp._(parent);

class _Injector$hackerNewsApp extends _i2.HierarchicalInjector {
  _Injector$hackerNewsApp._([_i1.Injector parent]) : super(parent);

  dynamic _field0;

  _i3.PathLocationStrategy _field1;

  _i4.BrowserPlatformLocation _field2;

  _i5.Location _field3;

  _i6.RouterImpl _field4;

  dynamic _getdynamic$0() => _field0 ??= _i7.getNewsService();
  _i3.PathLocationStrategy _getPathLocationStrategy$1() => _field1 ??= new _i3.PathLocationStrategy(inject(_i8.PlatformLocation), injectOptional(const _i9.OpaqueToken<String>('appBaseHref'), null));
  _i4.BrowserPlatformLocation _getBrowserPlatformLocation$2() => _field2 ??= new _i4.BrowserPlatformLocation();
  _i5.Location _getLocation$3() => _field3 ??= new _i5.Location(inject(_i10.LocationStrategy));
  _i6.RouterImpl _getRouterImpl$4() => _field4 ??= new _i6.RouterImpl(inject(_i5.Location), injectOptional(_i11.RouterHook, null));
  _i1.Injector _getInjector$5() => this;
  @override
  Object injectFromSelfOptional(Object token, [Object orElse = _i1.throwIfNotFound]) {
    if (identical(token, _i12.HackerNewsService)) {
      return _getdynamic$0();
    }
    if (identical(token, _i10.LocationStrategy)) {
      return _getPathLocationStrategy$1();
    }
    if (identical(token, _i8.PlatformLocation)) {
      return _getBrowserPlatformLocation$2();
    }
    if (identical(token, _i5.Location)) {
      return _getLocation$3();
    }
    if (identical(token, _i13.Router)) {
      return _getRouterImpl$4();
    }
    if (identical(token, _i1.Injector)) {
      return _getInjector$5();
    }
    return orElse;
  }
}

// No initReflector() linking required.
void initReflector() {}

NOTE:

initReflector() is a no-op.
There is no imports to other libraries to initReflector() them.

Marking as closed! @jakemac53

awesome, thanks @matanlurey !


Add support for github.com/yonahd/kor

https://github.com/yonahd/kor

Thank you.

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

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


Added Confirmation dialog for Logout

Added The Confirmation Dialog for the Logout
Preview: https://github.com/user-attachments/assets/c5e648b4-b36b-47ec-845b-87e13abd20e7
Checklist before requesting a review

[✅] I have performed a self-review of my code
[✅] I assure there is no similar/duplicate pull request regarding same issue

@siinghd

@devsargam


module build fails when rendering react app

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
I am trying to build a react app.

Unfortunately there is no example how to build a real js or react app. The only example loads pure html which does not demonstrate how to get a js or react app to run. So I tried on my own and have probably completely butchered it but please excuse me.
I have done:

npx create-electron-app kapla5test --template=webpack
yarn add react react-dom
added this to renderer.js:import React from 'react'
import { render } from 'react-dom'

render(
hello world
, document.getElementById('root'))

altered index.html by adding

 to:<!DOCTYPE html>

  <meta charset="UTF-8">
  <title>Hello World!</title>

💖 Hello World!

Welcome to your Electron application.

altered main.js from  mainWindow = new BrowserWindow({
    width: 800,
    height: 600
  })

tomainWindow = new BrowserWindow({
  width: 800,
  height: 600,
  webPreferences: {
    nodeIntegration: true,
  },
})

Now when I run yarn start the renderer logs:
Asset written to disk: .webpack\renderer\main_window\index.js
Asset written to disk: .webpack\renderer\main_window\index.html
Hash: b92a9214ead8c3a39e3c
Version: webpack 4.41.0
Time: 402ms
Built at: 2019-10-03 23:43:25
                 Asset       Size       Chunks             Chunk Names
main_window/index.html  285 bytes               [emitted]
  main_window/index.js    267 KiB  main_window  [emitted]  main_window
Entrypoint main_window = main_window/index.js
[0] multi ./src/renderer.js webpack-hot-middleware/client 40 bytes {main_window} [built]
[./node_modules/ansi-html/index.js] 4.16 KiB {main_window} [built]
[./node_modules/html-entities/index.js] 231 bytes {main_window} [built]
[./node_modules/html-entities/lib/html4-entities.js] 6.43 KiB {main_window} [built]
[./node_modules/html-entities/lib/html5-entities.js] 47.8 KiB {main_window} [built]
[./node_modules/html-entities/lib/xml-entities.js] 2.92 KiB {main_window} [built]
[./node_modules/webpack-hot-middleware/client-overlay.js] (webpack)-hot-middleware/client-overlay.js 2.17 KiB {main_window} [built]
[./node_modules/webpack-hot-middleware/client.js] (webpack)-hot-middleware/client.js 7.68 KiB {main_window} [built]
[./node_modules/webpack-hot-middleware/node_modules/ansi-regex/index.js] (webpack)-hot-middleware/node_modules/ansi-regex/index.js 135 bytes {main_window} [built]
[./node_modules/webpack-hot-middleware/node_modules/strip-ansi/index.js] (webpack)-hot-middleware/node_modules/strip-ansi/index.js 161 bytes {main_window} [built]
[./node_modules/webpack-hot-middleware/process-update.js] (webpack)-hot-middleware/process-update.js 4.35 KiB {main_window} [built]
[./node_modules/webpack/buildin/module.js] (webpack)/buildin/module.js 497 bytes {main_window} [built]
[./src/renderer.js] 2.65 KiB {main_window} [built] [failed] [1 error]

ERROR in ./src/renderer.js
Module build failed (from ./node_modules/@marshallofsound/webpack-asset-relocator-loader/dist/index.js):
SyntaxError: Unexpected token (31:7)
    at Object.module.exports.pp$4.raise (C:\Users\alexa\kapla5test\node_modules\@marshallofsound\webpack-asset-relocator-loader\dist\index.js:20834:13)
    at Object.module.exports.pp.unexpected (C:\Users\alexa\kapla5test\node_modules\@marshallofsound\webpack-asset-relocator-loader\dist\index.js:18680:8)
    at Object.module.exports.pp$3.parseExprAtom (C:\Users\alexa\kapla5test\node_modules\@marshallofsound\webpack-asset-relocator-loader\dist\index.js:20282:10)
    at Object.parseExprAtom (C:\Users\alexa\kapla5test\node_modules\@marshallofsound\webpack-asset-relocator-loader\dist\index.js:4551:117)
    at Object.parseExprAtom (C:\Users\alexa\kapla5test\node_modules\@marshallofsound\webpack-asset-relocator-loader\dist\index.js:42293:75)
    at Object.parseExprAtom (C:\Users\alexa\kapla5test\node_modules\@marshallofsound\webpack-asset-relocator-loader\dist\index.js:35894:26)
    at Object.parseExprAtom (C:\Users\alexa\kapla5test\node_modules\@marshallofsound\webpack-asset-relocator-loader\dist\index.js:15975:26)
    at Object.parseExprAtom (C:\Users\alexa\kapla5test\node_modules\@marshallofsound\webpack-asset-relocator-loader\dist\index.js:380:26)
    at Object.module.exports.pp$3.parseExprSubscripts (C:\Users\alexa\kapla5test\node_modules\@marshallofsound\webpack-asset-relocator-loader\dist\index.js:20116:19)
    at Object.module.exports.pp$3.parseMaybeUnary (C:\Users\alexa\kapla5test\node_modules\@marshallofsound\webpack-asset-relocator-loader\dist\index.js:20093:17)
    at Object.parseMaybeUnary (C:\Users\alexa\kapla5test\node_modules\@marshallofsound\webpack-asset-relocator-loader\dist\index.js:35875:29)
    at Object.parseMaybeUnary (C:\Users\alexa\kapla5test\node_modules\@marshallofsound\webpack-asset-relocator-loader\dist\index.js:15955:29)
    at Object.parseMaybeUnary (C:\Users\alexa\kapla5test\node_modules\@marshallofsound\webpack-asset-relocator-loader\dist\index.js:368:29)
    at Object.module.exports.pp$3.parseExprOps (C:\Users\alexa\kapla5test\node_modules\@marshallofsound\webpack-asset-relocator-loader\dist\index.js:20035:19)
    at Object.module.exports.pp$3.parseMaybeConditional (C:\Users\alexa\kapla5test\node_modules\@marshallofsound\webpack-asset-relocator-loader\dist\index.js:20018:19)
    at Object.module.exports.pp$3.parseMaybeAssign (C:\Users\alexa\kapla5test\node_modules\@marshallofsound\webpack-asset-relocator-loader\dist\index.js:19993:19)
 @ multi ./src/renderer.js webpack-hot-middleware/client main_window[0]
Child html-webpack-plugin for "main_window\index.html":
                     Asset     Size  Chunks  Chunk Names
    main_window/index.html  534 KiB       0
    Entrypoint undefined = main_window/index.html
    [./node_modules/html-webpack-plugin/lib/loader.js!./src/index.html] 428 bytes {0} [built]
    [./node_modules/lodash/lodash.js] 528 KiB {0} [built]
    [./node_modules/webpack/buildin/module.js] (webpack)/buildin/module.js 497 bytes {0} [built]
Failed to compile.

What am I doing wrong?

Console output when you run electron-forge with the environment variable DEBUG=electron-forge:*. (Instructions on how to do so here). Please include the stack trace if one exists.
Sorry, did not understand and manage this
Please provide either a failing minimal testcase (with a link to the code) or detailed steps to
reproduce your problem. Using electron-forge init is a good starting point, if that is not the
source of your problem.

clone https://github.com/barbalex/kapla5test
cd into it
run yarn start
watch console in electron

I just tried without
webPreferences: {
  nodeIntegration: true,
}

and the result es exact same.

O.k., got a basic react app working by following https://github.com/electron-userland/electron-forge/issues/1164#issuecomment-532621940
But please provide an example. I do not feel capable of building a pull request for it myself unfortunately.


GamepadHome button

Is there a plan to support also GamepadHome button?

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

ID: 42619a31-7175-4a29-98a6-7f6703b8c608
Version Independent ID: 5a517293-5bd4-5b9f-7fd3-8938d402d5fb
Content: Device Portal remote input API reference - UWP app developer
Content Source: windows-apps-src/xbox-apps/uwp-remoteinput-api.md
GitHub Login: @WilliamsJason

It works the same way.
It is just identified as "LeftWindows" virtual key on KeyDown/Up events.
Real "GamepadHome" cannot catch at all.


Understanding Case Sensitivity in Variables- properCamelCase

Describe your problem and how to reproduce it:
In the challenge it asks to fix the variable declarations and assignments so their names use camelCase. the second line of the challenge is "properCamelCase" and though it looks correct to me it is still coming up as an error and not accepting the answer. Am I missing something or is this an issue with the challenge?
Add a Link to the page with the problem:
http://precourse.devmountain.com/challenges/understanding-case-sensitivity-in-variables#?solution=
%2F%2F Declarations
var StUdLyCapVaR%3B
var properCamelCase%3B
var TitleCaseOver%3B

%2F%2F Assignments
STUDLYCAPVAR %3D 10%3B
PRoperCAmelCAse %3D "A String"%3B
tITLEcASEoVER %3D 9000%3B

%2F%2F Declarations
var studlyCapVar%3B
var properCamelCase%3B
var titleCaseOver%3B

%2F%2F Assignments
studlyCapVar %3D 10%3B
properCamelCase %3D "A String"%3B
titleCaseOver %3D 9000%3B
If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box):

Sorry you are having trouble, but your question is not related to Free Code Camp and is not an issue with the Free Code Camp platform, so we are closing this issue.
You should pose your question to Devmountain.
FYI - Your line 3, 8, 9, and 10 are not camelCase, which is probably the issue you need to resolve.


Typo fix: mainting -> maintaining

[x] This is a small change
[ ] This change has been discussed in issue #<?> and the solution has been agreed upon with maintainers.

Description:
Just a typo fix!

Oops
Thank you!

Oops
Thank you!


SAK-29740 Javadoc updates. Add new method for getGradebookGradeMappin…

…gs to make it more usable to third parties

Merging this straight in as it's a WIP.


pyzstd_pep517: name config_settings argument correctly

Ref: https://peps.python.org/pep-0517/#get-requires-for-build-wheel

Hello @gotmax23 and thank you for your patch!
I understand that the argument you changed is a positional or keyword parameter (e.g. inspect.Parameter.POSITIONAL_OR_KEYWORD), so having the wrong name breaks any build system that uses the parameter as a keyword parameter.
Could you tell a bit more about the context in which you are having an issue with this? For example, if your build system fails to build pyzstd as a result, please say which build system you are using and how you are calling it.
This will be helpful not only to reproduce, but also to give a proper importance level to this fix.
Thank you!

Hello @gotmax23 and thank you for your patch!

Sure!

Could you tell a bit more about the context in which you are having an issue with this? For example, if your build system fails to build pyzstd as a result, please say which build system you are using and how you are calling it.

I am using https://src.fedoraproject.org/rpms/pyproject-rpm-macros which is the build frontend tool we use for building python project RPMs for Fedora Linux (and Red Hat Enterprise Linux and CentOS and others). I am working on importing pyzstd into the official Fedora repositories.

Thank you for the explanations!
This will be shipped in next release (current target is by the end of May).

Fixed in version 0.16.0 that has just been released :rocket:


Fix some notes for Azure users

As is said in the docs (https://docs.microsoft.com/en-us/azure/aks/static-ip#create-static-ip-address), it must be the cluster node's resource group, not the cluster's resource group.

@Rajakavitha1 It's done.

/lgtm

/approve


Could you provide the Scannet training pairs?

Hi there,
Could you please help provide the training pairs for Scannet (maybe just a txt file)?  It seems generating the pairs need quite long time, that would be really helpful if you already have that. Thanks a lot！

Hi, the ScanNet metadata (~21G) is on the server of the company. I think we can handle this after the labour day holiday. And I personally recommend you using the MegaDepth dataset, which offers better depth quality and requires much less training time.
Just notice: we plan to release the whole training code/data around 2021-6-10.

Hi zehong,
Thanks for the quick reply. We also use megadepth, but it would be better
to use scannet as well for comparison with previous work. Really appreciate
it if you could share the pairs of scannet data! Happy holidays! Thank you!
On Sun, May 2, 2021 at 10:13 PM Zehong @.***> wrote:

Hi, the ScanNet metadata (~21G) is on the server of the company. I think
we can handle this after the labour day holiday. And I personally recommend
you using the MegaDepth dataset, which offers better depth quality and
requires much less training time.
Just notice: we plan to release the whole training code/data around
2021-6-10.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zju3dv/LoFTR/issues/16#issuecomment-831023541, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ADAOCFHJON4ARUUVRBCFJNLTLYWHLANCNFSM44ADPXNQ
.

We've added the training pair info on ScanNet to the README. Feel free to reopen this issue if you met any problems.


Question

Must you have Solar from Zonneplan (the one unit) to get the prices of the Connect module?

No, only the Zonneplan connect P1 dongle should also work


fix: Resolve SQL error during Plex collection recreation

Previously, an SQL error could occur when recreating a collection in Plex. This commit addresses the issue, ensuring smooth collection recreation without encountering SQL errors.

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


Multiple Regex examples

I found this repo through here: https://stackoverflow.com/questions/192957/efficiently-querying-one-string-against-multiple-regexes
I am specifically looking for code where I can define an arbitrary number of regexs (with captures!) and match against a single string with one pass over the string. Even though I'm working in C++, this library looks promising and I would be interested in porting it if it serves my needs.
I am curious if you have any examples where you create an arbitrary number of regexs and match them against a string and process the results? Nothing in the test folder jumps out as that but I'm still looking.

StringSearcherTest shows how to use SearchAndReplaceBuilder to search and replace multiple patterns in a string simultaneously.  If you don't to do replacements, you can use a StringSearcher.  SearchAndReplaceBuilder uses one of those so you can look at that code to see how it works.
There are no internal captures in these kinds of patterns (DFA-based rather than PCRE-type), but once you find a match you can always do more processing on it.  Finding the match is the part that needs to be fast.

There are no internal captures in these kinds of patterns (DFA-based rather than PCRE-type), but once you find a match you can always do more processing on it. Finding the match is the part that needs to be fast.

That's more or less what I was thinking. If I can narrow 10k regexs down to one and then run something like std::regex with that one... well, two passes over a string are still better than 10k.
I'm assuming this library just implements the basic operators (+ ? * ( | )), do you have any thoughts on how easily it would be to extend it to others? Namely [ ] and even ^ and $. (No backreferences!)

It supports character classes [ ].  ^ and $ are not specified in the patterns themselves, but it's quite easy to anchor searches to the beginning and/or end of the string when you call the library.
If you really have 10K regexes to match, then this kind of matcher is the way to do it, since the time required does not depend at all on the number of input expressions or their size.   Searching using std::regex and a very big union expression will not much faster than searching for the 10K regexes individually, because of the way those kinds regexes are implemented.
Porting my library to C++ is not an easy task, though!  Maybe you should try to fit your requirements into something like Flex instead: https://github.com/westes/flex

Porting my library to C++ is not an easy task, though! Maybe you should try to fit your requirements into something like Flex instead: https://github.com/westes/flex

As I understand the goal in general is to take the regexs, convert them into their NFA form, then into DFAs. Once I have that, the time it takes to search more regexs grows linearly.
Perhaps this is not an easy task but not an impossible task! :) Actually, it looks your library does some things I don't need, such as find-and-replace when really all I need is find-and-capture. I will probably use this as more of a guide.


Existing work item retrieval ignores filtering on target project

Note: This item is similar to issue #47 "Querying for already existing work items seems to ignore project".
To repro:

We are migrating from on-premise TFS to Azure DevOps.
Set the post-move-tags the config file to empty and set the skip-existing param to false
Create a test (i.e. Test) Azure DevOps project
Create a query to use in the on-premise TFS project that migrates 1/3 the work items
Run the migration tool to migrate the items into the Test Azure project (notice the # of existing items display as 0 in the target project during the migration)
Create a final (i.e. Final) Azure DevOps project
Update the query in TFS to migrate all the items
Run the migration tool again on the Final Azure project (notice how the # of existing items display as the 1/3 amount in the target project during the migration)

Expected behavior:
The migration tool should read any existing migrated work items from the target project only (as opposed to any work items in the target Azure DevOps organization)
Actual behavior:
The migration tool appears to be reading work items from any project (e.g. the Test) project rather than the target project (e.g. Final)

When this tool was originally written, work items only had account scoped URLs.  We now have project scoped URLs, so I coud consider that enhancement.  It would have to be opt in, since it would break anything that was previously migrated using the collection scoped URLs.

Closing as a dupe of #47


Rich text editor | Update dependency on prosemirror-markdown

Pull Request
🤨 Rationale

Fixes Bug 2518928: Rich text editor | Bold italics not updating as expected
In markdown-serializer, if the the markdown string contains leading or trailing whitespaces within marks, it will not parsed to an expected rich text content. For example, entering "Bold Italics bold" into the editor, the actual markdown serializer output is **Bold *italics *bold** which renders as below in viewer.

Expected output for the above example should be **Bold *italics* bold**
👩💻 Implementation

Bumped the prosemirror-markdown version from 1.11.0 to 1.11.2 which fixes expelEnclosingWhitespace property to expel any leading or trailing whitespaces within a mark to outer nodes.
🧪 Testing

Manually tested by getting markdown string for different bold and italics mixed cases and loading it in the viewer.
Add test cases in the markdown-serializer.ts for different scenarios with the example mentioned above and a few other test cases that cause the leading and trailing whitespace. Please note that the input HTML string given to the tests is the same as how the Tiptap renders bold and italics cases. For example, strong has a higher priority than italics, so the HTML will be like

Italics between bold (Bold italics bold):
    Bold
    italics
    bold

Bold between italics (Italics bold italics):Italics

     bold

italics

✅ Checklist

[x] I have updated the project documentation to reflect my changes or determined no changes are needed.

You don't need to wait for @m-akinc's review for a straightforward dependency upgrade. We need additional discussion for tests separate from this PR.


Add students PATCH tests

There are some improvements made to tests that are unrelated to PATCH endpoint.
Resolves #131

There are some improvements made to tests that are unrelated to PATCH endpoint. Resolves #131

Doesn't it resolve #133 ?


wdio-cucumber-framework : how can i Multiple scenarios from single feature file ?

how i can run multiple scenarios from single feature files.. requirement is after successful scenario execution browser should closed automatically and for next scenarios it should open again and execute

how i can run multiple scenarios from single feature files

I think this is not possible. There can be only one Scenario per feature file. Please create multiple feature files which then will be run in parallel. If you have further questions join our  . Thanks!

Thanks @christian-bromann for your quick help..  is there any way to mark scenario with tagnames and execute it which i want..
eg.
there are 4 scenarios with tag names @one, @two, @three, @four..  if i want to execute scenarios with tag names @one and @three..  how can i achieve it?
I have tried using --cucumberOpts.tags="@one,@three"  but it is executing all the scenarios from feature file.
thanks

how can i achieve it?

scenarios in feature files are basically spec files which you can define when running the wdio command, e.g.
wdio --spec ./features/some.feature

@christian-bromann  Thanks .   i have single  feature file which has following four scenarios.. in normal wedriver-cucumber we can achieve these specifiying tagname --cucumberOpts.tags="@one,@three"
feature file:
-scenario one
-scenario two
-scenario three
-scenario four
if i want to run only scenario two and three .. is it possible here?

Sure:
$ wdio --spec ./features/scenario1.feature,./features/scenario2.feature

Thanks @christian-bromann for your help.
but i observed that empty browser  opens for each feature file with no tests targeted??  is it bug or do i miss something??

It is a known bug


Add new Rails/InverseOf cop

This cop looks for has_(one|many) and belongs_to associations where ActiveRecord can't automatically determine the inverse association because of a scope or the options used. This can result in unnecessary queries in some circumstances. :inverse_of must be manually specified for associations to work in both ways, or set to false to opt-out.
At Shopify we have tests that track SQL queries of critical paths, and fixing these associations resulted in less database calls.

Before submitting the PR make sure the following are checked:

[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Used the same coding conventions as the rest of the project.
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x] All tests(rake spec) are passing.
[x] The new code doesn't generate RuboCop offenses that are checked by rake internal_investigation.
[x] The PR relates to only one subject with a clear title
and description in grammatically correct, complete sentences.
[x] Updated cop documentation with rake generate_cops_documentation (required only when you've added a new cop or changed the configuration/documentation of an existing cop).

At Shopify we have tests that track SQL queries of critical paths, and fixing these associations resulted in less database calls.

I'd like to understand the problem a bit more. Would you kindly show an example of an avoided database call?

I'd like to understand the problem a bit more.

These tests are there to ensure that developers do not accidentally add database queries, during our code review process any added SQL queries will have to be justified. This 2013 talk shows how the initial round of query optimization was done on paper by analyzing printed debug logs 😄

Would you kindly show an example of an avoided database call?

I initially started thinking about this PR after seeing the impact on Shopify's tests working on a feature that was adding a handful of queries in a case where we expected only one. After some investigation we fixed a misconfigured polymorphic association between classes that deal with orders and their various financial transactions. Now that the that the associations could be traversed in-memory and with the new feature in place, we saw a net decrease of 3 and 5 model loads in two test cases. After that we found a few more instances, but these aren't covered by these query tests so I don't know the impact.

@mikegee: Check this blog post. 🙂

@Drenmi thanks! That has a clear example.

@bdewater Great first contribution! 👍
P.S. You might also want to add an entry about this to the community Rails style guide https://github.com/bbatsov/rails-style-guide

@bdewater can you clarify whether this cop is still accurate based on your changes to the rails docs? It would seem that inverse_of should only be required in the case that there's a scope, through, or foreign_key specified, but this cop seemingly barks any time I have any options specified on a has_many association.

@bdewater upon further inspection, it seems to be barking because of my use of class_name which I don't see listed in INVALID_AUTOMATIC_INVERSE_OPTIONS.
There is, however, a spec for this cop that was added by @wata727 that indicates that it should fail on class_name. Not sure why that was added as it's basically a footnote in that commit.


Addon installation error

PS C:\Users\aleks> eso-addons-x86_64-pc-windows-msvc.exe add https://www.esoui.com/downloads/info3034-HarvestMap-Data.html
app error: cannot read addon HarvestMapData: missing addon metadata file

I believe that is just the data downloader scripts for the main HarvestMap addon. It doesn't have any actual addon information. I had to manually install this one, then run the DownloadNewData script.


fix(apps/prod/tekton/configs/tasks): fix tiup command

tiup -v depends on mirror setting.
Signed-off-by: wuhuizuo<EMAIL_ADDRESS>

/approve


Actually update epoll events if needed when unregistering

_dispatch_epoll_update() was being called without dmn->dmn_events being
updated beforehand.
Signed-off-by: Pierre Habouzit<EMAIL_ADDRESS>

@swift-ci please test


Export CSV for non-latin characters (mainly arabic)

Description

Steps to Reproduce

initialize apexchart with data having arabic characters
export to csv

Expected Behavior
all characters should show as shown in the website
Actual Behavior
characters are trash when opened with any excel version
Screenshots

Reproduction Link
Solution
Add BOM before the content

No reproduction link provided


Add files via upload to submit a new school

@MysticalMike60t The first verification stage is complete: the official domain for  Ella T. Grasso Technical Highschool is grasso.cttech.org, to the best of my knowledge. This is just an informational note. The pull request is still under review. The review may take some more time. I greatly appreciate your patience. Here is the proof of domain ownership: https://grasso.cttech.org/about/staff-directory/

@MysticalMike60t Thank you for your patience while waiting for a review and processing your request. Pull request merged.


1.9 Chunks not loading right

Hi,
on 1.9 client some chunks aren't loading right, when I move around the map, chunks fill in and out.
1.8 clients work fine.
This is basically with no plugins enabled. Some parts of map are completely fine, so weird.
http://imgur.com/y4NhnYe

Duplicate of #38 please close

As above


Add setup Nushell full release support

After this PR: https://github.com/nushell/nushell/pull/10457 been merged

features | Available choice: default or full, and the full features will include the commands from extra and dataframe

full features was support in v3.8


Fix some problems with Docker when HTTP proxy vars are empty

i'll leave this here as well, since it's more persistent.
the problem is quoting in the systemd drop-in unit and not a docker issue as i thought.
so all is needed is for the final provisioning of the proxy.conf to look like this:
[Service]
Environment="HTTP_PROXY="
Environment="HTTPS_PROXY="
Environment="NO_PROXY="

instead of what it currently looks like
9293820ab0ca4233ad1a5648aa8dfb48:/etc/systemd/system/docker.service.d # cat proxy.conf
[Service]
Environment=HTTP_PROXY=""
Environment=HTTPS_PROXY=""
Environment=NO_PROXY=""

I think @PI-Victor is a better approach by just fixing quoting... my 2 cents.

I think it should be fixed now: it seems that removing que yaml_encode and some " did it...

@PI-Victor Yeah, tests have been failing with those errors since last week... :-(


[Spaceship] Platform and Multiple App ID Support

This is the Spaceship portion of the following issues and pull requests.
Spaceship portion of #3693 and #3600. I merged the two because #3693 improves upon #3600 with constants instead of strings.
Also fixes:
fastlane/spaceship#229
fastlane/spaceship#238
#2027

Build failure is a class has too many lines. Does that need to be changed or is that ok? Not seeing off the top of my head a good way to reduce the class lines.

@mfurtak Made all the recommended changes and squashed them.

@bassrock
We had an issue with CI earlier, you’ll need to bring in a fix so the tests will pass on CI, please run:
git cherry-pick f6a7d2100b639c27ecd70c51f59f3542b9dc5cea

and push again to update this request.

@i2amsam @mfurtak rebased to master

If you wrap PortalClient in:
# rubocop:disable Metrics/ClassLength
class PortalClient < Spaceship::Client
  # ...
end
# rubocop:enable Metrics/ClassLength

we can silence that error for now.

@mfurtak and @KrauseFx Made suggested changes. Ready for another review :+1:

I added some comments, however please don't update the PR yet, since we still discuss some things

Got it. Was actually just going to start :) good thing coworkers pulled me away for lunch then.

Is the current status of this now a rebuild to a request builder function? Can I be of any assistance with that?

As I can see this PR is added TVos support. Really must have feature. Please let me know, if I can help with some tasks to get it done!

Yo guys, this PR is very important for us as well, let me if I could help somehow.

Hey @bassrock and everyone else! So we have given these PRs a lot of consideration and want to apologize for leading anyone on that these changes could be merged. Unfortunately, as it is right now, these changes are a bit too intrusive to Spaceship (where we very much bank on its reliablity) and while we definitely would like to get support for tvOS and any *OS that Apple is bound to introduce as time passes, we would really like to plan out as a team, the best possible way to achieve this while keeping Spaceship backwards compatible and standing up.

@ohwutup Is there an open issue where the community can help discuss this and the best way to do it? I think it is highly important to get support for tvOS and the other platforms into Spaceship so the other tools can start making use of them.

@ohwutup would very much like this feature as well


Last Will (LWT) authentication error.

Environment

VerneMQ Version: 1.6.2
OS: Official Docker image.
VerneMQ configuration: Disallow anonymous and activate diversity and postgres plugin.

Expected behavior
When I connect a new client with clientId and username which previously has connected with last will testament, and not clossed connection, the last will payload is posted in the last will topic without any authentication log warning.
Actual behaviour
When I do which I explain above, I get the following errors:
[error] can't auth publish [<<"xxx">>,{[],<<"xxx">>},0,[<<"xxx">>,<<"x">>,<<"xxx">>],<<"xxx">>,false] due to not_authorized
[warning] can't authenticate last will for client {[],<<"xxx">>} due to not_allowed.
The postgres ACL and authentication is working as expected, the client has permission to publish in the last will topic, even the last will message is published as expected, but the warning is annoyoing.
Maybe it is a simple log bug or maybe I missed some configuration, but If you could check it, I will be very grateful.
Thank you :+1:

Hi @selarep, thanks for reporting - we'll take a look at this!

I was thinking a bit about this and looked into the code. The last will is checked when the client connects, so I would think what you see is that the last will is send for the existing connection but the last will for the new connection is rejected (did the ACLs change?).
Hope that makes sense.

Thanks for your answer. What you say makes sense, but ACLs remain unchanged. Even I tried with a client with pubsub wildcard (#), and the same message appears.
Maybe is a problem due to accept an entering connection, having one pending last will of previous connection?
The way I reproduced the issue is with mosquitto_sub. I generate a connection with mosquitto_sub (with proper last will info), and abort client with Ctrl+Z. Then running the same mosquitto_sub command with same username and clientId I get the error.
If I wait for last will to be published (connection closed due to timeout), and then create the new connection, there is no problem.

Which plugins do you use? vmq_passwd and vmq_acl?

My mosquitto_sub command is:
mosquitto_sub -h localhost -u MYUSERNAME -i MYCLIENTID -P MYPASSWORD -t clima1/1 -k 10 -q 0 --will-topic clima1/1/status --will-qos 0 --will-payload "offline" -d
My publish ACL is:
[{
"pattern": "clima1/1/status"
}].
Maybe it is a plugin related issue?

The vmq_diversity plugin caches stuff - could you unload/load the plugin or restart vernemq to make sure it's not some kind of strange caching issue, though I think it's unlikely.... Anyway it could be interesting to see what the output of vmq-admin trace client client-id=<CLIENTID> is when reproducing it as well as what is written to the log without obscuring client-id/topics if possible.
Are you sure you're not picking up the wrong entry in the postgresql db for some reason? The key for each query is username, password and clientid - so if any of those change then you might not fetch the data you expect.

Firsf of all, I have configured an environment with vmq_acl and vmq_password, and the issue is not reproducible. So the issue seems to be related to postgres or diversity plugin.
I am working with docker containers, so I have erased docker caches and rebuild vernemq container. The problem persists.
Dump of the output of vmq-admin trace:
No sessions found for client "agromote-1"
New session with PID <7616.511.0> found for client "agromote-1"
RPC to<EMAIL_ADDRESS>failed: {'EXIT',
                                     {badarg,
                                      [{io,format,
                                        [<0.52.0>,
                                         "~p MQTT RECV: CID: \"~s\" CONNECT(c: ~s, v: ~p, u: ~s, p: ~s, cs: ~p, ka: ~p)~n    with LWT(wr: ~p, wq: ~p, wt: ~s) with payload:~n    ~s~n",
                                         [<7616.511.0>,<<"agromote-1">>,
                                          <<"agromote-1">>,3,<<"agromote-1">>,
                                          <<"password">>,1,10,0,0,
                                          <<"clima1/1/status">>,<<"offline">>,
                                          []]],
                                        []},
                                       {vmq_tracer,handle_call,3,
                                        [{file,
                                          "/vernemq-build/_build/default/lib/vmq_server/src/vmq_tracer.erl"},
                                         {line,174}]},
                                       {gen_server,try_handle_call,4,
                                        [{file,"gen_server.erl"},{line,636}]},
                                       {gen_server,handle_msg,6,
                                        [{file,"gen_server.erl"},{line,665}]},
                                       {proc_lib,init_p_do_apply,3,
                                        [{file,"proc_lib.erl"},{line,247}]}]}}

Dump of log when reproducing while running vmq-admin trace:
vernemq_1   | 14:58:30.270 [error] gen_server vmq_tracer terminated with reason: bad argument in call to io:format(<17575.52.0>, "~p MQTT RECV: CID: \"~s\" CONNECT(c: ~s, v: ~p, u: ~s, p: ~s, cs: ~p, ka: ~p)~n    with LWT(wr: ~...", [<0.511.0>,<<"agromote-1">>,<<"agromote-1">>,3,<<"agromote-1">>,<<"password">>,1,10,0,0,<<"clima1/...">>,...]) in vmq_tracer:handle_call/3 line 174
vernemq_1   | 14:58:30.270 [error] CRASH REPORT Process vmq_tracer with 2 neighbours crashed with reason: bad argument in call to io:format(<17575.52.0>, "~p MQTT RECV: CID: \"~s\" CONNECT(c: ~s, v: ~p, u: ~s, p: ~s, cs: ~p, ka: ~p)~n    with LWT(wr: ~...", [<0.511.0>,<<"agromote-1">>,<<"agromote-1">>,3,<<"agromote-1">>,<<"password">>,1,10,0,0,<<"clima1/...">>,...]) in vmq_tracer:handle_call/3 line 174
vernemq_1   | 14:58:30.270 [error] CRASH REPORT Process <0.511.0> with 0 neighbours exited with reason: bad argument incall to io:format(<17575.52.0>, "~p MQTT RECV: CID: \"~s\" CONNECT(c: ~s, v: ~p, u: ~s, p: ~s, cs: ~p, ka: ~p)~n    with LWT(wr: ~...", [<0.511.0>,<<"agromote-1">>,<<"agromote-1">>,3,<<"agromote-1">>,<<"password">>,1,10,0,0,<<"clima1/...">>,...]) in vmq_tracer:handle_call/3 line 174 in gen_server:call/2 line 206
vernemq_1   | 14:58:30.271 [error] Ranch listener {{172,20,0,3},1883} terminated with reason: bad argument in call to io:format(<17575.52.0>, "~p MQTT RECV: CID: \"~s\" CONNECT(c: ~s, v: ~p, u: ~s, p: ~s, cs: ~p, ka: ~p)~n    with LWT(wr: ~...", [<0.511.0>,<<"agromote-1">>,<<"agromote-1">>,3,<<"agromote-1">>,<<"password">>,1,10,0,0,<<"clima1/...">>,...]) invmq_tracer:handle_call/3 line 174
vernemq_1   | 14:58:36.190 [error] can't auth publish [<<"agromote-1">>,{[],<<"agromote-1">>},0,[<<"clima1">>,<<"1">>,<<"status">>],<<"offline">>,false] due to not_authorized
vernemq_1   | 14:58:36.190 [warning] can't authenticate last will
vernemq_1   |                           for client {[],<<"agromote-1">>} due to not_allowed

I'm completely sure about the entry that I'm picking from pgsql because I have reduced the scenario to a bare minimum in which i have only one acl client entry.
I hope that the info above helps to find the issue.

ok - thanks for the additional info. Is this setup something I could run locally to test? Otherwise I'd have to try to reproduce it by setting up postgres etc which would take a while.
Btw - seems like you found a bug in the tracer - seems there's a problem formatting the lwt.

@dergraf to reproduce this: a client is already connected and creates a second connection with the same client-id and lwt. The second LWT is then rejected due to authorization issues (even thought it worked the first time). My hypothesis is this is a racy interaction between the teardown of the old client (which will get kicked out) and the removal of the acl rules and the new client. Likely the new client will cause authentication rules to be fetched and overwrite the old ones and in the meantime the old client is kicked out and the authentication rules are deleted from the cache and then the new client tries to authenticate the LWT and fails?


Use peerDependencies instead of dependencies

Requiring react-tools as dependencies, means the transpilation is only
possible with the version on reactify package.json. By moving to
peerDependencies, when requiring a different version of React the
transpilation should just work. Of course this might eventually break but
different projects will want to use different versions of the trnaspiler
anyway, so I am suggesting to addopt peerDependencies.
The main reason I am creating this pull-request is that I am using new
features on React 0.13-rc1 and I need the transpilation to be in the same
version I am requiring from React.
I hope you like the idea, though in the long run, if react-tools introduce API
changes, it might mean supporting more then one version at a time.

+1 to this. I ran into this problem and so will anyone trying to use the latest React

I don't think peerDependencies is the way to go as npm now warns that peerDependencies won't be installed automatically in future npm version.


Testing To Do list: part 2

Use jest framework for testing.
Create a test file(s) ([..].test.js) for a file(s) containing the following functions:
a function for editing the task description.
a function for updating an item's 'completed' status.
the "Clear all completed" function.
Use the mock storage object you have created in Part 1 of this project to mock the localStorage updates.
Mock the HTML elements to test DOM manipulation functions.
Make sure you group your tests using the describe() method.

Project Status: INVALIDATED :red_circle:
Hi @BezzB ,
While you made a great effort in this project, I can't go ahead and review your code.

Invalid Code Review Request

This is because you have submitted a project, that is a pair-programming activity and as a result, needs to have commits from both you and your partner or partners just as the first reviewer mentioned. :wink:

If for some reason you had to work on the project alone, then please add a screenshot of the email you received from student success stating that you can work alone so the next reviewer can proceed to review your project :wink:

Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me @NahnahAJ in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.


CrosswordScraper not working...

...for the Seattle Times.
https://www.seattletimes.com/games-nytimes-crossword/

Looks like a minor URL change. Should be fixed in the next release.
As a workaround in the mean time, the old URL still appears to work: https://nytsyn.pzzl.com/cwd/


add count limit offset

Pull Request Test Coverage Report for Build 19

10 of 10 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 16:
0.0%

Covered Lines:
208

Relevant Lines:
208

💛  - Coveralls


The amp-testdrive email address bounces

[Enter feedback here]
The amp-testdrive email address bounces.
Would it be possible to write dedicated documentation on preparing a VM for capturing as an image for publishing on Azure Marketplace? Similar to this for AWS:
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/building-shared-amis.html

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

ID: 7947496e-c042-15bd-d6c1-ee2738a91119
Version Independent ID: 98730184-8c1e-9ece-09e7-31abdd60ccd2
Content: Publishing guide for virtual machine offers on Azure Marketplace
Content Source: articles/marketplace/marketplace-virtual-machines.md
Service: marketplace
Sub-service: partnercenter-marketplace-publisher
GitHub Login: @iqshahmicrosoft
Microsoft Alias: iqshah

@cfd-direct Thank you for reaching out and sharing your feedback. Assigning this issue to our document author @iqshahmicrosoft to further evaluate the feedback and get back to you.

@cfd-direct We have a documentation on preparing VM Image for publishing to Azure Marketplace. https://docs.microsoft.com/en-us/azure/marketplace/partner-center-portal/create-azure-vm-technical-asset
Does this help?

That document is massively convoluted.
For example, there is a whole section on connecting to the VM. Why? That is documented elsewhere and must be basic knowledge for anyone thinking about creating a VM marketplace product.
For the Linux VM, it describes an SSH login with PuTTY, without even mentioning that it is a Windows-only application.
Are you assuming everyone using Azure is running Windows?
The documentation relies on recognising the section structure from the size of the headings, rather than heading numbers. That is just confusing.
After wading through numerous lines of irrelevant information, you finally reach the important bit about preparing the VM:
https://docs.microsoft.com/en-us/azure/marketplace/partner-center-portal/create-azure-vm-technical-asset#linux-1
The information is far too brief, e.g. it tells the user to run:
sudo waagent -deprovision+user
If you look at this document...
https://docs.microsoft.com/en-us/azure/virtual-machines/linux/capture-image#step-1-deprovision-the-vm
it discusses the settings. In my circumstance, I don't think I should include "+user", but the information is not clear. It is using MS-speak, in the context of Linux.
A lot of related MS documentation suffers the same problems. For example, on creating a VM Offer
https://docs.microsoft.com/en-us/azure/marketplace/partner-center-portal/azure-vm-create-offer
why start with "The benefits of publishing to Azure Marketplace". Presumably the reader understands this already, otherwise why would they be looking into how to create a VM offer. It is not relevant at all.
Less is more.

@cfd-direct Thank you for your feedback on these documents and for reporting the invalid email address, which we'll remove as soon as possible.
You brought up good points regarding our virtual machine documentation. We plan to revisit those pages soon. Your feedback is very insightful and will help us improve our documentation.
Thanks again for your contribution!
#please-close


python310Packages.python-crfsuite: 0.9.7 -> 0.9.8

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.

WARNING: Package has meta.broken=true; Please manually test this package update and remove the broken attribute.

meta.description for python310Packages.python-crfsuite is: "Python binding for CRFsuite"
meta.homepage for python310Packages.python-crfsuite is: "https://github.com/scrapinghub/python-crfsuite"
meta.changelog for python310Packages.python-crfsuite is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.9.8 with grep in /nix/store/h2z38yp5k38ir6rwld42c1yb5vkwg4mx-python3.10-python-crfsuite-0.9.8

found 0.9.8 in filename of file in /nix/store/h2z38yp5k38ir6rwld42c1yb5vkwg4mx-python3.10-python-crfsuite-0.9.8

Rebuild report (if merged into master) (click to expand)

11 total rebuild path(s)

6 package rebuild(s)

6 x86_64-linux rebuild(s)
5 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
gruut
python310Packages.gruut
python310Packages.python-crfsuite
python39Packages.gruut
python39Packages.python-crfsuite
tts

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/h2z38yp5k38ir6rwld42c1yb5vkwg4mx-python3.10-python-crfsuite-0.9.8 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.python-crfsuite https://github.com/r-ryantm/nixpkgs/archive/782aefaf5bddb968f6517933397c5491b2c78c0f.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/h2z38yp5k38ir6rwld42c1yb5vkwg4mx-python3.10-python-crfsuite-0.9.8
ls -la /nix/store/h2z38yp5k38ir6rwld42c1yb5vkwg4mx-python3.10-python-crfsuite-0.9.8/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages marked as broken and skipped:

python310Packages.gruut
python310Packages.python-crfsuite

1 package failed to build:

tts

2 packages built:

gruut (python39Packages.gruut)
python39Packages.python-crfsuite

Maintainer pings
cc @mweinelt @mic92 for testing.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 165645 run on x86_64-linux 1

2 packages marked as broken and skipped:

python310Packages.gruut
python310Packages.python-crfsuite

2 packages built:

gruut (python39Packages.gruut)
python39Packages.python-crfsuite


Docker Synology DSM 7.X

Describe The Bug:

Theres no root access for the homebridge-ui
To Reproduce:

Install Docker on Synology (or choose xpenology + vbox)
Install Homebridge SPK file
Install your Plugin
Try to configure any PS
Expected behavior:

To work as written in the guide :D
Logs:
bash-4.4$ homebridge-playstation-login
Discovered device: {
  address: { address: 'xxx.xxx.xxx.xxx', family: 'IPv4', port: 52088, size: 156 },
  hostRequestPort: 997,
  extras: {
    statusLine: '200 Ok',
    statusCode: '200',
    statusMessage: 'Ok',
    status: 'AWAKE'
  },
  discoveryVersion: '00020020',
  systemVersion: '09030001',
  id: 'xxxxxxxxxxxxxxxxx',
  name: 'h@xPS',
  status: 'AWAKE',
  type: 'PS4'
}
Authenticate to h@xPS? (y/n) y
No credentials for h@xPS and unable to request (need root permissions).
Attempting to request root permissions now (we will relinquish them as soon as possible)...

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

Password:

And, yeah theres no account available as shown in the Syno's Description.
Plugin Config:
            "pollInterval": 5000,
            "platform": "playstation",
            "_bridge": {
                "username": "xx:xx:xx:xx:xx",
                "port": 32374

Environment:

Plugin Version: Latest
Homebridge Version:  Latest
Node.js Version:  Latest
NPM Version:  Latest
Operating System:  DSM 7.0.1-42218 Update 3

Hello; i'm not really familiar with your setup; do you have a root user available?

Hello; i'm not really familiar with your setup; do you have a root user available?

Hi
Yes, it exists 😄

@0n1cOn3 I had the same problem and I was able to fix it. So what I did:

Installed ps4-waker npm package to my MacBook
Run ps4-waker and followed the instructions so the utility created a file ~/.ps4-waker.credentials.json
Installed playactor npm package to my MacBook
Run playactor login so it was able to pick existing creds and created it's own version in ~/.config/playactor/credentials.json
Installed playactor to Synology via Homebridge terminal
Copied credentials file from 4 to ~/.config/playactor/credentials.json on my NAS
Run playactor login on NAS (still in same HB terminal) and followed the instructions
Profit :)

@0n1cOn3 I had the same problem and I was able to fix it. So what I did:

Installed ps4-waker npm package to my MacBook

Run ps4-waker and followed the instructions so the utility created a file ~/.ps4-waker.credentials.json

Installed playactor npm package to my MacBook

Run playactor login so it was able to pick existing creds and created it's own version in ~/.config/playactor/credentials.json

Installed playactor to Synology via Homebridge terminal

Copied credentials file from 4 to ~/.config/playactor/credentials.json on my NAS

Run playactor login on NAS (still in same HB terminal) and followed the instructions

Profit :)

Thanks for the Workaround! Will try that out and let you guys know if it has worked. Maybe this steps could be added to the Guide later ¯_(ツ)_/¯

@0n1cOn3 I had the same problem and I was able to fix it. So what I did:

Installed ps4-waker npm package to my MacBook
Run ps4-waker and followed the instructions so the utility created a file ~/.ps4-waker.credentials.json
Installed playactor npm package to my MacBook
Run playactor login so it was able to pick existing creds and created it's own version in ~/.config/playactor/credentials.json
Installed playactor to Synology via Homebridge terminal
Copied credentials file from 4 to ~/.config/playactor/credentials.json on my NAS
Run playactor login on NAS (still in same HB terminal) and followed the instructions
Profit :)

yeah thanks this helped me too.. i did the following. I run hb in docker on synology, using the inbuilt docker (yes yes, i know, im too lazy for portainer) tho i skip the SPK and just use a scheduled docker run command to refresh the container

Log in to Homebridge UI, Open Terminal, these commands (the user you run as may depend on ur config?):
npm install ps4-waker -g
ps4-waker
Followed the process (it appeared in the PS4 App on phone)
make sure this file exists cat ~/.ps4-wake.credentials.json
mkdir ~/.config
mkdir ~/.config/playactor
cp .ps4-wake.credentials.json ./.config/playactor/credentials.json
homebridge-playstation-login
Follow that process, though it shows in the PS as ps4 waker, i guess because thats what authenticated
(i also saw some error that it didnt work or something, but I just ignored that and carried on lol)
Restarted homebridge
Added accessory
???
Profit
optional: npm uninstall ps4-waker - on mine it still works without that module. not needed anymore, and coz its not part of HB and wont be updated, i removed it. easy enough to install later


Changed positional arg to keyword arg for compatibility with auto-gptq

This PR addresses an incompatibility with the auto-gptq library:
  File "/home/matt/miniconda3/envs/gptq/lib/python3.11/site-packages/jsonformer/main.py", line 112, in generate_string
    response = self.model.generate(
               ^^^^^^^^^^^^^^^^^^^^
TypeError: BaseGPTQForCausalLM.generate() takes 1 positional argument but 2 were given

@1rgs This one is must-have


wait for reconnect with backoff

i'm simulate kafka server down via adding lag/packet drops or disconnect.
you package works fine and try to reconnect but
{"addr":"<IP_ADDRESS>:29091","broker":"seed 1","caller":"kgo/broker.go:558","level":"debug","msg":"opening connection to broker","timestamp":"2021-08-23 23:12:59"}
{"addr":"<IP_ADDRESS>:29091","broker":"seed 1","caller":"kgo/broker.go:568","err":{"Op":"dial","Net":"tcp","Source":null,"Addr":{"IP":"<IP_ADDRESS>","Port":29091,"Zone":""},"Err":{"Syscall":"connect","Err":61}},"level":"warn","msg":"unable to open connection to broker","timestamp":"2021-08-23 23:12:59"}
{"addr":"<IP_ADDRESS>:29092","broker":"seed 2","caller":"kgo/broker.go:558","level":"debug","msg":"opening connection to broker","timestamp":"2021-08-23 23:12:59"}
{"addr":"<IP_ADDRESS>:29092","broker":"seed 2","caller":"kgo/broker.go:568","err":{"Op":"dial","Net":"tcp","Source":null,"Addr":{"IP":"<IP_ADDRESS>","Port":29092,"Zone":""},"Err":{"Syscall":"connect","Err":61}},"level":"warn","msg":"unable to open connection to broker","timestamp":"2021-08-23 23:12:59"}
{"addr":"<IP_ADDRESS>:29091","broker":"1001","caller":"kgo/broker.go:558","level":"debug","msg":"opening connection to broker","timestamp":"2021-08-23 23:12:59"}
{"addr":"<IP_ADDRESS>:29091","broker":"1001","caller":"kgo/broker.go:568","err":{"Op":"dial","Net":"tcp","Source":null,"Addr":{"IP":"<IP_ADDRESS>","Port":29091,"Zone":""},"Err":{"Syscall":"connect","Err":61}},"level":"warn","msg":"unable to open connection to broker","timestamp":"2021-08-23 23:12:59"}
{"addr":"<IP_ADDRESS>:29093","broker":"seed 0","caller":"kgo/broker.go:558","level":"debug","msg":"opening connection to broker","timestamp":"2021-08-23 23:12:59"}
{"addr":"<IP_ADDRESS>:29093","broker":"seed 0","caller":"kgo/broker.go:568","err":{"Op":"dial","Net":"tcp","Source":null,"Addr":{"IP":"<IP_ADDRESS>","Port":29093,"Zone":""},"Err":{"Syscall":"connect","Err":61}},"level":"warn","msg":"unable to open connection to broker","timestamp":"2021-08-23 23:12:59"}

as you see - it tries to connect without waiting, so it try to ddos kafka server if it have low resources and also spam in logs.
what you think about adding some func that can add backoff for reconnecting ?

There is a function, RetryBackoffFn. The default strategy is to start at 100ms and exponentially backoff with jitter to 1s (this mirrors the behavior described in KIP-144).
I think the timestamp resolution in your logs may not be fine grained enough -- try adding milliseconds with .999 if this is from time.Format.
I'd be opening to changing the default backoff to 250ms rather than 100, and bumping the max backoff to 2.5s or 5s, though. Let me know if upping the time format resolution shows some backoff?

Is this for producing, or general admin requests?
Producing already has unlimited retries by default, with acks == -1.
Admin requests have a 1min timeout. I recommend keeping that, but there does exist a RetryTimeout option.

this question for consuming. so i'm run client.PollFetches and want it connection is dies - auto reconnect to kafka brokers and continue fetching.

That's the default behavior already, and I think that's the behavior for any client. Any kafka client should continue to reconnect for fetching (with some backoff)

ok fine, now experimenting with backoff, thanks

:+1: sounds good! Plrease reopen the issue if this isn't worked, I think this is closed.