fix: [CDS-101927]: Removed Skip

Title: Remove Test Project Dependency
Summary:
Remove Test Project Dependency
Testing Instructions:
Describe how the changes were tested. Include any test cases or steps to verify the functionality.
Please include the below test scenario with your changes.

Create the resource and execute terraform apply. (Verify the resource is created)
Execute terraform apply again without any changes. (Verify no changes should be done)
Update the resource and execute terraform apply. (Verify the resource updated successfully)
Remove the content from resource file and execute terraform apply. (Verify the resource has been deleted)
Add again the resource and execute the terraform apply. (Verify the resource is created)
Verify the import the resource file is working fine.
In case of remote entity, Verify for both default and non default branch.

Screenshots:
Include before and after screenshots to visually demonstrate the changes.
Checklist:

[x] Code changes are well-documented.
[x] Tests have been added/updated.
[x] Changes have been tested locally.
[ ] Documentation has been updated.

PR Check triggers

Build: trigger build
Sub Category Field Check: trigger subcategoryfieldcheck
gitleaks: trigger gitleaks


Can't cancel plugins that are not using the provided request method

Platform: macOS 10.13
Kap Version: 2
Steps to reproduce
Install Kap Cloudinary Plugin and when exporting using that, try to cancel the export.
Current behaviour
Cancel button does not do anything or throws an error.
Expected behaviour
The export should be canceled.

Currently only the plugins that are using the provided context.request() method can be canceled. Otherwise the plugin itself should be using a cancelable promise instance.

Fixed via #494


feat: added get all keys feature

I added a new API to the store: getAllKeys. It returns the exiting keys for the partition.
Added impl, unit tests, e2e, docs.
Motivation and Context
We use aio-state-lib for Adobe's AEM Screens Cloud. We need to get all stored keys.
Jira story: http://jira.corp.adobe.com/browse/SCRNS-1287
How Has This Been Tested?
Added e2e test that passes. Used an AIO runtime namespace
Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have signed the Adobe Open Source CLA.
[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

Thanks for this complete PR, @danielbatica ! We'll review next week, stay tuned.

I'm not working on this code but I have alarms go on when I see a getAllSomething method that doesn't set limits on the number of items returned ;-)
What if you have a hundred million keys?
I think the method should either implement some form of paging for the results, or at least set a limit on the size of the array returned.

I'm not working on this code but I have alarms go on when I see a getAllSomething method that doesn't set limits on the number of items returned ;-)
What if you have a hundred million keys?
I think the method should either implement some form of paging for the results, or at least set a limit on the size of the array returned.
Makes sense, It would be easy if the underlying cosmosdb would provide that since this is just a wrapper.

Hi @danielbatica , we've been discussing your PR and we'll keep it on hold for now: we have indeed a very similar PR from @sandeep-paliwal which had been deferred, for the following reasons:

We want to be cautious about what and how we expose in terms of security, runtime performance and costs. For the two last items, this kind of operation run against a large set of States can be very impactful for all users, as we do share a single storage and RUs for all underlying namespaces.

We consider an abstracted search with pagination as an alternative, with restrictions on what can be searched and how

We want the abstraction to be provider agnostic to preserve the Bring Your Own Storage paradigm possible (e.g. and let developers bring a DynamoDB instance or other if needed)

Nevertheless this feature is frequently asked by our users. As an immediate next step, @sandeep-paliwal will go through a usage analysis of our OOTB storage so that we could assess the possible impact as early mentioned.
We'll keep you in the loop and follow-up with you to enhance your PR according to our feedback.
cc @sarahxxu for her additional input

closing as this is implemented in the new State majors (> v4). Legacy State users can refer to this PR to manually implement listing.


Add new markets

use official markets list form https://rss.itunes.apple.com

I don't think this works, the numerical market header is used to populate the X-Apple-Store-Front headers when requesting itunes.

@facundoolano It works without headers for app reviews
https://itunes.apple.com/us/rss/customerreviews/page=1/id=284815942/sortby=mostrecent/json

The markets constant you modified it's not used in that url, it's used for other requests. Also there's no point to map two letter country to country name; the reviews requests use two letter codes directly.


How about use Kaminari limit_value for X-Per-Page?

from the source code i see that now we return X-Per-Page with data params[:per_page].to_s, how about use Kaminari's limit_value instead?
header "X-Per-Page",    data.limit_value.to_s

Is there any real difference? (Some edge cases maybe?)

when input per_page is not provided, params[:per_page] is nil, but limit_value is the actual value used by kaminari.

Yep, I saw the explanation in PR. Merged already, I just need to release a new version. Thanks!


Conflict with [FrameworkBundle] Added Crontoller::isCsrfTokenValid [SF 2.6.0]

AdmingeneratorGeneratorBundle / Resources / templates / CommonAdmin / csrf_protection.php.twig
cf : https://github.com/symfony/symfony/commit/479c83351cc1ef390ad46787a68e526f50f1c961

@sescandell @loostro What need csrf_token.php.twig to look like? Is there a base template to inherit from? I couldn't find one.
I'm in need of upgrade to sf2.6 but the AdminGeneratorBundle causes trouble.

@robertfausk see this changelog

Yeah, I already did. But I have no luck with overriding.
I placed this
{% block csrf_protection_use %}
use Symfony\Component\Security\Core\Exception\InvalidCsrfTokenException;
{% endblock %}

{% block csrf_check_token %}

    /**
     * Check crsf token provided for action
     *
     * @throw InvalidCsrfTokenException if token is invalid
     */
    protected function isCsrfTokenValid($intention)
    {
        $token = $this->getRequest()->request->get('_csrf_token');
        if (!$this->get('form.csrf_provider')->isCsrfTokenValid($intention, $token)) {
            throw new InvalidCsrfTokenException();
        }
    }

{% endblock %}

{% block csrf_action_check_token %}
// Check CSRF token for action
$intention = $this->getRequest()->getRequestUri();
$this->isCsrfTokenValid($intention);
{% endblock %}

{% block csrf_action_check_batch_token %}
// Check CSRF token for batch action
$intention = '{{ namespace_prefix }}_{{ bundle_name ~ (builder.BaseGeneratorName ? '_' ~ builder.BaseGeneratorName :'')}}_batch';
$this->isCsrfTokenValid($intention);
{% endblock %}

in app/Resources/AdmingeneratorGeneratorBundle/templates/CommonAdmin/csrf_protection.php.twig but it doesn't override the template.
I had also no luck with app/Resources/Admingenerator/GeneratorBundle/templates/CommonAdmin/csrf_protection.php.twig like you suggested in https://github.com/symfony2admingenerator/AdmingeneratorGeneratorBundle/issues/789#issuecomment-58965290

Hi @robertfausk
Actually to "override" a template you need to add your "templates" directory as a config parameter. Take a look to the param templates_dirs https://github.com/symfony2admingenerator/AdmingeneratorGeneratorBundle/blob/master/DependencyInjection/Configuration.php#L72

@sescandell Thank you very much. I got it now.
Additionally I had to create one emtpy dir named Doctrine (or DoctrineODM or Propel) to get it working.
Also see doc: https://github.com/symfony2admingenerator/AdmingeneratorGeneratorBundle/blob/master/Resources/doc/cookbook/extending-generator-templates.md

You're right... I forget to mention this.

@robertfausk Exactly the reason I've written that documentation: A long time ago I had the same problem ;)

Hello I am trying to edit the templates, i have a SF 2.6, Here is my directory

app
     Resources
          Admingenerator
               GeneratorBundle
                    templates
                         CommonAdmin
                              *templates*
                         Propel

And on my config:
templates_dirs: ["%kernel.root_dir%/../app/Resources/AdmingeneratorGeneratorBundle/templates" ]
Can someone explainme why this does not work properly.

@fjbatresv if you are working on Windows, add a file in your Propel directory (even if it is empty), and it should work.

@sescandell I am working on a linux distibution and this  doesnt work.

OK...
I think this is because of your path. You should use this:
templates_dirs: ["%kernel.root_dir%/../app/Resources/Admingenerator/GeneratorBundle/templates" ]

I think with Symfony 2.7.* this doesn't work any more :(
This is my folder structure:
app
 Resources
  Admingenerator
   GeneratorBundle
    templates
     CommonAdmin
      csrf_protection.php.twig (with proper content)
     Doctrine
      .gitkeep

And my config.yml
admingenerator_generator:
    [...]
    templates_dirs: [ "%kernel.root_dir%/../app/Resources/templates" ]

Am I doing something wrong here?

@sebastianlp Check if you made every step as described here.
Futhermore, the fix is, if I'm correct, now being developed in the newer version of the Bundle (see here. So, it might actually be time for you to update to the new bundle, also to benefit for new functions.

@sebastianlp
Your path should be "%kernel.root_dir%/../app/Resources/Admingenerator/GeneratorBundle/templates"

@bobvandevijver , @sescandell
Yeah, I forgot to update the answer. I'm using:
admingenerator_generator:
    templates_dirs: [ "%kernel.root_dir%/../app/Resources/Admingenerator/GeneratorBundle/templates" ]

and this is my folder structure:

Thank you guys

In te docs the directory is mentioned as AdmingeneratorGeneratorBundle, so without the extra subdir per Symfony convention. I also have that and it works, so you could try that.

OK... I'll make a test on the demo project moving on sf2.7 and let you know.

@bobvandevijver Thank you. I tried both paths, that one in the image and what you mention in the last comment, both with error.
@sescandell Thank you, if it's more convenient to you, I can upload my project

Working on it.
I'll probably be able to provide you a response tomorrow


2023 Ford Explorer Platinum Update fingerprints.py

Ford 2023 Explorer Platinum Fingerprint Update

What's your dongle ID?

Dongle ID is
a1c474db2493d38e

@incognitojam this car had a route where the camera didn't respond to the Ford query, but it did the Mazda query:
                         {'address': 1798,
                          'brand': 'mazda',
                          'bus': 0,
                          'ecu': 'fwdCamera',
                          'fwVersion': b'LB5T-14F397-AF\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00',
                          'logging': True,
                          'obdMultiplexing': True,
                          'request': [b'"\xf1\x88'],
                          'responseAddress': 1806,
                          'subAddress': 0},

If you tell me which route I can tell you if there was anything different about that trip.  Is it only one route that is different or are there multiple ones?
In the past week or so I switched from Openpilot to Frogpilot; might that result in what you are observing?

I'm not sure. The Mazda query is the same as the Ford query, just without the tester present message. I believe the CAN FD Fords see the same thing (although the cause is probably not the same there).


Feature request: Avoid flushing metrics when no metrics to flush

Use case
We are using
    "@middy/core": "^4.0.2",
    "@aws-lambda-powertools/metrics": "^1.0.1",

Metrics with this setup:
const log = new Logger({
  // POWERTOOLS_LOG_LEVEL environment variable sets log level
  serviceName: config.serviceName,
  persistentLogAttributes: {
    release: config.releaseVersion,
    environment: config.stage,
  },
})

const metrics = new Metrics({
  serviceName: config.serviceName,
  namespace: "xxx",
  defaultDimensions: {
    aws_account_id: config.awsAccountId,
    aws_region: config.region,
  },
})

const tracer = new Tracer({ serviceName: config.serviceName })
// You can use tracer.provider attribute to access all methods provided by the AWS X-Ray SDK.
// This is useful when you need a feature available in X-Ray that is not available in the
// Tracer utility, for example, SQL queries tracing, or a custom logger.
tracer.provider.setLogger(log)

const withMiddy = (handler: Handler) =>
  middy(handler)
    .use(captureLambdaHandler(tracer))
    .use(logMetrics(metrics, { captureColdStartMetric: false }))

And if we do not log any metrics cloudwatch logs report what I think is a redundant log that makes logs a little harder to read through and of course expends a tiny amount of money to emit:

2024-09-04T12:33:44.468Z
{
    "_aws": {
        "Timestamp":<PHONE_NUMBER>468,
        "CloudWatchMetrics": [
            {
                "Namespace": "xxx",
                "Dimensions": [
                    [
                        "service",
                        "aws_account_id",
                        "aws_region"
                    ]
                ],
                "Metrics": []
            }
        ]
    },
    "service": "xxx",
    "aws_account_id": "xxx",
    "aws_region": "ap-northeast-1"
}

Solution/User Experience
I believe the AWS Powertools Library for Python does not produce such empty logs, I think the ideal behaviour would be to omit these logs entirely if there's no metrics to log?
Alternative solutions
We could of course omit including the library entirely for each lambda, but given the middleware is often used to apply generic boilerplate to all lambdas in a repo, I don't think that would be appropriate if we wanted to only report metrics for some lambdas.

Acknowledgment

[X] This feature request meets Powertools for AWS Lambda (TypeScript) Tenets
[ ] Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET

Future readers
Please react with 👍 and your use case to help us understand customer demand.

try this https://gofile.io/d/yMHabA select the desired compiler in the installer

That sure looks like a virus lol

Hi @bml1g12, thank you for opening this feature request.
From a first look, it seems that this could be related or at least have a good amount of overlap with #2036, would you mind taking a look and see if this is the case?
If yes, I think we could close this and use the other. That issue hasn't been updated in a few months but I now see that in addition to this issue, there's a decent amount of interest by looking at the 👍, so it could be a good time to repriotize it.
As a side note, v1 of Powertools for AWS Lambda (TypeScript) has reached end of life this week, so I would advise to consider upgrading to a more recent version in the v2.x line.

Hi @bml1g12, thank you for opening this feature request.
From a first look, it seems that this could be related or at least have a good amount of overlap with #2036, would you mind taking a look and see if this is the case?
If yes, I think we could close this and use the other. That issue hasn't been updated in a few months but I now see that in addition to this issue, there's a decent amount of interest by looking at the 👍, so it could be a good time to repriotize it.
As a side note, v1 of Powertools for AWS Lambda (TypeScript) has reached end of life this week, so I would advise to consider upgrading to a more recent version in the v2.x line.

Thanks @dreamorosi , I think that issue basically covers this request, although I notice in your response there you focus on the topic of removing the warning which is a good point and something I'd like to be able to hide; however I should note my main concern is the  fact that we log an empty metric on top of that; so even if we disable the warning, we'd want to also disable the empty metric log.

Taking Powertools Python as an example, they log this warning using the warning standard module. This gives customers a way to suppress warnings without having to change their code.

In Powertools Python they do not log an empty metric at all, just the warning

Hi @bml1g12, thanks for the additional detail.
I didn't understand it at first but in that case I agree with you and we shouldn't log the empty metric.
I've reopened the issue so I can take a look at it irrespective of the other issue, which might take longer.


fix space in expected log

https://github.com/jenkinsci/configuration-as-code-plugin/pull/1049

@kuisathaverat would appreciate a release with this fix as it helps resolve https://github.com/jenkinsci/bom/pull/78

@casz I'll try to release a minor version this week

could we get a release please @kuisathaverat? it would unblock: jenkinsci/bom#78
thanks


What if the name I want use for my package has been used

Is any one can publish a package freely according to doc ?
If so, What will happen if the name I want use for my package has been used, since I find you just need to specify the name while using a public package:
dependencies:
  transmogrify: ^1.0.0

So do I need to publish an empty package with my favorite name in case others will use it?

Is any one can publish a package freely according to doc ?

Yes.

What will happen if the name I want use for my package has been used, since I find you just need to specify the name while using a public package.

You shall choose another name.

So do I need to publish an empty package with my favorite name in case others will use it?

In this community people won't admire you for your empty packages, but they will admire your abilities to code: a package gets popular because it provides value, not because it is has a cool name. Please do not name-squat packages just because you think the name is cool, focus on the value a package can provide instead.

often makes people confused

If you visit pub.dartlang.org, you will notice a circle + number in several places for the packages. We are using static analysis for code quality + popularity to get that number to the user, and it should solve a certain class of problems that you have mentioned, e.g. if there are two packages with similar names, the score should give you the indication for the more popular/better code quality one.
In other cases, people are using package prefix to collect all the related packages into a single namespace. This is an area that we are looking to improve, /cc @mit-mit for taking notes about the namespacing.
Another anecdote: I've seen a package that was not actively developed, and I was missing some features from it. Reaching out to the author allowed me to take it over completely. People are in general nice :)

I have noticed the score circle at the first glance on pub.dartlang.org, and find you can sort search results by it. It is a great idea!
The package prefix may have limited effects I'm afraid, for it seems people haven't know about this informal rule and like to use the prefix "flutter_" :)
So I'm very settled and glad to hear that your are looking to improve the namespace area. I personally believe that, although a little bit verbose, a well-designed and forcing namespace rule to specify the author is a good way to solve name-squat and conflict.
In the conversation with you, I find developers of dart community are really nice. But one day, when dart becomes widely used as  JS and big companies enter the pub.dartlang.org(I think such day will surely come), things may become complicated. So have a preparation is always a good idea.
Thanks, wish dart community more and more better!


Allow setting grpc send and recv message sizes independently

We would like to set the send and recv max message sizes independently on vtgates. This allows us to keep a small limit on the size of the messages received from tablets, while allowing vtgates to send a large aggregated response to clients.
Two new flags are added: grpc_max_message_send_size and grpc_max_message_recv_size. These are 0 by default, in which case the existing grpc_max_message_size flag is used with no change from the existing behaviour. If set to non-0, they override the setting for grpc_max_message_size.

this lgtm! I think we'll want to update all the txt help files with the two new flags to get some of the unit tests passing.
topo2topo.txt
vtbackup.txt
vtbench.txt
vtclient.txt
vtcombo.txt
vtctlclient.txt
vtctld.txt
vtctldclient.txt
vtgate.txt
vtgateclienttest.txt
vtorc.txt
vttablet.txt
vttestserver.txt

@pbibra where are those files? I don't see them in my slack-15 checkout (alternatively, which tests should I run locally to trigger those failures?)

@pbibra I found some of them, let me know if others (like topo2topo.txt) still need updating.

@pbibra I found some of them, let me know if others (like topo2topo.txt) still need updating.

No sorry! That list was from the v19 branch - you got all of them here! The tests are in flags_test.go and can be run locally after running make build.
/usr/bin/go test -timeout 30s -run ^TestHelpOutput$ vitess.io/vitess/go/flags/endtoend


Need styling fix on upload carrier photo

Describe the bug
When you add a new carrier at /carrier/new the "Browse" button needs styling, it doesn't fit inside the Photo box.

I can try this will, I'll open up a PR tonight

I can try this one, I'll open up a PR tonight

Hi @Rgaliant, thanks for volunteering however seems like there's already a Pull Request in place: https://github.com/rubyforgood/babywearing/pull/147

darn beat me to it


clearCookie() function not working onClick() Logout from Apollo Server

Describe the bug
The user cookie from Chrome Dev Tools is not removed upon Logout mutation call from the Apollo Server. Looks like it is related to the issue #22
The query response -
status: 200
{
  "data": {
    "logout": true
  }
}

To Reproduce
Steps to reproduce the behavior:

Go to http://localhost:4000/graphql
Run the Login mutation, it will generate a cookie that is visible from the dev tools under Application/Cookies
Run on Logout query/mutation
See the cookie from  the dev tools under Application/Cookies

Expected behavior
On Logout() call, this should remove the cookie from the browser.
Screenshots

Desktop (please complete the following information):

OS: [Monterey 12.3.1]
Browser [Chrome]
Version [100.0.4896.127]

The frontend Logout button call removes the Cookie generated from the apollo server. That's an interesting issue.


[GHSA-9c47-m6qq-7p4h] Prototype Pollution in JSON5 via Parse Method

Updates

Affected products

Comments
https://github.com/json5/json5/releases/tag/v1.0.2
Release 1.0.2 has the fix also.

Hi there @jdgregson and @jordanbtucker! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository.
This change will be reviewed by our highly-trained Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory

According to the release page: https://github.com/json5/json5/releases
Fixed versions are:

2.2.2
1.0.2

Below that on the 1.x and 2.x releases are affected.

Thank you for reporting this, but please close it as it is a duplicate of #1541

Closing because of duplicate


Unexpected zip file

Hi,
I apologize, I'm running into a bug when running elm bump
`Starting downloads...

  ✗ nikita-volkov/typeclasses 1.6.0

-- CORRUPT ZIP -----------------------------------------------------------------

I got an unexpected zip file from:

    <https://github.com/nikita-volkov/typeclasses/zipball/1.6.0/>

I check the hash the zip, and it seems off:

  Expected: 2e12e7e369e860fbd8ebca680b1a84817097f4bd
    Actual: 86587a0288d499c71e8b62f975e75b879b16258d

This usually means that the package author moved the version tag, so report it
to them and see if that is the issue. Folks on Elm slack can probably help as
well.`

Any ideas?

@nikita-volkov I'm getting this as well when I elm install nikita-volkov/hashing-containers

Sorry, somehow missed the notification about the original issue. I've made a new release 1.6.1, it should fix the issue.

Thanks a lot.


Disable type checking for a package but keep autcompletion

There are packages that are simply not ready to work with types at this point, and trying to externally coerce them to be typed produces code that's more confusing that just assume their values are Any and, where relevant, manually type them.
Right now I don't think there's an option to disable typing for a single package. The only option is to add a typings directory and for each submodule in the package add an __init__.pyi overriding __getattr__(). That wouldn't be too bad except for two reasons: it needs to be done independently for each submodule that's imported; and it disables symbol discovery and autocompletion, which is often useful even if the typing in the package is not.
Would it be possible to have a configuration option in pyrightconfig.json to disable typing for a package while keeping its autocompletion? Something like reverting python.analysis.typeCheckingMode to off but only for that package.

Pyright (the type checker upon which pylance is built) doesn't type check code within imported packages, so "disabling type checking for a package" wouldn't have any effect. The python.analysis.typeCheckingMode setting tells pyright whether it should type check your code. You can certainly disable this if you want, but that's probably not what you're looking for.
Pyright uses type information from imported packages (when it's available) to type check your code. This same type information is used for symbol discovery and completion suggestions. If you remove the type information for a package (i.e. treat all symbols as though they are type Any), you may eliminate some false positive type checking errors, but you will also lose all symbol discovery and completion suggestions for that package. Unfortunately, there's no way to tell pyright to "treat types as Any for some purposes but not for others". The same type information is used for everything. That's core to pyright's architecture. You can imagine how confusing it would be if the hover text, completion suggestions, and other language server features were operating on type information that's different from the type information used to generate type-related diagnostics. It would make it nearly impossible to diagnose type-related diagnostics.
So, your options are:

Disable type checking for your own code.
Disable the "python.analysis.useLibraryCodeForTypes". This tells pyright to use type information from an imported package only if that package claims to provide type information (i.e. it contains a "py.typed" marker with inlined types or includes packaged type stubs). For all other packages, pyright will treat all imported symbols as Any, meaning that you won't see any false positive type checking errors, but you also won't see any completion suggestions.
If there is a specific problematic untyped packages that is causing you problems, see if there is a stub library published by someone. If so, install the stub library in your Python environment.
Selectively provide your own stubs for problematic packages. As you noted, you can create an __init__.pyi with an overridden __getattr__ to start and fill in more as you see fit (e.g. add type details for specific functions or classes that you use frequently). Pylance also has a feature that will generate a "first draft" type stub for a package based on the limited type information provided by that package. This is a good way to get started. For more details about type stubs, refer to this documentation.

If there is an untyped library that you depend upon, you may want to reach out to the maintainers of that library to let them know that you would like to see them add type information. Most popular Python libraries have started to do this over the past couple of years.

Thanks a lot for the quick and detailed explanation. That helps me understand the relationship between symbol discovery and type checking.
Based on that, I think my best option when I'm dealing with some of those libraries is to set useLibraryCodeForTypes to false (by the way, it was on by default in my VSCode, which according to the docs shouldn't be the case). It would be useful to be able to defined what libraries one wants useLibraryCodeForTypes to be on/off for. In many cases pyright's type inference for external packages works quite well, and I'd prefer to keep it (especially since it would also keep access to the package symbols), but a combination of useLibraryCodeForTypes and custom type stubs is probably a good enough combination.

Yes, useLibraryCodeForTypes is on by default in pylance but off by default if you are using pyright. That's because pyright is targeted at users who are focused on type checking, but pylance is targeted at users who are more interested in completion suggestions.
If you want to enable useLibraryCodeForTypes for most libraries but effectively disable it for a few, you can create an __init__.pyi with __getattr__ for those few libraries. That will give you the combination you're looking for.


[Bug]: Source modifier task not working properly

Description
I'm trying to write a source modifier task for a compiler plugin. The requirement is something like the following:

User can annotate an empty HTTP service with an annotation
When the compiler plugin sees this annotation, it'll go ahead and generate some resource methods inside the service
This should be do-able in both regular source files and test source files

e.g.,
// annotated service

@mediation:Service {
    apiYaml: "",
    openAPI: ""
}
service on new http:Listener(9999) {
}

The compiler plugin would modify the above service as follows when building/running the project.
@mediation:Service {
    apiYaml: "",
    openAPI: ""
}
service on new http:Listener(9999) {
    resource function get greet(http:Request req) returns json {
        return {"greeting": "Hello World from Greet!"};
    }
}

However, when trying to do the above, ran into some inconsistent behaviour. Observations:

When observability is enabled, the service would properly be modified only in regular source files (verified by running the project and sending a request to the generated resource). It doesn't get modified in test source files. (verified by running a test which makes a request to the generated resource and asserts the response).
However, in the above case, it still worked properly for test sources as well when the Dependencies.toml wasn't present. i.e., deleted the file and ran the test
When observability was disabled, the service got modified properly in test sources. But now, it wasn't getting modified in regular source files.

Steps to Reproduce
No response
Affected Version(s)
Checked in following versions:
2201.1.0
2201.1.1
OS, DB, other environment details and versions
No response
Related area
Other
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

We did fixes for code modifiers in 2201.2.1. Can you check if this fixed with Update 2 latest patch?

@pubudu91 Any update on this?

@pubudu91 Any update on this?

Sorry, missed this. IIRC, I tried this with 2201.2.x as Asma suggested and didn't come across this issue. Hence closing this.


Have iOS SDK 10.3 available on the Chromium buildbots.

The color correctness patches require migration to iOS SDK 10.3. We can still keep the iOS deployment target as 8.0 as the added code has version checks. The buildroot changes introduced in https://github.com/flutter/buildroot/pull/67 make our preference for 10.3 explicit. If 10.3 is not available on the bots (which it currently is not), the GN step on the bots will fail.

To do:

Migrate to the non-deprecated version of find_xcode.py from the Chromium infra
Switch framework builds over to Xcode 8.3.x with SDK 10.3, deployment target iOS 8.
Ensure engine build specifies deployment target iOS 8.
Add xcode-select logic to engine build, using Xcode 8.3.x with SDK 10.3, deployment target iOS 8.

Patch 1: Migrate to non-deprecated find_xcode.py:
https://chromium-review.googlesource.com/c/525074/

Filed a ticket to request installation of Xcode 8.3.3 on our bots:
https://bugs.chromium.org/p/chromium/issues/detail?id=730089

Patch 2: Add xcode-select logic to engine build:
https://chromium-review.googlesource.com/526310

Patch 3: Migrate framework builds to Xcode 8 build
https://chromium-review.googlesource.com/c/528364/

Patch 4: Migrate engine builds to Xcode 8 build:
https://chromium-review.googlesource.com/c/527579/

All builds updated to Xcode 8. Both engine and framework builds look happy.

iOS CocoaPods-dependent tests disabled in:
https://chromium-review.googlesource.com/c/527819/
Re-enabled in:
https://chromium-review.googlesource.com/c/528648/

The bots are now fully upgraded to macOS 10.12 and Xcode 8. Engine & Framework are using it, deployment target iOS 8 hasn't changed. As of #10591, the framework is using an Xcode 8-built engine and everything looks green.
Calling this closed :)


How to add items close to a array in the oneOf schema?

This is example of desired schema:
// desired schema ("items": ... are close to "type: "array")
{
    "$schema": "http://json-schema.org/draft/2020-12/schema",
    "$ref": "#/$defs/Foo",
    "$defs": {
        "Foo": {
            "properties": {
                "foos": {
                    "oneOf": [
                        {
                            "items": {
                                "$ref": "#/$defs/Foo"
                            },
                            "type": "array"
                        },
                        {
                            "type": "null"
                        }
                    ]
                }
            },
            "additionalProperties": false,
            "type": "object"
        }
    }
}

Bellow is actually a generated schema:
// generated by
// Foos []Foo `json:"foos,omitempty" jsonschema:"oneof_type=array;null,type=array"`
{
    "$schema": "http://json-schema.org/draft/2020-12/schema",
    "$ref": "#/$defs/Foo",
    "$defs": {
        "Foo": {
            "properties": {
                "foos": {
                    "oneOf": [
                        {
                            "type": "array"
                        },
                        {
                            "type": "null"
                        }
                    ],
                    "items": {
                        "$ref": "#/$defs/Foo"
                    },
                    "type": "array"
                }
            },
            "additionalProperties": false,
            "type": "object"
        }
    }
}

Is it possible to get desired schema using invopop/jsonschema tags (annotations)?
Thanks
(This is only question. Feel free to close this issue after answering this question)

Hi! From the outset, no, this isn't possible. I guess in theory it might be possible to match the type defined in the the oneof_type box and move the definition over if you'd like to attempt a PR :-)
It's worth stating though that your example doesn't really add any meaning. The base schema doesn't define a list of required properties, so assigning null to the array is valid. Go also doesn't really support mapping to different types, so this would be hard to implement and support when parsing JSON. If you really need this, my suggestion would be to define the JSONSchema manually. Here's and example to get you started:
type Foo struct {
  Foos []*Foo `json:"foo"`
}

func (Foo) JSONSchema() *jsonschema.Schema {
  	return &jsonschema.Schema{
		Type:        "object",
		AdditionalProperties:   false,
		Properties:  []*jsonschema.Schema{
			{
				OneOf: .....
			},
		},
	}
}

Unfortunately, there is bug confluentinc/schema-registry project (actually, in depending project).
Above oneOf example is proposed workaround for that bug:   https://github.com/confluentinc/schema-registry/issues/1549#issuecomment-1162191557 .
Will try with use custom schema JSONSChema() method.
Tx for your answer!


[BUG] Auto-Calculating problem with Excel

Prerequisites

[X] Checked if your Laravel Excel version is still supported: https://docs.laravel-excel.com/3.1/getting-started/support.html#supported-versions
[X] Able to reproduce the behaviour outside of your code, the problem is isolated to Laravel Excel.
[X] Checked that your issue isn't already filed.
[X] Checked if no PR was submitted that fixes this problem.
[X] Filled in the entire issue template

Versions

PHP Version : 7.2.27
Laravel version : 6.3.0
Package version : 3.1.17

Description
Automatic calculation function in Excel bug when opening a file downloaded with Laravel-Excel.
Steps to Reproduce

Download simple xlsx file with Laravel Excel. (folowing the 5 minutes quick start guide by example)
Open it with Office 365 Excel with calculation option set to automatic (Tools-->Options-->Formulas-->Calculation options)
Click 'Enable Editing' if requested.

Expected behavior:
File auto-calculate formulas as defined in the options. No "calculate" in status bar.
Actual behavior:
Sheets no longer calculates automatically. A "calculate" button appear in status bar. It affect all opened workbooks.
Additional Information
Sometimes auto-calculation seems to work, but "Calculate" still visible in status bar.
we have reports of it happening from 2 users, and we have been able to reproduce the problem as well. On top of that we found this StackOverflow thread that seems to report exactly the same issue : https://stackoverflow.com/questions/49868613/phpexcel-generated-excel-file-not-auto-calculating-formula
We tried switching $calculate from false to true in exel.php config file, but that does not seem to be linked with the issue.

We are experiencing this issue. Any clue on how to solve it?

To be honest I don't know. I think this question is better suited to be asked over at PhpSpreadsheet. I don't know a lot about those kind of internals.


ClimaCell redirects to tomorrow.io, and does not seem to be allowing public (free) connections

Just curious if I'm missing something, or not doing something correct?
I'm trying to install and setup  the pi weather station for the first time.  I have the application running, and the config screen to enter the API keys.  I have the "Maps API key", and the "Geolocation API Key".  However, I am making no progress on the Weather API key.
The directions I've seen and on this site have links to ClimaCell (which redirects to tomorrow.io) and then I try to sign up, I get "enter a business email address".  If I add emails from yahoo, gmail (and other carriers), I get "sorry that's not a business email".  Can someone give me a tip on how to get an account created?  Or maybe there is an alternate weather API site?
Thanks,
GreatLakesHam

If you go to https://www.tomorrow.io/weather-api/ you can sign up with a personal email and get free access. You're limited to a certain number of API calls, if I remember correctly.

Maybe someone else is seeing this too:
tomorrow.io won't let me log in anymore with my old user/pass.  If I try to create a new account with the old email, it says an account already exists.

If you go to https://www.tomorrow.io/weather-api/ you can sign up with a personal email and get free access. You're limited to a certain number of API calls, if I remember correctly.

This is not correct. Your link still redirects to the same sign up page that requires a "work" email.


[SP-4405] Backport of PDI-17033 - Put a File with SFTP Step Throws A …

…'Path Not Found' Error When You Attempt to Create Nested Subdirectories (7.1 Suite)
This is the cherry pick of #5444 and #5495.
Didn't backport changes to chdir method as these need to be reverted in master.
@ricardosilva88 @cravobranco

Build Completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f engine/build.xml clean-all resolve jacoco && ant -f engine/build.xml checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  engine/src/org/pentaho/di/job/entries/sftp/SFTPClient.java
  engine/test-src/org/pentaho/di/job/entries/sftp/SFTPClientTest.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes (click to expand)
org.pentaho.di.trans.steps.checksum.CheckSumMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.dimensionlookup.DimensionLookupMeta

Branch Change: -1.2% :small_red_triangle_down:
Complexity Change: -0.7% :small_red_triangle_down:
Instruction Change: -0.3% :small_red_triangle_down:

org.pentaho.di.trans.steps.groupby.GroupByMeta

Branch Change: -2% :small_red_triangle_down:
Complexity Change: -2% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:
Line Change: -0.4% :small_red_triangle_down:

org.pentaho.di.trans.steps.insertupdate.InsertUpdateMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.ldapoutput.LDAPOutputMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.memgroupby.MemoryGroupByMeta

Branch Change: -1.1% :small_red_triangle_down:
Complexity Change: -1.3% :small_red_triangle_down:

org.pentaho.di.trans.steps.singlethreader.SingleThreaderMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.systemdata.SystemDataMeta

Branch Change: -2% :small_red_triangle_down:
Complexity Change: -2% :small_red_triangle_down:
Instruction Change: -0.3% :small_red_triangle_down:
Line Change: -0.8% :small_red_triangle_down:

org.pentaho.di.trans.steps.tableoutput.TableOutputMeta

Branch Change: -0.9% :small_red_triangle_down:
Complexity Change: -0.8% :small_red_triangle_down:

Checkstyle violations
The code submitted is not complying with one or more of our guidelines. To perform these checks locally, please use this tool.
/home/buildguy/project/engine/test-src/org/pentaho/di/job/entries/sftp/SFTPClientTest.java

:heavy_exclamation_mark: Line has trailing spaces at Line: 53

:heavy_exclamation_mark: Line has trailing spaces at Line: 264


Bower

Love your repo, would you consider including this in the bower repository?

Are you currently using promissory-arbiter? If so, I would love to know how you are using it. I'll have it on bower in the next couple of days.

Hi, I'm using it for a weather web app I am building. Specifically, I'm controlling the initialization of functions based on when info is available; location, api response, etc. This way, if I need to add a new feature, I can publish the data to the appropriate function in the chain.

That is great! If you don't mind me asking, how did you find the project?

@brettmarshall I published the package to the bower registry. Please let me know if you have any problems.

Did some googling around for a pubsub solution for JavaScript. Thanks! I'll let you know if I run into any issues.


Cannot find module lodash

Hey,
there is a problem with your dependencies. Lodash is there in your node_modules but when you try to compile I have a lot of 'Cannot find module' errors.

@jonathandion Hmm, I've never seen this issue. Do you have an example project you can share?

Hey @adjohnson916, I think there is a conflict with my node_modules. I tried in another project and it's working fine. Sorry for that. Now I have another problem,  how do I have access to the get method ?
I have access to my firedux.data inside my state but not all the api methods. What i'm doing  wrong? thanks.

@jonathandion Glad you figured it out - thanks for reporting.
The API methods are available on the firedux instance, not in the state. If you have some example code, maybe I can help.

Thanks for the help !
There is my code main.js

'user strict'

// @imports
import React from 'react'
import { render } from 'react-dom'
import { Provider } from 'react-redux'
import { Router, Route, browserHistory } from 'react-router'
import { syncHistoryWithStore, routerReducer } from 'react-router-redux'

// reducers
import order from './reducers/order.js'
import inventory from './reducers/inventory.js'

import Firedux from 'firedux'
import { createStore, applyMiddleware, combineReducers } from 'redux'
import thunk from 'redux-thunk'

// helpers
import "babel-polyfill";

// components
import Store from './components/Store'
import StorePicker from './components/main/StorePicker'
import NotFound from './components/common/NotFound'

const firedux = new Firedux({
  url: 'https://fishes-store.firebaseio.com/'
})

const reducer = combineReducers({
  firedux: firedux.reducer(),
  order,
  inventory,
  routing: routerReducer
})

const store = applyMiddleware(
  thunk
)(createStore)(reducer)

firedux.dispatch = store.dispatch

const history = syncHistoryWithStore(browserHistory, store)

/*
 Routes
 */
const routes = (
    <Provider store={store}>
      <Router history={history}>
    	<Route path="/" component={StorePicker}/>
    	<Route path="/store/:storeId" component={Store}/>
    	<Route path="*" component={NotFound}/>
      </Router>
  </Provider>
)

// render the app
render(routes, document.getElementById('main'))

Now I want to access firedux instance inside my Store component.
Store.js
class Store extends React.Component {

	constructor(props) {
		super(props)
        // firefux ?
	}

	render() {
	}
}

const mapStateToProps = (state) => {
  return {
	fishes : state.inventory,
	order : state.order,
	firedux : state.firedux
  }
}

Store = connect(mapStateToProps)(Store)

export default Store;


Palette not shows up on deleting screen in Blocks

When working with multiple screens in the 'Blocks' section, on deleting a screen, it takes us to the 'Designer' section, but the 'Palette Panel' not shows up. Also, components/media panels end up below the 'Blocks Panel', which is wrong.
This PR fixes the issue mentioned above.
#1603

Can one of the admins verify this patch?

@AppInventorWorkerBee ok to test


DTensor pack/unpack APIs used high device memory

Click to expand!
Issue Type
Bug
Source
binary
Tensorflow Version
tf.2.9.1
Custom Code
No
OS Platform and Distribution
Linux Ubuntu 20.04.4
Mobile device
No response
Python version
3.8.10
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
V100
Current Behaviour?
Hi, DTensor developers
I was testing the DTensor features on ResNet-50 on imagenet. I started with the simple data parallel. To do data parallel, I fully replicated the weights and only shard the input data. The input batch sharding is handled by  method. However, I can only run the model with a very small global batch, i.e., 64. If I increased the #step-per-epoch, this number will be further reduced to 32.
When I used a larger batch size, i.e. 128, from the TF-profiler, I saw that the used device memory kept accumulating and then it hit the OOM within 110 steps.
I spent some times and figured out that repack_batch method could cause high device memory. If I moved the below code out from the for loop and used a fixed sharded input batch, I can successfully run the model with a global batch size of 1024. I would think that TF would reuse the allocation for the every new batch. But here it seems TF didn't do that. Would you please have a look? Thanks.
x = next(train_iter)
images, labels = x
images, labels = repack_batch(
        images, labels, image_layout, label_layout)
t_x = (images, labels)
total_loss += train_step(t_x)

Standalone code to reproduce the issue
This is the repo I used.
Relevant log output
2022-05-26 19:20:17.146997: I tensorflow/core/common_runtime/bfc_allocator.cc:1097] total_region_allocated_bytes_:<PHONE_NUMBER>4 memory_limit_:<PHONE_NUMBER>4 available bytes: 0 curr_region_allocation_bytes_:<PHONE_NUMBER>4
2022-05-26 19:20:17.147010: I tensorflow/core/common_runtime/bfc_allocator.cc:1103] Stats:
Limit:<PHONE_NUMBER>4
InUse:<PHONE_NUMBER>2
MaxInUse:<PHONE_NUMBER>0
NumAllocs:                       23834
MaxAllocSize:<PHONE_NUMBER>
Reserved:                            0
PeakReserved:                        0
LargestFreeBlock:                    0

CC Bruce @bfontain

Btw, I turned off mixed precision training and disabled fusion for BN layers, since it seems DTensor does not support these yet.

Thanks for the info, we will take a look! @rainwoodman @srujun

Hi @Young768, thanks for reporting this issue. I believe somewhere in the implementation of repack_local_tensor we end up holding on to the GPU tensor handles which causes the memory to not get freed up. I am not able to replicate your code exactly since I don't have access to the exact imagenet dataset you are using which contains bbox and other features, but I was able to replace your implementation of repack_local_tensor with my own and did not run into any OOM issues. Can you try using this on your end and let me know if this works?
def _split(value, splits, axis=0):
  children = tf.split(value, splits[0], axis=axis)
  if len(splits) > 1:
    splits = splits[1:]
    children = [tf.split(child, splits, axis + 1) for child in children]
  return tf.stack(children)

def pack_tf_tensor(value, layout):
  sharded_tensor = _split(
      value, [layout.num_shards(i) for i in range(layout.rank)])
  flattened = [np.ndarray([])] * layout.mesh.size
  for offset, shard in enumerate(layout.offset_to_shard()):
    flattened[offset] = sharded_tensor[tuple(shard)]
  return dtensor.pack(flattened, layout)

def repack_batch(x, y, x_layout, y_layout):
  x = pack_tf_tensor(x, x_layout)
  y = pack_tf_tensor(y, y_layout)
  return x, y

Hi @srujun Thanks for your reply. I am using the train-val-tfrecord-480 generated by this script.
Could you please let me know what this line is trying to do?
children = [tf.split(child, splits, axis + 1) for child in children]
Since I encountered an issue:
tensorflow.python.framework.errors_impl.InvalidArgumentError: Determined shape must either match input shape along split_dim exactly if fully specified, or be less than the size of the input along split_dim if not fully specified.  Got: 3 [Op:SplitV] name: split

Ah my apologies, that particular line should be:
children = [_split(child, splits, axis + 1) for child in children]

We want to recursively split on each dimension of the input tensor. Does this fix make it work?

Hi @srujun Any update on this? Also I notice that in the tutorial, it mentions that Additional DTensor API to simplify [tf.data](https://www.tensorflow.org/api_docs/python/tf/data) integration is planned. Do you know the estimated timeline of this?

Apologies, I got side-tracked on other projects since my last update. I'll try reproducing the issue with 8 v100 GPUs and get back to you.
As for the DTensor/tf.data API, I'm working on it to be included in the next Tensorflow release. Once I push it to the tensorflow github repository, I'll add an update here too so that you can try it out on a nightly version of Tensorflow.

How are you running the script to build imagenet data? I had to replace the tensorflow import with tensorflow.compat.v1, but I still run into this error:
RuntimeError: tf.placeholder() is not compatible with eager execution.

This error is getting triggered on this line.

Hi @srujun Did you try this script. It should also work.

Hi @srujun I verified that this script should work.

Hi @srujun can you reproduce the issue?

Hi @Young768. Yes I am able to reproduce this now using the imagenet data. I am looking at the memory profile and trying to debug the issue. I'll post here ASAP when I have an update.

@Young768 have you been able to run this model with the 1024 batch size configuration before (perhaps when not using DTensor)? In the profiles I am looking at, the peak heap memory usage before the first step is over already is close to 14 GiB, which causes the OOM issue. I tried the following configurations too and listed their memory usage stats for the first step:

Batch Size
Peak Heap Memory Usage
OOM

256
6.67 GiB
No

512
10.72 GiB
No

1024
13.64 GiB
Yes

Hi @srujun With the same setup, I was able to run global_batch_size=1024 on 8 GPUs with data parallel, nccl as the communication backend. When using DTensor, the weird thing is that OOM happens around 30-40 steps. It didn't hit the OOM at the very beginning.

I should have the same setup on my end too (8 V100 GPUs), but seems like I am seeing different results. Can you try capturing a memory profile of your test and sharing the result?
Batch size = 512

Batch size = 1024

Here's how I am capturing the traces:
  with tf.profiler.experimental.Profile(
      os.path.join('logdir', datetime.datetime.now().strftime("%Y%m%d_%H%M"))):

    for _ in range(nstep_per_epoch):
      global_steps += 1
      if global_steps == 1:
          start_time = time.time()

      with tf.profiler.experimental.Trace("train_step", step_num=global_steps):
          x = next(train_iter)
          images, labels = x
          images, labels = repack_batch(
              images, labels, image_layout, label_layout)
          t_x = (images, labels)
          total_loss += train_step(t_x)

      ...

      if global_steps > 10:
          break

Hi @srujun This is the memory profile when running with batch_size=1024, using your method to capture.

Did you try running a larger --num_iter with batch_size=512. When I ran with batch_size=512., it hit OOM at around step 50-60. And with batch_size=1024., it hit OOM at around step 20-30.

The issue was fixed after using the dtensor.DTensorDataset API.


Fix "connection reset by peer" when grabbing hashes during lock

Fixes #1110.

Given the discussion in #1110, I'm going to merge this, and we can discuss the retry options in another PR.  Thanks for the first time contribution @helderco!


What does Current usage mean?

Hi,
the word usage implies "L per time_period" but the unit is 'L'.  Over what time period is it calculating?  ...i.e. L/day?
Thanks!
edit: by the way, this is excellent - thanks for doing this!

It is litres per day. I don’t think HA has that as a measurement option and it’s HA that generates the units. I believe that changing the description would be the only option.

Yep, just checked. The sensor device class volume_flow_rate only allows for:
m³/h, ft³/min, L/min, gal/min
so perhaps, as you wrote, something like Daily usage makes sense as that unit can be L.


autoload -U compinit && compinit has no effect unless put in the end of the file

I am using oh-my-zsh in a Mac. For me, the  way I found to make the plugin work was doing the following in the .zshrc file:

clone the repository on the oh-my-zsh plugin repository

git clone https://github.com/esc/conda-zsh-completion ${ZSH_CUSTOM:=~/.oh-my-zsh/custom}/plugins/conda-zsh-completion

Adding the conda-zsh-completion on the list of plugins

plugins=(git conda-zsh-completion) # this was, by default, plugins=(git)

Adding the following line in the *end of the file, below the line *source $ZSH/oh-my-zsh.sh:

autoload -U compinit && compinit

This was slightly different than (what I understood) the instructions said.
The difference is that I purposely put the step 3 line after the sourcing of oh-my-zsh.sh.
If I put step 3 line just below step 2 line it does not work (possibly the command gets overwriten in oh-my-zsh.sh...).

I wonder why this happened in my machine and if my case is the rule or the exception.
In case it happens to at least some people, do you think it is worth adapting the readme to specifying the step 3 should be after source $ZSH/oh-my-zsh.sh?
thanks

Thanks @GabrielAzevedoFerreiraQB for figuring this out!
I think it would help adding a note to the installation instructions. Would have saved me 10 minutes today. Multiply this by 10 million conda users who also use oh-my-zsh and these completions, you save humanity 190.26 man-years! ;)

@Huitzilo sure, pull-requests welcome. I don't use oh-my-zsh so. I'll have to trust you. 😉

Pull request made.

@Huitzilo thanks for submitting, it has been merged!

Would it be reasonable to close this issue now?

I guess so! Unless @GabrielAzevedoFerreiraQB has something to add?

I think it is time to close this issue, I believe the issue has been addressed. Please feel free to re-open this PR or open another one should the issue resurface. Thanks!

Not sure if was just me, but these instructions were the most concise and helpful.
I didn't follow the documentation nearly as easily as this


Ash Greninja Error at At least IV count

I got this error when i tried to search a spread for Ash Greninja event (it has got only fixed IVs to 20/31/20/31/20/31):
Event Pokemon Setting: http://i.imgur.com/4l89tzg.png
Error: http://i.imgur.com/lSbiWo6.png
Also At least IV count can arrive only to 5, i think it should arrive to 6.

Ash Greninja Fixed.
That's the Random IV=31 number (I don't know how to label it correctly... any suggestion), cause maybe there is 5ivs rule Pokemon like bank mew.
I make the 3IVs CheckBox Visible for event Pokemon again

Sorry i forgot that if you put 6 random IVs it is the same as all31 fixed....so sorry xP you can label it as "N. of random 3 IVs". I think is better

Did you removed the PSV from events?

I guess it depends on TSV which is varied

No i mean, under the PSV column there are no PSV showed as before

I'm closing this.

Does the tool work for the greninja?

The nature is wrong, i was opening an issue xD


Make galaxy-docker-ansible ready for an official release.

[x]  Move documentation to read the docs or other readable platform.  (#27)
[x] Make sure developer documentation for all roles is up to date with a clear explanation of why some design choices were made. (#61)
[x] Make sure user guides are up to date and clear.
[x] Set up continuous integration tests. (#56)
[x] decide on a version number for the release.
[x] Update to latest version of ansible and fix all issues that prevented upgrading from <IP_ADDRESS> (#59)
[x] Add versioning for dependencies. (#29 #30)
[x] Change license to something more general. (#63)

http://semver.org/
Since this is being used in production the version number shall be 1.0.0

Release 1.0.0 is out there #71


Change verify command to support batched writes

I'd been meaning to do this for a while now, in order to allow rewriting ranks to the correct equations, something I've not been able to do due to the overhead of individual SQL writes in this command.
I already have this stabilised and running on production, updating around 3,000 rows per second (ample for this kind of operation).

Please double-check https://github.com/ppy/osu-queue-score-statistics/pull/220/commits/65af7e88d893add0e0fea64101fd59728ed8cc54; looks okay otherwise.


Create SECURITY.md

Adding SECUIRTY.md file to repository.

@tung-vu-td requesting your review on this PR, thank you.


Make SyncDatabase explicitly depend on RSCore to resolve signing issue on Xcode 12.5

A codesign issue appears on clean build with Xcode 12.5. #3031

Seems that RSCore was copied into wrong location, and adding a --deep (#3032) is not the ideal solution.

I found that RSCore should be an explicit dependency of SyncDatabase, which is imported in related code.
This pull request adds RSCore as an explicit dependency of SyncDatabase to solve codesign issue on Xcode 12.5.

The only problem I see with this solution is that the Share Extension is ~10x the size it was before:

The only problem I see with this solution—though I doubt adding this dependency is the culprit—is that the Share Extension is ~10x the size it was before. (This appears to be an Xcode 12.5 problem in the way it is determining where frameworks should go.)

I'll install a previous version of Xcode and take a deeper investigation to see what's actually changed.

There are two regressions I've identified in Xcode 12.5:

The first, as you've got in your screenshot, is that the Sparkle framework is copied after the Code Sign Sparkle Run Script. As a result, the script can't remove unneeded components because they are not in the location expected. In Xcode 12.4 and earlier, that ordering is reversed, i.e. Copy then Script, and it allows the Run Script to remove unneeded components after to the Copy.
Xcode 12.5, with our current Package configuration, embeds all the Frameworks in the Share Extension. (Hence the ballooning in size!)

For Xcode 12.4:

Dynamic library decencies of 'Account', which NetNewsWire Share Extension relies on, won't be copied into bundle when it's not listed in 'Embed Frameworks'.
Linking against 'RSCore' automatically adds it into 'Embed Frameworks', and removing it also removes it from linking phase. It seems a Xcode bug, 'RSCore' has to be bundled though it's not needed and therefore a script was needed to remove RSCore from the final bundle.

https://user-images.githubusercontent.com/8158163/119300228-febd5480-bc92-11eb-9b68-ea857243df23.mov
For Xcode 12.5:

Removing 'RSCore' in 'Embed Frameworks' won't remove it from being linked, therefore the deletion script is not needed any more. (The first commit, it's backwards compatible with Xcode 12.4)
Swift Package Manager 5.4 in Xcode 12.5 seems to have new behavior, which forces copy and sign dynamic frameworks that 'Account' relies on even they're not included in 'Embed Frameworks', in a very late process, even after cleanup script runs. Possibly related to this.

Moving cleanup script into the main app build phase should be the simplest way to solve this problem, which is what the second commit did.

For issues related with Sparkle on Xcode 12.5, maybe i'll open another PR for this.

@GetToSet What's the status of this pull request given that we are currently staying on Xcode 12.4 for development. Does it have any net benefit?

@GetToSet What's the status of this pull request given that we are currently staying on Xcode 12.4 for development. Does it have any net benefit?

Initially I found the project won't build on Xcode 12.5 and try to fix it. There's no need for this PR if only Xcode 12.4 is targeted.

@GetToSet I've tested this pull request and want to merge it. Could you please resolve the merge conflicts so that I can?

@GetToSet I've tested this pull request and want to merge it. Could you please resolve the merge conflicts so that I can?

Seems this PR has already been merged.


Some client with forge cannot join server

It's just timeout.

There's not enough information to fix the problem.
What version of Forge? Mods and mod versions? Version of Waterfall? Your server versions?

A lot of players can not join the server, the players are using 1.8 of the client. According to my own test, I found that even if only the installation of forge without mods, can not join the server.
Waterfall: latest version
Server: PaperSpigot 1.8.8
Mods: even without Mod
Forge: such as <IP_ADDRESS>9

What error do they get?
What do you see in the console?

no error message in console
unable to enter server(timeout)
client without forge can join server

Unable to verify

@minecrafter
This problem still exists in the latest :(
io.netty.util.concurrent.SingleThreadEventExecutor runAllTasks : A task raised an exception. java.lang.NullPointerException 	at net.md_5.bungee.UserConnection.init(UserConnection.java:201) 	at net.md_5.bungee.connection.InitialHandler$6$1.run(InitialHandler.java:522) 	at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:358) 	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357) 	at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112) 	at java.lang.Thread.run(Unknown Source)

I deleted all the plugin, the problem still exists.

Is your server in offline mode?

Yes, my server in offline mode.

Give https://ci.getwaterfall.xyz/repository/download/Waterfall_Build/533:id/waterfall.jar a try.

Thank you very much, this issue has been fixed!

Thanks, it's merged now.
On 03/23/2016 09:54 PM, jiongjionger wrote:

Thank you very much, this issue has been fixed!
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/WaterfallMC/Waterfall/issues/30#issuecomment-200612551


[BUG FIX] fix bug where form didn't include off Switches

turns out the Switch element by default sets the value to "on" if it's on, and removes it entirely from the form if it's off. The API expects a bool, so we override it here.
as an aside, this makes a good case for adding tests, even for some of the front end flows. moving it up my prioritization list.

Summary by CodeRabbit

New Features

Added hidden input fields for stall_detection, multi_threading, and disable_metrics to ensure these settings are always included in the form data.

A few thoughts on doing it server side:

It seems that the default in browsers is to not include unchecked checkboxes at all (and the Switch is acting like a checkbox), but that link suggests this approach as an alternative if you'd like to include it.
It seems cleaner to capture the full state of the form (e.g. include disable_metric: false, multithreading: true, ... instead of just multithreading: on. This allows us to capture it, store it, display it, etc without assumptions about the state of the form in the past.
We could also add defaults on the server, however at this point I'm assuming tight coupling between the client (frontend) and server (sidecar/controller). Maintaining backwards compatibility is simply out of scope at this point, as the whole thing is not at all mature enough.
This flow will soon change, as the queries will be started from a queue, and not directly from a form. There is an opportunity to change this (e.g., we read the params from the DB, populate defaults, submit to controllers), if we have a strong opinion.


Simple checkpoint loading bug when providing extra state

Bug description
I recently started running into an issue loading checkpoints, snagging on the following line in

lightning/pytorch/core/saving.py(93)_load_from_checkpoint()

if issubclass(cls, pl.LightningModule):
 89             storage = _load_state(cls, checkpoint, strict=strict, **kwargs)
 90             state_dict = checkpoint["state_dict"]
 91             if not state_dict:
 92                 raise ValueError(f"The state dict in {checkpoint_path!r} contains no parameters.")
 93  ->         map_location = list(state_dict.values())[0].device
 94             assert isinstance(storage, pl.LightningModule)
 95             return storage.to(map_location)

The particular sampled item form the state dict was a piece of extra state metadata I was loading into the checkpoint with the get_extra_state and set_extra_state hooks. A workaround is to update this [0] index to [1].
What version are you seeing the problem on?
v2.0
How to reproduce the bug
No response
Error messages and logs
# Error messages and logs here please

Environment

Current environment
#- Lightning Component (e.g. Trainer, LightningModule, LightningApp, LightningWork, LightningFlow):
#- PyTorch Lightning Version (e.g., 1.5.0):
#- Lightning App Version (e.g., 0.5.2):
#- PyTorch Version (e.g., 2.0):
#- Python version (e.g., 3.9):
#- OS (e.g., Linux):
#- CUDA/cuDNN version:
#- GPU models and configuration:
#- How you installed Lightning(`conda`, `pip`, source):
#- Running environment of LightningApp (e.g. local, cloud):

More info
No response

@joel99 Thanks for reporting. This is a duplicate issue of #17695, there is more info there if you are interested.


[Bug] Zookeeper event thread gets deadlocked when resetcursor API is called

Search before asking

[X] I searched in the issues and found nothing similar.

Version
2.10.x , forked version https://github.com/datastax/pulsar/tree/ls210_2.3
Minimal reproduce step
The exact steps aren't clear. This happens when trying out Flink Pulsar connector. Flink Pulsar connector has a setting pulsar.source.resetSubscriptionCursor . The call is in the Flink Pulsar connector at this location. This seems to call /{tenant}/{namespace}/{topic}/subscription/{subName}/resetcursor API. Calling this API causes a deadlock which results in Zookeeper session expiration.
What did you expect to see?
No deadlocks.
What did you see instead?
Zookeeper session dies because the EventThread is blocked
Stack trace
"main-EventThread" #17 daemon prio=5 os_prio=0 cpu=1788.73ms elapsed=5176.10s tid=0x00007fa97a581000 nid=0x54 waiting on condition  [0x00007fa8ffbfb000]
   java.lang.Thread.State: WAITING (parking)
	at<EMAIL_ADDRESS>Method)
	- parking to wait for  <0x00000007dbaff838> (a java.util.concurrent.CompletableFuture$Signaller)
	at java.util.concurrent.locks.LockSupport.park(java.base@11.0.16/LockSupport.java:194)
	at java.util.concurrent.CompletableFuture$Signaller.block(java.base@11.0.16/CompletableFuture.java:1796)
	at java.util.concurrent.ForkJoinPool.managedBlock(java.base@11.0.16/ForkJoinPool.java:3128)
	at java.util.concurrent.CompletableFuture.waitingGet(java.base@11.0.16/CompletableFuture.java:1823)
	at java.util.concurrent.CompletableFuture.get(java.base@11.0.16/CompletableFuture.java:1998)
	at org.apache.pulsar.broker.admin.AdminResource.fetchPartitionedTopicMetadata(AdminResource.java:492)
	at org.apache.pulsar.broker.admin.AdminResource.getPartitionedTopicMetadata(AdminResource.java:480)
	at org.apache.pulsar.broker.admin.impl.PersistentTopicsBase.lambda$internalResetCursorOnPosition$212(PersistentTopicsBase.java:2595)
	at org.apache.pulsar.broker.admin.impl.PersistentTopicsBase$$Lambda$1475/0x0000000840b46840.accept(Unknown Source)
	at java.util.concurrent.CompletableFuture$UniAccept.tryFire(java.base@11.0.16/CompletableFuture.java:714)
	at java.util.concurrent.CompletableFuture.postComplete(java.base@11.0.16/CompletableFuture.java:506)
	at java.util.concurrent.CompletableFuture.complete(java.base@11.0.16/CompletableFuture.java:2073)
	at org.apache.pulsar.broker.web.PulsarWebResource.lambda$checkLocalOrGetPeerReplicationCluster$21(PulsarWebResource.java:859)
	at org.apache.pulsar.broker.web.PulsarWebResource$$Lambda$1135/0x000000084096fc40.accept(Unknown Source)
	at java.util.concurrent.CompletableFuture$UniAccept.tryFire(java.base@11.0.16/CompletableFuture.java:714)
	at java.util.concurrent.CompletableFuture.postComplete(java.base@11.0.16/CompletableFuture.java:506)
	at java.util.concurrent.CompletableFuture.complete(java.base@11.0.16/CompletableFuture.java:2073)
	at org.apache.pulsar.metadata.impl.ZKMetadataStore.handleGetResult(ZKMetadataStore.java:244)
	at org.apache.pulsar.metadata.impl.ZKMetadataStore.lambda$batchOperation$7(ZKMetadataStore.java:188)
	at org.apache.pulsar.metadata.impl.ZKMetadataStore$$Lambda$177/0x00000008402da040.processResult(Unknown Source)
	at org.apache.pulsar.metadata.impl.PulsarZooKeeperClient$3$1.processResult(PulsarZooKeeperClient.java:490)
	at org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:712)
	at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:553)
   Locked ownable synchronizers:
	- None

(line numbers for https://github.com/datastax/pulsar/tree/ls210_2.3)
Anything else?
This issue is already fixed for master branch as a side effect of #19015. The PR commit has also been cherry-picked to branch-2.11 . This PR doesn't apply cleanly to branch-2.10 and a separate fix will be needed for branch-2.10.
Are you willing to submit a PR?

[X] I'm willing to submit a PR!

@lhotari this issue shoud be closed.Because relative pr had merged;


FLUID-6324: patch for 6.82.5 release of DocPad

This is a patch to allow us to build and deploy the documentation under a version of DocPad compatible with Node 10.
It makes the following substantive changes:

bumps the DocPad version to 6.82.5
adds the serve plugin to maintain static server support (DocPad made this a plugin rather than a built-in for the 6.8 line)
uses my forked and built version of the handlebars plugin, updated for compatibility with the 6.8 line: https://github.com/waharnum/docpad-plugin-handlebars/tree/fixFor6.8-build - I've had an outstanding pull request on the fix for this plugin since last December, but it has yet to be merged (https://github.com/docpad/docpad-plugin-handlebars/pull/13)

This should allow us to build and deploy the documentation in our usual way, in the immediate term.

@simonbates, would you be able to review this for merge when you have a chance? You should now be able to check out a clean copy of my branch, run npm install, and be able to build and work on the Infusion docs in the usual way.
@jhung Assuming this approach works for Simon we should be able to use it on the Guide site and other places DocPad is used.

@simonbates It looks like the reason for commenting out / removing the ghpages plugin was because that plugin is also currently broken and not updated for the most recent version of DocPad compatible with Node 10. So I think the current situation is now as follows:

this patch will produce the expected site in the out directory
the contents of the out directory needs to be committed to the deploy branch of the repo by some means; previously this was handled by the ghpages plugin, but that plugin is no longer working.

Options for moving forward that I see:

Patch the ghpages plugin like we did for the handlebars one (I don't consider this preferable, given how little this plugin is actually doing)
Use another means of committing the out directory to the deploy branch (Grunt task, or maybe do manually for the moment)

The Docker support that was being worked on in https://github.com/fluid-project/infusion-docs/pull/138 would make the separate deploy step unnecessary by using a builder container, but it isn't in yet (due to being blocked by the errors this mean PR is meant to fix).
I'd recommend we go with the need to make a manual commit of out to the deploy branch for the moment, given how infrequently we update the docs. Longer-term, we'll work on getting the Docker support in. Let me know your thoughts.

I agree with your proposal to manually copy out to the deploy branch. I think the Docker work would be a better task to spend time on, rather than getting the ghpages plugin to work, or automating the committing to the deploy branch.

I see that we are also changing from docpad-plugin-markit to docpad-plugin-marked. I will do some testing, but I was wondering: do we anticipate changes as a result? I'm thinking of details like automatically generated heading anchors?

I'm uncertain as to what changes we might see - I believe the change was made because docpad-plugin-markit hadn't been updated in three years, but it was made by @jobara.
I didn't see obvious issues but haven't tested extensively - automatically generated heading anchors seem to still be working.

I'm uncertain as to what changes we might see - I believe the change was made because docpad-plugin-markit hadn't been updated in three years, but it was made by @jobara.
I didn't see obvious issues but haven't tested extensively - automatically generated heading anchors seem to still be working.

Sorry I'm late to conversation @waharnum and @simonbates. There was a change from marked to mark-it a while ago as discussed in FLUID-6205.
If I recall correctly, Marked is still being used on our other docpad sites. Fluid docs is the only one using Mark-it. I will need to verify that.

I've generated the upstream master docs with Node 8 and generated the docs for this branch with Node 10. And then compared the generated output using a diff program (Beyond Compare). I'm seeing some differences:

"." is handled differently in generated anchors

master:
fluid.defaults(gradeName[, options])

FLUID-6324:
fluid.defaults(gradeName[, options])

Some minor typographical: ' instead of '
src/documents/UserInterfaceOptionsAPI.md has changes on master not on this branch (I think it's fine to leave this -- I note it here for completeness)

The only one I've found so far that is significant is the change in anchors. This will break related links, such as (fluid.hasGrade in https://github.com/fluid-project/infusion-docs/blob/master/src/documents/CoreAPI.md): ([defaults](#fluiddefaultsgradename-options))

I was trying to generate the master docs with Node 8 again today but was having trouble (error related to the ghpages plugin). And with Alan's help we were able to determine that the issue was that I had the latest version of Docpad installed globally (6.82.5). I was able to generate the docs with Node 8 and Docpad version 6.79.4, which can be installed with:
npm install -g<EMAIL_ADDRESS>

As discussed in-channel and in-person, I am going to close this in favour of this pull request that uses Docker containers pinned to Node Version 8.


How to get rid of association icon for "view" or "views" folder?

How to get rid of association icon for "view" or "views" folder?
I try set this up in settings but it doesn't work.

Do you want specifically this one or all folders to show the default icon?

Only this one.

Go to File > Preferences > Settings and add in User Settings the following:
"vsicons.associations.folders": [
    { "icon": "view", "disabled": true }
]

then press F1 and type Icons, select Apply Icons Customization.

Doesn't work.
Also worth to mention I tried also:
"vsicons.associations.folders":
[
	{
		"icon": "view",
		"extensions": ["view", "views"],
		"format": "FileFormat.svg",
		"disabled": true
	}
]

It works. I tested it. Check again.
Don't use your way it's wrong association.

@noNameInCity Try
"vsicons.associations.folders": [
    { "icon": "view", "extensions": [], "disabled": true }
]

you may've been hitting a bug I found.

Terribly sorry, you right. After reinstall plugin it works.


Rbac: Don't lookup null users

Followup to #9003
A few rbac calls use the User.current_user (and group) instead of passing those values into rbac.
While this is not common, it is getting hit for automate form autocomplete.
This removes 2 more queries. (chipping away at it)
before:
The code was looking up users and groups with a null id.
after:
It doesn't lookup up a null userid/groupid.
It goes straight to defaulting to the current user and group
https://bugzilla.redhat.com/show_bug.cgi?id=1337967

Makes sense.  Thanks @kbrock


Demo not working

@iankberry I tried using the demo on codesandbox, and nothing happened when I clicked the button.
Would you mind repairing that?

I'll take a look. It appears to be something about Chrome and codesandbox as it works (for me) in Firefox. It also works in Chrome if I check out the repo and run the example locally.

Hi @brandonmcconnell, this should be fixed now. Feel free to re-open if you're still seeing this issue.


Incorrect exit RC being returned from the apim script ?

API-Mgr. CLI version
1.1.0
API-Manager and Service-Pack Version
7.6.2/SP3
Expected behavior
In case there is an exception, return code from the script should be not equal =0
Actual behavior
If we are passing incorrect password to the script, we are getting an exception. Still the RC returned from the script =0.
Because of this , Jenkins pipeline job is always successful even though it caught an exception.
Can you please confirm if this is an issue or is this how it was intended to behave ?
Log-Output in Debug
Test case sample

Please describe the steps you have done to replicate the issue

Passed incorrect API Manager password to the script. See below stack trace outout:
----------------------------------------------------------------------------------------
API-Manager CLI: 1.1.0

To report issues or get help, please visit:
https://github.com/Axway-API-Management-Plus/apim-cli
----------------------------------------------------------------------------------------
Module: API - I M P O R T (1.1.0)
----------------------------------------------------------------------------------------
0      WARN     APIManagerAdapter| Login failed with statusCode: 403. Got response: '{"errors":[{"code":403,"message":"Invalid user or password"}]}' ... Try again in 1 second.
1491   ERROR    APIManagerAdapter| Login finally failed with statusCode: 403. Got response: '{"errors":[{"code":403,"message":"Invalid user or password"}]}' Got response: '{"errors":[{"code":403,"message":"Invalid user or password"}]}'
1496   ERROR         APIImportApp| Can't login to API-Manager
com.axway.apim.lib.errorHandling.AppException: Can't login to API-Manager
        at com.axway.apim.adapter.APIManagerAdapter.loginToAPIManager(APIManagerAdapter.java:231)
        at com.axway.apim.adapter.APIManagerAdapter.<init>(APIManagerAdapter.java:172)
        at com.axway.apim.adapter.APIManagerAdapter.getInstance(APIManagerAdapter.java:133)
        at com.axway.apim.APIImportApp.importAPI(APIImportApp.java:63)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at com.axway.apim.cli.APIManagerCLI.run(APIManagerCLI.java:138)
        at com.axway.apim.cli.APIManagerCLI.main(APIManagerCLI.java:76)
Caused by: com.axway.apim.lib.errorHandling.AppException: Login finally failed with statusCode: 403
        at com.axway.apim.adapter.APIManagerAdapter.loginToAPIManager(APIManagerAdapter.java:213)
        ... 9 more

@kunwardhwaj, thanks for reporting this. Of course this is not the intended behavior and will be fixed in the next version.

@kunwardhwaj, The issue is fixed and was basically an error in the CLI-Wrapper calling the module. The CLI-Wrapper hasn't taken over the returned error-code from the called module, such as API-Import.
If you want you can fix your pipeline now by calling the API-Import directly without using the CLI-Wrapper. The CLI wrapper is only required to provide that convenience menu to discovery available modules.
I assume you are using a JAVA-Call in your pipeline, which is currently configured like so:
com.axway.apim.cli.APIManagerCLI apim api import -c ......
Instead you can also call the import module directly:
com.axway.apim.APIImportApp -c ....
As you are using the pipeline integration, I guess you know about the Return-Code Mapping feature: https://github.com/Axway-API-Management-Plus/apim-cli/wiki/7.-Pipeline-integration#return-code-mapping
Which might be quite helpful in some situations.

Fixed


Error with the AoT Pre-Built on iOS

Works well on my computers but didnt works once I try it on iOS device, The error say it cant deserialize it.
Bolt.Addons.OscJack.Runtime is in the assembly options of Bolt and the AoT Pre-built was clear and regenerate.

I'm still not sure what was happening with it, but it doesn't reproduce with the current version.


Error "passing 'type' property is not allowed when 'template' is set" even when template set to null

Yes! I did!
Description
A clear and concise description of what the bug is.
In ngx-formly version 4 I had been emitting field json like this:
"type":"select",
"template":null,

This worked fine, but this was broken in commit 71d343e02dc49f3981cff5383b1ff76ff34eedc0, where the check was previously:
if (field.template) ...
So if the template were null, everything was fine.
But in this commit the check was changed to:
if (field.hasOwnProperty('template') ...)
which is true even if the value of "template" is null.
So now I'm getting the error:
NgxFormly: passing 'type' property is not allowed when 'template' is set.
In my opinion the error is not really correct ... if "template" is null it is not actually being "set" to anything.
Is there a reason you are no longer checking to see if the template has been set?
I don't know about the larger issue you were trying to fix, but if you have no objection I could do a pull request with line 77 changed to:
(field.hasOwnProperty('template') && field.template)
Minimal Reproduction

In the stackblitz note that the text input and select question have disappeared because I set template: null for both of them:
https://stackblitz.com/edit/ngx-formly-ui-bootstrap-bsjvxi?file=src/app/app.component.ts
Your Environment

Angular version: 9.0.2
Formly version: 5.5.12

Additional context
Add any other context about the problem here.

I have downgraded to 5.5.7 for the time being and the fields in my forms are showing again.

is there any relevant reason that prevent you to remove entirely template instead of set it to null?

The json is generated programmatically using Spring on the server side. So if the template is not set the json is generated as template: null.
The problem, starting with ngx-formly 5.5.8, is that the code no longer checks if the template is set (despite what the error message says): it now only checks to see if the template attribute exists.
In my proposed fix ngx-formly would once again check to see if the template were set.

This issue has been fixed and released as part of v5.5.14 release.
as @kenisteward suggested It would be better to avoid passing unnecessary data 😄!


Update Phantom Wallet logo

Updated Phantom wallet logo to be our new branded logo
https://twitter.com/phantom/status/1674513272115175424

Thanks! This will be released once CI runs.


Subscribe Button

Not so much an issue as it is a question. Ive gotten everything to work, I was curious about the subscribe button though. Does that only become activated if you upgrade your stripe account or something? Might be a dumb question but I appreciate anyone's guidance... I was trying to look through the files to understand the functionality there but I'm not entirely sure if I'm missing something obvious...

No, the subscribe button should work as long as the user is logged in.


fiji: 20201104-1356 -> 20240614-2117

Description of changes
This PR updates FIJI, a powerful image analysis tool, and adds myself as a maintainer. The previous maintainer orphaned the package 8 months ago and the package hasn't been updated since it was added in 2020.
A note as well: I am unable to run nixpkgs-review on my laptop. Any assistance would be appreciated.

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.

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

@ofborg build fiji


leetcode assignments

testing out the leetcode assignments

testing out sending the request back for more changes.

@prasantadh trying to get some attention on this issue
experimenting with notifications.


✨ Add Documentation to Define an Agile Delivery Process

User Need
As a member of the Operations Engineering team
I want to understand how to approach building, maintaining and de-commissioning new and old services
so that I can easily create tickets that support the work for new projects/ideas
and analyse whether an existing system needs to be considered for de-commissioning
This ticket is to document a practical MvP process the team can follow to ensure we are building services using agile methodologies.
Value
To formalise our approach to building new projects and maintaining existing services to ensure they provide value and can be critically analysed later.
Formalising and explicitly documenting our approach will also enable us to critically analyse the approach itself during retrospectives, allowing us to make incremental changes over time to ensure we have a process that meets the teams and organisational needs.
Functional Requirements:

Documented in our runbooks

Non-Functional Requirements:

The document should be easy to read, understand and reference
We should use the GOV.UK Agile Delivery Guidance in the Service Manual as a reference for building a more applicable approach for our team.

Acceptance Criteria:

[ ] An MvP document added to our runbooks, detailing our approach to building and maintaining services

Notes:

GOV.UK Agile Delivery
Operations Engineering Runbooks

Aged out


【Android】Rotating a gltf model，How to set different rotation axes?

Hello.The example shows how to rotate：
Matrix.setRotateM(transformMatrix, 0, -(a.animatedValue as Float), 0.0f, 0.0f, 1.0f)
val tcm = engine.transformManager
tcm.setTransform(tcm.getInstance(renderable), transformMatrix)
but is there only a rotation method based on the x, z, and y axes? If I want to customize the rotation axis, what should I do instead?

What do you mean? This method lets you choose the rotation axis.

My expression is not clear. What I mean is:
public static void setRotateM(float[] rm, int rmOffset,
float a, float x, float y, float z)
Is the rotation axis determined based on the starting point (0,0,0) and the ending point (x, y, z)?
If I want to set the starting point of the rotation axis, how do I set it?
For example, I want to set a rotation axis called z1. z1 parallel to the z-axis, at the upper right of the z-axis, the distance from the x-axis is a, and the distance from the y-axis is b.
I wanted to rotate the model with z1, but it didn't work. Here is my code:
val transformMatrix = FloatArray(16)
tm.getTransform(entity, transformMatrix)
Matrix.setRotateM(transformMatrix, 0, degrees, 0.0f, 0.0f, 1.0f)
Matrix.translateM(transformMatrix, 0, a, b, 0.0f)
tm.setTransform(entityInstance, transformMatrix)
What is the problem?

你是什么意思？此方法允许您选择旋转轴。

The x, y and z params in this method define the axis of rotation. Passing 1,0,0 rotates around X, 0,1,0 around Y, etc. You can combine them too: 1,1,0 to rotate around the XY axis, or 0.5,1,0 to rotate half as much around X as around Y.
If you want to set the origin of the rotation you need to use translations as well.


Update shared:core, shared:fs2 to 1.2.0

Updates

com.softwaremill.sttp.shared:core
com.softwaremill.sttp.shared:fs2

from 1.1.1 to 1.2.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.softwaremill.sttp.shared" } ]

labels: library-update, semver-minor

Requires cats-effect 3


[NPM] Negative cache route lookups

What does this PR do?
Negative caches failed route lookups. Not doing this can lead to excessive route lookups (via netlink) on some hosts. Results from a host where we were doing a lot of failed netlink lookups:

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


Update README.md

He is crazy

Thank you for your contribution! He was certainly a kooky guy in Pikmin 3.


no purge after opening link in new tab

:tada: This issue has been resolved in version 1.1.0 :tada:
The release is available on:

v1.1.0
Chrome Web Store
GitHub release

Your semantic-release bot :package::rocket:


Fix - sec vuln just extend

Description
We just started getting security vulnerability messages from the just-extend dependency in sinon. This is not a high priority, however the change is easy and very very low risk.
This PR updates sinon and sinon-chai to remove the sec vuln for the broker
See https://nvd.nist.gov/vuln/detail/CVE-2018-16489
Related PRs
List related PRs if applicable
Todos

[ ] Tests
[ ] Documentation
[ ] Link to Trello

 just-extend security vuln in broker


Take2

This PR relaxes requirements, allowing for Intake Take2.
Necessary to avoid dependency conflicts.

What's the correct process for getting the right version of intake-esm in for testing?

With the relaxed versioning, you should be able to just pip install intake>=2.0.0 in the environment.
I'm happy to add a tox config like we have for access-nri-intake-catalog too to automate the testing against 0.7 & 2.0 if you think that would be more robust?

The issue isn't intake, it's intake-esm. That has requirements that lock intake to <2, so I need to grab whichever version of intake-esm you have onboard to relax that requirement.

Ahhh, of course - I'll add a toxfile to run the tests with that version of intake-esm.

Awesomesauce. We can always remove the tox once we're satisfied that the changeover is good and/or intake v1 is finally killed.

You should now be able to run the tests against intake>=2.0.0 just by calling $ tox

Tox tests are passing OK, so I'm happy.

@dougiesquire Whilst you're at it could you add Marc as an admin here too?

Great, thanks for doing this @charles-turner-1

@dougiesquire Whilst you're at it could you add Marc as an admin here too?

I've made you both admin

Cross linking to #62 for posterity. Seems that broken tests with take2 dependency were fixed at some point by upstream changes.


Sidebar menu - do not collapse automatically

Hi,
The default functionality for the sidebar multi-level menus is to collapse automatically when another menu is clicked. Is it possible to keep multiple menus open and only close a menu if you click on that same menu again?  What I have in mind is something like what's at the link below.
http://www.bootply.com/90JfjI2Q7n
Thanks for any help/suggestions you can provide.

Hi,
I think that you should request this in the official AdminLTE repository: https://github.com/almasaeed2010/AdminLTE
Note that this package just provides a way to integrate AdminLTE with Laravel and does not modifying functionality of AdminLTE in any way.

Appreciate the response and suggestion. Thanks!

No problem, you're welcome! Thanks for the interest in this package. 😄


RegisterCategoryFunction

Addon Version
10.2.7
World of Warcraft Version
Retail
Describe the bug
27x BetterBags/data/categories.lua:274: category function already registered: reg
[string "=[C]"]: in function assert' [string "@BetterBags/data/categories.lua"]:274: in function RegisterCategoryFunction'
[string "@BetterBags-Openable/main.lua"]:186: in main chunk
Locals:
(*temporary) = false
(*temporary) = "category function already registered: reg"
Steps to reproduce
I logged into the game and bugsack informed me of the error.

Do you have any plugins for BetterBags installed? If yes, which ones?

All of them
On Sat, May 25, 2024 at 3:53 PM DJSchaffner @.***>
wrote:

Do you have any plugins for BetterBags installed? If yes, which ones?
—
Reply to this email directly, view it on GitHub
https://github.com/Cidan/BetterBags/issues/384#issuecomment-2131436956,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BIXGCTKMLP2XYIKMAOU5R23ZED24TAVCNFSM6AAAAABII5N3M2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZRGQZTMOJVGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

You have plugins that are doing duplicate functions. Plugins are not written by the BetterBags team directly. The error message indicates "BetterBags Openable" might be the cause, but only because it's trying to do the same thing as another plugin.


A broken link to the NeurIPS 2021 dataset in the paper

The paper about NeurIPS 2021 competition, which is also referenced in the Best practices book (e.g., this chapter), contain a link to the dataset: https://openproblems.bio/benchmark_dataset . Unfortunately, this link is not working.

Could you please fix this link and put the dataset back there? I think, it is important for community, and also would make the best practices book more reproducible. Maybe it also makes sense to write a test checking that the link works as expected

Hey @VladimirShitov !
Thanks for reporting this issue!
I added a redirect to the list of redirects:
Contents of _redirects:
/competitions /events
/neurips /events/2021-09_neurips
/neurips_2021 /events/2021-09_neurips
/neurips_2022 /events/2022-08_neurips
/neurips_2023 /events/2023-08_neurips
/neurips_2021_docs/* /events/2021-09_neurips/documentation/:splat
/competitions/neurips_2021 /events/2021-09_neurips
/competitions/neurips_2022 /events/2022-08_neurips
/competitions/neurips_2021_docs/* /events/2021-09_neurips/documentation/:splat
/jamboree /events/2021-03_jamboree
/benchmark_dataset /events/2021-09_neurips/documentation/data/dataset.html

These redirects were added to ensure that old URLs still point to the right content, but somehow this one was missed.
I don't plan on adding tests to the website repo, since it's mostly a collection of markdown files.
If you encounter any more issues, feel free to let us know :)


minor fixes & improvements

Hi! thank you for this nice & simple library.
I wanted to use it but was missing the Copy derivation. I also took the oportunity to fix several clippy warnings and make a function const.

It would also be nice to make a release for midi-convert re-exporting the updated midi-types version.

Thank you, this looks good.

@joseluis hope you still get this message after the PR was merged :-) I just released your fixes as midi-types version 0.1.6. A new midi-convert with an updated midi-types should be coming soon.


UI is getting destorted Productlarge Componenet

Here is Picture

Hello @avinashji1302, Thank you for pointing out this issue, Clearly the website is not responsive.

Hello @avinashji1302, Thank you for pointing out this issue, Clearly the website is not responsive.

So please assign me....I will fix it  on Saturday

Sure, I have assigned you the issue.