Uncaught RangeError: Maximum call stack size exceeded in backend.bundle.js

Hi recently I got this error when I open my react app in development mode:

It seems this function S has been called in an infinity loop

Perfomace record:

More details:
React v17.0.2
Redux v4.0.4
redux-thunk v2.3.0
React-Redux v7.1.0

Same problem.
Reactime
11.0.0
React Developer Tools
4.21.0 (10/31/2021)
Gatsby 3.14

same on Nextjs setup

I have proposed a fix for this in #257.  It seems to work fine for me.  Would be great if others could test it and report back here.  If you don't know how, please see #255 (and also #253, #254).

same error made me lost a lot of time. i thought something was wrong with my code but it was the extension. plz fix it. i'll disable it until then :)

same error made me lost a lot of time. i thought something was wrong with my code but it was the extension. plz fix it. i'll disable it until then :)

Same

Or you could try the fix I proposed above ;-)

This error is still happening for me, makes the extension unusable, unfortunately. I'm using Next.js 12.2 and React 18. If @aspiers has a fix, why not implement it?

Implemented a depth limiter in v17.0 that should now fix that issue!

Implemented a depth limiter that should now fix this issue in v17.0.0!

@jemzir I submitted a depth limiter fix in 2021 (see #257 as mentioned above) but it seems like no one reviewed it yet.  It would be really nice if all the fixes I submitted a long time ago could be reviewed - perhaps then you could save time having to duplicate the same fixes yourself.  There are 5 PRs I submitted which are still open.  Thanks for your consideration!

Hi @aspiers, we did actually implement that fix in this release! You're contributions were incredibly clutch, sorry it took the team so long get around to implementing them! We're going to be closing the corresponding PRs to the solutions we managed to implement this release shortly. Thanks again so much!

Glad to hear you've found them useful :-)  But I'm a bit puzzled why there was any need to reimplement this fix I submitted instead of just merging it?  I submitted the fix in #257 on Dec 11 2021, and I see that the exact same code change was committed a year later in fdb65c58e, without my name or email as the git committer, and without the explanation I took the time to write in my commit message.  Meanwhile #257 has gone over two years without any feedback at all.
Apologies if this sounds a bit petty, especially since I know this is a tiny code change - but it's the principle behind it which I want to highlight.  TBH it's a bit demoralising when I go to the effort of implementing a fix and even documenting it nicely, and then it gets reimplemented without any trace in the git history of my contribution.  In that kind of scenario, there's no evidence that I saved anyone else's time, or that I didn't waste my own.  Please don't get me wrong - I'm quite sure there was zero ill intentions here!  And also I know how hard it is to find spare time to maintain F/OSS projects; I do it myself, and sometimes I don't do a great job, so I can't even claim to fully practice what I preach.
But if you want to keep encouraging contributions from the wider community, as much as possible I'd recommend trying to give contributors the satisfaction of seeing our commits merged into the git history.  I don't ask for anything else, but that feeling of having proof I contributed is a little feel-good kick which motivates me to do it in the first place, and I'm pretty sure a lot of other F/OSS contributors feel the same :-)
Hope that makes sense, and thanks for listening!


XML Attributes for Bars are not accessible

Hello,
looks like the following atributes can't be accessed from XML even with namespace change.
     <attr name="bar_length" format="dimension" />
     <attr name="bar_pointer_radius" format="dimension" />
     <attr name="bar_pointer_halo_radius" format="dimension" />
     <attr name="bar_orientation_horizontal" format="boolean" />

The Wheel attributes are accessible.
I'm using the maven repository.
Thanks!

Sorry for the late response but its fixed in the current version, (Please reopen if it still occurs with you)


Is it possible to boot up raspberry-pi-os from Uboot?

I want to use tftpboot instead of copying the binary to sdcard each lesson so I curious that is there someone trying to boot up raspberry-pi-os from Uboot?

@rhett511 , I created a project to boot via UART with a few changes to the kernel in this project. I wrote a detailed blog post on what I did and mistakes I made along the way. I've made a few improvements since then. Feel free to take a look at the source.
I hope this helps.

Hi @nicolasmesa,
Thank you for responding to me.
However, I want to use u-boot instead of writing my own bootloader code.
I found the answer to this question.
U-boot finds the kernel image with the special format. And we can create it by mkimage tool that supported by u-boot:
MKIMAGE?=~/workspace/u-boot/tools/mkimage
$(MKIMAGE) -A arm64 -C none -O linux -T kernel -d $(BUILD_DIR)/kernel8.img -a 0x80000 -e 0x80000 $(BUILD_DIR)/kernel8.uimg
I close this issue.


SSL Config for Ruby is wrong

If you see the page https://github.com/brianmario/mysql2#ssl-options the SSL options for the mysql2 client are different. I can't manage to connect to the database using only the ssl ca so I needed to disable ssl in order to use on my rails application.

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

ID: 51acac74-aeca-592f-0e61-1bd363a617c2
Version Independent ID: e1322cb7-4d6a-7a26-7ca0-cf0a30302a1d
Content: Configure SSL - Azure Database for MariaDB
Content Source: articles/mariadb/howto-configure-ssl.md
Service: mariadb
GitHub Login: @ajlam
Microsoft Alias: andrela

@rhuanbarreto We are checking this and we will get back to you.

@rhuanbarreto The document does mention that using the options mentioned may give you error and you need to add the sslmode option as well to the code. Have you tried this:

@rhuanbarreto Please verify if you were able to check the above or not.

You are moving the discussion to the wrong way. There is nothing to do with mysql CLI. It's about the mysql2 gem
On mysql2 gem in github:
Mysql2::Client.new(
  # ...options as above...,
  :sslkey => '/path/to/client-key.pem',
  :sslcert => '/path/to/client-cert.pem',
  :sslca => '/path/to/ca-cert.pem',
  :sslcapath => '/path/to/cacerts',
  :sslcipher => 'DHE-RSA-AES256-SHA',
  :sslverify => true,
  )

On the doc page:
Ruby
client = Mysql2::Client.new(
        :host     => 'mydemoserver.mariadb.database.azure.com',
        :username => 'myadmin@mydemoserver',
        :password => 'yourpassword',
        :database => 'quickstartdb',
        :ssl_ca => '/var/www/html/BaltimoreCyberTrustRoot.crt.pem' # pay attention to this line. This is not the same as the mysql2 gem docs
    )

@ajlam Please check into feedback from user and help us regarding the same.

@rhuanbarreto, were you able to connect after updating to "ssl_ca" instead?

No. I will try to set up a demo with the error message

If you can set up a test mariadb instance, I can make an example on repl.it and show you the error

@rhuanbarreto - sure, here's connection info for a server I've created that has SSL enabled.
hostname: mariadb-test-github.mariadb.database.azure.com
admin username: admintest@mariadb-test-github
For the password, would you be able to email me at<EMAIL_ADDRESS>

I managed to configure a rails application to connect using the following parameters:
The certificate is on the root of the application.
default: &default
  adapter: mysql2
  encoding: utf8mb4
  pool: <%= ENV.fetch("RAILS_MAX_THREADS") { 5 } %>
  username: username@mydatabase
  password: pleaseChangeYouPasswordHere
  host: mydatabase.mariadb.database.azure.com
  sslca: BaltimoreCyberTrustRoot.crt.pem
  sslverify: true

But I need to have ssl enforced on the DB so I can do some further testing.

This is what I'm using through pure Ruby and not through Rails.
require 'mysql2'

begin
     # Initialize connection variables.
     host = String('myserver.mysql.database.azure.com')
     database = String('testdb')
     username = String('myadmin@myserver')
     password = String('mypassword')

    # Initialize connection object.
    client = Mysql2::Client.new(:host => host, :username => username, :database => database, :password => password, :sslca => 'BaltimoreCyberTrustRoot.crt.pem', :ssl_mode => :required)

end

Hi @rhuanbarreto, were you able to test with the server provided?

Yes. can put the server down. You could improve the docs with a rails DB config section like I did in addition to fixing the sslca parameter.


test(ui): add popover position workshop

We have one or more issues in the Sanity Studio where the position of the reference element of a popover changes due to external factors that doesn't trigger a reposition. Floating UI will listen for viewport resize or scroll events, but have a update method exposed by the useFloating hook for manual updating in those cases where the built-in detection isn't enough.
An example of this issue is when panes is toggled in the Sanity Studio. The actual viewport size didn't change, and there was  no scroll events, so the popover will end up misaligned.
This issue can be replicated in the Popover/Position story inside the workshop in this PR.
This PR adds a context for Popover, and exposes a forceUpdate method via a new hook called usePopover that allows consumers to trigger an update.
It also adds a hook called useOnForcedUpdate to be used inside the  popover component, that will trigger the update.. This should not trigger any errors if you are not using the popover inside a Popover context.
Questions:

Does the forceUpdate name make sense, or should we call it something else?

[sc-32108]

I suggest that we implement a fix only in the popover component, and without introducing a new React context. By doing so, users won't have to figure out that they need to use a force update function from usePopover when using popover with referenceElement.
A solution that I think works well is to set up a ResizeObserver when referenceElement is present. In the callback, we call the update function from useFloating. With this approach there is no need for a new React context and no additional logic is required to reposition the popover when used with referenceElement.

@hermanwikner The autoUpdate middleware already does this. The problem in this case is that the reference element, in this case the PTE, doesn’t change its size. There will be less or more whitespace around the PTE, but the size doesn’t change.


⚠ Bofrost.at has degraded performance

In 48b1f0c, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2587 ms

Resolved: Bofrost.at performance has improved in e51fe47 after 6 minutes.


Seconds indicator

[x] Add configurator screen to select second indicator style (none / dashes / dot)
[x] Do not render at high refresh rates when no seconds indicator is shown
[ ] Support square screens
[ ] Move complications inward only when seconds are visible
[ ] Do not render at 60fps on devices with 30fps screens if possible

There are only 2 targetted wearOS3 watch models (by Oppo) that have rectangular screens, with 0 active users currently. For that reason, any modifications to support such watches will be minimal, if any, to help focus on other features.

4 hours down the drain 🙈

Released on open testing: v2.9.6-beta1

Released in v2.9.8 (prod). See CHANGELOG.md for details.


Backspace character '\b' in Serial output

I'm trying to run a "spinner" in the serial output when my sketch is idle. This should output one of the '|' '/' '-' '\' characters on each loop with a backspace '\b' after the character.
When I try this with my sketch and TyCommander 0.9.7-2-g2475490 I get, what I assume is, a notofu symbol between the characters instead of the backspace.
Is the backspace character in the serial output a problem with TyCommander or a problem with the Serial print stuff in Arduino?
If it matters I'm doing this with a Teensy 4.0 board, Arduino 1.8.13, and Teensyduino 1.53. I'm trying this on an Ubuntu 18.04.6 LTS system.

Most GUI apps do not support the backspace control character, unlike terminal emulators (I guess).
But it could be useful so I'll look into it over the weekend ;)


[CT-3400] Document testing best practices in CONTRIBUTING.md

Examples:

one test method per class
additional, more precise assertion after using expect_pass=False with run_dbt
avoid asserting on specific things, not like '1.0' in message

some notes from things we've seen in adapter land pulling in tests.
our general teardown method defined for testing doesn't catch any default value schemas so any changes currently to schema, database, or the identifier from initial test initialization are not caught and require clean_up methods added to the test see prs like https://github.com/dbt-labs/dbt-core/pull/9195 for example where we have some changes to alt databases or modify the test_schema name.
not doing this leads to hanging artifacts that slowly build up and and causes the test databases to reach limits (typically around 10K for us) and cause all tests to fail. till items are dropped.


ember g --lazy=true in-repo-engine fails

leaving this here for later investigation:
 ember g --lazy=true in-repo-engine                                                                                (772ms)
Cannot read property 'enabled' of undefined
TypeError: Cannot read property 'enabled' of undefined
  ¦ at Class.findHost [as _findHost] (/Users/spenner/src/sass-eyeglass/ember-cli-eyeglass/node_modules/ember-engines/lib/engine-addon.js:71:29)
  ¦ at Class.options.init (/Users/spenner/src/sass-eyeglass/ember-cli-eyeglass/node_modules/ember-engines/lib/engine-addon.js:534:40)
  ¦ at Class.superWrapper [as init] (/Users/spenner/src/sass-eyeglass/ember-cli-eyeglass/node_modules/core-object/lib/assign-properties.js:34:20)
  ¦ at new CoreObject (/Users/spenner/src/sass-eyeglass/ember-cli-eyeglass/node_modules/core-object/core-object.js:9:15)
  ¦ at new Class (/Users/spenner/src/sass-eyeglass/ember-cli-eyeglass/node_modules/core-object/core-object.js:21:5)
  ¦ at new Class (/Users/spenner/src/sass-eyeglass/ember-cli-eyeglass/node_modules/core-object/core-object.js:21:5)
  ¦ at graph.each (/Users/spenner/src/sass-eyeglass/ember-cli-eyeglass/node_modules/ember-cli/lib/models/addons-factory.js:58:19)
  ¦ at Vertices.each (/Users/spenner/src/sass-eyeglass/ember-cli-eyeglass/node_modules/dag-map/dag-map.umd.js:197:13)
  ¦ at Vertices.walk (/Users/spenner/src/sass-eyeglass/ember-cli-eyeglass/node_modules/dag-map/dag-map.umd.js:125:14)
  ¦ at DAG.each (/Users/spenner/src/sass-eyeglass/ember-cli-eyeglass/node_modules/dag-map/dag-map.umd.js:68:24)
An error occurred in the constructor for eager at /Users/spenner/src/sass-eyeglass/ember-cli-eyeglass/lib/eager
An error occurred in the constructor for ember-cli-eyeglass at /Users/spenner/src/sass-eyeglass/ember-cli-eyeglass

Hmm, it seems to be post generation of ember g in-repo-engine eager all commands are dying. May be specific to ember-cli-eyeglass...

Ah, I think it my be an issue with the generators running within an add-on.
Steps to reproduce:
ember addon test-addon
cd test-addon
yarn add --dev ember-engines
ember g in-repo-engine the-engine
ember h // explosions

I'm curious if allowing regular EmberCLI addons to include in-repo-engines is something that is intended to work?
This doesn't blow up if the in-repo-engine is installed within an engine addon rather than within a regular EmberCLI addon.
ember new test-engine -b https://github.com/ember-engines/engine-blueprint.git
cd test-engine
yarn add --dev ember-engines
ember g in-repo-engine the-engine
ember h // works


Support nighthawk in mesheryctl system start, stop, and restart commands

Notes for Reviewers
This PR fixes #10371
Hi, I've included nighthawk adapter in mesheryctl system commands - start, restart, stop. Both platforms, docker and Kubernetes, are considered.
Signed commits

[x] Yes, I signed my commits.

Hi @leecalcote, @gyohuangxin,
I submitted this PR to fix the issue 10371. Can you please review the PR?
I've included the Nighthawk adapter in mesheryctl system commands - start, restart, stop.
In the issue, it also suggests to support this adapter in mesheryctl system context create --components, which I found that I don't need to do any modification. From my understanding, it's the user who could provided this adapter through the command mesheryctl system context create context-name --components meshery-nsm --platform docker --url http://localhost:9081 --set --yes, and the input components will be added to the context's components list and apply to err := config.AddContextToConfig(args[0], tempCntxt, viper.ConfigFileUsed(), set, false).  Please let me know if I missed anything.

Thank you @KunyueXing
Let's discuss this PR on Meshery development call today. Adding it as an agenda item to the meeting minutes.
Timing: 9:00 AM CT
Meeting minutes: Google Docs
Meeting link: meet.layer5.io/meshery

Hi @vishalvivekm, the meeting is held at 7am at my local time and I'm not able to attend it. Could we adjust the meeting time so that it could be more convenient for people in pacific time to join?

Thank you @KunyueXing, let's discuss this PR during the Meshery dev meeting call, if you would. Adding it as an agenda item to the meeting minutes.
Timing: 7:30 PM IST / 9:00 AM CT (Wednesday)
Meeting minutes: Google Doc
Meeting link: meet.layer5.io/meshery


Update -  fixing typo form.js

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #206
Test URLs:

Before: https://main--elixirsolutions--hlxsites.hlx.live/
After: https://form-typo-patch--elixirsolutions--hlxsites.hlx.live/

use this form to test
https://form-typo-patch--elixirsolutions--hlxsites.hlx.live/plansponsors/pharmacy-benefit-management/employers


Added my Fav Playlist

This playlist is not made by me, but this is one of the playlists I've been hearing for the past 4 years<3. Feel free to check it out

thanks for contributing @SachXD

<3


Download counter broken

I opened this issue, as #584 is closed.
The download counter is broken again, compare https://www.nuget.org/packages/OPTANO.Modeling
0 total downloads, but 34 of current version? that's odd.
https://status.nuget.org/ is all green. Is this issue already known?
Thanks!
jp

Well. It's back to normal today. Thanks!


chore: Ensure that inquire sale message is not shown in the grid

This PR resolves AMBER-725
Description
If the partner has the new price display flag enabled, we hide the saleMessage from the artwork grid.
Solution submitted by @Mitch-Henson
Before

After

PR Checklist

[x] I have tested my changes on iOS and Android.
[x] I hid my changes behind a feature flag, or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
[x] I added an app state migration, or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

Do not show the sale message in case of artworks with a price display set to "inquiry about availability"

iOS user-facing changes

Android user-facing changes

Dev changes

Need help with something? Have a look at our docs, or get in touch with us.
@artsy/amber-devs

This PR contains the following changes:

Cross-platform user-facing changes (Do not show the sale message in case of artworks with a price display set to "inquiry about availability")

  Generated by :no_entry_sign: dangerJS against 406f6cb729d2b2632ac3f1401a8d1092d830dee6


Enabling non-sha pins for whitelisted repos+actions

Testing steps:
Build the code with:
npm install
ncc build src/index.js -o dist --source-map --license licenses.txt

And then run the code with:
      - name: Ensure SHA pinned actions
        id: sha-pinned
        uses: nackerman-nydig/github-actions-ensure-sha-pinned-actions@nackerman/whitelist-v2
        with:
          white-listed-actions: |
            aws-actions/
            docker/login-action

and
      - name: Ensure SHA pinned actions
        id: sha-pinned
        uses: nackerman-nydig/github-actions-ensure-sha-pinned-actions@nackerman/whitelist-v2

Seems to be working.

However, there appears to be a regression since the last release. Now, this action is erroring on local actions. for example:
      - name: Ensure SHA pinned actions
        uses: zgosalvez/github-actions-ensure-sha-pinned-actions@8877889a5717dad0b139f1d2925689aa68f88a43

Correctly doesnt error for local actions, however
      - name: Ensure SHA pinned actions
        uses: zgosalvez/github-actions-ensure-sha-pinned-actions@7692976b7529253c9610ff3242b2693d678847b0

Will error on my local action -> Error: ./.github/actions/prepare is not pinned to a full length commit SHA.

@zgosalvez

@zgosalvez, I'd love if this were addressed, since we specifically whitelist actions, aws-actions, and our own organisation, and I think this pattern is quite common.


Issue with seeds + inc parameter

Hi. If you fetch this data:
https://randomuser.me/api/?results=10&seed=foobar
The first name is Miss Britney Sims and the last Mrs Addison Ross
But if you add the "inc" parameter, the data is different
https://randomuser.me/api/?results=10&inc=gender,name,email,nat&seed=foobar
The first name is Miss Britney Sims and the last Mrs Evelyn Lane
Is this an issue or is this normal? Because i want to export less data than the one i use on my page, and is not the same
Thanks!

Seed is kind of finicky in that it requires the exact same parameters that were provided to it when it generated the dataset.
For example, you can use the same seed foobar but specify one with nat US and another with nat AU. Both of the datasets will be different from each other, but the same datasets will be returned if you use the same seed and same parameters (nat).
This behavior is expected but admittedly wasn't the original intention.


Issue connecting to a Mongo server through an ssh tunnel on a mac

Hi,
I'm currently trying to connect to a mongo server using the ssh tunnel option, but when I attempt to connect, the button just shows a spinner forever.
I'm using key based authentication for the ssh part, and have manually entered the path to my key file:
/Users/MyUsername/.ssh/id_rsa
I've also tried copying this file to my desktop and using the file picker to select it.
Then in the connection 'hostname' I'm using "locahost", as that's what it is after the ssh tunnel.
Could you tell me how I access the log files for this application on my mac please? That may give me some clues as to why it's not working. I've been through the source to try and work out where the log files live, but thought it maybe best to ask the experts!
Thanks a lot,
Neil

Hello Neil,
thanks for trying mongoclient, currently there's no way to see log details in distributions, meteor has some issues with electron and for each release I have to build mongoclient manually at every platform. It's really annoying and couldn't have a chance to find a way to transport logs currently. You can try to compile as a web application and try it like that, then you'll able to see logs.
Apart from that, you shouldn't write file path manually, you have to pick it from file dialog, I'm able to connect via SSH tunnel currently.
 And make sure your SSH port and username is correct.
Btw how big is your key file ? Maybe there's something wrong with the upload process.
Cheers,

Thanks for the reply, I'll try and set it up locally to see if the logs are spitting anything out.

Hi Sercan
I work with Neil and I'm wondering if we're getting something wrong with the key files.
We can connect fine via ssh, using the id_rsa key, but I've had a read around some issue some others have mentioned using a .pem file.
Here's my key details
-rw-------    1 mjdavies  staff   1675 21 Jul  2015 id_rsa
-rw-r--r--    1 mjdavies  staff    415 21 Jul  2015 id_rsa.pub
I'm having the same issue as Neil.
We just add the contents of users .ssh/id_rsa.pub file to the authorized_keys file, and use a non standard port with only key access, no logins allowed.
Im' wondering if it's our setup that is causing an issue.
Thanks for helping
Matt

Hello Matt,
as far as I know, if you are able to connect via terminal there should be no problem to connect via Mongoclient as well. I'll investigate this further as soon as possible.
Your setup seems correct by the way.
Cheers

Bit more info from the server.
The auth.log is saying this when I'm trying to connect.
Connection closed by CLIENTIP [preauth]
It happens almost immediately, and I think means the client didn't send any authentication.
I think you may be right and we're filling in our connection properties incorrectly.
Is there any chance you could take some screen grabs, with secure bits removed of course, of your setup that is connecting properly over and ssh tunnel?
Failing that, are there any docs on how to set it up?
I realise this should be really simple, and most of the field names speak for themselves, but once you start hitting a problem you then start questioning all of them.
The screen grabs could even be the docs if you haven't got any already.
Thanks again Sercan, we're really looking forward to using the product, looks like it's exactly what we need.
Matt

Hello Matt,
I've rechecked my SSH connection details, and I've realized I'm using password instead of key file while connecting via SSH. With password there's no problem, but there's a bug for the key file usages, I'm now checking it.
Here's how I've configured my details (using key file and failed with error: Error: All configured authentication methods failed, will fix this until then you can use password authentication for SSH):

I've configured my connection details like I'm in that server:

Then I've configured my MongoDB authentication details, again like I'm in that server:

And finally I've configured my SSH connection details:

If you have a chance to login with password, try it like this and it will work, as I mentioned I'll fix the key file error.
Cheers

Hello,
ssh key file issue is fixed in the current active source code. If you have a chance to compile it as a web application you can use this feature now. I'll release 1.2.2 soon, after that you'll be able to use this on portables as well.
Cheers

Thanks very much Sercan, we'll try it out.

Hi Sercan,
I've just cloned your master branch to run it as a web app, and I'm getting the following error when trying to make the connection as before:
mongoclient[master]$ meteor --port 3000
[[[[[ ~/Local_Sites/mongoclient ]]]]]

=> Started proxy.
=> Meteor <IP_ADDRESS> is available. Update this project with 'meteor update'.
=> Started MongoDB.
=> Started your app.

=> App running at: http://localhost:3000/
I20160602-20:39:07.780(1)? info: [connect] mongodb://localhost:27017/ssot connectTimeoutMS=3000, socketTimeoutMS=5000, ssl=false, sslValidate=false
W20160602-20:39:07.786(1)? (STDERR)
W20160602-20:39:07.786(1)? (STDERR) events.js:72
W20160602-20:39:07.786(1)? (STDERR)         throw er; // Unhandled 'error' event
W20160602-20:39:07.786(1)? (STDERR)               ^
W20160602-20:39:07.786(1)? (STDERR) Error: listen EADDRINUSE
W20160602-20:39:07.786(1)? (STDERR)     at errnoException (net.js:905:11)
W20160602-20:39:07.786(1)? (STDERR)     at Server._listen2 (net.js:1043:14)
W20160602-20:39:07.786(1)? (STDERR)     at listen (net.js:1065:10)
W20160602-20:39:07.786(1)? (STDERR)     at net.js:1147:9
W20160602-20:39:07.786(1)? (STDERR)     at asyncCallback (dns.js:68:16)
W20160602-20:39:07.786(1)? (STDERR)     at Object.onanswer [as oncomplete] (dns.js:121:9)
=> Exited with code: 8

it looks as if the tunnel is conflicting with my local running mongodb instance.
I tried to play around in the source to see if I could fix this (be able to connect to a mongodb server even when a local instance is running on that default port), using the localPort option of tunnel-ssh:
https://www.npmjs.com/package/tunnel-ssh#remap-remote-port-to-localhost
But I couldn't get it to work.
It's not such a big deal closing my local instance, but thought I'd mention it incase it was an easy fix :).
Thanks very much for your quick response on this, I'll look forward to trying this out on our servers.
Neil

Hello,
in methods_common.js there's a connect function, ,in there you can try this out, I'll try to implement it as well.
Cheers


Several web links in the section how to install do not work , this makes it all very confusing how to install

Describe the problem
On webpage https://louisvdw.github.io/dbus-serialbattery/general/general/install#install-over-ssh  , under "Latest release " the link named "Install script " does not go to a valid location ( url https://louisvdw.github.io/dbus-serialbattery/general/general/install#install-over-ssh ) . Several other links on that page also do not work - makes it impossible to understand what the correct command is to install the latest release version
Driver version
v1.00
Venus OS device type
Cerbo GX
Venus OS version
3.13
BMS type
JKBMS / Heltec BMS
Cell count
16
Connection type
Serial USB adapter to RS485
Config file
asd

Relevant log output
we

Any other information that may be helpful
sad

Good question why. The links in the source code are correct. I have to take a deeper look.

Unfortunately the error is still present. When building locally there is no issue.

Found it. Problem fixed.


Write filepaths instead of csv data

Fixes #1114
Signed-off-by: Joe Grund<EMAIL_ADDRESS>

Codecov Report

Merging #1122 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1122   +/-   ##
=======================================
  Coverage   95.42%   95.42%
=======================================
  Files           2        2
  Lines         153      153
=======================================
  Hits          146      146
  Misses          7        7

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 b1a92f2...9b8bdbf. Read the comment docs.


Feature tls-webpki-roots causes duplicate definition

I was building off the example for gcp secrets and when enabling feature tls-webpki-roots like the example i get an error that duplicate definitions exist:
error[E0592]: duplicate definitions with name init_tls_config
--> /Users/chrisdupuy-admin/.cargo/git/checkouts/gcloud-sdk-rs-492432f787671ff2/4f4ba97/gcloud-sdk/src/api_client.rs:231:5
|
224 |     fn init_tls_config(domain_name: String) -> tonic::transport::ClientTlsConfig {
|     ---------------------------------------------------------------------------- other definition for init_tls_config
...
231 |     fn init_tls_config(domain_name: String) -> tonic::transport::ClientTlsConfig {
|     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ duplicate definitions for init_tls_config
when looking at the code it does appear both are included unless you use tls-roots:

To be able to use another TLS config you need to disable default-features since it has conflicting feature.

Thank you!  Sorry i missed that in the cargo.toml

No worries, I know the addictive nature of Cargo features might be quite frustrating, especially through transitive dependencies.


Resolved plain text rendering as HTML

Added escaping for plaintext so < and > are not recognised as HTML as in isssue #107
And updated documentation.

Thanks for your contribution and continued help Richard, appreciate it.


https://jira.baeldung.com/browse/BAEL-4630

Change Description :

Added TestNG tests in testng-jenkins folder
Added XML-based configs to run the tests
Added a pom.xml with the surefire plugin to use the XML file during the test phase of the build.

not needed, will point to existing testNg code


the code to do multiple-query person reid

Hi, I notice in your paper, you have calculated the multiple-query settings. But I can't find the code.

Hello, for multi-query code, please see: http://liangzheng.com.cn/Project/project_reid.html for details.


Flaky unit test in Firefox: threads multiple wtih allThreadsStopped

In today's build https://dev.azure.com/vscode/VSCode/_build/results?buildId=61491&view=logs&j=2d2b3007-3c5c-5840-9bb0-2b1ea49925f3&t=3bac50a7-8823-5ee7-170b-03223d1bbab7&l=26243
This is a bit difficult to see because of all the spammy output regarding Error, but if you download the raw logs an eliminate all the Cancellation errors that are printed you can see multiple stack traces pointing to out/vs/workbench/contrib/debug/test/browser/callStack.test.js e.g.:
Long stack trace
2021-01-08T11:34:43.2034685Z   Debug - REPL - /FIREFOX/
2021-01-08T11:34:43.2042148Z     âˆš repl output
2021-01-08T11:34:43.2084564Z     âˆš repl output count
2021-01-08T11:34:43.2115877Z     âˆš repl merging
2021-01-08T11:34:43.2186178Z     âˆš repl expressions
2021-01-08T11:34:43.4112763Z [JavaScript Error: "uncaught exception: Object" {file: "file:///D:/a/1/s/test/unit/assert.js" line: 231}]
2021-01-08T11:34:43.4115247Z fail@file:///D:/a/1/s/test/unit/assert.js:231:9
2021-01-08T11:34:43.4117955Z notEqual@file:///D:/a/1/s/test/unit/assert.js:268:9
2021-01-08T11:34:43.4119921Z @file:///D:/a/1/s/out/vs/workbench/contrib/debug/test/browser/callStack.test.js:124:24
2021-01-08T11:34:43.4122732Z promise callback*@file:///D:/a/1/s/out/vs/workbench/contrib/debug/test/browser/callStack.test.js:123:38
2021-01-08T11:34:43.4125538Z callFn@file:///D:/a/1/s/node_modules/mocha/mocha.js:21827:22
2021-01-08T11:34:43.4128448Z Runnable.prototype.run@file:///D:/a/1/s/node_modules/mocha/mocha.js:21813:12
2021-01-08T11:34:43.4129944Z Runner.prototype.runTest@file:///D:/a/1/s/node_modules/mocha/mocha.js:23466:11
2021-01-08T11:34:43.4131656Z next/<@file:///D:/a/1/s/node_modules/mocha/mocha.js:23597:13
2021-01-08T11:34:43.4133069Z next@file:///D:/a/1/s/node_modules/mocha/mocha.js:23374:15
2021-01-08T11:34:43.4135459Z next/<@file:///D:/a/1/s/node_modules/mocha/mocha.js:23384:12
2021-01-08T11:34:43.4138790Z next@file:///D:/a/1/s/node_modules/mocha/mocha.js:23259:15
2021-01-08T11:34:43.4140072Z cbHookRun@file:///D:/a/1/s/node_modules/mocha/mocha.js:23328:12
2021-01-08T11:34:43.4141519Z done@file:///D:/a/1/s/node_modules/mocha/mocha.js:21771:8
2021-01-08T11:34:43.4142787Z callFn@file:///D:/a/1/s/node_modules/mocha/mocha.js:21844:8
2021-01-08T11:34:43.4144027Z Runnable.prototype.run@file:///D:/a/1/s/node_modules/mocha/mocha.js:21813:12
2021-01-08T11:34:43.4145154Z next@file:///D:/a/1/s/node_modules/mocha/mocha.js:23282:11
2021-01-08T11:34:43.4146234Z Runner.prototype.hook/<@file:///D:/a/1/s/node_modules/mocha/mocha.js:23351:10
2021-01-08T11:34:43.4147244Z timeslice@file:///D:/a/1/s/node_modules/mocha/mocha.js:29607:28
2021-01-08T11:34:43.4148432Z setTimeout handler*mocha.Runner.immediately@file:///D:/a/1/s/node_modules/mocha/mocha.js:29625:25
2021-01-08T11:34:43.4149711Z Runner.prototype.hook@file:///D:/a/1/s/node_modules/mocha/mocha.js:23350:11
2021-01-08T11:34:43.4151967Z next@file:///D:/a/1/s/node_modules/mocha/mocha.js:23377:11
2021-01-08T11:34:43.4153089Z Runner.prototype.hooks@file:///D:/a/1/s/node_modules/mocha/mocha.js:23388:8
2021-01-08T11:34:43.4154423Z Runner.prototype.hookUp@file:///D:/a/1/s/node_modules/mocha/mocha.js:23401:9
2021-01-08T11:34:43.4155529Z next/</<@file:///D:/a/1/s/node_modules/mocha/mocha.js:23632:15
2021-01-08T11:34:43.4156705Z done@file:///D:/a/1/s/node_modules/mocha/mocha.js:21771:8
2021-01-08T11:34:43.4157752Z callFn/<@file:///D:/a/1/s/node_modules/mocha/mocha.js:21832:10
2021-01-08T11:34:43.4158845Z promise callback*callFn@file:///D:/a/1/s/node_modules/mocha/mocha.js:21831:15
2021-01-08T11:34:43.4160975Z Runnable.prototype.run@file:///D:/a/1/s/node_modules/mocha/mocha.js:21813:12
2021-01-08T11:34:43.4162124Z Runner.prototype.runTest@file:///D:/a/1/s/node_modules/mocha/mocha.js:23466:11
2021-01-08T11:34:43.4163237Z next/<@file:///D:/a/1/s/node_modules/mocha/mocha.js:23597:13
2021-01-08T11:34:43.4164401Z next@file:///D:/a/1/s/node_modules/mocha/mocha.js:23374:15
2021-01-08T11:34:43.4165385Z next/<@file:///D:/a/1/s/node_modules/mocha/mocha.js:23384:12
2021-01-08T11:34:43.4166412Z next@file:///D:/a/1/s/node_modules/mocha/mocha.js:23259:15
2021-01-08T11:34:43.4167423Z cbHookRun@file:///D:/a/1/s/node_modules/mocha/mocha.js:23328:12
2021-01-08T11:34:43.4168452Z done@file:///D:/a/1/s/node_modules/mocha/mocha.js:21771:8
2021-01-08T11:34:43.4169423Z callFn@file:///D:/a/1/s/node_modules/mocha/mocha.js:21844:8
2021-01-08T11:34:43.4170401Z Runnable.prototype.run@file:///D:/a/1/s/node_modules/mocha/mocha.js:21813:12
2021-01-08T11:34:43.4171484Z next@file:///D:/a/1/s/node_modules/mocha/mocha.js:23282:11
2021-01-08T11:34:43.4172605Z Runner.prototype.hook/<@file:///D:/a/1/s/node_modules/mocha/mocha.js:23351:10
2021-01-08T11:34:43.4174019Z timeslice@file:///D:/a/1/s/node_modules/mocha/mocha.js:29607:28
2021-01-08T11:34:43.4175441Z setTimeout handler*mocha.Runner.immediately@file:///D:/a/1/s/node_modules/mocha/mocha.js:29625:25
2021-01-08T11:34:43.4176948Z Runner.prototype.hook@file:///D:/a/1/s/node_modules/mocha/mocha.js:23350:11
2021-01-08T11:34:43.4178030Z next@file:///D:/a/1/s/node_modules/mocha/mocha.js:23377:11
2021-01-08T11:34:43.4179111Z Runner.prototype.hooks@file:///D:/a/1/s/node_modules/mocha/mocha.js:23388:8
2021-01-08T11:34:43.4180234Z Runner.prototype.hookUp@file:///D:/a/1/s/node_modules/mocha/mocha.js:23401:9
2021-01-08T11:34:43.4181606Z next/</<@file:///D:/a/1/s/node_modules/mocha/mocha.js:23632:15
2021-01-08T11:34:43.4182779Z done@file:///D:/a/1/s/node_modules/mocha/mocha.js:21771:8
2021-01-08T11:34:43.4184048Z callFn/<@file:///D:/a/1/s/node_modules/mocha/mocha.js:21832:10
2021-01-08T11:34:43.4185153Z promise callback*callFn@file:///D:/a/1/s/node_modules/mocha/mocha.js:21831:15
2021-01-08T11:34:43.4186228Z Runnable.prototype.run@file:///D:/a/1/s/node_modules/mocha/mocha.js:21813:12
2021-01-08T11:34:43.4187204Z Runner.prototype.runTest@file:///D:/a/1/s/node_modules/mocha/mocha.js:23466:11
2021-01-08T11:34:43.4188438Z next/<@file:///D:/a/1/s/node_modules/mocha/mocha.js:23597:13
2021-01-08T11:34:43.4189567Z next@file:///D:/a/1/s/node_modules/mocha/mocha.js:23374:15
2021-01-08T11:34:43.4190816Z next/<@file:///D:/a/1/s/node_modules/mocha/mocha.js:23384:12
2021-01-08T11:34:43.4191858Z next@file:///D:/a/1/s/node_modules/mocha/mocha.js:23259:15
2021-01-08T11:34:43.4193008Z cbHookRun@file:///D:/a/1/s/node_modules/mocha/mocha.js:23328:12
2021-01-08T11:34:43.4194938Z  [
2021-01-08T11:34:43.4195721Z   '[JavaScript Error: "uncaught exception: Object" {file: "file:///D:/a/1/s/test/unit/assert.js" line: 231}]\n' +
2021-01-08T11:34:43.4196876Z     'fail@file:///D:/a/1/s/test/unit/assert.js:231:9\n' +
2021-01-08T11:34:43.4197911Z     'notEqual@file:///D:/a/1/s/test/unit/assert.js:268:9\n' +
2021-01-08T11:34:43.4199907Z     '@file:///D:/a/1/s/out/vs/workbench/contrib/debug/test/browser/callStack.test.js:124:24\n' +
2021-01-08T11:34:43.4201305Z     'promise callback*@file:///D:/a/1/s/out/vs/workbench/contrib/debug/test/browser/callStack.test.js:123:38\n' +
2021-01-08T11:34:43.4202861Z     'callFn@file:///D:/a/1/s/node_modules/mocha/mocha.js:21827:22\n' +
2021-01-08T11:34:43.4204030Z     'Runnable.prototype.run@file:///D:/a/1/s/node_modules/mocha/mocha.js:21813:12\n' +
2021-01-08T11:34:43.4205262Z     'Runner.prototype.runTest@file:///D:/a/1/s/node_modules/mocha/mocha.js:23466:11\n' +
2021-01-08T11:34:43.4206333Z     'next/<@file:///D:/a/1/s/node_modules/mocha/mocha.js:23597:13\n' +
2021-01-08T11:34:43.4207485Z     'next@file:///D:/a/1/s/node_modules/mocha/mocha.js:23374:15\n' +
2021-01-08T11:34:43.4208571Z     'next/<@file:///D:/a/1/s/node_modules/mocha/mocha.js:23384:12\n' +
2021-01-08T11:34:43.4209601Z     'next@file:///D:/a/1/s/node_modules/mocha/mocha.js:23259:15\n' +
2021-01-08T11:34:43.4210860Z     'cbHookRun@file:///D:/a/1/s/node_modules/mocha/mocha.js:23328:12\n' +
2021-01-08T11:34:43.4211923Z     'done@file:///D:/a/1/s/node_modules/mocha/mocha.js:21771:8\n' +
2021-01-08T11:34:43.4213149Z     'callFn@file:///D:/a/1/s/node_modules/mocha/mocha.js:21844:8\n' +
2021-01-08T11:34:43.4214238Z     'Runnable.prototype.run@file:///D:/a/1/s/node_modules/mocha/mocha.js:21813:12\n' +
2021-01-08T11:34:43.4215324Z     'next@file:///D:/a/1/s/node_modules/mocha/mocha.js:23282:11\n' +
2021-01-08T11:34:43.4216401Z     'Runner.prototype.hook/<@file:///D:/a/1/s/node_modules/mocha/mocha.js:23351:10\n' +
2021-01-08T11:34:43.4217467Z     'timeslice@file:///D:/a/1/s/node_modules/mocha/mocha.js:29607:28\n' +
2021-01-08T11:34:43.4218627Z     'setTimeout handler*mocha.Runner.immediately@file:///D:/a/1/s/node_modules/mocha/mocha.js:29625:25\n' +
2021-01-08T11:34:43.4219833Z     'Runner.prototype.hook@file:///D:/a/1/s/node_modules/mocha/mocha.js:23350:11\n' +
2021-01-08T11:34:43.4221129Z     'next@file:///D:/a/1/s/node_modules/mocha/mocha.js:23377:11\n' +
2021-01-08T11:34:43.4222202Z     'Runner.prototype.hooks@file:///D:/a/1/s/node_modules/mocha/mocha.js:23388:8\n' +
2021-01-08T11:34:43.4224609Z     'Runner.prototype.hookUp@file:///D:/a/1/s/node_modules/mocha/mocha.js:23401:9\n' +
2021-01-08T11:34:43.4225548Z     'next/</<@file:///D:/a/1/s/node_modules/mocha/mocha.js:23632:15\n' +
2021-01-08T11:34:43.4226477Z     'done@file:///D:/a/1/s/node_modules/mocha/mocha.js:21771:8\n' +
2021-01-08T11:34:43.4227567Z     'callFn/<@file:///D:/a/1/s/node_modules/mocha/mocha.js:21832:10\n' +
2021-01-08T11:34:43.4228661Z     'promise callback*callFn@file:///D:/a/1/s/node_modules/mocha/mocha.js:21831:15\n' +
2021-01-08T11:34:43.4229778Z     'Runnable.prototype.run@file:///D:/a/1/s/node_modules/mocha/mocha.js:21813:12\n' +
2021-01-08T11:34:43.4231779Z     'Runner.prototype.runTest@file:///D:/a/1/s/node_modules/mocha/mocha.js:23466:11\n' +
2021-01-08T11:34:43.4233122Z     'next/<@file:///D:/a/1/s/node_modules/mocha/mocha.js:23597:13\n' +
2021-01-08T11:34:43.4234307Z     'next@file:///D:/a/1/s/node_modules/mocha/mocha.js:23374:15\n' +
2021-01-08T11:34:43.4235487Z     'next/<@file:///D:/a/1/s/node_modules/mocha/mocha.js:23384:12\n' +
2021-01-08T11:34:43.4236833Z     'next@file:///D:/a/1/s/node_modules/mocha/mocha.js:23259:15\n' +
2021-01-08T11:34:43.4238028Z     'cbHookRun@file:///D:/a/1/s/node_modules/mocha/mocha.js:23328:12\n' +
2021-01-08T11:34:43.4240090Z     'done@file:///D:/a/1/s/node_modules/mocha/mocha.js:21771:8\n' +
2021-01-08T11:34:43.4241635Z     'callFn@file:///D:/a/1/s/node_modules/mocha/mocha.js:21844:8\n' +
2021-01-08T11:34:43.4242834Z     'Runnable.prototype.run@file:///D:/a/1/s/node_modules/mocha/mocha.js:21813:12\n' +
2021-01-08T11:34:43.4245544Z     'next@file:///D:/a/1/s/node_modules/mocha/mocha.js:23282:11\n' +
2021-01-08T11:34:43.4246687Z     'Runner.prototype.hook/<@file:///D:/a/1/s/node_modules/mocha/mocha.js:23351:10\n' +
2021-01-08T11:34:43.4247837Z     'timeslice@file:///D:/a/1/s/node_modules/mocha/mocha.js:29607:28\n' +
2021-01-08T11:34:43.4249151Z     'setTimeout handler*mocha.Runner.immediately@file:///D:/a/1/s/node_modules/mocha/mocha.js:29625:25\n' +
2021-01-08T11:34:43.4251872Z     'Runner.prototype.hook@file:///D:/a/1/s/node_modules/mocha/mocha.js:23350:11\n' +
2021-01-08T11:34:43.4252995Z     'next@file:///D:/a/1/s/node_modules/mocha/mocha.js:23377:11\n' +
2021-01-08T11:34:43.4254225Z     'Runner.prototype.hooks@file:///D:/a/1/s/node_modules/mocha/mocha.js:23388:8\n' +
2021-01-08T11:34:43.4255536Z     'Runner.prototype.hookUp@file:///D:/a/1/s/node_modules/mocha/mocha.js:23401:9\n' +
2021-01-08T11:34:43.4256776Z     'next/</<@file:///D:/a/1/s/node_modules/mocha/mocha.js:23632:15\n' +
2021-01-08T11:34:43.4257961Z     'done@file:///D:/a/1/s/node_modules/mocha/mocha.js:21771:8\n' +
2021-01-08T11:34:43.4260028Z     'callFn/<@file:///D:/a/1/s/node_modules/mocha/mocha.js:21832:10\n' +
2021-01-08T11:34:43.4261600Z     'promise callback*callFn@file:///D:/a/1/s/node_modules/mocha/mocha.js:21831:15\n' +
2021-01-08T11:34:43.4262870Z     'Runnable.prototype.run@file:///D:/a/1/s/node_modules/mocha/mocha.js:21813:12\n' +
2021-01-08T11:34:43.4264228Z     'Runner.prototype.runTest@file:///D:/a/1/s/node_modules/mocha/mocha.js:23466:11\n' +
2021-01-08T11:34:43.4265481Z     'next/<@file:///D:/a/1/s/node_modules/mocha/mocha.js:23597:13\n' +
2021-01-08T11:34:43.4266619Z     'next@file:///D:/a/1/s/node_modules/mocha/mocha.js:23374:15\n' +
2021-01-08T11:34:43.4267714Z     'next/<@file:///D:/a/1/s/node_modules/mocha/mocha.js:23384:12\n' +
2021-01-08T11:34:43.4271483Z     'next@file:///D:/a/1/s/node_modules/mocha/mocha.js:23259:15\n' +
2021-01-08T11:34:43.4272673Z     'cbHookRun@file:///D:/a/1/s/node_modules/mocha/mocha.js:23328:12\n'
2021-01-08T11:34:43.4273493Z ]

There are multiple stack traces, I didn't paste all of them here. They involve the assertions:
callStack.test.js:124:24
            thread1.fetchCallStack().then(() => {
                assert.notEqual(thread1.getCallStack().length, 0);
            });

callStack.test.js:127:24
            thread2.fetchCallStack().then(() => {
                assert.notEqual(thread2.getCallStack().length, 0);
            });

callStack.test.js:196:24
            stoppedThread.fetchCallStack().then(() => {
                assert.notEqual(stoppedThread.getCallStack().length, 0);

FYI @jrieken here is an example where the spammy output made it very difficult to track down the root cause of the test failure. In this case it is the Cancellation error which spams us to death, but I had to go through every occurence of "Error" to find these stack traces.
cc @sandy081 this test failed for one of your commits, just so you don't start digging as well.

FYI @jrieken here is an example where the spammy output made it very difficult to track down the root cause of the test failure.

Yesterday @lszomoru showed a nice view of our tests that wasn't console.log output but some parsed version. I believe that's derived from some XML test runner output and IMO preferable. Assuming there is unwanted console.log spam there is still soo regular test output that I am scrolling indefinitely and in frustration. So, I would rather try to separate test results from console.log and have a nice presentation for those results (as shown yesterday)

FYI @jrieken here is an example where the spammy output made it very difficult to track down the root cause of the test failure.

Yesterday @lszomoru showed a nice view of our tests that wasn't console.log output but some parsed version. I believe that's derived from some XML test runner output and IMO preferable. Assuming there is unwanted console.log spam there is still soo regular test output that I am scrolling indefinitely and in frustration. So, I would rather try to separate test results from console.log and have a nice presentation for those results (as shown yesterday)

That would be really good to have. But in this case mocha or playwright (don't know which one actually) don't render a nice summary at the bottom at all:
https://dev.azure.com/vscode/VSCode/_build/results?buildId=61491&view=logs&j=2d2b3007-3c5c-5840-9bb0-2b1ea49925f3&t=3bac50a7-8823-5ee7-170b-03223d1bbab7&l=26238
    √ repl ordering (244ms)
    √ repl groups
    √ repl filter

to DEBUG, open FIREFOX and navigate to file:///D:/a/1/s/test/unit/browser/renderer.html?m=vs/base/test/common/async.test
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
##[error]PowerShell exited with code '1'.
Finishing: Run Unit Tests (Browser)

I'm not sure what's up with that, it is perhaps the fact that playwright runs tests in 3 browsers in parallel.

That would be really good to have. But in this case mocha or playwright (don't know which one actually) don't render a nice summary at the bottom at all:
https://dev.azure.com/vscode/VSCode/_build/results?buildId=61491&view=logs&j=2d2b3007-3c5c-5840-9bb0-2b1ea49925f3&t=3bac50a7-8823-5ee7-170b-03223d1bbab7&l=26238
    √ repl ordering (244ms)
    √ repl groups
    √ repl filter

to DEBUG, open FIREFOX and navigate to file:///D:/a/1/s/test/unit/browser/renderer.html?m=vs/base/test/common/async.test
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
##[error]PowerShell exited with code '1'.
Finishing: Run Unit Tests (Browser)

I'm not sure what's up with that, it is perhaps the fact that playwright runs tests in 3 browsers in parallel.

That would be really good to have. But in this case mocha or playwright (don't know which one actually) don't render a nice summary at the bottom at all:

This should be under our control. There is no playwright involvement except for running of course but how this works is that we have mocha reporter inside a browser/renderer which then forwards everything the main process which then replays the mocha reports. So, on that side we should also be able to feed reports into a "structured" mocha reporter...

That would be really good to have. But in this case mocha or playwright (don't know which one actually) don't render a nice summary at the bottom at all:

This should be under our control. There is no playwright involvement except for running of course but how this works is that we have mocha reporter inside a browser/renderer which then forwards everything the main process which then replays the mocha reports. So, on that side we should also be able to feed reports into a "structured" mocha reporter...

Thanks for creating this issue
However I can not reproduce this locally when running tests against firefox.
I have changed the test to be async which I am optimisitic might help.

Thanks for creating this issue
However I can not reproduce this locally when running tests against firefox.
I have changed the test to be async which I am optimisitic might help.

@jrieken, @alexdima, here is the test result view for that particular build. Couple of months ago we have done the work to publish the test results directly into Azure DevOps in order to get better analytics for test pass rate, and test execution time. The same is available for our product build. Do let me know if you see any issues with the published data.

@jrieken, @alexdima, here is the test result view for that particular build. Couple of months ago we have done the work to publish the test results directly into Azure DevOps in order to get better analytics for test pass rate, and test execution time. The same is available for our product build. Do let me know if you see any issues with the published data.

@lszomoru The test result view is exported AFAIK from the unit tests that execute in Electron. But this particular failure occurs in playwright which AFAIK is currently not exported in this format. I think that is why the linked test result view is not showing any particular test that failed?

@lszomoru The test result view is exported AFAIK from the unit tests that execute in Electron. But this particular failure occurs in playwright which AFAIK is currently not exported in this format. I think that is why the linked test result view is not showing any particular test that failed?

Actually @isidorn my bad, the test failure was different. After searching for    1) here is the real test failure:
    √ do not sync machine settings when spread across file
    √ raceTimeout
    √ SequencerByKey
    1) IntervalCounter
    √ firstParallel - simple
    √ firstParallel - uses null default
    √ do not sync machine settings when spread across file - 2

Actually @isidorn my bad, the test failure was different. After searching for    1) here is the real test failure:
    √ do not sync machine settings when spread across file
    √ raceTimeout
    √ SequencerByKey
    1) IntervalCounter
    √ firstParallel - simple
    √ firstParallel - uses null default
    √ do not sync machine settings when spread across file - 2

@alexdima what is the actual error stack trace? Was it a timeout or a assertion failure?

@alexdima what is the actual error stack trace? Was it a timeout or a assertion failure?

@bpasero: https://dev.azure.com/vscode/VSCode/_build/results?buildId=61491&view=logs&j=2d2b3007-3c5c-5840-9bb0-2b1ea49925f3&t=3bac50a7-8823-5ee7-170b-03223d1bbab7&l=26243

@bpasero: https://dev.azure.com/vscode/VSCode/_build/results?buildId=61491&view=logs&j=2d2b3007-3c5c-5840-9bb0-2b1ea49925f3&t=3bac50a7-8823-5ee7-170b-03223d1bbab7&l=26243


Show diagram previews in the signature

Like Globular, we should be able to toggle between a single image or a source/target view.


Only use anisotropic sampling if the device supports it

Fixes #610

Thanks for your PR. Very much appreciated.


Do not load unnecessary images in ci/kind/test-upgrade-antrea.sh

In particular, when testing upgrade from a minor version already using split images (e.g., 1.15.0), we should not pull the unified image and load it into the K8s Nodes, as it won't be used.
This should help reduce disk usage of the Kind cluster in CI.

/skip-all


Issue when backend is specified

this issue append with every backends and with and without a json theme in cache
$ wal -b wal -i ~/Images/wallpaper/
[I] image: Using image wallhaven-736570.jpg.
[I] theme: Set theme to _home_striker_Images_wallpaper_wallhaven-736570_jpg_dark_None_None_1.1.0.json.
[I] colors: Found cached colorscheme.
[I] wallpaper: Set the new wallpaper.
[I] sequences: Set terminal colors.

Traceback (most recent call last):
  File "/home/striker/.local/bin/wal", line 10, in <module>
    sys.exit(main())
  File "/home/striker/.local/venvs/pywal/lib/python3.6/site-packages/pywal/__main__.py", line 208, in main
    parse_args(parser)
  File "/home/striker/.local/venvs/pywal/lib/python3.6/site-packages/pywal/__main__.py", line 185, in parse_args
    export.every(colors_plain)
  File "/home/striker/.local/venvs/pywal/lib/python3.6/site-packages/pywal/export.py", line 68, in every
    template(colors, file.path, join(output_dir, file.name))
  File "/home/striker/.local/venvs/pywal/lib/python3.6/site-packages/pywal/export.py", line 15, in template
    template_data = "".join(template_data).format(**colors)
  File "/home/striker/.local/venvs/pywal/lib/python3.6/site-packages/pywal/util.py", line 25, in rgb
    return "%s,%s,%s" % (*hex_to_rgb(self.hex_color),)
  File "/home/striker/.local/venvs/pywal/lib/python3.6/site-packages/pywal/util.py", line 116, in hex_to_rgb
    return tuple(bytes.fromhex(color.strip("#")))
ValueError: non-hexadecimal number found in fromhex() arg at position 0
$ wal -i ~/Images/wallpaper/
[I] image: Using image wallhaven-736570.jpg.
[I] theme: Set theme to _home_striker_Images_wallpaper_wallhaven-736570_jpg_dark_None_None_1.1.0.json.
[I] colors: Found cached colorscheme.
[I] wallpaper: Set the new wallpaper.
[I] sequences: Set terminal colors.

[I] export: Exported all files.
[I] export: Exported all user files.
[I] reload: Reloaded environment.

I forgot to mention that this issue append on both my gentoo and arch install


Compiler crash

Review by @sjrd

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/1525/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/1967/
Test PASSed.

LGTM

Nice troubleshooting!


Question - Daily reminders

Hey,
I want to create the behavioral of sending the user 3 daily notifications, and the user should be able to modify the time of these notifications to whenever he/she wants. :/ I know how to set static ones but for when the user should have the option of choosing the time! how do I reschedule them?

I'm sorry, but this is an issue tracker. Stackoverflow or similar websites are better suited for such questions.

Ah, my bad misunderstood the use of issue tracker, Sorry. :)


Add all implementations to items in TODO.md

I’m interested in this project for its Python implementation, so I noticed Python was missing from most of the top-level items in TODO.md.
After a moment, I realized that there seem to be 6 implementations in this project, but many items in TODO.md have only 4 items (C#, Java, JavaScript, and Ruby).
Shouldn’t most of these tasks have all 6 implementations listed?
(…Or, am I missing something?)

The TODO was created while there was only 4 implementations. It's obsolete so I just yanked it (and added #78).


165847014:ios the app always goes to the appstore: having a previous version of the app in the market and adding dynamic links

[REQUIRED] Step 1: Describe your environment

Xcode version: 11.6 and 11.4
Firebase SDK version: 6.28.1
Firebase Component: Firebase/DynamicLinks
Component version: 6.28.1
Installation method: CocoaPods

Step 2: Describe the problem
we have an app in the appstore right now that has branch.io, and we are replacing that for firebase dynamic links
But for some reason, in some ios devices and with a few apps  (messages, whatsapp and others...)  when opening our link , the link goes to safari directly, and then goes to the appstore, even if we have the app installed in the iphone or ipad.
i have installed ad-hoc versions of the ipa and even run the app directly from the xcode, but im getting different behaviours between iphones and applications that triggers the links
the link works great for example if a share the link through facebook messenger, of if i open mail mail on chrome and then click the link that ive send previously in the body of the email
when we create the links we are using this flag:
       forcedRedirectEnabled: true,

we followed every step in your documentation and in the  firebase tutorial
Steps to reproduce:

create a deep link send it through an  sms to another iphone
click the link
watch how the safari is opened an then it goes to the appstore

is this the expected behaviour? is apple checking if the app that is installed in the phone was downloaded from the store before? i didnt find any documentations that support this

Could you please provide the Firebase Dynamic Link which is causing this issue?

@eldhosembabu
all links are causing this, (this link will no work in our production build, because now we are using branch.io)
here is an example:

@pabloearg hello, have you solved this problem? We have same issue with you --A previous production version. When i type the url in safari, it will always go to app store first, even if we have our debug or release app on the phone. And have you upgraded your production app? Does it work?

@MINISOCKS  if you type the url in safari, according to the universal links documentations, you will always be redirected to the appstore.
Dynamic links are not supposed to be using like this. you have to "click them".
in my case after i've open them, for example in whatsapp, i got redirected to safari and then to the appstore, instead to my app

Did you find a solution? In my case link always opens safari and then the app store as you. But if i type the link in chrome app and enter, it opens my app 😕

For me it worked after releasing in Testflight 🤷♂

Glad that it worked. Have you tried with forcedRedirectEnabled: false while creating the link?

Glad that it worked. Have you tried with forcedRedirectEnabled: false while creating the link?

Strang after the app release the dynamic links is not working any more :(
It is opening the app store app detail page while the app is installed.

Info.plist contains the domains
Firebase SDK is up to date and contains "Firebase/DynamicLinks" and "Firebase/Analytics" as per documentation : https://firebase.google.com/docs/dynamic-links/ios/receive?authuser=0
apple-app-site-association url content is correct
performDiagnostic completed successfully! No errors found.

Any suggestions?
Links are created in Firebase console so i have no idea about "forcedRedirectEnabled" :)

Closing for staleness. Please comment or open a new issue to reopen.


fix typo in pipeline.yml

Purpose

To-do

Content

[ ] I have read and checked the items on the review checklist.

bors r+


What's it support ElasticSearch version?

What's it support ElasticSearch version?
You know when the elastic release new ElasticSearch version ,the ElasticSearch  REST API will change .
So , we should tall our client the go-stash supported ElasticSearch version , eg: 7.1 ,6.5, 5.5. : )

你好，按照版本变化来说，可以支持6~6.8及的版本


How To Remove Features?

Title says all. For example "Anti Aim". How can i remove?

ctrl + f search "anti aim" = profit


[NEMO-15] Run Spark ALS in distributed mode

JIRA: NEMO-15: Run Spark ALS in distributed mode
Major changes:

Removes 'sideinput' from IRDAG, and instead introduces BroadcastVariableProperty
InMasterBroadcastVariables/BroadcastManagerWorker: Components that deal with broadcast variables
New RPC messages for exchanging broadcast variables between client->driver, and driver<->executor

Minor changes to note:

Explicit scala lambdas (update_ms, update_us) to get around serialization errors

Tests for the changes:

SparkScala#testALS

Other comments:

This PR also closes: [NEMO-14] Re-investigate Broadcast and SideInputs

Closes #GITHUB_PR_NUMBER

@wonook Maybe change the issue title from "Run Java Spark ALS in distributed mode" to "Run Spark ALS in distributed mode"?

@sanha @wonook The PR is ready. :smile:

Thanks @wonook and @sanha!
The tests should pass now. 😄


Refactor/modify repository defaults

It seems sensible enough to ignore the quality gate failures given this is essentially the initial commit.

Love the generation of task-definitions for both environments from the pipeline 🌮


New Versioning System?

The current versioning system isn't reliable.
Even i don't really know which version is what... can we redo the versioning (including the older versions of the botsuite)?
I don't really think that we are over a 1.0 if you ask me, not to speak of a version 4!
(Except you want to start like Mozilla when it comes to set a FireFox version) ...

Since active development stopped, this is no longer needed.


Some error questions about generate_P_fast.py

sorry to be a bother, when I run this python file, it shows an error called "AssertionError: /home/fxj/SO-Pose-main/datasets/BOP_DATASETS/lm/train_pbr/xyz_crop/000000/000000_000001-xyz.pkl", where can I find"000000_000001-xyz.pkl"?

I guess it may not generate the path successfully, how can I fix this problem?

I see. You should create a soft link under the folder '/home/fxj/SO-Pose-main/datasets' which points to your location of the dataset.
You can use ln -s file1 link1

I also encountered the same problem. I didn't find xyz_crop related files under the officially downloaded train_pbr folder.

https://github.com/THU-DA-6D-Pose-Group/GDR-Net/blob/main/tools/lm/lm_pbr_1_gen_xyz_crop.py
Note that xyz_crop is generated with the code from GDR-Net.
The generated xyz_crop file is too large, so I can't upload it.


feat: add module for Zitadel IdP infrastructure

Summary
Add the Terraform and Terragrunt configuration for the Zitadel IdP's infrastructure.  This includes the following:

ECS cluster for the Zitadel service.
RDS Aurora Serverless V2 cluster (Postgres v16) for the Zitadel database.
Load Balancer and certificate for requests to the Zitadel domain which will be auth.forms-formulaires.alpha.canada.ca.
ECR to hold the Zitadel Docker images.
VPC security groups for the new infrastructure network communication.

Goals

Make the IdP Terraform as standalone as possible from the Forms app Terraform.
Use generic naming conventions for the IdP Terraform resources.
Add an environment specific feature_flag_idp that can be used to control if shared IdP resources are created.

TODO
Once review is finished on the Terraform, the following will be needed:

Update the Staging Terraform plan/apply workflows to manage the infrastructure.
Update the Docker image build workflows to build and push the Zitadel Docker image.
Add a WAF ACL for the IdP load balancer.
Investigate Zitadel static asset caching using CloudFront.

note for next steps: how this will play out with localstack

That is a question I have in my mind as well.  I don't have a full license, so I can't do a test of this PR with localstack.  In terms of local dev environment, this would also work to give people a local Zitadel instance to test with:
https://zitadel.com/docs/self-hosting/deploy/compose


Support for yarn

Any idea for support yarn?

It's now possible with:
gulp.src('...').pipe(install({
  commands: {
    'package.json': 'yarn'
  }
}))

Ty @joakimbeng


Use none in api version so we don't get spn: in response.

See https://github.com/AzureAD/azure-activedirectory-library-for-python/issues/54 for similar issue and fix in the python repo.

@danieljin i think this is what we want to do? master is for tracking releases so i think we will want to publish to our npm repo from master.


Implement multiple file selection dialog

Fixes #167. This allows selecting multiple files in a similar way as OS's like windows allow. Then I had to update the behavior to handle multiple files such as downloading, moving, and deleting. Currently copying isn't implemented, but it would be for a different PR.
At this point, it appears to be working, but would like to do further testing before getting this merged in.

I've been testing a bunch and it seems to consistently be working, so will merge this in for now since it's just the beta site.


[Bug] Thank you / About Modal - X is in the wrong position

Thank you / About Modal - X is in the wrong position
To Reproduce
Steps to reproduce the behavior:

Click on  Thank you / About link in the footer

Expected behavior
X should be positioned closer to the left edge
Screenshots

Environment
Browser: Chrome

@yuvalbl
The problem is that the AnywayAppBar component is with left and right padding by default....
So, to fix that bug we need to edit the appbar component or to find another solution.

Duplication of #431


Unique Taxpayer Reference

10 digit number used in LISA and other services. We need to standardise this.

Note that in LISA it's possible the users may have a 13 digit UTR number. If that's the case we ask that they only provide the last 10 digits.

@jennifer-hodgson This is from AWRS.

These are from business matching.

This from Soft Drinks Industry Levy
Prototype here: https://www.prototypes.tax.service.gov.uk/sdil-prototype/register/4-0/identify

This from Lifetime ISA
Prototype here: https://www.prototypes.tax.service.gov.uk/lisa-prototype/sixteenth-iteration/non-isa/llp-reference-numbers

This from Register a company
Prototype here: https://www.prototypes.tax.service.gov.uk/business-registration-prototype/1-73-0/incorporation/GroupUTR

From pay online.
https://www.tax.service.gov.uk/pay-online/self-assessment

Discussion Summary of References/Identifies from the hackday

Issues we have asking for a UTR in the PODS service:
(1) the pattern says we should allow users to enter 10 or 13 numbers, with or without spaces and a k, and then strip the unnecessary characters. Our service can only send 10 digits to ETMP, so would have to strip extra characters anyway. The problem then is that when the UTR is played back to the user (e.g. when they return to the service at a later date) we can only retrieve the 10-digit UTR from ETMP and play it back to the user. Their first reaction is likely to be "hold on, that's not right - the number I entered was 13 digits / had a space / had a k" etc etc.
(2) the hint text states "This is 10 numbers, for example<PHONE_NUMBER>". We feel this can be as confusing as it is helpful: sometimes a paper UTR is in the format xxx xxxxx xxxxx, sometimes xxxxxxxxxx, sometimes xxxxx xxxxx (and there's probably more combinations than that!). We're allowing a user to enter k's and spaces and more numbers than they should, as we know how different the UTR can be presented to them, but then showing the single format example could make them unsure that they have the right number to enter in the first place.
On PODS we ask for a UTR over two pages - (a) do you have a UTR? (as not every user will have one), and if yes (b) what is your UTR? We have prototyped the content for this as follows (based primarily on design and UR that AMLS have already successfully done):
(a) Does [USER] have a Unique Taxpayer Reference (UTR)? with supporting text of "This is a 10-digit or 13-digit number. You can find it on tax returns and other documents from HMRC. It might be called ‘reference’, ‘UTR’ or ‘official use’."
(b) What is [USER]'s UTR? with supporting text of "If the UTR is 13 numbers, only enter the last 10." and "If there is a letter ‘K’ at the end of the number, do not enter it."
As mentioned this support text has been successfully tested by AMLS (minus the letter 'k' portion which they did not include). We will likewise test this and feed back on outcomes.

@jonathaninch I just came here with a question related your point (1) that I originally posted in slack but got no response:
Guidance at https://design.tax.service.gov.uk/hmrc-design-patterns/unique-taxpayer-reference/ says "Remove spaces, characters and extra numbers before validating." I'm confident about making a case within our team for removing spaces and punctuation. I'm less confident about making the case for removing extra digits. Can anybody give me the reason for removing extra digits so I can make the case to colleagues?

The pattern's hint text link content includes "UTR number" but the HMRC style guide says: "Not ‘Unique Taxpayer Reference number’ or ‘Unique Taxpayer Reference Number’". Should the word 'number' be removed from the pattern?

Thanks @JillRichardsonPratt this pattern is currently under review for other amendments, so we'll look at this as part of the update

I think most services will have the Find a lost UTR link open in a new tab. So that users can stay in the service. Is it possible to add '(opens in new tab)' to the Find a lost UTR link? Accessibility tests have flagged this- that we should add '(opens in new tab)'
The Welsh translation in the pattern has the entire text as a hyperlink for 'You can find a lost UTR', but the English version has the hyperlink only on the 'find a lost UTR' part of the text. Is this correct?

Thanks for the feedback @Colin172A we've updated the pattern

Thanks for the feedback @Colin172A we've updated the pattern

Hi again. We noticed that the Welsh translation for "You can find a lost UTR" was different in our service to the translation on the pattern. I checked this with the Welsh translation team. They've confirmed the correct translation is:
Gallwch ddod o hyd i UTR sydd ar goll (yn agor tab newydd)

Hi,
I attended an accessibility presentation about dyscalculia.
One of the principles is to add spacing around numbers to make them easier to read. This is done for the National Insurance number pattern. Could the same be applied to the example UTR in the hint text?

Hi @Colin172A I've updated the welsh.
Regarding how we show reference numbers, I'll raise this with our content designer when they start later this month (it's been a vacant position for some time). It would mean changes across several patterns and potentially style guide entries.

The guidance says 'Remove spaces, characters and extra numbers before validating.'
I think this has already been asked above, but if someone enters too many numbers, how do you know which ones to remove?
At the moment we've just been stripping out anything which can not be a valid character. If there are too many digits we display an error message to let the user know.

The existing pattern assumes that someone would only be able to find their UTR in an offline format like a letter. Users are likely to be able to access online systems too and may already be signed into GG and able to access their PTA or have the HMRC app.
Can the pattern be updated to include signposting (with links) to PTA and the HMRC app, as per the GOV.UK guidance?

Also is there any way people could be signposted to a place where they can get a copy of their UTR if they have lost it, as per the guidance?
Also, as a UTR can be between 10 and 13 characters, advising a user that it's 10 numbers is likely to confuse users who have a 13 character ref on a document or letter. Could the hint text be updated to accommodate this?

Another option could be to change the wording of the link from "You can find a lost UTR" to "Find your UTR". This matches the heading on the page that the link takes you to.
It also removes the assumption that the UTR is 'lost' and the link is only for users who have 'lost' it. It might not be lost, the user might just need to find out which online services allow them to view the UTR, which is what the "Find your UTR" page primarily provides. Changing it to "Find your UTR" accommodates both types of user- those who lost the UTR and those who just need help to look it up online.

@Colin172A I agree that changing the text to 'find your UTR' would be clearer.
My concern is that it seems from the screenshots of pages for the 'Enter a UTR page' that I've seen that often that first line of the text from the pattern isn't included when screens are developed so often the only guidance people have is the hint text telling them to look at a letter etc.
Having hint text that specifically says you can find your UTR in the HMRC app or your personal tax account will help people self serve. (Also telling people that UTRs can be 10 to 13 characters rather than just 10 numbers.
I'm suggesting something like this mock up below. It would mean the link in the pattern could be removed, which would keep people on the page.

@jeanesims the mockup looks good. Better to keep users on the screen than send them to another page to read through.
For Corporation Tax is there an online service they can use to look it up? I am not sure if they can get it from the HMRC app or is the only way to get it from paper documents?
I guess the text would still need a link for users who have lost/cannot find their UTR so they can get guidance about having it sent out in the post?

@Colin172A
Here's a version with the signpost for those who can't find their UTR

Thanks for these suggestions, we're taking them into account as we prepare our revised pattern. We would also like to address Rachel's initial concern around validation, removing characters etc.
Would you know of anyone we could reach out to to discuss how validation is handled? I'd particularly like to find out if the 'k' character in some UTR's is actually needed.

Here's a suggestion for CTUTR

The link above the green button would go here for CT https://www.tax.service.gov.uk/ask-for-copy-of-your-corporation-tax-utr?_ga=2.197867372.2131649915.1692788962-79046079.1665746662

@JackHMRC - @adamliptrot-oc would be a good person to speak to about this

Thanks Jean, I'll update as we progress :)

If someone signs in to their tax account then hopefully they will no longer need to enter their UTR, as we'd know it? This might depend on which service the user is in.
For paying Corporation Tax we have started to tell people that if you don't know your reference you can sign in and it will be filled in automatically. The user isn't expected to come back and enter it once they've found it, as we'll populate it for them.

Also, we've recently noticed that a lot of people include the letters 'UTR' at the start when entering their Unique Taxpayer Reference. Maybe we should strip these letters out before validation and accept the reference if it's otherwise formatted correctly? To save the user seeing an error message.

People use different GG user IDs to sign into services and this means that each service has to develop pathways for data, like a UTR, to be pulled in. If a service wants to pull in a UTR for example this has to be developed so isn't automatic.
So someone might sign into GG and a service to pay 'magicians tax' using a GG User ID that is different to the one they use for Self Assessment and because the magicians tax service hasn't built a way for a UTR to be pulled into that journey, the user will still need to enter it even though they are signed into GG.

One of the easiest ways to find your UTR is using the HMRC app. A lot of people find using the app easier than going to PTA. It would help users if the app were mentioned here along side PTA in the pattern. Is there any way it could be added?

In this current iteration of the design, the input doesnt have an  aria-describedby attribute so there is no hint text, just a standard paragraph that is not announced when the user is focused on the input.
I would have thought the paragraph about what the UTR is and the format of the UTR would have been hint text?

Hi @richardhattonUX
The full description includes a link, which shouldn't be included in hint text.
The optimal accessibility approach for these UTR examples is beyond my knowledge, but the latest version was created with the help of some of our accessibility experts.

@richardhattonUX @Jon-Rowe-HMRC I think the difficulty is in trying to achieve an outcome by staying as close to out-of-the-box   implementation of components as possible.
We could improve the current pattern by including an aria link to the hint text from the input even though it sits outside the form control:
h1 "What is your UTR?"
p[id="utr-hint"] "Your UTR can be ..."
p link:"How to find your UTR"
label.govuk-visually-hidden "What is your UTR?"
input[aria-describedby="utr-hint"]

Which would expose the format information whilst not including the link.
The difficulty is in communicating this requirement to the developers/IXD in the pattern.
However I think there is currently an issue with the pattern communication as visually it does look like the h1 is meant to be the label and the two paragraphs the hint. It is only when examining the code (which I expect not everyone does if it looks simple) that you realise it is not marked up in that way. The "Place the question on its own page. " instruction is not obvious enough considering this is a departure from the norm.

@Jon-Rowe-HMRC I think @adamliptrot-oc has articulated the issue I had better than I did.

Thanks @adamliptrot-oc and @richardhattonUX. The design resources team is working on an iteration of the examples and guidance.

Hi @adamliptrot-oc & @richardhattonUX, We've been looking into this on the design resources team and have another suggestion of using the standard GOV.UK complex question pattern. The content isn't final but as an example:
h1 "Your Self Assessment Unique Taxpayer Reference (UTR)"
p "Your UTR can be ..."
p link:"How to find your UTR"
label: "What is your UTR?"
input

There are some benefits to this over the other patterns:

There's no hidden code complexity such as visually hidden text or aria-describedby attributes so will be less likely for people to code it incorrectly
It uses the standard GOV.UK Design System pattern

The downsides I can think of are:

No association between input and "hint" text
It's a slightly bigger change visually from what currently exists

I think the pros of this approach outweigh the cons.
Any thoughts from yourselves?

Hi @timsb,
I think that the complex question approach is better (I am not a fan of hiding labels).
Looking at the copy on the UTR pattern, there is formatting content that could be added as hint text and the remaining as the into text, e.g.
h1 "Your Self Assessment Unique Taxpayer Reference (UTR)"
p "You can find it in your Personal Tax Account, the HMRC app or on tax returns and other documents from HMRC. It might be called ‘reference’, ‘UTR’ or ‘official use’."
p link:"How to find your UTR (opens in new tab)"
label: "What is your UTR?"
hint: "Can be 10 or 13 digits long"
input

Just an idea to accommodate one of the downsides.

Hi all, I was wondering why we don't have a pattern for Partnership UTR?
A need has been called out in our service to ask for Partnership UTR. This is to ensure if a user is part of/reporting on behalf of a partnership they enter the UTR of the partnership itself, and not the SA UTR of one of the partners.
We've been using this wording that I adapted slightly from the SA UTR wording based off this gov.uk site.

This wording appears if they selected "Partnership" or "Limited partnership or limited liability partnership" to "What type of business are you?" in the previous screen.
Any thoughts on this wording? And is it worth creating a Partnership UTR pattern?

Thanks @kerry-a-H we've added a partnership example: https://design.tax.service.gov.uk/hmrc-design-patterns/unique-taxpayer-reference/

Hi, is it possible to include an example in the hint or error message? We used to use<PHONE_NUMBER> but we would now also need a 13-digit version. I'm not sure if examples have been left out deliberately, for example, because we do not want to show an identifier that could be assigned to a real person.

Hi @JillRichardsonPratt they're been left out of the default examples intentionally as we had feedback they often didn't test well e.g. users being confused the example format didn't exactly match their format. Not just that there's different lengths, also that some contain letters.

Hi Henrik,
The examples used to use 'digits' instead of 'numbers'. After a working group discussion it was changed as more people are likely to understand the word 'numbers' over 'digits'. 'Numbers' is more commonly used in everyday language.

@Jon-Rowe-HMRC Noted, thank you. The copy in the examples still says ”digits” FWIW.

@henrik ah, my mistake. There have been so many changes to this pattern I'm confused :) We'll do another edit to make it consistent.


tool search page name sort is weird

On staging.dockstore.org/search, go to the Tools tab. Click on the 'name' header to sort by name. It seems to be sorting by the part of the name after the first slash, not the whole thing. For instance pfda2dockstore/bai/bai is before lynnlangit/blastn/blastn-test.
This does not happen on the Workflows tab. It does make sense to sort first by tool name rather than organization, but the way this is displayed is confusing. Maybe the name and the organization prefix should be separated into adjacent columns for a cleaner look.
┆Issue is synchronized with this Jira Bug
┆Fix Versions: Dockstore 2.X
┆Issue Number: DOCK-1075
┆Sprint: Sprint 46- Unicorn Fish
┆Issue Type: Bug

Can confirm that the name column is alphabetically sorted in a way that makes sense now for tools and workflows
dev.dockstore.net
Webservice - d836384
UI - 2.6.3-62-g17c33342
Compose Setup - f067256a177048809c59dfc4ae76f918e4e820f4
Deploy - 1.9.3-50-gac878e6


Bridge nodes are constantly rebooting after block height 24k+ in robusta-64

Celestia Node version
v0.11.0-rc6
OS
k8s/docker/alpine
Install tools
No response
Others
In metrics since 21:10 11/07/2023 at height 24k -> we see that nodes starts to suddenly reboot themselves

Steps to reproduce it
Start syncing a bridge node from genesis
Expected result
No reboots -> bridge nodes reach the tip of the chain
Actual result
Reboots starts with such such logs

node failed to start
2023-07-12T06:40:39.945107038Z stderr F 2023-07-12T06:40:39.940Z	WARN	shrex-sub	shrexsub/pubsub.go:83	unregistering topic	{"err": "no validator for topic robusta-64/eds-sub/v0.1.0"}
2023-07-11T19:26:27.51014414Z stderr F 2023-07-11T19:26:27.509Z	WARN	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:572	failed to recover state of shard : unexpected end of JSON input; skipping
2023-07-11T21:35:43.547463363Z stderr F 2023-07-11T21:35:43.530Z	ERROR	core	core/listener.go:128	listener: handling new block msg	{"height": 37696, "hash": "9B5D7F772F7B513E4F3608CB74C3EB1699709ACEC0892D841E0D640E5725B16E", "err": "storing EDS: context canceled"}

Relevant log output
look for grafana dashboards

Notes
There were no reboots before 21:10 11/06/2023 for all 4 bridge nodes

@Bidon15 @walldiss is this still an issue?

it's fixed IIRC @walldiss

@Bidon15 @walldiss is this still an issue?

It's fixed


Feat/clean up repo

Changes:

added isort, black, flake and pre-commit
format all the files
remove unused modules
remove quants lab

PR update:

Backend and dashboard source + broker compose file, no go and created bug ticket 25
Dashboard source + backend and broker compose file ok used on testing this PR

Added isort, black, flake8 and pre-commit

Remove and recreate env for dashboard ok
Not sure how we can check black ?

initial tests:

Test bot orchestration

Accounts with credentials (CRUD) and portfolio ok
Instances and random config-generator ok
Ran test with random config-generator and switch to diff config ok

Todo:

Run tests on all config-generator
Run backtests on pmm controllers
Deploy and observe instance

Test perfromed:

Clone dashboardPR160 + backendPR24
Removed dashboard and backend-api environment
set up env for dashboardPR160 + backendPR24 again
start dashboard and backend-api
Run backtesting successfully on PMM simple, PMM Dynamic, D-man maker v2, Bollinger bands, MACD_BB

Pending:
Instance test with https://github.com/hummingbot/hummingbot/pull/7121


[SPARK-19974][Block Manager] in-memory LRU for partitions of multiple RDDs testcase did a get that is no sense

What changes were proposed in this pull request?
in-memory LRU for partitions of multiple RDDs testcase did a get that is no sense; rdd_0_2  is the most recently used item that isn't the reason the rdd_0_2 is remain; store.getSingleAndReleaseLock(rdd(0, 2)).isDefined  as same as the previous line store.memoryStore.contains(rdd(0, 2)), so remove the no sense code
How was this patch tested?
run the test
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)
Please review http://spark.apache.org/contributing.html before opening a pull request.

Can one of the admins verify this patch?

I don't understand why you say this test doesn't make sense. The assertion is correct. You say you think the second assertion should always pass, but, isn't that the purpose of the test?

I am sorry,you are right, the second assertion is ok; but what do you think about the assertion comment:Do a get() on rdd_0_2 so that it is the most recently used item, what is the purpose of the test?  lru or same rdd rule ;  the reason for rdd_0_2 should not be dropped is the same rdd rule, not the comment said Do a get() on rdd_0_2 so that it is the most recently used item, so i think the comment is wrong or the assertion is wrong; I am sorry, if the  purpose of the test is only to test rdd_0_2 was not in store, it is ok, I didn't understand the purpose or the comment of the assertion, I am sorry;

I'm also not sure about the intent of these lines and it is possible the comment doesn't quite reflect the call that follows because it refers to get(). However it seems like the tests are still valid. Unless you know they are wrong yet pass then i would leave it.

do you agree remove the comment is more appreciable? can i only remove the comment?

Unless we are sure, I don't think it is worth changing.


MAR for Image-to-Image Generation

I am a green-hand of MAR, as I only explore LDMs in image generation currently. I wonder whether MAR can be used for Image-to-Image generation especially for image editing (e.g. temporal generation). Also, I wonder whether MAR (with diff loss) trained with large-scale dataset is able to be fine-tuned with a domain specific dataset for temporal generation.
Again, awesome work!

Thanks for your interest! Similar to MaskGIT and MAGE, MAR can naturally perform mask-based image editing tasks such as image inpainting, outpainting, and uncropping. If the temporal generation you mentioned is for video, then it would be hard to fine-tune a model that is trained to generate image to generate a video.

Thank you!
I am working with satellite image generation where each image captures the same region from different timestamp ( and this is what I meant to "temporal" and I am not sure whether this task can be categorized into inpainting or not).
It is witnessed that temporal layers used in LDMs for video synthesis can be incorporated into ControlNet so that LDMs are able to generate temporal images. I wonder if there are similar techniques for MAR.


Promote the interactive tutorial for programming courses

I think the interactive tutorial can be used to teach programming and I am sure, a lot of people are interested in using Oni for this.

Cool idea!
I was thinking about this a bit too - in the form of some lightweight 'katas' or simple problems. It would go great with the 'live preview' functionality, which is very helpful for new programmers. Or as a way to practice interview problems, etc.
Definitely would be open to something like this - it may make sense as a plugin, but our tutorial API should be sufficient actually to enable this. The difference would be that we could show a live preview instead of the 'notes' section, and we'd need to compile/run on buffer changes, but it really wouldn't be too different.

I suggest to create a tutorial, which shows how to create these tutorials ;)


upgrades obtained through terran addons require parent building

currently, only the addon is placed which causes the addon to not work, so the desired upgrade is not obtained.

parent buildings hosting the required addon will now be placed in version 0.5.1


⚠ Bofrost.at has degraded performance

In 617567a, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2436 ms

Resolved: Bofrost.at performance has improved in 5a36995 after 29 minutes.


[Migrated] zappa package doesn't include dist-packages

Originally from: https://github.com/Miserlou/Zappa/issues/905 by monkeypants
zappa --package bundles site-packages from the virtualenv. But, on some distributions, pip installs stuff into dist-packages. So, there is a problem that these platforms (e.g. AMI linux) that they don't include pip-installed packages when they zappa --package
Context
Do zappa --package on with an AMI linux box, or some other platform that does strange things to pip, so it installs stuff into dist-packages.
Expected Behavior
I would like to see all the stuff from dist-packages in the zappa package, so my thing works the same even if I build it on Amazon Linux.
Actual Behavior
The site-packages is included in the zappa package. The dist-packages are not. The stuff I installed with pip in my virtualenv is not included in the zappa package if I ran it on a wacky OS, and my thing doesn't work because it's requirements are not met.
Possible Fix

update create_handler_venv in zappa/core.py so it does stuff with dist-packages for the relevant platforms
update detect_flask_apps and detect_django_settings in zappa/utilities.py so they check dist-packages too
Is this maybe related to why /tests/tests.py#L70 is commented out?

Steps to Reproduce

Make yourself at home in an AWS Linux AMI
Create a virtualenv and activate it.
pip install a bunch of stuff, such as the requirements for you app
See for yourself how there is a bunch of stuff installed in dist-packages
do zappa --package
compare the size of the lambda.zip with one made on non-debian distribution (it's smaller, because it doesn't include the packages from your virtualenv)
see how the thing fails with unmet dependencies if you deploy it
see how the lambda.zip does not contain your requirements

Your Environment

Zappa version used: latest
Operating System and Python version: Amazon Linux AMI
The output of pip freeze: any
Link to your project (optional): N/A
Your zappa_settings.py: N/A (I think)

stale migrated issue.
If there is a packaging issue, create a new issue.
closing.


"about:" tabs are not opened

This is due to syntax validation where default protocol "https://" is wrongly prepended to urls that starts with "about:". This leads to creation of invalid url where browser does ignore them.

It turns out that extensions are not allowed to open "about:" protocol urls. Therefore from now on, the extension will ignore "about:" and other restricted protocols.


Chris add GitHub rules

Signed-off-by: Chris Sommers<EMAIL_ADDRESS>Adapted from https://github.com/Azure/DASH/blob/main/doc-github-rules.md which I co-authored with MSFT.
Per Slack thread: https://opi-project.slack.com/archives/C033E418VCK/p1649275592758869. Other opi projects can refer to this.

@mestery I addressed all your concerns and resolved all the conversations. Yet for some reason, the PR shows requested changes still need to be addressed.


Email are sent immediatly

Hi,
Thanks for creating the Gmail Scheduler!
I installed the plugin, but when I send an email, it will be send immediately. When I look at the send items I see that the email has the label e.g.  "GScheduler/Timer/1 hour later".
I don't understand why it don't work.
Anyone an idea?
Grtz,
Pieter

@pheijms did you press the send button in the email? This was reported in other issues in the past where users click on the SEND button in gmail. All you have to do is set the schedule and then leave the email to out.

@webdigi Thanks for the quick reply.
That's it!
What a great plugin! Don't understand that not more people use this free plugin. Keep up the good work!


v0.9.0 is not available for Mac M1 chip

Description
sea-orm version 0.9.0 is not available for Mac M1 chip.
Error:
rust-analyzer failed to load workspace: Failed to read Cargo metadata from Cargo.toml file api/rust/Cargo.toml, cargo 1.59.0: Failed to run "cargo" "metadata" "--format-version" "1" "--manifest-path" "/api/rust/Cargo.toml" "--filter-platform" "aarch64-apple-darwin": cargo metadata exited with an error: Blocking waiting for file lock on package cache Updating crates.io index error: failed to select a version for the requirement sea-orm = "^0.9" candidate versions found which didn't match: 0.8.0, 0.7.1, 0.7.0, ... location searched: crates.io index required by package apis v0.1.0 (/api/rust/apis)
Output of cargo check:
Updating crates.io index
error: failed to select a version for the requirement sea-orm = "^0.9"
candidate versions found which didn't match: 0.8.0, 0.7.1, 0.7.0, ...
location searched: crates.io index
required by package apis v0.1.0 (/api/rust/apis)
Additional Information
Please refer to attached screenshots for more information.

Try update local rust version to latest .
~ rustup update
~ rustc -V
~ rustc 1.62.0 (a8314ef7d 2022-06-27)

Thanks for reporting!! @itsAmitGoyani

Please let me know if upgrading Rust version helps or not
Thanks! @baoyachi

It's seems cargo bug.

@baoyachi @billy1624 Thanks a lot. My rustup version was 1.62.0 only. Just problem was my rustc path was set to separately installed location of version 1.59.0. But now I uninstalled it and it worked. Thanks again.

Interesting! Thanks all :)


Feature request: Multiple journals

My workflow consists of two journals (private and work-related). I'd love to be able to use the Periodic Notes for managing them both automatically.

You can by using calendar sets. As of the current date, you would need to install Periodic Notes using the BRAT plugin to get this feature, as calendar sets are only available on the beta release.

Thanks, I will check it out!


Prevent lockscreen

Would it be possible to prevent the screen of being locked while a video is playing?
It's just an idea, but it's often that the video is long enough for the screen to lock itself and it requires that the user authenticate to be able to use the controls.

This would be different for any given OS.
Why not just change your screensaver/lock setting?

I agree that that's a workaround, but it's very inconvenient to keep changing the lock settings every time I want to watch something, and leaving it disabled altogether is unfeasible for security reasons.
Couldn't there be a partial implementation where this feature is available for the OS's it was coded for?
I ask this because I know nothing about it, but is it really that different for each OS?

Yeah, it is. But I guess adding support for MacOS would be easy, just calling caffeinate :)


python311Packages.scikit-rf: 0.30.0 -> 0.31.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.scikit-rf is: A Python library for RF/Microwave engineering
meta.homepage for python311Packages.scikit-rf is: https://scikit-rf.org/
meta.changelog for python311Packages.scikit-rf is: https://github.com/scikit-rf/scikit-rf/releases/tag/v0.31.0
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.31.0 with grep in /nix/store/mi89riydggp3c69g2ap9c71vzbwz4w53-python3.11-scikit-rf-0.31.0
found 0.31.0 in filename of file in /nix/store/mi89riydggp3c69g2ap9c71vzbwz4w53-python3.11-scikit-rf-0.31.0

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
python311Packages.scikit-rf

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/mi89riydggp3c69g2ap9c71vzbwz4w53-python3.11-scikit-rf-0.31.0 \
  --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 python311Packages.scikit-rf https://github.com/r-ryantm/nixpkgs/archive/ce8999ae596f55ca66eda709ba245849a02a4800.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/ce8999ae596f55ca66eda709ba245849a02a4800#python311Packages.scikit-rf

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/mi89riydggp3c69g2ap9c71vzbwz4w53-python3.11-scikit-rf-0.31.0
ls -la /nix/store/mi89riydggp3c69g2ap9c71vzbwz4w53-python3.11-scikit-rf-0.31.0/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:

python311Packages.scikit-rf

Maintainer pings
cc @lugarun for testing.

@ofborg build python311Packages.scikit-rf python311Packages.scikit-rf.passthru.tests