Avoid deprecated sample_rate in our own code

Fixes #198.
At least I think it should. Let's wait for feedback.
The idea is that we should be able to read files with sample_rate for backwards compatibility, but not write files with sample_rate. Of course, this means that older versions of pyedflib won't be able to read files produced with newer versions of pyedeflib. Hence, I guess, the CI failure:
            for shead1, shead2 in zip(signal_headers1, signal_headers2):
                # When only 'sample_rate' is present, we use its value to write
                # the file, ignoring 'sample_frequency', which means that when
                # we read it back only the 'sample_rate' value is present.
>               self.assertDictEqual({**shead1, 'sample_frequency': shead1['sample_rate']},
                                     shead2)
E               KeyError: 'sample_rate'

An alternative would be to output warnings when reading files, only when the values of sample_rate and  sample_frequency are different.
Thoughts?

I still get the same error when running the test. I hope I installed the branch correctly:
pip install -U git+https://github.com/DimitriPapadopoulos/pyedflib@make_signal_header#egg=pyedflib

Not sure how to install a specific branch with pip. I installed myself from a repository clone with python setup.py develop.
@skjerns How do you think compatibility should be handled?

Should we write files with both sample_frequency and sample_rate, so that legacy software using older versions of pyedflib can still read new files?
If the answer to the above is yes, when reading files, shouldn't we emit a deprecation warning only when sample_frequency is missing or if the values of sample_frequency and sample_rate are different? Otherwise, we get a deprecation warning when reading our own files we have just written.

Should we write files with both sample_frequency and sample_rate, so that legacy software using older versions of pyedflib can still read new files?

I think there is a confusion - in all cases, sample_rate is written to the file, as is required by the EDF standard (there is no sample_frequency in EDF). The usage of sample_frequency is only used to avoid confusion, as the definition of sample_rate is not intuitive. Internally, sample_frequency is always converted to sample_rate.

If the answer to the above is yes, when reading files, shouldn't we emit a deprecation warning only when sample_frequency is missing or if the values of sample_frequency and sample_rate are different? Otherwise, we get a deprecation warning when reading our own files we have just written.

I think we should only give this warning if the user explicitly sets sample_rate. If subfunctions write sample_rate, that should be no problem.
That means:

Raise DeprecationWarning only if the user explicitly tries to set it.
Raise no warning if subfunctions use sample_rate without user interference.

Indeed, an EDF file contains:

8 ascii : duration of a data record, in seconds
4 ascii : number of signals (ns) in data record

ns * 8 ascii : ns * nr of samples in each data record

Not sure I understand how it works out for several non-contiguous recordings. Any way, I will let you figure out an elegant solution, unless you want help/input on the subject.


Index headlessui component names to improve search results

Version
Doesn't apply.
Reproduction Link
Doesn't apply.
Steps to reproduce

Open the docs and focus the search input
Enter the name for one of the components in headlessui (eg. Disclosure)
Observe the empty results box
Go to https://ui.nuxtlabs.com/elements/accordion to see the name you just searched for at the top of the page

This is coming from @nuxt-themes/ui-kit-edge/components/docs/DocsSearch.vue. There should probably be a way to extend the properties in fuse.fuseOptions.keys or even overwrite them on client projects (as in your projects using the DocsSearchButton component, not my clients).
What is Expected?
I would expect to be able to find the components from @nuxthq/ui that depend on one from headlessui by searching for their upstream name.
What is actually happening?
No result is shown making it difficult to find the desired component.
I have a project where I was using headlessui and recently started to swap my wrapping components for the ones from @nuxthq/ui in order to add some features and have a more cohesive API.

We won't address this in the current version as the next major (v3) docs should address this.


[QUESTION] How to use USB bluetooth dongle instead of built-in one?

Hello!
As you may know, the bluetooth works really bad, so I am trying to replace the built-in bluetooth with an USB bluetooth dongle, but I am not sure where should I start, I found this repo, followed the steps but it's not working, I am guessing that I need to disable the built-in one first, but I don't know how.
Does someone make it work?
The steps that I followed:

Downloaded the last release.
Copied BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext, BrcmPatchRAM3.kext and BrcmNonPatchRAM2.kext (this last one just in case) and pasted on /Library/Extensions.

The approach for disabling the bluetooth works, but my dongle is not working yet, I saw from a subreddit that my dongle should work with the injector, so I am not sure what to do.

Try to add the following code in your config.plist immediately after the (end of the) call for SMCProcessor (and before the call for WhateverGreen) in Kernel -> Add section:

<dict>
	<key>Arch</key>
	<string>x86_64</string>
	<key>BundlePath</key>
	<string>BrcmFirmwareData.kext</string>
	<key>Comment</key>
	<string>Bluetooth dongle Firmware</string>
	<key>Enabled</key>
	<true/>
	<key>ExecutablePath</key>
	<string>Contents/MacOS/BrcmFirmwareData</string>
	<key>MaxKernel</key>
	<string></string>
	<key>MinKernel</key>
	<string></string>
	<key>PlistPath</key>
	<string>Contents/Info.plist</string>
</dict>
<dict>
	<key>Arch</key>
	<string>x86_64</string>
	<key>BundlePath</key>
	<string>BrcmBluetoothInjector.kext</string>
	<key>Comment</key>
	<string>Bluetooth dongle Injector</string>
	<key>Enabled</key>
	<true/>
	<key>ExecutablePath</key>
	<string></string>
	<key>MaxKernel</key>
	<string></string>
	<key>MinKernel</key>
	<string></string>
	<key>PlistPath</key>
	<string>Contents/Info.plist</string>
</dict>
<dict>
	<key>Arch</key>
	<string>x86_64</string>
	<key>BundlePath</key>
	<string>BrcmPatchRAM3.kext</string>
	<key>Comment</key>
	<string>Bluetooth dongle Patch</string>
	<key>Enabled</key>
	<true/>
	<key>ExecutablePath</key>
	<string>Contents/MacOS/BrcmPatchRAM3</string>
	<key>MaxKernel</key>
	<string></string>
	<key>MinKernel</key>
	<string></string>
	<key>PlistPath</key>
	<string>Contents/Info.plist</string>
</dict>

(Cross your fingers and ) Reboot your device!

Alright! Now is working, I deleted all the kexts from /Library/Extensions and put BrcmFirmwareData.kext, BrcmBluetoothInjector.kext and BrcmPatchRAM3.kext on /EFI/OC/Kexts.
So, the steps are:

Disable built-in bluetooth by doing this.
Edit /EFI/OC/config.plist and add these new lines.
Download the lastest release from here.
Copy  BrcmFirmwareData.kext, BrcmBluetoothInjector.kext and BrcmPatchRAM3.kext and paste them on /EFI/OC/Kexts.
Done!

Thanks @profzei you are awsome!!

@hdamico Hope you don't mind me asking, but which bluetooth usb dongle did you use in particular? I'm also thinking of purchasing one, as the experience with built-in bluetooth is far from great.
Other than that, does using a Broadcom bluetooth dongle provide more continuity services (e.g. airdrop, apple watch unlock)? Looking forward to hearing from you!

@samwzlim sure! I bought this dongle, it does not provide much improvment but at least it solved my problem of my bluetooth peripherals getting random disconnections. So, in my opinion if you are hoping to get a better experience with apple services, this won't change much.

@samwzlim sure! I bought this dongle, it does not provide much improvment but at least it solved my problem of my bluetooth peripherals getting random disconnections. So, in my opinion if you are hoping to get a better experience with apple services, this won't change much.

Oh I see, thanks! I see you got the one with the BCM20702 chip inside. I'm trying to find that exact model, but unfortunately, it isn't sold in my country. The only one I can get my hands on is the CSR8510 A10 chip. Have you had any experience with this specific model, by any chance? Based on my research, it's either hit or miss with this dongle.


Implement support for cleartext authentication plugin

Resolves: https://github.com/trilogy-libraries/trilogy/issues/157
Redo of: https://github.com/trilogy-libraries/trilogy/pull/168
The server doesn't request for cleartext plugin in the first handshake as it is not a default plugin. The client should only provide cleartext password when the server requests an auth switch to it, and the client has enable_cleartext_plugin option enabled. If the client does not have cleartext auth plugin enabled, we will raise a Trilogy::AuthPluginError.
This is the authentication flow for a server that uses the cleartext client side plugin (https://github.com/trilogy-libraries/trilogy/pull/168#discussion_r1548811735):

Server sends handshake, with auth plugin caching_sha2_password
Client sends handshake response, still with auth plugin caching_sha2_password
Server sends auth switch request, now with auth plugin mysql_clear_password
Client sends auth switch response with just the cleartext password and nothing else
Server sends OK and we are connected

This PR introduces these changes:

Supports cleartext auth plugin!
Raises when the server auth switches to a plugin that Trilogy does not support. Note that at the moment Trilogy supports mysql_native_password, caching_sha2_password and now mysql_clear_password. This is the recommended behaviour according to mysql docs "Authentication Method Mismatch".
Adds a test dependency on this mysql test server plugin. It's unclear if the file will stick around in the long term but seeing that it is only a test dependency and makes our lives easier than the alternative testing options, we are inclined to just use it for the time being.

cc: @ngan @composerinteralia

I created an issue on the MySQL docker repo to see if they'd be open to building and tagging a mysql-community-test variant that we can use. If they do, we can switch to that and get the test auth plugin for free. If they don't, we can keep what we have (checked-in plugins for various mysql version), or build our own MySQL image.
https://github.com/docker-library/mysql/issues/1040

Would you mind squashing your commits?

I do like a clean git history, but we haven't historically been as opinionated about this as (for example) Rails.

Thank you!


PyTorch pinned Triton version does not compatible with Intel XPU backend Triton version.

LLVM-path based on the latest Triton code(after Triton refactor), while PyTorch (master branch) is using Triton CI: e28a256d71f3cf2bcc7b69d6bda73a9b855e385e (ci_commit_pins/triton.txt) which before Triton refactor(Wed Dec 13 08:21:52 2023).
These two versions incompatible, to make E2E run, we must backport Triton API to match PyTorch’s version, or PyTorch upgrade Triton to the latest version.

Backporting the llvm-target branch to Dec 13 isn't something we have in plan. Do we know when the PyTorch community has in plan to move up to the latest Triton ?

Pytorch has updated to latest Triton API: https://github.com/pytorch/pytorch/pull/117873
Triton usptream + Pytorch upstream are currently compatible.
We do not have an Intel XPU backend compatible with the latest pytorch yet, but there are two projects in progress to get there.

This issue have been resolved.


[Bug]: index.insert_nodes() using QdrantVectorStore is broken.

Bug Description
In previous versions, nodes could easily be inserted into the Qdrant vector store and also deleted. But this does not work anymore.
I have not yet migrated to v0.10.0 so I am not sure if the issue has been fixed but it exists in the v0.9.47
Version
0.9.47
Steps to Reproduce
vector_store = QdrantVectorStore(
client=client,
collection_name=collection_name,
prefer_grpc=prefer_grpc,
enable_hybrid=enable_hybrid
)
index = VectorStoreIndex.from_vector_store(
vector_store=vector_store,
service_context=service_context
)
index.insert_nodes(nodes=nodes)
Relevant Logs/Tracbacks
This throws an error:
'QdrantClient' object has no attribute 'upload_points'

@gich2009 I think you just need to update your qdrant client package version. This method is listed in their docs

Thanks @logan-markewich. Let me try this out.

Resolved @logan-markewich thanks for the tip.
To fix this issue, if you're on qdrant-client==1.7.0 then just upgrade to v1.7.3. Not sure which version introduced the change but v1.7.3 works as expected.


User Test 20230118

git simplification (!!!) -- this just means that we will put ssh keys on the machine
cookiecutter template of automate.yml from jupyter (duplicate of #27)
snippet quick paste of common code snippets like input_folder def (see below)
batches folder structure auto create (duplicate of #27)
@kashfifahim

[ ] Consider adding button to copy or paste the input_folder = header in notebook


Fix target type confusion

Previously, a integer string representing a valid name would be interpreted as an index by the parser, causing the user to not be able to refer to a Person who has a number as their name by their name.
Likewise, a valid mathematical integer but an invalid index would be interpreted as a name rather than an index. Examples include 0 and integers beyond 2^31.
Now, the Target class will first interpret the given string first as an Index, failing which will cause it to treat it as a Name, and failing which again will cause the Target class to throw a ParseException because of an invalid name, unless the string is a mathematical integer, which would throw a ParseException due to invalid index.
After ensuring that the given string is a valid Name (all valid indexes are valid names), the Target class will first interpret the given string as a Name to see if there are any matches in the list with the same Name.

If there are matches and the string is also a valid index within the bounds of the list, then the string is treated as an index, otherwise a name.
If there are no matches by name and the string is an integer, treat the string as an index, and throw index exceptions accordingly.
If there are matches by name and the string is not an integer, treat the string as a name, and throw exceptions due to name accordingly.

Codecov Report

Merging #232 (b42285a) into master (0cf977a) will increase coverage by 0.76%.
The diff coverage is 60.91%.

@@             Coverage Diff              @@
##             master     #232      +/-   ##
============================================
+ Coverage     47.58%   48.34%   +0.76%
- Complexity      629      639      +10
============================================
  Files           133      133
  Lines          2940     2902      -38
  Branches        390      366      -24
============================================
+ Hits           1399     1403       +4
+ Misses         1407     1374      -33
+ Partials        134      125       -9

Impacted Files
Coverage Δ

.../logic/commands/add/AddSocialsToPersonCommand.java
0.00% <0.00%> (ø)

...ress/logic/commands/add/AddTagToPersonCommand.java
0.00% <0.00%> (ø)

...ic/commands/delete/DeletePersonsSocialCommand.java
0.00% <0.00%> (ø)

...logic/commands/delete/DeletePersonsTagCommand.java
0.00% <0.00%> (ø)

...ss/logic/commands/edit/EditSocialMediaCommand.java
0.00% <0.00%> (ø)

...a/seedu/address/logic/parser/AddCommandParser.java
57.69% <0.00%> (ø)

.../seedu/address/logic/parser/EditCommandParser.java
71.42% <ø> (ø)

...ess/logic/parser/EditSocialMediaCommandParser.java
0.00% <ø> (ø)

...c/main/java/seedu/address/logic/parser/Target.java
71.66% <71.66%> (ø)

...in/java/seedu/address/commons/util/StringUtil.java
95.23% <100.00%> (-0.60%)
:arrow_down:

... and 9 more

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 0cf977a...b42285a. Read the comment docs.

should the output be "The meeting index provided is invalid" instead?

@zihaowrez
If the index is out of the list's range:
    public static final String MESSAGE_INVALID_PERSON_DISPLAYED_INDEX = "The person index provided does not exist";
    public static final String MESSAGE_INVALID_MEETING_DISPLAYED_INDEX = "The meeting index provided does not exist";

If the index is an invalid signed integer:
Index provided is invalid. It should have a valid range of 1 to<PHONE_NUMBER> inclusive.

Do u think these error messages are better?


auro-dropdown; initial development

User story
As a developer, I want to be able to have access to a dropdown component, so I can easily create select option experiences.
https://github.com/AlaskaAirlines/auro-menu/issues/1
Outline subtasks or tasks

List specific steps required to deliver this work.

[ ] Consult with a designer for any dropdown specifications
[ ] A11y in regards to role and live notifications need to be coded into the final WC
[ ] Review demo with the designer as well as the Auro team
[ ] All new work to be reviewed by Auro team

Definition of “Done” (exit criteria)

The story is generally “done” when the user can complete the outlined task, but make sure to define what that is.

Has been tested in all browsers

[ ] Chrome
[ ] Firefox
[ ] Edge (79 +)
[ ] Safari
[ ] Mobile Safari
[ ] IE11

Has been tested for accessibility

[ ] Screenreader
[ ] Axe
[ ] Keyboard use

Auro component features

[ ] README doc completed with all relative information
[ ] API documentation created
[ ] Bundled version tested and documented
[ ] Examples and use case info created
[ ] Pages added to the Auro Doc Site

Audit
https://github.com/AlaskaAirlines/auro/issues/216

auro-menu will not be in the scope of this release. The use of auro-dropdown is not mutually exclusive to menu. The first use of this element will be using a team's internally built content node to be exposed from the auro-dropdown element.

@blackfalcon what is the status of this work? Ideally, we will be consuming this as part of our Flight Search release.

@blackfalcon what is the status of this work? Ideally, we will be consuming this as part of our Flight Search release.

Progress is slow. Priority is still high.

Progress is slow. Priority is still high.


Bug fix: Time was parsed too wrong timezone

Fixes #930

LGTM :+1:  (tested on API 23 and 15)

Thanks


systemd

Hi
As of 1fd04d49ece3ae5202975cea51dc62242a526e10, I have now added a systemd unit heavily inspired by this PR.
Thank you!
There are, however, some differences:

I have integrated it with my hacky Makefile deployment workflow
I crosscompile and deploy to a remote target, instead of compiling on the raspi itself

In the course of this, I have also updated the docs a bit.


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-2.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 372

Questions ?
Please refer to the Backport tool documentation


New Feature Request: Newline HTML tag option defaults set to

Description:
By default new line is appended with paragraph tag.
Detail
Many editors, supports user specified option for new line like
It would be much helpful if you provide once such props.
Thanks in advance :)

Hi @vijayaragavan95
I'll add related options.
Thank you.

@JiHong88 ,
Okay got it. Thank you ☺

The 2.34.2 version has been updated.
If this issue has not been resolved, please reopen this issue.
Thank you.


Increasing font sizes

Is it possible to add controls to increase the font size and make the controls larger?

Should be easy once I implement the settings UI


correcting some typos

e.g. Einsihower -> Eisenhower

Hey cannibalox,
i just came across this great plugin i was searching for and discovered some typos wich may be confusing to others.
Regards
Eike

Thank you !


[shuffle] Fix hello blockchain console commands

Motivation
Console command fix
Test Plan
N/A
Related PRs
https://github.com/diem/diem/pull/9829

/land

:broken_heart: Test Failed - ci-test

/land


feat: add jsonschema common format arbitraries

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#134  👈
#133
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @pevisscher and the rest of your teammates on  Graphite


Emission of iteration_completed even for final iteration

This PR fixes #187 by emitting the iteration_completed event after the stopping criterion decided that the iteration should stop.
Though I feel this is just a workaround, and the real problem is properly deciding what constitutes the end of an operation.

I agree, it is somewhat a grey zone what a loop is... do have to complete everything, part of it... butI think this is fine. It is performance-oriented.

@hartwiganzt please read https://github.com/ginkgo-project/ginkgo/wiki/Instructions-for-pull-request-(PR)-reviewers#how-to-merge


Add an internal API to manipulate jobs and variants

This internal API is intended to be used by orchestration to manipulate jobs and variants using only the API instead of mongo.
For the time being, no specific security scheme is applied to the internal API.
The goal is to implement one in the future to restrict this API to the bazooka components and plugins.

:+1:


PSA for PSP test

This commit removes the deprecated PodSeucrityPolicy and provide a guide moving forward for users.

Changes

Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[ ] Has Docs included if any changes are user facing
[ ] Has Tests included if any functionality added or changed
[ ] Follows the commit message standard
[ ] Meets the Tekton contributor standards (including
functionality, content, code)
[ ] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[ ] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
[ ] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
NONE

/retest

/kind test

/kind bug

/ok-to-test

            role: "RunAsAny"

works for the seLinux configurations in controller.yaml

/retest

/retest


wireguard-go: 0.0.20220316 -> 0.0.20230223

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/wireguard-go/versions.
meta.description for wireguard-go is: Userspace Go implementation of WireGuard
meta.homepage for wireguard-go is: https://git.zx2c4.com/wireguard-go/about/
Updates performed

Golang update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.0.20230223 with grep in /nix/store/5ndg987jyln9szzs4cm97px0r05r4y7l-wireguard-go-0.0.20230223
found 0.0.20230223 in filename of file in /nix/store/5ndg987jyln9szzs4cm97px0r05r4y7l-wireguard-go-0.0.20230223

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
wireguard-go

Instructions to test this update (click to expand)

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

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/5ndg987jyln9szzs4cm97px0r05r4y7l-wireguard-go-0.0.20230223
ls -la /nix/store/5ndg987jyln9szzs4cm97px0r05r4y7l-wireguard-go-0.0.20230223/bin

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

1 package built:

wireguard-go

Maintainer pings
cc @kirelagin @yanalunaterra @zx2c4 for testing.


Unexpected nil value when configuring flutter_config_plus package in AppDelegate.swift

Issue Description: Unexpected nil value when configuring flutter_config_plus package in AppDelegate.swift
Steps to Reproduce:
Integrate the flutter_config_plus package into a Flutter project.
Open the AppDelegate.swift file.
Configure the package by adding the necessary code as instructed in the package documentation.
Run the project on iOS.
Expected Behavior:
The flutter_config_plus package should be successfully configured, and the necessary values should be retrieved from the configuration file or environment variables.
Actual Behavior:
Upon running the project on iOS, a fatal error is encountered with the following error message:
Fatal error: Unexpectedly found nil while implicitly unwrapping an Optional value: file Runner/AppDelegate.swift, line 13
Additional Information:
The error occurs on line 13 of the AppDelegate.swift file where the FlutterConfigPlusPlugin.env(for: "IOS_GOOGLE_MAP_API_KEY") method is called.
The IOS_GOOGLE_MAP_API_KEY is an environment variable set for the project, and it is expected to provide the necessary API key for Google Maps.
The error suggests that the optional value returned by FlutterConfigPlusPlugin.env(for:) is nil and is being force-unwrapped, resulting in the crash.
AppDelegate.swift file
import UIKit
import Flutter
import GoogleMaps
import flutter_config_plus

@UIApplicationMain
@objc class AppDelegate: FlutterAppDelegate {
  override func application(
    _ application: UIApplication,
    didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?
  ) -> Bool {
    GMSServices.provideAPIKey(FlutterConfigPlusPlugin.env(for: "IOS_GOOGLE_MAP_API_KEY"));
    GeneratedPluginRegistrant.register(with: self)
    return super.application(application, didFinishLaunchingWithOptions: launchOptions)
  }
}

Did you setup release.xcconfig or debug.xcconfigfile ?


Automated cherry pick of #3903: Operator: add patch for migration

Cherry pick of #3903 on release-v3.15.
#3903: Operator: add patch for migration

Deploy preview for calico ready!
Built with commit 449944c60003e524cba61f40791fa856ad4c3f52
https://deploy-preview-3904--calico.netlify.app


Investigate Argo Workflows

Nested workflows
Artifacts
Passing input/output
Conditions
Context
Discussion with Paul on solutions (& iteration?)
Ensure OCF documentation is up to date

Few things we have to brainstorm and discuss during this task:

porter runner with mixins (like Helm... Knative? Argo?)
runner lifecycle (install/upgrade/uninstall)?


migrate common.gradle to Kotlin DSL

This pr is mainly for review
Some migrated build.gradle files include examples of:

akuma -> regular extension
coomer -> multisrc extension
batoto -> implements a library dependency
komga -> implements external dependency

Known issue(s):

assert statments aren't working

We'll use one single extension function to register the metadata. Recorded in #1926 for now.


[packager] [0.45.0 hotfix] Fix broken default getProjectRoots

This is a backport of #14412 to 0.45.0.
You'll notice the code is slightly different -- this is because Config.js has changed quite a bit between versions. The intent of the code is the same however.
See #14412 for a more detailed description.
Fixes https://github.com/facebook/react-native/issues/14246

cc @grabbou (see convo in Slack)

Thanks guys!


OCM-7293 | ci: Automate tech debt for classic testing for OCP-70337|70336

…0336

What this PR does / why we need it:
Automation testing for ingress updating
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story (OCM-xxxx):
Fixes # OCM-7293
Change type

[ ] New feature
[ ] Bug fix
[ ] Build
[x] CI
[ ] Documentation
[ ] Performance
[ ] Refactor
[ ] Style
[ ] Unit tests
[ ] Subsystem tests

Checklist

[ ] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.

lixue@Xue-Lis-MacBook-Pro terraform-provider-rhcs % ginkgo -focus '(70337|70336)' tests/e2e
time="2024-04-08T12:48:26+08:00" level=info msg="Running against env staging with gateway url https://api.stage.openshift.com"
time="2024-04-08T12:48:26+08:00" level=info msg="Loaded cluster profile configuration from profile rosa-hcp-ad : map[admin_enabled:false autoscale:true byok:true byovpc:true channel_group:candidate cloud_provider:aws cluster_type:rosa-hcp compute_machine_type:m5.2xlarge etcd_encryption:true fips:false kms_key_arn:true labeling:false major_version:4.15 multi_az:true oidc_config:managed private:false product_id:rosa proxy:true region:us-west-2 sts:true tagging:true unified_acc_role_path: version: version_pattern:latest zones:a,b,c]"
Running Suite: e2e tests suite - /Users/lixue/Workspace/ocm-tf/terraform-provider-rhcs/tests/e2e
================================================================================================
Random Seed:<PHONE_NUMBER>

Will run 2 of 65 specs
time="2024-04-08T12:48:26+08:00" level=info msg="Loaded cluster profile configuration from profile rosa-hcp-ad : map[admin_enabled:false autoscale:true byok:true byovpc:true channel_group:candidate cloud_provider:aws cluster_type:rosa-hcp compute_machine_type:m5.2xlarge etcd_encryption:true fips:false kms_key_arn:true labeling:false major_version:4.15 multi_az:true oidc_config:managed private:false product_id:rosa proxy:true region:us-west-2 sts:true tagging:true unified_acc_role_path: version: version_pattern:latest zones:a,b,c]"
time="2024-04-08T12:48:26+08:00" level=info msg="Running terraform init against the dir /Users/lixue/Workspace/ocm-tf/terraform-provider-rhcs/tests/tf-manifests/rhcs/clusters/rosa-hcp"
time="2024-04-08T12:48:30+08:00" level=info msg="Running terraform output against the dir: /Users/lixue/Workspace/ocm-tf/terraform-provider-rhcs/tests/tf-manifests/rhcs/clusters/rosa-hcp"
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSStime="2024-04-08T12:48:32+08:00" level=info msg="Loaded cluster profile configuration from profile rosa-hcp-ad : map[admin_enabled:false autoscale:true byok:true byovpc:true channel_group:candidate cloud_provider:aws cluster_type:rosa-hcp compute_machine_type:m5.2xlarge etcd_encryption:true fips:false kms_key_arn:true labeling:false major_version:4.15 multi_az:true oidc_config:managed private:false product_id:rosa proxy:true region:us-west-2 sts:true tagging:true unified_acc_role_path: version: version_pattern:latest zones:a,b,c]"
time="2024-04-08T12:48:34+08:00" level=info msg="Running terraform init against the dir /Users/lixue/Workspace/ocm-tf/terraform-provider-rhcs/tests/tf-manifests/rhcs/ingresses/classic"
time="2024-04-08T12:48:34+08:00" level=info msg="Running terraform apply against the dir: /Users/lixue/Workspace/ocm-tf/terraform-provider-rhcs/tests/tf-manifests/rhcs/ingresses/classic with args [-var cluster=2agfoecai8bfqaaq7o92espb6a598n19 -var load_balancer_type=classic]"
time="2024-04-08T12:48:37+08:00" level=error msg="Terraform used the selected providers to generate the following execution\nplan. Resource actions are indicated with the following symbols:\n  + create\n\nTerraform will perform the following actions:\n\n  # rhcs_default_ingress.default_ingress will be created\n  + resource \"rhcs_default_ingress\" \"default_ingress\" {\n      + cluster                          = \"2agfoecai8bfqaaq7o92espb6a598n19\"\n      + id                               = (known after apply)\n      + load_balancer_type               = \"classic\"\n      + route_namespace_ownership_policy = (known after apply)\n      + route_wildcard_policy            = (known after apply)\n    }\n\nPlan: 1 to add, 0 to change, 0 to destroy.\n\nChanges to Outputs:\n  + id = (known after apply)\nrhcs_default_ingress.default_ingress: Creating...\n\nError: Failed building cluster default ingress\n\n  with rhcs_default_ingress.default_ingress,\n  on main.tf line 14, in resource \"rhcs_default_ingress\" \"default_ingress\":\n  14: resource \"rhcs_default_ingress\" \"default_ingress\" {\n\nFailed building default ingress for cluster\n'2agfoecai8bfqaaq7o92espb6a598n19': status is 400, identifier is '400', code\nis 'CLUSTERS-MGMT-400' and operation identifier is\n'4318ff1b-2192-4d36-a6c6-c79dcaf38201': Can't update load balancer type on\nHosted Control Plane cluster '2agfoecai8bfqaaq7o92espb6a598n19'"
•time="2024-04-08T12:48:37+08:00" level=info msg="Loaded cluster profile configuration from profile rosa-hcp-ad : map[admin_enabled:false autoscale:true byok:true byovpc:true channel_group:candidate cloud_provider:aws cluster_type:rosa-hcp compute_machine_type:m5.2xlarge etcd_encryption:true fips:false kms_key_arn:true labeling:false major_version:4.15 multi_az:true oidc_config:managed private:false product_id:rosa proxy:true region:us-west-2 sts:true tagging:true unified_acc_role_path: version: version_pattern:latest zones:a,b,c]"
time="2024-04-08T12:48:38+08:00" level=info msg="Running terraform init against the dir /Users/lixue/Workspace/ocm-tf/terraform-provider-rhcs/tests/tf-manifests/rhcs/ingresses/classic"
time="2024-04-08T12:48:38+08:00" level=info msg="Running terraform apply against the dir: /Users/lixue/Workspace/ocm-tf/terraform-provider-rhcs/tests/tf-manifests/rhcs/ingresses/classic with args [-var cluster=2agfoecai8bfqaaq7o92espb6a598n19 -var route_namespace_ownership_policy=Strict -var route_wildcard_policy=WildcardsAllowed -var excluded_namespaces=[\"qe\",\"test\"] -var route_selectors={\"route\":\"internal\"}]"
time="2024-04-08T12:48:41+08:00" level=error msg="Terraform used the selected providers to generate the following execution\nplan. Resource actions are indicated with the following symbols:\n  + create\n\nTerraform will perform the following actions:\n\n  # rhcs_default_ingress.default_ingress will be created\n  + resource \"rhcs_default_ingress\" \"default_ingress\" {\n      + cluster                          = \"2agfoecai8bfqaaq7o92espb6a598n19\"\n      + excluded_namespaces              = [\n          + \"qe\",\n          + \"test\",\n        ]\n      + id                               = (known after apply)\n      + load_balancer_type               = (known after apply)\n      + route_namespace_ownership_policy = \"Strict\"\n      + route_selectors                  = {\n          + \"route\" = \"internal\"\n        }\n      + route_wildcard_policy            = \"WildcardsAllowed\"\n    }\n\nPlan: 1 to add, 0 to change, 0 to destroy.\n\nChanges to Outputs:\n  + id = (known after apply)\nrhcs_default_ingress.default_ingress: Creating...\n\nError: Failed building cluster default ingress\n\n  with rhcs_default_ingress.default_ingress,\n  on main.tf line 14, in resource \"rhcs_default_ingress\" \"default_ingress\":\n  14: resource \"rhcs_default_ingress\" \"default_ingress\" {\n\nFailed building default ingress for cluster\n'2agfoecai8bfqaaq7o92espb6a598n19': status is 400, identifier is '400', code\nis 'CLUSTERS-MGMT-400' and operation identifier is\n'bdc79278-66b7-4a6e-b350-9ffc1e2a751f': Can't update route selectors on\nHosted Control Plane cluster '2agfoecai8bfqaaq7o92espb6a598n19'"
•SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS

Ran 2 of 65 Specs in 14.824 seconds
SUCCESS! -- 2 Passed | 0 Failed | 0 Pending | 63 Skipped
PASS
You're using deprecated Ginkgo functionality:
=============================================
  --ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo.  This feature has proved to be more noisy than useful.  You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.

To silence deprecations that can be silenced set the following environment variable:
  ACK_GINKGO_DEPRECATIONS=2.13.2

Ginkgo ran 1 suite in 17.331158969s
Test Suite Passed

/lgtm

/retest

/test rosa-sts-advanced-critical-high-presubmit

/test rosa-sts-private-critical-high-presubmit

/retest

/test rosa-sts-advanced-critical-high-presubmit

/test rosa-sts-private-critical-high-presubmit

/test rosa-sts-private-critical-high-presubmit

/test rosa-sts-private-critical-high-presubmit

/test rosa-sts-advanced-critical-high-presubmit

/approve

/lgtm

/approve


Merge partial logs for kubernetes

What does this PR do?

Refactor on logs/decoder, logs/line_handler
Add logic to aggregate partial logs to one full log

Motivation
Client requests
Additional Notes
The process logic changed to fix the issue with "...TRUNCATED..." prepend before timestamp.

LGTM


try to fix funding, close #1023

Use only those commits which are made by a 'CNCF-Bot' account. Not sure if that was the problem

Deploy preview for landscape ready!
Built with commit 6f4230a0ceffcc9c913340198b7f4c547de56e11
https://deploy-preview-1028--landscape.netlify.com

I hope this will either fix a problem or at least it will tell me which commit is used to get a different funding value.


Make clicking radio boxes and checkboxes on iPads more responsive

Currently clicking these buttons takes about a second for the page to respond. Make it more snappy.
Reported by DTang.

@mrueschman, we should test this on a tablet, a lot of JS was removed in 0.30.0, so hopefully these pages are more responsive.

Tried a survey with 77 questions and branching logic on iPhone, worked fine, closing.


Language translations

It would be nice to have language translations, for people who have low English skills, or just for people who love seeing software in their language of choice.

:+1: Is there already a I10N process ?
Can we contribute to translations ?


docs: added citation file

Contributing to Meteors
Thank you for contributing to Meteors! Please follow the guidelines below to ensure a smooth and efficient contribution process.
PR Checklist

[ ] PR Title: "semantic tag: description"

Package: Use the appropriate semantic tag for your PR:

fix: A bug fix.
feat: A new feature.
docs: Documentation only changes.
style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc).
refactor: A code change that neither fixes a bug nor adds a feature.
perf: A code change that improves performance.
test: Adding missing tests or correcting existing tests.
chore: Changes to the build process or auxiliary tools and libraries such as documentation generation.
build: Changes that affect the build system or external dependencies.

Example: "fix: typo in README.md"

[ ] PR Message: Delete this entire checklist and replace it with:

Description: A detailed description of the change.
Dependencies: Any dependencies required for this change.

[ ] Add tests and docs: If you're adding a new integration, please include

a test for the integration, preferably unit tests that do not rely on network access,
an example notebook showing its use, located in the examples directory.

[ ] Lint and test: Run rye run pre-commit run --all-files and rye test to ensure your changes pass all checks. See contribution guidelines for more.

[ ] Related Issue(s): If your PR fixes an issue, please link it in the PR description.

Additional Guidelines

Import optional dependencies within functions.
Avoid adding dependencies to pyproject.toml files unless required for unit tests.
Most PRs should not modify more than one package.
Ensure changes are backwards compatible.

Review Process
If no one reviews your PR within a few days, please @-mention one of the maintainers.

@pbiecek we also need to add (but after the release of 0.2.0 version) the doi. Just a reminder don't do it now :)


easy-ViTPose Import error

Hi, thank you for providing this simple implementation of ViTPose!
Two weeks ago I was running the code in Google Colab, but when I tried to run it again today, I encountered an error while trying to install the easy_ViTPose package.
The error message I received was as follows:
Obtaining file:///content/easy_ViTPose
error: subprocess-exited-with-error

× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.
Preparing metadata (setup.py) ... error
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

How can I solve this problem?

Thanks! there was a syntax error in last commit!
It should work now

Thanks for the quick response! It is working now!


📝(project) update documentation using the CLI

Proposal
Now that we have a CLI to use arnold, our documentation needed a solid revamp to reflect recent changes.
The documentation no longer focuses on edxapp but the tool itself, with a clear distinction between tool users and developers.
Depends on #576

Closing this PR because this work has been merged in #672


Material ui next

add prepare script to build lib/
fixed install issue for me

Done!
Big thanks @motiko

<EMAIL_ADDRESS>


Flesh out runtime bytecode validation behavior.

I'm not comfortable with the scope of this change. I think this is a much more substantial expansion of the change than we should be taking as a PR to a previously accepted proposal.
My central concern here is that this is an expansion of when and how the DIXL validator is used by the runtime. The expansion of using the DXIL validator beyond just the debug layers raises concern to me because of the DXIL validator's uncertain future and known security weaknesses.
At a minimum I think we need to have some discussions to more clearly understand the motivations for these expansions so that we can appropriately prioritize and plan for support, maintenance, and associated risk.

This isn't attempting to change the proposal, but rather concretely define what the accepted proposal mentioned, which is there would be runtime control on validation.  Note that the runtime will not have a built in validator, and by default it doesn't validate.  An app has to opt in to the runtime validating, because they want to see the invalid state creation fail.  And if they opt in, they have to provide a validator implementation.


tunnelx: init at 2023-07-nix

Description of changes
First solo attempt by at getting a cave surveying software package into nixpkgs.  (It's already packaged in Debian.)
It runs directly from the compiled java code (ie directory of .class files), because this is reproducible using a call to makeWrapper.  If I batch these up into a .jar file (which is standard practice), then the hash of the result seems to vary.
I am putting it into the /applications/gis/directory because it is mapping software.
In the future I hope to move the other two new cave survey packages /applications/misc/survex and /applications/misc/therion (which I helped @MatthewCroughan to package) into the proper '/applications/gis/`directory.
Homepage for this one: https://github.com/CaveSurveying/tunnelx/
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

@goatchurchprime please squash the commit that removes the trailing whitespace into your initial commit so this PR is just a single commit.

Result of nixpkgs-review pr 239739 run on x86_64-linux 1

1 package failed to build:

tunnelx

Result of nixpkgs-review pr 239739 run on x86_64-linux 1

1 package built:

tunnelx

Upstream re-released the same version which now has a different commit hash, can you fix that so we can get this merged?

Done.  I've no idea how this happened as I'm certain I didn't touch  tunnelx repo after I started on the nixpkgs stuff. Is this an error that one of the bots picks up?

Hm where are you actually getting your release from? It's not a tag in github right?

When starting tunnelx it throws a few warnings

When starting tunnelx it throws a few warnings

Those startup warnings don't mean anything and have been there for years.  I am going to give this app some love once it gets through this nixos process.

@goatchurchprime can you explain where you are pulling the release from? The only tag released on github seems to be from 2019 https://github.com/CaveSurveying/tunnelx/releases/tag/R2019a and your commit hash changed at some point.

@Janik-Haag since he authors this software, he made a new tag v2023-07-nix especially for the purpose of this PR

Oh I see, then it's interesting that the commit hash changed at some point without them noticing :/

@Artturin I made a new PR fixing the things you reported, please have a look!


Generating API doesn't work on WSL/Ubuntu

Describe the bug
./generate_code.sh gives errors on WSL
./server/swagger_server/models/api_url.py
sed: can't read 1i\
    # Copyright 2021 The MLX Contributors\
    #\
    # SPDX-License-Identifier: Apache-2.0\
    : No such file or directory

@ckadner

Hi @JAulet please check out PR #255 for a fix.


Allow binary docs

We need a place to store binary documents (e.g., PDFs) in the repo, a prefix for linking, and processing to make the link work.

Added a new prefixDef "bin:" in rev 12168.

Added a new folder data/binaries in rev 12169.

Remaining required changes done AFAICS by rev 12174.

We have our first test case in place, so by tomorrow we should be able to see whether the link in HW is correctly rendered, and whether the PDF itself is copied into the lemdo-dev and dre anthologies.

Working in the lemdo-dev build. Since we're not building DRE by default, I'll have to do a test build of it locally to see if the second part of the equation is working.

Tested, found a bug, fixed the bug in rev 12191. Closing this now.


Set up Travis CI

This PR fixes #2 by adding YAML file for Travis CI and Travis badge in README.
To make CI work, you need to link your GitHub account with Travis and enable builds for this repository. See this doc for the details.
Note that this PR is based on #1. So, please review #1 first.

Thanks! Let's see if I got the integration right...


Healthcheck unhealthy on multi-version server

I have three servers with type PAPER. All of them are working fine, but the healthchecks say they are "unhealthy".
Screenshot from Portainer:

docker-compose.yml:
networks:
  default:
    external:
      name: bungeecord_connector
services:
  vanilla:
    container_name: vanilla
    environment:
      EULA: "TRUE"
      TYPE: PAPER
    image: itzg/minecraft-server:latest
    stdin_open: true
    tty: true
    volumes:
    - ./data:/data:rw
    - /etc/timezone:/etc/timezone:ro
version: '3.0'

Hmm, that's an interesting scenario for them; however, either way the server list ping response isn't compliant with the JSON structure
https://wiki.vg/Server_List_Ping#Response

...I wonder why they don't put that multi-version list in version.name rather than setting version to -1?

@voruti sorry for getting your hopes up by commenting but could you please tell me how to put portainer in dark mode? i can't find the setting

Dark Reader

Danke shun!

I did some testing:
Basic vanilla server:
sudo docker container run --rm -e EULA=true -p 25561:25565 itzg/minecraft-server:
{
  "description": {
    "text": "A Vanilla Minecraft Server powered by Docker"
  },
  "players": {
    "max": 20,
    "online": 0
  },
  "version": {
    "name": "1.16.5",
    "protocol": 754
  }
}

Basic Paper server:
sudo docker container run --rm -e EULA=true -p 25561:25565 -e TYPE=PAPER itzg/minecraft-server:
{
  "description": {
    "text": "A Paper Minecraft Server powered by Docker"
  },
  "players": {
    "max": 20,
    "online": 0
  },
  "version": {
    "name": "Paper 1.16.5",
    "protocol": 754
  }
}

Difference: "Paper " is added to version.name
Paper server with plugin ProtocolSupport installed on it:
sudo docker container run --rm -e EULA=true -p 25561:25565 -e TYPE=PAPER -v /home/user/tmpWorkDir:/data itzg/minecraft-server (server started, Ctrl+C, moved ProtocolSupport.jar to /home/user/tmpWorkDir/plugins/ProtocolSupport.jar, server started again):
{
  "version": {
    "name": "Paper 1.16.5",
    "protocol": 4
  },
  "description": {
    "text": "A Paper Minecraft Server powered by Docker"
  },
  "players": {
    "max": 20,
    "online": 0
  }
}

Difference: version.protocol changed from 754 to 4 & the version block moved to the beginning of the JSON structure (this is reproducible!)
So, ... the version.name value is not changed by the plugin. It's the version.protocol that is changed to 4.

The information from https://github.com/itzg/docker-minecraft-server/issues/796#issuecomment-796880533 was collected with https://gist.github.com/zh32/7190955 which is linked in https://wiki.vg/Server_List_Ping#Examples.
I did the same with https://github.com/Raqbit/mc-pinger (which is used by mc-monitor, which is used by docker-minecraft-server): The JSON response from my server running the ProtocolSupport plugin is
{
  "description": {
    "text": "A Vanilla Minecraft Server powered by Docker"
  },
  "players": {
    "max": 8,
    "online": 0
  },
  "version": {
    "name": "Paper 1.16.5",
    "protocol": -1
  }
}

(Ignoring the modt and player count, which are different from the previous comment, because this JSON response is from my "production" server, e. g. further configured server ...)
... a difference in the version.protocol can be seen! There's that "-1" from the error message in the screenshot I attached in my first https://github.com/itzg/docker-minecraft-server/issues/796#issue-826576960.

Now for the solution :D
When I modified https://github.com/Raqbit/mc-pinger to extract the JSON response, I used the latest version from the master branch (git clone). No error is showing up!!
iverly just pushed a commit which fixed the problem. He changed the "Protocol" variable from uint to int32 which allows the variable to contain negative values and thus the error is fixed with this newest commit.
With this change integrated into this Docker image "itzg/minecraft-server", the healthcheck should be fixed!

Thanks @voruti . I had missed the ".protocol" part of the JSON path, so had gotten my investigation off track. I'll work getting mc-monitor and then this updated.

The latest image now includes https://github.com/Raqbit/mc-pinger/releases/tag/v0.1.1 so this is ready to test.


[Bug]: Citation syntax renders incorrectly in reading mode

Bug Description
When using the double-blockquote citation syntax to create a citation, the effect is rendered as expected in source and live preview modes, but incorrectly in reading mode.
Relevant Screenshot
Source:

Live Preview:

Reading:

To Reproduce
Create a blockquote with citation using the double-blockquote syntax, e.g.:
> this is a quote by me
>> Dan O'Leary

Observe the rendering behavior described above.
Obsidian Version
0.15.6
Installer Version
0.15.6
Font Size
16
Which editor are you using?

[X] New Editor
[ ] Legacy Editor

In which mode(s) does the problem occur? (if applicable)

[ ] Source (Edit)
[X] Reading (Preview)
[ ] Live Preview

Which operating system?

[X] macOS
[ ] Linux
[ ] Windows
[ ] iOS
[ ] Android

Plugin-Specific Problems

[X] I took note of the specific instructions regarding those plugins.

Checklist

[X] I updated to the latest version of the theme (Settings → Appearance → Themes - Manage → Update).
[X] I made sure that the issue is related to this theme by checking that the problem does not occur with the default theme.
[X] In case I am missing an UI element, I have checked that it cannot be re-enabled with the Style Settings plugin.
[X] If the bug occured after updating the theme, I read the last couple of entries in the changelog to make sure the bug is not an intentional change. (In that case, there will most likely be a style setting to turn it off again.)

Hi! As you may have heard, the upcoming Obsidian update 0.16 has a massive amount of changes for theme development, necessitating a complete rewrite of Shimmering Focus. This means:

A lot of bugs and feature requests will be obsolete. with Obsidian 0.16 and the rewritten Shimmering Focus.
As the theme has over 15,000 lines of CSS, the rewriting will take a considerable amount of time. Recreating the core features alone will likely take me a while, so I simply will not have much time to implement many feature requests, since the recreation of the past core features has priority.

Basically, this is the reason why I am – for now – closing this issue. If your bug still exists / your feature request is still relevant in the upcoming version 3.0 of Shimmering Focus, please comment here and I will re-open it. 🙂


fix debian install and docker version check

This PR fixes run.bash as follow:
linux-image-extra is an Ubuntu only package.
The command to get docker version was changed, got the new from: https://get.docker.com/
Also is possible to use: $(docker version --format '{{.Client.Version}}')

@guilhermebr thank you!


Fix code scanning alert - License

After implementing code scanning alerts, it seems as though there isn't a license for this. Adding a license for this repo would be beneficial because it would give users information on how they can use this repo!
Tracking issue for:

[ ] https://github.com/flutter/put-flutter-to-work/security/code-scanning/3

I can take a look


attempt to resolve issue 27

Please check this new suggested solution.

Thank you very much for this useful pull request.


Tested remote debugging with Termdebug: a small report and a feature request.

I tried to remote debugging with Termdebug, and everything worked great.  with the exception of a small singularity on Windows.
The setup was  gdb connected to an openocd server connected to a stlink probe and a stm32 Nucleo board.
With this setup in Windows, when you run continue  from the gdb console and there are no breakpoints, the control over the gdb console has gone and it seems that you cannot get it back.
Typically,  to get the control back you hit CTRL_C on the gdb console, but in this case nothing happens. Furthermore, if you try to type commands in the gdb console, you won't get any message back.
Nevertheless, and somehow surprisingly, if you run  <c-w>:q from the gdb console the messages that you were supposed to get back in response to your commands are displayed all at once.
The following is what I see after after I run continue
gdb> continue
Continuing.
gdb> monitor halt
gdb> monitor halt
gdb>

and the following is what I get displayed when I run <c-w>:q
gdb> continue
Continuing.
gdb> monitor halt
gdb> monitor halt
"monitor" command not supported by this target.
"monitor" command not supported by this target.

The command monitor halt was perfectly working before running continue.
I tried the same experiment on macos in Termdebug prompt mode and hitting CTRL_C after a continue command gave me back the gdb control, as it is supposed to be.
I analyzed the gdb logs of both Windows and macos to check the communication between gdb and openocd and it appear to identical:
...
&"c\n"
~"Continuing.\n"
^running
*running,thread-id="all"
(gdb)
&"[remote] Sending packet: $vCont?#49\n"
&"[remote] Packet received: vCont;c;C;s;S\n"
&"[remote] packet_ok: Packet vCont (verbose-resume) is supported\n"
&"[remote] Sending packet: $vCont;c#a8\n"
&"[remote] wait: enter\n"
&"[remote] wait: exit\n"
&"[remote] wait: enter\n"
&"  [remote] Packet received: O\n"
&"[remote] wait: exit\n"
&"[remote] wait: enter\n"
&"  [remote] Packet received: O\n"
&"[remote] wait: exit\n"
&"[remote] wait: enter\n"
&"  [remote] Packet received: O\n"
&"[remote] wait: exit\n"
&"[remote] wait: enter\n"
&"  [remote] Packet received: O\n"
&"[remote] wait: exit\n"
&"[remote] wait: enter\n"
...

Hence, I would exclude possible communication problems between gdb and openocd.
However, by looking at the Termdebug source code, I noticed that there is a special function called debugbreak() which seems to be designed to take back the control of the gdb console when using Windows.
Therefore, I tried to get both the gdb and openocd PIDs from a powershell (Get-Process -Name {arm-none-eabi-gdb, openocd} | Select-Object -Property Id) and run echo debugbreak(pid_openocd) first and  echo debugbreak(pid_gdb)  in another working session returning 1 in both cases - in my understanding you should only use the debugbreak(open_ocd) but I tried both anyways. . Yet, I couldn't get control back of the gdb console.
I am suspicious that the debugbreak() function works well when you have a "debugged program" window in the classical sense,  but for remote debbuging, or at least in this use-case. Hence, if this is the issue, my enhancement request would be to enhance  debugbreak()  to further deal with remote debugging, if possible.
In conclusion, using Termdebug for remote debugging seems to work fine, as long as one avoid to run continue when there are no breakpoints aand when working with Windows.
Sorry for the essay. :)

Possible workaround (on the user-side and not tested):
Download SendSignalCtrlC.exe (download link) and from powershell run SendSignalCtrlC.exe 12345, where 12345 is the gdb PID.
You could have something like:
if executable('SendSignalCtrlC') && has('win32')
var gdb_pid =  system($'powershell Get-Process -Name {gdb_bufname} | ForEach-Object { $_.Id }')
exe $"!SendSignalCtrlC.exe {gdb_pid}"
endif
to mimic CTRL_C on the gdb process.

BTW, are you familiar with the ch_log stuff. Just wondering if termdebug's log, in addition to gdb's might be useful.

BTW, are you familiar with the ch_log stuff. Just wondering if termdebug's log, in addition to gdb's might be useful.

Point. Yes, I run again and I sent few commands after continue. I filtered the debuglog file created by  ch_logfile('debuglog', 'w') with :g/ch_log() getting the following (excerpt after continue command) :
2875  16.162011 : ch_log(): sending to gdb: continue
2895  16.180201 : ch_log(): received from gdb: &"continue\n"
2897  16.180229 : ch_log(): received from gdb: ~"Continuing.\n"
2899  16.180320 : ch_log(): received from gdb: ^running
2901  16.180415 : ch_log(): received from gdb: *running,thread-id="all"
2902  16.180437 : ch_log(): program running
2904  16.180469 : ch_log(): received from gdb: (gdb)
2906  16.180482 : ch_log(): received from gdb: &"[remote] Sending packet: $vCont?#49\n"
2908  16.180499 : ch_log(): received from gdb: &"[remote] Packet received: vCont;c;C;s;S\n"
2910  16.180515 : ch_log(): received from gdb: &"[remote] packet_ok: Packet vCont (verbose-resume) is supported\n"
2912  16.180530 : ch_log(): received from gdb: &"[remote] Sending packet: $vCont;c#a8\n"
2914  16.180546 : ch_log(): received from gdb: &"[remote] wait: enter\n"
2916  16.180560 : ch_log(): received from gdb: &"[remote] wait: exit\n"
2968  16.695998 : ch_log(): received from gdb: &"[remote] wait: enter\n"
2970  16.696043 : ch_log(): received from gdb: &"  [remote] Packet received: O\n"
2972  16.696065 : ch_log(): received from gdb: &"[remote] wait: exit\n"
2988  17.205191 : ch_log(): received from gdb: &"[remote] wait: enter\n"
2990  17.205212 : ch_log(): received from gdb: &"  [remote] Packet received: O\n"
2992  17.205221 : ch_log(): received from gdb: &"[remote] wait: exit\n"
3009  17.720788 : ch_log(): received from gdb: &"[remote] wait: enter\n"
3011  17.720833 : ch_log(): received from gdb: &"  [remote] Packet received: O\n"
3013  17.720855 : ch_log(): received from gdb: &"[remote] wait: exit\n"
3033  18.231390 : ch_log(): received from gdb: &"[remote] wait: enter\n"
....
3724  29.321112 : ch_log(): sending to gdb: monitor halt
3738  29.491754 : ch_log(): received from gdb: &"[remote] wait: enter\n"
3740  29.491776 : ch_log(): received from gdb: &"  [remote] Packet received: O\n"
3742  29.491786 : ch_log(): received from gdb: &"[remote] wait: exit\n"
3758  30.003945 : ch_log(): received from gdb: &"[remote] wait: enter\n"
3760  30.003984 : ch_log(): received from gdb: &"  [remote] Packet received: O\n"
3762  30.004013 : ch_log(): received from gdb: &"[remote] wait: exit\n"
3790  30.519453 : ch_log(): received from gdb: &"[remote] wait: enter\n"
3792  30.519470 : ch_log(): received from gdb: &"  [remote] Packet received: O\n"
3794  30.519478 : ch_log(): received from gdb: &"[remote] wait: exit\n"
3829  31.028579 : ch_log(): received from gdb: &"[remote] wait: enter\n"
3831  31.028616 : ch_log(): received from gdb: &"  [remote] Packet received: O\n"
3833  31.028648 : ch_log(): received from gdb: &"[remote] wait: exit\n"
3867  31.540363 : ch_log(): received from gdb: &"[remote] wait: enter\n"
....
4158  36.178463 : ch_log(): sending to gdb: interrupt
4172  36.658684 : ch_log(): received from gdb: &"[remote] wait: enter\n"
4174  36.658727 : ch_log(): received from gdb: &"  [remote] Packet received: O\n"
4176  36.658765 : ch_log(): received from gdb: &"[remote] wait: exit\n"
4204  37.173201 : ch_log(): received from gdb: &"[remote] wait: enter\n"
4206  37.173229 : ch_log(): received from gdb: &"  [remote] Packet received: O\n"
4208  37.173249 : ch_log(): received from gdb: &"[remote] wait: exit\n"
4242  37.686056 : ch_log(): received from gdb: &"[remote] wait: enter\n"
4244  37.686093 : ch_log(): received from gdb: &"  [remote] Packet received: O\n"
4246  37.686111 : ch_log(): received from gdb: &"[remote] wait: exit\n"
4278  38.198646 : ch_log(): received from gdb: &"[remote] wait: enter\n"
4280  38.198677 : ch_log(): received from gdb: &"  [remote] Packet received: O\n"
4282  38.198695 : ch_log(): received from gdb: &"[remote] wait: exit\n"
4308  38.712366 : ch_log(): received from gdb: &"[remote] wait: enter\n"
...

... a more detail log excerpt follows

A more detailed log excerpt after continue:
16.162011 : ch_log(): sending to gdb: continue
16.162026 SEND on 6(in): 'continue
'
16.162331 : SafeState: Start triggering
16.163168 : looking for messages on channels
16.163183 : SafeState: back to waiting, triggering SafeStateAgain
16.180145 RECV on 6(out): '&"continue\n"

~"Continuing.\n"

^running

*running,thread-id="all"

(gdb)

&"[remote] Sending packet: $vCont?#49\n"

&"[remote] Packet received: vCont;c;C;s;S\n"

&"[remote] packet_ok: Packet vCont (verbose-resume) is supported\n"

&"[remote] Sending packet: $vCont;c#a8\n"

&"[remote] wait: enter\n"

&"[remote] wait: exit\n"

'
16.180174 RECV on 5(out): 'Deb'
16.180186 on 6: Invoking channel callback <SNR>166_GdbOutCallback
16.180201 : ch_log(): received from gdb: &"continue\n"
16.180220 on 6: Invoking channel callback <SNR>166_GdbOutCallback
16.180229 : ch_log(): received from gdb: ~"Continuing.\n"
16.180305 on 6: Invoking channel callback <SNR>166_GdbOutCallback
16.180320 : ch_log(): received from gdb: ^running
16.180404 on 6: Invoking channel callback <SNR>166_GdbOutCallback
16.180415 : ch_log(): received from gdb: *running,thread-id="all"
16.180437 : ch_log(): program running
16.180459 on 6: Invoking channel callback <SNR>166_GdbOutCallback
16.180469 : ch_log(): received from gdb: (gdb)
16.180475 on 6: Invoking channel callback <SNR>166_GdbOutCallback
16.180482 : ch_log(): received from gdb: &"[remote] Sending packet: $vCont?#49\n"
16.180492 on 6: Invoking channel callback <SNR>166_GdbOutCallback
16.180499 : ch_log(): received from gdb: &"[remote] Packet received: vCont;c;C;s;S\n"
16.180508 on 6: Invoking channel callback <SNR>166_GdbOutCallback
16.180515 : ch_log(): received from gdb: &"[remote] packet_ok: Packet vCont (verbose-resume) is supported\n"
16.180523 on 6: Invoking channel callback <SNR>166_GdbOutCallback
16.180530 : ch_log(): received from gdb: &"[remote] Sending packet: $vCont;c#a8\n"
16.180539 on 6: Invoking channel callback <SNR>166_GdbOutCallback
16.180546 : ch_log(): received from gdb: &"[remote] wait: enter\n"
16.180554 on 6: Invoking channel callback <SNR>166_GdbOutCallback
16.180560 : ch_log(): received from gdb: &"[remote] wait: exit\n"
16.180569 on 5: writing 23 bytes to terminal
16.180582 on 5: updating screen
16.182463 : SafeState: back to waiting, triggering SafeStateAgain
16.195817 : looking for messages on channels
16.195835 : SafeState: back to waiting, triggering SafeStateAgain
16.211375 RECV on 5(out): 'Debug: 1036 17153 gdb_server.c:375 gdb_log_incoming_packet()

: [stm32f4x.cpu] received packet: vCont?

Debug: 1037 17153 gdb_server.c:391 gdb_log_outgoing_packet()

: [stm32f4x.cpu] sending packet: $vCont;c;C;s;S#62

Debug: 1038 17153 gdb_server.c:375 gdb_log_incoming_packet()

: [stm32f4x.cpu] received packet: vCont;c

Debug: 1039 17153 gdb_server.c:3049 gdb_handle_vcont_packet(

): target stm32f4x.cpu continue

Debug: 1040 17168 target.c:1815 target_call_event_callbacks(

): target event 3 (resume-start) for core stm32f4x.cpu

Debug: 1041 17168 hla_target.c:448 adapter_resume(): adapter

_resume 1 0x00000000 0 0

Debug: 1042 17168 target.c:2171 target_free_all_working_area

s_restore(): freeing all working area'
16.211388 on 5: writing 796 bytes to terminal
16.211512 on 5: updating screen
16.214353 : SafeState: back to waiting, triggering SafeStateAgain
16.216088 : looking for messages on channels
16.216098 : SafeState: back to waiting, triggering SafeStateAgain
16.242656 RECV on 5(out): '
s_restore(): freeing all working areas

Debug: 1043 17184 target.c:2688 target_write_u32(): address:

0xe000edfc, value: 0x01000000

Debug: 1044 17184 hla_target.c:616 adapter_write_memory(): a

dapter_write_memory 0xe000edfc 4 1

Debug: 1045 17184 armv7m.c:174 armv7m_restore_context():

Debug: 1046 17184 target.c:2688 target_write_u32(): address:

0xe000edf8, value: 0x00000000

Debug: 1047 17184 hla_target.c:616 adapter_write_memory(): a

dapter_write_memory 0xe000edf8 4 1

Debug: 1048 17200 target.c:1815 target_call_event_callbacks(

): target event 2 (resumed) for core stm32f4x.cpu

Debug: 1049 17200 target.c:1815 target_call_event_callbacks(

): target event 4 (resume-end) for core stm32f4x.cpu

Debug: 1050 17200 target.c:1815 target_call_event_callbacks(

): target event 7 (gdb-start) for core stm32f4x.cpu

'
16.242687 on 5: writing 907 bytes to terminal
16.242852 on 5: updating screen
16.246454 : SafeState: back to waiting, triggering SafeStateAgain
16.258430 : looking for messages on channels
16.258484 : SafeState: back to waiting, triggering SafeStateAgain
16.695929 RECV on 6(out): '&"[remote] wait: enter\n"

&"  [remote] Packet received: O\n"

&"[remote] wait: exit\n"

'
16.695973 on 6: Invoking channel callback <SNR>166_GdbOutCallback
16.695998 : ch_log(): received from gdb: &"[remote] wait: enter\n"
16.696028 on 6: Invoking channel callback <SNR>166_GdbOutCallback
16.696043 : ch_log(): received from gdb: &"  [remote] Packet received: O\n"
16.696057 on 6: Invoking channel callback <SNR>166_GdbOutCallback
16.696065 : ch_log(): received from gdb: &"[remote] wait: exit\n"
16.696106 : SafeState: back to waiting, triggering SafeStateAgain
16.711681 RECV on 5(out): 'Debug: 1051 17668 gdb_server.c:391 gdb_log_outgoing_packet()

: [stm32f4x.cpu] sending packet: $O#4f

'
16.711705 : looking for messages on channels
16.711713 on 5: writing 126 bytes to terminal
16.711787 on 5: updating screen
16.714545 : SafeState: back to waiting, triggering SafeStateAgain
16.727337 : looking for messages on channels
16.727384 : SafeState: back to waiting, triggering SafeStateAgain
17.205110 RECV on 6(out): '&"[remote] wait: enter\n"

&"  [remote] Packet received: O\n"

&"[remote] wait: exit\n"

'
17.205163 on 6: Invoking channel callback <SNR>166_GdbOutCallback
17.205191 : ch_log(): received from gdb: &"[remote] wait: enter\n"
17.205208 on 6: Invoking channel callback <SNR>166_GdbOutCallback
17.205212 : ch_log(): received from gdb: &"  [remote] Packet received: O\n"
17.205217 on 6: Invoking channel callback <SNR>166_GdbOutCallback
17.205221 : ch_log(): received from gdb: &"[remote] wait: exit\n"
17.205247 : SafeState: back to waiting, triggering SafeStateAgain
17.220700 RECV on 5(out): 'Debug: 1052 18178 gdb_server.c:391 gdb_log_outgoing_packet()

: [stm32f4x.cpu] sending packet: $O#4f

'
17.220725 : looking for messages on channels
17.220733 on 5: writing 126 bytes to terminal
17.220768 on 5: updating screen
17.222504 : SafeState: back to waiting, triggering SafeStateAgain
17.236296 : looking for messages on channels
17.236312 : SafeState: back to waiting, triggering SafeStateAgain
17.720706 RECV on 6(out): '&"[remote] wait: enter\n"

&"  [remote] Packet received: O\n"

&"[remote] wait: exit\n"

'
17.720756 RECV on 5(out): 'Debug'
17.720767 on 6: Invoking channel callback <SNR>166_GdbOutCallback
17.720788 : ch_log(): received from gdb: &"[remote] wait: enter\n"
17.720823 on 6: Invoking channel callback <SNR>166_GdbOutCallback
17.720833 : ch_log(): received from gdb: &"  [remote] Packet received: O\n"
17.720847 on 6: Invoking channel callback <SNR>166_GdbOutCallback
17.720855 : ch_log(): received from gdb: &"[remote] wait: exit\n"
17.720865 on 5: writing 25 bytes to terminal
17.720879 on 5: updating screen
17.721118 : SafeState: back to waiting, triggering SafeStateAgain
17.736408 : looking for messages on channels
17.736440 : SafeState: back to waiting, triggering SafeStateAgain
17.751943 RECV on 5(out): '
Debug: 1053 18693 gdb_server.c:391 gdb_log_outgoing_packet()

: [stm32f4x.cpu] sending packet: $O#4f

'
17.751997 on 5: writing 127 bytes to terminal
17.752061 on 5: updating screen
17.754458 : SafeState: back to waiting, triggering SafeStateAgain
17.767580 : looking for messages on channels
17.767612 : SafeState: back to waiting, triggering SafeStateAgain
18.231309 RECV on 6(out): '&"[remote] wait: enter\n"

&"  [remote] Packet received: O\n"

&"[remote] wait: exit\n"

'
18.231356 RECV on 5(out): 'Debug:'
18.231367 on 6: Invoking channel callback <SNR>166_GdbOutCallback
18.231390 : ch_log(): received from gdb: &"[remote] wait: enter\n"
18.231419 on 6: Invoking channel callback <SNR>166_GdbOutCallback
18.231427 : ch_log(): received from gdb: &"  [remote] Packet received: O\n"
18.231437 on 6: Invoking channel callback <SNR>166_GdbOutCallback
18.231444 : ch_log(): received from gdb: &"[remote] wait: exit\n"
18.231454 on 5: writing 26 bytes to terminal
18.231468 on 5: updating screen
18.231693 : SafeState: back to waiting, triggering SafeStateAgain
18.247049 : looking for messages on channels
18.247087 : SafeState: back to waiting, triggering SafeStateAgain
18.262586 RECV on 5(out): '
Debug: 1054 19204 gdb_server.c:391 gdb_log_outgoing_packet()

: [stm32f4x.cpu] sending packet: $O#4f

'


DEVELOPMENT.rst

Thanks for this, @llgoncalves. I will accept this. But next time, please create separeted PRs.


[Runtime] Existential types marked as @objc should satisfy class requirement

Make sure that checkGenericRequirements properly enforces
"class requirement" constraint on the generic parameters.

Ah, the MetadataLookup.cpp code needs to use Casting.cpp's _conformsToProtocol. Sigh.

@DougGregor regarding _conformsToProtocol, it could be addressed separately right?

@DougGregor I think I made it the way you wanted, so please take a look!

@swift-ci please smoke test

@swift-ci please smoke test


gradio shape errors

trying any sample audio at all, no matter the format (wav, mp3, ..) I consistently get this error:
Traceback (most recent call last):
  File "/workspace/F5-TTS/venv/lib/python3.11/site-packages/gradio/queueing.py", line 622, in process_events
    response = await route_utils.call_process_api(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/workspace/F5-TTS/venv/lib/python3.11/site-packages/gradio/route_utils.py", line 323, in call_process_api
    output = await app.get_blocks().process_api(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/workspace/F5-TTS/venv/lib/python3.11/site-packages/gradio/blocks.py", line 2016, in process_api
    result = await self.call_function(
             ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/workspace/F5-TTS/venv/lib/python3.11/site-packages/gradio/blocks.py", line 1569, in call_function
    prediction = await anyio.to_thread.run_sync(  # type: ignore
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/workspace/F5-TTS/venv/lib/python3.11/site-packages/anyio/to_thread.py", line 56, in run_sync
    return await get_async_backend().run_sync_in_worker_thread(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/workspace/F5-TTS/venv/lib/python3.11/site-packages/anyio/_backends/_asyncio.py", line 2405, in run_sync_in_worker_thread
    return await future
           ^^^^^^^^^^^^
  File "/workspace/F5-TTS/venv/lib/python3.11/site-packages/anyio/_backends/_asyncio.py", line 914, in run
    result = context.run(func, *args)
             ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/workspace/F5-TTS/venv/lib/python3.11/site-packages/gradio/utils.py", line 846, in wrapper
    response = f(*args, **kwargs)
               ^^^^^^^^^^^^^^^^^^
  File "/workspace/F5-TTS/gradio_app.py", line 154, in infer
    generated, _ = base_model.sample(
                   ^^^^^^^^^^^^^^^^^^
  File "/workspace/F5-TTS/venv/lib/python3.11/site-packages/torch/utils/_contextlib.py", line 116, in decorate_context
    return func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/workspace/F5-TTS/model/cfm.py", line 120, in sample
    assert text.shape[0] == batch
           ^^^^^^^^^^^^^^^^^^^^^^

the same error prevents this space from working: https://huggingface.co/spaces/mrfakename/E2-F5-TTS and from-scratch git pulling this repo and setting it all up crashes it too.
I tried latest gradio and 4.44.1 (in case v5 is breaking everything).

a very possible reason is that you are using multichannel audio

do you happen to have a file that is guaranteed to work so I can test that? thanks

Any audio with mono channel is fine I thought, e.g. tests/ref_audio

Yes thats the issue- I had to convert audio to mono for it to work

can confirm! that indeed solves the issue, since ffmpeg is a dependency already, could maybe detect and auto convert to mono?

fixed in 83fbd34dc8ad890e9f43d4dd53382af9ac1fa9bb
# Audio
audio, sr = torchaudio.load(ref_audio)
if audio.shape[0] > 1:
    audio = torch.mean(audio, dim=0, keepdim=True)

And may need @fakerybakery 's help with hf space demo deployment~

Thanks! Pushed this to the Space

space and gradio both work now! thanks!


Edit hdinsight-hadoop-linux-use-ssh-unix.md

Edit complete.
On line 27, if "ssh-keygen" and "ssh" represent two utilities, the text should be changed from "This utility" to "These utilities."
The text "SSH establishes a secure connection to the cluster head node" (line 37) might imply a guarantee of security. Alternatives include "SSH establishes an encrypted connection to the cluster head node" or "SSH helps establish a secure connection to the cluster head node"--if either of those would be technically accurate.
The "Create an SSH key" internal link on line 175 didn't work when I tried it in the published article.
The text "enter a proxy name of HDInsight" (line 253) doesn't match what the screenshot shows. It shows "hdinsightproxy" as the name.
On line 273, the text entry "*headnode*" includes a slash mark, but the screenshot doesn't show a slash mark.

Hi @ShawnJackson, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (v-shawja). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, or work for Microsoft Open Technologies, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

Thanks Shawn, this looks OK to merge and I'll take care of changing the items called out above.


InterstellarFuelSwitch 1.5 contains a missing dll needed for the corr…

…ect operation of KSP
InterstellarFuelSwitch 1.5 contains a missing dll *Scale_Redist.dll) which needed for the correct operation of KSP people game will not function properly

Need to close the citation around InterstellarFuelSwitch-Core on line 6


2024/08/06: Jenkins regular patching cycle - update to 2.452.3

Process to follow: https://github.com/adoptium/infrastructure/blob/master/README.md#jenkins
Current version: 2.452.2
New version: 2.452.3
Jenkins event calendar
Previous patching issue: https://github.com/adoptium/infrastructure/issues/3636
Notes:
Part of https://github.com/adoptium/infrastructure/issues/3380

Notes:

Build name and description setter (2.4.2->2.4.3) does not have any change notes.
Scoring Load Balancer listed as having breaking changes. We're at 98 - latest in 114, breaking changes in 108 and 109
Many of the updates this time at for Enable Jenkins Security Scan (#2563) @strangelookingnerd
ThinBackup - same as last cycle
Credentials - Remove FileOnMasterKeyStroreSource and SECURITY-1322 - migration (#540) @jtnord in 1355 (We're on 1305, latest is 1371
Blue Ocean Executor Info now has DEPRECATED  as a prefix in the plugin title

General notes:

Only non-pipeline jobs (Including QPC/VPC) need to be stopped as they will prevent a restart

We have upgraded all three of the notable plugins above in this cycle, and backed up the old thinBackup.xml to ~/thinBackup.xml-BAK-240806 in the jenkins account

Non-pipeline job note added to https://github.com/adoptium/infrastructure/pull/3699.
There is already doc about backing up the war file, so that will not need to be added :-)

Noting that a subsequent upgrade was done on 8th August to 2.462.1 to address https://www.jenkins.io/security/advisory/2024-08-07/


Add support for toggleLineBreaks (2 spaces at the end of each line)

This is a very common case.
After pasting a paragraph, In order for the lines to be retained, 2 spaces need to be added at the end of each line.
It would be nice to support this.

Hi @ghuser, can you please explain a bit more? Could you give some sample input and output? Thanks!

See: https://daringfireball.net/projects/markdown/syntax#p
"When you do want to insert a  break tag using Markdown, you end a line with two or more spaces, then type return."
input (the input below is rendered as a b c in one line):
a
b
c

command:toggleLineBreaks
output (2 spaces at the end of each line):
a
b
c

The opposite should also work. E.g. remove two spaces from the end of each line.

Ahh, thanks for the clarification. I wasn't aware of this.


Accelerometer Options

Options :

Use the angular position to determine the angular rotations of the hand.
Use the angular velocity to determine the angular movements of the hand.
Preliminar Research:
MPU 9250 sensor give us the angular velocity. If we want to use the angular position, the MPU9250 will be doing continuous integral calculations.
Conclusion :
It's better use the angular velocity to reduce our calculations, having 11 analog inputs its important to optimize the information to comunicate.

With the euler angles will be enough to identify the hand orientation of static signs.


Add Upstream Issue as a Related Link

This commit updates the clone command to include the upstream issue url as a remoteLink as opposed to including it in the description body.
Looks like this:

obsoleted by #13, which includes the same capacity.


[Feature]: add support for Drupal and automatic updates

is it possible to add support for Composer command line tool in the dashboard?
and an option to update Drupal from the dashboard?

will create a new feature


Add sqlx database driver

The database drivers page is missing sqlx, a very commonly used database driver + toolkit with over 2.5k stars.

Thank you!


Support renderProp?

This should allow more control of the properties, i.e. pass the coordinate information to grandchildren, etc.
https://reactjs.org/docs/render-props.html

@Secretmapper - Thanks for suggesting the render-props pattern. I think if I were creating this library today, I might use it. Other than the convenience of passing props directly to deep descendants, I'm wondering what you think the benefits of the render-props pattern are over the currently implemented "decoration" pattern.

I'm not really sure 🤔. The real main use case I can think of is with props passing to deep descendants, as I have a use case where I need to keep track of the coordinates in a larger container, but only a deeper component handles the data.
There's already a way to do it in user space in the current API as I can write a component that wraps them in this way but it's a level of indirection that would be solved with renderProp.
If ever, do you think it best to migrate or keep both APIs and let the user decide? I'll try to submit PR soon.


Add NixOS options and darp6 support with new and updated packages

Hello, @stites!  Thanks very much for supporting System76 on NixOS.  I got a Darter recently and was really happy to see that you'd already done all this work.
Primarily, this PR adds support for the Darter Pro model darp6 currently being shipped by System76.  I've just completed an install of NixOS unstable based on these changes.  I have the keyboard backlight controls working, and the two kernel modules are loaded that were also loaded under Pop!_OS: system76-acpi-dkms and system76-io-dkms.
This also adds NixOS options for configuring System76 support under hardware.system76.
I also bumped the system76-dkms beta version from 1.0.4 to 1.0.6; initially I thought this driver was needed for darp6, but it seems it's not (despite there being an unreleased commit adding entries for it to the code, the module refuses to load).

Hi @khumba -- as I mentioned in one of the threads, this repo is no longer maintained (really need to update the readme). I've momentarily forgot about https://github.com/NixOS/nixos-hardware -- I think it might be best to put these contributions there.
I'm currently working against a couple of deadlines Happy to merge this in, if you do open up a PR at nixos-hardware, please ping me.

Hi @stites,
Thanks for merging.  I found that discussion after I'd opened this, so I appreciate you taking the time to get to this PR.  You're right, nixos-hardware would be a good home for these changes.  Once I get time I'll port them over.  (Kind of wish I'd switched the enable default to true before merging to avoid affecting existing users -- seems like the default for third-party modules is to be enabled by default, in contrast of official NixOS modules -- but oh well.)
Cheers!


Periods in taxonomies generates bad paths

See
http://discuss.gohugo.io/t/periods-in-taxonomies-are-generating-bad-paths/1258

I'm going to try to fix this. I don't know go: wish me luck... :smiley:

Good luck!
The URL handling in Hugo is a little bit too fragmented, but there should be test cases (see site_test.go and page_test.go - esp. the first) that will break when you add some periods.

Yes, I've discovered that the URL handling is rather complex and probably in need of streamlining.
I'm thinking the most straightforward way to do this is having a new simpler method on https://github.com/spf13/hugo/blob/master/hugolib/site.go#L1384. This new method would only know how to turn the "//" and "//" formats into pretty and ugly urls.

Yes, that sounds reasonable.

It appears that the rss feeds don't respect the ulgyURLs flag. Is this a bug?

No, that is by design.

I'm still working on this, as I have time. It's a rather tricky issue. I'm having trouble finding a non-invasive fix that doesn't cause side effects. And now I'm a couple months behind HEAD.
Anyway, just to let you know I'm not dead and that I'm still trying to fix this. I'd really like to upgrade from v0.12.


Fixes #171

Changed func (packets.Properties).Decode to return the total count of Properties bytes
including VBI header bytes.
Updated all invocations of (packets.Properties).Decode to use the changed return value directly.
Updated func TestDecodeProperties to check the changed return value

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

17 of 17 (100.0%)  changed or added relevant lines in 2 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.04%) to 98.55%

Files with Coverage Reduction
New Missed Lines
%

server.go
2
99.43%

Totals

Change from base Build<PHONE_NUMBER>:
-0.04%

Covered Lines:
5098

Relevant Lines:
5173

💛  - Coveralls

Thanks so much for incorporating the patch!


Error Message can Increase vertical size of status bar

I've noticed that when using a generic driver I setup for Cloudera hive I can get really long error messages when I get errors.
This has the side affect of making the status bar explode in size see screenshot.

Note when this happens on result panes that I've generated via control-\ i can just close the result window but for the main window I don't know to clear it without creating a new editor window.
Perhaps it sense to make it so that you can close the main result pane too?

I can't reproduce that (on Windows/Mac).
However I'll make status label single-line explicitly


Exception when try to run Bundler pre 1 or 2 on windows Gem::GemNotFoundException

I got this exception when trying to run "bundler install" or "bundler -v" on 2.0.0.pre.2 or pre1 on windows
C:/Ruby24-x64/lib/ruby/site_ruby/2.4.0/rubygems.rb:289:in find_spec_for_exe': can't find gem bundler (>= 0.a) with executable bundler (Gem::GemNotFoundException)         from C:/Ruby24-x64/lib/ruby/site_ruby/2.4.0/rubygems.rb:308:in activate_bin_path'
from C:/Ruby24-x64/bin/bundler:23:in `'

This seems answered. Closing.


how to disable field in redux-form

hi @erikras ,
could you tell me how to disable field in redux-form?
there is not disabled attr in form, if i want to skip one field's validate , or remove it in submit data,
i have to reset the fields and validate. hope you can help me .

Pass a prop to your form, then read it from validate:
<MyForm disabledFields={["foo", "bar"]} />
        ^^^^^^^^^^^^^
  This in Redux Form related!

function validate(values, props) {
  console.log(props.disabledFields) // foo, bar
}

@ooflorent thank you, i can not found the disabledFields in docs, could you tell me where is it?

Sorry I made a typo and my message wasn't clear!
There is no prop do do that. However, props are passed to validate so you can use them to mark some fields as disabled. In my example, I decided to create a prop named disabledFields to hold this information. It's up to you to name this property and instrument validate.