Node.js tool installer - 7zr.exe failed with return code: 2

Required Information
Question, Bug, or Feature?
Type: Bug
Enter Task Name: Node.js tool installer (v0)
Environment

Server - Azure Pipelines

Agent - Hosted

Issue Description
Using the Node.js tool installer task to install Node 8.9.2 and getting an error at the beginning when trying to open the archive. After retrying the build that has this task, this task works sometimes. The build that uses this task and this specific task have not been modified in the build definition and we have not seen this issue before. I did see that this task was recently changed about 9 days ago (according to the commit history).
Task logs
##[section]Starting: Use Node 8.9.2
==============================================================================
Task         : Node.js tool installer
Description  : Finds or downloads and caches the specified version spec of Node.js and adds it to the PATH
Version      : 0.153.1
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/tool/node-js
==============================================================================
Downloading: https://nodejs.org/dist/v8.9.2/node-v8.9.2-win-x64.7z
Extracting archive
[command]d:\a\_tasks\NodeTool_31c75bbb-bcdf-4706-8d7c-4da6a1959bc2\0.153.1\7zr.exe x -bb1 -bd -sccUTF-8 d:\a\_temp\c84e3231-3e9b-4d3d-86e4-21481127e009

7-Zip (r) 18.05 (x86) : Igor Pavlov : Public domain : 2018-04-30

Scanning the drive for archives:
1 file, 2195200 bytes (2144 KiB)

Extracting archive: d:\a\_temp\c84e3231-3e9b-4d3d-86e4-21481127e009
ERROR: d:\a\_temp\c84e3231-3e9b-4d3d-86e4-21481127e009
Can not open the file as archive

Can't open as archive: 1
Files: 0
Size:       0
Compressed: 0
##[error]d:\a\_tasks\NodeTool_31c75bbb-bcdf-4706-8d7c-4da6a1959bc2\0.153.1\7zr.exe failed with return code: 2
##[section]Finishing: Use Node 8.9.2

Troubleshooting
Error logs
d:\a\_tasks\NodeTool_31c75bbb-bcdf-4706-8d7c-4da6a1959bc2\0.153.1\7zr.exe failed with return code: 2

The same thing is happening to us for Node v12.6.0.

Is this new today? Node is having issues on their end, I strongly suspect that's what this is from.

Issue here - https://github.com/nodejs/build/issues/1993
There's unfortunately not anything we can do on our end. I'd recommend retrying builds (I know its annoying, I'm equally annoyed 😅). If you use a private agent, it will cache the version of node you're using, alternately you can use one of our cached versions of node on our hosted image if you're ok loosening your version requirements (aka specify version: 8.x instead of version 8.9.2
Also, note that the changes you reference haven't been deployed yet, so that's a red herring

Thanks @damccorm ! That makes sense. We will close this issue.

Starting happen to us today, did anything change?

Starting happen to us today, did anything change?

Seeing the same issue today.

Nothing changed on our end - looks like another node issue - https://github.com/nodejs/build/issues/2263

same issue 4 years later


Feature request: Checking type hint of fields against Doctrine metadata

phpstan-doctrine could check if a field's typehint matches Doctrine's metadata.
In the following example, the plugin could emit a warning telling that int does not match string:
/**
 * @var int
 *
 * @Column(type="string")
 */
 private $var;

In the following examples, the plugin could emit a warning telling that the field is nullable:
/**
 * @var int // Should be nullable
 *
 * @Column(type="integer", nullable=true)
 */
 private $var;

/**
 * @var Foo // Should be nullable
 *
 * @OneToOne(targetEntity="Foo")

We have exactly this in our company, I might be able to release it publicly.

It'd be cool to have it a part of phpstan-doctrine as rules.neon.

Problem with this is it would most likely require to have doctrine in composer.json as a require dependency, so I'm thinking a separate package instead? Thoughts, @ondrejmirtes?

This should now be possible in a nice way thanks to #49.

Basic version for @ORM\Column implemented in #74 :)

We consider this done :) #75 #76 Please test the hell out of it :)

Awesome ! Thanks @lookyman


chore(main): release sioyek 1.15.5

:robot: I have created a release beep boop
1.15.5 (2024-10-08)
Miscellaneous

main: release fish 1.16.3 (#124) (5799516)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

sioyek-v1.15.5
:sunflower:


login returns Bad Request

Hello, I wanted to create a selfbot, but I get this error when I attempt to log in using email and password:
(node:4400) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Bad Request

The code is basically:
var Discord = require("discord.js");
var api = new Discord.Client();
api.login('<email>', '<password>');

After using catch looks like it "detected a new login location", so that's why it wouldn't let me in, my bad

How did you end up resolving this? im having the same issue

@CornerOfTheOval I used tokens instead of username/password, because using tokens bypasses the location detector. You can get the token of an user account by logging in through the web client, then putting javascript:prompt("", localStorage.token) into the address bar

@CornerOfTheOval @ErmanSayin just for the future, we are removing the ability for the lib to login using an email and password, and only allowing tokens (see #963)


feat(react): add experimental wrap to remove unnecessary hocs

fix #269
Overview

I added wrap function as experimental to reduce all repetition of hocs implementation.
Library size has been reduced by 12%(2,114 bytes) than before
AS-IS dist/index.cjs
18,377 bytes (20KB on disk)

TO-BE dist/index.cjs if maintain wrap and hocs
16,263 bytes (16KB on disk)

TO-BE dist/index.cjs if maintain only wrap and remove hocs
15,117 bytes (16KB on disk)

I want to deprecate all hocs
In v1, I hope to add the wrap function as a public API and keep all hocs marked as deprecated, and in v2, I hope to remove all hocs and provide only the wrap function.
Why want to deprecate all hocs

To reduce library size more
User don't have to know withSuspense, withSuspense.CSROnly, withErrorBoudnary, withAsyncBoundary, withAsyncBoundary.CSROnly, withErrorBoundaryGroup, withDelay. just have to know wrap and existing components. (number of public apis, 15(with hocs) -> 11(without hocs))
wrap function allows us to place related code in a more relevant location. We can also create a function wrapped with wrap to reuse it because calling wrap will make hoc. (Interface refers to the connect function of react-redux.)

PR Checklist

[x] I did below actions if need

I read the Contributing Guide
I added documents and tests.

I'm considering about wrap's another alternative interface different with this Pull Request like below too. @minsoo-web @okinawaa
import { ErrorBoundary, ErrorBoundaryGroup, Suspense, useErrorBoundary, wrap } from '@suspensive/react'
import { UseSuspenseQuery } from '~/components'
import { api } from '~/utils'

const logError = (error: Error) => console.error(error)

export default wrap(ErrorBoundaryGroup, { blockOutside: false })
  .wrap(ErrorBoundary, { fallback: (props) => <>{props.error.message}</>, onError: logError })
  .wrap(Suspense.CSROnly, { fallback: <>loading...</> })
  .on<{ x: string }>((props) => {
    const errorBoundary = useErrorBoundary()

    return (
      <>
        <button onClick={() => errorBoundary.setError(new Error('trigger error by useErrorBoundary().setError'))}>
          trigger error by useErrorBoundary().setError
        </button>
        <UseSuspenseQuery queryKey={['with', 1] as const} queryFn={() => api.delay(200, { percentage: 50 })} />
      </>
    )
  })

I'm considering about wrap's another alternative interface different with this Pull Request like below too. @minsoo-web @okinawaa
I think this builder pattern have good point can make users don't have to make wrap functions is nested
import { ErrorBoundary, ErrorBoundaryGroup, Suspense, useErrorBoundary, wrap } from '@suspensive/react'
import { UseSuspenseQuery } from '~/components'
import { api } from '~/utils'

const logError = (error: Error) => console.error(error)

export default wrap(ErrorBoundaryGroup, { blockOutside: false })
  .wrap(ErrorBoundary, { fallback: (props) => <>{props.error.message}</>, onError: logError })
  .wrap(Suspense.CSROnly, { fallback: <>loading...</> })
  .on<{ x: string }>((props) => {
    const errorBoundary = useErrorBoundary()

    return (
      <>
        <button onClick={() => errorBoundary.setError(new Error('trigger error by useErrorBoundary().setError'))}>
          trigger error by useErrorBoundary().setError
        </button>
        <UseSuspenseQuery queryKey={['with', 1] as const} queryFn={() => api.delay(200, { percentage: 50 })} />
      </>
    )
  })

then this is way also okay
const wrapErrorBoundary = wrap(ErrorBoundary, { fallback: (props) => <>{props.error.message}</>, onError: logError })
const Page = wrapErrorBoundary.on((props) => {
    const errorBoundary = useErrorBoundary()

    return (
      <>
        <button onClick={() => errorBoundary.setError(new Error('trigger error by useErrorBoundary().setError'))}>
          trigger error by useErrorBoundary().setError
        </button>
        <UseSuspenseQuery queryKey={['with', 1] as const} queryFn={() => api.delay(200, { percentage: 50 })} />
      </>
    )
  })

I think it's a really good dx. In fact, it's a functional type, so I think giving a pipe-like feeling can be a better experience for the developer.
On the other hand, I'm worried that it might give me a callback hell experience like the case where promise was used consecutively, such as then.then.then.
The role is to remove unnecessarily declared wrappers, but is it rather lowering the readability too much?
That's what I'm worried about
To sum up, I think it's really good to provide a builder pattern with chaining, but I think it might rather hurt the dx if it's used in a row.

@minsoo-web Personally, I sometimes prefer the then keyword over the async/await keyword because it allows chaining and makes it easier to read the promises in order. So, if I need to use multiple suspensive components such as ErrorBoundary and Suspense together, I think I will use chaining rather than nesting the wrap function. Nevertheless, if you provide chaining of the wrap function like this, library users can choose whether to use chaining. So I want to provide this wrap chaining.
We can provide below chaining of wrap
import { ErrorBoundary, ErrorBoundaryGroup, Suspense, useErrorBoundary, wrap } from '@suspensive/react'
import { UseSuspenseQuery } from '~/components'
import { api } from '~/utils'

const logError = (error: Error) => console.error(error)

export default wrap(ErrorBoundaryGroup, { blockOutside: false })
  .wrap(ErrorBoundary, { fallback: (props) => <>{props.error.message}</>, onError: logError })
  .wrap(Suspense.CSROnly, { fallback: <>loading...</> })
  .on<{ x: string }>((props) => {
    const errorBoundary = useErrorBoundary()

    return (
      <>
        <button onClick={() => errorBoundary.setError(new Error('trigger error by useErrorBoundary().setError'))}>
          trigger error by useErrorBoundary().setError
        </button>
        <UseSuspenseQuery queryKey={['with', 1] as const} queryFn={() => api.delay(200, { percentage: 50 })} />
      </>
    )
  })

or also below is okay without chaining
import { ErrorBoundary, ErrorBoundaryGroup, Suspense, useErrorBoundary, wrap } from '@suspensive/react'
import { UseSuspenseQuery } from '~/components'
import { api } from '~/utils'

const logError = (error: Error) => console.error(error)

export default wrap(ErrorBoundaryGroup, { blockOutside: false }).on(
  wrap(ErrorBoundary, { fallback: (props) => <>{props.error.message}</>, onError: logError }).on(
    wrap(Suspense.CSROnly, { fallback: <>loading...</> }).on<{ x: string }>((props) => {
      const errorBoundary = useErrorBoundary()

      return (
        <>
          <button onClick={() => errorBoundary.setError(new Error('trigger error by useErrorBoundary().setError'))}>
            trigger error by useErrorBoundary().setError
          </button>
          <UseSuspenseQuery queryKey={['with', 1] as const} queryFn={() => api.delay(200, { percentage: 50 })} />
        </>
      )
    })
  )
)

I prefer chaining but library users can choose 2 ways both.

I change this Pull Request as draft. because I made this https://github.com/suspensive/react/pull/280 that update wrap as builder pattern to remove nested wrap functions with combination importing all public apis

@okinawaa It's experimental feature. I merge this to make new release contain this feature quickly. this will make us get feedback to improve this experimental feature easily and we can fix it later.


Move from recursive calls in wait to a loop

Per forki's request. https://github.com/lefthandedgoat/canopy/issues/388#issuecomment-337871263

awesome. thanks


[SYSTEMML-1096] Add Trademark Symbol to Apache SystemML

Add trademark symbol to top nav and header for each page and removed them from body

LGTM. Thank you @jazares. I'll merge.

@deroneriksson thank you


Support custom window functions

As well as custom functions and aggregate functions, SQLite supports custom window functions.
This would be good to have in sqlite3.
Thanks for all your hard work!

Done, this will be part of the next release!

Damn! Thanks!


ABET Consultant Notes

From Ben:
I am writing to provide more information on the EME 185AB report comments provided by the ABET consultant retained by the CoE. The consultant rated the EME 185AB reports as a Weakness/Deficiency from an ABET standpoint. This is because of the following:
"Some were missing engineering standards and or multiple (at least 2) realistic constraints (non-technical)."
The consultant stressed that all of the reports need to clearly discuss engineering standards and at least two realistic (non-technical) constraints. It is possible that these topics were actually discussed in all of the reports, but it was not readily evident this was the case.
For the actual ABET review in about a year, we will be submitting senior design reports from the 2017-18 academic year. It was recommended by the consultant that these reports have tabs, post-its, or similar guides to enable ABET reviewers to easily locate discussion of engineering standards and multiple realistic constraints, both of which should be included in all of the reports.
I want to also mention that the "realistic" design constraint comes from ABET student outcome c (see below).
"(c) an ability to design a system, component, or process to meet desired needs within realistic constraints such as economic, environmental, social, political, ethical, health and safety, manufacturability, and sustainability"
Let me know if you would like to meet to discuss this

ABET is done for now.


[GH-1052] - Fix prompts when default same as flag

This PR adds a map Config.__is_set to the Config class.
This map is from the flattened parameter name (e.g. config.subtensor.network -> config.__is_set["subtensor.network"]) to a boolean value indicating if the value has been set in a flag (or not).
This map is created from the defaults set in bittensor.defaults on creation of the config, from the parser. Any args that use default=argparse.SUPPRESS will be set to False in the map unless they are set as a flag.
Then, the config will be filled with the default values for these flags, avoiding a breaking change to the config class.
You can then check if any of these args are set using config.is_set('subtensor.network').
The result, is we don't require prompting the user for values that are set, even if the arg is equal to the default. i.e. btcli --subtensor.network finney will not prompt for network again.
Closes #1052

Closed to re-open as #1242


Bug Report: User can add a book in issue section without specifying the author.

Reproduction steps
Make select author field as mandatory in issue section and making "select author" option in dropdown unclickable
Expected behavior
Select author should be mandatory field and if author is not in list then user should select "Others" option
Actual Behavior

👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Please assign me this issue. I would like to work on it.

I want to work on this issue .

There is already an option of 'other' in the website.

The problem here is that the user can also issue a book by selecting "select author" option. In this case "select author" option should be only for reference this should unselectable option which doesn't get clicked.

okay @AbhinavBattu you have been assigned this issue! You can start working. All the best.


Allow Setting the dwcj classname from the EM using arguments.

This should go in dwcj.bbj:
if ARGC > 1 then
    class$=argv(1,err=*next)
fi

@mhawkinsbasis
Can you please add this In here:
https://dwcj.org/docs/getting_started/configuration


Allow specifying Hub IP for containers to communicate.

This is useful when the IP the hub is bound on is not directly reachable by the containers.  When the config option is not set, Hub.ip is used.

@bigzachattack do you know how you got a Merge pull request #1 from jupyter/master commit in here? Perhaps rebasing your branch on master would be the right way to go.

@minrk I rebased bigzachattack/dockerspawner/master to jupyter/dockerspawner/master. Then I forked bigzachattack/dockerspawner/hub-api-url from bigzachattack/dockerspawner/master.

Making a PR isn't rebasing, it's always creating a new merge. PRs are not the way to keep your master up to date.
You can rebase this branch on master with:
git checkout hub-api-url
git rebase jupyter/master


Add artichoke to platform detection in mspec

Update this commit in artichoke/mspec and revendor MSpec:
https://github.com/artichoke/mspec/commit/8c266ab5c65858b8cb39e9e8931c7a3a45966011
Originally posted by @lopopolo in https://github.com/artichoke/artichoke/pull/271#issuecomment-529060732

can I work on this issue if nobody working on it?

If you’d like. This is a bit of a weird ticket in that it requires touching two repos. If you’d like to sync MSpec with the latest upstream maste that’d be great too 💎

This is no longer necessary upstream.
https://twitter.com/eregontp/status/1186719295465672705


Mac OS, cannot create conda environment

On Mac OS, we cannot run "conda env create -n phy". Conda is present on the system, but we get an error
"SpecNotFound: Invalid name, try the format: user/package"

try "conda create -n phy"

This issue could be labeled 'Closed'.


/validation support

reported at https://discuss.eodc.eu/t/validation-of-process-failed/229 :
aggregator does not support /validation endpoint properly
even the simplest process graph with a "load_collection" gives
[{'code': 'ProcessUnsupported',
  'message': "Process with identifier 'load_collection' is not available in namespace 'backend'."}]

will be hidden with next deploy

Not sure what happened, but POST /validation is again listed in capabilites, but gives
OpenEoApiError: [500] Internal: Server error: TypeError("'NoneType' object is not callable")

Implemented basic /validation support in aggregator: forward to "best" upstream backend and send through validation errors.
will close this ticket, possible follow-ups are for other tickets


phpunit: 11.3.0 -> 11.3.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for phpunit is: PHP Unit Testing framework
meta.homepage for phpunit is: https://phpunit.de
meta.changelog for phpunit is: https://github.com/sebastianbergmann/phpunit/blob/11.3.1/ChangeLog-11.3.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 11.3.1 with grep in /nix/store/8yknp5ywpgw80cpjqkwzhnfzm8fjp982-phpunit-11.3.1
found 11.3.1 in filename of file in /nix/store/8yknp5ywpgw80cpjqkwzhnfzm8fjp982-phpunit-11.3.1

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

phpunit

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8yknp5ywpgw80cpjqkwzhnfzm8fjp982-phpunit-11.3.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/6b3823cbd02413c7fa57f206736210eae32b8ac8#phpunit

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8yknp5ywpgw80cpjqkwzhnfzm8fjp982-phpunit-11.3.1
ls -la /nix/store/8yknp5ywpgw80cpjqkwzhnfzm8fjp982-phpunit-11.3.1/bin

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

1 package built:

phpunit

Maintainer pings
cc @onny @aanderse @drupol @Ma27 @piotrkwiecinski @talyz for testing.

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

@NixOS/nixpkgs-merge-bot merge


STAR-452 add EverywhereStrategy

I applied review remarks and added one additional commit: 99e5695. It's meant to fix RangeStreamer for EverywhereStrategy as described here.
Please review.


bug: 4.10.1 does not accept minor/patch angular versions.

<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>- 8 but none is installed.
8.2.9 being latest.
Currently peerDependencies are set as "@angular-devkit/core": "7.2.1 - 8",
Which would limit it to 8.0.0.
A caret would be needed to support minor and patch versions

Thanks for the issue! The range is a semver partial range, so it should behave like the following:
>=7.2.1 and <9.0.0

Here's a little cheat sheet with an example: https://devhints.io/semver
Our conference app is currently using 8.1.1 without issues: https://github.com/ionic-team/ionic-conference-app/blob/master/package.json
I'm able to update our Angular conference app using the following:
ng update @angular/cli @angular/core

Which results in:
$ ng update @angular/cli @angular/core
Using package manager: 'npm'
Collecting installed dependencies...
Found 54 dependencies.
Fetching dependency metadata from registry...
    Updating package.json with dependency @angular/cli @ "8.3.8" (was "8.3.6")...
    Updating package.json with dependency @angular/core @ "8.2.9" (was "8.1.1")...
    Updating package.json with dependency @angular/language-service @ "8.2.9" (was "8.2.8")...
    Updating package.json with dependency @angular/compiler-cli @ "8.2.9" (was "8.1.1")...
    Updating package.json with dependency @angular/compiler @ "8.2.9" (was "8.1.1")...
    Updating package.json with dependency @angular-devkit/build-angular @ "0.803.8" (was "0.801.2")...
    Updating package.json with dependency @angular/common @ "8.2.9" (was "8.1.1")...
    Updating package.json with dependency @angular/forms @ "8.2.9" (was "8.1.1")...
    Updating package.json with dependency @angular/platform-browser-dynamic @ "8.2.9" (was "8.1.1")...
    Updating package.json with dependency @angular/platform-browser @ "8.2.9" (was "8.1.1")...
    Updating package.json with dependency @angular/router @ "8.2.9" (was "8.1.1")...
    Updating package.json with dependency @angular/service-worker @ "8.2.9" (was "8.1.1")...
UPDATE package.json (2816 bytes)

><EMAIL_ADDRESS>install /Users/brandyscarney/Documents/git/ionic-conference-app/node_modules/@angular/compiler-cli/node_modules/fsevents
> node install

node-pre-gyp WARN Using request for node-pre-gyp https download
node-pre-gyp WARN Pre-built binaries not installable for<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(node-v64 ABI, unknown) (falling back to source compile with node-gyp)
node-pre-gyp WARN Hit error getaddrinfo ENOTFOUND fsevents-binaries.s3-us-west-2.amazonaws.com fsevents-binaries.s3-us-west-2.amazonaws.com:443
  SOLINK_MODULE(target) Release/.node
  CXX(target) Release/obj.target/fse/fsevents.o
  SOLINK_MODULE(target) Release/fse.node
  COPY<EMAIL_ADDRESS>  TOUCH Release/obj.target/action_after_build.stamp

><EMAIL_ADDRESS>install /Users/brandyscarney/Documents/git/ionic-conference-app/node_modules/watchpack/node_modules/fsevents
> node install

node-pre-gyp WARN Using request for node-pre-gyp https download
[fsevents] Success: "/Users/brandyscarney/Documents/git/ionic-conference-app/node_modules/watchpack/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node" is installed via remote

><EMAIL_ADDRESS>install /Users/brandyscarney/Documents/git/ionic-conference-app/node_modules/webpack-dev-server/node_modules/fsevents
> node install

node-pre-gyp WARN Using request for node-pre-gyp https download
[fsevents] Success: "/Users/brandyscarney/Documents/git/ionic-conference-app/node_modules/webpack-dev-server/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node" is installed via remote

><EMAIL_ADDRESS>postinstall /Users/brandyscarney/Documents/git/ionic-conference-app/node_modules/@angular/cli
> node ./bin/postinstall/script.js

added 364 packages from 109 contributors, removed 145 packages, updated 116 packages, moved 11 packages and audited 17266 packages in 79.844s
found 0 vulnerabilities

Could you try running that command?

Trying with a fresh project it works. Something weird must have happened with npm to not detect already installed angular.


US01 file cleaning

Deleted harmonia's assets and Item/User files and cleaned the related files as well as App.jsx, App.css and schema.sql

Opened PR towards main by accident


Transaction fee amount

Hello! I have a question regarding the transaction fee amount. Does it reflect real fee amount which I can expect on the Mainnet?

Great question. Are you talking about the Chainlink fees or the gas fees?
For Chainlink VRF, you can find all the fees for each network here: https://docs.chain.link/docs/vrf-contracts/
I'm closing this issue for now, but feel free to follow up


refactor(tabs): padding update

Pull request type
Jira Link: -
Nikola requested to change the padding in the DS to the following:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Other (please describe):

How to test this PR

It's good to test inside the storyfront. There will be a second PR in the storyfront to fix all the tabs to be the same and aligned well:

cd storyblok-design-system && git checkout fix/sb-tabs-padding
Then on the localhost navigate the application and check if everything looks correct where tabs are used
You can also compare https://storyblok-design-system-git-fix-sb-tabs-padding-storyblok-com.vercel.app/ and https://blok.ink/

https://user-images.githubusercontent.com/11278408/167393508-c9c4ed2e-3f0f-4fef-8c17-aaa8b948ce02.mov
What is the new behavior?

Less padding left and right on sb tabs

Other information

After talking with Nikola, I still think we can add this change to the DS

Thanks @fernandacanto @fariacc I will check about these issues


Navbar - Collapse bug

Why are things shown inline?

Duplicate of #17250. Navbars are still a work-in-progress in Bootstrap v4.


does not remember last selected folder for downloads

MM does not remember last selected folder for downloads, but always defauklst to some not-configurable folder instead, no matter whatever folder I selected the last time.

there is already an ticket filed for that: https://mattermost.atlassian.net/browse/MM-22013


add dependabot

still have to test it.

blocked on https://github.com/dependabot/dependabot-core/issues/8508


Create functions to retrieve data from GH repos

@nicpuppa @Wabri @abe-101 @davideimola @TheJoin95 anyone willing to take on this POC to see what data we get?

  user(login: "wabri") {
    login
    avatarUrl
    contributionsCollection(
      from: "2022-01-01T00:00:01Z"
      to: "2022-12-31T23:59:59Z"
    ) {
      totalCommitContributions
      totalIssueContributions
      totalRepositoryContributions
      totalPullRequestContributions
      commitContributionsByRepository {
        repository {
          name
          languages(first: 100) {
            nodes {
              name
            }
          }
        }
        contributions(first: 5, orderBy: {field: COMMIT_COUNT, direction: DESC}) {
          totalCount
        }
      }
      user {
        topRepositories(first: 5, orderBy: {field: STARGAZERS, direction: DESC}) {
          edges {
            node {
              name
              stargazerCount
              languages(first: 100) {
                nodes {
                  name
                }
              }
            }
          }
        }
      }
    }
  }
}

Presentazione = tpl slide 1
Quanti commits = tpl slide 4
Top contributions repo = tpl slide 5
Top starred repo = tpl slide 5
Recap = tpl slide 6

The svg are now components and can be customize as we wish (by adding props).


Allow storagepoolmap remove from requested

And add some more logging on startup

https://github.com/rancher/rancher/issues/7122


Fix missing link

Fix missing link for raw markdown template.

Hi @lemmaa, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

Open Publishing Build Service: The pull request content has been published and here are some changed files links of this time:

Docset 1 - core-docs
No file of this docset changes.

Status: Succeeded.
Open Publishing Report.

@lemmaa Thanks for fixing this.


Support conditional put in TransferUtility (S3)

Describe the feature
There's currently no way to include a If-None-Match: * or similar condition with the transfer operation. It's not that S3 doesn't support this but it's not possible to pass this information to the CompleteMultipartUpload operation.
Use Case
I use If-None-Match: * specifically to prevent overwriting stuff already in storage.
Proposed Solution
Simply make it possible to add If-None-Match: * to TransferUtilityUploadRequest. Currently there's no way to influence the CompleteMultipartUpload operation via the TransferUtilityUploadRequest.
Other Information
I've snooped around the code and the only way I managed to do this of the V3 code, is this.
class AmazonX3CompleteMultipartUploadRequestMarshaller : IMarshaller<IRequest, CompleteMultipartUploadRequest>, IMarshaller<IRequest, AmazonWebServiceRequest>
{
	public IRequest Marshall(AmazonWebServiceRequest input)
	{
		return Marshall((CompleteMultipartUploadRequest)input);
	}

	public IRequest Marshall(CompleteMultipartUploadRequest input)
	{
		var req = CompleteMultipartUploadRequestMarshaller.Instance.Marshall(input);
		req.Headers["If-None-Match"] = "*";
		return req;
	}
}

class AmazonX3Client : AmazonS3Client
{
	public AmazonX3CompleteMultipartUploadRequestMarshaller CompleteMultipartUploadRequestMarshaller { get; } = new();

	public AmazonX3Client(AWSCredentials credentials, AmazonS3Config config) : base(credentials, config) { }

	public override Task<CompleteMultipartUploadResponse> CompleteMultipartUploadAsync(CompleteMultipartUploadRequest request, CancellationToken cancellationToken = default)
	{
		InvokeOptions options = new InvokeOptions();
		options.RequestMarshaller = CompleteMultipartUploadRequestMarshaller;
		options.ResponseUnmarshaller = CompleteMultipartUploadResponseUnmarshaller.Instance;
		return InvokeAsync<CompleteMultipartUploadResponse>(request, options, cancellationToken);
	}
}

I would prefer to use the TransferUtility but I need to be able to make it a conditional PUT that won't overwrite what is already in storage.
Acknowledgements

[X] I may be able to implement this feature request
[ ] This feature might incur a breaking change

AWS .NET SDK and/or Package version used
AWSSDK.S3 3.7.401.2
Targeted .NET Platform
.NET 8
Operating System and version
Windows 11

On second though, my solution to this problem will work with the TransferUtility, there should be no need for this because I can pass my AmazonX3Client to the TransferUtility instance and it should do the right thing.

Thanks for self resolution.


better contrast for kernel selection

For #9138

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

Old colors with low hover contrast:

New colors with high hover contrast:

Codecov Report

Merging #9139 into master will increase coverage by 0.66%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #9139      +/-   ##
==========================================
+ Coverage   56.39%   57.06%   +0.66%
==========================================
  Files         551      551
  Lines       28840    29210     +370
  Branches     4427     4427
==========================================
+ Hits        16264    16668     +404
+ Misses      11662    11628      -34
  Partials      914      914

Impacted Files
Coverage Δ

src/client/common/utils/platform.ts
70.58% <0%> (-5.89%)
:arrow_down:

...lient/datascience/jupyter/jupyterSelfCertsError.ts
100% <0%> (ø)
:arrow_up:

src/client/debugger/extension/serviceRegistry.ts
100% <0%> (ø)
:arrow_up:

src/client/common/variables/serviceRegistry.ts
100% <0%> (ø)
:arrow_up:

src/client/common/process/serviceRegistry.ts
100% <0%> (ø)
:arrow_up:

src/client/common/dotnet/serviceRegistry.ts
100% <0%> (ø)
:arrow_up:

src/client/linters/serviceRegistry.ts
100% <0%> (ø)
:arrow_up:

...tascience-ui/native-editor/redux/reducers/index.ts
100% <0%> (ø)
:arrow_up:

src/client/interpreter/serviceRegistry.ts
100% <0%> (ø)
:arrow_up:

src/client/common/platform/serviceRegistry.ts
100% <0%> (ø)
:arrow_up:

... and 40 more

Continue to review full report at Codecov.

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


[Question] How to install httpd modules without load errors due to apt package incompatibilities?

[Question] How to install httpd modules without load errors due to apt package incompatibilities?
Hi everyone,
I'm trying to install some modules using apt (e.g.: libapache2-mod-perl2). However, apt doesn't recognize that httpd is already present and will attempt to install apache2-bin as a dependency. The version of the apache2-bin package installed by apt might not be compatible with the httpd version currently in use, which is exactly my case.
For example, I'm using the httpd:2.4-bullseye image, and when installing libapache2-mod-perl2 apt installs apache2-bin package version 2.4.61. This version is incompatible with the other manually installed bynaries. As a result, when trying to load certain modules, such as mod_mime, I receive the following error:
Syntax error on line 124 of /usr/local/apache2/conf/httpd.conf: Cannot load modules/mod_mime.so into server: /usr/local/apache2/modules/mod_mime.so: undefined symbol: ap_set_content_type_ex

I've managed to install apache2-bin version 2.4.59 through apt, which seems compatible with the image installation, but I can't rely on that forever.
My Dockerfile:
FROM httpd:2.4-bullseye
    RUN ln -s /usr/local/apache2 /usr/lib/apache2
    RUN apt-get update \
        && apt-get install -y --no-install-recommends locales \
        && apt-get clean \
        && rm -rf /var/lib/apt/lists/* \
        && localedef -i en_US -c -f UTF-8 -A /usr/share/locale/locale.alias en_US.UTF-8
    ENV LANG=en_US.utf8
    RUN apt-get update \
        && apt-get install -y --no-install-recommends apache2-bin=2.4.59-1~deb11u1 \
        perl libapache2-mod-perl2 \
        libwww-perl s3cmd \
        && apt-get clean

Any thoughts about that?
Best regards!
samueldc

Another solution is removing the symbolic link of the server root path (removing line RUN ln -s /usr/local/apache2 /usr/lib/apache2 from the dockerfile above) and load the module referencing the full path (e.g.: LoadModule perl_module /usr/lib/apache2/modules/mod_perl.so instead of LoadModule perl_module modules/mod_perl.so). That way httpd looks to work just fine.
But I'm still concerned with compatibilities problems between the bynaries of the manual installation and the ones installed by apt.

More about it from the Check_MK forum. Looks like more people are struggling with this matter:
https://forum.checkmk.com/t/apache-failed-with-syntax-error/48244

Unfortunately, this image installs httpd in the "upstream recommended" / documented way, namely building it from source.  If you want more modules for it, and you want them to be compatible with it, you'll likely need to build them from source also.  I would not recommend mixing-and-matching in the way you've described with package-built binaries/modules and this image.  For that, you're going to be much better off just installing httpd itself from Debian/packages as well, and not using this image at all.

Totally agree with you. The problem is installing httpd from a base debian image is very troublesome and we are forced to use a process like supervisord since installing httpd from apt doesn't provide a httpd command like httpd-foreground.

Oh, it's uh, not much: :sweat_smile:
https://github.com/docker-library/httpd/blob/3056c115a9f3c2467cc6f67470cfded70c4adc64/2.4/httpd-foreground#L7
See also the "apache" variants of https://hub.docker.com/_/php which do exactly that:
https://github.com/docker-library/php/blob/21e6a92a1998c7f3157bc5df291fbd600330e33d/8.3/bookworm/apache/Dockerfile#L286
https://github.com/docker-library/php/blob/21e6a92a1998c7f3157bc5df291fbd600330e33d/8.3/bookworm/apache/apache2-foreground#L40
All that "envvars" and directory logic can be avoided via some other wrapper, but I can't remember it offhand (apache2ctl maybe?); this is what we do to prep for all that, if you do want that behavior:
https://github.com/docker-library/php/blob/21e6a92a1998c7f3157bc5df291fbd600330e33d/8.3/bookworm/apache/Dockerfile#L54-L90

Confirmed, the following seems to work pretty reasonably:
FROM debian:bookworm-slim

RUN apt-get update && apt-get install -y --no-install-recommends apache2 && rm -rf /var/lib/apt/lists/*

CMD ["apache2ctl", "-DFOREGROUND"]

Built, ran, connected via my browser on port 80, got:

Notably, you might want to include --init/init: true (or install/use tini explicitly) since apache2ctl is a shell script that notably does not use exec when launching the httpd process (https://salsa.debian.org/apache-team/apache2/-/blob/1d2fb82219a579e603dd8c52f3cccb0752f06115/debian/apache2ctl#L212), so will not transmit signals correctly by default (which I think is why we ended up implementing so much logic ourselves over in PHP).

@tianon Thank you so much for the help. I'll try that right away.


Update the deploy to include a warning before closing the cloud shell

Update the deploy script to include a warning before closing the cloud shell as publishers are closing it before copying the proper field to Partner Center.

@code4clouds can we add an issue to this PR please?


Error retrieving programs

Recently, we've started seeing this error when the app refreshes or when trying to tap through setup:
error java.lang.RuntimeException: bad character in base64 value @line 213 (parse)

After some digging, I believe this is caused by a recent SmartThings change that limits the size of data being transferred through the event object.
https://community.smartthings.com/t/event-data-limits/154109/16
The RainMachine call to get the list of programs returns quite a bit of data for each one, so it pretty easily exceeds this limit.
I'm currently toying with getting each program individually, and it mostly works, but I've got two main challenges with this:

I have no way of knowing ahead of time how many programs you have. Basically I have to just start at 0 and then make as many calls as I think would cover all your programs, knowing most of them will return nothing. If you ever delete a program, the next one you create just increments to the next ID, so if you've deleted your first 10 programs, your first RainMachine program ID is 11, but again - I have no way to know that beforehand. I can force this to work, but it may seem somewhat inefficient.

The calls to all programs happen simultaneously. While good for performance,  somehow I have to be able to have to code realize that we're done retrieving all programs. But yet again - since I never knew how many there were to begin with, it's tricky to set a clean "done" target. I may end up just setting a hard-coded 10-second wait, but hopefully I can find something a bit more elegant than that.

Fix pushed.


[formal] updated sv2v synthesis/lec flow

I have been working on fixing up this synthesis and verification flow. I found and fixed several different issues in sv2v going through this process. Running it through Yosys successfully depends on https://github.com/YosysHQ/yosys/pull/2136.
At this point, every module besides pwrmgr_cdc passes verification! I suspect there may be an issue with Conformal, as the discrepancy appears to be conditioned on the alphabetical ordering of fields in a struct (i.e., if the field names are a, b in the reference and x, y in the revised, it passes, but if the order is swapped in either module, it fails).
I want to get some eyes on this to see if my changes seem reasonable and if others can replicate my verification results. I'd also be curious to know whether the Yosys output is functional, and what else can be done to further the open source flow.

Hi Zach,
Thank you for the contribution, I was able to reproduce your results with only pwrmgr_cdc fails.
I do see a few warnings from Yosys:
Yosys:
Warning: Replacing memory \region_end with list of registers. See flash_mp.v:108, flash_mp.v:107
Warning: Replacing memory \pmp_addr_rdata with list of registers. See ibex_cs_registers.v:855
Warning: Replacing memory \mhpmevent with list of registers. See ibex_cs_registers.v:897
Warning: Replacing memory \fill_data_q with list of registers. See ibex_icache.v:513
Warning: Replacing memory \fill_way_q with list of registers. See ibex_icache.v:501
Warning: Replacing memory \fill_addr_q with list of registers. See ibex_icache.v:498
Warning: Yosys has only limited support for tri-state logic at the moment. (padring.v:135)
Warning: Yosys has only limited support for tri-state logic at the moment. (padring.v:181)
prim_lfsr.v:44: ERROR: Condition for generate if is not constant!

For the future open source flow, personally - I would be very interested to see if we cae use SymbiYosys to verify modules with assertions such as (prim_packer)[https://github.com/lowRISC/opentitan/blob/master/hw/ip/prim/rtl/prim_packer.sv] (prim_lfsr)[https://github.com/lowRISC/opentitan/blob/master/hw/ip/prim/rtl/prim_lfsr.sv].
I do recall discussing SymbiYosys with some colleagues, seems like it does not support bind unless using Verific.
Thanks,
Cindy

@cindychip @rswarbrick is working on bind support for Yosys.

It looks like adding set mapping method -noname before set system mode lec fixes the error and allows everything to pass cleanly. However, I noticed the key point mapping for prim_generic_rom takes minutes rather than seconds with that option.
@cindychip Yosys actually generates even more warnings once it gets past that error. Fixing the error requires either my changes on that Yosys PR, or removing the string size casts from prim_lfsr.

Ah, cool, I wasn't aware of this PR. I had created a similar one earlier today here.
Regarding the failing pwrmgr_cdc. I believe this mismatch is caused by this sv2v issue, which is now fixed.
The difference between this PR and PR #2493: The latter runs LEC for the entire module including all its submodules and uses filelists.

@NilsGraf The failure on pwrmgr_cdc is resolved with the addition of set mapping method -noname, which I included in my previous push. While pwrmgr_pkg does contain some single-bit parameters (PWR_CPU_DEFAULT and PWR_FLASH_DEFAULT ), they were not subject to that particular bug because the parameters took on the explicit size of the wrapping structs (pwr_cpu_t and pwr_flash_t).

With @NilsGraf's suggested fix in https://github.com/zachjs/sv2v/issues/93, the use of unresolved blackboxes in this LEC flow causes many discrepancies. It seems that Conformal is lenient when comparing the inputs to the blackboxes given the ports have unknown width. I was able to get past this for everything besides padring, prim_ram_2p_adv, and prim_ram_2p_async_adv by reading and -notranslateing all of the prim_ modules, rather than just the prim_generic_ modules.

Got it. I would suggest to go ahead and merge this PR #2465. I can then modify and merge my PR to add the flow that doesn't blackbox the submodules.


use poetry-core

Codecov Report

Merging #21 (4748b53) into main (3f1a016) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #21   +/-   ##
=======================================
  Coverage   96.19%   96.19%
=======================================
  Files          27       27
  Lines        1577     1577
=======================================
  Hits         1517     1517
  Misses         60       60

Continue to review full report at Codecov.

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


feat: add support for github.com/confluentinc/confluent-kafka-go/kafka (& its v2 counterpart)

Adds support for instrumenting github.com/confluentinc/confluent-kafka-go/kafka and github.com/confluentinc/confluent-kafka-go/v2/kafka.
Tests for v2 library are commented because both libraries cannot coexist in the same package. An upcoming PR from @rarguelloF will separate the tests in a way that will keep them apart, so we'll be able to run both test suites. The v2 tests have been tested locally successfully.

closed in favor of https://github.com/DataDog/orchestrion/pull/320


Contextual typing for more function return values

Suggestion
🔍 Search Terms
return type contextual typing
✅ Viability Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion + Motivating Example
I think this is a feature request rather than a bug report, but I'm not sure... I know that contextual typing is currently applied selectively, and that that's intentional, but I couldn't find many issues discussing what the boundaries for applying contextual typing are intended to be. I also don't know what real-world code would've motivated the current rules, so it's possible that my suggestion here would be helpful for the example case below but be counterproductive overall.
Anyway, here's the code I'm dealing with (simplified):
abstract class Item {
  abstract get categories(): Category[];
}

class Book extends Item {
  get categories() {
    return [{
      label: 'Sports',
      children: [
        { label: 'Baseball', children: [] },
        { label: 'Tennis', children: [] }
      ],
    }];
  }
}

type Category = ParentCategory | LeafCategory;
type ParentCategory = {
  label: string;
  children: [Category, ...Category[]];
};

type LeafCategory = {
    label: "Baseball" | "Tennis";
    children: [];
};

In this code, I'd expect the Book.categories getter to type check, but it doesn't.
The expression being returned is assignable to Category[] if Category[] is used to contextually type it — i.e., the code works if I add satisfies Category[] at the end of the returned expression, or if I do const x: Category[] = /* same expression */; return x;.
However, without contextual typing, TS infers an array type (i.e., { label: string; children: never[]; }[]) as the type for the outermost children property, whereas ParentCategory requires that be a tuple type, to enforce that the array is non-empty.
So, my suggestion/feature request would to apply contextual typing in (at least) the case above (if it's not already supposed to apply there) — but again, I'm not sure what downsides this might have for other code.

Duplicate of #32082.

Agh, not sure how I missed that whole family of issues. Seems more like https://github.com/microsoft/TypeScript/issues/23911, but it's still a duplicate. Closing.


Temporarily lower .python-version to fix dependabot

Dependabot has been broken since updating .python-version to 3.9.11 since it doesn't know about newer versions yet. Temporarily lowering the version until https://github.com/dependabot/dependabot-core/pull/5033 is merged and released.

Codecov Report

Merging #201 (934785c) into golden (6fa4122) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            golden      #201   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           38        38
  Lines         2258      2258
  Branches       490       490
=========================================
  Hits          2258      2258

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


[CT-4955] Handle long string in RichText

CT-4955
Description
Handle long string overflow in RichText component.
How to test

Temploy
FIXME: Add the steps describing how to verify your changes

Screenshots

Before.
After.

Development checks

[ ] Add changeset according to guidelines (if needed)
[ ] Read CONTRIBUTING.md and Component API principles
[ ] Make sure that additions and changes on the design follow Toptal's BASE design, and it's been already discussed with designers at #-base-core
[ ] Annotate all props in component with documentation
[ ] Create examples for component
[ ] Ensure that deployed demo has expected results and good examples
[ ] Ensure the changed/created components have not caused accessibility issues. How to use accessibility plugin in storybook.
[ ] Self reviewed
[ ] Covered with tests (visual tests included)

Breaking change

[ ] codemod is created and showcased in the changeset
[ ] test alpha package of Picasso in StaffPortal

All development checks should be done and set checked to pass the
GitHub Bot: TODOLess action

PR commands

List of available commands:

@toptal-bot run package:alpha-release - Release alpha version
@toptal-anvil ping reviewers - Ping FX team for review

PR Review Guidelines

When to approve? ✅
You are OK with merging this PR and

You have no extra requests.
You have optional requests.

Add nit: to your comment. (ex. nit: I'd rename this variable from makeCircle to getCircle)

When to request changes? ❌
You are not OK with merging this PR because

Something is broken after the changes.
Acceptance criteria is not reached.
Code is dirty.

When to comment (neither ✅ nor ❌)
You want your comments to be addressed before merging this PR in cases like:

There are leftovers like unnecessary logs, comments, etc.
You have an opinionated comment regarding the code that requires a discussion.
You have questions.

How to handle the comments?

An owner of a comment is the only one who can resolve it.
An owner of a comment must resolve it when it's addressed.
A PR owner must reply with ✅ when a comment is addressed.

@toptal-anvil ping reviewers

I can see that one of failing visual tests has "us" word split into two lines, is it expected?


⚠ Bofrost.ch has degraded performance

In d8e2e8d, Bofrost.ch (https://www.bofrost.ch) experienced degraded performance:

HTTP code: 200
Response time: 1450 ms

Resolved: Bofrost.ch performance has improved in fd63ed9 after 6 minutes.


Support addr:housename in the editor

At the moment, the “entrance mode” editor doesn't have a field for addr:housename. It makes it hard to use Every Door for survey in the regions, where a house name is an common part of an address.
According to OSM wiki, addr:housename...

is sometimes used in some countries like England, Spain, Portugal, Latvia instead of (or in addition to) a house number.

I suggest adding a “House Name” field in the editor, just between “Number” and “Street” fields. Maybe toggle it in the settings, to avoid confusing users from the regions where house names are not used.
Please note that in some countries housenames and housenumbers complement each other, they are not mutually exclusive, so don't hide “Number” field anyways.

Try entering a word into the "housenumber" field — it will ask you if that's a name.

Thanks, didn't realize it was possible! That's great.
Unfortunately, still can't find a way to enter housenumber and housename together. Can you please consider supporting both of those fields? In some countries it's rather common for a house to have a name as well as the number.

Currently there is no easy way to add both, that's true. What you can do is, tap "More..." button on the building card, then go into the raw tags editor (the button at the top right), and add a tag manually.


WIP read_distributed with local and non_local_data

This PR allows to read distributed from pregenerated local and non_local_data

Suggestion to make writing such functionality and passing communication data easier: We should add a distributed::RowGatherer (or RowGather? Gatherer is a handful) LinOp that does what communicate does inside distributed::Matrix. It gets constructed from an array of global indices and a corresponding Partition. Additionally, we should have the dual RowScatter that scatter-adds the values. Combining these two, we get row-distributed, column-distributed and overlapping distributed matrices.
That gives us a single place where we construct communication patterns and deal with MPI, everything else just passes information through.
cc @MarcelKoch


Implement rules checking order of elements in keyword and test case

Implement rules verifying order of elements in keyword and test case.

I believe in this  PR I implemented what in scope of #997


Multisource Checkpoints

Still missing

[x] unit tests
[x] when ingesting a file, we should publish a checkpoint with a source that makes sense.
The easiest way today is to go source_id = f(canonical_path), and keep the checkpoint as is.
A better way would be to add an "ingest_file" source and put the filename in the partition key.

That would require making a change in the FileSource however.

@guilload I tried but failed to get a good missing checkpoint story that worked properly with the ingest CLI.

@guilload ready for your review.
A couple of important changes...
The ingest stuff now gets a specific source id.
It is the same source id regardless of whether it is a file or stdin. Stdin is not a problem here since the fileSource the ignore checkpoint and do not emit checkpoints.
The filepath are canonicalized before creating a partition id out of it.


Add new role_credentials_provider module that implements auto refreshing credentials

This provider assumes the role and gets the temporary credentials and refreshes the credentials when they are close
to expiration.

This seems fine to me, but make sure you are aware of LazyBuilder it seems like it might allow you to reduce some amount of code here. Note the docs specifically mention the AssumeRole use case.

Yes, I've seen the LazyBuilder but it doesn't seem that it helps because it still requires implementing a struct that implements ProvideCredentials trait and then passes this entity by LazyCredentialsCache into the aws config builder. As the result it even brings more code which is harder to understand


Authorization header should be case-insensitive

According to https://stackoverflow.com/a/5259004 leading to RFC2616, Section 4.2:
Each header field consists of a name followed by a colon (":") and the field value.
Field names are case-insensitive.

Thus authenticate should find a way to handle these header field names in a case-insensitive way, so for example AUTHORIZATION would also be accepted, which is not presently the case:
https://github.com/ArupAus/authenticate/blob/594f20e9327851e76d2683531e975f641f32ada9/BackEndUtils/AuthUtils.js#L40

Closing due to inactivity.


Added elixir section to README

Documentation for Elixir usage of Lager. #348
I aimed to provide the useful context that would allow elixir developers to make a choice between directly usage or the more idiomatic Lager as a Logger Backend approach.
I felt it would be overkill to add elixir example for every Erlang snippet in the README.

This is lovely, thank you. I'd like to add a quick section about hut too but I can do that independently.


An error occurred when using the '@nuxtjs/i18n' plugin for packaging in nuxt3

Environment

Operating System: Windows_NT
Node Version:     v16.17.0
Nuxt Version:     3.4.2
Nitro Version:    2.3.3
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      runtimeConfig, app, modules, svgo, robots, i18n, components, css, vite, imports
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
none
Describe the bug
The following error occurred when using the latest version for packaging

[22:45:48]  ERROR  [nuxt] [request error] [unhandled] [500] Cannot find module 'G:\Web_Project\YunDao\YiHui\m_yihui\dist\server\_nuxt\i18n.config-0ae2e280.js' imported from G:\Web_Project\YunDao\YiHui\m_yihui\.nuxt\prerender\chunks\nitro-prerenderer.mjs
  at new NodeError (node:internal/errors:387:5)
  at finalizeResolution (node:internal/modules/esm/resolve:429:11)
  at moduleResolve (node:internal/modules/esm/resolve:1006:10)
  at defaultResolve (node:internal/modules/esm/resolve:1214:11)
  at nextResolve (node:internal/modules/esm/loader:165:28)
  at ESMLoader.resolve (node:internal/modules/esm/loader:844:30)
  at ESMLoader.getModuleJob (node:internal/modules/esm/loader:431:18)
  at ESMLoader.import (node:internal/modules/esm/loader:528:22)
  at importModuleDynamically (node:internal/modules/esm/translators:110:35)
  at importModuleDynamicallyCallback (node:internal/process/esm_loader:35:14)
  at /G:/Web_Project/YunDao/YiHui/m_yihui/.nuxt/prerender/chunks/nitro-prerenderer.mjs:24923:18
  at async Object.handler (/G:/Web_Project/YunDao/YiHui/m_yihui/node_modules/.pnpm/registry.npmmirror.com+h3@1.6.4/node_modules/h3/dist/index.mjs:1247:19)
  at async toNodeHandle (/G:/Web_Project/YunDao/YiHui/m_yihui/node_modules/.pnpm/registry.npmmirror.com+h3@1.6.4/node_modules/h3/dist/index.mjs:1322:7)
  at async ufetch (/G:/Web_Project/YunDao/YiHui/m_yihui/node_modules/.pnpm/registry.npmmirror.com+unenv@1.4.1/node_modules/unenv/runtime/fetch/index.mjs:9:17)
  at async generateRoute (/G:/Web_Project/YunDao/YiHui/m_yihui/node_modules/.pnpm/registry.npmmirror.com+nitropack@2.3.3/node_modules/nitropack/dist/shared/nitro.96034a6e.mjs:4190:17)
  at async prerender (/G:/Web_Project/YunDao/YiHui/m_yihui/node_modules/.pnpm/registry.npmmirror.com+nitropack@2.3.3/node_modules/nitropack/dist/shared/nitro.96034a6e.mjs:4248:22)
  at async /G:/Web_Project/YunDao/YiHui/m_yihui/node_modules/.pnpm/registry.npmmirror.com+nuxt@3.4.2_@types+node@18.0.0/node_modules/nuxt/dist/index.mjs:2226:7
  at async build (/G:/Web_Project/YunDao/YiHui/m_yihui/node_modules/.pnpm/registry.npmmirror.com+nuxt@3.4.2_@types+node@18.0.0/node_modules/nuxt/dist/index.mjs:3110:5)
  at async Object.invoke (/G:/Web_Project/YunDao/YiHui/m_yihui/node_modules/.pnpm/registry.npmmirror.com+nuxi@3.4.2/node_modules/nuxi/dist/chunks/build.mjs:55:5)
  at async _main (/G:/Web_Project/YunDao/YiHui/m_yihui/node_modules/.pnpm/registry.npmmirror.com+nuxi@3.4.2/node_modules/nuxi/dist/cli.mjs:48:20)

The path here seems incorrect, nuxt path is . nuxtt

Additional context
No response
Logs
No response

Hi, thanks for opening an issue. A minimum reproduction of the issue would really help understand and point the exact issue, because right now I'm unable to tell your configuration for Nuxt and i18n.

Hi, thanks for opening an issue. A minimum reproduction of the issue would really help understand and point the exact issue, because right now I'm unable to tell your configuration for Nuxt and i18n.
You can use https://stackblitz.com/github/nuxt/starter/tree/v3-stackblitz as starter.

It may be a dependency issue, I deleted node_modules directory has been reinstalled and the dependencies are ready for normal packaging


Sipml5 have issue For Hold/Resume in Chrome Last Version And FireFox last Version

Sipml5 have issue For Hold/Resume in Chrome Last Version And FireFox last Version;
IN FireFox Last version  Call Terminated

Hello
In my case the following occurs ... I put in the standby and I retrieve it once, putting on hold the second time I can not retrieve the call. I appreciate you helping me. Test done in the latest chrome.

Hello
In my case the following occurs ... I put in the standby and I retrieve it once, putting on hold the second time I can not retrieve the call. I appreciate you helping me. Test done in the latest chrome.
Using the latest version of mozilla the call terminates when trying to put it on hold.
I am using asterisk 16.0.1.
In short ... In Chrome I can put and retrieve the wait only once, in Mozilla the call is ended on the first try.

Your problem might be related to chrome entering into its next phase in the migration to the WebRTC unified plan.  Google now implements the Unified-Plan by default for WebRTC in Chrome 72.  See here for details.  There is a link to a transition guide.  It might be that specifying you want to use Plan-B will resolve your problem -- at least temporarily until the next phase when Google removes Plan-b implementation entirely.

@dlethin  thank you . Issue Fixed With Plan-B

@majidbigdeli i have the same issue. Can you help me to solve it? How i can use "Plan-B"?

@Udirley You Can Fix Issue With Change In tmedia_session_jsep.js File .
Please open tmedia_session_jsep.js File And Then Find  new window.RTCPeerConnection
And Then Change
From
this.o_pc = new window.RTCPeerConnection(                 (o_iceServers && !o_iceServers.length) ? null : { iceServers: o_iceServers, rtcpMuxPolicy: "negotiate" }, // empty array is used to disable STUN/TURN.                 this.o_media_constraints         );
To
this.o_pc = new window.RTCPeerConnection( 			(o_iceServers && !o_iceServers.length) ? null : { iceServers: o_iceServers, rtcpMuxPolicy: "negotiate", sdpSemantics: "plan-b" }, // empty array is used to disable STUN/TURN.                 this.o_media_constraints         );

@Udirley
To improve performance
In tmedia_session_jsep.js File
Find tmedia_session_jsep01.onIceCandidate Then Change
From
tmedia_session_jsep01.onIceCandidate = function (o_event, _This) {
    var This = (tmedia_session_jsep01.mozThis || _This);
    if (!This || !This.o_pc) {
        tsk_utils_log_error("This/PeerConnection is null: unexpected");
        return;
    }
    var iceState = (This.o_pc.iceGatheringState || This.o_pc.iceState);

    tsk_utils_log_info("onIceCandidate = " + iceState);

    if (iceState === "complete" || (o_event && !o_event.candidate)) {
        tsk_utils_log_info("ICE GATHERING COMPLETED!");
        tmedia_session_jsep01.onIceGatheringCompleted(This);
    }
    else if (This.o_pc.iceState === "failed") {
        tsk_utils_log_error("Ice state is 'failed'");
        This.o_mgr.callback(tmedia_session_events_e.GET_LO_FAILED, This.e_type);
    }
}

To
tmedia_session_jsep01.onIceCandidate = function (o_event, _This) {
	var This = (tmedia_session_jsep01.mozThis || _This);
	if (!This || !This.o_pc) {
		tsk_utils_log_error("This/PeerConnection is null: unexpected");
		return;
	}
	var iceState = (This.o_pc.iceGatheringState || This.o_pc.iceState);

	tsk_utils_log_info("onIceCandidate = " + iceState);

	if (!tmedia_session_jsep01.ice_timer) {
		tmedia_session_jsep01.ice_timer = setTimeout(function () {
			console.log("ICE timer...");
			tmedia_session_jsep01.onIceGatheringCompleted(This);
			tmedia_session_jsep01.ice_timer = null;
		}, 0);
	};

	if (iceState === "complete" || (o_event && !o_event.candidate)) {
		tsk_utils_log_info("ICE GATHERING COMPLETED!");
		tmedia_session_jsep01.onIceGatheringCompleted(This);
	}
	else if (This.o_pc.iceState === "failed") {
		tsk_utils_log_error("Ice state is 'failed'");
		This.o_mgr.callback(tmedia_session_events_e.GET_LO_FAILED, This.e_type);
	}
}

@pr0c

The fix @majidbigdeli mentioned is what we did as a short term fix.   However, long term it will not be enough when Google releases a newer version of Chrome with the final phase of there unified-plan migration to remove support for plan-b entirely.   Hopefully someone with a bit more application knowledge might be able to offer insight as to what if anything would need to change to fully support the unified-plan in sipml5.  Another possibility might be that its the system the sipml5 application is connecting with that will need to change.

Hello,
Chrome beta no longer supports plan-b.
I was not sure if I should update my pbx for the unified plan to work. After testing sip.js, I have seen that it works fine and it is a sipml5 problem.
Anyone know any solution ??
Thanks.

Is anyone fixed this issue


Range

How can I activate or deactivate time picker range? It is not allowing me to pick the time from past which i need to. (eg: Its 5:30 pm I need to pick 4:30 pm, which i cant)

Hi,
Sorry for the late reply. In order to pick a time further back to the past, you should set the min date for the picker some time way back. Please take a look at the demo project to see how you can set the min date in the init method.
Thanks


As a developer, I want the converter to have an option of converting through Docx4J, so that we can possibly improve conversion precision.

Testing has shown that Docx4J only works well when Microsoft Word is installed :(


openliberty_microprofile_tck_jdk8_hs failed

https://ci.adoptopenjdk.net/view/work-in-progress/job/grinder_sandbox_new/438/:
openliberty_microprofile_tck_jdk8_hs failed with:
:01  BUILD SUCCESSFUL
11:12:01  Total time: 1 minute 37 seconds
11:12:26  Error: No such container:path: openliberty-mp-tck-test:/testResults/surefire-reports
11:12:26
11:12:26  openliberty_microprofile_tck_jdk8_hs_0_FAILED

Shouldn't auto delete the container for tests need to keep the results.
https://github.com/adoptium/aqa-tests/blob/master/external/external.sh#L80
https://github.com/adoptium/aqa-tests/blob/master/external/external.sh#L157
This should be fixed by https://github.com/adoptium/aqa-tests/pull/3374/, which removed the rm option


Add .avif format to static types in typescript templates

Changes

Adds typing for .avif image format on Typescript templates.
Jake wrote a good article about it here: https://twitter.com/jaffathecake/status/1303290847958573057
Testing

No testing needed for typing update

LGTM!


Active and Archive Tabs are not properly visible in Shifting Page

Describe the bug
When we open the Shifting Page in Desktop, the Tabs: Active & Archive are not properly visible, making it difficult for the user to switch between them.
To Reproduce
Steps to reproduce the behavior:

Go to Facility Page
Check Active and Archive Tabs
On Desktop view, we can't seamlessly switch between them

Expected behavior
The Active & Archive tabs should appear properly for easy switch between them.
This can be fixed by adjusting the other elements in the same row
Screenshots
This is how it looks on Desktop View ( 100%):

This is how it looks in mobile view:

Desktop (please complete the following information):

OS: Windows
Browser: Chrome
Version: Latest

I'd like to work on this issue, please assign this to me

@nithish1018 which screen size are you finding the UI failing?

@nithish1018 which screen size are you finding the UI failing?

It's a 14-inch screen with 1080p resolution

Can you share a screen recording?

Can you share a screen recording?

Here's the screen recording:
https://github.com/user-attachments/assets/2e2bd4a6-88aa-405b-a4e8-e3901b07a29a

Is the app running on full screen?

Is the app running on full screen?

Yes, it was running on full screen


Service stops automation when calling a non existing tag

Describe the bug
When a tag has been unreachable for some time and Home Assistant is restarted or this integration is reloaded the corresponding entity gets removed. When an automation using the draw custom service is used with a removed/non existent tag entity ID that automation stops running and the following steps are not executed.
To Reproduce
Steps to reproduce the behavior:

Go to automations and create a valid call to the draw custom service and use a non existent tag identity as target. Add a second action after that doing whatever
Click on Run
Click on traces
See that automation does not run beyond the action containing the invalid tag identity

Expected behavior
Have some error handling allowing the next action to run

better error handling will be implemented later today


BOS API spec fixes & one small BOS code fix

Summary and Scope
This PR contains several fixes to the BOS API spec (including one that fixes a customer-reporter problem):

CASMCMS-8447: Update API spec to show that GET of session templates can return v1 or v2 templates
CASMCMS-8572: Update API spec to reflect that creating a BOS v1 session requires operation AND templateName/templateUuid
CASMCMS-8576: Update API spec to reflect that GET /v1/session returns list of IDs not sessions
CASMCMS-8577: Update the spec to accurately reflect what is returned when creating or getting a BOS v1 session
CASMCMS-8626: API spec linting to correct minor errors, omissions, and inconsistencies
CASMTRIAGE-5367: Update API spec to use valid ECMA 262 regular expressions

It also contains one minor fix to BOS itself, so that it returns a valid BOSv2 session template when an example v2 template is requested:

CASMCMS-8585: Return valid BOS v2 session template on GET request to /v2/sessiontemplatetemplate

It also pins the Alpine version in the BOS Dockerfile and specifies the updated Python version in the BOS module setup file, to avoid future surprise changes in the case of CVE rebuilds or similar. (CASMCMS-8628/CASMCMS-8631)
There will be a PR for main that includes these as well, but it isn't ready yet. There are additional changes going into it that aren't being backported, so we're waiting for those to be ready before we pull it all into a single manifest PR. @rbak-hpe  plans to create that later today or tomorrow.
I also noticed in the git log that some files had been updated this year but not had their copyright headers updated, so I made a commit to do that as well.
Issues and Related PRs
Source PRs:

CASMCMS-8447
CASMCMS-8572
CASMCMS-8576
CASMCMS-8577
CASMCMS-8585
CASMCMS-8626
CASMTRIAGE-5367

Testing

The updated API spec was run through an OpenAPI Swagger validation tool.
The updated regular expressions were run through a regular expression tester with various good and bad path inputs.
@jsollom-hpe  deployed the BOS image on a system and tested that it fixed the customer problem being reported.

Risks and Mitigations
Very low risk. Almost all changes are to the spec itself, and are just making the spec match how BOS actually behaves. The one fix to BOS code itself also wasn't even really a code logic change -- it was removing a leftover v1 field from an object definition.
Pull Request Checklist

[X] Version number(s) incremented, if applicable
[X] Copyrights updated
[X] License file intact
[X] Target branch correct
[X] CHANGELOG.md updated
[X] Testing is appropriate and complete, if applicable
[X] HPC Product Announcement prepared, if applicable

We are not planning for new NCN images in CSM 1.3.4 or 1.4.1. If this is really important, we could consider updating it with csm-config plays on the system.


[AppConfig, EventGrid, KeyVault, Tables] Run format

This PR has changes from running rushx format on the below packages. Since the changes were tiny, decided to create 1 single PR :)

App Config
Event Grid
Key Vault
Tables

This is a follow up for #13983

cc @deyaaeldeen


Feature request: after function (or lifecycle hook cmds, more generally)

Description
I am using lint-staged to test and lint everything.  It's great!
I'd like to cut down my deploy times and increase reliability/determinism by including the built artifacts in git, and shipping them as part of the bundle the deploy target receives.  So, instead of doing npm run build && npm start, it'll just do npm start, and the build will already be built.
My initial approach is just to run npm build-prod; git add ./build in a git precommit hook.  That works, but it means I'm also running the build if all I did was update the readme or a test or something.  My next thought was to use a Makefile, so that I could make ./build depend only on ./app, and then the postcommit hook is make build && git add ./build.
But the problem with both of those is that it'll always be running the build based on whatever's in the working directory, not what's staged, so it'll be possible to ship something I really don't intend!  No good!
But then I thought, oh, I could use lint-staged for this, and then only run the build if something changed, and run it in the context of the linted-tested-staged contents.  Beautiful!
Problem is, if I do something like "lint-staged": { "./app/**": "npm run build-prod" }, then it'll run the build multiple times, for every file that was changed, when really I just want it run once at the very end.
So something like: "lint-staged": { "__after": { "./app/**": "npm run build-prod" } }.  Of course, that's confusing if you have a file named __after, so idk what the best approach is there.  Maybe a new top-level field, like "lint-staged-after"?  Another idea would be extending the value of the commands so you could have something like "lint-staged": { "./app/**/*.{js,jsx,ts,tsx,md,mdx}": { "after": "npm run build-prod", "command": "prettier --write" } }. Then if the value is a string or array, it's equivalent to {before:null, after:null, command: <value>}?
It might also be nice to have a before method, so that you can have your tests generate snapshots for each commit as it goes in.  Something like "lint-staged": { "test/**/*.{js,ts,jsx,tsx}": { "before": "npm run snapshot" } }
tl;dr

[ ] Extend the acceptable types of values in the package.json "lint-staged" object from string | string[] to string | string[] | {before?: string, after?: string, command: string | string[]}
[ ] A string or array value is equivalent to {before:undefined, after:undefined, command: value}
[ ] If a before is present in the options for any matched file, then all before methods are run one time each, prior to any lint-staged commands.  If any before command fails, the process aborts, lint failed.
[ ] If a after is present in the options for any matched file, then all after methods are run one time each, after to any lint-staged commands.  If any after command fails, the process aborts, lint failed.

What do you think?  If you would like this, I'd be happy to write a PR for it.

Hello, thanks for the issue. If you think based on my response I understood you wrong, please correct me.
If your use-case is "run a script before/after other commands when certain files are staged", I believe you can already do it using the current config format with arrays:
{
   "./app/**": ["npm run build-pre", "eslint", "npm run build-post"]
}

Given staged files ['app/foo.js', 'app/bar.js', 'app/baz.js'] lint-staged will run, sequentially, using execa:

npm run build-pre app/foo.js app/bar.js app/baz.js
eslint app/foo.js app/bar.js app/baz.js
npm run build-post app/foo.js app/bar.js app/baz.js

The commands are of course free to ignore the argv list. This is to say, I don't think your assumption is true:

Problem is, if I do something like "lint-staged": { "./app/**": "npm run build-prod" }, then it'll run the build multiple times, for every file that was changed, when really I just want it run once at the very end.

Lint-staged should run the command only once, passing all files as arguments to the command. We do check for the "maximum argument length", so if you're on Windows with a more limited terminal client, the command might get split into multiple runs with a huge number of changed files.

I will think about the generic lifetime hook idea more over the weekend, but previously we got rid of "advanced" configuration in order to simplify the user experience, so it would be going against the decision to add something like this.
I wonder if this is something that could be exposed via the Node.js API:
// commit-hook.js

import lintStaged from 'lint-staged'

const passed = await lintStaged({ beforeAll, beforeEach, afterEach, afterAll })

Alternatively, the JS config format would allow exporting entities other than the config itself:
// lint-staged.config.js

export const beforeAll = async (allStagedFiles) => {}
export const beforeEach = async (allStagedFiles) => {}
export const afterEach = async (allStagedFiles) => {}
export const afterAll = async (allStagedFiles) => {}

export default {
  '*.js': async (jsFiles) => [`eslint ${jsFiles.join(' ')}`]
}

Ah! yes, I didn't explain it well.  Probably should have had an example, sorry, was writing it out as I was figuring out myself what I needed 😅
What I want is a sort of "top level" command that is run exactly once in the staged folder, before/after all other commands run, with no arguments, but only if at least one of the files mentioned is touched.
So like if you had this in package.json:
{
  "lint-staged": {
    "*.{js,jsx,ts,tsx,md,mdx}": "prettier --write",
    "*.{ts,tsx}": "tsc -d",
    "!(test)/*.{js,jsx,md,mdx,ts,tsx,json}": { "after": "npm run build-prod" },
    "!(test)/*.{js,jsx,md,mdx,ts,tsx}": { "after": "npm test" },
    "test/*.{js,jsx,ts,tsx}": { "before": "npm run snapshot" }
  }
}

If you modify and add foo.js and bar.ts, then it'll run:
pretter --write foo.js bar.ts
tsc -d bar.ts
npm test
npm run build-prod

If you stage test/foo.ts and lib/bar.js, then it'll run:
npm run snapshot  # the "before" match for test/foo.ts
prettier --write test/foo.ts lib/bar.js
tsc -d test/foo.ts
npm test
npm run build-prod

So it's like,

Run all the before commands for any matched files, without any arguments.
Run all the task commands for all matched files, with filename arguments.
Run all the after commands for any matched files, without any arguments.

You should be done with all the before functions before any of the "main" tasks run.  All "main" tasks should be done before any after functions run.

Thanks for the extra info, I now understand that multiple before/after commands should still run before/after all other configured tasks; it makes sense since their purpose is to do side-effects.
I wonder if this could be done in the commit hook outside lint-staged itself, for example in bash:
if [[ $(git diff --cached --name-only -- '*.js') ]]; then
  npm run build
endif

I wonder if this could be done in the commit hook outside lint-staged itself, for example in bash:

That's more or less how I'm doing it now, but the challenge is that it builds in the working dir, and lint-staged has all the cleverness of checking it into a temp dir and whatnot.  So at least a naive approach of running the command if the file is changed, will result in building all changes in the working dir, not just the staged changes, so the code in the commit won't match the build in the commit, making bisects busted.

Oh, looking at the code, I guess it doens't check into a temp dir, it just stashes and re-applies partially chnaged files.


random: rand32_ctr_drbg: Fix missed device constify change

Device constify PR missed changes needed within the mbedtls conditional code.
Fixes #28033
Signed-off-by: David Leach<EMAIL_ADDRESS>

@tbursztyka pls take a look once more


Try to use distribution support to validate params in smcabc

Resolves #504
Issue above contains the justification for the current change, though further feedback/changes/rejections are welcomed!

Closing because this is better resolved by #506.

Thanks @atiyo for suggesting this fix. We have been dealing with the change in pytorch API by introducing a function within_support instead of using torch.isfinite(log_prob). #506 uses this instead of your fix.
But thanks a lot for your contribution, much appreciated!


Add meta tags for cronos docs

Adding meta tags in cronos docs for better seo performance

Thanks! Good to merge! Later I will update the package version and add the caconical link~


Bookmarks in SQL Editor

When working with long list of code (two screens or more) in SQL there is no posibillity to set a bookmark near the row number. Navigation between bookmarks is very convenient, no need to scroll and scroll and scroll... code.

This bookmarks for database navigation, not for sql editor navigation.

Example from plsql developer.
I need to navigate from one code row to another.

You can also use it in the sql editor.
But there seems to be no pop-up menus or buttons.
At first, hot keys are set so that you can use them.

I recommend installing the plugin.
This plugin is an eclipse plugin but works fine in dbeaver.
https://marketplace.eclipse.org/content/quick-bookmarks-plugin#.U9p6nEThGlM

duplicate of #3416


[SPARK-1517] Refactor release scripts to facilitate nightly publishing

This update contains some code changes to the release scripts that allow easier nightly publishing. I've been using these new scripts on Jenkins for cutting and publishing nightly snapshots for the last month or so, and it has been going well. I'd like to get them merged back upstream so this can be maintained by the community.
The main changes are:

Separates the release tagging from various build possibilities for an already tagged release (release-tag.sh and release-build.sh).
Allow for injecting credentials through the environment, including GPG keys. This is then paired with secure key injection in Jenkins.
Support for copying build results to a remote directory, and also "rotating" results, e.g. the ability to keep the last N copies of binary or doc builds.

I'm happy if anyone wants to take a look at this - it's not user facing but an internal utility used for generating releases.

Merged build triggered.

Merged build started.

Test build #37307 has started for   PR 7411 at commit d28c240.

Test build #37307 has finished for   PR 7411 at commit d28c240.

This patch fails RAT tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class Exchange(newPartitioning: Partitioning, child: SparkPlan) extends UnaryNode

Merged build finished. Test FAILed.

Aw, looks like this conflicted with some recent Maven changes.

Yeah I need to update this - but it's off the critical path for the release
so it's on hold.
On Sat, Aug 1, 2015 at 10:59 AM, Josh Rosen<EMAIL_ADDRESS>wrote:

Aw, looks like this conflicted with some recent Maven changes.
—
Reply to this email directly or view it on GitHub
https://github.com/apache/spark/pull/7411#issuecomment-126942487.

Jenkins, test this please.

Merged build triggered.

Merged build started.

Test build #40321 has started for   PR 7411 at commit 233ce85.

Test build #40321 has finished for   PR 7411 at commit 233ce85.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #40327 has started for   PR 7411 at commit 74f9beb.

Test build #40327 has finished for   PR 7411 at commit 74f9beb.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Jenkins, retest this please.

Merged build triggered.

Merged build started.

Test build #40397 has started for   PR 7411 at commit 74f9beb.

Test build #40397 has finished for   PR 7411 at commit 74f9beb.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Jenkins, retest this please.

Merged build triggered.

Merged build started.

Merged build finished. Test FAILed.

Jenkins, test this please.

Merged build triggered.

Merged build started.

Test build #40463 has started for   PR 7411 at commit 74f9beb.

test

Test build #40463 has finished for   PR 7411 at commit 74f9beb.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Jenkins, retest this please.

Merged build triggered.

Merged build started.

Test build #40500 has started for   PR 7411 at commit 74f9beb.

Test build #40500 has finished for   PR 7411 at commit 74f9beb.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Okay will merge this - I've been keeping things in a separate repo and it's much better to have it in the upstream in case others want to modify it.


Minor fixes. Contrb to #1634

As per issue #1634 if there is an embedded method in Umple code that is uncompilable, Javadoc can not be generated and the UmpleOnline feature to generate javadoc would fail and display a 404 message.
This PR fixes that by displaying a sensible message. It also displays the actual syntax error. However, currently it does NOT display the Umple line where the syntax error occurred. That would require extra work (compiling with -c - will map the java error number to the umple line number, but javadoc doesn't do that). So there is more work to deal with #1634 properly, but this will at least avoid the confusion that currently results.
The 404 message was also misleading, so it is fixed here too. It referred to Models 2015, and needed updating.
A glitch in a manual page from a recent PR is also fixed.

It turns out that newer versions of Javadoc are less sensitive to bad methods, so this issue solves a problem that may no longer occur in recent java versions. Nonetheless it does no har,


Migration configuration changes

Two things I noticed as I updated my local site to drupal 9 this week.
migration_tags is now an array (this applies to a migration in islandora and in islandora_defaults)
Also, I flubbed on the update_hook in Islandora in the D9 PR to update the source keys to source ids.
I will have PRs for these.

PRs merged. 👍

PRs merged. 👍


More verify updates

Description:
This is another set of updates for #1515.
Changes (so far):

Don't include empty verification-related fields in serialized output
Validate verify config with go generate ./...

Checklist:

[ ] Does your PR pass tests?
[ ] Have you written new tests for your changes?
[ ] Have you lint your code locally prior to submission?

The latest commit is non-functional so I'll switch this back to a draft.


Unify ssl3_get_cipher_by_std_name() implementation

The handling for the SCSVs was the same as for regular ciphers;
just merge them into the same table-driven handler.

This PR is in a state where it requires action by @openssl/otc but the last update was 30 days ago

This pull request is ready to merge

Removing the 1.1.1 label, as this is not a clean cherry-pick.  I will try to remember to open a new PR for the backport.

This was already merged.

This was already merged.


fixed calibrator for CAN device

This PR fixes the calibrator for CAN devices on these robots :

iCubGenova06
iCubNancy01

Hi @pattacini !

I can still see the use of parametricCalibratorETH on the other parts of the robot iCubNancy01. Could you fix them as well?

The other parts are equipped w/ EMS so I thought that was right to leave Eth  , only the head is CAN based.
Isn't it?

Also, given that this is a fix, would you mind rebasing your PR against the upstream master instead of devel?
Sure

The other parts are equipped w/ EMS so I thought that was right to leave Eth , only the head is CAN based.
Isn't it?

I don't know actually. I assumed it was a full CAN robot. If you confirm that the other parts are ETH based, that's ok!


Update README

Update the README file to show an animation for the new GitterCLI layout for messages.

Please. Help me how can active. My bitcoin @wallet address.

How to send msg? I can display list but have to select and start a chat?

Hi @jinfagang, this project has not received a lot of love lately (my fault), but the command to join is gitter-cli join <roomName> for example gitter-cli join gitterHQ/gitter.


Empty GFA (and temporary file delete error)

First of all, cool tool!
We're trying it to run for a large collection of genomes and first built the k-mer database using:
kmc -k31 -m450 -fm -t30 -ci0 @paths.txt test_graph .
And then ran cuttlefish:
cuttlefish build -k 31 -s test_graph -o cuttle_graph -f 2 -t 30
This is the corresponding output:

Constructing the minimal perfect hash function.
Total number of k-mers in the set (KMC database):<PHONE_NUMBER>.
Building the MPH function from the k-mer database test_graph
for info, total work write each  : 2.649    total work inram from level 4 : 5.479  total work raw : 25.000
[Building BooPHF]  36.5 %   elapsed:  16 min 2  sec   remaining:  27 min 54 sec
Completed a pass over the k-mer database.
[Building BooPHF]  75.5 %   elapsed:  22 min 17 sec   remaining:   7 min 15 sec
Completed a pass over the k-mer database.
[Building BooPHF]  100  %   elapsed:  34 min 33 sec   remaining:   0 min 0  sec
Built the MPH function in memory.
Total data copy time to BBHash buffers 1596.47
Total MPH size (in MB): 4258; in bits / k-mer: 3.70962
Allocated hash table buckets for the k-mers. Total memory taken (in MB): 5740
Total memory usage by the hash table: 9999 MB.
Bits per k-mer: 8.70962
Done allocating the hash table. Time taken = 2083.64 seconds.
Classifying the vertices.
Processed 0 sequences. Total reference length is 0 bases.
Maximum buffer size used (in MB): 0
Done classifying the vertices. Time taken = 0.00212339 seconds.
Outputting the maximal unitigs.
Temporary path file name prefixes: ./cuttlefish-path-output-SoO15XQt3S
Processed 0 sequences. Total reference length is 0 bases.cuttlefish build -k 31 -s test_graph -o cuttle_graph_text -f 0 -t 30
Maximum seqeunce buffer size used (in MB): 0
Error deleting temporary files. Aborting

The resulting GFA file only has the header (H       VN:Z:2.0) any idea what's going wrong here? When using the default output (0) there is no temporary file error however the output is also empty

Hello @rickbeeloo,
Glad that you found Cuttlefish useful! About the empty output issue, I see that you did not provide any reference files to the build command; although, the reference file(s) are required by Cuttlefish. Theoretically, Cuttlefish compacts an edge-centric de Bruijn graph, and needs the (k + 1)-mers from the input to work with; and that is why the references are required. Cuttlefish accepts the input reference collection in three format (-r, -l, -d). And since it is possible to input the collection mixing these parameters, we kept the parameters optional. Although, we should add an empty input collection checker so that the build process warns the user of the issue.
In brief, I see that you built the KMC database over a list paths.txt of references. So, you should add -l paths.txt to the parameters list in the cuttlefish build command, and it should work. Please let us know if this fixes the problem, and if yes, then please close the issue.
On a different note, this issue emphasizes that we need to have a some toy example of the full build pipeline to help users interpret the parameters correctly. Thanks for the issue. Regards!

Hi,
I have a related question: how to you see "colors" in the final gfa1/gfa2 output?
I ran cuttelfish with -l paths.txt, successfully producing a large gfa file. How can we know that a given segment is specific or shared among references?
Thanks!

Hi!
I'm paraphrasing @rob-p on this:

We did struggle a bit regarding the best terminology here (for "colors").  Since cuttlefish isn’t an index, nothing is indexed per-se (specifically, we don't associate the color-information with each segment). When we build the compacted graph over multiple references, we consider it colored in the sense that the color information is encoded in the P (GFA1) or O (GFA2) entries.

To answer your query on how to know if some segment with id x is shared among multiple references or not — each reference has a corresponding path-tiling in the GFA format (withthe tag P or O based on the version), and x is present in those references whose path contain the id x.
Regards!

Thanks for the question @EA2106-Universite-Francois-Rabelais!
Relatedly, it would be possible in a post-processing step to build an index that would let you query with a contig (segment) and return the reference list in which that segment occurred.  Would this type of index be useful to have in your use case?  If so what would an ideal interface look like for this functionality?

@jamshed-k @rob-p  I would love to extend a little bit on this. It depends on what @EA2106-Universite-Francois-Rabelais means with "segment". If this is the S tag in the GFA this would be relatively straightforward as @jamshed-k  points out. However this gets more complicated when we are interested in finding large shared sequences (i.e. multiple segments between genomes), such as:
G1: S1, S2, S3, S4
G2: S0, S2, S3, S10

Then it would be cool to get a list saying S2, S3 found in G1 and G2 (with ideally the positions too). This can be defined as the maximum continuous frequent itemset problem in pan genome graphs (see this paper more detail). To find such shared regions we have tools such as Sibelia, SibeliaZ and FindFRs. For our dataset, consisting of diverse bacterial genomes, we find large blocks using Sibelia but it's terribly slow, SibeliaZ is fast but produces much shorter blocks. FindFR on the other hand is super fast and allows us to tolerate insertions but unfortunately cannot be used with the output of recent tools (see my discussion here)

Thanks @rob-p , @rickbeeloo  & @jamshed-k  for the interesting discussion. I am new to the gfa file formats and looking for ways to extract relevant biological information. I agree with @rickbeeloo regarding the access to a list of shared segments. I suppose that an index as suggested by @rob-p  may be useful to quickly  create these lists. I also wondered if this kind of index could be used to further read mapping from resequencing data? E.g. if you want to compare variation from a new individual to the graph constructed from the reference individuals?
Thanks for the support!


[CI] Android Builds

I feel as though it would be wise to start producing Android builds via Github Actions.
I personally dislike installing the Android SDK/NDK on my own machine, as it leaves residual files everywhere (and I'm using FreeBSD, so it might be a challenge). Github Actions has this pre-installed, so we may as well use it.
I can get this set up shortly.

Turns out this is a lot harder than I first thought.

Might have to put this one on the backburner for now.


docs app

the docs app refer to a non existing package: urigo:angularmeteormarkdown

it is a local package in the packages directory
I leave it there because it's not the best implementation...

I think I figured out the issue. Windows cannot create a folder with colon, hence "urigo:angularmeteormarkdown" is failing.

I embedded the markdown directive directly in directive and removed the package. Not that great. Let me know if I should make a PR for it.

yes, if that make the site work on Windows then please do!

well, I fail to do it because of the above errors (and probably some lack of github knowledge). Either you can rename the directory to avoid the colon (if that is possible for packages, proabably is, as other packages did not have this issue), or just embed the markdown.js under the directives directory and remove the package from packages.

To fix the problem when cloning the repo on Windows, I simply replaced "urigo:angularmeteormarkdown" with "urigo-angularmeteormarkdown".
Would that be ok? Should I make a PR?

@cedric25 yes of course!

Thanks!


Add onSubtractTime and onAddTime hooks

Description
Implement hooks for onSubtractTime and onAddTime.
Motivation and Context
This could be used to dynamically load selectable dates for each month.
Checklist
[ ] I have added tests covering my changes
[x] All new and existing tests pass
[x] My changes required the documentation to be updated
  [x] I have updated the documentation accordingly
  [x] I have updated the TypeScript 1.8 type definitions accordingly
  [x] I have updated the TypeScript 2.0+ type definitions accordingly

I have ran build but it seems to have updated more than only my changes in the dist folder.

Hi @DaanDD and thanks for contributing! Your code is changing a critical part of the component but you didn't write any tests. I would like to see some tests that verifies that it's working as you want it to work.
Also, no need to update the dist files. We do that when we release a new version, please remove them from your PR. Thanks!

Hello, thanks for the feedback! I have removed the dist files and added some tests.

@simeg I have changed the hook names. onSubtractTime and onAddTime are now called onNavigateBack and onNavigateForward

Looks good 👍 Thanks for contributing!

I am trying to call "onNavigateBack" and "onNavigateForward" both are not working.  "onViewModeChange" is working well.
<Datetime input={false} timeFormat={false} onChange={this.updateDate.bind(this)} renderDay={ this.renderDay } onViewModeChange={this.dateViewMode.bind(this)} onNavigateBack={this.dateNavigate.bind(this)} onNavigateForward={this.dateNavigate.bind(this)}/>

It worked for me If I install this package like  npm install  --save  YouCanBookMe/react-datetime