An event with only an English description does not display that description when the site / app is in Dutch

See the IntegraCee Wine Tasting event. It only has an English description but it is not displayed on the dutch version of the website.
This is also the case for the API, which then only shows the (empty) dutch description

That makes sense right? A summary is optional, and since the website either shows everything dutch or shows everything english, it shows the dutch summary on the (also) dutch site.
I would suggest this is an content issue, other activities (that are only dutch) have resorted to storing in the english field that only a dutch description is available or the other way around.
I dont think we want a mixed-language website, do we?

I agree with @windwarrior, this is intended behaviour. Committees need to enter both a dutch and english description if they want their events promoted in both languages. In exception cases it might be acceptable to put an english description in the dutch field, but I think that would only be ok after discussion with the board.

I agree with the comments made above, however I would like to point out that when only adding a description in Dutch, a notification is shown that an English description is missing. A warning for missing Dutch descriptions would be worth implementing in my opinion.

We will add a warning when there is no Dutch translation.


Add dynamic and static IP/MAC lookups

Option to remove DHCP-Proxy dependency (example dhcpd.conf PR https://github.com/RackHD/RackHD/pull/114) and decouple DHCP service/least file tailing.
Creates lookup entry based on DHCP bootfile option request query parameters
Fixed unit-tests to use unique http/https ports that are causing random ADDRINUSE errors

@RackHD/corecommitters @geoff-reid @zyoung51 @uppalk1 @tannoa2 @anhou

:+1:

:+1: if you add a catch block/log.

:+1: after addressing the comments

@benbp

@anhou added query param description

@jlongever Thanks for refinement!

*** BUILD #523 ***
Test Name: Http.Api.Pollers POST /pollers afterwards should update with PATCH /pollers
Error Details: timeout of 2000ms exceeded. Ensure the done() callback is being called in this test.
Stack Trace: Error: timeout of 2000ms exceeded. Ensure the done() callback is being called in this test.


ConfigurationVariantDetails mapToMavenScope test scope support

ConfigurationVariantDetails.mapToMavenScope should support all maven allowed scopes
Currently (Gradle 6.6.1):
components.java.withVariantsFromConfiguration(configurations.testFixturesApiElements) {
    mapToMavenScope('test')
}

> Invalid Maven scope 'test'. You must choose between 'compile' and 'runtime'
Maven defines 5 valid dependency scopes and it is up to the build author to decide which scope is published to the generated pom. Customizing resulting scope after generation e.g. with pom.withXml is hacky and it is not trivial to match configuration for the generated dependency.

Published Maven metadata will not make use of the test scope. When you consume a library, that information is not used. So there is no plan on the Gradle side to enhance that support.

Closing as "will not fix"

Published Maven metadata will not make use of the test scope. When you consume a library, that information is not used.

When you consume from Gradle with gradle metadata it may be not (as the generated pom in general), but when you consume the published pom from maven, obviously it is used. Please look at https://github.com/gradle/gradle/issues/14936. Obviously many maven projects use test scope in the published pom and test scope IS the correct way to publish test fixtures or other test dependencies for standard maven pom, not the wrong compile scope Gradle publishes in the pom.
Publishing test dependencies with compile scope for standard maven pom seems plainly wrong, IMHO there is no any justification having junit or fixtures with compile scope in the published pom as it will incorrectly bring transitive test dependency to maven projects on compile scope.
I'm not sure why it requires some special "support". It should be the decision of the build author and Gradle should just verify it is one of maven scopes. Filtering out a scope for which Gradle authors have an idea that it is "not used" scope and calling adding a standard maven scope to allowed list an "enhancement" is a bit against the documentation claim that Gradle publishes maven compatible pom to the repository.

The fact that many Maven projects publish their test dependencies is because the POM file is both a sharing format and a build format. And the later leaks information in the former.
When you declare a test dependency in Maven, its transitive compile scope dependencies will be added to the test compile classpath, while its transitive runtime scope dependencies will be added to the test runtime classpath.
The "transitive" test dependencies will be completely ignored as it is not a transitive scope
So Gradle is fully compatible with what matters for published POMs.

I have a feeling you misunderstand/misinterpret the problem.
Let me illustrate with https://github.com/gradle/gradle/issues/14936:
When one publishes a regular jar with junit test classpath dependency, junit dependency is added by Gradle to the resulting pom, with the test scope. This IS the current behavior, it is correct and expected, conforming to the behavior you describe above (and it is in fact it implies there is an internal mapping to the maven test scope). So I'm not sure why you provide the description above enumerating the known facts, there is no problem and this is exactly the behavior one expects.
The problem arises when the Gradle publishes a test fixture (a feature which does not directly exist in maven and by large should map to a test classifier jar in maven pom, consumed by maven with the test scope, while Gradle consumers should use the new Gradle metadata instead).
When fixture is published, junit and other fixture dependencies are suddenly published as a dependency with compile scope, not a test scope! This is not expected and this seems obviously incorrect behavior, leaking test fixture dependencies into compile class path (and not the test compile class path as expected). One obviously would expect test fixture compile dependencies to appear in the classic published pom under the test scope (and consumed in the test compile classpath as you describe), and not map to the compile scope and leak into the consumer compile classpath.
Was it possible to mapToMavenScope('test'), the problem (IMHO a fixture publishing bug) was easily and generically solved.  Now it requires manipulating the resulting pom xml to determine fixture dependencies which should not be at compile scope of a consumer and changing their scope to test, which is a quirk and is fragile.
The above is a specific problem/bug, but naturally it leads to the discussion why withVariantsFromConfiguration .. mapToMavenScope(xx) should be restricted by Gradle to some arbitrary scope subset at all. It is an advanced API for build authors and hence why not let the build author to decide which scope to map in the resulting pom. Were the Gradle developers ideas and default mapping sufficient in all imaginable cases, there was no need to expose this mapToMavenScope API to build authors in the first place.


Support writing Avro containers asynchronously

Currently avro_rs::Writer expects the underlying writer to implement std::io::Write which makes it unsuitable for use in streaming environments with futures/async_std/tokio.
I know the ecosystem is a little scattered but it would be great if avro_rs supported one of the asynchronous write interfaces like tokio::io::AsyncWrite or async_std::io::Write.

Would an MR that adds support for tokio::io::AsyncWrite be desired by this project?

Thanks for being willing to contribute, @kendru!
I am not thrilled by the perspective of tying this library to any of the async runtimes, as there isn't truly any standard atm (although tokio seems to be the most mature among them). Even if we want to add support for it, it would be under a cargo feature.
@alexbiehl is also the only one who asked for such a feature, so I can't really tell that there is much of request for it either.
As for now, perhaps we could offer the possibility to the users of implementing the Writer interface, so they can implement it for their runtime of choice? What do you people think?

@poros I completely understand not wanting to tie this library to a specific async runtime, and I would be happy to try implementing tokio's AsyncWrite interface under a cargo feature. This functionality would be very useful for a project that I am currently working on, and I would imagine that as the use of async code in Rust becomes more common, this will be useful for more people. Since tokio does look like the de-facto runtime, I think that it would make sense to support it. That said, if you are still not convinced that it would be useful for this library to offer an async interface, I completely understand.

I am only a bit worried that we will need to keep maintaining it in a fast-changing ecosystem when, at the end, it isn't a core component of a serde library.
@kendru : what do you think about the Writer public trait approach I mentioned above? Would that allow you to implement something that works with tokio? If not, I would be OK to go for the cargo feature approach.

Have you any ETA about async?
@kendru have you any fork or patch for async?
How to permit the usage of tokio and async_std?


pachctl inspect job workflow is unintuitive

What happened?:
I did the tutorial on Pachyderm 2, had a job run then did a pachctl list job followed by a pachctl inspect job <jobid>.
This returned a invalid format "<jobid>": expected pipeline@job-id
The problem is that doing a pachctl list job shows no info about which pipelines were involved in the job. For a simple scenario such as the tutorial, it is trivial to guess that the pipeline is edges, but for a complex production scenario with multiple pipelines involved with the job, this leaves the user guessing.
What you expected to happen?:
I would expect a pachctl inspect job <jobid> to return some aggregated information about all the pipelines were involved in the job.
Alternatively, doing a pachctl list job should specify which pipelines were involved with the job in a new column and maintain the pipeline@job-id format.
How to reproduce it (as minimally and precisely as possible)?:
As described above.

pachctl list job <job-id> does some of what you want - while it just looks like a filter, it shows output more similar to pachctl list job --expand which has the extra column you want. It isn't literally in name@id format, though, could be something to consider.


UPDATED | When solely using qsParams undefined was included in the qu…

When solely using qsParams undefined was included in the querystring
Description
In the function isUrlIgnored,
When solely using qsParams undefined would be appended to the resulting queystring
e.g: '/sitecore/layoutsvc/render/jss?item=%2Fabout&sc_apikey={GUID}&undefined&sc_site=mysite';
I note it has also updated the formatting on the file.
I note there is a .prettierrc file, as I user prettier, I'm assuming that this formatting changes are valid
Motivation
Ensure resultant querystring matches convention
How Has This Been Tested?
New unit test added
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation update (non-breaking change; modified files are limited to the /docs directory)

Checklist:

[x] I have read the Contributing guide.
[x] My code follows the code style of this project.
[x] My code/comments/docs fully adhere to the Code of Conduct.
[ ] My change is a code change and it requires an update to the documentation.
[ ] My change is a documentation change and it requires an update to the navigation.

@jpspringall Please, update your PR, pull changes.


"You must be logged in to deploy changes" v0.18.7

What are the steps to reproduce?

Install NR v018.7
Embedded Node-red in an expressJS App.
Do not enable any form of authentication in Node-red.
My custom NR settings are:

        httpAdminRoot: '/red',
        httpNodeRoot: '/api',
        nodesDir: config.nodesDir,
        userDir: config.nodeRedUserDir,
        verbose: true,
        editorTheme: {
            userMenu: false
        },
        functionGlobalContext: {},
        ui: {
            path: 'red/ui'
        }
    };

What happens?
The message You must be logged in to deploy changes is displayed, when I try to deploy any flows.
This started happening after I upgraded NR from 0.14.6 to 0.18.0, so I suspect the bug was introduced by the OAuth authentication.
What do you expect to happen?

The deployment to succeed,

Please tell us about your environment:

Node-RED version: v0.18.7
node.js version: 8.1.3
npm version: 5.0.3
Platform/OS: RaspberryPi 3
Browser: Chrome

In earlier versions of Node-RED we would ignore what we thought we knew about the user's logged in state and submit the deploy http request regardless.
In 0.18 we added a check to see if the current user has permission to access the route before sending the request.
A request to /settings includes information about the current user, including what permissions they have. For example:
{"httpNodeRoot":"/","version":"0.18.7","user":{"anonymous":true,"permissions":["read","inject.write"]}}
The fact you have used your own custom authentication rather than the built-in auth system means you probably don't have a permissions object being returned here.
The object is automatically populated from the req.user object the route handler receives: https://github.com/node-red/node-red/blob/master/red/api/editor/settings.js#L33-L40
So your app needs to be include a permissions object on the req.user you are creating.

I've tested a couple of other version to narrow the broken one down:

v0.16.2-  works
v0.17.2-  works

Hi @knolleary,
I will follow your advice and see if I can apply to my solution ASAP. Thanks.

Closing as this isn't a Node-RED issue. Happy to discuss further it if needs.

@knolleary it worked. Thanks


Add hook for redux devtools

This allows you to have all the benefits of redux dev tools, without having to hook middlewares up in your app.
https://github.com/zalmoxisus/redux-devtools-extension

@robinjoseph08 I changed the commit message in the other PRs as well 😄


Last steps before submission

Demonstrate the output options in one of the example and add these options to the respective documentation. I marked some with "TODO".

We decided to leave it as it is, because the added value for that is low.


fix: Fix chain of responsibility setting up [DEV-3047]

Task linked: DEV-3047 Credential Service: Fix API guarding


Explore sandbox

/assign @electrocucaracha @efiacor @lapentad @henderiw

@lapentad yes, it's the draw.io source file that the .png was generated from. It's there so that the diagram can be modified later.

Could we nudge this on please?

/lgtm
/approve


Update GopenPGP and set version 1.0.0

Update GopenPGP to v3.0.0-beta.0
Enable SEIPDv2 in default profile (i.e., it is generated if key advertises it)
Tag version 1.0.0

Oops, overlooked this. Resolved by https://github.com/ProtonMail/gosop/commit/3dab720d15a9fe44d645f0ccfc4655499aab132d, https://github.com/ProtonMail/gosop/commit/30cc938fee649782ef0c1ee8748434695754fe10, and https://github.com/ProtonMail/gosop/commit/6090f403f070ff587b5fb5efa5c4dd4469dfcfe1.
Enabling SEIPDv2 for public keys that support it should be done in go-crypto, instead.


Deprecation message in Chrome app

Fixes https://github.com/readium/readium-js-viewer/issues/712
Note that the same nagging dialog pops up every time the library or reader views are loaded. The user cannot tick a "stop nagging me" checkbox. The reading system does not limit the number of times the message is shown. There is no notion of reading "session" or time window during which the message should only be shown x number of times.
Test URL (reader view):
http://readium-chromeapp.surge.sh/?epub=https%3A%2F%2Freadium.firebaseapp.com%2Fepub_content%2Faccessible_epub_3
Test URL (library view):
http://readium-chromeapp.surge.sh/?epubs=https%3A%2F%2Freadium.firebaseapp.com%2Fepub_content%2Fepub_library.opds
Note that this Pull Request enables the nagging dialog for the cloud reader as well as the Chrome app, so that we can test this feature easily (using the above URLs). There is a boolean in the proposed code to enable this feature selectively, i.e. only for the Chrome app in the Chrome web browser, but not in Chrome OS.

@danielweck This is excellent. Much better than my hacky approach.  But I am not sure that we need to remind them every time they open a book.  I would think that each time when the library view is shown would be sufficient.

Sounds good to me. I forgot that in the Chrome App there is no way to open an EPUB directly (no direct URL to a specific publication). The UX always lands the user in the library view.

Okay, I removed the nagging message in the reader view.

@rkwright once the i18n file is fixed (rollback the specific line change I commented on), then I am happy to merge. Thanks for your tweaks! :)

LGTM, LGTM
(Looks Good To Me, Let's Get This Merged)
;)


Introduce Generic Object.

Trello: https://trello.com/c/bWD3nqEI

@gmcculloug @Fryguy @gtanzillo @jrafanie Please review.

@lfu Can you put a summary of the use case for this or a link to more information in the first comment on this PR?  I can't remember what the requirements were for this.

Can you verify which methods should be public vs private?  For example, I think type_cast should be private, because I can't see why a caller would need to call that directly.  I was going to comment on individual methods, but I'm not 100% sure which ones are which.

@Fryguy @gmcculloug Updated.

cc @bzwei

@Fryguy @gmcculloug Updated.


lodash: signatures of the method _.constant changed

https://lodash.com/docs#constant
https://lodash.com/docs#_ (description of the chainable wrapper)

thanks mate!


add more availability to bitwarden instance

create like a docker swarm

https://bitwarden.com/help/hosting-faqs/#general


Add a threads option

Coverage decreased (-0.8%) to 79.056% when pulling 5787cf07c6d5845b521a4bb9e88caeddd19461ac on rust-av:rayon into 65fd09f7bc71ecd19cdfe4b93b0dec98f778275a on xiph:master.


[FEATURE] Option to Quantize / GPTQ first then push to Huggingface

🚀 Feature

See https://github.com/PanQiWei/AutoGPTQ/tree/main#quantization-and-inference
Motivation

Much less VRAM & faster inference speeds.

Applicable code: https://github.com/h2oai/h2o-llmstudio/blob/25164164fd36c5e9ac8ce39275a709e649516531/app_utils/sections/experiment.py#L1776-L1811

I'm learning how to use AutoGPTQ now. I'd be up for contributing this!

Is there any benefit in pushing it directly quantized to HF vs. first pushing it in float16 and then quantizing?

I think it is either two projects, or two branches.
But probably two projects is what people most of the times do.
Would be great feature to have this toggle.

Work in progress: https://github.com/h2oai/h2o-llmstudio/pull/285

AWQ is the new preferred quantization method, will explore if we can add it.

Closing in favor of https://github.com/h2oai/h2o-llmstudio/issues/374


Error after install

After following the install procedure, this is the message that appears in the VSCODE log (Extension Host):
[2020-04-24 17:52:47.990] [exthost] [info] eager extensions activated
[2020-04-24 17:53:16.251] [exthost] [error] Activating extension textX.textX failed due to an error:
[2020-04-24 17:53:16.251] [exthost] [error] TypeError: Cannot read property 'onReady' of undefined
at c:\Users\berna.vscode\extensions\textx.textx-0.1.2\dist\extension.js:1:99773
at Generator.throw ()
at a (c:\Users\berna.vscode\extensions\textx.textx-0.1.2\dist\extension.js:1:98840)
Any suggestion on what to do next?

Hi @vlimmere ,
By looking at the logs, it seems to me that they are related to another vscode extension for textX which is not maintained by me. Try opening an issue on that repository.
However, your message made me realize that this extension is not working anymore as well, as it has been neglected by me for quite some time now. I will do my best to update it and make it functional again in the following days.
Thanks and good luck.


maint: remove sphinx-panels support; remove deprecated config shims

This PR removes shims for several configs marked as "deprecated" that had specific versions mentioned, and added target removal versions for the remaining unlabelled ones.

probably could also purge references to / support of sphinx-panels by now, seems like it's been long enough?

Agreed re: panels. Want to do that in this PR?

Agreed re: panels. Want to do that in this PR?

sure, will do this afternoon

Wanna take care of theme.conf too?
https://github.com/pydata/pydata-sphinx-theme/blob/e81108b6641f566c99d523804dc89bbcb8f4e3b9/src/pydata_sphinx_theme/theme/pydata_sphinx_theme/theme.conf#L48-L53

Wanna take care of theme.conf too?

oops, missed that in my git grep because all caps 🤦🏻
stand by

(looks like one more thing: remove the tests for the deprecated options)

OK @choldgraf hopefully that's done it!  I also added the newly deprecated footer_items to the deprecated test build


[AutoRelease] t2-springappdiscovery-2023-12-19-44765(can only be merged by SDK owner)

https://github.com/Azure/sdk-release-request/issues/4836
Live test success
https://dev.azure.com/azure-sdk/internal/_build?definitionId=6644

issue link:https://github.com/Azure/sdk-release-request/issues/4836


Sidebar content is not visible in light theme

can i work one this!

Issue is fixed, PR has been merged already, soon the changes will be live on app.100xdevs.com


WIP PHP: call OP_RECV_STATUS_ON_CLIENT at the end of server  streaming

In current implementation, the user should call getStatus for the server streaming call. However the user doesn't know when to call it because the user doesn't know when the call is finished. (Also, the user can more getStatus more than once, which will cause the problem).
Since the last response for the server streaming call is a nullptr, we can move the OP_RECV_STATUS_ON_CLIENT to when the nullptr is received from the server. The same idea from ruby.
@fengli79 . Save the status in order to make the original API still work. I think it should satisfy the backward compatibility. The only thing added is that the status can also be get when the last response is received without the need to call getStatus.

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences

Since the last read() is a NULL, getStatus is not needed to be called if no one cares about the status. The behavior is similar to c++ originally, thus this PR is not needed.


Fix AtomicWaker

The previous attempt at fixing AtomicWaker ended up introducing new
bugs. This is partially due to the implementation evolving (incorrectly)
over time.
This patch provides a brand new, from scratch, implementation of
AtomicWaker, addressing the soundness issues.

Once this lands, we should put out a -beta.

LGTM-- will merge w/ CI

Merged! @cramertj want to put out a -beta?

@aturon Sure!


Revendor dws and lustre-fs-operator

Then do go-mod-tidy. All of this is in prep for doing the ginkgo-v2 update.
Signed-off-by: Dean Roehrich<EMAIL_ADDRESS>

Don't need this.


Context Refactor

Two quick comments.

We should always use std::shared_ptr, std::make_shared etc
2 We need to change methods to create context to return a shared pointer, std::shared_ptr ctx = cylon::CylonContext::InitDistributed(mpi_config);

@supunkamburugamuve I modified the methods to return shared_ptr and also used make_shared in creation.
Resolving some issues in Java bindings.

@vibhatha it seems the test cases need to be updated

This PR has been merged to below PR.
https://github.com/cylondata/cylon/pull/135


uws above version v18  causes uws http server to crash

The parameter request is no longer available since this commit
https://github.com/uNetworking/uWebSockets.js/commit/b4df9ebf5f4c3ecc884d5f5e0df1cd04b8caa7c3#diff-01c1a4e28835a7d097ce62009d6e3db1L97-R127

Indeed, perhaps the upgrade property should be used now:
https://unetworking.github.io/uWebSockets.js/generated/interfaces/websocketbehavior.html#upgrade and then pass the url to the ws connection as in this example: https://github.com/uNetworking/uWebSockets.js/blob/master/examples/Upgrade.js
Feel free to make a pull request, I'll try to work on it this weekend.

👍 nice!


At first when I read the comment, I thought it was just a random rude user until i look above the comment

new owner interface is settled.

looking to adjust the enduser screen next

UI has been changed


DEP: linalg: sharpen deprecation warning for pinv {,r}cond

Reference issue

What does this implement/fix?

Adds a specific version for removing cond/rcond and, whilst unlikely to be needed as the arguments are at the end of the signature, uses _NoValue to trigger the deprecation warning instead of None. Also adds a test which checks the deprecation warning is emitted.
Additional information

Thanks for the ping. Some comments. I'm not a fan of pushing out the actual removal out by another 1.5 years (when 1.14 is released), but I guess that's what it is.

I personally agree. We could maybe be more flexible with such things. At least allowing to deprecate in n+1 would be nice.

Thanks for the review @h-vetinari, I have hopefully addressed your comments. My personal preference would be to be conservative with the removal version. Six months does not make that much difference at our end but my experience is that often in industry it can take a long time to get security clearance for new versions of software and hence versions are sometimes missed.

 I don't know how such a change went under the bridge, but it even got some encouragement in my defense #18166
I apologize for my past behavior but as a silver lining nobody cared. Hence we might be overdoing this disciplined deprecation in a slightly overzealous fashion.  Obviously I'm not advocating such behavior but I think we need to consider the usage patterns on a case by case basis.

Ah now I remember, because atol, rtol is a drop in replacement for cond, rcond in the positional argument case.

Hence we might be overdoing this disciplined deprecation in a slightly overzealous fashion. Obviously I'm not advocating such behavior but I think we need to consider the usage patterns on a case by case basis.

To clarify, the primary purpose of this PR is to add the version number at which we can get rid of cond/rcond. The change to _NoValue here is probably not strictly necessary but I think it is important to follow the best practice as newcomers tend to copy (and extrapolate) existing code.

All good from my side. Just wanted to mention that for the very long ongoing deprecation warnings we might be a bit more lax. Otherwise I fully agree.

The wisdom of the crowd seems to prefer 1.13.0 given the existing long-standing warning so have updated the messages


numba --annotate fails to handle lifted loops correctly

from numba import jit

def bar(x):
    return x

@jit
def foo(x):
    h = 0.
    for k in range(x):
        h = h + k
    if x:
        h = h - bar(x)
    return h

print(foo(10))

gives:
$ numba --annotate-html foo.html foobar.py
...
AttributeError: Failed at object (object mode frontend)
Failed at object (annotate type)
'LiftedLoop' object has no attribute 'bytecode'

Closing. Fixed in https://github.com/numba/numba/pull/2204.


Manual and automatic installations hyperlinks.

Please, let the people (like me) know that there is an automatic installation.

Actually, the automatic installation does not install terminal emulators or patched font. Maybe I can put it at the forefront of the doc?

Moving that on top would also work. Just so people could know they don't have to install everything piece by piece.

okay, I will close your PR and rework it a bit. Anything else you would like to change?

I don't think so. That's the only thing.


reputation cache isn't refreshed correctly

tested with 1.8.6
after fixing https://github.com/encointer/encointer-parachain/issues/145
the expectation was that the user could pull down on the home screen to refresh such that his outdated reputation would be purged and he could register for the ceremony
The rpc node now reproducibly returns no reputation for that user
still, the profile page shows "overall reputation" to be 1 and registering failed

@clangenb ideas?


Move binary test files to Google Drive

Let's reduce our repo size by moving rvts and other heavy binaries to GLF: https://docs.github.com/en/repositories/working-with-files/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage

The problem with that is that Git LFS is charged both by "data storage usage" and "network bandwidth". Meaning the more people pull the files, we get charged more for it.
If we ever stop paying for LFS (or gets too expensive), we'd need to back-edit the history of the LFS part for the repo to allow users to pull it again without it.
I've been through this in one of my repos and it was bit of a PITA.

Discussed with Alan today and we decided to:

move all Revit test files to a shared google drive folder (I made this one in our drive) and document so in our Readme @connorivy
try removing these binaries from our Git History to keep the repo size small, [see this] @AlanRynne (https://docs.github.com/en/repositories/working-with-files/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage)


use yellow color when version appears to be moving backwards

This is very much intended as a work in progress (no tests!) and proof-of-concept for #5506.
In cases where the dependencies change, it is not always possible to tell if they are going forwards or backwards -- for instance a change from > 2.0 to < 2.8 is neither obviously a forward or a backward change.
Hence the behavior here is to always default to the green color unless there are two specific version numbers and the new one is strictly less than the old one, in which case we use the yellow color.
I’d love any code review and any suggestions for the right place to add some tests for this. I think the tests should end up being quite simple -- we can check for \e[32m (green) versus e[33m (yellow) in the strings sent to the shell, and that’s easy enough -- but I’m simply not familiar enough with the test suite to know the appropriate place and syntax to do that. Suggestions welcome!

@colby-swandale Thanks for the review. I’ve extracted the color logic into a private method as you suggested, and have restricted the rescue to only catch ArgumentError, which is the relevant error in this case.

@segiddins does this look good to you?

Still needs a test, otherwise looks 💯

@segiddins I’m not sure yet how to set up the right test . . . would it go in bundler/source_spec.rb?
At a glance, I couldn’t find tests pertaining to the "Using ____ (was ____)" statements, which is where we should be adding tests. Once we find the right place to add them, the actual tests themselves should be quite simple. We’ll just check the output string for yellow or green as appropriate.

Yup, see line 64 of that file for an example

👍 Tests added for two conditions: an apparent regression (yellow) and an apparent forward change (green). All tests pass and things are looking good.

Woohoo!
One lingering question for me is that I’m not completely certain that the yellow coloring will work in cases where the entire line shows in green. For instance, something like this:

Not sure yet that cases like these will work. They may, actually, but I wasn’t sure how to test for that particular case... But maybe that’s a corner case anyway.

Looks great!
@bundlerbot r+


Folder picker always chooses my root directory

When I try to select a folder for projects, it always chooses the root directory regardless of which one I select.
Running ubuntu 12.04.5 LTS, kernel 3.5.0-54-generic

I experience this too on only one of my Ubuntu machines. Not sure what causes it, but it happens on Atom?
The work around until this is fixed is to launch via command line:
cd my-project
Code .

The machine in question happens to be Ubuntu 12.04 LTS as well, so maybe it's an Ubuntu or Electron bug?

I created an Atom issue for this a few months ago, no attention though https://github.com/atom/atom/issues/9320

Maybe this should be reported to Electron instead.

Created https://github.com/atom/electron/issues/4171 and closed the Atom issue in favor of it.

It was closed in favor of https://github.com/atom/electron/issues/1212. Apparently it's because Electron doesn't support ~ as it isn't meant to be meaningful outside of bash. Ubuntu 12.04's open folder dialog may be returning ~ in the path which is probably what is causing the issue. Electron removed the won't fix label though so they're open to accepting the change to support it.

:+1:

Closing, as there does not seem to be anything we can do.


4.4 index signature check on wrong generic?

Bug Report
We are using key remapping with template strings to type getters/setters generated automatically for our classes as can be seen in the simplified code below. This worked nicely in 4.3 and provided typing for getA() and getB() functions,
Using 4.4 it is still working but we are getting errors when any class member is named as 'getXXX'.
export interface AssociationConfig<U extends string> {
    [propName: string]: U;
};

export type AutoGeneratedFunctions<T extends AssociationConfig<string>> = {
        [K in keyof T as `get${Capitalize<string & K>}`]: () => T[K]
    }

interface FooAssociations extends AssociationConfig<string> {
    a: 'aaaa',
    b: 'bbbb'
}

interface Foo extends AutoGeneratedFunctions<FooAssociations> {

}

class Foo {
    doSome(a: number): string {
        return 'this works';
    }
    getSome(): string {
        return 'this works';
    }
    getSomethigElse(a: number): string {
        return "this fails: Property getSomethigElse' of type '(a: number) => string' is not assignable to '`get${string}`' index type '() => string' ";
    }
}

Output
;
class Foo {
    doSome(a) {
        return 'this works';
    }
    getSome() {
        return 'this works';
    }
    getSomethigElse(a) {
        return "this fails: Property getSomethigElse' of type '(a: number) => string' is not assignable to '`get${string}`' index type '() => string' ";
    }
}
export {};

Compiler Options
{
  "compilerOptions": {
    "strict": true,
    "noImplicitAny": true,
    "strictNullChecks": true,
    "strictFunctionTypes": true,
    "strictPropertyInitialization": true,
    "strictBindCallApply": true,
    "noImplicitThis": true,
    "noImplicitReturns": true,
    "alwaysStrict": true,
    "esModuleInterop": true,
    "declaration": true,
    "experimentalDecorators": true,
    "emitDecoratorMetadata": true,
    "target": "ES2017",
    "jsx": "react",
    "module": "ESNext",
    "moduleResolution": "node"
  }
}

Playground Link: Provided
🔎 Search Terms
key remapping, template strings, 4.4
🕗 Version & Regression Information
This changed between versions 4.3 and 4.4
🙁 Actual behavior
The Foo class can not have any member starting with get which doesn't match the signature defined in AutoGeneratedFunctions
🙂 Expected behavior
The  signature defined in AutoGeneratedFunctions should only be applied to getA() and getB() functions because only those are defined in FooAssociations.

One of the issues here is that the key remapping also applies to the index signature in
export interface AssociationConfig<U extends string> {
    [propName: string]: U;
};

so you end up creating a template index signature in the subclass. I don't think this was a situation that we had anticipated but I believe that the behavior is "expected". Tagging @ahejlsberg to get his take on this as well though.
It seems like the root issue is that index signatures are often also used as a "constraint" on all the properties in a class; but there's no way to say "I want all my properties to conform to SomeType" without creating an index signature. Ideally we would have a mechanism like that.

I want all my properties to conform to SomeType

could be done by https://github.com/microsoft/TypeScript/issues/7481

Well only for an expression - there's no way to ensure a type satisfies another type without unused local type aliases and the like (e.g. type _Assert = CompatibleWith<SomeType, Constraint>;).

The specific change in 4.4 is that we now generate index signatures in mapped types for keys that are template literal strings with placeholders. See #44512 for more details. In this particular example, the string index signature introduced by AssociationConfig is mapped by AutoGeneratedFunctions into an index signature for the key type `get${string}`. Previously we'd just drop that member, which was wrong. So, the new behavior is indeed intended.
It's pretty easy to get the old behavior by excluding string index signatures in AutoGeneratedFunctions:
export type AutoGeneratedFunctions<T extends AssociationConfig<string>> = {
    [K in keyof T as string extends K ? never : `get${Capitalize<string & K>}`]: () => T[K]
}


Zombie is hanging on WebSocket/Juggernaut connection

When trying:
var zombie = require("zombie");
zombie.visit("http://spine-fowa.herokuapp.com/", function (err, browser, status) {
  console.log("done");
});

Connection is stalled and never return anything.
Expected behavior: after 5 seconds(default value) javascript is disabled and browser/status object is returned.

Environment data:
node v0.4.7
npm v1.0.94
zombie v0.12.0
OS X 10.7.2


feat: Minimal server/client arch

Codecov Report
Attention: 142 lines in your changes are missing coverage. Please review.

Comparison is base (b0f3bf1) 87.87% compared to head (8d5c300) 85.89%.
Report is 2 commits behind head on main.

Files
Patch %
Lines

server/src/main.rs
0.00%
55 Missing :warning:

cli/src/main.rs
0.00%
53 Missing :warning:

liblykia/src/protocol/connection.rs
0.00%
34 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #25      +/-   ##
==========================================
- Coverage   87.87%   85.89%   -1.98%
==========================================
  Files          23       24       +1
  Lines        4388     4489     +101
==========================================
  Hits         3856     3856
- Misses        532      633     +101

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


Stringent linting

Missing return type should probably be an error
any should be an error too>
Anything else maybe?
Maybe more plugins?

RESERVED NO STEAL

Dibs for Hacktoberfest

Not if i get there first


WiFi Interruptions

What happened?
WiFi Signal drops, Connection to WiFi lost, low signal strengths
To Reproduce Bug
Start system, occurs after a short time / must be connected to 5V power; no defects with USB connected
Expected Behavior
No voltage drop
Install Method
Self-Compiled
What version of WLED?
2402120
Which microcontroller/board are you seeing the problem on?
ESP32
Relevant log/trace output
No response
Anything else?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Probably due to low power supply (5V) - which is being used for DI lines also. --> Separate power supply for ESP necessary?


TypeScript types for sx prop spreading broken

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
The docs recommend receiving and passing down the sx prop to a MUI component by spreading an array.
https://mui.com/system/the-sx-prop/#passing-sx-prop
Instead of doing ...(Array.isArray(sx) ? sx : [sx]) everywhere, as recommended in the docs, I'm using a generic & type-safe helper function for that (The above approach is not type safe because of isArray is not generic: isArray(arg: any): arg is any[];).
function castToArray<T>(oneOrMultipleElements: T | T[]): T[] {
  return Array.isArray(oneOrMultipleElements) ? oneOrMultipleElements : [oneOrMultipleElements];
}

const foo = castToArray([3, 4]); // => type number[]
const bar = castToArray(4); // => type number[]

Trying to use this with some MUI component like this, does not work though!
const sxArray = sx ? castToArray(sx) : [];
// ⬆ TS SHOWS for above:
/*
TS2345: Argument of type 'SystemCssProperties<Theme> | CSSPseudoSelectorProps<Theme> |
 CSSSelectorObjectOrCssVariables<Theme> | ((theme: Theme) => SystemStyleObject<...>) |
readonly (boolean | ... 1 more ... | ((theme: Theme) => SystemStyleObject<...>))[]' is not assignable
 to parameter of type 'Fill | Fill[] | (Fill | Fill[] | null | undefined)[] | null | undefined'.   Type 'SystemCssProperties<Theme>'
 is not assignable to type 'Fill | Fill[] | (Fill | Fill[] | null | undefined)[] | null | undefined'.     Type
'SystemCssProperties<Theme>' is missing the following properties from type '(Fill | Fill[] | null | undefined)[]': length, pop, push, concat, and 27 more.
*/

return (
  <Alert
    sx={[...sxArray, { "& .MuiAlert-message": { whiteSpace: "normal" } } ]}
    variant="standard"
    >
    <AlertTitle>{title}</AlertTitle>
  </Alert>
);

// ⬆ TS SHOWS for above:
/*
TS2322: Type '(Fill | Fill[] | null | undefined)[]' is not assignable to type 'SxProps<Theme> | undefined'.
   Type '(Fill | Fill[] | null | undefined)[]' is not assignable to type
'CSSSelectorObjectOrCssVariables<Theme>'.     Index signature for type 'string' is missing in
type '(Fill | Fill[] | null | undefined)[]'.
*/

Expected behavior 🤔
TS should not report an error.
Steps to reproduce 🕹
Link to TS Reproduction
Context 🔦
No response
Your environment 🌎

`npx @mui/envinfo`

  System:
    OS: macOS 11.6.6
    CPU: (8) arm64 Apple M1
    Memory: 80.06 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.13.2 - /usr/local/bin/node
    Yarn: 1.22.17 - /usr/local/bin/yarn
    npm: 8.1.2 - /usr/local/bin/npm
  Managers:
    Homebrew: 3.4.11 - /opt/homebrew/bin/brew
    pip3: 22.1.1 - ~/.pyenv/shims/pip3
    RubyGems: 3.0.3 - /usr/bin/gem
  Utilities:
    Make: 3.81 - /usr/bin/make
    GCC: 4.2.1 - /usr/bin/gcc
    Git: 2.32.0 - /usr/bin/git
    Clang: 13.0.0 - /usr/bin/clang
  Servers:
    Apache: 2.4.53 - /usr/sbin/apachectl
  Virtualization:
    Docker: 20.10.14 - /usr/local/bin/docker
  IDEs:
    Nano: 2.0.6 - /usr/bin/nano
    Vim: 8.2 - /usr/bin/vim
    WebStorm: 2022.1
    Xcode: /undefined - /usr/bin/xcodebuild
  Languages:
    Bash: 3.2.57 - /bin/bash
    Go: 1.18.2 - /opt/homebrew/bin/go
    Perl: 5.30.2 - /usr/bin/perl
    PHP: 7.3.29 - /usr/bin/php
    Python: 3.10.3 - /Users/nickluger/.pyenv/shims/python
    Python3: 3.10.3 - /Users/nickluger/.pyenv/shims/python3
    Ruby: 2.6.3 - /usr/bin/ruby
  Databases:
    SQLite: 3.32.3 - /usr/bin/sqlite3
  Browsers:
    Chrome: 102.0.5005.61
    Firefox: 100.0.2
    Safari: 15.5

I have updated the TS playground. However, I am not sure how to fix the Type 'SxProps<Theme>' must have a '[Symbol.iterator]()' method that returns an iterator. typescript error.
Closing it as this has nothing to do with MUI but rather typing properly with typescript.

Hey, thanks for the quick reply! 🙏

I have updated the TS playground.

Yes, you removed the generics - which is possible of course, but kinda misses the point of MUI's sx type not working with TS generics.

Closing it as this has nothing to do with MUI but rather typing it properly with typescript.

OK. I didn't know that broken types are not to be reported. 😄

OK. I didn't know that broken types are not to be reported.

I didn't mean that you can't report MUI's broken types. You can report those. But I don't think SxProp is broken here. Just need to find a way to type your method properly, which can be asked on Stackoverflow not here.

Ok, never mind. It's not that important for us, there's still any. 😄

I wonder if its because SxProps<Theme> can actually be an object, an array, or a function according to inspecting the types of it:


How I can show scroll by all time;

https://github.com/malte-wessel/react-custom-scrollbars/issues/96


fix: tell github to always treat php files as text

Speculative fix for https://github.com/googleapis/synthtool/issues/918

Seems like something that should be fixed in synthtool no?
I don't know the implications of setting the gitattribute. Ill have to do more research before approving.

Seems like something that should be fixed in synthtool no?
I don't know the implications of setting the gitattribute. Ill have to do more research before approving.

I think I found a better way to do this.

I think I found a better way to do this.


git项目显示问题

Type: Bug
无法在window11正常现在git项目，svn项目可正常显示，mac无该问题
VS Code version: Code 1.76.1 (5e805b79fcb6ba4c2d23712967df89a089da575b, 2023-03-08T16:32:00.131Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: No

源代码管理显示问题

感谢您创建此问题！
然而，由于您没有使用英语，我们很难进行处理。如果可能，请您将此问题描述修改为英文。请您直接编辑此问题，不要提交回复或新问题。
请注意，机器翻译服务通常无法处理用于讨论软件问题所需的技术性语言，所以我们推荐您寻找一位熟悉相关技术的人来协助翻译。
如果您无法做到，没有关系。此问题已经被标记为需要翻译，等待社区成员志愿进行翻译。

Thanks for creating this issue!
Unfortunately, as the description is not in English, it's hard for us to work on. If possible, please edit the original issue to be in English.
In our experience, automatic translation services are not able to handle the technical language needed to effectively communicate about software issues, so we recommend finding a human translator who is familiar with our technology to help.
Otherwise, we have marked this as needing translation and a community member may be able to help out.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Minimum Java version?

I'm trying to use:
dependencies {
    testImplementation 'io.hosuaby:inject-resources-core:0.2.2'
    testImplementation 'io.hosuaby:inject-resources-junit-jupiter:0.2.2'
}

when building the project got the
      > No matching variant of io.hosuaby:inject-resources-junit-jupiter:0.2.2 was found. The consumer was configured to find an API of a library compatible with Java 11, preferably in the form of class files, preferably optimized for standard JVMs, and its dependencies declared externally but:
          - Variant 'apiElements' capability io.hosuaby:inject-resources-junit-jupiter:0.2.2 declares an API of a library, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares a component compatible with Java 13 and the consumer needed a component compatible with Java 11
              - Other compatible attribute:
                  - Doesn't say anything about its target Java environment (preferred optimized for standard JVMs)
          - Variant 'runtimeElements' capability io.hosuaby:inject-resources-junit-jupiter:0.2.2 declares a runtime of a library, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares a component compatible with Java 13 and the consumer needed a component compatible with Java 11
              - Other compatible attribute:
                  - Doesn't say anything about its target Java environment (preferred optimized for standard JVMs)

but after adding block:
java {
    disableAutoTargetJvm()
}

build succeeds.
Environment
$ ./gradlew --version

------------------------------------------------------------
Gradle 7.2
------------------------------------------------------------

Build time:   2021-08-17 09:59:03 UTC
Revision:     a773786b58bb28710e3dc96c4d1a7063628952ad

Kotlin:       1.5.21
Groovy:       3.0.8
Ant:          Apache Ant(TM) version 1.10.9 compiled on September 27 2020
JVM:          11.0.11 (AdoptOpenJDK 11.0.11+9)
OS:           Mac OS X 11.5 x86_64

I believe there is an issue when publishing the package, because it requires for consumer compatibility with Java 13, meanwhile the library uses sourceCompatibility and targetCompatibility equal to JavaVersion.VERSION_1_8

Minimum Java version in 8. Yes, I confirm that this problem exist, while using Gradle. Your workaround is right. This will be fixed in future.


The variable 'g:syntastic_python_python_exec' has not effect

Setting the 'g:syntastic_python_python_exec' to '/usr/bin/python3' doesn't change the underlying interpreter. The valid python3 constructs are shown to be invalid.
Minimal .vimrc
set nocompatible
if has('vim_starting')
  "NeoBundle path
  set runtimepath+=~/.vim/bundle/neobundle.vim/
endif
call neobundle#begin(expand('~/.vim/bundle'))
NeoBundle 'scrooloose/syntastic'
call neobundle#end()
filetype plugin indent on

syntax enable        " enable syntax coloring
let g:syntastic_python_python_exec = '/usr/bin/python3'

Minimal example
print('hello',end='')

The issue was wrong version of pylint


Unable to connect to configured data backends with Composer

AppGyver Proxy returns {“error”:“Resource ‘resource' not configured”} for resources configured in Composer.
https://forums.appgyver.com/#!/composer:builtio-backend-and-compos

Resolved


Add evaluation for Object Detection

[ ] Local (Depends on dotnet/machinelearning#6712)
[ ] Azure


Windows 11 / VS 2022 / OF 0.12+ testing errors

Hey @Daandelange ,
I followed all the steps and created an example with PG but I am getting some unknown vars/methods...

Hey @moebiussurfing , thanks for testing so quickly ! :)
It's a bit of pseudo code indeed, and the loop was broken too.
The readme has been updated and there's an example now.
Did you get the rust library to compile on Windows ?

yes, I did all the RS command line stuff.
he only difference with the README is that I do not need to move or copy files., they were in the place already.
I just pulled + PG and got this:

Hmm... on osx I got it linking. Looks like the library is not found. I'd check in addon_config.mk, you need to define the library to link with and maybe some additional linker flags ? Maybe refer to ofxAssimp/addon_config.mk or another addon ?
Another thing to try : rust builds a static lib (osx:.a) and a dynamic lib (osx: .dylib). On osx I only use the dynamic lib because it's 500Kb vs 18Mb for the static one and it works. Try loading the static one ?

Did you try adding the ADDON_LDFLAGS line from linux64: to VS: ?
It seems to be a linker error anyways. Are there any linker warnings about bezier_rs_ffi.dll not being found ?


Add xml_tree_validations table

Pivotal story: 112939295

This PR is against import-5.0-xml-into-postgres

Yup, so it is! Looks good.


Possible breakout of implementation steps to a wiki

💡 Summary
It was under the assumption that SCB updates would be expected to undergo the CISA publication and review process for publication so a suggestion for the emerald release was to breakout the implementation steps into a wiki allowing the development team to update ad hoc.
Motivation and context
If implementation step updates require going through the CISA publication and review process, the breakout to a wiki may be able to eliminate this process for products that are continually changing.
Implementation notes

[ ] CREATE new wiki for each M365 SCB with the following:
Group Name
Policy ID
Links to associated Microsoft / External article
Implementation Steps
[ ] REMOVE All steps in implementation section
[ ] ADD link to newly created Wiki to the implementation section

Acceptance criteria
How do we know when this work is done?
See implementation notes above.

This issue seems OBE at quick glance.

closing due to issue is OBE


⚠ ClamAV has degraded performance

In 803df8d, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 65 ms

Resolved: ClamAV performance has improved in 592c856.


Camunda GraphQL Release 0.2.0

release version: 0.2.0
next dev version: 0.3.0-SNAPSHOT

0.2.0 is released, see https://app.camunda.com/nexus/content/groups/public/org/camunda/bpm/extension/graphql/camunda-bpm-graphql/0.2.0/. Should also be on Maven central after som sync time. Sorry once again for the delay.


No resource plugin 'pulumi-resource-aws' found

Hi, im pretty new with sst ion, just about a month into it. it's working fine till today. This morning when I do the  sst deploy --stage=development, I get this error:
`SST ❍ ion   ready!
➜  App:        omni-sales
Stage:      uizwmuha
~  Deploy
|  Error       default_6_47_0 pulumi:providers:aws
|  no resource plugin 'pulumi-resource-aws' found in the workspace at version v6.47.0 or on your $PATH
✕  Failed
default_6_47_0 pulumi:providers:aws
no resource plugin 'pulumi-resource-aws' found in the workspace at version v6.47.0 or on your $PATH`

UPDATE: i notice there's a problem with latest ion version 0.1.56 after the pulumi v6.47.0 update 3 days ago. we revert out ion version to 0.1.51 and everything works fine. Is it the right way to approach it?

@penzur try checking your version with sst version. I'm downgrading mine using this curl -fsSL https://ion.sst.dev/install | VERSION=0.1.51 bash.

@Firdaus-prog that's what I did. Did you make some changes to your CI/CD build config before running it with the reverted version?

This is in my pipeline:
- npm ci           - mkdir -p ~/.aws           - curl -fsSL https://ion.sst.dev/install | VERSION=0.1.51 bash           - source /root/.bashrc           - echo -e "[default]\naws_access_key_id =             $AWS_CENTRAL_ACCESS_KEY_ID\naws_secret_access_key =             $AWS_CENTRAL_SECRET_ACCESS_KEY" > ~/.aws/credentials           - echo -e "[profile ads-dev]\nrole_arn = SOMEVALUE             = default" > ~/.aws/config           - export AWS_DEFAULT_PROFILE=ads-dev           - export AWS_SDK_LOAD_CONFIG=1           - export AWS_DEFAULT_REGION=us-east-1           - sst secret set ClientId             SOMEVALUE           - sst secret set ClientSecret             SOMEVALUE             --stage=development           - sst version           - sst deploy --stage=development

I managed to avoid the issue by manually downgrading node_modules/sst-linux-x64/bin/sst to the v0.1.54 binary I downloaded from here: https://github.com/sst/ion/releases/tag/v0.1.54

Issue Fixed with ion V0.1.64


[BUG] Cant download Vids anymore

Describe the bug:
When i try to download an anime it doesnt work due to the chrome version. there is popping for a millisec the Browsertap and boom error on the cmd
Steps to Reproduce the bug:
just downland anything
Expected behavior:
Download the anime
Screenshots
Additional Info
Error:
2023-09-03 00:13:47,953: ERROR   Uncaught exception: <class 'selenium.common.exceptions.SessionNotCreatedException'> Message: session not created: This version of ChromeDriver only supports Chrome version 114
Current browser version is 116.0.5845.141 with binary path C:\Program Files\Google\Chrome\Application\chrome.exe
Stacktrace:
Backtrace:
GetHandleVerifier [0x0050A813+48355]
(No symbol) [0x0049C4B1]
(No symbol) [0x003A5358]
(No symbol) [0x003C61AC]
(No symbol) [0x003C1EF3]
(No symbol) [0x003C0579]
(No symbol) [0x003F0C55]
(No symbol) [0x003F093C]
(No symbol) [0x003EA536]
(No symbol) [0x003C82DC]
(No symbol) [0x003C93DD]
GetHandleVerifier [0x0076AABD+2539405]
GetHandleVerifier [0x007AA78F+2800735]
GetHandleVerifier [0x007A456C+2775612]
GetHandleVerifier [0x005951E0+616112]
(No symbol) [0x004A5F8C]
(No symbol) [0x004A2328]
(No symbol) [0x004A240B]
(No symbol) [0x00494FF7]
BaseThreadInitThunk [0x76747BA9+25]
RtlInitializeExceptionChain [0x77E3B7DB+107]
RtlClearBits [0x77E3B75F+191]
File "C:\Users\Lukas\OneDrive\Desktop\aniworld_scraper-V-1.8\src\start_app.py", line 168, in
captcha_link, provider = button_failsave(site_url[type], link)
File "C:\Users\Lukas\OneDrive\Desktop\aniworld_scraper-V-1.8\src\start_app.py", line 79, in button_failsave
internal_captcha_link = open_captcha_window(link_to_redirect)
File "C:\Users\Lukas\OneDrive\Desktop\aniworld_scraper-V-1.8\src\logic\captcha.py", line 41, in open_captcha_window
driver = webdriver.Chrome(service=service, options=options)
File "C:\Users\Lukas\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\selenium\webdriver\chrome\webdriver.py", line 49, in init
super().init(
File "C:\Users\Lukas\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\selenium\webdriver\chromium\webdriver.py", line 54, in init
super().init(
File "C:\Users\Lukas\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\selenium\webdriver\remote\webdriver.py", line 206, in init
self.start_session(capabilities)
File "C:\Users\Lukas\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\selenium\webdriver\remote\webdriver.py", line 291, in start_session
response = self.execute(Command.NEW_SESSION, caps)["value"]
File "C:\Users\Lukas\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\selenium\webdriver\remote\webdriver.py", line 346, in execute
self.error_handler.check_response(response)
File "C:\Users\Lukas\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\selenium\webdriver\remote\errorhandler.py", line 245, in check_response
raise exception_class(message, screen, stacktrace)
NoneType: None

I have the Cromeversion 116.0.5845.141

The Chrome devs have not yet released a Chrome Driver for this Version. This needs to be fixed by them or Selium.
You can try upgrading Selium or wait until the new Driver is out.
https://support.google.com/chrome/thread/232699038/new-chrome-version-116-0-5845-141?hl=en

@SnowSoldier03 It looks like you are using a Beta Version of Chrome or a to new not yet supported Version of Chrome.
Please either downgrade to the STABLE build of Chrome or wait until the Chrome Dev team has release a Driver for it.
See: https://googlechromelabs.github.io/chrome-for-testing/#stable

so i updated Selenium but that doesnt work.
I got this error:
2023-09-03 00:38:15,131: ERROR   Uncaught exception: <class 'selenium.common.exceptions.WebDriverException'> Message: 'chromedriver' executable needs to be in PATH. Please see https://chromedriver.chromium.org/home
I downgrade the version again. I reinstall Chrome fom the normal installer and i got the same version. Then i download the Driver from your website it says the same because its also the 116 version.

ah just forget it. I was to dump to update Selenium. I have installed an older Driver drom Selenium


chore: fixate minijinja version

Thanks. Possibly we can remove this, but possibly we'll find something useful for it too


Add pypi.org into Allow List for Nexus Firewall

Resolves #3694
Adds pypi.org into the allow list of FQDNs for the Nexus service.

/test-extended


Prevent selecting GitGutter when its loaded but not enabled

If GitGutter is loaded but not enabled, it will be selected in get_raw_hunks(), rather than another possibly loaded and enabled plugin.
I looked at adding something like sy#buffer_is_active() to GitGutter, however it seems that these two plugins differ slightly with regard to when their buffer enabled status is set. The function I came up with provided little difference to simply checking gitgutter_enabled in get_raw_hunks().
This PR allows a user to have GitGutter in their configuration, but disabled, and have a plugin with lower priority (in the if-else-if order) to provide the hunk summary (e.g. Gitsigns).

Thanks!


Implement #error preprocessor directive

Implement #error preprocessor directive. The reason not to consume #error (T_error) token on match is to avoid post side effect of lex_expect, in other word, to preseve the correct position of next_char.

Thank @ChAoSUnItY for contributing!


上一个提交写错了

Thank you for your contribution, I've published a full fix for the latest Terminus version.


Can't use tf.gradients to get the gradients of a tf.gather_np op

I wanna get the gradients of a tf.gather(params, indices) as for indices, but when I do gradients = tf.gradients(ys=out_1, xs=indices). Gradients is None.
params = tf.constant(np.array([[1,2], [3,4]]))
indices = tf.constant(np.array([[[0,0],[0,1]],[[1,1],[0,1]]]))
w = tf.constant(np.random.randn(4,3), dtype=tf.float32)
with tf.Session() as sess:
    out_1 = tf.gather_nd(params=params, indices=indices)
    print(sess.run(out_1))
    gradients = tf.gradients(ys=out_1, xs=indices)
    print(gradients)
    print(sess.run(gradients))

TypeError                                 Traceback (most recent call last)
 in ()
10     gradients = tf.gradients(ys=out_1, xs=indices)
11     print(gradients)
---> 12     print(sess.run(gradients))
C:\Users\11198\AppData\Roaming\Python\Python36\site-packages\tensorflow\python\client\session.py in run(self, fetches, feed_dict, options, run_metadata)
927     try:
928       result = self._run(None, fetches, feed_dict, options_ptr,
--> 929                          run_metadata_ptr)
930       if run_metadata:
931         proto_data = tf_session.TF_GetBuffer(run_metadata_ptr)
C:\Users\11198\AppData\Roaming\Python\Python36\site-packages\tensorflow\python\client\session.py in _run(self, handle, fetches, feed_dict, options, run_metadata)
1135     # Create a fetch handler to take care of the structure of fetches.
1136     fetch_handler = _FetchHandler(
-> 1137         self._graph, fetches, feed_dict_tensor, feed_handles=feed_handles)
1138
1139     # Run request and get response.
C:\Users\11198\AppData\Roaming\Python\Python36\site-packages\tensorflow\python\client\session.py in init(self, graph, fetches, feeds, feed_handles)
469     """
470     with graph.as_default():
--> 471       self._fetch_mapper = _FetchMapper.for_fetch(fetches)
472     self._fetches = []
473     self._targets = []
C:\Users\11198\AppData\Roaming\Python\Python36\site-packages\tensorflow\python\client\session.py in for_fetch(fetch)
259     elif isinstance(fetch, (list, tuple)):
260       # NOTE(touts): This is also the code path for namedtuples.
--> 261       return _ListFetchMapper(fetch)
262     elif isinstance(fetch, collections.Mapping):
263       return _DictFetchMapper(fetch)
C:\Users\11198\AppData\Roaming\Python\Python36\site-packages\tensorflow\python\client\session.py in init(self, fetches)
368     """
369     self._fetch_type = type(fetches)
--> 370     self._mappers = [_FetchMapper.for_fetch(fetch) for fetch in fetches]
371     self._unique_fetches, self._value_indices = _uniquify_fetches(self._mappers)
372
C:\Users\11198\AppData\Roaming\Python\Python36\site-packages\tensorflow\python\client\session.py in (.0)
368     """
369     self._fetch_type = type(fetches)
--> 370     self._mappers = [_FetchMapper.for_fetch(fetch) for fetch in fetches]
371     self._unique_fetches, self._value_indices = _uniquify_fetches(self._mappers)
372
C:\Users\11198\AppData\Roaming\Python\Python36\site-packages\tensorflow\python\client\session.py in for_fetch(fetch)
256     if fetch is None:
257       raise TypeError('Fetch argument %r has invalid type %r' % (fetch,
--> 258                                                                  type(fetch)))
259     elif isinstance(fetch, (list, tuple)):
260       # NOTE(touts): This is also the code path for namedtuples.
TypeError: Fetch argument None has invalid type <class 'NoneType'>

tf.gather_nd returns A Tensor out_1, and out_1 is not a function of indices.

If there is anyway to calculate the gradient of tf.gather_nd function?  I see there is a def _GatherNdGrad(op, grad): in https://github.com/tensorflow/tensorflow/blob/master/tensorflow/python/ops/array_grad.py#L355

@KrisHan999 This is not Build/Installation or Bug/Performance issue. Please post this kind of support questions at Stackoverflow. There is a big community to support and learn from your questions. GitHub is mainly for addressing bugs in installation and performance. Thanks!

Closing this support issue. Please post this kind of support questions at Stackoverflow. Thanks!


DNDtoggle - Initial release

The app itself seems to be working now as intended, but I am struggeling with the icon for the launcher.
Can you help me to find a conversion that works for Dark and Light mode? The icon is transparrent and basically 2 color. It always shows wrong - regardless of the settings I use in the image converter.

Hi! Sorry for the delay. For the icon, you just want this?

 But no other colors?
Or you say "2 color" - was part of the inner meant to be filled? Becayse I don't think it is in the source image.
I think in the image converter you want 1 bit black/white, transparent and also inverted (you want the image to show up as white in the preview).
Try:
require("heatshrink").decompress(atob("mEwwJC/AAl/Agf/AAUAgIFDwEHAofgh/g/0Ag/wj+AnwVB/EegEfEIN4nkAh+AgE8vgVBAoV4Aoce/EAgfADQIFcjwpFHYIFCnxBFJopZBn5ZCMopxFPoqJFSowA/gA="))

require("heatshrink").decompress(atob("mEwwJC/AAl/Agf/AAUAgIFDwEHAofgh/g/0Ag/wj+AnwVB/EegEfEIN4nkAh+AgE8vgVBAoV4Aoce/EAgfADQIFcjwpFHYIFCnxBFJopZBn5ZCMopxFPoqJFSowA/gA="))

This shows a totally white icon in light mode and a totally black icon in dark mode.
Actually I'd be totally fine if the inner of the image is also transparent. So technically the image is 1 color (black) with transparent background. The black should be shown as black in light mode and as white in dark mode.

This shows a totally white icon in light mode and a totally black icon in dark mode.
Are you sure? I just tried it in the emulator with g.drawImage(require("heatshrink").decompress(atob("mEwwJC/AAl/Agf/AAUAgIFDwEHAofgh/g/0Ag/wj+AnwVB/EegEfEIN4nkAh+AgE8vgVBAoV4Aoce/EAgfADQIFcjwpFHYIFCnxBFJopZBn5ZCMopxFPoqJFSowA/gA="))) and it seems to work ok for me? Black in the default light mode (basically using whatever the foreground color is)

I pushed the change and tried to re-load the app. Maybe something is cached somewhere.
It's hard to test for me. Can I somehow make a g.drawImage(require("heatshrink").decompress(atob( string with Windows out of a PNG? Otherwise I need to commit and push to wait until I can download the app from my app page.

You can just connect with https://www.espruino.com/ide/ and paste the code in on the left hand side?
Best to do a reset() first as since the draw call will use the current color, some other code might have set it up to something non-standard otherwise

It looks good when sending it through the ide. But the launcher icon doesn't look good though.

Ahh - I think I see what's happened - you have made a dndtoggle.img file.
Please can you just use the format that we do in the examples? https://github.com/espruino/BangleApps/tree/master/apps/_example_app
So app-icon.js and then evaluate:true: https://github.com/espruino/BangleApps/blob/master/apps/_example_app/metadata.json#L12

Great - thanks!


Merge pull request #1 from mattermost/master

Merging to Base

Summary

Ticket Link

Related Pull Requests

Has server changes (please link here)
Has redux changes (please link here)
Has mobile changes (please link here)

Screenshots

Hello @furqanmlk,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.


vtworker: VerticalSplitClone: Error when --tables is not set.

@alainjobart
And here I was, wondering why the diff fails complaining that no tables are set in the SourceShard record :)

LGTM


#2480 PDF viewer highlighted text color

I've made the appropriate CSS changes in the viewer-overrides.css. Here is the snapshot of what it looks like.

@ppatel221 this seems to have a lot of extra changes in it (mostly string changes) that mean you need to rebase.  Can you try this please:
# start by updating your local `master` branch
git checkout master
# assuming your git remote for mozilla/brackets is called `upstream`
git pull upstream master
# now rebase this branch on the updated master
git checkout PDFchange
git rebase master
# if this produces errors you don't understand, roll it back with `git rebase --abort`
# otherwise, push it up to GitHub like this:
git push origin PDFchange --force

This should mean that all the extra changes you have in this commit get removed.  If you have trouble getting this to work, let me know and I'll help you, and/or do it in class to show other students how to cope with this situation.

When I run your git commands, It tells me that everything is up to date. I've committed the new CSS changes.


Press Freedom Analysis

ML-Crate Repository (Proposing new issue)
:red_circle: Project Title : Press Freedom Analysis
:red_circle: Aim : Analyse the freedom of press in different aspects.
:red_circle: Dataset : https://www.kaggle.com/datasets/mfaaris/press-freedom-index-and-abuse
:red_circle: Approach : Try to use 3-4 algorithms to implement the models and compare all the algorithms to find out the best fitted algorithm for the model by checking the accuracy scores. Also do not forget to do a exploratory data analysis before creating any model.

📍 Follow the Guidelines to Contribute in the Project :

You need to create a separate folder named as the Project Title.
Inside that folder, there will be four main components.

Images - To store the required images.
Dataset - To store the dataset or, information/source about the dataset.
Model - To store the machine learning model you've created using the dataset.
requirements.txt - This file will contain the required packages/libraries to run the project in other machines.

Inside the Model folder, the README.md file must be filled up properly, with proper visualizations and conclusions.

:red_circle::yellow_circle: Points to Note :

The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include issue number along with it.
Follow Contributing Guidelines & Code of Conduct before start Contributing.
This issue is only for 'SWOC' and 'JWOC' contributors of 'ML-Crate' project.

:white_check_mark: To be Mentioned while taking the issue :

Full name :
GitHub Profile Link :
Participant ID (If not, then put NA) :
Approach for this Project :
What is your participant role? (Mention the Open Source Program name. Eg. HRSoC, GSSoC, GSOC etc.)

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

Full name : Astha Samaddar
GitHub Profile Link : https://github.com/Asttttha
Participant ID (If not, then put NA) : NA
Approach for this Project : To analyse various columns of this dataset.
What is your participant role? HRSoC 2022 Participant

Hey Astha, thanks for choosing ML-Crate. Issue assigned to you :rocket:

Updates please @Asttttha

Updates please @Asttttha

Still working on it

Okay. Carry on 🚀 @Asttttha

Please complete the issue before the deadline @Asttttha

Great one to work on. Issue assigned to you @Shruti1921. Go ahead!

Issue has been un-assigned from you due to inactivity.
@Shruti1921

Full name : Swadhin Satyaprakash Majhi
GitHub Profile Link : https://github.com/swadhin1237
Participant ID (If not, then put NA) : NA
Approach for this Project : To analyse the dataset and make proper EDA with visualization.
What is your participant role?KWOC 22 participants.

Issue assigned to you @swadhin1237


Can I create multiple pages using some class?

This is page 1

This is page 2

Yes. If you use fromHTML or you write your own domparser


avoid updating text node if value is the same after converting to a string

On this example, the node flashes on the dev tools because its failing the equality check, as whats on the dom is a string and the new value is a number https://playground.solidjs.com/anonymous/abf375c1-7f30-4d09-bf19-e543a5681e70
quoting from a discord message

That's happening because it's failing this triple equality check https://github.com/ryansolid/dom-expressions/blob/main/packages/dom-expressions/src/client.js#L409 , as what's rendered is the 0 string and the new data is 0 the number. It's then converted to a string https://github.com/ryansolid/dom-expressions/blob/main/packages/dom-expressions/src/client.js#L416
but then it's not compared when updating on this case https://github.com/ryansolid/dom-expressions/blob/main/packages/dom-expressions/src/client.js#L425C26-L425C41
If you convert it to a string on the neutralizeCount call it stops flashing on the dev tools https://playground.solidjs.com/anonymous/cadbf84e-aef3-4a19-9b99-f0b6434e2725

Thanks


[W4.4b][W09-A2]Ow Zhen Wei

Split class Address into more classes.

Good job on completing the activity.
Some comments added. Please close the PR after reading the comments.


chore(nix): update inputs

[X] I have read CONTRIBUTING.md and CODE_OF_CONDUCT.md
[ ] I have added to CHANGELOG.md relevant changes and any other user facing change
[ ] I have added or ran the appropriate tests

What this PR does / why we need it:
Updates the nix lock. Needed for the newer elixir and erlang versions defined in the .tool-versions
Which issue(s) this PR fixes:

Special notes for your reviewer:
Does this PR introduce a user-facing change?

[ ] Yes
[X] No

Additional documentation e.g. usage docs, diagrams, etc.:

I've also added the flake-utils input override to clean up the lock file a bit


Fix bug with DM Sans weights & update readme

Fix bug in font weight
https://github.com/Afordin/hackafor-2/issues/20

Add images to readme

Remove Remove h-[100vh]

This is amazing! LFG!! 😁


Slow generation on long input context

Hi @casper-hansen, I known large batch will decrese the performance. Recently I found that long input context will also meet a performance bottleneck(test with vLLM), but only for the first generate token, the speed of following output tokens is normal and faster than FP16, is this because the implementation of GEMM is slow with long context?

I am not sure what is causing this. You should warm up the GPU if you can. See the benchmarks in the README, they indicate fast context processing

I think is not because warm up, because it will happen in every request.

FP16 can be faster for prefilling, so this is not unusual. INT4 is faster during decoding if batch size is not too large

Why FP16 is faster for prefilling, is this because the de-quantize introduce an extra time cost? Does this mean vLLM will de-quantize INT4 on prefill phase, then decode just re-use the de-quantized weights?
I'm not familiar with CUDA, apologize if this problem is obvious.

FP16 is faster for large context and large batch sizes. vLLM uses the AWQ kernel which dequantizes the model weights every time you prefill and decode. You cannot reuse the dequantized weights because then you would be storing FP16 weights, which then uses a lot of memory.

This make no sense that FP16 will faster than INT4 as dequantization will happen in every forward. INT4 is fast in decoding phase, and after dequantize the computing should be same of FP16 and INT4, while dequantizing is a fixed time cost, then what make the slow down in prefilling phase?


Discovery service returns no results for long-tail questions sent from Conversation service

Hello,
I have run into an issue - Discovery service not returning results for long-tail questions.
After deploying this application on Bluemix, following the delpoyment instructions, the answer for "How do I check my tire pressure" is "That question is out of scope for this application, take a look at the Conversation Enhanced application to handle questions like these.", which is not expected. Doing a direct query on the Discovery service returns relevant results from the car manual
Also, when asking the same question on the official application page (at http://conversation-with-discovery.mybluemix.net/dist/index.html) the answer is "Great question. I found some ideas for you:", followed by relevant sections from the car manual.
The value for "CEPayload" (on the right pane, "Watson understands" section) is empty in the first case (the application deployed on my Bluemix account) and contains the relevant sections from the car manual in the second case (official website).
Please see attached screenshots below.

Thank you.

I have exactly the same issue.
Did you find the cause?
David

Hi David,
I found the cause:
The actual query sent to Discovery service is: "searchText:, enrichedText:"
see the project code: at DiscoveryQuery.query(String userQuery) at lines:
        sb.append("searchText:");
        sb.append(userQuery);
        sb.append(",");
        sb.append("enrichedText:");
        sb.append(userQuery);

Executing that exact query directly on the Discovery service will not return any results either. For some reason the "enrichedText" field is not added to the processed JSON collection.
Hope this helps,
Alex

If your docs are not well trained, or the question gets extremely low confidence returned, discovery will not send any results, thus none will be showed. we should write additional code to handle that scenario.
other htan that, looks like Alex found the issue already.

Might you suggest an actual solution?


[v0.9] Fix map errors during kernel loading

Don't error if a kernel page is already mapped to the correct frame
Fix: unmap temp page again to enable multiple bss-like sections

Published as v0.9.26


Event counters generate a lot of active time series

Microsoft.ApplicationInsights.AspNetCore (2.14.0)
Microsoft.ApplicationInsights.Kubernetes (1.1.2)
netcoreapp3.1
Kubernetes, Linux

What are you trying to achieve?
Lately, we noticed that some metrics we were sending to our Application Insights instance were getting dropped. We opened a support ticket on Azure and it turned out that we were exceeding the quota for active time series per subscription/region. While trying to identify the list of problematic metrics, I noticed that most entries listed by running this query:
customMetrics
were default event counters. I then ran the following query:
customMetrics
| where name == "System.Runtime|Gen 0 GC Count"
| project name, interval=parse_json(customDimensions)["AggregationInterval"]
| distinct tostring(interval)

and I got ~2800 results in the last 12 hours. Here's a sample of the values:

59.99983596801758
59.99934387207031
59.991455078125
60.0001335144043
59.999576568603516
59.999366760253906
60.00034713745117

Based on my current understanding of what is a time series:

An active time series is defined as any unique combination of metric, dimension key, or dimension value that has had metric values published in the past 12 hours.

Does this mean there are 2800 active time series for that single metric? Is there a known way to circumvent this issue. We currently have ~30 services that are all sending their telemetry to the same ApplicationInsights instance so if my hypothesis is correct, the time series are adding up quickly.
What have you tried so far?
To circumvent the issue, I'm planning to add a custom telemetry processor that will round up the AggregationInterval dimension. This way, it will generate a single time series per metric and we're not really using that dimension right now, so we don't really care if the value is rounded up.

This is an in EventCounter collection module.

Starting with 2.15.0-beta3, no counters are collected by default. User has to opt-in to get any counters.
Yes, we need to remove high cardinality duration from the dimension. Will try to address this for 2.15 itself.
You workaround of rounding up should work. There is no strong reason to have this duration added - all metrics are aggregated with 1 min interval, and there is no option to customize it. So one can always assume the aggregation interval is 1min. The actual value may drift slightly from exact 60 sec, which caused huge # of time series.


Add otadump

Description of changes
It helps to extract partitions from Android OTA files (payload.bin) like payload-dumper-go.
I removed the static feature of the rust-lzma crate since the author used it to build universal binaries using musl.
The binary works in nix-shell --pure -p too but I'm hoping someone with more experience can tell me if lzma needs to be added to propagatedBuildInputs or something.
https://github.com/crazystylus/otadump
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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
[x] 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.

@Aleksanaa  You're the maintainer of payload-dumper-go. Can you help review this PR?

@ofborg build otadump


Ability to specify the latest release version on cli

This would be similar to the --package flag, only, instead of using the version from package.json, the version would be specified explicitly.  Use case is that I'm maintaining a bunch of non-Node.js projects and want to avoid the additional commit of the CHANGELOG.md modification.  I guess I could create a dummy package.json file, but that smells funky, and I would think the addition of the cli flag would be fairly straightforward.  Thoughts?

I guess the other benefit of using package.json is that we get an easy way of setting the other options...  The current functionality will definitely work for us, not sure how other people feel.

Yeah I like the idea, although it could become messy – If you forget to tag the repo with the same version that you specify, that version will just get lost in the next run. Maybe that's ok just to leave up to the user to manage.

True, trying to get this working in our version/build/deploy workflow.  I'll hold off on any more suggestions until I've actually used it a bit more :)

--latest-version option added in 1.3.0 👍


blinking icons on position update

I don't know if anyone has this experience so this is more like a question, than an issue.
I have a interval in angular that is requesting the positions to the API, on every update, the icons blink or flicker.. any suggestions?
regards,
Ricardo

trackBy resolved my flickering problem as well.


Completion block called asynchronously when image is in memory cache

New Issue Checklist

[X] I have read and understood the CONTRIBUTING guide
[X] I have read the Documentation
[X] I have searched for a similar issue in the project and found none

Issue Info

Info
Value

Platform Name
iOS

Platform Version
11.1

SDWebImage Version
4.2.1

Integration Method
cocoapods

Xcode Version
Xcode 9.1

Repro rate
100%

Issue Description and Steps
Memory cache enabled.

Load image from network
Load it again

Observed:
For blink of an eye placeholder is visible
Expected:
After calling sd_setImage if image is in memory cache, completion block should be called in same run loop.
After some investigation I think issue is in this file:
UIView+WebCache.m
dispatch_queue_t targetQueue = shouldUseGlobalQueue ? dispatch_get_global_queue(DISPATCH_QUEUE_PRIORITY_HIGH, 0) : dispatch_get_main_queue();

dispatch_async(targetQueue, ^{
     [sself sd_setImage:targetImage imageData:targetData basedOnClassOrViaCustomSetImageBlock:setImageBlock];
     dispatch_main_async_safe(callCompletedBlockClojure);
});

for example when commenting out first dispatch_async, all works as expected.
dispatch_queue_t targetQueue = shouldUseGlobalQueue ? dispatch_get_global_queue(DISPATCH_QUEUE_PRIORITY_HIGH, 0) : dispatch_get_main_queue();

// dispatch_async(targetQueue, ^{
     [sself sd_setImage:targetImage imageData:targetData basedOnClassOrViaCustomSetImageBlock:setImageBlock];
     dispatch_main_async_safe(callCompletedBlockClojure);
// });

Maybe I am missing something but one solution I see is to not double dispatch it:
// Just store final block that later will be either dispatched or just executed
 void (^completionBlock)(void) = ^{
     [sself sd_setImage:targetImage imageData:targetData basedOnClassOrViaCustomSetImageBlock:setImageBlock];
     dispatch_main_async_safe(callCompletedBlockClojure);
};

 if (shouldUseGlobalQueue) {
     dispatch_queue_t targetQueue = dispatch_get_global_queue(DISPATCH_QUEUE_PRIORITY_HIGH, 0);
     dispatch_async(targetQueue, ^{
          completionBlock();
     });
} else {
     completionBlock();
}

Worth to mention I was not testing it with GIF images (only place when shouldUseGlobalQueue is true). I am not sure if in any case we should push completion in the next run loop when image is already in memory.

Maybe this is true. This code was changed during last 4.2.0 refactor which increase the GIF performance by moving set-image-block to global queue. But at that time we didn't find this internal changes to queue order.(We dispatch that queue instead of check current thread) This should be changed to this:
            if (shouldUseGlobalQueue) {
                dispatch_async(dispatch_get_global_queue(DISPATCH_QUEUE_PRIORITY_HIGH, 0), ^{
                    [sself sd_setImage:targetImage imageData:targetData basedOnClassOrViaCustomSetImageBlock:setImageBlock];
                    dispatch_main_async_safe(callCompletedBlockClojure);
                });
            } else {
                dispatch_main_async_safe(^{
                    [sself sd_setImage:targetImage imageData:targetData basedOnClassOrViaCustomSetImageBlock:setImageBlock];
                    callCompletedBlockClojure();
                });
            }

@pmiaskiewicz Please have a look at this #2093

Fixed by #2093

I found when we use the FLAnimateedImageView which enable shouldUseGlobalQueue by default still cause imageview blink and flash when tableview/collection reload. especially obviously in iOS9. I thought it's bette to make it user configurable.

@yichengchen Could you please create another issue and provide a little demo. I think maybe we enter something wrong with last performance enhancement.

@dreampiggy I have create issue here #2102


Roidmi Vacuum v60 (EVE PLUS)

Good afternoon, I connected my Roidmi EVE Plus vacuum cleaner, and without MiCloud connected, it refused to work at all, after connecting MiCloud, the vacuum cleaner can only turn on, it cannot turn off. The status of the vacuum cleaner at the charging station does not work - it always shows "no".

Hi, what is the model of your device?

model roidmi.vacuum.v60

I see that this model is not yet fully supported so proper support needs to be added. You could temporarily try to use model roidmi.vacuum.v6 as the model and see if that helps.

Ah, sorry, I thought it was the same model

if you use the roidmi.vacuum model.v6, controls are not displayed.

In that case you need to wait for proper support for your device.

Oh, somehow i mistook here. I see that the v60 is already supported so it should actually work (not sure how i missed that, sorry...)

homebridge.log.txt
Good afternoon, the token is correct, I choose the automatic search for a vacuum cleaner, attach the log.

homebridge.log (1).txt

Hi, from the second log it seems that everything is fine. The properties are syncing and the one error which appears should not cause any issues.


Added fetchOptions as param

With this code, developers can init the library with a PHFetchOptions configuration.
By doing that they will have the power to restrict the images shown by date for example.
let fromDate = Calendar.current.date(byAdding: dateComponent, to: Date())!
let toDate = Calendar.current.date(byAdding: dateComponent, to: Date().addingTimeInterval(5.0 * 60.0))!
let options = PHFetchOptions()
options.predicate = NSPredicate(format: "creationDate > %@ && creationDate < %@", fromDate as CVarArg, toDate as CVarArg)

 //Just a way to set order
let sortDescriptor = NSSortDescriptor(key: "creationDate", ascending: true)
options.sortDescriptors = [sortDescriptor]

var config = YPImagePickerConfiguration()
config.screens = [.library]
config.library.mediaType = .photo
config.library.onlySquare  = false
config.library.minNumberOfItems = 1
config.library.maxNumberOfItems = 10
config.albumName = "Nightlog"

let picker = YPImagePicker(configuration: config, options: options)
picker.imagePickerDelegate = self

Hi @mdb1,
First of all, thanks a ton for taking the time to contribute, this is really appreciated 👏
Secondly, I really like the idea of having custom predicates to fine tune even further what the library displays, very powerful!
I have just one point to discuss.
Is there a specific reason for using a separate "options" param?
I'd suggest we put that in the library section of the YPImagePickerConfiguration struct.
The usage would be the following:
// Only show library pictures from the last 3 days
let threDaysTimeInterval: TimeInterval = 3 * 60 * 60 * 24
let fromDate = Date().addingTimeInterval(-threDaysTimeInterval)
let toDate = Date()
let options = PHFetchOptions()
options.predicate = NSPredicate(format: "creationDate > %@ && creationDate < %@", fromDate as CVarArg, toDate as CVarArg)

//Just a way to set order
let sortDescriptor = NSSortDescriptor(key: "creationDate", ascending: true)
options.sortDescriptors = [sortDescriptor]

var config = YPImagePickerConfiguration()
// ...
config.library.options = options

let picker = YPImagePicker(configuration: config)

Indeed we ideally want to keep every customisation point via the configuration struct.
Hope this makes sense :)
PS: Here is the diff attached if you want to apply this modification:
diff.txt
Cheers,

@s4cha Thanks for the feedback and the time to review the PR. I have applied the diff and I think that now the code is more simple.

Awesome! 🚀

Where is the documentation on this? I need to sort by modification date


The payload includes keys that are usually numeric, but are sometimes null.

I now have new issue, however.  The payload includes keys that are usually numeric, but are sometimes null.  In this example printTime, printTimeLeft, and others are initially null before the print physically begins, after which they become real numbers.
Example payload:
{"_timestamp":<PHONE_NUMBER>, "progress": 0, "printer_data": {"progress": {"completion": null, "printTimeLeftOrigin": null, "printTime": null, "printTimeLeft": null, "filepos": null}, "state": {"text": "Operational", "flags": {"cancelling": false, "paused": false, "operational": true, "pausing": false, "printing": false, "resuming": false, "sdReady": true, "error": false, "ready": true, "finishing": false, "closedOrError": false}}, "currentZ": null, "job": {"averagePrintTime": null, "lastPrintTime": null, "user": "pi", "file": {"origin": "local", "name": "tray_sm_0.2mm_PLA_MK3S_7h4m-TEST-2.gcode", "date":<PHONE_NUMBER>, "path": "tray_sm_0.2mm_PLA_MK3S_7h4m-TEST-2.gcode", "display": "tray sm_0.2mm_PLA_MK3S_7h4m-TEST-2.gcode", "size": 7046139}, "estimatedPrintTime": 15356.916729460274, "filament": {"tool0": {"volume": 99.13513212812876, "length": 41215.598529984934}}}, "offsets": {}}, "location": "local", "path": "tray_sm_0.2mm_PLA_MK3S_7h4m-TEST-2.gcode"}

Error message:

Traceback (most recent call last):
  File "plugin.py", line 115, in runConcurrentThread
  File "plugin.py", line 139, in processMessages
  File "plugin.py", line 734, in update
TypeError: state value type must be bool, int, real, or string

   MQTT Shims Error                plugin runConcurrentThread function returned or failed (will attempt again in 10 seconds)

Could these states remain blank or zero when null?
Originally posted by @kmarkley in https://github.com/FlyingDiver/Indigo-Shims/issues/15#issuecomment-674453511

What's the payload look like when a print is in progress.

Payload while printing:
{"_timestamp":<PHONE_NUMBER>, "progress": 0, "printer_data": {"progress": {"completion": 0.4091744429112171, "printTimeLeftOrigin": "analysis", "printTime": 1, "printTimeLeft": 15355, "filepos": 28831}, "state": {"text": "Printing", "flags": {"cancelling": false, "paused": false, "operational": true, "pausing": false, "printing": true, "resuming": false, "sdReady": true, "error": false, "ready": false, "finishing": false, "closedOrError": false}}, "currentZ": null, "job": {"averagePrintTime": null, "lastPrintTime": null, "user": "pi", "file": {"origin": "local", "name": "tray_sm_0.2mm_PLA_MK3S_7h4m-TEST-2.gcode", "date":<PHONE_NUMBER>, "path": "tray_sm_0.2mm_PLA_MK3S_7h4m-TEST-2.gcode", "display": "tray sm_0.2mm_PLA_MK3S_7h4m-TEST-2.gcode", "size": 7046139}, "estimatedPrintTime": 15356.916729460274, "filament": {"tool0": {"volume": 99.13513212812876, "length": 41215.598529984934}}}, "offsets": {}}, "location": "local", "path": "tray_sm_0.2mm_PLA_MK3S_7h4m-TEST-2.gcode"}

Fixed in 0.3.6, I think.

https://github.com/FlyingDiver/Indigo-Shims/releases/tag/0.3.6


Add support for "tools only" build

For use with Muen where we need a solo5-elftool around, add support for a "tools only" build and install via ./configure.sh --only-tools and make install-tools.
/cc @Kensan

LGTM, works as advertised :)


Ability to Edit Town Ordinances

While @Slattz and I were looking at how Town Ordinances are set, I discovered that you could set multiple Town Ordinances at once. I'll give a brief explanation on how Town Ordinances work:
Offset 0xXXXCF contains the currently enabled ordinance flags. Specifically bits 1-4 (where 0 and >4 are used for something else).
Offset 0xXXXD1 contains the flag saying that a Town Ordinance change has been scheduled for that day (bit 4, 0x10). We don't really care about this flag, but if it's enabled, the player will not be able to change their Town Ordinance until the next day.
Offset 0xXXXD3's upper nibble contains the current town ordinance. 0x00 = Early Bird, 0x10 = Night Owl, 0x20 = Bell Boom, 0x30 = Keep X Beautiful. 0x40 means there is no ordinance in effect. The game uses this value to set 0xXXXCF on every new day. This includes both days where the ordinance has been changed, and days it hasn't. Setting this byte to 0x70 stops the game from updating 0xXXXCF, effectively locking in the ordinance flags there.
In conclusion, we're able to enable up to all four Town Ordinances (Early Bird overwrites Night Owl's effects if they're both enabled) at once. Then, by setting 0xXXXD3's upper nibble to 0x70, we freeze those values in place.
EDIT: I forgot to mention, when multiple ordinances are enabled, Isabelle will say that the last ordinance in the checkbox order is in effect currently. Example: Both Bell Boom & Keep X Beautiful ordinaces are enabled, Isabelle will say that "Keep X Beautiful" is the active ordinance. Despite what she says, the others are still enabled.
I added the checkboxes under the Other tab. I'm not sure if the design is acceptable, so you may want to review it. Here's a preview in Chrome:

Perhaps a radio button should be used for 'Early Bird' and 'Night Owl' instead since they don't work together? Or perhaps a warning or something?
Otherwise people will be confused and wondering why Night Owl doesn't work while Early Bird is on :sweat_smile:

A notification alert will now be shown when both are checked. It notifies the user that Early Bird will override Night Owl when they are both enabled.

I'll merge this as soon as possible :-)

@marcrobledo Any updates on this pull request?

Sorry guys, I was working on a big update for the editor. That's why I decided to put off your pull request until my update was ready. However, after a few months without working on this, today I wanted to resume my work and I had a lot of trouble to catch up, it's been a while since I left ACNL hacking.
Anyway, I decided to revert back to the old version (and promised myself not to touch this project anymore, unless it's needed). So I merged your pull request. Thanks a lot :-)
I'm also going to add a few features from the abandoned update, which will probably be my latest addition here.


add hint for inverted hip servos to servo calibration documentation

Add hint for inverted hip servos to calibration procedure
Closes #49

Looks good, thanks.


[BUG]AutoTrain advanced CLI: error: unrecognized arguments: --output

Prerequisites

[X] I have read the documentation.
[X] I have checked other issues for similar problems.

Backend
Local
Interface Used
CLI
CLI Command
autotrain dreambooth --model "stabilityai/stable-diffusion-xl-base-1.0" --output "E:/autobooth/model" --image-path "C:/Users/imacs/Pictures/ai/New folder" --prompt "photo of fadhil" --resolution 1024 --batch-size 1 --num-steps 500 --fp16 --gradient-accumulation 4 --lr 1e-4 --project-name "fadhil"
UI Screenshots & Parameters
No response
Error Logs
usage: autotrain  []
AutoTrain advanced CLI: error: unrecognized arguments: --output E:/autobooth/model
Additional Information
I am currently using Python 3.10.6, was able to install everything.
I am following this specific tutorial : https://www.youtube.com/watch?v=gF078Lhnr94&t=894s
and was unable to proceed using the arg "--output", is there a new way that i am not aware of to pass on the argument to output the trained model?
if i dont use "--output" arg in the CLI command, how do i reuse or locate the trained model (where is it saved by default)? Thanks in advance.

many arguments change from time to time. you need the same version in the tutorial (not recommended) or use the modified arguments. please see colab links in readme and other issues. this has been mentioned quite a few times btw :)
use autotrain dreambooth --help to get new arguments.


Stop nscd by default

https://bugs.launchpad.net/kolla-ansible/+bug/1680139

nscd is now stopped by default in the cookie cutter.


Autorest Regen Preview to 3.0.0-alpha.20231201.3 by Dapeng Zhang from refs/pull/3996/merge

Triggered from https://github.com/Azure/autorest.csharp/pull/3996

API change check
API changes are not detected in this pull request.