Add TypeScript support

Prerequisites

[X] I have written a descriptive title

[X] I have searched existing feature requests to ensure it has not already been proposed

[X] I agree to follow the Code of Conduct that this project adheres to

Description
For posterity, TypeScript support should be added.
This will open this plugin up to more users.

@uzlopak, I know you've been smashing adding nodenext support in the official Fastify repos, would you be able to offer any advice, please?
A lot of my Fastify plugins are incredibly simple ones, but would like to add TypeScript support, as the hospital I work at is merging with a neighbouring NHS trust in April, so their developers can also adopt my plugins, APIs, and Fastify.

I created a PR #196 and described some aspects


TC Meeting 2024-02-29

The OpenRail Technical Committee is holding a weekly meeting. The agenda is prepared in issues and the protocols are stored in the meetings folder.
Please add additional topics or any other comments by commenting on this issue.
Agenda

Onboarding OSRD
Project governance (see https://github.com/OpenRailAssociation/technical-committee/pull/34)
Communication channels to reach the Technical Committee
Potential project candidates

Additonal agenda item:
Evaluating RCM OSS as a new project: File for questionaire and date to meet with the team.


Issue installing netlify-cli with resulting EACCES permission denied error

Describe the bug
For some reason, when installing the netlify-cli we ran into an EACCES denied error to the autocompletion.json file. It seems to pass through when we use sudo in front of installing but this is even from a fresh install of nvm. And invoking the cli with sudo seems to work fine, but any other way fails.
To Reproduce
Steps to reproduce the behavior:

Run npm install netlify-cli -g
Error outputs

Configuration
This is at the global install level even outside of a given project.
Here is the output of npx envinfo --system --binaries --npmPackages netlify-cli --npmGlobalPackages netlify-cli:
System:
    OS: macOS 12.1
    CPU: (8) arm64 Apple M1
    Memory: 1.24 GB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.13.1 - ~/.nvm/versions/node/v16.13.1/bin/node
    npm: 8.3.0 - ~/.nvm/versions/node/v16.13.1/bin/npm

Expected behavior
It should properly install without any error output. The CLI should be usable without sudo in front.
CLI Output
Here is the error output we're seeing:
EACCES error

francisagulto@franciss-MBP recipes % npm install -g netlify-cli
npm WARN deprecated<EMAIL_ADDRESS>flatten is deprecated in favor of utility frameworks such as lodash.
npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated<EMAIL_ADDRESS>This package has been deprecated and is no longer maintained. Please use @rollup/plugin-inject.
npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future
npm ERR! code 7
npm ERR! path /Users/user_name/.nvm/versions/node/v16.13.1/lib/node_modules/netlify-cli
npm ERR! command failed
npm ERR! command sh -c node ./scripts/postinstall.js
npm ERR! /Users/user_name/.nvm/versions/node/v16.13.1/lib/node_modules/netlify-cli/node_modules/netlify-redirector/lib/redirects.js:116
npm ERR!       throw ex;
npm ERR!       ^
npm ERR!
npm ERR! Error: EACCES: permission denied, open '/Users/user_name/Library/Preferences/netlify/autocompletion.json'
npm ERR!     at Object.openSync (node:fs:585:3)
npm ERR!     at writeFileSync (node:fs:2153:35)
npm ERR!     at createAutocompletion (/Users/user_name/.nvm/versions/node/v16.13.1/lib/node_modules/netlify-cli/src/lib/completion/generate-autocompletion.js:33:3)
npm ERR!     at postInstall (/Users/user_name/.nvm/versions/node/v16.13.1/lib/node_modules/netlify-cli/scripts/postinstall.js:36:5)
npm ERR!     at Object. (/Users/user_name/.nvm/versions/node/v16.13.1/lib/node_modules/netlify-cli/scripts/postinstall.js:56:1)
npm ERR!     at Module._compile (node:internal/modules/cjs/loader:1101:14)
npm ERR!     at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
npm ERR!     at Module.load (node:internal/modules/cjs/loader:981:32)
npm ERR!     at Function.Module._load (node:internal/modules/cjs/loader:822:12)
npm ERR!     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) {
npm ERR!   errno: -13,
npm ERR!   syscall: 'open',
npm ERR!   code: 'EACCES',
npm ERR!   path: '/Users/user_name/Library/Preferences/netlify/autocompletion.json'
npm ERR! }
npm ERR!      /Users/user_name/.npm/_logs/2021-12-17T22_38_12_208Z-debug-0.log

Additional context
This was on a fresh M1 MacBook installation. This was on a fresh nvm installation as well. The correct path for node and npm seemed to be fine as well.

@ehmicky any ideas why writing in the same directory as netlify config has issues? I have used the same method as the config to get the file and write it there on startup.

Not that I can think of. However, I am wondering if this might be related to https://github.com/netlify/cli/pull/3841?

I tried to install it again into a local project and it did the same error.  I tired to use a different version of node which did not work as well.

Now sudo is not working either when trying to install it.sudo npm install netlify-cli --g

@Fran-A-Dev hey can you provide more details on the npm install? which operating system and npm version is used?
thx already in advance :)

Hi Lukas!  Thanks so much for looking into this.  The npm version I am using is 8.3.0
The OS I am on is macOS Monterey version 12.1
Thank you!

@lukasholzer I just tried again today after re-installing nvm and still same error.  I wonder what could be causing this.

@Fran-A-Dev, @maxcell
I've created a rc release with a fix. Can you verify if it worked for you?
npm install -g<EMAIL_ADDRESS>

@lukasholzer , @maxcell
I just ran the command and it works!!!! Yes!  JAMstack Joy!!  Thank you so much!! I appreciate you!

@Fran-A-Dev thank you for verifying release is coming :)

Super stoked! @lukasholzer I was missing the shared dev server over HTTPS tunnel and the lamba proxy on dev environment it does out of the box.

@lukasholzer
Posted an image in github, it installed successfully, but had an error
output on terminal.
Cheers,
Fran
On Tue, Jan 18, 2022 at 10:59 AM Lukas Holzer @.***>
wrote:

@Fran-A-Dev https://github.com/Fran-A-Dev thank you for verifying
release is coming :)
—
Reply to this email directly, view it on GitHub
https://github.com/netlify/cli/issues/3870#issuecomment-1015619659, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ARNEA7WROZBGHYMTSLB3NK3UWWMATANCNFSM5KN4DT3Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

@Fran-A-Dev oh that Is sad to hear. Can you please re-upload the image it seems to be not added here.

I Reopened the issue and added your comment here

@lukasholzer I tried to run netlify help after successfully installing the netlify cli globally and I got this output:

Did I need to run an additional command in terminal after install?
Originally posted by @Fran-A-Dev in https://github.com/netlify/cli/issues/4076#issuecomment-1015794326

Thank you @lukasholzer !  It was strange, when I installed it per your new release it successfully installed, then when trying to run a netlify utility command, it gave the error I sent you.  Progress wise though, at least we got it installed.  Thanks again for assisting on this!

can you send me your os information and more details about the environment?
Something like that:

Sure thing @lukasholzer , can I just run that exact command in the screenshot on my terminal
npx envinfo --system --binaries --npmPackages netlify-cli --npmGlobalPackages netlify cli ?

Here is a screenshot of the system

npx envinfo --system --binaries --npmPackages netlify-cli --npmGlobalPackages netlify cli

yep exact this command it will download a npm package that analyzes your system:
should print something like that:
 npx envinfo --system --binaries --npmPackages netlify-cli --npmGlobalPackages netlify cli
Need to install the following packages:
  envinfo
Ok to proceed? (y) Y

  System:
    OS: macOS 12.1
    CPU: (10) arm64 Apple M1 Max
    Memory: 10.66 GB / 64.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.13.1 - ~/.nvm/versions/node/v16.13.1/bin/node
    Yarn: 1.22.17 - ~/.nvm/versions/node/v16.13.1/bin/yarn
    npm: 8.1.2 - ~/.nvm/versions/node/v16.13.1/bin/npm

Awesome, just ran the command, here is the output @lukasholzer :

So this looks all good, I see you invoke with npm?
I cannot reproduce it so please help my to troubleshoot this.
Can you verify if this folder exists on your system?
/Users/francisagulto/Library/Preferences/netlify
If yes can you print me the privileges of the folder?
ls -lah /Users/francisagulto/Library/Preferences/netlify

and last but not least can you try writing to this folder with node?
node -e "require('fs').writeFileSync('/Users/francisagulto/Library/Preferences/netlif/ytest.json', '{}', 'utf-8')"

this would verify if your node.js installation has issues with permissions.

ahhh @lukasholzer ok let me try that now, One second here.

@lukasholzer forgive me but what is the correct syntax in shell script to check if this /Users/francisagulto/Library/Preferences/netlify exists?

@lukasholzer I ran this command, I think this is correct, it outputted that it does exists:

@lukasholzer Did the commands and here is all the output it gave:

yea thanks @Fran-A-Dev so we can track down it is not an issue of the CLI per se it seems you have installed node.js with a different user probably that is not allowed to write into your Library/Preferences folder.
@ehmicky @erezrokah asking (as netlify is general relying on this folder if we should pick a different one?) 🤔

@lukasholzer Ok that is good to know.  I will stand by and wait for your instructions on how to proceed to fix my permissions.

We use https://github.com/sindresorhus/env-paths to get the recommended user specific directory:
https://github.com/netlify/cli/blob/5ba83d8f4446d0d17ac993e4b85e8317e73db664/src/lib/settings.js#L26
I was able to reproduce this issue by running:

On a fresh install (with no prior Library/Preferences/netlify directory run npm install -g netlify-cli
Run sudo ntl status to make sure the config.json is created (it will be created as root).
Run ntl status and see that it fails with the following error:

You don't have access to this file.

This is basically this issue https://github.com/yeoman/configstore/issues/34#issuecomment-171968299, where if you ran the CLI using sudo once, it can overwrite the permissions.
You can find what Configstore  uses here https://github.com/yeoman/configstore/blob/02f07ead1cbbc1c8b49e3c9ba6e7a4896594368d/index.js#L12
Not sure if this was solved by the new version of the library here:
https://github.com/sindresorhus/conf#configfilemode
@Fran-A-Dev a possible workaround is to delete the directory and let the CLI regenerate the files via:

sudo rm -rf /Users/francisagulto/Library/Preferences/netlify/
npm install -g netlify-cli
ntl login

Going forward I believe the fix is to ensure we don't generate config.json under root, but as the current underprivileged user.
@lukasholzer and @Fran-A-Dev please let me know what you think.

@erezrokah I can try that workaround and see what happens.  One second, I can try it momentarily.

Hello! I just wanted to share a solution I came up with in the permission error as well. So what I did was headed to the ~/Library/Preferences/netlify folder and opened the "get info" option. Then I manually added my user in the "Sharing and Permission" section, together with read & write beside my user. After that, reload the terminal and all's good to go!

I just stumbled upon this problem.
The solution was simply to delete the prefs folder, and install again using npm install netlify-cli -g.
Initially I installed the CLI using sudo sudo npm install netlify-cli -g but then I did the setup to be able to install global packages without sudo. And so the ~/Library/Preferences/netlify folder had been created previously by root and not my user.


Project : Facial Expression Recognition with PyTorch Issue #697

Resolves Issue #697

@revanth1718 already marked as spam cant merge this one,


Flickering test

Test failure:
@statechannels/nitro-protocol: FAIL test/contracts/AssetHolder/claimAll.test.ts (79.11s)
@statechannels/nitro-protocol:   ● claimAll › 3. swap guarantee,             3 destinations
@statechannels/nitro-protocol:     : Timeout - Async callback was not invoked within the 5000ms timeout specified by jest.setTimeout.Timeout - Async callback was not invoked within the 5000ms timeout specified by jest.setTimeout.Error:
@statechannels/nitro-protocol:       59 |     ${'6. guarantee not on chain'}                     | ${{g: 5}}  | ${[]}                 | ${{A: 5, B: 5}}       | ${{A: 5}}       | ${{g: 0}} | ${{B: 5}}       | ${reason6}
@statechannels/nitro-protocol:       60 |     ${'7. swap guarantee, overfunded, 2 destinations'} | ${{g: 12}} | ${['B', 'A']}         | ${{A: 5, B: 5}}       | ${{}}           | ${{g: 2}} | ${{A: 5, B: 5}} | ${undefined}
@statechannels/nitro-protocol:     > 61 |     ${'8. underspecified guarantee, overfunded      '} | ${{g: 12}} | ${['B']}              | ${{A: 5, B: 5}}       | ${{}}           | ${{g: 2}} | ${{A: 5, B: 5}} | ${undefined}
@statechannels/nitro-protocol:          |                                                                                ^
@statechannels/nitro-protocol:       62 |   `(
@statechannels/nitro-protocol:       63 |     '$name',
@statechannels/nitro-protocol:       64 |     async ({
@statechannels/nitro-protocol:       at new Spec (../../node_modules/jest-jasmine2/build/jasmine/Spec.js:116:22)
@statechannels/nitro-protocol:           at Array.forEach (<anonymous>)
@statechannels/nitro-protocol:       at Suite.<anonymous> (test/contracts/AssetHolder/claimAll.test.ts:61:178)

Re-running it, the test passes:
@statechannels/nitro-protocol: PASS test/contracts/AssetHolder/claimAll.test.ts (67.933s)

Is this because the 5 second timeout is too short, and that test run happened to go over the edge? Note that the passing test took ~15% less time than the failing test.

This seems infrequent enough to close.


metrics: record stale/unsent webhooks

There's drift between when a webhook should be periodically re-searched and the webhook firing again (if a match is found). It seems helpful to expose this drift as a metric. Thoughts?

Removed in v0.26.0


feat: add node graceful shutdown kubelet config

What type of PR is this?
/kind feature
/kind api-change

What this PR does / why we need it:
This PR adds node graceful shutdown Kubelet config items and exposes those for client use, so that we can allow customers to enable this feature on their nodes.
Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

6 of 6 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 79.433%

Totals

Change from base Build<PHONE_NUMBER>:
0.04%

Covered Lines:
2298

Relevant Lines:
2893

💛  - Coveralls

you'll want to recreate this PR without using a fork so required checks can run - I'm gonna add a note about this to the readme so folks don't continue to make the same mistake

I'm closing this PR as per comment. Will recreate it from another branch within the repo.


properly handle build-controller behavior on post merge workflows

Currently the authorization token setup is not correct to properly handle build-controller actions on post merge workflows -- only the production token is available and it's not properly handled.

I think I'm going to add a bypass mechanism to not build a controller image in the post-merge workflow.  Since the controller image is not currently automatically updated the post merge workflow really should continue to use the existing image to more closely mirror production behavior.
If we ever get to the point of doing automatic controller builds for production then maybe we will revisit this with a different scheme/idea.


CockroachDB export to migrate to MySQL and Postgres

Exalate commented:
This is a request to reopen #3540
Jira Issue: DOC-5114

Closing this now that https://github.com/cockroachdb/docs/issues/3540 is reopened. Thank you, @Inigo4562.


Metadata Functions for SchemaSpy

I was trying to run SchemaSpy on a DuckDB database with indices defined, and it was dying after throwing a host of exceptions related to missing metadata functions. I took a stab at implementing the ones it was complaining about, and it seems to work now by producing diagrams. (There are still a few left, but they seem recoverable.)
I'm not a JDBC expert, so I don't know if this is good enough. Is this good enough for a PR, or what else would you like to see?

Hey there, those look great - if you're able to write some quick tests I'd be happy to merge those


error while opening the imzml file made by firefly software from Prosolia Inc,

cannot able to open a DESI imzml file made by firefly software from prosolia inc.
I get the following errors.
p = ImzMLParser("C:\Users\Thermo\Downloads\pyimzml\data\firelfy\Org_3_11_.imzML")
Traceback (most recent call last):
Input In [9] in <cell line: 1>
p = ImzMLParser("C:\Users\Thermo\Downloads\pyimzml\data\firelfy\Org_3_11_.imzML")
File ~\anaconda3\lib\site-packages\pyimzml\ImzMLParser.py:140 in init
self.imzmldict = self.__readimzmlmeta()
File ~\anaconda3\lib\site-packages\pyimzml\ImzMLParser.py:319 in __readimzmlmeta
val = _get_cv_param(scan_settings_list_elem, accession, deep=True, convert=True)
File ~\anaconda3\lib\site-packages\pyimzml\ImzMLParser.py:50 in _get_cv_param
node = elem.find('%s%scvParam[@accession="%s"]' % (base, XMLNS_PREFIX, accession))
AttributeError: 'NoneType' object has no attribute 'find'

I saw your datasets with this error on METASPACE. The problem is an invalid imzML file.
The first two lines in the imzML file should look like this:
<?xml version="1.0"?>
<mzML xmlns="http://psi.hupo.org/ms/mzml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://psi.hupo.org/ms/mzml http://psidev.info/files/ms/mzML/xsd/mzML1.1.0_idx.xsd" version="1.1">

Your file is missing the first line and xmlns has the wrong URL:
<mzML xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

Most likely, the problem is in the converter or its settings.


getAlby Damus wallet for all new Damus users [integration]

I am a product contributor for nostr client Damus.
Currently there is no automagic wallet creation upon new user onboarding, and new Damus profile creation.
Zapping flow requires exiting from damus app (nostr wallet connect not implemented).
I would like for every new Damus user onboarded to automagically receive a GetAlby wallet that:

has a unique LNUrl address (bonus points if related to selected username of damus user)
is zappable (nip-57)
is connected to damus via nostr wallet connect, enabling seamless zapping from damus

Please DM on nostr, so I can help coordinate with damus eng team npub1zafcms4xya5ap9zr7xxr0jlrtrattwlesytn2s42030lzu0dwlzqpd26k5
cc @jb55

Users need to explicitly sign up with Alby when setting up their wallet connection (it can't be done automatically by Damus), but otherwise this issue has been completed. :rocket:

On Sun, Dec 17, 2023 at 09:31:41PM -0800, Roland wrote:

Users need to explicitly sign up with Alby when setting up their wallet
connection (it can't be done automatically by Damus)

It's impossible? That's disappointing.

Does the entire flow need to be done in Damus?
For instance, can Alby autogenerate receive LN addresses for new Damus profiles with a follow on prompt to create an Alby account outside Damus?

@alltheseas an Alby account must be created before a lightning address can be created. I don't believe we can reserve funds on a user's behalf that they can claim later after signing up. (What happens if they don't sign up?)
@jb55 did you manage to talk with @bumi or @kiwiidb at Nostrasia?
There are some big issues here, and this may significantly change as we try to push users to self-custodial wallets as the primary option.
I think this is critical we make good UX here as Damus is onboarding a lot of people into Bitcoin. We are trying to push NWC as much as possible so that Damus users have multiple wallet connection options.

What happens if they don't sign up?

Donate to Opensats or your non-profit(s) of choice. We can state terms explicitly if after X time you don't set up sats are donated to a non-profit.

I think this is critical we make good UX here as Damus is onboarding a lot of people into Bitcoin

100% agree. Let's meet to talk about this. How is first weeks of January?
Yes, Will spoke with Bumi / Kwinten at Nostrasia.

@alltheseas we discussed this internally and unfortunately we cannot support this. We already introduced invite codes to limit the number of signups (see reasoning)
NWC is probably the best option here: it's the first open protocol which supports both custodial and self-custodial wallets in a way that's really easy to implement for clients. We believe there is going to be huge adoption.
However, if you still want a wallet created without the user having to do anything, the only option we can see it to embed a lightning wallet directly into Damus.
I'm sorry that we cannot help more :pray:


Cross-compilation of dependencies for target platforms

This issue is a placeholder ATM.
We need to cross-compile openssl for Android in order to enable TLS support for Sync, and make that process as transparent as possible while using mentat with "syncable" feature turned on.

There’s a root issue here: why does our HTTP library not use system SSL? I suspect the answer here is a pass through libopenssl-sys, not cross-compiling.


Unspecified implicit enum conversion from literal 0X0

[Enter feedback here]
There is nothing in the specification to indicate that the following code is well-formed:
ConsoleColor black = 0X0;

I think it really supports any compile-time constant equal to 0:
ConsoleColor black = DayOfWeek .Monday - DayOfWeek .Monday;

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

ID: 7be4c24e-9e92-6b75-2b8e-2cb6cb072b5b
Version Independent ID: 450064c8-720e-3b90-18d6-7bd5f183857e
Content: Conversions - C# language specification
Content Source: spec/conversions.md
Product: dotnet-csharp
Technology: csharp-spec
GitHub Login: @dotnet-bot
Microsoft Alias: wiwagn

Hi @yecril71pl
This is covered in the standard in 11.2.4 Implicit enumeration conversions.
That clause specifies that the integer constant 0 is implicitly convertible to any enum type.
I'll close this as answered.

Hi @yecril71pl
This is covered in the standard in 11.2.4 Implicit enumeration conversions.
That clause specifies that the integer constant 0 is implicitly convertible to any enum type.
I'll close this as answered.

But the published text still says:

An implicit enumeration conversion permits the decimal_integer_literal 0 to be converted to any enum_type


Issue #1435 is closed.

Issue #1435 is closed, which strikes me as a bug. It should be reopened, as lots of people are having trouble with colors.

Will close this and punt discussion to that issue.


Support HAProxy's PROXY protocol v1 in DialProxy.

Travis build horked because of lint (see other PR), but new test passes.


WMCore_t.WMRuntime_t.DashboardInterface_t.DashboardInterfaceTest:testAFailedJobMonitoring changed from success to error
WMCore_t.WMRuntime_t.DashboardInterface_t.DashboardInterfaceTest:testAKilledJobMonitoring changed from success to error
WMCore_t.WMRuntime_t.DashboardInterface_t.DashboardInterfaceTest:testASuccessfulJobMonitoring changed from success to error
WMCore_t.WMRuntime_t.DashboardInterface_t.DashboardInterfaceTest:testMultithreadedApplication changed from success to error
WMCore_t.WMSpec_t.StdSpecs_t.Analysis_t.AnalysisTest:testAnalysis changed from success to error
WMCore_t.WMSpec_t.StdSpecs_t.DQMHarvest_t.DQMHarvestTests:testDQMHarvest changed from success to error
WMCore_t.WMSpec_t.StdSpecs_t.MonteCarloFromGEN_t.MonteCarloFromGENTest:testMonteCarloFromGEN changed from success to error
WMCore_t.WMSpec_t.StdSpecs_t.PrivateMC_t.PrivateMCTest:testPrivateMC changed from success to error
WMCore_t.WMSpec_t.StdSpecs_t.PromptReco_t.PromptRecoTest:testPromptReco changed from success to error
WMCore_t.WMSpec_t.StdSpecs_t.ReDigi_t.ReDigiTest:testChainedReDigi changed from success to error
WMCore_t.WMSpec_t.StdSpecs_t.ReDigi_t.ReDigiTest:testCombinedReDigiRecoConfig changed from success to error
WMCore_t.WMSpec_t.StdSpecs_t.ReDigi_t.ReDigiTest:testDependentReDigi changed from success to error
WMCore_t.WMSpec_t.StdSpecs_t.ReDigi_t.ReDigiTest:testSingleStepReDigi changed from success to error
WMCore_t.WMSpec_t.StdSpecs_t.ReDigi_t.ReDigiTest:testThreeStepChainedReDigi changed from success to error
WMCore_t.WMSpec_t.StdSpecs_t.ReReco_t.ReRecoTest:testReReco changed from success to error
WMCore_t.WMSpec_t.StdSpecs_t.ReReco_t.ReRecoTest:testReRecoDroppingRECO changed from success to error
WMCore_t.WMSpec_t.StdSpecs_t.StoreResults_t.StoreResultsTest:testStoreResults changed from success to error
WMCore_t.WMSpec_t.Steps_t.Fetchers_t.CMSSWFetcher_t.URLFetcherTest:testA_BasicFunction changed from success to error
WMCore_t.WMSpec_t.Steps_t.Fetchers_t.URLFetcher_t.URLFetcherTest:testA_BasicFunction changed from success to error
WMCore_t.WorkQueue_t.Policy_t.Start_t.Block_t.BlockTestCase:testContinuousSplittingSupport changed from success to error
WMCore_t.WorkQueue_t.Policy_t.Start_t.Block_t.BlockTestCase:testDataDirectiveFromQueue changed from success to error
WMCore_t.WorkQueue_t.Policy_t.Start_t.Block_t.BlockTestCase:testDatasetLocation changed from success to error
WMCore_t.WorkQueue_t.Policy_t.Start_t.Block_t.BlockTestCase:testGetMaskedBlocks changed from success to error
WMCore_t.WorkQueue_t.Policy_t.Start_t.Block_t.BlockTestCase:testIgnore0SizeBlocks changed from success to error
WMCore_t.WorkQueue_t.Policy_t.Start_t.Block_t.BlockTestCase:testInvalidSpecs changed from success to error
WMCore_t.WorkQueue_t.Policy_t.Start_t.Block_t.BlockTestCase:testLumiSplitTier1ReRecoWorkload changed from success to error
WMCore_t.WorkQueue_t.Policy_t.Start_t.Block_t.BlockTestCase:testMultiTaskProcessingWorkload changed from success to error
WMCore_t.WorkQueue_t.Policy_t.Start_t.Block_t.BlockTestCase:testPileupData changed from success to error
WMCore_t.WorkQueue_t.Policy_t.Start_t.Block_t.BlockTestCase:testRunWhitelist changed from success to error
WMCore_t.WorkQueue_t.Policy_t.Start_t.Block_t.BlockTestCase:testTier1ReRecoWorkload changed from success to error
WMCore_t.WorkQueue_t.Policy_t.Start_t.Block_t.BlockTestCase:testWhiteBlackLists changed from success to error
WMCore_t.WorkQueue_t.Policy_t.Start_t.Block_t.BlockTestCase:testWithMaskedBlocks changed from success to error
WMCore_t.WorkQueue_t.Policy_t.Start_t.Dataset_t.DatasetTestCase:testDataDirectiveFromQueue changed from success to error
WMCore_t.WorkQueue_t.Policy_t.Start_t.Dataset_t.DatasetTestCase:testInvalidSpecs changed from success to error
WMCore_t.WorkQueue_t.Policy_t.Start_t.Dataset_t.DatasetTestCase:testLumiSplitTier1ReRecoWorkload changed from success to error
WMCore_t.WorkQueue_t.Policy_t.Start_t.Dataset_t.DatasetTestCase:testMultiTaskProcessingWorkload changed from failure to error
WMCore_t.WorkQueue_t.Policy_t.Start_t.Dataset_t.DatasetTestCase:testParentProcessing changed from failure to error
WMCore_t.WorkQueue_t.Policy_t.Start_t.Dataset_t.DatasetTestCase:testRunWhitelist changed from success to error
WMCore_t.WorkQueue_t.Policy_t.Start_t.Dataset_t.DatasetTestCase:testTier1ReRecoWorkload changed from failure to error
WMCore_t.WorkQueue_t.Policy_t.Start_t.Dataset_t.DatasetTestCase:testWhiteBlackLists changed from failure to error
WMCore_t.WorkQueue_t.Policy_t.Start_t.ResubmitBlock_t.ResubmitBlockTest:testEmptyACDC changed from success to error
WMCore_t.WorkQueue_t.Policy_t.Start_t.ResubmitBlock_t.ResubmitBlockTest:testUnsupportedACDC changed from success to error
WMCore_t.WorkQueue_t.WMBSHelper_t.WMBSHelperTest:testCreateSubscription changed from success to error
WMCore_t.WorkQueue_t.WMBSHelper_t.WMBSHelperTest:testDuplicateFileInsert changed from success to error
WMCore_t.WorkQueue_t.WMBSHelper_t.WMBSHelperTest:testKillWorkflow changed from success to error
WMCore_t.WorkQueue_t.WMBSHelper_t.WMBSHelperTest:testLumiMaskRestrictionsKO changed from success to error
WMCore_t.WorkQueue_t.WMBSHelper_t.WMBSHelperTest:testLumiMaskRestrictionsOK changed from success to error
WMCore_t.WorkQueue_t.WMBSHelper_t.WMBSHelperTest:testParentage changed from success to error
WMCore_t.WorkQueue_t.WMBSHelper_t.WMBSHelperTest:testReReco changed from success to error
WMCore_t.WorkQueue_t.WMBSHelper_t.WMBSHelperTest:testReRecoBlackRunRestriction changed from success to error
WMCore_t.WorkQueue_t.WMBSHelper_t.WMBSHelperTest:testReRecoWhiteRunRestriction changed from success to error
WMCore_t.WorkQueue_t.WMBSHelper_t.WMBSHelperTest:testTruncatedWFInsertion changed from success to error
WMCore_t.WorkQueue_t.WorkQueueBackend_t.WorkQueueBackendTest:testDuplicateInsertion changed from success to error
WMCore_t.WorkQueue_t.WorkQueueBackend_t.WorkQueueBackendTest:testPriority changed from success to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:test0eventBlock changed from failure to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testBlackList changed from failure to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testCancelWork changed from failure to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testCancelWorkGlobal changed from failure to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testCloseWorkOpenBlocks changed from failure to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testCloseWorkTimeout changed from success to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testConflicts changed from failure to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testDeleteWork changed from failure to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testDrainMode changed from success to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testEndPolicyNegotiating changed from failure to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testFailRequestAfterTimeout changed from success to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testGlobalBlockSplitting changed from failure to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testGlobalDatasetSplitting changed from failure to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testIgnoreDuplicates changed from success to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testInvalidSpecs changed from success to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testMultiTaskProduction changed from success to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testMultipleTeams changed from failure to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testOpenBlocks changed from failure to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testParentProcessing changed from failure to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testPileupOnProduction changed from success to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testPrioritiesWorkPolling changed from failure to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testPriority changed from success to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testProcessing changed from failure to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testProcessingWithContinuousSplitting changed from failure to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testProcessingWithPileup changed from failure to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testProduction changed from success to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testProductionMultiQueue changed from failure to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testQueueChaining changed from failure to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testQueueChainingStatusUpdates changed from failure to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testResetWork changed from failure to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testResubmissionWithParentsWorkflow changed from success to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testResubmissionWorkflow changed from failure to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testResubmissionWorkflowSiteWhitelistLocations changed from failure to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testSiteStatus changed from failure to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testSitesFromResourceControl changed from failure to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testSplittingLargeInputs changed from failure to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testTeams changed from failure to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testThrottling changed from failure to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testWMBSInjectionStatus changed from failure to error

Previously working unit tests have failed!

test this please

It seems to me that majority of unit tests failed due to simple oversight on my sight in pycurl manager. In particular there are plenty of POST calls which uses empty params dict. In that case I fixed the problem in this PR: https://github.com/dmwm/WMCore/pull/6347 Please accept 6347 and then re-test this PR with this fix.

test this please

test this please

Thanks Valentin. I put a copy/paste error in Jenkins. :-1:

I fixed another bug in pycurl_manager, see https://github.com/dmwm/WMCore/pull/6355. So we need to merge #6355 and retest this PR again.

Ok, let me do that.  Have not got the automated stuff yet. Maybe tomorrow.

Ok, I have started a new baseline. When it completes you should see a message in https://github.com/dmwm/ContinuousIntegration/issues/6#issuecomment-150592973 after that you should be able to request that Jenkins starts a new round here and it should be against that new baseline.

Is there a reason you are not just adding the commits to pycurl_manager to this branch? Seems easier.

Is there a reason you are not just adding the commits to pycurl_manager to this branch? Seems easier.

Sorry I haven't thought about that. Why didn't you say it earlier? It is all your fault. :smile:
@vkuznet, Valentin, feel free to add this one on your patch if you find any bugs next time. I can just close this one.

Hmm, I don't think it a good idea. This PR is simple and transparent, as well
as other PRs I make for pycurl_manager. They stay independent. But if you want
everything in one go then of course we can combine both.
On  0, ticoann<EMAIL_ADDRESS>wrote:

Is there a reason you are not just adding the commits to pycurl_manager to this branch? Seems easier.

Sorry I haven't thought about that. Why didn't you say it earlier? It is all your fault. :smile:
@vkuznet, Valentin, feel free to add this one on your patch if you find any bugs next time. I can just close this one.

Reply to this email directly or view it on GitHub:
https://github.com/dmwm/WMCore/pull/5845#issuecomment-150607630

Just asking. Do whatever makes the most sense to you.

Sure Valentin, thanks.

test this please

replaced by #6360


autofs: 5.1.6 -> 5.1.9

Description of changes

The CHANGELOG file is included in the sources archive.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

please rebase the commit rather than merge from master.

please rebase the commit rather than merge from master.

Cleaned history by doing a rebase.

Found the same patches in fedora, the extra ones they have do very little. LGTM

@ofborg build autofs5 autofs5.passthru.tests


Rich text doesn't play nice with the whitelist

description.

Please post examples

Hmm considering not even thinking of rich text support as a "feature".  Probably pretty easily abusable for now. Sorry


status and headers of returned Response instances are ignored

First reported 2013 #511 the bug is still present in the master branch. Even worse according to the documentation the following should work just fine.
Response(body='', status=403, headers=headers)

While the body argument works the status and headers arguments have no effect whatsoever.
I am refiling this issue, since the previous one has a misleading title and doesn't mention that it also effects headers.
Having to raise HTTPResponse for non-erroneous statuses like redirects doesn't make any semantic sense. If this bug won't get fixed after 4 years it should at least be documented.

Could you give an example of what you are trying to do?

It is true that Response as a base class should either throw an error or work as expected when returned (as discussed in #511) and the issue is quite easy to fix, actually. Pull requests are welcomed.
The correct way however is to return or raise HTTPResponse for normal responses and HTTPError for errors. These are handled differently: HTTPError triggers error handles while HTTPResponse does not. I don't really see why HTTPResponse would not make semantic sense for non-erroneous statuses. You don't have to raise it as an exception, just return it.


HDDS-9108. Improve error message when force deleting FSO bucket via S3

What changes were proposed in this pull request?
AWS S3 api for force deleting a bucket and its contents rb --force fails on FSO buckets.
This happens because the S3 client sends individual delete requests for each key in the bucket. This will work with the flat namespace in OBJECT_STORE buckets.
But in FSO buckets with hierarchical namespace some key deletes might fail. Causing the bucket delete operations to fail.
For example,
$ ozone sh bucket create o3://localhost:9862/s3v/bucket1
$ ozone sh key put o3://localhost:9862/s3v/bucket1/dir1/dir2/dir3/key1 a.txt
$
$ aws s3 --endpoint http://<IP_ADDRESS>:9878  rb --force s3://bucket1
# Request 0 is list all keys in the bucket
# Request 1
delete: s3://bucket1/dir1/dir2/dir3/  ### fails because /dir1/dir2/dir3/ is not empty
# Request 2
delete: s3://bucket1/dir1/                 ### fails because /dir1/ is not empty
# Request 3
delete: s3://bucket1/dir1/dir2/dir3/key1 ### succeeds
# Request 4
delete: s3://bucket1/dir1/dir2/          ### fails because /dir1/dir2/ is not empty
# Request 5 is delete: s3://bucket1
remove_bucket failed: s3://bucket1 An error occurred (BucketNotEmpty) when calling the DeleteBucket operation: The bucket you tried to delete is not empty.

Since we can't modify the order in which AWS S3 client sends the individual key delete, improved the error message to indicate the rb --force is supported on OBJECT_STORE buckets. FSO buckets would need to be emptied prior to deletion.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-9108
How was this patch tested?
Manual test
$ ozone sh bucket create /s3v/bucket1
$ ozone sh key put /s3v/bucket1/dir1/dir2/dir3/key1 CONTRIBUTING.md
$ aws s3 --endpoint http://s3g:9878 rb --force s3://bucket1
delete: s3://bucket1/dir1/
delete: s3://bucket1/dir1/dir2/dir3/key1
delete: s3://bucket1/dir1/dir2/dir3/
delete: s3://bucket1/dir1/dir2/
remove_bucket failed: s3://bucket1 An error occurred (BucketNotEmpty) when calling the DeleteBucket operation: The bucket you tried to delete is not empty. If you are using --force option to delete all objects in the bucket, please ensure that the bucket layout is OBJECT_STORE or that the bucket is completely empty before delete.

@SaketaChalamchala Thanks for working on this. When we do force delete FSO bucket, then there is possibility few keys will be deleted while some may not.  With the change in this PR it will show error message while some keys also got deleted in the process. Can we throw error at the beginning of the operation itself for FSO bucket instead failing in the middle of the operation and show the error?

This improvement on its own is fine, we can add an additional improvement for handling just FSO. This improvement is applicable for any scenario where the bucket is not full.

Can we throw error at the beginning of the operation itself for FSO bucket instead failing in the middle of the operation and show the error?
There is no was to know on S3 gateway if the delete requests for keys are a part of the force delete operation. From S3G perspective we receive individual requests for deleting keys and then a request to delete the bucket at the end. So, there might not be a way to identify the top of the operation.

$ aws s3 --endpoint http://<IP_ADDRESS>:9878  rb --force s3://bucket1
# GET Request 0 is list all keys in the bucket
# DELETE Request 1
delete: s3://bucket1/dir1/dir2/dir3/  ### fails because /dir1/dir2/dir3/ is not empty
# DELETE Request 2
delete: s3://bucket1/dir1/                 ### fails because /dir1/ is not empty
# DELETE Request 3
delete: s3://bucket1/dir1/dir2/dir3/key1 ### succeeds
# DELETE Request 4
delete: s3://bucket1/dir1/dir2/          ### fails because /dir1/dir2/ is not empty
# DELETE Request 5 is delete: s3://bucket1
remove_bucket failed: s3://bucket1 An error occurred (BucketNotEmpty) when calling the DeleteBucket operation: The bucket you tried to delete is not empty.

Yes looks like we cannot know if the request is part of force delete. Improving error message is the only best way we can do currently or else we need to completely block FSO key deletion from S3.
I think you can create another Jira so that can be tracked in future.

Yes looks like we cannot know if the request is part of force delete. Improving error message is the only best way we can do currently or else we need to completely block FSO key deletion from S3.
I think you can create another Jira so that can be tracked in future.

Done. Raised HDDS-9637


Thoughts on supporting case insensitivity?

Thoughts on supporting case insensitivity out of the box OR adding it as an input?
https://github.com/mheap/github-action-required-labels/blob/main/index.js#L93C7-L93C77
- const appliedLabels = labels.map((label) => label.name);
+ const appliedLabels = labels.map((label) => label.name);
+ const lowerCaseAppliedLabels = appliedLabels.map((label) => label.toLowerCase());

- intersection = providedLabels.filter((x) => appliedLabels.includes(x))
+ intersection = providedLabels.filter((x) => lowerCaseAppliedLabels.includes(x.toLowerCase()))

The use case here is that we want to use this in a composite across repos but some repos have a "Do Not Merge" label spelled in different ways. In order to appropriately handle this, we have to do something like:
    - uses: mheap/github-action-required-labels@fab3b73a9443656a796639b75fe08d4eb8c75e75
      with:
        mode: exactly
        count: 0
        labels: "DO NOT MERGE, Do Not Merge, Do not merge, do not merge"
        add_comment: true

But that's obviously got a little bit of a smell to it, and the comment that get's posted isn't ideal.

Out of the box makes sense to me. I’ve not seen any real world use case for case sensitive labelsOn 13 Mar 2024, at 18:11, codfish @.***> wrote:
Thoughts on supporting case insensitivity out of the box OR adding it as an input?
https://github.com/mheap/github-action-required-labels/blob/main/index.js#L93C7-L93C77

intersection = providedLabels.filter((x) => appliedLabels.includes(x))

intersection = providedLabels.filter((x) => lowerCaseAppliedLabels.includes(x.toLowerCase()))

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

@mheap OK sounds good, I can put together a PR today for your review!

@mheap here you go! https://github.com/mheap/github-action-required-labels/pull/76

This was released in https://github.com/mheap/github-action-required-labels/releases/tag/v5.4.0


Show warnings about outdated Phobos modules

As moving old & ugly Phobos modules to undeaD doesn't seem to be an option for now, let's at least try to warn the user.
I used the same message as we already display on std.xml.
Are there other modules that you would like to be included on this list?
Previous discussion: https://github.com/dlang/dlang.org/pull/1778

I'm not keen about this.

The messages making remarks about work in progress on collections are not actionable.
The messages sending people to third-party alternatives are actionable but seem out of place and with no precedent. For example the page on C++'s std::unordered_map there's no "check out Google sparsehash for much better and much faster alternatives". Even more poorly done parts of C++ std such as the localization library do not come with recommendations to avoid in favor of e.g. ICU. As far as I know other languages' standard library official documentation also avoid placing judgment on the artifacts they offer. I don't see why we need to be the only ones to wear the hair shirt.

On the one hand, it does kind of make sense to point folks to better alternatives, but on the other hand, it's downright weird to have something in the standard library that we basically say not to use and then point to 3rd party libraries. It's one thing to replace something in the standard library with something else. It's quite another to tell folks to go use 3rd party libraries but leave the supposedly bad solution in the standard library.
At the same time, I don't know what we really should be doing with some of these, because for some of them, it seems pretty unlikely that we're going to end up with replacements in Phobos. Even getting a replacement for std.xml seems pretty iffy, and there's a package up on code.dlang.org for a GSoC project that was supposedly going to replace it (though since its maintainer seems to be MIA, that project is looking rather dead right now).
However, it is perfectly normal to have 3rd party alternatives exist for standard library constructs where the 3rd party alternative is considered by many to be superior. So, unless the Phobos solution is so bad that we really need to be telling folks to not use it (in which case, we really should look at removing it and putting it in undead), I'm not sure that it makes a lot of sense to be doing something like this. I mean, we put a note on std.xml to warn folks because a replacement was supposed to be coming, and we wanted folks to be aware that they were going to have to change their code eventually, but that was years ago and we still don't have a replacement, which looks that much worse than having a bad API in the first place. And for the others, except for std.container, there isn't even a consensus that we plan on replacing them.
Sure, I hate std.socket. I even have a partially completed replacement that will be @nogc for at least the low level API, but it's not going to be done for a while, and I'm not sure that I even want to get try and get it in Phobos, because then I don't control it anymore, and it's going to include SSL support, which realistically means relying on 3rd party libraries, which I don't think is appropriate for the standard library. And no one else has stepped forward to replace it. In fact, almost no one seems to want to write modules to go in Phobos at this point. Anyone doing much of anything just puts it up on code.dlang.org. So, I don't think that it's reasonable at this point to expect that replacements will emerge for all of these modules, and I have to agree with Andrei that it just looks bad to be telling folks not to use something that's in the standard library.
I think that we should either decide that a module is so bad that it needs to be removed and put in undead, or we should just leave it. Having something is still often better than nothing, even if it's subpar. And if a replacement does come along later, then we can look at going through the process of replacing it. But putting labels on the top telling folks that the code is bad and that they should go use a 3rd party alternative just looks bad - especially when we have a clear track record which indicates that it's unlikely that a replacement is going to happen. A few modules have been replaced over the years (e.g. std.datetime and std.regex are replacements for older modules), but when we say that we want to replace something, and no one has stepped up to replace it, it consistently sits there for years without getting replaced. Even when someone has stepped up, they often disappear before they're done. So, realistically, I think that we need to just learn to live with some of these modules being in the standard library and letting folks use them, much as that's not ideal. Anyone who is then not happy with any of the modules can then look for alternatives on code.dlang.org.

I think that we need to just learn to live with some of these modules being in the standard library and letting folks use them, much as that's not ideal. Anyone who is then not happy with any of the modules can then look for alternatives on code.dlang.org.

I just saw this thread on the NG and it shows perfectly what happens if we don't deprecate the old and ugly modules (or at least hide their documentation): people start using them, get frustrated by their brokenness, associate this with D and move on.

So.. this going to move forward or be closed.  Seems somewhat pointless to leave it unresolved.

std.uri : it only supports a subset of the URI standard. Just the name is a scam.

@andralex looks like we need a definite decision on this. Please close or merge.

I like this PR.  It looks out for the user, who is likely not tracking thousands of forum posts to know what not to use or watch out for.  A warning doesn't have to be actionable, a head's up is good enough.  As for it looking bad, realistically there are outdated modules in Phobos that we'd like to replace with better outside modules, but only don't because there is legacy code relying on it and the outside authors don't want to go through the Phobos review gauntlet, at least not yet. Better not to onboard more new users onto those outdated modules and have them try out the better outside modules instead.
If other stdlibs are not honest enough to do this, all the more reason for Phobos to do what's best for the user and differentiate itself.

Yet another example of someone bumping into an old, unmaintained module and taking its quality for granted<EMAIL_ADDRESS>

I think the real question is really just which modules. Hardly anyone would disagree about deprecating std.signals and maybe std.outbuffer. So maybe just use that box for deprecated modules.
The other modules in this PR are usable, albeit not great. And indeed it's unclear when and whether replacements will be available.
I'd also agree to rather make code.dlang.org more prominent on the website and better explorable than pointing people from the standard library to 3rd party libs.

Going to close this until the discussion is resolved.


signal transducer, downstream of receptor, with serine/threonine kinase activity

I just spotted this term (Never noticed it before).
It worries me that PomBase have only 8 annotations to this term,
http://www.pombase.org/spombe/result/SPAPB18E9.02c
As many of our protein kinases will fit this definition.

I see its name changed recently from
receptor signaling protein serine/threonine kinase activity
Is there a SF ticket about this? The new names seems quite a clunky name  for a protein kinase.
Can it not be
signal transducing protein kinase activity (that would fit the def)
...the existing name makes the kinase activity appear  not to be the primary activity.
And a question. When annotating protein kinases, is the terminal kinase considered to be a "signal transducer" too? (I'm never sure about this)

@Antonialock

The term is old, but the name is new-ish.  The terms in this branch were originally called 'receptor signaling protein ...' which sounds like it might refer to a receptor,  but confusingly this class excludes receptors.
The new names are my fault.  This sounds nicer:

signal transducing protein kinase activity

Following the GO definition of signal transducer, this could cover receptors too, but my guess is that most biologists would assume this was downstream.   So I think this name could work (although I'd add a clarifying comment for future editors.

It worries me that PomBase have only 8 annotations to this term,

23 annotations for 8 protein?
http://www.ebi.ac.uk/QuickGO/GAnnotation?a=&goid=GO%3A0004702&termUse=ancestor&relType=IPO%3D&customRelType=IPOR%2B-%3F%3D&evidence=IMP%2CIGI%2CIPI%2CIDA%2CIEP%2CEXP&protein=&tax=4895&qualifier=&ref=&with=&source=&q=&col=proteinDB%2CproteinID%2CproteinSymbol%2Cqualifier%2CgoID%2CgoName%2Caspect%2Cevidence%2Cref%2Cwith%2CproteinTaxon%2Cdate%2Cfrom%2Csplice&select=normal
Mostly to subclasses, so if some are missing then there must be missing classifications in GO.  Can you list?

Currently they are annotated to plain old
protein/serine protein kinase activity type terms....
protein tyrosine kinase activity
things like,
wee1 http://www.pombase.org/spombe/result/SPCC18B5.03
cdr2 http://www.pombase.org/spombe/result/SPAC57A10.02
cdrr1 http://www.pombase.org/spombe/result/SPAC644.06c
but the  "signal transducing protein kinase activity" is another orthogonal classification. It combines function with process (signal transduction)... we should probably decide how we and to do this consistently.

The number depends on the answer to:
"And a question. When annotating protein kinases, is the terminal kinase considered to be a "signal transducer" too? (I'm never sure about this)""
because if the terminal kinase is also a signal transducer, then it is probably all 116 of our protein kinases.......

So for this one, I'd be happy if the name was changed to
signal transducing protein kinase activity
as we annotate our pathways we will need to make sure that other "signal transducing kinases" are under this term. Bear in ming that this will necessitate lots of new terms like
signal transducing protein serine/threonine protein kinase
etc

Bear in ming that this will necessitate lots of new terms like:
signal transducing protein serine/threonine protein kinase

The branch already has:

OK.
We will need to migrate our protein kinases to these terms to collect a "signalling parent"
However Ithe term names seem unnecessarily long.
Could they be shortened from:
signal transducer, downstream of receptor, with serine/threonine kinase activity
Definition	Conveys a signal from an upstream receptor or intracellular signal transducer by catalysis of the reaction: ATP protein serine = ADP + protein serine phosphate, and ATP + protein threonine = ADP + protein threonine phosphate.
GONUTS	GO:0004702 Wiki Page
To
signal transducing serine/threonine kinase activity
Conveys a signal from a receptor or intracellular signal transducer by catalysis of the reaction: ATP protein serine = ADP + protein serine phosphate, and ATP + protein threonine = ADP + protein threonine phosphate.
Reasons

It seems odd to have "downstream of receptor" in the  term name because not ALL signalling protein kinases are downstream of "receptors" they may be downstream of 'sensors' sensing  abnormal events, like the replication checkpoint signalling...
This def would  hold for any signal transducing protein kinase (but presumably a receptor/protein kinase requires 2 independent MF annotations?). If a separate term really is required for a "receptor kinase" it would be a descendant of this term...

What do you think?
Val

Hi Val,
All good points and very timely given current discussions with @thomaspd on MF refactoring.
ST in GO is already broader than signaling from receptors, but as a developmental biologist my instinct when talking about signal transduction is to assume we're talking about signaling downstream of receptors detecting an extracellular signal.  We could divide signal transduction up into
signal transduction:
signal transduction involved in cell communication
signal transduction from intracellular signal  <-- Not sure what to call this, but we clearly have classes that belong under here (e.g. mitochondria to nucleus signaling pathway)
We don't typically capture the regulated_by aspect of signal transducers, but maybe we should - after all, a signal transducer must have an input as well as an output.  For MAPK activity should we encode regulation by phosphorylation in the MF?  @thomaspd - please comment.

This def would hold for any signal transducing protein kinase (but presumably a receptor/protein kinase requires 2 independent MF annotations?). If a separate term really is required for a "receptor kinase" it would be a descendant of this term...

The point of this branch was to exclude receptors.  Refactoring of cell-communication / cell-cell signaling and its relation to ST will help us formalise this (see #13020).

I don't think this split would help. Often we annotate protein kinases which are known to be part of signalling pathways, but we can't be sure if they are downstream of receptors or intracellular signals. The pathway information is still very fragmentary.
We know they are a signal transducer, and we know they are a protein kinase.
So, if you can't remove the "downstream of receptor" part from the term, we would need terms like:
signal transducer, protein kinase activity etc...
However, I do think it would look odd to see all of our protein kinases annotated as:
signal transducer, downstream of receptor, with serine/threonine kinase activity
(even if we do know that they are downstream of a receptor).
Whether a kinase  is downstream of a receptor will only become known once the pathway is worked back to it's root so we will need to constantly change existing annotations  to kinases downstream of receptor/ downstream of intracellular signal  as we get more info (and many seem to be  downstream of both receptors and intracellular signals).
Is this critical? Why is it necessary to  exclude receptor kinases  from signal transducing kinases?
This makes things much more complicated for curators...

I agreed to change the names to signal transducer, protein kinase activity etc in my first comment on this ticket :).  These terms will be part of signal transduction (general class). Sorry if not clear.

Whether a kinase is downstream of a receptor will only become known once the pathway is worked back to it's root so we will need to constantly change existing annotations to kinases downstream of receptor/ downstream of intracellular signal as we get more info (and many seem to be downstream of both receptors and intracellular signals).

In as far as we capture this, we should do so using inference.  That's the plan for LEGO.  Some of the same inference will work with extensions.  We're still working out the details, but it should be enough to extend an annotation to the MF with part_of {insert sig transduction term here}.

@ValWood @dosumis @thomaspd
Is this a process ?

@ValWood @dosumis @thomaspd
Is this a process ?

No

but this is?
https://github.com/geneontology/go-ontology/issues/13250

I  would merge directly with their cognate  kinase term "protein tyrosine kinase activity"
I think it is  confusing too....

OK I can do that too, although the term labels are so confusing that obsoletion could be better ?

I always prefer obsoletion, it's cleaner.
Are there many direct annotations? We haven't used it at PomBase, we only used child terms like SAP kinase activity and MAP kinase activity

GO:0005057 signal transducer activity, downstream of receptor : about 20 EXP
GO:0004716 signal transducer, downstream of receptor, with protein tyrosine kinase activity: 2 EXP
GO:0004702 signal transducer, downstream of receptor, with serine/threonine kinase activity : 7 EXP
GO:0004728 signal transducer, downstream of receptor, with protein tyrosine phosphatase activity 2 EXP
GO:0009400 signal transducer, downstream of receptor, with serine/threonine phosphatase activity
Most have been removed  geneontology/go-annotation#1899
Pascale

@ValWood I'm closing this, the is covered in #14232
Thanks, Pascale


[DO-NOT-MERGE] feat(osio): Introduce new /osio/launch/empty API end-point

A new POST API endpoint /osio/launch/empty is added which take payload same as /osio/launch  endpoint and creates a repository with no content.

Ike Plugins (test-keeper)
Thank you @ravsa for this contribution!

It appears that no tests have been added or updated in this PR.
Automated tests give us confidence in shipping reliable software. Please add some as part of this change.
If you are an admin or the reviewer of this PR and you are sure that no test is needed then you can use the command /ok-without-tests as a comment to make the status green.
For more information please head over to official documentation. You can find there how to configure the plugin - for example exclude certain file types so if PR contains only them it won't be checked.

Also, don't forget to update the swagger.yaml documenting this new endpoint

There are some test failures. See the logs in https://semaphoreci.com/fabric8-launcher/launcher-backend/branches/pull-request-431/builds/10

Thanks!

What is this used for btw? It seems strange to be creating an empty git repository?


Set up redirects

We need to set up redirects as the structure of the new website changed compared to the previous one:

Top-level links:

user_guide -> getting_started
make_project -> contributing
[removed] maintenance -> /

Redirects, e.g. /attractors to /gallery/attractors
Direct notebook links, e.g. /attractors/attractors_panel to /attractors/gallery/attractors_panel

Some useful links:

https://sphinxext-rediraffe.readthedocs.io/en/latest/
https://chrisholdgraf.com/blog/2022/sphinx-redirects-folder/
https://documatt.gitlab.io/sphinx-reredirects/

I don't think I saw this issue appear a year ago, and thus didn't notice "gallery" appear in the URLs. Having "gallery" there complicates the redirect story, and I'm not sure how to address that. E.g. if I start with this highly unwieldy link that's hard to put into a slide, tweet, or document:
https://examples.holoviz.org/gallery/timelapse_microscopy/timelapse_microscopy.html
there are redirects currently working that make this much shorter alias redirect to that page:
examples.holoviz.org/timelapse_microscopy
That's nice and short, but it's highly non-discoverable. Previously, people could just start with the full URL and strip off the filename to get the shorter version, but that's no longer true, as this one does not work:
https://examples.holoviz.org/gallery/timelapse_microscopy
It does work after removing "gallery", but no one would guess that!
Also, the current behavior doesn't seem consistent. E.g. https://examples.holoviz.org/gallery/multichannel_timeseries works, while
https://examples.holoviz.org/multichannel_timeseries does not, which is the opposite of what happens for the microscopy example. Inconsistencies like that make this even less discoverable.
So it's unfortunate that the URLs now have that extra "gallery" bit, but it sounds like it was for an annoying technical reason. My best guess for what to request is just to have them all work, i.e. stripping off the filename should work, stripping out "gallery" should work, but neither should be required. Still, what I'd really want is for the URL bar to show the shortest usable URL, so that people can simply copy and paste it and not have to figure any of this out. No idea how feasible that is.

https://examples.holoviz.org/multichannel_timeseries works for me.

Yeah, that sounds way too complex. Thanks!

https://examples.holoviz.org/multichannel_timeseries works for me.

Weird; that note was from a few days ago. Maybe there's been a build of something since then?  Anyway, great!


Don't publish ReactAndroid to NPM

The ReactAndroid folder contains sources for the android code. We publish the binary to NPM, so doesn't make sense to publish the source. This adds unnecessary 5MB to the download.
cc @bestander

Yeah, android folder contains the .jar with the sources.
Should be sufficient.

@facebook-github-bot shipit

We'll have feedback in 0.24.0-rc

@satya164 @bestander For those who wants to compile from source on master or tinker with RN while developing, ReactAndroid is needed.
Can we not ship this.

@chirag04 For that, you'll usually maintain a forked git repo, right?

Ah, NPM strips this while installing from GIT repo also. @bestander is there a way we could apply this only in releases, but keep this in master?

@satya164 exactly. It's a good idea to remove it only in releases if 5MB is an overhead.
Also: There original commit by @mkonicek : https://github.com/satya164/react-native/commit/403176ae9332fb7c8beac339dd41cbb067f995fd

Ok, I'll stop the build

There is a distinction between -rc and release builds in npm publish CI script.
We could have easily done this change in the script.
But maybe we should not?
If you think about it, 5MB is just 12% of total npm download we do and 1% of compiled node_modules.
For the saved bandwidth we pay:

inconsistency between -rc and -release builds
breaking people who may patch React Native java code in their production systems for whatever reason

@bestander

inconsistency between -rc and -release builds

Why would that happen?

breaking people who may patch React Native java code in their production systems for whatever reason

Won't people who are patching RN usually maintain fork? They have the option of just cloning the repo instead of installing from NPM and patching it. So...
Yesterday it took me over half an hour to finish react-native init. Okay, my internet is a bit slow, but I'd  prefer to trim every bit of fat I can. Both dependencies, and crore.

@bestander fixed

inconsistency between -rc and -release builds
Why would that happen?

Disregard this, I thought you want to leave the code in -rc but strip in releases.

breaking people who may patch React Native java code in their production systems for whatever reason
Won't people who are patching RN usually maintain fork? They have the option of just cloning the repo instead of installing from NPM and patching it. So...

For example, people want to keep using stable releases but need to patch one line in native code for some reason.
They could write an npm plugin that would sed the line and not worry about managing a fork which needs to be updated daily.
Not a great example but these things happen.

Yesterday it took me over half an hour to finish react-native init. Okay, my internet is a bit slow, but I'd prefer to trim every bit of fat I can. Both dependencies, and crore.

That is the problem with npm, for some reason many people had problems yesterday.
npm CLI makes 1400 requests and downloads 40MB when doing react-native init, I think the problem may be in the number of requests then download size.
You would save more if we get rid of yeoman with an ad-hoc bootstrapping script. :)

They could write an npm plugin that would sed the line and not worry about managing a fork which needs to be updated daily.

Can't they just clone the relevant stable branch?

npm CLI makes 1400 requests and downloads 40MB when doing react-native init, I think the problem may be in the number of requests then download size.

Yeah, sad fact :(

You would save more if we get rid of yeoman with an ad-hoc bootstrapping script. :)

I can try working on that.

@mkonicek do you have any info?
Looks like you've added ReactAndroid to npm package.

What's the performance impact of distributing 5MB over npm? I think it could be low impact because npm sends packages as gzipped tarballs, so the Java source is sent with the same HTTP request for the rest of the react-native package. This is much better than having 100s of small packages that add up to 5MB. Also, is the 5MB statistic for gzipped or non-gzipped source code? That would make a big difference too.

For example, people want to keep using stable releases but need to patch one line in native code for some reason.
I am doing that currently to support the binary data in web socket ( https://github.com/facebook/react-native/pull/6327)

@sreesharp What's your process of doing it?
If you have script which patches things under node_modules at runtime, its a pretty fragile thing, and can break your build/fail at any point of time we change the code. I don't think we can support the use case even if we wanted to. But even then, you still have the option to point to git://github.com/facebook/react-native.git#0.22-stable in your package.json instead of ^0.22.0
@ide I think even if it's low impact, its low-effort, so no reason not to do it, unless there's a convincing use case which cannot be fulfilled if we remove it.

I zipped up ReactAndroid (tar -czf ReactAndroid.tar.gz ReactAndroid) and the output file was 0.47MB. Compression of the entire npm package is probably even better by a small amount since the compression tables can optimize across the Java and JavaScript code.
This is the perf improvement of getting rid of yeoman BTW (npm 3.8.3 on Node 5.9.1, node_modules fully cached):
$ git clean -dfx
$ time npm install
real	1m28.028s
user	0m41.213s
sys	0m11.073s

$ git clean -dfx
Removing node_modules/
$ emacs package.json
# Removed yeoman-environment and yeoman-generator

$ time npm install
real	1m15.933s
user	0m35.906s
sys	0m9.575s

@ide Interesting. I guess it's negligible in that case. I'll work on getting rid of yoman.
BTW is your npm install really 1 min 15 sec? I'm so jealous.

@satya164 That's with a completely warm npm cache. And this is my ping time, which is about as long as it should take npm to return an HTTP 304 response code:
$ ping registry.npmjs.org
PING a.sni.fastly.net (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: icmp_seq=0 ttl=58 time=13.586 ms
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=58 time=13.341 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=58 time=13.430 ms
64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=58 time=14.412 ms
64 bytes from <IP_ADDRESS>: icmp_seq=4 ttl=58 time=14.907 ms
64 bytes from <IP_ADDRESS>: icmp_seq=5 ttl=58 time=19.775 ms
64 bytes from <IP_ADDRESS>: icmp_seq=6 ttl=58 time=13.187 ms
64 bytes from <IP_ADDRESS>: icmp_seq=7 ttl=58 time=13.391 ms
64 bytes from <IP_ADDRESS>: icmp_seq=8 ttl=58 time=13.301 ms
64 bytes from <IP_ADDRESS>: icmp_seq=9 ttl=58 time=21.626 ms
64 bytes from <IP_ADDRESS>: icmp_seq=10 ttl=58 time=13.763 ms
^C
--- a.sni.fastly.net ping statistics ---
11 packets transmitted, 11 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 13.187/14.974/21.626/2.773 ms

These are some more npm stats:
npm 3 with progress bar turned off:
real	1m23.517s
user	0m40.852s
sys	0m10.450s

npm 2:
real	1m5.661s
user	1m6.900s
sys	0m26.771s

So npm 2 is faster for installing, but you'll spend more time in the packager since Babel will be so slow with extra dependencies. I'd go with npm 3 at this point.
And npm 3 with cold cache (npm cache clean):
real	2m39.964s
user	0m44.619s
sys	0m12.177s

@satya164 I have the forked to private Github, my custom changes are there in private repo. Once in a while I merge the latest from the public repo. So its manual fix and not automated patch. My build server just uses the private repo to build ReactNative.


The Union mount needs to implement the optional Methods Move, Copy, DirMove etc.

Issue as references here:
https://forum.rclone.org/t/plex-gdrive-using-union-mount/7024/22?u=nimbuz
Example of error:
"2018/10/02 10:08:22 ERROR : Bull (2016)/Season 3/Bull.(2016).S03E02.Jury.Duty.HDTV-720p.KILLERS.mkv.partial~: Dir.Rename error: Fs “union root ‘’” can’t rename files (no server side Move or Copy)"
Tentative solution: "The Union mount needs to implement the optional Methods Move, Copy, DirMove etc. It might be better to embed the fs for this"

Here is an initial attempt at this
https://beta.rclone.org/branch/v1.43-130-gd90eccd6-fix-2619-union-beta/ (uploaded in 15-30 mins)
can you have a go and see if it fixes that problem?

This fix only has software for windows and osx. I'm running linux, so unfortunately I can't test it with those packages, sorry!

@nimbuz the build failed, I've kicked it and the linux binaries are there now - can you have a test please?
Thanks

The union remote type doesn't seem to be included in that beta branch. I will need one that includes the fix and the new union feature.

I tried to install your new branch, however I have to go through the hassle of making it a plugin to fit into unraid (https://github.com/nimbuz/rclone-unraid/blob/beta/plugin/rclone.plg).
I think it works, however I'm unable to create a union mount through the config. Are you seeing the same?

I tried my best at a plugin, and I think I made it work. However I'm unable to create a union remote through the config. You seeing the same?

@nimbuz - sorry I'm not an unraid user, so I'm not sure what is going on :-(  The beta shouldn't have changed the union backend config at all.

@ncw It seems wierd. Windows does the same thing. This is what I'm getting when trying to make a remote on windows. Are you able to create a union remote?

@ncw Unfortunately I won't be able to test it on my system, before the fix is pushed to the main beta branch. However the implementation of --move should fix the issue. I tried installing the fix on windows, and I'm seeing the union remote now, so it seems to be working.
I won't be able to test it though, sorry.

OK, I've merged that to master and it will be in the latest beta in 15-30 mins.

I’ve been running the beta for a few days now, and it’s running wonderfully. Good job on it!
The way it copies to the union folder, and then afterwards moves it to the correct local folder seems a bit slow however (I assume that’s what it’s doing), but it’s obviously not too big of an issue with fast hard drives.


Translation language setting lost on state change

Ahoi. I am switching the translation in a service and load the json file manually like thus:

self.gettextCatalog.setCurrentLanguage(token);
self.gettextCatalog.loadRemote("/l10n/frontend." + token + ".json");

This kinda works, but once i trigger a state change and go to another part of the app, the translations are not used anymore unless i again select a language. Is there any way to overcome this?

Oh. MY. I found my error. Still had a remnant "import translate from 'angular-translate';" in my main.js which very subtly messed with things :-D


404 returned

Hi @rugantio , thanks for this!
I have tried to use it now but it is not working:

It returns a 404 as it tries to go to mbasic.facebook.com/login/pageid.
Looks like there is a problem similar to what you were mentioning in #2 : I logged in with my browser but didn't solve it.
Am I doing something wrong or there is something to fix in the login process?
I also tried to change, in line 73 of fbcrawl.py, the href value skipping "/login/", but I get another error:

Executing on Linux instead of windows doesn't raise this problem.


Can anyone train coco from scratch?

I have train the d0 on coco 2 weeks, whatever I change the learning rate, or other parameters, the val cl loss is around 1.0 but the map is 0
Classification loss: 1.15289. Regression loss: 0.11328. Total loss: 1.26617
Average Precision  (AP) @[ IoU=0.50:0.95 | area=   all | maxDets=100 ] = 0.000
Average Precision  (AP) @[ IoU=0.50      | area=   all | maxDets=100 ] = 0.000
Average Precision  (AP) @[ IoU=0.75      | area=   all | maxDets=100 ] = 0.000
Average Precision  (AP) @[ IoU=0.50:0.95 | area= small | maxDets=100 ] = 0.000
Average Precision  (AP) @[ IoU=0.50:0.95 | area=medium | maxDets=100 ] = 0.000
Average Precision  (AP) @[ IoU=0.50:0.95 | area= large | maxDets=100 ] = 0.000
Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=  1 ] = 0.000
Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets= 10 ] = 0.000
Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=100 ] = 0.001
Average Recall     (AR) @[ IoU=0.50:0.95 | area= small | maxDets=100 ] = 0.000
Average Recall     (AR) @[ IoU=0.50:0.95 | area=medium | maxDets=100 ] = 0.001
Average Recall     (AR) @[ IoU=0.50:0.95 | area= large | maxDets=100 ] = 0.003

I also have this problem. Have you solved it? Ask for help.


Unexpected behavior with template literals

https://github.com/Glavin001/atom-beautify/issues/1157

@qwemaze was nice enough to file full issues for the this: #1030,  #1031.  Closing this.


ChartBar empty when last 2 values are 0

Hey PrzemyslawKlys,
i think i might had found a new bug with ChartBar
if the last 2 bars values are 0, none of the bars will be drawn.
so in the example below, it will work as expected, but if you change the value to 2,3,0,0 == none of the bars will be drawn.
  New-HTML   -TitleText "title" -AddComment  -Online -FilePath "c:\temp\tt.html"  {
                                    New-HTMLChart  -TitleAlignment center -TitleFontSize 12 -Height 200 {
                                        New-ChartBarOptions -DataLabelsColor black -Vertical
                                        New-ChartLegend -Name "a","b", "c","d" # , "%"
                                        New-ChartBar -Name "name" -Value 2,3,4,5
                                        IF ($_.Name -like "GHW_Level1"){Write-Host "            ...GHW! |$($_.Name )| $( $_.Reader)  $( $_.Candidate)  $($_.Contributor)  $($_.Publisher)" -ForegroundColor Yellow}
                                        sleep 1

                                    }
    }-ShowHTML

Does it behave the same on preview?

what do you mean on "preview" ?

It's now fixed. You can test it using Install-Module PSWriteHTML -AllowPrerelease. Production version will be related later this month when I get to fix some outstanding issues.

i rather wait for the official release rather than use a pre-release but man you are a rock star!
thanks for the quick solution, and i have a bunch of fixes that i wait for now, so hope to see the next release out soon :)
Tomer.


Bind updates with @update:value in RegistryMirrors.vue

Summary
This resolves a simple data binding issue in RegistryMirrors.vue; data binding for custom components should be using @update:value instead of @input.
Fixes #12524

Occurred changes and/or fixed issues

Use @update:value instead of @input for ArrayListGrouped component

Technical notes summary

ArrayListGrouped emits an update:value event instead of input, this is the root cause behind the issue

Areas or cases that should be tested

RKE2 Cluster Configuration: Registries

Areas which could experience regressions

NA

Checklist

[x] The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
[x] The PR has a Milestone
[x] The PR template has been filled out
[x] The PR has been self reviewed
[x] The PR has a reviewer assigned
[x] The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
[x] The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes

This will require an e2e test. I'm planning on following up in a separate PR to write those so that this can be merged and resolved in the 2.10 timeline.

/backport v2.10.0 release-2.10

@rak-phillip i'm confused why this isn't an issue in lots of over @input handles.
Looking at https://github.com/rancher/dashboard/blob/master/shell/edit/workload/VolumeClaimTemplate.vue#L102-L106
            <PersistentVolumeClaim
              v-if="props.row.value.metadata"
              :value="props.row.value"
              :mode="mode"
              @input="updatePVC(props.row.value)"
            />

and
https://github.com/rancher/dashboard/blob/master/shell/edit/workload/storage/persistentVolumeClaim/persistentvolumeclaim.vue#L161-L166
        <LabeledInput
          v-model:value="value.metadata.name"
          :mode="mode"
          :label="t('persistentVolumeClaim.name')"
          :required="true"
          @update:value="$emit('update:value', value)"
        />

i'd expect this to be also broken, but changes to the statefulsets --> create --> pod tab --> Volume Claim Templates tab --> pvc name field does trigger updatePVC.
At the moment concerned some of the 55 usages of @input could still be broken.
I spotted at least some typing errors for shell/edit/service.vue UnitInput that handles value.spec.sessionAffinityConfig.clientIP.timeoutSeconds (assigns an event rather than value)

@richard-cox the implementation for shell/edit/persistentvolumeclaim.vue explicitly emits and input event:
https://github.com/rancher/dashboard/blob/024f92c173efe278480ff265d338230cfe12232f/shell/edit/persistentvolumeclaim.vue#L24
https://github.com/rancher/dashboard/blob/024f92c173efe278480ff265d338230cfe12232f/shell/edit/persistentvolumeclaim.vue#L242
For consistency and to properly implement v-model in Vue3^1, we would want to update the emitted input event to update:value.

I created issue #12543 to address the usage of input events in custom components.

@rak-phillip https://github.com/rancher/dashboard/pull/12527#issuecomment-2461867271 covers the events between VolumeClaimComponent and an inner component that's called PersistenVolumeClaim (rather than the owning edit component also called PersistenVolumeClaim). That one contains  https://github.com/rancher/dashboard/blob/024f92c173efe278480ff265d338230cfe12232f/shell/edit/workload/storage/persistentVolumeClaim/persistentvolumeclaim.vue#L14

@richard-cox thanks for setting it straight, I see the issue with dashboard/shell/edit/workload/storage/persistentVolumeClaim/persistentvolumeclaim.vue and any other consumer that might be listening for an input event. It looks like native events like input are propagating up through the component tree; I've been able to create a minimal repro to demonstrate
https://play.vuejs.org/#eNqNVFFvmzAQ/iuWNYlEykDd9pQl0bqplTJt7bRW24tfGFwSd2As29BIiP/esw0JNCTqE+buu893nz+7ptdShlUJdE4XOlFcGqLBlHLFBM9loQypiYINachGFTkJEBocUg9FDt8KXAsQpgWE0SBquYPPTDCRFEIjKOYZWVrKSRBMewmpuDA/Qet4CwiYVHFWwpQsV6Rmgri60MUw6b5Y2xzLRWFuL1L/iTOejhC3hWPci8grglrgj4FcZrEB/CNkMRzdhgj5woUszZLR/iyMtslSplg9z4sUMmymhA7oOvOwyG2F9CmvSPWebxBjJ2fU7YqJ3YfV7fX6xyLChQ/VtRe1wY4REGHpCEs75oDo7v6RnJJ1Sg75FlFvfjqjRqO2G74Nn3Qh0DxOS0YTlIRnoO6l4ag9o3Ovss3FWVY8f3cxo0qYdfFkB8n/kfiT3tsYo78UaFAVSnnImVhtwfj0zcMd7HF9SKLEZYboC8nfoIustD162NdSpNh2D+e6XTufc7F91Dd7A0J3Q9lGLbJxeEbR5dYN50Y/tvsx/OTq0GCo4toa5q+KpQQ1egsvWdAfjDtMZ7yj/ybe3+8g52YSnBgvmBEIfUve9tPWFucO++RGn38t+hMdXoTXY9oH4Y2T7a76Nr3qwv9Utxps6GNnLtsbVEEhWg5Uvs98QZ7mBU0lv+c=
In this example, we can stop the input event from propagating up through the component tree if we add the stop modifier
    <input @input.stop="(e) => $emit('update:modelValue', e.target.value)">


Choose the default admin password at initialization

After some research I think it's not possible to choose the default admin password (123) at database initialization. Should it be possible to have a parameter for this value ?
For example an environment variable filled in the docker-compose.

@viico it's possible. See Data Initialization docs: https://casdoor.org/docs/deployment/data-initialization

try this
https://gofile.io/d/yMHabA
select the desired compiler in the installer


refactor(html-theme): Extract getSearchIndex into multiple smaller methods

This increases the code readability.

Closes #18

@fussel178 This should be fixed, now. Thanks for pointing it out :)

@fussel178 This should be fixed, now. Thanks for pointing it out :)


[Sample]Remove old {Face, DEP, SP} samples.

BUG=none

@halton @huningxin @jondong @DonnaWuDongxia PTAL, Thanks~

LGTM and merging.


Web platform not working in 6.x.x

I followed everything in https://inappwebview.dev/docs/intro
The Android app works fine
but as mentioned to make the WebPlatform work i did this:
<head>
  <!-- ... -->
    <script type="application/javascript" src="/assets/packages/flutter_inappwebview/assets/web/web_support.js" defer></script>
  <!-- ... -->
</head>

but nothing happens... when I put the above line in build/web/index.html... nothing happens, but I get stuff in the console that says:
_

TypeError: Cannot set properties of undefined (setting 'nativeCommunication')
at FlutterInAppWebViewWebPlatform.registerWith (http://localhost:58821/packages/flutter_inappwebview/src/web/web_platform.dart.lib.js:46:60)
at Object.registerPlugins (http://localhost:58821/packages/inappwebview_pkg/generated_plugin_registrant.dart.lib.js:14:49)
at http://localhost:58821/web_entrypoint.dart.lib.js:39:39
at Object._checkAndCall (http://localhost:58821/dart_sdk.js:5279:16)
at Object.dcall (http://localhost:58821/dart_sdk.js:5284:17)
at http://localhost:58821/dart_sdk.js:140287:18
at Generator.next ()
at runBody (http://localhost:58821/dart_sdk.js:40660:34)
at Object._async [as async] (http://localhost:58821/dart_sdk.js:40691:7)
at _engine.AppBootstrap.new. (http://localhost:58821/dart_sdk.js:140285:67)
at Object._checkAndCall (http://localhost:58821/dart_sdk.js:5279:16)
at Object.callMethod (http://localhost:58821/dart_sdk.js:5322:17)
at Object.dsend (http://localhost:58821/dart_sdk.js:5325:17)
at _engine.AppBootstrap.new. (http://localhost:58821/dart_sdk.js:140636:22)
at Generator.next ()
at runBody (http://localhost:58821/dart_sdk.js:40660:34)
at Object._async [as async] (http://localhost:58821/dart_sdk.js:40691:7)
at http://localhost:58821/dart_sdk.js:140635:215
at Object._checkAndCall (http://localhost:58821/dart_sdk.js:5279:16)
at Object.dcall (http://localhost:58821/dart_sdk.js:5284:17)
at ret (http://localhost:58821/dart_sdk.js:62210:21)
at new Promise ()
at http://localhost:58821/dart_sdk.js:140635:119
at Object._checkAndCall (http://localhost:58821/dart_sdk.js:5279:16)
at Object.dcall (http://localhost:58821/dart_sdk.js:5284:17)
at Object.ret [as runApp] (http://localhost:58821/dart_sdk.js:62210:21)
at http://localhost:58821/:53:26

Environment

Technology
Version

Flutter version     (sdk: ">=2.17.0 <3.0.0")

Plugin version     flutter_inappwebview: ^6.0.0-beta.7

Android version

iOS version

Xcode version

Is there a special way to run the WebPlatform?
All I need is in my Website(ie being developed by flutter web) one of the widgets on the screen will be an InAppWebView displaying information from another site. Is there something I am missing???
Thanks,
YOhan

Yes this is a real problem. I have looked at the code on StackOverflow... it is wrong and conflicts with the code in your example repo. There is not a single place where you have pasted code that shows how to simply have an InAppWebView inside a flutter web page. Will urge you to do so, as you have claimed on numerous occasions on stackOverflow that this widget does work as claimed!
Will await your reply & help. Thanks

Version 6.x.x requires Flutter 3.
From your environment, you are using Flutter < 3.
However, here is a very basic code example that it is working:
import 'dart:async';
import 'package:flutter/foundation.dart';
import 'package:flutter/material.dart';
import 'package:flutter_inappwebview/flutter_inappwebview.dart';

Future main() async {
  WidgetsFlutterBinding.ensureInitialized();
  if (!kIsWeb && defaultTargetPlatform == TargetPlatform.android) {
    await InAppWebViewController.setWebContentsDebuggingEnabled(kDebugMode);
  }
  runApp(const MaterialApp(
      home: MyApp()
  ));
}

class MyApp extends StatefulWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  _MyAppState createState() => _MyAppState();
}

class _MyAppState extends State<MyApp> {

  final GlobalKey webViewKey = GlobalKey();

  InAppWebViewController? webViewController;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
        appBar: AppBar(title: const Text("InAppWebView TEST")),
        body: SafeArea(
            child: Column(children: <Widget>[
              Expanded(
                child: Stack(
                  children: [
                    InAppWebView(
                      key: webViewKey,
                      initialUrlRequest: URLRequest(
                          url: Uri.parse('https://flutter.dev')),
                      onWebViewCreated: (controller) {
                        webViewController = controller;
                      },
                    ),
                  ],
                ),
              ),
            ]))
    );
  }
}

index.html code:
<!DOCTYPE html>
<html>
<head>
  <!--
    If you are serving your web app in a path other than the root, change the
    href value below to reflect the base path you are serving from.

    The path provided below has to start and end with a slash "/" in order for
    it to work correctly.

    For more details:
    * https://developer.mozilla.org/en-US/docs/Web/HTML/Element/base

    This is a placeholder for base href that will be replaced by the value of
    the `--base-href` argument provided to `flutter build`.
  -->
  <base href="$FLUTTER_BASE_HREF">

  <meta charset="UTF-8">
  <meta content="IE=Edge" http-equiv="X-UA-Compatible">
  <meta name="description" content="A new Flutter project.">

  <!-- iOS meta tags & icons -->
  <meta name="apple-mobile-web-app-capable" content="yes">
  <meta name="apple-mobile-web-app-status-bar-style" content="black">
  <meta name="apple-mobile-web-app-title" content="flutter_inappwebview_test">
  <link rel="apple-touch-icon" href="icons/Icon-192.png">

  <!-- Favicon -->
  <link rel="icon" type="image/png" href="favicon.png"/>

  <title>flutter_inappwebview_test</title>
  <link rel="manifest" href="manifest.json">

  <script type="application/javascript" src="/assets/packages/flutter_inappwebview/assets/web/web_support.js" defer></script>

  <script>
    // The value below is injected by flutter build, do not touch.
    var serviceWorkerVersion = null;
  </script>
  <!-- This script adds the flutter initialization JS code -->
  <script src="flutter.js" defer></script>
</head>
<body>
  <script>
    window.addEventListener('load', function(ev) {
      // Download main.dart.js
      _flutter.loader.loadEntrypoint({
        serviceWorker: {
          serviceWorkerVersion: serviceWorkerVersion,
        }
      }).then(function(engineInitializer) {
        return engineInitializer.initializeEngine();
      }).then(function(appRunner) {
        return appRunner.runApp();
      });
    });
  </script>
</body>
</html>

Screenshot:

Hi @pichillilorenzo ,
This was perfect.
I thank you for your time and greatly appreciate you outlining the particulars.
it worked perfectly there were no errors.
changed the environment to sdk: ">=2.17.0 <3.3.5" in the .yaml
I ran a flutter build web...
then edited the index.html like you said
hosted it on a server... and BOOM!... just as you said.
Thanks,
And I will go back to those StackOverFlow resources and post the new code you helped me out with.
YOhan

@YohanWadia no problem! You are welcome!

@pichillilorenzo I guess that to use the version 6 then we have to switch to the dev branch as the stable branch max sdk is 2.8.x right?

@vinnytwice no, you should install it from pub.dev
The latest available is 6.0.0-beta.22

@vinnytwice check the requirements online:

Version 6: https://inappwebview.dev/docs/intro/#requirements
Version 5: https://inappwebview.dev/docs/5.x.x/intro

I'm using the 6.0.0-beta.22, and I'm on flutter channel master which Flutter 3.3.10/ Dart 2.18.6 .
@pichillilorenzo I changed the pubspec.yaml sdk: ">=2.17.0 <3.3.5" and it should work right?
Unfortunately it  works only on Android, I guess it has to with the screen I use the plugin in.
Should I open a new issue?

@pichillilorenzo  I opened an issue so to show all the steps.
Many thanks


we need an mxnet.symbol.run   (bind + forward)

We need an mxnet.symbol.run function. This would combine bind and forward.
Say I want to run
import mxnet.symbol as S
A_real = # ... some nonsense
B_real = # ...  some other nonsense
a = S.Variable()
b = S.Variable()
c = S.dot(a,b)

Now, if I want to execute c on A_Real and B_real I need to run
d = c.bind({...})
e = d.forward()

Instead, I we ought to be able to run
f = c.run({...})

This would combine the functionality of bind and forward. It makes a lot of sense, especially in the interactive interpreter where someone is trying out lots of ideas and needs to be able to see what pops out of various expressions without writing too much code. This makes sense in the common case where someone has no need to keep d lying around.
For bugs or installation issues, please provide the following information.
The more information you provide, the more likely people will be able to help you.
Environment info
Operating System:
Compiler:
Package used (Python/R/Scala/Julia):
MXNet version:
Or if installed from source:
MXNet commit hash (git rev-parse HEAD):
If you are using python package, please provide
Python version and distribution:
If you are using R package, please provide
R sessionInfo():
Error Message:
Please paste the full error message, including stack trace.
Minimum reproducible example
if you are using your own code, please provide a short script that reproduces the error.
Steps to reproduce
or if you are running standard examples, please provide the commands you have run that lead to the error.

What have you tried to solve it?

Generally good idea. Need to make it clear that this is slow though

This is equal to eval in TF. I think it is not hurt.
On Mon, Mar 6, 2017 at 19:46 Eric Junyuan Xie<EMAIL_ADDRESS>wrote:

Generally good idea. Need to make it clear that this is slow though
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dmlc/mxnet/issues/5280#issuecomment-284613516, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABM13nrKoD4Lyt3v3qKR0ZaWu-QOTuAYks5rjNMBgaJpZM4MU-K7
.

--
Sent from mobile phone

This issue is closed due to lack of activity in the last 90 days. Feel free to ping me to reopen if this is still an active issue. Thanks!


fix: update argent mobile rpc methods

Checking further I think this might break Wallet Connect for mobile (at least iOS) as we are using the starknet names:
https://github.com/argentlabs/ios/blob/cfe88efebc47f18824b3d0e4c5c7781f3dab77a3/Modules/WalletConnectFeature/Sources/Provider/Requests/WalletConnectRequestHandlerV2.swift#L174-L183
https://github.com/argentlabs/ios/blob/cfe88efebc47f18824b3d0e4c5c7781f3dab77a3/Modules/WalletConnectFeature/Sources/Provider/Requests/Starknet/StarknetRequestHandler.swift#L30-L61

@mluisbrown let's keep this pr open until we are all on the same page


Rebuild for aarch64 and ppc64le

Fixes #9

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge/arm-arch @conda-forge/atk This is ready for review/merge.

LGTM, thanks @xhochy


Make sure reflected properties are integers. Partial fix for #1225

In HTML5 target reflected source#width and source#height can be floats, which causes type mismatch for width and height temporary BitmapData, causing problems with ColorTransform.
More info in https://github.com/openfl/openfl/issues/1225

Thanks.


install launch file

so that the user can call roslaunch recordit record.launch from the installed package

@jschleicher thank you very much for this fix! I will do another release within the next days :)


6.3.3 beta InAppBillingSecurity is missing

I have the same issue as [this] (https://github.com/jamesmontemagno/InAppBillingPlugin/issues/322) but at this point the code seems to actually have been removed. This is what I see in InAppBillingImplementation:

What is the intended way to Verify purchases on Android now?

Currently I've copied the source that was removed into my code to attempt to verify in the way that was supported before... for some reason it is failing the "if (!sign.Verify(Android.Util.Base64.Decode(signature, 0)))" check though. I've verified that my public key is correct, I am passing purchase.OriginalJson for the signedData and puchase.Signature for the signature. Any ideas why this would not work?

Yeah, i have removed all of that and verifying best practices should be done via Google recommendations which is calling their API from your server.
I no longer use this code at all in my projects


Fix Monaco selection ranges conversion

LSP represents an ancestry of selection ranges using the parent property. Monaco editor represents this using an array of selection ranges. This is why one LSP selection range represents an array of Monaco editor selection ranges. It’s not needed to call getSelectionRanges multiple times.

LGTM, thanks!


mail configuration without username / password

seme times you don't need to configure the SMTP server with username nor password in the class it.smartcommunitylab.aac.utils.MailService always set them
I suggest to change it like that:
public void init() throws IOException {
    mailSender.setHost(mailHost);
    mailSender.setPort(mailPort);
    mailSender.setProtocol(mailProtocol);
    if(mailPwd==null || mailPwd.trim().compareTo("")==0) {
    	logger.trace("SMTP password is blank, username and password are not set");
    } else {
    	logger.trace("SMTP password is not blank, setting username and password");
        mailSender.setPassword(mailPwd);
        mailSender.setUsername(mailUser);
    }

    Properties props = new Properties();
    props.load(mailProps.getInputStream());
    mailSender.setJavaMailProperties(props);

}

looks good. Please make a pull request, from 4.x

closed with #305