KYLIN-4295 Instances displayed on Query Node are inconsistent with JobNode

Query Node can't get allParticipants because query node no need to run job scheduler, so the jobClient is null.
Job Node:

Query Node:

We can add instance of the mode  equals ‘job’ or ‘all’ to job node list in query server, but query server can not find which job node is Leader. In order to avoid instance page display a leader as a follower by mistake, just display the Leader of job node as Job Node (Leader), the others display as Job Node.
Job Node:

Query Node:

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@8623cae). Click here to learn what that means.
The diff coverage is 0%.

@@            Coverage Diff            @@
##             master    #1014   +/-   ##
=========================================
  Coverage          ?   25.13%
  Complexity        ?     6178
=========================================
  Files             ?     1431
  Lines             ?    87168
  Branches          ?    12191
=========================================
  Hits              ?    21913
  Misses            ?    63110
  Partials          ?     2145

Impacted Files
Coverage Δ
Complexity Δ

...st/controller/ServiceDiscoveryStateController.java
0% <0%> (ø)
0 <0> (?)

Continue to review full report at Codecov.

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


Add new runtime setting for JSON string used with mapping

Now user could use field com.mendix.integration.MaxJsonReadingLength in studio pro to provide the required value which would override the default 20 million (20000000) max length. If this field is not used then 20 million (20000000) which is a default would be used as max length

@quinntracy : To be released for Mendix 10.9.0


Need a way to differentiate between loaded data

There might be circumstances where you would like data to be loaded in different environments. For example you might want to load some example records in the dev environment, but not in the test or prod environments (clean slate for both deployments).
Also, there might be some data you would like to load in every environment, for example some business logic mapping or caption tables etc.
maybe adding a 3 bit identifier to the file name of the csv data might solve this issue. For example
data.011.csv, where the 3 binary tuple stands for "load into (prod, dev, test)"

The schema.yaml data section has a modes list that does this


rangeslider.scss missing error while building

I'm doing npm update everytime. Recently i'm getting this error when building the project
ERROR in ./~/react-rangeslider/lib/Rangeslider.js
Module not found: Error: Cannot resolve 'file' or 'directory' ./rangeslider.less in /project_path/node_modules/react-rangeslider/lib
resolve file
  /project_path/node_modules/react-rangeslider/lib/rangeslider.less doesn't exist
  /project_path/node_modules/react-rangeslider/lib/rangeslider.less.json doesn't exist
  /project_path/node_modules/react-rangeslider/lib/rangeslider.less.js doesn't exist
  /project_path/node_modules/react-rangeslider/lib/rangeslider.less.jsx doesn't exist
resolve directory
  /project_path/node_modules/react-rangeslider/lib/rangeslider.less doesn't exist (directory default file)
  /project_path/node_modules/react-rangeslider/lib/rangeslider.less/package.json doesn't exist (directory description file)
[/project_path/node_modules/react-rangeslider/lib/rangeslider.less]
[/project_path/node_modules/react-rangeslider/lib/rangeslider.less.json]
[/project_path/node_modules/react-rangeslider/lib/rangeslider.less.js]
[/project_path/node_modules/react-rangeslider/lib/rangeslider.less.jsx]
 @ ./~/react-rangeslider/lib/Rangeslider.js 19:0-29

How do i resolve it. in my package.json the version "react-rangeslider": "^1.0.9"

Same problem here

Same problem here

+1 this is occurring to us also. We're not able to start our server because of this.

same here

Yeah guys, thats a breaking change. Use the the less file from lib directory in development. The less file has to be imported for the styles to be applied as of 2.0.1, like the one in the code snippet below.
import React, {Component} from 'react';
import Slider from 'react-rangeslider';
import 'react-rangeslider/lib/index.css';

class Volume extends Component {
  ...
}

Also 9e7ce831752df717c61bf5d3eff5589bcc4522cd fixes the missing less file issue.


[zh] Resync install-kubectl-windows.md

Resync page content/zh-cn/docs/tasks/tools/install-kubectl-windows.md.
Refer to #39298

Thanks.
/lgtm
/approve


Planner improvements

A number of improvements and fixes to the planners:
iLQG

initial copy of nominal policy to prevent threading conflicts with policy scratch space
fix backward pass initialization (ie, remove incorrect trajectory copy)
cost-to-go regularization option
regularization type GUI menu option
default regularization type setting changed to control

Gradient

initial copy of nominal policy to prevent threading conflicts/locks
remove Trajectory from policy

Sampling

initial copy of nominal policy to prevent threading conflicts/locks
remove Uniform sampling
simplify noise sampling function
more descriptive naming for functions

Fix for CostDerivatives::Compute

time shift scratch spaces to prevent threading conflicts

Rename infotext Cost -> Objective
Modification to humanoid stand task to achieve more stable behaviour: change balance norm 1 -> 6
Include norm_test

@yuvaltassa  Addressed your comments above.

@nimrod-gileadi the norm_test was not running so I included it in the tests. However, this is causing the Windows build to fail. Do I need to do additional things to add tests?


Support Video in img

As described in this article: https://cloudinary.com/blog/evolution_of_img_gif_without_the_gif

Duplicate of #3929. The link is missing there though.


Tuning support

Description
Previous versions of the sampler's Swift wrapper offered a setNoteFrequency() method  that allowed tuning individual notes. Current versions lack this method thus limiting Swift apps to 12-ET.
Proposed Solution
Bring back setNoteFrequency(). Allow it to work on the fly (ie., without reloading samples).
Describe Alternatives You've Considered
Write a custom wrapper
Additional Context
No response

I stopped development on this repo a long time ago. Anyone who wishes is welcome to fork it for their own use, but I cannot spare any time to assist.


Code-gen should add markers for nested shapes

Is your feature request related to a problem?
Yes, in the EventBridge controller we use custom_fields to embed model shapes into a CR:
Rule:
      Targets:
        custom_field:
          list_of: Target

Currently, neither comments (on the Targets field in a Rule) nor kube markers are added to required field to this shape in the resulting Kubernetes API definitions.
Describe the solution you'd like
Treat nested/custom fields like top level fields when it comes to adding comments, kube markers, setting immutability, etc. in code-gen.
Describe alternatives you've considered
n/a

@embano1 I don't recommend using custom_field except as a last resort. If you want the kube required markers for a field, use the type configuration option and the is_required configuration option.
For example, here's how I added a custom Policies field in the IAM controller:
      Policies:
        type: "[]*string"
        references:
          resource: Policy
          path: Status.ACKResourceMetadata.ARN

that particular field isn't required, but I could add:
      Policies:
        is_required: true
        type: "[]*string"
        references:
          resource: Policy
          path: Status.ACKResourceMetadata.ARN

to make it so.
Still doesn't have documentation, though, which is a definite known issue!

Thx, the reason we had to go with custom_field is that we wanted to include a larger shape into a specific resource, which would otherwise have been its own CR. See this generated code for details: https://github.com/embano1/eventbridge-controller/blob/ce041375b73dc09fe0d898125f341cf30b51ad09/apis/v1alpha1/rule.go#L53
The issue is also not just with custom_field, but structs within a defined resource. For example, the generated code for Endpoint is this spec:
If you look at RoutingConfig, it's field FailoverConfig is marked as required by the API, but the generated code does not add a marker: https://github.com/embano1/eventbridge-controller/blob/ce041375b73dc09fe0d898125f341cf30b51ad09/apis/v1alpha1/types.go#L362

Related: https://github.com/aws-controllers-k8s/code-generator/pull/393

Thx @jaypipes for already looking into it. IIUC, the related PR addresses the required marker issue here?

Resolved, please re-open this if https://github.com/aws-controllers-k8s/code-generator/pull/393 didn't resolve the issue

@jljaco can't reopen (or is there a Prow command I need to use?).
The issue is not fixed for me. The generated code for the embedded custom_field targets (PR example) does not contain any required markers as per the object model.

Yeah, my patch only fixed for the non-custom nested fields... I will work on a fix for the custom fields.

Yeah, my patch only fixed for the non-custom nested fields... I will work on a fix for the custom fields.

Thx, will try this one once I get EndPoint running which saw this issue with non-custom nested fields.


update the ratelimit service image

Please provide a description of this PR:
update the image used by the ratelimit service
using envoyproxy/ratelimit:6f5de117 image on the gateway will not work.
ref: https://github.com/istio/istio/issues/30900#issuecomment-786754760
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

[ ] Configuration Infrastructure
[x] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Please check any characteristics that apply to this pull request.

[ ] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

Hi @xichengliudui. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/ok-to-test

@xichengliudui: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
783913bec20beb018dd4f603faa1dd6233cf2c86
link
true
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@xichengliudui: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
783913bec20beb018dd4f603faa1dd6233cf2c86
link
true
/test release-notes_istio

integ-security-k8s-tests_istio
783913bec20beb018dd4f603faa1dd6233cf2c86
link
true
/test integ-security-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@xichengliudui: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
783913bec20beb018dd4f603faa1dd6233cf2c86
link
true
/test release-notes_istio

integ-security-k8s-tests_istio
783913bec20beb018dd4f603faa1dd6233cf2c86
link
true
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
783913bec20beb018dd4f603faa1dd6233cf2c86
link
true
/test integ-security-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@xichengliudui: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-k8s-tests_istio
783913bec20beb018dd4f603faa1dd6233cf2c86
link
true
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
783913bec20beb018dd4f603faa1dd6233cf2c86
link
true
/test integ-security-multicluster-tests_istio

release-notes_istio
783913bec20beb018dd4f603faa1dd6233cf2c86
link
true
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@xichengliudui: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster-tests_istio
783913bec20beb018dd4f603faa1dd6233cf2c86
link
true
/test integ-security-multicluster-tests_istio

release-notes_istio
783913bec20beb018dd4f603faa1dd6233cf2c86
link
true
/test release-notes_istio

integ-security-k8s-tests_istio
783913bec20beb018dd4f603faa1dd6233cf2c86
link
true
/test integ-security-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@xichengliudui: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
783913bec20beb018dd4f603faa1dd6233cf2c86
link
true
/test release-notes_istio

integ-security-k8s-tests_istio
783913bec20beb018dd4f603faa1dd6233cf2c86
link
true
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
783913bec20beb018dd4f603faa1dd6233cf2c86
link
true
/test integ-security-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio/wg-networking-maintainers Any issues with updating the image tag? Backwards compatibility? Do we need to have a release note?


ci: add tooling and other open-sauced cool stuff

What type of PR is this? (check all applicable)

[x] ♻ Refactor
[x] ✨ Feature
[ ] 🐛 Bug Fix
[ ] 👷 Optimization
[x] 📝 Documentation Update
[x] 🔖 Release
[ ] 🚩 Other

Description

This PR adds 🔥 🍕 features:

base .editor configuration
astro compatible eslint configuration
open-sauced/open-sauced dependabot configuration
open-sauced/open-sauced codeql configuration
open-sauced/open-sauced check-engines npm scripts
open-sauced/open-sauced push npm scripts
open-sauced/open-sauced dot npm configuration defaults
open-sauced/open-sauced pull request development workflow
open-sauced/open-sauced main release workflow
corrects compliance flow syntax
added docker configuration
added MIT license file
updated readme documentation
updated astro configuration
added npm shrinkwrap configuration
updated npm package defaults for release

Related Tickets & Documents

closes #11
closes #14
Mobile & Desktop Screenshots/Recordings

Added tests?

[ ] 👍 yes
[x] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

Added to documentation?

[x] 📜 readme
[ ] 📜 contributing.md
[ ] 📓 docs
[ ] 📕 storybook
[ ] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?

give @open-sauced/maintainers settings and push access
add proper netlify badge

[optional] What gif best describes this PR or how it makes you feel?

@bdougie the netlify configuration needs to apply build instead of dist folder, just like open-sauced/open-sauced


Add localization for attributed strings

Please add localization for attribute strings i.e UILabel.

@Petro-Lomaka tell me more about that. examples or what do you would like.

Localize framework added extension to UILabel.
Extension do this:
self.text = self.localizeTag?.localize()
even if you add attributed text to UILabel it will be replaced with non-attributed text.

@Petro-Lomaka ok 👍, I will work in that feature,  thanks

@andresilvagomez any updates on this?

@LinusGeffarth right now no 👎 will work in this one.

@andresilvagomez any updates on attributed strings localization?


Gate systemd's preset-all so it runs only on first install

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[x] Any updated packages successfully build (or no packages were changed)
[x] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[x] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[x] Ready to merge

Summary

When upgrading systemd, sometimes user customized services would be enabled/disabled unexpectedly. Our systemd package was calling systemctl preset-all during upgrade, which would clear any user customizations and reset all services back to their default enabled/disabled state.
We should only run this during the first install of systemd to guard against transaction ordering issues (say a transaction requires both a service and systemd, but rpm may occasionally choose a poor ordering even if the service has Requires(post): systemd if the transactions are complex). Once systemd is installed all future attempts to configure services during install should function normally.
Change Log

Gate systemd's %post: systemctl preset-all behind a conditional that only runs on first install.

Does this affect the toolchain?

YES
Test Methodology

Local build, running full pipeline to validate toolchain changes

re: requested review, this LGTM, I approve
I don't appear to be on the mariner devs github team so I don't think I am able to give official review yet ;-)


Add Data Structures - Aditya CSE

Creative Commons by/sa 3.0 (license on last page)
check_urls=http://adityacse.weebly.com/uploads/2/4/0/7/24078687/data-structures.pdf
What does this PR do?
Add resource
For resources
Description
Data Structures Book
Why is this valuable (or not)?
503 pages of details on programming data structures, including charts and source code.
How do we know it's really free?
CC BY/SA 3.0 license details on last page (page numbered: 496; actual page: 503)
For book lists, is it a book? For course lists, is it a course? etc.
Book
Checklist:

[x] Read our contributing guidelines
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction)

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

TIP :rocket:: Thanks for taking your time on fill Pull Request fields in your first contribution :heart:
It's always a good practice which it use to increase the mantainers productivity.

Scraped from: https://adityacse.weebly.com/news

Thanks, and welcome to free-programming-books!


Feature: add support for unit file override

As specified by the systemd.unit manual it is possible to override vendor settings by creating a unit.d directory containing one or multiple foobar.conf config files that override only a specific setting.
I would be glad to implement this feature but I would like your opinion on how to do it.
I think I would update systemd::service defined type in order to:

add a $unit_d_override boolean parameter (that defaults to false)
add a $unit_d_purge boolean param (defaults to true)
modify service.erb template to make every section/directive optional (i.e. WantedBy, User...) so that we can drop a file containing only relevant section(s) and directive(s).

When $unit_d_override = true, systemd::service would automatically create the /etc/systemd/system/example.service.d/50-override.conf file with provided directives in it.
If $unit_d_purge = true then the directory would have purge => true.
What do you think about that ?
Regards,

Any news about that one ?

I'm not a maintainer or allowed-contributor to this code base, but my opinion, for what it's worth is:
You should create a new defined type for overrides. This way you can call one type with the original unit file and another type with the override. This becomes handy when you have two modules that need to update the same service.

@cedef - Are you talking about drop-in files ?

@jduemes : I'm currently on holidays. Should do it by mid-september.
If you would like to start the job, please do :)

a PR adding the feature has appeared: https://github.com/NTTCom-MS/eyp-systemd/issues/49


Roll Flutter from 2b2cda15293d to aa2f567babf9 (34 revisions)

Roll Flutter from 2b2cda15293d to aa2f567babf9 (34 revisions)
https://github.com/flutter/flutter/compare/2b2cda15293d...aa2f567babf9
2022-05-15<EMAIL_ADDRESS>Roll Flutter Engine from decfc94a44ef to fdf2ddc04cbe (1 revision) (flutter/flutter#103841)
2022-05-15<EMAIL_ADDRESS>Roll Flutter Engine from d09cf345042f to decfc94a44ef (2 revisions) (flutter/flutter#103837)
2022-05-15<EMAIL_ADDRESS>[macOS] Update template icons to Big Sur style (flutter/flutter#103739)
2022-05-14<EMAIL_ADDRESS>Roll dependendencies (flutter/flutter#103771)
2022-05-14<EMAIL_ADDRESS>Roll Flutter Engine from 260e5e286c05 to d09cf345042f (2 revisions) (flutter/flutter#103828)
2022-05-14<EMAIL_ADDRESS>[flutter_tools] fix missing cmake (flutter/flutter#103761)
2022-05-14<EMAIL_ADDRESS>[flutter_tools] fix test asset loading (flutter/flutter#103667)
2022-05-14<EMAIL_ADDRESS>Roll Flutter Engine from b2f31f56f8b0 to 260e5e286c05 (1 revision) (flutter/flutter#103812)
2022-05-14<EMAIL_ADDRESS>[ci] Add pointer to template image assets wiki (flutter/flutter#103787)
2022-05-14<EMAIL_ADDRESS>[tool] Fix BuildInfo.packagesPath doc comment (flutter/flutter#103785)
2022-05-14<EMAIL_ADDRESS>b2f31f56f Reland: Roll clang and buildroot (flutter/engine#33339) (flutter/flutter#103809)
2022-05-14<EMAIL_ADDRESS>a71d3867a Roll Dart SDK from c23ec46618c1 to e7590a9bb416 (1 revision) (flutter/engine#33342) (flutter/flutter#103806)
2022-05-14<EMAIL_ADDRESS>Roll Flutter Engine from 00b9e2bfb06a to 4c8ba5eb1c33 (1 revision) (flutter/flutter#103801)
2022-05-14<EMAIL_ADDRESS>Roll Flutter Engine from b4788d2aaa62 to 00b9e2bfb06a (1 revision) (flutter/flutter#103792)
2022-05-14<EMAIL_ADDRESS>Roll Flutter Engine from 7697febb9ead to b4788d2aaa62 (1 revision) (flutter/flutter#103784)
2022-05-14<EMAIL_ADDRESS>Roll Flutter Engine from 996ca3a18669 to 7697febb9ead (2 revisions) (flutter/flutter#103781)
2022-05-14<EMAIL_ADDRESS>Roll Flutter Engine from c4a1a72da5dd to 996ca3a18669 (1 revision) (flutter/flutter#103778)
2022-05-14<EMAIL_ADDRESS>Fix deprecation doc comment (flutter/flutter#103776)
2022-05-14<EMAIL_ADDRESS>Roll Flutter Engine from 4e7024db361c to c4a1a72da5dd (4 revisions) (flutter/flutter#103770)
2022-05-14<EMAIL_ADDRESS>[flutter_tools] ensure linux doctor validator finishes when pkg-config is not installed (flutter/flutter#103755)
2022-05-14<EMAIL_ADDRESS>Make _RenderCustomClip respect clipBehavior (flutter/flutter#103748)
2022-05-14<EMAIL_ADDRESS>Roll Flutter Engine from bd906a8fc61b to 4e7024db361c (2 revisions) (flutter/flutter#103764)
2022-05-13<EMAIL_ADDRESS>Roll Flutter Engine from 10e0e15347d3 to bd906a8fc61b (1 revision) (flutter/flutter#103756)
2022-05-13<EMAIL_ADDRESS>Bump snippets tool to 0.3.0 (flutter/flutter#103751)
2022-05-13<EMAIL_ADDRESS>Roll Flutter Engine from 58193a3b6ef1 to 10e0e15347d3 (5 revisions) (flutter/flutter#103742)
2022-05-13<EMAIL_ADDRESS>[macOS] Adds macOS project files to layers example (flutter/flutter#102539)
2022-05-13<EMAIL_ADDRESS>[flutter_tools] remove assertion for deprecation .packages (flutter/flutter#103729)
2022-05-13<EMAIL_ADDRESS>Fix avoid_redundant_argument_values analyzer warnings enabled in the latest Dart SDK (flutter/flutter#103734)
2022-05-13<EMAIL_ADDRESS>Revert "Delete flaky flutter_gallery XCUITest (#103666)" (flutter/flutter#103726)
2022-05-13<EMAIL_ADDRESS>Delete flaky flutter_gallery XCUITest (flutter/flutter#103666)
2022-05-13<EMAIL_ADDRESS>Enforce minimum plugin version iOS 11 (flutter/flutter#103545)
2022-05-13<EMAIL_ADDRESS>[flutter_tools] migrate some integration tests to null safety (flutter/flutter#103560)
2022-05-13<EMAIL_ADDRESS>Roll Flutter Engine from 53c57d5e4620 to 58193a3b6ef1 (1 revision) (flutter/flutter#103711)
2022-05-13<EMAIL_ADDRESS>Roll Plugins from 4479e26172b9 to 053c4bdb3812 (9 revisions) (flutter/flutter#103708)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-plugins
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Plugins: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
...

Commit queue failed; closing this roll.


Can't compile

I have the following compilation error:
 error[E0599]: no method named `max_1_min_k` found for reference `&[T]` in the current scope
   --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/medians-2.1.0/src/lib.rs:225:14
    |
225 |         self.max_1_min_k(self.len() / 2 + 1)
    |              ^^^^^^^^^^^ method not found in `&[T]`

error[E0599]: no method named `max_2_min_k` found for reference `&[T]` in the current scope
   --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/medians-2.1.0/src/lib.rs:233:14
    |
233 |         self.max_2_min_k(self.len() / 2 + 1)
    |              ^^^^^^^^^^^ method not found in `&[T]`

For more information about this error, try `rustc --explain E0599`.
error: could not compile `medians` due to 2 previous errors
warning: build failed, waiting for other jobs to finish...
Error: Process completed with exit code 101.

I use rustc 1.69.0.

It looks like it is picking up an old version of indexvec crate dependency.
Try cargo update?

Right, it was the issue. Updated indxvec from 1.4.10 to 1.4.13.

You are welcome. I hope you find the fast medians useful.

@liborty just had the same issue with library again. The solution was to update indxvec from 1.4.13 to 1.4.15.
I see that you are the author of indexvec. Please, don't break semver. If you making a breaking change in the library, it should be a minor version bump instead of a patch version bump.
And in your Cargo.toml in medians you set minimal version of indexvec to 1.4:
https://github.com/liborty/medians/blob/838e83f88dd51f85dc8e4acc66e474b1a9888059/Cargo.toml#L25
But it's not true, the minimal version is 1.4.15 since you break semver in it.
My recommendation would to bump indexvec to 1.5.0, set minimal version in medians to 1.5 and next time bump minor version (e.g. to 1.6) after next breaking change. This is how rust libraries usually do.


Add --not-album ALBUM to find photos not in a given album

This will simplify excluding specific albums from the export.
Alternative is to use --query-eval " 'ALBUM' not in photo.albums"

What's the full export command line you're using?

I'll just post my entire script for clarity:
#!/bin/bash

OSXPHOTOS="/Users/peter/.local/bin/osxphotos"
DIRECTORY="/Volumes/Photos/Photos Export/"
LOG="/Users/peter/Library/Mobile Documents/com~apple~CloudDocs/Tech/Scripts/osxphotos/osxphotos.log"

# Clear log
echo "" > "$LOG"

# Add date to log
date >> "$LOG"

# Run osxphotos
"$OSXPHOTOS" export --query-eval " 'All-Photos' not in photo.albums" --download-missing --not-syndicated --not-shared --skip-original-if-edited --update --cleanup "$DIRECTORY" --directory "{folder_album}" --no-progress >> "$LOG"

@petebocken I have not been able to reproduce this. I create an album "All-Photos" and added some photos then ran the same command you are using. The export worked as expected -- all albums were created with exception of "All-Photos" and all photos were exported with exception of those in "All-Photos".
I will keep tinkering but I can't think of a reason at the moment for the issue you're seeing.  What version of macOS are you using? If on macOS 15, there's a bug discovered today (#1687) that affects some edited photos but I don't think it would affect your use case.

The All-Photos album does not get exported, but now my export consists of just a few of my total albums, folders and photos.

Hello. Maybe adumb question! Would it be related with pics belonging to multiple Albums?

@petebocken Are the pics that are actually being exported not in the All-Photos album at all?
@petebocken Are your non exported pics in other Albums while part of All-Photos album also?

I think @oPromessa may be on to something. @petebocken if your "All-Photos" album really contains all (or most) of the photos in the library then the use of --query-eval excludes these photos from the export set (meaning the photos in the All-Photos album will not be exported at all) which sounds like what you're seeing. From your question, I assumed that was the intended behavior: "do not export any photo that is in the 'All-Photos' album" which is what the --query-eval does.
However, if what you really meant was "All my photos are in 'All-Photos'. Some photos are also in one or more other albums. I want to export those albums and all the photos not in them but not the 'All-Photos' album" then that's a different problem and I don't have a full solution.
One means to do this is to use a --directory template.  Instead of {folder_album} as you're currently using (which evaluates to all albums a photo is in), you could exclude the All-Photos album from the list generated by the template:
--directory "{folder_album|remove(All-Photos),}"
This removes 'All-Photos' from the list of folders/albums.  However, in the case where you have photos that were only in All-Photos, those photos now will still get exported, either in the root folder of the export or in the default folder (_ unless you have specified something different). For example:
--directory "{folder_album|remove(All-Photos),}" adds a comma with nothing following it which says "don't use a default" and that means those photos won't get a folder name assigned and will be dumped in the root of the export folder.
--directory "{folder_album|remove(All-Photos)}" excludes the default value and preceeding comman and thus the default will be _ which is the OSXPhotos template default when no value is specified.
--directory "{folder_album|remove(All-Photos),All-Photos}" uses All-Photos as the default and this is thus the same as using {folder_album}
However, we can combine this with a new --query-eval to filter out photos that are only in All-Photos:
--query-eval "len(photo.albums) > 1 or 'All-Photos' not in photo.albums" --directory "{folder_album|remove(All-Photos)}"
This excludes (via --query-eval) any photo that is only in All-Photos. Photos in another album or photos not in any album will be included. The --directory template excludes the All-Photos folder for any photo that is in All-Photos but also in one or more other albums.  You'll need to decide how to handle the photos not in any album using the template default as described above. Currently, they'll go to the default folder _.

Ohhhh, I feel like such a dork. @oPromessa got it exactly. The photos that are not getting excluded and are getting exported are the ones that are not in the "All-Photos" album. So it's working exactly as expected. I just didn't know that is how it worked apparently!
Some context as to why do I have an "All-Photos" album with all my photos:
I use the iOS Featured Photos Widget on my home screen and I was sick of it surfacing the same photos over and over again. I was also sick of Apple's decision of what photos are "good enough" to show me.
So I thought what if I used the Album Photos Widget. Throw all my photos in an album and point the widget to it. Turns out it works great! I see more different photos!
I can try messing with these query-eval options, but I do have enough disk space on the drive I export to, so I could just leave my script alone and not try to exclude this and just essentially have duplicates of all photos (since I already have all photos organized into albums ---  I maintain all photos in albums, no photo is not in an album).
So sorry for making you run in circles @RhetTbull! Guess we solved my issue! 😳

No worries! If all photos are in more than one album and you want to exclude the duplicates from 'All-Photos' then dropping the query eval and using this should work: --directory "{folder_album|remove(All-Photos)}"

No worries! If all photos are in more than one album and you want to exclude the duplicates from 'All-Photos' then dropping the query eval and using this should work: --directory "{folder_album|remove(All-Photos)}"

Works perfectly, thanks so much!!


Add Nong Song

Song Name
CaramellDansen
Artist Name
Caramella Girls
Source
Youtube
Youtube Link
https://youtu.be/6-8E4Nirh9s?si=U0Tfyb224AcJrFcW
Direct File Link
No response
Song ID
44
Extra
No response

accept

De: auto-nong[bot] @.>
Enviado: sábado, 15 de junio de 2024 21:30
Para: FlafyDev/auto-nong-indexes @.>
Cc: Benjx618 @.>; Author @.>
Asunto: Re: [FlafyDev/auto-nong-indexes] Add Nong Song (Issue #237)
Thanks for contributing!
Someone will soon review your request.
Here is the JSON result for the reviewer:
{
"name": "CaramellDansen",
"artist": "Caramella Girls",
"source": "youtube",
"yt-id": "6-8E4Nirh9s",
"songs": [
44
]
}
To accept the request, a reviewer needs to write "accept".
—
Reply to this email directly, view it on GitHubhttps://github.com/FlafyDev/auto-nong-indexes/issues/237#issuecomment-2171030394, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BJHPVSV3NGFWUDB3ICW2QZDZHUBD5AVCNFSM6AAAAABJMHE3GSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZRGAZTAMZZGQ.
You are receiving this because you authored the thread.Message ID: @.***>


Multiple sets of mutually exclusives properties lead to wrong compiler error

Bug Report
🔎 Search Terms
type union interface mutually exclusive property never
🕗 Version & Regression Information
I stumble on it today.
Happen in the nightly.
Happen from ES3 to ESNext on the playground.

This is the behavior in every version I tried, and I reviewed the FAQ for entries about a bug with properties of type never.

⏯ Playground Link
Playground link with relevant code
💻 Code
interface Person
{
    kind: "Person";
    name: string;
}

interface Company
{
    kind: "Company";
    name: string;
}

// Fragments
interface _fromPerson
{
    fromPerson: Person;
    fromCompany?: never;
}

interface _fromCompany
{
    fromPerson?: never;
    fromCompany: Company;
}

interface _toPerson
{
    toPerson: Person;
    toCompany?: never;
}

interface _toCompany
{
    toPerson?: never;
    toCompany: Company;
}

interface RawMessage
{
    timestamp: number;
    title: string;
    content: string;
}

// Combined type
type Message = (
    RawMessage
    & (_fromPerson | _fromCompany)
    & (_toPerson | _toCompany)
);

const MESSAGE: Message = {
    timestamp:<PHONE_NUMBER>000,
    title: "Bug",
    content: "This is an example",
    fromPerson: {
        kind: "Person",
        name: "Alice"
    },
    toPerson: {
        kind: "Person",
        name: "Bob"
    },
    toCompany: {
        kind: "Company",
        name: "ACME"
    },
};

🙁 Actual behavior
toPerson and toCompany are mutually exclusive, but the compiler report as error that property fromCompany is missing while fromPerson is already there and mutually exclusive with fromCompany.
(ts2322)
Type '{ ... }' is not assignable to type 'Message'.
  Type '{ ... }' is not assignable to type 'RawMessage & _fromCompany & _toCompany'.
    Property 'fromCompany' is missing in type '{ ... }' but required in type '_fromCompany'.

If you only have 1 set of mutually exclusive interfaces, you get a correct error :
(ts2322)
Type '{ ... }' is not assignable to type 'Message'.
  Type '{ ... }' is not assignable to type 'RawMessage & _toCompany'.
    Type '{ ... }' is not assignable to type '_toCompany'.
      Types of property 'toPerson' are incompatible.
        Type '{ kind: "Person"; name: string; }' is not assignable to type 'never'.

🙂 Expected behavior
The compiler do not mention fromCompany, but mention toPerson and toCompany being mutually exclusive.
(ts2322)
Type '{ ... }' is not assignable to type 'Message'.
  Type '{ ... }' is not assignable to type 'RawMessage & _toCompany'.
    Type '{ ... }' is not assignable to type '_toCompany'.
      Types of property 'toPerson' are incompatible.
        Type '{ kind: "Person"; name: string; }' is not assignable to type 'never'.

The error reporting algorithm roughly works like this:

Find the type you "meant" from the union

Check for a discriminant (here, there is none)
Check for some other heuristics (nothing applies here)

If we find the type you "meant", report the error about that one
Otherwise report on the first one from the union that plausibly matches (e.g. is also an object type)

To make this case work better, we could add some additional logic in the "other heuristics" to filter out types that have a never property matching a non-never property in the source and see if that results in one or more types.


feat(lxp) returnnstriplet and EntityDecl added

This anticipates on #15 by also returning the parser.
Adds returnnstriplet and sethashsalt to the interface, and adds the following handlers;

EntityDecl
AttlistDecl
SkippedEntity
ElementDecl

Seems sethashsalt is called by default with a random value; https://libexpat.github.io/doc/api/latest/#XML_SetHashSalt
So I think it should be removed from this PR again as there is no need for it in that case.

Hi Thijs
You are doing a great job!
Sorry if this comment is way too late, but since you asked me to review, I am feeling comfortable to write down what I think about.
I noticed the new method 'returnnstriplet (boolean)' and it seems too-C-like.  I don't know what is that triplet or duo namespace neither the consequences of setting this or that way, but reading the documentation makes me wonder:

What if there is no separator?  The call to this method will fail?
Why don't you call it 'setnsreturn ("triplet"|"duo")' (I try to avoid boolean arguments unless they are too obvious)
If this only works if the parser was created with a separator, there might be a way to bind this configuration to the separator definition.  I take a look at the C API and it is exacly that, which does not seem good to me.  I am not sure, but I would prefer a complete API redefinition regarding these parser configuration, maybe adding it in the callbacks table...

I think the set_info function needs update too.
Regards,
Tomás

I agree, the problem I ran into is that the current parser configuration is a list of arguments. So it would mean adding another one. I think the better aproach would be to redefine the parser creation and pass in a table of options. But that would be a breaking change.
One thing that I did consider is renaming the lxp module to lxp.core, and create a new Lua module lxp that wraps the core with some new methods. The new method would then do the same thing (and provide backward compatibility), but a new create method could take a table of options as described above, and be more "lua-ish".


Improve getFileContents by using pathlib instead of os

Before submitting a PR, please review the guidelines:
Contributing Guidelines
What does this PR do?
Improve getFileContents by using pathlib instead of os
Why was it initiated? Any relevant Issues?
On Windows 11 under some conditions os.read can fail not finding the
path with an error about Unicode encoding. This does not fail with
pathlib. Additionally, since Python 3 'U' is the default behavior and
since 3.10 has no longer any effect, and is considered deprecated.
PR Checklist

[x] Correct base branch selected? Should be develop branch.
[x] Enabled commit hook or executed ./bin/autoformat-nuitka-source.
[ ] All tests still pass. Check the Developer Manual about Running the Tests. There are GitHub
Actions tests that cover the most important things however, and you are welcome to rely on those,
but they might not cover enough.
[ ] Ideally new features or fixed regressions ought to be covered via new tests.
[ ] Ideally new or changed features have documentation updates.

Nuitka officially supports Python2, so we need to keep backwards compatibility with it

Also is it just me, or doesn't the code change look terribly more complex, by handling the open locally, and limiting what modes there are.

Also is it just me, or doesn't the code change look terribly more complex, by handling the open locally,

Are you referring to using 2 open instead of one? I could have factored out the open and used pathlib on the file pointer instead no problem.

and limiting what modes there are.

The function docstring states that the two modes are r and rb making the code explicitly fail when that contract is breached is a good practice IMHO.

The function's job is not to enforce mode limitations on other code. If you think that's a good practice, raising a RuntimeError rather than AssertionError or TypeError or ValueError, that's not it.
Also, the universal line buffer mode is needed for compatibility with older Python and should, of course, not be removed just because it doesn't fit your idea of limited modes allowed.
As for the open functionality, we already got openTextFile, which dispatches between codecs.open and regular open, and just generally handles portability for us. I don't see pathlib contributing anything there that those cannot do, except maybe combining opening and reading into one thing, which honestly, doesn't get easier than this
        with openTextFile(filename, mode, encoding=encoding) as f:
            return f.read()

I feel pathlib might be a nice interface, but I don't think it's helpful with everything or that it helps portability across Python versions to use it at all. Until codecs.open get removed, there is nothing that speaks against using it.


[Cross-device sync] Implement anonymous download from Firebase storage

Similar to #102 - simple and straightforward, no sign-in, auth, etc. Just download images from the storage bucket.


[Java] Add typed child getter to StructVector

Describe the enhancement requested
StructVector lets you use getVectorById/getChild to get the children, but you have to cast the result afterwards; it would be nice (if not absolutely necessary) to have an accessor that casts for you (and provides a nicer exception if it turns out the type was different, the field was missing, etc.)
Component(s)
Java

take

AbstractContainer#getChild() has an overload that lets you specify the target FieldVector subtype.
I've added to NonNullableStructVector an overload for getVectorById() that lets you specify a target ValueVector subtype.


Md-datepicker touchUi is always treated as if touchUi is set to true

Bug, feature request, or proposal:
Bug
What is the expected behavior?
when touchUi="true" the md-datepicker will be opened in touchscreen mode, but when touchUi="false", md-datepicker will be opened as a popup under the input
What is the current behavior?
even when touchUi="false" md-datepicker opens in touchscreen mode
What are the steps to reproduce?
Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: http://plnkr.co/edit/XcGBezjJ27qYTRdvQt0v?p=preview (I changed an existing plunker with md-datepicker I found and added the touchUi="false".)
What is the use-case or motivation for changing an existing behavior?
I want to be able use a boolean 'showInTouchMode' like this: [touchUi]="showInTouchMode".
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
I use in my package.json among others:
"@angular/common": "4.3.1",
"@angular/cdk": "2.0.0-beta.8",
"@angular/material": "2.0.0-beta.8",
"typescript": "2.4.1"
Is there anything else we should know?
Not about this point, but I would really appreciate more examples in the documentation at material.angular.io. How exactly should I customize md-datepicker with the parse and display formats? And How exactly should I localize labels and messages? For example, how should a 'MY_DATE_FORMATS' file look?

Remember the brackets

@willshowell  Although you're correct, I'm just curious as why only this specific @Input doesn't have a getter and setter (calling coerceBooleanProperty).

Thanks! It works indeed with the brackets!

@rafaelss95 Fair question - maybe raise a separate issue about that be included in a library-wide audit? IMO coerceBooleanProperty teaches bad habits, but I'm sure there is a valid reason behind it


refactor(katana): define types + trait for state db

Stack:

#631
#629
#628
#627
#626
#625
#624 ⬅
#623

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

✓ Commit merged in pull request #631


Kqueue

Netty has kqueue as transport as well http://netty.io/wiki/native-transports.html, I use mac and FreeBSD for servers, is there any plans to add kqueue here as well?

It should be pretty straightforward, let me take a look at the Netty
implementation and see what I can do.
On Mon, Sep 11, 2017 at 12:13 PM Rafael Custódio<EMAIL_ADDRESS>wrote:

Netty has kqueue as transport as well
http://netty.io/wiki/native-transports.html, I use mac and FreeBSD for
servers, is there any plans to add kqueue here as well?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ztellman/aleph/issues/330, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB6PzoQZB98PbHzoF0lEneuY5NbKAbjks5shYZYgaJpZM4PToxC
.

Closing the issue as we have another one with KQueue feature request #526


bug in the spike_train_surrogates module

@etorre
isi_shuffling function in the spike_train_surrogates module does not perform correctly in the two cases below:
1- when the given spike train is not sorted in an increasing order
2- sometimes the last spike of generated surrogates is larger than t_stop of original spike train. This I did not figure out yet when it exactly happens, but it happens!

A regression test would be appropriate, to indicate the bug and also to test it in the unittests.


App crashes after trying to start service

https://developer.android.com/about/versions/oreo/android-8.0-changes#back-all
Android 8.0 (API level 26) also includes the following changes to specific methods:

The startService() method now throws an IllegalStateException if an app targeting Android 8.0 tries to use that method in a situation when it isn't permitted to create background services.

I have a service to stop download notifications in the event the user closes the app from the Recents Android menu. Apparently these new battery saving features of Oreo will not allow me to run this service and instead throw an IllegalStateException . Fix is in route.

Fix 1902089f844f2d3a1d57aaae08a04923c4a47106
Solution: Start the service only when the app is in the foreground.


Migrated errors for models package

Signed-off-by: dhruv0000<EMAIL_ADDRESS>Description
This PR fixes:

#3471
#3472
#3473
#3475
#3474
#3478
#3476
#3480
#3479
#3481
#3482
#3483

Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

Codecov Report

Merging #3505 (c917a75) into master (8c8b465) will decrease coverage by 6.86%.
The diff coverage is n/a.

:exclamation: Current head c917a75 differs from pull request most recent head eab000f. Consider uploading reports for the commit eab000f to get more accurate results

@@            Coverage Diff             @@
##           master    #3505      +/-   ##
==========================================
- Coverage   17.35%   10.49%   -6.87%
==========================================
  Files          37       37
  Lines        3203     3203
==========================================
- Hits          556      336     -220
- Misses       2505     2800     +295
+ Partials      142       67      -75

Flag
Coverage Δ

gointegrationtests
?

unittests
10.49% <ø> (ø)

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

Impacted Files
Coverage Δ

mesheryctl/internal/cli/root/system/start.go
1.27% <0.00%> (-50.43%)
:arrow_down:

mesheryctl/internal/cli/root/system/stop.go
0.93% <0.00%> (-39.26%)
:arrow_down:

mesheryctl/internal/cli/root/system/check.go
1.49% <0.00%> (-22.10%)
:arrow_down:

Continue to review full report at Codecov.

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

@Shreyas220 a PR you might review...


site.js should be under wwwroot/js folder

and there is no site.css in the doc.

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

ID: c31071a6-97f2-d0ae-22a7-10e461a3c679
Version Independent ID: d3227595-fe2a-7630-0379-8da3b1dba2ee
Content: Tutorial: Call an ASP.NET Core web API with JavaScript
Content Source: aspnetcore/tutorials/web-api-javascript.md
Product: aspnet-core
Technology: aspnetcore-tutorials
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

site.css is used for the test page
Add an HTML file named _index.htm_l to the wwwroot directory. Replace its contents with the following markup:
Putting site.js in /js is a good convention.

Cannot get index.html to load. Deleted launchUrl from Properties\launchSettings.json. Browser is blank and debug log shows a 404 error.

index.html needs to have <script src="js/site.js" changed to "site.js". Instructions above do not say to create a folder named js in wwwroot


Update jp.m3u

Fix missing EPG for Osaka channels.
Changing CNN US to CNNj upon live verification with an online TV Guide.

If they accept to add the channels left, I might resubmit this as a full merge with a new EPG provider.
https://github.com/Animenosekai/japanterebi-xmltv/issues/1

Branch has been renamed as patch-2. This PR will be resubmitted once the issue mentioned before is resolved.

If they accept to add the channels left, I might resubmit this as a full merge with a new EPG provider. Animenosekai/japanterebi-xmltv#1

JCOM EPG doesn't have Tokyo MX2, it's impossible to add it
And the CNN channel in the list is CNN US, not CNN J (needs to be confirmed)
I think just need to wait for my host to be fixed. My script uses Bangumi epg, which contains most of all JP channels.

Talking about that, I've noticed before the host broke that sometimes, EPG would be empty for some channels in some days. In the particular case of the Osaka Channels, it would be avaliable for some days, then be empty on other days, and this happened with some other channels as well.
Apart from the necessary EPG info fix, idk if the issue I mentioned will be covered as well.

It's annoying that iptv-org uses weird IDs for the channels like JOOYDTV.jp instead of MBS

I have a great idea, how about @luongz modifying the script so the TVG IDs match Anise/IPTV-org IDs, then, Anise source is added as a backup in case yours is not avaliable.

I have a great idea, how about @luongz modifying the script so the TVG IDs match Anise/IPTV-org IDs, then, Anise source is added as a backup in case yours is not avaliable.

Tbh i don't like the iptv-org channels id format. My EPG grabber is not the iptv-org one.

In regards to CNN, the channel is currently CNNj. Right now they are on a program about environment, while CNN US is on News Room.
Check here:
https://tvguide.myjcom.jp/?channelType=120&date=20240728

Tbh i don't like the iptv-org channels id format.

Me too lmao


Interactivity based on design

Hey
I think the site is responsive, also I love the simplicity you put in designs,
But what I feels is to make site:
More attractive so that more audience gets involved,
designs can be improved,
More colours to be added,
If you select me, then I can add designs,I can made the site dynamic,can add transitions, and enhance the creativity of site by improving css.

please assign me this issue for GSSoc'24, i will improve the aesthetics of the website to make it look user friendly

Hi, I am confident that i would be able to make this website quite interactive and attractive as well. Please assign me this issue as a part of GSSOC contributor. THanks :)

I am okay with it. But depends on others as well Anshika
On Fri, May 10, 2024 at 11:53 PM Anishkagupta04 @.***>
wrote:

Could you all three work together?
—
Reply to this email directly, view it on GitHub
https://github.com/Anishkagupta04/RAPIDOC-HEALTHCARE-WEBSITE-/issues/17#issuecomment-2105074514,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXIWYDHDOELSCO5MZOSFEKLZBUGAHAVCNFSM6AAAAABHQRRNACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBVGA3TINJRGQ
.
You are receiving this because you commented.Message ID:
@.***
com>

yes we can work

Hello @Anishkagupta04, I am Gargi! I work with html,css,js,react.js and so on and am eager to learn more. I'd appreciate being assigned this task for GSSoC 24.

Oky, I will

@Bhoovi333 @kanikaa-3018 @KeshavPandia Thanks for your enthusiasm to work on this issue as a collaborative issue. Before assigning, I think comment here on what topics you are going to work on regarding this issue, so that duplicate efforts couldn't be there

First and foremost the padding and margins are not proper so i would correct that. Followed by that ,i will work on improving the positioning and look of the video portion on the website. And similarly some other small details can be corrected. Would be great if I am assigned this issue asap so that i can start working on it :)

@Bhoovi333 @kanikaa-3018

Meanwhile can I be assigned so that i can work on my part?

Please submit your PRs separately by linking this issue

Any updates @kanikaa-3018 @Bhoovi333 @

I'm having my exams right now... I'll be giving the updates asap.


Calculate the unit summary data rather than hardcoding it

Right now the JSON files have the unit summaries hardcoded in them, but we should calculate this on the server side.

@bk3c I'm trying to figure out the best way to do this. And it got me to thinking if we really need grouped units and unit_summaries, as it feels like they are at least very similar. Am I missing something here?

reserved and priority will have the same structure as grouped


Publishing package errors with Cannot read properties of undefined (reading 'Id')

Summary
Cannot publish package due to cannot read properties of undefined (reading 'Id')
Steps To Reproduce:
I can't provide a repository as it contains confidential material.
I have two separate machines (my local development machine and a build agent machine). Currently I am successfully able to publish our specific package on my local development machine. The build agent however gets the above error about not being able to read undefined.
As far as I can work out, the machines are configured (for sfdx) identically, and they are attempting the publish operations from identical projects (from git). Both machines are authorized to the devpkg org via sfdxurl:store operations. The sfdx project the following command is based on is attached.

Run npx sfdx package version create -p qa -v devpkg --json --skip-validation --j -x

The error message is really not clear here. It does not tell me if it's something I've got configured wrong on my machine (which may well be the case). These build agents were able to publish these packages before when it was in a completely separate sfdx-project. Having joined them together in a single project (easier development on our side) publishing still obviously works as I can publish from my local machine.
Expected result
The package is published.
Actual result
Error: Cannot read properties of undefined (reading 'Id')
System Information
PowerShell 7
See attached files for doctor output from both machines. The sfdx proejct file that we're using has also been attached, scrubbed of some information.
Additional information
sfdx-doctor-local.txt
sfdx-doctor-agent.txt
sfdx-project.redacted.txt

@TheOptimist I don't see the doctor output for the debug output. Is that file available?

Attached two trace files from the publishing operations @peternhale - let me know if that's what you need. I've included both the SCVQA and SCV package traces (I only experience the problem when publishing SCVQA).
publishing-scv-trace-log.txt
publishing-scvqa-trace-log.txt

Thank you @TheOptimist

@TheOptimist I was expecting debug level logging in these files. I was wondering if you could run with doctor again like this.
sfdx doctor -c "package version create -p qa -v devpkg --json --skip-validation --j -x"
and then return the files produced to me. Thanks in advance

Thank you


db where

where is database file sir?
please share sir

hello, @akifamlg Apologies for the delayed response. After completing the project I will share the database file.

hello @akifamlg  database file is now included. Please check it out.


Element Context

I am seeing the need for different contexts for elements. For example the element search can be about searching for an API before you go building it, or make sure your APIs available for search. Or the word schema in the context of OpenAPI is different description than for GraphQL. I'd like to be able to have multiple descriptions or summaries for an element with different contexts. Then be able to add a property for the context in the blueprint that uses the element.

Added up to 3 element contexts, if we need more we can add them easily to the blueprint and other layouts.


[WIP] chore: Add workflows, update README

Fixes #1
Summary

Brings workflows and README inline with rest of the org

TODO

[x] <script src="https://unpkg.com/<EMAIL_ADDRESS>doesn't work
[x] Add tests to ensure the above does work if possible
[ ] There is a lot of ci jobs, maybe we could target latest of node?

TODO: Doesnt seem like <script src="https://unpkg.com/<EMAIL_ADDRESS>works

using https://unpkg.com/<EMAIL_ADDRESS>doesn't seem to work

using https://unpkg.com/<EMAIL_ADDRESS>doesn't seem to work

The reason is that that version was not published to npm since the workflow failed. That's why this is still "alpha", because if failing release all over the place.
0.0.1-alpha-1 was the last one that I was able to publish.

One can also use jsdelivery

Alright I’ll try check it with specifying then alpha 1 version

Btw, the README.md stopped having syntax highlighting. Is it because of the extra spaces added?

Btw, the README.md stopped having syntax highlighting. Is it because of the extra spaces added?

yeah i guess so - seems like a bug with deno fmt, but ill just 'unindent' it lol

good catch!

Using alpha 1 as the release, using moogle from the browser does work

That's why I had the formatter only working on ./src. Maybe we could be specific about the directories/files?

That's why I had the formatter only working on ./src. Maybe we could be specific about the directories/files?

it's all good now, i think it's just cause the code blocks were indented and using \```

As for the node tests, I followed the ones that still are not EOL, but we could just as well just test on Active LTS and Current.


[feature request] User Search

Will the Python SDK be updated to include the user search functionality?
https://stytch.com/docs/api/search-users
This would be helpful for my usecase.

Hi Derek - we're working on this now. Should have it released soon.

Search has been added in v5.1.0. If you run into issues please reopen this issue.


Add support for exporting a dashboard as a curl command

Goal is to allow user to easily import a dashboard without giving us their API keys.

Will not implement.


🎁: WO groupings

Expected outcome
Add more grouping options

Comm Priority 1
Comm Priority 2
Comm Priority 3

FYI @JoneUE this is now in production.


How to use github oauth?

Hi guys.
I want to enable GitHub Auth.
Duplicated issue #755 but I don't know how to enable.
I installed superset using this playbook.
https://github.com/rluisr/playbook-for-superset/blob/master/main.yml

@rluisr auth is handled by flask app builder, you should refer to its documentation.
BTW if you know this has been already discussed why open a new bug?

Hi I managed to set it up and wrote a post here.
https://medium.com/@aungmt/superset-with-google-oauth-3ba7a1c1f459

@Aung-Myint-Thein what about adding an example to superset documentation?

@xrmx Happy to contribute if you all think this is good :D ..


Wrong temp owner:group on Linux

Docker runs as root on Linux, that means everything created by Docker has the owner and group root. So, a Docker-created temp directory makes it impossible to write in it while inside of a container, as the user inside the container is the host-user (!= root). Let pro-cli check for the right owner:group of temp, fix it if possible or print a warning.

This will be fixed in 0.27.5. pro-cli will create directories on the host (only Linux), if they are specified as volume to mount from, but don't exist. Requirement is ruby to read the yaml file and get available volumes.
Additionally, use docker-compose run (project run|php|composer|...) instead of docker-compose exec for project specific commands. Only the run command provides the ability to start the container with a specific user.
After fixing the permissions manually, this issue should not occur anymore after updating pro-cli to the latest version.


[Bug] [seatunnel-translation-spark] Fix NPE caused by incorrect setting of field nullable

Purpose of this pull request
Fix NPE caused by incorrect setting of field nullable
reference:
https://github.com/apache/spark/blob/v2.4.0/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/SpecificInternalRow.scala#L177
https://github.com/apache/spark/blob/v2.4.0/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/SpecificInternalRow.scala#L162
Check list

[ ] Code changed are covered with tests, or it does not need tests for reason:
[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/incubator-seatunnel/tree/dev/docs


purchaseUpdatedStream not work when restore purchase in ios

purchaseUpdatedStream not work when restore purchase in ios, while a SKTransactionObserverWrapper observe skPaymentQueueWrapper can work. But it's not good idea to add mutiple observer.

@ArwenChan
I assume your issue refers to in_app_purchase
can you provide your flutter doctor -v , your pubspec.yaml and most importantly a minimal reproducible code sample

@ArwenChan
Please provide above requested details. Also check out this issue and see if it resembles your case.

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


Can't create public image from Dockerhub

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Related command
az container create -g Observabilty --name test13313323 --image jaegertracing/all-in-one:latest
Describe the bug
I can't create the public image above, I get this error:
(InaccessibleImage) The image 'jaegertracing/all-in-one:latest' in container group
'test' is not accessible. Please check the image and registry credential.
Code: InaccessibleImage
But running it locally works fine using docker pull jaegertracing/all-in-one:latest
However, tag 1.41 works:
az container create -g $rgname --name $JaegerContainerName --image jaegertracing/all-in-one:1.41
So, why does not 1.42 or latest work?
To Reproduce

Expected behavior
I would expect that all public containers on Github was deployable:
az container create -g MyResourceGroup --name test123--image jaegertracing/all-in-one:latest
Environment summary
Additional context

Also, deploying the same image from Azure Portal results in the same error

route to CXP team

Seeing the same issue via terraform
@JoeMarkov Thanks for noting that 1.41 still works.

'also, trying to create Jaeger via Docker fails on version 1.41 fails for me, but this time, it never completes...
docker --context myacicontext run -d --name observabilty-jaeger --domainname observabilty-jaeger  --cpus=".5" --memory="0.5" -e COLLECTOR_ZIPKIN_HOST_PORT=:9411 -p 5775:5775/udp -p 6831:6831/udp -p 6832:6832/udp -p 5778:5778 -p 16686:16686 -p 14268:14268 -p 14250:14250 -p 9411:9411 jaegertracing/all-in-one:1.41
It should not take many minutes for this to deploy, but it hangs....

I still have this problem
az container create -g 'MyResourceGroup' --name test13313323 --image jaegertracing/all-in-one:latest  --os-type linux   --cpu 0.5 --memory 0.5
(RegistryErrorResponse) An error response is received from the docker registry 'index.docker.io'. Please retry later.
Code: RegistryErrorResponse
Message: An error response is received from the docker registry 'index.docker.io'. Please retry later.
PS Z:\GitHubTN\AzureTraining\Modules\5-Logging and Observability\6 - OpenTelemetry\Deploy Jaeger Scripts>

It also fails if I try with a specific tag, that used to work in the past. Other images from index.Docker.io works fine, like Grafana.
If, I am being rate limited as described here, https://docs.docker.com/docker-hub/download-rate-limit/, then I wish the az container create command would tell me that. If this is a common issue.


New version: Unity.Unity.6000 version 6000.0.30f1

Created by 🥟 Dumplings in workflow run #10052.

Log
Updated: 6000.0.29f1 → 6000.0.30f1
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

@stephengillie


2022-10-23 Recommend

https://github.com/tonybaloney/vscode-pets
https://github.com/codex-team/editor.js
https://github.com/mifi/editly
https://github.com/kochrt/markwhen
https://github.com/bigskysoftware/htmx
https://github.com/logseq/logseq

0d792912b28254f89670add3466185d4fe9af6d2


Handle audio FileObjects/FileSets in Croissant

Proposal:
We propose to handle audio features using https://schema.org/AudioObject.
Technical strategy:

Done: Check that https://schema.org/AudioObject has all the needed attributes. Decision: use additionalProperties if missing (see the discussion https://github.com/mlcommons/croissant/discussions/242).
Add an example toy dataset (used for fixtures in the integration tests). Make the mp3 file as small as possible in order to be able to commit it. You can generate the audio. For example, we generated 1-pixel images in pass-mini.
Add a schema.org constant for sc:AudioObject in _src/core/constants.py
Add a case to handle audio in Python in _src/operation_graph/operations/field.py. We have to choose a library to handle audio. We recommend choosing between librosa or sounddevice or pydub. Before choosing the library, make pros and cons of the library, and publish here to have the validation of a maintainer.
Add unit tests when needed.
Update the Croissant standard in the paragraph Known supported data types:.

This can be split in several PRs.

I think we should look into adding support for https://schema.org/VideoObject and plain binary files at some point too.

I had a look at some audio libraries, here are my thoughts. In short: I'm in favor of using librosa.
Libraries overview
Things in common:

pros:

using MIT or ISC or BSD 3-Clause license.

cons:

still in 0.* version.

librosa:

Uses soundfile or audioread.
pros:

Has a reach documentation with lots of examples.
Downstream libraries support many audio formats.

cons:

Doesn't support integer-value samples. The rationale being that downstream analyses would implicitly to floating point.

sounddevice:

Provides bindings for PortAudio. It's mainly focused on playing and recording audio.

pydub:

Uses ffmpeg or libav(abandoned project) for file reading/writing.
pros:

Supports practically all audio formats.

cons:

Returns integer-value samples which might require additional conversion.

soundfile:

Uses libsndfile for file reading/writing.
pros:

Supports many audio formats.

cons:

The online documentation is slightly behind the actual repository. E.g. it lacks information about MP3 support.

audioread:

pros:

Supports many backends for file reading.

cons:

Doesn't support file writing.

Conclusion
It looks to me that librosa and pydub are the two most used Python libraries for audio processing. pydub was last released in 2021 while librosa has been steadily updated. Given that librosa also has a better documentation, I'd recommend using it.

I also had a look at the most popular audio datasets from Hugging Face and Papers With Code. They all use either FLAC or WAV audio formats. The only exception is Common Voice which uses MP3.

Hey, I notice that in #242 , one of the fields that we look into is the bitrate. What do we do if there are multiple bitrates, due to there being multiple mp3 files?


[Alamofire 5]: responseSerializationFailed error for empty body in Response Data

[x] I've read, understood, and done my best to follow the *CONTRIBUTING guidelines.

What did you do?
Migrating existing code from Almofire v4.8.2 to the latest beta  v5.0.0-beta.5.
I have a post network request which returns empty response body with an Authorization header.
What did you expect to happen?
as in the previous stable version, Response Data call should succeed and I can parse Headers from the response
What happened instead?
It throws error responseSerializationFailed(reason: Alamofire.AFError.ResponseSerializationFailureReason.inputDataNilOrZeroLength)
Alamofire Environment
Alamofire version: 5.0.0-beta.5
Xcode version: 10.2
Swift version: 5
Platform(s) running Alamofire: iOS
macOS version running Xcode: 10.14.4
Demo Project
https://github.com/ashusath/AlamofireBetaAlamofireTestEmptyResponse
https://github.com/ashusath/AlamofireTestEmptyResponse

Can you provide more information about your response? We support the automatic handling of 204 and 205 response codes, as well as .head requests. If your response does not have one of those properties you'll need to customize your response serializer to allow it.

Thank you for response @jshier, Here is the mock URL http://www.mocky.io/v2/5cb82f8b4c00000319d3d3c9. I have to parse the Authorization header from the response, It has an empty body.
It's a login request and we post the credentials to this endpoint.
It is working properly on v4.8.2 and before.
Will I have to make changes to use with Alamofire 5?

If you can update the server to return a proper 204 response, it should work automatically, as a 200 isn't usually considered valid for an empty response.
If you can't make the change, there are a variety of things you can do. You could:

Pass your own serializer instance to response(queue:responseSerializer:completionHandler) that enables the additional empty response codes.
Manually parse the entire response using response(queue:completionHandler:).
Write your own ResponseSerializer that allows all of the flexibility you need. You can use our built in serializers as examples.

Thank you! We think about it and decided to update the server to return a proper 204 response.

isn't usually considered valid for an empty response.

What's the benefit of adding this check, if it's only "usually"?
Complicates life a little bit for the cases where it's the case. Eg. Uploading to Amazon S3 now requires the workarounds..

Ok turned out easier than I imagined from jshier's answer, pasting here for anyone else facing:
let dataResponseSerializer = DataResponseSerializer(emptyResponseCodes: [200, 204, 205]) // Default is [204, 205]

manager.upload(multipartFormData: { multipartFormData in
            /// ...
        }, usingThreshold: UInt64.init(), to: ep.s3.virginiaBucketUrl, method: .post, headers: headers)
        .response(responseSerializer: dataResponseSerializer) { response in
            switch response.result {
                case .failure(let error):
                    // ...
                case .success(let value):
                    // ...
            }
        }


updating config file without restarting

How can I add users or change config file without restarting the proxy?

I really doubt because only once USERS is set and it's here.
Unless @alexbers adds a feature.

Hello,
This functionality was just implemented: https://github.com/alexbers/mtprotoproxy/commit/a2890cf21320dbfef23a3620ffa6e11a44619895
To reload the config you can send the SIGUSR2 signal to the proxy proccess

How to send the SIGUSR2 signal to the proxy proccess in Ubuntu when using proxy in docker-compose?

Just like without the docker-compose - find a process and send a signal to it.

@alexbers
Can you please add code to  if hasattr(signal, 'SIGUSR2') to print  print_tg_info() again?
when I add a user to config file I need their fake_tls secrets.

Done, https://github.com/alexbers/mtprotoproxy/commit/80062c95bc488b4f5b5dc34833812769eaeee3a4


Allow setting the template file for pilot-agent

This change is just to allow overriding the bootstrap template file in
pilot-agent.
This will NOT impact existing code paths, this is only to support
running pilot-agent in local environment

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-istioio-k8s-tests_istio
e4242706f2ae4e767ae06afb41d80669146be21e
link
/test integ-istioio-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-istioio-k8s-tests_istio
e4242706f2ae4e767ae06afb41d80669146be21e
link
/test integ-istioio-k8s-tests_istio

unit-tests_istio
e4242706f2ae4e767ae06afb41d80669146be21e
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


Update rails version

Updates rails to a newer version.
Also replaces FactoryGirl with FactoryBot to stop the warnings.
Also the linter seems to have been updated, so have appeased the linter so that we can push.

I'm closing this PR as it has been open for a considerable amount of time and we're trying to cut down the number of orphaned PRs in alphagov.


[CT-3021] [Spike+] Interactive dbt show should not require model name to be present in --select arg

Housekeeping

[X] I am a maintainer of dbt-core

Short description
When "interactive" dbt compile or dbt show are passed selection criteria that selects a single node, always include that node's compiled/previewed result in the logs.
If:

you have a versioned model using the defined_in version config
the filename you choose does not contain the model name
you use the --select path:<path/to/file> method to unambiguously identify that resource (plus --indirect-selection empty to exclude any tests defined on that model)

Currently, because the model's name is not explicitly included in the --select argument, the compiled/previewed result is missing from the logs.
Acceptance state: `dbt show always include the compiled/previewed result if exactly one node has been selected for compilation/preview.
Acceptance criteria
Following the test case described above — a versioned model with a name different from its defined_in file name, with generic tests defined on it:

Current state: dbt compile --select path:<path/to/versioned/model/file> --indirect-selection empty and dbt show --select path:<path/to/versioned/model/file> --indirect-selection empty do not include the compiled/previewed result in the logs
Acceptance state: Those commands must include the compiled/previewed result in the logs

Impact to Other Teams
Exp/IDE. They will need to start passing --indirect-selection empty when doing --select interactive compiles/previews.
Will backports be required?
1.5.latest + 1.6.latest
Context
Currently, both "interactive" commands (dbt compile and dbt show) require that a model's name be explicitly included in the --select argument, when deciding which compiled / previewed result(s) to include in log output:
https://github.com/dbt-labs/dbt-core/blob/582faa129e8516bae38a4d42d4f8ed7892d4a99a/core/dbt/task/compile.py#L79-L83
https://github.com/dbt-labs/dbt-core/blob/582faa129e8516bae38a4d42d4f8ed7892d4a99a/core/dbt/task/show.py#L67-L70
While this is nice as a way of supporting dbt show --select model_one model_two, it also limits the other types of selection criteria (namely path: selection) that can be used to unambiguously select a single resource.

Related: Interactive command documentation

As discussed in refinement:

let's spike this
if it's a straightforward fix, go ahead and fix it!

Exp/IDE. They will need to start passing --indirect-selection empty when doing --select interactive compiles/previews.

@jtcohen6 What is the timeline on this?

@jtcohen6 What is the timeline on this?

I believe they're now doing this (slack thread), so no outstanding blockers here


Where does ollama.pull() store the models?

Where does ollama-python store the pulled models to?

ollama-python doesn't store models. it's a client library to ollama. models are stored on the server. see the faq for details


Sent USDC from Sollet to Meta but nothing happened

Hi,
I sent 2000 USDC from my sollet wallet to Metamask I never got a request to approve on Meta and the money seems to be gone now. Could someone please help!
Thanks,
Jonathan

https://explorer.solana.com/address/GaeEeZWZkesCuUu2xdkwSP9A8ZFCPmgNP5u1DKFe3zre
This is the tx hash

Please join discord for assistance with this.


License

Thanks for releasing this code along with your research paper.
Do you have a license that you can add to the source code, so that users know what the restrictions may be? If you have no preference, I suggest the 3-clause BSD license.

Thanks Robert! I just added the MIT License to the code.


Improve the explanation of merger changes

Adding a real world example to help convey the meaning

I attempted to draw diagrams, use code and many real world examples but none of them were as clear and this quote.

/rebase


md-datepicker allows to enter alpha numeric characters

Angular material 5 date picker control is accepting special character . To resolve this I tried regex form validation but it didn't work.
I observe that form control value doesn't accept special character and that is the reason regex validation is not working.
please suggest any workaround .

Please keep GitHub issues for bug reports / feature requests. Better avenues for troubleshooting / questions are stack overflow, gitter, mailing list, etc.


ENH: pass through config_settings coming from build frontends

Closes gh-54
This came up when Spack tried to package SciPy 1.9.0 (see https://github.com/spack/spack/pull/31810). It turned out that most of the infra is already there, config_settings simply needed plumbing through. I have tested that this works for SciPy, when building a wheel against a non-default BLAS/LAPACK.
@FFY00 in gh-54 you said "I am struggling to decide on the design", but as far as I can tell there is no UI design aspect here? This is up to build front-ends, all a backend has to do is pass on the config_settings dict that is passed into build_sdist and build_wheel?
I haven't added tests yet, I thought I'd first put this up for feedback.
EDIT: config_settings is part of PEP 517: https://peps.python.org/pep-0517/#config-settings

Thanks for opening this. Unfortunately, it is not that simple :sweat_smile:. Blindly passing the options will cause breakage if you mess with any of the options we rely on. That said, the -D option would not be an issue, so we can allow that option for now and then work on the other ones.

@FFY00 in gh-54 you said "I am struggling to decide on the design", but as far as I can tell there is no UI design aspect here? This is up to build front-ends, all a backend has to do is pass on the config_settings dict that is passed into build_sdist and build_wheel?

Well, we do multiple meson calls! Currently, we do setup, compile, and install. So, there are indeed some design decisions there. There is also specifying the extra Meson arguments in the config and then adding/overriding them on the call.

Blindly passing the options will cause breakage if you mess with any of the options we rely on. That said, the -D option would not be an issue, so we can allow that option for now and then work on the other ones.

I think the only option you rely on is -Dprefix={sys.base_prefix} (yes, that can be a -D option)?

Well, we do multiple meson calls! Currently, we do setup, compile, and install.

Only the meson setup program is relevant here, I guess. :) The other two programs merely happen to share a multi-call program launcher.

I think the only option you rely on is -Dprefix={sys.base_prefix} (yes, that can be a -D option)?

IIRC changing the prefix should only be an issue in the heuristics code paths, but yeah, we do set that. We also use --native-file, so we cannot let users override that, at least blindly. Similarly, cross builds will need some extra handling.

Only the meson setup program is relevant here, I guess. :) The other two programs merely happen to share a multi-call program launcher.

Yes, but I would want to allow users to pass --{ninja,vs,xcode}-args to meson compile if they need, or tweak --jobs and --load-average.
In meson install, some users might want --skip-subprojects, but I am still not entirely sure how to handle that. See #35 for eg.

We also use --native-file, so we cannot let users override that, at least blindly.

These will simply stack, so passing your native file as the very last option would work and override any settings the user specified.
TBH I'd want to configure the python installation being compiled for 🤷♂ but that might be challenging for build requirements.

These will simply stack, so passing your native file as the very last option would work and override any settings the user specified.

Yep, though the UX of quietly overriding it is not great, so we'd probably want to try detecting those situations and either throw an error or a warning. Is there anything fancy in the syntax that would make parsing not trivial?

TBH I'd want to configure the python installation being compiled for man_shrugging but that might be challenging for build requirements.

Well, that goes against PEP 517 :sweat_smile:. For cross builds, I have thrown around the idea of defining a new hook specifically for that, so that build backends may support that use case correctly. That needs a new PEP though, so I am not sure when I'll get around to do it.

Yep, though the UX of quietly overriding it is not great, so we'd probably want to try detecting those situations and either throw an error or a warning. Is there anything fancy in the syntax that would make parsing not trivial?

The file must be a valid configparser file, but the RHS of a binaries entry can have a limited amount of meson.build syntax. mesonbuild.coredata -> class MachineFileParser(configparser.ConfigParser) is the reference implementation. Off the top of my head, the things which might actually be expected to see in a binaries entry are:

[] arrays (such as cpp = ['ccache', 'g++'])
+ concatenation
/ path joining
variable references to a constants entry, e.g. a target triplet

Since you don't actually care about the contents, only whether the key exists, you can simply load it as a configparser file, and check the names of binaries being set in cfg = ConfigParser(); cfg.read(...); cfg['binaries'].keys().

It's indeed the case that the vast majority of options need to go to setup. This PR as it stands does not break anything that is possible today, and just adds that capability. Filtering config_settings to pass on known supported options to compile / install steps should not be hard to add, your suggestions in https://github.com/FFY00/meson-python/pull/122#issuecomment-1211366152 seem like the right ones to me.
The optimization and debug levels we use can be overridden, that requires custom handling.

Yep, though the UX of quietly overriding it is not great, so we'd probably want to try detecting those situations and either throw an error or a warning.

I'd throw an error for --native-file for now, and leave any parsing till the time someone needs it (let's open a new enhancement issue to track).

That said, the -D option would not be an issue, so we can allow that option for now and then work on the other ones.

This isn't a great approach. Each time someone needs to pass something else to setup, they're going to run into a problem, come here to open an issue, and then wait for a new release. Unless there's a good reason to not pass everything on to setup, we should do that instead.

@FFY00 and I had a chat about this PR on Friday. One issue @FFY00 pointed out was that if any new options are added to the build or install stages in Meson, those are not supported through the UX proposed in this PR until they are explicitly handled. That shouldn't happen often, but it is a small downside.
I now understand better the alternative he had in mind: explicitly letting the user define which options go to setup, which to build and to install. That is more comprehensive and requires less special handling of options to redirect them.
The flip side of that coin is that the UX is going to be more verbose. It's not clear exactly what that UX should be yet. The pip and build --config-settings docs say it must be key=value pairs as the argument:

https://pip.pypa.io/en/stable/cli/pip_install/#cmdoption-config-settings
https://pypa-build.readthedocs.io/en/stable/#python--m-build---config-setting

So likely something like:
-config-settings --setup-opt-key=value
-config-settings --build-opt-key=value
-config-settings --install-opt-key=value
# or shorter (can be with or without a space after -C):
-C--setup-opt-key=value
-C--build-opt-key=value
-C--install-opt-key=value

# With concrete options:
-C --setup-opt--Dblas=blis
-C --build-opt--n=8
-C --install-opt---strip

There's a couple of different ways of spelling this (e.g. --setup-key instead of --setup-opt-key, and one could automatically prepend one dash to key so it'd be --setup-Dblas=blis rather than --setup--Dblas-blis). The principle is clear though.
Opinions pro or con this idea? If separate setup/build/install stages, preferred way of spelling it?

if any new options are added to the build or install stages in Meson

The install stage does have some fine-tuning you can do to it, e.g. you can define a subset of tags to be installed, or skip subprojects. I'm not sure how useful either one is for wheels though. There's also --strip, but that duplicates the setup option of the same name.
In general, it seems plausible that further options might be added.
In comparison, the build stage is just "run ninja". It is both more and less interesting -- there are no options to fine-tune the resulting wheel, but several options to control the resources used (parallelism, etc.)
But, the build stage is also probably best controlled by e.g. $SAMUFLAGS which is already a supported interface for the c89 Unix-only version of ninja, assuming that leaving out build stage support would allow reducing the complexity of config_settings (it might not).

It turns out mesonpep517 already has this: https://thiblahute.gitlab.io/mesonpep517/pyproject.html#mesonoptions. It has
--setup-args
--dist-args
--install-args

There's one missing, --compile-args. The naming scheme is logical though: --<meson-subcommand-name>-args.
Would make sense to adopt that I think.

--compile-args doesn't exist because mesonpep517 calls out to Meson directly. I am the one that implemented the feature there.

Ah, good to know, thanks. Are you still happy with how that interface works in mesonpep517 now @tristan957?

Having a way to specify default options in the pyproject.toml would also be nice. Not sure if that has been taken into account yet. Passing options on the command line would override the defaults in a perfect world I think

renaming them to --meson-xxx-args might not be a bad idea.

That may be helpful for clarity. It makes very long lines even longer, but overall that is still a good tradeoff perhaps.

Having a way to specify default options in the pyproject.toml would also be nice.

That is gh-108. It seems reasonable, and the issue submitter there also explains why it must be in pyproject.toml rather than in meson.build or meson-options.txt.

I wasn't referring to -Dxxx options. I was referring to --skip-subprojects for instance.

Closing in favor of #167.


taoria先生，请规范git提交的名字

taoria先生，请规范git提交的名字
我真的不知道你更新的是啥TAT

Hi, thanks for the contribution.
Some changes look nice, but it's a bit much to review for one PR. Is this meant for pre1.29 only? Please check the merge target fix the conflicts.

@fbicirno any explanation?

@fbicirno any explanation?

oh sry, it's a chinese branch for dz platform. i just talk with taoria


N Dimensional Distance

Submission Title
N_Dimensional_Distance
Submission Type
Maths_And_Stats
Submission Description
In mathematics, the Euclidean distance or Euclidean metric is the "ordinary" straight-line distance between two points in Euclidean space. With this distance, Euclidean space becomes a metric space. The associated norm is called the Euclidean norm. Older literature refers to the metric as the Pythagorean metric. A generalized term for the Euclidean norm is the L2 norm or L2 distance.
Folder Related To
Maths_And_Stats => Geometry => N_Dimensional_Distance => Filename.extension
Contributors

[ ]  C++ -
[ ]  C -
[ ]  Python -
[ ] Java -
[ ] JavaScript -
[ ] TypeScript -
[ ] Golang -
[ ] Ruby -
[ ] php -
[ ] Swift -
[ ] C# -

i'll do python version

I would like to implement in C++. May I?

I can do this for cpp. Can I be assigned.

I'd like to do the C implementation.

I can do it in java @Vimlesh-Kumar please assign me this issue

I'd like to have a go at this in C# if possible.

@ahampriyanshu  could I get assigned for ruby version?

Please assign the java part to me

thanks everyone :v:


Use list of URLs for configuring hosts for all the upstream hosts

Fixes #83

@PeterFCaswell Please take a look at this.

Current coverage is 94.42%

Merging #84 into master will decrease coverage by -0.77% as of 13a45e6

@@            master     #84   diff @@
======================================
  Files           26      26
  Stmts          354     359     +5
  Branches        11      13     +2
  Methods          0       0
======================================
+ Hit            337     339     +2
  Partial          0       0
- Missed          17      20     +3

Review entire Coverage Diff as of 13a45e6

Powered by Codecov. Updated on successful CI builds.


Api1000/FC Network

Description
Api1000 Support for FC Network
Issues Resolved
NA
Check List

[x] New functionality includes testing.

[x] All tests pass for go 1.11 + gofmt checks.

[x] New functionality has been documented in the README if applicable.

[x] New functionality has been thoroughly documented in the examples (please include helpful comments).

[x] Changes are documented in the CHANGELOG.

Merging FC Network


There are two conditions but both are the same

Describe the Issue
In the Back End Development and APIs course in challenge Get Query Parameter Input from the Client(Challenge number 10), there are two conditions to pass the test which are Your API endpoint should respond with the correct name.
This condition is written two times so this is a user interface issue.
Affected Page
https://www.freecodecamp.org/learn/back-end-development-and-apis/basic-node-and-express/get-query-parameter-input-from-the-client
Steps to Reproduce
.
Expected behavior
The condition should only be written one time
Screenshots

System

Device: [e.g. iPhone 6, Laptop]
OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04]
Browser: [e.g. Chrome, Safari]
Version: [e.g. 22]

Additional context
No response

Thanks @Feanor96 this could use an update.
I propose we change the wording to this

Your API endpoint should respond with { "name": "Mick Jagger" } when the /name endpoint is called with ?first=Mick&last=Jagger
Your API endpoint should respond with { "name": "Keith Richards" } when the /name endpoint is called with ?first=Keith&last=Richards

Done, please review it!


Parquet reading functions

This adds functions for reading Parquet files from either S3 or a local directory structure.
These functions will be used in the Lambda function performing the automated L1B-processing.
Part of #68

@skymandr Oh and what are your thoughts now on testing, linting and mypy here?

@skymandr Oh and what are your thoughts now on testing, linting and mypy here?

@skymandr Oh and what are your thoughts now on testing, linting and mypy here?

I would love it... I tried getting mypy to work, but no such luck. I think the linting would have to look at the specific file, unfortunately. Would that be worth it? Maybe... I'll give it another go.

@skymandr Oh and what are your thoughts now on testing, linting and mypy here?

I would love it... I tried getting mypy to work, but no such luck. I think the linting would have to look at the specific file, unfortunately. Would that be worth it? Maybe... I'll give it another go.

Actually, I don't think this is worth the effort. The lambda-code will be linted and type-checked, that will have to do.


Adding License File

Hi authors,
Thanks for sharing this very interesting work! I was wondering if it would be possible to add a license file to the repository? Congrats!
Julian

Hi Julian,
Thank you for the interest you expressed in our work. We just added a LICENSE file
Have a good day


Trim trailing zeroes

I see formatNearAmount and trimTrailingZeroes function are the same in the nearlib.js and utils/format.js, how about call one of them from the other? If function is changed, there will be only one place to change

One of them is an autogenerated file (it gets created with yarn build and yarn dist)


Add a Gitter chat badge to README.md

Betterment/backbone.blazer now has a Chat Room on Gitter
@samandmoore has just created a chat room. You can visit it here: https://gitter.im/Betterment/backbone.blazer.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

did not know this would happen. neat! closing because i already added one myself.