Reference links 2 and 3 are reversed

Description
The URL 2 is for ressource 3, and URL 3 is for 2.
(Optional:) Please add any files, screenshots, or other information here.
No response
(Required) What is this issue most closely related to? Select one.
References
Internal issue ID
bec91d12-320d-4813-887a-9a7430539359
Paper URL
https://arxiv.org/html/2409.12676v1
Browser
Chrome/<IP_ADDRESS>
Device Type
Android

Hi @lrobert69 could you show one example URL where this is the case?
Also, is this the same as in the PDF? If the mistake is in the article's source, you should contact the authors for a correction.
This space only tracks issues with the HTML format of the article.

You are right, it's a simple error in the content, an inversion in the
references at the bottom of the article. So it's not really important.
Le ven. 4 oct. 2024 à 17:47, Deyan Ginev @.***> a
écrit :

Hi @lrobert69 https://github.com/lrobert69 could you show one example
URL where this is the case?
Also, is this the same as in the PDF? If the mistake is in the article's
source, you should contact the authors for a correction.
This space only tracks issues with the HTML format of the article.
—
Reply to this email directly, view it on GitHub
https://github.com/arXiv/html_feedback/issues/2238#issuecomment-2393996288,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADC5ZZWB62F7F2INVOZL5TZZ22BTAVCNFSM6AAAAABPKEGBZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJTHE4TMMRYHA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Adding author info to the osci2023

Description
I follow Ashwin's guide and adding my info on the osci2023 folder
Issues Resolved
Finished Day2 and my first PR
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.

Additionally, please do the following two things to signoff on the commits missing signoff:

In your local branch, run: git rebase HEAD~1 --signoff
Force push your changes to overwrite the branch: git push --force-with-lease origin main

@TrungBui59 not seeing the changes to short_name just yet. Once those are in we can merge. Thank you!

Closing as still missing DCO


2.3.1 release

Ready when all other issues forming part of the release are Done.

[x] merge dev/release-x.y.z to master
[ ] await release of https://github.com/xunit/xunit/issues/1611
[ ] tag master
[ ] smoke test package
[ ] convert tag to GH release
[ ] push package
[ ] tweet, mentioning contributors
[ ] post tweet in Gitter
[ ] increment patch version on dev
[ ] create next milestone
[ ] update samples/raise issue
[ ] close this milestone
[ ] raise PR's to consumers:

[ ] 3rd party:

[ ] https://github.com/agartee/Brickweave
[ ] https://github.com/config-r/config-r
[ ] https://github.com/DSilence/MiniPie
[ ] https://github.com/KallynGowdy/ReactiveUI.Routing
[ ] https://github.com/scriptcs/scriptcs

[ ] other:

[ ] https://github.com/adamralph/liteguard
[ ] https://github.com/adamralph/simple-exec
[ ] https://github.com/FakeItEasy/FakeItEasy
[ ] https://github.com/xbehave/xbehave.net-samples

Changing to 2.4.0, since https://github.com/xunit/xunit/issues/1611 will be released no sooner than xunit 2.4.0. See https://github.com/xunit/xunit.analyzers/pull/92#pullrequestreview-98815686


Show-Off-Gif at top of Readme.MD

We have a great logo, a great tag line, but no show off gif.
We need a GIF showing a complex and useful solidarity check in a project.  The output of a --verbose perhaps?
As plugins and new features enter Solidarity, we should add to the gif.

Thoughts @derekgreenberg ?


Fix tag parsing

This PR fixes #5380  and #5381.
I've added a new type to the test package, which allows for more robust testing by validating that the tags you specify in your expected case are what you get from the processed point. Prior to this the bugs were being introduced to the expected tags values because one had to use point.Tags() to retrieve them.
Heads up: anywhere that skips a buffer by two places when the current byte is \  (as in if buf[i] == '\\' { i +=2 }) is possibly hiding a bug. I'd be happy to look in more detail at the Points/tags/fields stuff in a couple of weeks when I come on board @jwilder.

@jsternberg Can you take a look as well?
@e-dard Looks good.  Can you update the changelog as well?

@jwilder updated

@jsternberg :+1:

If you can just squash the commits, this looks good to me :+1:

Done

:+1: and merging since @jwilder gave his +1 too.

@e-dard nice fixes! let me know if you find yourself bored over the next two weeks. ;)


Dynamic JavaScript Root Object?

In traditional way we can define the new JS root object using bean definition:
<bean id="myBean" class="mypackage.MyRootClass" parent="baseJavaScriptExtension">
    <property name="extensionName" value="myRootObj"/>
    <property name="serviceRegistry" ref="ServiceRegistry" />
</bean>

and Java class:
public class MyRootClass extends BaseScopableProcessorExtension {
    protected ServiceRegistry serviceRegistry = null;
    public void setServiceRegistry(ServiceRegistry serviceRegistry) {
        this.serviceRegistry = serviceRegistry;
    }
    public String doSomething(){
       return "test";
    }
}

Can we implement this as dynamic extension?

Not out of the box.
Looking at the BaseScopableProcessorExtension, it would appear you can simply register your JS extensions via the javaScriptProcessor bean using the Processor.registerProcessorExtension method.
(use @PostConstruct to initialize a bean)
However, like most Alfresco API's there is no unregister functionality. Meaning you will get a memory leak when undeploying your extension.
Registering a new version will replace the previous implementation, avoiding a leak. So not a huge problem.


cardano-wallet sync error

deplosy cardano-wallet version latest master and running with nix-build -A cardano-wallet-byron.
[cardano-wallet.wallet-engine:Error:37] [2020-08-01 07:51:14.54 UTC] 5180708f: Unexpected error following the chain: ExceptionInLinkedThread ThreadId 389937 DecoderFailure (ChainSync (ByronBlock) (Tip ByronBlock)) ServerAgency TokNext TokCanAwait) (DeserialiseFailure 1015 "Found unknown tag 2 while decoding Block")
sync block by error upon?
what should i do

Do not use cardano-wallet-byron. This version can no longer sync behind the hard fork. It is currently being removed from the repository
Instead, use cardano-wallet-shelley


file_state_unknown errors on Backblaze B2 via S3 backend

Output of restic version
restic 0.14.0 compiled with go1.19.6 on linux/amd64
How did you run restic exactly?

/nix/store/lal3q0sgdhppjnk0ml2lfg0109ibwqk5-restic-0.14.0/bin/restic check --cache-dir=/var/cache/restic-backups-prune

Apr 14 07:37:39 anxi restic[981658]: using temporary cache in /var/cache/restic-backups-prune/restic-check-cache-1558294841
Apr 14 07:37:41 anxi restic[981658]: create exclusive lock for repository
Apr 14 07:37:43 anxi restic[981658]: load indexes
Apr 14 07:37:56 anxi restic[981658]: check all packs
Apr 14 07:38:04 anxi restic[981658]: check snapshots, trees and blobs
Apr 14 07:42:13 anxi restic[981658]: Load(<data/1a8f74b6d4>, 0, 0) returned error, retrying after 552.330144ms: file_state_unknown
Apr 14 07:42:27 anxi restic[981658]: Load(<data/1a8f74b6d4>, 0, 0) returned error, retrying after 1.080381816s: file_state_unknown
Apr 14 07:42:57 anxi restic[981658]: Load(<data/1a8f74b6d4>, 0, 0) returned error, retrying after 1.31013006s: file_state_unknown
Apr 14 07:43:27 anxi restic[981658]: Load(<data/1a8f74b6d4>, 0, 0) returned error, retrying after 1.582392691s: file_state_unknown
Apr 14 07:43:48 anxi restic[981658]: Load(<data/1a8f74b6d4>, 0, 0) returned error, retrying after 2.340488664s: async file read timed out
Apr 14 07:44:24 anxi restic[981658]: Load(<data/1a8f74b6d4>, 0, 0) returned error, retrying after 4.506218855s: file_state_unknown
Apr 14 07:44:47 anxi restic[981658]: Load(<data/1a8f74b6d4>, 0, 0) returned error, retrying after 3.221479586s: file_state_unknown
Apr 14 07:45:18 anxi restic[981658]: Load(<data/1a8f74b6d4>, 0, 0) returned error, retrying after 5.608623477s: file_state_unknown
Apr 14 07:45:39 anxi restic[981658]: Load(<data/1a8f74b6d4>, 0, 0) returned error, retrying after 7.649837917s: async file read timed out
Apr 14 07:46:05 anxi restic[981658]: Load(<data/1a8f74b6d4>, 0, 0) returned error, retrying after 15.394871241s: file_state_unknown
Apr 14 07:46:43 anxi restic[981658]: Load(<data/1a8f74b6d4>, 886, 2693844) returned error, retrying after 507.606314ms: file_state_unknown
Apr 14 07:46:48 anxi restic[981658]: Load(<data/1a8f74b6d4>, 0, 0) returned error, retrying after 656.819981ms: file_state_unknown
Apr 14 07:46:48 anxi restic[981658]: Load(<data/1a8f74b6d4>, 886, 2693844) returned error, retrying after 535.697904ms: file_state_unknown
Apr 14 07:46:53 anxi restic[981658]: Load(<data/1a8f74b6d4>, 886, 2693844) returned error, retrying after 990.739338ms: file_state_unknown
Apr 14 07:46:58 anxi restic[981658]: Load(<data/1a8f74b6d4>, 0, 0) returned error, retrying after 613.543631ms: file_state_unknown
Apr 14 07:46:59 anxi restic[981658]: Load(<data/1a8f74b6d4>, 886, 2693844) returned error, retrying after 1.635001613s: file_state_unknown
Apr 14 07:47:03 anxi restic[981658]: Load(<data/1a8f74b6d4>, 0, 0) returned error, retrying after 880.91342ms: file_state_unknown
Apr 14 07:47:07 anxi restic[981658]: Load(<data/1a8f74b6d4>, 886, 2693844) returned error, retrying after 2.007539076s: file_state_unknown
Apr 14 07:47:09 anxi restic[981658]: Load(<data/1a8f74b6d4>, 0, 0) returned error, retrying after 1.989705391s: file_state_unknown
Apr 14 07:47:14 anxi restic[981658]: Load(<data/1a8f74b6d4>, 886, 2693844) returned error, retrying after 2.728256121s: file_state_unknown
Apr 14 07:47:15 anxi restic[981658]: Load(<data/1a8f74b6d4>, 0, 0) returned error, retrying after 1.779941781s: file_state_unknown
Apr 14 07:47:21 anxi restic[981658]: Load(<data/1a8f74b6d4>, 886, 2693844) returned error, retrying after 4.902931741s: file_state_unknown
Apr 14 07:47:30 anxi restic[981658]: Load(<data/1a8f74b6d4>, 0, 0) returned error, retrying after 4.065212595s: file_state_unknown
Apr 14 07:47:44 anxi restic[981658]: Load(<data/1a8f74b6d4>, 0, 0) returned error, retrying after 7.759814515s: file_state_unknown
Apr 14 07:47:46 anxi restic[981658]: Load(<data/1a8f74b6d4>, 886, 2693844) returned error, retrying after 6.775550206s: file_state_unknown
Apr 14 07:47:56 anxi restic[981658]: Load(<data/1a8f74b6d4>, 0, 0) returned error, retrying after 6.809451431s: file_state_unknown
Apr 14 07:48:02 anxi restic[981658]: Load(<data/1a8f74b6d4>, 886, 2693844) returned error, retrying after 16.05103845s: file_state_unknown
Apr 14 07:48:12 anxi restic[981658]: Load(<data/1a8f74b6d4>, 0, 0) returned error, retrying after 9.0544704s: file_state_unknown
Apr 14 07:48:23 anxi restic[981658]: Load(<data/1a8f74b6d4>, 886, 2693844) returned error, retrying after 26.244032286s: file_state_unknown
Apr 14 07:48:25 anxi restic[981658]: Load(<data/1a8f74b6d4>, 0, 0) returned error, retrying after 23.002952479s: file_state_unknown
Apr 14 07:48:54 anxi restic[981658]: error for tree 1622b937:
Apr 14 07:48:54 anxi restic[981658]:   ReadFull(<data/1a8f74b6d4>): file_state_unknown
Apr 14 07:48:56 anxi restic[981658]: Load(<data/1a8f74b6d4>, 262, 3034078) returned error, retrying after 511.910153ms: file_state_unknown
Apr 14 07:48:58 anxi restic[981658]: Load(<data/1a8f74b6d4>, 255, 3420945) returned error, retrying after 264.151541ms: file_state_unknown
Apr 14 07:49:02 anxi restic[981658]: Load(<data/1a8f74b6d4>, 255, 3420945) returned error, retrying after 493.746208ms: file_state_unknown
Apr 14 07:49:06 anxi restic[981658]: Load(<data/1a8f74b6d4>, 262, 3034078) returned error, retrying after 830.44008ms: file_state_unknown
Apr 14 07:49:15 anxi restic[981658]: Load(<data/1a8f74b6d4>, 262, 3034078) returned error, retrying after 1.659646822s: file_state_unknown
Apr 14 07:49:17 anxi restic[981658]: Load(<data/1a8f74b6d4>, 255, 3420945) returned error, retrying after 651.885326ms: file_state_unknown
Apr 14 07:49:22 anxi restic[981658]: Load(<data/1a8f74b6d4>, 255, 3420945) returned error, retrying after 1.847489509s: file_state_unknown
Apr 14 07:49:26 anxi restic[981658]: Load(<data/1a8f74b6d4>, 262, 3034078) returned error, retrying after 943.516099ms: file_state_unknown
Apr 14 07:49:32 anxi restic[981658]: Load(<data/1a8f74b6d4>, 262, 3034078) returned error, retrying after 3.017312237s: file_state_unknown
Apr 14 07:49:32 anxi restic[981658]: Load(<data/1a8f74b6d4>, 255, 3420945) returned error, retrying after 2.028854286s: file_state_unknown
Apr 14 07:49:38 anxi restic[981658]: Load(<data/1a8f74b6d4>, 255, 3420945) returned error, retrying after 2.556307748s: file_state_unknown
Apr 14 07:49:39 anxi restic[981658]: Load(<data/1a8f74b6d4>, 262, 3034078) returned error, retrying after 3.952926012s: file_state_unknown
Apr 14 07:49:49 anxi restic[981658]: Load(<data/1a8f74b6d4>, 255, 3420945) returned error, retrying after 5.946792287s: file_state_unknown
Apr 14 07:50:01 anxi restic[981658]: Load(<data/1a8f74b6d4>, 262, 3034078) returned error, retrying after 4.43384419s: file_state_unknown
Apr 14 07:50:09 anxi restic[981658]: Load(<data/1a8f74b6d4>, 255, 3420945) returned error, retrying after 7.886460409s: file_state_unknown
Apr 14 07:50:26 anxi restic[981658]: Load(<data/1a8f74b6d4>, 262, 3034078) returned error, retrying after 8.80426156s: file_state_unknown
Apr 14 07:50:33 anxi restic[981658]: Load(<data/1a8f74b6d4>, 255, 3420945) returned error, retrying after 9.656209421s: file_state_unknown
Apr 14 07:50:48 anxi restic[981658]: Load(<data/1a8f74b6d4>, 262, 3034078) returned error, retrying after 10.02194025s: file_state_unknown
Apr 14 07:51:14 anxi restic[981658]: Load(<data/1a8f74b6d4>, 255, 3420945) returned error, retrying after 24.76915092s: async file read timed out
Apr 14 07:51:47 anxi restic[981658]: Load(<data/1a8f74b6d4>, 262, 3034078) returned error, retrying after 16.565348898s: file_state_unknown
Apr 14 07:51:49 anxi restic[981658]: error for tree 6c671d21:
Apr 14 07:51:49 anxi restic[981658]:   ReadFull(<data/1a8f74b6d4>): file_state_unknown
Apr 14 07:52:19 anxi restic[981658]: error for tree c5fd4c7f:
Apr 14 07:52:19 anxi restic[981658]:   ReadFull(<data/1a8f74b6d4>): file_state_unknown
Apr 14 07:52:19 anxi restic[981658]: [14:14] 100.00%  219 / 219 snapshots
Apr 14 07:52:19 anxi restic[981658]: Fatal: repository contains errors

What backend/server/service did you use to store the repository?
S3 backend w/ a Backblaze B2 repository.
Expected behavior

I understand that restic is reporting read errors with the repository.  I've manually accessed Backblaze B2 through the B2 console and I've successfully been able to read and download the data/1a/1a8f74b6d4... file.  Therefore, I'd expect restic to be able to read it as well.
Actual behavior

restic check fails making me fear that my repository is corrupt.
Steps to reproduce the behavior

I don't know.  At this point, I've retried the check operation four times over about 24 hours, and it has occurred consistently for me.  But that isn't a useful step to reproduce it.
Do you have any idea what may have caused this?
It has been working fine in this configuration for months.  I suppose my best guess is that B2 is rate-limiting access and that's causing restic to show errors, but I don't have any data to support this.
Do you have an idea how to solve the issue?
Possibly having longer timeout periods for intermittent/unknown errors?  Possibly more logging information about the nature of the error to allow debugging backend problems?
Did restic help you today? Did it make you happy in any way?

restic is a fantastic tool.
I'm sorry for my poor bug report here -- I know it's not a "bug", but I don't know what to do other than to reach out in this way to try to get help understanding the logs and figuring out next steps.

The file_state_unknown and async file read timed out are errors that were returned by B2. That is, these problems are the result of an (temporary) problem at the B2 servers.

I suppose my best guess is that B2 is rate-limiting access and that's causing restic to show errors, but I don't have any data to support this.

A rate-limit would result in a different error message.

I've manually accessed Backblaze B2 through the B2 console and I've successfully been able to read and download the data/1a/1a8f74b6d4... file. Therefore, I'd expect restic to be able to read it as well.

The B2 console is likely not using the S3 interface. That is, it looks like a  problem of the B2's S3 interface. You could try whether you are able to access the problematic file using the S3 backend of rclone or some other tool. But if the problem persists, please contact the B2 support.

Possibly more logging information about the nature of the error to allow debugging backend problems?

More logging would definitely be useful. Right now, the only option to learn more details is to create a debug log by setting the DEBUG_LOG=logfile.log environment variable, but that is very verbose.

After another 12hr, I retried this check operation and it passed, which is consistent with it being a temporary problem at the B2 side.  I'll close this report then, as the restic behavior seems appropriate considering the state.
Thanks!


C/wavelets

I am going to close this as stale. In order for this is to be considered, you will need to provide some description of what this new wavelet is and why it should be included. We are only likely to accept very well established wavelets that are common in the literature.


Add potential authentication mechanism for port 8091 of Seata Server

Why you need it?
Is your feature request related to a problem? Please describe in details

I noticed something strange when trying to improve the unit test execution time of https://github.com/apache/shardingsphere/blob/5.5.1/test/native/src/test/java/org/apache/shardingsphere/test/natived/jdbc/transactions/base/SeataTest.java .
For the 7091 port of Seata Server, there is an authentication mechanism that requires users to log in with the account of seata and the password of seata.
But for the 8091 port of Seata Server, it seems that there is no authentication mechanism. Any Seata Client can directly connect to the 8091 port of Seata Server. This does not seem to change anything because Seata Server switches to Nacos's configuration center or registration center. After Seata Client connects to Nacos Server, it still needs to directly access port 8091 of Seata Server.
I know that Seata Server should be deployed in an intranet environment, but in this case, the authentication of Seata Server's port 7091 seems redundant. Docker Images like keycloak, zitadel, and nginx can quickly add authentication functions to Seata Server's port 7091.
A potential understanding is that the docker imager of the seata server should allow the passing of environment variables like SEATA_SERVER_SECRET_TOKEN="yourStrongPassword123!", and the configuration file registry.conf of the seata client allows the setting of content like seata.server.secret_token="yourStrongPassword123!". To ensure communication security, Seata Server may also support the generation of self-signed TLS certificates or custom TLS certificates.
Or another possibility is to support JVM arguments like Zookeeper Server does which reads JAAS java.security.auth.login.config. Like https://shardingsphere.apache.org/elasticjob/current/cn/user-manual/configuration/external-integration/sasl/ does.

services:
  zookeeper-test:
    image: zookeeper:3.9.2
    volumes:
      - ./jaas-server-test.conf:/jaas-test.conf
    environment:
      JVMFLAGS: "-Djava.security.auth.login.config=/jaas-test.conf"
      ZOO_CFG_EXTRA: "authProvider.1=org.apache.zookeeper.server.auth.SASLAuthenticationProvider sessionRequireClientSASLAuth=true"
    ports:
      - "2181:2181"

Server {
    org.apache.zookeeper.server.auth.DigestLoginModule required
    user_bob="bobsecret";
};

How it could be?
A clear and concise description of what you want to happen. You can explain more about input of the feature, and output of it.

https://github.com/apache/incubator-seata/wiki/20240427/57e39735794787dd5d6a6975ce80421ecde7e6c6 seems to mention this requirement, but I can't find the corresponding PR.

According to multiple CVEs in the history of ElasticSearch, an authentication that does not support the configuration of TLS certificates does not seem to be secure enough.

Other related information
Add any other context or screenshots about the feature request here.

Null.

@funky-eyes Given that PR already exists, should I close the current issue to avoid misunderstandings?

Yes, we can close this issue because I found the latest progress in the PR: https://github.com/apache/incubator-seata/pull/6913. We can discuss it there


Revert "Remove incorrect has_lookup=False for JndiLookup.class"

Reverts fox-it/log4j-finder#36
The old behaviour was actually correct, when there is a KeyError, it means no JndiLookup.class file is found. However the KeyError was also triggered due to non posix paths on Windows, that is now fixed in #37.

This incorrect patch was reverted, see also #35


mangastream is now using readms.net

therefore script does not work anymore

You mean MangaStream*

Adding readms to the script does make it work somewhat but there are indeed issues (for example the new issue for some reason has every page in it try to load the first page from 2 chapters prior and then the script breaks)

I've fixed it in a pull request that @anka-213 has yet to merge. You can check out the raw at https://github.com/lauyuen/webcomic_reader/raw/fd50d5caf4393c00089703ff2cdcb56510626e5e/webcomic_reader.user.js

yeah mangastream* sorry about typo

@Lunarhawk Please submit a new issue for those problems, I'm closing this now.


🚚 Better name for from_values

As discussed, @sunnyosun.

.from_values() now has a create: bool flag that can be switched on if people want to make new records.


Provide metadata service as separate server extension

I'm loving the metadata service inside of elyra!
I'd really like to tap into this extension without installing all of elyra's dependencies. Right now, installing the Python package leads to the installation of a few other server extensions, such as jupyterlab-git and nbdime, because they are required in elyra's setup.py. However, it would be nice to install this extension without these extra dependencies.
One option is to create a new repo and provide the metadata service as a separate PyPI package; the second option is to make these other dependencies optional (though this is likely a problem for the elyra distribution).
Let me know your thoughts. I'd be happy to help move this part of the code out into a separate repo if you think this make sense. Thanks!
cc @kevin-bates

Hi Zach.  I'm curious how you envision using this outside of Elyra?
There are some behaviors with respect to the file hierarchy that are not intuitive.  For example, the precedence for searching for metadata instances is:

User's home directory
System shared directories (/usr/local/...)
Python sys.prefix

while the default Jupyter hierarchy is: 1, 3, 2.
We (Elyra) treat the third location as "factory data" in which the installation of Elyra will place some "system owned" instances.  Updates via the REST API only occur against location 1 (user's home) as there's no way to indicate where the location should be.  As a result, the other locations will appear in retrievals, only in the event there isn't the same-named instance in a prior directory.  Since there's been discussion of changing the Jupyter path hierarchy, I'm beginning to think "factory data" should be included in the package installation location and require one-off logic for retrievals [*].
For example, if I go to 'update' one of the factory items located in sys.prefix, the result of that update will be placed into the hierarchy located within my home directory.  All subsequent retrievals will pull that instance, essentially masking out the instance in sys.prefix.
[*]: This model will also need to be revisited when adding support for other forms of persistence (namely NoSQL DBs).  This way, the same one-off logic for retrievals of factory data could be utilized irrespective of persistence forms.
Hmm, but if we split out metadata as it's own thing, the notion of "factory data" will need to be revisited entirely. (Which isn't such a bad idea IMHO. :smile: )

Hi Zach. I'm curious how you envision using this outside of Elyra?

My immediate reason is that our "code-snippets" team (@jupytercalpoly) is building a stand-alone code-snippets extension on top of Elyra's metadata service backend (i.e. using the metadata service for validating+storing snippets). Their plan is to work in a sandbox, outside of Elyra, for a little while and contribute upstream later when they make some progress.
The issue is that they can't install the metadata service without getting all of Elyra's dependencies. Further, Elyra doesn't include a code-snippets directory/namespace in the user's jupyter paths by default. Instead this directory has to be manually created by the user. To circumvent this, we had to create a middle-man python package that creates this directory when their extension is installed.
I see what you're saying about jupyter paths, though. It seems to me that you might want to separate the logic for where the extension's data files get placed from the extension's source. In this case, Elyra could become a mono-package (is that a thing? ... I'm thinking like a monorepo) with its own setup.py that depends on the metadata service package, but handles the placement of its data files, putting them in the custom "system owned" locations. Other Jupyter deployments/distributions/suites can the ship this metadata service separate from Elyra and decide where to place these data files in their context.
cc'ing @kpinnipa  and @jahn96, our interns working on this project, to watch this thread.

Elyra doesn't include a code-snippets directory/namespace in the user's jupyter paths by default. Instead this directory has to be manually created by the user. To circumvent this, we had to create a middle-man python package that creates this directory when their extension is installed.

Hmm - No Elyra namespaces are created until first use.  Namespaces are known to Elyra, but don't exist until metadata is installed via the CLI tool, or created via POST to /elyra/metadata/code-snippets.  Here's the CLI tool example (directory /Users/kbates/Library/Jupyter/metadata did not exist prior to this call):
~/Library/Jupyter/metadata$ elyra-metadata install code-snippets --schema_name=code-snippet --name=foo --display_name=Foo --language=Python --code="['import os']"
Metadata instance 'foo' for schema 'code-snippet' has been written to: /Users/kbates/Library/Jupyter/metadata/code-snippets/foo.json

Their plan is to work in a sandbox, outside of Elyra, for a little while and contribute upstream later when they make some progress.
The issue is that they can't install the metadata service without getting all of Elyra's dependencies.

Why not just work from a fork?  Seems like it would be easier to contribute and adds some time for splitting out the MD service.
One of the things I wanted to do is split the logic as you describe - the place holders are already there - but I just haven't been diligent about honoring that separation.  Most of the logic should move into the base class and I had made a mental note to address that (but mental notes might as well be written on an etch-a-sketch these days :smile: ).  I'm also unsure about the current class hierarchy - which I suspect is a source of that neglect.

Hi @Zsailer,
In development mode, make install-server on the Elyra repo should do what you need.
In a release, we want to simplify the user experience for the user, and thus we drop these extensions into the JupyterLab folder which makes the pip install elyra && jupyter lab build the only thing the user needs to do and that's very useful.
Separating the modules is definitely something we might be open to, but as we are still having a lot of changes on the metadata services, having a separate module might increase the work necessary to make quick progress, as changes on the new module need to be released to be used with the main Elyra repo.
One thing I was thinking about, at least for now,  is to customize the setup.py to allow something like ELYRA_DISABLE_LAB_EXTENSIONS=true pip install elyra which then would only install the backend.

My immediate reason is that our "code-snippets" team (@jupytercalpoly) is building a stand-alone code-snippets extension on top of Elyra's metadata service backend (i.e. using the metadata service for validating+storing snippets). Their plan is to work in a sandbox, outside of Elyra, for a little while and contribute upstream later when they make some progress.

Don't be shy :) we can create a branch for the interns so they can work in 'isolation' and in a more 'stable' environment, which will give them some flexibility to experiment but also provide the real open source experience working with the community.

don't exist until metadata is installed via the CLI tool

Gotcha. I totally missed the CLI tool 🤦 😄.
Our interns were running into this basic issue. They installed Elyra (from source), clicked on the code-snippets icon, and received an error: the code-snippets namespace does not exist—i.e. making a GET /elyra/metadata/code-snippets request before you create the code-snippets namespace throws an error.
It makes sense why this is happening, but it also complicates the setup/install instructions for extensions like code-snippets. I was thinking that each frontend extension should exist as separate Python + JS packages that register their schemas with the metadata service and initialize their own namespace.

Why not just work from a fork? Seems like it would be easier to contribute and adds some time for splitting out the MD service.

Don't be shy :) we can create a branch for the interns so they can work in isolation and in a more stable environment, which will give them some flexibility to experiment but also provide the real open source experience working with the community.

😄 absolutely agree. That's the goal. Right now, they're just doing some initial exploration, learning to write jupyterlab extensions from tutorials, and trying out Elyra at the same time. Once they get more familiar with jupyterlab and begin to work on the extension for real, we'll switch to a fork of Elyra 👍

There isn't a complete solution for this yet, but note that we now publish a elyra-server package to python that has only the elyra backend components. This allows you to deploy individual Elyra extensions to jupyterlab.

I think there are a number of additional functional items for making the metadata service a separate extension as well:

Namespace objects that hold schemas and define storage characteristics
Ability to bring your own namespaces and schemas
Proper definitions for specifying "scopes" or "storage areas" of instances (e.g., user, shared, system) or simplification of the current hierarchy
Addition of some meta-behaviors (e.g., "system-owned", "default-instance")


neo4j-browser  connect to server with wrong address

version: 4.05
running with on a remote host:
docker run \
>     --publish=7474:7474 --publish=7687:7687 \
>     --volume=$HOME/neo4j/data:/data \
>     neo4j

neo4j-browser can login in with initial username/password, but execute any Cypher statement will fail:
e6906fea-5fd6-4ca4-a329-43f60195291c:16 WebSocket connection to 'ws://<IP_ADDRESS>:7687/' failed: Connection closed before receiving a handshake response

I think this is the same issue as #240
Does it work if you start neo4j like this?
docker run -it --rm \
    --publish=7474:7474 --publish=7687:7687 \
	-e NEO4J_dbms_connector_https_advertised__address=":7473" \
	-e NEO4J_dbms_connector_http_advertised__address=":7474" \
	-e NEO4J_dbms_connector_bolt_advertised__address=":7687" \
    neo4j

Since there was no reply I'm going to assume my suggestion worked and this was the same underlying issue as #240 .
Neo4j 4.0.4 has been released and has the fix for the networking problem.


feat: update ApplyBackgroundNoise augmentation

This is a work in progress but I'd love to receive early feedback anyway.

I can take another look when it's out of draft :)

There's a merge conflict, and this is the reason: https://github.com/asteroid-team/torch-audiomentations/pull/50/files#diff-6e77014151191ab9ff2d304e38e00227aacf5f13c96d97b95bb4ace36bf834c1

This PR now fails because tests try to augment 2d samples.
Shouldn't we first come up with a PR that switches to 3d only (as discussed last week in slack)?

This PR now fails because tests try to augment 2d samples.
Shouldn't we first come up with a PR that switches to 3d only (as discussed last week in slack)?

Yes, we should adapt (or remove) tests that currently provide 2d input. We can enforce/assert 3d input in a different pull request.

I tried to run the demo script, and I get an exception like this:
Traceback (most recent call last):
  File "C:/Users/Iver/Code/torch-audiomentations/scripts/demo.py", line 139, in <module>
    samples=samples, sample_rate=SAMPLE_RATE
  File "C:\Users\Iver\Anaconda3\envs\torch-audiomentations-gpu\lib\site-packages\torch\nn\modules\module.py", line 722, in _call_impl
    result = self.forward(*input, **kwargs)
  File "C:\Users\Iver\Code\torch-audiomentations\torch_audiomentations\core\transforms_interface.py", line 189, in forward
    self.randomize_parameters(cloned_samples, sample_rate)
  File "C:\Users\Iver\Code\torch-audiomentations\torch_audiomentations\augmentations\background_noise.py", line 113, in randomize_parameters
    [self.random_background(audio, num_samples) for _ in range(batch_size)]
  File "C:\Users\Iver\Code\torch-audiomentations\torch_audiomentations\augmentations\background_noise.py", line 113, in <listcomp>
    [self.random_background(audio, num_samples) for _ in range(batch_size)]
  File "C:\Users\Iver\Code\torch-audiomentations\torch_audiomentations\augmentations\background_noise.py", line 84, in random_background
    background_path, sample_offset=sample_offset, num_samples=num_samples,
  File "C:\Users\Iver\Code\torch-audiomentations\torch_audiomentations\utils\io.py", line 240, in __call__
    raise ValueError()
ValueError

Somehow the numbers don't add up in this case, and I think it's related to signal and noise having different original sample rates
        # io.py line 239-240
        if original_sample_offset + original_num_samples > original_total_num_samples:
            raise ValueError()

Could you try to run the demo script and see if you can reproduce it?
python -m scripts.demo

LGTM! 🚀
Thanks for the contribution 😄


markdown: add mathjax support

Adds the mathjax-react package and a Math component to display equations. In context, you'd use {% math %} to wrap an equation with an optional block parameter when you want it to be a block, not inline.
Fixes #12
Open questions:

This requires String.raw() to parse strings without assuming we're using backslashes as escapes, or else obviously LaTeX doesn't work. We can't really selectively do this processing, as the first time we pass a string without String.raw(), it seems to escape the slashes. Are there consequences of enforcing String.raw() on every single call of our Markdown parser? (How often are we using backslash escapes in our writing anyway?) Basically I want to test some Markdown processing more before merging.
Obviously the above would be a big breaking change necessitating a major version bump. But does this even meet our needs? @sigilante If you can present some examples of what you'd want processed, it would help assess suitability.

Thus far \sum_{2}^{\longrightarrow \beta}\equiv \beta\beta\beta\beta becomes, well,

Looks like it's sticking with inline form rather than tall form.

Can you elaborate?

The summation sigma should have the values above and below it (you can see this in my examples now) rather than at the side.  That's common for shorthand in running text but not ideal for standalone expressions.

So it is ... let me see .....

Adding \displaystyle seems to do it, but I don't know why it's assuming we're always inline. I need to look at MathJax config options.

Oh wait. I'm dumb. I already had the answer with the block parameter!

{% math block=true %}\sin(x) = \sum_{n=0}^\infty \frac{(-1)^n}{(2n+1)!}x^{2n+1}= x - \frac{x^3}{3!} + \frac{x^5}{5!} -   \frac{x^7}{7!} + \cdots{% /math %}

yes, that looks textbook!

How often are we using backslash escapes in our writing anyway?

just went through all 893 instances of \ in the developer docs:

should be fine (these are the vast majority of backslashes, and are not used as escapes)

inline code
code blocks
the latex image urls
(though i guess you should check just to make sure: inline code (`\n` under Et cetera. heading of jetting.md), code block (> =z ;p(class "\">


Add support for Python 3.13 (10/2024)

Ref: https://peps.python.org/pep-0719/

Not all dependencies are 3.13 ready yet.

Fixed via #169


Run benchmarks after building stuff.

Pull Request Description
As discussed in https://discord.com/channels/401396655599124480/1106814204175978516
Important Notes

Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[x] The documentation has been updated, if necessary.
[x] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[x] All code follows the
Scala,
Java,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
All code has been tested:

[x] Unit tests have been written where possible.
[x] If GUI codebase was changed, the GUI was tested when built using ./run ide build.

@mwu-tow who should review it?

I will complete this today.


Add iconStart and iconEnd to input field

See https://www.figma.com/file/mibA3VIpBm4nyJTsIKtY8o/React---UI-Library?node-id=10%3A1303

@mmalfertheiner These input adornments are a very nice idea. But in this case we have to style the div as if it was an input and place the "invisible" input field inside the div so that it takes the full space between the adornments. The current solution is easier because the icon width is known, so we can work with absolute positioning and input padding.
Should I proceed to implement the adornments solution?

@mmalfertheiner These input adornments are a very nice idea. But in this case we have to style the div as if it was an input and place the "invisible" input field inside the div so that it takes the full space between the adornments. The current solution is easier because the icon width is known, so we can work with absolute positioning and input padding. Should I proceed to implement the adornments solution?

Ok, then leave the icons as they are. We can change that if we need it at a later stage.


Generate marshalling functions for TypeScript models

Reason/Context
In Modelina for TypeScript, you can make it generate the models with marshaling functions and it should also be possible through the CLI.
To do this I suggest we add a flag called tsMarshalling as a boolean. If true the generator should include the following options:
  presets: [
    {
      preset: TS_COMMON_PRESET,
      options: {
        marshalling: true
      }
    }
  ]

Which should be added here: https://github.com/asyncapi/cli/blob/438de0741e9ef29672b6e3af483b90e796903a7d/src/commands/generate/models.ts#L118 as the code example show: https://github.com/asyncapi/modelina/blob/master/examples/typescript-generate-marshalling/index.ts
These will be the generated results: https://github.com/asyncapi/modelina/blob/master/examples/typescript-generate-marshalling/snapshots/index.spec.ts.snap
Remember to also add a test here: https://github.com/asyncapi/cli/blob/438de0741e9ef29672b6e3af483b90e796903a7d/test/commands/generate/models.test.ts#L39
Feel free to reach out if you have any questions or get stuck!

@AayushSaini101 there are no assignments or anything in that way, so it's all about just doing it 😊 Go for it 👍

@AayushSaini101 if you are not doing this i will be adding this change will create a pr shortly

this is being discussed here
https://github.com/asyncapi/cli


Disable k3s embedded containerd process, start k3s-containerd binary as external process

The embedded k3s containerd instance does not allow changing the containerd root path away from a subdirectory of the k3s-data-dir as they specify a root on command line args overriding whatever is in the config.toml file.  So we will disable the embedded k3s containerd process and instead use the k3s supplied containerd binary to start a containerd instance next to k3s (still in the kube container) which will allow us to allow us to change the containerd root.  This containerd instance will re-use the pillar /run/containerd-user/containerd.sock to allow ease of reusing wait-ready code on the pillar side.
Add missing findutils package for longhorn.
Raise io priority for embedded etcd.
Add Pramodhs containerd.go change to skip starting containerd-user in pillar.

I find it surprising that k3s doesn't let you select a different containerd or control the path, as that is the kind of thing they would, but maybe they never got to it.
The two questions I have are:

why do we care? It's all inside of the container or VM anyways, so why do we care?
what do you mean by reusing the pillar containerd socket? That would mean it's talking to the main containerd. Why would we want that?

@deitch
To answer your questions.

We care because we want to download apps using eve download mechanism which is a known secure way and store blobs/images the way we do today. In other words we do not depend on Kubernetes image download mechanism

2)I think Andrew meant that we will be using pillar user containerd not the main containerd.  So basically we will be using /run/containerd-user/containerd.sock that is the socket access point for deployed images.

We care because we want to download apps using eve download mechanism which is a known secure way and store blobs/images the way we do today. In other words we do not depend on Kubernetes image download mechanism

Thanks for the explanation; this definitely helps.
To the best of my knowledge, Kubernetes actually does not have a download mechanism. It depends entirely on the container runtime (in this case, containerd). Either way, pointing k3s at a different containerd doesn't change its download flow. If you ask it to run a pod, and the image is not there, it will use the containerd API (not precisely, but close enough) to download the image. If containerd has network access, it will do so.
This raises an interesting question, which @eriknordmark is likely to know as well. Right now, I do not think our containerd is network-blocked. We do not use it to download - instead we use the volumemgr+downloader+verifier and load it into containerd, and then use containerd to run it. But is containerd actually blocked from downloading? I don't think it is. Maybe we configure it to have no network access, but I am somewhat sure we do not have that.
So pointing at a different containerd does not change the flow. If k3s is asked for a container, it will ask containerd to get that image unless available. Mind, if ImagePullPolicy is set to always, then it always will ask it to pull it.
I think we have some experiments here to determine:

can user containerd pull images directly or is it blocked; ie is it not downloading because we do not use it, or because it cannot?
if it is not used, then what happens if a container has ImagePullPolicy=always? I am almost certain it will try to pull it

we will be using pillar user containerd not the main containerd

We currently have 2 containerd running: system (runs pillar, etc.) and user (runs user workloads, i.e. ECOs). I think you are saying, k3s will add another, which would make it 3. Change it so that it remains only 2, and k3s points at the user containerd managed by pillar?
If that is so, 100% in favour. I still am surprised you cannot just point k3s at an existing containerd, but you did the research, so I must put my surprise aside and accept it.
Summary:

We definitely should use the user containerd, however we get that (this PR ✅ )
We should check if the user containerd is blocked from downloading or just we never happen to use it
If the latter, we need to find a way to ensure k3s doesn't trigger it

@deitch  You brought up good points let me summarize it for you.

Yes k3s supports external containerd,  but k3s ships with a compatible containerd which they test extensively. Hence it is in our best interest to use containerd shipped with k3s. So, basically on kubevirt eve we will not start user containerd from eve and start containerd shipped by k3s but use the same socket endpoint (/run/containerd-user/containerd.sock) and repository location (/persist/vault/containerd) for code compatibility.

Yes containerd itself will not pull the images, it has to be triggered from Kubernetes. But our approach is that eve will always pull the image and make it available for k3s.  And yes we are setting the flag ImagePullPolicy=Never.  If image is not found the app launch will fail. That you will see in different PR. This project will have multiple PRs, we cannot put everything in one PR. We are trying to divide those as independent as possible.

Yes k3s supports external containerd, but k3s ships with a compatible containerd which they test extensively. Hence it is in our best interest to use containerd shipped with k3s. So, basically on kubevirt eve we will not start user containerd from eve and start containerd shipped by k3s but use the same socket endpoint (/run/containerd-user/containerd.sock) and repository location (/persist/vault/containerd) for code compatibility.

That might be a pretty big change. Have we tested the shipped version with everything else that we do that depends on containerd? Version and functionality mismatches? CVEs opened or closed?
It might be fine, but we definitely need to consciously decide, "we are ok switching the specific version we are using".

Yes containerd itself will not pull the images, it has to be triggered from Kubernetes

You can get containerd to pull directly, whether using ctr or the gRPC API from somewhere other than Kubernetes, but we might not here.

But our approach is that eve will always pull the image and make it available for k3s

Yes, makes sense. That has been our philosophy all along.

And yes we are setting the flag ImagePullPolicy=Never

That probably should do it. I think we still should test if containerd has the ability to bypass our downloading. It is pretty simple:

Launch an eve device
Connect to user containerd via ctr
Do an image pull
See what happens

Yes k3s supports external containerd, but k3s ships with a compatible containerd which they test extensively. Hence it is in our best interest to use containerd shipped with k3s. So, basically on kubevirt eve we will not start user containerd from eve and start containerd shipped by k3s but use the same socket endpoint (/run/containerd-user/containerd.sock) and repository location (/persist/vault/containerd) for code compatibility.

That might be a pretty big change. Have we tested the shipped version with everything else that we do that depends on containerd? Version and functionality mismatches? CVEs opened or closed?
It might be fine, but we definitely need to consciously decide, "we are ok switching the specific version we are using".

I am not sure I understood your question correctly. This is a new eve flavor and we will not be upgrading any existing kvm based installs.  This is a new product altogether and we will be starting with containerd that comes with k3s.

Yes containerd itself will not pull the images, it has to be triggered from Kubernetes

You can get containerd to pull directly, whether using ctr or the gRPC API from somewhere other than Kubernetes, but we might not here.

But our approach is that eve will always pull the image and make it available for k3s

Yes, makes sense. That has been our philosophy all along.

And yes we are setting the flag ImagePullPolicy=Never

That probably should do it. I think we still should test if containerd has the ability to bypass our downloading. It is pretty simple:

Launch an eve device
Connect to user containerd via ctr
Do an image pull
See what happens

Yes containerd can pull images if we explicitly ask it to, but as a product we are not doing that and will not do that. No user is logging into the device to do that manually. So basically nothing changes from what we have now.

This is a new eve flavor and we will not be upgrading any existing kvm based installs. This is a new product altogether and we will be starting with containerd that comes with k3s

I wasn't worried about upgrades. We still are releasing a new eve, which has lots of components that depend on that containerd. It likely will be just fine, but we should not change the version or location of a central component in eve without validating first that we are ok.
To put it in other terms: let's say that the current version is 1.7.0, and k3s comes with 1.7.6. We should first check that we are ok with 1.7.6 in place, and then switch. Conversely, if we are running 1.7.6, and k3s is running 1.6.5, then we very well might have compatibility issues.

Yes containerd can pull images if we explicitly ask it to, but as a product we are not doing that and will not do that. No user is logging into the device to do that manually. So basically nothing changes from what we have now

Which is good. We should, however, disable containerd from doing that entirely, as long as that is our philosophy, and not rely on, "we don't do that". This is not an issue for your deliverable here; you just happen to be lucky enough to have brought it to the fore by having another component that communicates with containerd.

I wasn't worried about upgrades. We still are releasing a new eve, which has lots of components that depend on that containerd. It likely will be just fine, but we should not change the version or location of a central component in eve without validating first that we are ok.
To put it in other terms: let's say that the current version is 1.7.0, and k3s comes with 1.7.6. We should first check that we are ok with 1.7.6 in place, and then switch. Conversely, if we are running 1.7.6, and k3s is running 1.6.5, then we very well might have compatibility issues.

I am sorry but this is what I am not getting. We do not run any different user containerd version  in eve. We just run the version that comes with k3s. So the compatibility between k3s and user containerd is always maintained.

Now I am confused. We already install a containerd in eve. Didn't we write above that we will replace that one with the one that comes with k3s?

Now I am confused. We already install a containerd in eve. Didn't we write above that we will replace that one with the one that comes with k3s?

We won't replace the one that that comes with eve. We just do not start the one that comes with eve and start the one that comes with k3s.

That is replacing it. It doesn't matter if we have it on disk or not, it matters if we use it.
Again, it could be fine, but now we are tying our eve containerd version to the k3s one. That is a change - completely independent of k3s usage - that requires testing.
BTW, what happens when we need to upgrade containerd to some version for a feature, if k3s isn't there yet?

That is replacing it. It doesn't matter if we have it on disk or not, it matters if we use it.
Again, it could be fine, but now we are tying our eve containerd version to the k3s one. That is a change - completely independent of k3s usage - that requires testing.
BTW, what happens when we need to upgrade containerd to some version for a feature, if k3s isn't there yet?

This change is only in kubevirt eve and will not effect kvm based eve. So we will be always  using containerd that comes with k3s on kubevirt eve only.  This does not effect our existing kvm eve and the upgrades of it.
Are you concerned about eve containerd client code working with containerd from k3s ? Yes that will be tested, so far we did not see any issue in our testing.

Yes, I am concerned about that. I also am concerned about having variants on eve that change fundamental compatibility components.

Yes, I am concerned about that. I also am concerned about having variants on eve that change fundamental compatibility components.

I will be happy to get on call and learn about your concerns. From my point of view this commit or upcoming commits are no-op on existing eve ie does not change anything. Only changes are in new kubevirt eve.

@deitch
To address the question of containerd versions here are each so it does appear the k3s one is at least one minor version behind.
k3s version:
8c857dec-7cb8-45cb-8e20-a6c7569446c4:/# /var/lib/rancher/k3s/data/current/bin/containerd -v
containerd github.com/k3s-io/containerd v1.6.19-k3s1
existing pillar version:
(ns: pillar) 8c857dec-7cb8-45cb-8e20-a6c7569446c4:/# /usr/bin/containerd -v
containerd github.com/containerd/containerd v1.7.2 0cae528dd6cb557f7201036e9f43420650207b58

@deitch @zedi-pramodh
We're currently on k3s version v1.26.3+k3s1.  If we upgrade to the latest k3s v1.28.2+k3s1 then we'll get a containerd upgrade to v1.7.6-k3s1.

We are opening a Pandora's box (which, ironically, probably wasn't a box, as they didn't really have "boxes" back then 😄 ), in having different versions of containerd on different versions of eve which are almost the same but not quite. That is my concern. We should have eve, with its tested and supported version of its components, and things that plug into it and are tested with it.

I will be happy to get on call and learn about your concern

Sure, let's coordinate offline.

Re-opening from @zedi-pramodh 's request.  We're there any requested changes to this PR from the offline conversation @deitch and @zedi-pramodh ?

Not that I know of @andrewd-zededa.  @deitch reviewed the design document and in general agreed with this approach. But I will leave it to him to review and approve.

Converted to draft since with the merge commits this is clearly not ready for review.

Sorry I'm just closing this to reopen with a cleaner pr, the rebase isn't happening cleanly.


create Sockets.createSocket not working

Whenever I run the application always return this error on the terminal

Hi,
Could you please share the line of code in detail so that I can understand the problem?

This is my component
`import React, { useEffect, useState } from 'react'
import { SamsungRemote, DeviceDiscovery } from '@ersinayaz/rn-samsung-tv-remote';
import { Alert, Text, View } from 'react-native';
const Remote = () => {
const [device, setDevice] = useState({})
useEffect(() => {
handleGetDevices()
}, [])
const handleGetDevices = async () => {
    Alert.alert('Start handleGetDevices')
    const devices = await DeviceDiscovery.discover("urn:samsung.com:device:RemoteControlReceiver:1");
    Alert.alert('after DeviceDiscovery')
    setDevice(devices)
    Alert.alert(JSON.stringify(devices))
    Alert.alert('end handleGetDevices')
}

return (
    <View>
        <Text>Remote</Text>
        <Text>{JSON.stringify(device)}</Text>
    </View>
)

}
export default Remote
`

Can you try installing the following dependencies?
yarn add<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>npx pod-install

restart project.

Hi, are you still having problems?

@soufiansaidi yes Problem solved after I install<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>


Wrong doi of FWHM

On the user manual about IQMs (i.e., http://mriqc.readthedocs.io/en/latest/iqms/t1w.html), the reference doi of FWHM is wrong.
Forman SD et al., Improved assessment of significant activation in functional magnetic resonance imaging (fMRI): use of a cluster-size threshold, Magn. Reson. Med. 33 (5), 636–647, 1995. doi:10.1016/j.neuroimage.2006.03.062.

Thanks for reporting!


Updated the  CONTRIBUTING.md

Revamp the file
Related issue

What changes does this PR do?
Screenshots (If any)
Questions

Thanks four your contribution please only adjust the readme and add your name if not already done. Thanks for your understanding


Restart animation

Hi,
I have just discovered this library, and it's amazing, really great work, I have a question about the usage, I have connected on the click of a button a simple animation:
      var cssSelector = anime({
       targets: '.js-search-icon',
       rotate: '1turn'
      });

When I press it the first time I can see it, but if I press it another time the animation no longer works, can anyone explain me why?

The animation rotates the element from 0 (default) to '1turn'.
Then if you animate it again, it will try to animate the element from '1turn' (the new value) to '1turn'.
Some options:
Force the initial value:
var rotateIcon = anime({
  targets: '.js-search-icon',
  rotate: ['0turn', '1turn']
});

Or add one more turn each time:
var rotateIcon = anime({
  targets: '.js-search-icon',
  rotate: '+=1turn',
  autoplay: false
});

Or create your animation outside the click event:
var rotateIcon = anime({
  targets: '.js-search-icon',
  rotate: '1turn',
  autoplay: false
});

then call it on click or whatever:
rotateIcon.restart()

This will restart the animation, from 0 to 1.
Next time look the documentation http://animejs.com/documentation/#restartAnim

Thank you very very much!


Bug report

This issue is a: Bug Report
Due to security reasons of your company, i am adding a link that will ask for request access to view this report.
Bug Report

Thanks for this. I'm looking at it. Please do not accept any further requests for access (as this is a public repo others may find it and fake being from Civo)

Can you please change the label, if you find this issue a valid kne

We've fixed this issue, thank you for reporting it. Feel free to re-test, but we can no longer reproduce this.

Yes, it's fixed


alter welcome title for spanish onboarding

#987  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @shakyShane and the rest of your teammates on  Graphite


add accel events and iconOverride

@tballmsft with the accelEvent.iconOverride = icon when you I add a filter to accel event, the whole rendering is messed up - the tiles are drawn over each other; any idea why?
also, I can't go back to home screen to save the program and deploy it...

for reference: the iconOverride crashes because PickerButtonDef distinguishes things based on icon name, which doesn't work if icon is an image...


add details polyfill

Forgot this - needs to be included for <details> elements to work in non-Webkit browsers.

:+1: great


APIs as plugins

Get rid of tight coupling

@achalpandeyy merge this for Vulkan work, I've refactored the windows, surfaces and swapchains as well as refcounted backlinks
@Crisspl & @AnastaZIuk its ready for merging


feat: support self hosted urls with db commands

What kind of change does this PR introduce?
feature
closes https://github.com/supabase/cli/issues/753
What is the new behavior?
support migrations for self-hosted database via --db-url flag, including

[x] supabase migration list [--db-url]
[x] supabase migration repair [--db-url]
[x] supabase db dump [--db-url]
[x] supabase db push [--db-url]
[x] supabase db remote commit [--db-url]
[x] supabase db diff [--linked | --db-url]

Additional context
Add any other context or screenshots.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 29 (3.45%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.004%) to 62.658%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

internal/db/remote/changes/changes.go
0
3
0.0%

internal/db/remote/commit/commit.go
0
3
0.0%

cmd/db.go
1
23
4.35%

Totals

Change from base Build<PHONE_NUMBER>:
-0.004%

Covered Lines:
3762

Relevant Lines:
6004

💛  - Coveralls

OMG, catching up on the release notes from a bunch of versions back and major thanks to all for this one.

@sweatybridge @soedirgo Is there any documentation regarding how to use the same? I might be a bit lost here but I am trying to run push migrations to a self-hosted supabase docker instance which is running locally at http://localhost:8000. Can you help me with how can I achieve this?

Yes you can find a self-hosted example in our documentation here https://supabase.com/docs/reference/cli/supabase-db-push

Is it expected behavior for "seed.sql" to be applied to remote databases by default? I want a way to specify seed data for local dev only. Is there a preferred way for me to create migrations that are only applied to the local db (supabase db reset), but not my self-hosted remote db (supabase db reset --db-url )?


plots: support dict for x field

Closes #4120

@shcheklein It's pretty confusing to describe accurately, but I tried to reword/reorganize and add an example.


Request: Info icon and search filter

Hello guys!
Great work.
What you think about adding the possibility to filter through the icons by typing their names?
Sometimes it gives an headache to scroll down several times all the icons to look for the one that fit the best for each specific case.
Thank you!

You can use the search bar at the top of the page to do just that.

Holy cow!
It works perfectly!
I swear i didn't see it

:+1: !


Low power settings for OV2640

From the sparse documentation I have found the following registers:
0x86 bit 2 borad LDO
0x86 bit 1 PWDN pin on sensor???
0x03 bit 6 low power mode control
0x05 bit 1, bit 2 sensor power down I/O
0x06 bit 1 sensor power down I/O
0x45 bit 1 sensor power down I/O
Alas this is all the documentation mentions. Please provide more information as to what these registers do and the impact of setting/clearing these bits.
My goal is to be able to put the board to sleep to reduce power consumption while running on batteries, waking up on demand.

@steveww
Write 0x15 to the register 0x06 address to go to sleep mode
Write 0x17 to the register 0x06 address to go to normal mode

If this is the case, please improve your documentation to make this clear. The documentation is totally ambiguous on these settings.
What are the power setting on registers 0x05 0x45?


Mission starts at closest waypoint

Behaviour introduced with PR https://github.com/PX4/Firmware/pull/8749.
Opening an issue on @dagar's request.
Description:

Takeoff and leave the drone in position hold.

Create waypoint mission where some intermediate waypoint is close to the current location.

Start mission. The vehicle will jump to the closest waypoint and commence the mission from there, skipping all waypoints before that.

The changes responsible for this are these two blocks in mission::on_activation() and mission::on_active(), setting the current waypoint to the closest mission item.
https://github.com/acfloria/Firmware/blob/a70cd4e54567ae774ada1d0197797890c16e717f/src/modules/navigator/mission.cpp#L155-L158
https://github.com/acfloria/Firmware/blob/a70cd4e54567ae774ada1d0197797890c16e717f/src/modules/navigator/mission.cpp#L198-L206
Tested on current master (ca5e22583f9dd81852856a9169523d8135b81db6) with SITL make posix_sitl_default jmavsim and default parameters.

I agree that for 1.8.0 release this behavior should probably be changed backed to the way it was before for all auto modes except the new RTL_TYPE=2.  However, I think there should be a bigger discussion about if the default mission item handling when uploading a new mission could be improved after 1.8.0.  PX4 resets the mission index to 1 when a new mission is uploaded; this is not how most professional systems have traditionally worked and many users find it frustrating/confusing.  I'd be happy to open a separate "discussion" issue about this for future consideration if people are willing to discuss/debate.

@acfloria @dagar Do you have cycles this weekend to make the change? I really would like to get v1.8 out of the door.
Thanks!

@dagar Any news on this?

I am currently working on it.


🐛 BUG: secret is not defined in local dev

What version of Wrangler are you using?
2.0.16
What operating system are you using?
Mac
Describe the Bug
Hello, I'm facing an issue where wrangler in local dev tells me that my secret is undefined. Checking the Cloudflare dashboard confirms the secret its set, and wrangler secret list lists it as well. I believe the same code used to work, but it doesn't anymore. Any idea?
PS: this is my first issue, is this the right place vs the community site to request for help like this?

Update: I got this solved using the (thus far) undocumented .dev.vars file as pointed to me in the forum. Docs is on the way also so I'll close this - https://github.com/cloudflare/cloudflare-docs/issues/4770.
I'm understanding the first round of help request would be better in the forum or discord and move here if devs are required.

Glad you were unblocked!


Issue 1824 - Object not const correct

http://d.puremagic.com/issues/show_bug.cgi?id=1824
https://github.com/D-Programming-Language/dmd/pull/387
https://github.com/D-Programming-Language/druntime/pull/72
https://github.com/D-Programming-Language/phobos/pull/262

Change Object.opEquals, opCmp, toHash and toString to const member functions.
Change using TypeInfo objects to const.

Updated for interface and typedef'ed class/interface comparison.


This ticker was canceled: Ticker(created by _MyHomePageState#a2d8d(lifecycle state: created))

When I was using AnimationController.animateTo, I received the following tips:
[VERBOSE-2:shell.cc(181)] Dart Error: Unhandled exception:
This ticker was canceled: Ticker(created by _MyHomePageState#a2d8d(lifecycle state: created))
#0      _rootHandleUncaughtError.<anonymous closure> (dart:async/zone.dart:1112:29)
#1      _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#2      _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)

This is the smallest example to reproduce this problem.
import 'package:flutter/material.dart';

void main() => runApp(new MyApp());

class MyApp extends StatelessWidget {
  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return new MaterialApp(
      title: 'Flutter Demo',
      theme: new ThemeData(
        // This is the theme of your application.
        //
        // Try running your application with "flutter run". You'll see the
        // application has a blue toolbar. Then, without quitting the app, try
        // changing the primarySwatch below to Colors.green and then invoke
        // "hot reload" (press "r" in the console where you ran "flutter run",
        // or press Run > Flutter Hot Reload in IntelliJ). Notice that the
        // counter didn't reset back to zero; the application is not restarted.
        primarySwatch: Colors.blue,
      ),
      home: new MyHomePage(title: 'animate To Test'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  MyHomePage({Key key, this.title}) : super(key: key);

  // This widget is the home page of your application. It is stateful, meaning
  // that it has a State object (defined below) that contains fields that affect
  // how it looks.

  // This class is the configuration for the state. It holds the values (in this
  // case the title) provided by the parent (in this case the App widget) and
  // used by the build method of the State. Fields in a Widget subclass are
  // always marked "final".

  final String title;

  @override
  _MyHomePageState createState() => new _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage>
    with SingleTickerProviderStateMixin {
  AnimationController progressBarAnimationController;
  Animation progressBarAnimation;

  void _incrementCounter() {
    progressBarAnimationController.forward().orCancel;
  }

  @override
  void initState() {
    // TODO: implement initState
    super.initState();

    progressBarAnimationController = new AnimationController(
      vsync: this,
      duration: new Duration(seconds: 10),
    );

    progressBarAnimation =
        new Tween(begin: 0.0, end: 400.0).animate(new CurvedAnimation(
      parent: progressBarAnimationController,
      curve: Curves.linear,
    ));

    progressBarAnimation.addListener(() {
      setState(() {
        if (progressBarAnimation.value > 100.0) {
          progressBarAnimationController.animateTo(
            1.0,
            duration: const Duration(milliseconds: 200),
          );
        }
      });
    });

    progressBarAnimationController.addStatusListener((status) {
      if (status == AnimationStatus.completed) {
        progressBarAnimationController.animateTo(
          0.0,
          duration: Duration.zero,
        );
      }
    });
  }

  @override
  void dispose() {
    progressBarAnimationController.dispose();

    super.dispose();
  }

  @override
  Widget build(BuildContext context) {
    // This method is rerun every time setState is called, for instance as done
    // by the _incrementCounter method above.
    //
    // The Flutter framework has been optimized to make rerunning build methods
    // fast, so that you can just rebuild anything that needs updating rather
    // than having to individually change instances of widgets.
    return new Scaffold(
      appBar: new AppBar(
        // Here we take the value from the MyHomePage object that was created by
        // the App.build method, and use it to set our appbar title.
        title: new Text(widget.title),
      ),
      body: new Stack(
        children: [
          new Positioned(
            left: 0.0,
            top: 0.0,
            child: new Container(
              height: 3.0,
              width: progressBarAnimation.value,
              color: Colors.green,
            ),
          )
        ],
      ),
      floatingActionButton: new FloatingActionButton(
        onPressed: _incrementCounter,
        tooltip: 'animation',
        child: new Icon(Icons.add),
      ), // This trailing comma makes auto-formatting nicer for build methods.
    );
  }
}

flutter doctor -v:
 frank@Frank-2  /web/native/animateto  flutter doctor -v
[✓] Flutter (Channel master, v0.8.7-pre.5, on Mac OS X 10.13.5 17F77, locale zh-Hans-CN)
    • Flutter version 0.8.7-pre.5 at /web/native/flutter
    • Framework revision e2d0b062d9 (3 weeks ago), 2018-09-18 05:54:03 +0200
    • Engine revision dcbc8a8207
    • Dart version 2.1.0-dev.4.0.flutter-050561fd82

[✓] Android toolchain - develop for Android devices (Android SDK 28.0.0)
    • Android SDK at /Users/frank/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 9.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 9.4.1, Build version 9F2000
    • ios-deploy 1.9.2
    • CocoaPods version 1.5.3

[✓] Android Studio (version 3.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 26.0.1
    • Dart plugin version 173.4700
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)

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

[✓] Connected devices (1 available)
    • iPhone X • 40D64B13-F4EC-4C72-9E74-C1749D568F1F • ios • iOS 11.4 (simulator)

• No issues found!

I would be very grateful if you could help me solve this problem.

Thank you for your help, you are doing a great job.

Sounds like expected behavior to me
  /// A future that resolves when this future resolves or throws when the ticker
  /// is canceled.
  ///
  /// If this property is never accessed, then canceling the ticker does not
  /// throw any exceptions. Once this property is accessed, though, if the
  /// corresponding ticker is canceled, then the [Future] returned by this
  /// getter will complete with an error, and if that error is not caught, there
  /// will be an uncaught exception in the current zone.
  Future<void> get orCancel {

removing .orCancel from  progressBarAnimationController.forward().orCancel; fixes the issue.

Sounds like expected behavior to me
  /// A future that resolves when this future resolves or throws when the ticker
  /// is canceled.
  ///
  /// If this property is never accessed, then canceling the ticker does not
  /// throw any exceptions. Once this property is accessed, though, if the
  /// corresponding ticker is canceled, then the [Future] returned by this
  /// getter will complete with an error, and if that error is not caught, there
  /// will be an uncaught exception in the current zone.
  Future<void> get orCancel {

removing .orCancel from  progressBarAnimationController.forward().orCancel; fixes the issue.

Thank you for your help, you are doing a great job.


correct typo

add the missing comma in data array

Good catch!  Can you also make the same change to the react example in https://github.com/SheetJS/js-xlsx/blob/master/demos/react/README.md and squash to one commit with the message:
correct vue and react README typos [ci skip]


Create test to logics

Context
The project not have tests in logics.
Should create teste for home, details and favorites.

branch: improvement/create-test-to-logic


Remove the unused streaming combine operator

These operators are not really streaming, and not used.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 0.00%. Comparing base (59551e4) to head (657aecd).
Report is 1509 commits behind head on master.

:exclamation:  There is a different number of reports uploaded between BASE (59551e4) and HEAD (657aecd). Click for more details.
HEAD has 53 uploads less than BASE

Flag
BASE (59551e4)
HEAD (657aecd)

integration
7
1

integration2
3
1

temurin
12
1

java-21
7
1

skip-bytebuffers-true
3
1

skip-bytebuffers-false
7
0

unittests
5
0

unittests1
2
0

java-11
5
0

unittests2
3
0

integration1
2
0

custom-integration1
2
0

Additional details and impacted files
@@              Coverage Diff              @@
##             master   #14718       +/-   ##
=============================================
- Coverage     61.75%    0.00%   -61.76%
=============================================
  Files          2436        3     -2433
  Lines        133233        6   -133227
  Branches      20636        0    -20636
=============================================
- Hits          82274        0    -82274
+ Misses        44911        6    -44905
+ Partials       6048        0     -6048

Flag
Coverage Δ

custom-integration1
?

integration
0.00% <ø> (-0.01%)
:arrow_down:

integration1
?

integration2
0.00% <ø> (ø)

java-11
?

java-21
0.00% <ø> (-61.63%)
:arrow_down:

skip-bytebuffers-false
?

skip-bytebuffers-true
0.00% <ø> (-27.73%)
:arrow_down:

temurin
0.00% <ø> (-61.76%)
:arrow_down:

unittests
?

unittests1
?

unittests2
?

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Add baselines for codegen tests

This will make is much easier to investigate failures that bubble up to
the codegen level. You'll be able to see if there was a change to the IR
rather than just the final code.

FYI only


Remove dependency on json-document.

Closes issue #4.
Closes issue #3.

Reduced minified bundle size from 74K to 42K.