ImageCollection images no longer array when delete element other than last

Screenshots

Hi @MuGGYStyle ,
Thank you for your contribution.
We know this case and we are correcting it on Sylius directly using this patch :
https://github.com/sylius/sylius/pull/13666
Check https://github.com/cweagans/composer-patches package to see how to apply a patch in your project.
But it does not work since Sylius 1.11 and we haven't got another patch at this moment.
We had a discussion about this issue before on #174 and we have specific case when indexes are not integer as said @jacquesbh in https://github.com/monsieurbiz/SyliusRichEditorPlugin/pull/174#issuecomment-1054461706


feat: Reference lines for RKB, MSL and Seabed

https://app.zenhub.com/workspaces/wellx-5f89a0db386bba0014989b28/issues/gh/equinor/esv-intersection/163

This feature adds reference lines to the esv-intersection.
Based on this code, but modified to allow dynamically adding / changing the lines:
https://github.com/equinor/mad-project-rep/blob/dev/src/components/intersection/SeaAndRKBLayer.js

Do we use this new layer in wellx-designer? If not let's create a task for it


Smooth Cache Updates for Access Token Providers #59 issue

Use the Oracle JDBC Driver implementation of  caching  JWTs, instead of the standard CachedResourceFactory .This cache is designed for "smooth" updates when a token expires.  this cache uses a background thread to begin requesting a new token at one minute before the current token expires. If the request completes within 30 seconds (which is almost always the case), then threads will not become blocked. Unlike CachedResourceFactory will block the thread while it requests a new token.
This Pr contain also test to verify if that thread will be blocked or not , and verify how much it would take to request a token after it expires .
issue : #59
note : I aded  some  new dependencies for testing and jwt generating :Mockito,JJWT

Now we are relying on CachedResourceFactory<Supplier> to cache token  supplier per each parameter set instead of caching the token itself . so the request() method of AccessTokenFactory now returns Supplier , and the driver's cache will handle caching the tokens .
I added tests to make sure that this mechanism is thread safe also to verify the uniqueness of tokens per parameter set .

Awesome: Looks like the Supplier-as-a-resource design is working out.
mockito and the jwt lib need to go. I'll bet that with just a little bit of code, you can solve the same problems that you're using these libraries to solve. This would be preferable because a few lines of code is much easier to understand than the API and source code of these libraries.
I don't have much experience working with these libraries, and I don't know if other programmers on this project do either. When you introduce a new library into a code base, you are forcing everyone else who works on that code to also have learn how that library works. If the only benefit of the library is you not having to write a bit of code, then this doesn't feel like a good trade off :)
In any case, we need to replace mock-ups with integration tests. That is, we need tests that actually request tokens from Azure and OCI. Our test suite is already designed to do this, so you can look to existing tests for examples.
We really favor integration testing over mock-ups because at the end of the day, our users need this code to work correctly with cloud services. Mock classes won't provide that level of verification. I think you can hit all the cases you're wanting to test without needing to mock a token request.

Please add a documentation note in the "Access Token Provider" section of both OCI and Azure and explain how tokens are cached. You can provide a link to the javadoc:
https://docs.oracle.com/en//database/oracle/oracle-database/23/jajdb/oracle/jdbc/AccessToken.html#createJsonWebTokenCache(java.util.function.Supplier)

The latest commit reworks the solution a bit:

The existing AccessTokenFactory classes remain unchanged
A new AccessTokenCacheFactory delegates to the existing AccessTokenFactory implementations. This new factory resides in the common module because it is not specific to OCI or Azure. It interfaces with the ResourceFactory abstraction.
The existing tests were consolidated into a single test. The single test verifies the AccessTokenCacheFactory using a mock ResourceFactory
The existing tests were converted to JUnit 5.
Unused dependencies on JWT library and Mockito were removed from the pom.xml files


Migration of storage layer to delta-rs

This is the initial effort of switching our custom MVCC/Lakehouse protocol to use the Delta lake protocol instead.
A couple of general points:

This is still very very rough around the edges, the purpose of the PR is to get some feedback
Support for DELETE & UPDATE statements is missing, so the corresponding tests are disabled
Likewise some other minor stuff is still not implemented (VACUUM, system schema tables)
Other than that all else should work—besides the 8 ignored tests all other tests are passing (though a fair number of them exercise the legacy logic which isn't in use anymore)
No perf testing has been done yet (the object upload code is likely sub-optimal)
cleanup of legacy code hasn't been done yet: I only replaced the stuff that was in the way of getting things working with delta-rs, in theory the entire writing logic for Seafowl tables can be erased now. The reading logic for Seafowl tables should still remain (plan to add a test for that too), as the plan is to have this available throughout the transient Seafowl versions for easier data migration.

As for the implementation details:

I've opted for keeping a single root object store around (the inner in internal_object_store), and then "scoping" it for each DeltaTable accordingly. This means wrapping it up with some other object stores so that / points to the table root uri (see below). The other alternative that delta-rs offers is providing the store_options, out of which it will then build the store for a given uri, but I didn't like this mostly because the memory store implementation then doesn't work (it get's re-created from scratch for each create/write/table builder instantiation).
I've opted for a <inner_store_root>/<db_name>/<schema_name>/<table_name>/ as the the table root uri (place where delta-rs puts all the table-related stuff as per the protocol). For instance s3://my_bucket/my_db/my_schema/my_table/ or file:///data/dir/my_db/my_schema/my_table/
While this is nice and intuitive it does have some downsides. A big one is that deleting a schema means deleting all objects with a <db_name>/<schema_name> prefix (and similarly for dropping a table or renaming a table) which is asking for trouble (let alone dropping a DB, which we don't support yet). And we can't do a lazy deletion there, since we have to enable subsequent schema/table re-creation which will fail if delta-rs detects something exists there already (not sure if this will change).
The other side of the tradeoff is to gain some flexibility/performance and store tables in <inner_store_root>/<table id uuid5 hash or something of that nature>/ (where the id comes from our own catalog). That means that deleting a schema/ table or renaming a table need not be performance critical, but can instead be done lazily (e.g. during VACUUM in chunked batches) because table uri is unique to a given table and independent of db/schema/table name. This does mean that the store is less transparent (slightly harder to use other tooling from delta lake ecosystem?), and that we need to keep the table table in our own catalog (though that could still be beneficial for the purpose of satisfying information schema queries). Nonetheless, I think this could be a better approach overall.

How do information schema queries work under this proposed model? It looks like we use the catalog DB to satisfy them instead of crawling the object store for all tables and their schemas?

Yes, that is correct, we pre-load the schema information from our catalog.


Test suite takes a lot longer when I am not looking

Yeah I know how this sounds, but I tried it two times and it seems reproducible.^^ I am running the Miri test suite in rustc, ./x.py test miri. I then quickly switch to a different tab in my terminal emulator to do something else while the tests are running. And then somehow the first round of Miri tests takes 205.899s. But when I stay in the same tab it's only 29.842s.
The same seems to happen when I just switch from the terminal emulator to a different application.
My terminal emulator is the Gnome Terminal Version 3.51.90.
This may have something to do with ui_test's fancy output mode? Cc @oli-obk

How does this fancy output stuff work... is there some kind of callback to "draw next frame"? Maybe that callback simply does not get called when the terminal is in the background?

It's eagerly pushed information, but it sounds similar to a situation I have had before with just plain libtest tests. Doing output (like writing a single new . char), will block if the buffer is full (so if the terminal hasn't read yet).

True, I just had this with a ./miri check as well there a lot of output was produced and the build didn't finish until I started looking at the terminal again.
This is probably a bug in the terminal emulator then.


Fix UI CI and update QASE/Documentation

The UI CI is not all green so I would like to check everything once my PR about Prime is merged.
The documentation in Confluence should be updated and QASE with Prime tests.

All good, CI was fully green yesterday and we do not have to update anything in QASE regarding Prime.


Fixed challenge typo

Fixes a typo in JavaScript challenge Stand in line that asks for a different array name. (Asks for 'myArr' which should be 'testArr')
Tested locally and npm test passes all tests.
Closes #7614
On a side note, I am not sure why the Travis-CI tests aren't starting on here. Is that a problem or just not required?

@drk7891 You change looks good to me. But just in case I am blocking this for @BerkeleyTrue to check why the Travis-CI has failed.
I am not aware of any recent changes that might do this.

:+1:
Looks like the Travis thing cleared itself up?


Update dysonairpurifier to 3.2.4

Please update my adapter ioBroker.dysonairpurifier to version 3.2.4.
This pull request was created by https://www.iobroker.dev c0726ff.

@Grizzelbee
Are you sure this release is working?
Github tests are failing:
2024-10-01T12:00:49.039Z testing:unit:adapterTools   => found main.js
node:internal/modules/cjs/loader:1143
  throw err;
  ^
Error: Cannot find module './dyson-utils.js'

@Grizzelbee
PLEASE CONFIRM THAT RELEASE TO STABLE IS OK.

You're right.
Updates would have worked - but new installations were broken.
Just released 3.2.5 with working tests.
I'll do a new PR soon for this version.

thanjs for feedback


Add CLI switches for debug mode

When a cop raises an exception, RuboCop will swallow it and tell you to use debug mode if you want to see the backtrace.
I needed to add this in order to be able to debug the problems which lead to PR #5.

Thanks! There were some parts that failed in RuboCop, so I merged your commits on main branch while fixing them on my end.


build: improve github workflow to check if go mod needs updating

Is your feature request related to a problem? Please describe.
Our github workflow should check for if the go mod needs updating when we create pull requests.
Describe the solution you'd like
We should have a go mod tidy step in the github workflow. This can be something similar to:
https://github.com/dapr/dapr/blob/120247a632262d82e5a02726a7fdb70d46df8fe1/.github/workflows/dapr.yml#L91
Additional context
Creating this as a follow up to this PR: https://github.com/dapr/go-sdk/pull/448 and originating issue: https://github.com/dapr/go-sdk/issues/447

/assign

Closed via #458


Outdated documentation for DataFormatVecPermute

This came up while creating a TF-TRT converter for DataFormatVecPermute in #52942
cc @bixia1
URL(s) with the issue:

Python: https://www.tensorflow.org/api_docs/python/tf/raw_ops/DataFormatVecPermute
C++: https://www.tensorflow.org/api_docs/cc/class/tensorflow/ops/data-format-vec-permute
Java: https://www.tensorflow.org/jvm/api_docs/java/org/tensorflow/op/nn/DataFormatVecPermute

Description of the issue (what needs changing):

Examples imply that an input of shape (2, 4) is valid, but that should be (4, 2).
The format strings can be of size 4 or 5 (e.g "NHWC", "NDHWC").
The first dimension of the input shape vector can be src_format.size() or src_format.size() - 2, in which case it is assumed that non-spatial dimensions are omitted.

As an example, here is a valid Python code that is not covered by the documentation:
import tensorflow as tf
a = tf.constant([1, 2, 3, 4, 5])
print(tf.raw_ops.DataFormatVecPermute(x=a, src_format="NDHWC", dst_format="NCDHW"))

Output:
tf.Tensor([1 5 2 3 4], shape=(5,), dtype=int32)

Submit a pull request?
I'm planning to submit a PR.

Hi @Nyrio ! This issue will be closed once the PR #53158  is merged. Thanks!

Hi @Nyrio ! Is this issue good to close now ? As the above PR seems to be merged now . Thanks!

@mohantym No, that's a different PR. #53158 is the one that closes this issue.

Ok @Nyrio! Thanks for the confirmation!


chore: release master

:robot: I have created a release beep boop
@allaround/all-components: 1.1.2
Dependencies

The following workspace dependencies were updated

dependencies

@allaround/button bumped from ^1.0.0 to ^1.0.1
@allaround/input bumped from ^1.0.0 to ^1.0.1

button: 1.0.1
1.0.1 (2023-06-03)
Bug Fixes

package entry index (b00c320)

input: 1.0.1
1.0.1 (2023-06-03)
Bug Fixes

package entry index (b00c320)

allaround-components: 1.2.3
1.2.3 (2023-06-03)
Bug Fixes

package entry index (b00c320)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/allaround-components-v1.2.3 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/all-components-v1.1.2 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/button-v1.0.1 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/input-v1.0.1 :sunflower:


Remote ref fix

Fixes #19.
Not absolutely sure about test cases still. Jesse test system is not so easy.

Looked like a pretty safe fix, so I have merged this. Thanks! and sorry for the delay.
Are you waiting for this to make it into a release (git tag)?

I use my own fork now, but will switch if new tag will be added.
19 Июн 2016 г. 2:07 AM пользователь "Andrei Neculau" <
<EMAIL_ADDRESS>написал:

Looked like a pretty safe fix, so I have merged this. Thanks! and sorry
for the delay.
Are you waiting for this to make it into a release (git tag)?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/for-GET/jesse/pull/20#issuecomment-226969875, or mute
the thread
https://github.com/notifications/unsubscribe/AAZwfsl6wubmU8sPDmkIvxrLQxeVdw8uks5qNHopgaJpZM4Ir0Vk
.


Make Playwright a first-class citizen of MSTest SDK

Summary
Make it easy to enable Playwright when using MSTest SDK.
Background and Motivation
Currently MSTest SDK doesn't support Playwright so users will have to manually install the Microsoft.Playwright.MSTest package.
Proposed Feature
We could improve this experience by adding a new property (e.g. EnablePlaywright) that would add the package.
AB#2020957

It was already done.


Add support for custom crash and log collection URL (to use own proxies)

Summary
When using Android or iOS native agents you can add a custom crash and log collection url. See here:
https://docs.newrelic.com/docs/mobile-monitoring/new-relic-mobile-android/android-sdk-api/android-agent-configuration-feature-flags/#logging
e.g.
NewRelic.withApplicationToken("YOUR_APP_TOKEN")
.usingCollectorAddress("harvest-upload-delegate.domain.com")<------
.start(this.getApplication());

This functionality is missing in this Plugin.
Desired Behavior
A method overload which takes the collector and crash collector endpoint in addition to the appkey when init the new relic capacitor plugin
If this gets implemented and you update the documentation, one small thing:

In the readme it mentions to put the init code into the index.tsx, I think thats react. Would be nice to get an example for Angular aswell

Thanks for this plugin!

Just noticed it's already added here but not yet released:
https://github.com/newrelic/newrelic-capacitor-plugin/pull/16

Hello, appreciate the feedback. You should be able to put the init code within main.ts of your angular app and I'll update the README for that. We hope to push out a new release sometime soon, so I'll notify you via this thread when we do.

Hello @johnfriedrich, we have released v1.1.0 that will have agent configuration options for collector endpoints. You can find the release here<EMAIL_ADDRESS>


Binder build fails for version 1.5.2

https://mybinder.org/v2/gh/elyra-ai/elyra/v1.5.2?urlpath=lab/tree/binder-demo
Waiting for build to start...
Picked Git content provider.
Cloning into '/tmp/repo2dockerz9horcih'...
 Memory limitedwithout swap.
 ---> Running in 26a564c194f4
Removing intermediate container 26a564c194f4
 ---><PHONE_NUMBER>51
Step 40/47 : LABEL repo2docker.repo="https://github.com/elyra-ai/elyra"
 ---> [Warning] Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limitedwithout swap.
 ---> Running in 64d6c3277e2f
Removing intermediate container 64d6c3277e2f
 ---> cea86af18706
Step 41/47 : LABEL repo2docker.version="0.11.0+195.g2f1914d"
 ---> [Warning] Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limitedwithout swap.
 ---> Running in 1ca630f7bb5e
Removing intermediate container 1ca630f7bb5e
 ---> 404a8e6b0965
Step 42/47 : USER ${NB_USER}
 ---> [Warning] Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limitedwithout swap.
 ---> Running in fe8614842839
Removing intermediate container fe8614842839
 ---><PHONE_NUMBER>f4
Step 43/47 : RUN chmod +x binder/postBuild
 ---> [Warning] Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limitedwithout swap.
 ---> Running in 05c9aa5bcbe5
Removing intermediate container 05c9aa5bcbe5
 ---> 9007bcbf5249
Step 44/47 : RUN ./binder/postBuild
 ---> [Warning] Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limitedwithout swap.
 ---> Running in 21e9ecef2f5e
--2021-01-08 19:51:59--  https://github.com/yarnpkg/yarn/releases/download/v1.22.4/yarn-v1.22.4.tar.gz
Resolving github.com (github.com)... <IP_ADDRESS>
Connecting to github.com (github.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://github-production-release-asset-2e65be.s3.amazonaws.com/49970642/487f6380-61e3-11ea-8294-0d743f488ef6?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20210108%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20210108T195014Z&X-Amz-Expires=300&X-Amz-Signature=182801d3be3f1e43e981f55aee737a0c9902a8b60484ffd7b269bc21b58e3895&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=49970642&response-content-disposition=attachment%3B%20filename%3Dyarn-v1.22.4.tar.gz&response-content-type=application%2Foctet-stream [following]
--2021-01-08 19:51:59--  https://github-production-release-asset-2e65be.s3.amazonaws.com/49970642/487f6380-61e3-11ea-8294-0d743f488ef6?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20210108%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20210108T195014Z&X-Amz-Expires=300&X-Amz-Signature=182801d3be3f1e43e981f55aee737a0c9902a8b60484ffd7b269bc21b58e3895&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=49970642&response-content-disposition=attachment%3B%20filename%3Dyarn-v1.22.4.tar.gz&response-content-type=application%2Foctet-stream
Resolving github-production-release-asset-2e65be.s3.amazonaws.com (github-production-release-asset-2e65be.s3.amazonaws.com)... <IP_ADDRESS>
Connecting to github-production-release-asset-2e65be.s3.amazonaws.com (github-production-release-asset-2e65be.s3.amazonaws.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1244785 (1.2M) [application/octet-stream]
Saving to: ‘yarn-v1.22.4.tar.gz’

     0K .......... .......... .......... .......... ..........  4%  600K 2s
    50K .......... .......... .......... .......... ..........  8%  576K 2s
   100K .......... .......... .......... .......... .......... 12%  628K 2s
   150K .......... .......... .......... .......... .......... 16% 96.5M 1s
   200K .......... .......... .......... .......... .......... 20%  592K 1s
   250K .......... .......... .......... .......... .......... 24% 23.5M 1s
   300K .......... .......... .......... .......... .......... 28% 24.9M 1s
   350K .......... .......... .......... .......... .......... 32% 44.7M 1s
   400K .......... .......... .......... .......... .......... 37%  658K 1s
   450K .......... .......... .......... .......... .......... 41% 78.9M 1s
   500K .......... .......... .......... .......... .......... 45% 14.7M 1s
   550K .......... .......... .......... .......... .......... 49% 20.5M 0s
   600K .......... .......... .......... .......... .......... 53% 61.6M 0s
   650K .......... .......... .......... .......... .......... 57%  104M 0s
   700K .......... .......... .......... .......... .......... 61% 93.7M 0s
   750K .......... .......... .......... .......... .......... 65% 54.5M 0s
   800K .......... .......... .......... .......... .......... 69% 87.7M 0s
   850K .......... .......... .......... .......... .......... 74% 79.0M 0s
   900K .......... .......... .......... .......... .......... 78%  677K 0s
   950K .......... .......... .......... .......... .......... 82% 84.2M 0s
  1000K .......... .......... .......... .......... .......... 86% 25.3M 0s
  1050K .......... .......... .......... .......... .......... 90% 36.6M 0s
  1100K .......... .......... .......... .......... .......... 94% 69.0M 0s
  1150K .......... .......... .......... .......... .......... 98% 82.8M 0s
  1200K .......... .....                                      100% 70.6M=0.5s

2021-01-08 19:52:00 (2.35 MB/s) - ‘yarn-v1.22.4.tar.gz’ saved [1244785/1244785]

yarn-v1.22.4/LICENSE
yarn-v1.22.4/README.md
yarn-v1.22.4/bin/
yarn-v1.22.4/bin/yarn
yarn-v1.22.4/bin/yarn.js
yarn-v1.22.4/bin/yarnpkg
yarn-v1.22.4/bin/yarn.cmd
yarn-v1.22.4/bin/yarnpkg.cmd
yarn-v1.22.4/lib/
yarn-v1.22.4/lib/cli.js
yarn-v1.22.4/lib/v8-compile-cache.js
yarn-v1.22.4/package.json
yarn
yarn install v1.22.4
info No lockfile found.
[1/4] Resolving packages...
warning @blueprintjs/core ><EMAIL_ADDRESS>You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1
warning @blueprintjs/core > react-popper ><EMAIL_ADDRESS>You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1
warning react-intl ><EMAIL_ADDRESS>This package has been deprecated, please see migration guide at 'https://github.com/formatjs/formatjs/tree/master/packages/intl-relativeformat#migration-guide'
warning @cypress/webpack-preprocessor ><EMAIL_ADDRESS>Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
warning Resolution field "<EMAIL_ADDRESS>is incompatible with requested version "<EMAIL_ADDRESS>warning Resolution field "<EMAIL_ADDRESS>is incompatible with requested version "<EMAIL_ADDRESS>warning Resolution field "<EMAIL_ADDRESS>is incompatible with requested version "<EMAIL_ADDRESS>warning Resolution field "<EMAIL_ADDRESS>is incompatible with requested version "<EMAIL_ADDRESS>warning @jupyterlab/testutils > jest > @jest/core > jest-config > jest-environment-jsdom > jsdom ><EMAIL_ADDRESS>request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
warning @jupyterlab/testutils > jest > @jest/core > jest-config > jest-environment-jsdom > jsdom ><EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
warning @jupyterlab/testutils > jest > @jest/core > jest-config > jest-environment-jsdom > jsdom > request ><EMAIL_ADDRESS>this library is no longer supported
warning @jupyterlab/testutils > jest > @jest/core > jest-haste-map > sane > micromatch > snapdragon > source-map-resolve ><EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
warning @jupyterlab/testutils > jest > @jest/core > jest-haste-map > sane > micromatch > snapdragon > source-map-resolve ><EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
warning cypress > @cypress/request ><EMAIL_ADDRESS>this library is no longer supported
warning enzyme > cheerio ><EMAIL_ADDRESS>Use cheerio-select instead
warning jest > jest-cli > @jest/core > jest-haste-map ><EMAIL_ADDRESS>fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
warning jest > jest-cli > jest-config > jest-environment-jsdom > jsdom ><EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
warning jest > jest-cli > jest-config > jest-environment-jsdom > jsdom ><EMAIL_ADDRESS>request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
warning jest > jest-cli > jest-config > jest-environment-jsdom > jsdom ><EMAIL_ADDRESS>use String.prototype.padStart()
warning lerna > @lerna/bootstrap > @lerna/run-lifecycle > npm-lifecycle > node-gyp ><EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
warning lerna > @lerna/bootstrap > @lerna/symlink-binary > @lerna/create-symlink > @zkochan/cmd-shim ><EMAIL_ADDRESS>This package is broken and no longer maintained. 'mkdirp' itself supports promises now, please switch to that.
warning start-server-and-test ><EMAIL_ADDRESS>Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
warning start-server-and-test > wait-on ><EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
warning start-server-and-test > wait-on ><EMAIL_ADDRESS>core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
warning start-server-and-test > wait-on ><EMAIL_ADDRESS>This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
warning start-server-and-test > wait-on > joi ><EMAIL_ADDRESS>This module has moved and is now available at @hapi/topo. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
warning start-server-and-test > wait-on > joi ><EMAIL_ADDRESS>This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
warning start-server-and-test > wait-on > joi > topo ><EMAIL_ADDRESS>This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
warning webpack > watchpack > watchpack-chokidar2 ><EMAIL_ADDRESS>Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
warning webpack > watchpack > watchpack-chokidar2 > chokidar ><EMAIL_ADDRESS>fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
warning workspace-aggregator-b91eacfc-544e-4b80-b040-f06bcca92c19 > @elyra/pipeline-editor-extension > react-scripts ><EMAIL_ADDRESS>"Please update to latest v2.3 or v2.2"
warning workspace-aggregator-b91eacfc-544e-4b80-b040-f06bcca92c19 > @elyra/pipeline-editor-extension > react-scripts ><EMAIL_ADDRESS>This loader has been deprecated. Please use eslint-webpack-plugin
warning workspace-aggregator-b91eacfc-544e-4b80-b040-f06bcca92c19 > @elyra/pipeline-editor-extension > react-scripts > jest-environment-jsdom-fourteen > jsdom ><EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
warning workspace-aggregator-b91eacfc-544e-4b80-b040-f06bcca92c19 > @elyra/pipeline-editor-extension > react-scripts > jest-environment-jsdom-fourteen > jsdom ><EMAIL_ADDRESS>request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
warning workspace-aggregator-b91eacfc-544e-4b80-b040-f06bcca92c19 > @elyra/pipeline-editor-extension > react-scripts > webpack-dev-server ><EMAIL_ADDRESS>Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x lessdependencies.
warning workspace-aggregator-b91eacfc-544e-4b80-b040-f06bcca92c19 > @elyra/ui-components > react-json-tree > babel-runtime ><EMAIL_ADDRESS>core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
warning workspace-aggregator-b91eacfc-544e-4b80-b040-f06bcca92c19 > @elyra/pipeline-editor-extension > react-scripts > react-dev-utils > fork-ts-checker-webpack-plugin ><EMAIL_ADDRESS>Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
warning Resolution field "<EMAIL_ADDRESS>is incompatible with requested version "<EMAIL_ADDRESS>warning workspace-aggregator-b91eacfc-544e-4b80-b040-f06bcca92c19 > @elyra/pipeline-editor-extension > react-scripts > workbox-webpack-plugin > workbox-build ><EMAIL_ADDRESS>Switch to 'npm install joi'
warning workspace-aggregator-b91eacfc-544e-4b80-b040-f06bcca92c19 > @elyra/pipeline-editor-extension > react-scripts > workbox-webpack-plugin > workbox-build > @hapi/joi ><EMAIL_ADDRESS>This version has been deprecated and is no longer supported or maintained
warning workspace-aggregator-b91eacfc-544e-4b80-b040-f06bcca92c19 > @elyra/pipeline-editor-extension > react-scripts > workbox-webpack-plugin > workbox-build > @hapi/joi ><EMAIL_ADDRESS>This version has been deprecated and is no longer supported or maintained
warning workspace-aggregator-b91eacfc-544e-4b80-b040-f06bcca92c19 > @elyra/pipeline-editor-extension > react-scripts > workbox-webpack-plugin > workbox-build > @hapi/joi ><EMAIL_ADDRESS>This version has been deprecated and is no longer supported or maintained
warning workspace-aggregator-b91eacfc-544e-4b80-b040-f06bcca92c19 > @elyra/pipeline-editor-extension > react-scripts > workbox-webpack-plugin > workbox-build > @hapi/joi > @hapi/topo ><EMAIL_ADDRESS>This version has been deprecated and is no longer supported or maintained
warning workspace-aggregator-b91eacfc-544e-4b80-b040-f06bcca92c19 > @elyra/pipeline-editor-extension > react-scripts > workbox-webpack-plugin > workbox-build > @hapi/joi ><EMAIL_ADDRESS>Moved to 'npm install @sideway/address'
[2/4] Fetching packages...
warning<EMAIL_ADDRESS>Invalid bin field for "mini-css-extract-plugin".
warning<EMAIL_ADDRESS>Invalid bin field for "url-loader".
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "@jupyterlab/testutils > @jupyterlab/notebook ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "enzyme-adapter-react-16 ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "lerna > @lerna/version > @lerna/github-client > @octokit/rest ><EMAIL_ADDRESS>has unmet peer dependency "@octokit/core@>=3".
warning "workspace-aggregator-b91eacfc-544e-4b80-b040-f06bcca92c19 > @elyra/pipeline-editor-extension ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^3.0.0 || ^4.0.0-0".
warning "workspace-aggregator-b91eacfc-544e-4b80-b040-f06bcca92c19 > @elyra/pipeline-editor-extension ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-b91eacfc-544e-4b80-b040-f06bcca92c19 > @elyra/pipeline-editor-extension > @elyra/canvas ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>| ^4.0.0-rc.12".
[4/4] Building fresh packages...
success Saved lockfile.
Done in 213.90s.
yarn run prettier
yarn run v1.22.4
$ prettier --ignore-path .gitignore --write "**/*{.ts,.tsx,.js,.jsx,.css,.json}"
.config/configstore/update-notifier-npm.json 36ms
.eslintrc.json 17ms
cypress.json 7ms
docs/source/_static/custom.css 52ms
elyra/metadata/schemas/code-snippet.json 16ms
elyra/metadata/schemas/kfp.json 28ms
elyra/metadata/schemas/metadata-test.json 30ms
elyra/metadata/schemas/metadata-test2.json 26ms
elyra/metadata/schemas/runtime-image.json 12ms
elyra/pipeline/tests/resources/archive/airflow.json 7ms
elyra/pipeline/tests/resources/sample_pipelines/pipeline_3_node_sample_with_dependencies.json 22ms
elyra/pipeline/tests/resources/sample_pipelines/pipeline_3_node_sample.json 13ms
elyra/pipeline/tests/resources/sample_pipelines/pipeline_dependency_complex.json 50ms
elyra/pipeline/tests/resources/sample_pipelines/pipeline_dependency_simple.json 28ms
elyra/pipeline/tests/resources/sample_pipelines/pipeline_invalid.json 10ms
elyra/pipeline/tests/resources/sample_pipelines/pipeline_multiple_pipeline_definitions.json 20ms
elyra/pipeline/tests/resources/sample_pipelines/pipeline_valid.json 12ms
elyra/pipeline/tests/resources/sample_pipelines/pipeline_with_supernode.json 24ms
etc/config/jupyter_notebook_config.d/elyra.json 7ms
etc/config/jupyter_notebook_config.d/jupyterlab_git.json 6ms
etc/config/metadata/runtime-images/anaconda.json 8ms
etc/config/metadata/runtime-images/pandas.json 10ms
etc/config/metadata/runtime-images/pytorch-devel.json 9ms
etc/config/metadata/runtime-images/pytorch-runtime.json 6ms
etc/config/metadata/runtime-images/tensorflow_2x_gpu_py3.json 6ms
etc/config/metadata/runtime-images/tensorflow_2x_py3.json 15ms
etc/config/metadata/runtime-images/tensorflow_gpu_py3.json 8ms
etc/config/metadata/runtime-images/tensorflow_py3.json 8ms
etc/config/settings/page_config.json 7ms
lerna.json 8ms
package.json 10ms
packages/application/jest.config.js 13ms
packages/application/package.json 12ms
packages/application/src/index.ts 161ms
packages/application/src/parsing.ts 46ms
packages/application/src/requests.tsx 85ms
packages/application/src/services.tsx 47ms
packages/application/src/test/application.spec.ts 80ms
packages/application/style/index.css 12ms
packages/application/tsconfig.json 8ms
packages/application/tsconfig.test.json 7ms
packages/code-snippet/package.json 19ms
packages/code-snippet/src/CodeSnippetService.ts 30ms
packages/code-snippet/src/CodeSnippetWidget.tsx 134ms
packages/code-snippet/src/index.ts 20ms
packages/code-snippet/style/index.css 25ms
packages/code-snippet/tsconfig.json 12ms
packages/metadata-common/package.json 9ms
packages/metadata-common/src/FilterTools.tsx 56ms
packages/metadata-common/src/index.ts 12ms
packages/metadata-common/src/MetadataEditor.tsx 141ms
packages/metadata-common/src/MetadataEditorTags.tsx 83ms
packages/metadata-common/src/MetadataWidget.tsx 74ms
packages/metadata-common/style/index.css 58ms
packages/metadata-common/tsconfig.json 17ms
packages/metadata/package.json 7ms
packages/metadata/src/index.ts 36ms
packages/metadata/style/index.css 16ms
packages/metadata/tsconfig.json 9ms
packages/pipeline-editor/jest.config.js 11ms
packages/pipeline-editor/package.json 10ms
packages/pipeline-editor/src/canvas.ts 21ms
packages/pipeline-editor/src/common-canvas.d.ts 6ms
packages/pipeline-editor/src/constants.ts 6ms
packages/pipeline-editor/src/en.json 12ms
packages/pipeline-editor/src/formDialogWidget.ts 13ms
packages/pipeline-editor/src/index.ts 35ms
packages/pipeline-editor/src/json-loader.d.ts 8ms
packages/pipeline-editor/src/NotebookSubmissionDialog.tsx 28ms
packages/pipeline-editor/src/palette.json 18ms
packages/pipeline-editor/src/pipeline-template.json 10ms
packages/pipeline-editor/src/PipelineEditorWidget.tsx 281ms
packages/pipeline-editor/src/PipelineExportDialog.tsx 17ms
packages/pipeline-editor/src/PipelineService.tsx 50ms
packages/pipeline-editor/src/PipelineSubmissionDialog.tsx 14ms
packages/pipeline-editor/src/properties.json 20ms
packages/pipeline-editor/src/RuntimesWidget.tsx 18ms
packages/pipeline-editor/src/SubmitNotebookButtonExtension.tsx 14ms
packages/pipeline-editor/src/test/__mocks__/PipelineService.tsx 7ms
packages/pipeline-editor/src/test/pipeline.spec.tsx 26ms
packages/pipeline-editor/src/utils.ts 41ms
packages/pipeline-editor/style/canvas.css 64ms
packages/pipeline-editor/style/index.css 22ms
packages/pipeline-editor/tsconfig.json 8ms
packages/pipeline-editor/tsconfig.test.json 5ms
packages/pipeline-editor/webpack.config.js 14ms
packages/python-editor/package.json 8ms
packages/python-editor/src/index.ts 28ms
packages/python-editor/src/KernelDropdown.tsx 27ms
packages/python-editor/src/PythonFileEditor.tsx 66ms
packages/python-editor/src/PythonRunner.ts 35ms
packages/python-editor/style/index.css 21ms
packages/python-editor/tsconfig.json 7ms
packages/theme/package.json 8ms
packages/theme/src/index.ts 20ms
packages/theme/src/launcher.tsx 26ms
packages/theme/style/index.css 8ms
packages/theme/tsconfig.json 7ms
packages/ui-components/package.json 7ms
packages/ui-components/src/BrowseFileDialog.tsx 37ms
packages/ui-components/src/DropDown.tsx 22ms
packages/ui-components/src/ExpandableComponent.tsx 27ms
packages/ui-components/src/ExpandableErrorDialog.tsx 15ms
packages/ui-components/src/FeedbackButton.tsx 15ms
packages/ui-components/src/FormDialog.tsx 31ms
packages/ui-components/src/icons.tsx 27ms
packages/ui-components/src/index.ts 9ms
packages/ui-components/src/JSONComponent.tsx 18ms
packages/ui-components/src/svg.d.ts 12ms
packages/ui-components/style/index.css 37ms
packages/ui-components/tsconfig.json 8ms
tests/integration/codesnippet.ts 11ms
tests/integration/git.ts 8ms
tests/integration/pipeline.ts 33ms
tests/integration/pythoneditor.ts 19ms
tests/integration/submitbutton.ts 9ms
tests/integration/toc.ts 8ms
tests/plugins/index.js 10ms
tests/tsconfig.json 6ms
tests/webpack.config.js 8ms
testutils/babel.config.js 6ms
testutils/jest.config.js 10ms
testutils/jest.setup.js 16ms
testutils/transform.js 8ms
tsconfig-base.json 11ms
tsconfigbase.test.json 7ms
Done in 5.70s.
yarn run eslint
yarn run v1.22.4
$ eslint . --fix --ignore-path .gitignore --ext .ts,.tsx,.js
Done in 4.43s.
export PATH=$(pwd)/node_modules/.bin:$PATH && lerna run build
lerna notice cli v3.22.1
lerna info Executing command in 8 packages: "yarn run build"
lerna info run Ran npm script 'build' in '@elyra/ui-components' in 12.3s:
yarn run v1.22.4
$ tsc
Done in 12.04s.
lerna info run Ran npm script 'build' in '@elyra/python-editor-extension' in 13.0s:
yarn run v1.22.4
$ tsc
Done in 12.78s.
lerna info run Ran npm script 'build' in '@elyra/theme-extension' in 10.8s:
yarn run v1.22.4
$ tsc
Done in 10.49s.
lerna info run Ran npm script 'build' in '@elyra/application' in 12.9s:
yarn run v1.22.4
$ tsc
Done in 12.61s.
lerna info run Ran npm script 'build' in '@elyra/metadata-common' in 9.7s:
yarn run v1.22.4
$ tsc
Done in 9.52s.
lerna info run Ran npm script 'build' in '@elyra/metadata-extension' in 16.3s:
yarn run v1.22.4
$ tsc
Done in 15.97s.
lerna info run Ran npm script 'build' in '@elyra/code-snippet-extension' in 17.3s:
yarn run v1.22.4
$ tsc
Done in 16.96s.
lerna ERR! yarn run build exited 1 in '@elyra/pipeline-editor-extension'
lerna ERR! yarn run build stdout:
yarn run v1.22.4
$ tsc
../../node_modules/@types/enzyme/index.d.ts(384,15): error TS2503: Cannot find namespace 'cheerio'.
../../node_modules/@types/enzyme/index.d.ts(728,69): error TS2503: Cannot find namespace 'cheerio'.
../../node_modules/cheerio/node_modules/htmlparser2/lib/index.d.ts(36,10): error TS1005: 'from' expected.
../../node_modules/cheerio/node_modules/htmlparser2/lib/index.d.ts(36,10): error TS1141: String literal expected.
../../node_modules/cheerio/node_modules/htmlparser2/lib/index.d.ts(36,13): error TS1005: ';' expected.
../../node_modules/cheerio/node_modules/htmlparser2/lib/index.d.ts(36,13): error TS2304: Cannot find name 'DomUtils'.
../../node_modules/cheerio/node_modules/htmlparser2/lib/index.d.ts(36,22): error TS1005: ';' expected.
../../node_modules/cheerio/node_modules/htmlparser2/lib/index.d.ts(36,22): error TS2304: Cannot find name 'from'.
../../node_modules/cheerio/node_modules/htmlparser2/lib/index.d.ts(36,27): error TS1005: ';' expected.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

lerna ERR! yarn run build stderr:
error Command failed with exit code 1.

lerna ERR! yarn run build exited 1 in '@elyra/pipeline-editor-extension'
make: *** [build-ui] Error 1
Makefile:84: recipe for target 'build-ui' failed

See related issue https://github.com/elyra-ai/elyra/issues/1168

See related issue https://github.com/elyra-ai/elyra/issues/1168

This has been fixed with release 1.5.3

This has been fixed with release 1.5.3


Python 2 and 3 compatibility

I've added Python 3 compatibility to existing code using python-future, and so it should now run on both Python 2 and 3.

Ok, so this is currently failing to build on Travis CI with Python 2. I'll investigate further soon, it's likely that future will need to be added to requirements.txt

Can you update .travis.yml to test python3 also? This might require some changes to the tests too...

Tests already converted so all should be good now.

Thanks for the PR. Unfortunately, I pushed this without adequate testing and it looks like the local environment needs to have the future module globally installed in order to build sodapy. I'm going to move all of these exciting compatibility changes out of master and into a separate branch for now, and further meditate on how to accommodate python3 (probably a separate package, sodapy3?). I'm open to ideas here though.


Type error at offer/create

Description:
Type error occurs while adding new offer
Current behaviour:
While adding an offer, when start point is set to "already going" and end point is set to some date, an error occurs:
TypeError at /o/offers/create
unorderable types: NoneType() < datetime.datetime()

However an offer is added to database.
Expected behaviour:
Describe expected behaviour of application.
Steps to reproduce:

We had this bug before in backlog, but I will close the former one, as this one better described.

Biorę.

closed in #738


First ABAP connectivity tutorials: MQTT & Daemons (2 new Tutorials)

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


WebIO not working in Juno

Hi,
is it normal that the simple WebIO example does not work properly with (the excellent) Juno (even after these  PRs https://github.com/JunoLab/Atom.jl/pull/130,  https://github.com/JunoLab/Atom.jl/pull/133 and https://github.com/JunoLab/Atom.jl/pull/135):
using WebIO
node(:div, "Hello, World")

No "Hello, World" is shown inside the plotpane. Only inlined Node{WebIO.DOM} is printed. Is it aWebIO.jl or a Atom.jl issue?  I mention that here since Atom.jl is requiring WebIO.jl.
As expected, the following Blink.jl example is working properly
using Blink
w = Blink.Window()
body!(w, dom"div"("Hello, World"))

I also checked that the example in the Juno documentation is working properly in the plotpane.
Hope this will work very soon since this is a very interesting tools to promote Juno.
Many thanks for this beautiful work.

I close the issue since the code is working now.


docs: add exit command description, more description for find command and remove invalid line breaking

docs: add exit command description, more description for find command and remove invalid line breaking

Codecov Report

Merging #181 (aad2ea5) into master (4f7660a) will increase coverage by 1.75%.
The diff coverage is 81.09%.

@@             Coverage Diff              @@
##             master     #181      +/-   ##
============================================
+ Coverage     72.15%   73.91%   +1.75%
- Complexity      399      560     +161
============================================
  Files            70       84      +14
  Lines          1232     1955     +723
  Branches        125      179      +54
============================================
+ Hits            889     1445     +556
- Misses          311      449     +138
- Partials         32       61      +29

Impacted Files
Coverage Δ

src/main/java/seedu/address/MainApp.java
0.00% <0.00%> (ø)

...in/java/seedu/address/commons/core/LogsCenter.java
78.37% <ø> (ø)

...main/java/seedu/address/commons/core/Messages.java
0.00% <ø> (ø)

...rc/main/java/seedu/address/logic/LogicManager.java
0.00% <0.00%> (-75.00%)
:arrow_down:

...java/seedu/address/logic/commands/ExitCommand.java
100.00% <ø> (ø)

...ss/logic/commands/exceptions/CommandException.java
50.00% <ø> (-50.00%)
:arrow_down:

...c/main/java/seedu/address/logic/parser/Prefix.java
91.66% <0.00%> (ø)

...a/seedu/address/logic/parser/RecipeBookParser.java
0.00% <0.00%> (ø)

...ain/java/seedu/address/storage/JsonAdaptedTag.java
100.00% <ø> (ø)

src/main/java/seedu/address/ui/HelpWindow.java
0.00% <ø> (ø)

... and 66 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 4f7660a...aad2ea5. Read the comment docs.


鼠标无法划选多个文件、文件夹

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS Version: [e.g. Windows 10 1903 18362.175]
App version: [v0.5.0]

Additional context
Add any other context about the problem here. Does this problem occur again after restarting the app?

We are tracking a selection rectangle in #94.

Thank you for opening this issue. We are tracking a selection rectangle in #94.


(wrong-type-argument . arrayp) error when cloning a package during doom {install,upgrade}

What did you expect to happen?
When I did doom up I expected doom to update

doom up
❯ doom up
> Executing 'doom upgrade' with Emacs 27.2 at 2021-11-21 12:36:28
  > Preparing to upgrade Doom Emacs and its packages...
  - A new version of Doom Emacs is available!

    Old revision: df64e5024b (7 days ago)
    New revision: 407cf56a04 (9 hours ago)

  Link to diff: https://github.com/hlissner/doom-emacs/compare/df64e5024b036ffeadf26226a7fa28473d270ba0...407cf56a04424f7165f360c604e3db5769f99a79
View the comparison diff in your browser? (y or n) n
Proceed with upgrade? (y or n) y
  > Upgrading Doom Emacs...
    > Cleaning .elc files
      - No elc files to clean
    - From https://github.com/hlissner/doom-emacs
     * [new branch]          develop    -> _upgrade_develop
     * [new branch]          develop    -> _upgrade/develop
  - Reloading Doom Emacs
> Executing 'doom upgrade -p' with Emacs 27.2 at 2021-11-21 12:36:36
  > Synchronizing your config with Doom Emacs...
    > Regenerating envvars file at "~/hacking/doom-emacs/.local/env"
      ✓ Successfully generated "~/hacking/doom-emacs/.local/env"
    > Installing packages...
      > Updating recipe repos...
        ✓ melpa updated (43726f8 -> db77988)
          - $ cd /Users/tmk/hacking/doom-emacs/.local/straight/repos/melpa/
          $ git config --get remote.origin.url

          https://github.com/melpa/melpa.git

          [Return code: 0]

          $ cd /Users/tmk/hacking/doom-emacs/.local/straight/repos/melpa/
          $ git fetch origin

          From https://github.com/melpa/melpa
             43726f8e..db77988a  master     -> origin/master
        ✓ gnu-elpa-mirror updated (870aae4 -> 7eed1d9)
          - $ cd /Users/tmk/hacking/doom-emacs/.local/straight/repos/gnu-elpa-mirror/
          $ git config --get remote.origin.url

          https://github.com/emacs-straight/gnu-elpa-mirror.git

          [Return code: 0]

          $ cd /Users/tmk/hacking/doom-emacs/.local/straight/repos/gnu-elpa-mirror/
          $ git fetch origin

          From https://github.com/emacs-straight/gnu-elpa-mirror
             870aae4..7eed1d9  master     -> origin/master
        ✓ emacsmirror-mirror updated (5bcbacb -> 371e4a0)
          - $ cd /Users/tmk/hacking/doom-emacs/.local/straight/repos/emacsmirror-mirror/
          $ git config --get remote.origin.url

          https://github.com/emacs-straight/emacsmirror-mirror.git

          [Return code: 0]

          $ cd /Users/tmk/hacking/doom-emacs/.local/straight/repos/emacsmirror-mirror/
          $ git fetch origin

          From https://github.com/emacs-straight/emacsmirror-mirror
             5bcbacb..371e4a0  master     -> origin/master
      > Cloning consult-dir...
      - Checked out consult-dir: 08f543ae6acbfc1ffe579ba1d00a5414012d5c0b
      > Building consult-dir...
      > Building spinner...
      > Building map...
      > Building queue...
      ✓ Installed 4 packages
    > (Re)building packages...
      - No packages need rebuilding
    > Updating packages (this may take a while)...
      ✓ (28/275) vertico: cd3c400 -> 75f33e3 [35 commit(s)]
          75f33e3 Introduce vertico--metadata-get
          9479c5d Version 0.15
          0df38cf vertico--recompute-candidates: Minor simplification
          d646722 vertico-flat/grid-mode: Copy string properties when shrinking string
          99e6d90 vertico-grid-mode: Set completion predicate
          5c10607 Fix indexed mode (Fix #151)
          665660f Autoload vertico-repeat to improve error message
          6b0ea6b vertico-grid-mode: Improve alignment
          ad2ba13 vertico-grid/flat-mode: Add check
          3e16230 vertico-grid/flat-mode: Allow toggling between vertical/grid/flat mode
          cdc3334 Remove while-no-input-ignore-events workaround (#150)
          5624aaf Minor simplification
          371e264 vertico-grid-mode: Compute numbers of columns
          d42f315 vertico-grid: Minor improvements
          42aca1f README updates
          298379e Ensure that vertico-mouse+buffer works
          94e399e vertico-buffer: Mark as read-only
          804d8ca Add vertico-grid-mode extension
          3c33998 Update version bounds
          3dd5794 README: Update paragraph about child frames
          [...]
      ✓ (30/275) consult: 166e3b0 -> 57dc1ad [25 commit(s)]
          57dc1ad Adjust consult--grep-match-regexp in order to support -[ABC] grep options (Fix #466)
          7708dc7 consult-completion-in-region: insert initial text for file completion (#463)
          3b18b04 README: Minor improvement
          39f41ed consult--format-location: Only append colon if STR is non-nil (Fix #460)
          e8f4d9d consult-flymake: Sort by severity
          e10775a README: Update link to @bdarcus' citar
          56a6a9f README: Update links
          901b12f README: Update links
          0bd4b40 README: Add link to consult-projectile
          8bc1f05 Update changelog
          9229b5a Internal renamings
          b56bd11 Rename consult-isearch to consult-isearch-history
          ae2761e  Make menu-item :fiter functions pure functions (#453)
          b903bce Minor readme updates
          6769f21 README: Fix typo
          04d9cb0 README: Minor update
          e0c3b2c Update list of completion UIs, in particular add @protesilaos' mct.el
          67fa3a2 consult-register-store: Add support to create file register value
          d8c925b consult-register: Add support for file values (Fix #449)
          3715f73 README: Add link to all-the-icons-completion
          [...]

What actually happened?
Instead I got the following error
      x There was an unexpected error
        Message: Wrong type argument
        Error: (wrong-type-argument stringp arrayp)
        Backtrace:
          (string-match "\n" arrayp 0)
          (split-string arrayp "\n")
          (let ((parts (split-string string "\n"))) (while (equal (car parts) "") (s...
          (straight--split-and-trim arrayp 2)
          (format "In repository %S, failed to get status:\n\n%s" local-repo (straig...
          (straight--popup-raw (format "In repository %S, failed to get status:\n\n%...
          (cond (failure (straight--popup-raw (format "In repository %S, failed to g...
          (let* ((--cl-rest-- status) (left-ref (car (cdr (plist-member --cl-rest-- ...
          (let ((status (straight-vc-git--compare-and-canonicalize default-branch "H...
          (straight-vc-git--ensure-head-at-branch "embark" nil)
      ! Extended backtrace logged to ~/hacking/doom-emacs/.local/doom.error.log

extended backtrace
Describe your attempts to resolve the issue
I then tried to do a clean doom install

`doom install`
❯ doom install
> Installing straight...
  > Cloning use-package...
> Executing 'doom install' with Emacs 27.2 at 2021-11-21 15:16:37
  Installing Doom Emacs!

  > Creating .config/doom/
    ✓ Created .config/doom/
  ! init.el already exists, skipping
  ! config.el already exists, skipping
  ! packages.el already exists, skipping
Generate an envvar file? (see `doom help env` for details) (y or n) y
  > Generating envvars file at "~/hacking/doom-emacs/.local/env"
    ✓ Successfully generated "~/hacking/doom-emacs/.local/env"
  Installing plugins
  > Installing packages...
    > Building straight...
    - Checked out use-package: a7422fb8ab1baee19adb2717b5b47b9c3812a84c
    > Building use-package...
    > Building use-package > Building bind-key...
    > Building use-package...
    > Updating recipe repos...
    > Cloning auto-minor-mode...csmirror-mirror...
    - Checked out auto-minor-mode: 17cfa1b54800fdef2975c0c0531dad34846a5065
    > Building auto-minor-mode...
    > Cloning gcmh...
    - Checked out gcmh: 0089f9c3a6d4e9a310d0791cf6fa8f35642ecfd9
    > Building gcmh...
    > Cloning explain-pause-mode...
    - Checked out explain-pause-mode: 2356c8c3639cbeeb9751744dbe737267849b4b51
    > Building explain-pause-mode...
    > Cloning all-the-icons.el...
    > Building all-the-icons...
    > Cloning emacs-hide-mode-line...
    > Building hide-mode-line...
    > Cloning highlight-numbers...
    - Checked out highlight-numbers: 8b4744c7f46c72b1d3d599d4fb75ef8183dee307
    > Building highlight-numbers...
    > Building highlight-numbers > Cloning parent-mode...
    > Building highlight-numbers > Building parent-mode...
    > Building highlight-numbers...
    > Cloning rainbow-delimiters...
    - Checked out rainbow-delimiters: d576e6694ad3a3e88b2bb1363305b38fa364c149
    > Building rainbow-delimiters...
    > Cloning restart-emacs...
    - Checked out restart-emacs: 1607da2bc657fe05ae01f7fdf26f716eafead02c
    > Building restart-emacs...
    > Cloning better-jumper...
    - Checked out better-jumper: 7f328a886ba4dd01993d269eee01c8ee3d0ddf52
    > Building better-jumper...
    > Cloning dtrt-indent...
    - Checked out dtrt-indent: 9714f2c5f1c9b7c21e732df8c15a870a88caba84
    > Building dtrt-indent...
    > Cloning helpful...
    - Checked out helpful: 7e4b1f0d5572a4e2b8ee7a9b084ef863d0315a73
    > Building helpful...
    > Building helpful > Cloning dash.el...
    > Building helpful > Building dash...
    > Building helpful > Cloning s.el...
    > Building helpful > Building s...
    > Building helpful > Cloning f.el...
    > Building helpful > Building f...
    > Building helpful > Cloning elisp-refs...
    > Building helpful > Building elisp-refs...
    > Building helpful...
    > Cloning pcre2el...
    - Checked out pcre2el: 0b5b2a2c173aab3fd14aac6cf5e90ad3bf58fa7d
    > Building pcre2el...
    > Cloning smartparens...
    - Checked out smartparens: 2834c66c4f09778d0c57e99886c329188eed591a
    > Building smartparens...
    > Cloning ws-butler...
    - Checked out ws-butler: 572a10c11b6cb88293de48acbb59a059d36f9ba5
    > Building ws-butler...
    > Cloning projectile...
    - Checked out projectile: 7f64570d3e6829d767d340c8584f3e4f3472ee81
    > Building projectile...
    > Cloning project...
    - Checked out project: a546cce47c434b0b4bf24bf1d5ed6e4623492072
    > Building project...
    > Building project > Cloning xref...
    > Building project > Building xref...
    > Building project...
    > Cloning general.el...
    > Building general...
    > Cloning emacs-which-key...
    > Building which-key...
    > Cloning company-mode (for company)...
    > Building company...
    > Cloning emacs-company-dict...
    > Building company-dict...
    > Cloning company-box...
    - Checked out company-box: 156f65cfbf690ed84e0e84f90277d665d873ff24
    > Building company-box...
    > Building company-box > Building dash-functional...
    > Building company-box > Cloning frame-local...
    > Building company-box > Building frame-local...
    > Building company-box...
    > Cloning vertico...
    - Checked out vertico: 75f33e36204f8a72d0b8cde81e04d3350a848981
    > Building vertico...
    > Cloning orderless...
    - Checked out orderless: 62f71c34baca0b7d0adeab4a1c07d85ffcee80d9
    > Building orderless...
    > Cloning consult...
    - Checked out consult: 57dc1adfdc0feafc71c6f418ff7aa1adbe47a5fd
    > Building consult...
    > Cloning consult-dir...
    - Checked out consult-dir: 08f543ae6acbfc1ffe579ba1d00a5414012d5c0b
    > Building consult-dir...
    > Cloning consult-flycheck...
    - Checked out consult-flycheck: 92b259e6a8ebe6439f67d3d7ffa44b7e64b76478
    > Building consult-flycheck...
    > Building consult-flycheck > Cloning flycheck...
    - Checked out flycheck: 784f184cdd9f9cb4e3dbb997c09d93e954142842
    > Building consult-flycheck > Building flycheck...
    > Building consult-flycheck > Building flycheck > Cloning pkg-info...
    > Building consult-flycheck > Building flycheck > Building pkg-info...
    > Building consult-flycheck > Building flycheck > Building pkg-info > Cloning epl...
    > Building consult-flycheck > Building flycheck > Building pkg-info > Building epl...
    > Building consult-flycheck > Building flycheck > Building pkg-info...
    > Building consult-flycheck > Building flycheck...
    > Building consult-flycheck...
    > Cloning embark...
    - Checked out embark: 5b34b2b60370cea5ad9da5931856667a6fae0501
    > Building embark...
    > Building embark-consult...
    > Cloning marginalia...
    - Checked out marginalia: 678b6528f3905e624b01daf787461d8c7e06ec0f
    > Building marginalia...
    > Cloning Emacs-wgrep (for wgrep)...
    > Building wgrep...
    > Cloning all-the-icons-completion...
    - Checked out all-the-icons-completion: a0f34d68cc12330ab3992a7521f9caa1de3b8470
    > Building all-the-icons-completion...
    > Cloning emacs-doom-themes...
    > Building doom-themes...
    > Cloning emacs-solaire-mode...
    > Building solaire-mode...
    > Cloning emacs-emojify...
    > Building emojify...
    > Building emojify > Cloning ht.el...
    > Building emojify > Building ht...
    > Building emojify...
    > Cloning hl-todo...
    - Checked out hl-todo: 42f744ffb513cf2b95517144c64dbf3fc69f711a
    > Building hl-todo...
    > Cloning minimap...
    - Checked out minimap: ed7490652a676c0510ed57d5366c445de20a370b
    > Building minimap...
    > Cloning anzu...
    - Checked out anzu: bdb3da5028935a4aea55c40769bc191a81afb54e
    > Building anzu...
    > Cloning evil-anzu...
    - Checked out evil-anzu: d3f6ed4773b48767bd5f4708c7f083336a8a8a86
    > Building evil-anzu...
    > Building evil-anzu > Cloning evil...
    - Checked out evil: 07aba40dd32c667f36eb1ad244f859983a077d12
    > Building evil-anzu > Building evil...
    > Building evil-anzu > Building evil > Cloning goto-chg...
    > Building evil-anzu > Building evil > Building goto-chg...
    > Building evil-anzu > Building evil...
    > Building evil-anzu...
    > Cloning nav-flash...
    - Checked out nav-flash: 2e31f32085757e1dfdd8ec78e9940fd1c88750de
    > Building nav-flash...
    > Cloning evil-goggles...
    - Checked out evil-goggles: 08a22058fd6a167f9f1b684c649008caef571459
    > Building evil-goggles...
    > Cloning treemacs...
    - Checked out treemacs: 63e2bc207a2a4a36a3eebbe994353cb4845ad2de
    > Building treemacs...
    > Building treemacs > Cloning ace-window...
    - Checked out ace-window: c7cb315c14e36fded5ac4096e158497ae974bec9
    > Building treemacs > Building ace-window...
    > Building treemacs > Building ace-window > Cloning avy...
    - Checked out avy: e92cb37457b43336b765630dbfbea8ba4be601fa
    > Building treemacs > Building ace-window > Building avy...
    > Building treemacs > Building ace-window...
    > Building treemacs > Cloning pfuture...
    > Building treemacs > Building pfuture...
    > Building treemacs > Cloning hydra...
    > Building treemacs > Building hydra...
    > Building treemacs > Building hydra > Building lv...
    > Building treemacs > Building hydra...
    > Building treemacs > Cloning cfrs...
    > Building treemacs > Building cfrs...
    > Building treemacs > Building cfrs > Cloning posframe...
    > Building treemacs > Building cfrs > Building posframe...
    > Building treemacs > Building cfrs...
    > Building treemacs...
    > Building treemacs-evil...
    > Building treemacs-projectile...
    > Building treemacs-magit...
    > Building treemacs-magit > Cloning magit...
    - Checked out magit: aba0a596115b42fbd60347d893bcc319020ce5a2
    > Building treemacs-magit > Building magit...
    > Building treemacs-magit > Building magit > Building git-commit...
    > Building treemacs-magit > Building magit > Building git-commit > Cloning transient...
    > Building treemacs-magit > Building magit > Building git-commit > Building transient...
    > Building treemacs-magit > Building magit > Building git-commit > Cloning with-editor...
    > Building treemacs-magit > Building magit > Building git-commit > Building with-editor...
    > Building treemacs-magit > Building magit > Building git-commit...
    > Building treemacs-magit > Building magit > Building magit-section...
    > Building treemacs-magit > Building magit...
    > Building treemacs-magit...
    > Building treemacs-persp...
    > Building treemacs-persp > Cloning persp-mode.el...
    > Building treemacs-persp > Building persp-mode...
    > Building treemacs-persp...
    > Cloning unicode-fonts...
    - Checked out unicode-fonts: e3942fe40b418bfb2dc4e73633e09195437fef01
    > Building unicode-fonts...
    > Building unicode-fonts > Cloning font-utils...
    > Building unicode-fonts > Building font-utils...
    > Building unicode-fonts > Building font-utils > Cloning persistent-soft...
    > Building unicode-fonts > Building font-utils > Building persistent-soft...
    > Building unicode-fonts > Building font-utils > Building persistent-soft > Cloning pcache...
    > Building unicode-fonts > Building font-utils > Building persistent-soft > Building pcache...
    > Building unicode-fonts > Building font-utils > Building persistent-soft > Cloning list-utils...
    > Building unicode-fonts > Building font-utils > Building persistent-soft > Building list-utils...
    > Building unicode-fonts > Building font-utils > Building persistent-soft...
    > Building unicode-fonts > Building font-utils...
    > Building unicode-fonts > Cloning ucs-utils...
    > Building unicode-fonts > Building ucs-utils...
    > Building unicode-fonts...
    > Cloning git-gutter-fringe...
    - Checked out git-gutter-fringe: 4f19866494fa1debfa319382913e39a153431634
    > Building git-gutter-fringe...
    > Building git-gutter-fringe > Cloning git-gutter...
    > Building git-gutter-fringe > Building git-gutter...
    > Building git-gutter-fringe > Cloning fringe-helper.el...
    > Building git-gutter-fringe > Building fringe-helper...
    > Building git-gutter-fringe...
    > Cloning vi-tilde-fringe...
    - Checked out vi-tilde-fringe: f1597a8d54535bb1d84b442577b2024e6f910308
    > Building vi-tilde-fringe...
    > Cloning evil-args...
    - Checked out evil-args: 758ad5ae54ad34202064fec192c88151c08cb387
    > Building evil-args...
    > Cloning evil-easymotion...
    - Checked out evil-easymotion: f96c2ed38ddc07908db7c3c11bcd6285a3e8c2e9
    > Building evil-easymotion...
    > Cloning evil-embrace.el...
    > Building evil-embrace...
    > Building evil-embrace > Cloning embrace.el...
    > Building evil-embrace > Building embrace...
    > Building evil-embrace > Building embrace > Cloning expand-region.el...
    > Building evil-embrace > Building embrace > Building expand-region...
    > Building evil-embrace > Building embrace...
    > Building evil-embrace > Cloning evil-surround...
    - Checked out evil-surround: 282a975bda83310d20a2c536ac3cf95d2bf188a5
    > Building evil-embrace > Building evil-surround...
    > Building evil-embrace...
    > Cloning evil-escape...
    - Checked out evil-escape: 819f1ee1cf3f69a1ae920e6004f2c0baeebbe077
    > Building evil-escape...
    > Cloning evil-exchange...
    - Checked out evil-exchange: ac50f21b29b6e3a111e10a9e88ae61c907ac5ee8
    > Building evil-exchange...
    > Cloning evil-indent-plus...

But I also got an error message:
x There was an unexpected error
      Message: Wrong type argument
      Error: (wrong-type-argument arrayp nil)
      Backtrace:
        (substring nil 0 0)
        (replace-regexp-in-string "[^-0-9a-zA-Z_./\n]" "\\\\\\&" nil)
        (shell-quote-argument nil)
        (mapconcat shell-quote-argument ("git" "branch" "-m" nil) " ")
        (format "$ cd %s\n$ %s\n\n" (shell-quote-argument (expand-file-name direct...
        (propertize (format "$ cd %s\n$ %s\n\n" (shell-quote-argument (expand-file...
        (concat (propertize (format "$ cd %s\n$ %s\n\n" (shell-quote-argument (exp...
        (let* ((inhibit-read-only t) (entry (concat (propertize (format "$ cd %s\n...
        (let* ((result result) (exit (car result)) (invoked (numberp exit)) (succe...
        (let ((directory x6) (result x4) (args x2) (program x0)) (let* ((result re...
    ! Extended backtrace logged to ~/hacking/doom-emacs/.local/doom.error.log

extended backtrace
Steps to reproduce

clone doom repository
run doom install

System Information
https://pastebin.com/uQyTyTMR

Duplicate of https://github.com/hlissner/doom-emacs/issues/5207.
See https://github.com/hlissner/doom-emacs/issues/5207#issuecomment-877750996.

Thanks for the quick reply.
I'll try updating again.


ion-slides not working in modal when ion-button is present in modal

Bug Report
Ionic version:

[x] 4.0.1
Current behavior:
On second opening of modal view with ion-slides and ion-button inside of modal template ion-slides becomes unresponsive, without ion-button everything is working correctly
Expected behavior:
ion-slides should work correctly everytime modal is opened and it should not depend on other components in templates like ion-button
Steps to reproduce:
Use ionic source code, core->src->components->modal->test->basic and add to test ion-slides, first time when modal is opened everything is ok, second time that modal is opened it is unresponsive, if you change ion-button in test with anchor tag everything is going to be ok
Related code:

Not working
 async function createModal() {
    // initialize controller
    const modalController = document.querySelector('ion-modal-controller');
    await modalController.componentOnReady();

    // create component to open
    const element = document.createElement('div');
    element.innerHTML = `
      <ion-header>
        <ion-toolbar>
          <ion-title>Super Modal</ion-title>
        </ion-toolbar>
      </ion-header>
      <ion-content>

Content of doom

Here's some more content

        <ion-slides mode="md">
          <ion-slide>

1

          </ion-slide>
          <ion-slide>

2

          </ion-slide>
          <ion-slide>

3

          </ion-slide>
        </ion-slides>
      <ion-button class="dismiss">Dismiss Modal</ion-button>
    </ion-content>
      `;

    // listen for close event
    const button = element.querySelector('ion-button');
    button.addEventListener('click', () => {
      modalController.dismiss();
    });

    // present the modal
    const modalElement = await modalController.create({
      component: element
    });
    return modalElement;
  }

Working
  async function createModal() {
    // initialize controller
    const modalController = document.querySelector('ion-modal-controller');
    await modalController.componentOnReady();

    // create component to open
    const element = document.createElement('div');
    element.innerHTML = `
      <ion-header>
        <ion-toolbar>
          <ion-title>Super Modal</ion-title>
        </ion-toolbar>
      </ion-header>
      <ion-content>

Content of doom

Here's some more content

        <ion-slides mode="md">
          <ion-slide>

1

          </ion-slide>
          <ion-slide>

2

          </ion-slide>
          <ion-slide>

3

          </ion-slide>
        </ion-slides>
      Dismiss Modal
    </ion-content>
      `;

    // listen for close event
    const button = element.querySelector('a');
    button.addEventListener('click', () => {
      modalController.dismiss();
    });

    // present the modal
    const modalElement = await modalController.create({
      component: element
    });
    return modalElement;
  }

Other information:

Ionic info:

insert the output from ionic info here

same here
no matter   or , the issue persistent.
@ionic/angular 4.0.2

+1

+1

+1

I've got the same issue. Just on Android though, iOS is working fine.

Better solution, use Ionic lifecycle hook:
ionViewDidEnter() {
    this.showSlides = true;
}

It's more clear what the code is trying to accomplish rather than arbitrary timeouts.

Better solution, use Ionic lifecycle hook:
ionViewDidEnter() {
    this.showSlides = true;
}

It's more clear what the code is trying to accomplish rather than arbitrary timeouts.

In my case that was a fix:
import { IonSlides } from '@ionic/angular';

@ViewChild(IonSlides, { static: true }) slides: IonSlides;

ngOnInit() {
  this.slides.update();
}

Save my day :)

Thank you very match!!!!)))

Better solution, use Ionic lifecycle hook:
ionViewDidEnter() {
    this.showSlides = true;
}

It's more clear what the code is trying to accomplish rather than arbitrary timeouts.

In my case that was a fix:
import { IonSlides } from '@ionic/angular';

@ViewChild(IonSlides, { static: true }) slides: IonSlides;

ngOnInit() {
  this.slides.update();
}

Save my day :)

I'm using slides in a modal view to make pictures zoomable. On a page where multiple pictures, each picture opens a modal with ion slides in it. Slides work well with first open, but after the first open on the same page, slides were let me swipe into empty - out of the screen with no content.
Your fix worked.
Thanks

Hi everyone,
Is this still an issue with the latest version of Ionic Framework? If so, can you please provide a repo with the code required to reproduce the issue?
Thanks!

@liamdebeasi We encountered this today in a project using @ionic/angular: 5.0.4. The workaround worked, but I had to change @ViewChild('comp', { static: true }) to @ViewChild('comp', { static: false }). Unfortunately I can't share the code :/

Hi,
This is work for me:
`import {ViewChild, AfterViewChecked} from '@angular/core';
...........................................
export class ModalPage implements OnInit, AfterViewChecked {
@ViewChild(IonSlides, { static: false }) slides: IonSlides;
............................
ngAfterViewChecked(): void {
this.slides.update(); // This will update slide after view checked
}
`


"provider network not in network entries

can you provide more details?

what network are you trying to connect to (e.g. eth, arbitrum, polygon)?
what command is triggering this error?
what OS + OS version + python version are you using?


docs: Add Scoop installation info to README

Description

This PR adds Scoop installation instructions to the README as Bruno was just added to the Scoop package manager. See #310 and https://github.com/ScoopInstaller/Extras/pull/11970 for details. I might also make a PR for the website too.
Contribution Checklist:

[x] The pull request only addresses one issue or adds one feature.
[x] The pull request does not introduce any breaking changes
[x] I have added screenshots or gifs to help explain the change if applicable.
[x] I have read the contribution guidelines.
[x] Create an issue and link to the pull request.

Note: Keeping the PR small and focused helps make it easier to review and merge. If you have multiple changes you want to make, please consider submitting them as separate pull requests.
Publishing to New Package Managers
Please see here for more information.

Should I make edits to the other language versions too (since I'm just editing the commands I won't need to know the language)?

Thanks @tech189 !


cache store max-age header is not working

Hi team,
I moved this from here: https://github.com/MicrosoftDocs/azure-docs.de-de/issues/598
@hendriksteinhorst commented 7 hours ago
Using the code snipped for the max-age calculation in the cache store policy does not work for me. If the cache misses I get the following result:
"message": "Cache lookup resulted in a miss. Cache headers listed below were removed from the request to prompt the backend service to send back a complete response.",
"cacheKey": omitted for brevity,
"cacheHeaders": [
{
"name": "Cache-Control",
"value": "max-age=10"
}
]
This means the Cache-Control header is removed from the request. The script
<cache-store duration="@{
var header = context.Response.Headers.GetValueOrDefault("Cache-Control","");
var maxAge = Regex.Match(header, @"max-age=(?\d+)").Groups["maxAge"]?.Value;
return (!string.IsNullOrEmpty(maxAge))?int.Parse(maxAge):300;
}"
/>
does not find the Cache-Control header and uses the default of 300 seconds.
Am I missing something?

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

ID: 181c69b0-e136-426b-02f5-4a1a8f0f419d
Version Independent ID: 2e57c2f1-fc01-17c9-cd94-920b582e6aa2
Content: Azure API Management caching policies
Content Source: articles/api-management/api-management-caching-policies.md
Service: api-management
GitHub Login: @vladvino
Microsoft Alias: apimpm

@CeciAc Thanks for  reaching out. We will review and update as appropriate.

@hendriksteinhorst , I am sorry for the extreme delay in my response.
If you are using Consumption tier in Azure API Management, the internal cache in not available for this tier and external Redis-compatible cache should be used instead.

@hendriksteinhorst, We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and tag me in your response and we will gladly continue the discussion.


Add database storage backend

A database will be required to run Grafeas in anything but development mode.

We would get a lot of flexibility for querying various metadata by using Elastic (https://github.com/elastic/elasticsearch) in development go client: https://github.com/elastic/go-elasticsearch

Sounds like a good idea.
Any ideas on type of database? Normalizating all those nested fields will be messy and require lots of join ops during querying so if we go the SQL route (which seems reasonable to me) it’s probably a good idea to store some of the data in serialized form.

PostgreSQL would be a good option, as we could use the built in [text search] (https://www.postgresql.org/docs/current/static/textsearch-features.html) if we parse incoming protos into documents.
We could then store fields required for get/indexing as well as the bytes of the proto, while indexing the proto into a ts_vector in our table.

Maybe the JSON support in PostgreSQL could be of interest as well? I have not used it myself (and I'm not sure how it interacts with the text search features) so it would be interesting to hear what others have to say about it.


update readme.md

Added project overview.
Added configuration details for RiakCS.
Reformatted text to make it more clear.

Thanks @boddumanohar this is awesome. I also added some more details in your overview section.

closes #43


Graph visualization error

Hello.
I am trying the Using CBOW to embed Cora python notebook (linked) and after replacing "CBOWEnsmallen" with "DeepWalkCBOWEnsmallen", the first order embedding runs successfully but fails at the graph visualization. I get the following error:
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
/tmp/ipykernel_3453/3695275499.py in <module>
----> 1 GraphVisualizer(
      2     graph,
      3     node_embedding_method_name="CBOW - First order"
      4 ).fit_and_plot_all(first_embedding)

~/anaconda3/lib/python3.9/site-packages/embiggen/visualizations/graph_visualizer.py in fit_and_plot_all(self, node_embedding, number_of_columns, show_letters, include_distribution_plots, **node_embedding_kwargs)
   4236         distribution_plot_methods_to_call = []
   4237
-> 4238         if not self._graph.has_constant_non_zero_node_degrees():
   4239             node_scatter_plot_methods_to_call.append(
   4240                 self.plot_node_degrees,

AttributeError: The method 'has_constant_non_zero_node_degrees' does not exists, did you mean one of the following?
* 'has_constant_edge_weights'
* 'get_non_zero_subgraph_node_degrees'
* 'has_nodes'
* 'has_edges'
* 'has_selfloops'
* 'has_node_ontologies'
* 'has_node_oddities'
* 'get_node_degrees'
* 'has_node_name'
* 'has_node_types'

Looks like the issue has to do with embiggen dependencies in the graph visualization. Below are the package versions I am using:
embiggen==0.11.13
ensmallen==0.8.7
grape==0.1.9
As well, I was not able to successfully run the second-order embeddings
model = DeepWalkCBOWEnsmallen(
    return_weight=2.0,
    explore_weight=0.1
)
second_embedding = model.fit_transform(graph).get_node_embedding_from_index(0)

The above code gives the below error:
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
/tmp/ipykernel_3453/3112314827.py in <module>
----> 1 model = DeepWalkCBOWEnsmallen(
      2     return_weight=2.0,
      3     explore_weight=0.1
      4 )
      5 second_embedding = model.fit_transform(graph).get_node_embedding_from_index(0)

TypeError: __init__() got an unexpected keyword argument 'return_weight'```

Thank you for the clear issue!
The issue boils down to a not up-to-date jupyter notebook; I have now inserted the execution of jupyter notebooks in the test suite to avoid such things from happening again.
I expect to make available the update Jupiters by later this afternoon (central European time).

To keep you posted, I am currently rendering the Jupyter Notebooks. I had to solve some cross-browser compatibility issues to integrate the animated embeddings, which took far more than I had hoped.
If everything goes smoothly, I expect to push them online later today or tomorrow.

Hello and sorry for the delay! The reported issue is solved in the current version of 🍇, namely the 0.1.10.
Furthermore, I have updated and extended the available tutorials in this directory.

I assume the error is no more since I have tested all tutorials. Please feel free to reopen the issue if that is not the case.


ExtraAttributes is not clear

File: engine/admin/logging/log_tags.md, CC @mstanleyjones
Is it supposed to refer to the environment?
I find it odd how these tags don't make to docker inspect output.

Hi @kaihendry, I am not sure what you mean by "Is it supposed to refer to the environment".
Logging tags are just a way for you to tweak the logging output, using a combination of strings and specific templates that are documented at https://docs.docker.com/engine/admin/logging/log_tags/.
The tags configured for a given container should show up in docker container inspect output for that container, along with any other logging options. Can you provide the command you are using to start the container, where the logging tag info is not showing up? Here is an example of setting a tag on a container:
$ docker run --rm -itd --log-driver journald --log-opt tag="foo" alpine ash
e8e62cc2865720280484e90256964d26918d10a35e4a0232f331c568424da44a

$ docker inspect e8e62cc2865720280484e90256964d26918d10a35e4a0232f331c568424da44a

[
    {
        "Id": "e8e62cc2865720280484e90256964d26918d10a35e4a0232f331c568424da44a",
        "Created": "2017-11-10T00:10:34.593871323Z",
        "Path": "ash",
        "Args": [],
        "State": {
            "Status": "running",
            "Running": true,
            "Paused": false,
            "Restarting": false,
            "OOMKilled": false,
            "Dead": false,
            "Pid": 18477,
            "ExitCode": 0,
            "Error": "",
            "StartedAt": "2017-11-10T00:10:34.992488732Z",
            "FinishedAt": "0001-01-01T00:00:00Z"
        },
        "Image": "sha256:76da55c8019d7a47c347c0dceb7a6591144d232a7dd616242a367b8bed18ecbc",
        "ResolvConfPath": "/var/lib/docker/containers/e8e62cc2865720280484e90256964d26918d10a35e4a0232f331c568424da44a/resolv.conf",
        "HostnamePath": "/var/lib/docker/containers/e8e62cc2865720280484e90256964d26918d10a35e4a0232f331c568424da44a/hostname",
        "HostsPath": "/var/lib/docker/containers/e8e62cc2865720280484e90256964d26918d10a35e4a0232f331c568424da44a/hosts",
        "LogPath": "",
        "Name": "/jolly_babbage",
        "RestartCount": 0,
        "Driver": "aufs",
        "MountLabel": "",
        "ProcessLabel": "",
        "AppArmorProfile": "docker-default",
        "ExecIDs": null,
        "HostConfig": {
            "Binds": null,
            "ContainerIDFile": "",
            "LogConfig": {
                "Type": "journald",
                "Config": {
                    "tag": "foo"
                }
            },
            "NetworkMode": "default",
            "PortBindings": {},
            "RestartPolicy": {
                "Name": "no",
                "MaximumRetryCount": 0
            },
            "AutoRemove": true,
            "VolumeDriver": "",
            "VolumesFrom": null,
            "CapAdd": null,
            "CapDrop": null,
            "Dns": [],
            "DnsOptions": [],
            "DnsSearch": [],
            "ExtraHosts": null,
            "GroupAdd": null,
            "IpcMode": "",
            "Cgroup": "",
            "Links": null,
            "OomScoreAdj": 0,
            "PidMode": "",
            "Privileged": false,
            "PublishAllPorts": false,
            "ReadonlyRootfs": false,
            "SecurityOpt": null,
            "UTSMode": "",
            "UsernsMode": "",
            "ShmSize": 67108864,
            "Runtime": "runc",
            "ConsoleSize": [
                0,
                0
            ],
            "Isolation": "",
            "CpuShares": 0,
            "Memory": 0,
            "NanoCpus": 0,
            "CgroupParent": "",
            "BlkioWeight": 0,
            "BlkioWeightDevice": null,
            "BlkioDeviceReadBps": null,
            "BlkioDeviceWriteBps": null,
            "BlkioDeviceReadIOps": null,
            "BlkioDeviceWriteIOps": null,
            "CpuPeriod": 0,
            "CpuQuota": 0,
            "CpuRealtimePeriod": 0,
            "CpuRealtimeRuntime": 0,
            "CpusetCpus": "",
            "CpusetMems": "",
            "Devices": [],
            "DeviceCgroupRules": null,
            "DiskQuota": 0,
            "KernelMemory": 0,
            "MemoryReservation": 0,
            "MemorySwap": 0,
            "MemorySwappiness": -1,
            "OomKillDisable": false,
            "PidsLimit": 0,
            "Ulimits": null,
            "CpuCount": 0,
            "CpuPercent": 0,
            "IOMaximumIOps": 0,
            "IOMaximumBandwidth": 0
        },
        "GraphDriver": {
            "Data": null,
            "Name": "aufs"
        },
        "Mounts": [],
        "Config": {
            "Hostname": "e8e62cc28657",
            "Domainname": "",
            "User": "",
            "AttachStdin": false,
            "AttachStdout": false,
            "AttachStderr": false,
            "Tty": true,
            "OpenStdin": true,
            "StdinOnce": false,
            "Env": [
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
            ],
            "Cmd": [
                "ash"
            ],
            "Image": "alpine",
            "Volumes": null,
            "WorkingDir": "",
            "Entrypoint": null,
            "OnBuild": null,
            "Labels": {}
        },
        "NetworkSettings": {
            "Bridge": "",
            "SandboxID": "ab3ccf663272135eb9eac8e4968dc061eea6ec138976f93f644ca8a04940436c",
            "HairpinMode": false,
            "LinkLocalIPv6Address": "",
            "LinkLocalIPv6PrefixLen": 0,
            "Ports": {},
            "SandboxKey": "/var/run/docker/netns/ab3ccf663272",
            "SecondaryIPAddresses": null,
            "SecondaryIPv6Addresses": null,
            "EndpointID": "98609099ca4382464db77fb5f10d7063bdaf757f6541fb459f26a891acc9457c",
            "Gateway": "<IP_ADDRESS>",
            "GlobalIPv6Address": "",
            "GlobalIPv6PrefixLen": 0,
            "IPAddress": "<IP_ADDRESS>",
            "IPPrefixLen": 16,
            "IPv6Gateway": "",
            "MacAddress": "02:42:ac:11:00:02",
            "Networks": {
                "bridge": {
                    "IPAMConfig": null,
                    "Links": null,
                    "Aliases": null,
                    "NetworkID": "519df30369f60e6a24f2577dba39c4176483f5454048888549a7cab14f601a09",
                    "EndpointID": "98609099ca4382464db77fb5f10d7063bdaf757f6541fb459f26a891acc9457c",
                    "Gateway": "<IP_ADDRESS>",
                    "IPAddress": "<IP_ADDRESS>",
                    "IPPrefixLen": 16,
                    "IPv6Gateway": "",
                    "GlobalIPv6Address": "",
                    "GlobalIPv6PrefixLen": 0,
                    "MacAddress": "02:42:ac:11:00:02",
                    "DriverOpts": null
                }
            }
        }
    }
]

Here is an exerpt which shows exactly what you should be looking for, to see your tags in the docker inspect output:
<snip>
"LogConfig": {
    "Type": "journald",
    "Config": {
        "tag": "foo"
    }
},
</snip>

If you have more questions about your specific set-up, you might want to ask on https://forums.docker.com/. Thanks!

FYI we are actually pulling the ExtraAttributes example because that functionality is unclear and is not meant to be used by end users, but by logging driver implementors. See https://github.com/docker/docker.github.io/pull/5278.

I think this feature instead would be really useful for end users that wants for example to customize their awslog stream value with something else other than the few tags available by default, for example add the service/stack name in the format they want


There is a performance difference between audio-separator and UVR_v5.6.0_setup_10_14.exe

UVR GUI takes only 14 seconds, while audio-separator takes 21 seconds
I want to know what is the reason? How can I configure it?

There are so many differences in the overall code it's hard to say.
You're very welcome to investigate, please share your results if you decide to figure it out! 🙏

audio-separator does not separate Vocals and Instrumental correctly.

I don't think that's a fair description, especially if you consider the results from different models.
The model you've chosen there (UVR-MDX-NET-Inst_HQ_3.onnx) is quite old and honestly not worth using these days - try the Roformer models e.g. model_bs_roformer_ep_317_sdr_12.9755.ckpt!
I tested your example file anyway, and you're right, there is a difference in the secondary (Vocals) stem for your input track and that UVR-MDX-NET-Inst_HQ_3.onnx model specifically.
However, the Instrumental stem sounds pretty clean to my ears, so considering UVR-MDX-NET-Inst_HQ_3.onnx is an instrumental focused model, I feel the results are good!
In the dropbox link below are the outputs from separating your track using UVR and audio-separator with the UVR-MDX-NET-Inst_HQ_3.onnx model, and from audio-separator with the model_bs_roformer_ep_317_sdr_12.9755.ckpt model - hopefully that demonstrates that there isn't a general issue with audio-separator!

If vocals is your focus, I'd recommend trying one of the other models I mention in this comment:
https://github.com/nomadkaraoke/python-audio-separator/issues/121#issuecomment-2389911649
But overall, my original response still stands; you're very welcome to investigate and raise a PR if you see something worth fixing!
I can't guarantee that my code is identical to UVR or that it produces identical results to UVR, that was never the intention. Getting good enough results for the majority of use cases was my goal, and I believe I've achieved that as many people are now happily using this library on a day-to-day basis including me 😄

Due to work needs, I need to use the UVR-MDX-NET series model

If "work" is paid work, then either you or some other engineer working for your employer should do the work of finding and fixing whatever problem you have.
This is a free and open source software project - I do not get paid, and I have very limited free time to work on a wild goose chase for free for some other company.
You have full access to fix the problem yourself and raise a PR.
If you decide you or another engineer is going to try and tackle the problem you are having, I am happy to schedule a zoom/google meet call and talk you through the code, try to help you get up to speed.

FYI @OneSeven to answer your previous question:

In your experience which model is the best for separating Instrumental?

I've just written up a full answer to that, here: https://github.com/nomadkaraoke/python-audio-separator/discussions/133
Hope it helps! 🙏


chore: add requests and limits to initContainer

Avoids issues with Gatekeeper policies rejecting workloads that do not specify resource requests.
Note - the scheduler should not be affected, as the maximum of initContainers and containers is considered the effective request amount.
Also fixes a minor nit where we were setting the wrong container requests from the values file. We rename "collector" values to "prometheus" and fix the incorrect mapping in our helm charts.

Yea - I may hold off on merging. For some reason E2E tests are timing out with this change...


ISY Component incorrectly detects light as fan

#Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.62 (havent tested 0.61)
Python release (python3 --version):
3.6 - from official docker container
Component/platform:
ISY
Description of problem:
Fanlinc's are a composite device that handle a fan as well as a light. ISY presents each device properly as its own device; however, since 0.62 (or probably 0.61), HASS is now importing these 2 objects as two fans. I believe the PR that caused this #11243. I am running ISY 4.6.2
Expected:
I should have 1 fan and 1 light.
Problem-relevant configuration.yaml entries and steps to reproduce:

Traceback (if applicable):

Additional info:

I'm seeing the same output on my /rest/nodes... sub 1 is the light, sub 2 is the fan. Happy to pull any other info that'll help.

14 A8 63 1
Master FanLinc-Light
<IP_ADDRESS>
true
0
0
0
0
0
14 A8 63 1
A16

14 A8 63 2
Master FanLinc-Motor
<IP_ADDRESS>
true
0
0
0
0
0
14 A8 63 1
B01

@koolsb - what version of ISY are you running?

Thanks for the reports everyone
I am planning on doing some work on this over the weekend and hopefully get the PRs up for the next release. I can already see how to solve the FanLinc issue based on those nodes you provided :)
@boojew: You're both on 4.x because you don't have NodeDefs :)

Awesome. Would running 5.0.x solve this bug?

From: Greg Laabs<EMAIL_ADDRESS>Sent: Friday, February 9, 2018 4:14:20 PM
To: home-assistant/home-assistant
Cc: boojew; Mention
Subject: Re: [home-assistant/home-assistant] ISY Component incorrectly detects light as fan (#12030)
Thanks for the reports everyone
I am planning on doing some work on this over the weekend and hopefully get the PRs up for the next release. I can already see how to solve the FanLinc issue based on those nodes you provided :)
@boojewhttps://github.com/boojew: You're both on 4.x because you don't have NodeDefs :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/home-assistant/issues/12030#issuecomment-364568952, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AA9_Drr6Cp58ncIQgN74GNAnGAEXQjg3ks5tTLUsgaJpZM4Rwns_.

@boojew OverloadUT is correct, I'm on 4.6.2.

@koolsb yea, i should posted here - but I tested w/5.0.11c and yes it does work; however, there are a few issues. See #12327 and #12340
Otherwise, probably not a bad idea to upgrade to 5.0.x. 5.0 has been in beta for the ISY for 2.5 years and I get the impression they are in no rush to change that

Thanks for the reports and example node XML everyone. I have submitted a fix for this issue here: #12421
If you have the know-how to check out that branch and try it on your systems, I would appreciate it! I don't have a FanLinc so I have to go on faith that my changes will work.

@OverloadUT I pulled your new ISY code tonight and looks like we may have overcorrected. Both the fan and light are showing as lights now. Anything code or logs I can pull to assist?

@koolsb Thanks for testing! I see the mistake - we had "medium" spelled out in the filter logic, but the fanlinc only reports "med"
I corrected this in this branch: https://github.com/OverloadUT/home-assistant/tree/fix-fix-isy994-fan-detection
Before I submit the PR, could you give it a shot?

@OverloadUT Tested the new code and no change, both are coming up as lights.
From looking through the code, it looks like the _categorize_nodes function prefers insteon type over uom for identification. Unfortunately both the light and fan show up with the same node type (<IP_ADDRESS>), thus the light identification.
Not a coder myself but I do work in IT and know enough to at least read and understand it :)... so take this for what it's worth... couple thoughts on a fix:
Looking at the home assistant master branch, it previously matched on type 1.46 which is what caused the original issue of both identifying as a fan. Perhaps adding the fan type (1.46) back in the NODE_FILTERS definition and then modifying the _check_for_insteon_type function to have an if statement when 1.46 is detected to do a secondary check on the node address for the last character to distinguish (1 light vs 2 fan)? Another possible solution could be when node type matches 1.46, skip node type identification to force it to use uom?

@koolsb You are 100% correct. I missed the fact that the FanLinc device type weirdly lives inside the "dimmer" device type (1.x) which is what we use to pretty reliably detect which devices are lights.
I was trying to go for a solution that didn't require special casing for this one specific device but it looks like that is going to be unavoidable.
I missed the 0.63.3 cutoff, but I'll work on getting this fixed up for the next release! Thanks for the help with testing and investigation here.

@OverloadUT That did it! Thanks again for all your work on this component!!


Add Import/Export Functionality.

Task:

Add functionality for Data export to Excel file.
Add functionality for Data Importing from Excel files.

Note: Please assign the task to yourself and start working on it.

We can split it into two separate tasks - excel import and excel export.


devices: test devices before collecting on auto discovery

In some scenarios with NVMe, a device might be identified by Ansible but could actually be a multipath device rather than an actual device. We need to exclude these as Ceph cannot create OSDs on them.

jenkins test centos-container-all_in_one

jenkins test centos-container-collocation
jenkins test centos-container-external_clients

jenkins retest this please