feat: gcd of N numbers

Feature Request
Describe the Feature Request

Add a function which allows to calculate the gcd of N numbers in an array. The function will need to handle all cases (including empty array).
Describe Preferred Solution

The function's signature will be the following:
fn gcd(ref n: Array::<felt>) -> felt

Takes as input the array of numbers to calculate the GCD for and returns their greatest common divisor.
The feature will include unit testing.
If the feature request is approved, would you be willing to submit a PR?
(Help can be provided if you need assistance submitting a PR)

[x] Yes
[ ] No

Merged


Support piping of filenames

Is your feature request related to a problem? Please describe.
I have an obsidian vault. I want to rag all *.md files. However, there are *.excalidraw.md files, and other md files I'd like to exclude.
Describe the solution you'd like
Ideally, I'd like to just use a command like find to select all the correct files and then pipe it into aichat.
Describe alternatives you've considered
Alternatively, I it would also be good if you could specify a file where each line is a path.
Additional context
Right now this does not work at all actually. There are so many files that it takes many minutes to just paste them at the interactive prompt. Even if I just select the correct directories it does not work. For some reason, I get:
...
Load  [82/82]
Error: Permission denied (os error 13)

After all the files have been loaded.

I tend not to support this feature.
When aichat receives a pipe, it uses it as the message text. This works well and I'm not planning on changing it, because it would be ambiguous or make the cli options too redundant.
add_documents can load complex document paths.

If you confirm that there is a problem with aichat add_document, please submit a new issue.


How to create new package

Hello. I am trying to define a new package but I cant find the correct way of doing it, looking at the builtins folder I am trying:
func main() {
	env := vm.NewEnv()
	anko_core.LoadAllBuiltins(env)
	env.Define("println", log.Println)
	c := env.NewPackage("cc")
	err := c.Define("test", 10)
	if err != nil {
		log.Fatalf("Define error: %v\n", err)
	}
	script := `
	var cc = import("cc")
	println(cc.test)
	`
	_, err = env.Execute(script)
	if err != nil {
		log.Fatal(err)
	}
}

However I keep getting package cc not defined.

currently, appending package dynamicaly was not supported. and NewPackage is a function to create new struct Package. now I added core.AddImportable. please use anko_core.AddImportable(c).


Online version file has wrong min version

http://ksp-avc.cybutek.net/version.php?id=666
"KSP_VERSION_MIN":{"MAJOR":0,"MINOR":8,"PATCH":1}}

This is promising compatibility with KSP 0.8.1 and later. Based on the forum thread it should be 1.8.0 instead.

Unfortunately ksp-avc.cybutek.net can't do pull requests; it should be:
"KSP_VERSION_MIN":{"MAJOR":1,"MINOR":8,"PATCH":0}}

This is messing up the CKAN metadata in KSP-CKAN/NetKAN#7972:
    "ksp_version_min": "0.8.1",

Tagging @sswelm since not everybody has GitHub notifications turned on for issues.

ok, I fixed it. Sorry for the mistake

Looks good, thanks!


feat: use fixed point crate for angle constant + folding

e.g. https://docs.rs/fixed/1.27.0/fixed/index.html

Yes, closing as not planned


Create template ISA for all Nodes

💡 Description

Initial draft completed and distributed to SBN for initial review.


Error For Stargaze airdrop in Mission #1, Claim initial 20%

Error
Type URL does not exist in the Amino message type register. If you need support for this message type, you can pass in additional entries to the AminoTypes constructor. If you think this message type should be included by default, please open an issue at https://github.com/cosmos/cosmjs/issues.
Is this because I use a ledger?
my address is stars1zdw82cflxz4hanmc55ermc649d5ec6rklzxjf

I also get this using Ledger Nano X

The same problem with ledger

Yes , I have the same problem, but other 2 actions I've done :)

Me too)))

Same, ledger Nano S

Same here with Ledger X

same.  i have a ledger and am getting this error

Stargaze needs to add amino support for this message in the blockchain and ensure they register the amino mapping for this protobuf message in the cosmjs app.
@shanev may be able to respond on this one

Same here, Also using a Ledger

Hey all, the Stargaze team is working on a fix this. We are aware of the issue. It has nothing to do with CosmJS and opening issues in this repo won't help.

@shanev I would suggest that they change the error message so it doesn't tell people to create issues here then.  :)

The error message is pretty good, but meant for a different audience. But yeah, not ideal this way. We'll figure something out and the Stargaze app is getting fixed in parallel.

Stargaze has fixed this issue: https://github.com/public-awesome/stargaze/pull/522, so this can be closed.

🚀🚀🚀🚀🌟🌠✨🌟🌠✨🌟🌠✨


onevnet release should return error if the IP to free is not part of the vnet

Author Name: Carlos Martín (Carlos Martín)
Original Redmine Issue: 3098, https://dev.opennebula.org/issues/3098
Original Date: 2014-07-28

None

current behavior as expected


fix README setImmediate typo

Coverage remained the same at 100.0% when pulling 2f6fa657ea7d0ddb3b861348ee3c3f06215b98c2 on alessioalex:patch-1 into 91b398ce124a8c48ab2618bc963fb4c8ec3b5f81 on unshiftio:master.

Coverage remained the same at 100.0% when pulling 2f6fa657ea7d0ddb3b861348ee3c3f06215b98c2 on alessioalex:patch-1 into 91b398ce124a8c48ab2618bc963fb4c8ec3b5f81 on unshiftio:master.

Woops, nice catch and thanks for the pull request!


Logging to Elastic Agent and logs are showing in unknown_service_node instead of services

[x] This only affects the JavaScript OpenTelemetry library
[ ] This may affect other libraries, but I would like to get opinions here first

I'm working with nodeSDK and pushing the data to otel-collector which will push the data to elastic agent
this is my tracker.js file
import { NodeSDK } from "@opentelemetry/sdk-node";
import { getNodeAutoInstrumentations } from "@opentelemetry/auto-instrumentations-node";
import { OTLPLogExporter } from "@opentelemetry/exporter-logs-otlp-http";
import {
	LoggerProvider,
	BatchLogRecordProcessor,
} from "@opentelemetry/sdk-logs";
import { OTLPTraceExporter } from "@opentelemetry/exporter-trace-otlp-http";
import { OTLPMetricExporter } from "@opentelemetry/exporter-metrics-otlp-http";
import { PeriodicExportingMetricReader } from "@opentelemetry/sdk-metrics";

const traceExporter = new OTLPTraceExporter({
	url: "http://localhost:4318/v1/traces",
});

const metricExporter = new OTLPMetricExporter({
	url: "http://localhost:4318/v1/metrics",
});

const sdk = new NodeSDK({
	serviceName: "App 1",
	traceExporter: traceExporter,
	metricReader: new PeriodicExportingMetricReader({
		exporter: metricExporter,
	}),
	instrumentations: [getNodeAutoInstrumentations()],
});

sdk.start();

const logExporter = new OTLPLogExporter({
	url: "http://localhost:4318/v1/logs",
});
const loggerProvider = new LoggerProvider({});

loggerProvider.addLogRecordProcessor(new BatchLogRecordProcessor(logExporter));

const logger = loggerProvider.getLogger("default", "1.0.0");

export { logger };

I have 2 apps pushing to one collector and then it pushes to single elastic agent. When metrics are pushed I can see them in their appropriate services but logs are being pushed to unknow_service_node service. I want the logs in their respective services how can i do that?

Found the solution:
By create a resource like this:
import { SEMRESATTRS_SERVICE_NAME } from "@opentelemetry/semantic-conventions";

const resource = Resource.default().merge(
	new Resource({
		[SEMRESATTRS_SERVICE_NAME]: "App 1",
	})
);

passing this to my loggers and Nodesdk worked


Fix breakpoint verification UI for the multi session case

Problem:
If two (or more) concurrent debug sessions return differing verification status for a (shared) breakpoint, then the outcome in the UI is not clear, e.g. we show the verification error for the breakpoint but he breakpoint actually verified fine in one of the sessions. This should not affect the ability to hit a verified breakpoint and miss an unverified breakpoint.
3 Possible solutions:

The UI shows multiple breakpoint stati with a new UI: if a BP has different stati, we do not show the red dot but something else (and a hover could show the individual stati per debug session).
Since VS Code has the concept of an active debug session, the UI could multiplex the different breakpoint stati: the UI reflects only the status of the active debug session.
we use voting, e.g. we show the breakpoint verified if it got verified in at least one session.

Today VS Code uses approach 3 but we should strive for solution 2.
In addition we should clarify/improve the DAP in order to support a "don't care" verification status.

I have refactored the breakpoint model such that now there are core breakpoint attributes which are edited by user explicitly and attributes on top which belong to a debug adapter session.
So now we use the second solution in your proposel above. And it can happen that breakpoints change properties once a user switches the active debug session (for example a breakpoint can appear as verified in one session and unverified in the other, but the line number and other things can changes as well)
Since I have reafactored a big part of the model we should keep our eyes open for regressions
fyi @roblourens

Removed text from June release notes:
In VS Code, breakpoints are shared between all debuggers and every debugger can decide whether to honor a breakpoint or adjust the breakpoint position, for example, move it to a different line. This results in dynamic state that is associated with a breakpoint for the duration of a debug session. With parallel debug sessions, there can even be multiple states per breakpoint. Previously, VS Code had merged the different states, which sometimes resulted in a confusing experience. With this release, the breakpoint UI now properly reflects only the state of the active debug session. Focusing on a different debug session properly updates the breakpoint state.


azure_sd_configs environment default not being applied

What did you do?
I have created system managed identity in Azure on my Prometheus VM and assigned Contributor permission on target Resource Group where is my second VM with node-exporter (configured on port 9100).
What did you expect to see?
Properly discovered second VM in Prometheus SD
What did you see instead? Under which circumstances?
I see error in Prometheus logs.
Environment
I run Prometheus on Azure VM.

System information:

Linux 5.0.0-1029-azure x86_64
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.2 LTS
Release:        18.04
Codename:       bionic

Prometheus version:

prometheus, version 2.15.2 (branch: HEAD, revision: d9613e5c466c6e9de548c4dae1b9aabf9aaf7c57)
build user:       root@688433cf4ff7
build date:       20200106-14:50:51
go version:       go1.13.5

Alertmanager version:

I don't have alertmanager

Prometheus configuration file:

global:
  evaluation_interval: 15s
  scrape_interval: 15s
  scrape_timeout: 10s

  external_labels:
    environment: prometheus.mydomain.com

rule_files:
  - /etc/prometheus/rules/*.rules

scrape_configs:
  - job_name: prometheus
    metrics_path: /metrics
    static_configs:
    - targets:
      - localhost:9090
  - file_sd_configs:
    - files:
      - /etc/prometheus/file_sd/node.yml
    job_name: node
  - job_name: bi
    metrics_path: /metrics
    static_configs:
    - targets:
      - 'working target here'
  - job_name: azure_service_discovery
    azure_sd_configs:
      - authentication_method: ManagedIdentity
        port: 9100
        subscription_id:  XXXXXXX

Logs:

level=error ts=2020-02-05T15:08:05.636Z caller=azure.go:317 component="discovery manager scrape" discovery=azure msg="Unable to get network interface" name=/subscriptions/XXX/resourceGroups/magenes-ccc/providers/Microsoft.Network/networkInterfaces/target-nic-name-here err="network.InterfacesClient#Get: Failure responding to request: StatusCode=403 -- Original Error: autorest/azure: Service returned an error. Status=403 Code=\"AuthorizationFailed\" Message=\"The client 'XXXXXXXXX' with object id 'XXXXXXXXXX' does not have authorization to perform action 'Microsoft.Network/networkInterfaces/read' over scope '/subscriptions/XXXXXXXXX/resourceGroups/magenes-ccc/providers/Microsoft.Network/networkInterfaces/target-nic-name-here' or the scope is invalid. If access was recently granted, please refresh your credentials.\""

It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided.

@brian-brazil it's not a question, but bug report in my opinion.

This looks like a permissions issue on your end, not a bug in Prometheus itself.

I solved it. environment parameter in azure_sd_config is actually required. I thought it's optional since it has default value = AzurePublicCloud.

Are you saying you explicitly needed to provide AzurePublicCloud as the value?

Exactly. Here's how my config looks like now:
- azure_sd_configs:
    - authentication_method: ManagedIdentity
      environment: AzurePublicCloud
      port: 9100
      subscription_id: 147faf87-d87f-4b62-bf0c-a004924c652f
    job_name: azure_service_discovery
``

Exactly.
Here's my fixed config:
- azure_sd_configs:
    - authentication_method: ManagedIdentity
      environment: AzurePublicCloud
      port: 9100
      subscription_id: XXXXX
    job_name: azure_service_discovery

That would be a bug then.

I can't reproduce this.

@szymon3 can you share the copy of the configuration as displayed in the UI when you don't define the environment field?

@simonpasquier
global:
  scrape_interval: 15s
  scrape_timeout: 10s
  evaluation_interval: 15s
  external_labels:
    environment: prometheus.XXXXX.eu
rule_files:
- /etc/prometheus/rules/*.rules
scrape_configs:
- job_name: prometheus
  honor_timestamps: true
  scrape_interval: 15s
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: http
  static_configs:
  - targets:
    - localhost:9090
- job_name: node
  honor_timestamps: true
  scrape_interval: 15s
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: http
  file_sd_configs:
  - files:
    - /etc/prometheus/file_sd/node.yml
    refresh_interval: 5m
- job_name: azure_service_discovery
  honor_timestamps: true
  scrape_interval: 15s
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: http
  azure_sd_configs:
  - authentication_method: ManagedIdentity
    port: 9100
    subscription_id: XXXXXXXXXXXXX
    refresh_interval: 5m

Just like @simonpasquier I can not reproduce this.
When I explicitely set it to empty, I get another error:
level=error ts=2020-02-09T14:15:33.074Z caller=refresh.go:79 component="discovery manager scrape" discovery=azure msg="Unable to refresh target groups" err="could not create Azure client: autorest/azure: There is no cloud environment matching the name \"\""

The error you pasted says:
If access was recently granted, please refresh your credentials.

Maybe you tried too soon?

Hmm, I tried this configuration locally and environment defaults to AzurePublicCloud for me.
# This is my original configuration file
global:
  scrape_interval: 15s
  scrape_timeout: 10s
  evaluation_interval: 15s
  external_labels:
    environment: prometheus.XXXXX.eu
scrape_configs:
- job_name: prometheus
  honor_timestamps: true
  scrape_interval: 15s
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: http
  static_configs:
  - targets:
    - localhost:9090
- job_name: azure_service_discovery
  honor_timestamps: true
  scrape_interval: 15s
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: http
  azure_sd_configs:
  - authentication_method: ManagedIdentity
    port: 9100
    subscription_id: XXXXXXXXXXXXX
    refresh_interval: 5m

Hmm, I tried this configuration locally and environment defaults to AzurePublicCloud for me.

That is what I said. And when it is REALLY not set (I set it to "" in the config), I have another error that the original report.

Discussed at bug-scrub: has been in "more-info-needed" state for 4 years so closing.


Invariants [v2]

This is basically Akshay's invariants series. https://github.com/NetSys/quilt/pull/493 can be closed.

I'm fine removing it as well.
On Thu, Sep 29, 2016 at 6:17 PM, kklin<EMAIL_ADDRESS>wrote:

@kklin commented on this pull request.
In stitch/query.go https://github.com/NetSys/quilt/pull/533:

@@ -20,51 +20,59 @@ type query struct {
str    string // Original query text.
}

+type queryError struct {
I'd be fine removing it, what do you think @ejj https://github.com/ejj?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NetSys/quilt/pull/533, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAl3lr-x6TaxW-LVVsVJJ0VR7qM73UM9ks5qvGMmgaJpZM4KIgUC
.

--
Ethan J. Jackson
cs.berkeley.edu/~ejj/

Added a commit that removes the query code.


ci(): Add code formatter

Add a script to format the scripts using Invoke-Formatter and Edit-DTWBeautifyScript.

What is the plan for this? Is it intended to get run locally as part of making changes or are we expecting it to be run as part of making pr/merging/etc?

I would like to add a CI and have that run the formatting check on PR and have that fail if there's an issue. Additionally I'd like the CI to run the linter on PR as well.


[SPONSOR] Implement the Kits dashboard

Implement the view for the Kits dashboard on the SPONSOR.
Populate it with some dummy data for the moment.
The data will will read from the database (kits table - you have to implement it).
Implement the filtering

Not able to see any changes.


What's a right way to include normal directions or color components in addition to positions (x,y,z)?

❓ Questions & Help

I am looking for the right way to add normal directions or color components in addition to positions (x,y,z). I can't find any example.
Is it ok just to increase the dimension of the position like the below pseudo code?
pos = ([torch.tensor(data['vertex'][axis]) for axis in ['x', 'y', 'z']])
nn =   ([torch.tensor(data['vertex'][axis]) for axis in ['nx', 'ny', 'nz']])
cc = ([torch.tensor(data['vertex'][axis]) for axis in ['r', z', 'b']])
pos = torch.cat((pos, nn, cc), 1)
data = Data(pos=pos)

Hi, we generally refer to x as our input features, but you can enhance data objects by any attribute you want, e.g., data.norm or data.color, or save everything in data.x by default. I do not recommend adding any other information to data.pos as their position due to semantic reasons. Hope this makes things clearer.


modified time on /proc/PID is not correct

Hello,
        let uptime = metadata.modified()?.elapsed()?;

That's wrong, the modified time in /proc is usually more recent than the start time of the process.
Linux exposes the proc tree "lazily". It's created on first read.
$ echo $$; date
2650914
2021-12-19T13:58:07 UTC
$ ls -ld /proc/$$; date
dr-xr-xr-x 9 myuser users 0 Dec 19 14:00 /proc/2650914
2021-12-19T14:00:28 UTC

Correct fallback implementation (for linux) should use /proc/PID/stat file content, column 22:

          (22) starttime  %llu
                 The time the process started after system boot.  In kernels before Linux 2.6,  this  value  was
                 expressed  in  jiffies.   Since  Linux  2.6,  the  value is expressed in clock ticks (divide by
                 sysconf(_SC_CLK_TCK)).

                 The format for this field was %lu before Linux 2.6.

And calculate it, i think you can use libc::_SC_CLK_TCK.

Thank you for this! I'll check this tomorrow.


Add Tuff to the mechanical extruder recipe

Add the Tuff recipe to the mechanical extruder or the CustomCobbleGen mod. Please

I don't know how you people stay out of format but I have a comment about why this feature wasn't added in one of the last updates. This feature is overpowered at the current state because you can crush the tuff in the crushing wheels and get quite a lot of resources easily which I kinda want to avoid so if this ends up getting added it will provide some basic resource automation but it will be best for building and not for resource gathering

The Gold and iron could be removed tbh the point is to be able to have a renewable zinc and copper source


Feature request: Inspection breakdown by package/type

It would be nice to have a view of the errors (or even just a summary of counts) by package as well as by type (in addition to the the flat list view.

(Note that the Jenkins Static Analysis plugin would automatically generate such breakdowns if the output was in Checkstyle format when scapegoat is run on a Jenkins CI server. See #107.)


fix(lsp): completions and hover quickinfo are not woking

Enhance document handling in LSP server by ensuring service availability and updating documents

After some testing, I do think that autocompletion behavior is improved. I still don't see completions after typing . (is this supposed to work with triggerCharacters now set, or does it require robust compilation?), but I do see them after typing the first character. Without the PR, I'm having trouble getting completions to work in general.

After some testing, I do think that autocompletion behavior is improved. I still don't see completions after typing . (is this supposed to work with triggerCharacters now set, or does it require robust compilation?), but I do see them after typing the first character. Without the PR, I'm having trouble getting completions to work in general.

Yes, if we want triggerCharacters to work, we need to perform some fault-tolerant compilation as mentioned in Discord. Otherwise, with the current work content directly, it will lead to many other problems.
We can support better prompts with a new pull request. However, before this, I think we need some unit tests about LSP like those in Volar to provide some functional guarantees.
https://github.com/vuejs/language-tools/blob/baa1319e37fd881967791e7ea84be73e02f8a0b3/packages/language-server/tests/completions.spec.ts#L10


Update greatest of three numbers.py

Hey, I just try to add some more value to the program by handling the ValueError as if someone give a value that is not integer or float than that Error in red colour don't seem good. So, handling it is a good practice.
Please review it and if it's ok than merge it.

Thank you.


Outdated luis_schema_version when parsing .lu file

Tool
Name: Ludown
Version: 1.3.2
OS: Windows 10
Describe the bug
The JSON output from ludown parse toluis command contains an outdated value for the luis_schema_version property.
To Reproduce

Run the ludown parse toluis command on this .lu file

# Intent
- test

The generated JSON file contains an outdated value for the luis_schema_version property. It should be 3.2.0, not 3.0.0

{
  "intents": [
    {
      "name": "Intent"
    }
  ],
  "entities": [],
  "composites": [],
  "closedLists": [],
  "regex_entities": [],
  "model_features": [],
  "regex_features": [],
  "utterances": [
    {
      "text": "test",
      "intent": "Intent",
      "entities": []
    }
  ],
  "patterns": [],
  "patternAnyEntities": [],
  "prebuiltEntities": [],
  "luis_schema_version": "3.0.0",
  "versionId": "0.1",
  "name": "demo",
  "desc": "",
  "culture": "en-us"
}

If I export an application from the LUIS portal, the value for the luis_schema_version property is 3.2.0.

Expected behavior
The same behaviour as exporting the application from the LUIS portal.
....
"luis_schema_version": "3.2.0"
....

@ionut-matei thank you for opening the issue.  we'll work to fix this in our 4.6 release.

@munozemilio @vishwacsena when we fix this lets put the fix into the Bf-CLI extension


feat(get demand factor settings): init new IO method PE-6894

:tada: This PR is included in version 2.6.0-alpha.4 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.6.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[AutoTVM] Fix hang/crash issues on feature extraction

Currently, if a schedule is invalid and makes tvm crashes during tvm.lower (e.g. failed tensorization), it will make the XGBTuner with feature_type="itervar" crashes or hangs.
This pr fixes it.

cc @cbalint13 @eqy


RCTRootView: updating appProperties does not work on iOS if bridge is still loading

[x] Review the documentation: https://facebook.github.io/react-native
[x] Search for existing issues: https://github.com/facebook/react-native/issues
[x] Use the latest React Native release: https://github.com/facebook/react-native/releases

Environment
Scanning folders for symlinks in /Users/veen011/Projects/Apps/AppPropertiesNoReRenderWhileBridgeIsLoading/node_modules (13ms)

  React Native Environment Info:
    System:
      ### Please let me know if you need this ###
    Binaries:
      Node: 10.5.0 - /usr/local/bin/node
      Yarn: 1.7.0 - /usr/local/bin/yarn
      npm: 6.1.0 - /usr/local/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 11.4, macOS 10.13, tvOS 11.4, watchOS 4.3
    IDEs:
      Android Studio: 3.1 AI-173.4819257
      Xcode: 9.4.1/9F2000 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.4.1 => 16.4.1
      react-native: 0.56.0 => 0.56.0

Short description
Follow up on https://github.com/facebook/react-native/issues/15938
Relevant documentation:

RCTRootView also provides a read-write property appProperties. After appProperties is set, the React Native app is re-rendered with new properties. The update is only performed when the new updated properties differ from the previous ones.
{...}
It is fine to update properties anytime. However, updates have to be performed on the main thread. You use the getter on any thread.

This is not the case, the app is not re-rendered if the bridge was still loading when the properties are updated.
Reproducible Demo
git clone git@github.com:teameh/AppPropertiesNoReRenderWhileBridgeIsLoading.git
cd AppPropertiesNoReRenderWhileBridgeIsLoading
react-native run-ios

or

create new RN app (react-native init MyProject)
apply this commit https://github.com/teameh/AppPropertiesNoReRenderWhileBridgeIsLoading/commit/981e953d45ff440bf4dde6bc24100a41822e53ec
react-native run-ios

The only change I made to the sample project is adding and updating some some props of the view:
    RCTRootView *rootView = [[RCTRootView alloc] initWithBundleURL:jsCodeLocation
                                                       moduleName:@"AppPropertiesNoReRenderWhileBridgeIsLoading"
-                                               initialProperties:nil
+                                               initialProperties:@{@"foo" : @"bar"}
                                                    launchOptions:launchOptions];
+
+  rootView.appProperties = @{@"foo" : @"qux"};

Which are used in the RN view:
<Text style={styles.welcome}>"{this.props.foo}"</Text>

Before reloading the project the 3rd text node on the view should display "qux" if it displays "bar" it means the props have not been updated.

I did some more digging and I think this is caused by the following:

In RCTRootView's initWithBridge method bundleFinishedLoading is always called even though the javascript might still be loading..

bundleFinishedLoading calls runApplication:bridge with the initial properties.

An instant later, when setAppProperties is called (and normally the app runs again) the bridge is still loading so the app won't run again:

- (void)setAppProperties:(NSDictionary *)appProperties
{
  RCTAssertMainQueue();

  if ([_appProperties isEqualToDictionary:appProperties]) {
    return;
  }

  _appProperties = [appProperties copy];

  if (_contentView && _bridge.valid && !_bridge.loading) {
    [self runApplication:_bridge];
  }
}

Somewhere after this the loading of the javascript completes and javaScriptDidLoad is called. But the bridge is the same and thus bundleFinishedLoading won't get called again, preventing the update:

- (void)javaScriptDidLoad:(NSNotification *)notification
{
  RCTAssertMainQueue();

  // Use the (batched) bridge that's sent in the notification payload, so the
  // RCTRootContentView is scoped to the right bridge
  RCTBridge *bridge = notification.userInfo[@"bridge"];
  if (bridge != _contentView.bridge) {
    [self bundleFinishedLoading:bridge];
  }
}

Tried to write some code that fixes this, see the PR.

Is there anything I can do to help fix this issue? No worries, I understand that it's hard to maintain a repo with 600+ open issues :)

I'm having the same issue, any updates?

Until this is fixed, a workaround is to listen to the RCTJavaScriptDidLoad and set the appProperties in there.
NotificationCenter.default.addObserver(forName: NSNotification.Name.RCTJavaScriptDidLoad, object: nil, queue: nil) {
    [weak self] _ in
    self?.setAppProperties()
}

@cpojer The issue has been closed, does that mean that this bug has been fixed

I think I am still experiencing this issue. The Objective C code is slightly different:
[[NSNotificationCenter defaultCenter] addObserverForName:RCTJavaScriptDidLoadNotification object:nil queue:nil usingBlock:^(NSNotification * _Nonnull note) {

}];

@jessedijkstra This is a react native repo, which means they close bugs whenever they want because otherwise they'd have too many to ever actually fix ;) Need to use the workaround.


How could I use vue-awesome for icons ?

I was testing many thing how could I use https://github.com/Justineo/vue-awesome with this table.
So far I was trying with thing like
        css: {
          table: {
            tableClass: '',
            ascendingIcon: 'chevron-up',
            descendingIcon: 'chevron-down',
            handleIcon: 'ellipsis-v',
            renderIcon: (classes, options) => {
              return `<icon name="${classes[1]}"></icon>`
            }
          }
        }

but for obvious reason the render does not compile the component icon.
Thanks in advance for this component!

@killua99 renderIcon only works with normal DOM element, so its purpose is to allow you to config Vuetable to work with CSS frameworks other than the default one.
However, you should be able to use vue-awesome inside __component and __slot special fields.

I'm using a __slot for actions, but I'm trying to figure out how to add the __slot inside the th table, and not a data cell.
I'll keep looking the examples but if you have something quick to show me, what I'm trying to achieve.
Again thanks

For the way I see it, I could do:
  import Vuetable from '../VuetableCustom'
  import VuetablePagination from '../VuetablePaginationCustom'
  import _ from 'lodash'
  import FilterBar from '../FilterBar'
  import Modal from '../Modal'

There I could use vue-awesome without any problem, is that right? then I could do something like <icon :name="renderIcon" />
I was trying to understand how could I use __component but I didn't figure out how edit  specially th

@killua99 Unfortunately, the current version of Vuetable does not support __slot nor __component rendering in the <thead> and <th>.  That would be available only for field component in the next version.
The only way to render icon in <th> in v1.7, you will have to use normal HTML like <i class="fa fa-xxxx"></i> instead.

Would you like a PR about it, or do you have some roadmap to include these things?

@killua99 It's already in the work. Just need to tidy up things and re-do the tutorial and documentation before I can publish it. Thanks for asking anyway. 👍


fix(aws lambda wrapper): allow exception without type

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


TypedFactory facility disposes singletons created during factory lifetime

I guess it was my mistake to make a PR with failing tests without accompanying issue in https://github.com/castleproject/Windsor/pull/61
In short, some instances registered with Singleton lifestyle could be disposed too early and later throw ObjectDisposedException. Like here

As @ivan-danilov mentioned in #61:

I believe it is very similar to IOC-345: TypedFactory creates its own release SubPolicy since the breaking change IReleasePolicy interface has a new method: IReleasePolicy CreateSubPolicy(), thus tracks singleton as part of this policy, while it should use parent container's one in order to avoid disposing singletons...
The test right above added one is almost the same except that it uses enclosing SubContainer over singleton factory and my test uses transient factory over singleton factory.

This obviously isn't just a problem for singleton components created inside a factory, but all other non-transient lifestyles will get prematurely disposed components.
I think It sounds like the fix would be for transient components created inside the factory to be tracked by the factory's release policy, and for everything else to get the parent IKernel's IReleasePolicy.
I don't know exactly how this would be implemented because TypedFactoryInterceptor.Resolve doesn't have the ComponentModel for the selected component, and it would only support one level deep (i.e. if the (transient) factory resolves a transient which in turn resolves a singleton).
If the factory is a different lifestyle (i.e. scoped) then tracking transients against the factory is a good idea to make sure they always get cleaned up, however what about components of the same lifestyle, should scoped components also get tracked against the factory or leave them for normal lifestyle decommission?
I think we need to decide what the behaviour of this facility should be on components it creates before trying to make a fix.
/cc @ivan-danilov @jberezanski @xlegalles @IanYates @petr-k @ghost @hammett @bindu-purhar @fir3pho3nixx (unsub if you aren't interested anymore)

I don't know exactly how this would be implemented because TypedFactoryInterceptor.Resolve doesn't have the ComponentModel for the selected component

My experimental PR is a proposal to walk through the flow of information we need in the TypedFactoryInterceptor by exposing a CreationContext using reflection(bad I know!) on the component, this also gives the SingletonLifestyleManager the ability to dump the creation context for disposals(ultimately when the container is disposed). Based on those two signals the TypedFactoryInterceptor can then inspect the existance of the CreationContext and then decide whether to dispose a singleton correctly. Nowhere near a solution yet, but hopefully a template for discussion.

Maybe I'm completely misunderstanding something, but this isn't a problem for the SingletonLifestyleManager, this defect applies to all lifestyles. We need to get the right release policy assigned for those components. What are your thoughts on the rest of my remarks in my last comment about component ownership (therefore decommission)?

Is it by chance fixed by #439 ?
At least it sounds close enough.
cc @jnm2 @jonorossi

Yes, I do believe it is!

Thanks, I'll close this issue. I'll leave it to you guys to determine if those unit tests add value on top of the tests added in #439.


RuntimeError: The GPU device does not support Double (Float64) operations!

when i run bert models to obtin embedding. The above error occurs.
i try exchange tensor type to float32,but useless,The above error still occurs

Might be related #430

#430 might be related DML tensor cannot be printed to the console directly for non-float64 supported machines.
I'm not printing out，i meas a770 not support float64 for calculation？

 So I was thinkg at during your run, some steps might trigger the datatype conversion like printing or creating tensor in double.

i meas a770 not support float64 for calculation
You can simply test with the following code snippet.

a = torch.randn(3,3).to(dml)
torch.add(a,a)

If the tiled error still occurs, then no, your device doesn't support float64 for DML.

If the tiled error still occurs, then no, your device doesn't support float64 for DML.
Note that calling torch.add(a,a) would try printing it to the console which might be what is failing.
Also noted here.


No script VM support?

Hi, I was just inspecting the engine, great work!
Just a tiny question, why haven't you included a built in script support (a VM) inside the engine for languages like Lua or Python?
Would love to hear your thoughts about this feature possibility in the engine.
Keep up the great job,
Ron

There are a couple of reasons why I don't want to pollute the code with VM's:

I want the engine to stay as close to the metal as possible (and sane)
Everybody has their own favorite language, so there is no clear choice what to add. Should I add all of them? Lots of people like Lua (and it is the most popular one), so I guess Lua would be the first choice but I hate it (arrays starting at 1, weird syntax etc.). Anybody can add bindings for their favorite scripting language to the engine if they want.
I am writing my games exclusively in C++ and I love it, so I don't need VM's.
I don't have time for it.


how to use pca model to fit a mesh

how to use pca model to fit a mesh.  the tutorial provides examples for icp and cpd registration using gp model,  i wonder if it would be better to fit with pca, then register with gp model, would that be more accurate or reliable?  how could one do that,  I did not find an example, e.g., optimizing pca coeffeicients.

ok, i seem to understand now. both gpmm_gp and gpmm_pca are the same in terms of using low-rank basis and covariance, so i just need to use gpmm_pca the same way as gpmm_gp for mesh registration.


"InvalidUserCodeException: Task.project Invocation Unsupported in buildIl2Cpp Task

When attempting to execute the :module-unity:buildIl2Cpp task in our Gradle build, we encounter an InvalidUserCodeException with the following error message:
Caused by: org.gradle.api.InvalidUserCodeException: Invocation of 'Task.project' by task ':module-unity:buildIl2Cpp' at execution time is unsupported.

Steps to Reproduce:

Run the Gradle build process that includes the :module-unity:buildIl2Cpp task.

Expected Behavior:
The :module-unity:buildIl2Cpp task should execute without errors.
Actual Behavior:
The task encounters an InvalidUserCodeException with the mentioned error message.
Additional Information:

This issue seems to be related to accessing the project property within the @TaskAction method of the buildIl2Cpp task.
We need assistance in refactoring the task to resolve this issue and ensure that it correctly configures and executes without invoking Task.project during execution.

We appreciate your detailed description and steps to reproduce the problem. Rest assured, we are actively working on resolving this issue promptly.
The error you're encountering, InvalidUserCodeException, is indeed related to accessing the project property within the @TaskAction method of the buildIl2Cpp task, which is currently unsupported and can lead to issues during task execution.
To address this, we'll need to refactor the buildIl2Cpp task to avoid accessing the project property during execution. Our goal is to make the necessary adjustments to the plugin code to ensure the task runs smoothly without invoking Task.project.
We will keep you updated on our progress and provide a new plugin version once this issue is resolved. In the meantime, if you have any additional information or insights that could help us, please feel free to share them.
Thank you for your patience and understanding. We are committed to resolving this issue as soon as possible. You can expect the fix in drifter-plugin version 1.0.0-alpha02.

Great news! 🎉 The issue regarding the implementation of Ceres Plugins has been successfully resolved with the implementation of the plugins in the latest pull request titled #6
All the required Ceres Plugins have been added, and they are now configured to reference the ceres-plugin version. This ensures that the project is up-to-date and ready to utilize these plugins as needed. 🚀

Thank you! We'll check it out once the next library version is released.


Fix a document error

Coverage remained the same at 19.191% when pulling 3fc76f50efa7f8ee452250b43b42308bff4ceb58 on wu-sheng-patch-1 into c56046d29a3ee07ba1d98ac34b9eefdd3ace098a on master.


Demo

The Guest id and password for you website ate not working i need a demo of you website give me its guest login

May I kindly request a reset of the demo-login, too, once again :)

Thx for the input, wrong password is fixed again.

I believe this is not working, again.

in 2017-06-12 , the password of guest was wrong, please fix it again~

Thx for the input, wrong password is fixed again.


calicoctl checksystem should examine etcd version and warn

There are some versions of etcd that have known problems.  As part of check-system we should check the running version of etcd and drop a warning if it isn't the version we recommend.
This means we would need to introduce the concept of a recommended version, do our testing with it, and be proactive about testing the new versions.

Who knows what the problems are? And what should the recommended version be?
We're not (yet) relying on new features so we just use 2.0.11 in the STs - can that be our minimum version https://github.com/coreos/etcd/releases/tag/v2.0.11
Do we need the concept of a minimum version (i.e. the oldest that will still work) and a recommended (the oldest that will perform well).

The issue is overstated (sorry!); the only known problem is version 2.0.9, in which Compare-and-swap fails using python-etcd.
We could track minimum and recommended, but that increases our testing burden.  I'm not sure we'll get enough out of it to justify it.


Replayer cron job for devnet

Adding this job is meant to reveal whether the archive node fix for bad nonces is working.

!ci-build-me

!ci-build-me


add min order quantity error to product cart processor

1. Why is this change necessary?
When adding a product to the cart, with a lower quantity than the product min order quantity, the line items quantity will be silently changed to the min order quantity, without any errors. This is especially unfavourable when working with the API, as there is no indication that the quantity was updated.
With this change, the behaviour is the same as when the quantity is updated to match the purchase steps.
2. What does this change do, exactly?

Adds a new Cart Error \Shopware\Core\Content\Product\Cart\MinOrderQuantityError
Refactors \Shopware\Core\Content\Product\Cart\ProductCartProcessor::validateStock to add an error to the cart when the quantity is modified to match the products min order quantity.
And some minor refactoring of the validateStock method

3. Describe each step to reproduce the issue or behaviour.
via API

add a product line item to the cart with a quantity of 1, where the min order quantity of the product is higher
the quantity will be updated to match the min order quantity without any errors

4. Checklist

[x] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[x] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/NEXT-19840
Please use this issue to track the state of your pull request.

Hey @NilsEvers thanks for your contribution, we've merged your changes! :tada: :blue_heart:


Provide a browser version

We should check browserify or something similar and generate a web standalone version too.

So clean-css has a Web interface now: https://jakubpawlowicz.github.io/clean-css/

And public repo with clean-css builds, so far only the latest: https://github.com/jakubpawlowicz/clean-css-builds


Disable whispers and not other channels

Is your feature request related to a problem? Please describe.
I only want to use this for guild chat because I'm always missing messages as a GM, but I do not want whispers to also be enabled.
Describe the solution you'd like
Give an option to only disable whispers like how you can enable/disable other specific channels.
Describe alternatives you've considered
Finding another addon or making my own just for this. I want it for the notification.
Additional context
None.

The core of the app is based on whispers. Everything else is an added feature. Your best option to accomplish what you're asking for is to create a filter under the whisper options, ignoring all messages:

Then disable all the behaviors in Window Behaviors for whispers.


(chore) Generate config reference for 2.8

Summary
Generate configuration reference for Gateway 2.8 from kong.conf.default.
Manually document admin_auto_create_rbac_token_disabled, as it is missing from the source file in the kong-ee repo. This one will need tech review.
Reason
Chore PR.
Testing
https://deploy-preview-3717--kongdocs.netlify.app/gateway/2.8.x/reference/configuration/

@mayocream can you please review the doc entry for admin_auto_create_rbac_token_disabled (based on https://github.com/Kong/kong-ee/pull/2988)? Normally it would be generated from kong.conf.default, but I noticed this parameter is missing from that file.

@mayocream can you please review the doc entry for admin_auto_create_rbac_token_disabled (based on https://github.com/Kong/kong-ee/pull/2988)? Normally it would be generated from kong.conf.default, but I noticed this parameter is missing from that file.

I am sorry I didn't noticed that the option added is not in the kong.conf.default file.
The new added option is in admin_gui_auth_conf on this page:
https://docs.konghq.com/gateway/2.7.x/configure/auth/kong-manager/oidc-mapping/

I am sorry I didn't noticed that the option added is not in the kong.conf.default file.
The new added option is in admin_gui_auth_conf on this page:
https://docs.konghq.com/gateway/2.7.x/configure/auth/kong-manager/oidc-mapping/

Ack. I'll move the info to that page.
Is admin_auto_create_rbac_token_disabled then an OpenID connect property?

@mayocream moved it, see https://github.com/Kong/docs.konghq.com/pull/3727.


CUDA: Lower launch overhead by launching kernel directly

Instead of configuring a driver.Function, which creates a copy, we can directly launch with the configuration - it seems that we don't really do anything with the configured copy other than launch with it then immediately forget it anyway. Using the code from Issue #3003 (See
https://github.com/numba/numba/issues/3003#issuecomment-627872661)., timings on my system (i7-6700K, RTX 8000) before:
$ ipython repro.ipy
31.3 µs ± 71.5 ns per loop (mean ± std. dev. of 7 runs, 10000 loops each)
46.1 µs ± 87.7 ns per loop (mean ± std. dev. of 7 runs, 10000 loops each)
56 µs ± 110 ns per loop (mean ± std. dev. of 7 runs, 10000 loops each)
64.8 µs ± 173 ns per loop (mean ± std. dev. of 7 runs, 10000 loops each)
73.2 µs ± 91.3 ns per loop (mean ± std. dev. of 7 runs, 10000 loops each)

After:
$ ipython repro.ipy
26.4 µs ± 78 ns per loop (mean ± std. dev. of 7 runs, 10000 loops each)
41.4 µs ± 185 ns per loop (mean ± std. dev. of 7 runs, 10000 loops each)
51.1 µs ± 511 ns per loop (mean ± std. dev. of 7 runs, 10000 loops each)
59.5 µs ± 193 ns per loop (mean ± std. dev. of 7 runs, 10000 loops each)
68 µs ± 87 ns per loop (mean ± std. dev. of 7 runs, 10000 loops each)

i.e. a saving of about 5µs per kernel launch. I plan to make further changes in subsequent PRs to eat away at other sources of overhead (_prepare_args, etc.) at some point in the future.

Very excited to see this!

Looking forward to the dream where we can launch CUDA kernels directly from nopython mode on the CPU.  :)

Looking forward to the dream where we can launch CUDA kernels directly from nopython mode on the CPU. :)

I made this PR because it seemed like a quick win, but it's really part of an experiment where I'm converting the kernel launches and argument preparation to be done by a generated wrapper function instead of using the Python driver API wrappers - I was doing this because I wanted boxing/unboxing extensions to work for CUDA, but as you point out, it's also a part of the road to being able to launch kernels from nopython mode.

/AzurePipelines run

/azp run

To add another data point: this PR seems to cut the runtime of GPU-STUMP down by 59%: https://github.com/TDAmeritrade/stumpy/issues/245

Should this close https://github.com/numba/numba/issues/3003 ?

I don't think so, there's plenty more opportunity after this PR.

I've just taken a look at the patch and think this is a good change, however, it is altering behaviour, question is... does it warrant a deprecation cycle as it's advertised public API? Could something like:
from numba import cuda

@cuda.jit
def foo():
    pass

foo_1_1 = foo.configure(1, 1)
foo_3_3 = foo[3, 3]

foo_1_1()
foo_3_3()

exist in the wild?

I've just taken a look at the patch and think this is a good change, however, it is altering behaviour, question is... does it warrant a deprecation cycle as it's advertised public API? Could something like:
from numba import cuda

@cuda.jit
def foo():
    pass

foo_1_1 = foo.configure(1, 1)
foo_3_3 = foo[3, 3]

foo_1_1()
foo_3_3()

exist in the wild?

This isn't changing a public API - the configure that is removed here is numba.cuda.cudadrv.Function.configure, not numba.cuda.compiler.Dispatcher.configure - your above example still works with the change in this PR.
I've just merged master and resolved conflicts - is this now ready for a buildfarm run?

I've just taken a look at the patch and think this is a good change, however, it is altering behaviour, question is... does it warrant a deprecation cycle as it's advertised public API? Could something like:
from numba import cuda

@cuda.jit
def foo():
    pass

foo_1_1 = foo.configure(1, 1)
foo_3_3 = foo[3, 3]

foo_1_1()
foo_3_3()

exist in the wild?

This isn't changing a public API - the configure that is removed here is numba.cuda.cudadrv.Function.configure, not numba.cuda.compiler.Dispatcher.configure - your above example still works with the change in this PR.

Apologies, I evidently misread this and thought it was referring to the dispatcher config.

I've just merged master and resolved conflicts - is this now ready for a buildfarm run?

I think so. Will schedule it.

Buildfarm ID: numba_smoketest_cuda_107.

Buildfarm ID: numba_smoketest_cuda_107.

Passed.


[SPARK-27416][SQL]:UnsafeMapData & UnsafeArrayData Kryo serialization breaks when two machines have different Oops size

What changes were proposed in this pull request?
Finish the rest work of https://github.com/apache/spark/pull/24317, https://github.com/apache/spark/pull/9030
a. Implement Kryo serialization for UnsafeArrayData
b. fix UnsafeMapData Java/Kryo Serialization issue when two machines have different Oops size
c. Move the duplicate code "getBytes()" to Utils.
How was this patch tested?
According Units has been added & tested

Can one of the admins verify this patch?

cc @cloud-fan @sandeep-katta @rxin

Can one of the admins verify this patch?

Can one of the admins verify this patch?


REFACTOR: Use the same structure as core topic-list-item

Updating the way docs-topic-list-item works in order for more functionality. I have changed the structure to match the way core renders it uses topic-list-item.hbs / topic-list-item.hbr
I have also added the same plugin outlets into the respective templates that core has.

Can you post before/after screenshots? I am assuming there are visual changes here.
Also, since this is touching on some Ruby files, do you need an engineer familiar with Docs to review this @jordanvidrine?

Can you post before/after screenshots? I am assuming there are visual changes here.
Also, since this is touching on some Ruby files, do you need an engineer familiar with Docs to review this @jordanvidrine?

Martin did the ruby work here. Im not sure a screenshot is necessary as this will look just like before, but with the ability to have an excerpt via theme component.
An excerpt will look like it does when it is seen on a regular topic-list-item.

@jordanvidrine I've updated the PR description + title to incorporate my description from the other PR, and closed that one off. @pmusaraj LMK if you want me to make any changes to the spec based on my other comment :+1:


Connect a frontal ultrasound sensor

As a safety advisor I want to be able to detect the distance to objects in front of the car in centimeters so that I can ensure the safety of the vehicle's collision avoidance.
Acceptance Criteria:
Be able to return distances between 1 cm and 100cm with an accuracy of 5 cm.

The sensor is connected but the calibration for distance measurements still needs to be calibrated. Some sort of measurement device is required for this task.

Can we close this issue?


Tales missing images

On the main browsing page two tales have broken image links.  I have cleared cache and these links still don't load. Is there a way we can store images used for tales somewhere so that we don't end up with broken links?

It's fixed. Thanks for the report!


undefined method 'buttons' on erb

hi guys,
I am building a 'one person-many address' form with cocoon in the erb/standard rail forms. Downloaded the  'project app' which runs normally, but when building my person-addresss form I found some small tricky problems.
1 - on https://github.com/nathanvda/cocoon/wiki/ERB-examples (Using standard rails forms topic)
the code used on 'projects/_form' is :
<% f.buttons do %>
<%= f.submit 'Save' %>
<% end %>
I could only make it work when I changed to

    <%= f.submit %>

2 - I notice that if I change the 'f' iterator on form to 'form' as usual on my rails 5 app I got some strange errors which vanish completely if I change to the old 'f'
attached is the working code and thank you very much. It's a great gem and for the great gem!! Next time i will improve using the haml and other improvements suggested on the read me.
cocoonTestPersonAddress.zip

Oops yes that is a type. f.buttons is from formtastic.
If you want to use form instead of f inside the partial, you will also have to specify the form_name parameter in your link_to_add_association call.

I already corrected the documentation. Closing due to inactivity.


Fixing the links to docs

Nice!
Could you please bump the patch version in VERSION? Then when this is merged, you can do a new release so PyPi is updated.

yessir!


DetermineBucketLocation method called even when region is defined

Currently, we are facing a problem in the AWS environment. Even though the aws.region is configured to eu-central-1, the S3ClientProvider always tries to first call determineBucketLocation. For this call, the DEFAULT_CLIENT is used.
 private static final S3AsyncClient DEFAULT_CLIENT = S3AsyncClient.builder() .endpointOverride(URI.create("https://s3.us-east-1.amazonaws.com")) .crossRegionAccessEnabled(true) .region(Region.US_EAST_1).build();
Unfortunately, in our case, the us-east endpoint is not reachable from our cluster, resulting in a timeout exception.
java.util.concurrent.ExecutionException: software.amazon.awssdk.core.exception.SdkClientException: Unable to execute HTTP request: connection timed out after 2000 ms: xxx.s3.us-east-1.amazonaws.com at software.amazon.nio.spi.s3.S3ClientProvider.generateClient(S3ClientProvider.java:85) at software.amazon.nio.spi.s3.S3FileSystem.client(S3FileSystem.java:415) at software.amazon.nio.spi.s3.S3FileSystemProvider.getCompletableFutureForHead(S3FileSystemProvider.java:653) at software.amazon.nio.spi.s3.S3FileSystemProvider.checkAccess(S3FileSystemProvider.java:607) at java.base/java.nio.file.Files.exists(Files.java:2440)
If I try to call the "DetermineBucketLocation" with manually created client configured to the "eu-central-1" it works as expected.
In general, it is not clear to me why there is even a need to call DetermineBucketLocation when the region is already defined…
Are we doing something wrong, or is this a bug?"

The problem lies with the fact that S3 buckets predate AWS regions. This means that neither the bucket arn nor the S3 URI will tell you which location the bucket is located in. Cross region access of buckets is fine so in theory we don't need to know where it is but all AWS requests must be signed following the Sigv4 spec which requires that the region in the signature matches the region in the bucket endpoint. S3 has an API called GetBucketLocation which can tell you the region of a bucket but all calls to GetBucketLocation must be directed to us-east-1. The library also uses some other tricks to determine a bucket location based on response headers but will try the above API call first.
In your case it seems it doesn't gracefully recover from the attempt to get the location from the GetBucketLocation api.
Some other complications - it looks like the GetBucketLocation api is deprecated in favor of the HeadBucket api but is supported for backward compatibility.
For this library we probably need to reconsider the strategy used when determining locations and likely we will need to make it configurable. In reality you usually know where your bucket is, except in the case of public buckets or buckets shared by another account that you don't own so a "just use my region" configuration would not be unreasonable.  So, not entirely a bug but certainly something we could see if we can improve.
As a work around, you might want to allow list https://s3.us-east-1.amazonaws.com at least for the purposes of calling the GetBucketLocation API. I'm not sure if your cluster can be that granular in it's access though.
A secondary work around would be to for the library and change the endpoint of the default client. You may also have to remove the logic that calls the GetBucketLocation api as well though?

I got similar error but not exactly sure if it's caused by this bug.
My app was deployed  a region which is not "us-east-1", and has Environment value "AWS_REGION" set to the app's region,   but got connection error which indicate the nio.file operation tried to connect to "xxxx.s3.us-east-1.amazonaws.com".
My sample code is below.  and use this library's 1.2.4.
        String s3BucketName = "xxx" //some bucket name which exists and accessble by the service running the code.
        URI s3BucketURI = createS3BucketURI(s3BucketName);
        S3FileSystemProvider provider = new S3FileSystemProvider();
        FileSystem = provider.newFileSystem(s3BucketURI);
        Path filePath = fileSystem.getPath(someBucketFilePathName);
        Writer writer = Files.newBufferedWriter(filePath);

Error was thrown in above new writer line.
Caused by: software.amazon.awssdk.core.exception.SdkClientException: Unable to execute HTTP request: Connect to xxxx.s3.us-east-1.amazonaws.com:443 failed: connect timed out
at software.amazon.awssdk.core.exception.SdkClientException$BuilderImpl.build(SdkClientException.java:111)
at

software.amazon.awssdk.core.internal.http.pipeline.stages.utils.RetryableStageHelper.setLastException(RetryableStageHelper.java:223)
at
software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallTimeoutTrackingStage.executeWithTimer(ApiCallTimeoutTrackingStage.java:80)
at software.amazon.awssdk.awscore.client.handler.AwsSyncClientHandler.execute(AwsSyncClientHandler.java:53)
at software.amazon.awssdk.services.s3.DefaultS3Client.getBucketLocation(DefaultS3Client.java:4005)
at software.amazon.awssdk.services.s3.S3Client.getBucketLocation(S3Client.java:6383)
at software.amazon.nio.spi.s3.S3ClientProvider.generateAsyncClient(S3ClientProvider.java:250)
at software.amazon.nio.spi.s3.S3ClientProvider.generateAsyncClient(S3ClientProvider.java:165)
at software.amazon.nio.spi.s3.S3FileSystem.client(S3FileSystem.java:195)
at software.amazon.nio.spi.s3.S3FileSystemProvider.newByteChannel(S3FileSystemProvider.java:321)
at java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:434)
at java.nio.file.Files.newOutputStream(Files.java:216)
I am not using S3 client directly, not sure how UQIQLP5 could manually invoke "DetermineBucketLocation" (which seems not a public method).   And Mark,  I don't quite follow your workaround 1 since my bucket was not in us-east-1 and somehow the library though my s3 bucket was.   and wonder if you could point me to an example with more details for workaround 2.  Thanks !

This could well be the same issue. BTW, what version of the library are you using?
Work around 1. would require figuring out what part of your network setup might be responsible for blocking the access to the us-east-1 endpoint.
Work around 2 (currently) would require forking the code, removing the region location check and then recompiling (not impossible but perhaps not simple).
Longer term I am thinking we might want to change the way that the library tries to resolve the bucket region, maybe by first assuming it will be in the same region and then if that doesn't work falling back to trying other approaches.

This could well be the same issue. BTW, what version of the library are you using?
Work around 1. would require figuring out what part of your network setup might be responsible for blocking the access to the us-east-1 endpoint.
Work around 2 (currently) would require forking the code, removing the region location check and then recompiling (not impossible but perhaps not simple).
Longer term I am thinking we might want to change the way that the library tries to resolve the bucket region, maybe by first assuming it will be in the same region and then if that doesn't work falling back to trying other approaches.

I am using version 1.2.4.
The "xxxx" in the error is s3 bucket name: Connect to xxxx.s3.us-east-1.amazonaws.com:443 failed: connect timed out .
For workaround 1,  even my cluster netowork is configured to allow to access us-east-1.amazonaws.com,  but there is no s3 bucket on that region.   So the error probably still exists with invalid bucket.
It seems I can not do workaround 2 which need forking code.
Thanks.

@hubfruser, @UQIQLP5 I think this should now be fixed in main for version 2.x.
Let me know if it is still an issue.

It seems it really helped. Thank you! I also noticed that you also changed the timeout length. I am not sure if it was intentional, though. When I tried it first in AWS, I was getting connection timeouts on that request. Once I changed that change back, it worked. It might have been caused by some unrelated problem in my setup, so I would have to test it again to confirm if this is a problem

Thanks, can you tell me which time out you want changed. I can fix that. Or you could make a pull request.

I think I found the location and have patched main. Let me know if this works.

Thanks for the fix, Mark.  But since I have to use  version 1.2.4 instead of 2.0.x,  I may have to wait my organization to upgrade to JRE from 8 to later version in order to use library 2.0.x which have the fix.    Also I am relying on maven to get official releases and not using forking to get the latest code.


[OCPCLOUD-1657] Add initial readme to repository root

This PR adds an initial readme with an overview of the project and some links out to enhancements that are relevant.
I've also added some basic instructions for setting up the project and getting it running on an existing cluster which I think could be useful for some.

/lgtm

Thanks for the review @damdo and good catch, updated as per your suggestions

/approve


Use curly brace literal instead of dict function

I know it's a silly little change. Though, surely it is better to use the literal syntax?

Coverage remained the same at 57.381% when pulling d838880c0b7e444c7e28b5353048d02862f796f1 on Saturn:dict-curly-brace-literal into d19ccb4646ed7a6af2e8a5fe583dbede18b57908 on randomchars:master.

+1 for OCD :smile:


[FEATURE] DataFrame type fails pydantic validation when using Spark Connect / Serverless

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

Pydantic enforces strict types. In the current implementation all Spark related logic (readers, writers, transforms, integrations) expect DataFrame (pyspark.sql.DataFrame) class as input or output. However in Spark Connect and subsequently in the Serverless compute the DataFrame class is pyspark.sql.connect.DataFrame, which causes errors in pydantic model validations.
Describe the solution you'd like

Model should except both native and connect DataFrames as a valid input / output
Describe alternatives you've considered

...
Additional context

...

Maybe take a look at here: https://github.com/Nike-Inc/koheesio/tree/33-feature-ensure-that-we-can-support-dbr-143lts

We will have to integrate changes you doing to this branch.

This commit especially: https://github.com/Nike-Inc/koheesio/commit/2e8620888264eec1d96c44431de092c9647cce02#diff-5a83c2ed86f340ff6a3110cd2a8a71ddd29947487301ad7941e4d99fbc8def6cR12

@mikita-sakalouski to be honest, I would prefer if we treat this a separate issue and merge to main as part of the #59 .
Reason being is that this small change only addresses the strict validation of the DF types, nothing else. It unlocks the next steps for the serverless compute poc.
The feature you are referring is much bigger and will probably require more testing and time.

@maxim-mityutko Looks like PR #63 is covering requested functionality, please check and close the request.

Solved with #63


errors in windows

Hi,
Im getting these errors in windows version:
package:media_kit_libs_windows_audio registered.
Debug service listening on ws://<IP_ADDRESS>:61298/GdMlX4ted4k=/ws
Syncing files to device Windows...
[ERROR:flutter/runtime/dart_vm_initializer.cc(40)] Unhandled Exception: MissingPluginException(No implementation found for method disposeAllPlayers on channel com.ryanheise.just_audio.methods)
#0      MethodChannel._invokeMethod (package:flutter/src/services/platform_channel.dart:332:7)
<asynchronous suspension>
#1      MethodChannelJustAudio.disposeAllPlayers (package:just_audio_platform_interface/method_channel_just_audio.dart:29:10)
<asynchronous suspension>

[ERROR:flutter/runtime/dart_vm_initializer.cc(40)] Unhandled Exception: MissingPluginException(No implementation found for method init on channel com.ryanheise.just_audio.methods)
#0      MethodChannel._invokeMethod (package:flutter/src/services/platform_channel.dart:332:7)
<asynchronous suspension>
#1      MethodChannelJustAudio.init (package:just_audio_platform_interface/method_channel_just_audio.dart:13:5)
<asynchronous suspension>
#2      AudioPlayer._setPlatformActive.setPlatform (package:just_audio/just_audio.dart:1401:13)
<asynchronous suspension>

any hint on how to solve this

Have you initialized the player with JustAudioMediaKit.ensureInitialized?

thanks, it works now.
the documentation is saying by default, windows and linux are enabled so maybe this needs to be updated

the documentation is saying by default, windows and linux are enabled so maybe this needs to be updated

It says that the windows and linux parameters are enabled (true) by default, but you still need to call the function, as it's necessary to register the plugin.


Update 16S copy numbers with the latest rrnDB data

Data downloaded from https://rrndb.umms.med.umich.edu/static/download (version 5.7)
Used a script to clean up existing copy_number tables and retain only rows for genuses not present in the rrnDB dataset https://gist.github.com/sh4nth/4fc3f4c541b62e2bc1086191403456e4
New records now include

Bacteria records representing 5716 species
Archaeal records representing 292 species

I couldn't find the source for your original 16S data. Is this from your own research group or some other public data? I have retained all the taxa that were present in your original dataset but not there in the rrnDB release, but I'm curious where that is from.
Thanks for creating and maintaining this project!

Hi @sh4nth, Thank you for contributing to this project.
For the 16S rRNA database, earlier we planned to include one of the existing databases like SILVA, GreenGenes, RDP or Eztaxon. But we found that each database has its own limitations. When we benchmark our tool using one of the existing databases, only a small proportion of query sequences was observed to map on these databases. Hence, we developed one consolidated database by merging and clustering all sequences from these databases.
For 16S rRNA gene copy numbers we just counted the number of 16S rRNA genes present in each genome of our reference sets.
Thank you for adding data from rrnDB. This will expand the copy number data as well. If you want any other information, please feel free to reply.

Can you just add "" in the organism name in the new rrnDB file?
In previous db files, I have followed the pattern like "genus_species_subspecies_strain". For making genus-level copy numbers, I have applied split on basis of "" in the main MicFunPred script.


Change logo and remove api key

Summary

...
Changes

...
...

Notes for Reviewers

...
Checklist

[ ] Scope: The referenced issue is addressed, there are no unrelated changes.
[ ] Compatibility: The changes are backwards compatible, they don't break existing deployments.
[ ] Testing: The changes are tested.
[ ] Documentation: Relevant documentation is added or updated.

Hi,
We'd like to ask if we are doing something wrong as when we create an integration through the template, the join accept path is not checked. We wrote it in the YML file.
Thank you.

Yes, I see it now - the path uses _ instead of -. You have join_accept instead of join-accept.

Yeah, I just submitted a PR to fix it https://github.com/TheThingsNetwork/lorawan-webhook-templates/pull/59


Fix: build target wasm32-unknown-emscripten

What does this PR do
Fix failed to build for target wasm32-unknown-emscripten with this error:
error[E0432]: unresolved import `self::consts`
  --> src/errno.rs:19:15
   |
19 | pub use self::consts::*;
   |               ^^^^^^ could not find `consts` in `self`

error[E0432]: unresolved import `self::Errno`
   --> src/errno.rs:198:15
    |
198 |     use self::Errno::*;
    |               ^^^^^ could not find `Errno` in `self`

error[E0432]: unresolved import `crate::errno::Errno`
 --> src/fcntl.rs:2:5
  |
2 | use crate::errno::Errno;
  |     ^^^^^^^^^^^^^^-----
  |     |             |
  |     |             help: a similar name exists in the module: `errno`
  |     no `Errno` in `errno`

error[E0432]: unresolved import `crate::errno::Errno`
 --> src/sys/signal.rs:3:5
  |
3 | use crate::errno::Errno;
  |     ^^^^^^^^^^^^^^-----
  |     |             |
  |     |             help: a similar name exists in the module: `errno`
  |     no `Errno` in `errno`

error[E0432]: unresolved import `crate::errno::Errno`
 --> src/unistd.rs:3:5
  |
3 | use crate::errno::Errno;
  |     ^^^^^^^^^^^^^^-----
  |     |             |
  |     |             help: a similar name exists in the module: `errno`
  |     no `Errno` in `errno`

error[E0432]: unresolved import `errno::Errno`
   --> src/lib.rs:205:5
    |
205 | use errno::Errno;
    |     ^^^^^^^-----
    |     |      |
    |     |      help: a similar name exists in the module: `errno`
    |     no `Errno` in `errno`

For more information about this error, try `rustc --explain E0432`.
error: could not compile `nix` (lib) due to 6 previous errors

To pass the build, I made the following changes:

Added the errno::errno_location function for Emscripten.
Uses the same errno::consts module as Linux.

Checklist:

[x] I have read CONTRIBUTING.md
[x] I have written necessary tests and rustdoc comments
[ ] A change log has been added if this PR modifies nix's API

CI fixed in #2478, please rebase your branch:)

BTW, perhaps we can have a changelog for this, please see CONTRIBUTING.md on how to add one, something like this would suffice:

2477.added.md

Add the support for Emscripten.

Ahh, our Cirrus CI has been quite unstable recently...

Damn it, I think our Cirrus CI is broken, which is definitely not related to this PR, I will take a look later:<

Weird, Cirrus CI works fine in other PRs, let's merge this PR anyway!


WIP: Update onkyo-eiscp to 1.2.5

Description:
This updates the onkyo-eisco package to 1.2.5.
Changelog:

1.2.5 (2018-04-20)
- Fix some commands.
- Better handle slow receivers.
- Add a socket timeout.

Checklist:

[ ] The code change is tested and works locally.
[ ] Local tests pass with tox. Your PR cannot be merged unless tests pass

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.


Surfing System

I decided to create a new issue to discuss how to properly implement surfing. I created a modified version of the example map to test with. Furthermore, I've found that using 30 to 40 percent of the add.x and add.z velocity gets us somewhat close to the desired effects, but there are still some issues. I'll have to look further into how surfing works in the original source engine, and how others have simulated it.

https://www.ryanliptak.com/blog/rampsliding-quake-engine-quirk/#what-about-surfing-like-in-counter-strike-surf-maps

I think I've made some progress, albeit very minor. According to what I can find documenting the Quake and Source engines, I added a check in the acceleration function to return a zero vector if the result is greater than max_air_speed. This seems to result in slightly better surf physics, in that holding W will make you lose velocity, while only strafing will increase it. However, I'm still having issues debugging why you can still accelerate directly up the slope by strafing into it. From what I've found documenting the physics mathematics of half-life, there's some calculation related to the surface normal that should be modifying and slowing the player velocity, but I've yet to properly recreate it.

Here are some more resources for anyone interested:
https://www.jwchong.com/hl/
https://www.jwchong.com/hl/strafing.html
https://www.jwchong.com/hl/surfing.html

Nice, feel free to open a PR when ready. Can even be a draft for now.

Alright. I'll push what I've gotten working for now.

I'm still studying the physics math of Half-Life, but I found this interesting formula for calculating the collision of non-player entities:
$v'=v-b(Cb,Ke)(v \cdotp \hat{n})\hat{n}$
Where:
$v'$ is the new velocity
$v$ is the current velocity
$b(Cb,Ke)$ is the function for the bounce coefficient
$\hat{n}$ is the plane normal of the colliding surface

Another piece of interest, is that there's a few different entity movement types we could theoretically implement, but I'm not sure if they're in scope for this project, as to my understanding we're only focusing on the player entity:
https://www.jwchong.com/hl/entity.html#movement
Maybe I'll eventually make a fork for other entities. I don't know.


Removed unneeded MIME text before base64

This data in front of base64 encoded images is absolutely unneeded and brakes decoding (for example, for python standard libraries)


No video formats found

Checklist

[ ] I'm reporting a broken site support issue
[x] I've verified that I'm running youtube-dl version 2<IP_ADDRESS>298
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar bug reports including closed ones
[x] I've read bugs section in FAQ

Verbose log

❯ .\youtube-dl -F https://youtu.be/Z5-rdr0qhWk?si=Hg_dbGgMSsDSSS7Y --verbose
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-F', 'https://youtu.be/Z5-rdr0qhWk?si=Hg_dbGgMSsDSSS7Y', '--verbose']
[debug] Encodings: locale cp1252, fs mbcs, out cp850, pref cp1252
[debug] youtube-dl version 2<IP_ADDRESS>298 (single file build)
** This build is unofficial daily builds, provided for ease of use.
** Please do not ask for any support.
[debug] Python 3.4.4 (CPython AMD64 32bit) - Windows-10-10.0.19041 - OpenSSL 1.0.2d 9 Jul 2015
[debug] exe versions: none
[debug] Proxy map: {}
[youtube] Z5-rdr0qhWk: Downloading webpage
[youtube] Z5-rdr0qhWk: Downloading API JSON
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
ERROR: No video formats found; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "D:\a\youtube-dl\youtube-dl\youtube_dl\YoutubeDL.py", line 825, in wrapper
  File "D:\a\youtube-dl\youtube-dl\youtube_dl\YoutubeDL.py", line 846, in __extract_info
  File "D:\a\youtube-dl\youtube-dl\youtube_dl\extractor\common.py", line 535, in extract
  File "D:\a\youtube-dl\youtube-dl\youtube_dl\extractor\youtube.py", line 2121, in _real_extract
  File "D:\a\youtube-dl\youtube-dl\youtube_dl\extractor\common.py", line 1375, in _sort_formats
youtube_dl.utils.ExtractorError: No video formats found; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Description

Trying to download the audio of a YouTube video. (As I have for several years, using the same command format)
youtube-dl -f 140 https://youtu.be/Z5-rdr0qhWk?si=GQzP0TI3DqEMOc2U
I have the latest version.
Other commands fail in the same way.
Summary trace:
a long list of "WARNING: unable to extract player URL"
followed by "ERROR: No video formats found"

This seems to be another manifestation of #32499 and fixed by the WIP YT extractor that fixes that:
$ python -m youtube_dl -v -F 'https://youtu.be/Z5-rdr0qhWk?si=GQzP0TI3DqEMOc2U'
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'-v', u'-F', u'https://youtu.be/Z5-rdr0qhWk?si=GQzP0TI3DqEMOc2U']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2021.12.17
[debug] Git HEAD: 86e3cf5e5
[debug] Python 2.7.15 (CPython i686 32bit) - Linux-6.1.0-11-686-pae-i686-with-debian-12.1 - OpenSSL 1.1.1a  20 Nov 2018 - glibc 2.1.3
[debug] exe versions: none
[debug] Proxy map: {}
[youtube] Z5-rdr0qhWk: Downloading webpage
[youtube] Z5-rdr0qhWk: Downloading player c153b631
[debug] [youtube] Decrypted nsig VtPNynxZT9NIRusX => inur3uwD_Gn-KQ
[debug] [youtube] Decrypted nsig jrknynRP_TZIcnRl => CnkX3H-tkccp6w
[info] Available formats for Z5-rdr0qhWk:
format code  extension  resolution note
249          webm       audio only tiny   49k , webm_dash container, opus  (48000Hz), 1.32MiB
250          webm       audio only tiny   65k , webm_dash container, opus  (48000Hz), 1.75MiB
140          m4a        audio only tiny  127k , m4a_dash container, mp4a.40.2 (44100Hz), 3.38MiB
251          webm       audio only tiny  130k , webm_dash container, opus  (48000Hz), 3.46MiB
160          mp4        192x144    144p   11k , mp4_dash container, avc1.4d400c, 30fps, video only, 326.04KiB
278          webm       192x144    144p   24k , webm_dash container, vp9, 30fps, video only, 666.09KiB
394          mp4        192x144    144p   33k , mp4_dash container, av01.0.00M.08, 30fps, video only, 910.98KiB
133          mp4        320x240    240p   17k , mp4_dash container, avc1.4d400d, 30fps, video only, 482.46KiB
242          webm       320x240    240p   49k , webm_dash container, vp9, 30fps, video only, 1.31MiB
395          mp4        320x240    240p   67k , mp4_dash container, av01.0.00M.08, 30fps, video only, 1.80MiB
134          mp4        480x360    360p   37k , mp4_dash container, avc1.4d401e, 30fps, video only, 1008.61KiB
243          webm       480x360    360p   86k , webm_dash container, vp9, 30fps, video only, 2.30MiB
396          mp4        480x360    360p  111k , mp4_dash container, av01.0.01M.08, 30fps, video only, 2.95MiB
135          mp4        640x480    480p   89k , mp4_dash container, avc1.4d401e, 30fps, video only, 2.38MiB
244          webm       640x480    480p  137k , webm_dash container, vp9, 30fps, video only, 3.65MiB
397          mp4        640x480    480p  189k , mp4_dash container, av01.0.04M.08, 30fps, video only, 5.03MiB
18           mp4        480x360    360p  162k , avc1.42001E, 30fps, mp4a.40.2 (44100Hz) (best)
$

@DonaldsoJo wrote:

I have the latest version.

... You think you are:
[debug] youtube-dl version 2<IP_ADDRESS>298 (single file build)
** This build is unofficial daily builds, provided for ease of use.
** Please do not ask for any support.

... but, in reality, you're NOT!
The "unofficial daily builds" that are being auto-released by GitHub Actions and are found in below repo:
https://github.com/ytdl-patched/youtube-dl/tags
are, in fact, being compiled on quite old yt-dl source code, specifically master-git-20230617-g07af479 from 2.5 months ago...
As pinned issue #30839 explains (which you should've carefully read prior to filing a new issue here 😜 ), having the "latest" yt-dl version now implies you have migrated to the "nightly" update channel,
https://github.com/ytdl-org/ytdl-nightly/releases/latest
which now is at version 2023.08.07 ; having done that, you'd have probably still encountered #32499 (as attested by @brickinthewall4138), but, at least, you'd have truly been on "latest" 😉 ...
@nicolaasjan wrote:

Same here.

... Until dirkf kindly divulges the "WIP YT extractor" code 😄 , I "shoehorned" in yt-dl's youtube.py the "downstream" fix from https://github.com/yt-dlp/yt-dlp/commit/378ae9f9fb8e8c86e6ac89c4c5b815b48ce93620
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--ffmpeg-location', '.\\FFmpeg', '--external-downloader-args', '-v 8 -stats', '-vF', 'https://youtu.be/Z5-rdr0qhWk?si=GQzP0TI3DqEMOc2U']
[debug] Encodings: locale cp1253, fs mbcs, out cp737, pref cp1253
[debug] youtube-dl version 2<IP_ADDRESS>4
[debug] Lazy loading extractors enabled
[debug] Single file build
[debug] Python 3.4.10 (CPython x86 32bit) - Windows-Vista-6.0.6003-SP2 - OpenSSL 1.0.2k  26 Jan 2017
[debug] exe versions: ffmpeg n6.1-dev-1700-N-111584-ga4e6168, ffprobe n6.1-dev-1700-N-111584-ga4e6168, phantomjs 2.1.1, rtmpdump 2.4
[debug] Proxy map: {}
[youtube] Z5-rdr0qhWk: Downloading webpage
[debug] [youtube] Decrypted nsig TFhF98o5a6EtYjbMd => KGICjS3bV6b6YA
[debug] [youtube] Decrypted nsig 0GmbWnEK-1sF-qZNI => tZ2cm3YsAW0_uQ
[info] Available formats for Z5-rdr0qhWk:
format code  extension  resolution note
249          webm       audio only tiny   49k , webm_dash container, opus  (48000Hz), 1.32MiB
250          webm       audio only tiny   65k , webm_dash container, opus  (48000Hz), 1.75MiB
140          m4a        audio only tiny  127k , m4a_dash container, mp4a.40.2 (44100Hz), 3.38MiB
251          webm       audio only tiny  130k , webm_dash container, opus  (48000Hz), 3.46MiB
160          mp4        192x144    144p   11k , mp4_dash container, avc1.4d400c, 30fps, video only, 326.04KiB
278          webm       192x144    144p   24k , webm_dash container, vp9, 30fps, video only, 666.09KiB
394          mp4        192x144    144p   33k , mp4_dash container, av01.0.00M.08, 30fps, video only, 910.98KiB
133          mp4        320x240    240p   17k , mp4_dash container, avc1.4d400d, 30fps, video only, 482.46KiB
242          webm       320x240    240p   49k , webm_dash container, vp9, 30fps, video only, 1.31MiB
395          mp4        320x240    240p   67k , mp4_dash container, av01.0.00M.08, 30fps, video only, 1.80MiB
134          mp4        480x360    360p   37k , mp4_dash container, avc1.4d401e, 30fps, video only, 1008.61KiB
243          webm       480x360    360p   86k , webm_dash container, vp9, 30fps, video only, 2.30MiB
396          mp4        480x360    360p  111k , mp4_dash container, av01.0.01M.08, 30fps, video only, 2.95MiB
135          mp4        640x480    480p   89k , mp4_dash container, avc1.4d401e, 30fps, video only, 2.38MiB
244          webm       640x480    480p  137k , webm_dash container, vp9, 30fps, video only, 3.65MiB
397          mp4        640x480    480p  189k , mp4_dash container, av01.0.04M.08, 30fps, video only, 5.03MiB
18           mp4        480x360    360p  162k , avc1.42001E, 30fps, mp4a.40.2 (44100Hz) (best)

@Vangelis66 thanks for the clarification.
I admit, I just used the -U option and assumed I had the "latest". Mea culpa.
But, as you expected, the nightly build didn't actually fix the problem. :-(

Absent divulging, cookies should work round the issue per #32499.

... Until dirkf kindly divulges the "WIP YT extractor" code 😄 , I "shoehorned" in yt-dl's youtube.py the "downstream" fix from yt-dlp/yt-dlp@378ae9f

Thanks for this!🌻
I applied the change in youtube.py and compiled again.
No error now. 🙂

I tried the --cookies switch as described in the FAQ (search for cookies).
This did indeed fix the problem. So many thanks for the suggestion.
I was using Chrome and got the "get cookies.txt LOCALLY" extension.
I opened YouTube and the video I wanted.
Then created a cookies.txt file using the extension.
Then the following command line (and result):

youtube-dl --cookies .\www.youtube.com_cookies.txt -f 140 https://youtu.be/Z5-rdr0qhWk?si=-N0irE61t6FmzdSe
[youtube] Z5-rdr0qhWk: Downloading webpage
[dashsegments] Total fragments: 1
[download] Destination: @TheCarsOfficial ― JUST WHAT I NEEDED (1978)-Z5-rdr0qhWk.m4a
[download] 100% of 3.38MiB in 00:00
WARNING: Z5-rdr0qhWk: writing DASH m4a. Only some players support this container. Install ffmpeg or avconv to fix this automatically.

I'm ok with that kind of workaround, but it would be nice if youtube-dl worked without faffing with cookies.
Thanks for the help.
Should I close this issue? Or leave it open?


stabilise fn_args_density

I think fn_args_density passes the conditions to be made stable.

Is the default value correct ?

Tall is the best compromise for formatting arguments by default:

horizontally when there is enough space
vertically otherwise

The design and implementation of the option are sound and clean.

An enum Density is used so it is easy to add a new kind of density later if needed without breaking backward compatibility. That enum is mapped internally to another enum called ListTactic, the core logic is limited to the function lists::definitive_tactic which looks clear.
The enum Density is used to rewrite where clauses which should probably be decoupled. However, this doesn't prevent stabilisation: it looks like it can be replaced straightforwardly by a boolean though:
src/items.rs
703-            &generics.where_clause,
704-            context.config.brace_style(),
705-            Shape::legacy(where_budget, offset.block_only()),
706:            Density::Vertical,
707-            "{",
708-            where_span_end,
709-            self_ty.span.hi(),
--
1045-
1046-        // Rewrite where-clause.
1047-        if !generics.where_clause.predicates.is_empty() {
1048:            let where_density = if context.config.indent_style() == IndentStyle::Block {
1049:                Density::Compressed
1050-            } else {
1051:                Density::Tall
1052-            };
1053-
1054-            let where_budget = context.budget(last_line_width(&result));
--
1063-                &generics.where_clause,
1064-                context.config.brace_style(),
1065-                Shape::legacy(where_budget, offset.block_only()),
1066:                where_density,
1067-                "{",
1068-                None,
1069-                pos_before_where,
--
1382-                &generics.where_clause,
1383-                context.config.brace_style(),
1384-                Shape::legacy(where_budget, offset.block_only()),
1385:                Density::Compressed,
1386-                ";",
1387-                None,
1388-                body_hi,
--
1459-        &generics.where_clause,
1460-        context.config.brace_style(),
1461-        Shape::legacy(where_budget, indent),
1462:        Density::Vertical,
1463-        "=",
1464-        None,
1465-        generics.span.hi(),
--
2211-        where_clause,
2212-        context.config.brace_style(),
2213-        Shape::indented(indent, context.config),
2214:        Density::Tall,
2215-        "{",
2216-        Some(span.hi()),
2217-        pos_before_where,
--
2322-        &arg_items,
2323-        context
2324-            .config
2325:            .fn_args_density()
2326-            .to_list_tactic(arg_items.len()),
2327-        Separator::Comma,
2328-        one_line_budget,
--
2564-    where_clause: &ast::WhereClause,
2565-    brace_style: BraceStyle,
2566-    shape: Shape,
2567:    density: Density,
2568-    terminator: &str,
2569-    span_end: Option<BytePos>,
2570-    span_end_before_where: BytePos,
--
2646-    } else {
2647-        terminator.len()
2648-    };
2649:    if density == Density::Tall
2650-        || preds_str.contains('\n')
2651-        || shape.indent.width() + " where ".len() + preds_str.len() + end_length > shape.width
2652-    {
--
2737-            &generics.where_clause,
2738-            brace_style,
2739-            Shape::legacy(budget, offset.block_only()),
2740:            Density::Tall,
2741-            "{",
2742-            Some(span.hi()),
2743-            span_end_before_where,

The option is well tested, both in unit tests and, optimally, in real usage.

Plenty of time passed with rustfmt being released with that option, giving it plenty of real usage:

Vertical variant got added 3 years ago https://github.com/rust-lang/rustfmt/commit/db9d1290254c5703d67fcf4f277b23641fb92d60
Compressed and Tall were added 4 years ago https://github.com/rust-lang/rustfmt/commit/89cda8d43a92f16060319515343b69f5cbf3e1da

In that time frame, it got only 19 issues showing its implementation is quite stable.
Also, there are few tests about all 3 variants of Density:
tests/target/fn-custom.rs
1:// rustfmt-fn_args_density: Compressed

tests/target/fn_args_density-vertical.rs
1:// rustfmt-fn_args_density: Vertical

tests/target/configs/fn_args_density/tall.rs
1:// rustfmt-fn_args_density: Tall

tests/target/configs/fn_args_density/compressed.rs
1:// rustfmt-fn_args_density: Compressed

tests/target/configs/fn_args_density/vertical.rs
1:// rustfmt-fn_args_density: Vertical

tests/target/fn-custom-7.rs
2:// rustfmt-fn_args_density: Vertical

There is no open bug about the option that prevents its use.

None.
Close #3375

Seems reasonable to me. My concern is its name, density sounds odd. I prefer to rename it to fn_args_layout.

@topecongiro Actually sounds good to me! It reminds me of css flex so using a similar term gives a good idea of what the option does.
@softprops @aldanor you on board with this ?

@scampi Looks good!
fn_args_layout seems reasonable, one question though - in case it's renamed, would fn_args_density become an invalid option?

in case it's renamed, would fn_args_density become an invalid option?

Yes, that's the price of an unstable option. Once stabilised, that'd be a totally different story!

@topecongiro it has been renamed in the latest commit

It keeps on failing with the error below, but locally it builds fine:
error[E0433]: failed to resolve: use of undeclared type or module `Density`
    --> src/items.rs:1170:13
     |
1170 |             Density::Compressed,
     |             ^^^^^^^ use of undeclared type or module `Density`
error: aborting due to previous error
For more information about this error, try `rustc --explain E0433`.
error: Could not compile `rustfmt-nightly`.

Thank you for the updates!

@topecongiro How soon before we could see this in a release?


fix(vendor): fixed broccoli concat for vendor files

Fixed Broccoli concatenation of vendor files without listing them again.
Also nice solution from @cironunes to easily add vendor files now works properly. Custom vendor files are added at the bottom of vendor.js in th order that we listed them.
Example of adding vendor file in our project
// ember-cli-build.js
vendorNpmFiles: ['moment/moment.js']

Otherwise lgtm

cool. @cironunes maybe you could document how to use vendor files in the readme?

We'll need to revert this.

Okay, no problem


Simplifying log density tests

the tests are not changed, but simplified and moved into one file.
instead of using DynamicPPL for reference values, now uses hardcoded values for BUGS model (still random for single distribution tests)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>0
Details

0 of 0   changed or added relevant lines in 0 files are covered.
27 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-1.5%) to 81.458%

Files with Coverage Reduction
New Missed Lines
%

src/logdensityproblems.jl
1
88.89%

src/BUGSPrimitives/distributions.jl
6
21.9%

src/model.jl
20
78.99%

Totals

Change from base Build<PHONE_NUMBER>1:
-1.5%

Covered Lines:
1441

Relevant Lines:
1769

💛  - Coveralls


Hybrid mode of local and local container.

local-container mode has a config now which can do this.
For example:
dag:
steps:
first:
mode_config:
local_contianer:
run_in_local: True


Delete Rule Guides Icon Commit

Added a Font Awesome Icon update to the delete rule guides area. Not sure if this is something you'd consider for the master branch. I wanted the font size to be variable based on the height/width setting but I'm not sure how to do this. I'm going to keep working on it though!

Also don't think you should exclude screenshot.PNG, unless you have plans to reference it in the README.

awesome I will work on they today.