Create 6000-ground-truth-of-voc-and-notarial-deeds-and-3000000-htr-of…

Hi there, I have added my project to the catalog. Hopefully you can accept this addition?

It looks good to me from most of the metadata perspective but I think if you could do the following it would be better:

The dataset title is quite quite long and most of all uses acronyms (VOC ?). I think it would be great if this could be either/or expanded regarding the acronyms and shorten regarding the general length of the data
There are no authors, no institutions or languages provided.

Otherwise, I'll probably compute some statistics to complete the volume key :)

And thanks for making your data known and shared !

Added and fixed stuff, looks good in the test, thanks !


GridFieldFilterHeader and ArrayLists

Affected Version
4.*
Description
GridFieldFilterHeader parameters are typed against SS_List, but since it's using a SearchContext under the hood, it only works with a DataList
    $results = $this->getSearchContext($gridField)
        ->getQuery($filterArguments, false, false, $dataListClone);

This means you don't get the issue until someone actually tries it (for example, I only realized the issue today in an app that's been in production for two years :-) )
I'm not sure what's the best course of action here:

Show some kind of runtime exception ?
Prevent adding invalid components ?
Introduce a new GridFieldConfig_ArrayList config that have components that actually work with it to make it clear the _Base is only really meant for Datalist ?
Use the filter api for ArrayLists ?

Steps to Reproduce

Create a grid field with a GridFieldConfig_Base config
Pass an ArrayList as value
Try to search => it breaks

@GuySartorelli is this still relevant with your recent work to make GridField work with ArrayList?

Dont think so, but I'd have to follow the reproduction steps to be sure.

This is mostly handled now - though the core complaint that an exception isn't thrown until someone tries to search is still a problem. The exception it throws is better now, but it still isn't thrown until someone searches, so developers could miss the fact that their config is set incorrectly.
New reproduction steps
Set up an ArrayList in a GridField.
public function getCMSFields()
{
    $fields = parent::getCMSFields();
    $list = ArrayList::create([ArrayData::create(['Title' => 'value1']),ArrayData::create(['Title' => 'value2'])]);
    $config = GridFieldConfig_Base::create();
    $fields->addFieldToTab('Root.Main', GridField::create('test', 'test', $list, $config));
    return $fields;
}

Accessing the form that owns this GridField will immediately result in this exception:
Uncaught LogicException: Cannot dynamically determine columns. Pass the column names to setDisplayFields() or implement a summaryFields() method on SilverStripe\View\ArrayData

Call setDisplayFields() as per the exception message
$config->getComponentByType(GridFieldDataColumns::class)->setDisplayFields(['Title' => 'Title']);

You can now access the form fine, but as soon as you try to search you get this exception:
Uncaught LogicException: Cannot dynamically instantiate SearchContext. Pass the SearchContext to setSearchContext() or implement a getDefaultSearchContext() method on SilverStripe\View\ArrayData

Add the search context as per the exception (the new BasicSearchContext was added in 5.2 and handles arbitrary data just fine)
$searchContext = BasicSearchContext::create(ArrayData::class);
$searchContext->setFields(FieldList::create([
    HiddenField::create(BasicSearchContext::config()->get('general_search_field_name')),
    TextField::create('Title', 'Title'),
]));
$config->getComponentByType(GridFieldFilterHeader::class)->setSearchContext($searchContext);

Searching now works without exceptions.

@maxime-rainville Probably still worth looking at throwing that second exception when the form loads instead of waiting for someone to search.


x/mobile/exp/sensor: can't reenable sensors once disabled on Android

The proxying goroutine will block on readSignal forever if all sensors are disabled on Android. Once every sensor is disabled, there is no way for other signals to be consumed by the same proxying goroutine.

I would like to reuse the the existing app looper to enable, disable and read the sensor events.
The app looper is not suffering from the indefinitely blocked case because there will be new app lifecycle events during the lifetime of an app. Reusing it sounds like a better strategy than trying to invent a preemption strategy for the sensor looper.
@crawshaw, any thoughts?

Given it a second thought, trying to wake the blocked pollAll with ALooper_wake or destroying the underlying ALooper if no sensors enabled sound like a better option than coupling the sensor package with app's ALooper.

I would prefer minimizing the number of OS-specific hooks the app package needs to export, so if this can be done inside the sensor package that would be best.

Rather than going for one of the complex proposals above, I decided to introduce a hard poll timeout which allowed the thread not to be blocked indefinitely and gave the poller a fair execution time.


New union representation

More commits to come:

[x] handle null union values
[x] handle containers in unions

(And for completeness, zjson and ndjson (including type "inference") are also outstanding but will  come on a separate PR).

Ready for review

rebased and resolved conflicts from #290

I didn't hear back on zng.ContainedType() so going ahead and making @nwt 's requested change to say union is a container, and leaving the ensuing quirk of zng.ContainedType()


Documentation Typo

In the documentation for Labels and badges, the "yellow" class is not listed as a valid option.
Additionally, the yellow label in the Demo box has the text "red label" instead of "yellow label".
If it matters, the listed CSS classes aren't in the same order as the examples in the Demo boxes.

Acknowledged. If our CSS angels don't get there first, I'll fix that one

Thanks @Asuza.


Can not generate-changelog for Azure Synapse Analytics (formerly SQL DW) database

Search first

[X] I searched and no similar issues were found

Description
Hi fellas,
I’m trying the cli command ‘generate-changelog’ for my database (dedicated SQL pool (formerly SQL DW) in Azure Synapse Analytics. this database have many schemas.
my command :
liquibase generate-changelog --changelog-file=test-changelog-dwmicbas01.xml
the error :
Unexpected error running Liquibase: Error executing SQL
SELECT SEQUENCE_NAME,
cast(START_VALUE AS BIGINT) AS START_VALUE,
cast(MINIMUM_VALUE AS BIGINT) AS MIN_VALUE,
cast(MAXIMUM_VALUE AS BIGINT) AS MAX_VALUE,
CAST(INCREMENT AS BIGINT) AS INCREMENT_BY,
CYCLE_OPTION AS WILL_CYCLE
FROM INFORMATION_SCHEMA.SEQUENCES
WHERE SEQUENCE_SCHEMA = ‘dbo’
: Catalog view ‘SEQUENCES’ is not supported in this version.
Can anyone help me with this error.
Liquibase’s version : Liquibase Community 4.17.0
SQL Server version : SQL Server 2014
Thanks in advance :smiley:
Steps To Reproduce

liquibase.properties :
changeLogFile: dbchangelog.xml
url: jdbc:sqlserver://pzbdmicb00001.database.windows.net:1433;database=dwmicbas01
username: u_pzbdmicb00001_owner
password: *******

dbchangelog.xml :

<include file="changelogs/init-db.xml" />
<include file="changelogs/add-created.xml" />

CLI command :
liquibase generate-changelog --changelog-file=example-changelog.xml

Expected/Desired Behavior
expecting a full changelog file for my database.
Liquibase Version
Liquibase Community 4.17.0
Database Vendor & Version
SQL Server 2014
Liquibase Integration
CLI
Liquibase Extensions
No response
OS and/or Infrastructure Type/Provider
Windows 10
Additional Context
I have already post in the Liquibase's Forum : https://forum.liquibase.org/t/can-not-generate-changelog-for-a-dedicated-sql-pool-formerly-sql-dw-database/7947
Are you willing to submit a PR?

[ ] I'm willing to submit a PR (Thank you!)

Hi @nvoxland
We are facing the same issue.
Can you tell us if there is any schedule behind:

Synapse support
New database support process
?
Thanks in advance!

Same issue here as well.

+1 - Same issue


github workflows to run tests

Result preview: https://github.com/youknowone/Violet/pull/1/checks?check_run_id=3893157774

Ooo… nice.
I was going to work on this over the weekend, but this makes things so much simpler.
Thanks!


Autorest Regen Preview to 3.0.0-alpha.20230914.4 by Chun Yu from refs/pull/3737/head

Triggered from https://github.com/Azure/autorest.csharp/pull/3737

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Verticals.AgriFood.Farming


When connecting via USB, disconnecting will cause the browser page to crash.

Scratch3 - micro:bit more When connecting to a micro:bit via USB, disconnecting it, including selecting "Disconnect" in the interface or simply unplugging the micro:bit from the computer, will crash the current page.
Refreshing the page will bring you back to Scratch3, but may result in the last few steps in your work not being saved.

Latest version of Google Chrome
Firmware version V0.2.3
micro:bit board version V2.00

The serial port was incorrectly closed.
This was fixed at 94f37a5f38f361a25a7363e8414efe7a42d89766  and released Release 0.2.5 · microbit-more/mbit-more-v2.


recv panic if mavlink specification is not used correctly

Message::parse should result an Result and not an Option.
This is necessary since the parser can fail if someone does not follow the mavlink specification, E.g:
https://github.com/patrickelectric/mavlink2rest/issues/7#issuecomment-633636231

This was fixed by 0.8.2


Remove ssl_key_passphrase

This setting doesn't appear to work (see elastic/logstash#1597), and is
confusing that it's still in the code.
Fixes #66

Jenkins standing by to test this. If you aren't a maintainer, you can ignore this comment. Someone with commit access, please review this and clear it for Jenkins to run; then  say 'jenkins, test it'.


Implement an optional "simple" format

This PR implements a format parameter that lets the user decide which format is being used. The default is json, so it works just like before.
The new simple format only logs the log message, like the "-o simple" parameter in the Bunyan CLI.
Fixes #14.

@printscreen Thanks for your feedback – I deleted the unused skip variable. And added support for component (child loggers in Bunyan).

Any news on this?


Liquid template transformations are available for Standard Logic Apps too

The way this doc is written makes it seem (https://stackoverflow.com/posts/comments/124464699) that this functionality is only available in Logic Apps that use an integration account. However, the functionality is also available in Standard plan Logic Apps.

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

ID: e02fc497-8e32-b0e1-6ae3-cf1039cc1c7b
Version Independent ID: 2ce45d89-18b7-8465-8ab7-bef9b544a474
Content: Convert JSON and XML with Liquid templates - Azure Logic Apps
Content Source: articles/logic-apps/logic-apps-enterprise-integration-liquid-transform.md
Service: logic-apps
GitHub Login: @divyaswarnkar
Microsoft Alias: divswa

@SvenAelterman Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

@SvenAelterman Thanks! I've created a doc work item on the backlog for triage and prioritization.

Can you also review the docs for other areas. I am looking at std and most of the docs (eg monitoring, B2B) all seem to apply to consumption/ISE.

@ahmedsza Thanks! Yes, we're continuing to work on getting the docs updated.

@ahmedsza As we have existing work items on the backlog to update the docs with info about Standard logic apps, which is being updated in priority order, I'm closing this thread for now. Thanks!
@MayankBargali-MSFT: #please-close

#assign:@ecfan


Bug related to Import NFT, Token

Describe the bug
Version test: v1.0.1(142)
UI bugs:

[x] Button Import NFT

[x] Display message This field is required when select Network valid

Logic bug

[x] Need re-select network in case import NFT, import token
Steps:

Go to the Import NFT/ Import token
Input valid NFT contract address
Input valid network
Input invalid network then input valid network
Observe screen displayed

Actual:
In steps 3: Display message Invalid contract for the selected chain
In steps 4: Import NFT succesfully
https://github.com/Koniverse/SubWallet-Mobile/assets/117999489/d2e19a14-ec59-4eb4-8d1f-c81094ae57af
Expect: Import NFT succesfully in steps 3

Version test: v1.0.2(158)
Devices test: IP 11
Validation passed.


[0.50.2] ImportError: No module named 'pydispatch'

Home Assistant release (hass --version):
0.50.2
Python release (python3 --version):
Python 3.4.2
Component/platform:
zwave
Description of problem:
After updating from 0.49.0 to 0.50.2 on one of my Pi's its ZWave setup has broken:
2017-08-04 09:03:40 ERROR (MainThread) [homeassistant.setup] Error during setup of component zwave
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/setup.py", line 194, in _async_setup_component
    component.setup, hass, processed_config)
  File "/usr/lib/python3.4/asyncio/futures.py", line 388, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup
    value = future.result()
  File "/usr/lib/python3.4/asyncio/futures.py", line 277, in result
    raise self._exception
  File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/zwave/__init__.py", line 243, in setup
    from pydispatch import dispatcher
ImportError: No module named 'pydispatch'

This module however exists:
(homeassistant) me@pi:/srv/homeassistant/lib/python3.4/site-packages $ pip3 list | grep pydispatch
pydispatch (1.1.0)

The Zwave package:
(homeassistant) me@pi:/srv/homeassistant/lib/python3.4/site-packages $ pip3 list | grep zwave
python-openzwave (<IP_ADDRESS>)

Expected:
Zwave to work, since its dependencies are met.

It seems you have an older version of pydispatcher installed. Current requirement is pydispatcher==2.0.5. I'm not sure why home assistant failed to install the correct version. Try installing pydispatcher==2.0.5 in your home assistant environment manually.
pip3 install pydispatcher==2.0.5

@MartinHjelmare I have already (manually) installed pydispatcher==2.0.5 within the virtualenv but for some reason it doesn't fix it.

What do you get if you run within the virtualenv:
pip3 list --format=legacy | grep "PyDispatcher"

It's pretty strange..
(homeassistant) homeassistant@deuropener:~ $ pip3 list --format=legacy | grep "PyDispatcher"

No output
The whole list:
(homeassistant) homeassistant@deuropener:~ $ pip3 list --format=legacy
aiohttp (2.2.3)
aiohttp-cors (0.5.3)
appdirs (1.4.3)
astral (1.4)
async-timeout (1.2.1)
axis (8)
certifi (2017.4.17)
chardet (3.0.4)
colorama (0.3.9)
Cython (0.25.2)
distro (1.0.4)
docopt (0.6.2)
enum-compat (0.0.2)
fuzzywuzzy (0.14.0)
gi (1.2)
gTTS-token (1.1.1)
hbmqtt (0.8)
holidays (0.8.1)
homeassistant (0.50.2)
idna (2.5)
Jinja2 (2.9.6)
MarkupSafe (1.0)
multidict (3.1.3)
mutagen (1.38)
netdisco (1.1.0)
netifaces (0.10.6)
packaging (16.8)
passlib (1.7.1)
phue (1.0)
pip (9.0.1)
protobuf (3.3.0)
PyChromecast (0.8.2)
pydispatch (1.1.0)
pyparsing (2.2.0)
python-dateutil (2.6.0)
python-openzwave (<IP_ADDRESS>)
pytz (2017.2)
PyYAML (3.12)
requests (2.14.2)
setuptools (36.2.7)
six (1.10.0)
slacker (0.9.50)
soco (0.12)
SQLAlchemy (1.1.4)
transitions (0.2.5)
typing (3.6.1)
urllib3 (1.21.1)
voluptuous (0.10.5)
websockets (3.2)
xmltodict (0.10.2)
yarl (0.12.0)
zeroconf (0.19.1)

Let's install it then:
(homeassistant) homeassistant@deuropener:~ $ pip3 install 'PyDispatcher==2.0.5'
Requirement already satisfied: PyDispatcher==2.0.5 in /srv/homeassistant/lib/python3.4/site-packages/PyDispatcher-2.0.5-py3.4.egg

A bit strange, one command doesn't show it and the other does.


Linter doesn't raise any issues

Hi, I continually see "No Issues" listed at the bottom of my editor. I'm sure my flake8 is successfully installed and that the executable path for it in settings, matches what I see when I enter which flake8 (~/anaconda/bin/flake8).
Is it possible that this issue is with the base linter package? What else could be causing this error?
Thanks

Do you have any other linter plugins installed? Do any of them work?
If so, can you open Atom's Developer Tools and set a breakpoint here to check whether the lint() function is even being called?

I will try another linter now and see if that helps, but it appears that lint() is being called. I've attached a screenshot with some extra debug output from stepping through that might be helpful. Let me know if I can help provide any other details.

I was able to get pylint to work, so this problem is confirmed to be specific to flake8.

I'm also getting this. JSHint and ESLint working fine in Atom, flake8 working fine on the command line (with no venvs or anything like that), getting no lint reporting for flake8

It looks like the parameters being sent to it are correct, if you place a breakpoint here what does the result object contain?

I noticed a similar behavior: when the flake8 executable couldn't be found I see an error message in a popup window. But if it is found the linter doesn't show any errors.
The result object looks like this at the above mentioned breakpoint:
Object {stdout: "", stderr: ""}

FTR I noticed that flake8 outputs nothing when called directly on the command line with the same file. pyflakes shows errors as expected. So maybe this isn't an issue with linter-flake8 but flake8 itself.

I got tricked by https://github.com/SublimeLinter/SublimeLinter-flake8/issues/20
A # flake8: noqa comment at the end of a line disables flake8 for the whole file (and not only a single line). After replacing this specific comment with # noqa flake8 and linter-flake8 worked as expected. Sorry for the noise ;)

I also had a Python file with "No Issues" even though it clearly had flake8 issues. Setting the breakpoint recomended by @Arcanemagus above didn't stop the execution, which told me that the linter was not being called at all.
Looking at the preferences for the base Linter package I found the setting "Do Not Lint Files Ignored by VCS" switched on, and the file I wanted to scan was in a section of my repository that was ignored by my top-level project git repository (because it was managed by a nested git repository which is fetched by the build tool)
As a quick reminder, if you have a complex repository layout (e.g. using zc.buildout) where some of the files you edit are ignored by the top level git directory, remember to switch off that setting.

Nice catch @leorochael!
@cscanlin Are you still having issues?

I got the same problem and for me the issue was that i had format=pylint in my ~/.config/flake8 file so the linter-flake8-regex did not work. This can be fixed in linter-flake8 by always adding --format=default to the spawn parameters so it always get the expected format.

Heh, #217 didn't actually "fix" this, but I'm going to leave this as closed since @cscanlin hasn't responded.


Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Note! I had a typo in the content I added
I wrote:
(Shift right - SQL Server 2022& and abive#41;
But it should be:
(Shift right - SQL Server 2022 and above)
I fixed it now

Learn Build status updates of commit 9b7bc13:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/t-sql/language-elements/bitwise-operators-transact-sql.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@pituach Ronen, do you mind editing the typo in the pull request title?

@rwestMSFT
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Thanks for the edit, @Court72. I'll look into this PR shortly.


Websocket is not closed upon missing pong when connection is interrupted

Websockets should be closed with WebSocketStatus.GOING_AWAY if no pong message is received within pingInterval. Why doesn't this work when connectivity is lost, e.g. with an un-plugged cable? Is this expected behaviour?
Reproduce:

With a low pingInterval (e.g. 1ms), websocket is correctly closed with closeCode==1001
With a high pingInterval (e.g. 1000ms), kill connectivity after a while, websocket will not close (closeCode is null)

import 'dart:async';

import 'package:web_socket_channel/io.dart';

void main() {
  final channel = IOWebSocketChannel.connect("ws://echo.websocket.org/",
      pingInterval: Duration(milliseconds: 1000));
  channel.stream.listen(print, onError: print, onDone: () => print('done'));
  Timer.periodic(Duration(seconds: 3), (t) {
    int time = DateTime.now().millisecondsSinceEpoch;
    channel.sink.add("message: hi, $time");
  });
  Timer.periodic(Duration(seconds: 10), (t) {
    print("close?");
    print(channel.closeCode);
  });
}

Dart SDK Version: 2.4.0
Linux

Because closeCode won't get updated until the connection is closed, which is expected. Defination here . So even connectivity is lost, the closeCode will shows null, because the websocket is not closed yet.


Add unit tests

See JIRA ticket for more info

@petersear The class names (even unqualified) are very long, plus the Sign-off comment is a requirement from them. I've fixed the typo in the commit message

Good point @JohnLBergqvist I'd overlooked the length of the class names.


Latest backup in any state should not be deleted while partial delete command

Example:
backup100 CREATING
backup99 CREATED
backup98 FAILED
...
backup0 CREATED

backup100 - newest
backup0 - oldest
Given:
We want to delete oldest one, but backup100 is still creating.
Actions:

we run ch-backup delete --purge-partial backup0
we compute deleting_backups and retained_backups and collect deduplication data
backup100's metadata is loaded with state=CREATING, so we think it could be deleted/partially deleted as well
while we downloading other backups metadata (it could take a while) backup0 is changing state to CREATED
delete command finishes metadata downloading
backup100 will be deleted, but it was created right now

Fix
Skip newest backup while purge-partial flag in delete command.
Btw, lock on backup and delete commands does not help there because metadata loading works outside of lock scope.
Also newest backup could be useful for future's backups because of deduplication.

LGTM

Btw, lock on backup and delete commands does not help there because metadata loading works outside of lock scope.

It's worth to revisit this logic. Probably we should reload metadata after acquiring lock or take lock before loading metadata.
But it doesn't supersede the changes from the current PR. As already mentioned in the PR description, it's worth to keep the newest backup for deduplication purposes regardless of its state.

I've investigated more precisely your suggestions:

Take lock before loading metadata - it is easy, I can do it right now, but it has one obvious disadvantage: it will lock command for a longer time.
Reload metadata after acquiring lock - we reload full metadata about backup there, so we could move out this line to here (the same for purge command).
Then check backup status again and if it differs from previous one (and only if it is CREATED? because CREATING -> FAILED is ok to delete) - skip deleting this backup.
It is more complex logic and maybe needs more investigation, so I am not ready to do it in current PR.

What do you think about second option and to do it separately?
@Alex-Burmak

I think we can go with the first option. Even it's a trivial change I propose to do it in a separate PR.

It's ok to hold lock for a longer time, before this feature we holder it for even longer period


chore: export metrics on warnning type during build new point

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


ghostServer.restart() not working

Issue Summary
When running Ghost as a node module (as described here), the .restart() method throws an error. The gulpfile, ghost settings and terminal output are in this gist. After installing ghost and gulp locally, you should be able to recreate the bug by running gulp test.
I'm not familiar with the software ghost is built upon, but given that running .stop() and .start() in sequence works, I thought this has to be a bug.
I'm working on a Linux Mint 18 system, running Node.js 6.9.1. I'm using Ghost 0.11.3 (latest stable).

Newbie here. Be kind....
GhostServer.restart calls GhostServer.stop which returns a promise. When the promise is resolved, it does so with self. self is then passed to GhostServer.start as the externalApp and there begins the downfall. :(
GhostServer.start ends up doing externalApp.listen which in this case is self ergo the instance itself. GhostServer doesn't have a listen method.......hope I am right. Fix should be
    // Inside GhostServer.restart, replace this.......     return this.stop().then(this.start.bind(this));     // with this.....     return this.stop().then(function(ghostServer) {         return ghostServer.start(); // for chaining....     });

Hey @c0d0g3n ! Sorry for late response and sorry to hear you are having trouble. I can confirm this bug, thanks for reporting.
@vivekannan The fix you have suggested works perfectly. A PR is very welcome.

When I run grunt validate, all the tests pass but the command ends with
an error about my Chrome browser version being incorrect or something...Can
I still make the pull request?
On Wed, Jan 4, 2017 at 4:08 PM, Katharina Irrgang<EMAIL_ADDRESS>wrote:

Hey @c0d0g3n https://github.com/c0d0g3n ! Sorry for late response and
sorry to hear you are having trouble. I can confirm this bug, thanks for
reporting.
@vivekannan https://github.com/vivekannan The fix you have suggested
works perfectly. A PR is very welcome.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/TryGhost/Ghost/issues/7760#issuecomment-270341968,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHkl-gxW1eTK_c-a2GmcgWWjTZJWbCqhks5rO3aOgaJpZM4LCyzP
.

@vivekannan that error is coming from the Ghost-Admin tests so I don't think it's relevant to this issue. It's fine to submit your PR in any case, the tests are re-run on Travis and the PR will be reviewed and tested before merging so nothing to worry about 😄


[#1206] chore(rust): ignore generated proto code in git

What changes were proposed in this pull request?
Follow up #1218
Why are the changes needed?
For #1206
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Needn't

Codecov Report

Merging #1229 (0f14e85) into master (05aba70) will increase coverage by 0.61%.
Report is 5 commits behind head on master.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #1229      +/-   ##
============================================
+ Coverage     54.60%   55.22%   +0.61%
+ Complexity     2606     2283     -323
============================================
  Files           372      337      -35
  Lines         20186    15741    -4445
  Branches       1925     1451     -474
============================================
- Hits          11023     8693    -2330
+ Misses         8502     6570    -1932
+ Partials        661      478     -183

see 36 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


install download error

wget https://github.com/ul/kak-lsp/releases/download/v5.2.2/kak-lsp.x86_64-unknown-linux-musl.tar.gz
--2018-09-21 16:21:59--  https://github.com/ul/kak-lsp/releases/download/v5.2.2/kak-lsp.x86_64-unknown-linux-musl.tar.gz
Resolving github.com... <IP_ADDRESS>, <IP_ADDRESS>
Connecting to github.com|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2018-09-21 16:21:59 ERROR 404: Not Found.

i copied the url from the releases page and it worked: https://github.com/ul/kak-lsp/releases/download/v5.2.2/kak-lsp-v5.2.2-x86_64-unknown-linux-musl.tar.gz

Thanks for reporting! Not sure how I ended up with this typo, but it should be fixed now.


new release?

@apaleyes what do you think about a new release on pypi? The quadrature package changed quite a bit in the last months.

Great, good spot! My other task is done too, and resulted in no changes in Emukit.
Shall we get to the bottom of #421 before releasing though?

Shall we get to the bottom of #421 before releasing though?

yes, sounds good.

I was away during the summer for a bit. Found one more kernel embedding as well #430 . That should now be fairly complete for quad though (famous last words).

Are we ready now for new release @apaleyes ?


Exposing refresh token in AuthContext

What does this pull request change?
I have a use case where I'd like to collect and store the refresh token for some async processes that I run but I don't have a way to get it.
Why is this pull request needed?
Currently the refresh token isn't exposed in the context

Just out of curiosity, what is the use case for this change? Are you using the refresh token for anything else than just refreshing the access token?

Hi @thedewpoint, thank you for showing interest and this pull-request.
You can easily grab the refreshToken today by accessing locaStorage and reading the ROCP_refreshToken-key.
So since most people will not need the "refreshToken", and there is a simple workaround to get it, I'm reluctant to put it in the interface as this PR proposes.

Just out of curiosity, what is the use case for this change? Are you using the refresh token for anything else than just refreshing the access token?

Yea I'd like to post it to a service where I will persist it and asynchronously refresh that token to make requests on a users behalf


OSError: [Errno 22] Invalid argument with large files (4-8 GB)

python 3.7.1
Mac OS
Processor Name: Intel Core i5
Processor Speed: 3.4 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 6 MB
Memory: 8 GB
import cdblib
import random
import time
import sys

val = 'a' * 1000000

with open("info.cdb",'wb') as f:
    writer = cdblib.Writer64(f)
    for i in range(9000):
        key = "key1_" + str(random.randint(1,10000))
        writer.put(key.encode(), val.encode())
    writer.finalize()

with open('info.cdb', 'rb') as f:
    data = f.read()
reader = cdblib.Reader64(data)

maybe I am missing something.. but I found one so post, could be related
https://stackoverflow.com/questions/48122798/oserror-errno-22-invalid-argument-when-reading-a-huge-file

Please include the full stack trace, thanks

$ python speed_test.py
Traceback (most recent call last):
File "speed_test.py", line 16, in
data = f.read()
OSError: [Errno 22] Invalid argument

I'm late to the party here, but this method provide a useful workaround.


Delete an Admin Set

As a user who has the ability to manage Admin Sets, I should see a button on the Admin Set show view (next to the Edit button) that allows me to delete the Admin Set. When I click the button, I should be asked to confirm the deletion. When the Admin Set is deleted, all relationships pointing at the Admin Set should also be destroyed.
Comments on the above, @jcoyne @hannahfrost @ggeisler?

Technically, this should be implemented as a background job as you might be re-indexing thousands of objects.  Should we ask if the user wants to move the objects to a different admin set?

Yeah, I agree we need to offer the user the opportunity to move the objects to another admin set before deleting them.

@hannahfrost @ggeisler Do y'all think this needs design, or should we wing it and use our best judgment?

I don't think the basic action needs design, @mjgiarlo, you describe it well in your initial comment. Probably obvious but the key things are using the danger color for the button and asking for confirmation (with a way to easily cancel) before destroying anything. (Similar to the Deactivate user button in https://github.com/projecthydra-labs/hyku/issues/444.)
But if we've agreed that the user should be able to move objects to a different admin set before proceeding with deleting the admin set, the interaction and wording on the confirmation dialog gets more complex. I wouldn't have a problem if you guys want to take a crack at it without a design, as long as I retain the right to suggest (hopefully only minor) changes after seeing the implementation...

as long as I retain the right to suggest (hopefully only minor) changes after seeing the implementation... (@ggeisler)

Yes, of course! Always.

@mjgiarlo @ggeisler I think an admin set should only be deletable when it is empty. This seems like an appropriate safeguard for a repository application. So the user will need to have the option to move the content to a different admin set (including the default one) or deleting the contained works deliberately before deleting the admin set. I realize that this complicates the UI. Design needed?

@hannahfrost :speech_balloon:

user will need to have the option to move the content to a different admin set (including the default one)

Yeah, this is the bit that could benefit greatly from some design, IMO.

It sounds like your "another option" above, @mjgiarlo, might also warrant some design thinking (unless the idea is to just automatically toss any objects in a to-be-deleted admin set to the default admin set, which would be easiest to do, but might be too subtle to be good UX?).
So either doing a design or having a developer try to implement it without a design is fine with me; if you want a design just put it in design needed and prioritize it and I'll come up with some ideas.

Thanks, @ggeisler. Let's see what the peeps most likely to work on this think about it:
@atz @jcoyne @tdonohue if you were working on this issue, would you be comfortable whipping up a PR without a design, or would you prefer we have more design available?

Taking a look at this today, it sounds like there are several outstanding questions that a design (or at least finalized user needs) could answer relating to this ticket:

Can admin sets be deleted if they have content? Or only if empty?
If it must be empty, we also need a way to bulk move works to a different (or several different) admin set(s).
If it can be deleted while content exists in it, what happens to the existing content?  Does it get auto-moved elsewhere? Is it also deleted? (yikes) Or, are you presented with options for what to do with the content?

My gut says the easiest implementation is likely to require the admin set is empty before it can be deleted. However, that implies we need a separate ticket for bulk moving works between admin sets. We would also need a way to communicate in the UI that an admin set can only be deleted when empty (e.g. grayed out delete button with mouse over text or some better design).
So, in summary here, I don't know we need a full design, but I think we need some decisions on when an admin set is deletable, etc.

@tdonohue @jcoyne @ggeisler @hannahfrost Let's talk through this in our stand-up today.

@tdonohue:

My gut says the easiest implementation is likely to require the admin set is empty before it can be deleted. However, that implies we need a separate ticket for bulk moving works between admin sets. We would also need a way to communicate in the UI that an admin set can only be deleted when empty (e.g. grayed out delete button with mouse over text or some better design).

I agree with this. This ticket will be easier (and have a better UX) if we can assume https://github.com/projecthydra-labs/hyku/issues/347 supports moving Works between admin sets.

Claiming. As discussed in standup today, I'll begin this implementation in Sufia.  Will implement as described above (only delete admin sets if empty. If non-empty, display a disabled delete button with messaging).

A brief update: After running into issues with the Sufia implementation (see https://github.com/projecthydra/sufia/issues/3041), and based on feedback from @jcoyne, I've decided to split this work into two (related) PRs:

A basic implementation for Sufia, which is simply a delete button (with no validation that the AdminSet is empty). For Sufia, that will mean that deleting a non-empty AdminSet will simply detach all works from that AdminSet (this behavior is inherited from CC). The basic implementation is in https://github.com/projecthydra/sufia/issues/3041
A full implementation for Hyrax, which changes the current behavior of CC/Sufia to first validate that an AdminSet is empty before allowing deletion to occur. This will be in a forthcoming Hyrax PR (based on the Sufia one).


[SecretsManagement] Get-Secret should return plain text by default.

Summary of the new feature/enhancement
Currently, Get-Secret returns System.Security.SecureString by default, but now System.Security.SecureString is obsolete.

DE0001: SecureString shouldn't be used

Proposed technical implementation details (optional)
Get-Secret returns plain text by default, and add -AsSecureString parameter instead of -AsPlainText parameter.
-AsSecureString parameter is for backward compatiblity.

@stknohg This one is tricky. While SecureString is indeed deprecated, it's still integrally used by Powershell especially with the [PSCredential] object. It does also help prevent exposing secrets to the console or logs in a way, so while it's not the ideal solution, I don't think plaintext default is a better solution due to the exposure risk mentioned.

I disagree. The entire premise of DE0001 is flawed:

The general approach of dealing with credentials is to avoid them and instead rely on other means to authenticate, such as certificates or Windows authentication.

Sure. You should totally avoid credentials and api tokens and secrets. Except in the real world, where they are required for roughly ... everything.
Even if the only purpose of a SecureString is that it doesn't spill the secret into the console, it's preferable to a simple string as the default output.

"I disagree. The entire premise of DE0001 is flawed"
I think the premise of DE0001 is to not assume SecureString will protect/encrypt your credentials in memory especially on .NET core implementations. It's no longer guaranteed to do that, so using securestring is a false/misunderstood sense of security. "But the string was secure! How come someone was able to just mimikatz it out?"
However 100% that the casual obfuscation it provides is worth continuing to use, and DE0001 is kind of crappy to say "don't use it" without offering a better implementation because as you say, real world tokens need to be used and at least temporarily stored somewhere.

I undarstand that the real world needs SecureString, and I really undarstand that "DE0001 is flawed" reading this ISSUE.
I withdraw "using plain text by default".
But I still think it is better not to use SecureString directly.
To prevent spill the secret into the console, we can use custom class containing supported secret types(byte[], string, PSCredential, Hashtable) and SecureString.

A custom class makes more sense, its ToString() could indicate what kind of secret it is without divulging the secret itself to the console.

I am closing this as 'by design'.  We are aware that SecureString has limitations, and isn't implemented with crypto on Linux platforms, but decided to include it anyway since it at least prevents the secret from being displayed as plain text.  We view Get-Secret not returning a string as plain text by default a security in depth mitigation, and will continue with this approach.


ci: Improve distribution via GitHub Releases

Distribute *.tar.gz file for Windows. The current Windows 10 has bsdtar by default, so this makes it easy to install cross-platform.
host=$(rustc -Vv | grep host | sed 's/host: //')
curl -LsSf https://github.com/taiki-e/cargo-hack/releases/latest/download/cargo-hack-"$host".tar.gz | tar xzf - -C ~/.cargo/bin

Distribute x86_64-unknown-linux-musl binary.

bors r+


CICD pushes new docker images packages on new tags

On tags, create a new docker image release through CICD.
0ver or Semver?

Closing. This has been completed.


Recover from emitter errors

PyNotify raises an error when showing a message if no service is available.  Instead of dying when an emitter raises, that emitter is removed.  If the last emitter is removed an exception is raised (because there would be no way to monitor test results).
This solution might be worse than checking that a libnotify service exists and using a NullEmitter if not.  A quick google didn't turn up any documentation for pynotify so I didn't look into this.
A third possibility for my use-case is adding a --no-libnotify argument.

Hey @mrgriffin, I'm going to try and reexplain what you said to make sure I understand it correctly: Pyinotify raises an exception when the OS doesn't support inotify. So it would be better if sniffer would still fallback to the naive file system watching method it uses when no file system libraries are installed.
Also, I don't think it's safe to remove an item from a list while iterating over it. But other than that, I don't have any other problems about the PR.

Hey @mrgriffin, I'm going to try and reexplain what you said to make sure I understand it correctly: Pyinotify raises an exception when the OS doesn't support inotify. So it would be better if sniffer would still fallback to the naive file system watching method it uses when no file system libraries are installed.
Also, I don't think it's safe to remove an item from a list while iterating over it. But other than that, I don't have any other problems about the PR.

Hi, it's not pyinotify that's the problem but pynotify.  I'd hazard a guess that my OS comes with pynotify, but my xmonad config doesn't start a daemon to handle notifications and so I get the following behavior:
>>> import pynotify
>>> pynotify.init('Test')
True
>>> pynotify.Notification('Test', 'test')
Traceback (most recent call last):
  File "<stdin>", line 1 in <module>
glib.GError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files

You're probably right about mutating the list, I'll fix that!

Hi, it's not pyinotify that's the problem but pynotify.  I'd hazard a guess that my OS comes with pynotify, but my xmonad config doesn't start a daemon to handle notifications and so I get the following behavior:
>>> import pynotify
>>> pynotify.init('Test')
True
>>> pynotify.Notification('Test', 'test')
Traceback (most recent call last):
  File "<stdin>", line 1 in <module>
glib.GError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files

You're probably right about mutating the list, I'll fix that!

Thanks @mrgriffin


feat(karma): add acls setting and hostAliases

add acls setting in configmap
add hostAliases for pod

@maxime1907 are you able to check this ?

Thanks for the contribution!


chore!: rename the "detail" field in DRF exceptions to "message"

Description
On error (HTTP 4XX or 5XX), our API's JSON reponses are inconsistent. This is in large part because our own code returns {"message": ...} but DRF returns {"detail": ...}.
This adds a custom exception handler so DRF error reponses match our own style.
The alternative (renaming message to detail in our code) was a lot more work, but it might be a bit preferable: this PR adds code and a new layer rather than correct things, and maybe detail really is better. I don't think these pros outweigh having to perform and test the change, but I'm open to being wrong.
How has this been tested?
Tried it out on my personal machine
Checklist

[x] changelog was updated with notable changes
[x] documentation was updated

/e2e --tests sdk,frontend

End to end tests: :hourglass_flowing_sand: STARTING

detail is a field defined in RFC 9457. It is also widely adopted by different frameworks. What is the added value to use message over detail?

@guilhem-barthes

detail is a field defined in RFC 9457. It is also widely adopted by different web frameworks. What is the added value to use message over detail?

As mentioned in the PR description, it's just easier in our codebase to standardize on message over detail. I don't know how that weights compared to industry standardization.

I think there is value in following industry standards. Do you have any estimate of how much work that would represent?

See https://github.com/Substra/substra-backend/pull/705 for replacement to this PR


Add Readme in Api Server example

🚀 The feature

add readme for api-server.

add setup instructions
explain each endpoint
Curl call for each endpoint so that anyone can quickly try it out
How to set OpenAI key in environment variables

Motivation, pitch
Improve the example so that anyone can easily try it out.
Alternatives
No response
Additional context
No response

hello @taranjeet
I want to work on this one. Please assign me this issue.


fix: issues with schematics api calls and tar creation

Description
Fixes for several issues relating to recently added IBM Cloud Schematics test framework.

Fix TAR file creation, do not use os.Chdir() which is not thread-safe
Add retry mechanic to all Schematics SDK calls
Logging of Schematic Workspace name in errors and test fail assertions

Types of changes in this PR
Bug fixes and minor enhancements
No release required

[x] Examples or tests (addition or updates of examples or tests)
[ ] Documentation update
[ ] CI-related update (pipeline, etc.)
[ ] Other changes that don't affect Terraform code

Release required

[x] Bug fix (patch release (x.x.X): Change that fixes an issue and is compatible with earlier versions)
[ ] New feature (minor release (x.X.x): Change that adds functionality and is compatible with earlier versions)
[ ] Breaking change (major release (X.x.x): Change that is likely incompatible with previous versions)

Release notes content
Fixes for several issues relating to recently added IBM Cloud Schematics test framework.

Fix TAR file creation, do not use os.Chdir() which is not thread-safe
Add retry mechanic to all Schematics SDK calls
Logging of Schematic Workspace name in errors and test fail assertions

Checklist for reviewers

[ ] The PR references a GitHub issue.
[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

Merge actions for mergers

Merge by using "Squash and merge".

Use a relevant conventional commit message that is based on the PR contents and any release notes provided by the PR author.
The commit message determines whether a new version of the module is needed, and if so, which semver increment to use (major, minor, or patch).

:tada: This PR is included in version 1.5.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


fix: improve unnest_generic_list handling of null list

Which issue does this PR close?

Closes #9932.
Rationale for this change
In a GenericListArray, the data in the values corresponding to a null list may not be empty; it can be any data.
pub struct GenericListArray<OffsetSize: OffsetSizeTrait> {
    data_type: DataType,
    nulls: Option<NullBuffer>,
    values: ArrayRef,
    value_offsets: OffsetBuffer<OffsetSize>,
}

For example, in the description of this document, the value of the null list is ?, it's not empty.
In this situation, merely checking the values is unsafe, we must obtain valid values based on the value_offsets.
What changes are included in this PR?

Fix bug in unnest_generic_list.

Are these changes tested?
Yes
Are there any user-facing changes?
No

Nice fix! Thanks @jonahgao and @Jefffrey


Update documentation for page-level params

This fixes inconsistencies in the toc page-level param and adds documentation for all page-level params I found.
I'm adding this because I didn't realise you could disable the table of contents or disqus comments on a page level until I searched the code.

Looks helpful!
Thanks for your PR!

Thanks for merging and your work on this theme.  :)


[Suggestion] Avoid printing IP address or provide control flag

The IP address can be sensitive at times, if possible please provide a flag or dont print IP address.
Another suggestion would be to have flags to skip/include specific information.

Done, I added --ignore argument, as well as improved --colour and --artcolour parsing.
Update to 1.1.3 to experience this new update, thank you for your lovely suggestion 🥰


[ci] Set the account dynamically in the configuration file for unit tests

Adding an option to ./test_reframe.py for setting the account is not so straightforward as for the standard cli. It would require either to do hacks or to modify all the unit tests that use a temporary runtime. For this reason, I believe the solution proposed here is the best.
Fixes #1406.

Let me know if you want me to follow this approach also on the basic configuration file.

@jenkins-cscs retry all


added ability to upgrade package installations

Signed-off-by: Corey Hemminger<EMAIL_ADDRESS>Description
Adds the ability to install latest package version by not specifying package_version property or version property. Maintains backwards compatibility by still defaulting to old functionality if version is specified it'll calculate debain family package version properly and ensure system has that version installed or revert system back if newer package is found.
Check List

[ ] All tests pass. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD
[x ] New functionality includes testing.
[x ] New functionality has been documented in the README if applicable
[x ] All commits have been signed for the Developer Certificate of Origin. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/CONTRIBUTING.MD

@tas50 this is the update I mentioned in the sous-chefs meeting this morning. simple update that retains backwards functionality for those that have specified version or package_version properties. Biggest difference is now it allows latest package install if no version(or package_version) is specified and thus also allows patching process to update package install if new version is available.
if version or package_version are defined it retains old behavior to install that version even if newer ones are available and if a package is updated by outside source chef auto re-installs specified version on next client run.
Failing tests are for other issues not touched by this PR.


compile error (unstructured.go:64:38: cannot use doc (variable of type *"github.com/google/gnostic/openapiv2".Document) as *"github.com/google/gnostic-models/openapiv2".Document value in argument to proto.NewOpenAPIData)

Sorry to revive this. I am using client-go with the e2e-framework (to write tests). When I compile my code, I am stuck on this error:
# k8s.io/client-go/applyconfigurations/meta/v1
/go/pkg/mod/k8s.io/client-go@v0.27.4/applyconfigurations/meta/v1/unstructured.go:64:38: cannot use doc (variable of type *"github.com/google/gnostic/openapiv2".Document) as *"github.com/google/gnostic-models/openapiv2".Document value in argument to proto.NewOpenAPIData

And after Googling, I found a ticket that references this as a workaround:
https://github.com/kubernetes/client-go/issues/1075#issuecomment-1632677511
But what exactly is one supposed to do to make it run? I did try updating my dependencies to the latest client-go (even though that's not what I want), but that did not help either.

Hi, I used client-go 0.28.3 with
openapi v0.0.0-20230717233707-2695361300d9
and it fix this problem
but then i have other problem that the swagger which is generated is corrupted
(different issue, and not sure it affects you as well)
For visibility, fields are removed and ref is added instead
      "parameters": [
       {
-       "uniqueItems": true,
-       "type": "string",
-       "description": "The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.",
-       "name": "continue",
-       "in": "query"
+       "$ref": "#/parameters/continue-tuthsW5V"
       },

I also have an issue like this
# k8s.io/client-go/applyconfigurations/meta/v1
vendor/k8s.io/client-go/applyconfigurations/meta/v1/unstructured.go:64:38: cannot use doc (variable of type *"github.com/google/gnostic-models/openapiv2".Document) as *"github.com/google/gnostic/openapiv2".Document value in argument to proto.NewOpenAPIData
make: *** [build-bin] Error 1

go.mod
	k8s.io/api v0.28.3
	k8s.io/apimachinery v0.28.3
	k8s.io/client-go v0.28.3
	k8s.io/component-base v0.28.3
	k8s.io/kube-openapi v0.0.0-20230717233707-2695361300d9 // indirect

Is there any workarounds?

reverted to k8s.io/kube-openapi v0.0.0-20230501164219-8b0f38b5fd1f // indirect works in my env

reverted to k8s.io/kube-openapi v0.0.0-20230501164219-8b0f38b5fd1f // indirect works in my env

I am facing the same issue client-go v1.28.1, can anyone help me out ?

Using helm.sh/helm/v3 v3.13.0 and k8s.io/kubectl v0.28.3 should fix this issue.
go.mod

	helm.sh/helm/v3 v3.13.0
	k8s.io/api v0.28.3
	k8s.io/apiextensions-apiserver v0.28.3
	k8s.io/apimachinery v0.28.3
	k8s.io/cli-runtime v0.28.3
	k8s.io/client-go v0.28.3
	sigs.k8s.io/controller-runtime v0.16.5

	k8s.io/kubectl v0.28.3 // indirect

Upgrading old and new packages can also solve:
# go get github.com/google/gnostic && go get github.com/google/gnostic-models
go: upgraded github.com/google/gnostic v0.6.9 => v0.7.0
go: upgraded github.com/google/gnostic-models v0.6.8 => v0.6.9-0.20230804172637-c7be7c783f49


do not start lighttpd when nginx is installed

the nginx plugin takes over and handles those requests so the port can be reused for other things like a reverse proxy or serving local files.

@fabianfrz I think we should make this more generic, someone else might prefer apache which in this case requires our core package to be changed again for just disabling it. Cluttering dependencies is usually not a good idea.

If I'm not mistaken, you should be able to add a similar construction like this https://github.com/opnsense/core/blob/18.1.9/src/etc/inc/plugins.inc.d/webgui.inc#L31-L38 for Nginx, which only leaves the minor problem of disabling the core webserver.

@AdSchellevis the problem is that nginx is started via RC and because lighttpd is started early, I would have to kill the process already running which means I would have to manipulate the RC file. I also do use the files generated here (certificate, dh parameters etc. so the user does not see any difference).

I understand, but still don't think we should clutter these things together, so maybe we need to split some functionality first to offer a swap-in replacement, adding all kinds of hooks specific for software not installed is something we should try to avoid.
At the moment I don't have a lot of time available, so I can't help out with a better solution now, maybe after 18.7 comes out.


"pipenv install --user"

Hello
Can we imagine a "--user" option for "pipenv install", that would allow a content of a Pipfile/Lock to be installed into the ~/.local directory of the user? Pip provides this option, and is used by pipenv to update itself.
I should not be the "normal" way of using pipenv, but since there is a "--system" that install on the system (requiring sudo permission), a similar "--user" can be useful.
I am looking for this option especially for embedded the application inside a docker image, most of a time it is fine to recreate a virtualenv inside the docker (it is still better than using "--system" even from inside a docker), but sometimes we want the application directly callable by the docker user.
thanks

i think this would complicate things.

For the moment, I replace this behavior with the following snippet in my Docker file:
RUN pipenv install --dev \
    &&  pipenv run pipenv_to_requirements \
    &&  pip install --user requirements.txt

@gsemet But why? I thought one of the main virtue of using Docker is you get a whole clean system for yourself, and don’t need to worry about system/user distinction in the first place, is it not?

My use case is when replacing requirements.txt for jupyter notebook docker. I need to install python package to current user only (because of npm dependencies).
But I think it is a legit need, even inside a docker image, changing the system python package can lead to unwanted issues

Wouldn’t a virtualenv be better, thinking along that line? It’s even more isolated than --user.

sure, that's why i said "I should not be the "normal" way". But for jupyter we typically install several kernels (anaconda's environment or virtualenv) in the image so user choose which one.
The option --user is available for pip, and is heavily used by pipenv itself. It is legit to understand similar situation might occur to programs packaged by pipenv themselve.


cfitsio400 with patches

This PR is a copy of #16 with backported patches from upstream to fix the build.

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

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

Seems like the tests passed so I'll go ahead and merge this, thanks.  I think we can remove these patches next time we release a new psrchive version here, correct?  It's probably time for that soon..


disabling default control event

Hi, I'm trying to disable all the event on the map.
The one thing I found is removing all the interactions. but map is still moving by control actions.
is there a way to disable event on default controls?
without hiding control buttons

You can also instantiate the map without controls or only with the controls you need:
var map = new ol.Map({controls: []});
// or
var map = new ol.Map({controls: ol.control.defaults({zoom: false, rotate: false})});

See: http://openlayers.org/en/latest/apidoc/ol.control.html#defaults and http://openlayers.org/en/latest/apidoc/ol.Map.html

Yes, but with the control icons, I couldn't disable the events.

can you explain why you want the visuals, but not the event handling? What is your use case?

I'm making a function that can disable all the events. but if there's controls then I still can able to use the event by the controls then it doesn't mean disable all the events. however, if I remove the controls when the function's called, it's like having two functionalities(disable events, hiding controls).

I am not sure I understand, but regarding the UX it might be confusing for your users if they see the zoom controls and can click them, but nothing happens.

I agree with you. I feel that is right. but I think interactions and controls working should be synchronized. because to disable zoom functionality, we should remove the control and disable the interactions.


Osiris Wrong title, Set missing space and Horus description

Describe the bug
A clear and concise description of what the bug is.
Osiris's has the wrong titles, it should be Lord of the Living.
In Set's description after Set Vying the words to steal are missing a space and are instead "tosteal", look at the last line at the bottom of the picture to see what it mean.
Screenshots
If applicable, add screenshots to help explain your problem.

In Horus's description, after "An ally of Osiris and Isis" there is a space before the comma. Also the word churches in the last line has a space between churche and the s written as "churche s".

Thanks for the report, I'll have these fixed for the next update.

Fixed most of these, left the hyphens as they look fine to me as instead of using   ,   they refer to the previous section.
Will be in next update.

Here some more bugs for gods. Some spelling mistakes and the wrong favoured weapon for some gods.
Lady Nanbyo gives the wrong favoured weapon, giving a quarterstaff instead of a Warhammer.

Nalinivati gives the wrong favoured weapon, giving a quarterstaff instead of a Sai.

Tsukiyo has a missing space.

Yamatsumi has make missing the m.

Nalinivati gives the wrong favoured weapon, giving a quarterstaff instead of a Rapier.

Varg has Greataxe misspelled as Greataxw.

Verex has Battleaxe misspelled as Battleaxw.

All fixed


non-string types changed to string automatically by editor

Describe the Bug with repro steps
This is not limited to the select action - it appears to be present whenever the logic app is saved, but I will detail how to repro using select:

create a logic app with any trigger - in my case an array of objects
add a second step: the inbuilt data operation "select"
make the "from" field of the select action any array
add one row to the select. Call it anything. Add an expression to the value bool(false)
save the workflow and inspect the workflow.json. You'll notice the expression is saved (e.g.) "isAvailable": "@{bool(false)}", which is a string
edit the workflow.json to be "isAvailable": "@bool(false)", (remove the curly braces)
reload the designer window in vs Code
add another row to the select statement - anything
save the workflow and inspect the workflow.json again - you'll notice the expression is changed back to the version with braces

If the select action is not edited, the logic app works and can be deployed/run with the boolean value, however if the select action is edited, the boolean value is changed to string interpolation (curly braces).
The outcome of this is that the object becomes:
[
   {
      "isAvailable": "False"
   }
]

instead of
[
   {
      "isAvailable": false
   }
]

What type of Logic App Is this happening in?
Standard (VSCode)
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
No response
Screenshots or Videos
No response
Browser
VS Code (haven't tried in portal)
Additional context
No response

@thinkOfaNumber - Can you please share what all actions and editors you have noticed this?

I recall the select action, possibly in others such as compose, but this was some time ago so I’d have to go back and just try more to be sure.
I mainly used VS Code as the editor, again would have to try the online editor as I don’t remember!


Release notes should be in code repository

Currently we use GitHub's releases when writing release notes. They work fine with smallish releases, but with big releases like RF 2.9 what have long release notes there are problems:

Not possible to create table of contents. GitHub's Markdown doesn't support that automatically in general, but it isn't possible to create them manually either because headings don't create anchors.
No versioning.
Can only edit in a text area on a browser.
Notes are in GitHub itself making possible transition to other services harder.
We generally prefer reStructuredText over Markdown.

We can avoid all these problems by putting release notes under doc/releasenotes directory in reST format. We can then have shorter notes in GitHub's releases with a link to the actual release notes.
Tasks related to this:

[x] Create a script to generate release notes templates based on the issues in the tracker and place it under doc/releasenotes. It can be based on the current Invoke tasks in tasks.py, but needs to be converted to use reST instead of Markdown. Having it as a standalone script makes tasks.py shorter and easier to maintain.
[x] Update tasks.py to use the new standalone script.
[x] As a test, convert RF 2.9 release notes into the new format.

We decided that tasks.py does not really need to call the generation script. It is enough to call that script directly.


issue

Hey man, i really enjoyed your project and would like to maybe sponser it or buy a service from you.
Add me on discord: lostsomewhere. we can talk in there since github has not dm option

Sure.


Fixes/usage instructions

Hey @etagwerker, @schmierkov,
This PR fixes #1. I added some basic usage instructions, should be enough to get someone new started.
Please check it out, thanks!

@mauro-oto Looks good! Just added those two comments.

@etagwerker just updated the PR based on your comments. Thanks!

@mauro-oto :+1:


[improve] Allow to build and push multi-arch Docker images

Fixes #12944
Motivation
Added support to build multi-arch x86_64 & arm64 Docker images and push them to DockerHub.
The same tag will refer to the 2 different images and docker will fetch the one matching the user's machine arch.
Added Maven profile -Pdocker-push that will trigger the multi-arch build and push of the tagged image
Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

[ ] Dependencies (add or upgrade a dependency)
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The threading model
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[ ] The metrics
[ ] Anything that affects deployment

Documentation

[ ] doc
[ ] doc-required
[X] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository:

Seems we failed to build the test image in time (killed due to 1 hour timeout). I'm retriggering the workflow, but if it remains, we may find someway to speed up the execution.

It seems "Build Pulsar Docker image" becomes quite easily to timeout now.

/pulsarbot rerun-failure-checks

/pulsarbot run-failure-checks

"Build Pulsar Docker image" becomes a more time-consuming task. The step "Build latest-version-image docker image" takes 54 min. How about we increase the timeout minutes for this job:
https://github.com/apache/pulsar/blob/dc1cdacab8eadbd3f9d207e66d4aefbca8bca920/.github/workflows/pulsar-ci.yaml#L739

I believe it's a concern that the CI build time is greatly increased by this PR.

It shouldn't be different per-se. By default it's still building the native architecture for the Docker image. Only when we pass the "release" flag is creating the multi-arch.

It can be delayed. It's essentially to make the Docker image much more friendlier on Mac M1, though it's definitely not a blocker.

OK. Then I'll put it for 3.1 milestone as it will also change the release process and we need some time to do it correctly.

Is there a timeline for this
Will this be done in a release before 3.1 release or is that to specifically address the increased build time due to these changes?

Codecov Report

Merging #19432 (99b2ebc) into master (9b72302) will increase coverage by 39.76%.
The diff coverage is 82.94%.

@@              Coverage Diff              @@
##             master   #19432       +/-   ##
=============================================
+ Coverage     33.17%   72.94%   +39.76%
- Complexity    12236    31930    +19694
=============================================
  Files          1499     1868      +369
  Lines        114413   138449    +24036
  Branches      12431    15235     +2804
=============================================
+ Hits          37962   100987    +63025
+ Misses        71499    29414    -42085
- Partials       4952     8048     +3096

Flag
Coverage Δ

inttests
24.21% <17.82%> (?)

systests
24.85% <15.50%> (?)

unittests
72.22% <82.94%> (+39.04%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...e/pulsar/broker/authentication/oidc/JwksCache.java
56.62% <0.00%> (ø)

...thentication/oidc/OpenIDProviderMetadataCache.java
78.48% <0.00%> (ø)

...nt/internal/PulsarClientImplementationBinding.java
62.50% <ø> (+12.50%)
:arrow_up:

...ava/org/apache/pulsar/client/api/MessageIdAdv.java
84.21% <ø> (ø)

...unctions/runtime/kubernetes/KubernetesRuntime.java
38.34% <0.00%> (+38.34%)
:arrow_up:

...nt/impl/PulsarClientImplementationBindingImpl.java
80.00% <28.57%> (+24.82%)
:arrow_up:

...broker/intercept/ManagedLedgerInterceptorImpl.java
75.00% <75.00%> (+75.00%)
:arrow_up:

.../pulsar/broker/delayed/bucket/ImmutableBucket.java
85.71% <76.19%> (+85.71%)
:arrow_up:

...ulsar/client/impl/transaction/TransactionImpl.java
87.20% <80.95%> (+48.00%)
:arrow_up:

...elayed/bucket/BookkeeperBucketSnapshotStorage.java
85.71% <100.00%> (+85.71%)
:arrow_up:

... and 11 more

... and 1519 files with indirect coverage changes

I see this was merged, will arm64 images be generated now going forward for 3.0+.
I can see images in dockerhub, but didn't see this issue referenced in the release notes?.

@GerMoranOverstock Hi, this feature is supported in 3.0.0.
This PR was not marked with the 3.0.0 milestone, so the release note mistakenly omitted it.
I will fix the release note later. Thanks for your report.


error TS2786

Describe the bug
Run Start.cmd. It runs though until comes to building front end  then i get 17 ts2786 errors
eg
src/components/Answer/Answer.tsx:318:22 - error TS2786: 'DefaultButton' cannot be used as a JSX component.
Its instance type 'DefaultButton' is not a valid JSX element.
To Reproduce
Steps to reproduce the behavior: using VScode. In the integrated terminal ./start.cmd
Expected behavior
I expected it to finish.
Configuration: Please provide the following

Azure OpenAI model name and version -- gpt-4)
Is chat history enabled? yes
Are you using data? If so, what data source?Azure AI Search,
Additional context
All works from azure , just trying to run locally.

I was able to work around this by adding the following code under compilerOptions in tsconfig.json
"paths": {
"react": [ "./node_modules/@types/react" ]
}

@michbalazs Are you still having this issue? I'm not able to reproduce.


[ Services ] Invalid Color

you can see the actual color from the psd file.
I suggest opening it with https://www.photopea.com and follow this


role assignment module

!iam
!iamnot
!accept - for accepting rules and getting default role assigned

to do: !accept


Comment requirements.txt for easy start

Add instructions to requirements to txt to make it easier to install virtual env

Fixed in pr 16


Update DKIM Glossary Entry with Custom DKIM info

Users are always provided with custom DKIM Keys, but when automated security is OFF, they are responsible for updating their DKIM Keys whenever they make a change to their sending domain/IP address

Hello @eschallock,Thank you for the PR! We will be reviewing this PR soon, in the mean                                              time, please be sure to                                                                                sign our CLA so that we can merge your changes. Thanks again!                                             Team DX


Support projecting downward, and projecting to Wayfinders located literally anywhere

Eventually, the constraint that the wayfinder must be located in a parent or ancestor of a waypoint will be removed. This is possible without any breaking changes or changes to the interface.
This feature is very low-pri right now.

support fixed elements (see other issue)
implement downward projection
implement more sophisticated path-finding from the waypoint to the wayfinder

Will write a new library to support this feature, and may eventually use it in Wayfinder


Portainer integration won't install

Problem/Motivation

Portainer won't install when "Install" is clicked in HA addon store.

Expected behavior

Expect to see "Installing..." and an activity swirly thing, then: Installed.... Start integration.... options

Actual behavior

Literally nothing happens - like the Install link/button is dead.

Steps to reproduce

Try to install portainer integration from the HA addon store.
currently running version HA core-2021.3.0 and HASSOS 5.12. Tried a HA restart.

Proposed changes

would be great if it could install when I click install.

Cannot reproduce. This seems to be something with your system.
Besides, this is an add-on. Installing/managing the add-on is not provided by the add-on itself (as well, it isn't installed even in your case). So there is no amount of code I can adjust to fix that.
Please report your issue with the Home Assistant project. Thanks 👍

@frenck thank you.
For others who might stumble on this, my issue was caused by lack of free drive space. Although the host monitoring stated 2Gb free, and there were no relevant items in the HA log, the HA supervisor log stated errors when updating or attempting to install Portainer due to only 0.7Gb remaining.


Event Hub Private Endpoint Connection - cannot create

I believe the v2018-01-01-preview API is mistaken in defining this request as a create request. Attempting to create a private endpoint connection via this request fails with the following:
{
    "error": {
        "message": "The requested resource PRIVATE_ENDPOINT_CONNECTION_NAME does not exist. CorrelationId: 4d820ac2-2645-4897-957c-314b5a1501ee",
        "code": "NotFound"
    }
}

This happens when sending a request to the following endpoint with the following body:
Endpoint - https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventHub/namespaces/{namespaceName}/privateEndpointConnections/{privateEndpointConnectionName}?api-version=2018-01-01-preview
Body:
{
  "properties": {
    "privateEndpoint": {
      "id": "resourceId"
    },
    "privateLinkServiceConnectionState": {
      "status": "Approved",
      "description": "testing"
    },
    "provisioningState": "Succeeded"
  }
}

Is there any update on this? Trying to update an endpoint using the REST API also fails with the following:
{     "error": {         "code": "NoRegisteredProviderFound",         "message": "No registered resource provider found for location 'uksouth' and API version '2018-01-01-preview'' for type 'namespaces/privateEndpointConnections'. The supported api-versions are '2018-01-01-preview'. The supported locations are ''."     } }

@cesarme @arundsouza @sjkwak would you be able to take a look at the issue?

Is there any news on this? It's been awhile since the initial report and this is quite a blocker for us.

This issue is still open, and ongoing. Suggested work around is to simply not create the private link in ARM/Bicep. The underlying cause appears to be the ServiceBus Private Endpoint not respecting the name field, and instead creating the requested resource with a GUID as the name. This prevents the deployment from completing, despite the resource being created as expected.
Failure reproduces in ARM, and Bicep, and all API versions:

2018-01-01-preview
2021-11-01
2022-01-01-preview
2021-06-01-preview


[Model Update]: CX-0040 PartsAnalyses to V2.0.0

Update Reason
During mapping of test data the use case QAX team figured out that some attributes/properties were missing.
Therefore we would like to add the missing attributes. In addition there were 2 attributes that were named inconsistently and we would like to migrate to SAMM 2.0. --> Both will lead to a new major version 2.0.0 of the model
MS1 Criteria

[x] The model that should be updated exists
[x] The referenced use case exists
[x] The potential updates are discussed with all stakeholders: Discussed with QAX members
[x] The potential update will be either

[ ] backward compatible or
[x] a (chain of) migration strategy(-ies) from all non-deprecated previous versions to the new model will be developed

https://github.com/eclipse-tractusx/sldt-semantic-models/tree/main/io.catenax.parts_analyses/1.0.0


False cyclic term detection

For following code, Trealla will report a false cyclic term detection:
last_element([], Out) :- Out = nil.
last_element([Arg|Rest], Out) :- write(Arg), last_element(Rest, Out).

foo(A, B, Out) :- last_element([A|B], Out).
bar(A, B) :- foo(A, [B], Out).

main :- bar(a, b), halt.

Trealla output:
Trealla v0.1alpha, 64-bits (int=128-bits), Dec  2 2016
aWARN: ERROR ABORT_MAXDEPTH - CYCLIC TERM

There is no problem in GProlog and SWI an Yap.

Simply test case further:
foo([A]) :- write(A), halt.
bar(A, B) :- foo(B).
baz(A, B) :- bar(A, [B]).

main :- baz(a, b).

After enable DEBUG in jela.c, I found following unification is not correct, bar(a,[b]) <==> bar(a,b) should be bar(a,[b]) <==> bar(A,B):
---
### match : baz(a,b) <==> baz(A,B)
### unify_term baz(a,b) : baz(A,B)
### unify_term a : A
### unify_term b : B
###[ try_me ] ==> size=0, choice_point=2, curr_choice=1, env_point=0
###[ execute_term ] ==> size=0, choice_point=3, curr_choice=2, env_point=0
###[ follow ] ==> size=2, choice_point=3, curr_choice=2, env_point=2
###[ allocate_frame ] ==> size=2, choice_point=3, curr_choice=2, env_point=2
### prepare_frame size=2, curr_choice=2, env_point=2
### match : bar(a,[b]) <==> bar(a,b)
### unify_term bar(a,[b]) : bar(a,b)
### unify_term a : A
### unify_term [B] : B
...

Simplify even more:
bar(A) :- write(A), halt.
foo(A) :- bar([A]).

main :- foo(a).

Yep, I am onto it, but have limited time at the moment.
On 3 Dec 2016 5:32 pm, "Xin Wang"<EMAIL_ADDRESS>wrote:

After enable DEBUG in jela.c, I found following unification is not
correct, bar(a,[b]) <==> bar(a,b) should be bar(a,[b]) <==> bar(A,B):

match : baz(a,b) <==> baz(A,B)
unify_term baz(a,b) : baz(A,B)
unify_term a : A
unify_term b : B
###[ try_me ] ==> size=0, choice_point=2, curr_choice=1, env_point=0
###[ execute_term ] ==> size=0, choice_point=3, curr_choice=2, env_point=0
###[ follow ] ==> size=2, choice_point=3, curr_choice=2, env_point=2
###[ allocate_frame ] ==> size=2, choice_point=3, curr_choice=2, env_point=2
prepare_frame size=2, curr_choice=2, env_point=2
match : bar(a,[b]) <==> bar(a,b)
unify_term bar(a,[b]) : bar(a,b)
unify_term a : A
unify_term [B] : B
...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/trealla-lang/trealla/issues/27#issuecomment-264623445,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVqpEqU_YmUSejeOZO3UUtMbc-lZDIkdks5rERr2gaJpZM4LCUBM
.

No hurry, take your time.

Change the last line to this:
main :- B=1, foo(a).
and it works, For some reason main was getting a frame-size of 0 allocated, when it should be 1. This works for the earlier examples you posted as well.
Now to find out why...

Actually I think now that explanation was bogus! But it's something related to that.

Also,
main :- X=a, foo(X).
works as well.

I was close, it seems creating a choice-point with zero frame-size is the cause.  Now I have something to work with...

Wow, Excellent!
Thanks!
BTW, I find that following line in jela debug info is not quite right, [A] <==> A should be [a] <==> A?
...
### match : bar([a]) <==> bar(A)
### unify_term : bar([a]) <==> bar(A)
### unify_compound : bar([a]) <==> bar(A)
### unify_term : [A] <==> A
...

You're right, it still prints the debug info incorrectly. But the result is right.


Can you please bump the angular dependency version to 1.3.13 or newer

Hey @santbob, what reason is there for that ?

@mrzmyr I m using grunt for workflow and user bower install simple module to install the depdencies and it stops with conflict coz my angular dependency is latest, whereas angular-facebook uses 1.2


Epochs.plot load epochs on the fly

In raw.plot, raw data are loaded on demand when preload=False, is it possible to do the same when for epochs when preload=False too instead of loading them all.

good idea
how come you have so big epochs?

It should be possible. @jaeilepp?

I'll look into it.


Version 0.9.1

Signed-off-by: Rehan S. Durrani<EMAIL_ADDRESS>
What do these changes do?

[ ] commit message follows format outlined here
[ ] passes flake8 modin
[ ] passes black --check modin
[ ] signed commit with git commit -s
[ ] Resolves #?
[ ] tests added and passing

Let's merge #2870 first.

I agree @YarShev


Refactor: Merge code for inlining into a template visitor class

Currently there are three AST conversions to do inlining:
Statement inlineAsStatement(Statement s, InlineDoState ids);
Expression doInline(Statement s, InlineDoState ids);
Expression doInline(Expression e, InlineDoState ids);

The functions have very similar visitor classs in their own. Now, by using template
and conditional compilation, the visitor classes can be merged into one with few compile-time branches.
This is a PR to show final improvement. If someone hard to review each commits, I can break down it to separated PRs.

The end result of this merging is the same amount of code. What is the improvement?

My points:

Having only one logic name doInlineAs and encapsulating its logic into a visitor,
is much better than having inconsistent two names inlineAsStatement/doInline with three functions/visitors.
In old days, the bad naming really confused me when I tried to grasp the inline mechanism design.

Added ddoc comments are increasing the total count of line additons. Without that, the code lines are reduced.

Auto-merge toggled on

Thanks!

Probably need to pull https://github.com/D-Programming-Language/dmd/pull/5634 before anything is going to pass the autotester.


Interpreter discovery times out on first load

In our monorepo (which uses Python + Bazel), we have a setup where the very first python run in the repo can take longer to complete (there is some additional work like building generating dependencies and setting up the venv going on).  As a result, the interpreter info script fails to complete in time on this initial run.
It appears there is a hard coded 15 seconds in place for this step - we would like to make this configurable so that it waits long enough for this to complete and users don't get an error in this scenario.

Can you provide some details on the very first run of python? Is it that we select the venv the moment it gets created and then it fails? Can you provide details on the failure?

Can you provide some details on the very first run of python?

With Bazel, the first run also has to populate the Bazel cache (e.g. including downloading external dependencies and creating any generated files), then creates the venv and symlinks to the python interpreter inside the cache.  After that python can actually run.

Can you provide details on the failure?

Once the run takes longer than the 15 second timeout (the line I edited in the PR mentioned above), the process gets killed and interpreter discovery fails or may search the system for other possible interpreters and select the wrong one.  If it weren't for the timeout, it would succeed.
Given this, and the fact that this setup likely only affects a small subset of users, I suggest a configuration option that would allow this timeout to be extended if a repo's setup warrants it.

Would it be enough if this timeout was set via an environment variable?
We are working on changing the python discovery process. Making it reliable and extensible. We would like to avoid adding any settings that we may need to take out as a part of the process. The work that we are doing would allow you to contribute a custom environment manager (creator, selector, etc), so you can control that experience.

Yes, that will work too.  Do you just mean an environment variable via the extension's process.env?

Yes. process.env.

Hi @karthiknadig - I went ahead and updated #24227 to support this.  Can you take a look?

This looks solved- closing but comment if not. Thanks!