Add AWS::Organizations::Organization

Add AWS::Organizations::Organization

Looks like the CodeBuild failed, may be due to some pre-commit checks

Bot failed, retrying PR


chore: remove metadata for internal modules

Np! I opened an issue to track https://github.com/GoogleCloudPlatform/cloud-foundation-toolkit/issues/1426


Invoke-DscResource doesn't display any stream output from the dsc resource

Steps to reproduce
Invoke a dsc resource that contains any stream ouput (ex. Verbose). Below is a simple example only to demonstrate verbose output.
StreamTest.psm1
[DscResource()]
class MyTestResource
{
    [DscProperty(Key)]
    [string] $SomeVal

	[void] Set() {
                Write-Verbose "Entered Set method"
	}

	[MyTestResource] Get() {
		Write-Verbose "Entered Get method"

		return $this
	}

	[bool] Test() {
		Write-Verbose "Entered Test method"

                return $true
	}
}

StreamTest.psd1
@{

    # Script module or binary module file associated with this manifest.
    RootModule = 'StreamTest.psm1'

    DscResourcesToExport = @(
    'MyTestResource'
    )

    # Version number of this module.
    ModuleVersion = '<IP_ADDRESS>'

    # ID used to uniquely identify this module
    GUID = '6c583f5e-3712-432d-a65c-29f665a7a07a'

    # Minimum version of the Windows PowerShell engine required by this module
    PowerShellVersion = '5.0'
}

Invoking the dsc resource
$splat = @{
    Name = 'MyTestResource'
    ModuleName = 'StreamTest'
    Method = 'Test'
    Property = @{
        SomeVal = 'Test'
    }
    Verbose = $true
}

Invoke-DscResource @splat

Expected behavior
Should display verbose output from the dsc resource.
Actual behavior
Does not display verbose output from the dsc resource.

Environment data

Name
Value

PSVersion
7.1.0

PSEdition
Core

GitCommitId
7.1.0

OS
Microsoft Windows 10.0.18363

Platform
Win32NT

PSCompatibleVersions
{1.0, 2.0, 3.0, 4.0…}

PSRemotingProtocolVersion
2.3

SerializationVersion
<IP_ADDRESS>

WSManStackVersion
3.0

I should test this again but I think it was fixed in 7.3, or somewhere in 7.2 by Andrew...


Feature Request: YouTube Music Support

I wanna thank you for letting us have a part of the youtube red experience. I use youtube music app because it works as a great radio service. I would love if you could mimic the same functionality over to the youtube music app. I am not a developer so I wouldn't know if I am asking for a minor tweak or a whole new module. I hope it is gonna be as helpful to others and you as it would be to me.

I realised this question has been answered in the closed section, therefore I closed it.


Object fields initialization

I see that Wangscape uses the same name for constructor arguments as for class attributes (in TilesetGenerator). It could be a problem after changing (or removing) name of any argument. Consider this example:
#include <iostream>

struct A
{
    A(int /* a */)
        : a(a)
    {}
    int a;
};

int main()
{
    A a(3);
    std::cout << a.a << "\n";
}

It compiles (at least without warnings flag, it should be an error in my opinion) and runs. std::cout prints e.g.:
> ./h
-1654812272
> ./h
1764974992
> ./h
-807848544
> ./h
-1030225712
> ./h
1040083440

...and because of that, I want to suggest adding _ suffix to class members (and enable all warning flags + treat warnings as errors) to emphasise the difference between them and constructor's arguments, so after attribute name removal it will be:
#include <iostream>

struct A
{
    A(int /* a */)
        : a_(a)
    {}
    int a_;
};

int main()
{
    A a(3);
    std::cout << a.a_ << "\n";
}

and won't compile at all. I noticed there is a m prefix in (at least) one class - that's another way to do it :). Maybe there could be a small CONTRIBUTING.md file with some style/naming rules (that's good example for me: https://github.com/openstreetmap/osm2pgsql/blob/master/CONTRIBUTING.md)? I think we could use one of formatting tools to check it (code style) during Travis build (as soon as it will work). I linked already my cpp project in one of comments - it uses the clang-format tool (configuration file).

I see that Wangscape uses the same name for constructor arguments as for class attributes (in TilesetGenerator). It could be a problem after changing (or removing) name of any argument. Consider this example:
[snip]
It compiles (at least without warnings flag, it should be an error in my opinion) and runs. std::cout prints e.g.:
[snip]
...and because of that, I want to suggest adding _ suffix to class members (and enable all warning flags + treat warnings as errors) to emphasise the difference between them and constructor's arguments, so after attribute name removal it will be:
[snip]
and won't compile at all. I noticed there is a m prefix in (at least) one class - that's another way to do it :).
I don't plan to use unnamed parameters in constructors (the most likely use cases for them are callbacks, virtual functions, and post-increment/decrement operators). But the codebase is still unstable and there is a possibility that changes like that may be made accidentally. So, it would be worthwhile to require differently named data variables and contructor parameters.

I prefer to keep classes' public interfaces as clean as possible, so the trailing underscores would have to be in the parameter names. m prefixes are used in private and protected data members.

Maybe there could be a small CONTRIBUTING.md file with some style/naming rules (that's good example for me: https://github.com/openstreetmap/osm2pgsql/blob/master/CONTRIBUTING.md)? I think we could use one of formatting tools to check it (code style) during Travis build (as soon as it will work). I linked already my cpp project in one of comments - it uses the clang-format tool (configuration file).
Yes, a contributing guide and automatic format checking would be a worthwhile addition to the project. Once the architecture of the code is more settled it would be a good idea to choose a documentation tool and format.

As of https://github.com/Wangscape/Wangscape/commit/3119049e1331e95ff1123d86f95ebeed068c2275 there are no more constructor parameters sharing their name with a data member, so this can be closed. We can open a separate issue for automatic format checking.


Minor fixes

Description
Minor fixes

Codecov Report

Merging #848 (1e4a511) into master (d4959d2) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #848   +/-   ##
=======================================
  Coverage   60.05%   60.05%
=======================================
  Files          22       22
  Lines        2899     2899
=======================================
  Hits         1741     1741
  Misses        965      965
  Partials      193      193

Impacted Files
Coverage Δ

server/router_utils.go
71.64% <100.00%> (ø)

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 d4959d2...1e4a511. Read the comment docs.


Bring closed-source LicenseManager to main SDK repository

This allows users to compile SDK locally with full support accessing CARTO services.

Amazing!

Done. Closing this.


Refactor requirements

retest this please

retest this please

I don't have time to dig through all of this, but I'll note after working with them that the Mapper classes have a lot of duplicated logic both between themselves and OfferEvaluator. Knowledge of evaluation stages should be concentrated in one place and the ad hoc Labels classes are duplicated between the two (not sure they need to exist, IMO, their scope is so small that the nominal "type safety" benefit they provide over e.g. a map isn't worth the hit to convenience).

@nickbp and @mrbrowning: I'll look at the mapper/label classes in detail after I get CI passing.

retest this please

retest this please

retest this please


Feature request:  Allow custom dumping location

This tool is commonly used as part of a toolchain for being able to mod UWP games (example:  https://www.reddit.com/r/OutreachHPG/comments/gowlwb/how_to_add_mods_to_mechwarrior_5_mercenaries_pc/)
These games can be in excess of 50GB, which can be hard to fit on OS drive (current default for the tool).  Having the ability to redirect the dump to a custom location will unblock this process for many users.

After digging in on the code, I can see why this may be tricky.
I tried to add an additional IPC for SetDumpPath, but it looks like the IPC mechanism being used to pass process IDs relies on atomics which don't like strings.

Last bit to close this out.
Turns out that when you install a UWP app in a location other than your OS drive, the system creates a series of hard links on your OS drive to the install location.
Functionally this means that when you dump a UWP, it will dump it to a folder on the OS drive that actually redirects to the app's install location.

Ah yea these are all similar conclusions that I've made myself on the matter.. I've ran into this issue myself as games have started to simply get massive but UWP virtualization is very tight about what folders you can touch and what you can hardlink and softlink and all that mess.
The Shared-Memory that I use for IPC can do a lot if you use it right(but you have to use the data on the shared pages, so a heap allocation in process 1 will not make sense in process 2, you have to copy it into the shared memory).
I think the better direction for this is to read the file on the UWP side, and the pump the file data through the IPC onto a listening windows-space executable so that it can create and write the file "anywhere" on the OS outside of UWP space.
So rather than a file-copy within UWP, the UWP dumper is telling the windows side to create files and pipes through the file data itself. It may be much slower but it would be the most flexible.


Updating Angular to v13 installs a few Angular v14 packages

🐞 Bug report
Command (mark with an x)

[ ] new
[ ] build
[ ] serve
[ ] test
[ ] e2e
[ ] generate
[ ] add
[x] update
[ ] lint
[ ] extract-i18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Description
After I wanted to upgrade a NG v12 project to v13, some NG v14 packages were installed.
I run the update process via
ng update @angular/cdk@13 @angular/cli@13 @angular/core@13 @ngrx/store ng-mocks --force as ng update suggested it.

However, the update installed a mixture of v13 and v14 packages.

PS: I am not sure if the --force has anything to do with it, but I could not do the update without it.
🌍 Your Environment

$ ng version
Your global Angular CLI version (14.0.0-rc.0) is greater than your local version (13.3.7). The local Angular CLI version is used.

What was the error message when not using the --force option? Can you please provide the contents of the  package.json prior to the update?

❯ ng update @angular/cdk@13 @angular/cli@13 @angular/core@13 @ngrx/store ng-mocks
The installed Angular CLI version is outdated.
Installing a temporary Angular CLI versioned 13.3.7 to perform the update.
✔ Packages successfully installed.
Using package manager: 'yarn'
Collecting installed dependencies...
Found 133 dependencies.
Fetching dependency metadata from registry...
                  Package "<internal package>" has an incompatible peer dependency to "@angular/language-service" (requires ">=7.0.0 <11.0.0" (extended), would install "14.0.0").
                  Package "@angular-devkit/build-angular" has an incompatible peer dependency to "typescript" (requires ">=4.4.3 <4.7", would install "4.7.2").
                  Package "@angular-devkit/build-angular" has an incompatible peer dependency to "@angular/compiler-cli" (requires "^13.0.0 || ^13.3.0-rc.0", would install "14.0.0")
                  Package "@angular-devkit/build-angular" has an incompatible peer dependency to "typescript" (requires ">=4.4.3 <4.7", would install "4.7.2")
                  Package "@angular/animations" has an incompatible peer dependency to "@angular/core" (requires "14.0.0", would install "13.3.11")
                  Package "<internal package>" has an incompatible peer dependency to "@angular/animations" (requires "^12.x" (extended), would install "14.0.0").
                  Package "<internal package>" has an incompatible peer dependency to "@angular/cdk" (requires "^12.x", would install "13.3.9").
                  Package "@angular/common" has an incompatible peer dependency to "@angular/core" (requires "14.0.0", would install "13.3.11")
                  Package "<internal package>" has an incompatible peer dependency to "@angular/common" (requires "^12.2.15" (extended), would install "14.0.0").
                  Package "@angular/compiler" has an incompatible peer dependency to "@angular/core" (requires "14.0.0", would install "13.3.11")
                  Package "<internal package>" has an incompatible peer dependency to "@angular/compiler" (requires ">=7.0.0 <11.0.0" (extended), would install "14.0.0").
                  Package "@angular/animations" has an incompatible peer dependency to "@angular/core" (requires "14.0.0" (extended), would install "13.3.11").
                  Package "@angular/elements" has an incompatible peer dependency to "@angular/core" (requires "14.0.0", would install "13.3.11")
                  Package "@angular/forms" has an incompatible peer dependency to "@angular/core" (requires "14.0.0", would install "13.3.11")
                  Package "<internal package>" has an incompatible peer dependency to "@angular/forms" (requires "^12.x" (extended), would install "14.0.0").
                  Package "@angular/platform-browser" has an incompatible peer dependency to "@angular/core" (requires "14.0.0", would install "13.3.11")
                  Package "<internal package>" has an incompatible peer dependency to "@angular/platform-browser" (requires ">=7.0.0 <11.0.0" (extended), would install "14.0.0").
                  Package "@angular/platform-browser-dynamic" has an incompatible peer dependency to "@angular/core" (requires "14.0.0", would install "13.3.11")
                  Package "<internal package>" has an incompatible peer dependency to "@angular/platform-browser-dynamic" (requires ">=7.0.0 <11.0.0" (extended), would install "14.0.0").
                  Package "@angular/platform-server" has an incompatible peer dependency to "@angular/core" (requires "14.0.0", would install "13.3.11")
                  Package "@angular/router" has an incompatible peer dependency to "@angular/core" (requires "14.0.0", would install "13.3.11")
                  Package "<internal package>" has an incompatible peer dependency to "@angular/router" (requires "^12.x" (extended), would install "14.0.0").
                  Package "@ngrx/router-store" has an incompatible peer dependency to "@angular/common" (requires "^13.0.0", would install "14.0.0")
                  Package "@ngrx/router-store" has an incompatible peer dependency to "@angular/router" (requires "^13.0.0", would install "14.0.0")
✖ Migration failed: Incompatible peer dependencies found.
Peer dependency warnings when installing dependencies means that those dependencies might not work correctly together.
You can use the '--force' option to ignore incompatible peer dependencies and instead address these warnings later.
  See "/private/var/folders/y7/grv62hc90zn8h8k24gkj8b2h0000gn/T/ng-5s4x7k/angular-errors.log" for further details.

This whole upgrade process is currently just a POC to see if we can get rid of a JavaScript heap-out-of-memory error we've had since updating to v12 of our very large app. We haven't had a chance to update our libs to v13/14 yet, but we had used ng update with --force in the past with no issues like this. FYI, for confidentiality reasons, I have replaced some of my company's internal packages.

I have tried to reproduce this on a smaller scale. I created a test project with this package.json
{
  "name": "ng-mixed-packages",
  "version": "0.0.0",
  "scripts": {
    "ng": "ng",
    "start": "ng serve",
    "build": "ng build",
    "watch": "ng build --watch --configuration development",
    "test": "ng test"
  },
  "private": true,
  "dependencies": {
    "@angular/animations": "^12.2.16",
    "@angular/cdk": "^12.2.13",
    "@angular/common": "^12.2.16",
    "@angular/compiler": "^12.2.16",
    "@angular/core": "^12.2.16",
    "@angular/elements": "^12.2.16",
    "@angular/forms": "^12.2.16",
    "@angular/platform-browser": "^12.2.16",
    "@angular/platform-browser-dynamic": "^12.2.16",
    "@angular/platform-server": "^12.2.16",
    "@angular/router": "^12.2.16",
    "rxjs": "~6.6.0",
    "tslib": "^2.3.0",
    "zone.js": "~0.11.4"
  },
  "devDependencies": {
    "@angular/compiler-cli": "^12.2.16",
    "@angular/language-service": "^12.2.16",
    "@angular-devkit/build-angular": "~12.2.17",
    "@angular/cli": "~12.2.17",
    "@types/jasmine": "~3.8.0",
    "@types/node": "^12.11.1",
    "jasmine-core": "~3.8.0",
    "karma": "~6.3.0",
    "karma-chrome-launcher": "~3.1.0",
    "karma-coverage": "~2.0.3",
    "karma-jasmine": "~4.0.0",
    "karma-jasmine-html-reporter": "~1.7.0",
    "typescript": "~4.3.5"
  }
}

Here is the output of ng update @angular/cdk@13 @angular/cli@13 @angular/core@13
❯ ng update @angular/cdk@13 @angular/cli@13 @angular/core@13
The installed Angular CLI version is outdated.
Installing a temporary Angular CLI versioned 13.3.7 to perform the update.
✔ Packages successfully installed.
Using package manager: 'yarn'
Collecting installed dependencies...
Found 27 dependencies.
Fetching dependency metadata from registry...
                  Package "@angular-devkit/build-angular" has an incompatible peer dependency to "@angular/compiler-cli" (requires "^13.0.0 || ^13.3.0-rc.0", would install "14.0.0")
                  Package "@angular-devkit/build-angular" has an incompatible peer dependency to "typescript" (requires ">=4.4.3 <4.7", would install "4.7.2")
                  Package "@angular-devkit/build-angular" has an incompatible peer dependency to "typescript" (requires ">=4.4.3 <4.7", would install "4.7.2").
                  Package "@angular/animations" has an incompatible peer dependency to "@angular/core" (requires "14.0.0", would install "13.3.11")
                  Package "@angular/common" has an incompatible peer dependency to "@angular/core" (requires "14.0.0", would install "13.3.11")
                  Package "@angular/compiler" has an incompatible peer dependency to "@angular/core" (requires "14.0.0", would install "13.3.11")
                  Package "@angular/animations" has an incompatible peer dependency to "@angular/core" (requires "14.0.0" (extended), would install "13.3.11").
                  Package "@angular/elements" has an incompatible peer dependency to "@angular/core" (requires "14.0.0", would install "13.3.11")
                  Package "@angular/forms" has an incompatible peer dependency to "@angular/core" (requires "14.0.0", would install "13.3.11")
                  Package "@angular/platform-browser" has an incompatible peer dependency to "@angular/core" (requires "14.0.0", would install "13.3.11")
                  Package "@angular/platform-browser-dynamic" has an incompatible peer dependency to "@angular/core" (requires "14.0.0", would install "13.3.11")
                  Package "@angular/platform-server" has an incompatible peer dependency to "@angular/core" (requires "14.0.0", would install "13.3.11")
                  Package "@angular/router" has an incompatible peer dependency to "@angular/core" (requires "14.0.0", would install "13.3.11")
✖ Migration failed: Incompatible peer dependencies found.
Peer dependency warnings when installing dependencies means that those dependencies might not work correctly together.
You can use the '--force' option to ignore incompatible peer dependencies and instead address these warnings later.
  See "/private/var/folders/y7/grv62hc90zn8h8k24gkj8b2h0000gn/T/ng-5Bk5w1/angular-errors.log" for further details.

Could it be that @angular-devkit/build-angular is the culprit because of would install "14.0.0" & would install "4.7.2"?
Package "@angular-devkit/build-angular" has an incompatible peer dependency to "@angular/compiler-cli" (requires "^13.0.0 || ^13.3.0-rc.0", would install "14.0.0")
Package "@angular-devkit/build-angular" has an incompatible peer dependency to "typescript" (requires ">=4.4.3 <4.7", would install "4.7.2")

I have tried to reproduce this on a smaller scale. I created a test project with this package.json
{
  "name": "ng-mixed-packages",
  "version": "0.0.0",
  "scripts": {
    "ng": "ng",
    "start": "ng serve",
    "build": "ng build",
    "watch": "ng build --watch --configuration development",
    "test": "ng test"
  },
  "private": true,
  "dependencies": {
    "@angular/animations": "^12.2.16",
    "@angular/cdk": "^12.2.13",
    "@angular/common": "^12.2.16",
    "@angular/compiler": "^12.2.16",
    "@angular/core": "^12.2.16",
    "@angular/elements": "^12.2.16",
    "@angular/forms": "^12.2.16",
    "@angular/platform-browser": "^12.2.16",
    "@angular/platform-browser-dynamic": "^12.2.16",
    "@angular/platform-server": "^12.2.16",
    "@angular/router": "^12.2.16",
    "rxjs": "~6.6.0",
    "tslib": "^2.3.0",
    "zone.js": "~0.11.4"
  },
  "devDependencies": {
    "@angular/compiler-cli": "^12.2.16",
    "@angular/language-service": "^12.2.16",
    "@angular-devkit/build-angular": "~12.2.17",
    "@angular/cli": "~12.2.17",
    "@types/jasmine": "~3.8.0",
    "@types/node": "^12.11.1",
    "jasmine-core": "~3.8.0",
    "karma": "~6.3.0",
    "karma-chrome-launcher": "~3.1.0",
    "karma-coverage": "~2.0.3",
    "karma-jasmine": "~4.0.0",
    "karma-jasmine-html-reporter": "~1.7.0",
    "typescript": "~4.3.5"
  }
}

Here is the output of ng update @angular/cdk@13 @angular/cli@13 @angular/core@13
❯ ng update @angular/cdk@13 @angular/cli@13 @angular/core@13
The installed Angular CLI version is outdated.
Installing a temporary Angular CLI versioned 13.3.7 to perform the update.
✔ Packages successfully installed.
Using package manager: 'yarn'
Collecting installed dependencies...
Found 27 dependencies.
Fetching dependency metadata from registry...
                  Package "@angular-devkit/build-angular" has an incompatible peer dependency to "@angular/compiler-cli" (requires "^13.0.0 || ^13.3.0-rc.0", would install "14.0.0")
                  Package "@angular-devkit/build-angular" has an incompatible peer dependency to "typescript" (requires ">=4.4.3 <4.7", would install "4.7.2")
                  Package "@angular-devkit/build-angular" has an incompatible peer dependency to "typescript" (requires ">=4.4.3 <4.7", would install "4.7.2").
                  Package "@angular/animations" has an incompatible peer dependency to "@angular/core" (requires "14.0.0", would install "13.3.11")
                  Package "@angular/common" has an incompatible peer dependency to "@angular/core" (requires "14.0.0", would install "13.3.11")
                  Package "@angular/compiler" has an incompatible peer dependency to "@angular/core" (requires "14.0.0", would install "13.3.11")
                  Package "@angular/animations" has an incompatible peer dependency to "@angular/core" (requires "14.0.0" (extended), would install "13.3.11").
                  Package "@angular/elements" has an incompatible peer dependency to "@angular/core" (requires "14.0.0", would install "13.3.11")
                  Package "@angular/forms" has an incompatible peer dependency to "@angular/core" (requires "14.0.0", would install "13.3.11")
                  Package "@angular/platform-browser" has an incompatible peer dependency to "@angular/core" (requires "14.0.0", would install "13.3.11")
                  Package "@angular/platform-browser-dynamic" has an incompatible peer dependency to "@angular/core" (requires "14.0.0", would install "13.3.11")
                  Package "@angular/platform-server" has an incompatible peer dependency to "@angular/core" (requires "14.0.0", would install "13.3.11")
                  Package "@angular/router" has an incompatible peer dependency to "@angular/core" (requires "14.0.0", would install "13.3.11")
✖ Migration failed: Incompatible peer dependencies found.
Peer dependency warnings when installing dependencies means that those dependencies might not work correctly together.
You can use the '--force' option to ignore incompatible peer dependencies and instead address these warnings later.
  See "/private/var/folders/y7/grv62hc90zn8h8k24gkj8b2h0000gn/T/ng-5Bk5w1/angular-errors.log" for further details.


Add URL for Logstash module

I'm not sure which format you want for custom modul links, this is a suggestion. What do you think is appropriate?

Looks good!


[TB] Correct text in Button section of Color Theme panel

Problem/Concern
The text in the Button section of the Color Theme panel mentions the "To:" field.  It is obviously a copy/paste error since the text is identical to the gradient section above it.

Proposed Solution
Remove or improve the text for the Button section of the Color Theme panel.

fixed


Missing FormControl Button

I have an .xlsm file that contains a macro tied to a button.
If I run the following:
const xlsx = require('xlsx');

const workbook = xlsx.readFile('./test.xlsm', { bookVBA: true });
xlsx.writeFile(workbook, './test_saved.xlsm');

and open test_saved.xlsm, the button is missing. The macro is still available but the button is gone.
Some simple steps to reproduce (in Office 2019)

Create a blank workbook
Add a button via Developer tab -> Insert. Click the button icon under Form Controls
Record whatever macro you want when you add the button
Save file as test.xlsm
Run the code above
Open test_saved.xlsm

I'd upload my test.xlsm if I could.

need to specify the option bookVBA: true on write:
const xlsx = require('xlsx');

const workbook = xlsx.readFile('./test.xlsm', { bookVBA: true });
xlsx.writeFile(workbook, './test_saved.xlsm', { bookVBA: true });

need to specify the option bookVBA: true on write

still does not work

email the file to<EMAIL_ADDRESS>

hey @tchari , did you end up solving this issue?

No, I am using a different product/solution instead.

There are two types of controls in Excel:

"ActiveX controls" are stored in the VBA blob and can be round-tripped by setting the bookVBA option on read and write

"Form controls" are stored elsewhere and are currently supported in our Pro builds but not in the open source


chore: migrate from vue-cli to vite for building

This PR resolves #241
with this we are now using vite and have some extra eslint settings to hopefully ease the migration to vue 3 process.

Adding @loneil to the review as well since he has more experience with Vue 3

When it's ready I'll try running locally

I have now resolved the issues with translation failing and this is now ready for review

Don't really know this app so can't give too much of a test, but if I try a manage build I do get
16.83 x Build failed in 15.25s
16.83 error during build:
16.83 [vite:esbuild-transpile] Transform failed with 1 error:
16.83 assets/index-!~{001}~.js:19239:12: ERROR: Top-level await is not available in the configured target environment ("chrome87", "edge88", "es2020", "firefox78", "safari14" + 2 overrides)
16.83
16.83 Top-level await is not available in the configured target environment ("chrome87", "edge88", "es2020", "firefox78", "safari14" + 2 overrides)
16.83 19237|    locale: "en",
16.83 19238|    fallbackLocale: "en",
16.83 19239|    messages: await loadLocaleMessages()
16.83    |              ^
16.83 19240|  });
16.83 19241|
16.83
16.83     at failureErrorWithLog (/app/node_modules/esbuild/lib/main.js:1472:15)
16.83     at /app/node_modules/esbuild/lib/main.js:755:50
16.83     at responseCallbacks.<computed> (/app/node_modules/esbuild/lib/main.js:622:9)
16.83     at handleIncomingPacket (/app/node_modules/esbuild/lib/main.js:677:12)
16.83     at Socket.readFromStdout (/app/node_modules/esbuild/lib/main.js:600:7)
16.83     at Socket.emit (node:events:513:28)
16.83     at addChunk (node:internal/streams/readable:315:12)
16.83     at readableAddChunk (node:internal/streams/readable:289:9)
16.83     at Socket.Readable.push (node:internal/streams/readable:228:10)

again, not sure if I'm doing things right (following readme instructions).
Also a ton of SASS related deprecation warnings get thrown but that's probably something to sort with the bulk code changes with library updates.

If we can resolve the build issue, otherwise everything LGTM

Oh one other thing to consider, since changing the build process is the dockerfile that runs build (at least I assume that's the build we're dealing with) is on ARG build_image=node:gallium which is Node 16.
So could switch to 20 or 22 for the build if we're updating the build to use Vite anyways. (or at least track an issue to update, but then would have to retest)
Also note devcontainer (I didn't try that, not sure if it's in use) has 16 as well.
And looks like it adds vetur, where Volar should be used for Vue3, so can consider that for an update when switching the Vue version.

Agreed with above.

The babel and jest config files in the project still have vue/cli-plugin references, those configs might not be needed using Vite to build?

I have made the requested chances to the docker file, updated the vite config, and removed the unused files. Hopefully that covers everything remaining. I haven't managed to get von running but if @amanji is able to confirm that it starts up and runs as expected this should be ready to merge

A couple of things:

The docker build is failing:

npm run build will successfully complete, however the served bundle (using npx vite preview) shows an error resolving require

Running in development seems to work fine.

@amanji Seems like an issue with the vue2 plugin. I incorporated a workaround until we can move to vue3

Did a light testing, application builds correctly and starts up as expected.

Actually having build issues on a different machine, so checking further

I could have sworn I just fixed that. I'll give it another try. There is an unresolved bug in the vue 2 plugin I've been working around


Fix url_for with i18n when "mount_at_root" is false

This fixes #2594.

@tdreyno Just pushed a minor change to the test code, could you approve running the workflows?


Fix internet explorer HTTP accept

Closes #104

Great decision to remove rack-patch.rb IMHO and exceptionally documenting this problem. Great work as always @jodosha :tophat:

@gotjosh Thank you, Sir :tophat:


Get latest block from zcashd

I propose that we get the latest block from zcashd instead of from the cache.
This fixes an issue where in some rare cases, the value returned from GetLightDInfo doesn't match what GetLatestBlock returns if the cache is slightly behind.
Also, If the cache is behind or if the server is just starting, we should ask zcashd for the latest block height, because when the clients request for a block and we don't have it, we go to zcashd  anyway.

I'd like to understand better the motivation for this change. Is this strictly a performance improvement? Or does this fix incorrect behavior? I would guess this isn't a performance-only improvement, because, as you mentioned, it happens only rarely. If it fixes a behavioral problem, then I don't think it will actually fix anything, because even with this change, the result of GetLightdInfo can differ from the result of GetLatestBlock anyway. It will just be rarer still. But wallets (lightwalletd clients) must be tolerant of these two gRPCs returning different results.
I'm  not aware if this was intentional, but GetLightdInfo always queries zcashd to generate its results, whereas GetLatestBlock does not, it should have been named GetLatestCachedBlock (or more accurately yet, GetLatestCachedHeight since it returns only a height, not a block).
It may be helpful to understand that lightwalletd does something perhaps unexpected: Every few seconds, it forgets the latest block. If it knows about block 10 as the latest block, then it polls (every couple of seconds) for a block at height 11. Usually, the reply is "no such block" (until block 11 is mined). What I was concerned about while coding this is: What happens if a one-block reorg occurs, replacing block 10? Simply polling for block 11 will continue to return "no such block" -- with no indication that a reorg has occurred. Only when a new block 11 is mined (which takes, on average, 75 seconds but can be much longer) will lightwalletd notice (after fetching this version of block 11) that its prev-hash doesn't refer to block 10, so it will begin to back up, looking for the fork point, and then move forward along the new chain.
This delay (in recognizing that a reorg has occurred) seemed to me to be much too long.
The simplest, most bullet-proof way to solve this problem is to completely forget about the tip every few seconds. If block 10 is the tip, lightwalletd suddenly thinks 9 is the tip, and immediately request 10, and, if there's been a reorg, it will get the new version of 10. (If no reorg, it will get the version of 10 that it forgot, no harm done.) One side-effect of this approach is that every few seconds, there's a small window during which GetLatestBlock will return 9 instead of 10 -- because that really is the latest block in the cache.
At first I thought, that's very bad! But then I realized that wallets have to be able to deal with this situation anyway. There could be a real reorg that makes 9 the tip, at least for an instant, while we're fetching the new version of 10 from zcashd.
And here's a situation that's even more subtle: Suppose 10 is the tip, and a reorg happens with 5 as the fork point, and there's a new 6 and a new 7, and that's the new tip. It's true that the better branch will almost always be at least as long as the old (abandoned) branch, but "best chain" isn't based on length, it's based on total work. So it's possible that the new best chain has 7 as its tip. If we simply keep asking for 11, we'll have to wait for 8, 9, 10, and 11 to be mined, before we realize there's been a reorg.
The way lightwalletd works today in this (admittedly unlikely) scenario is that (as I said) it will forget about 10 every few seconds (think 9 is the tip), so it will re-request 10, get "no such block", so immediately request 9, then 8, getting "no such block" to those requests, then 7, and get the new block 7, but notice its prev-hash doesn't refer to the 6 we know about, so it will request 6, and will see that its prev-hash does indeed refer to the 5 we know about, so it will keep that 6, then move ahead in the normal way, requesting 7, and then finally 8 but will get a "no such block" and now we're back to our normal synced state. So, during this time, GetLatestBlock could return a height as low as 6! The wallets must be able to handle this.
@gmale @pacu

By the way, it seems to me that the wallets must implement an approach equivalent to this for the same reason. If the wallet polls for new blocks by requesting the latest height, or requesting the block at what they think is the tip height plus one, then it won't know there's been a reorg until quite some time has passed.
I'm sorry I didn't think of this before now, but it seems like we could improve this by adding a new gRPC that takes as its argument the hash of the block that the wallet considers to be the tip, and the gRPC will return the child of that hash, or "no such block" if it hasn't been mined yet. Both of those are sunny-day cases. But, let's take the previous example of a one-block reorg. If the wallet thinks the tip is height 10, the wallet would make a gRPC call passing its hash, and lightwalletd would notice that has doesn't match the hash of what it considers to be block 10 (or that block doesn't exist at all), so it would return an error that says, in effect, "the hash you sent me doesn't correspond to a block I know about". So then the wallet can immediately request block 9 by sending its hash, and lightwalletd would reply with the new (post-reorg) version of block 10.
So, to summarize, there should be a form of getblock gRPC that takes a block hash, and returns one of three ways:

the block whose prev-hash matches the argument (that is, the child of the block with that hash, we're still syncing)
the error "this is the tip" (or "no such child") -- this would mean the wallet is synced
the error "unknown hash" -- this would mean there's been a reorg, wallet should begin looking backwards for the branch point

This same change could be implemented in zcashd (new RPC) so that lightwalletd could also use this algorithm, which would be more efficient. But it works as is, so it's probably not worth it. It is worth it in the interface between the wallet and lightwalletd, because bandwidth is at a premium.

Thanks for this great explanation @LarryRuane. I think it's very important to have it surfaced somewhere. As you mentioned this is probably the same logic than the one needed for chain reorgs, but probably people don't expect the lightclient server to do this 'forget' logic on its own.

Having worked on #358, I think I now see the motivation for this PR better. As I was testing #358, I noticed that the GetMempoolStream() gRPC returned early (when there wasn't a new block), far more often than I would have expected. This doesn't break anything but definitely is inefficient.
But also, I noticed there's a way to fix this problem without changing the zcashd RPC interface at all. There already exists a getbestblockhash RPC, so what the ingestor loop should do is, instead of requesting the block at the next height every few seconds, it should do something like this (Golang-ish pseudo-code, may not be quite right):
loop {
    hash = zcashd_getbestblockhash()
    latest = blocks[-1]
    if latest.hash == hash {
        // synced
        sleep(2 seconds)
        continue
    }
    // may be a new block
    block, error = zcashd_getblock(latest.height + 1)
    if error == ok {
        // have a later block (we may be syncing)
        if block.prevhash == latest.hash {
            // extend the chain ("push" or append to the list of blocks)
            blocks = append(blocks, block)
            continue
        }
    }
    // this is a reorg, back up
    blocks = blocks[0:-1] // "pop" off the latest block, back up one
}

This way we'll detect a reorg within a few seconds even if a one-block (or any length) reorg changes the tip. It won't be necessary to "forget" the latest block as is currently done, and we won't have this problem of GetLatestBlock backing up one block for a small window every few seconds.
I don't know exactly how the various wallets detect a reorg, but we could implement the same functionality in the gRPC interface -- either add a GetBestBlockHash gRPC, or what I mentioned above, a form of GetBlock gRPC that takes a block hash and returns the next (child) block (or one of two errors, and correction on that, the "unknown hash" should really be "not part of the best chain").

This is very cool. I think detecting 1-block reorgs is very important, and I think Zecwallet has not been doing that properly. I'm 100% in favor of @LarryRuane 's comment above - LightwalletD should detect the 1-block reorg, and clients should too.
Thanks for looking into this and fixing it!

@LarryRuane the pseudocode above looks good to me. The "this is a reorg, back up" part should probably go inside the if error = ok { ... } so that if there's some kind of transient rpc connection error it won't delete all of the blocks.

Closing in favor of #363 (see https://github.com/zcash/lightwalletd/pull/348#issuecomment-882876624 above).


Fixing sprockets wysihtml5 problem

This solution was attempted on pull request #2299 by @gagalago. He mentions it didn't work on production, however I find it does quite well. Could you check it out?

My bad. I should have tested more. Styles don't seem to be applied correctly on production. We need a better fix!

I had a typo, sorry :( I will reissue…


Create a showroom for notebooks

like - https://markroxor.github.io/gensim/showroom/index.html

issues facing -

doc strings will not auto generate html.

For docstrings we are now redirecting to the auto generated docs by pip - https://www.pydoc.io/pypi/fromscratchtoml-0.0.1/


Added Xcode plugin for localization in Plugin section

Project URL

Description

Checklist

[x] Only one project is in this pull request
[x] Addition in chronological order (bottom of category)
[ ] Travis CI pass
[x] Supports iOS 7 or later
[ ] Has a commit from less than 2 years ago
[ ] Has a clear README in English

Hey @aashishtamsya, thanks for the contribution! 😄
The only problem is that you have to skip a line between Dash and our Themes section because this happened:

Also for next time, please send just one library per pull request.

Sry for that mistake, I will make sure that doesn't happen next time 😄
Kind Regards,
Aashish Tamsya
On Wed, Jul 20, 2016 at 7:10 PM, Lucas Farah<EMAIL_ADDRESS>wrote:

Hey @aashishtamsya https://github.com/aashishtamsya, thanks for the
contribution! 😄
The only problem is that you have to skip a line between Dash and our
Themes section because this happened:
[image: screen shot 2016-07-20 at 10 36 54 am]
https://cloud.githubusercontent.com/assets/6511079/16988265/33eda812-4e66-11e6-8f2b-e90ea1dedd03.png
Also for next time, please send just one library per pull request.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/vsouza/awesome-ios/pull/962#issuecomment-233951735,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKOPKaWweaftV_29BA12JB4q0DmLLVHmks5qXiVYgaJpZM4JQuJJ
.

Hey @aashishtamsya, I still need you to rebase and add a line before Theme

Sure I will do that. 😊👍

Sorry but there are still conflicts and you need to do a rebase


Wrong algorithm used at C-Plus-Plus/stack/maximum_size_of_balanced_bracket_sequence.cpp

🐛 Bug Report
(A clear and concise description of what the bug is.)
Have you read the Contributing Guidelines on Pull Requests?
This code doesnot handle the domain of question. It fails in many testcases.

/assign

Hey, @Rishabh7896
Could you please specify the test cases on which the algorithm fails?

Input: )()()(((()
Expected Output: 4
Output: 6
If we will assume the answer to be the sum of the length of all valid sequences then it is correct, otherwise, it is wrong

Thank you for the test case.
But I think in this particular question, it is asked to print the maximum length of valid bracket sequence. So, we have to sum the number of brackets that make it valid.
So, the solution according to me is correct.


JAMES-4034 Fix receival of external badly formated From message

Dropping some production messages because of this.
Be strict about what we send but relaxed about what we receive.
Would fix this regression:

Test failing on the CI?
https://ci-builds.apache.org/job/james/job/ApacheJames/job/PR-2400/1/testReport/junit/org.apache.james.smtp/SmtpIdentityVerificationTest/errorsShouldBeIgnoredWhenUnAuthed_File_/

cc @Arsnael can you rerun the CI?

Done


arch/arm/stm32h7: add workaround for Renode

Summary
arch/arm/stm32h7: add workaround for Renode
Add an option to disable busy wait PWR_CSR1_ACTVOSRDY during boot which doesn't work with Renode simulation
Impact
workaround to run nucleo-h743zi/nsh on Renode
Testing
nucleo-h743zi/nsh on Renode

[Experimental Bot, please feedback here]
This PR does not meet the NuttX requirements in its current state. Here's why and how to improve it:
Missing Information

Summary:

What functional part is changed?  Be specific. Is it a driver, core kernel code, build system change, etc.?
How does it work? Briefly explain the technical implementation of the workaround.

Impact:

Is a new feature added? It sounds like a bug fix, so be clear about that.
Impact on Build:  Does this introduce a new build option? If so, describe it.
Impact on Hardware: This seems specific to STM32H7. Be explicit.
Impact on Documentation:  Does this workaround need to be documented somewhere for others to understand?

Testing:

Build Host(s):  List the specific OS and versions you used to build the code.
Target(s):  Be specific – which Renode version and any relevant configuration details.
Testing logs: The logs are missing entirely. Provide "before" and "after" logs showing the issue and the fix.

How to Improve the PR

Expand the Summary: Provide the missing technical details about what's changing and how.
Complete the Impact Section: Address all the points, even if the answer is "NO" with a brief explanation.
Provide Detailed Testing Information: Include build host specifics, target environment details, and the actual log output demonstrating the problem and the solution.

Concise Example (Adapt to your specific changes)
Summary
This PR addresses an issue where the STM32H7 boot process hangs in Renode due to an incorrect busy wait on the PWR_CSR1_ACTVOSRDY flag. It introduces a new build option to disable this wait specifically for Renode simulations.
Impact

Bug fix: Addresses a boot issue in Renode.
Impact on user:  Users running STM32H7 simulations in Renode will now have a working boot process.
Impact on build: A new build option (e.g., CONFIG_STM32H7_RENODE_WORKAROUND) is added to enable the workaround.
Impact on hardware:  This specifically affects STM32H7 boards.
Impact on documentation: A brief note should be added to the STM32H7 documentation about this workaround for Renode users.
Other impacts:  None.

Testing

Build Host: Ubuntu 20.04, GCC 10.2.1
Target: Renode version 1.13.0, nucleo-h743zi platform, using the nsh configuration.

Testing logs before change:
[Relevant log output showing the hang]

Testing logs after change:
[Relevant log output showing successful boot]


Studio: Improving graph rendering to split vertices and edges

Collect only the edges that are relevant to the vertices in the resultset.
Example:
{
	"graph": {
		"vertices": [{
			"@rid": "#17:62",
			"@class": "Whisky",
			"name": "Springbank"
		}, {
			"@rid": "#17:67",
			"@class": "Whisky",
			"name": "Tobermory"
		}, {
			"@rid": "#15:3",
			"@class": "FlavourGroup",
			"dryness": "Medium",
			"name": "D",
			"description": "Low or No Peat, with Fruity, Floral, Malty Notes and Nutty Hints.",
			"body": "Light"
		}, {
			"@rid": "#15:5",
			"@class": "FlavourGroup",
			"dryness": "Medium",
			"name": "F",
			"description": "Medium-Bodied, Medium-Sweet, Low Peat, Malty Notes and Sherry, Honey, Spicy Hints.",
			"body": "Medium"
		}, {
			"@rid": "#12:1",
			"@class": "Location",
			"name": "Alexandria"
		}, {
			"@rid": "#17:2",
			"@class": "Whisky",
			"name": "Arran"
		}, {
			"@rid": "#12:6",
			"@class": "Location",
			"name": "Blackford"
		}, {
			"@rid": "#17:7",
			"@class": "Whisky",
			"name": "BenRiach"
		}, {
			"@rid": "#12:11",
			"@class": "Location",
			"name": "Dalmuir"
		}, {
			"@rid": "#17:12",
			"@class": "Whisky",
			"name": "Bruichladdich"
		}, {
			"@rid": "#12:16",
			"@class": "Location",
			"name": "Elgin"
		}, {
			"@rid": "#17:17",
			"@class": "Whisky",
			"name": "Cragganmore"
		}, {
			"@rid": "#12:21",
			"@class": "Location",
			"name": "Isle of Islay"
		}, {
			"@rid": "#14:3",
			"@class": "Flavour",
			"name": "Malt"
		}, {
			"@rid": "#17:22",
			"@class": "Whisky",
			"name": "Deanston"
		}, {
			"@rid": "#12:26",
			"@class": "Location",
			"name": "Kirkwall"
		}, {
			"@rid": "#14:8",
			"@class": "Flavour",
			"name": "Peat"
		}, {
			"@rid": "#17:27",
			"@class": "Whisky",
			"name": "Glen Grant"
		}, {
			"@rid": "#12:31",
			"@class": "Location",
			"name": "Muir of Ord"
		}, {
			"@rid": "#17:32",
			"@class": "Whisky",
			"name": "Glendronach"
		}, {
			"@rid": "#12:36",
			"@class": "Location",
			"name": "Oldmeldrum"
		}, {
			"@rid": "#11:4",
			"@class": "Region",
			"name": "Lowlands"
		}, {
			"@rid": "#17:37",
			"@class": "Whisky",
			"name": "Glenkinchie"
		}, {
			"@rid": "#12:41",
			"@class": "Location",
			"name": "Rothes"
		}, {
			"@rid": "#17:42",
			"@class": "Whisky",
			"name": "Glenturret"
		}, {
			"@rid": "#17:47",
			"@class": "Whisky",
			"name": "Knockando"
		}, {
			"@rid": "#17:52",
			"@class": "Whisky",
			"name": "Macallan"
		}, {
			"@rid": "#17:57",
			"@class": "Whisky",
			"name": "Old Pulteney"
		}],
		"edges": [{
			"@rid": "#13:11",
			"@class": "InRegion",
			"from": "#11:4",
			"to": "#12:11"
		}, {
			"@rid": "#16:30",
			"@class": "FlavourInGroup",
			"from": "#14:2",
			"to": "#15:5"
		}, {
			"@rid": "#13:16",
			"@class": "InRegion",
			"from": "#11:5",
			"to": "#12:16"
		}, {
			"@rid": "#16:35",
			"@class": "FlavourInGroup",
			"from": "#14:2",
			"to": "#15:7"
		}, {
			"@rid": "#16:25",
			"@class": "FlavourInGroup",
			"from": "#14:7",
			"to": "#15:4"
		}]
	}
}

@lvca
i'm implementing this on Studio. I have one question. What if i have a property on the edge called from or to?

Good question. Do you prefer I rename them as @from and @to so they are metadata? Makes a lot of sense to me.

Hi,
As today is not possible have a property on the edge called from or to that is not the one that have that meaning, not sure is a good idea add a new keyword for this specific case.

My idea was to separate attributes by metadata. Since from and to are not edge's attributes, but they are semantically metadata, it's logical for me using @.

I suggest to keep in/out instead of renaming them.

@luigidellaquila WDYT ?

That's absolutely reasonable for me.
(just let me know, I'll update GoG ;-) )
Thanks
Luigi

Hi,
Sorry i may missed my point a bit, and it was that we should not change the in/out to @from/@to here in this context, as well this issue seems target 2.2.x ... that it's an hotfix, and this seems not a fix.
In any case i'm not against to rename in/out to @from/@to, but it shoudl only in the context of 3.0 and probably evaluating similar naming for out_relation and in_relation field of vertex to similar conventions, with the relative changes in all the database internal api.
If we do this change it should be coherent everywhere, would be a nightmare maintain two different names in two different contexts.

this command has been released few days before 2.2 and it's completely new and not even documented, so it's not a problem changing it now.

Restored in/out
https://github.com/orientechnologies/orientdb/commit/4dd6e62582a229a0d985c496e410395fa1d17cd3


Add activity-stream to API

Hi. I see that backend at Crowdin has its own endpoint for getting the project's last activity: /backend/project_actions/activity_stream.
But I cannot find where this method is in the client API. So can you add this endpoint to the client, please?

Hi @easysugar!
The Crowdin API Client Python - is an interface to the public APIs - crowdin.com, Crowdin Enterprise. It's not supposed to support these backend endpoints.

@andrii-bodnar
OK. But are you planning to add the same endpoint for the last activity to the public API?

@easysugar currently, we are not planning such an endpoint in the nearest future, but I need to discuss it with the Team.
Could you please describe your use case in more detail? It will help us a lot with designing this new Activity API. Or we can find a workaround for this case.

Sure. I want to calculate something like "top contributors" for last week using the last activity.
Currently, I have to use different endpoints (for translations, approvals, comments), get all historical data, and then filter by date.

@easysugar please check the Reports section.
The Top Members or Contribution Raw Data report should help to collect data regarding users' contributions.

Actually, I would like to make a report by myself. But I will try Reports.

The Contribution Raw Data report contains just the raw data regarding contributions so you will be able to calculate the report you want based on this data.


(New Sheet) Cruelty Squad TTRPG by SPRUG Workshop

Cruelty Squad sheet by Notepad Anon (aka SPRUG Workshop)

Submission Checklist
Required

[X] The pull request title clearly contains the name of the sheet I am editing.
[X] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[X] The pull request makes changes to files in only one sub-folder.
[X] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is:  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: SPRUG Workshop (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: Center System (i.e. Dungeons & Dragons, FATE)

[ ] I have followed the Character Sheets Standards when building this sheet.

[X] This sheet has been made (on behalf of), or by, the game's publisher.
[ ] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: <   >
[ ] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description
Character sheet for the Cruelty Squad TTRPG - a system made using the Center System by SPRUG Workshop.

Character Sheet Info Roll20 Internal Use only.


Remove duplicate of react-native-pdf-view

Removing duplicate entry of react-native-pdf-view
Appears on line 291 and 1181 of the react-native-libraries.json file at the time of this commit.
I removed the latest entry.

:+1: LGTM, I don't know what I would do without you :)


Extending HTTP retries to all methods

By default urllib3 only retries certain HTTP methods: https://urllib3.readthedocs.io/en/latest/reference/urllib3.util.html#urllib3.util.retry.Retry.DEFAULT_METHOD_WHITELIST
Lot of our APIs use the POST method and some even use PATCH. Therefore I'm enabling retry support for all HTTP methods.
Related to #248

Related documentation from GCP (adding here for more context): https://cloud.google.com/apis/design/errors#error_retries


Remove unnecessary try / catch expect.fail() pattern

The pattern
    try {
      await jobs;
    } catch (e) {
      expect.fail();
    }

provides no extra functionality than just
      await jobs;

expect that it's muting the error so it's less useful to debug

file conflict


Setup Wizard ended prematurely : setupapi file marks error 0xe0000223

I have an error, when I try to install Vigem, because before I had it on another pc and if it worked, this one gives me an error

Why do people insist on not reading logs that explain the issue, ignore the issue templates, and then expect help....

Nice, sure, add screenshots of text so it's extra hard to read or copy. Sometimes I really worry about the world...
Read 👏 And 👏 Follow 👏 The 👏 Templates 👏 And 👏 Get 👏 Out 👏 Of 👏 The 👏 Issue 👏 Tracker 👏


Add Email Notification Schedule

📑 I have found these related issues/pull requests
None
🏷 Feature Request Type
Other
🔖 Feature description
Would love to see an Email Notification Schedule.  I don't see a way to put one in. So it only would email to this address between hours or on some Schedule
✔ Solution
Would love to see an Email Notification Schedule.  I don't see a way to put one in. So it only would email to this address between hours or on some Schedule
❓ Alternatives
No response
📝 Additional Context
No response

So you mean you want to put a monitor into a sheduled maintanance mode to disabling sending mails to said notification provider?

I would want that monitor to be still working. I guess that can work by setting that up.  The idea was a way that one email used from like hours 7 am to 7pm. And then a different email used from like 7pm to 7am

You likely want to use grafana oncall as a notifcation provider to shedule your oncall shifts then.
I am going to close this as this is covered by https://github.com/louislam/uptime-kuma/issues/3375


fix: #1374 add a watch cache reduce the number of queries needed to watch or device changes in large orgs.

@russellb could use your help figuring out if there are any data race gremlins in this stuff.

@chirino In case of multiple replica's of apiserver deployed, I assume this approach won't cause any data inconsistency? For example, if the request  to update the database row goes to one replica and request to read that same row goes to another replica?

AFAIK @vishnoianil it should not cause any data inconsistency.

@russellb could use your help figuring out if there are any data race gremlins in this stuff.

just a general review, or are you observing any problems that make you think something is wrong? I'm assuming just a general review since it's tricky, but let me know if there's a problem to look out for.
happy to review it

just a general review.

@russellb do you think this needs a design doc?

@russellb do you think this needs a design doc?

You could add a section to the existing watch-api doc with an overview

TODO: I think I need to add a unit test to simulate multiple apiserver replicas using a single redis server.


Adding tests for failing to call complete, produce fewer,more items incase of splitting.

This is great! Thanks @gaurikholkar.

:)


Decoding gwt request with SyncProxy

Hi Everyone,
I am trying to decode GWT request by using SyncProxy,
I saw there is a way to decode GWT response but I couldn't find way to decoding request.
am I missing something?
Thank you,
Dina

Typically, this is done by the service interface created in the SyncProxy class, but if you're looking for some of the indepth details, the entire SyncProxy system uses code directly from GWT to do the decoding back into an object. See the #doInvoke method in the RemoteServicesSyncProxy class for some details: RemoteServiceSyncProxy. Best practice is the read through the Wiki QuickStart.
If i'm missing what, youi're asking, please advise. Thanks


chore: replace more occurrences of "auth token" with "API key"

looks like this branch has some conflicts @cprice404


Takes lot of CPU time when press and hold j/k if the file is large

This is a very good plugin. But if I try to navigate by pressing j/k in a large file, CPU utilization seems on a higher side and the cursor jumps to the right side of command line more often than a normal use case.
It will be nice to reduce CPU utilization and make navigation smoother.

Sorry, I don't maintain this plugin any more.

Thanks for the comment.
Do you know if any other vim plugin which achieves this functionality?

https://github.com/vim-scripts/ShowPairs  ?

@Yggdroot This matches my requirement partially. Thanks for the suggestion.

Closing this issue as I was able to address this issue by removing CursorMoved autocmd.


Brightness should be Illuminance

This may seem minor and pedantic but… when the Tempest entities were renamed to Weatherflow entities for unknown reasons “illuminance” was renamed to “brightness”.
Illuminance is the technical term for light falling on a surface, which is what is being measured by the sensor, in units of lux.
  Luminance is the technical term, with units of lumens.
So brightness is the wrong name.  Illuminance was correct.

To be honest this does not annoy me as much as another zigbee "illuminance" sensor I have that actually just returns an uncalibrated brightness (as a percentage).  But the Tempest at least makes an attempt at calibration, so...

This integration is no longer been maintained as the domain name conflicts with a new Core Integration that uses UDP to get pure local data - but is then missing a lot of the sensors you can get from the REST API. I have made a new and more up-to-date integration that replaces this one. The new integration names the sensor illuminance.
Get it from here


Speedtest not working

I installed everything with Mac-CLI, but every time I use mac speedtest it asks me if I want to install the Speed Test Utility, I put yes and it installs fast-cli and thats it...

Hi @manuel0097,
Could you please run the following command?
npm install --global fast-cli
Please let me know if the installation was successful.

Hi @guarinogabriel,
The installation was successful but the problem persists.

@mcartagenah just took out a PR for this: https://github.com/guarinogabriel/Mac-CLI/pull/151

Bump. Hasn't been working for me since December.

Hi there,
I am closing this issue since the speed test command has been updated with the following native command from MacOS:
networkQuality -v


Hman 22

Merge branch into Master
JIRA link (if applicable)
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

changes are in hman-28 #36


Calling a Db2 for z/OS Stored procedure with output parameters - can't get parameters back

Description
I am using Dbeaver 24.0.2 with Db2 for z/OS. Trying to call a stored procedure that has one input parm and two output parms.
Call StoredProcName(:In_Schema, :Out_Cnt, :Out_List);   Product says that procedure executed fine with rc=0 , however I can't get back those two output parms. It doesn't show them, period.
DBeaver Version
Community Edition 24.0.2
Operating System
Windows 10
Database and driver
Db2 for z/OS, Db2 Connect driver <IP_ADDRESS>
Steps to reproduce
Just trying to execute stored procedure mentioned above and see returned values. Those output parms are not showing anywhere.
Additional context
No response

The right of calling this  stored procedure would be CALL SP_NAME(:In_Schema, ? , ?)  and have procedure return two output parms.  However, doing it this way returns error SQL Code= -440, SQL State=42884 - No authorized procedure named SP_NAME having compatible argument was found

Thanks for your report.

Do you see the following dialogue?

Yes, I do see this dialogue.

@PavelDG What are those output parameters? It may be working as expected because DBeaver doesn't show individual results if they are not a resultset. The procedure was executed succesfully, but if you want to see the output that is for example a simpe int or float you need to use it inside a query or another procedure that would eventualy return a resultset.

One of them is Integer count and another one is CLOB -large string.  But it doesn't matter what type, Dbeaver doesn't show any output parms for Stored Procedure call. How can I see it inside a query?  For ex., I have two variables :a and :b with output data.
How can I see those? When you saying working as designed, it means that design is not right if you can't see results of calling SP that returns data as parms.

I have been running into this same issue.  Has this been accepted as an issue and any plan to allow for output parameters?

We accepted this issue as a bug.
We don't give any estimations for plans about this issue. Also, we don't have Db2 for z/OS, so I'm not sure it will be fixed soon.

if it helps, the code (in java) to set up and retrieve output parms looks like this:


Pick correct route id from multiple results

I had issues with some shorter route numbers like "23" (route id 1023) which got mixed with "239" (route id 2239) due to their order in results.

Thanks! I thought this might happen, but forgot about it as everything worked for me 😄
Ultimately I'd prefer a completely non-ambiguous way to define the buses, but this should at least make things better so I'll merge. On a separate note, it would be nice to have some tests for cases like this, but that would also make my dumb hobby project feel slightly more serious and I don't think I want that.

No problem. I spent some time to think about better fix, non-ambiguous, but then decided that this is already an improvement :smile:
Thanks for this bot! I am already using it to track speeding on street next to my apartment. Ultimately I'd like to convince the municipal authorities to add a speed bump there.


Add type field to pill items.

Reference: https://github.com/zulip/zulip/pull/17994#issuecomment-822886392 Point-1.
Testing plan:
node tests
GIFs or screenshots: There should be no UI changes due to this.

I think this field cannot be utilized in pill_typeahead.js because items in those function are actual stream/user_group/user objects. May be expanding pills into users is the only place where this could be utilized.
For avoiding weird checks in pill_typeahead I think it will require work that is not related to type field added here. I am opening a thread for discussing what sort of refactoring is needed their, I'll add those in separate commit/pr if they appears reasonable to you after discussion.

OK; I went ahead and merged this and we can just do that as a new PR; having this is useful for readability already, even if we're not using it yet.
@ryanreh99 FYI.


work completed on verifyLink

note: this has been some of the trickiest code I've written in a very long time. lots of moving parts.
work on proofSet accumulations
it hasn't been tested, it just compiles...

The commits 300d803c25a5...aac18e569482 introduce visual changes on linux. :mag_right: 1 changed

Changed: Markdown-emoji (before) (after)

The commits 300d803c25a5...464e40ea675d introduce visual changes on linux. :mag_right: 1 changed

Changed: Tracker-New_user_Scroll_1 (before) (after)

thanks for the review miles.

The commits 300d803c25a5...10a586f39698 introduce visual changes on linux. :mag_right: 2 changed

Changed: Tracker-New_user_Scroll_1 (before) (after)

Changed: Markdown-emoji (before) (after)

The commits ccf3f71f9aad...b60014bb53a6 introduce visual changes on linux. :mag_right: 1 changed

Changed: Markdown-emoji (before) (after)

The commits ccf3f71f9aad...fea8528162a0 introduce visual changes on linux. :mag_right: 1 changed

Changed: Tracker-New_user_Scroll_1 (before) (after)


The compilation in "release" mode fails (with a solution)

The compilation in "release" mode fails:

Git commit id: 319e6eb3c1d51d5a0e7f97133a9ea87e0f4404ed
Error report: At the end.

To reproduce the problem:
script/cmake-build
-DCMAKE_BUILD_TYPE=RELEASE
...
A solution:
A simple solution is to remove the intermediate variable (splitError) used to store the result, as done in the following function "TranslateDomain".
The patch:
index 6aeccb2823..35df8e4a0e 100644
@@ -259,14 +259,12 @@ void DiscoveryProxy::OnHostDiscovered(const std::string &
         std::string      hostName, domain;
         char             queryName[OT_DNS_MAX_NAME_SIZE];
         otDnssdQueryType type = otDnssdGetQueryTypeAndName(query, &queryName);
-        otbrError        splitError;

         if (type != OT_DNSSD_QUERY_TYPE_RESOLVE_HOST)
         {
             continue;
         }
-        splitError = SplitFullHostName(queryName, hostName, domain);
-        assert(splitError == OTBR_ERROR_NONE);
+        assert(SplitFullHostName(queryName, hostName, domain) == OTBR_ERROR_NONE);

         if (DnsLabelsEqual(hostName, aHostName))
         {

The error reported by the tool chain :
[12/54] Building CXX object src/sdp_proxy/CMakeFiles/otbr-sdp-proxy.dir/discovery_proxy.cpp.o
FAILED: src/sdp_proxy/CMakeFiles/otbr-sdp-proxy.dir/discovery_proxy.cpp.o
/usr/bin/c++ -DHAVE_LIBSYSTEMD=1 -DOTBR_ENABLE_BORDER_AGENT=1 -DOTBR_ENABLE_DBUS_SERVER=1 -DOTBR_ENABLE_DNSSD_DISCOVERY_PROXY=1 -DOTBR_ENABLE_MDNS_MDNSSD=1 -DOTBR_ENABLE_NOTIFY_UPSTART=1 -DOTBR_ENABLE_SRP_ADVERTISING_PROXY=1 -DOTBR_MESHCOP_SERVICE_INSTANCE_NAME=""OpenThread BorderRouter"" -DOTBR_PACKAGE_NAME="OpenThread_BorderRouter" -DOTBR_PACKAGE_VERSION="0.3.0-319e6eb3c1" -DOTBR_PRODUCT_NAME="BorderRouter" -DOTBR_SYSLOG_FACILITY_ID=LOG_USER -DOTBR_VENDOR_NAME="OpenThread" -I/home/sah0588/Downloads/matter/ot-br-posix/include -I/home/sah0588/Downloads/matter/ot-br-posix/src -I/home/sah0588/Downloads/matter/ot-br-posix/build/otbr/third_party/openthread/repo/etc/cmake -I/home/sah0588/Downloads/matter/ot-br-posix/third_party/openthread/repo/etc/cmake -I/home/sah0588/Downloads/matter/ot-br-posix/third_party/openthread/repo/include -I/home/sah0588/Downloads/matter/ot-br-posix/third_party/openthread/repo/src/posix/platform/include -I/home/sah0588/Downloads/matter/ot-br-posix/third_party/openthread/repo/src -O3 -DNDEBUG -Wall -Wextra -Werror -Wfatal-errors -Wuninitialized -Wno-missing-braces -std=c++11 -MD -MT src/sdp_proxy/CMakeFiles/otbr-sdp-proxy.dir/discovery_proxy.cpp.o -MF src/sdp_proxy/CMakeFiles/otbr-sdp-proxy.dir/discovery_proxy.cpp.o.d -o src/sdp_proxy/CMakeFiles/otbr-sdp-proxy.dir/discovery_proxy.cpp.o -c /home/sah0588/Downloads/matter/ot-br-posix/src/sdp_proxy/discovery_proxy.cpp
/home/sah0588/Downloads/matter/ot-br-posix/src/sdp_proxy/discovery_proxy.cpp: In member function ‘void otbr::Dnssd::DiscoveryProxy::OnHostDiscovered(const string&, const otbr::Mdns::Publisher::DiscoveredHostInfo&)’:
/home/sah0588/Downloads/matter/ot-br-posix/src/sdp_proxy/discovery_proxy.cpp:262:26: error: variable ‘splitError’ set but not used [-Werror=unused-but-set-variable]
262 |         otbrError        splitError;
|                          ^~~~~~~~~~
compilation terminated due to -Wfatal-errors.
cc1plus: all warnings being treated as errors

@achsoftathome , thanks for raising this issue.
I submitted #1482 with a proposed fix. Note that we do not want to move SplitFullHostName() into an assert() statement, otherwise that method will not be called in release mode.

Thanks,

From: Jonathan Hui @.>
Sent: Thursday, July 28, 2022 9:58 PM
To: openthread/ot-br-posix @.>
Cc: Arnaud CHAINARD @.>; Mention @.>
Subject: Re: [openthread/ot-br-posix] The compilation in "release" mode fails (with a solution) (Issue #1477)
@achsoftathomehttps://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fachsoftathome&data=05|01|arnaud.chainard%40softathome.com|915c4046d24541ae9d8208da70d3980f|aa10e044e4054c10835336b4d0cce511|0|0|637946351338969443|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=U%2B8jz3NykKvBbrFaUffxcuN0h15X4cHDexCLU%2BOZW48%3D&reserved=0 , thanks for raising this issue.
I submitted #1482https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fopenthread%2Fot-br-posix%2Fpull%2F1482&data=05|01|arnaud.chainard%40softathome.com|915c4046d24541ae9d8208da70d3980f|aa10e044e4054c10835336b4d0cce511|0|0|637946351338969443|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=6sWRtYP3Gw7ewVoheWfqvIGk%2BASyZJNKWMC0b4F%2FruQ%3D&reserved=0 with a proposed fix. Note that we do not want to move SplitFullHostName() into an assert() statement, otherwise that method will not be called in release mode.
—
Reply to this email directly, view it on GitHubhttps://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fopenthread%2Fot-br-posix%2Fissues%2F1477%23issuecomment-1198571109&data=05|01|arnaud.chainard%40softathome.com|915c4046d24541ae9d8208da70d3980f|aa10e044e4054c10835336b4d0cce511|0|0|637946351338969443|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=bAOw4ZsCTw8AdDq7Y38kg294Vez4WkF1NBkcjaQgnKo%3D&reserved=0, or unsubscribehttps://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAZW7IC6X7O6ZAXWOUCVSTIDVWLQ7VANCNFSM54R3KCMQ&data=05|01|arnaud.chainard%40softathome.com|915c4046d24541ae9d8208da70d3980f|aa10e044e4054c10835336b4d0cce511|0|0|637946351338969443|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=aj2ActwLmUaBsas9Ldyfn3bo4NHVN3XIWM6mrMPTQDQ%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>
-- This message and any attachments herein are confidential, intended solely for the addressees and are SoftAtHome’s ownership. Any unauthorized use or dissemination is prohibited. If you are not the intended addressee of this message, please cancel it immediately and inform the sender.


Multiple cursors doesnt work correct with Vim mode plugin

Steps to Reproduce:

Wtite similar code:

function ffff() {
}
$users = ffff();
$user2 = ffff();

$user3 = ffff();

While in VIM mode using VIM plugin place the cursor somewhere in the first 'ffff' word

Exit vim mode with 'a' or 'i' key.

Click 'ctrl-d' a couple of times

Expected result:
4 cursors should be created.
Actual result:
Only 2 multiple cursors are created for the first 2 occurences of the word 'ffff'
Useful information:
I'm not sure if this is a bug with VSCode or VIM plugin but the solution that works is this:

When I enter insert mode and i add some character (space or other) then e delete it - after  that when i select ctrl-d the cursors works great as expected.

Basically the cursors start working good when I edit some text anywhere in the editor and then click 'ctrl-d'.
If I go to NORMAL mode and immediately try to set multiple cursors it doesnt work correct.

I see there is no activity. (and maybe there will never be).
So I'm closing the issue.


[Style] Styling Try Now button

What's the style idea?
When we hover on Try now button it tilts through certain angle, instead of that it will look better if color and background color changes on hovering
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[ ] I am a IWOC'24 contributor.
[X] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

[X] I agree to follow this project's "Code of Conduct".

Pls complete the assigned issues for every projects first @pranjal12-web

Assign me under iwoc

@AftabMankapure What enhancement will you do?

Hi @Rakesh9100
I want style it like a glassmorphism with hover effect
Please assign it to me under JWOC 2024

@pranjal12-web Do you want to work

yes sir

Go ahead @pranjal12-web


docs: Restrict user email addresses to certain domains

Added a doc to restrict user email addresses to certain domains.

@derAnfaenger Oops! You were right but I've now fixed the problem. Here is a screenshot of the working page:

@anirudhjain75 Fixed 👍

Hi @Jeffthebest1!
Thanks for working on this!
Added a few comments, could you address those?

I think the title of this topic is kind of overly technical, and the first paragraph also reflects that.  We allow administrators to restrict users to certain domains, but I think it's more fluent to say something like "We allow administrators to block new users from signing up who are not in the organization.  The administrator can accomplish this by restricting users to certains domains.  (Ordinary user don't have this power.)"
This is a little verbose, and my wording is just a suggestion, but I feel like the current wording is too abrupt and sort of assumes the user knows the context.
I'm ok with leaving the title as it is.

@showell I left the title because I couldn't come up with anything better but I improved the first few sentences.

@showell @trueskawka Fixed! 👍


Update ADOPTERS.md

Update ADOPTERS.md, add Pier insurance from Brazil. @brunopadz just let me know that it is ok to add :)

/merge

/merge


web: two-stage build Dockerfile

Reduces resulting image size from 1.39GB to 143MB.

Wow, that's a much bigger difference than I would have expected. I'll take a look at this sometime soon but I need to bring down the demo server to fully test it so I'll want to wait until my post falls off the front page of HN :)

Cheers, and I should add that I didn't fully test this myself yet - just did a quick diff at the resulting images.
BTW, what do you think of the prospect of changing base_url from file to either build-args or env-vars (could use envusbst)? That would also make it smoother to similarly parameterize the upstreams and resolver args (making this image useful outside of the compose setup)

I'm totally open to either of those changes, but I think I want to keep the Makefile logic to load the base url from a file. I don't have a good reason but I like this way of doing things over environment variables from the user's perspective. It fits more with the philosophy of dead-simple builds. Anything downstream of the Makefile could be changed though as long as it preserves existing functionality.

It's your call of course but on flip side:
With the current approach any change (port, upstream change, etc) will require a full image rebuild. Whereas making it to env-vars means that configuration can all be changed at run-time. Depending on the environment this runs in, that can become more of a hassle. We could still keep the currently hardcoded ones as defaults, of course.
Also consider if prebuilt images at some point will be shared through e.g. Docker Hub or quay.

That's true, I just hate environment variables. This will be necessary if the project grows to the point that it's feasible to use for large areas, but there will be a number of other architectural problems that will crop up. I deliberately did some things that don't scale just because they're easy for the time being.
My demo server is still getting hammered so in all likelihood I won't be able to test until tomorrow but I will get to this because saving a gigabyte in the web image is a big deal. :)

Just in case you're not aware, you can still set those through a single .env files and include that from the docker-compose yaml
Slightly OT to this PR but I'm happy to look at things like this to making things more scalable/reusable/easy for others to use and make some more PRs (for example I noted that the photon image currently includes and transforms the data in the image build step - it could be split up in two images where one transforms the dataset at runtime, and the output of that can then be mounted as a volume in the second one). I think it could lower the bars for others to run and contribute (and could improve quality of life for yourself as well if you're open for adapting).
But maybe hint with a reaction to this comment on if this is :+1: or :-1: :)

I would absolutely love contributions to help with docker config stuff! I think the concept for this project is sound in that this is a thing that the world deserves, but the implementation was literally thrown together in a week so I'm not married to anything except the idea that it should be easy for new users to bring up their own instances.

Could you remove the trailing * from the COPY statement? it appears to have strange behavior and removing it but keeping the trailing slash solves things. Otherwise LGTM.

ohdd, perhaps some difference between docker versions..
either way, fixed now.

Thank you for the contribution!!!


Problem writing IBM 720kB disks

Hello David,
I can write DD floppy's for the MAC and they are readable on a mac classic. I can write a DD disk in HP-LIF format and my logic analyzer reads them. But when i want to write a DD IBM 720kB disk no machine can read this because they can't find a sector. So the disk won't even show up as a empty disk.
The command i use:
$ ./fluxengine write ibm --ibm-preset-720 -i empty-formatted-disk.img
reading 80 tracks, 2 heads, 9 sectors, 512 bytes per sector, 720 kB total
Writing to: :d=0:s=0-1:t=0-79
0.0: Using FluxEngine with serial number 6000020A180D0593
199 ms in 61866 bytes
0.1: 199 ms in 61876 bytes
1.0: 199 ms in 61875 bytes
1.1: 199 ms in 61883 bytes
2.0: 199 ms in 61873 bytes
2.1: 199 ms in 61885 bytes
Then if i read the disk back; i get:
$ ./fluxengine read ibm --write-csv test.csv
Reading from: :d=0:s=0-1:t=0-79
Using FluxEngine with serial number 6000020A180D0593
Measuring rotational speed... 200ms
0.0: 249.093 ms in 77184 bytes
0 records, 0 sectors;
0 bytes decoded.
0.1: 249.107 ms in 77248 bytes
0 records, 0 sectors;
0 bytes decoded.
1.0: 249.936 ms in 77504 bytes
0 records, 0 sectors;
0 bytes decoded.
... etc
... etc
79.1: 249.484 ms in 77376 bytes
0 records, 0 sectors;
0 bytes decoded.
Autodetecting output geometry
H.SS Tracks --->
No sectors in output; skipping analysis
writing 0 tracks, 0 heads, 0 sectors, 0 bytes per sector, 0 kB total
Do you have any idea what could go wrong here?
I tested the same with 1.44Mb disks and used --ibm-preset-1440 and that works flawless. no problems reading and writing back.
thanks in advance,
Wybren

I found the little bug. With the 720 preset the default IBM settings were not loaded.. Submitting a fix in my latest pull request. #242


Corrected a spelling mistake

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thank you @shahzaib919 for your contribution and congratulations on your first PR merge to this repo! 🎉


Remove deprecated  suffixes for isize

This PR fixes some warnings that pop up due to us suffixes being deprecated:
src/features.rs:27:24: 27:27 warning: the `u` and `us` suffixes on integers are deprecated; use `usize` or one of the fixed-sized suffixes
src/features.rs:27         let mut curr = 0us;
                                          ^~~
src/features.rs:27:24: 27:27 help: add #![feature(int_uint)] to the crate attributes to silence this warning
src/features.rs:27         let mut curr = 0us;

Please note: the CI build will fail due to this PR not including #77

Thanks. Merged 6637e4dc70e46feedc6e31366a0441a345c8721d


Make crypto provider configurable, rename feature and make hyper-tls feature visible

instead of setting default provider when none set in authenticator.rs, should use [with_provider_and_native_roots](https://docs.rs/hyper-rustls/latest/hyper_rustls/struct.HttpsConnectorBuilder.html#method.with_provider_and_native_roots)

@dermesser tested with the four feature combinations

"hyper-rustls", "service-account", "ring"
"hyper-rustls", "service-account", "aws-lc-rs"
"hyper-tls", "service-account", "ring"
"hyper-tls", "service-account", "aws-lc-rs"

The test with the file seems to be flaky, could you please rerun this test?

Thank you for taking the time to clean this up, it's much needed! I will merge and release soon, I just left a minor comment on the tests.


Convert to ES6

Babel is a good choice. :santa:

After migrate, it is great to remove the following package dependencies:

q
lodash

Considered completed.


Setup CI tests and fuzzing for baking app

https://github.com/trilitech/ledger-app-tezos-wallet/pull/76#pullrequestreview-1697360941

Not relevant in this repo. Baking app moved to another repo.


Added fingerprinting headers

Added a few examples to header that disclose information that is better to hide.

Good idea. :+1:

kind of security by obscurity, but definitely slows down potential attackers and saves some bandwidth

Thanks


Update dependency pulldown-cmark to v0.12.0 for mdman

Problem
Renovate bot found a newer version available for dependency pulldown-cmark in https://github.com/rust-lang/cargo/pull/14623. pulldown-cmark is used by mdman for templatizing and generating man pages.
However, the new version has some API changes that need to be fixed:
Build failure. Click to See details

error[E0532]: expected unit struct, unit variant or constant, found tuple variant `TagEnd::BlockQuote`
   --> crates/mdman/src/format/man.rs:266:25
    |
2[66](https://github.com/rust-lang/cargo/actions/runs/11116205209/job/30886065074?pr=14623#step:16:67) |                         TagEnd::BlockQuote => {
    |                         ^^^^^^^^^^^^^^^^^^ help: use the tuple variant pattern syntax instead: `TagEnd::BlockQuote(_)`
    |
   ::: /Users/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pulldown-cmark-0.12.1/src/lib.rs:256:5
    |
256 |     BlockQuote(Option<BlockQuoteKind>),
    |     ---------- `TagEnd::BlockQuote` defined here

error[E0532]: expected unit struct, unit variant or constant, found tuple variant `TagEnd::BlockQuote`
   --> crates/mdman/src/format/text.rs:234:21
    |
234 |                     TagEnd::BlockQuote => {
    |                     ^^^^^^^^^^^^^^^^^^ help: use the tuple variant pattern syntax instead: `TagEnd::BlockQuote(_)`
    |
   ::: /Users/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pulldown-cmark-0.12.1/src/lib.rs:256:5
    |
256 |     BlockQuote(Option<BlockQuoteKind>),
    |     ---------- `TagEnd::BlockQuote` defined here

For more information about this error, try `rustc --explain E0532`.

Steps

Clone rust-lang/cargo
Run cargo build-man
Fix the build failure.

Possible Solution(s)
Look into what have been changed in pulldown-cmark and update accordingly.
Version
15fbd2f607d4defc87053b8b76bf5038f2483cf4

I will claim this issue.

@rustbot claim


Add GPU metrics to metrics logging

Currently MMS_METRICS that are logged include things like CPUUtilization and Memory usage. It would be great if these also included things like GPU usage and memory.
This would make it easier to track how well we are utilizing a server's GPU resources as well as diagnose out of memory issues.
Thanks!

@mikeobr : Thanks for raising this issue. We will look into how to get  functionality in.


Support Generator Comprehensions

I am using jscs and the esnext option.
It seems that Array Comprehensions parse properly but Generator Comprehensions do not.
It would be great to get initial support for parsing these.

We'll probably support this through babel-jscs: https://github.com/jscs-dev/babel-jscs which I'l add soon.

@KylePDavis ok it's added https://github.com/jscs-dev/babel-jscs


Fix running tests on Android by tweaking interpreter paths

Checklist

[ ] documentation is added or updated
Currently Android support is incomplete, especially for the ./Configure step. I'd like to postpone documentation until everything is set.
[x] tests are added or updated
[ ] CLA is signed (I don't remember whether I've signed or not, sorry)

Description of change
My patch fixes two issues relating to running tests on Android devices.

On the device perl may not be installed in the same path as the building host, so I allow PERL to be overridden. For example, I use the following command to run tests on Android:

PERL=$(which perl) make test

The hashbangperl approach does not always work as perl, unlike sh, is not built-in in Android. It's likely that path to third-party perl builds are unknown during the build time, while some tests require an absolute path in $PERL.

Android put the default shell at /system/bin/sh instead of /bin/sh. I create a variable so that packagers can choose a different interpreter path for sh, or tests may fail. An example usage can be:

export HASHBANGSH=/system/bin/sh
./Configure android-xxx

I don't include $ENV{SHELL} in candidates as it might points to /bin/bash or even /bin/zsh, which may break tests. I don't use /usr/bin/env sh either as on Android there's no /usr/bin/env but only /system/bin/env.
An example run for tests on Android can be found at https://github.com/openssl/openssl/issues/1531#issuecomment-255370578

The PERL patch is not necessary. I'll open a new pull request.


Set development branch as default branch

@lukasschor @mikheevm would it make sense to set development to be default branch? This way we make sure new PRs are, by default, targeting this branch instead of master as it set nowadays.

Yes, both masted and development are protected and require at least one review for each PR. If proper ci with automated testing is setup I would also add successful tests as a requirement.

@rithanks @mikheevm  for your feedback. What about making development the default branch

@rmeissner any feedback on this? can we please make development the default branch?

its default now


Manage contributed jupyter kernels registration

For #4490

[x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[x] Title summarizes what is changing.
[x] Has a news entry file (remember to thank yourself!).
[ ] Appropriate comments and documentation strings in the code.
[ ] Has sufficient logging.
[ ] Has telemetry for enhancements.
[ ] Unit tests & system/integration tests are added/updated.
[ ] Test plan is updated as appropriate.
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed).

Codecov Report

Merging #5573 (c1106dc) into main (689a2de) will decrease coverage by 0%.
The diff coverage is 44%.

@@          Coverage Diff          @@
##            main   #5573   +/-   ##
=====================================
- Coverage     72%     72%   -1%
=====================================
  Files        402     402
  Lines      26641   26649    +8
  Branches    3887    3888    +1
=====================================
- Hits       19444   19377   -67
- Misses      5589    5663   +74
- Partials    1608    1609    +1

Impacted Files
Coverage Δ

...cience/notebook/creation/creationOptionsService.ts
72% <44%> (-17%)
:arrow_down:

src/client/common/errors/errorUtils.ts
34% <0%> (-38%)
:arrow_down:

src/client/datascience/kernel-launcher/types.ts
56% <0%> (-24%)
:arrow_down:

src/client/common/errors/types.ts
35% <0%> (-18%)
:arrow_down:

src/client/api/pythonApi.ts
64% <0%> (-11%)
:arrow_down:

src/client/datascience/openNotebookBanner.ts
80% <0%> (-8%)
:arrow_down:

src/client/common/errors/index.ts
72% <0%> (-8%)
:arrow_down:

...ience/notebook/emptyNotebookCellLanguageService.ts
72% <0%> (-7%)
:arrow_down:

src/client/common/application/applicationShell.ts
23% <0%> (-5%)
:arrow_down:

...lient/datascience/kernel-launcher/kernelProcess.ts
75% <0%> (-5%)
:arrow_down:

... and 12 more


:bug: Year updation to be done

On seeing the info section of Konveyor , Copyright @ 2022 is mentioned. First of all it needs to be updated and I would like to replace the regular update by adding Date.getFullYear(). this will update the year automatically. Following is the screenshot

Looking good @khareyash05 - There is one small issue RE: tests passing on your PR. Otherwise LGTM! Thanks for helping with out with this.

Thank you but this was just a small issue. I am not able to understand from the CI what is the error as all I have changed is the format of the Date. Could you pls help me with that?

@khareyash05 To run the tests locally, you can run
npm run test -w client -- --watch
And then, press the u key to update any failed tests locally.

@khareyash05 To run the tests locally, you can run
npm run test -w client -- --watch
And then, press the u key to update any failed tests locally.

Thank you will do that

Bonus points if you can hard set a timezone for the snapshot tests to run in as a part of this PR ( as @mturley suggested)
Something similar to https://medium.com/front-end-weekly/jest-snapshot-testing-with-dates-and-times-f3badb8f1d87

I think a time zone wouldn't help because the issue is what year the test was run in when the snapshot was created. You'd have to simulate a specific clock time when running the snapshots. Probably doable?
@ibolton336 in the example you linked the test passes in a specific date/time as a prop when rendering the component for the snapshot, which we could totally do (and in production it would just always default to the current date)

I think a time zone wouldn't help because the issue is what year the test was run in when the snapshot was created. You'd have to simulate a specific clock time when running the snapshots. Probably doable?
@ibolton336 in the example you linked the test passes in a specific date/time as a prop when rendering the component for the snapshot, which we could totally do (and in production it would just always default to the current date)

Can I take sometime for this? @mturley @ibolton336 I am actually occupied with the Hub tests right now and will do that probably in the weekend.

Of course! We could also just update the existing text to say 2023 and come back to it. Either way it's not a priority, no worries


Seems confused by ES6 modules

For some reason in http://inch-ci.org/github/kasperisager/doem both ES6 exported functions (export default ...) and the CJS exports module.exports show up for the same functions. I remember this not being the case when I initially set up the project. Any ideas as to what the issue might be?

Mmmh, actually I have no idea. I've had problems with ES6 from the beginning. Guess I will have to spend some time with the JS implementation of Inch (in order to figure this out).
Thx for the report! :+1:

This seems to have been fixed so I'll go ahead and close it 🎉


More than one callback in jack.Client.set_process_callback

Related to #100: can jack.Client.set_process_callback register more than one process callback?
Thank you!
Carlo

Strictly speaking, no. At least not in the way you're thinking about in https://github.com/spatialaudio/jackclient-python/issues/100#issuecomment-725984668.
Since this framework is really just a nice pythonic wrapper around the JACK API, Client.set_process_callback() only wraps the corresponding C function jack_set_process_callback(). Every time that function is called, the last registered callback is overwritten.
But there is a pretty easy way to accomplish your goal of calling multiple callbacks per cycle per client. Instead of registering multiple callbacks individually, create a wrapper function around your callbacks and register that as the callback.
# you want these to callbacks to be called on every cycle
def process_first(frames):
    # wörkwörk
	pass

def process_last(frames):
    # wörkwörk
	pass

# so instead of
wont_client = jack.Client('wontwork')
wont_client.set_process_callback(process_first)		# will never be called
wont_client.set_process_callback(process_last)		# only this one is actually called

# you create a combining callback
def process_all(frames):
	try:
		process_first(frames)
	except jack.CallbackExit:
		# proper handling recommended
		pass
	try:
		process_last(frames)
	except jack.CallbackExit:
		# proper handling recommended
		pass

# and register that one
will_client = jack.Client('willwork')
will_client.set_process_callback(process_all)		# will always call both callbacks in a specific order

If you're concerned about performance and do not care about execution order of your sub-callbacks, you can run them asynchronously.

Thank you, @C0nsultant!

The above example uses pass as a placeholder, but the "proper handling recommended" should imply that the exception should probably not be swallowed but in many cases it should probably be propagated to the main callback with raise.


Fix support for Nullables when object is null.

The Nullable support I added recently returns a bare CLR null when the value is null.  Comparing this code to the reference type conversion, it looks like I should have returned a Jurassic.Null object instead.
I noticed this when doing a strict comparison against null (e.g., return obj.nullable === null).  It returns false because null gets converted as Jurassic.Null but the obj.nullable value is just plain null.

Sorry for all the extraneous commits.  I made a change to another file that I didn't want to have pulled but pushed the change accidentally.


Adding FAQ section [New Feature]:

🎮 feature Request
feature logic and basic description
Point down the features
feature points
Select program in which you are contributing
No response
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

@rajlaxmi03 @Durgesh4993 I follow all contributing guidelines and code of conduct for this project, can you please label it properly as per GSSOC' 24 guidelines, I am willing to fix this issues ASAP.

Kindly assign me this issue ,I can contribute to this

@MrCodYrohit @Shubhra-Narang Please raise any other issue, i'll assign you
If you have any doubt you can directly send message on our discord (https://discord.gg/rZb46cCMmK), we have created seprate chennals for all projects...
Thank you :)

@rajlaxmi03 you need to edit the issue template, there is no description

i am gssoc contributor please assign this work to me.


Find all references shows bogus results

Do a find all references a couple of times
Notice that some results appear to highlight an empty line
After closing and reopening find all references widget result are no longer bogus

Notice that I only started seeing this today, it was working fine last week
Just try doing find all references a couple of times on the MenuRegistry here

This looks like a duplicate of #22310. Did you change branches recently? Also, what version of TS is active in the workspace?

I do not know if I changed branches - this happened 15 days ago.
I have tsc 2.1.4 installed.  This is our vscode repo and I have "typescript.check.tscVersion": false. So I am not sure which tsc you take in that case

Ok, please let me know if you hit this again. I know that TypeScript can get goofy when switching branches though so I suspect this is a duplicate of #22310


start web error

Traceback (most recent call last):
File "D:\git\chanlun-pro\web\chanlun_chart\app.py", line 15, in
from app import create_app
File "D:\git\chanlun-pro\web\chanlun_chart\app_init_.py", line 33, in
from chanlun.cl_utils import (
File "D:\git\chanlun-pro\src\chanlun\cl_utils.py", line 3, in
from chanlun.exchange import exchange
File "D:\git\chanlun-pro\src\chanlun\exchange_init_.py", line 5, in
from chanlun.exchange.exchange_tdx import ExchangeTDX
File "D:\git\chanlun-pro\src\chanlun\exchange\exchange_tdx.py", line 17, in
from chanlun.file_db import FileCacheDB
File "D:\git\chanlun-pro\src\chanlun\file_db.py", line 13, in
from chanlun import cl
File "D:\git\chanlun-pro\src\chanlun\cl.py", line 2, in
from pyarmor_runtime_005445 import pyarmor
File "D:\git\chanlun-pro\src\pyarmor_runtime_005445_init_.py", line 49, in
pyarmor = pyarmor().pyarmor
File "D:\git\chanlun-pro\src\pyarmor_runtime_005445_init_.py", line 48, in pyarmor
return import(name, globals(), locals(), ['pyarmor'], level=1)
RuntimeError: missing license key to run the script (1:10606)
missing license key to run the script (1:10606)
出现异常，按回车键退出Traceback (most recent call last):
File "D:\git\chanlun-pro\web\chanlun_chart\app.py", line 15, in
from app import create_app
File "D:\git\chanlun-pro\web\chanlun_chart\app_init_.py", line 33, in
from chanlun.cl_utils import (
File "D:\git\chanlun-pro\src\chanlun\cl_utils.py", line 3, in
from chanlun.exchange import exchange
File "D:\git\chanlun-pro\src\chanlun\exchange_init_.py", line 5, in
from chanlun.exchange.exchange_tdx import ExchangeTDX
File "D:\git\chanlun-pro\src\chanlun\exchange\exchange_tdx.py", line 17, in
from chanlun.file_db import FileCacheDB
File "D:\git\chanlun-pro\src\chanlun\file_db.py", line 13, in
from chanlun import cl
File "D:\git\chanlun-pro\src\chanlun\cl.py", line 2, in
from pyarmor_runtime_005445 import pyarmor
File "D:\git\chanlun-pro\src\pyarmor_runtime_005445_init_.py", line 49, in
pyarmor = pyarmor().pyarmor
File "D:\git\chanlun-pro\src\pyarmor_runtime_005445_init_.py", line 48, in pyarmor
return import(name, globals(), locals(), ['pyarmor'], level=1)
RuntimeError: missing license key to run the script (1:10606)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "D:\git\chanlun-pro\web\chanlun_chart\app.py", line 20, in
input("出现异常，按回车键退出")
AttributeError: 'filter' object has no attribute 'readline'
(chanlun) D:\git\chanlun-pro\web\chanlun_chart>

这是来自QQ邮箱的假期自动回复邮件。

您好，我最近正在休假中，无法亲自回复您的邮件。我将在假期结束后，尽快给您回复。