feat: Add core-metadata device service related db methods for postgres

related #4909

If your build fails  due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[x] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[x] I am not introducing a new dependency (add notes below if you are)
[ ] I have added unit tests for the new feature or bug fix (if not, why?)
[ ] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[ ] I have opened a PR for the related docs change (if not, why?)

Testing Instructions

New Dependency Instructions (If applicable)

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 0% with 139 lines in your changes missing coverage. Please review.

Project coverage is 37.40%. Comparing base (31004d1) to head (8c22ab0).
Report is 1 commits behind head on main.

Files with missing lines
Patch %
Lines

...rnal/pkg/infrastructure/postgres/device_service.go
0.00%
127 Missing :warning:

internal/pkg/infrastructure/postgres/sql.go
0.00%
11 Missing :warning:

...nternal/pkg/infrastructure/redis/intervalaction.go
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4913      +/-   ##
==========================================
- Coverage   37.93%   37.40%   -0.54%
==========================================
  Files         122      123       +1
  Lines       11806    12112     +306
==========================================
+ Hits         4479     4530      +51
- Misses       6944     7188     +244
- Partials      383      394      +11

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


Delete test_public.sh

删除无用测试内容

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Set held_type of World to shared_ptr

This is necessary to pass world to dart::gui::SimWindow(...) that takes only shared_ptr<World>.

Resolved by #64


Add Task for code quality and CI

JSHint + TravisCI?

Done in https://github.com/afonsopacifer/react-pomodoro/commit/7c4d40c446a35a45b328d01cac200ee427af6dc7


literature limit not working

We recently moved the literature endpoint from using APIv1 to go straight to ElasticSearch (this was done to allow users to have richer scopes). In that process the limit parameter stopped working.

@MortenHofft would this be the reason the literature on gbif.us is not paging correctly? The issue is that no matter what page you go to it's the same papers listed.

It sounds likely, though at the time when I created this issue it was my conclusion that this only mattered for a single user of the unstable API and hence wasn't a priority. I will check, it sounds a lot like I've missed something!

It is fixed and is deployed to staging

@MortenHofft Thank you, it was easy to fix that thanks to your message :) https://github.com/gbif/hp-living-norway/commit/851e50e905c68e940e57ebd508a4930c6b52240c


Official code for FCANet?

Hi, @cfzd
I have paid attention to FCANet from last year, so is this official code?

@1187697147
Yes, it is  : )

@cfzd,
Thanks for your reply! I found that FCANet must set dct_w/h when initliaze the model, Is there any way to adapt the input size?

@1187697147
FcaNet could support arbitrary input size. I have made a commit to fix the bug. You can try it with(you might need to delete the old cached file to make the torch hub update new code):
import torch
model = torch.hub.load('cfzd/FcaNet', 'fca50' ,pretrained=True)
x = torch.zeros(1,3,224,224)
y = model(x)
x = torch.zeros(1,3,300,300)
y = model(x)

@cfzd Okay, I will try and thanks for your work!


Bedtools cannot be matched

Hi , thanks for the very helpful package!
I have used the method in the https://github.com/gao-lab/GLUE/issues/22#issuecomment-1161983847, but it didn't solve my question.Could you give me a help?Thanks!
BEST!
XUE

I can run the code in the ipython at the same conda environment, is there any wrong with my jupyter Lab?
Cause the Lab was installed by root, I doubt something wrong with the pathway of the bedtools in the Lab. How could I fixed it?

Thanks for your interest in GLUE!
The scglue.config.BEDTOOLS_PATH should be set to the bedtools executable itself, rather than the bin directory.
scglue.config.BEDTOOLS_PATH = "/data/user/xhw/miniconda3/envs/scglue/bin/bedtools"

The results was the same.

I tried to change the code as follow, but it didn't work.
CHECKERS = dict(
    bedtools=CmdChecker(
        "bedtools", f"{‘/data/user/xhw/miniconda3/envs/scglue/bin/bedtools’} --version", r"v([0-9\.]+)",
        vmin="2.29.2", install_hint=INSTALL_HINTS.bedtools
    ),
    plotly=ModuleChecker(
        "plotly",
        vmin=None, install_hint=INSTALL_HINTS.plotly
    )
)

Well that's strange. Could you confirm that the executable file "/data/user/xhw/miniconda3/envs/scglue/bin/bedtools" exists? E.g., check ls /data/user/xhw/miniconda3/envs/scglue/bin/bedtools.
Meanwhile, the code change should be:
CHECKERS = dict(
    bedtools=CmdChecker(
        "bedtools", "/data/user/xhw/miniconda3/envs/scglue/bin/bedtools --version", r"v([0-9\.]+)",
        vmin="2.29.2", install_hint=INSTALL_HINTS.bedtools
    ),
    plotly=ModuleChecker(
        "plotly",
        vmin=None, install_hint=INSTALL_HINTS.plotly
    )
)

And you would need to restart the jupyter kernel to make the code change effective (reimporting scglue will not work).

I have done all the suggestions you gived as follow, but it seemed no working.

I have finished the data processing in the ipython, it worked well.  So the problem doesn't matter. Thanks for your nice job and patience.
BEST!
XUE

Okay great! Let me know if there are further issues though.


chore(main): release 3.1.5

:robot: I have created a release beep boop
3.1.5 (2024-07-25)
Bug Fixes

grug-far appending extra text at the end of replaced files (#263) (be2ac43)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v3.1.5
:sunflower:


How to calculate yaw value and yaw coefficient

I used the pose estimator in dlib to predict the yaw angle and calculated the yaw coefficient according to the formula given in the article, but it is very different from the value that author given in IJBA.

Please refer to this issue #2


Request for Privacy Changes Updates in SDK and Required Signed XCFramework.

We are using the TTLock third-party SDK in our iOS project. Could you please confirm whether you are planning to adopt the privacy changes mentioned in the article "Privacy changes for app developers"? This is important because failure to comply could result in Apple rejecting our app. Please find the below reference links.

https://developer.apple.com/documentation/bundleresources/privacy_manifest_files
https://www.adjust.com/blog/privacy-changes-for-app-developers-ios-17/

Additionally, we require a signed XCFramework for the TTLock.  As we are using it as Swift package.

https://developer.apple.com/documentation/xcode/verifying-the-origin-of-your-xcframeworks

Ok, we have received it and will reply in the next two days.

Ok, we have received it and will reply in the next two days.

Ok, Thank you for quick response.

The listed SDKs will affect app release.
https://developer.apple.com/cn/support/third-party-SDK-requirements/
This SDK does not require any privacy , you can use it with confidence.

The listed SDKs will affect app release. https://developer.apple.com/cn/support/third-party-SDK-requirements/
This SDK does not require any privacy , you can use it with confidence.

Thank you for the clarification.

We also required signed Xcframework for TTlock. Any update on the same?
https://developer.apple.com/documentation/xcode/verifying-the-origin-of-your-xcframeworks

The listed SDKs will affect app release.
https://developer.apple.com/cn/support/third-party-SDK-requirements/
This SDK does not require signed.

We require a signed XCFramework for TTlock to be used within a Swift package, allowing it to be utilized in other projects.
We have tried with current unsigned XCFramework but getting an error. Please find the below attached error screenshot.

TTLock.xcframework.zip
please try this one. if ok, we will update it.

TTLock.xcframework.zip
please try this one. if ok, we will update it.

Thank you for sharing signed Xcframework quickly. We tried to add into watchOS target but we face below error.
While building for watchOS, no library for this platform was found in '/Frameworks/TTLock.xcframework'.
So kindly request to send us updated signed Xcframework with watchOS support.

TTLockWatchOS.xcframework.zip
please try this one.

Thanks for sharing the watch Xcframework!
We noticed an update for TTLock framework. Could you please add the watch Xcframework to the repo?
This ensures any changes in TTLock framework also apply to the watch OS Xcframework.
Appreciate your help!

Updated watch OS Xcframework

Updated watch OS Xcframework

Where is it?

https://github.com/ttlock/watchOS_SDK


Can ecurve use bitcoin's wallet public key to encrypt a message?

I'd like to perform asymmetric encryption using the public key (derived from wallet address) and decrypt by private key.
I assume 'bitcoinjs-message' uses ecurve/ecdsa internally to hash and sign a message, and I know ECDSA in general is capable of asymmetric encryption, but can't find example or MB it's not even implemented.

@Livshitz I don't think this library should be used in projects going forward.
Please use elliptic.


Make publisher dashboard no-jobs text depend on filters

And use private attr_readers where possible in VacanciesComponent, and refactor the spec thereof.
Previously, we displayed the text 'You currently have no [type] jobs', even when thatvwas not true, when the filters were applied such that there were no [type] jobs belonging to the filtered job locations.
This was deemed misleading.
Now, the text displayed when there are no jobs to display varies depending on whether any filters are applied.
This text has been reviewed by Content Design.
Screenshots of UI changes:

Review app deployed to https://teaching-vacancies-review-pr-3054.london.cloudapps.digital


Patch: Add non-ix alternative solution to Puzzle 8

Thanks! This solution does need to be fixed following the deprecation of ix.
Your proposed code works, but chaining indexing operations in pandas is generally discouraged. I think we should go with one of the alternatives for ix that's mentioned in the docs. Probably this one:
df.loc[df.index[[3, 4, 8]], ['animal', 'age']]

We can just delete the ix solution since it will soon be gone for good.
Do you want to make these changes to the pull request and then I'll merge?

Still figuring out how to use Github properly, and I hope I've done it right. I've made the necessary changes to the patch branch.

That's perfect - I've merged the changes you made. Thank you!

Happy to contribute. Been going through your exercises, they're very helpful. I'll make suggestions if I find anything else.


BUG: Implementation of Bessel Functions in Scipy

Describe your issue.
According to the documentation in scipy, the spherical bessel function (https://docs.scipy.org/doc/scipy/reference/generated/scipy.special.spherical_jn.html#r1a410864550e-3)
is implemented using a recursion relation provided in the documentation:
(https://dlmf.nist.gov/10.51#E1)
However, there are two issues I seem to have with this:

The documentation says that for arguments bigger than the order, reference [1] is used and for small arguments
reference [2] is used. However, when rearranging reference [2], I get the same equation as in reference [1], which seems
very suspicious to me. Can someone explain this?

When using the relation given in the reference, it only seems to hold for arguments bigger than the order
but not for arguments smaller than the order, even though the documentation specifies that for small arguments
the same relation is used.

PLEASE clarify this. It is a very important and urgent issue for me.
Reproducing Code Example
#Implementation using the derivative definition for the spherical bessel functions
def besselrecursion(n,x):

    if n >= 2:
        result = (2*(n-1)+1)/x * besselrecursion(n-1,x) - besselrecursion(n-2,x)
    elif n == 1:
        result = np.sin(x)/x**2 - np.cos(x)/x
    elif n == 0:
        result = np.sin(x)/x
    return result

#Alternative definition of the recurrence relation using the implemented jn directly

def besselrecursion(n,x):

    if n >= 2:
        result = (2*(n-1)+1)/x * besselrecursion(n-1,x) - besselrecursion(n-2,x)
    elif n == 1:
        result = spherical_jn(1,x)
    elif n == 0:
        result = spherical_jn(0,x)
    return result

#already with order 30 and argument 12 the results vary greatly
z = 12
n = 30
print(besselrecursion(n,z))
print(spherical_jn(n,z))

Error message
No Error message

SciPy/NumPy/Python version information
1.7.1 1.19.5 sys.version_info(major=3, minor=8, micro=11, releaselevel='final', serial=0)

Hi! Maybe having a look at the tests and implementation could give you some insights? https://github.com/scipy/scipy/blob/57bf4d674c6d31ce5e070498c8cbdc0f2ea8c8d6/scipy/special/tests/test_spherical_bessel.py#L14
https://github.com/scipy/scipy/blob/master/scipy/special/_spherical_bessel.pxd

Thanks for the answer. I checked it out but it doesn't give any more information regarding the problem.
In any text I can find there is no restriction on order or argument for which the recursion relation holds.
So as far as I can see the recurrence relation has to hold for every order and every argument.
However, as can be seen from my code example, if I implement the recursion relation, the values do not
match the values computed by the implemented functions.
This is the problem and (at least for me) to solve this problem one of two things are needed.
Either (1) there is a source specifying that this recurrence relation only holds for arguments bigger than the order
(documentation page says that but I didn't find any independent source verifying this), or (2) there is something
wrong with the implementation in scipy and the recursion relation gives the correct values.
Any help is greatly appreciated.
Here some sources for the recursion relations:
Handbook of mathematical functions, Abramowitz, p.439
The NIST link provided above doesn't specify a constraint on the argument/order either

Also, the documentation talks about the "definitional relation to the cylindrical Bessel functions"
(https://docs.scipy.org/doc/scipy/reference/generated/scipy.special.spherical_jn.html#scipy.special.spherical_jn)
However, I cannot find any reference anywhere to "cylindrical" Bessel functions or a "definitional" relation.

@pontsm, the "cylindrical" Bessel functions are just the usual ones, scipy.special.jv(v,z). The docs can definitely be improved. If you look at the relevant part of the implementation, you see that it dispatches to the usual Bessel function when n>=x. This is what's meant by the "definitional relation". Meanwhile, when x>n, the multiplicative factors in the recurrence relation will have absolute value less than one. That's the region where using the recurrence relation is advantageous.

@duetosymmetry Thank you for the code reference and your answer! This helped.
It did, however, not yet fully answer why the recurrence relation seems to give values that diverge more and more
from the correct value when applying it to x<n, for example x=12, z=30, which is the case in the code example above.
Is the recurrence relation only valid for x>n? This is the statement I cannot find anywhere in literature.
Thank you again :)

The recurrence relation is valid everywhere in the complex plane. Back on the DLMF, they include conditions for when an identity is valid. Here the only condition is that n=1, 2, …, but z is any complex variable.
As n becomes very large with fixed z, the result for spherical_jn(n,z) becomes exponentially small (see the asymptotic expansion on the DLMF and apply the relationship between ordinary and spherical Bessel functions). This means that if you tried to use the recurrence relation to compute spherical_jn, you would be relying on very large cancellations. This will be extremely inaccurate. This is why the code only uses the recurrence relation when n < |z|.

I think this issue is settled so I'll close but feel free to continue discussion if there is anything left


Support Jenkins CLI environment variables

The Jenkins CLI guide suggests setting $JENKINS_URL, $JENKINS_USER_ID, and $JENKINS_API_TOKEN to avoid having to pass them as command line arguments.
However, this plugin expects $JENKINS_HOST, $JENKINS_USERNAME, and $JENKINS_TOKEN, respectively.
Would you be opposed to supporting the official CLI environment variables? I would be happy to do the legwork, I just wanted to confirm first.

Hey @HoldenLucas!

Would you be opposed to supporting the official CLI environment variables? I would be happy to do the legwork, I just wanted to confirm first.

Sure, to be honest I'm not sure why I picked those names over the actual ones that are suggested. One thing I'd recommend though is to advertise the recommend ones but still keep the old ones and just alias them. Mainly I want to avoid this breaking for anyone that already has those set.


Add thumbnails to the raster function templates

Sentinel1_RTC_Power.rft.xml and Sentinel1_RTC_dB.rft.xml look like what I expect, adding <Thumbail> and <ThumbnailEx> values. I notice <Thumbnail> refers to a local file on your computer. I wonder if that value is necessary if we're providing the image itself in the <ThumbnailEx> field.
Sentinel1_RTC_Amplitude.rft.xml and Sentinel1_RTC_dB_Stretch.rft.xml have some structural changes I didn't expect. The double-quotes changed to single-quotes, and the first line of <?xml version="1.0" encoding="utf-8"?> disappeared. Were these intention?

Good call. I think we can actually remove that path. It's just there to
document the action of adding the thumbnail.
On Thu, Mar 2, 2023 at 3:33 PM Andrew Johnston @.***>
wrote:

Sentinel1_RTC_Power.rft.xml and Sentinel1_RTC_dB.rft.xml look like what I
expect, adding  and  values. I notice
refers to a local file on your computer. I wonder if that value is
necessary if we're providing the image itself in the  field.
Sentinel1_RTC_Amplitude.rft.xml and Sentinel1_RTC_dB_Stretch.rft.xml have
some structural changes I didn't expect. The double-quotes changed to
single-quotes, and the first line of  disappeared. Were these intention?
—
Reply to this email directly, view it on GitHub
https://github.com/ASFHyP3/gis-services/pull/27#issuecomment-1452767990,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOYE56Y7KMVJ2F7CTMPQUDLW2E36PANCNFSM6AAAAAAVOAHCMA
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Heidi Kristenson
Alaska Satellite Facility
Senior GIS Specialist
(907) 474-7471

I now notice the formatting changes in Amp and dB_Stretch bring them in line with the other two, so no concerns there.

Yes, I'm not sure why they'd been strange before. I used the PyCharm
reformat code function to tidy up the indentation, etc. of the rft files
the first time around, but it's possible they were generated on different
versions of Pro or something that resulted in different formatting. Once I
ran them through Pro to add the thumbnails, all formatting was lost again
(specifically the new lines and indentation; it was essentially one line of
soft-wrapped code), so I re-ran the reformat code to make them readable. I
think they are now more consistent across the board.
On Thu, Mar 2, 2023 at 3:36 PM Andrew Johnston @.***>
wrote:

I now notice the formatting changes in Amp and dB_Stretch bring them in
line with the other two, so no concerns there.
—
Reply to this email directly, view it on GitHub
https://github.com/ASFHyP3/gis-services/pull/27#issuecomment-1452769611,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOYE566QEY2VQ57NUCJQP4DW2E4I3ANCNFSM6AAAAAAVOAHCMA
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Heidi Kristenson
Alaska Satellite Facility
Senior GIS Specialist
(907) 474-7471


Update cloud-architecture-models.md

Made changes from Enterprise Architects to IT Architect as the information pertains generally to IT architects.

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/5049

@JohanFreelancer9 Please copy review

@samanro Please merge this PR. Thanks


Create a deployment backout plan

Create a wiki page with instructions on how to roll back via cap

If the cap deployment is unsuccessful  no roll back is needed
The current directory may have moved if cap was in cleanup when it failed
If the cap deployment is successful roll back

FYI, Capistrano logs each step of the process to your terminal after you run deploy. If you see deploy:symlink:release execute successfully, then the app has been deployed. There are six additional steps that follow this, in order:

deploy:resquepoolrestart
deploy:resolrize
deploy:passenger:config_update
deploy:cleanup
rbenv_custom_ruby_cleanup:purge_old_versions
deploy:log_revision

If any of the above fail, it may appear that the deploy failed, but it didn't. The new application version is out there. It's possible to re-run these tasks, if needed. Ex:
bundle exec cap deploy:log_revision BRANCH_NAME=[release-branch]
But not all of them are critical for a successful release.

Added a wiki page for rolling back:
https://github.com/psu-stewardship/scholarsphere/wiki/Deployment-Rollback-Procedure


AKS 1.27 with Cgroups V1?

AKS 1.27 is listed with Cgroups V1 and not V2, can this be right? Are you reverting the default of using cgroups v2?

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

ID: ec484163-5d73-af3a-3d7b-9e0d421d2824
Version Independent ID: 42da7aed-a33d-e331-fb7f-4fb4b40e5813
Content: Supported Kubernetes versions in Azure Kubernetes Service (AKS). - Azure Kubernetes Service
Content Source: articles/aks/supported-kubernetes-versions.md
Service: azure-kubernetes-service
GitHub Login: @palma21
Microsoft Alias: jpalma

@pauska
Thanks for your feedback! We will investigate and update as appropriate.

@pauska
Since this issue isn't directly related to improving our docs, and to gain a better understanding of your issue, I'd recommend working closer with our Q&A forum by posting your issue there so our community, and MVPs can further assist you in troubleshooting this issue or finding potential workarounds.
[Teams Q&A forum] (https://docs.microsoft.com/en-us/answers/topics/46488/office-teams-windows-itpro.html) for technical questions about the configuration and administration of Microsoft Teams on Windows.
[Microsoft Teams Community forum] (https://answers.microsoft.com/en-us/msteams/forum?sort=LastReplyDate&dir=Desc&tab=All&status=all&mod=&modAge=&advFil=&postedAfter=&postedBefore=&threadType=All&isFilterExpanded=false&page=1

@SaibabaBalapur-MSFT No, I am specifically asking for clarification if the documentation is correct, as cgroups v1 is depracated. It would be a very strange move to go from cgroups v1 to cgroups v2, and then back to v1 again.

@

@pauska
I'm going to assign this to the document author so they can take a look at it accordingly.
@palma21
Can you please check and add your comments on this doc update request as applicable.

#Reassign:Nickomang

@pauska, Thanks for catching this! 1.27 (and future versions) will continue to use Cgroups V2 and the table has been updated accordingly.
#please-close


Connection Error

Hello, when this line:
LOG_PRINTFLN("Connection error: %i", rc);
is rturning:
Connection error: %i-5
or
Connection error: %i-6
what do these errors mean?
What is the meaning of the other numbers it can return?

It just prints the value of the rc.
I assume you are about the rc of the connect call: Error::type connect(const MQTTPacket_connectData& connectOptions, ConnectResult& result) call.
See enum for all possible Error::type values: MqttClient.h#L200
See the connect implementation to find more details: MqttClient.h#L469


Docs on custom scalar types

I've been struggling with getting a custom scalar type working with GraphQLite.  I'm running into a number of issues, but at the end of the day, I'm just not clear on how everything is supposed to work.
The type mappers are quite confusing as there seem to be a lot of them used by GraphQLite internally.  IMO, the library shouldn't use anything but the basic scalar types by default, and allow you to add custom, or pre-built, type mappers/scalar types during configuration.
Overall though, I just don't really understand how to get this working.  A full code example would be awesome.  In fact, an entire sample codebase that shows how everything is wired up would be even more helpful.
Most of the confusion stems from 2 places.

Knowing how to register these scalar types properly.  Do you use the $factory->addTypeNamespace() method?  Do you just $factory->addRootTypeMapper() and allow it to handle the mapping without needing to register the custom scalar?
Why do I need a mapper and a scalar type?  I must be missing something, but it'd seem to me I could just register a custom scalar type that implements a given interface and the default mapper would attempt using it.  Maybe there is some additional flexibility to having a custom root typemapper as well (probably is), but I'm not seeing it.

I was finally able to get custom scalar types working.  The issue, at the end of the day was that the mapper must not return a new instance of the GraphQL type.  By using a static cached property of the type object on the mapper, it resolves this issue.
For those that might come across this confusing error and see this issue, the error in question is:

Schema must contain unique named types but contains multiple types named "Date". Make sure that type loader returns the same instance as defined in Foo.date (see http://webonyx.github.io/graphql-php/type-system/#type-registry)."

The error message made me think that the getter method that was annotated had to return the actual GraphQL type and that I couldn't map it accordingly.
It would still be really helpful for the docs to explain more on how to write and register custom scalar types.  I think this is a very common need for people and I agree with the reference implementation's opinion of not implementing these by default as there is a wide variety of needs for each application.  Therefore, I suggest the removal of the DateTime scalar type from being mapped and instead support a way for it to be configured/mapped, should the developer wish to do so.

I'm reopening this issue.  I've updated to the latest code and things have broken with type mapping.  I have most of it pieced together again, but the custom scalar type mapping is broken again.
The docs on this subject aren't exhaustive enough.  I have no idea how to handle the following:
/**
 * @GraphQLite\Type()
 */
class Product
{
    protected Money $amount;

    /**
     * @GraphQLite\Field()
     */
    public function getAmount(): Money
    {
        return $this->amount;
    }
}

How do I tell GraphQLite how to handle a Money object, how to convert that to a scalar value?  I see the docs on creating the mapper and factory.  I have done that.  Does this Money object have to extend GraphQL\Type\Definition\ScalarType?  If so, how is one supposed to go about that?  That class has a pretty hairy constructor.

Okay, after some digging, I was able to figure out the issue.  I'll leave some details here for other folks that might come across this.
Firstly, you're going to want to create a new scalar type object that extends GraphQL\Type\Definition\ScalarType and implement it to do the conversion.  It's probably very possible to create a single one of these that follows an interface.  I haven't gone down that path though.  I know there are some other interfaces pointing to using serialize, etc.
Here is my custom type mapper that I created which handles all of our custom types:
<?php

declare(strict_types = 1);

namespace Acme\GraphQL\Type;

use GraphQL\Type\Definition\InputType;
use GraphQL\Type\Definition\NamedType;
use GraphQL\Type\Definition\OutputType;
use GraphQL\Type\Definition\ScalarType;
use phpDocumentor\Reflection\DocBlock;
use phpDocumentor\Reflection\Type;
use Acme\Cog\Date;
use Acme\GraphQL\Type\Scalar\Date as DateType;
use TheCodingMachine\GraphQLite\Mappers\Root\RootTypeMapperInterface;

/**
 * Handles the type mapping for GraphQL
 *
 * @author Jacob Thomason<EMAIL_ADDRESS> */
class Mapper implements RootTypeMapperInterface
{

    protected RootTypeMapperInterface $next;

    protected array $typeMaps;

    /**
     * Constructor
     *
     * @param RootTypeMapperInterface $next
     */
    public function __construct(RootTypeMapperInterface $next)
    {
        $this->next = $next;

        // Define your type maps here
        $this->typeMaps = [
            'Date' => [Date::class => new DateType()],
        ];
    }

    /**
     * Gets the type maps
     */
    protected function getTypeMaps(): array
    {
        return $this->typeMaps;
    }

    /**
     * Gets the respective type for a type name
     *
     * @param Type $type
     */
    protected function getType(Type $type): ?ScalarType
    {
        $fqcn = ltrim((string)$type, '\\');
        foreach ($this->getTypeMaps() as $map) {
            if (isset($map[$fqcn])) {
                return $map[$fqcn];
            }
        }

        return null;
    }

    /**
     * Returns a GraphQL type by name.
     * If this root type mapper can return this type in "toGraphQLOutputType" or "toGraphQLInputType", it should
     * also map these types by name in the "mapNameToType" method.
     *
     * @param string $typeName The name of the GraphQL type
     */
    public function mapNameToType(string $typeName): NamedType
    {
        if (isset($this->getTypeMaps()[$typeName])) {
            return array_values($this->getTypeMaps()[$typeName])[0];
        }

        return $this->next->mapNameToType($typeName);
    }

    /**
     * Handles the conversion to an input type
     *
     * @param Type $type
     * @param InputType|null $subType
     * @param string $argumentName
     * @param \ReflectionMethod $refMethod
     * @param DocBlock $docBlockObj
     */
    public function toGraphQLInputType(
        Type $type,
        ?InputType $subType,
        string $argumentName,
        \ReflectionMethod $refMethod,
        DocBlock $docBlockObj
    ): InputType
    {
        return $this->getType($type)
            ?: $this->next->toGraphQLInputType($type, $subType, $argumentName, $refMethod, $docBlockObj);
    }

    /**
     * Handles the conversion to an output type
     *
     * @param Type $type
     * @param OutputType|null $subType
     * @param \ReflectionMethod $refMethod
     * @param DocBlock $docBlockObj
     */
    public function toGraphQLOutputType(
        Type $type,
        ?OutputType $subType,
        \ReflectionMethod $refMethod,
        DocBlock $docBlockObj
    ): OutputType
    {
        return $this->getType($type)
            ?: $this->next->toGraphQLOutputType($type, $subType, $refMethod, $docBlockObj);
    }
}

Now, the only thing you need to do is define your "type maps" in the constructor.  The key in the array is the type name you're using in your GraphQLite annotations.  The array value assigned to that key is your domain object/type mapped to the scalar type that Webonyx graphql lib expects.
Honestly, I think you could add an interface to your domain objects/types, and have one class that implements the ScalarType.  I think this may be what AnyScalarType was trying to accomplish.  But I couldn't ever make any sense of that lib and how it tied into graphqlite.

Hey @oojacoboo ,
You are certainly right.
The RootTypeMapperInterface allows to hook into type resolving and allows anyone to do almost anything. But it is hard to use.
And defining a scalar type is certainly something common enough to try to simplify it.
Your Mapper class is a great start to simplify this.
Out of curiosity, if you were to define an interface for Scalar types, how would you design it?

@moufmouf honestly, after a little more thought here, I think I'd prefer to not pollute my domain objects/scalars with the particulars of GraphQL.  The class that I've written above is fairly agnostic.  The only thing that's required is the mapping in the constructor.  If that mapping could be exposed and state managed through the config, that'd be ideal, IMO.  You'd just provide the simple $typeMaps mapping array to a config setter and that's that.
Of course, the highly customizable nature of the RootTypeMapperInterface could remain, but providing a simple map like this would be ideal.  It'd unlikely that most people would ever need to actually write one themselves.  The type mapper doesn't define how the actual scalar is serialized/deserialized just the mapping from a string to a class.  The logic for the actual serializing/deserializing would be handled in the Webonyx ScalarType object.  So, you just need to tell GraphQLite where to map the annotation definition/string.  Like, in my example above, I'm mapping Date, which returns my domain, Acme\Cog\Date object and I want Acme\GraphQL\Type\Scalar\Date to handle all my GraphQL serialization/deserialization logic.


Start with 6.5 -> 7.0 upgrade recipe

@krisv or @mbiarnes could you please review? It's very much the same I did for drools-website recently.

+1


Label color with leading zeros error

If the label color code consists of leading zeros, in some cases it will take it as an integer and it will truncate the leading zeros which leads to following error.

Suggest solution,

Found a better solution:
    if (label.color) {
      label.color = String(label.color)
      if(label.color.length < 6) {
        label.color.padStart(6, '0')
      }
    }


externalize the script and other fixes

I thought I would be easier to contribute to the repo if the python script was in its own file rather than embedded in the blend file.
This way, we can work on it concurrently, merge it, see its history, etc.
Other fixes:

fix vertex explosion by resetting the armature between fbx imports
apply LOCAL constraint to fix wrong hips relative bone position
apply an offset position to the root bone constraint to try to correct the position (kinda works)
change the animation crawling algorithm to be more granular

To be honest I don't know if this will work better in all cases or not.

Some animations are wrong in LOCAL space:

shoulder position is incorrect

I seem to recall the shoulder twisted around issue went away if I edited the target armature on PolygonSyntyCharacter to have the right clavicle connected to the upper arm bone and rolled it so X/Z axes matched other ones on the arm, but it's been a while since I originally tried that character, so I'd probably have to go back to confirm that's all I did other than disconnect hip bone from root bone (but that was when I still had issue with the third finger on left hand).

@cdoise-vbg thanks for the reply!
For reference, on which model did you have the most success with the re-targeting? Was it a synty character?
Since I'm only interested in the animation library, any known good model would do.

other than disconnect hip bone from root bone

Wouldn't that prevent using the root motion animations?
I would be happy with only the non-root animations working if they can reliably be retargeted.

PolygonSyntyCharacter from the Synty animation packages was the one I had the best results with, after making the aforementioned changes to hip bone and right clavicle. For hip, I said "keep offset" after disconnecting. It appeared to be working with root motion when I looked at the animation in playback, but now that you mention it, that might just be because it was copying the global transform...
I'm afraid I'm thinking of pausing my efforts on this particular sample for the time being. I need to go back and spend some time on the basics of Blender add-ons and animations.


Bug: (sort-imports) prefix-only builtin modules are defined as external modules

Describe the bug
When using the node: prefix for an builtin module, the sort-imports rule defines it as an external module.
Code example
IN CONFIG:
"perfectionist/sort-imports": [
  "error",
  {
    "type": "natural",
    "groups": [
      "builtin",
      "external",
      "internal",
      "parent",
      "sibling",
      "index",
      "side-effect"
    ]
  }
]

IN CODE:
import { writeFile } from "node:fs/promises"; // ⤸ There is no space between groups.
import { createRoot } from "react-dom/client";

ESLint version
v8.48.0
ESLint Plugin Perfectionist version
v2.0.0
Additional comments
No response
Validations

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

Made PR.

Thanks! Released in v2.0.1


Fix excludefrommanifest

Fixes #1595 by not modifying the same collection. Even though a resource may already have the ManifestPublishingCallbackAnnotation.Ignore now when added, there's no guarantee that the behaviour will remain constant. Allowing ExcludeFromManifest to operate despite this keeps the API consistent.
Also adds test for the method.
Microsoft Reviewers: Open in CodeFlow

Thanks for the contribution. There should only ever be one or zero manifest publishing callback annotations. We could simplify this by calling resource.Annotations.OfType<Manifest...Annotation>().SingleOrDefault().
If there are multiple then this would cause it to throw (good). And if there is one, its no longer inside a foreach loop and we can just remove it.

If that holds true for the foreseeable future too, then sure that change makes sense and I can make it.
The main purpose of this was to fix the issue whereby calling .ExcludeFromManifest on a resource that is already excluded (by the extension method that adds it) doesn't cause it to throw. Either solution solves it, current if there's the potential for multiple, or with the change if it's always 0-1.

If there are multiple then this would cause it to throw (good).

The error message Collection was modified; enumeration operation may not execute. is extremely obscure. If there should only be ManifestPublishingCallbackAnnotation instance, then the error should be linked to adding the annotation.

I'm not sure this should throw. I think we want to make this resilient. ExcludeFromManifest is broken in multiple ways because it'll create broken references in the manifest (it doesn't fix WithReference calls to an excluded resource).

We fixed this https://github.com/dotnet/aspire/pull/2052.
Thanks for the PR @rudiv ! Hope you can contribute again


thuang-update-review-checkbox

Description
Update wording:

Update checkbox:

Issue
ch<fill_in_issue_number>
Test plan
Write how your changes are tested, or give a convincing reason why they can't be tested automatically.

awesome thanks! GO TEAMM!!


feat[api-client]: add support to set resource version when interact with metadata api.

Codecov Report

Merging #130 (dd8dc10) into main (0767146) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##               main     #130   +/-   ##
=========================================
  Coverage     94.34%   94.35%
- Complexity      602      603    +1
=========================================
  Files           132      132
  Lines          2407     2409    +2
=========================================
+ Hits           2271     2273    +2
  Misses          136      136

Flag
Coverage Δ

phpunit
94.35% <100.00%> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/api-client/src/MetadataApi.php
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Add badge to display install size

This adds a badge to the README.md to display the npm install size

Since this is a dev/build tool, it's not really intended to be installed in other applications. I don't think it makes sense to advertise that this is a (necessarily) massive CLI install

There is at least one other person who cares about the install size of their tools: https://github.com/styfle/packagephobia/issues/218
I realize it's not a goal but I'm trying to bring awareness because I don't believe there is any other way for users to know the size of mdx-deck before installing.

v2 has removed the puppeteer dependency from the core CLI, which should substantially reduce the install size. I took another look at this PR and it seems like the image link is either broken or extremely slow. I'm going to close this out for now

The badge is probably timing out when installing all the dependencies.

version
install size

1.8.2

2.0.0-8

Once you publish v2 as latest to npm, it will work nicely 👍


[1.20.1] [0.6.10-7] Block colors not working if not in instancing mode

Describe the Bug
Hi, Create: Copycats+ dev again. This is another issue with the Copycat Shaft, where it seems that block colors don't get rendered when using the batching backend or when Flywheel is off. I have checked that the correct colors are definitely provided in our custom BlockColor and BlockAndTintGetter implementations, but grass still looks gray if the active flywheel backend is not instancing. Sorry if this one ends up to be a bug in C:Copycats+, but the fact that only instancing works makes it even more confusing.
If it's related, here are the relevant sections of C:Copycats+ code:

BlockColor implementation: https://github.com/copycats-plus/copycats/blob/6a5f7d253f9925a82f5b2738c5ec796ecad33f90/common/src/main/java/com/copycatsplus/copycats/content/copycat/base/functional/IFunctionalCopycatBlock.java#L255-L268
getBlockTint in our BlockAndTintGetter wrapper: https://github.com/copycats-plus/copycats/blob/6a5f7d253f9925a82f5b2738c5ec796ecad33f90/common/src/main/java/com/copycatsplus/copycats/content/copycat/base/model/functional/WrappedRenderWorld.java#L147-L151
Helper that generates buffered data: https://github.com/copycats-plus/copycats/blob/6a5f7d253f9925a82f5b2738c5ec796ecad33f90/common/src/main/java/com/copycatsplus/copycats/content/copycat/base/model/functional/FunctionalCopycatRenderHelper.java
Forge implementation: https://github.com/copycats-plus/copycats/blob/6a5f7d253f9925a82f5b2738c5ec796ecad33f90/forge/src/main/java/com/copycatsplus/copycats/content/copycat/base/model/functional/forge/FunctionalCopycatRenderHelperImpl.java
Fabric implementation: https://github.com/copycats-plus/copycats/blob/6a5f7d253f9925a82f5b2738c5ec796ecad33f90/fabric/src/main/java/com/copycatsplus/copycats/content/copycat/base/model/functional/fabric/FunctionalCopycatRenderHelperImpl.java

Reproduction Steps

Download this test version of C:Copycats+ or build https://github.com/copycats-plus/copycats/tree/6a5f7d253f9925a82f5b2738c5ec796ecad33f90 from source:
UNZIP Copycats-forge.1.20.1-1.3.5-shaft-TEST.6a5f7d2.zip
UNZIP Copycats-fabric.1.20.1-1.3.5-shaft-TEST.6a5f7d2.zip

Place a Copycat Shaft and place grass inside

Switch flywheel backend and observe the grass color

Expected Result
The grass should always appear green and should always look like grass in plains biome.
Screenshots and Videos

Crash Report or Log
No response
Operating System
Windows 11
What is your GPU?
NVIDIA GeForce GTX 1650/PCIe/SSE2  4.6.0 NVIDIA 537.13
Mod Version
0.6.8.a
Minecraft Version
1.19.2
Loader Version
Forge 47.2.20, Fabric 0.15.7
Other Mods
(From dev environment)
Mod List:
		forge-1.20.1-47.2.20-minecraft-merged-1.20.1-loom.|Minecraft                     |minecraft                     |1.20.1              |DONE      |Manifest: NOSIGNATURE
		mixinextras-forge-0.3.2.jar                       |MixinExtras                   |mixinextras                   |0.3.2               |DONE      |Manifest: NOSIGNATURE
<PHONE_NUMBER>021441488.jar                           |generated_7dfba9c             |generated_7dfba9c             |1                   |DONE      |Manifest: NOSIGNATURE
		additional-placements-674852-5142065.jar          |Additional Placements         |additionalplacements          |1.8.0               |DONE      |Manifest: NOSIGNATURE
		                                                  |Forge                         |forge                         |47.2.20             |DONE      |Manifest: NOSIGNATURE
		rubidium-574856-4952685.jar                       |Rubidium                      |rubidium                      |0.7.1a              |DONE      |Manifest: NOSIGNATURE
		flywheel-forge-1.20.1-0.6.10-7.jar                |Flywheel                      |flywheel                      |0.6.10-7            |DONE      |Manifest: NOSIGNATURE
		jade-324717-5390389.jar                           |Jade                          |jade                          |11.9.3+forge        |DONE      |Manifest: NOSIGNATURE
		create-1.20.1-0.5.1.f-26-slim.jar                 |Create                        |create                        |0.5.1.f-26          |DONE      |Manifest: NOSIGNATURE
		main                                              |Create: Copycats+             |copycats                      |1.20.1-1.3.5-shaft-T|DONE      |Manifest: NOSIGNATURE
		jei-1.20.1-forge-<IP_ADDRESS>.jar                     |Just Enough Items             |jei                           |<IP_ADDRESS>            |DONE      |Manifest: NOSIGNATURE

Additional Context
No response

It was a bug in Copycats+ 😅 Sorry


Add FSMonitor

Thanks for the contribution

Not a problem!
And just for the future -- you should leave issues open until they're closed. I noticed you closed the issue I opened relating to this before I actually made the changes and opened a PR, which breaks the typical GitHub workflow.

Good point. I'll do that in the future.
On Mon, Apr 16, 2018, 7:09 PM Aaron Lichtman<EMAIL_ADDRESS>wrote:

Not a problem!
And just for the future -- you should leave issues open until they're
closed. I noticed you closed the issue I opened relating to this before I
actually made the changes and opened a PR, which breaks the typical GitHub
workflow.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ashishb/osx-and-ios-security-awesome/pull/12#issuecomment-381806908,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAXwdHUbQ_j08x4-BLu_hFl4G7YZyg5Cks5tpU7vgaJpZM4TXfdf
.


validate LOC's lat/long field values not to be out of range

The current implementation of LOC RR's (text) parser doesn't perform range check on the latitude and longitude fields, so it can allow values out of the range specified by RFC1876:
       d1:     [0 .. 90]            (degrees latitude)
       d2:     [0 .. 180]           (degrees longitude)
       m1, m2: [0 .. 59]            (minutes latitude/longitude)
       s1, s2: [0 .. 59.999]        (seconds latitude/longitude)

This PR makes sure that a textual LOC RDATA unexpectedly contains out of range latutide or longitude values.  Note also that it's possible that the resulting 32-bit encoded value is out of range even if degrees, minutes and seconds in the textual representation are all in range.  This PR prevents this type of out-of-range value, too.  These validations help improve interoperability there's a known implementation (BIND) that rejects out-of-range values in the wire format.
Also, while working on it I've noticed one additional glitch: the current implementation could lose the 'cm' part of some large altitude values, e.g., 42849672.95, due to insufficient precision specified for ParseFloat.  This PR fixes that issue, too.

Codecov Report

Merging #1149 into master will increase coverage by 0.26%.
The diff coverage is 90.90%.

@@            Coverage Diff             @@
##           master    #1149      +/-   ##
==========================================
+ Coverage   55.56%   55.82%   +0.26%
==========================================
  Files          41       41
  Lines       10124    10128       +4
==========================================
+ Hits         5625     5654      +29
+ Misses       3476     3466      -10
+ Partials     1023     1008      -15

Impacted Files
Coverage Δ

scan_rr.go
62.36% <85.71%> (+1.54%)
:arrow_up:

scan.go
83.57% <100.00%> (+1.10%)
:arrow_up:

msg.go
76.53% <0.00%> (-0.69%)
:arrow_down:

types.go
74.64% <0.00%> (+0.61%)
:arrow_up:

Continue to review full report at Codecov.

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

/merge
On Mon, 17 Aug 2020, 04:41 Tom Thorogood<EMAIL_ADDRESS>wrote:

@tmthrgd approved this pull request.
LGTM from a curious glance.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/miekg/dns/pull/1149#pullrequestreview-468147700, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACWIWYG2DLF6H3OS7ZY3ZDSBCRFDANCNFSM4P5QUCJA
.


Run query in SQL Lab raise up error "Shape of passed values is (1, y), indices imply (x, y)"

Make sure these boxes are checked before submitting your issue - thank you!

[√ ] I have checked the superset logs for python stacktraces and included it here as text if any
[√] I have reproduced the issue with at least the latest released version of superset
[√] I have checked the issue tracker for the same issue and I haven't found one similar

Superset version
0.20.6 on windows 10 x64
Expected results
When run query in SQL Lab, the Results returns correct data.
Actual results
Raise up error "Shape of passed values is (1, y), indices imply (x, y)"
Steps to reproduce
1.Open "SQL Lab"
2.Create a new query like "SELECT * FROM Table_Name;"
3.Run Query
Bug fixing process
This bug was caused by:
Use list instead of numpy array. Hotfix. #2412
As refer to the pandas doc:
pandas.DataFrame(data=None, index=None, columns=None, dtype=None, copy=False)
data : numpy ndarray (structured or homogeneous), dict, or DataFrame
Dict can contain Series, arrays, constants, or list-like objects
the data should not be a list.
When changed the code:
cdf = dataframe.SupersetDataFrame(
pd.DataFrame(list(data), columns=column_names))
to:
import numpy as np
cdf = dataframe.SupersetDataFrame(
pd.DataFrame(np.array(data), columns=column_names))
the bug was fixed.

Also experiencing this issue on Debian Stretch running Superset 0.22.1


python3Packages.fontforge: disable for python 3.9 and older

Addresses https://github.com/NixOS/nixpkgs/issues/327819
Description of changes
For reasons I couldn't figure out myself with git bisect, Fontforge doesn't build anymore with python39. I figured it would be best to at least mark that explicitly. The only package affected that I know of is the monoid font, which has no reverse dependencies.
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
[ ] 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

[ ] Fits CONTRIBUTING.md.

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

https://docs.python.org/3/library/sysconfig.html#sysconfig.get_preferred_scheme
This function was only introduced in 3.10.

Yeah I saw that, still curious how it ever used to build.


Admin Page

I tried to made an admin page from where I can supervise feeds and articles but when I used the conventional method (adding admin in urls and in settings), it didn't work. The error points to bootcamp.core.views.profile and I really didn't get it. Would you please guide me on this?

Hi @NothingxFluctuation Do you mind to provide the stack trace for that error with relevant information about your setup and deployment?

Hi @NothingxFluctuation do you have any update on this?

Closing for inactivity.


Not an issue as such, but package name beautification :)

Sir,
Suggestion to change package name with proper case...
sharpconfig.2.0.1 => SharpConfig.2.0.1
Thanks for such an awesome package, so simple and so useful.

Hey there, the lower-case naming is still there from the first versions of SharpConfig.
I would want to change the package name, but that would automatically create a new package on NuGet, which many existing users might not notice. For now, it's best if the name stays that way, since it should not be a hindrance SharpConfig's usage. I'll think about a solution for future releases, thanks.


FMN example?

Is it possible to provide an example of the FMN usage? For example, recreating Figure 3 of HAGO19?

Hi,
I have added an example notebook on FMN, with code to produce such plot.

Hi,
What do you mean about not being able to obtain consistent bases ?
In the example, I had some rough precomputed correspondences and just randomly sampled a set of pairs.
For each pair (i,j), I input both the map i->j and j->i, which I find to be a good strategy. The network also performs better with many 3-cycles, which might be a good thing to look at.
Also, note that the results are heavily dependent on the quality of the input maps, maybe refining maps individually or via consistent zoomout would help in your case.

Thanks. I've simply modified your example to combine the FM and FMN examples.
calculate_maps = True

process_params = {
    "n_ev": (30, 30),
    "subsample_step": 1,
    "descr_type": "WKS",  # WKS or HKS
}
fit_params = {
    "w_descr": 1e0,
    "w_lap": 1e-2,
    "w_dcomm": 1e-1,
    "w_orient": 0,
}

maps_dict = {}

for map_filename in tqdm(map_files):
    ind2, ind1 = map_filename.split("_to_")
    ind1, ind2 = int(ind1), int(ind2)

    # Indicing starts at 1 in the names, but at 0 on the meshlist
    mesh1, mesh2 = meshlist[ind1 - 1], meshlist[ind2 - 1]

    if calculate_maps:

        model = FunctionalMapping(meshlist[ind1-1], meshlist[ind2-1])
        model.preprocess(**process_params, verbose=False)
        model.fit(**fit_params, verbose=False)

        model.zoomout_refine(nit=15, step=1, verbose=False)

        FM_12 = model.FM
    else:
        # Load the pointwise map
        p2p_21 = np.loadtxt(f"../data/camel_gallop/maps/{map_filename}", dtype=int)

        # Convert to functional map
        FM_12 = spectral.mesh_p2p_to_FM(p2p_21, mesh1, mesh2, dims=K)

    # Populate the dictionary
    maps_dict[(ind1 - 1, ind2 - 1)] = FM_12

Using the uploaded example maps, we get an embedding something like what I expect.

My understanding is that the limit basis $\Phi_0$ can be retrieved from shape i as $\Phi_i \tilde{Y}_i$, where $\Phi$ and $\tilde{Y}$ are respectively the eigen and canonical latent bases. Using the provided FMs, the latent basis derived from any of the shapes is completely consistent.

However, when I calculate the maps as above, I cannot get a reasonable and consistent result. In fact, this isn't so bad as long as I used the topology in the example. When I choose a random network or use another topology like a chain, I get much worse results.

The apparent limit basis when calculating from each shape is inconsistent.

Advice on improving the map computation would be appreciated!

Calculation of latent bases and plotting.
import pyvista as pv

N_plots = 5
ev = 1
zoom = 2

meshlist_sub = [
    int(i) for i in np.linspace(0, len(fmn_model.meshlist) - 1, N_plots)
]

base_eigs_bitmap = []
clb_eigs_bitmap = []
cclb_eigs_bitmap = []

for i in meshlist_sub:
    m = meshlist[i]

    pl = pv.Plotter(off_screen=True)

    scalars = m.eigenvectors[:, ev]

    meshp = pv.make_tri_mesh(m.vertices, m.faces)
    meshp["scalars"] = (scalars - scalars.min()) / np.ptp(scalars)
    pl.add_mesh(meshp, scalars="scalars")
    pl.view_zy()
    pl.remove_scalar_bar()
    pl.show()

    base_eigs_bitmap += [pl.image]

for i in meshlist_sub:
    m = meshlist[i]

    m_ord = np.argsort(m.eigenvalues)
    m_eigv = m.eigenvectors[:, m_ord][:, : fmn_model.M]
    lb0 = (m.eigenvectors[:, : fmn_model.M] @ fmn_model.CLB[i])[:, ev]

    meshp0 = pv.make_tri_mesh(m.vertices, m.faces)
    meshp0["scalars"] = (lb0 - lb0.min()) / np.ptp(lb0)

    pl = pv.Plotter(off_screen=True)
    pl.add_mesh(meshp0, scalars="scalars")
    pl.view_zy()
    pl.remove_scalar_bar()
    pl.show()

    clb_eigs_bitmap += [pl.image]

for i in meshlist_sub:
    m = meshlist[i]

    m_ord = np.argsort(m.eigenvalues)
    m_eigv = m.eigenvectors[:, m_ord][:, : fmn_model.M]
    lb0 = (m_eigv @ fmn_model.CCLB[i])[:, ev]

    meshp0 = pv.make_tri_mesh(m.vertices, m.faces)
    meshp0["scalars"] = (lb0 - lb0.min()) / np.ptp(lb0)

    pl = pv.Plotter(off_screen=True)
    pl.add_mesh(meshp0, scalars="scalars")
    pl.view_zy()
    pl.remove_scalar_bar()
    pl.show()

    cclb_eigs_bitmap += [pl.image]

bitmap_dims = base_eigs_bitmap[0].shape[:2]

fig, axs = plt.subplots(3, N_plots)

for i, (m, m_clb, m_cclb) in enumerate(
    zip(base_eigs_bitmap, clb_eigs_bitmap, cclb_eigs_bitmap)
):
    axs[0, i].imshow(m, interpolation="none")
    axs[1, i].imshow(m_clb, interpolation="none")
    axs[2, i].imshow(m_cclb, interpolation="none")

    axs[0, i].set_axis_off()
    axs[1, i].set_axis_off()
    axs[2, i].set_axis_off()

    if i == 0:
        axs[0, 0].set_title("Mesh eigenbasis")
        axs[1, 0].set_title("CLB")
        axs[2, 0].set_title("CCLB")

plt.gcf().set_size_inches(
    (N_plots * bitmap_dims[0] / 200, 3 * bitmap_dims[0] / 200)
)
plt.subplots_adjust(wspace=0, hspace=0)


Feature/dray/recursion update

W-8886893
Critical Changes
Changes

Updated the recursive flow checking to prevent false positives when the same flow is called from different ancestors

Issues Closed

I'd edit the changelog entry to say something like "It is now possible to create a flow which runs the same sub-flow multiple times, as long as they don't create a self-referential cycle."

It is now possible to create a flow which runs the same sub-flow multiple times, as long as they don't create a self-referential cycle.

 :D

@davidjray The way I think about it is that for release notes I'm generally trying to put myself in the user's shoes and imagine what the change looks like from their perspective. It's the place to call out what functionality it breaks or makes possible, not details about what changed in the implementation (unless it's a detail that we know people are treating as a public API).


ADFS Auth fails with Invalid SAML Attributes

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):
Enable auth with AD then disable and enable auth with ADFS
Result:
Invalid SAML Attribute messages, SAML Trace shows that SAML Attributes are in fact fine
Rancher logs indicate a failure to get UPN (also fine in the SAML trace)
No other info is shown to be discovered and the environment has been validated several times for correct settings
Other details that may be helpful:
Debug logging in Rancher showed no extra information, equivalent environments configured with ADFS OOTB work
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.4.8

gz#12724

Validated on 238e9f21be0554b8c237a1226e337bea0a972c56.  I first configured AD auth and was able to log in.  AD auth was disabled and ADFS was configured.  I was able to login with an ADFS user.

On 2.5.5 was able to reproduce.
From the global --> authentication --> enable AD auth --> disable AD ---> Enable the ADFS auth and when we try to save, it fails with the error "Invalid SAML Attributes"

On v2.5-4e48b8a9fbedad498fa21fd00e6e426ab3e13770-head
From Auth providers --> Enable AD and save --> Disable AD and enable ADFS by providing all the details --> Enabling goes through without any error --> Logout and login with ADFS credentials --> Authentication goes through and users are allowed to login

Changing the label to-test as @paynejacob has provided the commit ID for master-head https://github.com/rancher/rancher/pull/31106

on master-2dca0c67b48331c23c05c025208bacfc258d45bd-head
From Auth providers --> Enable AD and save --> Disable AD and enable ADFS by providing all the details --> Enabling goes through without any error --> Logout and login with ADFS credentials --> Authentication goes through and users are allowed to login
Log in as standard user --> Able to create a cluster

Rancher before upgrade v2.5.6
After upgrade : v2.5-fa087c81628de057406608f077d0952bb03cea56-head
Upgrade testcase:

Create rancher server on v2.5.6
Upgrade the cluster to v2.5-fa087c81628de057406608f077d0952bb03cea56-head
Enable AD and disable
Enable ADFS, log out and login as a standard user
Create a cluster as standard user


Docker Kong does not start - Following the getting started guide

Summary
I'm just following the getting started guide with Docker Kong. I'm able to start Cassandra correctly (step 1 in the guide), and when I try to start Kong (step 2 in the guide) I get the following error:

docker: Error response from daemon: driver failed programming external connectivity on endpoint kong (d6f3d2198b6f6785b1a7dfa09189fe1dd624eb8a423c593ced39ddfd6a1b7d64): Error starting userland proxy: listen tcp <IP_ADDRESS>:7946: bind: address already in use.

Steps To Reproduce
Follow the getting started guide for Docker Kong
Additional Details & Logs

Kong version: 0.10.3
Kong configuration: The one specified in the guide
Operating System: Ubuntu 16.04
Docker version: 17.06.0-ce, API Version 1.30
Things to  notice: Something that  called my attention is that in my local machine I have the port 7946 taken by the process dockerd (both tcp and udp). As far as I read this is related with Docker Swarm.

Kong use port 7946(UPD, TCP) for clustering, so please make sure its not being used by any other application.

Wow thanks! this is good info, I'm going to try it out today :)
I think it should be officially included on the Getting started guide with Docker (at least a simple comment mentioning it), this could save a lot of time to a lot of people.

@augusto-altman Yes

@augusto-altman may I know why you want to expose that port in Docker Swarm setup? Should't you using be create kong as service in a overlay network? We definitely need separate documentation for running Kong in swarm mode.

@shashiranjan84 Mmmm, I am really not intending to do so, actually I'm just learning, trying to setup a fresh infrastructure using Kong as Api Gateway. Look this is the complete shortened story about what happened:

I installed Ubuntu 16.04 in my personal laptop this monday.
Right after that I installed docker ce following this. This installed docker v17.06.0-ce on my machine.
I completed the official Docker getting started guide. So far everything was working very smooth. That guide is really focused on Docker Swarm.
I tried to follow the Kong over Docker getting started guide and I got blocked on the step 2 because of the issue with the port 7946.
I checked with lsof lsof -i tcp:7946 which process was taking the port 7946 in my machine and surprisingly it was docker :/ (process name dockerd)
I dag a little and I found that Docker Swarm was the one taking that port.

I don't know if I am missing something here, but it seems to be that Docker latest (or at least Docker v17.06.0-ce) comes with Docker Swarm enabled out of the box and is taking that port by default to communicate between Docker Swarm nodes. So basically what I think is that, if I'm correct, newcomers as me trying to start from the ground (fresh install) with Kong will crash against the same wall (because they will probably have the latest Docker version on their machines as well).
I'm far of being an expert, I'm actually a new starter. As you can see I'm just following getting started guides (docker, kong, etc). But I got blocked doing this, so I think it is worth to use my case to improve the docs. I know Kong is an awesome product, very mature, that is why I wanted to use it. We can work through this and maybe find some points for improving the getting started experience for newcomers.

Thanks for information. We are glad you like Kong. We will try to reproduce and resolve it asap. Meanwhile feel free to send us feedback or even a PR with correction.

@augusto-altman I just followed your steps and Kong ran just fine for me on Ubuntu 16.04 LTS
  sudo apt-get update
  sudo apt-get install     apt-transport-https     ca-certificates     curl     software-properties-common
  sudo apt-get install     linux-image-extra-$(uname -r)     linux-image-extra-virtual
  curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
  sudo add-apt-repository    "deb [arch=amd64] https://download.docker.com/linux/ubuntu \
   $(lsb_release -cs) \
   stable"
  sudo apt-get update
  sudo apt-get install docker-ce

Seems like you were running swarm mode.

@shashiranjan84 Yes!! you are right. I ran a sudo docker node ls and effectively my machine was a node (as you said I was running on swarm mode). After finding that I ran sudo docker swarm leave --force and then everything worked as expected.
Thank you so much for your help and sorry for the inconvenience. Just a question out of curiosity, is there any known guide or documentation for using Kong over Docker Swarm (it doesn't have to be an official docs)? The only thing that somebody would have to do to run Kong over Docker Swarm is to change the the KONG_CLUSTER_ADVERTISE property?

......listen tcp <IP_ADDRESS>:7946: bind: address already in use., I have this problem, too. if swarm mode is active.
After docker swarm leave --force , worked ok.

7946 port conflict
serf
The address that Serf will bind to for communication with other Serf nodes. By default this is "<IP_ADDRESS>:7946".
docker swarm
In order to use the ingress network in the swarm, you need to have the following ports open between the swarm nodes before you enable swarm mode:
Port 7946 TCP/UDP for container network discovery.
Port 4789 UDP for the container ingress network.


Moving to saveourtool domain (omg)

What's done:

updated packages
updated deploy scripts
updated links on the FE

Maybe, we can do this in two iterations: updates related to GH organization (links and docker images) and renaming of packages?


Lightning Terminal Pool Account Recovery

Hello
I am trying to recover my Pool account at Lightning Terminal, following the instructions from Troubleshooting - Builder’s Guide (lightning.engineering), but I am getting this error:
[pool] rpc error: code = Unknown desc = error performing recovery: could not recover account xxxxxx: error during authentication, before sending subscribe: server sent unexpected error
If I repeat the procedure the error changes to:
[pool] rpc error: code = Unknown desc = error performing recovery: could not recover account xxxx: account xxxx is already subscribed, cannot recover
I am afraid of loosing my funds!
Can you help me complete the recovery?
Thanks.

It looks like you already have an instance of pool (or lit) running. You need to shut it down before starting a new one (and the recovery process)

I have already deleted the Lightning Terminal app from Umbrel and reinstalled many times.

@bpedreira did you double check that there was no other litd/poold terminal running in the machine?


[3.x] Implemented UWP version of OS.get_unique_id function.

I have successfully implemented the OS.get_unique_id function for
Universal Windows builds of Godot.
Here is a basic overview of how it works:

fetch package specific token
get an IBuffer interface for the hardware specific ID of the package
create a data reader to read the hardware ID data
allocate a buffer to hold the hardware ID data
read the hardware ID data into the buffer
convert the hardware ID data into a hexadecimal string
free the buffer
return the hexadecimal ID string

I have used clang-format 13 to fix the style issues and corrected the commit.

This is what OS.get_unique_id() returns in my Windows 11 PC running Godot in UWP:

And this is what returns in a Windows 11 VM:

I reinstalled the Windows 11 VM and the ID was still the same :)
Seems that it's working well enough!

Sorry for the late review, we don't have an active maintainer for the UWP platform in 3.x currently.
I haven't reviewed the code in depth but if it works, it should be fine. Maybe @panreyes can help testing?
You also need to update the docs which say that this method isn't supported on UWP.
diff --git a/doc/classes/OS.xml b/doc/classes/OS.xml
index e20f6c0c1a..a393cdff8e 100644
--- a/doc/classes/OS.xml
+++ b/doc/classes/OS.xml
@@ -550,7 +550,7 @@
 			<description>
 				Returns a string that is unique to the device.
 				[b]Note:[/b] This string may change without notice if the user reinstalls/upgrades their operating system or changes their hardware. This means it should generally not be used to encrypt persistent data as the data saved before an unexpected ID change would become inaccessible. The returned string may also be falsified using external programs, so do not rely on the string returned by [method get_unique_id] for security purposes.
-				[b]Note:[/b] Returns an empty string on HTML5 and UWP, as this method isn't implemented on those platforms yet.
+				[b]Note:[/b] Returns an empty string on HTML5, as this method isn't implemented on this platform yet.
 			</description>
 		</method>
 		<method name="get_unix_time" qualifiers="const">

I agree with your suggestions. It looks cleaner now. The changes have been committed.

Looks good! Could you squash the commits? See PR workflow for instructions.

I squashed the commits and amended the doc change myself, should be ready to merge now.

Thanks!


Support PRETTIERD_DEFAULT_CONFIG

Fix should just be:
prettierddata=$(cat ${PRETTIERD_DEFAULT_CONFIG:-$HOME/.prettierd} 2> /dev/null)

Nevermind, realized that the prettierd file is the data file for the daemon and not the configuration file. Would still be nice to support some XDG base specification though, but that likely rests on prettierd and not prettierme.


Fixed Color Issue in Dark Mode

Description
Please include a summary of the change and state which issue is fixed or which new feature implemented. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes #126

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality not to work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.

[ ] Test A
[ ] Test B

Test Configuration:

Firmware version:
Hardware:
Toolchain:
SDK:

Also, include screenshots for verification and reviewing purpose.
Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my code
[ ] I have commented on my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

@SahanDisa Could i chip in here and just complete the changes you requested from @hs05june . This branch seems to behind so could you confirm whether these are all the required changes or the new versions of code require different implementation


tilt: 0.33.5 -> 0.33.6

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/tilt-dev/tilt/releases.
meta.description for tilt is: Local development tool to manage your developer instance when your team deploys to Kubernetes in production
meta.homepage for tilt is: https://tilt.dev/
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.33.6 with grep in /nix/store/d4qwg5xbkicirq3ighb16sg9861lqr4r-tilt-0.33.6
found 0.33.6 in filename of file in /nix/store/d4qwg5xbkicirq3ighb16sg9861lqr4r-tilt-0.33.6

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
tilt

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/d4qwg5xbkicirq3ighb16sg9861lqr4r-tilt-0.33.6 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/34ba3cc742f7418bad175193ee9cce7938f921aa#tilt

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/d4qwg5xbkicirq3ighb16sg9861lqr4r-tilt-0.33.6
ls -la /nix/store/d4qwg5xbkicirq3ighb16sg9861lqr4r-tilt-0.33.6/bin

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

1 package built:

tilt

Maintainer pings
cc @anton-dessiatov for testing.

This build is broken for myself and others. Not yet sure if that's a nix issue or upstream issue.
$ tilt up
Tilt started on http://localhost:10350/
v0.33.6, built
Tilt analytics disabled: Environment variable DO_NOT_TRACK=1
Error: running in prod mode, but JS/CSS files are not available.
Please report this: https://github.com/tilt-dev/tilt/issues

@glennpratt, thanks for reporting. This is a known issue and should be fixed by #260712 when it gets merged.


[BUG] Words containing italic tags fails when trying to fetch definitions

Recently trying to consume from this API project, we found that searching for words that contain italic tags fails.
So what we're basically trying to do, following the current documentation is to:
rae.fetchWord(response.getRes()[0].getId()))
What throws an error of body.res is not iterable
We try with Pizza and Paparazzi words and get the same result, the only reason we reach that this could be happening is related to the italic tags in the header word when trying to fetch the ID of the word.

Thanks for reporting, i am just resolving the issue. If you ask what happened, it's because the API was confunding a json (word metadata) with an html paragraph (definition)

I finally fixed the issue. The new version is 1.5.0 and it's working.

Thank you! @account0123

The issue is again present in latest release 1.5.1, reverting back to 1.50 fixes it, just so you know.
I think the problem is in HttpInterface.js line 68. The Regex returns a null value and it still tries to access the index [1].
I tried with 'pizza' and 'jazz'


Overlap with mgmtconfig?

There seems to be some plausible overlap with the event system over at https://github.com/purpleidea/mgmt/
I just figured I'd give a shout out over here in case you'd be interested in collaborating on the project or discussing event sources which are missing in current operating systems which we could both work on getting added.
Feel free to find me in #mgmtconfig on Freenode IRC as purpleidea, or at this years http://cfgmgmtcamp.eu/
Thanks!

I think it could be feasible to add an integration of falco that would push events to mgmt. We have other integrations with event systems in the integrations subdirectory. We can continue the discussion on our public slack, and of course PRs are always welcome!

of course PRs are always welcome!

@mstemm I actually just took another look (it's been a year) and I can't really sign any CLA's, so at this time, I can help out with code, sorry. If you change your mind, or if you're interesting in helping with mgmt, please feel free to ping me! Thanks!


Call to undefined function Basemkhirat\Elasticsearch\array_except()

In laravel 8 and php 7.3  when I call save function as written in the docs I get this error
Call to undefined function Basemkhirat\Elasticsearch\array_except() in file /home/elasticsearch/elasticsearch-practice/vendor/basemkhirat/elasticsearch/src/Model.php on line 349

I ran across this same issue when implementing this inside Lumen. I didn't wish to butcher the package itself so implemented the array_except function in a local helper.
Not suggesting my logic is the best solution
if (!function_exists('array_except')) {
    /**
     * Provide array_except helper. This is normally available in Laravel, however, not in Lumen.
     * Basemkhirat\Elasticsearch requires this
     *
     * @param array $array
     * @param array $exclude
     * @return array
     */
    function array_except(array $array, array $exclude)
    {
        return collect($array)->except($exclude)->toArray();
    }
}

Afterwards, I added this helper to my psr files list and rebuilt the autoload.. composer.json
...
    "autoload": {
        "psr-4": {
            "App\\": "app/",
            "Database\\Factories\\": "database/factories/",
            "Database\\Seeders\\": "database/seeders/"
        },
        "files": [
            "app/Helpers/Array.php"
        ]
    },
...

Hey @hrabbit take a look at matchory/elasticsearch - we're actively maintaining a fork without this issue and support for newer versions :)


Optionally support flexible column lengths

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
Add the ability to parse csv files that have flexible number of columns. Specifically a large subset of CSVs have columns missing from the ends of rows, and expect them to be treated as null.
Describe the solution you'd like
The ability to configure via the format or reader builder the option to enable flexible columns.
Describe alternatives you've considered
I have tried python and rust solutions, and while pandas and polars work for the general case, they both have poor support for streaming reads of csv into arrow buffers. Specifically they require either memory mapped files, or buffering most of the file in memory to work, unlike the convenience of the build/build_buffered methods offered by arrow-csv. And while the Rust csv crate is excellent, it is limited to row at a time parsing, and from basic testing I've done arrow-csv outperforms it when it comes to loading large datasets into arrow buffers.
Additional context
Example from other implementations:
Rust csv
https://docs.rs/csv/latest/csv/struct.ReaderBuilder.html#method.flexible
https://pandas.pydata.org/docs/reference/api/pandas.read_csv.html#pandas-read-csv
Pandas doesn't specify, but testing shows it allows missing trailing columns by default.
Similarly Polars behaves the same as Pandas and Rust.
https://docs.pola.rs/py-polars/html/reference/api/polars.read_csv.html
However one conflict is that the arrow-cpp csv parser doesn't allow ragged/flexible columns like the current arrow-csv.

label_issue.py automatically added labels {'arrow'} from #5679


Arch Linux package dependency

Hi, folks! Thank for a awesome tool!
Arch package have dependency awesome-terminal-fonts, it is possible to mark it as optional?  =)

See bug report for this: https://bugs.archlinux.org/task/62761

See bug report for this: https://bugs.archlinux.org/task/62761

Thanks @nogerine . Closing this issue as this is arch packaging issue and is not something that is controlled by us.

Thanks @nogerine . Closing this issue as this is arch packaging issue and is not something that is controlled by us.


[uss_qualifier] DSS0210,2 check op-intent references are synchronized

First round of checks regarding op-intent reference synchronization.
(This currently excludes DSS0210,2e which will come in a later PR, as well as constraint references, which will have their dedicated scenario)

Taking to draft while splitting fragments. Might elect to split things out to separate PRs

Ready for another round of review.
This PR sits on top of #535, the range of two last commits on the present PR represent its intended changes.

Parking as draft while a dependent PR is being updated.

Moved to draft while we reword and restructure the test fragments

Closing to reopen a clean PR, as things have diverged a lot from the origina.


Animating toast in and out

I'm submitting a ...
[ ] bug report
[x ] feature request
[ ] question about the decisions made in the repository

feature
Is it possible to easily add an animation (e.g. fade in or slide in) to all toast messages?

What is the current behavior?
No animation

What is the expected behavior?
Depending on the Animation type, a blending/moving/sliding toast message

What is the motivation / use case for changing the behavior?
Better User Experience

Please tell us about your environment:

Angular version: 2.1.0
Browser: all

Thanks
Torsten

Please add this it would be a nice addition to a great addon

+1

+1 👍

+1

+1


ConCurrentModificationException running dbm-gorm-diff in Grails 3.0.11

I can't seem to run within a multi-module gradle project the 'dbm-gorm-diff' command:
Command execution error: liquibase.command.CommandExecutionException: java.util.ConcurrentModificationException
dbmGormDiff FAILED
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':dbmGormDiff'.

Process 'command '/usr/lib/jvm/java-7-oracle/bin/java'' finished with non-zero exit value 1

Try:
Run with --info or --debug option to get more log output.

Exception is:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':dbmGormDiff'.
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:69)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:46)
at org.gradle.api.internal.tasks.execution.PostExecutionAnalysisTaskExecuter.execute(PostExecutionAnalysisTaskExecuter.java:35)
at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:64)
at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:58)
at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:52)
at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:52)
at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:53)
at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)
at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:203)
at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:185)
at org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.processTask(AbstractTaskPlanExecutor.java:66)
at org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.run(AbstractTaskPlanExecutor.java:50)
at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor.process(DefaultTaskPlanExecutor.java:25)
at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter.execute(DefaultTaskGraphExecuter.java:110)
at org.gradle.execution.SelectedTaskExecutionAction.execute(SelectedTaskExecutionAction.java:37)
at org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:37)
at org.gradle.execution.DefaultBuildExecuter.access$000(DefaultBuildExecuter.java:23)
at org.gradle.execution.DefaultBuildExecuter$1.proceed(DefaultBuildExecuter.java:43)
at org.gradle.execution.DryRunBuildExecutionAction.execute(DryRunBuildExecutionAction.java:32)
at org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:37)
at org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:30)
at org.gradle.initialization.DefaultGradleLauncher$4.run(DefaultGradleLauncher.java:154)
at org.gradle.internal.Factories$1.create(Factories.java:22)
at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:90)
at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:52)
at org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:151)
at org.gradle.initialization.DefaultGradleLauncher.access$200(DefaultGradleLauncher.java:32)
at org.gradle.initialization.DefaultGradleLauncher$1.create(DefaultGradleLauncher.java:99)
at org.gradle.initialization.DefaultGradleLauncher$1.create(DefaultGradleLauncher.java:93)
at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:90)
at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:62)
at org.gradle.initialization.DefaultGradleLauncher.doBuild(DefaultGradleLauncher.java:93)
at org.gradle.initialization.DefaultGradleLauncher.run(DefaultGradleLauncher.java:82)
at org.gradle.launcher.exec.InProcessBuildActionExecuter$DefaultBuildController.run(InProcessBuildActionExecuter.java:94)
at org.gradle.tooling.internal.provider.runner.BuildModelActionRunner.run(BuildModelActionRunner.java:46)
at org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35)
at org.gradle.tooling.internal.provider.runner.SubscribableBuildActionRunner.run(SubscribableBuildActionRunner.java:58)
at org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35)
at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:43)
at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:28)
at org.gradle.launcher.exec.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:77)
at org.gradle.launcher.exec.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:47)
at org.gradle.launcher.daemon.server.exec.ExecuteBuild.doBuild(ExecuteBuild.java:52)
at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
at org.gradle.launcher.daemon.server.exec.WatchForDisconnection.execute(WatchForDisconnection.java:37)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
at org.gradle.launcher.daemon.server.exec.ResetDeprecationLogger.execute(ResetDeprecationLogger.java:26)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
at org.gradle.launcher.daemon.server.exec.RequestStopIfSingleUsedDaemon.execute(RequestStopIfSingleUsedDaemon.java:34)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.call(ForwardClientInput.java:74)
at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.call(ForwardClientInput.java:72)
at org.gradle.util.Swapper.swap(Swapper.java:38)
at org.gradle.launcher.daemon.server.exec.ForwardClientInput.execute(ForwardClientInput.java:72)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
at org.gradle.launcher.daemon.server.health.DaemonHealthTracker.execute(DaemonHealthTracker.java:47)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
at org.gradle.launcher.daemon.server.exec.LogToClient.doBuild(LogToClient.java:66)
at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
at org.gradle.launcher.daemon.server.exec.EstablishBuildEnvironment.doBuild(EstablishBuildEnvironment.java:72)
at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
at org.gradle.launcher.daemon.server.health.HintGCAfterBuild.execute(HintGCAfterBuild.java:41)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
at org.gradle.launcher.daemon.server.exec.StartBuildOrRespondWithBusy$1.run(StartBuildOrRespondWithBusy.java:50)
at org.gradle.launcher.daemon.server.DaemonStateCoordinator$1.run(DaemonStateCoordinator.java:246)
at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
at org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
Caused by: org.gradle.process.internal.ExecException: Process 'command '/usr/lib/jvm/java-7-oracle/bin/java'' finished with non-zero exit value 1
at org.gradle.process.internal.DefaultExecHandle$ExecResultImpl.assertNormalExitValue(DefaultExecHandle.java:367)
at org.gradle.process.internal.DefaultJavaExecAction.execute(DefaultJavaExecAction.java:31)
at org.gradle.api.tasks.JavaExec.exec(JavaExec.java:75)
at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:75)
at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.doExecute(AnnotationProcessingTaskFactory.java:227)
at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.execute(AnnotationProcessingTaskFactory.java:220)
at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.execute(AnnotationProcessingTaskFactory.java:209)
at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:585)
at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:568)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:80)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:61)
... 70 more

I have the same problem with dbmGormDiff and dbmGenerateGormChangelog with Java 8 and Grails 3.0.10.  I'm assuming its ultimately related to this issue in Liquibase Hibernate
https://github.com/liquibase/liquibase-hibernate/issues/75
This plugin is largely unusable because it - unless anyone knows of a workaround?

upgrade liquibase-core to 3.4.2

@jkolobok Nice find, can confirm its working for me.

Awesome, this solved it for me too. If you're having this problem, swap out the liquibase version to 3.4.2 instead of the 3.3.2 recommended in the docs in your build.gradle
compile 'org.liquibase:liquibase-core:3.4.2'

Thanks @jkolobok !

So this fixes the original problem but breaks running migrations. So you have to go back and forth between the core older version and this newer one :( I suppose we need to open a bug with the liquibase core people?

Yeah.
I have this issue too. the only workaround I found is to generate and run using different version

I've created a PR to try an address this once and for all, by including the newer version of liquibase-core in the database-migration plug-in and updating the code where the liquibase API has changed.  so far I've tested dbmUpdate and dbmGormDiff on my own projects and its working fine, but it would be useful if others could build the PR and provide feedback.
The project itself seems to be in a big of a mess, a large number of the tests are broken locally, so I suspect the CI build will fail.  I'm working through fixing some of them at the moment.

Thanks @tjayr !

I had to revert the PR because too many tests are failing. They are all passing before the PR. @tjayr any word on fixing those? I can give it a shot, it seems the errors are related to not cleaning the database up between tests (getting table 'book' already exists) among other issues. I can take a look at your branch and see if I can fix them.

@rvanderwerf  Sure thats fair enough. A second pair of eyes certainly wouldn't hurt.
I don't think the issue is the cleanup between tests, but rather it seems that its executing a 'change' blocks in a grailsChange multiple times. It doesn't seem to be happening with validate, init etc.
`
databaseChangeLog = {
changeSet(author: "John Smith", id: "1") {
grailsChange {
init { ${GroovyChangeLogSpec.name}.calledBlocks << 'init' }
validate { ${GroovyChangeLogSpec.name}.calledBlocks << 'validate' }
        /* This change block executed multiple times! *
        change { ${GroovyChangeLogSpec.name}.calledBlocks << 'change' }

        rollback { ${GroovyChangeLogSpec.name}.calledBlocks << 'rollback' }
        confirm 'confirmation message'
        checkSum 'override value for checksum'
    }
}

}
I've been stepping through it with the debugger for a while now, but I can't see where its coming from.

The change block was being executed multiple times. Latest PR submitted adds a guard in to prevent this from happening and I've updated the the tests accordingly.


New Parameter for firstOrCreate

'firstOrCreate' Now Can Check In Specific Column With Specific Value
User::firstOrCreate( $data,  ['user_id',$id] );

Please fix the cs.

See https://styleci.io/analyses/8nW11X.

Also, please add tests.

Just seen about 5 dodgie PRs from you. Please get this working, then send a single PR with one commit.


Updated Device Specifying Command

The command react-native run-ios --simulator "iPhone 4s" wasn't working, and I think it's because there needs to be an equals sign in the command. ie. react-native run-ios --simulator="iPhone 4s"
I ran that command again, and it worked for me.

@facebook-github-bot shipit

Not sure why the builds failed.

I can import the PR and follow the builds internally to see what's happening - it's likely unrelated to this change. I can do that once you sign the CLA.

@hramos was there any reason why this pr was closed?

The PR was merged and closed. Your changes are now in master.