TAB should select a result

This was previously in issue #4578 and then closed and referred to #3472 but I do not see any code change behind it in the source.
When a user opens Select2 and TABs, can we have the result selected? TAB seems like it should select, not close.

yes we have the same problem? I tried with the events but cannot make to work.

I figured out a workaround:
`
$(document).ready(function () {
...
var $selects = $('select');
if ($selects.length > 0) {
for (var i = 0; i < $selects.length; i++) {
$($selects[i]).parents('.form-group').attr('tabindex', '0');
}
}
});
`

OR... you could just add TAB to the results.select like the previous issues stated would occur.

This makes sense to me, since this is how a native Select element behaves.  It is unclear how this would translate to multi-select, however.

Even it does not work in official demo at https://select2.org/getting-started/basic-usage

We don't have immediate plans to provide this. We are focused now to fix UI bugs. But if you open a PR with unit tests, I will be glad to review and approve if everything is ok.

We don't have immediate plans to provide this. We are focused now to fix UI bugs. But if you open a PR with unit tests, I will be glad to review and approve if everything is ok.

Would you mind explaining why?

Paolo, see: https://github.com/select2/select2/issues/5367
On Sun, Sep 23, 2018 at 4:37 AM Paolo Broccardo<EMAIL_ADDRESS>wrote:

We don't have immediate plans to provide this. We are focused now to fix
UI bugs. But if you open a PR with unit tests, I will be glad to review and
approve if everything is ok.
Would you mind explaining why?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/select2/select2/issues/4820#issuecomment-423803734,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQAS78uBr_YTg37wWjdWZpTTmX5A-NQRks5ud1ZEgaJpZM4MUoi_
.

This seems like a critical problem and makes stock select2 unusable in my product. For data entry, people expect to be able to start typing, then hit tab to select the highlighted result.

I am not sure why this was originally closed. I am going to ping @kevin-brown  to get his opinion.

I just confirmed that the behaviour of Chrome when you hit tab is to select the currently highlighted option and close. Right now we just close, but we do not select the currently highlighted option.
https://github.com/select2/select2/blob/48775d027c3e301b0bd2c4bfefbf1e1536e94cee/src/js/select2/core.js#L332-L334
Tab should behave more like the enter key rather than the esc key.

Same. Wish selecting via tab was default functionality.

Unfortunately the wait for this functionality is very long, users expect this to work by default.
I managed to create a workaround for it;
$.fn.select2.amd.define("select2/TabSelect",
  ['select2/core', 'select2/utils', 'select2/keys'],
  function(Select2, Utils, KEYS) {
    return function($el, options) {
      function TabSelect($element, options) {
        TabSelect.__super__.constructor.call(this, $element, options)
      }

      Utils.Extend(TabSelect, Select2)

      TabSelect.prototype._registerDomEvents = function() {
        this.on('keypress', (e) => {
          let key = e.which
          if (this.isOpen() && key === KEYS.TAB) {
            this.trigger('results:select', {});
          }
        })

        TabSelect.__super__._registerDomEvents.call(this)
      }

      return new TabSelect($el, options);
    }
  }
);

const TabSelect = $.fn.select2.amd.require('select2/TabSelect')

TabSelect($('select'), {/*options*/})

check out the selectOnClose option. it solved my issue.
h/t KevinBrown on S/O

Implemented in https://github.com/select2/select2/pull/5759 to bring us more in line with standard browser behaviour.

Implemented in https://github.com/select2/select2/pull/5759 to bring us more in line with standard browser behaviour.


run the authorization plugin

Hi,
what are the differences between  runs the authorization plugin directly on the host or inside a container ?
Many thanks.
Ibrahim

Hello @alobaidan, no difference, it's a static binary.


⚠ Bofrost.de has degraded performance

In 5ba552f, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1376 ms

Resolved: Bofrost.de performance has improved in aba7f49.


PowerPC page size issue with released binaries

The released binaries for powerpc64le don't run on 64k page size systems, but uv runs on those systems when compiled from source.
~/Downloads
❯ ./uv-powerpc64le-unknown-linux-gnu/uv -V
<jemalloc>: Unsupported system page size
<jemalloc>: Unsupported system page size
memory allocation of 56 bytes failed
Aborted

~/Downloads
❯ ./uv-powerpc64le-unknown-linux-musl/uv -V
<jemalloc>: Unsupported system page size
<jemalloc>: Unsupported system page size
memory allocation of 56 bytes failed
Aborted

~/Downloads
❯ ./uv-0.3.2/target/release/uv -V
uv 0.3.2

~/Downloads
❯ uname -a
Linux behemoth 6.1.0-23-powerpc64le #1 SMP Debian 6.1.99-1 (2024-07-15) ppc64le GNU/Linux

~/Downloads
❯ lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux 12 (bookworm)
Release:	12
Codename:	bookworm

~/Downloads
❯ getconf PAGESIZE
65536

This may be an issue since I think most ppc64 systems use 64k as that seems to be the default. As far as I know, the discontinued Void Linux PPC and Chimera Linux are the only ppc64 systems which used 4k pages.

Is this a duplicate of https://github.com/astral-sh/uv/issues/4647 but for our distributions?

Yes, sorry I missed that. It's also not clear that issue is with the released binaries from the GitHub releases page or something else, but I think aarch64 has the same issue with some distributions but I'm not sure.
This is an issue with the ppc64le binaries on the releases page.

Any idea how to approach fixing this? Do we need to set a different page size during build?

I'd say just have a note in the readme, release notes, or the binary file name to indicate the binary expects 4k pages on ppc64 (and probably arm) where 4k isn't the default. As for how to have your build environment run with a 64k page size when you likely aren't running on bare metal, I don't know. Can Docker allow running with different page sizes?

We do this
https://github.com/astral-sh/uv/blob/e097f948c9eca7fb09948d73ac03248363c8ce7a/.github/workflows/build-binaries.yml#L574
per

https://github.com/gnzlbg/jemallocator/issues/170
https://github.com/astral-sh/ruff/issues/3791

That looks good for ARM devices.

Maybe build from source and cache the binary for your CI? The build is pretty simple and straightforward.

Looks like this was fixed for ppc64le in Ruff using the same build flags that are being passed to maturin for aarch64. Could the same fix be applied to uv?
https://github.com/astral-sh/ruff/issues/10073

I'm happy to review a PR and see if it fixes it.


empowerer depowered

the empowerer doesn't appear to work. Can't open the ui, can only put the main component in. can't feed it power.

Could you send a video and/or a list of steps for reproduction?

craft empowerer, place it down. No ui appears when right clicking. Cannot feed power into it as energy cables don't connect to it. Also won't charge when placed adjacent to energy blocks that should be able to feed it power. Can only feed ingredient to its main slot which appear but can't do anything with them.

The empowerer is a multiblock structure, and won't do anything on its own. You'll need to place it in a cross shape surrounded by display stands, and power the display stands.

It would be nice if that was stated in the guide book but there are seemingly missing entries


Fix first batch of mobility issues on website

The Google Search Console for www.pulumi.com is reporting a lot of "mobility issues" for pages. I suspect that all of these are duplicates of a small class of core issues in our layouts and/or CSS.
Mobility Usage dashboard
https://search.google.com/u/1/search-console/mobile-usability?resource_id=sc-domain%3Apulumi.com&hl=en
I don't think we want to spend the time to fix 100% of these issues in the current milestone. But if we time-boxed it to ~5-10 targeted fixes, I would guess we can remove a lot of these problems.
Now as far as the core dev/test loop, do not visit https://search.google.com/test/mobile-friendly. As that seems to report fewer items than the more in-depth Google Search Console. Instead, use the page here, and click "TEST LIVE URL":
https://search.google.com/u/1/search-console/inspect/mobile-usability?resource_id=sc-domain%3Apulumi.com&id=DIp3ZwAMy200QN_SIq3vPQ&hl=en
That will point out:

Content is wider than screen
Clickable elements too close together

Unfortunately for both of those, it doesn't tell us exactly what element(s) on the page are the offenders. But it is close enough to get started on some sort of investigation.
Part of https://github.com/pulumi/home/issues/514

#1426 fixed all Content wider than screen errors.

Looks like Clickable elements too close together's all good now, too.

... and Text too small to read looks green now, too.
The Mobile-Friendly overview doesn't seem to have updated yet, but individually clicked URLs are all green, with two exceptions:

https://www-production.pulumi.com/docs/quickstart/aws/modify-program/, which is presumably happening because the page has been indexed -- we've since set a canonical URL, so it shouldn't affect SEO negatively, but since it's the result of a production build, Disallow: * isn't applied -- but the page fails the CSS integrity check. If we can somehow block this host from responding at all, that'd be best, but I'm not concerned about this page's mobile friendliness.

https://www.pulumi.com/blog/page/3/. For some reason, Google's test UI is reporting issues with this page that have been fixed with all other pages, but the page is clearly okay, so I'm comfortable ignoring this for now.

Closing as fixed by #1426.

but the page fails the CSS integrity check. If we can somehow block this host from responding at all, that'd be best.

The www-production DNS record was created as part of the devstack. So it seems like we might want to just update the underlying Pulumi program to no longer create that record... I'd need to think about it a little more.

https://www.pulumi.com/blog/page/3/. For some reason, Google's test UI is reporting issues with this page that have been fixed with all other pages

I would guess it has to do with a particular blog post on that page, right? e.g. whatever markup is in its particular summary blurb? If we ignore it for now, I just wonder if it will come back as /page/4 and /page/5, etc.

I would guess it has to do with a particular blog post on that page, right?

I'd guess the same thing, so 🤷♂. Could definitely spend more time getting to the bottom of why the bot isn't happy with something about this page, but as a human looking at it on a real device, and in desktop emulators, I'm not seeing any issues, so I'm okay with it for now.


TypeError: Expected state_dict to be dict-like, got <class 'NoneType'>

HI:  I use the face-editor in img2img script(figure0),
"TypeError: Expected state_dict to be dict-like, got <class 'NoneType'>"  this issue happen when i clicked "generate"(figure1)
                                                             figure0

                                                            figure1

got it   thank a lot


VSTest Task doesn't stop after test session times out

Environment

Server - VSTS

Account Name - PBIX
Team Project Name - PowerBIClients
Build Definition Name/Build number - Desktop E2E Tests v2 (Custom) / desktop_e2e_v2_custom_20180529.3

Agent - Private

Version - 2.133.3
OS - Windows Server 2012 R2

Issue Description
We have some UI tests that run on a machine. The agent is setup to run interactively. The build definition that installs the tests first runs the "Visual Studio Test Platform Installer" task to install the framework to run the tests, then runs the "Visual Studio Test" task to run the tests.
The "Visual Studio Test" task has a .runsettings file with a TestSessionTimeout of 1 hour. The task itself has a timeout of 1.5 hours.  When the TestSessionTimeout is hit, tests are stopped running but the task doesn't finish. It waits until its timeout has elapsed and then stops the task.  This results in longer build times and the partial test results are not uploaded to the server.
Any ideas why the Visual Studio Test task does not return then the TestSessionTimeout is hit?
Error logs
2018-05-29T18:03:19.1354975Z ##[section]Starting: Run Desktop E2E Tests (ImportFromMinerva disabled)
2018-05-29T18:03:19.1385468Z ==============================================================================
2018-05-29T18:03:19.1385969Z Task         : Visual Studio Test
2018-05-29T18:03:19.1386815Z Description  : Run unit and functional tests (Selenium, Appium, Coded UI test, etc.) using the Visual Studio Test runner. Test frameworks that have a Visual Studio test adapter such as xUnit, NUnit, Chutzpah, etc. can also be run. Tests can be distributed on multiple agents using this task (version 2).
2018-05-29T18:03:19.1387625Z Version      : 2.5.12
2018-05-29T18:03:19.1387993Z Author       : Microsoft Corporation
2018-05-29T18:03:19.1388465Z Help         : [More Information](https://go.microsoft.com/fwlink/?LinkId=835764)
2018-05-29T18:03:19.1389032Z ==============================================================================
2018-05-29T18:03:20.1112389Z Run the tests locally using vstest.console.exe
2018-05-29T18:03:20.1113889Z ========================================================
2018-05-29T18:03:20.1123992Z Test selector : Test assemblies
2018-05-29T18:03:20.1127052Z Test assemblies : D:\_work\3\b/DataExplorerBinaries/Tests/PowerBITests.dll
2018-05-29T18:03:20.1133671Z Test filter criteria : Priority=1&(Testcategory=ReportViewTests|Testcategory=SortTests|Testcategory=ReportPageListTests|Testcategory=InsertImageTest|Testcategory=InsertVisualTests|Testcategory=ImportCustomVisualTests|Testcategory=AnalyticsTests|Testcategory=SaveFileTests2)&(Name!=CutCopyPasteRibbonTest&Name!=UndoRedoKeyDownTest&Name!=CopySwitchViewsAndPasteKeyDownTest&Name!=InsertImage&Name!=CopySwitchViewsAndPasteRibbonTest&Name!=InsertTextbox&Name!=FieldListRenameTable&Name!=FieldListRenameColumn&Name!=FieldListDeleteTable&Name!=MapVisualBingAjaxCallCrossOriginException&Name!=UndoRedoImageVisualTest&Name!=ImportFromMinerva)
2018-05-29T18:03:20.1139785Z Search folder : D:\_work\3\s
2018-05-29T18:03:20.1142562Z Run settings file : D:\_work\3\s\tools\RollingDesktopE2E\desktopE2E.runsettings
2018-05-29T18:03:20.1146392Z Run in parallel : false
2018-05-29T18:03:20.1148632Z Run in isolation : false
2018-05-29T18:03:20.1167488Z Path to custom adapters : null
2018-05-29T18:03:20.1169533Z Other console options : null
2018-05-29T18:03:20.1170973Z Code coverage enabled : false
2018-05-29T18:03:20.1173824Z Rerun failed tests: false
2018-05-29T18:03:20.7629169Z VisualStudio version selected for test execution : toolsInstaller
2018-05-29T18:03:20.9213438Z ========================================================
2018-05-29T18:04:29.2111850Z [command]D:\_work\_tool\VsTest\15.8.0-preview-20180510-03\x64\tools\net451\Common7\IDE\Extensions\TestPlatform\vstest.console.exe @D:\_work\_temp\92622971-636a-11e8-a0d6-e77b5ffe9016.txt
2018-05-29T18:04:31.3268963Z Microsoft (R) Test Execution Command Line Tool Version 15.8.0-preview-20180510-03
2018-05-29T18:04:31.3270134Z Copyright (c) Microsoft Corporation.  All rights reserved.
2018-05-29T18:04:31.3270462Z
....
2018-05-29T18:15:59.1925113Z Passed   DisableSecurityWarningPromptFromWarningDialog
2018-05-29T18:16:27.7871993Z Passed   TestSecurityWarningPromptSettingFromOptionsDialog
2018-05-29T19:04:30.9972418Z Aborting test run: test run timeout of 3600000 milliseconds exceeded.
2018-05-29T19:04:31.1232064Z Results File: D:\_work\3\s\TestResults\vsoagent_TST-TA-PB-G1-02_2018-05-29_18_09_35.trx
2018-05-29T19:04:31.1258731Z
2018-05-29T19:04:31.1274754Z Total tests: Unknown. Passed: 5. Failed: 2. Skipped: 4.Test Run Aborted.
2018-05-29T19:04:31.1275271Z
2018-05-29T19:04:31.1350979Z Test execution time: 1.0000 Hours
2018-05-29T19:27:04.3513901Z ##[error]The operation was canceled.
2018-05-29T19:27:04.3557319Z ##[section]Finishing: Run Desktop E2E Tests (ImportFromMinerva disabled)

@compuguru Thanks for reporting. Can you share the logs of this run at<EMAIL_ADDRESS>

@compuguru were you able to send the logs?

@prawalagarwal Yup, I sent it on May 31st. Subject of the email is "VSTest Task doesn't stop after test session times out #7318"

@compuguru are your tests selenium based tests?

@compuguru any updates here?

Sorry for the late response. They're not selenium tests. Let me see if I can come up with a reliable repo. If not, I'll close this issue.

@compuguru the general trend we have seen here is that the tests either start certain processes (in case of selenium its browsers) or hold on to some resources that don't get closed or killed and vstest.console.exe waits on these child processes on connections to close before exiting thus causing your timeout.

@compuguru closing this for now. Please re-open if you get a reliable re-pro.

@prawalagarwal @ShreyasRmsft
Hi,
I have been facing the same issue, while trying to on board our product to continuous testing using Selenium. Locally all our Selenium tests are passing, however they are failing on AzDev Ops instead.
I’ve tried following this tutorial
https://docs.microsoft.com/en-us/azure/devops/pipelines/test/continuous-test-selenium?view=vsts
But I’m facing few issues:

Unable to finish/terminate VSTest task (it keeps running indefinitely until I add timeout in control options)
Unable to collect video recordings of the test run https://docs.microsoft.com/en-us/azure/devops/test/collect-screenshots-and-video?view=vsts , so cannot debug failures on the pipeline

Clearly, if the VSTest task were to terminate gracefully, it should ideally publish test results including screenshots/video_recordings, so that we could debug why some test cases are failing on remote agent.
But the VSTest task is not closing, I've already tried multiple timeout values and hosted agent versions but still the same issue.
I've also mailed multiple instances of my logs during testing, to the alias mentioned above.


Add topic management

Add topic management methods (subscribe/unsubscribe) to the client.
Add FcmOptions attr to message dataclass.

Please update your branch, as it is out-of-date, and we will be good to go further.


Feature Request: made the seek backward/forward time configurable

Please consider making the seek backward/forward time configurable, presumably through an attribute on the element such as in the following:
<media-seek-backward-button amount="10"></media-seek-backward-button>

The amount, 30 seconds, is currently hardcoded as a constant used in the line: https://github.com/muxinc/media-chrome/blob/6c6d8576be6c80cf7f0acebf951763fa42dd21db/src/js/media-seek-backward-button.js#L44
The small visible number in the control bar curved arrow would also need to update to reflect the new seek back amount.

Hey @ShaunDychko just a heads up that this is a feature we're planning on working on soon and has a related discussion here: #115


chore: generate brillig opcodes for an empty function

Description

Problem*

Resolves
Summary*
This PR sets out to compile noir functions to brillig and creates a brillig acir opcode for unsafe functions.
The mechanism for doing this is added to this PR but:

brillig bytecodes definition are temporarily put inside a file because they are not available yet from ACVM
brillig compilation returns a STOP opcode for all functions, it will be implemented in a later PR.
brillig acir opcode is not added and have a todo!() instead, because the opcode is not available from ACIR.
We assume no argument nor return value from the function. They will be implemented in a later PR.

Example

Before:

After:

Documentation

[ ] This PR requires documentation updates when merged.

[ ] I will submit a noir-lang/docs PR.

[ ] I will request for and support Dev Rel's help in documenting this PR.

Additional Context

PR Checklist*

[ ] I have tested the changes locally.
[ ] I have formatted the changes with Prettier and/or cargo fmt on default settings.

I merged with the 'base branch', should the PR still target master or rather the base branch?

I merged with the 'base branch', should the PR still target master or rather the base branch?

I have changed the branch to target the base branch


Recipe: Simple push notification (without payload)

We should showcase both immediate notifications (with TTL=0) and long-lived ones (with TTL > 0).


capture output from various az cli commands

@jchauncey,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Mock async SQLAlchemy 2.0

Describe the bug
Hi, I start to apply async sqlalchemy to my project and got stuck as mocking an AsyncSession
To Reproduce
CRUD function:
async def get_record_by_id(db: AsyncSession, user_id: int) -> Optional[sql_models.User]:
    result = await db.execute(select(sql_models.User).filter(sql_models.User.id == user_id))
    result = result.scalars().first()
    return result

Unit test function:
@pytest.mark.asyncio
async def test_get_investment_record_by_id():
    mock_result = AlchemyMagicMock()
    mock_result.scalars.return_value.first.return_value = user_obj

    mock_db = AlchemyMagicMock()
    mock_db.execute.return_value = mock_result

    user_id = 1234
    await get__record_by_id(mock_db, user_id)
    mock_db.execute.assert_called_with(select(sql_models.User).filter(sql_models.User.id == user_id))

Outcome:
E       TypeError: object AlchemyMagicMock can't be used in 'await' expression

Expected behavior

AlchemyMagicMock support async

Desktop (please complete the following information):

OS: Ubuntu
Version 20.04

I would also find this feature useful 👍

I also would like this

Any updates on this?

hi, I share an alternative way to mock AsyncSession
`
from unittest.mock import AsyncMock
from unittest.mock import MagicMock
@pytest.mark.asyncio
async def test_get_investment_record_by_id():
mock_result = MagicMock()
mock_result.scalars.return_value.first.return_value = user_obj
mock_db = AsyncMock(return_value=asyncio.Future())
mock_db.execute.return_value = mock_result

user_id = 1234
await get__record_by_id(mock_db, user_id)
mock_db.execute.assert_called_with(select(sql_models.User).filter(sql_models.User.id == user_id))`


Improve username behavior

Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[x] Tests pass
[x] Appropriate changes to README are included in PR

Done with validtaions '
@username


💅 Enum Initializer putting initialization inside inline comment

Environment information
CLI:
  Version:                      1.5.3
  Color support:                true

Platform:
  CPU Architecture:             x86_64
  OS:                           windows

Environment:
  BIOME_LOG_DIR:                unset
  NO_COLOR:                     unset
  TERM:                         unset
  JS_RUNTIME_VERSION:           "v20.9.0"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "npm/10.1.0"

Biome Configuration:
  Status:                       Loaded successfully
  Formatter disabled:           false
  Linter disabled:              false
  Organize imports disabled:    false
  VCS disabled:                 true

Workspace:
  Open Documents:               0

Rule name
lint/style/useEnumInitializers
Playground link
https://biomejs.dev/playground/?code=ZQBuAHUAbQAgAFMAZQB2AGUAcgBpAHQAeQAgAHsACgAgACAAIAAgAEkAbgBmAG8AIAA9ACAAMQAsACAALwAvACAATgBvAHQAIABhACAAcAByAG8AYgBsAGUAbQAsACAAcwBvAG0AZQB0AGkAbQBlAHMAIABhACAAbQBpAHMAdABhAGsAZQAKACAAIAAgACAAQQBkAHYAaQBzAG8AcgB5ACwAIAAvAC8AIABOAG8AdAAgAGEAIABwAHIAbwBiAGwAZQBtACwAIABvAGYAdABlAG4AIABhACAAbQBpAHMAdABhAGsAZQAKACAAIAAgACAAQwBhAHUAdABpAG8AbgAsACAALwAvACAATQBpAG4AbwByACAAZQByAHIAbwByACwAIABuAG8AbgAtAHAAcgBlAHYAZQBuAHQAaQBuAGcACgAgACAAIAAgAFcAYQByAG4AaQBuAGcALAAgAC8ALwAgAFMAZQByAGkAbwB1AHMAIABlAHIAcgBvAHIALAAgAHAAcgBlAHYAZQBuAHQAcwAgAHAAcgBvAGQAdQBjAHQAaQBvAG4ACgAgACAAIAAgAEUAcgByAG8AcgAgAC8ALwAgAEMAcgBpAHQAaQBjAGEAbAAgAGUAcgByAG8AcgAsACAAcAByAGUAdgBlAG4AdABzACAAZABlAHYAIABhAG4AZAAgAHAAcgBvAGQAdQBjAHQAaQBvAG4ACgB9AA%3D%3D
Expected result
enum Severity {
	Info = 1, // Not a problem, sometimes a mistake
	Advisory = 2, // Not a problem, often a mistake
	Caution = 3, // Minor error, non-preventing
	Warning = 4, // Serious error, prevents production
	Error = 5 // Critical error, prevents dev and production
}

Actual Result
enum Severity {
	Info = 1, // Not a problem, sometimes a mistake
	Advisory = 2, // Not a problem, often a mistake
	Caution = 3, // Minor error, non-preventing
	Warning = 4, // Serious error, prevents production
	Error // Critical error, prevents dev and production = 5
}

Code of Conduct

[X] I agree to follow Biome's Code of Conduct

Seems like this only happens when the last element is missing a comma. I can look into this one :)

Forgot to link to the issue in the pr but this one can be closed because https://github.com/biomejs/biome/pull/1650 was merged


squid:S00118 - Abstract class names should comply with a naming convention

This pull request is focused on resolving occurrences of Sonar rule squid:S00118

Abstract class names should comply with a naming convention
You can find more information about the issue here:
https://dev.eclipse.org/sonar/coding_rules#q=squid:S00118
Please let me know if you have any questions.
M-Ezzat

Prefixing abstract classes with Abstract is a ridiculous rule, as the 'abstract` keyword already converys the meaning. I'm therefore rejecting this PR.


cci task run upload_beta initiates a Major Release

I have made my tests fail in order to reproduce this.
cci task run upload_beta -o name 'package'   --org packaging
results in a major release in our current packaging org:

Running cci task run upload_beta -o name 'package'   -o production false --org packaging  works as expected.

I'm a little stumped on this one.  We've been running the release_beta flow that calls upload_beta with no extra options since January without ever seeing this.  Reviewing the relevant code, it seems that it will default to production = False:
https://github.com/SalesforceFoundation/CumulusCI/blob/master/cumulusci/tasks/salesforce.py#L1114-L1119
Here's how the upload_beta task is defined in the cumulusci.yml:
https://github.com/SalesforceFoundation/CumulusCI/blob/master/cumulusci/cumulusci.yml#L209-L211
One possibility that might explain this.. Does this only occur when there's an Apex test failure?  I know the package upload UI has scared me a few times before thinking that it was uploading a production version when it was really uploading a beta.  It doesn't show that its a beta until the upload completes.

I think we should close this issue. I couldn't not reproduce it since the initial screenshot.


Embeded block is super long with images pasted under it.

I created an embed automatically and then pasted images after it and it was making the embed super long for no reason.
In the screenshots I provide below, you can see that it spans longer than 2 pages. I thought adding the random letters before the images would help but they do not. I have tried re-creating the images as well as enabling debug mode to see any errors. No errors it is just super long for no reason.
The last screenshot I am adding (3rd) it is simply there so you can see how far down the page I had to scroll before I got to my screenshots/text.

Here is a gif video showing this as well: https://i.imgur.com/x2cprk8.gif
I don't understand why this is happening.

I can not reproduce it. Maybe there is a conflict between plugins. Can you disable other plugins and see if this issue still exists?

Closed due to inactivation.


Poll owner to see results before they are released

Great app.
Is it possible to hide the results from voters, but let the organizers see how voting is progressing before the vote cutoff?

Thanks!
Yes, it is possible! If you create a profile, then you can see the results before released while you are logged in.
Let me know if that works for you!

It did register, but it did not work. After you said it should, I realized it must have something to do with cookies, so I clicked "remember me" on the login page, and now it works. Thank you very much!


Remove copy of podman CLI implementation and migrate to new API when implemented

Current implementation is copied form podman extension and should be removed when podman desktop has new API to call podman commands https://github.com/containers/podman-desktop/issues/5990.

@benoitf where package with API definition should be placed. Should it be done the same way as for @podman-destop/api.

yes probably we should have it part of the podman extension and published on each release
probably another package or refactor the podman extension to have multiple folders (not sure it'll work fine to automatically load the extension using that way)

@benoitf Would implementing it as podman module in the extension-api similar to docker.exec work?
Here is an implementation https://github.com/containers/podman-desktop/compare/main...dgolovin:i5990?expand=1

@dgolovin there should be no podman module ( no changes in the extension loader file)
it's the other extensions that can get the extension object from get extensions(extensionName) and then use the .exports object from there

there should be no podman module ( no changes in the extension loader file)

@benoitf I can do it in similar fashion as #7961, but that will:

produce additional package in packages folder
package will be published not matter if there is no changes in API
it still would be used in extension only

For external contributions that would be required, podman extension is built-in and always present why not expose it in @podamn-desktop/api?

because the podman extension might not always be a default extension. Also users can disable the extension.
And it should always be within extensions.


Many errors on docker installation

Hello to all,
i've already tried to install in several ways (blank from source on lxc, docker compose, yarn) but i am still encountering following errors (last installed with docker on lxc).
I am thankful for any help, Arthur.
Cardano-node:
cardano-node_1              | [0567b65f:cardano.node.ChainDB:Notice:307] [2021-04-08 20:53:36.26 UTC] Chain extended, new tip: 643a48cb8ca0b92da2f77baabd1ca7250893f2126be759eaa9feb08acad6bd26 at slot 26348925 cardano-node_1              | [0567b65f:cardano.node.LocalErrorPolicy:Error:324] [2021-04-08 20:53:44.15 UTC] IP LocalAddress "" ErrorPolicyUnhandledApplicationException (MuxError MuxBearerClosed "<socket: 30> closed when reading data, waiting on next header True") cardano-node_1              | [0567b65f:cardano.node.ChainDB:Notice:307] [2021-04-08 20:53:46.17 UTC] Chain extended, new tip: 38ae1f0b662ea78a60a75ba7f2ff03589381fbec33d451901f013136c1b46a68 at slot 26348935 cardano-node_1              | [0567b65f:cardano.node.ChainDB:Info:88963] [2021-04-08 20:53:48.05 UTC] before next, messages elided =<PHONE_NUMBER>869759 cardano-node_1              | [0567b65f:cardano.node.ChainDB:Info:88963] [2021-04-08 20:53:48.05 UTC] Ignoring block already in DB: 38ae1f0b662ea78a60a75ba7f2ff03589381fbec33d451901f013136c1b46a68 at slot 26348935 cardano-node_1              | [0567b65f:cardano.node.LocalErrorPolicy:Error:324] [2021-04-08 20:53:54.16 UTC] IP LocalAddress "" ErrorPolicyUnhandledApplicationException (MuxError MuxBearerClosed "<socket: 24> closed when reading data, waiting on next header True")
cardano-db-sync-extended
cardano-db-sync-extended_1  | [db-sync-node.Subscription:Warning:46] [2021-04-08 20:59:33.45 UTC] Identity Failed to start all required subscriptions cardano-db-sync-extended_1  | [db-sync-node.Subscription:Notice:46] [2021-04-08 20:59:34.64 UTC] Identity Restarting Subscription after 1.221642607s desired valency 1 current valency 0 cardano-db-sync-extended_1  | [db-sync-node.Subscription:Notice:46] [2021-04-08 20:59:43.43 UTC] Identity Starting Subscription Worker, valency 1 cardano-db-sync-extended_1  | [db-sync-node.Subscription:Notice:17201] [2021-04-08 20:59:43.43 UTC] Identity Connection Attempt Start, destination LocalAddress "/node-ipc/node.socket" cardano-db-sync-extended_1  | [db-sync-node.Subscription:Notice:17201] [2021-04-08 20:59:43.43 UTC] Identity Connection Attempt End, destination LocalAddress "/node-ipc/node.socket" outcome: ConnectSuccessLast cardano-db-sync-extended_1  | [db-sync-node.Handshake:Info:17201] [2021-04-08 20:59:43.43 UTC] WithMuxBearer (ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/ipc/node.socket"}) Send (ClientAgency TokPropose,MsgProposeVersions (fromList [(NodeToClientV_1,TInt 764824073),(NodeToClientV_2,TInt 764824073),(NodeToClientV_3,TInt 764824073),(NodeToClientV_4,TInt 764824073),(NodeToClientV_5,TInt 764824073),(NodeToClientV_6,TInt 764824073),(NodeToClientV_7,TInt 764824073),(NodeToClientV_8,TInt 764824073)])) cardano-db-sync-extended_1  | [db-sync-node.Handshake:Info:17201] [2021-04-08 20:59:43.43 UTC] WithMuxBearer (ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/ipc/node.socket"}) Recv (ServerAgency TokConfirm,MsgAcceptVersion NodeToClientV_8 (TInt 764824073)) cardano-db-sync-extended_1  | [db-sync-node.Mux:Info:17201] [2021-04-08 20:59:43.43 UTC] Bearer on ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/ipc/node.socket"} event: Handshake Client end, duration 0.000506936s cardano-db-sync-extended_1  | [db-sync-node.Mux:Info:17202] [2021-04-08 20:59:43.43 UTC] Bearer on ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/ipc/node.socket"} event: State: Mature cardano-db-sync-extended_1  | [db-sync-node:Info:17205] [2021-04-08 20:59:43.43 UTC] Starting chainSyncClient cardano-db-sync-extended_1  | [db-sync-node:Error:17205] [2021-04-08 20:59:43.43 UTC] ChainSyncWithBlocksPtcl: libpq: failed (no connection to the server cardano-db-sync-extended_1  | ) cardano-db-sync-extended_1  | [db-sync-node.Mux:Info:17202] [2021-04-08 20:59:43.43 UTC] Bearer on ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/ipc/node.socket"} event: State: Dead cardano-db-sync-extended_1  | [db-sync-node.Mux:Notice:17202] [2021-04-08 20:59:43.43 UTC] Bearer on ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/ipc/node.socket"} event: Miniprotocol MiniProtocolNum 5 InitiatorDir terminated with exception libpq: failed (no connection to the server cardano-db-sync-extended_1  | ) cardano-db-sync-extended_1  | [db-sync-node.Subscription:Error:17201] [2021-04-08 20:59:43.43 UTC] Identity Application Exception: LocalAddress "/node-ipc/node.socket" libpq: failed (no connection to the server cardano-db-sync-extended_1  | ) cardano-db-sync-extended_1  | [db-sync-node.ErrorPolicy:Error:4] [2021-04-08 20:59:43.43 UTC] IP LocalAddress "/node-ipc/node.socket" ErrorPolicyUnhandledApplicationException libpq: failed (no connection to the server cardano-db-sync-extended_1  | ) cardano-db-sync-extended_1  | [db-sync-node.Subscription:Warning:46] [2021-04-08 20:59:43.45 UTC] Identity Failed to start all required subscriptions cardano-db-sync-extended_1  | [db-sync-node.Subscription:Notice:46] [2021-04-08 20:59:44.71 UTC] Identity Restarting Subscription after 1.284401106s desired valency 1 current valency 0
postgres:
postgres_1                  | 2021-04-08 21:00:16.627 UTC [15771] ERROR:  relation "public.Epoch" does not exist at character 296 postgres_1                  | 2021-04-08 21:00:16.627 UTC [15771] STATEMENT:  SELECT  coalesce(json_agg("root" ORDER BY "root.pg.number" DESC NULLS FIRST), '[]' ) AS "root" FROM  (SELECT  row_to_json((SELECT  "_1_e"  FROM  (SELECT  "_0_root.base"."number" AS "number"       ) AS "_1_e"      ) ) AS "root", "_0_root.base"."number" AS "root.pg.number" FROM  (SELECT  *  FROM "public"."Epoch"  WHERE ('true')     ) AS "_0_root.base"    ORDER BY "root.pg.number" DESC NULLS FIRST LIMIT 1 ) AS "_2_root"       postgres_1                  | 2021-04-08 21:00:21.630 UTC [15771] ERROR:  relation "public.Epoch" does not exist at character 296 postgres_1                  | 2021-04-08 21:00:21.630 UTC [15771] STATEMENT:  SELECT  coalesce(json_agg("root" ORDER BY "root.pg.number" DESC NULLS FIRST), '[]' ) AS "root" FROM  (SELECT  row_to_json((SELECT  "_1_e"  FROM  (SELECT  "_0_root.base"."number" AS "number"       ) AS "_1_e"      ) ) AS "root", "_0_root.base"."number" AS "root.pg.number" FROM  (SELECT  *  FROM "public"."Epoch"  WHERE ('true')     ) AS "_0_root.base"    ORDER BY "root.pg.number" DESC NULLS FIRST LIMIT 1 ) AS "_2_root"       postgres_1                  | 2021-04-08 21:00:58.658 UTC [15771] ERROR:  relation "public.Epoch" does not exist at character 296 postgres_1                  | 2021-04-08 21:00:58.658 UTC [15771] STATEMENT:  SELECT  coalesce(json_agg("root" ORDER BY "root.pg.number" DESC NULLS FIRST), '[]' ) AS "root" FROM  (SELECT  row_to_json((SELECT  "_1_e"  FROM  (SELECT  "_0_root.base"."number" AS "number"       ) AS "_1_e"      ) ) AS "root", "_0_root.base"."number" AS "root.pg.number" FROM  (SELECT  *  FROM "public"."Epoch"  WHERE ('true')     ) AS "_0_root.base"    ORDER BY "root.pg.number" DESC NULLS FIRST LIMIT 1 ) AS "_2_root"       postgres_1                  | 2021-04-08 21:01:03.644 UTC [15771] ERROR:  relation "public.Epoch" does not exist at character 296 postgres_1                  | 2021-04-08 21:01:03.644 UTC [15771] STATEMENT:  SELECT  coalesce(json_agg("root" ORDER BY "root.pg.number" DESC NULLS FIRST), '[]' ) AS "root" FROM  (SELECT  row_to_json((SELECT  "_1_e"  FROM  (SELECT  "_0_root.base"."number" AS "number"       ) AS "_1_e"      ) ) AS "root", "_0_root.base"."number" AS "root.pg.number" FROM  (SELECT  *  FROM "public"."Epoch"  WHERE ('true')     ) AS "_0_root.base"    ORDER BY "root.pg.number" DESC NULLS FIRST LIMIT 1 ) AS "_2_root"
hasura:
hasura_1                    | {"type":"http-log","timestamp":"2021-04-08T21:01:40.553+0000","level":"info","detail":{"operation":{"query_execution_time":8.81291e-4,"user_vars":{"x-hasura-role":"admin"},"request_id":"2ebec07a-0c6d-4ead-8a87-a89c6d679c54","response_size":68,"request_read_time":2.728e-6},"http_info":{"status":200,"http_version":"HTTP/1.1","url":"/v1/query","ip":"<IP_ADDRESS>","method":"POST","content_encoding":"gzip"}}} hasura_1                    | {"type":"http-log","timestamp":"2021-04-08T21:01:45.883+0000","level":"error","detail":{"operation":{"user_vars":{"x-hasura-role":"cardano-graphql"},"error":{"internal":{"statement":"SELECT  coalesce(json_agg(\"root\" ORDER BY \"root.pg.number\" DESC NULLS FIRST), '[]' ) AS \"root\" FROM  (SELECT  row_to_json((SELECT  \"_1_e\"  FROM  (SELECT  \"_0_root.base\".\"number\" AS \"number\"       ) AS \"_1_e\"      ) ) AS \"root\", \"_0_root.base\".\"number\" AS \"root.pg.number\" FROM  (SELECT  *  FROM \"public\".\"Epoch\"  WHERE ('true')     ) AS \"_0_root.base\"    ORDER BY \"root.pg.number\" DESC NULLS FIRST LIMIT 1 ) AS \"_2_root\"      ","prepared":true,"error":{"exec_status":"FatalError","hint":null,"message":"relation \"public.Epoch\" does not exist","status_code":"42P01","description":null},"arguments":["(Oid 114,Just (\"{\\\"x-hasura-role\\\":\\\"cardano-graphql\\\"}\",Binary))"]},"path":"$","error":"database query error","code":"unexpected"},"request_id":"556e16ce-83fa-4f2b-bb14-42f2104a6e60","response_size":802,"query":{"query":"query {\n          epochs (limit: 1, order_by: { number: desc }) {\n              number\n          }\n          cardano {\n              tip {\n                  epoch {\n                      number\n                  }\n                  number\n                  forgedAt\n              }\n          }}"}},"http_info":{"status":200,"http_version":"HTTP/1.1","url":"/v1/graphql","ip":"<IP_ADDRESS>","method":"POST","content_encoding":null}}}
cardano-graphql:
cardano-graphql_1           | {"name":"cardano-graphql","hostname":"cb8d94279fec","pid":1,"level":30,"msg":"GraphQL HTTP server at http://<IP_ADDRESS>:3100/ started","time":"2021-04-08T21:00:53.612Z","v":0} cardano-graphql_1           | {"name":"cardano-graphql","hostname":"cb8d94279fec","pid":1,"level":30,"msg":"DB ready","time":"2021-04-08T21:01:18.660Z","v":0} cardano-graphql_1           | {"name":"cardano-graphql","hostname":"cb8d94279fec","pid":1,"level":30,"msg":"Initialized { module: 'HasuraClient' }","time":"2021-04-08T21:01:28.712Z","v":0} cardano-graphql_1           | {"name":"cardano-graphql","hostname":"cb8d94279fec","pid":1,"level":30,"msg":"Initializing { module: 'DataSyncController' }","time":"2021-04-08T21:01:28.712Z","v":0} cardano-graphql_1           | {"name":"cardano-graphql","hostname":"cb8d94279fec","pid":1,"level":50,"msg":"Host for metadata server does not exist","time":"2021-04-08T21:01:39.273Z","v":0} cardano-graphql_1           | {"name":"cardano-graphql","hostname":"cb8d94279fec","pid":1,"level":30,"msg":"Initializing { module: 'HasuraClient' }","time":"2021-04-08T21:01:40.449Z","v":0} cardano-graphql_1           | {"name":"cardano-graphql","hostname":"cb8d94279fec","pid":1,"level":30,"msg":"GraphQL HTTP server at http://<IP_ADDRESS>:3100/ started","time":"2021-04-08T21:01:40.832Z","v":0} cardano-graphql_1           | {"name":"cardano-graphql","hostname":"cb8d94279fec","pid":1,"level":30,"msg":"DB ready","time":"2021-04-08T21:02:05.883Z","v":0} cardano-graphql_1           | {"name":"cardano-graphql","hostname":"cb8d94279fec","pid":1,"level":30,"msg":"Initialized { module: 'HasuraClient' }","time":"2021-04-08T21:02:16.309Z","v":0} cardano-graphql_1           | {"name":"cardano-graphql","hostname":"cb8d94279fec","pid":1,"level":30,"msg":"Initializing { module: 'DataSyncController' }","time":"2021-04-08T21:02:16.310Z","v":0} cardano-graphql_1           | {"name":"cardano-graphql","hostname":"cb8d94279fec","pid":1,"level":50,"msg":"Host for metadata server does not exist","time":"2021-04-08T21:02:27.054Z","v":0} cardano-graphql_1           | {"name":"cardano-graphql","hostname":"cb8d94279fec","pid":1,"level":30,"msg":"Initializing { module: 'HasuraClient' }","time":"2021-04-08T21:02:28.224Z","v":0} cardano-graphql_1           | {"name":"cardano-graphql","hostname":"cb8d94279fec","pid":1,"level":30,"msg":"GraphQL HTTP server at http://<IP_ADDRESS>:3100/ started","time":"2021-04-08T21:02:28.590Z","v":0} cardano-graphql_1           | {"name":"cardano-graphql","hostname":"cb8d94279fec","pid":1,"level":30,"msg":"DB ready","time":"2021-04-08T21:02:48.628Z","v":0} cardano-graphql_1           | {"name":"cardano-graphql","hostname":"cb8d94279fec","pid":1,"level":30,"msg":"Initialized { module: 'HasuraClient' }","time":"2021-04-08T21:03:03.879Z","v":0} cardano-graphql_1           | {"name":"cardano-graphql","hostname":"cb8d94279fec","pid":1,"level":30,"msg":"Initializing { module: 'DataSyncController' }","time":"2021-04-08T21:03:03.880Z","v":0}

Hi @aleincsharp .
I'll close this in favour of #464
Prior to the patch you can set METADATA_SERVER_URI to https://tokens.cardano.org


Using a hardcoded working folder .vscode in the extension?

Hi,
The extension uses a subfolder in the .vscode folder of the user folder:

This path appears to be hardcoded into the extension as it is not the path we use in our VS Code installation.

Thanks.

That segment is in fact hard-coded. I haven't seen a variable to obtain the path to the set-up directory. I will check again to solve this problem.

Hi @antonkc,
vscode.extensions.getExtension('extension.id').extensionUri.path
vscode.extensions.getExtension('extension.id').extensionUri.fsPath
https://code.visualstudio.com/api/references/vscode-api#extensions
https://code.visualstudio.com/api/references/vscode-api#Extension<T>
Regards,

Actually, I already knew "context.extensionPath". This path is not the same that the one I am searching for. It is precisely because my intent is to separate user files from the one the extension requieres for running. the ".vscode" path is there only to store downloads and other temporal files.
Now that I took more time to check this, I think the problem is exclusive to the profile.

Hi @antonkc,
Do you want to use the .vscode folder of the VS Code workspace?
This folder only exists if you are in folder mode, and I don't think it is also a place to use, because it is reserved for the operation of VS Code.
Perhaps you should use the temporary folder of the system or the active user, (%temp% on Windows, to be seen for Linux).
Another solution would be to provide a parameter in the extension to declare the working folder to use, with a default value, which refers to the previous point.
I asked Copilot who referred me to a node.js module temp which allows you to manage temporary folders and files, depending on the OS used. There is also another node.js module tmp which does the same thing. They also provide tracking and automatic cleaning of temporary files created.
By analyzing the code, these modules use os.tmpdir() to obtain the temporary folder of the host system.

And the result for a Windows context:

Regards,

Greetings @FALLAI-Denis , let's focus in the profile issue in this thread.
We are not able to recreate the error. So we would appreciate a bit of help here. First, have you checked if reloading the profile fixes the problem?

We may find useful information in the output window too:

If both of these fail, I actually already did an adjustement that may fix the problem, but since we are not able to recreate it in the first place, I am not sure if it did anything. My proposition is to give you the vsix before publishing as a last resort.

Hi @antonkc,
I installed the new version 2.2.1:

I switched to English display for screenshots.
I restarted VS Code.
I reloaded the Zowe profiles using the IBM Z Open Editor command.
The Zowe Explorer output shows:

Still the same problem:

But I see in the menu a specific command to associate a profile with z/OS File Editor:

If I activate it, it does not offer me profiles present in the zowe project team profiles file that exists in my workspace, but user profiles that exist only in a team profiles file in my  personal user folder:

Clearly, it only shows profiles that exist in my user folder's team profiles file minus profiles that exist in my workspace's team profiles file...

So actually the z/OS File Editor extension only takes into account user level profiles, and does not take into account project level profiles. And if the new user profiles are hidden by project level profiles they are ignored.
See: How Zowe CLI uses configurations.
Regards.

PS:
I disabled project level team profiles (in workspace)...
But z/OS File Editor only sees one more profile:

I disabled all user profiles in my user folder to leave only team profiles at the global level:

Reload VS Code...
No improvement...

I disabled all profiles at global and project level...

This time z/OS File Editor can't find any profiles...

I only reactivate team profiles at the project level (reload Window).
no more errors at Zowe Explorer and IBM Z Open Editor level, but z/OS File Editor does not want my profiles: a protocol is required?

Indeed, the protocol is not indicated in the profiles...

Adding the protocol:

Nice!

But if I don't force a profile at the z/OS File Editor level, the file recovery is not correct, the structure of the records is not recognized, and the encoding is still not that of the profile:

If I don't force a profile at the z/OS File Editor level, the structure of the records is recognized, but the encoding is still not that of the profile:

PS 2:
Finally, I reactivated all profiles at the global level (user folder) and at the project level: all z/OSMF profiles that have a protocol are recognized, and those that do not are ignored (but no error message if at least one profile is found with a protocol).

So the problem in identifying profiles is related to the lack of a property at the profile level that has a default value in the schema.
Which was not the subject of this issue which concerns the use of a hardcoded folder to store working files.

Okey, thanks for the extensive information

This shall be the thread to discuss the profile problem.
The path is ancilliary and is a non-problem in this case. I created #7 to talk about it.


fix: Update Retrieval Augmented Generation Notebook for new Langchain connector

Waiting on https://github.com/langchain-ai/langchain/pull/10513

PR https://github.com/langchain-ai/langchain/pull/10513 has been merged! Now just waiting for a new release of 0.0.310


Fix parent artifactId in hawkular-wildfly-agent-example-jndi

@jmazzitelli could you please review and eventually merge?


Helm install v2.14.0 "validation failed" error when using a template variable with value ""

Hello,
After upgrading from v2.13.1 to v2.14.0, my chart now throws an error on helm install:
Error: validation failed: error validating "": error validating data: unknown object type "nil" in Deployment.spec.template.metadata.annotations.buildID
This seems to be due to the use in deployment.yaml file of a template variable "buildID" that is actually never declared in values.yaml.
Extract from deployment.yaml:
template:
  metadata:
    labels:
      app: {{ template "gateway.name" . }}
      draft: {{ default "draft-app" .Values.draft }}
      release: {{ .Release.Name }}
    annotations:
      buildID: {{ .Values.buildID }}

If I set the buildID variable in values.yaml file to "", I get the same error.
If I set the buildID variable in values.yaml file to any other string, such as "a", then my install works.
If I set "" to buildID in deployment.yaml (buildID: {{ "" }}), I get the same error.
If I set "" directly to buildID in deployment.yaml (buildID: ""), then my install works.
Could you please let me know if this is a known issue, or if I am missing anything here?
Thanks!

Output of helm version:
Client: &version.Version{SemVer:"v2.14.0", GitCommit:"05811b84a3f93603dd6c2fcfe57944dfa7ab7fd0", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.14.0", GitCommit:"05811b84a3f93603dd6c2fcfe57944dfa7ab7fd0", GitTreeState:"clean"}
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.11", GitCommit:"637c7e288581ee40ab4ca210618a89a555b6e7e9", GitTreeState:"clean", BuildDate:"2018-11-26T14:38:32Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.7", GitCommit:"6f482974b76db3f1e0f5d24605a9d1d38fad9a2b", GitTreeState:"clean", BuildDate:"2019-03-25T02:41:57Z", GoVersion:"go1.10.8", Compiler:"gc", Platform:"linux/amd64"}
Cloud Provider/Platform:
AKS

This bit me today as well.

Looks like it might be due to this commit:
https://github.com/helm/helm/commit/32d7f1a3fc226c1745a58b51e318b7362bc7a0bf
TL;DR  - Fix manifest validation
Unfortunately, if you have something already deployed with an empty string you can't deploy something that's "fixed" as your already deployed components will fail validation.  Your only recourse is to helm delete --purge to get rid of the offending template(s) from history and go forward.  Or roll back helm/tiller

As discussed with a community member earlier today, 32d7f1a was the change. We hadn't considered charts that were already stored in a release. #5576 should fix this, and we'd love to hear if that solves the issue in here. If so we may need to cut a 2.14.1 with the fix.

EDIT: #5576 was the PR that made the change. #5643 is the PR that should fix this. :)

I can try #5643 tomorrow unless someone beats me to it.

Wouldn't the prudent course of action to surface validation errors that were 'silently' failing before, with a warning ,that in a future release becomes an error?  Or at the least, honor a force flag or some such that allows the user to choose how to handle it?

Thank you everyone for your replies!
I tried downloading the binaries from the latest Helm Canary build but the issue still reproduces. I'm not sure that these binaries correspond to the latest version of master though.
I'm having issues building Helm locally, so I'd be really interested in the outcome of your test @fooka03 !

I'm not sure that these binaries correspond to the latest version of master though.

Check the output of helm version - that should tell you what commit your helm client and tiller are running as. Because the patch in #5643 was a server-side patch, you'll have to ensure that tiller was updated.

Same, using k8s 1.8.4 :
`Error: error validating "": error validating data: [ValidationError(Deployment.spec.template.spec.containers[1].ports[0]): unknown field "exec" in io.k8s.api.core.v1.ContainerPort, ValidationError(Deployment.spec.template.spec.containers[1].ports[0]): unknown field "initialDelaySeconds" in io.k8s.api.core.v1.ContainerPort]
Error: error validating "": error validating data: ValidationError(StatefulSet.spec): missing required field "serviceName" in io.k8s.api.apps.v1beta1.StatefulSetSpec Error: UPGRADE FAILED: error validating "": error validating data: ValidationError(StatefulSet.spec): missing required field "serviceName" in io.k8s.api.apps.v1beta1.StatefulSetSpec`

I'm not sure that these binaries correspond to the latest version of master though.

Check the output of helm version - that should tell you what commit your helm client and tiller are running as. Because the patch in #5643 was a server-side patch, you'll have to ensure that tiller was updated.

Thanks @bacongobbler ! Following your comment I upgraded my tiller:
Client: &version.Version{SemVer:"v2.14+unreleased", GitCommit:"9fb19967bab21ecb9748440a99487f2fb0560f63", GitTreeState:"clean"}
Server: &version.Version{SemVer:"canary+unreleased", GitCommit:"9fb19967bab21ecb9748440a99487f2fb0560f63", GitTreeState:"clean"}

However, I'm still getting the exact same error when running helm install. :(
Error: validation failed: error validating "": error validating data: unknown object type "nil" in Deployment.spec.template.metadata.annotations.buildID
The commit corresponds to https://github.com/helm/helm/commit/9fb19967bab21ecb9748440a99487f2fb0560f63, so it looks like the issue still reproduces in my case despite the fix.

Can we get an ETA for the hotfix? I really would like to avoid patching my server with a self-build helm/tiller. Thank you!

@daniv-msft Could you try doing this in your template yaml?
template:
  metadata:
    labels:
      app: {{ template "gateway.name" . }}
      draft: {{ default "draft-app" .Values.draft }}
      release: {{ .Release.Name }}
    annotations:
      buildID: {{ .Values.buildID | quote }}

@SeriousM for now you can rollback to 2.13.1 and wait for 2.14.1 release. I tried the commit 9fb19967 and it works for me

@SeriousM for now you can rollback to 2.13.1 and wait for 2.14.1 release. I tried the commit 9fb19967 and it works for me

we have a lot of azure devops release pipelines (30+) and each of them is trying to keep helm at the latest stable build version. I could downgrade for now but once the next build pipeline is started the version would be back on 2.14.0 and I really don't go over all the 30+ to disable the step and enable it later back again. Sorry, but I need to wait for the hotfix.
Is there any ETA on the hotfix?

@daniv-msft Could you try doing this in your template yaml?
template:
  metadata:
    labels:
      app: {{ template "gateway.name" . }}
      draft: {{ default "draft-app" .Values.draft }}
      release: {{ .Release.Name }}
    annotations:
      buildID: {{ .Values.buildID | quote }}

This is my content of the deployment.yaml file that matches the path Deployment.spec.template.metadata.annotations.buildID:
spec:
  template:
    metadata:
      annotations:
        buildID: {{ .Values.buildID }}
      labels:
        app: {{ template "fullname" . }}
        env: {{ .Values.labels.env }}

Do you think a | quote could fix the problem?

@SeriousM Oh. What error are you getting currently? And I tried the | quote with the master commit, not released version, and it will basically surround the value with double quotes, and it's useful when the value is empty, as the yaml is rendered as
  annotations:
    buildID: ""

If you don't use | quote, it will get rendered as
  annotations:
    buildID:

which will lead to a validation error that is described in the issue. I verified this by using this dummy chart that I created:
issue-5750.tar.gz

@SeriousM Oh. What error are you getting currently?

My error Error: UPGRADE FAILED: error validating "": error validating data: unknown object type "nil" in Deployment.spec.template.metadata.annotations.buildID but I don't see why. First I thought that the buildID was not passed into the cli command from azure devops but since @daniv-msft got the same error I guess it's because of the server validation.

@SeriousM Oh. What error are you getting currently?

I tried to modify my deployment.yaml by adding | quote and even remove the metadata/annotations/buildID at all but this didn't helped.
This is the error I got when I removed the buildID annotation:
Error: failed decoding reader into objects: error validating "": error validating data: unknown object type "nil" in Deployment.spec.template.metadata.annotations.buildID

In regards to a 2.14.1 release, we probably won't be able to cut a release until after KubeCon.

In regards to a 2.14.1 release, we probably won't be able to cut a release until after KubeCon.

To be sure to get this right, you mean this KubeCon?

Is this the way how you deal with broken releases?

KubeCon EU, which is next week, not November. :)

KubeCon EU, which is next week, not November. :)

So we can expect a fix in form of v2.14.1 at the 24.5.19 ?

@SeriousM The first error you got, which is
Error: UPGRADE FAILED: error validating "": error validating data: unknown object type "nil" in Deployment.spec.template.metadata.annotations.buildID
is due to the issue in the chart template yamls , which you seem to have fixed with the | quote
The next error
Error: failed decoding reader into objects: error validating "": error validating data: unknown object type "nil" in Deployment.spec.template.metadata.annotations.buildID
is due to the bad manifest in the existing release. To avoid this, the tiller should not validate the release manifests and only check the manifests that are given by the user, and that's what the PR https://github.com/helm/helm/pull/5643 (fix) does and has been merged into master. You can may be use the canary image of tiller to check if it all works for you. If the failing releases are fixed once (by upgrading with proper manifests), then if the pipeline uses 2.14 version, there won't be any validation problems

You can may be use the canary image of tiller to check if it all works for you.

How can I deploy this image?

@SeriousM With any helm client version, you can use
helm init --tiller-namespace <namespace> --upgrade --canary-image

To get the latest helm client (master), you can use this : https://helm.sh/docs/using_helm/#from-canary-builds

So it looks like 5643 does fix the manifest validation issue:
helm version
Client: &version.Version{SemVer:"v2.14.0", GitCommit:"05811b84a3f93603dd6c2fcfe57944dfa7ab7fd0", GitTreeState:"clean"}
Server: &version.Version{SemVer:"canary+unreleased", GitCommit:"9fb19967bab21ecb9748440a99487f2fb0560f63", GitTreeState:"clean"}

Release "belligerent-horse" has been upgraded.
LAST DEPLOYED: Fri May 17 10:32:12 2019
NAMESPACE: default
STATUS: DEPLOYED

RESOURCES:
==> v1/ConfigMap
NAME                             DATA  AGE
<redacted>-belligerent-horse  1     181d
<redacted>                      2     181d

==> v1/Pod(related)
NAME                               READY  STATUS       RESTARTS  AGE
<redacted>-belligerent-horse-0  1/1    Running      0         5m16s
<redacted>-belligerent-horse-1  1/1    Terminating  0         17h

==> v1/Service
NAME           TYPE       CLUSTER-IP  EXTERNAL-IP  PORT(S)   AGE
<redacted>  ClusterIP  None        <none>       8080/TCP  181d

==> v1/StatefulSet
NAME                             READY  AGE
<redacted>-belligerent-horse  2/2    181d

@SeriousM With any helm client version, you can use
helm init --tiller-namespace <namespace> --upgrade --canary-image

To get the latest helm client (master), you can use this : https://helm.sh/docs/using_helm/#from-canary-builds

Thank you very much, I will try it out asap

@fooka03 > Thanks for sharing the results of your test! Despite the fix, I'm still reproducing the issue with both my own chart and the chart provided by @karuppiah7890 (issue-5750.tar.gz). Could you please share the chart you're using, or let us know if you see any difference in your chart compared to this one?
@karuppiah7890 > With the chart you provided, for the helm install to be successful, I have to add the | quote to deployment.yaml and the buildID must also be provided in values.yaml. If I'm commenting the line to #buildID: "" or removing the | quote, then the error reproduces whereas it was working fine on v2.13.1.
Unfortunately in my case it is not really possible to upgrade the chart's files, so a fix not implying any changes to existing charts would be far easier to handle.
Am I the only one reproducing the issue despite the fix? Helm version seems to return the correct versions, but is there anything else I should verify to make sure I'm using the latest bits?
Client: &version.Version{SemVer:"v2.14+unreleased", GitCommit:"9fb19967bab21ecb9748440a99487f2fb0560f63", GitTreeState:"clean"}
Server: &version.Version{SemVer:"canary+unreleased", GitCommit:"9fb19967bab21ecb9748440a99487f2fb0560f63", GitTreeState:"clean"}

@daniv-msft In my chart, the invalid template was missing the key entirely (serviceName for a statefulset).  Since helm had set this automagically to empty string (serviceName: "") in the deployed manifest I simply added {{ .Values.serviceName | default "" | quote }} to my template.  The default filter in this case means I don't have to supply a value for serviceName.  As I mentioned in my comment, the fixed version still requires that you make changes to the new manifests in order to pass validation.  The only thing different is that it does not also perform validation against already deployed charts.  Ultimately I think in your scenario where you are unable to update your chart files you're going to be stuck using 2.13.1 until they are changed to pass validation.

@fooka03 > Thanks for your reply! I didn't understand previously that the fix would only apply to deployed charts being upgraded, and not new ones.
In my case unfortunately sticking to v2.13.1 isn't an option either. :(
The charts we created and that were working for v2.13.1 are provided to our users as part of a tool, and even though we would push a new version fixing this, we cannot force our users to use the latest version of our tool.
Pushing a new version of the tool/charts might reduce the impact, but we'll have in any case some of our users trying to install previous versions of our charts with Helm v2.14.0, and thus getting the validation error.
Even though I understand that my case is specific, isn't this change going to also break some of the other charts that were generated previously (I'm thinking of https://github.com/helm/charts/tree/master/stable)?
If this is the case, would it be conceivable to postpone the validation change to Helm v3, and/or apply @StephanX suggestion above of displaying a warning for now?

Any thoughts on a mitigation strategy, @mortent? Perhaps we should pull this out and move it over to Helm 3. While it's certainly useful, it seems like it breaks existing use cases which were previously working. What do you think about that?

@bacongobbler I agree we should pull this out. Based on the discussion here, I'm not convinced that just restricting validation to new manifests (as in #5643) would be enough to help all users. I have a PR that disables schema validation in all cases: #5760.
It would be great if someone having problems can verify that this really resolves their issues.

I just used the canary image but got the same error as before: Error: failed decoding reader into objects: error validating "": error validating data: unknown object type "nil" in Deployment.spec.template.metadata.annotations.buildID.
So I did the closest thing I could do and removed the annotations.buildID property from the deployment.yaml. This probably not the way others can solve this issue, but it you can, just remove it.
I run the 2.14.0 tiller image without problems.

@SeriousM it appears that the canary build is only based off the master branch, you would need to build #5760 yourself as it's not merged yet.
I'm in the middle of a massive outage here so I likely won't be able to test it myself today.

Thank you for your replies! I would like to test the bug fix as well, but I'm still having issues building Helm locally.
I looked at the pull-request and, even though I'm not familiar with the codebase, the change looks quite straightforward.
Would it be possible to complete the pull-request, so that I can give this a try in the next Canary build?
Worst case, if something really goes wrong, it would still be possible to revert this commit before it reaches actual users, right?

We have been using YAML forward references for the last 2 years in our values.yaml without any problems. It's not a valid YAML - but it worked and made lives of our developers easier.
YAML is way too simple and restrictive for more complex configurations, but that's the declarative language Helm used so far.
Please consider making this validation either enabled by a flag, or provide an option to disable it with a flag in an upcoming Helm 3.0.

We're backing out this change and cutting 2.14.1.

Sounds good, thank you @bacongobbler and everyone involved in fixing this!
I'll try the fix as soon as it is available.

The fun thing is that I'm getting the same validation error "" for restartPolicy for AKS... GCP, DigitalOcean, and Locally with Kubernetes Desktop it doesn't happen at all.

Any idea when v2.14.1 will be available?

@WoLfulus I'm seeing this with 2.14.0 on GKE:
$ helm upgrade my-release --install --namespace test ./my-chart/ -f ./my-chart/values.yaml
UPGRADE FAILED
Error: failed decoding reader into objects: error validating "": error validating data: ValidationError(Deployment.spec.template): unknown field "annotations" in io.k8s.api.core.v1.PodTemplateSpec
Error: UPGRADE FAILED: failed decoding reader into objects: error validating "": error validating data: ValidationError(Deployment.spec.template): unknown field "annotations" in io.k8s.api.core.v1.PodTemplateSpec

$ helm version
Client: &version.Version{SemVer:"v2.14.0", GitCommit:"05811b84a3f93603dd6c2fcfe57944dfa7ab7fd0", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.14.0", GitCommit:"05811b84a3f93603dd6c2fcfe57944dfa7ab7fd0", GitTreeState:"clean"}

@WoLfulus I'm using a handspun cluster so it's decidedly not limited to AKS.  I'm not sure how you were going about your tests to give you any insight as to why you ran into inconsistent behavior like that.
@andyast from what @bacongobbler was saying earlier, it should be sometime this week at the earliest.  They were delayed due to kubecon which was last week.
https://github.com/helm/helm/issues/5750#issuecomment-493464958

@fooka03 and @achton
It's really weird actually.
I think it has something to do with AKS (in my case), but my problem was slightly different.
I was trying to set a restartPolicy for a deployment's initContainers (which doesn't exists in the spec of a Container, but some vendors (DigitalOcean) accepted it as if kubectl was called with --validate=false).
I had to remove restartPolicy in order to make it work on AKS.
So I think in my case it had nothing to do with Helm, even though the error format is exactly the same as this issue.

when can we expect a fix for this ?

The pull-request https://github.com/helm/helm/pull/5760 disabling the validation has been merged to master by @bacongobbler (thanks!).
I assume that, as mentioned by @fooka03, the version 2.14.1 won't be available before a couple of days but I wanted to share the good news. :)

The changes have been merged onto master, so you should be able to pull the changes now.

For those that want to try the canary builds: https://helm.sh/docs/using_helm/#from-canary-builds

Has anyone been able to test the canary and confirm if the patches applied to master fixed this issue? I'd like to get this bug verified and fixed before having to cut a 2.14.1 (and a subsequent 2.14.2 if that didn't fix things). Thanks!

I will verify the fix in canary build today and will let you know the outcome.

I can confirm that for us it worked

Same thing here: I tested the fix from the latest canary build and it works for us too.

@SeriousM With any helm client version, you can use
helm init --tiller-namespace <namespace> --upgrade --canary-image

To get the latest helm client (master), you can use this : https://helm.sh/docs/using_helm/#from-canary-builds

This worked for me, thanks very much

Does anyone knows how to prevent gitlab pipelines to use helm:latest? We are deploying everything via our laptops since gitlab uses 2.14. It's taking us lots of time.

@pulpbill How do you install or get the helm client in GitLab ? Do you download from releases? or use a docker image? And you want to install 2.13.1 right?
I tried to find a docker image for helm, but couldn't find any official ones. If you want, you could build a docker image by downloading and putting helm binary in it and then you can use that image in gitlab ci config. You can find the url for downloading binaries (all versions) from releases page - https://github.com/helm/helm/releases . And you can do the same (download and install in $PATH) inside your gitlab job too, if you don't want to use docker image and docker runner in gitlab.

Let's try to keep the topic on subject. @pulpbill if you don't mind sending an email to the helm-users mailing list or by asking the gitlab team directly that'd be great; this seems like an issue with gitlab moreso than with Helm, and it doesn't seem related to the issue present here.

AutoDevops downloads helm when it runs the deploy job if you take a look here: https://gitlab.com/gitlab-org/gitlab-ce/blob/master/lib/gitlab/ci/templates/Jobs/Deploy.gitlab-ci.yml#L472
I think if you set the env var HELM_VERSION in the cicd variables it might allow you to override it but  am not sure.

Helm v2.14.1 has been released: https://github.com/helm/helm/releases/tag/v2.14.1

Hello Team, We are facing this issue in the newly released v3 as well but not in the beta version v3.0.0-beta.4. Kindly help with the resolution.

this is still happening on v3.2.4

this is still happening on v3.2.4. v3.2.3 works fine though.

Happening on 3.2.3 too on Mac

helm version
version.BuildInfo{Version:"v3.2.3", GitCommit:"8f832046e258e2cb800894579b1b3b50c2d83492", GitTreeState:"clean", GoVersion:"go1.13.12"}

I don't have access to the old code, but I did have a real issue on my chart which resulted in and error on v3.3.0 and the error was gone when I fixed it


click button "Open Sample iModel" have dialog box "Property imjs_test_project does not exists."

Your statement
https://z5h64q92x9.net/proxy_u/en-ru.ru/https/github.com/imodeljs/simple-viewer-app
https://imodeljs.github.io/iModelJs-docs-output/getting-started/
does not have enough data on which file to write "imjs_test_project"
This is only described in the video https://www.youtube.com/watch?v=SPyN8w1XEAE
add a link to it in the statement
did everything as in video but all the same I receive an error: "Property imjs_test_project does not exists."
С:\project\simple-viewer-app>npm install
run 'npm audit fix' to fix them, or 'npm audit' for details
after
npm run build
npm run start:servers
http://localhost:3000/
click button "Open Sample iModel"
have dialog box "Property imjs_test_project does not exists."

Сам нашел в чем проблема
Помогло видео https://www.youtube.com/watch?v=SPyN8w1XEAE
В моем файле по умолчанию C:\project\simple-viewer-app\src\common\configuration.ts
Отсутствовали строки для заполнения
28 imjs_test_project : "<Name of iProject>", // Set this to the name of the sample project  29 imjs_test_imodel: "<Name of iModel>", // Set this to the name of the sample iModel
After watching the video I wrote them manually and everything worked
Similar lines I have by default in another file: C:\project\simple-viewer-app\src\common\config.json
But filling them did not lead to any effect

Hi @bimmodel,
In the config.json file, the project and imodel entries are commented out:
// "imjs_test_project" : "", // Set this to the name of the sample project
// "imjs_test_imodel"  : "" // Set this to the name of the sample iModel
You need to uncomment them after you fill them out.
"imjs_test_project" : "your-sample-project-name", // Set this to the name of the sample project
"imjs_test_imodel"  : "your-sample-imodel-name" // Set this to the name of the sample iModel
Hope this helps.

Hi @roopsaini
Thank you!
Helped I forgot to remove symbol of "//" in file: C:\project\simple-viewer-app\src\common\config.json
It would be necessary to write about it in the instructions:
https://z5h64q92x9.net/proxy_u/en-ru.ru/https/github.com/imodeljs/simple-viewer-app
https://imodeljs.github.io/iModelJs-docs-output/getting-started/


feat: travis CI support for Python 3.7

Referencing https://github.com/travis-ci/travis-ci/issues/9815
listed as a current workaround until travis CI comes up with official support for 3.7

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@TheSriram Do we need to be updating tox.ini or DEVELOPMENT_GUIDE.rst with Py37 things.
If we are supporting 3.7, we should add the classifier in the classifiers dict of setup.py.

@jfuss  Yes I think we should. They are small enough that we can bundle it in this PR

we could, I had to do some wrangling with symlinks to get tox -e py36 working after adding py37 to tox.ini, but that could be because of brew's python getting updated to 3.7.0 by default.


[test] Split TestLocation column into explicit utf8/utf16 indices

Previously we were using character index, which doesn't match what any
clients want. LSP will generally want to compare to the utf16 index,
while anything else probably uses utf8.

https://github.com/apple/sourcekit-lsp/pull/136
@swift-ci please test

apple/sourcekit-lsp#136
@swift-ci please test

apple/sourcekit-lsp#136
@swift-ci please test

apple/sourcekit-lsp#136
@swift-ci please test macOS

apple/sourcekit-lsp#136
@swift-ci please test macOS


retornam/updates

Upgrade to Go 1.23.0
Update Golang packages

Approval is dependent on fixing the failures, of course. :)


add support for zx install scripts

Why?

Nicer scripting language than the shell. Suitable for more complicated installs where lots of plumbing needs to be done.
Allow for more sophisticated install scripts, for example interactive ones with different branches controlled by user input.
Potentially broader platform support out of the box.
Make it easier to write test suites for these install scripts and hook them up to CI and whatnot.
JS/TS has a much better ecosystem for static analysis.

Well, you're naming all os types under the sun though
On May 16, 2021 11:26:31 PM GMT+02:00, William Boman @.> wrote:
@. commented on this pull request.

@@ -0,0 +1,38 @@
+local uv = vim.loop

+local sep = (function()
Pretty sure. This was copied from plenary.nvim actually.

couldn't you use os.platform and for win32 use \ otherwise / ?

Isn't that pretty much exactly what it's doing right now though?
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/williamboman/nvim-lsp-installer/pull/13#discussion_r633141557

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


[bug] closeButton

Is there an existing issue for this?

[X] I have searched the existing issues

RainbowKit Version
0.5.0
wagmi Version
0.6.4
Current Behavior
I am trying to click the close button of connectModal and then do something, such as redirecting to another page, or forcing the user to not close the modal as soon as connectModal appears, and only closing the modal after connecting to the wallet.
Expected Behavior
No response
Steps To Reproduce
No response
Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)
No response
Anything else?

Have opened #1251 to offer an new API that should meet your needs:
const { connectModalOpen } = useConnectModal();
const { accountModalOpen } = useAccountModal();
const { chainModalOpen } = useChainModal();

I also updated the docs for guidance on your usecase. Typically, it is recommended that you keep RainbowKit non-interruptive so that users can connect to your dApp at their leisure.

RainbowKit is designed to be non-interruptive and responsive, so dApps should always render an interface for users whether or not they have connected their wallet. A user could connect or disconnect their wallet directly from MetaMask, so the dApp must be responsive to the underlying connection status directly.

dApps that rely on mechanisms like Sign-in with Ethereum for user verification should instead rely on the Authentication feature.


Overrides wait for ssh delay time

This patch overrides the wait for ssh delay time. This will give
containers longer to start before failing on ssh.
This is to reduce gate failures on "wait for container ssh" which occour
when ansible fails to connect to a container after creation or restart.
Connects rcbops/u-suk-dev#279
(cherry picked from commit c4fbcc4332b41998a8f60d5f0f0e6f01bc22db72)

recheck_swift
failed on setup-infrastructure

recheck_swift

recheck_ceph

@hughsaunders @git-harry This also failed attempting to publish results that did not exist.

Failure for ceph check was:
14:20:51 TASK: [Verify Checks & Alarms are registered] *********************************
14:50:51 Build timed out (after 30 minutes). Marking the build as aborted.
In verify-maas play.

recheck_ceph

LGTM 👍

Awesome! 👍


Wasm support?

Can you be more specific with what you mean here? This is a compile-time crate, so I don't think there's anything wasm specific.

Sorry for the non descriptive issue.
I couldn't get the crate to work with the wasm toolchain.
The error is comming from this line: https://github.com/Shizcow/caller_modpath/blob/aa1defd4ae427fc9ce0c423eec8f9342116487ac/caller_modpath/src/lib.rs#L287
I think because the wasm toolchain produce different deps artefacts, but i am not sure i did not end up using this crate for my use case.


lb: add hash_key support to envoy.lb endpoint metadata

Fixes #13862
Adds hash_key filter in the envoy.lb metadata key for an endpoint
If this key is set, then consistent hashing loadbalancers (maglev,
ring hash) will use its value to hash the corresponding host
Risk Level: Low
Testing: Unit testing
Docs Changes: Unknown
Release Notes: Unknown

Sorry I let the https://github.com/envoyproxy/envoy/pull/14162 close @mattklein123 It didn't let me reopen it so I rebased and recreated this PR and fixed the comment about adding a test with a non string value for the hash_key.

I made it return an EnvoyException if the hash_key is set to something other than a string. Seemed like a foot gun to leave it silently fall back to the hostname/address on misconfig.

/retest


add more metrics for slow commit log diagnostics

What is changed and how it works?

Issue Number: Ref #15175
What's Changed:

Add more metrics for slow commit log duration investigation.
In this PR, it adds raft message process wait duration and exposes raft
message recv by store counter. Together with raft-engine write duration,
we can further narrow reason of the commit log duration. With this PR,
we still cannot tell if the slowness comes from network or
raft-client's (grpc client).

Related changes

PR to update pingcap/docs/pingcap/docs-cn:
Need to cherry-pick to the release branch

Check List
Release note
None

/merge

/merge


Added import map tab

Updated compiler so that it maintains an importMap object, which contains all of the esm.sh URLs for each imported module
This importMap object is then sent within an event into the repl, which then updates the value within the monaco editor's model which is switched to when the Import Map button is pressed

This seems to build to a uno.css file in the root instead of in lib/. I wonder if unocss could process the main.css and automatically insert content there? (no big deal if not, but it would be nice)

I've just added a script that runs after the build, which should merge the generated css files and then delete the uno.css file in the root dir. I don't think it's possible to get the unocss CLI to do this, and there's nothing mentioned about it in the docs


Make email authentication case insensitive

https://github.com/saleor/saleor/issues/11277
I want to merge this change, because I want to make email authentication case insensitive. It should be possible to login under the same account using<EMAIL_ADDRESS>and<EMAIL_ADDRESS>This PR also force emails to be lower case only.

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

In therms of This PR also force emails to be the lower case only.
Should staffCreate customerCreate mutations return email to lowercase?


[ENH] Use numpy asser array equal in test_multitaper_cohere_perfect_cohere

This PR is to adress Issue #569

use numpy assert_array_equal for unit test

coverage: 86.667%. remained the same when pulling c491978962e79f2ae95868a4836e258e2c6ee64c on INM-6:enh/MultitaperCoherenceTestCase into 5b464ecd358e871719b47990c48ac039871cfd63 on NeuralEnsemble:master.


Finish TODOs in Robinhood.py

Add the custom exceptions marked as TODOs in Robinhood.py

See
https://github.com/Jamonek/Robinhood/pull/49

I'll have a look or if anyone else wants to go ahead. My time has been taken up with work and my business lately. Will definitely make more time for this project so that it may continue to thrive.

@Jamonek no worries - I actually just implemented it (see the PR). I actually worked on an early version of this with Rohan Pai a few years ago when he first wrote the article

Thank you for your hard work @dsouzarc! Very thankful to you and Rohan


Make status.address.url consistent across installations

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #2874
Type of changes
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

Feature/Issue validation/testing:
Please describe the tests that you ran to verify your changes and relevent result summary. Provide instructions so it can be reproduced.
Please also list any relevant details for your test configuration.

[ ] Test A

[ ] Test B

Logs

Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Checklist:

[x] Have you added unit/e2e tests that prove your fix is effective or that this feature works?
[ ] Has code been commented, particularly in hard-to-understand areas?
[ ] Have you made corresponding changes to the documentation?

Release note:
Now, The `status.address.url` points to the hostname only. For example, the older versions point to the url `http://sklearn-iris.default.svc.cluster.local/v2/models/sklearn-irisv2/infer`. But now it points to the url `http://sklearn-iris.default.svc.cluster.local`

/lgtm
/approve


[Web] - Space Key on Physical keyboard scrolls the list on mobile devices

In super_editor we ran into the problem in #74191, whereby the space bar on mobile causes the page scroll, rather than insert a space.
The solution that we had to use was to block Shortcuts behavior: https://github.com/superlistapp/super_editor/pull/665
super_editor doesn't use Shortcuts and therefore I believe it's an inappropriate solution for super_editor to introduce arbitrary interventions into the Shortcuts system. This seems to be either a bug or a poor architecture within Shortcuts.
Is there a way to obtain expected space bar behavior without adding Shortcuts references to our widget tree? If not, I think Flutter should update the Shortcuts architecture to make that possible.

CC @justinmc @LongCatIsLooong @Renzo-Olivares

Hi @matthew-carroll, Thanks for filing the issue. Can you please share a minimal reproducible sample that shows this behavior ?

whereby the space bar on mobile causes the page scroll, rather than insert a space.

Thanks

I reference the original issue that this is based on. That issue should have any relevant reproduction information.

thanks for the info @matthew-carroll, I  tried to reproduce the issue, and I see that the page scrolls, if the textfield does not have focus and space, is entered when in focus.
In the below video at 0:35, I am pressing space using a physical keyboard as a result the page scrolls to bottom
https://user-images.githubusercontent.com/31410839/177168333-361db80a-e1b5-4e41-975b-5dbaf676ac61.mov

flutter doctor -v (mac)
[✓] Flutter (Channel stable, 3.0.4, on macOS 12.4 21F79 darwin-arm, locale en-IN)
    • Flutter version 3.0.4 at /Users/mahesh/Documents/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 85684f9300 (4 days ago), 2022-06-30 13:22:47 -0700
    • Engine revision 6ba2af10bb
    • Dart version 2.17.5
    • DevTools version 2.12.2

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0-rc4)
    • Android SDK at /Users/mahesh/Library/Android/sdk
    • Platform android-32, build-tools 33.0.0-rc4
    • ANDROID_HOME = /Users/mahesh/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] IntelliJ IDEA Community Edition (version 2021.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 61.2.4
    • Dart plugin version 212.5080.8

[✓] VS Code (version 1.67.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.44.0

[✓] Connected device (3 available)
    • sdk gphone arm64 (mobile) • emulator-5554 • android-arm64  • Android 11 (API 30) (emulator)
    • macOS (desktop)           • macos         • darwin-arm64   • macOS 12.4 21F79 darwin-arm
    • Chrome (web)              • chrome        • web-javascript • Google Chrome 103.0.5060.53

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

[✓] Flutter (Channel master, 3.1.0-0.0.pre.1494, on macOS 12.4 21F79 darwin-arm, locale en-IN)
    • Flutter version 3.1.0-0.0.pre.1494 on channel master at /Users/mahesh/Documents/flutter_master
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 829bddf616 (3 hours ago), 2022-07-04 03:49:08 -0400
    • Engine revision e78ed7f1c9
    • Dart version 2.18.0 (build 2.18.0-251.0.dev)
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0-rc4)
    • Android SDK at /Users/mahesh/Library/Android/sdk
    • Platform android-32, build-tools 33.0.0-rc4
    • ANDROID_HOME = /Users/mahesh/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 13C100
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] IntelliJ IDEA Community Edition (version 2021.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 61.2.4
    • Dart plugin version 212.5080.8

[✓] VS Code (version 1.67.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.44.0

[✓] Connected device (3 available)
    • sdk gphone arm64 (mobile) • emulator-5554 • android-arm64  • Android 11 (API 30) (emulator)
    • macOS (desktop)           • macos         • darwin-arm64   • macOS 12.4 21F79 darwin-arm
    • Chrome (web)              • chrome        • web-javascript • Google Chrome 103.0.5060.53

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

@maheshmnj - I don't think this behavior should be intentional. Please tag a member of the team who can provide insight on this functionality.

Thanks for the clarification @matthew-carroll, Perhaps it should scroll with the space key on the desktop and not on the mobile platforms. I am labeling this issue for further insights from the team.
Triage details can be found here https://github.com/flutter/flutter/issues/107014#issuecomment-1173851302
cc: @LongCatIsLooong, @gspencergoog

Notice in my original post that when the user presses space, the app isn't even notified that the user pressed space. I might have an opinion about forcing scrolling on us, but beyond that, Flutter almost certainly shouldn't be blocking the app from receiving the space input. Doesn't matter which platform you're on.

The described behavior is indeed as designed and expected.
In web pages (even those not using Flutter), the expected behavior is to scroll on spacebar if a text field isn't focused, and those shortcuts exist because developers expect those bindings to work out of the box.  If your use case requires them to not work in that way, then it is entirely appropriate to modify the shortcuts.

Also, I agree that the key event should be given to the framework, but if modifying the shortcuts works for you, then the key event is indeed getting to the framework.

I'll remove the web label for now, unless we find that work needs to be done on the web engine side. So far it looks like the fix is purely in the framework.

Here's a video of the problem, which should contrast against the earlier video of "expected behavior":
https://user-images.githubusercontent.com/7259036/183311804-a06c50e9-cb04-4d9b-866f-62d8ccfb6f7a.mp4

In your video, it appears that the screen is scrolling on space even when the text field has focus, which is not intended behavior. Is the text field in the example a Flutter text field based on EditableText, or something else? If it's something else, then that text field needs to handle the key events correctly.

in my original post that when the user presses space, the app isn't even notified that the user pressed space.

Are you sure this is the case?  Because if modifying the shortcuts is working, then the Shortcuts widget, at least, is getting the event. Your widget should be able to get the same event and handle it, inserting a space and preventing the space shortcut from being activated.


How continue playing video after reconnect the internet?

Two cases:

When opening screen without internet
When during playing video I disable internet and then turn on back

Hi! We're devoting our time heavily in #250. Once that lands, you can listen to the player.stream.error & re-open that file.

I'll update when that PR gets over the line.

Player.stream.error is now available (with ton of other features & stability improvements) in package:media_kit 1.0.0.
dependencies:
  media_kit: ^1.0.0                              # Primary package.

  media_kit_video: ^1.0.0                        # For video rendering.

  media_kit_native_event_loop: ^1.0.5            # Support for higher number of concurrent instances & better performance.

  media_kit_libs_android_video: ^1.1.1           # Android package for video native libraries.
  media_kit_libs_ios_video: ^1.0.4               # iOS package for video native libraries.
  media_kit_libs_macos_video: ^1.0.5             # macOS package for video native libraries.
  media_kit_libs_windows_video: ^1.0.2           # Windows package for video native libraries.
  media_kit_libs_linux: ^1.0.2                   # GNU/Linux dependency package.

Refer to the README for updated project guide.


Remove invalid attributes

Headers do not have type & name attributes which are being inherited from the extended classes.

I'm restarting the test... that cache test is terribly unreliable and needs removing / rewriting.


carlikebot with teleop_twist_keyboard control

does anyone know how can i use teleop_twist_keyboard with carlikebot in ros2 humble
as this video uses teleop_twist with diff_bot robot
https://youtu.be/J02jEKawE5U?si=zKH39WVIPKfwr0t0
thanks and regards

Have you had a look into the readme of teleop_twist_keyboard?
You need to remap the topic, and take care that you use the same settings for the stamped version of the twist message: use_stamped_vel is default false on humble, but also the default for the teleop_twist_keyboard's stamped parameter.

Have you had a look into the readme of teleop_twist_keyboard? You need to remap the topic, and take care that you use the same settings for the stamped version of the twist message: use_stamped_vel is default false on humble, but also the default for the teleop_twist_keyboard's stamped parameter.

thanks for response but i am new to ros and i can not understand how do i do it .....

The remap command is written in the first section of the readme, just use the topic necessary for the bicycle_steering_controller
ros2 run teleop_twist_keyboard teleop_twist_keyboard --ros-args --remap cmd_vel:=/bicycle_steering_controller/reference
If you have further questions, I suggest that you open a question on https://robotics.stackexchange.com/questions, because this topic is not related to our repository here.


Single Line staging

https://user-images.githubusercontent.com/10099533/165257678-f69082f7-bedb-4fe3-97c0-25bd675100ae.MP4

in #298 the test was written for. The problem is that the line with the "\n" is not at the same position in the complete patch and in the staged patch:
Patch lines: 15
0 )  "Origin:  ; OldLine: 305; NewLine: 305" Content:  "\tdocument->setRenderHint(Poppler::Document::TextHinting);\n"
1 )  "Origin:  ; OldLine: 306; NewLine: 306" Content:  "\tdocument->setRenderHint(Poppler::Document::TextSlightHinting);\n"
2 )  "Origin:  ; OldLine: 307; NewLine: 307" Content:  "\tdocument->setRenderHint(Poppler::Document::ThinLineSolid);\n"
3 )  "Origin: -; OldLine: 308; NewLine: " Content:  "\n"
4 )  "Origin: -; OldLine: 309; NewLine: " Content:  "\tconst static int dpi = QApplication::desktop()->logicalDpiX();\n"
5 )  "Origin: -; OldLine: 310; NewLine: " Content:  "\tQImage image = page->renderToImage(dpi, dpi);\n"
6 )  "Origin: +; OldLine: ; NewLine: 308" Content:  "    const double scaling = 1.5; // scale to reasonable size\n"
7 )  "Origin: +; OldLine: ; NewLine: 309" Content:  "    QImage image;\n"
8 )  "Origin: +; OldLine: ; NewLine: 310" Content:  "    if(dpi)\n"
9 )  "Origin: +; OldLine: ; NewLine: 311" Content:  "        image = page->renderToImage((double)dpi, (double)dpi);\n"
10 )  "Origin: +; OldLine: ; NewLine: 312" Content:  "    else\n"
11 )  "Origin: +; OldLine: ; NewLine: 313" Content:  "        image = page->renderToImage(scaling * QApplication::desktop()->locale())\n"
12 )  "Origin:  ; OldLine: 311; NewLine: 314" Content:  "\n"
13 )  "Origin:  ; OldLine: 312; NewLine: 315" Content:  "\tdelete page;\n"
14 )  "Origin:  ; OldLine: 313; NewLine: 316" Content:  "\tdelete document;\n"
Staged linesStaged: 1
Staged patch No.  0
0 )  "Origin:  ; OldLine: 306; NewLine: 306" "\tdocument->setRenderHint(Poppler::Document::TextSlightHinting);\n"
1 )  "Origin:  ; OldLine: 307; NewLine: 307" "\tdocument->setRenderHint(Poppler::Document::ThinLineSolid);\n"
2 )  "Origin:  ; OldLine: 308; NewLine: 308" "\n"
3 )  "Origin: -; OldLine: 309; NewLine: " "\tconst static int dpi = QApplication::desktop()->logicalDpiX();\n"
4 )  "Origin: -; OldLine: 310; NewLine: " "\tQImage image = page->renderToImage(dpi, dpi);\n"
5 )  "Origin: -; OldLine: 311; NewLine: " "\n"
6 )  "Origin:  ; OldLine: 312; NewLine: 309" "\tdelete page;\n"
7 )  "Origin:  ; OldLine: 313; NewLine: 310" "\tdelete document;\n"
8 )  "Origin:  ; OldLine: 314; NewLine: 311" "\n"

It will be correctly staged, but not correctly shown:
From git-cola:


Ineffective READMe

The name of this package does not exist on Packagist. Sirolad\evangelist
Are you lying?  Mr Sirolad :flushed: and even if it exists, it should be composer require sirolad/evangelist . Please Fix!

I am very sorry, its an error of omission. It has been amended but when I required it and tried to use it locally, some files appeared locked in Sublime Text but its accessible through the my system file manager.

I dont understand. How do some files appear locked?
On 7 Oct 2015 18:01, "andela-sakande"<EMAIL_ADDRESS>wrote:

I am very sorry, its an error of omission. It has been amended but when I
required it and tried to use it locally, some files appeared locked in
Sublime Text but its accessible through the my system file manager.
—
Reply to this email directly or view it on GitHub
https://github.com/andela-sakande/evangelist/issues/8#issuecomment-146262476
.