Update on Payment card number

Hello,
An update on Payment card number was released the 2022-08-11T19:27:02Z. Check for any new Issuer identification number edit. Link to the diff. Here is the summary:
rescue several links; correct spelling BORIKA  to BORICA

← Previous revision
Revision as of 19:27, 11 August 2022

Line 62:
Line 62:

|No Validation

|No Validation

|-

|-

| [[Diners Club International]]<ref name="MC DC Ref"></ref>

| [[Diners Club International]]<ref name="MC DC Ref"></ref>

|36

|36

| style="color:green" |Yes

| style="color:green" |Yes

Line 68:
Line 68:

| rowspan="23" | [[Luhn algorithm]]

| rowspan="23" | [[Luhn algorithm]]

|-

|-

|[[Diners Club International|Diners Club]] United States & Canada<ref name="DinerUS"></ref>

|[[Diners Club International|Diners Club]] United States & Canada<ref name="DinerUS"></ref>

|54

|54

|style="color:green" |Yes

|style="color:green" |Yes

Line 117:
Line 117:

|-

|-

|[[Maestro (debit card)|Maestro]] UK

|[[Maestro (debit card)|Maestro]] UK

|6759, 676770, 676774<ref name="Barclaycard"></ref>

|6759, 676770, 676774<ref name="Barclaycard"></ref>

|style="color:green" |Yes

|style="color:green" |Yes

|12–19

|12–19

Line 140:
Line 140:

|16–19

|16–19

|-

|-

|[[BORIKA (Bulgarian national payment system)]]

|[[BORICA (Bulgarian national payment system)]]

|2205

|2205

|style="color:green" |Yes

|style="color:green" |Yes

Line 151:
Line 151:

|-

|-

| rowspan="2" | [[Mastercard]]

| rowspan="2" | [[Mastercard]]

|2221–2720<ref name="mastercard-rules">{{Cite web|url=https://www.mastercard.us/content/dam/mccom/global/documents/mastercard-rules.pdf|title=Maestro Global Rules |date=21 December 2017 |publisher=MasterCard }}</ref>

|2221–2720<ref name="mastercard-rules">{{Cite web |url=https://www.mastercard.us/content/dam/mccom/global/documents/mastercard-rules.pdf |archive-url=https://web.archive.org/web/20180514224309/https://www.mastercard.us/content/dam/mccom/global/documents/mastercard-rules.pdf |archive-date=2018-05-14 |url-status=dead |title=Mastercard Rules |date=21 December 2017 |publisher=[[Mastercard]] }}</ref>

|style="color:green" |Yes (since 2017)<ref></ref>

|style="color:green" |Yes (since 2017)<ref></ref>

|16

|16

Line 170:
Line 170:

|-

|-

|[[Troy (card scheme)|Troy]]

|[[Troy (card scheme)|Troy]]

|65 (Discover co-branded<ref></ref>), 9792<ref></ref>

|65 (Discover co-branded<ref></ref>), 9792<ref></ref>

|style="color:green" |Yes

|style="color:green" |Yes

|16

|16

If this Wikipedia's edit does not affect us, just ask for this issue to be close.
In case of trouble, ask for @aloisdg

Duplicate of https://github.com/d-edge/Cardidy/issues/94


manifest.json to "v3"

Updated the "name" field to v3 instead of v2

Pre-flight checklist

[x] I have read the Contributing Guidelines on pull requests.
[ ] If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
[ ] If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation

Docusaurus is not in v2 anymore.
Test Plan

N/A
Related issues/PRs

N/A

Also currently the colors are shades of blue.


Option to disable glowing border in grid view

Would it be possible to add an option to disable the glowing border around games that are highlighted and moused over in grid view?
Specifically in Helium in my case.

It is the theme that must integrate this functionality with the plugin capabilities and not vice versa.


Run more CI tests on Ubuntu 20.04

Had to revert due to a GitHub Actions change :(
(note to self: check for https://clang.llvm.org/extra/clang-tidy/checks/google-global-names-in-headers.html)


Add a public ErrorBarAlignment property in PopulationPlot.cs for boxplot.

Box plot in population plots does not have public option for setting error bar alignment. Current setting is align to the right. Aligning to the center is by far the most common error bar alignment in box plots.
Added public property ErrorBarAlignment that sets the HorizontalAlignment enum. Default value is now Center.
Also added errorAlignment: ErrorBarAlignment parameter to two calls to Box() method.
This is my first ever pull request, so I apologize if I'm not doing it right.

Hi @benton-anderson, thank you for opening this issue!
Allowing users to customize this alignment is a big win - thanks for this PR!
This type of plot is what the default behavior is designed for:
https://scottplot.net/cookbook/4.1/category/plottable-population/#multiple-populations

While I agree that center is more common, I don't want to change the default behavior as it may break existing apps. I'll certainly make the center alignment the default in the next major version of ScottPlot (version 5) which permits breaking changes like this 👍


Syntax highlighter does not recognise imaginary, binary or octal numbers

From<EMAIL_ADDRESS>on 2011-05-09T23:25:27Z
I am using the hg version of spyder, change 6bdffe7f8b5f
Imaginary numbers are not picked up correctly by the syntax highlighter.  I guess this appeared after dropping QScintilla.
I have attached a fix, and while I was at it I also added support for binary and octal numbers.
Attachment: numbers.diff
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=649

From pierre.raybaut on 2011-05-11T03:16:45Z
Thanks for this fix. I'll integrate this change ASAP (I'm currently on vacation without any computer...).
Status: Accepted
Labels: Milestone-Release2.1

From ccordoba12 on 2011-05-15T08:20:42Z
Labels: -Type-Defect Type-Enhancement

From pierre.raybaut on 2011-05-15T13:26:21Z
This issue was closed by revision 3f734ce8ba86 .

From pierre.raybaut on 2011-05-15T13:26:08Z
This issue was closed by revision faee74fa7b3a .
Status: Fixed


#193: Added css variables and simplified dom

Fixes #193

Let's discuss #198 first

@LTiger14 I've gave it another pass with flexible layout for review items. The key lesson learned from this exercise is that we should avoid using html markup to build our style. This blocks us from customising easily (with pure css).
I've start to create a small .md file in the component, just to make sure we don't need to rebuild those customisation examples, and also for you to check. You can use them in the app styles to checkout the level of customisation.


[Feature Request]: Nutrition Tracking

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
IT allows users to log their meals by entering food items, portion sizes, and meal types through a user-friendly interface. Once logged, the application fetches nutritional information from a database or API, calculates total calories and macronutrients, and updates the user's daily intake on their dashboard. Users can review their meal history, edit or delete entries, and receive notifications if they approach their caloric goals. This feature promotes healthier eating habits by providing users with insights into their nutrition and helping them stay aligned with their dietary goals.
Use Case
Sarah, a 28-year-old fitness enthusiast aiming to lose 10 pounds, uses the app's nutrition tracking feature to log her meals and receive instant nutritional information. The app sends reminders, provides visual insights into her eating habits, and connects her with a supportive community. This feature empowers Sarah to make informed dietary choices and enhances her accountability, increasing her chances of achieving her weight loss goal before her beach vacation.
Benefits
No response
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC-EXT contributor
[X] I'm a HACKTOBERFEST contributor
[X] I have starred the repository

@Sami3160 please assign me this issue i want to work on it

@meghanakn473 go ahead 👍

hey @jeevan10017 i have almost implemented the feature....im not able to fetch the meal data from the api...
could u guide me on next steps..
im getting like this

@GAVINESHWAR

hey @jeevan10017 i have almost implemented the feature....im not able to fetch the meal data from the api...
could u guide me on next steps..
im getting like this

@GAVINESHWAR

hey @jeevan10017 i have almost implemented the feature....im not able to fetch the meal data from the api...
could u guide me on next steps..
im getting like this

@GAVINESHWAR

??

He is the mentor of this repository under Gssoc-24 ext

hey @jeevan10017 i have almost implemented the feature....im not able to fetch the meal data from the api... could u guide me on next steps..
im getting like this

@GAVINESHWAR please suggest me wt i can do with

hey @jeevan10017 i have almost implemented the feature....im not able to fetch the meal data from the api... could u guide me on next steps..
im getting like this

@GAVINESHWAR please suggest me wt i can do with

@meghanakn473 I am unable to view the photo you send in the comment could you please send once again

hey @jeevan10017 i have almost implemented the feature....im not able to fetch the meal data from the api... could u guide me on next steps..
im getting like this

@GAVINESHWAR please suggest me wt i can do with

@meghanakn473 I am unable to view the photo you send in the comment could you please send once again

@meghanakn473 , please check the api is working correctly or not and see the whether the syntax of the code is correct or not
async function getData() {
try {
const response = await fetch('https://api.example.com/data'); // Make the API call
const data = await response.json(); // Wait for the response to be converted to JSON
console.log(data);  // Handle the data from the API
} catch (error) {
console.error('Error:', error);  // Handle any errors
}
}
getData();  // Call the async function
this is the general syntax for getting the data from the external API
Please go through my repository where i used api for fetching data .
https://github.com/GAVINESHWAR/Photos_Search_Engine/blob/main/script.js
I hope this will help you

@meghanakn473 , please check the api is working correctly or not and see the whether the syntax of the code is correct or not
async function getData() { try { const response = await fetch('https://api.example.com/data'); // Make the API call const data = await response.json(); // Wait for the response to be converted to JSON console.log(data); // Handle the data from the API } catch (error) { console.error('Error:', error); // Handle any errors } }
getData(); // Call the async function
this is the general syntax for getting the data from the external API
Please go through my repository where i used api for fetching data .
https://github.com/GAVINESHWAR/Photos_Search_Engine/blob/main/script.js
I hope this will help you

this is my data fetching function from nutritionix.com
const API_URL = 'https://trackapi.nutritionix.com/v2/natural/nutrients';
export const fetchNutritionData = async (foodItem) => {
try {
const response = await axios.post(API_URL,
{ query: foodItem },
{
headers: {
'x-app-id': APP_ID,
'x-app-key': API_KEY,
'Content-Type': 'application/json',
}
}
);
return response.data.foods; // Return array of foods with nutrition data
} catch (error) {
console.error('Error fetching data:', error);
return null;
}
};
please guide me if smtg is wrong @GAVINESHWAR

@meghanakn473  please check weather you the access key entered correctly or not , please check weather you have the access to fetch the data. Fo getting the data from the external api you should have the access for that you need the access key which given when you login to the Platform where your fetching data .

@meghanakn473  please check weather you the access key entered correctly or not , please check weather you have the access to fetch the data. Fo getting the data from the external api you should have the access for that you need the access key which given when you login to the Platform where your fetching data .

Yes sir I'm having access to Fetch data and also crossed the api key
Everything is correct

@meghanakn473  please check weather you the access key entered correctly or not , please check weather you have the access to fetch the data. Fo getting the data from the external api you should have the access for that you need the access key which given when you login to the Platform where your fetching data .

Yes sir I'm having access to Fetch data and also crossed checked the api key Everything is correct
@meghanakn473
Please send me complete api code of it , because the code you mention above I didn't observe any access key it it

i hv put the api id and api key in .env file.
REACT_APP_NUTRITIONIX_APP_ID='466e8d9a'
REACT_APP_NUTRITIONIX_API_KEY='
b1975484d742bede95d2098e323b2bba'
and fetched it in this way
import axios from 'axios';
// Replace with your Nutritionix App ID and API Key
const APP_ID = process.env.REACT_APP_NUTRITIONIX_APP_ID;
const API_KEY = process.env.REACT_APP_NUTRITIONIX_API_KEY;
const API_URL = 'https://trackapi.nutritionix.com/v2/natural/nutrients';
export const fetchNutritionData = async (foodItem) => {
try {
const response = await axios.post(API_URL,
{ query: foodItem },
{
headers: {
'x-app-id': APP_ID,
'x-app-key': API_KEY,
'Content-Type': 'application/json',
}
}
);
return response.data.foods; // Return array of foods with nutrition data
} catch (error) {
console.error('Error fetching data:', error);
return null;
}
};
@GAVINESHWAR please check and review

import axios from 'axios';
const APP_ID = process.env.REACT_APP_NUTRITIONIX_APP_ID;
const API_KEY = process.env.REACT_APP_NUTRITIONIX_API_KEY;
const API_URL = 'https://trackapi.nutritionix.com/v2/natural/nutrients';
export const fetchNutritionData = async (foodItem) => {
try {
// Make POST request to Nutritionix API
const response = await axios.post(
API_URL,
{ query: foodItem }, // Send the food item as 'query'
{
headers: {
'x-app-id': APP_ID,      // Nutritionix App ID from env
'x-app-key': API_KEY,    // Nutritionix API Key from env
'Content-Type': 'application/json', // Specify JSON format
},
}
);
return response.data.foods;

} catch (error) {
console.error('Error fetching data:', error);
return null;
}
};
@meghanakn473 , please go through this code i hope this will work

Sure I'll check and update

import axios from 'axios';
const APP_ID = process.env.REACT_APP_NUTRITIONIX_APP_ID; const API_KEY = process.env.REACT_APP_NUTRITIONIX_API_KEY;
const API_URL = 'https://trackapi.nutritionix.com/v2/natural/nutrients';
export const fetchNutritionData = async (foodItem) => { try { // Make POST request to Nutritionix API const response = await axios.post( API_URL, { query: foodItem }, // Send the food item as 'query' { headers: { 'x-app-id': APP_ID, // Nutritionix App ID from env 'x-app-key': API_KEY, // Nutritionix API Key from env 'Content-Type': 'application/json', // Specify JSON format }, } );
return response.data.foods;

} catch (error) { console.error('Error fetching data:', error); return null; } };
@meghanakn473 , please go through this code i hope this will work

tried it, but the result is same ntg changed @GAVINESHWAR

hey it worked, so shd i dispose api keys directly in file or keep it in .env

@GAVINESHWAR hey it worked, so shd i add api keys directly in file or keep it in .env
Ok @meghanakn473


Identify 438E as Pure Cool Formaldehyde, and add formaldehyde env data

Hey there, this is motivated by seanrees/prometheus-dyson#13 to support the Dyson Pure Cool Formaldehyde. After chatting with the requestor, we identified this as model 438E.
This creates a new DysonPureCoolFormaldehyde class in dyson_pure_cool.py. As far as I can tell, the new model behaves just like a PureCool but with the extra metric. So in this case I simply added it to dyson_pure_cool.py and extended directly from DysonPureCool. I also updated the references throughout libdyson from PURE_COOL_2021 to PURE_COOL_FORMALDEHYDE.
I didn't add a test for this. I wanted to run this design by you first before I did -- if there's another way you prefer this to be implemented, let me know. :-)

Gentle ping on this @shenxn ? (looking for directional feedback :))

Thanks, added a test.


Fix null pointer exception when using ConfigKey.Scope.ManagementServer

Description

A null pointer is thrown if a ConfigKey.Scope.ManagementServer is used for configuring a ConfigKey.
The null pointer happens because the map _scopeLevelConfigsMap does not contain the ConfigKey.Scope.ManagementServer as a key.
Fixed by adding ConfigKey.Scope.ManagementServer in the map _scopeLevelConfigsMap.

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[x] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Screenshots (if appropriate):
How Has This Been Tested?

@GabrielBrascher can you check:

ERROR] /home/jenkins/jenkins-slave/workspace/cloudstack-pr-analysis/framework/config/src/main/java/org/apache/cloudstack/framework/config/impl/ConfigDepotImpl.java:88: Line has trailing spaces. [RegexpSingleline]

@blueorangutan package

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✔debian. JID-2466

@blueorangutan test

@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Trillian test result (tid-3224)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 34070 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr3062-t3224-kvm-centos7.zip
Intermittent failure detected: /marvin/tests/smoke/test_multipleips_per_nic.py
Intermittent failure detected: /marvin/tests/smoke/test_privategw_acl.py
Intermittent failure detected: /marvin/tests/smoke/test_vpc_redundant.py
Intermittent failure detected: /marvin/tests/smoke/test_host_maintenance.py
Smoke tests completed. 68 look OK, 2 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File

test_nic_secondaryip_add_remove
Error
47.23
test_multipleips_per_nic.py

test_04_rvpc_network_garbage_collector_nics
Failure
520.93
test_vpc_redundant.py


Is there any guide which shows how to duplicate this app behavior?

Readme file mentioned that firebase Queue was used with a node server. I am unclear how to achieve this. THe node server contained in the backend folder was not hosted on Firebase right?

No you have to host your own node.js server

Yep, I host this on Google App Engine: https://cloud.google.com/appengine/docs/flexible/nodejs/


Full Reactive Repository Support, Rebranding DocumentDb to CosmosDb

Rebranding DocumentDb to CosmosDb (mainly name changes)
** upgrade to latest Cosmos Db SDK (v3.2.0)
Full Reactive Repository support.
** Reactive query support.
** Reactive configuration support.
** Enabling Reactive Repository support.
All bug fixes, and new features from master.

Codecov Report

Merging #434 into master will decrease coverage by 5.56%.
The diff coverage is 51.33%.

@@            Coverage Diff             @@
##           master     #434      +/-   ##
==========================================
- Coverage   75.12%   69.55%   -5.57%
==========================================
  Files          48       56       +8
  Lines        1439     1544     +105
  Branches      161      163       +2
==========================================
- Hits         1081     1074       -7
- Misses        271      390     +119
+ Partials       87       80       -7

Impacted Files
Coverage Δ

...osdb/core/mapping/BasicCosmosPersistentEntity.java
100% <ø> (ø)

...sitory/query/CosmosParameterParameterAccessor.java
75% <ø> (ø)

.../spring/data/cosmosdb/core/query/CriteriaType.java
83.07% <ø> (ø)
:arrow_up:

...a/cosmosdb/core/generator/CountQueryGenerator.java
100% <ø> (+33.33%)
:arrow_up:

...ata/cosmosdb/repository/query/CosmosParameter.java
0% <ø> (ø)

...osmosdb/core/generator/FindQuerySpecGenerator.java
100% <ø> (ø)
:arrow_up:

...ta/cosmosdb/exception/CosmosDBAccessException.java
100% <ø> (ø)

...db/core/mapping/BasicCosmosPersistentProperty.java
83.33% <ø> (ø)

...ry/config/ReactiveCosmosRepositoriesRegistrar.java
0% <0%> (ø)

...uery/SimpleReactiveCosmosEntityMetadataUnused.java
0% <0%> (ø)

... and 46 more

Continue to review full report at Codecov.

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


Implement Splay Tree | #451

Pull Request Template
What have you Changed(must)

Built extra functions which can be used by any binary search tree in extended_binary_search_tree.py
Implemented Splay tree with splay and delete in splay_tree.py to fix #451

Issue no.(must) - #451
Pr will be closed and marked as spam. If issue number not found or issue was assigned to someone else.
Marking as spam can block your account from HacktoberFest.
Self Check(Tick After Making pull Request)

[x] This issue was assigned to me if not it will marked as spam.
[x] My file is in proper folder.
[x] I am following clean code and Documentation.
[x] I have added title and what program will do first in the file.

README - How to Contribute

If my branch is good enough to be merged, please mark the issue as hacktoberfest-accepted. Thank you!


"spec.forProvider.name is a required parameter" error but this is inconsistent with doc and example

What happened?
Invalid: Secret.keyvault.azure.upbound.io "policy-tst-postgresql-postgresql-password" is invalid: spec: Invalid value: "object": spec.forProvider.name is a required parameter"
Why? This is not listed as a required field in the documentation: https://marketplace.upbound.io/providers/upbound/provider-azure-keyvault/v0.38.2/resources/keyvault.azure.upbound.io/Secret/v1beta1 and my example looks similar to the first example on the example tab of that document which also doesn't have spec.forProvider.name
Workaround: add value for spec.forProvider.name
How can we reproduce it?
apiVersion: keyvault.azure.upbound.io/v1beta1
kind: Secret
metadata:
  name: policy-tst-postgresql-postgresql-password
spec:
  deletionPolicy: Orphan
  forProvider:
    keyVaultIdRef:
      name: policy-tst-opal-kv
    tags:
      release: opal-policy-tst
      cluster: ${CLUSTER_NAME}
    valueSecretRef:
      key: postgresql-password
      name: policy-tst-generated-secrets
      namespace: opal-policy-tst
  providerConfigRef:
    name: provider-config-azure

What environment did it happen in?

Crossplane Version: v1.12.2
Provider Version: provider-azure-keyvault:v0.38.2
Kubernetes Version: v1.26.6
Kubernetes Distribution: AKS

Hi @emily-zall,
Thank you for raising this issue. With this PR, the name field for this resource became required. There are two examples in Marketplace, but the first one has not been updated and its name field has not been added.


PrimeNG: Refactor Email-Validate Form Component

The Email-Validate form component, used for creating and updating forms, should be refactored to use PrimeNG's form components so that the styling is consistent with the remainder of the application.
Relative path: frontend/src/app/email-validate

on it ^^

Looks good! Thank you for another contribution!


[WIP] Add master side logic for worker registration flow control

What changes are proposed in this pull request?
Please outline the changes and how this PR fixes the issue.
Why are the changes needed?
Please clarify why the changes are needed. For instance,

If you propose a new API, clarify the use case for a new API.
If you fix a bug, describe the bug.

Does this PR introduce any user facing changes?
Please list the user-facing changes introduced by your change, including

change in user-facing APIs
addition or removal of property keys
webui

Codecov Report

Merging #14148 (86ad1f8) into master (449d1ae) will decrease coverage by 18.94%.
The diff coverage is 69.23%.

@@              Coverage Diff              @@
##             master   #14148       +/-   ##
=============================================
- Coverage     36.29%   17.34%   -18.95%
+ Complexity     7469     2700     -4769
=============================================
  Files          1415     1432       +17
  Lines         81972    82848      +876
  Branches       9922    10017       +95
=============================================
- Hits          29750    14371    -15379
- Misses        49663    67218    +17555
+ Partials       2559     1259     -1300

Impacted Files
Coverage Δ

...ain/java/alluxio/worker/block/BlockMasterSync.java
65.57% <ø> (ø)

.../master/block/BlockMasterWorkerServiceHandler.java
60.00% <40.00%> (-2.13%)
:arrow_down:

...n/java/alluxio/worker/block/BlockMasterClient.java
72.94% <50.00%> (-6.01%)
:arrow_down:

...common/src/main/java/alluxio/conf/PropertyKey.java
97.89% <100.00%> (-1.56%)
:arrow_down:

.../java/alluxio/master/block/DefaultBlockMaster.java
42.80% <100.00%> (+1.27%)
:arrow_up:

...mon/src/main/java/alluxio/shell/CommandReturn.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...mon/src/main/java/alluxio/util/ExceptionUtils.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...n/src/main/java/alluxio/wire/AlluxioProxyInfo.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../src/main/java/alluxio/wire/AlluxioMasterInfo.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...src/main/java/alluxio/job/meta/JobIdGenerator.java
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 591 more

Continue to review full report at Codecov.

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

Closed. Moved to https://github.com/Alluxio/alluxio/pull/14220


Fix per-run combine time (fixes #181)

Before change:
benchmarking perRun
measurement took 231495 s (60 hours!!!)
analysing with 1000 resamples
bootstrapping with 13 of 22 samples (59%)
time                 3.112 ms   (3.102 ms .. 3.122 ms)
                     1.000 R²   (1.000 R² .. 1.000 R²)
mean                 3.119 ms   (3.111 ms .. 3.122 ms)
std dev              10.00 μs   (5.617 μs .. 16.74 μs)
found 1 outliers among 13 samples (7.7%)
  1 (7.7%) low severe
variance introduced by outliers: 4% (slightly inflated)

After:
benchmarking perRun
measurement took 5.135 s
analysing with 1000 resamples
bootstrapping with 33 of 42 samples (78%)
time                 3.120 ms   (3.116 ms .. 3.124 ms)
                     1.000 R²   (1.000 R² .. 1.000 R²)
mean                 3.117 ms   (3.111 ms .. 3.120 ms)
std dev              11.95 μs   (6.974 μs .. 20.56 μs)
found 3 outliers among 33 samples (9.1%)
  3 (9.1%) low severe
variance introduced by outliers: 2% (slightly inflated)

The reported time is now much more accurate, and we get double the number samples.

Done and done. I promise I will remember the changelog in the future 😣


Support field directives

The first commit just refactors some of the File creation methods in the test files.
For the second commit, the approach was as followsL
The generated IR provides an optional isConditional field  if the 'skip' or 'include' directives exist.
I pushed the nullable check back to the Fields class and combined that with isConditional to yield isOptional.
I feel that it makes more sense for the non-null check to be part of the field class but I'm open to discussions/suggestions on that.

@marwanad you'll need to rebase this, sorry!

Should fix #28


[Feat]: Gift Cards Feature

Feature Description
Implement a gift card functionality allowing users to purchase and send gift cards for the platform.
Provide a detailed description of the feature
This feature will enable users to buy digital gift cards that can be sent to friends or family members. The gift cards can be used to pay for subscriptions or in-app purchases, enhancing user engagement and providing a new revenue stream for the platform.
Put here any screenshots or videos (optional)

By submitting this issue, you agree to

[X] I agree to follow this project's Code of Conduct
[X] I’ve read all the issues in the issue section, and this feature has not been proposed yet.

Other Information

[X] I'm a GSSoC '24 Extended contributor
[X] I'm a Hacktoberfest '24 contributor
[X] I am willing to work on this feature (optional)

@maniyaom Check this issue!

@SCR01 please start working on it. Ensure that the pages are responsive across all devices and implement them using Tailwind CSS.


Add Dontorrent as a torrent provider.

Hello again:
In the search for constant improvement of Torrentio I propose to complement
torrent providers with the addition of Dontorrent.
Dontorrent is a stable and trustworthy website that has been in operation for a long time.
Official Domains - DonTorrent https://dontorrent.city/dominios
DonTorrent (Official Channel) – Telegram
https://t.me/DonTorrent
Please and thank you.

Duplicate #260
Use search before opening new issues

Sorry for the inconvenience, it is far from my intention to waste your time but in my opinion the duplicate request reflects the sincere interest of Torrentio users.
In any case, I want to take this opportunity to thank you once again for having added Wolfmax4k to the torrent providers.
🤗


Add patched ZK files

@hmusum is this right? :>

Yes, changed the startup logging a bit

👍

@hakonhall FYI


Add RemarkCommand

Do not merge. This is tutorial work.

Closing since the tP dashboard now reflects all changes.


Add encoding attribte to info

This PR adds encoding attribute to the AudioMetaData class and make info function returns encoding as well.
In the legacy backend implementations, this information was available in sox backend, but in new backends, we do not expose the native structure of libsox directly, so we use str class to represent the encoding. See #1184 for the specification.
Resolves #1184

Thanks!

Thanks!


"Ungive" Item command

Should support bool, int, and custom skill items (which are apparently not also bool items for some reason).

Since Load and Unload can have side effects, any implementation of this is too fragile to support


keyboard [enter] , click OK.png not working - duplicated issue see #1171 instead

closing due to duplication with #1171


C# Language specific leaderboard is showing the wrong language dialects

Currently the C# Leaderboard shows C and C++ dialects and not C# anymore. this was working as of yesterday. I can provide more details if needed
C# Leaderboard : https://wakatime.com/leaders?language=C%23

Thanks, it's fixed now. I was stripping non-word characters from the cache key :fearful:

Thanks a lot! It is working now.


svg Viewbox

Issue description:
http://prntscr.com/qa8uk9
Version used:
wp org
Using theme_mods or options?
theme_mods
Code to reproduce the issue (config + field(s))
who has to fix this question http://prntscr.com/qa8uk9 ?
When adding svg icon from first-found svg icons service there is an error (but if ignore it then it is ok but anyway for clients it is looking as warning )
Most popular services are using in next way viewBox not viewbox

https://www.flaticon.com/
https://fontawesome.com/
https://www.iconfinder.com/
https://freeicons.io/
https://icomoon.io/

The question is who should fix this and when could it be ?

Kirki uses the default WordPress code highlighter control, so these come from wp-core.
WordPress uses CodeMirror, so in order to fix this it would have to be fixed in https://github.com/codemirror/codemirror first, and then updated in WordPress.
I don't see any reports in the CodeMirror repository, so the 1st step would be to report it there. 👍


Documentation additions

Putting this here as a bit of a work in progress for a bit of feedback before I add to it further.
I've added a couple of examples to the docblocks and changed the callback param to a callback type rather than function.

What does requestHandshake actually do? The callback seems to have no parameters to give me details on the current installation and if the hive_keychain object isn't there then we'd get an undefined error anyway.
I tested it with
keychain.requestHandshake((response) => {
    console.log(response);
});```

What does requestHandshake actually do? The callback seems to have no parameters to give me details on the current installation and if the hive_keychain object isn't there then we'd get an undefined error anyway.
I tested it with
keychain.requestHandshake((response) => {
    console.log(response);
});```

It's just there to make sure that Keychain is there and working properly.

Thanks for your contribution @npfedwards


Add optional timeout field

This would timeout an async operation if it takes over timeout duration.

This isn't the libraries responsibility. Instead, add a timeout modifier to your async call and handle it appropriately
AsyncButtonBuilder(
  child: Text('Click Me'),
  onPressed: () async {
    try {
      await Future.delayed(Duration(seconds: 1))
          .timeout(Duration(milliseconds: 500));
    } on TimeoutException catch (e) {
      // Show a popup or something
      rethrow;
    } on Exception catch (e) {
      // Show a dialog or something
      rethrow;
    }
  },
  builder: (context, child, callback, _) {
    return TextButton(
      child: child,
      onPressed: callback,
    );
  },
),

You rethrow because AsyncButtonBuilder needs to know of the error in order to show the error state


it is failing through proxy

The following is the error message. How to make it work through proxy. I have http_proxy_host and http_proxy_port in puppet config but it does not work
PS C:\ProgramData\PuppetLabs\puppet\manifests> puppet apply .\fourthcoffee.pp
Warning: Config file C:/ProgramData/PuppetLabs/puppet/etc/hiera.yaml not found, using Hiera defaults
Notice: Compiled catalog for rbwindev004.aap.pwcinternal.com in environment production in 0.22 seconds
Notice: /Stage[main]/Fourthcoffee/Dsc_xwebsite[Stop DefaultSite]/ensure: created
Error: PowerShell DSC resource MSFT_xRemoteFile  failed to execute Set-TargetResource functionality with error message: Invoking web request failed with error :
Error: /Stage[main]/Fourthcoffee/Dsc_xremotefile[Download WebContent Zip]/ensure: change from absent to present failed: PowerShell DSC resource MSFT_xRemoteFile  failed to execute Set-T
Notice: /Stage[main]/Fourthcoffee/Dsc_archive[Unzip and Copy the WebContent]: Dependency Dsc_xremotefile[Download WebContent Zip] has failures: true
Warning: /Stage[main]/Fourthcoffee/Dsc_archive[Unzip and Copy the WebContent]: Skipping because of failed dependencies
Notice: /Stage[main]/Fourthcoffee/Dsc_xwebsite[BackeryWebSite]: Dependency Dsc_xremotefile[Download WebContent Zip] has failures: true

The error is occurring in the xRemoteFile DSC Resource, not in Puppet:

Error: PowerShell DSC resource MSFT_xRemoteFile failed to execute Set-TargetResource functionality with error message: Invoking web request failed with error

The xRemoteFile DSC Resource is a wrapper around the Invoke-WebRequest cmdlet. Invoke-WebRequest does provide parameters to handle proxy details, however xRemoteFile does not expose parameters itself that uses them. A possible option is to open a feature request in the official Microsoft DSC Resource repo or fork their implementation and use it here.

Agreed that this is something we can't address with Puppet - thanks for the report though, and good luck with getting this addressed upstream!


feat: 🎸 @W-8712470@ add env var for target registry

Added a env var, NPM_REGISTRY, that allows users to select which npm
registry is to be used for install and publish actions.
What does this PR do?
Gives the user the ability to direct certain actions to a specific npm registry by setting env var NPM_REGISTRY.

@amphro @mdonnalley I did some additional work when I found out the the original changes just didn't work.
Created an abstraction of a registry to help isolate decisions made around that subject.

@amphro @mdonnalley I did some additional work when I found out the the original changes just didn't work.
Created an abstraction of a registry to help isolate decisions made around that subject.

Testing notes: I published a couple of different packages to a local verdaccio including some error conditions. Things look good. The release-package is waiting for a status.... but everything else is successful... I'll merge in the morning even if it hasn't run yet.

Testing notes: I published a couple of different packages to a local verdaccio including some error conditions. Things look good. The release-package is waiting for a status.... but everything else is successful... I'll merge in the morning even if it hasn't run yet.


Text "Undefine" in textarea when geoform hosted by own webserver

When hosting the geoform via our own webserver we get the text "undefinied" under an field defined as a textarea. The geoform hostet by arcgisonline shows correct value

Actually I have no idea where the text "undefined" comes from. Both form refer to the same webmap...
Thanks in advance :-)))

I'll take a look. thanks!

Hi,
I applied the changes to the .\js\main.js but they don't show any effect. I still got that "undefined"-text... underneath the textarea-field...

hey @STGiese can you share your app? What language is that?

Hi, the app is not public yet. It's going to be by august... But I can send you username/passwd via PN (if you give me) for support purposes.
The language is german...

Hi @STGiese. I am not able to reproduce that with the latest code on GitHub. Are you sure you're running the latest code on your web server?
If it's working on ArcGIS Online but not your web server that leads me to believe the code is different.


Fix Reseller Club

Fix issues by fixing the error reporting...

Fixes: https://github.com/FOSSBilling/FOSSBilling/issues/2096

Does this fix #1733 as well?
Also I thought you said that a bunch of the API endpoints were removed, doesn't look like any of those have been updated here...

Does this fix #1733 as well? Also I thought you said that a bunch of the API endpoints were removed, doesn't look like any of those have been updated here...

No it seems still to be fine the  move to http-client broke more or less the handling..
$result -> toarray()  causes to trigger an exception ...
I have tested it against the end points and it works fine.

LGTM. I still hate how their API doesn't always return JSON, but there's not much we can do about it

It took me way to long to find that out ...
Also their support issn't either the best ...


[zh-cn]Update configure-projected-volume-storage.md

Preview:
https://github.com/kubernetes/website/pull/35415/files?short_path=ba82377#diff-ba82377355f9b7fac53cada50ea54fe74706d4b8922614f1a61bd9a8039950e9

This PR doesn't have to close. Only 3 lines of indention are wrong, but the other part are valuable.
You can re-open this PR by yourself, and continue to be merged after fixing that.


Add -x flag to README

The -x flag exists when running $ nidyx -h, but it isn't mentioned in the README, as mentioned in #30. Fixing that

Thanks. Merged.


chore: add grpc health check.

fix https://github.com/drone/drone/issues/2246
cc @jmccann @tboerger @bradrydzewski

@appleboy Thanks for tackling this!!
Not sure I can offer a LGTM as I don't have confidence in my go-fu for this one but I'd be willing to test this in my dev environment if it gets merged (I use EE features in dev so can't compile/test myself in existing dev env ...)  😄
The only comment I have otherwise is if we should have this enabled by default or have it disabled by default for now until we have more confidence in the check.
Thanks again!!!

@jmccann I try this solution on Kubernetes. It still not working for me. Maybe you can help to try on Kubernetes or Docker swarm but it is working for binary install or docker-compose.

@tboerger already rebase.

I try this solution on Kubernetes. It still not working for me

If I understand correctly, this patch doesn't solve the issue? If so, I think we should wait and merge a working solution.

@bradrydzewski Yes. maybe we should wait for another solution.

@appleboy any news?


feat(pd): add --gas-price-simple flag to generate

Describe your changes
Adds a new CLI flag for pd testnet generate, to opt in to non-zero gas
prices. It's a bit of a shortcut to reuse the same numeric value across
all of them, but we can always add more CLI flags later to finetune.
Closes https://github.com/penumbra-zone/penumbra/issues/4154.
Checklist before requesting a review

[x] If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason:

Adds opt-in behavior, and modifies CI runs, but does not touch application code.

Testing/review
The simplest way to validate the new behavior here is:

check out this feature branch
cargo run --bin pd -- testnet generate --gas-price-simple 5
start cometbft/pd to serve the local devnet
configure pcli to use http://locahost:8080 as grpc_addr
run pcli --home <path> view balance and confirm you have multiple denoms
run pcli --home <path> tx send --to <different_addr_in_same_wallet> 1test_usd
run pcli --home <path> view balance and confirm that 1) the sent denom moved; and 2) a wee bit of penumbra was burned to pay the fee.

LGTM!
so the trick here is to use another denom? I'm looking forward to seeing how our modified planner logic fares in this smoke test environment.

so the trick here is to use another denom? I'm looking forward to seeing how our modified planner logic fares in this smoke test environment.

To my surprise, I didn't need to modify the smoke tests at all, because the tx send tests already use a non-staking token TEST_ASSET, so the addition of fees doesn't affect the balance checks of TEST_ASSET.


Add get_message() helper command

Add an informational command that can fetch messages by ID, and display their contents, and the picture of about who posted it. (See mawabot's "quote" command) It should also provide links to any attached files.
Since get_message() is per-channel, a parallel asynchronous coroutine should be invoked to search all channels in the guild. As such, this command is to be guild-only.

Should have an option or related command that fetches the raw message content for purposes like filtering of getting mentions/emojis.


Boot image selection

The question here is what's the choice of boot image in case we find multiple matched or compatible boot images found on step 3.
AFAIK the right answer is that we select top 1 boot image ordered by DeploymentIDs DESC: that means if we create the deployment from site ZZZ, it will overrule all other deployments :)

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

ID: 3527c358-cf3f-07ec-1cb8-88982ff99122
Version Independent ID: 2c618192-bb71-d934-d20e-1ceb15cb2e01
Content: Use PXE for OSD over the network - Configuration Manager
Content Source: sccm/osd/deploy-use/use-pxe-to-deploy-windows-over-the-network.md
Product: configuration-manager
GitHub Login: @aczechowski
Microsoft Alias: aaroncz

Thanks for the feedback @Yupiter2005. Let me check and followup.

Yes, it uses the "highest" or most recent deployment ID. In the case of a multi-site hierarchy, the "higher" letter site would take precedence in that string comparison. So in your example, a year-old deployment from site ZZZ would be selected over yesterday's deployment from site AAA. (In the case where they are both matched otherwise.) I think that's a good clarification to add to this article, so will use this issue to track that change.
If you think the behavior should change, please file Product feedback.

I revised the article and included this information. The change will be live on or about Monday, 6 May. I'm closing this issue.


duckdb: 0.8.0 -> 0.8.1

Description of changes
Bump duckdb: 0.8.0 -> 0.8.1
Bump python3Packages.sqlglot: 15.0.0 -> 16.3.1
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

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

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

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

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

[x] Fits CONTRIBUTING.md.

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

20 packages built:

duckdb
mycli
mycli.dist
python310Packages.duckdb
python310Packages.duckdb-engine
python310Packages.duckdb-engine.dist
python310Packages.duckdb.dist
python310Packages.ibis-framework
python310Packages.ibis-framework.dist
python310Packages.sqlglot
python310Packages.sqlglot.dist
python311Packages.duckdb
python311Packages.duckdb-engine
python311Packages.duckdb-engine.dist
python311Packages.duckdb.dist
python311Packages.ibis-framework
python311Packages.ibis-framework.dist
python311Packages.sqlglot
python311Packages.sqlglot.dist
sbclPackages.duckdb

Both commit messages lack a motivation, or as CONTRIBUTING.md states it:

(Motivation for change. Link to release notes. Additional information.)

Is this a new criteria? I don't remember this requirement from previous PRs. Happy to add it though. Is there anything needed beyond "The motivation for this change is to update the version of $package?"

@mweinelt Are you looking for release notes, or something specific?

@mweinelt Added links to release notes.

Is this a new criteria? I don't remember this requirement from previous PRs. Happy to add it though. Is there anything needed beyond "The motivation for this change is to update the version of $package?"

I only consider this a clarification, of what a motivation can be, but that happend in 2022/04. https://github.com/NixOS/nixpkgs/commit/cd00cafaaddb06e4b7075e0ca1562dd8610a9e7a

@mweinelt Are you looking for release notes, or something more specific?

Yes, I am. Release notes are more or less a good way to understand what changed between two versions, if one does not intend to trawl through the diff. So my thinking is they are crucial to evaluate a package bump, because of dependency changes etc..

@mweinelt I think this is ready for review.


Add characteristic polylines and more benchmarks

More benchmarks should be added for the core polyline functions:

Polyline path length
Polyline parallel offset
Polyline winding number
These benchmarks can be added to cavalier_contours/benches/benches.rs.

More polylines (capturing different characteristics, e.g. polyline with lots of lines, polyline with lots of arcs, polyline when offset that has many self intersects, polyline when offset that has very little self intersects, etc.) should be added and available for the benchmarks as well. These can be added to cavalier_contours/benches/test_polylines.rs.
As things grow it may make sense to create another crate in the workspace that has all the characteristic polylines we want to add for testing so it may be accessed from the other crates (test_suite, etc.).

Hey @jbuckmccready,
It's me back again :D.
I'd like to contribute to your work as much as I can.
As I've never used rust before would you mind giving me some insights on how you're testing and running the library?
Thanks

@denisraison Hello! For getting started I recommend the Rust book getting started here and reading through the chapters. That will get you up and going with cargo to build the library and run tests.
I use Visual Studio Code with the rust-analyzer extension for editing.
This library follows the all the standard cargo conventions so cargo test will run all the tests, cargo bench will run all the benchmarks, etc.

The benchmarks use the criterion library which you can read about here and you can also just look at the existing code and add to the structure. You can also see some example use of criterion benchmark code here which is from the spatial index crate this library uses.

I actually decided to move the benchmarks out of this repository since criterion slowed the fresh dev build significantly. I am closing this issue for now (I plan to make another git repository that references this one solely for benchmarks sometime in the future). If you'd like to contribute please check out the other issues.


Fixed backslashes.

https://github.com/MicrosoftDocs/windows-uwp/issues/2240

Microsoft authors of articles need to make updates through the private repository so the updates can be staged and validated by the current validation rules. After you review staging and fix all validation issues, you can add the sign-off comment to let the PR reviewers know the updates are ready to be merged.It's easy to access the private repo version of your articles in GitHub. Just add -pr to the URL, as follows:
Public repo URL: https://github.com/Microsoft/azure-docs/blob/master/articles/azure-portal-overview.md
Private repo URL: https://github.com/Microsoft/azure-docs-pr/blob/master/articles/azure-portal-overview.md
We have closed this pull request. Please resubmit the updates through the private repo. If you need perms to the private repo, see the contributor guide instructions


Why not just make an MR to performance_test to add eCAL and fast DDS there?

@ZhenshengLee awesome work! Would be great if you could make an MR / PR back to performance_test so that others can also test eCAL and fastdds like you did here.
Would this be something you or @rex-schilasky would consider?
Also, it appears you had some issues setting up cyclonedds zero copy (specifically configuring the roudi). Would be happy to help you out here if needed.

Hi @flynneva

Would be great if you could make an MR / PR back to performance_test so that others can also test eCAL and fastdds like you did here.

I'd like to make a MR to the official repo, after the job of developing an image zero-copy example in https://github.com/ZhenshengLee/ros2_shm_msgs, so the MR/PR may be created in about two weeks.

Also, it appears you had some issues setting up cyclonedds zero copy (specifically configuring the roudi). Would be happy to help you out here if needed.

Yes, but I followed the config in https://github.com/ZhenshengLee/performance_test/blob/outdoor/master/dockerfiles/roudi_config.toml , that can be tracked in another issue.
Thanks.


[FEAT] An scrolling animation when changing page programmaticaly

Maybe I'm not getting the animation settings right, but I think that the transition from one page to another could be animated in the same way a dragging gesture does.
Maybe adding a modifier to opt-in to perform swipe animation on page change.

Hi @pblanchetteNventive , can I see your code to change the page? Are you calling it inside a withAnimation bock and using the Page.update method? Check out the examples I provide in the repo and you'll see an example of how to do this

Here's how i'm using it
struct ContentView: View {
    var body: some View {
        VStack {
            Pager(
                page: page,
                data: array,
                id: \.id,
                content: { index in
                    VStack{
                        Text("Item Content")
                    }
                    .background(index.color)
            })
            .itemAspectRatio(1)
            .draggingAnimation(.steep(duration: 1.0))
            .pagingPriority(.simultaneous)
            .loopPages()
            .onReceive(timer, perform: {_ in
                withAnimation {
                    page.update(.next)
                }
            })
            .frame(width: 400, height: 200, alignment: .center)
            .background(Color.gray.opacity(0.2))
        }
    }
}

What's timer and is it being updated in the main thread? Check out ColorExampleView to see how it works

Thanks, I checked your code in the ColorExampleView and managed to make it work !


Flakiness in TestSquareSizeIntegrationTest

Problem
TestSquareSizeIntegrationTest is flakey.
Link to the logs.
--- FAIL: TestSquareSizeIntegrationTest (61.04s)
    square_size_test.go:46: setting up square size integration test
    --- FAIL: TestSquareSizeIntegrationTest/TestSquareSizeUpperBound (49.82s)
        --- FAIL: TestSquareSizeIntegrationTest/TestSquareSizeUpperBound/gov_square_size_==_hardcoded_max (16.26s)
            square_size_test.go:137:
                	Error Trace:	/home/runner/work/celestia-app/celestia-app/app/test/square_size_test.go:1[37](https://github.com/celestiaorg/celestia-app/actions/runs/9569869274/job/26383358195?pr=3583#step:4:38)
                	Error:      	Not equal:
                	            	expected: 128
                	            	actual  : 64
                	Test:       	TestSquareSizeIntegrationTest/TestSquareSizeUpperBound/gov_square_size_==_hardcoded_max
    network.go:46: tearing down testnode

Acceptance Criteria

[ ] Resolve the flakiness.

Another instance of flakiness if this test https://github.com/celestiaorg/celestia-app/actions/runs/9584852073/job/26429395522?pr=3591

One idea to resolve the flakiness is to refactor the test to use testapp instead of a testnode. That way the test can invoke BeginBlock, DeliverTx with enough txs to fill a 128 x 128 square, EndBlock and make assertions. IMO the flakiness is caused by the current test using a testnode which runs txsim. Since txsim can't control which blocks its transactions get included in, there is no guarantee that enough txs land in one block to cause a 128 x 128 square.


test: Start coverage from python module

Runing module from python will help
portability between systems.
Those scripts may be renamed by distros,
for instance Debian provides python3-converage.
Signed-off-by: Philippe Coval<EMAIL_ADDRESS>Please fill in the fields below to submit a pull request.  The more information
that is provided, the better.
Fixes #
Description of the changes being introduced by the pull request:
Please verify and check that the pull request fulfills the following
requirements:

[x] The code follows the Code Style Guidelines
[x] Tests have been added for the bug fix or new feature
[x] Docs have been added for the bug fix or new feature

Those scripts may be renamed by distros, for instance Debian provides python3-converage.

Alternatively Debian could just stop being weird when it's no longer necessary (Bullseye has no conflicts, /usr/bin/coverage could just exist) :)
Seriously speaking I think this change looks reasonable. That said, I think the tox configuration might not run on Debian even after this: calling "python" (without a version) does not work unless you've done some extra steps, right?

yes I have added a patch that add "3" suffix:
https://salsa.debian.org/python-team/packages/tuf/-/tree/debian/master/debian/patches
maybe this could be forwarded upstream because python2 is not more supported
note that there is Debian package python-is-python3 that add the symlink.


Delete Price Labels When Not Used

We have a ton of price labels. I'm thinking through this still, but ideally the bot should be able to delete the price label if it is no longer in use by any open issues.
Ideally if we could hide it from the labels list when creating the issue.
The reason why I am a little hesitant though is because after the issues are closed it could be nice to retain the label data. For whatever its worth we could always see the Etherscan transaction to review things.

@0xcodercrane do you know why github-actions is performing the actions instead of UbiquiBot[dev]?

@0xcodercrane do you know why github-actions is performing the actions instead of UbiquiBot[dev]?

yeah because embedded github token is used instead of ubiquibot app token in marketplace.yml

Let me update it

/assign

/assign

https://etherscan.io/tx/0x2cc091b71653ddefd4df5b35c35fab0b13156538423380a234f5a39f0d7f2401


[BUG] TPC-DS-like query 77 at scale=3TB fails with maxResultSize exceeded error

Running q77 at 3TB fails with:
21/01/29 16:55:30 ERROR TaskSetManager: Total size of serialized results of 24771 tasks (1053.8 MiB) is bigger than spark.driver.maxResultSize (1024.0 MiB)

This issue is likely related to: https://github.com/NVIDIA/spark-rapids/issues/1284. But this is being run with the released 0.3 version of the plugin.
Upping the spark.driver.maxResultSize does help, but we still seem to see 20MB of output per task, which is adding up quickly.

So Apache Spark has mad this a little bit more difficult that I would like.  They are trying really hard to keep users from shooting themselves in the foot and creating an AccumulatorV2 that is not registered.  What is more when the accumulator is deserialized it auto registers it with the TaskContext. This means that I am going to have to put in an abstraction layer around GPU metrics to allow for a NOOP.

Does it help the payload size if the metric is still created but never updated?  Wonder if they've optimized for the case where a metric reports zero.

The string labels for each of the metrics are being transmitted with every update, as far as I can tell. I think this is the bulk of it too.


[fmt] Build error on x64-linux

Package<EMAIL_ADDRESS>Host Environment

Host: x64-linux
Compiler: GNU 13.2.0
vcpkg-tool version: 2024-08-01-fd884a0d390d12783076341bd43d77c3a6a15658
vcpkg-scripts version: eba7c6a89 2024-09-08 (13 hours ago)

To Reproduce
vcpkg install
Failure logs
-- Using cached fmtlib-fmt-11.0.2.tar.gz.
-- Cleaning sources at /home/licc/pkgs/vcpkg/buildtrees/fmt/src/11.0.2-463dc5ff21.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source /home/licc/pkgs/vcpkg/downloads/fmtlib-fmt-11.0.2.tar.gz
-- Applying patch fix-write-batch.patch
-- Using source at /home/licc/pkgs/vcpkg/buildtrees/fmt/src/11.0.2-463dc5ff21.clean
-- Found external ninja('1.11.1').
-- Configuring x64-linux
-- Building x64-linux-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:134 (message):
    Command failed: /home/licc/pkgs/vcpkg/downloads/tools/cmake-3.29.2-linux/cmake-3.29.2-linux-x86_64/bin/cmake --build . --config Debug --target install -- -v -j65
    Working Directory: /home/licc/pkgs/vcpkg/buildtrees/fmt/x64-linux-dbg
    See logs for more information:
      /home/licc/pkgs/vcpkg/buildtrees/fmt/install-x64-linux-dbg-out.log

Call Stack (most recent call first):
  /home/licc/sources/webrtc/mediasoup-clientpp/build/vcpkg_installed/x64-linux/share/vcpkg-cmake/vcpkg_cmake_build.cmake:74 (vcpkg_execute_build_process)
  /home/licc/sources/webrtc/mediasoup-clientpp/build/vcpkg_installed/x64-linux/share/vcpkg-cmake/vcpkg_cmake_install.cmake:16 (vcpkg_cmake_build)
  ports/fmt/portfile.cmake:19 (vcpkg_cmake_install)
  scripts/ports.cmake:192 (include)

/home/licc/pkgs/vcpkg/buildtrees/fmt/install-x64-linux-dbg-out.log
Change Dir: '/home/licc/pkgs/vcpkg/buildtrees/fmt/x64-linux-dbg'

Run Build Command(s): /home/licc/.local/bin/ninja -v -v -j65 install
[1/4] /home/licc/pkgs/gcc-13.2.0/bin/g++  -I/home/licc/pkgs/vcpkg/buildtrees/fmt/src/11.0.2-463dc5ff21.clean/include -fPIC -g -fvisibility=hidden -fvisibility-inlines-hidden -MD -MT CMakeFiles/fmt.dir/src/os.cc.o -MF CMakeFiles/fmt.dir/src/os.cc.o.d -o CMakeFiles/fmt.dir/src/os.cc.o -c /home/licc/pkgs/vcpkg/buildtrees/fmt/src/11.0.2-463dc5ff21.clean/src/os.cc
FAILED: CMakeFiles/fmt.dir/src/os.cc.o
/home/licc/pkgs/gcc-13.2.0/bin/g++  -I/home/licc/pkgs/vcpkg/buildtrees/fmt/src/11.0.2-463dc5ff21.clean/include -fPIC -g -fvisibility=hidden -fvisibility-inlines-hidden -MD -MT CMakeFiles/fmt.dir/src/os.cc.o -MF CMakeFiles/fmt.dir/src/os.cc.o.d -o CMakeFiles/fmt.dir/src/os.cc.o -c /home/licc/pkgs/vcpkg/buildtrees/fmt/src/11.0.2-463dc5ff21.clean/src/os.cc
In file included from /home/licc/pkgs/vcpkg/buildtrees/fmt/src/11.0.2-463dc5ff21.clean/include/fmt/os.h:20,
                 from /home/licc/pkgs/vcpkg/buildtrees/fmt/src/11.0.2-463dc5ff21.clean/src/os.cc:13:
/usr/include/xlocale.h:27:16: error: redefinition of ‘struct __locale_struct’
   27 | typedef struct __locale_struct
      |                ^~~~~~~~~~~~~~~
In file included from /usr/include/bits/types/locale_t.h:22,
                 from /usr/include/string.h:152,
                 from /home/licc/pkgs/vcpkg/buildtrees/fmt/src/11.0.2-463dc5ff21.clean/include/fmt/base.h:18,
                 from /home/licc/pkgs/vcpkg/buildtrees/fmt/src/11.0.2-463dc5ff21.clean/include/fmt/format.h:41,
                 from /home/licc/pkgs/vcpkg/buildtrees/fmt/src/11.0.2-463dc5ff21.clean/include/fmt/os.h:11:
/usr/include/bits/types/__locale_t.h:28:8: note: previous definition of ‘struct __locale_struct’
   28 | struct __locale_struct
      |        ^~~~~~~~~~~~~~~
/usr/include/xlocale.h:39:4: error: conflicting declaration ‘typedef int* __locale_t’
   39 | } *__locale_t;
      |    ^~~~~~~~~~
/usr/include/bits/types/__locale_t.h:42:33: note: previous declaration as ‘typedef struct __locale_struct* __locale_t’
   42 | typedef struct __locale_struct *__locale_t;
      |                                 ^~~~~~~~~~
[2/4] /home/licc/pkgs/gcc-13.2.0/bin/g++  -I/home/licc/pkgs/vcpkg/buildtrees/fmt/src/11.0.2-463dc5ff21.clean/include -fPIC -g -fvisibility=hidden -fvisibility-inlines-hidden -MD -MT CMakeFiles/fmt.dir/src/format.cc.o -MF CMakeFiles/fmt.dir/src/format.cc.o.d -o CMakeFiles/fmt.dir/src/format.cc.o -c /home/licc/pkgs/vcpkg/buildtrees/fmt/src/11.0.2-463dc5ff21.clean/src/format.cc
ninja: build stopped: subcommand failed.

Additional context
vcpkg.json
{
  "$schema": "https://raw.githubusercontent.com/microsoft/vcpkg-tool/main/docs/vcpkg.schema.json",
  "name": "zwrtc",
  "version": "0.1.0",
  "dependencies": [
    {
      "name": "ixwebsocket",
      "default-features": false,
      "features": [
        "mbedtls"
      ]
    },
    "asio",
    "spdlog",
    "doctest",
    "stb"
  ]
}

I can't reproduce this issue locally, I test this issue on the Linux with GCC 9.4.0 and GCC 13.2.0, and all install succeed.

Thank you for your work!
The problem is on a centos7 server, and according to the compilation error message, it may be related to the header file environment that comes with centos7
The problem occurs with fmt 11 and above, I ended up locking the fmt version to 10.1.1 to get around it.


Keep the app bundle and build versions in source control

We need a convenient way to set the versionCode and versionName of an app when we are sending it to the AppStore. Currently it can be set manually in the ios project generated in the platforms folder but we try to keep it out of source control.
So a few options are to keep them in:

app/App_Resources/ios/Info.plist
package.json
anywhere appropriate for source control

+1 for App_Resources: https://github.com/NativeScript/nativescript-cli/issues/1089

Info.plist in App_Resources is the first thing in my todo list for the next year. When the android is ready with their counterpart we'll just have to document this.

This is already implemented, closing the issue.


Question/Feature Request

Just a quick question. I am looking into implementing this into my environment however I was wondering if there was a way to adapt this to utilizing tags instead of TTL?
The reason behind this is we often have ec2 instances brought up with either incorrect tags or in some cases large ec2 instances that have been forgotten. This is becoming quite costly. With the ability to use this cleanup method with tags I could eliminate this all together by having people stick with a standard or have their ec2 instance removed should they not follow it.

Hey @dfaulks-ops apologies for the delayed response. You can actually achieve this using AWS Organisations. You can set up a tagging policy and if those tags aren't used, the EC2 instances can be shutdown. Have a look into that to see if it'll help.

Thank you for your response. I will have a look into that now! Have a great
day.
On Wed, May 20, 2020 at 8:44 PM Marat Levit<EMAIL_ADDRESS>wrote:

Hey @dfaulks-ops https://github.com/dfaulks-ops apologies for the
delayed response. You can actually achieve this using AWS Organisations.
You can set up a tagging policy and if those tags aren't used, the EC2
instances can be shutdown. Have a look into that to see if it'll help.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/servian/aws-auto-cleanup/issues/43#issuecomment-631811911,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APGXYVXSYUZPWXSLFRNNL5LRSR2NLANCNFSM4MJXJVFQ
.

--
Derrick Faulks
System Administrator CoLinx, LLC.
O<PHONE_NUMBER> M<PHONE_NUMBER>


Commands cannot be interrupted on Cygwin build

As the title says. I am unable to interrupt [i search function with ctrl-c or other ways. I don't know if this is a bug or just a missing feature, but it would be cool to be able to do that.

this is in fact a common theme, since a lot of commands can't be interrupted

this is in fact a common theme, since a lot of commands can't be interrupted

most commands should be interruptable. Please fill out the issue template. It is there for a reason. Also, does that happen with running from vim --clean?

I have vim compiled for cygwin:
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Mar 30 2020 21:58:19)
Included patches: 1-486
The same behaviour is observed with vim --clean
Are you saying it works for you? Try having lots of includes and interrupting.

On Mi, 30 Dez 2020, AvianY wrote:

I have vim compiled for cygwin:
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Mar 30 2020 21:58:19)
Included patches: 1-486
The same behaviour is observed with vim --clean
Are you saying it works for you? Try having lots of includes and interrupting.

No I did not observe this behaviour with [i
I was just responding to your message that most commands are not
interruptible. I think they are.
Can you please provide an easy reproducible example?
Best,
Christian
Wenn Microsoft Autos bauen würde ...
würden neue Sitze erfordern, daß alle die selbe Gesäßgröße haben.

1.) download cygwin
2.) install vim
3.) run vim however you like
4.) open a file with many includes
5.) press [i
6.) try to interrupt
7.) pikachu face

okay, now this is getting ridiculous...
Perhaps it is a cygwin issue? Can you reproduce this on a vim without Cygwin?
I had a quick look into the find_pattern_in_path() function. It already contains some checks for got_int. Perhaps its the while loop that is not interruptible?
Would you help getting this fixed and do some C profiling, which takes that long? Thanks.

I tried on vim on linux and there is no issue (I can interrupt it).... so I guess it is connected to cygwin somehow, but I would still like to solve it, because it is annoying.
I would be glad to help. How do I do what you said?

Perhaps it gets stuck in a network request?  Try changing the 'path' option to exclude problematic directories.

Are you sure 'path' could be the problem?
I tried interrupting in the same codebase on cygwin and linux with the same 'path' set and there is no problem on linux

so I guess it is connected to cygwin somehow

Well, cygwin is known to be slow.

it's not about "slow". It's about not being able to interrupt the command.

it's not about "slow". It's about not being able to interrupt the command.

Can you interrupt other commands, where on Linux it would say
"Interrupted"?  If yes, then it's not specific for [i but for Cygwin not
checking for CTRL-C.  Actually, try using the Break key (might be called
something else, depending on the keyboard).
On MS-Windows CTRL-C also means "copy", thus perhaps it doesn't
interrupt.
--
The real
trick is
this: to
keep the
lines as
short as
possible
and keep
the size
the same
yet free
from the
need for
hyphena-
Dammit!!  (Matthew Winn)
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

No, I am not able to break any command. Not even Ex command.
I tried ctrl c, pause and break and simmilar.

Although, ctrl-c does break bash commands in cygwin terminal.

On Mi, 30 Dez 2020, AvianY wrote:

No, I am not able to break any command. Not even Ex command.
I tried ctrl c, pause and break and simmilar.

Did you try Ctrl-Break (see :h dos-CTRL-Break)?
Best,
Christian
Eine Million Steuerzahler verhalten sich vernünftiger als eine
öffentliche Hand.
-- Hermann Josef Abs

Yes, I tried and it doesn't work. It can stop commands in cygwin shell, but not in vim.

For what it's worth, CTRL-C does interrupt a long [i for me on Linux x86_64 (xubuntu-18.04.5) with vim-8.2.2246.
And it shows Interrupted immediately after pressing CTRL-C.  I tried with vim --clean as well as with my full ~/.vimrc.
I don't have Windows or Cygwin.
Are other commands interruptible?  Can you e.g. interrupt :sleep 60?

Breaking works fine for me on linux as well.
I am asking specifically for vim on cygwin. I cannot break anything. Not [i, not :isearch SMTH and not :sleep 60.

So the actual problem is that on this Cygwin build CTRL-C is not considered the interrupt character.  Please update the title of the issue accordingly, it's not about the [i command doing something problematic (other than taking a while).
I'm afraid I won't have time to look into debugging a Cygwin build, I hope someone else can.

It seems that mintty is related to this issue.
When I ran Cygwin vim on Command Prompt directly, sleep was interrupted by Ctrl-C.
I'm not sure whether this is caused by mintty or Cygwin itself, though.

@AvianY this can be confirmed before asking, Cygwin had native build vim, just try there, if no, then it’s not a problem of vim, unless the recent patch changed that. Or can narrow down patch range also if so.

And mintty can configure some key’s esc value as well, as I remember..

I found that this is a modifyOtherKeys issue.
When I disabled the modifyOtherKeys, Ctrl-C worked as expected.

I can confirm @k-takata  that it works, thanks a lot. Now the question is, what do we make of this?

I can confirm @k-takata  that it works, thanks a lot. Now the question is, what do we make of this?

Ken Takata wrote:

I found that this is a modifyOtherKeys issue.
When I disabled the modifyOtherKeys, Ctrl-C worked as expected.

Aha, so apparently it doesn't reach the code in fill_input_buf() that
checks for the CTRL-C Escape sequence (src/ui.c line 1020).
Where does this build check for keys, which machine specific function is
used?
--
hundred-and-one symptoms of being an internet addict:
71. You wonder how people walk
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

Ken Takata wrote:

I found that this is a modifyOtherKeys issue.
When I disabled the modifyOtherKeys, Ctrl-C worked as expected.

Aha, so apparently it doesn't reach the code in fill_input_buf() that
checks for the CTRL-C Escape sequence (src/ui.c line 1020).
Where does this build check for keys, which machine specific function is
used?
--
hundred-and-one symptoms of being an internet addict:
71. You wonder how people walk
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

I did run vim -u NONE -N --cmd "call ch_logfile('cygwin.log', 'w')" and just typed :sleep 10and pressedCtrl-C` a couple of times.
The log looks like this:
==== start log session ====
  0.003330 : raw terminal output: "[>4;2m="
  0.004941 : raw terminal output: ""
  0.081887 : raw terminal output: "▽"
  0.082870 : raw terminal output: "  Pzz\[0%m"
  0.084498 : raw terminal output: "[>c"
  0.085092 : raw terminal output: "]10;?]11;?"
  0.085167 : SafeState: Start triggering
  0.088913 : looking for messages on channels
  0.088949 : SafeState: back to waiting, triggering SafeStateAgain
  0.106492 : raw key input: "[>77;30404;0c]10;rgb:bfbf/bfbf/bfbf]11;rgb:0000/0000/0000"
  0.107687 : raw terminal output: "[?12$p"
  0.107865 : looking for messages on channels
  0.107891 : SafeState: back to waiting, triggering SafeStateAgain
  0.137455 : raw key input: "[?12;2$y"
  0.137598 : looking for messages on channels
  0.137665 : SafeState: back to waiting, triggering SafeStateAgain
  2.480000 : raw key input: "j"
  2.480245 : SafeState: reset: key typed
  2.480413 : SafeState: Start triggering
  2.481954 : looking for messages on channels
  2.482143 : SafeState: back to waiting, triggering SafeStateAgain
  2.936416 : raw key input: ":"
  2.936648 : SafeState: reset: key typed
  2.936887 : SafeState: Start triggering
  2.938686 : looking for messages on channels
  2.938823 : SafeState: back to waiting, triggering SafeStateAgain
  3.139082 : raw key input: "s"
  3.139254 : SafeState: reset: key typed
  3.139386 : SafeState: Start triggering
  3.140188 : looking for messages on channels
  3.140300 : SafeState: back to waiting, triggering SafeStateAgain
  3.294129 : raw key input: "l"
  3.294418 : SafeState: reset: key typed
  3.294551 : SafeState: Start triggering
  3.296200 : looking for messages on channels
  3.296338 : SafeState: back to waiting, triggering SafeStateAgain
  3.386380 : raw key input: "e"
  3.386676 : SafeState: reset: key typed
  3.386875 : SafeState: Start triggering
  3.388282 : looking for messages on channels
  3.388465 : SafeState: back to waiting, triggering SafeStateAgain
  3.526711 : raw key input: "e"
  3.526957 : SafeState: reset: key typed
  3.527092 : SafeState: Start triggering
  3.528692 : looking for messages on channels
  3.528861 : SafeState: back to waiting, triggering SafeStateAgain
  3.637025 : raw key input: "p"
  3.637151 : SafeState: reset: key typed
  3.637212 : SafeState: Start triggering
  3.637687 : looking for messages on channels
  3.637751 : SafeState: back to waiting, triggering SafeStateAgain
  3.778554 : raw key input: " "
  3.778649 : SafeState: reset: key typed
  3.778687 : SafeState: Start triggering
  3.779870 : looking for messages on channels
  3.779916 : SafeState: back to waiting, triggering SafeStateAgain
  3.949400 : raw key input: "1"
  3.949523 : SafeState: reset: key typed
  3.949570 : SafeState: Start triggering
  3.949980 : looking for messages on channels
  3.950025 : SafeState: back to waiting, triggering SafeStateAgain
  3.980468 : raw key input: "0"
  3.980571 : SafeState: reset: key typed
  3.980611 : SafeState: Start triggering
  3.981381 : looking for messages on channels
  3.981454 : SafeState: back to waiting, triggering SafeStateAgain
  6.489875 : raw key input: "
"
  6.489988 : SafeState: reset: key typed
  6.491579 : ui_delay(1000)
  7.504899 : raw key input: ""
  7.505120 : looking for messages on channels
  7.505265 : ui_delay(1000)
  8.520085 : raw key input: ""
  8.520261 : looking for messages on channels
  8.520346 : ui_delay(1000)
  9.523245 : raw key input: ""
  9.523349 : looking for messages on channels
  9.523391 : ui_delay(1000)
 10.537232 : raw key input: ""
 10.537451 : looking for messages on channels
 10.537537 : ui_delay(1000)
 11.552793 : looking for messages on channels
 11.553021 : ui_delay(1000)
 12.565324 : raw key input: ""
 12.565447 : looking for messages on channels
 12.565517 : ui_delay(1000)
 13.580113 : raw key input: ""
 13.580185 : looking for messages on channels
 13.580215 : ui_delay(1000)
 14.586493 : looking for messages on channels
 14.586752 : ui_delay(1000)
 15.596159 : raw key input: ""
 15.596244 : looking for messages on channels
 15.596272 : ui_delay(894)
 16.503193 : raw key input: ""
 16.503500 : looking for messages on channels
 16.503598 : SafeState: Start triggering
 16.503697 : looking for messages on channels
 16.503754 : SafeState: back to waiting, triggering SafeStateAgain
 16.503885 : SafeState: reset: key typed
 16.515460 : looking for messages on channels
 16.527236 : SafeState: Start triggering
 16.528294 : looking for messages on channels
 16.528389 : SafeState: back to waiting, triggering SafeStateAgain
 16.641439 : raw key input: ""
 16.641640 : SafeState: reset: key typed
 16.643179 : SafeState: Start triggering
 16.644673 : looking for messages on channels
 16.644776 : SafeState: back to waiting, triggering SafeStateAgain
 17.269145 : raw key input: ":"
 17.269304 : SafeState: reset: key typed
 17.269388 : SafeState: Start triggering
 17.270356 : looking for messages on channels
 17.270499 : SafeState: back to waiting, triggering SafeStateAgain
 17.346651 : raw key input: "q"
 17.346785 : SafeState: reset: key typed
 17.346846 : SafeState: Start triggering
 17.347981 : looking for messages on channels
 17.348058 : SafeState: back to waiting, triggering SafeStateAgain
 17.486923 : raw key input: "a"
 17.487023 : SafeState: reset: key typed
 17.487080 : SafeState: Start triggering
 17.487721 : looking for messages on channels
 17.487774 : SafeState: back to waiting, triggering SafeStateAgain
 17.596503 : raw key input: "
"
 17.596638 : SafeState: reset: key typed
 17.597562 : Exiting...
 17.617552 : raw terminal output: "[>4;m"
 17.619620 : raw terminal output: ">"

According to the Mintty project, Ctrl keys send a bit other keys than xterm. If I read their wiki page correctly, it should send something like ^[[99;5u where 99 is the keycode and 5 is the modifier. So Ctrl-C should send ^[[99;5u and that is exactly what Vim sees above.
So mintty does not use the xterm modifyOtherKeys control sequences, but something similar. I think the following patch should do it:
diff --git a/src/ui.c b/src/ui.c
index 7c8667559..6573e0841 100644
--- a/src/ui.c
+++ b/src/ui.c
@@ -1018,7 +1018,10 @@ fill_input_buf(int exit_on_error UNUSED)
             */
            if (ctrl_c_interrupts && (inbuf[inbufcount] == 3
                        || (len >= 9 && STRNCMP(inbuf + inbufcount,
-                                                  "\033[27;5;99~", 10) == 0)))
+                                                  "\033[27;5;99~", 10) == 0)
+                       || (len >= 7 && STRNCMP(inbuf + inbufcount,
+                                                  "\033[99;5u", 7) == 0)
+                   ))
            {
                // remove everything typed before the CTRL-C
                mch_memmove(inbuf, inbuf + inbufcount, (size_t)(len + 1));

But perhaps it is better to disable modifyOtherKeys when we are detecting that we are running in mintty? Or the condition above should at least add a check for the terminal? However, I suppose we need a lot more changes for modifyOtherKeys in mintty, as those are quite different from xterms one.

I did run vim -u NONE -N --cmd "call ch_logfile('cygwin.log', 'w')" and just typed :sleep 10and pressedCtrl-C` a couple of times.
The log looks like this:
==== start log session ====
  0.003330 : raw terminal output: "[>4;2m="
  0.004941 : raw terminal output: ""
  0.081887 : raw terminal output: "▽"
  0.082870 : raw terminal output: "  Pzz\[0%m"
  0.084498 : raw terminal output: "[>c"
  0.085092 : raw terminal output: "]10;?]11;?"
  0.085167 : SafeState: Start triggering
  0.088913 : looking for messages on channels
  0.088949 : SafeState: back to waiting, triggering SafeStateAgain
  0.106492 : raw key input: "[>77;30404;0c]10;rgb:bfbf/bfbf/bfbf]11;rgb:0000/0000/0000"
  0.107687 : raw terminal output: "[?12$p"
  0.107865 : looking for messages on channels
  0.107891 : SafeState: back to waiting, triggering SafeStateAgain
  0.137455 : raw key input: "[?12;2$y"
  0.137598 : looking for messages on channels
  0.137665 : SafeState: back to waiting, triggering SafeStateAgain
  2.480000 : raw key input: "j"
  2.480245 : SafeState: reset: key typed
  2.480413 : SafeState: Start triggering
  2.481954 : looking for messages on channels
  2.482143 : SafeState: back to waiting, triggering SafeStateAgain
  2.936416 : raw key input: ":"
  2.936648 : SafeState: reset: key typed
  2.936887 : SafeState: Start triggering
  2.938686 : looking for messages on channels
  2.938823 : SafeState: back to waiting, triggering SafeStateAgain
  3.139082 : raw key input: "s"
  3.139254 : SafeState: reset: key typed
  3.139386 : SafeState: Start triggering
  3.140188 : looking for messages on channels
  3.140300 : SafeState: back to waiting, triggering SafeStateAgain
  3.294129 : raw key input: "l"
  3.294418 : SafeState: reset: key typed
  3.294551 : SafeState: Start triggering
  3.296200 : looking for messages on channels
  3.296338 : SafeState: back to waiting, triggering SafeStateAgain
  3.386380 : raw key input: "e"
  3.386676 : SafeState: reset: key typed
  3.386875 : SafeState: Start triggering
  3.388282 : looking for messages on channels
  3.388465 : SafeState: back to waiting, triggering SafeStateAgain
  3.526711 : raw key input: "e"
  3.526957 : SafeState: reset: key typed
  3.527092 : SafeState: Start triggering
  3.528692 : looking for messages on channels
  3.528861 : SafeState: back to waiting, triggering SafeStateAgain
  3.637025 : raw key input: "p"
  3.637151 : SafeState: reset: key typed
  3.637212 : SafeState: Start triggering
  3.637687 : looking for messages on channels
  3.637751 : SafeState: back to waiting, triggering SafeStateAgain
  3.778554 : raw key input: " "
  3.778649 : SafeState: reset: key typed
  3.778687 : SafeState: Start triggering
  3.779870 : looking for messages on channels
  3.779916 : SafeState: back to waiting, triggering SafeStateAgain
  3.949400 : raw key input: "1"
  3.949523 : SafeState: reset: key typed
  3.949570 : SafeState: Start triggering
  3.949980 : looking for messages on channels
  3.950025 : SafeState: back to waiting, triggering SafeStateAgain
  3.980468 : raw key input: "0"
  3.980571 : SafeState: reset: key typed
  3.980611 : SafeState: Start triggering
  3.981381 : looking for messages on channels
  3.981454 : SafeState: back to waiting, triggering SafeStateAgain
  6.489875 : raw key input: "
"
  6.489988 : SafeState: reset: key typed
  6.491579 : ui_delay(1000)
  7.504899 : raw key input: ""
  7.505120 : looking for messages on channels
  7.505265 : ui_delay(1000)
  8.520085 : raw key input: ""
  8.520261 : looking for messages on channels
  8.520346 : ui_delay(1000)
  9.523245 : raw key input: ""
  9.523349 : looking for messages on channels
  9.523391 : ui_delay(1000)
 10.537232 : raw key input: ""
 10.537451 : looking for messages on channels
 10.537537 : ui_delay(1000)
 11.552793 : looking for messages on channels
 11.553021 : ui_delay(1000)
 12.565324 : raw key input: ""
 12.565447 : looking for messages on channels
 12.565517 : ui_delay(1000)
 13.580113 : raw key input: ""
 13.580185 : looking for messages on channels
 13.580215 : ui_delay(1000)
 14.586493 : looking for messages on channels
 14.586752 : ui_delay(1000)
 15.596159 : raw key input: ""
 15.596244 : looking for messages on channels
 15.596272 : ui_delay(894)
 16.503193 : raw key input: ""
 16.503500 : looking for messages on channels
 16.503598 : SafeState: Start triggering
 16.503697 : looking for messages on channels
 16.503754 : SafeState: back to waiting, triggering SafeStateAgain
 16.503885 : SafeState: reset: key typed
 16.515460 : looking for messages on channels
 16.527236 : SafeState: Start triggering
 16.528294 : looking for messages on channels
 16.528389 : SafeState: back to waiting, triggering SafeStateAgain
 16.641439 : raw key input: ""
 16.641640 : SafeState: reset: key typed
 16.643179 : SafeState: Start triggering
 16.644673 : looking for messages on channels
 16.644776 : SafeState: back to waiting, triggering SafeStateAgain
 17.269145 : raw key input: ":"
 17.269304 : SafeState: reset: key typed
 17.269388 : SafeState: Start triggering
 17.270356 : looking for messages on channels
 17.270499 : SafeState: back to waiting, triggering SafeStateAgain
 17.346651 : raw key input: "q"
 17.346785 : SafeState: reset: key typed
 17.346846 : SafeState: Start triggering
 17.347981 : looking for messages on channels
 17.348058 : SafeState: back to waiting, triggering SafeStateAgain
 17.486923 : raw key input: "a"
 17.487023 : SafeState: reset: key typed
 17.487080 : SafeState: Start triggering
 17.487721 : looking for messages on channels
 17.487774 : SafeState: back to waiting, triggering SafeStateAgain
 17.596503 : raw key input: "
"
 17.596638 : SafeState: reset: key typed
 17.597562 : Exiting...
 17.617552 : raw terminal output: "[>4;m"
 17.619620 : raw terminal output: ">"

According to the Mintty project, Ctrl keys send a bit other keys than xterm. If I read their wiki page correctly, it should send something like ^[[99;5u where 99 is the keycode and 5 is the modifier. So Ctrl-C should send ^[[99;5u and that is exactly what Vim sees above.
So mintty does not use the xterm modifyOtherKeys control sequences, but something similar. I think the following patch should do it:
diff --git a/src/ui.c b/src/ui.c
index 7c8667559..6573e0841 100644
--- a/src/ui.c
+++ b/src/ui.c
@@ -1018,7 +1018,10 @@ fill_input_buf(int exit_on_error UNUSED)
             */
            if (ctrl_c_interrupts && (inbuf[inbufcount] == 3
                        || (len >= 9 && STRNCMP(inbuf + inbufcount,
-                                                  "\033[27;5;99~", 10) == 0)))
+                                                  "\033[27;5;99~", 10) == 0)
+                       || (len >= 7 && STRNCMP(inbuf + inbufcount,
+                                                  "\033[99;5u", 7) == 0)
+                   ))
            {
                // remove everything typed before the CTRL-C
                mch_memmove(inbuf, inbuf + inbufcount, (size_t)(len + 1));

But perhaps it is better to disable modifyOtherKeys when we are detecting that we are running in mintty? Or the condition above should at least add a check for the terminal? However, I suppose we need a lot more changes for modifyOtherKeys in mintty, as those are quite different from xterms one.

donot know those code much, but for your reference: you are right.
void other_code(wchar c) {
    trace_key("other");
    len = sprintf(buf, "\e[%u;%uu", c, mods + 1);
  }

looks this is mintty 's 'other key'.. vs xterm 's '27' sth...

donot know those code much, but for your reference: you are right.
void other_code(wchar c) {
    trace_key("other");
    len = sprintf(buf, "\e[%u;%uu", c, mods + 1);
  }

looks this is mintty 's 'other key'.. vs xterm 's '27' sth...

@brammool hate to say, but like #7574 said, i am not care, but e.g this ticket, looks many guys joined to discuss to find out the cause.. just a friendly..wish... :(

@brammool hate to say, but like #7574 said, i am not care, but e.g this ticket, looks many guys joined to discuss to find out the cause.. just a friendly..wish... :(

https://github.com/vim/vim/issues/4518#issuecomment-754656370

https://github.com/vim/vim/issues/4518#issuecomment-754656370


Implement directional window splitting

While VSCode allows splitting of windows to the left using ctrl+\, Atom allows splitting in 4 directions with the shortcut ctrl+k, <arrow>. The main advantage this has over the current workbench.action.splitEditor command is that it enables splitting the editor to allow both horizontal and vertical layouts.
Note: VSCode currently uses ctrl+k, up and ctrl+k, down for opening the previous and next working file.

I agree horizontal splitting would be awesome :D

@stevencl @bgashler1 @bpasero not sure if there's a dupe for this already

#1749


Bintools Wrapper: Init by refactoring out of cc-wrapper, take 2

edit see my question in https://github.com/NixOS/nixpkgs/pull/29396#issuecomment-333688023
Motivation for this change
This is meant to be reviewed commit by commit.
This is needed so packages that just use binutils get the same setup-hook support. That is, variables like BUILD_AS or LD should be defined the same way, along with the LD_FLAGS.  This will be necessary to clean up at least the gcc derivation (which must be built with an unwrapped binutils when target != host), and probably other compilers too.
More broadly, having two wrappers will help enforce proper layering between binutils and the C compiler. For languages besides C/C++, it would be neat to use `stdenvNoCC + binutils, avoiding a C compiler dependency. This wrapper makes that change possible.
@edolstra I'm hoping for you to merge this change when you approve of it, to avoid a repeat of last time.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built stdenv on platform(s)

[ ] NixOS --- in progress
[x] macOS
[ ] Linux

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

[Blocked by https://github.com/NixOS/nixpkgs/pull/29568]

I'm rebuilding now, but I've built other PRs containing this so quite confident it will succeed. This is ready for final review!

On second thought, I'd like to rename this utils-wrapper, and stdenv.cc.utils. "cctools + GNU binutils" is also wrapped, and isn't "GNU Binutils" so I think a name like "utils" would be better.

@Ericson2314 that seems fine to me

I'm going to wait to kick of a nixborg mass rebuild until https://github.com/NixOS/nixpkgs/pull/31775 is finished, but this is now again ready for rebuild.

@nixborg buidl

@nixborg build

Jobset created at https://hydra.mayflower.de/jobset/nixos/pr-29396

Jobset created at https://hydra.mayflower.de/jobset/nixos/pr-29396

@nixborg build

Jobset created at https://hydra.mayflower.de/jobset/nixos/pr-29396

@nixborg build

Jobset created at https://hydra.mayflower.de/jobset/nixos/pr-29396

I built Atlas locally (without any rebase, unlike nixborg) and it succeeded. This reassures me the build failure is spurious / from something else, not a problem with the wrapper and gfortran as I feared.

I've add a few more cleanups on top, doing another rebuild.

@nixborg build

Curious whether the last LDEMULATION-defining commit unbroke cross, so repurposed https://hydra.nixos.org/jobset/nixpkgs/ericson2314-cross-trunk . If not, I'll just give up on --enable-targets=all in binutils: it's less a panacea than I thought because the GNU Assembler doesn't become multi-target.

Jobset created at https://hydra.mayflower.de/jobset/nixos/pr-29396

If not, I'll just give up on --enable-targets=all in binutils

I think multitarget binutils (enabled in https://github.com/NixOS/nixpkgs/pull/30484/commits/f8741c38cd546e3ff18ce9d708de14ff2aae68ab) is a good thing even if they can not be used for cross.

@nixborg build

Jobset created at https://hydra.mayflower.de/jobset/nixos/pr-29396

@nixborg build

Jobset created at https://hydra.mayflower.de/jobset/nixos/pr-29396

@nixborg build

Jobset created at https://hydra.mayflower.de/jobset/nixos/pr-29396

https://github.com/NixOS/nixpkgs/pull/26805 is needed to fix progated inputs, so there's little point trying cross with this PR alone. I moved the LDEMULATION commit to that other PR accordingly. I also pullled  some non-controversial stuff out of the end of this into https://github.com/NixOS/nixpkgs/issues/28448 into https://github.com/NixOS/nixpkgs/issues/28448.
I'm looking to merge this within the week, so I can get onward to the more interesting cross stuff. I now count 3 separate instances of people decently blocked on me unbreaking things, and this has sat open for a while. @edolstra you're the point person for a change this big, so let me know what I can do to help you review.

These breaks the build of libstdcxx5.

@nixborg build

Jobset created at https://hydra.mayflower.de/jobset/nixos/pr-29396

@grahamc what is the nix-instantiate ... that's failing? the ellipses won't expand.

If you triple-click the text it'll select it all and you can copy it out: grahamcofborg-eval-nixpkgs-unstable-jobset — nix-instantiate ./pkgs/top-level/release.nix -A unstable

@grahamc thanks!

Ah, I did dynamic-linker-32 not dynamic-linker-m32 in the fix. @orivej I think I fixed those issues you mentioned.

@nixborg build

Jobset created at https://hydra.mayflower.de/jobset/nixos/pr-29396

@orivej both are now fixed

@edolstra told me he doesn't have time to review this any time soon, so we might as well not hold it up further. Yay, thanks!
This has passed nixborg CI many times before. the last change is a mass rebuild, but just from merging with staging. The post-merge change is just an eval fix for a newer package (clang multilib). Merging, but will keep an I on staging just in case.

This bloke bloaty, fixed in fe61c3b84e8e81a8ec2bf6b3ed2a0e8652cea190.

This broke lispPackages.cl-fuse. @Ericson2314 could you fix it? It exports NIX_LDFLAGS with -L/nix/store/wr579906xik1qbnblm0wq1nissxh53sy-fuse-2.9.7/lib and runs gcc (wrapper), but gcc invokes unwrapped gcc without these NIX_LDFLAGS. Here is this sequence of steps: https://gist.github.com/orivej/4c8fc1b12d8d630edf24b6ff5f88cd80 (141-142-sbcl runs sbcl, which runs gcc in the same way as 142-143-gcc, which runs the unwrapped gcc just like 143-144-gcc .) Here is how NIX_LDFLAGS are defined: https://github.com/NixOS/nixpkgs/blob/ea15e43693908291b48f3852c32721a085aa8f84/pkgs/development/lisp-modules/define-package.nix#L23

Two perl packages,perlPackages.EncodeDetect and perlPackages.ExtUtilsCppGuess, fail to build with ld: cannot find -lstdc++. They are needed for spamassassin and slic3r. @Ericson2314 agreed to try to fix them.
It seems that lispPackages.cl-fuse may not be fixed before the merge to master. /cc @7c6f434c

Can't fix this instant, but the crux of the Perl packages' problem is that ld no longer magically see's into the C(XX)'s compiler's lib directory. LD=$CC might be the best solution to avoid violating layers.

Thanks! I'm fixing perl packages in #32830.

Hm. I don't really understand where NIX_LDFLAGS gets lost in CL-Fuse build… So I gave up and the shared library is now prebuilt separately.


Add Nong Song:

Song Name
Yoru Ni Kakeru (Racing Into The Night)
Artist Name
YOASOBI
Source
Direct file download
Youtube Link
No response
Direct File Link
https://api.songfilehub.com/song/64f54c6ceba5efcdadf789a7?download=true&name=1024087
Song ID
1024087
Extra
Used in the level "Kuzureta" by Teno and other variations (LDMs, easier versions, etc.)

reject
don't add files from songfilehub


docs: Improve examples

improving the existing examples

@B4nan used removed using Dataset instead used crawler
anything else that I can improve in examples?


Add new NN blocks: "get weight from ... to ..." and "get bias of ..."

not only setting weight/bias, but also getting the values should be supported

already implemented


Tests are failing due to ModuleNotFoundError

see https://github.com/CWorthy-ocean/roms-tools/actions/runs/8972322248/job/24640316780
The error is
ModuleNotFoundError: No module named 'scipy'
even though scipy is now part of https://github.com/CWorthy-ocean/roms-tools/blob/main/ci/environment.yml
@TomNicholas any idea what is going wrong?

I have no idea 😕 Does it run locally with an env set up from the same yml file?

Locally, I do
conda env create -f ci/environment.yml
conda activate romstools-test

and then
pytest

which successfully runs the four tests in https://github.com/CWorthy-ocean/roms-tools/blob/main/roms_tools/tests/test_setup.py.
So the ci/environment.yml itself seems to be okay.

Do we maybe have to add scipy to pyproject.toml?


Add link to quick start to see the generated page.

Add link to quick start to see the generated page.
Added new note to permalinks to know that index.* is special case and it goes to root /
Re-do of PR#68

Yes this is a wonderful addition, thank you for taking my feedback!


Can't scan datetime into time.Time

Trying to scan a *time.Time (select datetime('now')) using the below running example gives the error:

panic: cannot scan row: sql: Scan error on column index 0: unsupported Scan, storing driver.Value type []uint8 into type *time.Time

I would expect it to not give an error and instead populate the Time variable with the result, because time.Time/datetime is in the list of supported types.
However, changing the Time variable to string works as expected and outputs:

the time is: 2016-07-08 22:01:38

package main

import (
	"database/sql"
	"fmt"
	"time"

	_ "github.com/mattn/go-sqlite3"
)

func main() {
	db, err := sql.Open("sqlite3", ":memory:")
	if err != nil {
		panic(fmt.Sprintf("cannot open db: %v", err))
	}
	err = db.Ping()
	if err != nil {
		panic(fmt.Sprintf("cannot open db: %v", err))
	}
	// interesting stuff starts here
	row := db.QueryRow(`select datetime('now')`)
	var t time.Time
	// var t string  // NOTE: using this declaration for t works
	if err = row.Scan(&t); err != nil {
		panic(fmt.Sprintf("cannot scan row: %v", err))
	}
	fmt.Printf("the time is: %s\n", t)
}

See issue #190

Thanks for the link. Closing as a duplicate.