Rename test cases for beta feature validations

Changes
This commit renames the test cases for beta feature validations which previously had the tests constructed to return an error without the feature flags being set. This was no longer the case after the refactor and this commit aims to avoid the confusions.
/kind misc

Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[n/a] Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
[n/a] Has Tests included if any functionality added or changed
[n/a] Follows the commit message standard
[n/a ] Meets the Tekton contributor standards (including functionality, content, code)
[n/a] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[n/a] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
[n/a ] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
NONE

/retest
known flake: https://github.com/tektoncd/pipeline/issues/4643


while creating delta pkg .forceignore not getting copied to working directory

Create Delta Package based on two commits task is failing with below error while delta package creation
##[error]ENOENT: no such file or directory, open 'portal_src_delta/.forceignore'

@azlam-abdulsalam not able to reproduce this one, we are handling project not having forceignore. i have tested in project where forceignore not exist as well.
keeping this open to see if @ramesh-karanji facing this anymore.

@azlam-abdulsalam not able to reproduce this one, we are handling project not having forceignore. i have tested in project where forceignore not exist as well.
keeping this open to see if @ramesh-karanji facing this anymore.

Closing this as no further feedback from @ramesh-karanji . Please feel free to reopen of required

Closing this as no further feedback from @ramesh-karanji . Please feel free to reopen of required


Add qemu udp unicast tunneling support.

Fixes #17
Signed-off-by: Jeroen Simonetti<EMAIL_ADDRESS>

Feel free to squash this PR if you feel it is needed.

I appologise for use this read-only repo. I will resubmit via libvirt-list.


⚠ ClamAV has degraded performance

In 86a0a3b, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 444 ms

Resolved: ClamAV performance has improved in 2506e81.


feat: basic implementation for Dependency Track

This adds a basic implementation for sending data to Dependency Track.
When launching the operator make sure to also set --format=cyclonedx
This is how the Dependency Track project is found:

Search for project with the property "image-name" in the group "container" with the image name
If found use this project, if not found create a new project with the image name as the project name + also add the property "image-name"

See #5

Thanks to everyone who has contributed here :tada:
Now only the README docs (under the target-section) need to be enhanced with the general behaviour and specifics (e.g. cyclonedx as format). I can add this in the next few days, but if anyone has time to do a PR, this would be great :)


Update for MySQL8 (8.0.23) usage

fixed incorrect DATETIME value for mysql 8

1. Why is this change necessary?
Ups! Ein Fehler ist aufgetreten! Die nachfolgenden Hinweise sollten Ihnen weiterhelfen. An exception occurred while executing 'SELECT DATE_FORMAT(orders.ordertime, '%Y-%m'), DATE_FORMAT(orders.ordertime, '%Y-%m') as yearMonth, COUNT(DISTINCT orders.id) count_orders, MIN(orders.invoice_amount / orders.currencyFactor) as invoice_amount_min, MAX(orders.invoice_amount / orders.currencyFactor) as invoice_amount_max, MIN(orders.ordertime) as first_order_time, MAX(orders.ordertime) as last_order_time, ROUND(AVG(details.price / orders.currencyFactor), 2) as product_avg FROM s_order orders INNER JOIN s_order_details details ON details.orderID = orders.id AND details.modus = 0 INNER JOIN s_customer_streams_mapping stream ON stream.customer_id = orders.userID AND stream.stream_id = ? WHERE (orders.status != ?) AND (orders.ordernumber IS NOT NULL) AND (orders.ordertime >= ?) AND (orders.ordernumber != 0) GROUP BY DATE_FORMAT(orders.ordertime,'%Y-%m')' with params ["21", -1, "2020-03"]: SQLSTATE[HY000]: General error: 1525 Incorrect DATETIME value: '2020-03' in vendor/doctrine/dbal/lib/Doctrine/DBAL/DBALException.php on line 179 Stack trace: #0 vendor/doctrine/dbal/lib/Doctrine/DBAL/DBALException.php(150): Doctrine\DBAL\DBALException::wrapException() #1 vendor/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(915): Doctrine\DBAL\DBALException::driverExceptionDuringQuery() #2 vendor/doctrine/dbal/lib/Doctrine/DBAL/Query/QueryBuilder.php(206): Doctrine\DBAL\Connection->executeQuery() #3 engine/Shopware/Models/CustomerStream/CustomerStreamRepository.php(187): Doctrine\DBAL\Query\QueryBuilder->execute() #4 engine/Shopware/Controllers/Backend/CustomerStream.php(196): Shopware\Models\CustomerStream\CustomerStreamRepository->fetchCustomerAmount() #5 engine/Library/Enlight/Controller/Action.php(192): Shopware_Controllers_Backend_CustomerStream->loadChartAction() #6 engine/Library/Enlight/Controller/Dispatcher/Default.php(478): Enlight_Controller_Action->dispatch() #7 engine/Library/Enlight/Controller/Front.php(228): Enlight_Controller_Dispatcher_Default->dispatch() #8 engine/Shopware/Kernel.php(188): Enlight_Controller_Front->dispatch() #9 vendor/symfony/http-kernel/HttpCache/SubRequestHandler.php(102): Shopware\Kernel->handle() #10 vendor/symfony/http-kernel/HttpCache/HttpCache.php(453): Symfony\Component\HttpKernel\HttpCache\SubRequestHandler::handle() #11 engine/Shopware/Components/HttpCache/AppCache.php(261): Symfony\Component\HttpKernel\HttpCache\HttpCache->forward() #12 vendor/symfony/http-kernel/HttpCache/HttpCache.php(238): Shopware\Components\HttpCache\AppCache->forward() #13 engine/Shopware/Components/HttpCache/AppCache.php(102): Symfony\Component\HttpKernel\HttpCache\HttpCache->pass() #14 shopware.php(122): Shopware\Components\HttpCache\AppCache->handle() #15 {main}
2. What does this change do, exactly?
it transfers a correct date for MySQL8, for example 2021-03-01
3. Describe each step to reproduce the issue or behaviour.
Activate mysql8 and, for existing customer streams, simply click on one under customers -> customer streams and you will get exactly this error
4. Please link to the relevant issues (if any).
5. Which documentation changes (if any) need to be made because of this PR?
6. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-26018
Please use this issue to track the state of your pull request.

Thanks for your Contribution! 💙


Failed to change SFTP-Password

Then I changing password for SFTP-account of server. It returns this error:
There was an error while attmping to contact the remote service to change the password.
In logs of daemon I find only this:

14:58:10.416Z FATAL wings: A fatal error occured during an operation.
Error: Can't remove headers after they are sent
at ServerResponse.OutgoingMessage.removeHeader (_http_outgoing.js:390:11)
at ServerResponse.restifyWriteHead [as writeHead] (/srv/daemon/node_modules/restify/lib/response.js:426:14)
at _cb (/srv/daemon/node_modules/restify/lib/response.js:326:14)
at ServerResponse.send (/srv/daemon/node_modules/restify/lib/response.js:342:9)
at Responses.generic204 (/srv/daemon/src/helpers/responses.js:35:25)
at Auth.server.start.err (/srv/daemon/src/controllers/routes.js:154:27)
at Async.series.err (/srv/daemon/src/controllers/server.js:243:20)
at /srv/daemon/node_modules/async/dist/async.js:3853:9
at /srv/daemon/node_modules/async/dist/async.js:484:16
at replenish (/srv/daemon/node_modules/async/dist/async.js:1025:25)
14:58:10.418Z FATAL wings: A fatal error occured during an operation.
Error: Callback was already called.
at /srv/daemon/node_modules/async/dist/async.js:985:32
at /srv/daemon/node_modules/async/dist/async.js:3850:13
at apply (/srv/daemon/node_modules/async/dist/async.js:41:25)
at /srv/daemon/node_modules/async/dist/async.js:76:12
at Object.container.stats [as callback] (/srv/daemon/src/controllers/docker.js:246:29)
at /srv/daemon/node_modules/dockerode/lib/container.js:645:10
at Modem.buildPayload (/srv/daemon/node_modules/docker-modem/lib/modem.js:230:19)
at ClientRequest. (/srv/daemon/node_modules/docker-modem/lib/modem.js:215:10)
at emitOne (events.js:96:13)
at ClientRequest.emit (events.js:188:7)

Can you try rebooting the daemon and see if that fixes it?

Yeah, thanks, it didn`t work before, now it works.

Excellent! It's a known issue that should be fixed soon.


Add a MemorySettingStore

Store settings in memory only, and don't write them to anywhere permanent.
The use case for this is for Unit Tests. Can't be writing to a json file every time I run Unit Tests.

Would this be better called ArraySettingStore?
—
Sent from Mailbox
On Mon, Jun 8, 2015 at 9:54 PM, Rob<EMAIL_ADDRESS>wrote:

Store settings in memory only, and don't write them to anywhere permanent.
The use case for this is for Unit Tests. Can't be writing to a json file every time I run Unit Tests.
Reply to this email directly or view it on GitHub:
https://github.com/anlutro/laravel-settings/issues/23

Good idea.
I think "array" would be more consistent with Laravel, but "memory" is definitely the correct word to use.

Added in 0.4, no breaking changes.

Thanks so much for the fast response! This works great from my tests.


Setup oEQ clustering environment

Use docker-compose to setup the oEQ clustering environment
Update docker/Readme.md

I have login/logout issues sometimes with this docker-compose file. I will investigate after fixing the ECS issue.


Fix Download Stats By Language

Just needed to tweak it a little, since now both the stable and pre-releases will have multiple languages.
Download stats by language:

| Board            | 4.0.1  | 4.0.0-rc.3  |
| -----------------|--------|-------------|
| ID               |   7    |      0      |
| de_DE            |   28   |      4      |
| en_US            |  1914  |     533     |
| en_x_pirate      |   31   |      6      |
| es               |   47   |      5      |
| fil              |   2    |      0      |
| fr               |   55   |     10      |
| it_IT            |   7    |      2      |
| pl               |   8    |      1      |
| pt_BR            |   10   |      5      |
| zh_Latn_pinyin   |   5    |      1      |
| -----------------|--------|-------------|
|            Total |  2114  |     567     |
| -----------------|--------|-------------|

Relevant code is in lines 267 thru 297. I keep PEP8ing in increments, fully knowing that its going to muddy up the PRs. Apologies.

Thank you!


Linux packaged peruse version crashes when using --debug

Operation System and Version: Ubuntu 18
SAFE Browser Version: Peruse 0.7.0-
Network: Mock
Description: Linux packaged peruse version crashes when using --debug arg
Steps to reproduce: package it and try to use --debug mode

Unable to reproduce this issue building with master @ https://github.com/maidsafe/safe_browser/commit/f1b80cf1016d6a14b4f55b57223fab87b1100ce6.

I'm not reproducing this either on Linux Debian 9 with same commit of the browser @hunterlester .

@joshuef Are you still able to crash the browser?

@joshuef  I tried reproducing this with the same commit that @bochaco and @hunterlester did. I wasn't able to reproduce it either.

It's not crashing for me no, but we're not getting into full debug mode either... (with devtools windows showing for the browser).
I'll close this as it's not strictly the issue then. And create a new one to track what should be happening in --debug mode in a packaged browser.


fix(Docker): fixing a permissions issue with Docker container

:tada: This PR is included in version 1.4.1 :tada:
Your semantic-release bot :package::rocket:


Fix link of Bot Framework Composer docs

Overview
I found the following link is the below 404.
So, I guess the correct link is "https://github.com/microsoft/BotFramework-Composer/blob/stable/toc.md".
If my understanding is right, please confirm this.

Expiration link : https://github.com/microsoft/BotFramework-Composer/tree/kaiqb/Ignite2019
Fix : https://github.com/microsoft/BotFramework-Composer/blob/stable/toc.md

This was fixed earlier today.


Added umaryland.txt

Added umaryland.txt (University of Maryland, umaryland.edu)
Thank you JetBrains for your student licenses- they really are phenomenal!

@tanjera Thank you for your patience while waiting for a review and processing your request. Pull request merged. Please start applying for JetBrains educational subscription at https://www.jetbrains.com/shop/eform/students in an hour, to allow the changes to propagate through JetBrains systems.

Thank you so much!
On Wed, Oct 2, 2024 at 8:00 AM Philip Torchinsky @.***>
wrote:

@tanjera https://github.com/tanjera Thank you for your patience while
waiting for a review and processing your request. Pull request merged.
Please start applying for JetBrains educational subscription at
https://www.jetbrains.com/shop/eform/students in an hour, to allow the
changes to propagate through JetBrains systems.
—
Reply to this email directly, view it on GitHub
https://github.com/JetBrains/swot/pull/24054#issuecomment-2388466719,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEESWX43DNLQPQCEHT76J3ZZPN7PAVCNFSM6AAAAABPEPULWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBYGQ3DMNZRHE
.
You are receiving this because you were mentioned.Message ID:
@.***>


Revert #1650 (and #3366) due to regressions

A few months ago I started suspecting that my reasoning behind #1650 was wrong.
Time proved it, I found many other breaking changes, some of them not that exotic as the one I found originally (see the one added as a test in this commit) and also caused some headaches with the mishandling of the new internal exception which btw I still find it from time to time, so it's still mishandled.
I think it's better to assume that I was wrong and rectify, in any case the speed up of this PR was the marginal (up to 2x in some cases whereas the other 3 PRs provided exponential speed up).
But now it's clear to me that when the resolution fails in that SolveMemberConstraint function, for whatever reason we shouldn't abort in the case of unresolved overload because that will prevent in some cases to analyze further and re-run the resolution with more information which would lead to the right candidate selection.
The question remains open as to why can't we commit the trait solution before short-cutting the type equivalence if ty1 === ty2 then CompleteD else, my impression is that there's still some dark logic there which is not 100% correct, but now I'm sure this is not the answer.

Does this also fix #4063? If so can we add a test case for it?

No, unfortunately that issue seems to be unrelated to these changes.
We would need to find out at which commit it stopped working, but I suspect from https://github.com/Microsoft/visualfsharp/commit/4f89b4c872b59b0d70cef63b15e4bb91ac12cdfe in which case simply reverting it shouldn't be an option, since it will be regression of that feature.
This reversion is different, in the sense that there were no new features in that commit, only (a very marginal) speed-up.

@gusty We need to talk about this - this reversion itself caused a regression, see https://github.com/Microsoft/visualfsharp/issues/4343.

that's what I thought, but I tried to rebase https://github.com/Microsoft/visualfsharp/pull/4285 on before and after the PR. but maybe I did something wrong


Naming alignment — option field and resulting field names

It is exciting to see novel work on the exec interface being also forward-looking. I am sure at least a few have dared to explore this space so it makes sense to expect a few more proposals coming this way.
That said, can I propose reconsidering the parametric aspects further here.
I am particularly wondering that with exec(…, options) being an object it might (imho) lend nicer to change the parameter to options.captureOffsets = true.
Not sure if that is easier to optimize engine-side, but JS-side, and at least if more potential options come this way, boolean checks will likely be easier to work with (and review).
It also gives a nice parallelism between options.capture… and match.… which might lessen the cognitive burdens, especially for developers that generally try to avoid RegExp because of its mystery.
Certainly there is more to the naming which I might have missed (apologies if this is redundant).
Thanks

That does make them harder to annotate in type systems like TS and Flow; typically enums are preferred over booleans as well because then you can add a third option in the future.

I personally cannot talk about internals, but also feel a little hesitant to think it technically ill-advised.
Irrespective, I guess the more immediate concern I am getting at, for someone not with the same perspective looking at { capture: 'indices' } being what it takes to end up with { offsets: something[] } is seemingly not as straightforward — more so of { capture: 'strings' } being the default and what that means.
My fear is that capture in this context is too generic, in the sense that down the road something might be proposed that could more intuitively relate to capture but will need yet another somewhat confusing (to one or more that are not the authors) burden.
Do you agree this is a valid concern generally — to at least want to put out feelers on this? (my opinion being just one that made its way to you of possibly more out there)

capture is the term used for what a RegExp does for (pattern) (a capture group) and (?<name>pattern) (a named capture group). It is also consistent with the terminology used in other languages and in the Prior Art referenced in the explainer.

{ capture: 'indices' } being what it takes to end up with { offsets: something[] }

That is not what happens. { capture: 'indices' } indicates that the captures should only be pairs of indices:
const re = /a*(?<Z>z)?/;
const input = "xaaaz";
const match1 = re.exec(input, { capture: 'strings' }); // or just re.exec(input)
console.log(match1); // ["aaaz", "z"]

const match2 = re.exec(input, { capture: 'indices' });
console.log(match2); // [[1, 5], [4, 5]]

This differs from the alternative version of proposal that instead adds an additional indices property to the result.

@rbuckton — thanks for the added clarification… to be fair, I'll need to reflect more on this myself before arguing oneway or another, and at least hope my input here being one from the end-user perspective is of value somehow.

I'm closing this as the consensus decision was to switch back to a property on the result from RegExpBuiltinExec. As a result we are no longer using an options object.


feat(sync-files): enable auto merge

Signed-off-by: h-ohta<EMAIL_ADDRESS>Description

Add Enable auto merge as a reference
https://github.com/autowarefoundation/autoware-github-actions/blob/main/sync-branches/action.yaml#L102-L108
Actually, we also have to set auto-merge-method variables` to any in order to enable auto merge.

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[x] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[x] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

Released v1.5.0.
https://github.com/autowarefoundation/autoware-github-actions/releases/tag/v1.5.0


IllegalArgumentException on Export from Query

System information:

MacOS 10.14.6 (Mojave)
DBeaver <IP_ADDRESS>001191557
java 13 2019-09-17

Connection specification:

DB: Hive 1.2.1
Driver: DBeaver Hive Default
No tunnels or proxies

Describe the problem you're observing:
When I use the "Export from Query" flow, I get a "Task Execution Failed" error message.
Prior to upgrading to DBeaver 6.3.3, I would regularly export data from queries to a CSV file. Since the upgrade, this process is no longer working. After I go through the various export dialogs and click "Start", I immediately get an error message with "Task Execution Failed"
One interesting thing I found: the error message details (posted below) reference a file: /Users/cwalker/.eclipse_keyring. This file does not exist on my system.
The query is a simple one:
select * from userdb_cwalker.cdh_contacts_combined;

I can execute this query & get results from the main DB window just fine; it's the export that's failing.
Steps to reproduce, if exist:
This happens 100% of the time for me, but I don't know what circumstances are necessary for others to reproduce it. I select my query, choose "Execute from Query" from the contextual menu, step through the dialogs, click "Start", and then get the error message.
Include any warning/errors/backtraces from the logs
In the Error pane, I see error messages logged for every attempt. Here's the details from the most useful one:

Plug-In: org.jkiss.dbeaver.model

Severity: Error

Message: [none]

Stack trace:
java.lang.IllegalArgumentException:
at org.eclipse.core.runtime.Assert.isLegal(Assert.java:66)
at org.eclipse.core.runtime.Assert.isLegal(Assert.java:50)
at org.jkiss.dbeaver.model.text.parser.TPRuleBasedScanner.checkRange(TPRuleBasedScanner.java:116)
at org.jkiss.dbeaver.model.text.parser.TPRuleBasedScanner.setRange(TPRuleBasedScanner.java:88)
at org.jkiss.dbeaver.model.sql.parser.SQLScriptParser.parseParameters(SQLScriptParser.java:524)
at org.jkiss.dbeaver.model.sql.data.SQLQueryDataContainer.readData(SQLQueryDataContainer.java:93)
at org.jkiss.dbeaver.tools.transfer.database.DatabaseTransferProducer.lambda$0(DatabaseTransferProducer.java:214)
at org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:159)
at org.jkiss.dbeaver.tools.transfer.database.DatabaseTransferProducer.transferData(DatabaseTransferProducer.java:138)
at org.jkiss.dbeaver.tools.transfer.database.DatabaseTransferProducer.transferData(DatabaseTransferProducer.java:1)
at org.jkiss.dbeaver.tools.transfer.DataTransferJob.transferData(DataTransferJob.java:109)
at org.jkiss.dbeaver.tools.transfer.DataTransferJob.run(DataTransferJob.java:80)
at org.jkiss.dbeaver.runtime.RunnableContextDelegate.lambda$0(RunnableContextDelegate.java:39)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)

Session data:
eclipse.buildId=unknown
java.version=13
java.vendor=Oracle Corporation
BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_CA
Framework arguments:  -keyring /Users/cwalker/.eclipse_keyring
Command-line arguments:  -os macosx -ws cocoa -arch x86_64 -keyring /Users/cwalker/.eclipse_keyring

Confirmed that this is working for me in 6.3.4. Thank you!


catalog app upgrade does not work with 4 digit version

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):
Setup helm chart with 4 digit version number
Result:
Upgrade window will not work with helm chart.
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.4.3
Installation option (single install/HA): HA

gz#10473

Closing issue in favor of https://github.com/rancher/rancher/issues/27150


Occasional DB deadlock causes update to fail

Which version and edition of Flyway are you using?
Flyway Community Edition 5.1.4 by Boxfuse
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Command-line
Which database are you using (type & version)?
PostgreSQL 9.6.3 (Amazon RDS)
Which operating system are you using?
I assume it's linux, though I'm not seeing any specific OS listed on the RDS instance info page.
What did you do?
Ran the migrate script to upgrade my DB.
docker run --rm -v ./docker/postgres/rules/migration:/flyway/sql boxfuse/flyway:5.1.4-alpine -user=$POSTGRES_USERNAME -password=$POSTGRES_PASSWORD -url=jdbc:postgresql://$POSTGRES_HOSTNAME:$POSTGRES_PORT/rules -mixed=true -installedBy=ds-jenkins migrate
The upgrade failed on the recreation of the view (as noted in the error below).
ALTER table rule
  ADD COLUMN is_batch BOOLEAN;

ALTER table rule
  ALTER COLUMN is_batch SET DEFAULT FALSE;

CREATE OR REPLACE VIEW complete_rule_view AS ...big view join related to the rule table that was modified...

What did you expect to see?
Successful table alter and view recreation.
The bug isn't easy to reproduce. I've run this script a couple dozen times on the DB as various test runs for a production deploy. I'll test it, then restore a snapshot back before the flyway change. Then do it again, rinse lather, repeat.
It's failed twice in those couple dozen runs.
We've done a bunch of similar flyway migrations in the past without issue. Same table, same view even. I'm not sure what's special about this particular one. Then again, it's erratic, so maybe we just got lucky before and not hit it.
I haven't had to stop the processes using the DB in the past to run the migration, but maybe I need to this time?
What did you see instead?
SQL State  : 40P01
Error Code : 0
Message    : ERROR: deadlock detected
  Detail: Process 15195 waits for AccessExclusiveLock on relation 37941 of database 16671; blocked by process 12370.
Process 12370 waits for AccessShareLock on relation 37879 of database 16671; blocked by process 15195.
  Hint: See server log for query details.
Location   : /flyway/sql/V3_0__add_is_bulk_to_rule.sql (/flyway/sql/V3_0__add_is_bulk_to_rule.sql)
Line       : 7
Statement  : CREATE OR REPLACE VIEW complete_rule_view .... blah blah

Flyway executes all these statements sequentially within a single transaction on a single connection. This is most likely a PostgreSQL bug. Try upgrading to PostgreSQL 9.6.10 or 10.5 and see if this fixes the issue. Otherwise file an issue with PostgreSQL.


Inconsistent evaluation of tf/ss systems with pole at the origin

Systems that have a pole at the origin return inconsistent values:
import control as ct
sys_tf = ct.tf([1], [1, 0])
sys_ss = ct.tf2ss(sys_tf)

sys_tf(0)        # returns (inf+0j) with divide by zero warning
sys_ss(0)        # LinAlgError: Singular matrix
sys_tf.dcgain()  # return array(inf)
sys_ss.dcgain()  # returns array(nan)

I think all of these should return inf (or array(inf)).
If you have a pole and zero at the origin, you get nan or 1:
sys_tf = ct.tf([1, 0], [1, 0])
sys_ss = ct.tf2ss(sys_tf)

sys_tf(0)        # returns (nan+0j) with invalid value warning
sys_ss(0)        # returns (1+0j) [state space system is empty]
sys_tf.dcgain()  # returns array(nan)
sys_ss.dcgain()  # returns (1+0j) [state space system is empty]

I think all of these cases should produce nan.
I have a partial fix in a branch, but want to see what people think the "right" answer is before committing it.

Would this apply to evaluating a system at any s-value where it has a pole?
For the second set of examples, for TFs one objection is that \lim_{s->0} (s/s) = 1.  For a Bode or Nyquist plot, for example, wouldn't one want this limit, and not a NaN ?
For state-space objects, why would you want a static gain to evaluate to NaN?
Separarately for state-space, the MIMO case might be tricky: consider a diagonal system with g_11 = 1/(s+1), g_22 = 1/s; would evaluating this at s = 0 be expected to give [[1, 0], [0, inf]] ?  I wonder how easy this will be to arrange:
n [37]: np.eye(2) @ np.diag([1, np.inf]) @ np.eye(2)
<ipython-input-37-7a3bfddc9905>:1: RuntimeWarning: invalid value encountered in matmul
  np.eye(2) @ np.diag([1, np.inf]) @ np.eye(2)
Out[37]:
array([[nan, nan],
       [nan, inf]])

+1 for consistency. nan looks like a good choice to me.
Although one could argue that the transfer function should make a distinction between true marginal stability cases and cases where the pole/zero at 0 cancel each other. (Just as @roryyorke pointed out just now)

I think point-wise evaluation at 0 is not the correct way to compute the limit but using the explicit expression C @ solve(A, B) for the limit should be preferred (and the discrete version obviously).  If A is not invertible then it should return inf with correct shape. NaN doesn't seem to be a meaningful return value for the gain.

For state-space objects, why would you want a static gain to evaluate to NaN?

If the system is not asymptotically stable, is there a static gain?

That's inf by convention which is the value of the limit, NaN is suitable for cases like 0/0 etc.

I thought it might be interesting to see what Python and NumPy do with various cases:
Expression                                             Returns
----------                                             --------
1 / 0                                                  ZeroDivisionError
1j / 0j                                                ZeroDivisionError
np.array(1) / np.array(0)                              inf
np.array(0) / np.array(0)                              nan
np.array(1j) / np.array(0j)                            nan + infj
np.array(1) / np.array(0j)                             inf + nanj
np.array(1 + 0j) / np.array(0j)                        inf + nanj
np.array(1j) / np.array(0)                             nan + infj
np.array(0j) / np.array(0j)                            nan + nanj
np.array(0) / np.array(0j)                             nan + nanj
np.polyval([1, 0], 1j) / np.polyval([1, 0], 0j)        nan + infj
np.polyval([1, 1], 1j) / np.polyval([1, 0], 0j)        inf + infj
np.polyval([1, 0], 1j) / np.polyval([1, 0, 0], 0j)     nan + infj
np.polyval([1, 0], 0j) / np.polyval([1, 0], 0j)        nan + nanj
np.polyval([1, 1], 0j) / np.polyval([1, 0], 0j)        inf + nanj

So basically the real and imaginary parts of the numerator are evaluated independently and 1 / 0 returns inf while 0 / 0 returns nan.  These should happen automatically for the TransferFunction class and StateSpace objects should be consistent.
Regarding unstable systems: while it is true that H(jw) is not well defined in terms of giving the magnitude and phase of the output for a sinusoidal input, it is still the case that we want to evaluate transfer functions at these values.  For example, the loop transfer function can be unstable while the closed loop system is stable.
Thoughts?


Don't get any data via Resol Vbus/USB Set-Up?!

Hi, I'm trying to get the Resol Vbus data into Home Assistant via the USB approach. My Resol is connected via an USB connection to my raspberry. I'm using the Json Live Server as a HAOS add-on but can't manage to get the data into Home Assistant. What am I doing wrong??
I modified the config file as described.. .  see below:
/*! resol-vbus | Copyright (c) 2013-present, Daniel Wippermann | MIT license */
const path = require('path');
const config = {
/**
 * The level of details for log messages.
 * @type {String}
 */
logLevel: 'debug',

/**
 * The port number for the HTTP server to listen to.
 * @type {Number}
 */
httpPort: 3333,

/**
 * The inteval in milliseconds between two writes of the logging file.
 * @type {Number}
 */
loggingInterval: 60000,

/**
 * The filename of the logging file.
 * @type {String}
 */
loggingFilename: path.resolve(__dirname, 'live-data.json'),

/**
 * Text file logging interval in milliseconds. A value of zero disables this functionality.
 */
textLoggingInterval: 0,

/**
 * Text file logging time to live in milliseconds.
 */
textLoggingTimeToLive: 60000,

/**
 * Text file logging directory.
 */
textLoggingPath: path.resolve(__dirname, 'log'),

/**
 * Text file logging options, passed to the `TextConverter` constructor.
 */
textLoggingOptions: {
    columnSeparator: '\t',
    lineSeparator: '\r\n',
    separateDateAndTime: false,
},

/**
 * Either 'TcpConnection' or 'SerialConnection' to connect to the VBus.
 * @type {String}
 */
connectionClassName: 'SerialConnection',

connectionOptions: {
    /**
     * SerialConnection only:
     * The serial port to which the Vbus/USB device is connected.
     * @type {String}
     */
    path: '/dev/ttyUSB0',

    /**
     * TcpConnection only:
     * The host name / IP address of the VBus/LAN or Datalogger device.
     * @type {String}
     */
    host: '<IP_ADDRESS>:3333',

    /**
     * TcpConnection only:
     * The password for the VBus/LAN or Datalogger device.
     * @type {String}
     */
    password: 'vbus',
},

/**
 * A map of packet field IDs to their custom name.
 */
packetFieldNameMap: {
    '00_0010_7E11_10_0100_000_2_0': 'Temperature collector',  // instead of "Temperater sensor 1"
},

/**
 * A list of EM (extension module) sub-addresses to simulate.
 */
emSimulatorSubAdresses: [
    // 1,
    // 2,
    // 3,
    // 4,
    // 5,
],

};
module.exports = config;
I created the following sensor under Sensors.yaml
- platform: deltasol
host: <IP_ADDRESS>:3333
And find below the log data Json Live Server:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
--- VERSIONS ---
add-on version: 0.0.7
nodejs version: v21.7.1
npm version: 10.5.0
--- DEVICES ---
/dev/ttyUSB0
/dev/ttyACM0
--- json-live-data-server ---
debug: Starting server...
debug: Connect to VBus data source...
info: Ready to serve from the following URLs:
info:     - http://<IP_ADDRESS>:3333/api/v1/live-data (internal)
info:     - http://<IP_ADDRESS>:3333/api/v1/live-data
debug: HeaderSet complete
debug: HeaderSet complete
debug: HeaderSet complete
debug: HeaderSet complete
debug: HeaderSet complete
debug: HeaderSet complete
debug: HeaderSet complete
debug: HeaderSet complete
debug: HeaderSet complete
debug: HeaderSet complete
debug: HeaderSet complete
debug: HeaderSet complete
debug: HeaderSet complete
debug: HeaderSet complete
debug: HeaderSet complete
debug: HeaderSet complete
debug: HeaderSet complete
debug: HeaderSet complete
debug: HeaderSet complete

First remove host and password from config.js then restart the addon. Then enable debugging for the integration and restart Home Assistant Core. Post all deltasol logs from home Assistant core here.

I think this is it.
2024-03-13 09:31:14.825 WARNING (SyncWorker_3) [homeassistant.loader] We found a custom integration deltasol which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-03-13 09:31:26.196 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.components.frontend. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to import functions used from frontend directly at custom_components/hacs/frontend.py, line 68: hass.components.frontend.async_register_built_in_panel(, please create a bug report at https://github.com/hacs/integration/issues

There is no debug log, read documentation of integration and enable debug logs and post them here.

I'm sorry.
here it is
2024-03-13 10:11:54.092 INFO (SyncWorker_2) [custom_components.deltasol] Auto detecting Resol product from http://<IP_ADDRESS>:3333/cgi-bin/get_resol_device_information
2024-03-13 10:11:54.129 DEBUG (SyncWorker_2) [custom_components.deltasol] response: vendor = "RESOL"
product = "DL2"
serial = "001E66000000"
version = "2.1.0"
build = "201311280853"
name = "DL2-001E66000000"
features = "vbus,dl2"
2024-03-13 10:11:54.129 INFO (SyncWorker_2) [custom_components.deltasol] Detected Resol product: dl2
2024-03-13 10:11:54.135 DEBUG (SyncWorker_2) [custom_components.deltasol] Retrieving data from dlx
2024-03-13 10:11:54.135 DEBUG (SyncWorker_2) [custom_components.deltasol] DLX requesting sensor data url http://<IP_ADDRESS>:3333/dlx/download/live
2024-03-13 10:11:54.162 DEBUG (SyncWorker_2) [custom_components.deltasol] DLX response: {'headersets': [{'timestamp':<PHONE_NUMBER>.952, 'packets': []}], 'headerset_stats': {'headerset_count': 1, 'min_timestamp':<PHONE_NUMBER>.952, 'max_timestamp':<PHONE_NUMBER>.952}, 'headers': [], 'language': 'en'}
2024-03-13 10:11:54.163 DEBUG (MainThread) [custom_components.deltasol] Finished fetching deltasol_sensor data in 0.071 seconds (success: True)
2024-03-13 10:11:54.163 DEBUG (MainThread) [custom_components.deltasol] Checking for sensors with old ids in registry.

okay. the connection of the integration to the addon seems to work. but it gets no data content of the addon. can you please
path: '/dev/ttyACM0',
in add-on config.js
and restart the add-on and then restart home assistant core and post both logs. of add-on and home asisstant core debug deltasol.

It is difficult for me to understand some things, i have some brain damage so what for some one else is a walk in the park is for me very difficult.
So be patient

okay, it should work now. you should find the sensors in home assistant now. check for the sensor sensor.temperature_sensor_1 for example.

YES.
thank you.
somethimes it so easy.


rvm::passenger::apache doesn't pass spawnmethod to apache::mod::passenger

While rvm::passenger::apache defines a default for spawnmethod and the docs refer to setting this parameter, I don't see anywhere where it gets passed along to apache::mod::passenger to make it into the actual passenger configuration files.  This might be because puppetlabs-apache didn't support the parameter either, so passing it here wouldn't have done any good.
I've got changes merged into puppetlabs-apache to support spawnmethod, although it hasn't made it into a release yet.  With that in place we should be able to pass the variable and have something actually happen.

I'm going to close this based on its age. If you can still reproduce it, please reopen.


[Enhancement] Support Nextra v3 Template

The current Nextra docs template is based on version 2.2.14, but v3 is on the way. We could update the main branch to support Nextra v3, while keeping the v2 version in a separate branch.

related: #72

Any updates on this?
Following the v3 nextra docs, I deployed directly to vercel but then it is using the nextra v2 it seems.

Hi @clemwo, you can check out my website's documentation at https://1chooo.com: https://github.com/1chooo/1chooo.com/tree/main/apps/docs. I've updated it to Nextra V3, as the official template isn't available yet. I followed the website's guidance to recreate and implement it successfully. I hope this helps!

Hi @clemwo, you can check out my website's documentation at https://1chooo.com: https://github.com/1chooo/1chooo.com/tree/main/apps/docs. I've updated it to Nextra V3, as the official template isn't available yet. I followed the website's guidance to recreate and implement it successfully. I hope this helps!

Hi, thanks for your work!
I will check it out in a couple of days. Just wanted to leave a thank you before :)

Hi I was looking on this and created a template for this. Checkout https://github.com/ShrihariMohan/nextra-v3-docs-template


App crashes with failed to initialise OKHTTP client in pre-21 devices

Summary:
App crashes with failed to initialize OKHTTP client in pre-LoliPop devices
Steps to reproduce:
How can we reproduce the issue?
Open the app in [19]- devices
System logs:
java.lang.ExceptionInInitializerError
at okhttp3.internal.platform.Platform$Companion.findPlatform(Platform.kt:211)
at okhttp3.internal.platform.Platform$Companion.access$findPlatform(Platform.kt:179)
at okhttp3.internal.platform.Platform.<clinit>(Platform.kt:180)
at okhttp3.OkHttpClient.<init>(OkHttpClient.kt:219)
at okhttp3.OkHttpClient$Builder.build(OkHttpClient.kt:955)
at fr.free.nrw.commons.OkHttpConnectionFactory.createClient(OkHttpConnectionFactory.java:38)
at fr.free.nrw.commons.OkHttpConnectionFactory.<clinit>(OkHttpConnectionFactory.java:24)
at fr.free.nrw.commons.CommonsAppAdapter.getOkHttpClient(CommonsAppAdapter.java:39)
at org.wikipedia.dataclient.ServiceFactory.createRetrofit(ServiceFactory.java:60)
at org.wikipedia.dataclient.ServiceFactory.get(ServiceFactory.java:27)
at fr.free.nrw.commons.auth.LoginActivity.doLogin(LoginActivity.java:262)
at fr.free.nrw.commons.auth.LoginActivity.performLogin(LoginActivity.java:257)
at fr.free.nrw.commons.auth.LoginActivity_ViewBinding$1.doClick(LoginActivity_ViewBinding.java:53)
at butterknife.internal.DebouncingOnClickListener.onClick(DebouncingOnClickListener.java:18)
at android.view.View.performClick(View.java:4640)
at android.view.View$PerformClick.run(View.java:19421)
at android.os.Handler.handleCallback(Handler.java:733)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:146)
at android.app.ActivityThread.main(ActivityThread.java:5487)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1283)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1099)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.IllegalStateException: Expected Android API level 21+ but was 19
at okhttp3.internal.platform.AndroidPlatform.<clinit>(AndroidPlatform.kt:232)

Device and Android version:
ANDROID_VERSION=4.4.2
PHONE_MODEL=GT-N5110
Commons app version:
2.12.3
Screen-shots:
NA

Any suggestions on this, @maskaravivek @neslihanturan @macgills.  The solution I have come to is degrading the okhttp version. Do you guys think there could be a better way to do this?

Degrade, okhttp later versions require android 5.0.
Or upgrade our minSDK, I don't have access to our statistics to see how many users would be affected

Upgrading to 21 is something not we are considering as of now, I remember having a discussion regarding this with @misaochan . Seems like the only option is to degrade okhttp, waiting for input from others.

Removing access from 5.9% of devices is a lot, especially given that we are targeting underrepresented (i.e. global south) countries. If it was possible to degrade okhttp without adverse effect I would strongly prefer that.

4% as we already do not target all devices. I don't have any data to  point to about the SDK levels of android by region as these are only global figures but they are global so  *3/*2 might not shock me for a particular region but *10 certainly would

Hi @macgills  @misaochan  Do we have a conclusion on this?

Downgrade okhttp, safest all around, if we want to upgrade the sdk we can open an issue and discuss it there

HI @misaochan  @macgills Apparently downgrading the okhttp would need us to downgrade retrofit as well to one of the 1.9 versions instead of the 2.X on which we are, would we be okay with that?


Paused subscriptions should keep access until end of billing period

Describe the bug
When a paying customer pauses their subscription they should keep access to paid features until the end of their current billing period. Currently, they immediately lose access.
This PR in Pay should handle the issue without any changes (outside of the migration) to this codebase. https://github.com/pay-rails/pay/pull/687

Closed via #726.


Metadata

charset

@hannahzacharski55 could you be more specific on what this Issue (or any of the others are) about?

This is a private account. My issues are private.

I would recommend forking this repository and creating issues on your account, then.


about thesis

Hello，I want to konw whether your thesis have English version? Thank you very much!

Sadly not yet. I haven't found the time to translate it yet, but i plan to.

Sorry to bother you.I can't find the link to your paper. Can you offer the link to read it? Thanks very much!


[github-actions] build checks fail intermittently

Log snippet:
++ repo_dir=/home/runner/work/ot-efr32/ot-efr32
+ OT_OPTIONS=("-DCMAKE_BUILD_TYPE=MinSizeRel" "-DOT_DIAGNOSTIC=ON" "-DOT_EXTERNAL_HEAP=ON" "-DOT_SLAAC=ON")
+ readonly OT_OPTIONS
+ main efr32mg13 -DOT_COMPILE_WARNING_AS_ERROR=ON -DOT_COMMISSIONER=ON -DOT_DHCP6_CLIENT=ON -DOT_DHCP6_SERVER=ON -DOT_DNS_CLIENT=ON -DOT_JOINER=ON -DOT_BORDER_ROUTER=ON -DOT_REFERENCE_DEVICE=ON -DOT_COAP=ON -DOT_COAPS=ON -DOT_LOG_LEVEL_DYNAMIC=ON -DOT_DIAGNOSTIC=ON -DOT_FULL_LOGS=ON -DOT_MAC_FILTER=ON -DBOARD=brd4168a
+ local 'usage=usage: /home/runner/work/ot-efr32/ot-efr32/script/build [-h] [--skip-silabs-apps] <efr32 platform> -DBOARD=<brdXXXXy> [-D<OT_XXXX=ON> -D<OT_YYYY=OFF>]'
+ local skip_silabs_apps=false
+ optspec=:h-:
+ getopts :h-: optchar
+ local efr32_platforms
++ efr32_get_platforms
++ '[' 0 -ne 0 ']'
++ local platform_dir=/home/runner/work/ot-efr32/ot-efr32/src
++ find /home/runner/work/ot-efr32/ot-efr32/src -type d -name '*efr32*' -exec basename '{}' ';'
++ sort
+ efr32_platforms='efr32mg1
efr32mg12
efr32mg13
efr32mg21'
+ [[ 16 == 0 ]]
+ local platform=efr32mg13
+ grep -wq efr32mg13
+ echo 'efr32mg1
efr32mg12
efr32mg13
efr32mg21'
/home/runner/work/ot-efr32/ot-efr32/script/build: line 128: echo: write error: Broken pipe
+ die 'Unsupported platform efr32mg13'
 ** ERROR: Unsupported platform efr32mg13
+ echo ' ** ERROR: Unsupported platform efr32mg13'
+ exit 1
Error: Process completed with exit code 1.

logs_566.zip
https://github.com/openthread/ot-efr32/runs/5195633403?check_suite_focus=true

@lmnotran , can you help take a look?

Hi @jwhui ! That's strange. We haven't changed anything related to this check recently. I'll look into it. Thanks!

Hi @jwhui ! That's strange. We haven't changed anything related to this check recently. I'll look into it. Thanks!

@lmnotran , it's actually been happening for quite some time. I just haven't reported it until now. Thanks for taking a look!

Another example: https://github.com/openthread/ot-efr32/runs/5243657339?check_suite_focus=true

Another instance: https://github.com/openthread/ot-efr32/runs/5342665788?check_suite_focus=true


Implement PrimaryKey for all &T where T implements PrimaryKey.

    for<'a> &'a (K, u64): PrimaryKey<'a>,

This allows having type constraints like this for types that wrap storage-plus. In english: for all lifetimes 'a &'a (K, u64) is a valid key. I need this generic in order to implement cw-future-map.

i am going to fork pending some resolution to how to land PRs into CosmWasm. no bad vibes, and i'd like to continue to contribute to and work with the CosmWasm repositories when there is a way to do so again.
relevant PRs:

https://github.com/CosmWasm/cosmwasm/pull/1593
https://github.com/cosmorama/wynddao/pull/4
https://github.com/CosmWasm/cw-multi-test/pull/23
https://github.com/CosmWasm/cw-storage-plus/pull/30

@webmaster128 my understanding is that because serialization takes a reference to the type being serialized, it is more efficient to use references as keys as (1) the underlying serialization doesn't change and (2) you can avoid moves (and in turn clones) when calling methods on the map.

Not sure what kind of issues the CI has or had. Somehow the GitHub connection got lost. But in #31 it worked today, also for fork PRs.
When the changes requested by @chipshort are in this is good to go IMO.

@webmaster128 my understanding is that because serialization takes a reference to the type being serialized, it is more efficient to use references as keys as (1) the underlying serialization doesn't change and (2) you can avoid moves (and in turn clones) when calling methods on the map.

This is correct. Using references is a good option for serialising stuff, while deserialization is always to an owned type, so, using references doesn't impact it.
Just seen this. Will take a detailed look and comment back.

for some additional context, here is the map that i was able to make with these changes (we forked to include this change while the ATOM proposal was pending): cw-wormhole.
@chipshort - I've made your requested changes in the most recent commit. thank you!


hakyll package on 20.03 has preview server disabled

Describe the bug
The hakyll package on NixOS 20.03 has the preview server disabled, but this does not seem to be explicitly configured anywhere, and the dependencies are still pulled in which suggests that this isn't intentional. Previously the preview server has always been available, so I was hoping this could be reinstated.
To Reproduce

git clone https://github.com/vaibhavsagar/website
cd website
git checkout b07fce730ed566300e0a6304e875965b5bb1a7ff
nix-shell --run 'runhaskell site.hs server'

Expected behavior
A web server is launched.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
I looked at the source and couldn't find any mentions of previewServer, which is the flag that disables the preview server for Hakyll.
Notify maintainers
@cdepillabout(?)
Metadata
This is my system info, although the problem is with commit 5272327b81ed355bbed5659b8d303cf2979b6953 of nixpkgs (see versions.json in my repository)

system: "x86_64-linux"
host os: Linux 4.19.113, NixOS, 19.09.2345.6d445f8398d (Loris)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.3
channels(vaibhavsagar): ""
channels(root): "nixos-19.09.2345.6d445f8398d"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

I confirm the issue, I just stumbled on exactly the same issue after upgrading to 20.03 today :disappointed:
I think ideally the default flags should respect the default, that is all enabled except buildwebsite.
In the mean time, if anyone has a workaround, I'd be interested!

I took a quick look at this as well, and I also don't see why the preview server wouldn't be enabled.
If one of you (or anyone else) wants to take a look at this and figure out why the preview server is disabled, I'd be happy to merge in a fix.

Here's a snippet of the build output of callHackage "hakyll" "<IP_ADDRESS>" {}:
Configuring hakyll-<IP_ADDRESS>...
Flags chosen: buildwebsite=False, checkexternal=True, previewserver=False,
usepandoc=True, watchserver=True

I don't understand why the previewServer=False flag is being set though. Still investigating.

I think I've figured this out: the upper bound on warp is too restrictive, so Cabal seems to be setting that flag to False for us.
If I clone the hakyll repository, check out the v<IP_ADDRESS> tag, and try to build it with this default.nix:
let
  nixpkgs-src = builtins.fetchTarball {
    url = "https://github.com/NixOS/nixpkgs/tarball/5272327b81ed355bbed5659b8d303cf2979b6953";
    sha256 = "0182ys095dfx02vl2a20j1hz92dx3mfgz2a6fhn31bqlp1wa8hlq";
  };
  nixpkgs = import nixpkgs-src {};
  hakyll = nixpkgs.haskellPackages.callCabal2nix "hakyll" ./. {};
in if nixpkgs.lib.inNixShell then hakyll.env else hakyll

Then I get this (previewServer=False):
Flags chosen: buildwebsite=False, checkexternal=True, previewserver=False,
usepandoc=True, watchserver=True

When I try to runghc Setup.hs configure --enable-tests; runghc Setup.hs build then I also get the same thing.
However, if I look at the version of warp that's pulled in:
[nix-shell:~/repos/hakyll]$ ghc-pkg list | grep warp
    warp-3.3.5

I see that it is higher than the upper bound of 3.3 in hakyll.cabal. After changing the upper bound to 3.4, this is what I get from nix-build (previewServer=True):
Flags chosen: buildwebsite=False, checkexternal=True, previewserver=True,
usepandoc=True, watchserver=True

I suggest patching hakyll in nixpkgs to bump the upper bound on warp, because doJailbreak doesn't work on conditional stanzas anyway.

Here's my suggested fix: https://github.com/NixOS/nixpkgs/pull/85753


ARROW-6411: [Python][Parquet] Improve performance of DictEncoder::PutIndices

I don't really understand why this is faster, though.
before:
[ 25.00%] ··· parquet.ParquetWriteDictionaries.time_write_random_order
               nunique
              --------- ---------
                 1000    2.16±0s
                100000   1.87±0s
[ 50.00%] ··· parquet.ParquetWriteDictionaries.time_write_sequential
               nunique
              --------- ---------
                 1000    1.85±0s
                100000   1.33±0s

After:
[ 25.00%] ··· parquet.ParquetWriteDictionaries.time_write_random_order
               nunique
              --------- ---------
                 1000    942±0ms
                100000   1.21±0s
[ 50.00%] ··· parquet.ParquetWriteDictionaries.time_write_sequential
               nunique
              --------- ---------
                 1000    571±0ms
                100000   704±0ms

On an i9-9960X CPU before these changes perf reported that __memmove_avx_unaligned_erms was taking up a lot of time. In principle std::vector::reserve should be correct since memory is not initialized, but something weird seems to be going wrong. If anyone has any ideas I'm interested to learn more. In any case I'll stick with the empirical benchmark evidence on this
I started to refactor to use TypedBufferBuilder<int32_t> but I'm not sure about the performance of that for scalar appends vs. std::vector so I'll leave that for future experimentation.

Here's a different processor (Xeon E-2176M), still compiling with clang 7.0
before
[ 25.00%] ··· parquet.ParquetWriteDictionaries.time_write_random_order                                                                                ok
[ 25.00%] ··· ========= =========
               nunique
              --------- ---------
                 1000    1.65±0s
                100000   1.53±0s
              ========= =========

[ 50.00%] ··· parquet.ParquetWriteDictionaries.time_write_sequential                                                                                ok
[ 50.00%] ··· ========= =========
               nunique
              --------- ---------
                 1000    1.31±0s
                100000   1.04±0s
              ========= =========

after
[ 25.00%] ··· parquet.ParquetWriteDictionaries.time_write_random_order                                                                                ok
[ 25.00%] ··· ========= =========
               nunique
              --------- ---------
                 1000    891±0ms
                100000   1.16±0s
              ========= =========

[ 50.00%] ··· parquet.ParquetWriteDictionaries.time_write_sequential                                                                                ok
[ 50.00%] ··· ========= =========
               nunique
              --------- ---------
                 1000    566±0ms
                100000   720±0ms
              ========= =========

The perf issue is also present with gcc 8.3, which net performs better on this machine
before
[ 25.00%] ··· parquet.ParquetWriteDictionaries.time_write_random_order                                                                                ok
[ 25.00%] ··· ========= =========
               nunique
              --------- ---------
                 1000    1.57±0s
                100000   1.40±0s
              ========= =========

[ 50.00%] ··· parquet.ParquetWriteDictionaries.time_write_sequential                                                                                ok
[ 50.00%] ··· ========= =========
               nunique
              --------- ---------
                 1000    1.28±0s
                100000   955±0ms
              ========= =========

after
[ 25.00%] ··· parquet.ParquetWriteDictionaries.time_write_random_order
                                                                                ok
[ 25.00%] ··· ========= =========
               nunique
              --------- ---------
                 1000    695±0ms
                100000   988±0ms
              ========= =========

[ 50.00%] ··· parquet.ParquetWriteDictionaries.time_write_sequential                                                                                ok
[ 50.00%] ··· ========= =========
               nunique
              --------- ---------
                 1000    418±0ms
                100000   564±0ms
              ========= =========

Codecov Report

Merging #5248 into master will increase coverage by 1.54%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #5248      +/-   ##
==========================================
+ Coverage   87.65%   89.19%   +1.54%
==========================================
  Files        1033      750     -283
  Lines      148767   107803   -40964
  Branches     1437        0    -1437
==========================================
- Hits       130397    96160   -34237
+ Misses      18008    11643    -6365
+ Partials      362        0     -362

Impacted Files
Coverage Δ

cpp/src/parquet/encoding.cc
92.37% <100%> (ø)
:arrow_up:

cpp/src/arrow/csv/column_builder.cc
95.54% <0%> (-1.49%)
:arrow_down:

cpp/src/plasma/thirdparty/ae/ae.c
70.75% <0%> (-0.95%)
:arrow_down:

python/pyarrow/tests/test_parquet.py
96.55% <0%> (-0.12%)
:arrow_down:

js/src/util/fn.ts

go/arrow/memory/memory_avx2_amd64.go

rust/datafusion/src/execution/filter.rs

rust/arrow/src/csv/writer.rs

rust/datafusion/src/bin/main.rs

go/arrow/ipc/file_reader.go

... and 277 more

Continue to review full report at Codecov.

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

I'm going to add a C++ benchmark so this is easy to profile without having to go through Python

C++ benchmark results
before
----------------------------------------------------------------------------------------
Benchmark                                                 Time           CPU Iterations
----------------------------------------------------------------------------------------
BM_ArrowBinaryDict/EncodeDictDirectInt8/1048576     7334087 ns    7333876 ns         98   136.354M items/s
BM_ArrowBinaryDict/EncodeDictDirectInt16/1048576    7022430 ns    7022412 ns        100   142.401M items/s
BM_ArrowBinaryDict/EncodeDictDirectInt32/1048576    7061033 ns    7060870 ns         99   141.626M items/s
BM_ArrowBinaryDict/EncodeDictDirectInt64/1048576    7084581 ns    7084398 ns         97   141.155M items/s

after
----------------------------------------------------------------------------------------
Benchmark                                                 Time           CPU Iterations
----------------------------------------------------------------------------------------
BM_ArrowBinaryDict/EncodeDictDirectInt8/1048576     4387151 ns    4387175 ns        156   227.937M items/s
BM_ArrowBinaryDict/EncodeDictDirectInt16/1048576    4446167 ns    4446074 ns        159   224.918M items/s
BM_ArrowBinaryDict/EncodeDictDirectInt32/1048576    4501028 ns    4500934 ns        156   222.176M items/s
BM_ArrowBinaryDict/EncodeDictDirectInt64/1048576    4635792 ns    4635728 ns        150   215.716M items/s

+1. I welcome further analysis of this issue in subsequent JIRA issues, etc.


[stable/redis] fix cluster-less mode

what
bring back role selector to redis-master-svc
why
If cluster.enabled has value 'false' and metrics.enabled has value true then redis-master service selects both pods (master one and metrics one)

/assign @carrodher

Hi @alebabai
I don't really understand the issue. I deployed this chart using cluster.enabled and metrics.enabled as you suggested:
helm install stable/redis --set cluster.enabled=true,metrics.enabled=true --name xxx-xxx

I checked the selectors of Master svc:
kubectl get svc xxx-xxx-redis-master -o jsonpath='{.spec.selector}'
map[app:redis release:xxx-xxx role:master]

There's only a pod that meets those requirements:
kubectl get pods -l app=redis -l release=dusty-porcupine -l role=master
NAME                             READY     STATUS    RESTARTS   AGE
xxx-xxx-redis-master-0   1/1       Running   0          2m

Why would it select another pod?

Oh! I can reproduce the bug now! Thanks for reporting it!

/ok-to-test
/lgtm


SecurityError in Safari when storage is disabled

When a user has selected to block "cookies and website data" in Safari, attempting to access localStorage (annoyingly) throws a SecurityError.

For our particular use case, it would be completely fine to simply have the state live in memory and get blown away as soon as the user leaves the page.
However, you could also imagine wanting a way to handle the situation in application code, perhaps warning the user. Maybe based on an event emitted by the adapter, similar to the QUOTA_EXCEEDED_ERR case?

Can you create a PR for that?


Bug: First selected item is wrong

Using Compose for Desktop v1.4.3 I observed a wrong behavior on selection of the first item that activates the selection mode.
Please see this short demonstration video:
https://github.com/jordond/drag-select-compose/assets/9299303/2fd05370-604d-48d1-a032-9284641ac975
This is the part where I included the library in my code:
    BoxWithConstraints {

        val dragSelectState = rememberDragSelectState<Photo>()

        val tileSizePt: Dp = remember(maxWidth, tileSize) {
            calcTileSizePt(maxWidth, tileSize, state.screenWidth, state.screenHeight)
        }

        val cells: GridCells = remember(tileSize) {
            calcCells(tileSize, state.screenWidth, state.screenHeight)
        }

        val items = state.photosToDisplay

        LaunchedEffect(dragSelectState.inSelectionMode) {

            if (dragSelectState.inSelectionMode != state.photoSelectionMode)
                store.dispatch(AppAction.TogglePhotoSelectionMode)
        }

        LaunchedEffect(state.photoSelectionMode) {

            if (!state.photoSelectionMode)
                dragSelectState.clear()
        }

        LazyDragSelectVerticalGrid(
            columns = cells,
            items = items,
            state = dragSelectState,
        ) {

            items(key = { it.id!! }) { photo ->

                SelectableItem(
                    item = photo
                ) {

                    GalleryPhotoView(
                        // [... snip ... ]
                    )
                }
            }
        }

        VerticalScrollbar(
            modifier = remember { fillWholeMaxHeightModifier.align(Alignment.CenterEnd) },
            theme = state.theme,
            color = getTextColor(state.theme),
            scrollState = dragSelectState.gridState
        )

        // [... Overlays and other stuff ... ]
    }

Photo is a data class and also has an unique id.
I tried without key = { it.id!! } with no difference.

Very interesting! Thanks for the report, I'll look into it asap

I wasn't able to reproduce this. Are you able to provide a repro?

The wrong behavior occurs in closed-source code, unfortunately.
I need to check if I can reproduce it in your demo.

Looks like it must be something in my code. The demo does not have the problem.


refactor: use hubdevices endpoint from core SDK

refactor to use hubdevices endpoints from core SDK
updated unit tests
added unit test for edge:channels:enrollments command
moved chooseInstalledDriver from uninstall command to drivers-util.ts

Types of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] I have read the CONTRIBUTING document
[x] My code follows the code style of this project (npm run lint produces no warnings/errors)
[ ] Any required documentation has been added
[x] I have added tests to cover my changes

:tada: This PR is included in version 1.15.0 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


[Android] - Tapping TextInput unfocuses it

Steps to reproduce
This happens on my Pixel C emulator but not my Pixel 6 emulator.

Have the TextInput displayed on the screen with nothing focused for at least 8 to 10 seconds.
Tap the TextInput.

Expected results
TextInput focuses and remains focused.
Actual results
TextInput may briefly focus, soft keyboard opens, TextInput however does not remain focused. You can repeat the process as many times as you like, and it still happens.
Chuck a breakpoint on FocusNode.unfocus to see the stack trace. "TextInputClient.onConnectionClosed" is passed to Future<dynamic> _handleTextInputInvocation(MethodCall methodCall) in TextInput class from a platform channel.
Code sample
Code sample

import 'package:flutter/material.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        appBar: AppBar(
          title: const Text('Text Input Example'),
        ),
        body: const Center(
          child: Padding(
            padding: EdgeInsets.all(8.0),
            child: TextField(
              decoration: InputDecoration(
                border: OutlineInputBorder(),
                labelText: 'Enter something',
              ),
            ),
          ),
        ),
      ),
    );
  }
}

Screenshots or Video

Screenshots / Video demonstration
Here I wait for 8 or so seconds, then tap the TextInput, the soft keyboard opens for a few seconds while the TextInput remains unfocused, then I tap the TextInput a second time and it finally focuses.
textinputbug2.webm

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
[✓] Flutter (Channel stable, 3.16.8, on macOS 14.2.1 23C71 darwin-arm64, locale en-GB)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 15.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.3)
[✓] IntelliJ IDEA Community Edition (version 2023.2.2)
[✓] VS Code (version 1.86.1)
[✓] Connected device (7 available)
[✓] Network resources

• No issues found!

Hello @BenjiFarquhar.
Thanks for filing this.
I can't seem to reproduce this on my end both on an emulator device (Pixel 3a) and on a real Android device.

the soft keyboard opens for a few seconds

From the video shared, I can't see this behaviour, could this be an issue with where in the TextField onTap was received?
Also, can you try this on a real Android device to see if this reproduces there as well?

Hi there, @dam-ease. Thanks for taking a look.

From the video shared, I can't see this behaviour

My video shows me waiting, then near the end, I tap the TextInput, and the soft keyboard goes up for a few seconds, but the TextInput remains unfocused; then I tap the TextInput a second time, and the TextInput focuses.
Can you wait 30 seconds with nothing focused, then tap the TextInput on your Pixel C emulator?

could this be an issue with where in the TextField onTap was received?

I don't understand what you mean.

@dam-ease No, in mine, the field becomes unfocused as soon as you tap it, but the keyboard opens. So, keyboard with no focus.
Yours was the opposite; the field is focused without a keyboard opening. So, focus with no keyboard.

Thanks for checking this out.
I have tried producing this severally on my device but can only reproduce as above.
Can you help with the full device information you are testing with?

Cheers. This might be an emulator issue, so it should be closed. I have just started using a different emulator to work around it. But here are the specs if you want to reproduce the issue on this emulator.

Thanks for sharing these.
Looking through, this is quite similar to the device I ran my tests on as well but with different API levels, my device is a Pixel C API 34.
This might be specific to this emulator, I'll label this for more insights per what you shared in original comment:

Chuck a breakpoint on FocusNode.unfocus to see the stack trace. "TextInputClient.onConnectionClosed" is passed to Future _handleTextInputInvocation(MethodCall methodCall) in TextInput class from a platform channel.

You could also share any logs that pop on your end to provide more helpful insights into the issue.

CC @LongCatIsLooong from triage.


feat(trie): Palindrome Pairs

Coverage remained the same at 100.0% when pulling bd8d0b31379735e696cabe11b6cabee430359d28 on palindrome-pairs into cb5605a11694307a4b0230cab32ad179c82d42ba on master.


corrected burn asset example

Thanks for this! This is my fault for not adding instructions on how to make docs changes, but can you edit the source markdown file directly so the change doesn't get overwritten next time I generate the docs.
If you want to only modify the markdown that's fine and I'll merge that and run the docs generation myself, or you can also run the deploy.sh script in docs-src and push the generated docs in the PR as well.

@metasal1


New previous & next buttons on GridFieldDetailForms inconsistently work

Affected Version
>= 4.4.x
Description
Previous & next arrow buttons on GridField detail forms are inconsistent.
Steps to Reproduce

Install the userforms module
Create a form with a field
Use the form on the page to create a few submissions
Browse those submissions with the CMS
Observe that despite there being submissions - the previous and next buttons are constantly disabled

Notes
I've had a little look at this. Not really sure what's causing it but by forcing GridField to run through all GridField_DataManipulator components before calling GridFieldDetailForm_ItemRequest::getAdjacentRecordID it seems to correctly get pagination state - the crux of this issue.
The problem then, however, is that setting the state from the request (in that same method) sometimes clears out the valid state with empty state. Wrapping it in an if(!empty) condition works but I'm not hugely familiar with this implementation.

I set impact/high because it's weird choosing a record in a list and having disabled navigation buttons.

Closing as associated PR was merged.


Syn additions

Used the synthesis flow recently which resulted in me adding these additions.
The flow is actually broken out of the box currently, there's some RTL issues to investigate which I haven't had time to do but could be quickly hacked around for getting the flow going.

Fixing the issues so the flow does work out of the box is something I'll hopefully look at soon, along with getting some kind of yosys CI integration to avoid it breaking without us realising in the future.


Paid until - how to check date during logging

In the tutorial, I saw a model with a paid_until = models.DateField() column.
I would like to use this in my application.
Below are my models for the client and domain:
class Client(TenantMixin):
    name = models.CharField(_('Name of client'), max_length=50, unique=True)
    on_trial = models.BooleanField(default=True)
    paid_until = models.DateTimeField(auto_now_add=True)
    created = models.DateTimeField(auto_now_add=True)
    updated = models.DateTimeField(auto_now=True)

    auto_create_schema = True

    def __str__(self):
        return self.name

    def get_name(self):
        return self.name

class Domain(DomainMixin):
    pass

Could I get a little hint on how to go about it for example in the form when logging in? In order for the user to get a notification that his account will soon be blocked or it is already is.
class LoginForm(AuthenticationForm):
    email = forms.CharField(label='Email', max_length=50, widget=forms.TextInput(attrs={'class': 'form-control',
                                                                                'placeholder': 'Email',
                                                                                'type': 'text', 'id': 'email'}))
    password = forms.CharField(label='Password', max_length=50, widget=forms.TextInput(attrs={'class': 'form-control',
                                                                                'placeholder': 'Password',
                                                                                'type': 'password',
                                                                                'id': 'password'}))
    field_order = ['email', 'password']

    def __init__(self, *args, **kwargs):
        super(LoginForm, self).__init__(*args, **kwargs)

I tried to do something with connection.tenant (this is FakeTenant type) - I tried to get the name and forward it to the client - without success.

We use middleware for this purpose, see:
https://github.com/kiwitcms/tenants/blob/master/tcms_tenants/middleware.py

Thanks a lot Alexander, I will check this solution in my project :) :+1:


Implement blocking support for eventfd and socketpair

Our socketpair and eventfd implementations currently do not support blocking.
To fix that will require a bit of re-structuring to enable FileDescription::{read,write} to block. In that case we can't use the convenient bytes: &mut [u8]/bytes: &[u8] arguments, we need the underlying Miri place, so that we can store it in a callback to be used on unblocking. (Incidentally that would also simplify eventfd read/write a bit since we could use the normal memory APIs to reading/writing u64 in an endianess-aware way, rather than having to implement that on a byte slice.) The functions also need access to the return place so they can write the return value later, when they are unblocked.
Basically, a bunch of the convenience that is currently implemented here can't be used when blocking is involved. We have to make read/write lower-level functions that look more like the usual Miri hooks, and possibly add some helper functions to make it still easy to implement the current behavior. (Those helper functions are then likely useful with other file system functions as well.)

Alternatively we could implement it similar to sleep, but instead of waking on the next instruction, just reexecute the current one.
That does mean we cannot mutate any state before blocking or we'd get incorrect behavior

sleep uses the same blocking machinery as everything else. We don't currently use the "re-execute instruction" approach for anything and TBH I think that is a bit too hacky for my taste. For instance if an intrinsic argument is *ptr then we don't want to re-load it from memory each time... though I guess if the value would change that would be a data race so it doesn't actually make a difference?

May I work on this issue? Or it belongs to a larger project?

I think my work on #3448 might potentially block this. The current specification for epoll is only for non-blocking eventfd and socketpair. I wish to let that land then incorporate blocking mechanism to it.

I see. Thanks for letting me know. I'll look for something else then.

FWIW we could have blocking socketpair without that being supported by epoll.
But also we currently don't have enough review capacity for another large projects like this. I can't even keep up with the PRs we already have. So picking something smaller is probably better.

I'd like to work on this.
@rustbot claim

A good preparation for this would be to change FileDescription::read/write to take a dest: &MPlace<'tcx> rather than returning an io::Result. That's the most conflict-heavy part and can be done in a separate PR.


Added impress:stepgoto event to api

Needed an event to be triggered when going to step (with the target) and prior to the entering it.

Hi @dbankier, in an effort to clear up older issues/PRs we are pinging back to know if you are still tracking this request.
To give a little bit of context, recently a decision was made in the project to make the development more active and the first task is to clear up older issues like this one to see if the OP is still interested in keep it going.

This PR is long forgotten to me (3.5 years old). I have forgotten the context and need of this PR and have not used impress for a long time. Feel free to merge it if you see any value. As project maintainer it is ultimately your decision.

@dbankier Thanks for the response!
Since you are not tracking this PR anymore and you lost context, I have created an issue to track this request instead: #513
This PR will be closed but we might cherry-pick the commit later if we see the need. Thank you!


Unable to subscribe to any data sets on marketplace

Unable to subscribe to any of the data sets listed in the documentation (link)
Entering this command into terminal:
$ catalyst marketplace subscribe --dataset=Marketcap
Getting this response:
Using 0xmyaddress for this transaction.
The requested "marketcap" dataset is not registered in the Data Marketplace.

Environment:

Operating System: Ubuntu 16.04
Python Version: 3.5.2
Python Bitness: 64
How did you install Catalyst: pip

Hi @tingwai-to the datasets will become available when we launch the data-marketplace on mainnet, after the smart contract has been audited by a third party. Even if the datasets were available right now, you wouldn't be able to subscribe to them because you would need test-ENG (analogous to test-ether), and that's not available either to the general public.

I see, happy to hear that the marketplace is being actively tested. Are there other features of the marketplace that the general public can try out right now?
If I may, I would also suggest updating the marketplace datasets documentation to reflect that datasets are not currently available for general public/while on testnet.

Thank you for the suggestion. I have edited the documentation accordingly.
Answering your question, you get a preview of how the data marketplace will work, and if you would consider offering some of your datasets to the marketplace you have the specs to get it ready in advance of the release on mainnet.

Much appreciated. Closing issue


Remove FIRAppAssociationRegistration class.

This is no longer used in any Firebase SDK. I'm not sure when the last usage was removed, so it's safest to wait until the next breaking change to do so.
https://github.com/firebase/firebase-ios-sdk/blob/78b9b7fb10fa10d8605c865eb660b921afe0a27c/FirebaseCore/Sources/FIRAppAssociationRegistration.h#L27

Merged into v9 branch


kernels visible to conda but not to jupyter

OS: debian 9
Clean install on Google Cloud Platform running python notebook
Ran these commands:
conda create -n fastai
conda activate fastai
Created ~jupyter/.jupyter/jupyter_config.json with this content:
$ cat ~jupyter/.jupyter/jupyter_config.json
{
"kernel_spec_class": {
"kernelspec_path": ""
}
}
$ python -m nb_conda_kernels list
[ListKernelSpecs] [nb_conda_kernels] enabled, 3 kernels found
Available kernels:
conda-env-fastai-py    /opt/conda/envs/fastai/share/jupyter/kernels/python3
conda-env-py27-py      /opt/conda/envs/py27/share/jupyter/kernels/python2
python2                /opt/conda/share/jupyter/kernels/python2
conda-root-py          /opt/conda/share/jupyter/kernels/python2
python3                /opt/conda/share/jupyter/kernels/python3
$ jupyter kernelspec list
Available kernels:
python2    /opt/conda/share/jupyter/kernels/python2
python3    /opt/conda/share/jupyter/kernels/python3
Attempted to shutdown and start instance. Same results.
This is preventing me from seeing available kernels and choosing appropriate kernel after launching a notebook.
Appreciate any pointers on troubleshooting. Thank you!

Can you share the output of python -m nb_conda_kernels.install --status --verbose?
And why did you create that jupyter_config.json file manually?

Same issue here! And here is the verbose from your code.
Entry points:

conda = nb_conda_kernels.discovery:CondaKernelProvider
NOTE: entry points not used in Jupyter 6.1.6
jupyter_config.json entries:
/etc/jupyter:
/usr/local/etc/jupyter:

/home/young/anaconda3/etc/jupyter: {
"JupyterApp": {
"kernel_spec_manager_class": "nb_conda_kernels.CondaKernelSpecManager"
}
}

/home/young/.jupyter:

@gkovaig
If you want to install the kernel to make them available for other tools than notebook and jupyterlab. You indeed need to set a configuration file, jupyter_config.json that should contain:
{
  "CondaKernelSpecManager": {
    "kernelspec_path": "--user"
  }
}

Two main differences with what you reported:

The main entry should be the class name: CondaKernelSpecManager
The value for the path: --user => avoid "" as usually users do not have write permission on system /etc folder.

If you are really in a multi-user case, make sure the shared jupyter kernel directory is writable by your users.

@ahnchive have a look at the documentation: https://github.com/Anaconda-Platform/nb_conda_kernels#use-with-nbconvert-voila-papermill

I have the same issue as the OP.
Just installed     nb_conda_kernels-2.2.4     |   py37hc8dfbb8_0          23 KB  conda-forge into my py37 environment where I start a jupyter lab with this config:
c.NotebookApp.allow_remote_access = False
c.NotebookApp.open_browser = False
c.NotebookApp.password_required = True
c.NotebookApp.port = 9999
c.NotebookApp.port_retries = 0
c.NotebookApp.quit_button = False

I also have:
$ cat /opt/miniconda3/envs/py37/etc/jupyter/jupyter_notebook_config.json
{
  "NotebookApp": {
    "kernel_spec_manager_class": "nb_conda_kernels.CondaKernelSpecManager"
  }
}

Symptoms identical to the OP:
$ python -m nb_conda_kernels list
[ListKernelSpecs] [nb_conda_kernels] enabled, 2 kernels found
Available kernels:
  conda-env-dev-py     /opt/miniconda3/envs/dev/share/jupyter/kernels/python3
  python3              /opt/miniconda3/envs/py37/share/jupyter/kernels/python3
  conda-env-py37-py    /opt/miniconda3/envs/py37/share/jupyter/kernels/python3

$ which python
/opt/miniconda3/envs/py37/bin/python

$ jupyter kernelspec list
Available kernels:
  python3    /opt/miniconda3/envs/py37/share/jupyter/kernels/python3

$ which jupyter
/opt/miniconda3/envs/py37/bin/jupyter

Add stated in the readme, this extension builds kernel specs dynamically. So by default jupyter kernelspec list will not see your conda environments. But the environments will be available in notebook and JupyterLab. As the first post is not clear on its usage, please describe precisely what you would like to achieve. And what is wrong with screenshots (pictures are worth thousands of words).

But the environments will be available in notebook and JupyterLab.

My issue is that this is not happening. Based on the README, "This extension enables a Jupyter Notebook or JupyterLab application in one conda environment to access kernels for Python, R, and other languages found in other environments." This is what I am trying to accomplish.
The problem with a screenshot in this case is that it's difficult to take a screenshot of something that's not there.

The problem with a screenshot in this case is that it's difficult to take a screenshot of something that's not there.

This is actually good because now I have no doubt about your use case ;)
So it definitely looks like the kernel spec manager as not been loaded in JupyterLab. Could you run jupyter lab --debug? No need to open JupyterLab itself, it should report something like that:
jupyter lab --debug
[D 15:36:26.787 LabApp] Searching ['/home/fcollonval/.jupyter', '/home/fcollonval/miniconda3/envs/jconda/etc/jupyter', '/usr/local/etc/jupyter', '/etc/jupyter'] for config files
[D 15:36:26.788 LabApp] Looking for jupyter_config in /etc/jupyter
[D 15:36:26.788 LabApp] Looking for jupyter_config in /usr/local/etc/jupyter
[D 15:36:26.788 LabApp] Looking for jupyter_config in /home/fcollonval/miniconda3/envs/jconda/etc/jupyter
[D 15:36:26.789 LabApp] Looking for jupyter_notebook_config in /etc/jupyter
[D 15:36:26.789 LabApp] Looking for jupyter_notebook_config in /usr/local/etc/jupyter
[D 15:36:26.789 LabApp] Looking for jupyter_notebook_config in /home/fcollonval/miniconda3/envs/jconda/etc/jupyter
[D 15:36:26.789 LabApp] Loaded config file: /home/fcollonval/miniconda3/envs/jconda/etc/jupyter/jupyter_notebook_config.json
[D 15:36:26.789 LabApp] Looking for jupyter_notebook_config in /home/fcollonval/.jupyter
[D 15:36:26.790 LabApp] Loaded config file: /home/fcollonval/.jupyter/jupyter_notebook_config.json
[D 15:36:26.794 LabApp] [nb_conda_kernels] refreshing conda info
[I 15:36:27.095 LabApp] [nb_conda_kernels] enabled, 5 kernels found

There are two things that you should see:

The configuration files being loaded; check that it is loading the one in /opt/miniconda3/envs/py37/etc/jupyter in your case.
Log messages from nb_conda_kernels

If you do not see the first one, run jupyter --paths and create a jupyter_notebook_config.json in one of the config folders that contains:
{
  "NotebookApp": {
    "kernel_spec_manager_class": "nb_conda_kernels.CondaKernelSpecManager"
  }
}

Could you also report the content of your py37 environment: conda list -n py37?

I have a similar issue when trying to execute a particular kernel using papermill.
Some outputs from my side:
$ python -m nb_conda_kernels.install -v --enable
Enabling nb_conda_kernels...
Entry points:
  - conda = nb_conda_kernels.discovery:CondaKernelProvider
  NOTE: entry points not used in Jupyter 6.1.6
jupyter_notebook_config.json entries:
  - /etc/jupyter: <no file>
  - /usr/local/etc/jupyter: <no file>
  * /Users/thvasilo/opt/anaconda3/etc/jupyter: {
      "NotebookApp": {
        "kernel_spec_manager_class": "nb_conda_kernels.CondaKernelSpecManager"
      }
    }
  - /Users/thvasilo/.jupyter: <no file>
Status: enabled

$ which jupyter
/Users/thvasilo/opt/anaconda3/bin/jupyter

$ jupyter --config-dir
/Users/thvasilo/.jupyter

$ cat ~/.jupyter/jupyter_config.json
{
  "CondaKernelSpecManager": {
    "kernelspec_path": "--user"
  }
}

$ jupyter --version
jupyter core     : 4.6.3
jupyter-notebook : 6.1.1
qtconsole        : 4.7.5
ipython          : 7.16.1
ipykernel        : 5.3.4
jupyter client   : 6.1.6
jupyter lab      : 2.1.5
nbconvert        : 5.6.1
ipywidgets       : 7.5.1
nbformat         : 5.0.7
traitlets        : 4.3.3

$ jupyter kernelspec list
Available kernels:
  pycharm-46453bda    /Users/thvasilo/Library/Jupyter/kernels/pycharm-46453bda
  python3             /Users/thvasilo/opt/anaconda3/share/jupyter/kernels/python3

$ python -m nb_conda_kernels list
[ListKernelSpecs] WARNING | Config option `kernelspec_path` not recognized by `CondaKernelSpecManager`.  Did you mean `kernel_spec_class`?
[ListKernelSpecs] [nb_conda_kernels] enabled, 6 kernels found # Some kernels removed for confidentiallity
Available kernels:
  conda-env-base-np-py                                   /users/thvasilo/opt/anaconda3/envs/base-np/share/jupyter/kernels/python3
  conda-env-tables-py                                    /users/thvasilo/opt/anaconda3/envs/tables/share/jupyter/kernels/python3
  conda-root-py                                          /users/thvasilo/opt/anaconda3/share/jupyter/kernels/python3
  pycharm-46453bda                                       /Users/thvasilo/Library/Jupyter/kernels/pycharm-46453bda
  python3                                                /Users/thvasilo/opt/anaconda3/share/jupyter/kernels/python3

Although the kernels don't appear when using jupyter kernelspec list they do appear when running Jupyter notebook:

But when I try to use the kernel using papermill it doesn't work:
 papermill tabulate_test.ipynb output.ipynb -k tables
Input Notebook:  tabulate_test.ipynb
Output Notebook: output.ipynb
Executing:   0%|                                                                                | 0/4 [00:00<?, ?cell/s]
Traceback (most recent call last):
  File "/Users/thvasilo/opt/anaconda3/bin/papermill", line 11, in <module>
    sys.exit(papermill())
  File "/Users/thvasilo/opt/anaconda3/lib/python3.7/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/Users/thvasilo/opt/anaconda3/lib/python3.7/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/Users/thvasilo/opt/anaconda3/lib/python3.7/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/Users/thvasilo/opt/anaconda3/lib/python3.7/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/Users/thvasilo/opt/anaconda3/lib/python3.7/site-packages/papermill/cli.py", line 238, in papermill
    execution_timeout=execution_timeout,
  File "/Users/thvasilo/opt/anaconda3/lib/python3.7/site-packages/papermill/execute.py", line 106, in execute_notebook
    **engine_kwargs
  File "/Users/thvasilo/opt/anaconda3/lib/python3.7/site-packages/papermill/engines.py", line 49, in execute_notebook_with_engine
    return self.get_engine(engine_name).execute_notebook(nb, kernel_name, **kwargs)
  File "/Users/thvasilo/opt/anaconda3/lib/python3.7/site-packages/papermill/engines.py", line 343, in execute_notebook
    cls.execute_managed_notebook(nb_man, kernel_name, log_output=log_output, **kwargs)
  File "/Users/thvasilo/opt/anaconda3/lib/python3.7/site-packages/papermill/engines.py", line 402, in execute_managed_notebook
    return PapermillNotebookClient(nb_man, **final_kwargs).execute()
  File "/Users/thvasilo/opt/anaconda3/lib/python3.7/site-packages/papermill/clientwrap.py", line 43, in execute
    with self.setup_kernel(**kwargs):
  File "/Users/thvasilo/opt/anaconda3/lib/python3.7/contextlib.py", line 112, in __enter__
    return next(self.gen)
  File "/Users/thvasilo/opt/anaconda3/lib/python3.7/site-packages/nbclient/client.py", line 438, in setup_kernel
    self.start_new_kernel_client(**kwargs)
  File "/Users/thvasilo/opt/anaconda3/lib/python3.7/site-packages/nbclient/util.py", line 74, in wrapped
    return just_run(coro(*args, **kwargs))
  File "/Users/thvasilo/opt/anaconda3/lib/python3.7/site-packages/nbclient/util.py", line 53, in just_run
    return loop.run_until_complete(coro)
  File "/Users/thvasilo/opt/anaconda3/lib/python3.7/asyncio/base_events.py", line 579, in run_until_complete
    return future.result()
  File "/Users/thvasilo/opt/anaconda3/lib/python3.7/site-packages/nbclient/client.py", line 393, in async_start_new_kernel_client
    **kwargs))
  File "/Users/thvasilo/opt/anaconda3/lib/python3.7/site-packages/nbclient/util.py", line 85, in ensure_async
    result = await obj
  File "/Users/thvasilo/opt/anaconda3/lib/python3.7/site-packages/jupyter_client/manager.py", line 569, in start_kernel
    kernel_cmd, kw = self.pre_start_kernel(**kw)
  File "/Users/thvasilo/opt/anaconda3/lib/python3.7/site-packages/jupyter_client/manager.py", line 257, in pre_start_kernel
    kernel_cmd = self.format_kernel_cmd(extra_arguments=extra_arguments)
  File "/Users/thvasilo/opt/anaconda3/lib/python3.7/site-packages/jupyter_client/manager.py", line 181, in format_kernel_cmd
    cmd = self.kernel_spec.argv + extra_arguments
  File "/Users/thvasilo/opt/anaconda3/lib/python3.7/site-packages/jupyter_client/manager.py", line 87, in kernel_spec
    self._kernel_spec = self.kernel_spec_manager.get_kernel_spec(self.kernel_name)
  File "/Users/thvasilo/opt/anaconda3/lib/python3.7/site-packages/jupyter_client/kernelspec.py", line 235, in get_kernel_spec
    raise NoSuchKernel(kernel_name)
jupyter_client.kernelspec.NoSuchKernel: No such kernel named tables

Using tables or conda-env-tables-py doesn't make a difference.
Also note the warning [ListKernelSpecs] WARNING | Config option kernelspec_path not recognized by CondaKernelSpecManager.  Did you mean kernel_spec_class?

[ListKernelSpecs] WARNING | Config option kernelspec_path not recognized by CondaKernelSpecManager.  Did you mean kernel_spec_class?

@thvasilo The option kernelspec_path has been introduced in nb_conda_kernels 2.3.0. From the log above, it looks like you are using a older version. Could you update to the latest version and try again?

closing as stale; but feel free to open if necessary


[sitecore-jss-nextjs] Placeholder applies the modifyComponentProps prop.

[x] This PR follows the Contribution Guide
[x] Changelog updated

Description / Motivation

The Placeholder component in the "nextjs package" does not apply the modifyComponentProps when given. Instead, the component adds its own implementation of modifyComponentProps that it provides to the Placeholder component from the "react package". The component needs to also apply the modifyComponentProps property as well.
Testing Details

[ ] Unit Test Added
[x] Manual Test/Other (Please elaborate)

I tried to add a unit test but I lack knowledge of how Enzyme works. When I attempt to call mount on the Placeholder component it fails with the message Cannot read properties of null (reading 'useContext'). All other tests seem to have no problems though.
So far I tested this solution by modifying the module files inside the node_modules folder of my particular project.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

@Adamduehansen Thank you for submitting your contribution! I've added a ticket containing all the details, which has been added to our internal backlog for thorough review


How to add preBootstrapCommands in Karpenter NodePool/NodeClass definitions

We use eksctl to provision our EKS cluster and node groups. It provides support for preBootstrapCommands which actually runs even before bootstrap script (/etc/eks/bootstrap.sh) runs.
Is there any way to achieve the same functionality in Karpenter ?
I do not want to use custom AMIs.

If you are using the AMI families, you can specify spec.userData in your NodeClass which will prepend the userData that you specify with the default userData for that AMI family. Karpenter docs has some pretty good examples on this for the different AMI families: https://karpenter.sh/docs/concepts/nodeclasses/#specuserdata


Prevent reading nbt from mod blocks

I know that this mod is no longer supported but i hope to find a good man to solve a problem:
Im using steves factory manager and i have there 300+ commands (a lot of TagCompound). So if I look at it, Factory Manager block, it becomes a bit laggy. Is there a way to blacklist a mod or block? Waiting for any answer

There was a blacklist for blocks.
https://github.com/exzhawk/OmniOcular/blob/master/src/main/java/me/exz/omniocular/handler/TileEntityHandler.java#L24-L38
https://github.com/exzhawk/OmniOcular/blob/b5f2d5d8e1/src/main/java/me/exz/omniocular/reference/Reference.java#L9-L11

Wow thanks a lot! It took me some time to figure how to blacklist a right way.
My mistake: tryed to use nei block dump function to find a proper name in game, got:
StevesFactoryManager:BlockMachineManagerName,708,true,null,vswe.stevesfactory.blocks.BlockManager
but no combination of words did not help.
So the next step was to use nbtedit ingame to find name of this block and it was "TileEntityMachineManagerName" and it works!
Sad that there is no config file for this, but anyway: Closed. Thanks.