nuget CommonServiceLocator  Dependencies should be >= 1.0.0

Last nuget version SolrNet 0.5.0-alpha2

Dependencies
CommonServiceLocator (= 1.0.0)

the  CommonServiceLocator  Dependency should be >= 1.0.0

Yes, previous versions had >= 1.0.0, very annoying

Landed in master branch through PR #292
Will be part of next release

Included in next release.

Completed in 0.7.1


Makemd makes the # symbol for headings disappear

First, I would like to thank you for creating this fantastic plugin.
I am concerned that this plugin makes the symbol of # for headers disappear in LP when I put the cursor in the heading.
This is the screenshot when the plugin is disabled.

This is when the plugin is enabled.

Thanks

You can disable mark sans inside of make.Md settings to get the markdown syntax back
Get Outlook for iOShttps://aka.ms/o0ukef

From: Liong1976 @.>
Sent: Friday, December 16, 2022 7:18:26 PM
To: Make-md/makemd @.>
Cc: Subscribed @.***>
Subject: [Make-md/makemd] Makemd makes the # symbol for headings disappear (Issue #18)
First, I would like to thank you for creating this fantastic plugin.
I am concerned that this plugin makes the symbol of # for headers disappear in LP when I put the cursor in the heading.
This is the screenshot when the plugin is disabled.
[image]https://user-images.githubusercontent.com/88898230/208212222-e82435e6-3246-4e0a-bbec-156dbd291e86.png
This is when the plugin is enabled.
[image]https://user-images.githubusercontent.com/88898230/208212265-3028128d-ac63-4db3-9b1c-6d6f530dd6a0.png
Thanks
—
Reply to this email directly, view it on GitHubhttps://github.com/Make-md/makemd/issues/18, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAFHKNXIJPDLLTIOHIYIXRDWNUBFFANCNFSM6AAAAAATBT54UQ.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Oh, thanks @jp-cen

Hi @jp-cen.
Is there a way to disable Mark Sans permanently? I am not sure if there is an issue with Obsidian Sync, but I keep having to disable Mark Sans because it keeps re-enabling itself

That’s strange, the setting is also default off so not sure why it would turn back on. Will be disabling mark sans in the next update for now to until the issue can be resolved.

On Jan 18, 2023, at 1:08 AM, Andyspickle @.***> wrote:
Hi @jp-cen https://github.com/jp-cen.
Is there a way to disable Mark Sans permanently? I am not sure if there is an issue with Obsidian Sync, but I keep having to disable Mark Sans because it keeps re-enabling itself
—
Reply to this email directly, view it on GitHub https://github.com/Make-md/makemd/issues/18#issuecomment-1386539013, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFHKNRPQAFHSRC37V3FX23WS6CF5ANCNFSM6AAAAAATBT54UQ.
You are receiving this because you were mentioned.

Mark sans has been disabled and will be revisited in a future update with more stability


Homebrew halts installation on a fresh MacOS

Hey,
When installing YADR on a fresh installation I noticed that Homebrew fails because the installation method has changed. I am attaching the screenshot for the same.
I can open a PR for the required change. 😃

Sure, a PR is most welcome


Remove "New" from NewCaseForm(Values) and send curator edits

Sorry got git-snipped here where I got two PRs in one somehow :(

one does s/NewCaseForm/CaseForm everywhere
one sets the udpateMetadata upon edits, waiting for #394 to be properly implemented to show the last editor in the details page.

Is the NewCaseForm cypress test in this PR?

ah, actually no it's not been renamed but it only tests the "New" case... as we have the EditCase tests as well in a separate file... no big deal to leave it as is imo.

Is the NewCaseForm cypress test in this PR?

ah, actually no it's not been renamed but it only tests the "New" case... as we have the EditCase tests as well in a separate file... no big deal to leave it as is imo.

Ah true, sg.


Add a way to access context headers in the cache key for caching

Is your feature request related to a problem? Please describe.
I'm trying to add caching to one of our requests that is requested very often and I want to add a request header to the cache key. We're adding headers like { "store": "nl_NL" }
To achieve this I presume I need to access the context, but the documentatino doesn't mention anything about it. https://graphql-mesh.com/docs/transforms/cache
I've tried using the context but that doesn't work:
{typeName}-{fieldName}-{argsHash}-{fieldNamesHash}-{context.req.headers.store}
It seems it isn't used for calculating the cache key https://github.com/Urigo/graphql-mesh/blob/master/packages/transforms/cache/src/compute-cache-key.ts
Describe the solution you'd like
Pass the context to the computeCacheKey method and make it available
https://github.com/Urigo/graphql-mesh/blob/master/packages/transforms/cache/src/index.ts#L37-L42
Describe alternatives you've considered
Maybe it is already possible in some way, but would be nice if there was a mention in the docs somewhere :)
Additional context

Although the issue is still valid that it isn't able to use headers, we've found a workaround (do some caching at the ApolloClient)


Core: SlotMap refactor - Added NodesMap, Update the slot map upon MOVED errors

Description
This PR was previously reviewed in our redis-rs fork at https://github.com/amazon-contributing/redis-rs/pull/190 but was on hold due to lock issues. The recently merged PR #2643 addresses the encountered lock issues, making this PR now ready for merging.
This pull request introduces two significant updates:

SlotMap Refactor: The SlotMap structure has been updated with the addition of a NodesMap, which allows shard addresses to be shared between shard nodes and slot map values. This refactor optimizes how shard information is managed. For a detailed explanation, refer to PR #185.
The diagram on the left illustrates the current SlotMap design, while the diagram on the right shows the newly implemented structure:

MOVED Error Handling: Logic has been added to update the slot map in response to MOVED errors. Previously, this was handled only during refresh_slots operations. With this change, the slot map is updated immediately upon encountering a MOVED error. More information can be found in PR #186.

Issue link
This Pull Request is linked to issue (URL): closes #2123
Checklist
Before submitting the PR make sure the following are checked:

[ X] This Pull Request is related to one issue.
[ X] Commit message has a detailed description of what changed and why.
[X ] Tests are added or updated.
[X ] CHANGELOG.md and documentation files are updated.
[ X] Destination branch is correct - main or release
[X ] Commits will be squashed upon merging.

How can we test this with a real cluster and client? I think we can do E2E tests with CLUSTER SETSLOT command.

#2643

How can we test this with a real cluster and client? I think we can do E2E tests with CLUSTER SETSLOT command.

ATM we don't have a way to test the inner behavior of the cluster client in redis-rs, so we need to use mocks to make sure the right number of errors were caught/commands were executed internally.
Later on we can use the Telemetry lib Eran added to add these counters and use them for tests.
E2E tests are now being done with polyglot - where we test glide with EC clusters while performing different workflows such as scaling in/out/up/down, failover, upgrade and so on.
I ran these changes twice in polyglot to make sure our downtime remain the same/improves during topology changes.


TOA Plugin Incompatible

Runelite is stating that the plugin is incompatible and requires an update:

It's broken due to an accidental change on RuneLite's end, it'll be fixed probably later today

It's broken due to an accidental change on RuneLite's end, it'll be fixed probably later today

Where did you find this info?


missing files in package.json

Version
5.0.0-alpha.2 (react-router-redux)
Test Case
Not sure how to test an npm pack
Steps to reproduce

 npm install react-router-redux@next
include in project

Expected Behavior
Run without breaking
Actual Behavior
ERROR in ./~/react-router-redux/index.js
Module not found: Error: Cannot resolve 'file' or 'directory' ./actions in /Users/joshfurie/hero.client/node_modules/react-router-redux
@ ./~/react-router-redux/index.js 21:15-35
ERROR in ./~/react-router-redux/index.js
Module not found: Error: Cannot resolve 'file' or 'directory' ./middleware in /Users/joshfurie/hero.client/node_modules/react-router-redux
@ ./~/react-router-redux/index.js 70:18-41

Was just about to do the same PR. Related to #4694

Was just hit by this one as well

Is there a way to pull this change into my project? I can't seem to use the git repo because the project is nested.

@shawnmclean You can temporarily download this repo at this commit to your local environment then install react-router-redux with 'npm install --save file:Downloads/react-router/packages/react-router-redux/'. Section after 'file:' is the path where you downloaded/cloned this repo. After this gets merged remember to use react-redux-router from NPM.

Thanks!
BTW, please don't update the version from a PR. That will undoubtedly cause issues when pulling several PRs at once. And it signals a release when that hasn't necessarily happened.


Fixed issue when cluster was removed in e846f312

clang format successful! https://ci.trafficserver.apache.org/job/clang-format-github/397/

RAT check successful! https://ci.trafficserver.apache.org/job/RAT-github/408/

FreeBSD11 build successful! https://ci.trafficserver.apache.org/job/freebsd-github/2091/

AU check successful! https://ci.trafficserver.apache.org/job/autest-github/394/

Intel CC build successful! https://ci.trafficserver.apache.org/job/icc-github/522/

Linux build successful! https://ci.trafficserver.apache.org/job/linux-github/1986/

clang-analyzer build successful! https://ci.trafficserver.apache.org/job/clang-analyzer-github/655/


oud_status.sh does not work with default instance

oud_status.sh can somehow not handle the current oud instance. It tries to add a new one....

seems to work. don't know yet why...


[BUG] Ship Jitter

Describe the bug
Player ship appears to jitter randomly (ie, sway left and right really quickly) ever since the game speed was increased. May be caused by the aiming system being designed for a slower game.
To Reproduce
Play the game, fly around a bit. Sometimes staying still will trigger it. Ship orientation is not smooth.
Expected behavior
Ship orientation should be smooth and consistently pointing at or moving towards the player cursor, without jitter
Additional context
Liam H mentioned this may be caused by the aiming system being physics based.

This was resolved some time ago but the issue wasn't closed correctly.


Add documentation for CAProvider namespace and fix issue with SecretStore

Closes #509
The Namespace field in SecretStore was required, but not used since only ClusterSecretStores can access secrets in other namespaces. I modified the validation to instead ignore the namespace unless the type is ClusterSecretStore and in this case it isn't optional.
I also updated the docs to remove caProvider.namespace from the SecretStore CRD and add the new CAProvider documentation to ClusterSecretStore.

LGTM. Thanks for the fix, docs and tests :) There's a old comment in the example store that needs to be changed.

LGTM as well! Thank you for your contribution!

/approve

/ok-to-test sha=f468868

/merge


[1580] use callbacks to add or remote sites to course

this replaces the functionality of add_site! and remove_site!

Context
We should be able to add or remove sites to a course without having to resort to custom methods like add_site! or remove_site!.
Changes proposed in this pull request
Replace the functionality in those methods with callbacks in SiteStatus.
Guidance to review
This code was done as a proof of concept and, on account of it being pretty late and me not being able to see straight, could probably use a little tidying up. It also doesn't remove the mentioned methods, that might be slightly more work.
This change could probably happen independent of 1580-edit-locations-validations, if we think it's a good idea.
Checklist

[ ] Make sure all information from the Trello card is in here
[ ] Attach to Trello card
[ ] Rebased master
[ ] Cleaned commit history
[ ] Tested by running locally

I'm cool with this being separate. I'll prep it up now, and probably give it a new card.

Will re-cut this PR from another branch


Feature/refactor integrations

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


Graphback overwrites custom query with same name

Given this model:
type Query {
  getNote(id: ID!, test: String): Note
}

Graphback will ignore it and still use the generated query:
type Query {
  getNote(id: ID!): Note
}

Discussion we had in https://github.com/aerogear/graphback/issues/1597 could be useful here too.

See #1670
The problem is that buildModel is called multiple times, so the approach taken here will not work.
The first time buildModel is called it is using the original data model schema, which does not have any generated CRUD API yet. At this point it is easy to identify custom queries that have a clashing name. This PR uses this information to update the CRUD options on the ModelDefinition. The main benefit of this is there is a single source of truth for the model's CRUD config.
The next time buildModel is called, it is using the schema which has the Graphback queries generated. It sees this as custom user queries and updates the CRUD config accordingly, so no resolvers are created.
The obvious quick solution is to not update the model CRUD config from the custom queries, instead calculating this when needed. The issue I have with this is there are now two truths - The model CRUD config will say that the create CRUD is enabled (as an example), but Graphback does not generate this because the user supplied their own custom create query in the schema.

See #1670
The problem is that buildModel is called multiple times, so the approach taken here will not work.
The first time buildModel is called it is using the original data model schema, which does not have any generated CRUD API yet. At this point it is easy to identify custom queries that have a clashing name. This PR uses this information to update the CRUD options on the ModelDefinition. The main benefit of this is there is a single source of truth for the model's CRUD config.
The next time buildModel is called, it is using the schema which has the Graphback queries generated. It sees this as custom user queries and updates the CRUD config accordingly, so no resolvers are created.

Instead of updating the CRUD config, I was thinking maybe we can throw an error if the a model's crud config is activated for a certain query/mutation and the user provides a custom one? The error message could be indicative proposing either changing the name of the custom query/mutation or suggesting deactivating the corresponding crud operation on the model config.

That sounds like a better approach. The current approach silently disables generation giving no explanation to why the CRUD query is not working for them.
This PR is re-implementing the same behaviour that existed in an early version of Graphback (pre-plugins). That is not to say it should be the case.
I like your idea, I will leave this open a bit longer for discussion and we can decide to action it then.

Instead of updating the CRUD config, I was thinking maybe we can throw an error if the a model's crud config is activated for a certain query/mutation and the user provides a custom one? The error message could be indicative proposing either changing the name of the custom query/mutation or suggesting deactivating the corresponding crud operation on the model config.

Best way to resolve problem post 0.14.0 IMHO
For 0.14.0 I would document it briefly


Pie chart?

Is there a way to plot a pie chart ?

I'have done some modification in the header file to add the pie function.


Update OpenSSL to 1.0.2o and update Qt download URL

Oh boy you sure need to fix your CI.

We've focused on 1.14 (under the 1.14-dev branch) for the CI fixes, although yes, yes we do.

Should I retarget this one to 1.14-dev?

Ideally could you raise it against 1.10-dev and 1.14-dev? I'll be catching up with Doge tomorrow and hope to get it merged then!

update?

This PR was superseded by !1630


Support for sessionStorage

mobx-persist right now supports only localStorage, localForage and AsyncStorage. It would be better if it can support sessionStorage.
hydrate = create({ storage: sessionStorage }).then(() => /*do something*/ );
This will not work as create returns null.

mobx-persist doesn't support sessionStorage. So I went for localForage.
Problem was, localForage too doesn't support sessionStorage.
So I forked localForage and added support for sessionStorage. Since I needed the patch as soon as possible, I went on to create a new module instead of pull request to localForage.
Here is the client-persist package for sessionStorage support.
Installation
yarn add client-persist
or
npm install client-pesist
Usage
import { create } from 'mobx-persist';
import clientPersist from 'client-persist';

// to use sessionStorage
clientPersist.setDriver(clientPersist.SESSIONSTORAGE)

hydrate = create({ storage: clientPersist }).then(() => /*do something*/ );


Discriminator configuration

This is mostly a question, I saw in the stylegan2 implementation that they use mbstd_group_size=4:
https://github.com/NVlabs/stylegan2/blob/master/training/networks_stylegan2.py#L625.
In our case, it's set to None by default and then we use the batch size: https://github.com/patil-suraj/vit-vqgan/blob/main/vit_vqgan/modeling_stylegan_disc.py#L150.
My questions are:

Do we need to use 4 as they do? (this PR)
Do we need a way to disable minibatch_stddev_layer?

Hum, with batch size does it mean it just projects to unit vectors (mean + stdev) @patil-suraj


Display issue with indicators (images/text overlap)

Hi, see the screenshot below:

As you can see, the number of the country is overlapping with the country name. Can we fix this?

yes, I don't know why it's also borken in production.
Marcello pointed it on the release doc as well
it's fixed and visible on beta & dev


Grid span

Please can you provide more info on why you've submitted this PR? This branch exists for a reason.


Peer to peer programing

Please add card images of card in SVG format as these images are blurred.
It would be better if you add your profile links to your project.

Nice flow of the code and easy to understand


fix: Data manipulation issues in saml_credentials_provider

Description
issue #55 fix
Some minor changes to data manipulation to fix bugs that I have encountered when using redshift_connector.
Adding arn.strip(), because in some cases, when the list of arns is created in the line value.contents[0].split(","), value.contents[0] is a comma delimited string, and there can be whitespace before or after that string. For example
value.contents[0] = "my_arn_1, my_arn_2"
arns = value.contents[0].split(",")
print(arns)
>> ["my_arn_1", " my_arn_2"]

The second arn has a leading whitespace, which causes it to fail a regex formatting check. Adding strip lets us remove the unwanted whitespace.
issue #56 fix
The current check only confirms that values exists, but the existence of values doesn't guarantee that contents attribute will have a non-empty list. So this check fails when values[0].contents = []
                if len(values) == 0:
                    # Ignore empty-valued attributes.
                    continue
                value: str = values[0].contents[0]

Changing this to if len(values) == 0 or not values[0].contents: adds an extra or check to also ensure that there
Motivation and Context
This fix solves the following issues:
issue #55
issue #56
Testing

Both changes were tested by running a simple script to create a connection and run a query.
import redshift_connector

gdp_conn = redshift_connector.connect(
    iam=True,
    database="mydb",
    cluster_identifier="mycluster",
    credentials_provider='OktaCredentialsProvider',
<EMAIL_ADDRESS>    password="mypassword",
    idp_host="myidphost",
    app_id="myapp/id",
    region="us-east-1",
    role_arn="arn:aws:iam::999999999999:role/My_Role",
)

with gdp_conn.cursor() as c:
    c.execute("select top 1 * from pg_user")
    result = c.fetchall()

    print(result)

(['dbuser', 100, True, True, False, '********', None, None],)

(note: all string values have been replaced with dummy values as they contain sensitive information)
Backwards compatibility was not explicitly tested, but we can be sure that these changes won't do anything to harm the existing code:
arn = arn.split() will only remove whitespace. If executions did not previously introduce whitespace, the value of arn will not be changed.
if len(values) == 0 or not values[0].contents: will only change the logic if values[0].contents is empty (and if it is empty, it will throw an error anyway)
Screenshots (if appropriate)
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Checklist

[x] Local run of ./build.sh succeeds
[x] Code changes have been run against the repository's pre-commit hooks
[x] Commit messages follow Conventional Commit Specification
[x] I have read the README document
[ ] I have added tests to cover my changes
[x] I have run all unit tests using pytest test/unit and they are passing.
Note that I did not add any unit tests, as I felt the scope of the changes were so minor that they did not warrant an additional unit test.

Note, that unit tests failed 18 tests, however these tests also appear to be failing on the master branch of the repository, so the code changes introduced did not cause the unit tests to fail. (this could just be an environment issue on my end, but this seems okay to me)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hi @kylemcleland-fanduel ,
I hope to give this a review by end of week, thanks again!

Hey @kylemcleland-fanduel ,
I've been able to reproduce the issue with ARNs on my end.
I've confirmed this change does not cause any regressions in our test suite.
As for the failing unit tests you noted above, the cause of this is a missing config.ini file in the repo -- so no error on your part :)
We use this file in our CI to store information specific to our testing setup (i.e. Identity provider information, connection parameters, etc.). Since it's missing from the repo, these errors occur. I need to include some mocked out config.ini file in the repo, so the unit tests can run without issue and if desired the integration tests can be run with a valid Redshift cluster and identity provider setup (if applicable)....but this is a problem for later.
let's get this merged!


Remove expect_raises matcher without type argument

As @yxhuvud mentioned in #5092 (line-comment), the arg-less expect_raises matcher doesn't verify the type of an exception: it rescues any exception raised by the example block and thus can lead to hidden errors because even unexpected exceptions are accepted.
That's why this matcher has been deprecated in rspec.
An example should only be expected to raise one specific type of exception.
I'd suggest to remove this matcher entirely. There is no reason to have it besides implicitly advising people to use this instead of a proper type-checking matcher. There were quite a few in the standard lib alone.
If, for some reason, there is a very unlikely need to rescue any spec, it can simply be replaced by expect_raises(Exception).
It's also an option to deprecate it at first and remove it later, but it's only breaking (badly-designed) specs.
As a replacement, it might be considered to add expect_raises(message) which only matches an exception of the exact type Exception (no subtypes -- but that's debatable) with a matching message, being the equivalent matcher for exceptions created by raise(message : String).
I also noticed a few exceptions which could be improved:

Nil#not_nil! could raise a custom exception (NilAssertionError). It is commonly used such that a specific exception type would be great.
writing to a read-only Slice could also be a candidate for a custom exception.
Enum.from_yaml parsing an integer id raises Exception: Unknown enum YAMLSpecEnum value: 3, but parsing a enum name raises ArgumentError: Unknown enum YAMLSpecEnum value: Three (messages taken from yaml/serialization_spec.cr). I think both should raise the same error type, since there is no real semantic difference.

@straight-shoota ouch on last commit noise 😞
As suggested, this PR should focus on one specific thing. The cosmetic details of other elements across the codebase can be solved in a separate PR.
It now makes the entire PR review a bit more tedious, basically:

Well, you can look at the individual commits like 6b727eb3. But okay, I'll reorganize this in a different PR.


Strikethough Syntax

When using a google doc and assigning font as strikethrough this is not created correctly.
Strikethrough uses two tildes. ~~Scratch this.~~

Thanks I really have been enjoying this add in.

Hi - will look at this for you shortly!
Jd

I don't really use it, but was just testing all the possibilities and noticed it wasn't working.

Hi,
Thanks for the report & feedback - I've popped some extra code in the Markdown.gs file to check for strikethrough text and output appropriately. As 'strikethough' is not part of the 'original' Markdown syntax, I am thinking of fully going over to Github-Flavoured Markdown (as that's where all the stuff ends up!), which means a few more changes to bring the parser in line with all it's features / idiosyncrasies. The code base (on this repo) is now up to date, but I've been working on a few other changes (YAML property setting in the Add-On) so will await completion of that version before pushing it live to the Add-On store.
Yours,
JD


IOS - Chat - Language is not updated after go back online

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Issue found when executing PR https://github.com/Expensify/App/pull/14591
Action Performed:

Log in with the same account in IOS app (main) and Web (secondary)
Disable the internet in IOS device
Change the language in Web to Spanish
Enable the internet in IOS app

Expected Result:
Language should be updated in IOS app after back online
Actual Result:
Language is not updated after go back online
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[x] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/93399543/217266822-af755af1-b653-4286-ba8e-a7df177dd30f.MP4
Another tester's video
https://user-images.githubusercontent.com/93399543/217267089-0d74901a-41fd-4503-a9a0-82449f7b9161.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub

Triggered auto assignment to @NicMendonca (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

@kbecciv did you mean to iOS safari or app? I can't reproduce this on either. My language is set to Spanish as soon as I get back online (on safari and app)

@NicMendonca I meant IOS app.
Let me check again, will update you shortly

Not reproduced with build <IP_ADDRESS>
https://user-images.githubusercontent.com/93399543/217852927-a67b0704-2d1f-4990-a210-23c4a1c7a9c9.MP4

@kbecciv got it! in that case, can we close this?


About the color jitter

Hi! Thanks for releasing the code of this great work. I have a question about the color jitter. Why is it only added in training but not in validation? I thought it was added to avoid reconstructing inputs through shortcuts. However, if it is only added in the training phase, it is more likely to be an augmentation.

"Identical shortcut" is a problem brought by the training process. If the model has avoided the shortcut during the training, it is not necessary to use the feature jittering during testing.
Also, all operations in test stage should be non-random, but feature jittering is random.

Thank you for your response. I have an additional question for clarification. As I understand it, abnormalities are identifiable due to their distinct feature distribution compared to normal data. The model never learns to reconstruct the abnormality in training and thus fails in the testing phase. However, if all images in the training phase were processed by the color jitter, is it possible that the normal images without color jitter will be detected as abnormal in the testing phase?


[$500] Web - Preferences, Security, About, Workspaces animations are missing

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.36-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Issue found when executing PR https://github.com/Expensify/App/pull/34718
Action Performed:

Log in to New Expensify
Navigate to Preferences
Navigate to Security
Navigate to About
Navigate to Workspaces settings

Expected Result:
Appropriate animation should be displayed in all of the pages
Actual Result:
Animations for all above mentioned pages are missing
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[x] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/3d3d6fe0-dd3d-4041-b0d9-962c29da8a62
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0158a6748a5057f6d8
Upwork Job ID:<PHONE_NUMBER>000962048
Last Price Increase: 2024-02-02

@lanitochka17 sidenote I can't tell from the screenshots, are the fonts correct here?

I think your assets may not have loaded @lanitochka17

I can repro on web, but only in the Security tab. The Preferences tab works fine.
The console shows a Invalid .lottie file, manifest.json is missing error.

The fonts are also incorrect but I think that's a separate issue 😄

It works fine on dev though. That page uses the Safe.lottie animation, which hasn't been changed in months. I'll make this external, let's see if anyone can figure it out.

@francoisl thanks for looking into this deeper, I'm still unable to reproduce on staging

Same, I can't repro anymore today. Let's get someone else to test for good measure, and if they can't repro either then let's close this.

Can't repro either. Gonna close it out.


【Hackathon 4 No.132】IBot

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: diadestiny:x: PommesPeterYou have signed the CLA already but the status is still pending? Let us recheck it.


[UX Design] Visual design of interface

Mockup of what the layout, colors, buttons of the interface should be.
Some references, but just recommendations:

http://rui.dc.gov/style-guide/
https://standards.usa.gov/getting-started/ (design package)
https://www.michiganbenefits.org/steps/introduce-yourself (similar data-entry type interface)

Refer to progress and mockups in #20

Closing, design is incorporated into https://github.com/codefordc/cfsa-referral/issues/20


Analog tile with torch tensor interface

Description and motivation
Currently, each analog layer creates and maintain its own analog tile, invoking its functionality at selected points in time. An interesting alternative would be to move the analog tiles "closer" to being tensor-like entities, as it is likely to make the integration with torch easier and more robust and open more possibilities and use cases.
In particular:

avoid workarounds for passing information such as in #211, #140 and others, and streamline other pieces.
be able to treat them as first-class citizen in torch (either as Parameters or Buffers if needed)
potentially being able to move functionality into them (optimizers, etc)
simplify the library, potentially cutting down the number of code layers involved in some operations

Proposed solution
Explore the possibility of creating a AnalogTensor which overloads the tensor functions that are implemented in analog (rank update, addr and matrix-matrix product mm):
https://pytorch.org/docs/stable/notes/extending.html#extending-torch-with-a-tensor-like-type
Alternatives and other information
N/A

Is it possible to define multiple tiles per kernel? Let say the device is a binary device (low and high resistance), and you want to have multiple cells per weight to achieve high precision weight representation. Then you will need multiple tiles per kernel where each tile represents a single bit position for all the weights in the kernel.
Also, would it be possible to define multiple tiles per layer (corresponding to the number of kernels in the layer)?

Hi @SaBaKa2020 ,
thank you for your question (best to open up a new issue for any new question, to make it easier to find). We have the option to have multiple unit devices per weight element (see VectorUnitCell here), however, the input is identical for each of the devices.
If you want to have a specific layer, with scaled input you could build your own compound linear/conv layer by connecting multiple AnalogLinear/Conv layers each for a different scaled input slice and summing the output. Note that in this case the summing would happen after the ADC (in contrast to above, where the current is summed in analog).


Adding example using imageops

As discussed here, tried reading in GeoTiffReader to image::ImageBuffer but cannot seem to get it working with any of the from methods. Would you have a link to the points iterator? I couldn't find it in this repo or image or tiff.
Another interesting alternative might be to use image::load.
But that would need GeoTiffReader to have the traits Seek and BufRead. Any thoughts?

Added an example using image-rs in 6d593f6d403845f8380f56f5bb583401aea20c8c


Specify mutably borrowed field is mutably borrowed

Changes immutably to mutably borrowed for the description of a mutably borrowed field in the docs.
Saw this from the reddit post you made. Good luck with the project!

Thanks, nice catch!

Wrong button, my bad :P


[gpu] Mesh normals are not being passed to the shader

Not sure if ive setup the shader properly but as far as i can tell all GenMesh functions (GenCube, etc) are meant to generate normals automatically, and these normals are meant to be passed to the shaders automatically as 'vertexNormal'.
Apologies if i got this wrong.

the cube in this image should be white if a normal is being passed.
ShaderNormalsTest.zip

@danemadsen Yes, that's right, default shader does not support normals. To use them a custom shader is required.
Default shader is mostly intended for batch system drawing or very simple models. When normals are involved, it's supposed user needs them for lighting so a custom shader is required.


Added Const, Iota, Iterate, Replicate

In an informal nutshell: (*s can be a sequence)

(Const!Xs)!Ys == Xs; where Ys is not evaluated.

These functions have been requested once in a while in the learning forum. Are there any cons against having them in the library?
If someone has ideas to further generalize them, please tell me.

There are two problems with Iota:

it's already defined in std.experimental.ndslice internal package (you've probably noticed the auto-tester failure)
phobos already defines something similar: std.typecons.staticIota, but its protection is package.

Considering the last point, I think that it would be better to

remove Iota from this PR
in a new PR

rename your template to staticIota, add this template to std.meta.
alias the one from typecons to this new version (since yours is a bit better).

There's already been discussion about the existing staticIota, saying that it should be public. Now that the bug 314 is fixed, I think it's a good opportunity to replace it and make it public.

std.meta.aliasSeqOf superseded staticIota:
static assert(aliasSeqOf!(iota(1, 6, 2)) == AliasSeq!(1, 3, 5));

Replicate looks quite similar to std.mete.Repeat, though the latter does not allow n==0. In fact, it was written by me and the design is based on the idea that no repetition would be meaningless.
If necessary, it can be modified for zero n.

@BBasile Your suggestions are sensible, so I just removed Iota. If the workaround is that easy like @JakobOvrum stated, maybe we just don't need Iota at all. As this is for a new pull request, let's discuss that there.
@e10s Somehow I must have overseen Repeat (looking embarrassed to the ground...). I think making Repeat allowing n = 0 is easy, sometimes useful and nobody will have serious problems with it. In contrary, sooner or later someone will expect it to work for n = 0 in this way.
@9il I've never seen sizediff_t. It seems to be very unknown and Google has no results searching the language spec. Is it the same as ptrdiff_t? I've changed it to that. If there is a reason for using sizediff_t, I'll just change it again.

I'm sorry but it seems, according to Jakob O, that I was wrong. I missed that aliasSeqOf was added to phobos and my comment is actually based on an older discussion related to a Q. on stackoverflow.

Sorry, this was a mistake.

I'm closing this and open a new PR with Iterate only. So far, nobody has complained about it. Then we can discuss if it is worth having it in Phobos.


Fill travel document details screen

POST request to users/self/bookings/edit/{bookingId} with token/simple_token


New version: NextDNS.NextDNS version 2.2.1

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[X] Does your manifest conform to the 1.0 schema?

Microsoft Reviewers: Open in CodeFlow


Resolve issues with traits in ClassScanner

Only the first use statement would be accounted for when getting lists
of traits, due to unnecessary break statements at the end of the loop.
Fixes #58
If one of the methods touched by this commit, such as getTraitNames(),
or getTraits(), which calls getTraitNames(), was called as the first
action on this class, no traits would be returned, due to the fact
that scan() was not called at the start of the method. Fixes #57

I'd really appreciate it if this and #61 could be reviewed. I'm writing a piece of software that depends on these issues being resolved

Is there a reason why this wasn't looked at before the release of v3.0.3?

@djmattyg007 Honestly, I accidentally skipped over it when reviewing PRs yesterday. It looks like we'll be doing a 3.0.4 quite soon, though, so I'll merge this now and target that version.


Class 'Bjrnblm\Messagebird\MessagebirdServiceProvider' not found

Since upgrade to Laravel 5.6 i get: Class 'Bjrnblm\Messagebird\MessagebirdServiceProvider' not found

Made a pull request

Hi @basvandertogt
Thanks for your PR, i merged it. I would advise not using this package, it was just a little test package made years ago and not maintained at all.
Its safer to use messagebirds package directly: https://github.com/messagebird/php-rest-api
I might archive this package in the near future.


Add JavaScript to antlr and clean up the Java code

Describe your changes :

See #4010
I have committed the generated code because we do the same thing for the JSON Schema generated code.

Type of change :

[x] Improvement

Checklist:

[x] I have read the CONTRIBUTING document.
[x] I have commented on my code, particularly in hard-to-understand areas.
[x] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

Reviewers
Frontend: @shahsank3t, @darth-coder00, @Sachin-chaurasiya, @vivekratnavel

@amiorin do we need antlr inside of generated directory or can we keep it separate?
The script to generate typescript from schema will clean-up generated directory and then create typescript interfaces


rdbroker.wvd.microsoft.com

This doesn't work..
Basically shows that URL is down

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

ID: 970202b7-165f-18df-e928-c47c45a18755
Version Independent ID: d5393b62-4211-72f5-fc7a-363f68f6d8a2
Content: Create a host pool with Azure Marketplace (preview)  - Azure
Content Source: articles/virtual-desktop/create-host-pools-azure-marketplace.md
Service: virtual-desktop
GitHub Login: @Heidilohr
Microsoft Alias: helohr

Worked for me. What's the actual error you are seeing?

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

The URL itself doesn't load as a web page, you use the Remote Desktop client to access the resources.

@jontowles This worked for me.

@jontowles We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


[BACKEND] Prevent vectorization in convert_layout transposes

When convert layout transpose elements we cannot vectorize both loads and stores. Deciding to only vectorize one would cause extra bank conflicts on the non-vectorized one that cause performance slowdown.

Is it worth having a test?

Bank conflicts might be sometimes fine and could be compensated by higher throughput instructions. Like sometimes it might be beneficial to load fast with some store conflicts.
I agree that it's probably worth looking into experimental statistics.

Bank conflicts might be sometimes fine and could be compensated by higher throughput instructions. Like sometimes it might be beneficial to load fast with some store conflicts.
I agree that it's probably worth looking into experimental statistics.

On a simple transpose kernel it shows significant performance differences

On a simple transpose kernel it shows significant performance differences

Can you please attach the kernel as a reference? Thanks

On a simple transpose kernel it shows significant performance differences

Can you please attach the kernel as a reference? Thanks

I don't have a public kernel, I'll write one at some point

Is it worth having a test?

updated the test


feature: add verification to check if the mason registry is correctly added

Did you check the docs?

[X] I have read all the docs

Is your feature request related to a problem? Please describe.

Describe the solution you'd like

Describe alternatives you've considered

Additional context
No response

Adding registries programmatically seems not possible.
https://github.com/williamboman/mason.nvim/issues/1749

r


There is no Wireguard-related configuration UI in SoftEtherVPN

If Wireguard was added to SoftEtherVPN, where is Wireguard related UI?

Unfortunately the new settings API is not implemented in the graphical server manager, please use vpncmd.


reimplement openmp in pseudopotential calculation

In PR#216, total elapsed time of an optical response calculation in the isolated system slowed down from 165.2 sec to 169.7 sec with 12 nodes on the K computer . By this implementation, it recovers to 164.0 sec.
@syamada0 san, could you check this PR?

Thank you @mn2007 san. I will check it later.

@mn2007 san, I checked the performance of the code but could not confirm such speedup on the Oakforest-PACS computer.
However, in principles, this modification cannot negatively effect the performance.
So I merge this PR.

Thank you for checking details and merging, @syamada0 san.


Backup-DbaDatabase support for taking copy only backup from a non-readable secondary

Support taking a copy only backup from a non-readable secondary instance of a db in an always on availability group.

@mqunbar how are you not able to do this now?
Something like this should work:
$params = @{
    SqlInstance = SecondaryReplica
    Database = YourAgDb
    BackupDirectory = "\\SomeNetworkShare\Backups\YourAgDb\"
    CreateFolder = $true
    Type = Full
    Initialize = $true
    CopyOnly = $true
    CompressBackup = $true
}
Backup-DbaDatabase @params

Just tried that in the current version and it works.
@mqunbar : Can you please try and tell us if it works for you?


Refractor App.js HomeScreen & Updated HomeButton.js

Changes Made

Refractored the HomeScreen function in App.js to have buttons and logos to be within a StyledView, ScrollView, StyledLogo, and StyledHomeButtonView views
In StyledView, added flex property in StyledHomeButtonView and StyledLogo to have the logo and buttons take up the appropriate amount of space in the Home Screen
In addition, refractored how the HomeButton component was called  in App.jsand included source as a prop.
Refractored HomeButton.js to use props and styles applied to the text on the home screen.

Current Roadblock Right now, the Home Buttons in different screen sizes look a bit inconsistent and weird to me. I know that I'll need to:

Use specific properties to help make the buttons responsive for different screen sizes (min-width, max-width, flex-grow?)
Apply these properties to the right location (should it be applied in the View for these buttons or the button themselves?)

My brain is kind of in a fog so as I break, I am going to go and work for Uber for a few hours to refresh my mind.
Please drop down any feedback on what I could be overthinking or whether these changes look good as is.
Cheers, Maya (:
Time Spent: 3+ Hours

You could use the @media CSS selector to hard code values for different screens size intervals that don't display properly to avoid unexpected behavior and not have to create one solution to fit all screens.

As of now, the HomeScreen reflects the Figma! Please leave any remaining comments and or your approval to merge this to the main branch. @varmaa23 @sukritsangvong
In terms of responsive design to the smaller and larger iPhone screens, that is something outstanding and something I feel like is its own task in itself.


Already Finished Module 4 but push rejected

Hi I need some help pushing the latest module4_VV_VEP_final.py to which branch. Its there on my local remote

I have successfully push it to main. Its weird though. I thought we are protecting main and keep the branches open

Hi, I have encountered this new problem today: Is it the same?
! [remote rejected] HEAD -> Team-3 (protected branch hook declined)
error: failed to push some refs to 'https://github.com/gl186/SprintFinish'
But as I am testing for main.pyintegration I am not eager to push to main. I will show my result directly to team in meeting.

It is a problem with the branch protection I have put. I am editing it now and will let you know if it works.
I am going to still require a pull request to merge but I will allow force pushes to us specifically as a back up. Does that sound reasonable?

please try and commit and push now. I have set the rules as this:
all branches require pull request to merge
no deletions or force push onto main
do we think that is sensible?

I wiil try to push to branch Team-4 and will update

I wiil try to push to branch Team-4 and will updateI

I think the protection on branch needed to be modified

I have not tried that yet for today but will let you know if there is positive result. I got a feeling when we tick the first upper box that say commit to non protected branch bla bla is what cause it ...but im not sure..just a wild guess. i mean for the branch setting

the box that say require a pull request before merging...on the section protecting matching branch...just my assumption that is the one that cause the hook thing

Any suggestions? Force pushes are blocked but pull requests are allowed so I don't see why it won't let you. Maybe commit and then pull request rather than pushing and it will merge the changes?
yup already tried that just now. my push still got rejected. I think the only choice now is to untick the box that say 'require a pull request before merging'...'on the section protecting matching branches'..I think that is the only I can suggest right now

problem rectified by amending branch rules during team meeting with @LMP2005 @SonjaR-UniMan @Lindaalnsour

you will be able to push onto all branches but main now which remains protected. issue completed but not closed to remain open for assessment purposes.

Glad you guys managed to sort that out. Thank you so much. I have able to push to Team-4 branch now. I will close this issue now.

Thanks again.

Thanks


Confirmations fix

Fixing wrong confirmation number (#57)
Corrected Claim link on home page (#58)

Thanks @marcdeb1 , you da man! Will shoot you a DM on Slack. @nikooo777 / @akinwale can you please review / merge / deploy?


:focus-visible

Related to this story
https://github.com/WICG/focus-ring/issues/95
The :focus-ring pseudo class seems to be renamed to :focus-visible https://drafts.csswg.org/selectors-4/#the-focusring-pseudo
https://github.com/w3c/csswg-drafts/pull/2104

Thank you @jonathantneal , I hope the release soon.


Print the error detail from the cli

When a user does blueapi controller run <...>, getting a message which simply says "Error 422" is not very helpful. The server does define error response detail, this should be printed in the console.

@stan-dot has previously expressed a preference for terse output, maybe we should just add a --verbose flag and let the user decide?

Sure, I'm ok if it's behind a flag, I just don't want to have to run the server in a debugger just to find out how my params are wrong


dart2js inlines over deferred-library boundary

Dart2js should not inline over deferred-library boundaries, as this is the mechanism that we recommend for (confidential) experiments.
In the following example, the deferred library's code is inlined into the main fragment:
a.dart:
import 'b.dart' deferred as def;

main() {
  def.loadLibrary().then((_) {
    print(def.foo());
  });
}

b.dart:
foo() => "some str";

output.js:
    main_closure: {
      "^": "Closure:1;",
      call$1: function(_) {
        H.checkDeferredIsLoaded("def", "b.dart");
        P.print("some str");
      }
    }

Related to #24356.


Add relay metrics

Add Prometheus metrics to the relay package. The new metrics match the existing Stats struct.

Pass the channel name to the NewChannel func so it can be used as a label.
Refactor metrics namespace into the config package.

CC @danimo


Kubernetes GenericClient delete methods throws JsonException

Our Test_KubeGenericClient tests throw JsonException when deleting existing objects.
Why is this happening?  I don't believe we're causing this and the objects appear to be deleted correctly.
I'm temporarily ignoring this in the KubeSenericClient.DeleteAsync() and DeleteNamespacedAsync() methods.

We're quite a bit behind on the KubernetesClient releases because KubeOps is too.  Perhaps upgrading will fix this.  I don't see any related issues on their github repo.

CLOSING: Turns out that we don't need to use GenericClient after all, so this is moot.


Please consider releasing a new version.

A number of tech firms have legal and security departments that periodically review the use of 3rd party libraries like this one, looking for libraries that considered "abandoned".  Now, I know karma-junit-reporter is not actually abandoned, but it hasn't had a release in almost 3 years, higher than the usual threshold of 2 years.
I see that there have been several PRs with updates to dependencies and such (e.g. #166, #167, among others) and some have been accepted and merged to master.
Is is possible for the owner of this repository to generate a release with a new version number?

2.0.1 is available


Ability to use FetchOperation directly.

We'd like to be able to use FetchOperation directly, to enable us to cancel previous operations.
//Cancel previous operation
self.operation.cancel()

//
self.operation = FetchOperation(query: query, spine: self)
self.operation.completionBlock = { [unowned operation] in
....
self.operation.start()

I think it's better to keep the operation itself an implementation detail. Making it a public API will make it much harder to refactor inner workings if needed. Luckily the FetchOperation class is pretty simple, you it should be easy for you to create your own NSOperation subclass that does the work.

Thanks for response @wvteijlingen.
I'm in the process of having to create my own operation.
It would be good to be able to subclass from ConcurrentOperation, however this doesn't seem to be possible due to:

Even if subclassing from NSOperation it would be good if Spine's Failable was public also.


[Tabs] Keyboard navigation does not work with disabled tabs

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current behavior
Tabs keyboard navigation does not behave correctly when there are disabled tab items
Expected Behavior 🤔
Keyboard navigation should either allow the selected tabs to be focusable but not selectable or skip them. According to W3C accessibility standards, they should be focusable but not selectable.
Steps to Reproduce 🕹
https://codesandbox.io/s/material-demo-v5ddi?file=/demo.js
Steps:

Try to use the keyboard to navigate through the tabs after focusing it

Tech
Version

Material-UI
v4.10.0

Hmm, I’m in favour of allowing keyboard navigation to disabled items in group components.

When a custom control becomes disabled, remove it from the tab order by setting tabindex="-1". Note that disabled items within a grouped widget (such as menu items in a menu) should remain navigable using arrow keys.

Source: https://developer.mozilla.org/en-US/docs/Web/Accessibility/Keyboard-navigable_JavaScript_widgets

The main issue here is that you cant actually navigate through the tabs if you have disabled items.
@joshwooding thanks for pulling the link for the reference

@diogofscmariano Could you link the W3C recommendation?
All I'm aware of is https://www.w3.org/TR/wai-aria-practices-1.1/#kbd_disabled_controls which basically says: "It depends but be consistent".
Which means we're technically good but we should offer customization and a better default. I'm always in favor of following the APG by default but it's clear that there should be an option to remove disabled items from the focus order.

That was the one I'm talking about: https://www.w3.org/TR/wai-aria-practices-1.1/#kbd_disabled_controls
I'm fine not having them focusable. I just dont think we should not allow the user to navigate through the non-disabled ones. If you try to use the keyboard with disabled tabs you will see you cant circle over all navigable tabs.

That was the one I'm talking about: https://www.w3.org/TR/wai-aria-practices-1.1/#kbd_disabled_controls
I'm fine not having them focusable. I just dont think we should not allow the user to navigate through the non-disabled ones. If you try to use the keyboard with disabled tabs you will see you cant circle over all navigable tabs.

+1.  Without some form of skipping you can never get to the active tabs between two disabled ones.

still actual

This is exactly what we have found. We would like to be able to use the arrow keys and allow focus to aria-disabled="true". We have actually implemented our own disabled attribute that does not make buttons/tabs html disabled, but does make them aria-disabled and we style them via CSS to be disabled.
We would like: "Keyboard navigation should allow the selected tabs to be focusable but not selectable."
Basically line 55: https://github.com/mui/material-ui/blob/master/packages/mui-material/src/Tabs/Tabs.js#L55
should just not have the || nextFocus.getAttribute('aria-disabled') === 'true'
and it will work for our needs.


[SPARK-16391][SQL] KeyValueGroupedDataset.reduceGroups should support partial aggregation

What changes were proposed in this pull request?
KeyValueGroupedDataset.reduceGroups is currently implemented via flatMapGroups, which does not support partial aggregation and so is very inefficient.
KeyValueGroupedDataset.reduceGroups should support partial aggregation. This PR implements it with Aggregator.
How was this patch tested?
Existing tests.

Test build #62375 has started for PR 14222 at commit 1135773.

Test build #62375 has finished for PR 14222 at commit 1135773.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62375/
Test PASSed.

there is a usefulness to this ReduceAggregator beyond .reduceGroups. basically you can take any Aggregator without a zero and turn it into a valid Aggregator, with the caveat being that the result is nullable and will be null if no inputs are provided to the Aggregator.

Test build #62454 has started for PR 14222 at commit 4ba124c.

Test build #62456 has started for PR 14222 at commit 7e8d8c1.

Test build #62454 has finished for PR 14222 at commit 4ba124c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62454/
Test PASSed.

Test build #62456 has finished for PR 14222 at commit 7e8d8c1.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62456/
Test PASSed.

ping @rxin The change is ok for you? Thanks.

@viirya I'm going to take over the PR and play with the API a little bit.

Ok.

Test build #62594 has started for PR 14222 at commit 6032325.

Test build #62594 has finished for PR 14222 at commit 6032325.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62594/
Test PASSed.

Merged build finished. Test PASSed.

@rxin Any thing I need to update for this? Thanks.

ping @rxin

ping @rxin any thoughts on this? It is waiting for a while. Thanks.

I've created a pr here for discussion, based on my playing with the API: https://github.com/apache/spark/pull/14576

Close this now since the pr #14576 is merged.


fix STI for config via php attributes

STI not works for config via php8-attributes without doc comments.
I have similar 2 pair of classes with ORM config via Annotations and Attributes. As you see on  left side on screenshot ORM creates one table for [ClassA1, ClassA2] and two tables for [ClassB1, ClassB2]

👍


Collisions

When I wrote a polyfill for this feature, I considered many different options, including something similar to used in your ponyfill. I already don't remember all the pitfalls I encountered and why I chose full parsing for parse. However, your code has at least one obvious problem:
parse('{"a":9007199254740993,"b":9007199254740992}', reviver); // => { a:<PHONE_NUMBER>740992, b:<PHONE_NUMBER>740992 }
parse('{"a":9007199254740992,"b":9007199254740993}', reviver); // => { a:<PHONE_NUMBER>740993n, b:<PHONE_NUMBER>740993n }

I see, yes I need to change numbers as key into special strings as key so that each number will preserve its identity, thank you

Aha, I found a (hopefully) smart way to have the source for free without a sweat while preserving, or preventing, collisions. It was a lovely call and gotcha to fix but if you have anything else I didn't think about please do let me know and I'll fix all the things.
The only "caveat" I see with this approach is malformed JSON that would throw anyway on parse or the possibility that a JSON contains 2**52-1 strings (as values, keys are not pushed) but I think at that point anyone using this module would have a "slightly bigger problem" and I don't need to cover terabytes of JSON parsing in my projects that need this feature. Beside that, I think this should work fairly well, fast, and compact 👋


[iOS Wrapper] Fixed build issues

Replaced OpenSSL with OpenSSL-Universal
Removed CoreBitcoin pod
Added logic for Base58 data conversion.
Added support of Swift classes in Indy-demoTest

Nice! It would be great to include support for Swift 5 here (https://github.com/hyperledger/indy-sdk/pull/1611).

It looks like this is failing to pass because the CI pipeline is still running XCode 9.2. We would need to update to 10.2 in order to compile this Swift 5 code, and have the CI pipeline pass. @esplinr or @stevengubler do either of you know if someone is able to do this work so we can merge this PR? (I'm not familiar enough with CI pipelines to do the work)


Fix astyle Display Language Dependency & Makefile Colored Output

This PR solves two problems which I found during Cygwin Toolchain usage:

astyle check passes in any case
The shell script which checks the style relies on greping for the keyword "Formatted" in the output of astyle. But the program has localization support and will output in other languages e.g. german. This leads to all style checks always succeeding. I only tested this on Windows in Cygwin but I can imagine the problem also exists on non-english Ubuntu installations.
Solution: is the parameter --formatted of astyle which only produces any output if there was something to fix. This allows for a display language independent condition for an empty string inside the shell script.

Makefile colors do not work e.g. \033[0;34mFormatting with astyle \033[m
Certain terminal combinations like cygwin - mintty - xterm - bash do not escape colors by default.
Solution: Force interpretation of backslash escapes with the parameter -e of echo.

I also switched the colored messages to a lighter blue (94 instead of 34) because in certain terminals default blue is hard to read on black background while on linux both blues were easy to read (see pictures).

I just manually tested on linux and the escape parameter gets put out to the terminal -e Formatting with astyle... I have to look up why.

Fixed:

It seems that on linux only inside a makefile the parameter after the echo
command gets printed if no single quoted sting comes afterwards so I had
to switch to single quotes such that I can use the parameter.

I successfully tested also on linux now.

@haozhang-yuneec Thanks for reporting! Unfortunately I have no access to a mac to test this. I assumed it would behave the same as a linux terminal... (Why does every console have to be different?)


Missing license

Hello, I am interested to use Stellaru in one of my projects, but I do not see a license under which I can use this project. Can you guys include a license so it is easy to know whether it is compatible with my project?
Best regards,
daki4

Hey sorry for the delay with this. Just added a license!


Bad error message when not enough type arguments in method call

Code:
use "collections"

actor Main
  new create(env: Env) =>
    let xs = List[USize]
    xs.map(lambda(n: USize): I64 => n.i64() end)

Output:
Error:
/usr/local/ponyc/packages/collections/list.pony:247:10: not enough type arguments
  fun map[B](f: {(this->A!): B^} box): List[B]^ =>
         ^
    Info:
    /usr/local/ponyc/packages/collections/list.pony:247:10: definition is here
      fun map[B](f: {(this->A!): B^} box): List[B]^ =>
             ^

The error message shows the method definition rather than the location of the error.

Update: the error message is fine when the method has more than one type arg.


Add support for passing a custom router

When using a localization library, in this case next-intl, you have to use their router so that they can handle locales when changing the url.
Example:
import { createSharedPathnamesNavigation } from "next-intl/navigation";

const navigation = createSharedPathnamesNavigation({ locales: PATH_LOCALES });

// localized router
navigation.useRouter

This means there is currently no way to use next-nprogress-bar's router.
Ask
Provide a function that accepts a useRouter hook, and returns a modified version of it that supports nprogress as well.
Example:
import { makeNprogressRouter } from 'next-nprogress-bar';
import { createSharedPathnamesNavigation } from "next-intl/navigation";

const navigation = createSharedPathnamesNavigation({ locales: PATH_LOCALES });

export const useRouter = makeNprogressRouter(navigation.useRouter);

By upgrading to version 2.3.15 you should be able to do :
import { useRouter as useNextIntlRouter } from "next-intl";
const router = useRouter(useNextIntlRouter);

router.push('/about');
router.replace('/?counter=10');
router.back();

Perfect, thank you @Skyleen77 !

@Skyleen77 Hi, it doesnt accept type-safe router. If u use pathnames (localized) on next-intl the createNavigation function returns type-safe useRouter and your useRouter just accepts AppRouterInstance type.


Interface for plugins to trigger hardware detect

Sometimes SDKs can tell us when a new device shows up. While we could probably just add the device then, we might get into threading issues depending on a number of factors. An easy way of handling this would be to be able to tell the server from the plugin, "please hardware detect when you get a chance". Related to #153 in this way.

And this basically is just wiring the API parts, since there is an internal API for triggering hardware detect of course.


[Suggestion] It would be better to keep consistently for the last tooltip of "Start Streaming Logs..." and "Stop Streaming Logs..."

OS: Win 10
Build Version: 20230815.2
Regression: Not a Regression
Repro Steps:

Create one container app -> Right click one container app -> Select "Start Streaming Logs..." -> Select a replicas -> The next tooltip is "Select a container".

Select the container to start the command "Start Streaming Logs...".
Right click the above container app and select "Stop Streaming Logs...".
Check whether the last tooltip for "Stop Streaming Logs..." is consistent with "Start Streaming Logs...".

Actual:
The last tooltip for "Stop Streaming Logs..." is "Select a stream" instead of "Select a container".

Suggestion:
It would be better to keep consistently for the last tooltip of "Start Streaming Logs..." and "Stop Streaming Logs...".

The stream is the correct modifier here, it just so happens to match the container name.


Change lists fetching to APT way or similar

A detailed description of the proposed feature
Replace homebrew source lists to the lists system which will be similar to APT Lists in the Debian (read plain list without Git).
The motivation for the feature
Updating of Homebrew lists is very slow. It takes a few minutes because brew takes full repository from GitHub.
How the feature would be relevant to at least 90% of Homebrew users
The speed of downloading a fresh list will be fast. This will work for all users. So most Homebrew users will see the speed boost.
What alternatives to the feature have been considered
Maybe just fetch only the top commit of the repository through Git is enough to work fast.

This would require rewriting the way we do updates so won't happen, sorry.

It takes a few minutes because brew takes full repository from GitHub.

The first time. Afterwards it's only an incremental diff. What you propose would make the first fetch faster but each additional one would be slower.


ts2kt: "StringLiteral" kind unsupported yet here

ts2kt version: 0.1.3
A fragment from phaser.d.ts (https://github.com/photonstorm/phaser3-docs/blob/master/typescript/phaser.d.ts):
declare type GameConfig = {
    input?: boolean | object;
    "input.keyboard"?: boolean;
    ...
}

results into ts2kt: "StringLiteral" kind unsupported yet here! in the stderr.

It looks like the latest phaser no longer uses that string literal.  It now has:
declare type KeyboardInputConfig = {
    target?: any;
};
declare type InputConfig = {
    keyboard?: boolean | KeyboardInputConfig;
    ...
}
declare type GameConfig = {
    input?: boolean | InputConfig;
    ...
}

which successfully creates this:
external interface KeyboardInputConfig {
    var target: Any? get() = definedExternally; set(value) = definedExternally
}
external interface InputConfig {
    var keyboard: dynamic /* Boolean | KeyboardInputConfig */ get() = definedExternally; set(value) = definedExternally
}
external interface GameConfig {
    var input: dynamic /* Boolean | InputConfig */ get() = definedExternally; set(value) = definedExternally
}

Can this be closed?

Just tried the last versions, got a list of warnings (maybe it is different from the first one I get):
ts2kt version: 0.1.3 Converting phaser.d.ts ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:780:21 to 784:15) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:784:25 to 788:15) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:788:25 to 792:19) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:792:29 to 796:20) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:932:25 to 936:8) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:936:17 to 940:8) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:940:17 to 944:8) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:944:17 to 948:8) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:948:17 to 952:8) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:952:17 to 956:8) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:956:17 to 960:8) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:960:17 to 964:8) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:964:17 to 968:8) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:968:17 to 972:8) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:1635:19 to 1639:14) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:1639:23 to 1643:14) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:1647:20 to 1651:15) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:1651:24 to 1655:15) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:1865:20 to 1869:14) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:1869:24 to 1873:14) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:1873:24 to 1877:18) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:1877:28 to 1881:18) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:1882:26 to 1886:24) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:1886:34 to 1890:23) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:1891:23 to 1895:17) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:1895:27 to 1899:17) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:1899:27 to 1903:21) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:1903:31 to 1907:21) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:1908:23 to 1912:21) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:1912:31 to 1916:20) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:2349:27 to 2353:21) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:2353:31 to 2357:21) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:10487:31 to 10491:27) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:10491:36 to 10495:27) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:10511:37 to 10515:28) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:10515:37 to 10519:28) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:15194:22 to 15194:36) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:15407:22 to 15407:36) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:51984:46 to 51988:30) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:51988:40 to 51992:30) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:51992:40 to 51996:34) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:51996:44 to 52000:35) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:52000:45 to 52004:38) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:52004:48 to 52008:33) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:52008:44 to 52012:34) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:52012:45 to 52016:32) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:52016:43 to 52020:35) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:67717:22 to 67721:16) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:67721:26 to 67725:16) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:67745:29 to 67749:24) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:67749:35 to 67753:26) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:67753:37 to 67757:26) ts2kt: "StringLiteral" kind unsupported yet here! (phaser.d.ts:67757:37 to 67761:27)
This issue is not about converting phaser, it's about supporting string literals if they are allowed by typescript spec. Probaly should be marked as enhancement, not bug.

What should the Kotlin look like?

I'm not familiar with TS enough, but it seems to be like some autogenerated intermediate type.

I believe this is the TypeScript equivalent of Kotlin's backquote ```.
Am I missing something or could it simply be translated as backquoted identifiers?

A StringLiteral is a type in TypeScript which is like an enum class in what
values are allowed,  except that it is still a String.

@epabst The issue at hand is not about string literal types. What ts2kt fails to process here is a StringLiteral token in the position of a property name in a type declaration. ts2kt does not seem to support property names declared as string literals (as opposed to regular identifiers).
This kind of string literals used as property names is a way to define type safe properties that have invalid characters for identifiers, such as the dash -.
For instance, the following declaration:
export interface Headers {
  'content-length'?: string;
}

allows this kind of property access in a type-safe way: headers["content-length"].


long press preview setting

Task/Issue URL: https://app.asana.com/0/414235014887631/1145895736139511
Tech Design URL:
CC:
Description:
Allows user to disable long press previews on links (not images since that's iOS)
Steps to test this PR:

Visit a site with links, preview should be shown for long press
Go to settings and change toggle for "Long-Press Links" to off
Visit a site with links, preview should not be shown for long press
Go to settings and change toggle for "Long-Press Links" to on
Visit a site with links, preview should be shown for long press
Ensure pixels fire for the different states

Internal references:
Software Engineering Expectations
Technical Design Template

Thanks @bwaresiak - have updated with fixes.

thanks!


[Progress] Add progress component

Description
We want to display progress of a task.
Mockups are not done yet.
Radix component exists:

https://www.radix-ui.com/docs/primitives/components/progress

@seedy The need doesn't exist anymore, I guess you can close this issue.


Scope rerun dependency to development environment

As far as I know, we don't need rerun neither in production, where application should be rebooted on deploy, nor in test, where the application is usually booted on demand.

Thanks @waiting-for-dev!


griddata sensible to size of original grid when it should not

I am using scipy.interpolate.griddata in order to interpolate data from an original 2d grid to a target sub-region of that grid but at a higher resolution. In order to speed the computation, instead of using the whole original data I used only the part that contains the target region (with a buffer). To my surprise, I obtain different results on the target grid wether I use the whole original grid or a sub-region of that grid.
The code aims to illustrate this. I am wondering if this is to be expected or if it is a bug in griddata.
Any help/feedback  appreciated.
ps : I posted the same question but with a slightly more complex example on https://stackoverflow.com/questions/46164415/scipy-interpolate-griddata-sensitivity-to-original-grid without success until now.
Reproducing code example:

# modification to expample 1 of
# http://scipy-cookbook.readthedocs.io/items/Matplotlib_Gridding_irregularly_spaced_data.html
# to show problems with griddata

import numpy as np
from scipy.interpolate import griddata
import matplotlib.pyplot as plt

# generate inital fields on 2d grid
x = np.arange(1,11)
y = np.arange(1,11)
x2d, y2d = np.meshgrid(x,y)
z = x2d*2 + y2d*3
z = np.abs(x*np.exp(-(x2d/10.)**2-(y2d/10.)**2)) + 1

# define target grid
# (sub region of initial grid but with finer mesh)
x_target = np.arange(4.5,6.6,0.5)
y_target = np.arange(4.5,6.6,0.5)
x2d_target, y2d_target = np.meshgrid(x_target, y_target)

# define interpolation function
def f_int(data, x, y, xt, yt):
    nj, ni = data.shape
    nij = ni * nj
    zi = data.reshape((nij))
    xi = x.ravel()
    yi = y.ravel()
    xo = xt.ravel()
    yo = yt.ravel()
    zo = griddata((xi, yi), zi, (xo, yo),
                  method = 'nearest', fill_value = np.nan)
    zo = zo.reshape(xt.shape)
    return zo

# interpolate on target grid using the whole initial field
z_int_full = f_int(z, x2d, y2d, x2d_target, y2d_target)

# interpolate on taget grid using a subset of initial field
buffer = 1
x2d_sub = x2d[buffer:-buffer, buffer:-buffer]
y2d_sub = y2d[buffer:-buffer, buffer:-buffer]
z_sub = z[buffer:-buffer, buffer:-buffer]
z_int_sub = f_int(z_sub, x2d_sub, y2d_sub, x2d_target, y2d_target)

fig = plt.figure()
fig.set_size_inches(fig.get_size_inches() * 2)
ax1 = fig.add_subplot(221)
plt.pcolormesh(x2d, y2d, z)
plt.colorbar()
plt.title('initial data')

ax2 = fig.add_subplot(222)
plt.pcolormesh(x2d_target, y2d_target, z_int_full)
plt.colorbar()
plt.title('interpolate from full grid')

ax3 = fig.add_subplot(223)
plt.pcolormesh(x2d_target, y2d_target, z_int_sub)
plt.colorbar()
plt.title('interpolate from sub grid')

ax4 = fig.add_subplot(224)
diff = (z_int_full - z_int_sub)
rel = diff / z_int_full * 100
plt.pcolormesh(x2d_target, y2d_target, rel)
plt.colorbar()
plt.title('relative difference between \n interpolated data [%]')

plt.show()

<<A short code example that reproduces the problem. It should be self-contained, i.e., possible to run as-is via 'python myproblem.py'>>

Error message:
no error message

Scipy/Numpy/Python version information:
sys.version_info(major=2, minor=7, micro=11, releaselevel='final', serial=0)
numpy : '1.10.2'
scipy : '0.16.1'

I do see no indications of a problem in griddata.
The differences are a question of how the triangle-based interpolation
aligns with the target grid. Use a denser x_target, y_target to see it.
Also, if you are interpolating data that's already on a grid, griddata
is the wrong tool (inefficient), should use interpn.

Ah sorry, the code is using method='nearest' so it's voronoi-based. But
I think the explanation is still that the target points happen to be
exactly on the voronoi cell boundaries --- in this case which cell they
belong to is ill-defined so you can get different answers depending of
the precise input points, e.g., change '4.5' to '4.50001'.

Thanks for the feedback.
I understand the sensitivity for the 'nearest option' but the value of the point for the input grid are identical ... Notice that I am also surprised by the results when I use "linear" interpolation. The differences are of the order of 0.1%.
I would expect that if I do a nearest or linear interpolation the closer points would be used to make the interpolation. I do not expect the choice of those points to be sensible to the size of the input grid as long as they do not contain any points close enough to the target points.
The whole problem was revealed when I tried to interpolate temperature data on a regular global lat/lon grid to an irregular (in lat/lon coord) grid (that's why I used griddate). The interpolation  was long so I tried to trim the input global grid to make the code run faster. It changed the results by up to 1 deg C for some points, which does not make sense to me.

For the nearest mode, your problem is that 0.5 is equally close to 0 and 1, and for scattered data it is ill-defined which point is closer.
For linear mode, the Delaunay triangulation can differ for different input points when it is not unique (the case of rectangular grids). If your data is sparse, linear interpolation can of course differ significantly for different triangulations.
If the original data is on a rectangular grid, as you write above, then interpn is the right tool.

At this point, the behavior of the code example above is now explained and it does not appear there is something that needs to be addressed. For the other issues you discuss, it would be necessary to have a second code example illustrating them.

I made a test moving my target grid by 0.01 and it takes care of the differences using the 'nearest' option. I still have differences with the 'linear' option.
I will work on a code to illustrate my initial problem. This said I still am surprised to say the least by this "sensitivity" of the interpolation to the presence/absence of points relatively far from the target points.
Regarding the interpn/griddata choice, does this imply that one should not use griddata with a regular input grid or just that interpn would be faster?

interpn likely is, and it's not triangle-based.
Anyway, as I understand, the issue you have is that your data is so sparse that it's possible to construct several quite different but still equally good interpolations --- and moreover, you the data is on a grid, which is degenerate problem for triangulation. Because you are using a scattered data interpolation method, which has no idea the data is actually on a square grid, it has to construct the locality structure first. The locality structure construction is a global process, but it only depends on coordinates and not on data values. This is expected behavior, so if this is the issue, this issue can be closed.

I will come back with an example of my problem.

I confirm that the problem mentioned is not present when using interpn instead of griddata. I also got rid of the problem by using random numbers in order to render the regular grid irregular.
So if I understand, I should try to use interpn if possible and griddata if it is not. It still bugs me that something that work on an irregular grid is showing faulty sensitivity when used on a regular grid. Preliminary results using matlab did not show this kind of behaviour from its implementation of griddata.

I confirm : tests done with matlab show their implementation of griddata is not sensible to the size of the input grid as scipy.griddata seens to be.

Perhaps Matlab checks whether the data is on a regular grid and in that case uses a more appropriate algorithm? Could do that, but maybe it would be better to just make a note in the docs that the user should pick interpn if they have a regular grid?


Invalid directory

I made example from your page and Im getting error:

Did you npm install? If so it's probably a packager error, try restarting it.

Problem was that npm installed it in wrong folder


Fix:Cards are not displaying in some Sub categories #1652

Fixes Issue
Closes #1652

Changes proposed

Screenshots

Note to reviewers

Hi @pankajdharmik4.😊 Thanks for contributing to LinksHub! :) Please don't make any pull requests until it has been unlocked and reviewed by the maintainers.

Okay, Sure.


Crash during rustfmt

I ran cargo fmt on a crate and this was the response.
thread 'main' panicked at src\tools\rustfmt\src\items.rs:548:10:
called `Option::unwrap()` on a `None` value
stack backtrace:
   0:     0x7ffd0db30f51 - std::backtrace_rs::backtrace::dbghelp64::trace
                               at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/std\src\..\..\backtrace\src\backtrace\dbghelp64.rs:91
   1:     0x7ffd0db30f51 - std::backtrace_rs::backtrace::trace_unsynchronized
                               at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/std\src\..\..\backtrace\src\backtrace\mod.rs:66
   2:     0x7ffd0db30f51 - std::sys::backtrace::_print_fmt
                               at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/std\src\sys\backtrace.rs:66
   3:     0x7ffd0db30f51 - std::sys::backtrace::impl$0::print::impl$0::fmt
                               at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/std\src\sys\backtrace.rs:39
   4:     0x7ffd0db62629 - core::fmt::rt::Argument::fmt
                               at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/core\src\fmt\rt.rs:177
   5:     0x7ffd0db62629 - core::fmt::write
                               at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/core\src\fmt\mod.rs:1178
   6:     0x7ffd0db27117 - std::io::Write::write_fmt<std::sys::pal::windows::stdio::Stderr>
                               at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/std\src\io\mod.rs:1823
   7:     0x7ffd0db34069 - std::panicking::default_hook::closure$1
                               at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/std\src\panicking.rs:266
   8:     0x7ffd0db33bec - std::panicking::default_hook
                               at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/std\src\panicking.rs:293
   9:     0x7ffd0f085e40 - memchr
  10:     0x7ffd0db34a7b - alloc::boxed::impl$50::call
                               at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/alloc\src\boxed.rs:2245
  11:     0x7ffd0db34a7b - std::panicking::rust_panic_with_hook
                               at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/std\src\panicking.rs:805
  12:     0x7ffd0db3484f - std::panicking::begin_panic_handler::closure$0
                               at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/std\src\panicking.rs:664
  13:     0x7ffd0db31a0f - std::sys::backtrace::__rust_end_short_backtrace<std::panicking::begin_panic_handler::closure_env$0,never$>
                               at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/std\src\sys\backtrace.rs:170
  14:     0x7ffd0db34496 - std::panicking::begin_panic_handler
                               at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/std\src\panicking.rs:662
  15:     0x7ffd108f47d4 - core::panicking::panic_fmt
                               at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/core\src\panicking.rs:74
  16:     0x7ffd108f487d - core::panicking::panic
                               at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/core\src\panicking.rs:148
  17:     0x7ffd108f473e - core::option::unwrap_failed
                               at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/core\src\option.rs:2015
  18:     0x7ff737826bea - <unknown>
  19:     0x7ff7378976b0 - <unknown>
  20:     0x7ff7378779ed - <unknown>
  21:     0x7ff73789cfd6 - <unknown>
  22:     0x7ff7376c3b7a - <unknown>
  23:     0x7ff7376f3290 - <unknown>
  24:     0x7ff7376ee98d - <unknown>
  25:     0x7ff7376ea332 - <unknown>
  26:     0x7ff7376dd006 - <unknown>
  27:     0x7ff7376dd6cc - <unknown>
  28:     0x7ffd0db17ff9 - std::rt::lang_start_internal::closure$2
                               at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/std\src\rt.rs:143
  29:     0x7ffd0db17ff9 - std::panicking::try::do_call
                               at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/std\src\panicking.rs:554
  30:     0x7ffd0db17ff9 - std::panicking::try
                               at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/std\src\panicking.rs:518
  31:     0x7ffd0db17ff9 - std::panic::catch_unwind
                               at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/std\src\panic.rs:345
  32:     0x7ffd0db17ff9 - std::rt::lang_start_internal
                               at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/std\src\rt.rs:143
  33:     0x7ff7376f46cc - <unknown>
  34:     0x7ff737a0de50 - <unknown>
  35:     0x7ffdf5b6257d - BaseThreadInitThunk
  36:     0x7ffdf778af08 - RtlUserThreadStart

error: the compiler unexpectedly panicked. this is a bug.

note: we would appreciate a bug report: https://github.com/rust-lang/rustfmt/issues/new?labels=bug

note: rustc 1.82.0 (f6e511eec 2024-10-15) running on x86_64-pc-windows-msvc

query stack during panic:
end of query stack

I was working on the following codebase [github.com/douweschulte/mzdata] and made a snapshot commit of the state when the crash happened. If I can help by providing more information let me know.

@douweschulte Thanks for reaching out and reporting the crash. It would be really helpful to provide a minimal code snippet that reproduces the crash, otherwise it's going to be a lot harder to get to the bottom of this issue.

Based off of the info in the backtrace I suspect this is related to #5738, possibly a duplicate.


MAISTRA-1940 Wait for components when updating control planes

We're already waiting for individual components to be ready in order when deploying the first time, but when updating a control plane we just apply everything instantly. This PR uses the same waiting mechanism when updating an existing control plane.
Note the ugly use of hacks.ReduceLikelihoodOfRepeatedReconciliation- but I couldn't find another way to make sure the cache is updated before we calculate readiness. This is because we're using unstructured to apply the resources, so the cache has no chance of updating. @luksa I'd be especially interested in our opinion here, maybe you know of a better solution.

/test istio-operator_gen-check

/retest

@rcernich Any clue on this failure? It's failing on TestExternalJaegerV1_1

@dgn, sorry, i tried to add patch to fix the issue, but i think i broke the history.  i think a rebase and force push should fix the issue.

Closed in favor of https://github.com/maistra/istio-operator/pull/641


Exclusion of weekdays causes syntax error

Hello, I am having some issues in using the plugin for gantt with days exclusion.
Example:
gantt
dateFormat  YYYY-MM-DD
title Topic
excludes weekdays saturday,sunday

section Timeline
Task          :crit, spawn, 2020-01-30, 1d

it results in the following syntax error:
Parse error on line 4:
...days saturday,sundaysection TimelineC
-----------------------^
Expecting 'taskData', got 'NL'

Am I doing something wrong or maybe there's some parsing issue here?
Thanks in advance!

I am having the same problem.


Fix deploy with network filesystem

Also make some prints only happen in verbose mode.

Updated based on the comments.

Thanks!


Fix SW-23403: remove business logic from order model

1. Why is this change necessary?
https://issues.shopware.com/issues/SW-23403
2. What does this change do, exactly?
Move the business logic from order model to service & doctrine subscriber
3. Describe each step to reproduce the issue or behaviour.
4. Please link to the relevant issues (if any).
https://issues.shopware.com/issues/SW-23403
5. Which documentation changes (if any) need to be made because of this PR?
6. Checklist

[X] I have written tests and verified that they fail without my change
[X] I have squashed any insignificant commits
[X] This change has comments for package types, values, functions, and non-obvious lines of code
[X] I have read the contribution requirements and fulfil them.

Squash the commits

Still one commit to go. Would be highly appreciated if you could get rid of the second "merge" commit as well. 👍

That merge was accidental, the change got reverted by our internal repository, force-pushing to github. Just in case you're wondering :)

I have created a new pull request https://github.com/shopware/shopware/pull/2014 cause there are some issues in the source repo.


Not working, even when enabled

Im having a weird issue. I have installed the extension on my main 1111 ambient, the extension didnt work at all. I assumed tha was my installation so i installed on a brand new 1111 ambient, only with the Latent Couple extension installed. Same results. Somehow, looks the extension its all set and working, but actually its not doing anything with the image.

No erros on the CMD prompt either.

The info of the image:
flower garden background
AND beautiful cute woman, long blond hair
AND a man, short brown hair
Negative prompt: (deformed, distorted, disfigured:1.3), poorly drawn, bad anatomy, wrong anatomy, extra limb, missing limb, floating limbs, (mutated hands and fingers:1.4), disconnected limbs, mutation, mutated, ugly, disgusting, blurry, amputation, watermark, text, disabled body, paintings, sketches, (worst quality:2), (low quality:2), (normal quality:2), lowres, normal quality, ((monochrome)), ((grayscale)), skin spots, acnes, skin blemishes, age spot, glans,wrong amount of fingers,
Steps: 20, Sampler: Euler a, CFG scale: 7, Seed:<PHONE_NUMBER>, Size: 512x512, Model hash: 1dceefec07, Model: dreamshaper_331BakedVae, Latent Couple: "divisions=1:1,1:2,1:2 positions=0:0,0:0,0:1 weights=0.2,0.8,0.8 end at step=20"

it still didn't work, or I'm the luckiest person on the planet. I tested with about 15 seeds. When i put higher resolutions, the results are a little better, but not even close to the prompt

Prompt:
(8k, RAW photo, best quality, masterpiece:1.2), (realistic, photo-realistic:1.4), best quality, ultra high res, (photorealistic:1.4), city background, 2girls
AND  (8k, RAW photo, best quality, masterpiece:1.2), (realistic, photo-realistic:1.4), best quality, ultra high res, (photorealistic:1.4), 2girls ,  (smiling at camera:1),  lora:tifa:0.5,  lora:dosmix:0.6,  lora:koreanDollLikeness_v10:0.2 ,lora:japaneseDollLikeness_v10:0.3,   (black jacket), slim body, abs, slim legs, ((black jeans)), normal hand, large breast, ((brown hair)),  ((white shirt))
AND (8k, RAW photo, best quality, masterpiece:1.2), (realistic, photo-realistic:1.4), best quality, ultra high res, (photorealistic:1.4), 2 girls ,  (smiling at camera:1), lora:aerith:1,  lora:dosmix2:0.6 ,lora:koreanDollLikeness2_v10:0.2, lora:japaneseDollLikeness2_v10:0.3, normal hand,  ((blue eyes)), (((flat chest))), (brown hair),  ((red long dress))

i have the same issue. Can't access the mask area in the Extension in A1111. Under Latent Couple its the same view as stated above in https://github.com/opparco/stable-diffusion-webui-two-shot/issues/25#issue-1609925811

more than 2 girls are bad.

You need to use correct prompt. ((ultra-detailed)), ((illustration)), (a man and a girl) AND ((ultra-detailed)), ((illustration)), (a man and a girl) a girl with (black hair) AND ((ultra-detailed)), ((illustration)), (a man and a girl) a man with (white hair)

This doesn't work. There are two subjects, but they don't correspond with the divisions at all.

I am also having the same error. If you can find a solution, I would love to know!
error: patch failed: modules/script_callbacks.py:68
error: modules/script_callbacks.py: patch does not apply
error: patch failed: modules/sd_samplers_kdiffusion.py:8
error: modules/sd_samplers_kdiffusion.py: patch does not apply

I'm getting the same thing. It used to work, and sometimes it still will, but usually it merges my two characters and puts both of them (now one person) on the left or right side. If I disable the extension the results look completely different, so it's doing something, but it doesn't work anymore.

I don't know if something changed, but I have updated everything and reinstalled the extension and latent coupling is working for me now. If you guys get it working, here's a helpful site to set up your parameters: https://badnoise.net/latentcoupleregionmapper/

Ok, so I was having this exact issue and through painful elimination realised it was due to not giving the canvas enough space.
a city in background, golden hour, morning AND
a young nordic woman wearing a long coat AND
an old jamaican man with a walking stick

512x512

1024x512

Hopefully this helps someone! 🏞😁

Thanks for the nice comment.
I made a mistake in my setup and it worked fine.
Thank you so much.
(I curse myself for being so stupid)

additionally, I noticed if you use a ControlNet, you can reliably get it to work on square (512x512) aspect ratios fwiw.

additionally, I noticed if you use a ControlNet, you can reliably get it to work on square (512x512) aspect ratios fwiw.

Can you provide more details about how you would need to go for this to happen?