text:
wrap stdio of workload containers

Instead of redirecting workload container stderr and stdout to vhive stderr and stdout, it is now logged as:
time="2021-07-02T16:52:41.467607817Z" level=info msg="ERROR:root:testing logging2" vmID=15

Tested with pyaes code / image@docker hub.

Changelog updated. I can't check your marks though (by clicking them).
Why the test is failing, i don't understand yet.

please add a spelling exception to configs/.wordlist* file to fix the linter error

source: gharchive/pull-request

authors: pogobanane ustiugov

repo: ease-lab/vhive

license: MIT

license_type: permissive

license_source: github-api


text:
番源扩展为空

添加不了番源

添加不了番源
安装插件后给纯纯看番 获取其他应用列表权限

waydroid Android 11 x86，纯纯看番权限列表只有文件访问权限，没法添加获取应用列表权限，无法获取番源

source: gharchive/issue

authors: Q2453267246 ShulkerSakura heyanLE

repo: easybangumiorg/EasyBangumi


text:
data

https://easyj.icu/docs/#/data
EasyJ开源项目是为了简化Java项目开发而诞生的，主要提供通用的工具、即插即用功能、中间件，并提供一些简化和增强配置的功能，使业务项目开发变得更加快捷。

文档

Data


text:
Fix markdown

The bad formatting really hurt my eyes... hope you don't mind pull this in.

@ebattenberg
Just a ping in case you didn't noticed there are a few PRs around.

repo: ebattenberg/ggmm


text:
Please check Status Ok for Chebi: 89484, 89719, 89891, 89828, 88764, 80946 and 58784

Hello,
I have just noticed that the ChEBIs still have status OK:
89484
89719
89891
89828
88764
80946
58784
Can you please check them? We need them for RHEA.
TIA,
Lucila

Hi Lucila,
All these entries have now been upgraded to checked status.
Cheers,
Steve

repo: ebi-chebi/ChEBI


text:
Fix a sample_field reference in non-droplet context

This tiny fix addresses an issue reported by @YalanBi caused by use of sample_field in a non-droplet experiment. Use of .get() (returning None in this case) should solve the problem (the droplet status is used properly in the called function).

Thanks for the report @YalanBi

repo: ebi-gene-expression-group/atlas-anndata


text:
VS2017 compatibility

Hi,
thanks for your demo, managed to make it run on Win32. Few problems were using constexpr variables as a result of trig functions (as they are not implemented to be constexpr, but it's a bug in gcc that it works). Replacing them with const works fine. M_PI needed to be defined, that's easy to define myself. Biggest problem were string literals when constructing shaders. There is a limit, I think 16kB, or even less in MSVC, so I had to split the std::string into multiple literals. Maybe better approach could be reading the file? Don't know.
Hope this helps somebody

Hi,
Thanks for your feedback. I'm working on Linux, could you send me a patch with your changes of const/constexpr? For string literals, does it work better if you replace the last lines of the makefile with
%.glsl.inc: %.glsl
sed -e '1i const char* $(F)_glsl = R"(' -e '$$a )*";' $< > $@
i.e. by using "const char*" constants instead of string constants?
Eric

Hi,
thanks for your demo, managed to make it run on Win32. Few problems
were using constexpr variables as a result of trig functions (as
they are not implemented to be constexpr, but it's a bug in gcc that
it works). Replacing them with const works fine. M_PI needed to be
defined, that's easy to define myself. Biggest problem were string
literals when constructing shaders. There is a limit, I think 16kB,
or even less in MSVC, so I had to split the std::string into
multiple literals. Maybe better approach could be reading the file?
Don't know.
Hope this helps somebody
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub , or mute the thread
.

Closing this as "infeasible" (missing input from requester).

authors: ebruneton janspisiak

license_source: bigquery


text:
Deprecation in 2.18.0

I like this addon. Thanks!
Everytime I install this using e-cli 2.18.0 though, the following deprecation notice appears:
DEPRECATION: An addon is trying to access project.nodeModulesPath. This is not a reliable way to discover npm modules. Instead, consider doing: require("resolve").sync(something, { basedir: project.root }). Accessed from:   NPMDependencyVersionChecker

How could I possibly remove this deprecation notice?
Thanks!

I believe this has been resolved. Feel free to reopen if not.

authors: greyhwndz webark

repo: ebryn/ember-component-css

license: mit


text:
Compatability with Ember 1.11 and 1.12

Ember.Descriptor has gone the way of the dodo in ember. This was stolen
from the ember inspector and makes everything work again. See the
following for more information:
https://github.com/emberjs/ember.js/pull/10672
https://github.com/emberjs/ember-inspector/pull/327

There are other issues besides this one, but I'm still trying to track down others.

Thanks!

authors: ebryn jonnii

repo: ebryn/ember-model


text:
[WIP] Insert URL Modal

What does this PR?
fixes #2208 .

added modal for inserting url while writing post in editor
takes label and url from input and formats it.
insert raw url if no label is provided

Where should the reviewer start?

Go to editor screen
tap on link button in editor footer.
modal opens with rspective fields.

Issue number
#2208
Screenshots/Video
https://user-images.githubusercontent.com/48380998/157290599-1790d053-5e45-4022-8fb8-41a613510f0f.mp4

@noumantahir check the latest update here.

added support for plain, video and image type urls
added support for preview of video and images
added select text/url to prefill the label/url and insert the other.
minor bugs fixed as well.

https://user-images.githubusercontent.com/48380998/159011370-225dadf0-d1d7-4738-bae3-8cc2b084d79b.mp4

@aliseyalvi take it easy, always test each feature you implement aggressive with an intention to break you own code....

@noumantahir PR updated.

fixed preview not changing issue
fixed label not updating issue
fixed url not showing complete issue
removed url label from plain url
added line breaks before and after image and video
added side effect for each change e-g label/url/urltype and update the preview

@noumantahir PR updated.

added clipboard listener. When insert model opens it checks for clipboard and if there is a valid urls it prefills the url input.
fixed preview View height with scrollview support to contain large and portrait images/videos
added image label when image url is inserted.

authors: aliseyalvi noumantahir

repo: ecency/ecency-mobile


text:
Migrate to Spotify | API key not allowed

I expect that due to the migration of Echonest API to Spotify API, I'm now getting an error when I try to retrieve an audio_analysis object.
But I'm not sure how or where to change the API I'm calling from the Echonest API to the Spotify API.
The code is basically:
from echonest.remix.audio import AudioAnalysis
AudioAnalysis(str(track_md5))

Will pyechonest and remix still work? And if so, where do I need to make configuration changes?
I imagine I am missing something obvious.

你永远不会得到一个密钥，所以数据集永远不会解决

那他放出来干什么，哥们你不是骗我的吧，你能借我用用你的么？大哥？

authors: Dbochman MikeiLL xin19961512

repo: echonest/pyechonest


text:
s3-data-plane documentation

Hello,
I want to try out the data-plane-s3 extension, but the readme file is very short and does not contain any information about how to use it.
At the moment, I just don't know how to specify the s3 endpoint and a bucket name. I think the credentials for the bucket can be provided as an environment, but please correct me if I'm wrong.
ralph

The data-plane-s3 extension was implemented mainly to move the communication logic away from the deprecated InlineDataFlowController to the data-plane, it's not documented nor tested appropriately.
Currently, the credentials are obtained through the aws-sdk's DefaultCredentialsProvider, that loads the credentials in this order (according to the documentation):
AWS credentials provider chain that looks for credentials in this order:
- Java System Properties - aws.accessKeyId and aws.secretAccessKey
- Environment Variables - AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY
- Credential profiles file at the default location (~/.aws/credentials) shared by all AWS SDKs and the AWS CLI
- Credentials delivered through the Amazon EC2 container service if AWS_CONTAINER_CREDENTIALS_RELATIVE_URI" environment variable is set and security manager has permission to access the variable,
- Instance profile credentials delivered through the Amazon EC2 metadata service

If you are interested in contributing with testing and documenting would be great.

Thanks for the response! I did a first small test with the data-plane-s3 extension, in which I copy a file from s3 to local. You can find  it in my fork and s3-test branch.  https://github.com/reisman234/DataSpaceConnector/tree/s3-test
I think also some parts in the s3-core needs some updates, e.g. the S3ClientProviderImpl.java does not provide functionality to choose a self-hosted S3-Server (minio).
I will see what I can do for testing and documentation. What resources do you expect as a test for this extension? Just Unit tests, or is such an example also sufficient?
In general to that data-plan topic, I have another question. In the file transfer samples, only the provider realizes the data plane part. How can a consumer download a file after the negotiation part?

I created an issue about the provider being able to create a client to connect to a self hosted S3 (#1309).
I think the best test would be an end to end one, that uses a dokerized minio to verify the data transfer (as already done by the S3 integration-tests).

I created a patch in my fork for this issue https://github.com/reisman234/DataSpaceConnector/tree/feature/%231309-configurable-s3-endpoint, if you want to have a look.
In a first manual test, I was able to do a provider push from s3 to a http endpoint.
What can I use for as a reference for doing end-to-end testing? I found some resources in ./system-tests/e2e-transfer-test/  but I don't know how to tun them.


text:
feat(build): use the published version catalog

What this PR changes/adds
Imports and utilises the Version Catalog that is getting published as Maven Artifact.
Why it does that
To centralize version management. Also gets rid of all those val XYZ : String by project declarations.
And we can now have "bundles", which are essentially lists of dependencies.
Further notes

merge only AFTER PR https://github.com/eclipse-dataspaceconnector/GradlePlugins/pull/38 is merged and published! Until then, all checks in this PR will fail, because the artifact containing the catalog is not found in any Maven repo.
documentation was added to docs/developer/version-catalogs.md

Linked Issue(s)
.
Checklist

[ ] added appropriate tests?
[ ] performed checkstyle check locally?
[ ] added/updated copyright headers?
[ ] documented public classes/methods?
[x] added/updated relevant documentation?
[x] assigned appropriate label? (exclude from changelog with label no-changelog)
[x] formatted title correctly? (take a look at the CONTRIBUTING and Etiquette for pull requests for details)

Codecov Report
Base: 64.54% // Head: 64.54% // No change to project coverage :thumbsup:

Coverage data is based on head (6f7508b) compared to base (61b1757).
Patch has no changes to coverable lines.

:exclamation: Current head 6f7508b differs from pull request most recent head 4553e7a. Consider uploading reports for the commit 4553e7a to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2178   +/-   ##
=======================================
  Coverage   64.54%   64.54%
=======================================
  Files         836      836
  Lines       17421    17421
  Branches     1099     1099
=======================================
  Hits        11244    11244
  Misses       5720     5720
  Partials      457      457

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

authors: codecov-commenter paullatzelsperger


text:
fix: avoid sending messages on failing not-yet-requested consumer transfers

What this PR changes/adds
Avoid sending TranferRequestMessages on failing CONSUMER TransferProcesses that have not been notified to the PROVIDER yet.
Why it does that
bugfix
Further notes

moved the test classes from package org.eclipse.edc.connector.transfer.transfer; to package org.eclipse.edc.connector.transfer.process;

Linked Issue(s)
Closes #3247
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (2999513) 65.96% compared to head (f753869) 65.97%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3249   +/-   ##
=======================================
  Coverage   65.96%   65.97%
=======================================
  Files         842      842
  Lines       16887    16894    +7
  Branches      928      928
=======================================
+ Hits        11139    11145    +6
- Misses       5379     5380    +1
  Partials      369      369

Impacted Files
Coverage Δ

...r/transfer/process/TransferProcessManagerImpl.java
90.04% <100.00%> (+0.15%)
:arrow_up:

... and 1 file with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

authors: codecov-commenter ndr-brt

repo: eclipse-edc/Connector


text:
test: avoid getFreePort collisions

What this PR changes/adds
Add an ALREADY_RETURNED HashSet to ensure that the port generated by getFreePort is not already returned.
Why it does that
Avoid possible collisions.
Further notes

changed the "incremental" port generation to the complete randomic. Looking at the tests they are always calling the getFreePort without arguments, that is generating a random number anyway, so the "efficiency" of using the next number instead is pretty negligible.

Linked Issue(s)
Closes #4365
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 90.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 74.91%. Comparing base (7f20ba5) to head (433f7df).
Report is 362 commits behind head on main.

Files
Patch %
Lines

...b/src/main/java/org/eclipse/edc/util/io/Ports.java
90.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4366      +/-   ##
==========================================
+ Coverage   71.74%   74.91%   +3.17%
==========================================
  Files         919     1066     +147
  Lines       18457    21383    +2926
  Branches     1037     1171     +134
==========================================
+ Hits        13242    16020    +2778
- Misses       4756     4839      +83
- Partials      459      524      +65

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


text:
Need to get an RC staged by Dec 15.

We need to put together a full release candidate that I can then stage for review by the specification project by Dec 15 for inclusion in EE10. Please link to whatever tasks are needed for that and feel free to assign any to me.

Here is what I know we need to do.
CDI spec:

Move BeanContainer method under BeanManager, see https://github.com/eclipse-ee4j/cdi/issues/568
Allow OM to access declaring class via CDI API, see https://github.com/eclipse-ee4j/cdi/issues/563
Specify invalid treatment of @Enhancement and @Registration phases, see https://github.com/eclipse-ee4j/cdi/pull/576
Move @SessionScoped into CDI Full as this is poorly

No issue ATM @Ladicek works on this as we speak

TCKs:

Some tests are not under appropriate package https://github.com/eclipse-ee4j/cdi-tck/issues/320
Adjust CustomStereotypeTest, see https://github.com/eclipse-ee4j/cdi-tck/pull/323
Provide tests for negative scenarios when using Build compatible extensions, see https://github.com/eclipse-ee4j/cdi-tck/issues/321
Add tests for withSubtypes and withAnnotations, see https://github.com/eclipse-ee4j/cdi-tck/pull/322
Check whether tests with @SessionScope are under "Full" category

Issue not created yet

These issues are already being worked on by either me or @Ladicek and I guess we'll be able to address them pretty fast.

@manovotn thanks, I wanted to put down a similar list myself :-) Can you make each item a TODO item? It's enough to put [ ] after the bullet point. For example, this:
- [ ] my TODO item
- [ ] my other TODO item

results in:

[ ] my TODO item
[ ] my other TODO item

@Ladicek, I was going to do it once I had all the issues.
Updated with checkboxes and updated with additional issues.

Perfect, thanks!

Correct me if I am wrong @Ladicek but I think we have everything done except for merge of https://github.com/eclipse-ee4j/cdi-tck/pull/328 which requires new CDI API version anyway :-)

How about we do a 4.0.0.Beta3 so that we can get the PR done and merged? :-)

In other words, yea I agree, we should be ready for RC.

How about we do a 4.0.0.Beta3 so that we can get the PR done and merged? :-)

Did you just volunteer? :D

How about we do a 4.0.0.Beta3 so that we can get the PR done and merged? :-)

Did you just volunteer? :D

I'm on it!

Aaaand done, Beta3 should be on its way to Central.

@starksm64 all the tasks that I was aware of are now completed.

Ok, I'll start on an RC. Is there an updated Weld release that should be used in the TCK distribution?

@starksm64 mmm, not for the latest version. There is Alpha1, but that doesn't implement latest of changes.
If you need that, I can have it within a day or two - it's exactly what I'm going to work on starting tomorrow.

Ok, I'll get started but wait on putting out the release until the new Weld version is out.

@starksm64 I have just released new Weld version that implements latest CDI and CDI TCK (4.0.0.Alpha5 which I also released). Expect it to land in Central within an hour.
Weld core - 5.0.0.Alpha2
Weld API - 5.0.Beta4
The above version passes all TCK when ran against embedded container.

Ok, thanks.

@graemerocher Ladislav is on PTO.
I dont this @Registration supported it at any point.
And looking at javadoc, I don't think it needs to. To quote a bit of it:
 * If a {@code @Registration} method has a parameter of type {@code BeanInfo}, the method is called once
 * for each bean whose set of bean types contains at least one expected type.

I.e. it already goes through all types of any bean to notify the method so it should cover the same case you are looking for.
Or am I missing something?

ok gotcha

So I have 4.0.0-RC1 version of cdi-api and cdi-tck staged. I tried running the latest weld core code against these using a staging repo profile, and I'm seeing the following errors:
[ERROR] Tests run: 1254, Failures: 14, Errors: 0, Skipped: 6, Time elapsed: 47.415 s <<< FAILURE! - in TestSuite
[ERROR] org.jboss.cdi.tck.tests.definition.stereotype.priority.inherited.StereotypeInheritedPriorityTest.testPriorityWasInherited  Time elapsed: 0.01 s  <<< FAILURE!
java.lang.AssertionError: expected [true] but found [false]
        at org.jboss.cdi.tck.tests.definition.stereotype.priority.inherited.StereotypeInheritedPriorityTest.testPriorityWasInherited(StereotypeInheritedPriorityTest.java:31)

[ERROR] org.jboss.cdi.tck.tests.definition.stereotype.priority.StereotypeWithPriorityTest.testBeanPriorityFromStereotypeOverridesOtherAlternative  Time elapsed: 0.002 s  <<< FAILURE!
java.lang.AssertionError: expected [BazAlternative2] but found [BazAlternative]
        at org.jboss.cdi.tck.tests.definition.stereotype.priority.StereotypeWithPriorityTest.testBeanPriorityFromStereotypeOverridesOtherAlternative(StereotypeWithPriorityTest.java:54)

[ERROR] org.jboss.cdi.tck.tests.definition.stereotype.priority.StereotypeWithPriorityTest.testStereotypeWithAlternativeAndPriority  Time elapsed: 0.002 s  <<< FAILURE!
java.lang.AssertionError: expected [BarExtended] but found [Bar]
        at org.jboss.cdi.tck.tests.definition.stereotype.priority.StereotypeWithPriorityTest.testStereotypeWithAlternativeAndPriority(StereotypeWithPriorityTest.java:47)

[ERROR] org.jboss.cdi.tck.tests.definition.stereotype.priority.StereotypeWithPriorityTest.testStereotypeWithPriority  Time elapsed: 0.002 s  <<< FAILURE!
java.lang.AssertionError: expected [FooAlternative] but found [Foo]
        at org.jboss.cdi.tck.tests.definition.stereotype.priority.StereotypeWithPriorityTest.testStereotypeWithPriority(StereotypeWithPriorityTest.java:40)

[ERROR] org.jboss.cdi.tck.tests.definition.stereotype.broken.multiplePriorities.inherited.StereotypeInheritedPriorityConflictTest.arquillianBeforeClass  Time elapsed: 0.075 s  <<< FAILURE!
java.lang.RuntimeException: Expected exception of type jakarta.enterprise.inject.spi.DefinitionException during deployment of _DEFAULT_, but no exception was thrown.

[ERROR] org.jboss.cdi.tck.tests.definition.stereotype.broken.multiplePriorities.ConflictingPrioritiesFromSingleStereotypeTest.arquillianBeforeClass  Time elapsed: 0.077 s  <<< FAILURE!
java.lang.RuntimeException: Expected exception of type jakarta.enterprise.inject.spi.DefinitionException during deployment of _DEFAULT_, but no exception was thrown.

[ERROR] org.jboss.cdi.tck.tests.definition.stereotype.broken.multiplePriorities.ConflictingPriorityStereotypesTest.arquillianBeforeClass  Time elapsed: 0.07 s  <<< FAILURE!
java.lang.RuntimeException: Expected exception of type jakarta.enterprise.inject.spi.DefinitionException during deployment of _DEFAULT_, but no exception was thrown.

[ERROR] org.jboss.cdi.tck.tests.event.observer.method.ObserverMethodTest.testGetDeclaringBeanOnObserverMethod  Time elapsed: 0.002 s  <<< FAILURE!
java.lang.AssertionError: expected object to not be null
        at org.jboss.cdi.tck.tests.event.observer.method.ObserverMethodTest.testGetDeclaringBeanOnObserverMethod(ObserverMethodTest.java:71)

[ERROR] org.jboss.cdi.tck.tests.lookup.dynamic.handle.InstanceHandleTest.testGetAfterDestroyingContextualInstance  Time elapsed: 0.002 s  <<< FAILURE!
java.lang.AbstractMethodError: Receiver class org.jboss.weld.bean.builtin.InstanceImpl does not define or inherit an implementation of the resolved method abstract getHandle()Ljakarta/enterprise/inject/Instance$Handle; of interface jakarta.enterprise.inject.Instance.
        at org.jboss.cdi.tck.tests.lookup.dynamic.handle.InstanceHandleTest.testGetAfterDestroyingContextualInstance(InstanceHandleTest.java:96)

[ERROR] org.jboss.cdi.tck.tests.lookup.dynamic.handle.InstanceHandleTest.testGetHandle  Time elapsed: 0.002 s  <<< FAILURE!
java.lang.AbstractMethodError: Receiver class org.jboss.weld.bean.builtin.InstanceImpl does not define or inherit an implementation of the resolved method abstract getHandle()Ljakarta/enterprise/inject/Instance$Handle; of interface jakarta.enterprise.inject.Instance.
        at org.jboss.cdi.tck.tests.lookup.dynamic.handle.InstanceHandleTest.testGetHandle(InstanceHandleTest.java:54)

[ERROR] org.jboss.cdi.tck.tests.lookup.dynamic.handle.InstanceHandleTest.testHandles  Time elapsed: 0.002 s  <<< FAILURE!
java.lang.AbstractMethodError: Receiver class org.jboss.weld.bean.builtin.InstanceImpl does not define or inherit an implementation of the resolved method abstract handles()Ljava/lang/Iterable; of interface jakarta.enterprise.inject.Instance.
        at org.jboss.cdi.tck.tests.lookup.dynamic.handle.InstanceHandleTest.testHandles(InstanceHandleTest.java:120)

[ERROR] org.jboss.cdi.tck.tests.build.compatible.extensions.syntheticBean.SyntheticBeanTest.test  Time elapsed: 0.001 s  <<< FAILURE!
java.lang.AbstractMethodError: Receiver class org.jboss.weld.bean.builtin.InstanceImpl does not define or inherit an implementation of the resolved method abstract getHandle()Ljakarta/enterprise/inject/Instance$Handle; of interface jakarta.enterprise.inject.Instance.
        at org.jboss.cdi.tck.tests.build.compatible.extensions.syntheticBean.SyntheticBeanTest.test(SyntheticBeanTest.java:30)

[ERROR] org.jboss.cdi.tck.tests.build.compatible.extensions.syntheticBeanWithLookup.SyntheticBeanWithLookupTest.test  Time elapsed: 0.002 s  <<< FAILURE!
java.lang.AbstractMethodError: Receiver class org.jboss.weld.bean.builtin.InstanceImpl does not define or inherit an implementation of the resolved method abstract getHandle()Ljakarta/enterprise/inject/Instance$Handle; of interface jakarta.enterprise.inject.Instance.
        at org.jboss.cdi.tck.tests.build.compatible.extensions.syntheticBeanWithLookup.SyntheticBeanWithLookupTest.test(SyntheticBeanWithLookupTest.java:37)

[ERROR] org.jboss.cdi.tck.tests.build.compatible.extensions.syntheticBeanInjectionPoint.SyntheticBeanInjectionPointTest.test  Time elapsed: 0.001 s  <<< FAILURE!
java.lang.AbstractMethodError: Receiver class org.jboss.weld.bean.builtin.InstanceImpl does not define or inherit an implementation of the resolved method abstract getHandle()Ljakarta/enterprise/inject/Instance$Handle; of interface jakarta.enterprise.inject.Instance.
        at org.jboss.cdi.tck.tests.build.compatible.extensions.syntheticBeanInjectionPoint.SyntheticBeanInjectionPointTest.test(SyntheticBeanInjectionPointTest.java:39)

[INFO]
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR]   SyntheticBeanTest>Arquillian.run:138->test:30 AbstractMethod Receiver class or...
[ERROR]   SyntheticBeanInjectionPointTest>Arquillian.run:138->test:39 AbstractMethod Rec...
[ERROR]   SyntheticBeanWithLookupTest>Arquillian.run:138->test:37 AbstractMethod Receive...
[ERROR]   ConflictingPrioritiesFromSingleStereotypeTest>Arquillian.arquillianBeforeClass:99 » Runtime
[ERROR]   ConflictingPriorityStereotypesTest>Arquillian.arquillianBeforeClass:99 » Runtime
[ERROR]   StereotypeInheritedPriorityConflictTest>Arquillian.arquillianBeforeClass:99 » Runtime
[ERROR]   StereotypeWithPriorityTest>Arquillian.run:138->testBeanPriorityFromStereotypeOverridesOtherAlternative:54 expected [BazAlternative2] but found [BazAlternative]
[ERROR]   StereotypeWithPriorityTest>Arquillian.run:138->testStereotypeWithAlternativeAndPriority:47 expected [BarExtended] but found [Bar]
[ERROR]   StereotypeWithPriorityTest>Arquillian.run:138->testStereotypeWithPriority:40 expected [FooAlternative] but found [Foo]
[ERROR]   StereotypeInheritedPriorityTest>Arquillian.run:138->testPriorityWasInherited:31 expected [true] but found [false]
[ERROR]   ObserverMethodTest>Arquillian.run:138->testGetDeclaringBeanOnObserverMethod:71 expected object to not be null
[ERROR]   InstanceHandleTest>Arquillian.run:138->testGetAfterDestroyingContextualInstance:96 AbstractMethod
[ERROR]   InstanceHandleTest>Arquillian.run:138->testGetHandle:54 AbstractMethod Receive...
[ERROR]   InstanceHandleTest>Arquillian.run:138->testHandles:120 AbstractMethod Receiver...
[INFO]
[ERROR] Tests run: 1254, Failures: 14, Errors: 0, Skipped: 6
[INFO]
[INFO] ------------------------------------------------------------------------

Are you sure you have the right version?
When I did a release of Weld 5.0.0.Alpha2, it ran the whole CDI TCK against 4.0.0.Alpha5 (which is the same as RC content-wise) and that passed just fine.
You'd need to give me some details on how you execute it.

I was using an updated local weld core repo. I created a fresh fork and reran with a staging repo profile and all tests are passing:
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] Running TestSuite
[INFO] Tests run: 1248, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 94.966 s - in TestSuite
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 1248, Failures: 0, Errors: 0, Skipped: 0

Closing this as CR was staged successfully.

authors: Ladicek graemerocher manovotn starksm64


text:
BSD addon fails to compile

v6.4.1_rel of netxduo, filex, and threadx
Hosted build for Linux - Ubuntu 20.04.6 LTS (GNU/Linux 5.15.0-97-generic x86_64)
Nested filex inside this project as follows:
diff --git a/CMakeLists.txt b/CMakeLists.txt
index c490b3c..f9f1b6b 100755
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -5,6 +5,8 @@ project(netxduo
     LANGUAGES C ASM
 )

+add_subdirectory (filex)
+
 option(NXD_ENABLE_FILE_SERVERS "Includes a dependency on FileX to support 'server' protocol handlers" ON)

and similarly for threadx inside filex.
Running cmake as follows:
$ mkdir build && cd build
$ cmake -DCMAKE_BUILD_TYPE=Debug -DNXD_ENABLE_BSD=yes -DTHREADX_ARCH=linux -DTHREADX_TOOLCHAIN=gnu ..

Make fails with the following errors:
[ 31%] Building C object CMakeFiles/netxduo.dir/addons/BSD/nxd_bsd.c.o
In file included from /home/sj/netxduo/addons/BSD/nxd_bsd.c:28:
/home/sj/netxduo/addons/BSD/nxd_bsd.h:628:21: error: typedef redefinition with different types ('LONG' (aka 'int') vs '__suseconds_t' (aka 'long'))
typedef LONG        nx_bsd_suseconds_t;
                    ^
/home/sj/netxduo/addons/BSD/nxd_bsd.h:208:33: note: expanded from macro 'nx_bsd_suseconds_t'
#define nx_bsd_suseconds_t      suseconds_t
                                ^
/usr/include/x86_64-linux-gnu/sys/types.h:138:23: note: previous definition is here
typedef __suseconds_t suseconds_t;
                      ^
In file included from /home/sj/netxduo/addons/BSD/nxd_bsd.c:28:
/home/sj/netxduo/addons/BSD/nxd_bsd.h:631:8: error: redefinition of 'timeval'
struct nx_bsd_timeval
       ^
/home/sj/netxduo/addons/BSD/nxd_bsd.h:210:33: note: expanded from macro 'nx_bsd_timeval'
#define nx_bsd_timeval          timeval
                                ^
/usr/include/x86_64-linux-gnu/bits/types/struct_timeval.h:8:8: note: previous definition is here
struct timeval
       ^
In file included from /home/sj/netxduo/addons/BSD/nxd_bsd.c:28:
/home/sj/netxduo/addons/BSD/nxd_bsd.h:703:3: error: typedef redefinition with different types ('struct FD_SET_STRUCT' vs 'struct fd_set')
} nx_bsd_fd_set;
  ^
/home/sj/netxduo/addons/BSD/nxd_bsd.h:226:33: note: expanded from macro 'nx_bsd_fd_set'
#define nx_bsd_fd_set           fd_set
                                ^
/usr/include/x86_64-linux-gnu/sys/select.h:70:5: note: previous definition is here
  } fd_set;
    ^

Adding this define:
diff --git a/addons/BSD/nxd_bsd.h b/addons/BSD/nxd_bsd.h
index 3810a81..e2b0460 100644
--- a/addons/BSD/nxd_bsd.h
+++ b/addons/BSD/nxd_bsd.h
@@ -135,9 +135,7 @@ extern   "C" {

 /* Defined, APIs are natively named with nx_bsd_ prefix to avoid conflicting/overriding OS BSD APIs.  */
-/*
 #define NX_BSD_ENABLE_NATIVE_API
-*/

gives instead these errors:
/home/sj/netxduo/addons/BSD/nxd_bsd.c:10121:29: error: no member named 'bsd_errno' in 'struct TX_THREAD_STRUCT'
      current_thread_ptr -> bsd_errno = tx_errno;
      ~~~~~~~~~~~~~~~~~~    ^
/home/sj/netxduo/addons/BSD/nxd_bsd.c:10180:33: error: no member named 'bsd_errno' in 'struct TX_THREAD_STRUCT'
    val = current_thread_ptr -> bsd_errno;
          ~~~~~~~~~~~~~~~~~~    ^

hi @sj-raima,
you'll need to add a define in the 'tx_user.h' file as below:
https://github.com/eclipse-threadx/netxduo/blob/18704ffa7383071ce1b335730fbde131f27be045/test/cmake/libs/tx_user.h#L53

@rahmanih The solution you proposed was enough to get me on track but it is really not appropriate to define this in a test.  There should instead be a define to enable this (NX_BSD or similar)  and I would suggest code in threadx/common/inc(_smp)/tx_api.h to add the declaration:
#ifdef NX_BSD
    int bsd_errno;
#endif

Also, I would like to add that if you are using errno.h header file in the implementation, you will find incompatibility error due a definition of error code in both files, nxd_bsd.h and errno.h.
Keep an eye on that 👀

authors: rahmanih rubenax97 sj-raima

repo: eclipse-threadx/netxduo


text:
chore: upgrade nuget packages

Description
Upgrade Nuget Packages to fix medium security issues
Why
To fix some security issues
Issue
N/A
Checklist

[x] I have followed the contributing guidelines
[x] I have performed IP checks for added or updated 3rd party libraries
[x] I have created and linked IP issues or requested their creation by a committer
[x] I have performed a self-review of my own code
[x] I have successfully tested my changes locally
[x] I have added tests that prove my changes work
[x] I have checked that new and existing tests pass locally with my changes
[x] I have commented my code, particularly in hard-to-understand areas

This PR is obsolete due to the net8 upgrade #456

repo: eclipse-tractusx/portal-backend


text:
App Release | App manager is allowed to upload duplicate roles

These are the following backend issues. (https://github.com/eclipse-tractusx/portal-backend/issues/868)
Issue #1

Users are allowed to upload the same CSV file with the same Role values any number of times, resulting in the same roles being repeated multiple times in the app's role list.
Current Behavior: The same role being repeated n times in the list and also does not allow to delete of the role.
Expected Behavior: It should ignore the duplicate role and also deletion of each recently uploaded should be working.

Steps To Reproduce:

Login to the Portal as App Manager
Register an App
Add/Input all the required data
Under Technical integration --> Download the CSV template and then upload it
Delete the recently uploaded CSV template and Upload it again (N Times)

Issue# 2

When the User deletes the uploaded file of roles then uploaded roles are not removed from the list.
Current Behavior: The Uploaded file was removed successfully but its associated roles remain as it is and due to that duplication of roles is happening in the section.
Expected Behavior: The Roles file should be deleted and its associated roles should be removed.

Steps To Reproduce:

Login to the Portal as App Manager
Register an app
Add/Input all the required data
Under Technical integration --> Download CSV template and then upload it back
Delete the recently uploaded CSV template
The roles will be unchanged. (The attached file's roles should be removed )

Proposed Solutions

While Onboarding a New App: At the Technical Integration step
Backend: API exists to upload the App Roles but the backend would need to change the API and ignore the duplicate role values while uploading the roles to the server

While Onboarding a New App: Delete all roles that were recently uploaded by the .csv file
Frontend: Frontend would be integrating this API and passing all the recently uploaded role's IDs to the API to delete the roles

While updating the Onboarded App: Delete all the roles that were recently uploaded by the .csv file
Frontend: Frontend would have to identify the recently uploaded roles (because in case of an update, already assigned roles would already be part of the app) and then pass the recently uploaded role IDs to the API to delete them from the database

@ss-nikunj  can we close this ? respective PR is merged

authors: MaximilianHauer ss-nikunj

repo: eclipse-tractusx/portal-frontend


text:
[New Model]: Shared CatenaX Identifier (UUIDv4)

Model Description
A lot of released models reference the CatenaX ID. It would make sense to create a shared aspect for it. For simpler dependency management I would suggest creating a separate model for it.
For backward compatibility reasons, it might be necessary to create 2 or 3 versions of it, Since originally the CatenaXId was just added raw and unprefixed, while it has been changed to be prefixed by a UUID URN.

version 1.0.0 describing the older unprefixed version
version 2.0.0 describing the newer prefixed URN prefixed version
version 1.1.0 allowing both

Relevant Standards
https://datatracker.ietf.org/doc/html/rfc4122
Example Data
see the following relevant snippet from an already released model.
...
:catenaXId a bamm:Property;
    bamm:name "catenaXId";
    bamm:preferredName "Catena-X Identifier"@en;
    bamm:description "The fully anonymous Catena-X ID of an object, organization or concept, valid for the Catena-X dataspace."@en;
    bamm:characteristic :CatenaXIdTrait;
    bamm:exampleValue "urn:uuid:580d3adf-1981-44a0-a214-13d6ceed9379".
:CatenaXIdTrait a bamm-c:Trait;
    bamm:name "CatenaXIdTrait";
    bamm:preferredName "Catena-X ID Trait"@en;
    bamm:description "Trait to ensure data format for Catena-X ID"@en;
    bamm-c:constraint :UUIDv4RegularExpression;
    bamm-c:baseCharacteristic :UUIDv4.
:UUIDv4RegularExpression a bamm-c:RegularExpressionConstraint;
    bamm:name "UUIDv4RegularExpression";
    bamm:preferredName "Catena-X Id Regular Expression"@en;
    bamm:description "The provided regular expression ensures that the UUID is composed of five groups of characters separated by hyphens, in the form 8-4-4-4-12 for a total of 36 characters (32 hexadecimal characters and 4 hyphens), optionally prefixed by \"urn:uuid:\" to make it an IRI."@en;
    bamm:value "(^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$)|(^urn:uuid:[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$)";
    bamm:see <https://datatracker.ietf.org/doc/html/rfc4122>.
:UUIDv4 a bamm:Characteristic;
    bamm:name "UUIDv4";
    bamm:preferredName "UUIDv4"@en;
    bamm:description "A version 4 UUID is a universally unique identifier that is generated using random 32 hexadecimal characters."@en;
    bamm:dataType xsd:string.

MS1 Criteria

[x] The proposed aspect model does not exist already
[x] The proposed aspect model does not extend an existing aspect but introduces completely new functionality
[x] The proposal references a Catena-X use case
[x] Relevant standards are mentioned/linked
[x] A first draft of the data structure is provided in an example

modeling_team

[ok]model doesn't exist
[ok] not relevant for shared aspect model
[ok] not individual use case, for all BAMM models that uses catenaXId
[ok] standard is linked, uuid with prefix
[ok] example given

@bs-jokri
MS1 approved

While you're at it - I think there is a general conversation to be had about how closely the models should be tied to Catena-X. There is a general consensus that Submodel Templates generated from SAMM should be proposed in the IDTA. The IDTA will not standardize something that is called "catenaXId". My proposal would be to avoid:
{
  "catenaXId": "foobar"
}

and to encourage something like
{
  "idType": "catenaXId",
  "value": "foobar"
}

Of course this is going to be ugly af when SAMM-properties are mapped to AAS-properties but it's the best I can think of.

The alternative might be also something like a property "assetId" and a value like
urn:dataspace:catena-x:caenaXId:foobar
or two models: one with an abstract identifier and another one derived from it with a catena-x specific ID
abstract id
catenaXId inherits from abstract id

@jacewski-bosch - can I assist you with the modeling in any way?

authors: BirgitBoss ZazraltMagic arnoweiss jacewski-bosch

repo: eclipse-tractusx/sldt-semantic-models


text:
Include OpenSSF score card

As designed by the OpenSSF, this workflow will work only it has been merged to main:
2024/11/10 09:08:32 creating scorecard entrypoint: validating options: only default branch is supported
EnvGithubAuthToken: GITHUB_AUTH_TOKEN ***
refs/heads/gardena/rs/upstream/run-openssf-score-card not supported with push event.
Only the default branch main is supported.

Until then, the following can be done to verify this:

Apply this PR to main of a dedicated testing fork (e.g. https://github.com/rettichschnidi/wakaama/commit/0e266917cbde85d8482824ca68e1849aacdabbda)
Check out the score card generated by the OpenSSF (unfortunately, they are still using the old URL)
Check out the badge generated by the OpenSSF:  (unfortunately, they are still using the old URL)

LGTM

authors: LukasWoodtli rettichschnidi

repo: eclipse-wakaama/wakaama


text:
Consistency in basic ssarch figure. Order and arows

Changed arrow direction to reflect logical flow of data for consumers
Changed consumer order for easier readability

How about, on Consumer 1 I change text to get/subscribe to indicate both options, and on "consumer n" I remove the text and make a double arrow, das you suggested?
The the first two are like "examples" ordered according to logical data flow direction, and the "n" is the generic template

Done


text:
OSCORE Californium API/behavior changes.

I will list here all the Californium changes we talked about with @rikard-sics.

probably move classes about OscoreStore in org.eclipse.leshan.core.californium.oscore.cf(or something like this) from Leshan to Californium.
Add a way to specify in EndpointContext the recipient ID targeted. (https://github.com/eclipse/leshan/pull/1212#discussion_r830937966)
Being able to create an CoapEnpoint which allow OSCORE communication only.
Do not send Request if there is an OSCORE option but no context (see https://github.com/eclipse/leshan/pull/1212#issuecomment-1072266510)
(maybe some context lifetime feature ? (https://github.com/eclipse/leshan/issues/1230)
(maybe a fix about :https://github.com/eclipse/leshan/pull/1226#issuecomment-1086024736)

@rikard-sics tell me if I missed something ?

Yes I had many of the same points listed down.
The only possible additions are:

It could be better to have an API which doesn't need a CBOR object but just a int ?

In the OSCoreCtx constructor? Yeah I think that would be convenient and make sense.

Yes or/and adding AlgorithmID.fromValue(int value) ?

Yep, that one also makes sense to add.

(Not really an API changes but maybe a tiny bug ?)
In org.eclipse.californium.oscore.OSCoreCtx.OSCoreCtx() line 319
try {
	this.sender_key = deriveKey(this.common_master_secret, this.common_master_salt, this.key_length, digest,
			info.EncodeToBytes());
} catch (CoseException e) {
-	LOGGER.error(e.getMessage());
-       throw new OSException(e.getMessage());
+	LOGGER.error(e.getMessage(), e);
+      throw new OSException(e.getMessage(), e);
}

First line, it could make sense to display exception stack trace in the log.
Second line, CoseException should be added as cause of OSException
(except all of this is hiding for Security reason ?)

(except all of this is hiding for Security reason ?)

Yes, I did not write that particular code (it was a previous colleague), but I could imagine it was for security reasons.

I think we have a good list of changes to be done in Californium then. I have one PR pending related to the plugtest server/client, after that has been merged I can go through and perform these changes.

I added the point about Ctx.setURI raised at : https://github.com/eclipse/leshan/pull/1232#discussion_r841851488

(@rikard-sics  just to let you know : I will be unavailable from the end of day to Monday 18th april, back on Tuesday)

(@rikard-sics just to let you know : I will be unavailable from the end of day to Monday 18th april, back on Tuesday)

Okay, thanks for letting me know.
Meanwhile I can spend time on testing the current code (as you mention in #920), and work on implementing the additions to Californium.

@rikard-sics any news about this :slightly_smiling_face:  ?

@rikard-sics any news about this slightly_smiling_face ?

I have been focusing a bit on the addition of OSCORE support to the sandbox client/server in Californium, and related discussions on interoperability with libcoap that was triggered by this which took some time to investigate.
However, I have begun working on some of the points listed and am planning to create a PR covering those. Currently I am on a business trip and will be back on Saturday so probably I can get this first PR done by the middle of next week.
When I create the PR you could also review it to check that it suits the intended functionality.

OK I will be often unavailable during April and May. (e.g. I'm back on Tuesday)
Do you think Leshan opened PR about OSCORE should be merge in oscore branch or prefer to wait you test it more ?

@rikard-sics, I integrated all opened OSCORE PR in oscore branch.
For the integration in master I don't know yet, maybe too soon.  :thinking:
Just to let you know about my availability on May :
I will be unavailable :

from April 29th to May 8th (included)
from May 13th to 22th
and  26/27th

then I will be avaialble again as usual :slightly_smiling_face:.

@rikard-sics, I try to move forward on Bootstrap config support at server side : #1254
(to do that I rebase oscore branch again on master)

@rikard-sics, let me know if I can help in any way ?

Working on #1220, I found a blocker issue :x:.
For transport layer abstraction, we need to know the endpoint which receive a request.
We currently retrieve it using Message.getLocalAddress() :
/**
 * Gets the local address of the receiving endpoint.
 *
 * @return local address of the receiving endpoint. {@code null} for
 *         outgoing messages.
 * @since 3.0
 */
public InetSocketAddress getLocalAddress() {
	return localAddress;
}

But with OSCORE this returns null, maybe because a request is created under the hood and this field in not set.
(maybe here ? : https://github.com/eclipse/californium/blob/main/cf-oscore/src/main/java/org/eclipse/californium/oscore/OptionJuggle.java#L280-L291)

repo: eclipse/leshan


text:
Deploy releases on central

RC2 is not public, not sure the intention behind but it makes the spec not adoptable

We had a discussion on the MicroProfile mailing list about it. RCs are not public and require a bit of "config" (add the repository). Only the 1.0.0 will be GA. I don't have a strong opinion about it but it seems to be the MicroProfile process.

I would be more than happy to click the button to deploy to central right now, but I've been told that's not how we do things in MicroProfile. This is an issue to bring up with the rest of the MicroProfile community, perhaps at the next community hangout.
In the meantime, it can be consumed from the Sonatype staging repository, https://oss.sonatype.org/content/repositories/orgeclipsemicroprofile-1126. That repo won't be around forever, Sonatype automatically drops them after a month (and this is another reason why I don't like not deploying to central), so for people that want a stable artifact location that they can rely on, I've deployed it to my own bintray repository, at https://dl.bintray.com/jroper/maven.

Hi @jroper can you bring it to next MP meeting please?
Another question is: does the staging existence means the review process didnt happen or passed? (https://www.eclipse.org/projects/handbook/#release)

I raised this issue on the mailing list, and it turns out the only reason we don't publish RCs to Maven central is that no one ever asked to. So 1.0-RC2 is now published to Maven central.

authors: cescoffier jroper rmannibucau

repo: eclipse/microprofile-reactive-streams


text:
Should AbstractCloseableIterator implement AutoCloseable?

AbstractCloseableIterator already implements Closeable but should it also implement AutoCloseable?
If so this might be considered an API change. Even though AutoCloseable is a java.lang default imported type and all implementations will behave correctly as the Interface contract is already provided by the fact that Closeable is already a super Interface.
In any case it will allow using try-with-resources for any code, with the relevant IDE warnings etc.

Do we even still use that class anywhere in our code? The distinction we previously made between iterations and iterators has become less necessary since RDF4J exceptions were made unchecked by default.
I wonder if we could clean up things a little and replace its use with AbstractCloseableIteration everywhere (or the other way around).

I pretty much only found this use case:
https://github.com/eclipse/rdf4j/blob/07d77aca70acff4229f89fdfa5e3932629b2bf04/core/queryalgebra/evaluation/src/main/java/org/eclipse/rdf4j/query/algebra/evaluation/iterator/HashJoinIte
ration.java#L135

Btw I'm not against making it autocloseable either. @JervenBolleman what is that you needed this for? Do you use it internally?

Mostly, I am just trying to be a good citizen with my new write-once/read-lots sail. Where I need to do some stream like operations with iterators so I was looking into which style code RDF4J uses, and then I noticed this.

Let's just go with making it AutoCloseable, I don't think this counts as a backward-incompatible change so am fine with putting this in the next minor release.
The discussion about cleaning up some of the redundancies between Iterators and Iterations is something we can do separately.

authors: JervenBolleman hmottestad jeenbroekstra


text:
Add methods on org.eclipse.rdf4j.rio.RDFHandler to help with pretty-printing

It could be useful to be able to have advisory methods that signal:

that a blank node that will only be use for a relatively short time is about to be used.
that the last statement using such a blank node has been seen.

The idea is to be able to signal that turtle/TriG '[]' formatting may be possible, without having to rely on a fixed size buffer. ( I think I'm missing a semantic condition here. )
This could be generalized to signaling the start of a sequence of statements that will contain all uses of an identifier in a subject position, as well as indicating that no more statements using that identifier as subject will be used.
It would also be useful to be able to signal that a blank node will identify an rdf:List instance that is

the object of precisely one property, and that that property is not rdf:rest, and
that the instance is the subject of precisely two statements, one of which has a property of rdf:first and the other has a property of rdf:rest, and
the object of the rdf:rest property is either nil, or an instance of rdf:List satisfying conditions 2 and 3., and which is the object of no other statement.

The idea is to be able to signal that '(...)' abbreviation is possible.
All of these methods could have default implementations that are no-ops.

+1, would be very useful to use default methods in this way to add optionally supported methods. In this case, if the writer/handler doesn't recognise the signal they are free to ignore it without corrupting any data.

Rio.write(Iterable<Statement> model, RDFHandler writer) method checks if a model is instance of Model class. In practice namespaces are printed only in case of Model.

Release related question:
As a matter of release engineering policy, do team rdf4j consider default methods on interfaces like RDFHandler to be Major or Minor?
The Java language specification explicitly classes them as binary compatible; however the eclipse classification treats them as generally breaking iff the interface may be implemented by outside classes.
This is because there is an edge case where under release n, such a class might implement an interface that has a  default method with the same ; if the added default method has the same signature and name, (and is used but not implemented, IIR), there can be a run time error.
If such a clash is unlikely, the guidelines say it can be treated as non breaking. I'd say this is the case here.
If the change is still pending, when are the cutoff dates for the next minor, or the next major if appropriate?
(I have been spending an ungodly amount of time examining backwards compatibility in all OSGI bundle series on maven central. Exploratory data analysis indicates that almost everyone lies about semantic versioning. I have to post my hypotheses before running real experiments)

There is the possibility that default methods could be binary incompatible if another interface defines the same method name already with a different signature. Having said that, there is no way to know what users are currently inheriting besides our classes (and we have a fairly high chance of noticing if we made that mistake ourselves).
Personally I am all in for adding default methods to interfaces in minor releases, not patch releases. It is one of the best lifecycle features Java has ever thought up IMO.

New interfaces can also be added in minor releases as long as they don't break any existing public APIs. I will add a new interface for NamespaceAware or similar, with the naming open for discussion still. The existing Rio.write methods will need to stay, but I will modify the instanceof check internally for the new interface.
RepositoryResult<Statement> is difficult as it is an iteration of Statement, not a collection of Statement with Namespace attached. Not sure how to fix that one other than to also support another Rio.write signature, but will also explore that in a PR.

authors: ansell jgrzebyta sesuncedu


text:
issue#273 : Use non-deprecated methods to be compatible with jackson2.7+

This PR addresses GitHub issue: #273
Briefly describe the changes proposed in this PR:

Fix use of deprecated Jackson public API methods/variables including one that was removed in 2.7

Make sure you've followed the Contributor Guidelines. In particular (please tick to indicate you've taken care of it):

[x] RDF4J code formatting has been applied
[n/a] tests are included
[x] all tests succeed

Lf2SpacesIndenter was removed in 2.7, so to be compatible with
2.7/2.8/etc. changing here to use the new name for it. There is no need to update to Jackson-2.7/2.8 at this point, other than to get bug fixes, but this will make it possible to interoperate with other libraries that do depend on features added there.
The previous pull request was targeted at master, but I would like this to be fixed in 2.0 given it is a small change.
Signed-off-by: Peter Ansell p_ansell@yahoo.com

Looks good to me.

authors: ansell jeenbroekstra


text:
How to warp text on android?

Question

How to warp text on android

There's not much to go on here; a code snippet would help to know where you are starting from.  And I assume you mean wrap not warp.
If you have something like this:
import {TextView, contentView} from 'tabris';

new TextView({
  top: 0, left: 0,
  text: 'Hello World!'
}).appendTo(contentView);

You will notice that the text will start in the upper left corner and continue on to the right for all the text specified.
If you add right as specified like so:
new TextView({
  top: 0, left: 0, right: 0,
  text: 'Hello World!'
}).appendTo(contentView);

It will force the TextView to end at the right edge of the screen, and text will flow to the next line as necessary.
There's also a Tabris.js Slack Channel full of experts that can answer questions any time

Thank you!

repo: eclipsesource/tabris-js


text:
get_request() or get_remote()

I am having this problem with the newer version. But it works fine with the older version (1.3.0). Can anyone help? am i doing it wrong? @mcucchi9 @malmans2
import cads_api_client

url = 'https://cds-beta.climate.copernicus.eu/api'
key_tisanjid = '45b3b45b-a89c-47c9-87bd-76249d963***' # changed it to keep it secret.

client=cads_api_client.ApiClient(key_tisanjid,url)

request_id='4224adc8-29a0-4961-ad54-e6c8f89ff2c2'
print(type(request_id))
r=client.get_request(request_id).make_remote()
reply=r.status
print(reply)

---------------------------------------------------------------------------
MissingSchema                             Traceback (most recent call last)
[<ipython-input-5-43d533076d30>](https://localhost:8080/#) in <cell line: 11>()
      9 request_id='4224adc8-29a0-4961-ad54-e6c8f89ff2c2'
     10 print(type(request_id))
---> 11 r=client.get_request(request_id).make_remote()
     12 reply=r.status
     13 print(reply)

7 frames
[/usr/local/lib/python3.10/dist-packages/requests/models.py](https://localhost:8080/#) in prepare_url(self, url, params)
    436
    437         if not scheme:
--> 438             raise MissingSchema(
    439                 f"Invalid URL {url!r}: No scheme supplied. "
    440                 f"Perhaps you meant [https://{url}?](https://{url}/?)"

MissingSchema: Invalid URL '45b3b45b-a89c-47c9-87bd-76249d963814/retrieve/v1/jobs/4224adc8-29a0-4961-ad54-e6c8f89ff2c2': No scheme supplied. Perhaps you meant https://45b3b45b-a89c-47c9-87bd-76249d963814/retrieve/v1/jobs/4224adc8-29a0-4961-ad54-e6c8f89ff2c2?

Hi @ti-sanjid,
This is a breaking change in cads-api-client, sorry about that! Please note that at the moment cads-api-client is not stable.
We inverted the order of the arguments key/url to align with cdsapi. Any of the following should work:
client=cads_api_client.ApiClient(url, key_tisanjid)

client=cads_api_client.ApiClient(key=key_tisanjid, url=url)

Thanks a lot. Now it works perfectly fine.

repo: ecmwf-projects/cads-api-client


text:
提供lru的封装

#3
考虑3个场景:
场景1:用户删除注入cache中的key--需要同步删除lru副本中的key；
场景2:执行lru淘汰--需要同步删除注入cache中的key；
场景3:过期淘汰--需要同步删除lru副本中的key；
可以总结出两个方向的调用:
方向1:场景1&场景3--先删cache—触发删除lru的keys
方向2:场景2--先删lru--触发删除cache中的数据
实现方式：
Lru的keys key存放cache中的key，val存放枚举值，用于标识这个key在删除调用过程中应该走哪些分支,避免触发循环回调
fromCache对应方向1   fromLru对应方向2

OK，等我今晚上完课或者明天看看

哦哦哦好的，有个问题，golang-lru.expirable golang-lru只提供了统一的key过期时间，不支持对key指定过期时间，如果适配过来的话对key指定过期时间这个功能就需要阉割掉了；如果我们既要用golang-lru又要自己管理过期时间的话，实现方式和这个关闭的pr差不多，但会存在并发问题。这样看来最合适的办法是自研一个

repo: ecodeclub/ecache


text:
萌新 落落的问 个问题

在vue中怎么引入 这个气泡球插件
Error: Component series.liquidFill not exists. Load it first.
堆栈跟踪：
clazz.enableClassManagement/entity.getClass@webpack-internal:///23:166:23
visitComponent/<@webpack-internal:///440:195:51
each@webpack-internal:///0:263:13
visitComponent@webpack-internal:///440:178:17
componentUtil.enableTopologicalTravel/entity.topologicalTravel@webpack-internal:///89:89:21
mergeOption@webpack-internal:///440:147:13
initBase@webpack-internal:///440:642:9
resetOption@webpack-internal:///440:92:21
setOption@webpack-internal:///440:74:13
echartsProto.setOption@webpack-internal:///1:279:9
initChart@webpack-internal:///208:65:7
boundFn@webpack-internal:///17:184:9
mounted@webpack-internal:///208:27:5
callHook@webpack-internal:///17:2666:9
insert@webpack-internal:///17:3527:7
invokeInsertHook@webpack-internal:///17:5470:9
patch@webpack-internal:///17:5640:5
lifecycleMixin/Vue.prototype._update@webpack-internal:///17:2425:16
updateComponent@webpack-internal:///17:2539:7
get@webpack-internal:///17:2882:13
run@webpack-internal:///17:2959:17
flushSchedulerQueue@webpack-internal:///17:2725:5
queueNextTick/<@webpack-internal:///17:702:11
nextTickHandler@webpack-internal:///17:649:7

在echarts/index.js里面加上require('../echarts-liquidfill/index')就可以了，试试看~

repo: ecomfe/echarts-liquidfill


text:
tool/color Gradient

生成渐变颜色的API不存在?
getGradientColors echart-example
getLinearGradient zrender-api#getGradientColors
tool/color中并没有上述方法
tool/color.js
我需要自己调用graphic/LinearGradient?或者其他api?
烦请更新一下doc&相关的example

自己引用了LinearGradient,echart2引用的zrender版本也比较早,就这样吧

repo: ecomfe/zrender


text:
Broken for relativeElement with dynamic height

Hello!
I've been trying to use this plugin for my list of ajax-fetched results and it seems vue-affix can't properly deal with the relativeElement which height is changing during his lifetime. vue-affix saves the dimensions of relativeElement when it's mounted. If it's height changes, vue-affix is not catching the change.
I tried to extract the initialization logic to separate methods to make it able to control the flow but i'm not too good at JS and it's still broken, just in a different way. I'm gonna try to show you some demo of this later but, for now: is there anything you can say is 100% wrong in my code?: https://gist.github.com/mbajur/8273745f03846fd153e0f4b3083be9f3
Sample usage:
<template>
  <affix :delayed="true" ref="affix">...</affix>
</template>

<script>
  export default {
    // ...

    methods: {

      // First fetch
      onAjaxFetched () {
        this.$refs.affix.start()
      },

      // All the next fetches
      onAjaxFetchedMore () {
        this.$refs.affix.update()
      }
    }

    // ...
  }
</script>

Thanks in advance!

Ok, i created a sample project to illustrate my problem: https://github.com/mbajur/vue-affix-delayed

Here are few scenarios i have a problem with:

First of all - the original package. You can test the behaviour i mentioned in original post by uncommenting the regular vue-affix import in App.vue and commenting the custom one. Loading first set of results is delayed so vue-affix makes it's calculations for non-filled results div (which has no height). When results comes up - affix thinks bottom of a relative div is way higher than it really is. You can see it by just scrolling down the page and looking at the green element.
For the first, initial set of results, red affix is not working at all. After adding another set of 10 results, it starts to work but acts weird (start scrolling down - red box will start to scroll with the page way too early)
Load the page, scroll to the bottom and refresh the page. This is where things goes mad - the red box has a weird top offset instead of top: 0 and is basically permanently sticked to the top. Untill you click the "Add 10 results" - this is fixing the issue.

I'm still working really hard on #3 and will probably finish it tonight, then I'll have a look at this closely. I was sure it would have problems with dynamic content but didn't have the time to test yet, sorry for the lack of time :(
Thanks for the feedback!

Hey, sure, don't stress yourself, i really appreciate what you've done so far in here :) That's also probably the only affix/sticky plugin for vue out there and i need to use affix/sticky in my project pretty bad so i'm gonna do whatever i can to help in here with that. Let me know if you need any more feedback or testing when time will come.

Thanks for that :D
I'm changing a lot of things while implementing #3, refactoring a lot of code, I made this plugin in one day last weekend and it still have a lot of early stage code, but when I finish it I will sure ask for more tests regarding this issue :)

Hello, could you update the lib and test it again? I rewrote almost the whole code and I wanted to see if your problem still persists. I didn't work to fix it but it might be good after this refactoring. If you still have problems, describe them here again and I'll take a close look this weekend.
Thanks :)

Ha! yes, now it all works as it should. All my issues are gone :) Thanks for the awesome work!

Awesome :D
Its good to know the performance is better, as I said, i rewrote almost everything and it's much better now, I just need to update the docs with the new functionalities.

authors: eddiemf mbajur

repo: eddiemf/vue-affix


text:
[Feature Request]: Add top padding to maximized window

Description
Make more consistent with how Chrome appears by adding a few pixels(I counted ~6 pixels on Chrome) of padding to the top of the browser window. On top of being more consistent with Chrome, it also accentuates the fact that tabs are rounded.
Firefox:

Chrome:

Additional info (Optional)
Firefox version: 128.0
Operating system: Windows 10 (64-bit)

There are no indentations in the old UI, you should enable userChrome.ui-chrome-refresh if you want this.

authors: Crunchbits edelvarden

repo: edelvarden/material-fox-updated


text:
Edit broken link to raw script in README

Self-explanatory

Good catch, thank you!

authors: HugoGiraudel cdax


text:
Data loss when recording data over BLE.

When recording data over BLE, some data can get lost when the tab / browser is inactive.
Maybe this only occurs when the notebook is running on battery power.

hotefix: show warning when the user switches the tab and let them confirm? is it only during tab switches or also when the browser is in the background?
warning should only show once before page is reloaded to avoid annoying the user

I am not quite sure when exactly this happens. I just found the execution of js code is being stopped when the browser is running in the background.
Warning the user could prevent the problem for now.

Per default I would guess js code keeps running even after tab switches. Are we using setInterval or any related functions?

Did we ever look into this issue @tk-king ?

Yes we did, but the exact reason for the data loss could not be determined yet as the behavior seems to be inconsistent, at least on my machine.

authors: TobiasRoeddiger tk-king

repo: edge-ml/frontend


text:
Update gh-pages.rake

Allow configuration of Website root directory.
I'm using middleman-gh-pages to publish the website of a C library project and doesn't want to have any Ruby stuff on the toplevel, mixed in with the autotools stuff. This quick and dirty patch allow you to configure the PROJECT_ROOT from the Rakefile (which isn't ideal but has the advantage of having the smallest impact possible on your code).

Just triaging. I know this PR has sat open and untouched for a long time now, but I wanted to open the discussion again and check if it's still relevant. I'm not sure I'm properly following the use-case yet.

I'm using middleman-gh-pages to publish the website of a C library project and doesn't want to have any Ruby stuff on the toplevel.

Ruby stuff at the toplevel of what? Autotools stuff? Only the build directory should be getting pushed to the gh-pages branch (and that can be .gitignored). Are you saying that the middleman source is not the root of the repository?

To be honest, I don't remember at all. I'll go have a look on the project

My project is a C library, it has a whole autotools setup at the root of the git repository.
I want my middleman-gh-pages data/config/files to be stored in a www folder, so I set the ROOT_FOLDER in my rakefile.
Here's how I use it:
  PROJECT_ROOT = `git rev-parse --show-toplevel`.strip + '/www'

  require 'middleman-gh-pages'

To answer your question :

Are you saying that the middleman source is not the root of the repository?

Yes !

Understood. Thanks. I think this would be better solved with ENV variables -- just to stay consistent with the other configuration parameters used on the project, but I better understand your use-case now. Thanks.

Closed by 8346e4e

repo: edgecase/middleman-gh-pages


text:
Fails at cmake on Windows

I got an issue while making .uf2 on Windows CMD. And it fails at "cmake -G "NMake Makefiles" .."
C:\Pico\firmware-pi-rp2040-main\build>cmake -G "NMake Makefiles" ..
PICO_SDK_PATH is C:/Pico/pico-sdk
PICO platform is rp2040.
CMake Error at ThirdParty/FreeRTOS-Kernel/portable/ThirdParty/GCC/RP2040/CMakeLists.txt:17 (project):
Running
'nmake' '-?'
failed with:
The system cannot find the file specified
-- Configuring incomplete, errors occurred!
See also "C:/Pico/firmware-pi-rp2040-main/build/CMakeFiles/CMakeOutput.log".

This is an issue with selecting the makefile generator, I think by default on Windows it will try to use NMake (Visual Studio??). You have to manually state the generator that you use.
If you use VS Code and CMake extension then you could  add  "cmake.generator": "MinGW Makefiles", to settings.json file

authors: Abby-Sun micropicostack


text:
Updated checksec to version 1.7.10

Updated checksec recipe to source from maintained github repository, included two patches; a whitespace fix and a fix to work with busybox-sysctl.

@dbge do you want me to approve this or are you planning on moving this recipe into meta-edgeos so its applied to both morty and pyro?

@jpward, I'll be reissuing the PR for meta-edgeos today so it can be applied to both morty and pyro branches. Was just getting other commits lined up for PR today as well. I'll close this one out.

authors: dbge jpward

repo: edgeos/meta-security


text:
build: update alpine base to 3.14

Signed-off-by: Leonard Goodell leonard.goodell@intel.com
PR Checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What is the current behavior?

Issue Number:
What is the new behavior?
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Are there any new imports or modules? If so, what are they used for and why?
Are there any specific instructions or things that should be known prior to reviewing?
Other information

recheck

recheck

recheck

repo: edgexfoundry/app-rfid-llrp-inventory


text:
docker-compose-fuji.yml  run error

.../releases/fuji/compose-files/docker-compose-fuji.yml
#docker-compose -f docker-compose-fuji.yml  up
# docker ps -a |grep Exit
7430ac892aa2 edgexfoundry/docker-support-rulesengine:1.1.0         7 minutes ago  Exited (1)
46e6f2b4c4e4 edgexfoundry/docker-app-service-configurable:1.0.0   7 minutes ago  Exited
f8ff77b73b86 edgexfoundry/docker-core-command-go:1.1.0             7 minutes ago  Exited (0)
c6c03c85bb85 edgexfoundry/docker-support-scheduler-go:1.1.0       7 minutes ago  Exited (0)
81854df184d0 edgexfoundry/docker-core-metadata-go:1.1.0             7 minutes ago  Exited (0)
1ae2227893a0 edgexfoundry/docker-support-notifications-go:1.1.0   7 minutes ago  Exited (0)
d32c1b30bea4 edgexfoundry/docker-core-data-go:1.1.0                    7 minutes ago  Exited (0)
dfd61bf9713e edgexfoundry/docker-support-logging-go:1.1.0          7 minutes ago  Exited (0)
edf57ffd09e2 edgexfoundry/docker-core-config-seed-go:1.1.0          7 minutes ago  Exited (0)
496a8ae2c227 portainer/portainer                                                        7 minutes ago  Exited (1)
# docker logs d32c1b30bea4
level=INFO ts=2020-03-12T04:30:38.745664818Z app=edgex-core-data source=registry.go:144 msg="Writeable configuration has been updated from the Registry"
Post http://edgex-support-logging:48061/api/v1/logs: dial tcp 172.29.0.11:48061: connect: connection refused
level=WARN ts=2020-03-12T04:30:50.54718672Z app=edgex-core-data source=database.go:112 msg="couldn't retrieve database credentials: Unable to obtain secrets from underlying data-store: Received a '503' response from the secret store"
Post http://edgex-support-logging:48061/api/v1/logs: dial tcp 172.29.0.11:48061: connect: connection refused
level=WARN ts=2020-03-12T04:31:04.181010116Z app=edgex-core-data source=database.go:112 msg="couldn't retrieve database credentials: Unable to obtain secrets from underlying data-store: Received a '503' response from the secret store"
Post http://edgex-support-logging:48061/api/v1/logs: dial tcp 172.29.0.11:48061: connect: connection refused
level=WARN ts=2020-03-12T04:31:16.971770254Z app=edgex-core-data source=database.go:112 msg="couldn't retrieve database credentials: Unable to obtain secrets from underlying data-store: Received a '503' response from the secret store"
# docker logs dfd61bf9713e
level=INFO ts=2020-03-12T04:30:35.03631324Z app=edgex-support-logging source=registry.go:144 msg="Writeable configuration has been updated from the Registry"
level=WARN ts=2020-03-12T04:30:47.201160753Z app=edgex-support-logging source=init.go:82 msg="couldn't retrieve database credentials: Unable to obtain secrets from underlying data-store: Received a '503' response from the secret store"
level=WARN ts=2020-03-12T04:30:59.988612957Z app=edgex-support-logging source=init.go:82 msg="couldn't retrieve database credentials: Unable to obtain secrets from underlying data-store: Received a '503' response from the secret store"
level=WARN ts=2020-03-12T04:31:13.191743962Z app=edgex-support-logging source=init.go:82 msg="couldn't retrieve database credentials: Unable to obtain secrets from underlying data-store: Received a '503' response from the secret store"

Need the output of edgex-vault and edgex-vault-worker to see what is going on.  Edgex-vault has the server process that is returning the 503.  edgex-vault-worker is the process that seeds the database passwords.

No activity in > 6 months.

authors: bnevis-i jpwhitemn zhanglt

repo: edgexfoundry/developer-scripts


text:
fix: missing configuration.toml in release packages

Signed-off-by: Malini Bhandaru mbhandaru@vmware.com
PR Checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-cli/blob/master/.github/Contributing.md.
What is the current behavior?

Issue Number: 353
What is the new behavior?
Bundle contains res directory with configuration.toml
Does this PR introduce a breaking change?

[ ] Yes
[X ] No

New Imports

[ ] Yes
[X ] No

Specific Instructions
Are there any specific instructions or things that should be known prior to reviewing?
Do we want to include an install script or modify docs to give install instructions?
Snaps hashes will need to change too and the location where the configuration.toml is copied to.
Other information

Codecov Report

Merging #357 (4ad0f08) into master (1412a6a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #357   +/-   ##
=======================================
  Coverage   14.51%   14.51%
=======================================
  Files           3        3
  Lines          62       62
=======================================
  Hits            9        9
  Misses         53       53

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 1412a6a...4ad0f08. Read the comment docs.

Codecov Report

Merging #357 (4ad0f08) into master (1412a6a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #357   +/-   ##
=======================================
  Coverage   14.51%   14.51%
=======================================
  Files           3        3
  Lines          62       62
=======================================
  Hits            9        9
  Misses         53       53

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 1412a6a...4ad0f08. Read the comment docs.

Thank you @difince for catching the semantic PR issue. I had mentioned in the PR message the issue you raised ...
"Do we want to include an install script or modify docs to give install instructions?
Snaps hashes will need to change too and the location where the configuration.toml is copied to."

Thank you @difince for catching the semantic PR issue. I had mentioned in the PR message the issue you raised ...
"Do we want to include an install script or modify docs to give install instructions?
Snaps hashes will need to change too and the location where the configuration.toml is copied to."

@mkbhanda, @jpwhitemn, @lenny-intel
My suggestion for the installation process/documentation is to be like that:

Download the appropriate distribution archive for your operating system containing the edgex-cli executable from GitHub.

Unpack the edgex-cli distribution archive into a desired installation directory {installation dir}.

Start the application by opening a console, cd into "{installation dir}" and type:
./edgex-cli (device list)
This should initialize configuration.toml file in the "~/.edgex-cli" directory if it does not exists:

[OPTIONAL] Add "{installation dir}" to your PATH environment
variable so that edgex-cli could be run from any directory.

From implementation point of view Step number 2) means:
Prior executing a command (example edgex-cli device list), the application need to validate that ~/.edgex-cli/configuration.toml file exists.

If the file exists, it load the configuration and continue with the specified command execution. ( current functionality)
If the file does not exists, create directory ~/.edgex-cli with 744 permissions, and copy ./res/configuration.toml file (already part of the distribution archive done by @mkbhanda ) into the newly created  ~/.edgex-cli directory and then continue with the execution of the specified command. (instead of having additional installation script)

Note: at the moment all archives contains edgex-cli executable file under different name:  edgex-cli-linux-amd64, edgex-cli-linux-arm64,  edgex-cli-mac, edgex-cli-win.exe. Let's make them consistent

@mkbhanda, @jpwhitemn, @lenny-intel
My suggestion for the installation process/documentation is to be like that:

Download the appropriate distribution archive for your operating system containing the edgex-cli executable from GitHub.

Unpack the edgex-cli distribution archive into a desired installation directory {installation dir}.

Start the application by opening a console, cd into "{installation dir}" and type:
./edgex-cli (device list)
This should initialize configuration.toml file in the "~/.edgex-cli" directory if it does not exists:

[OPTIONAL] Add "{installation dir}" to your PATH environment
variable so that edgex-cli could be run from any directory.

From implementation point of view Step number 2) means:
Prior executing a command (example edgex-cli device list), the application need to validate that ~/.edgex-cli/configuration.toml file exists.

If the file exists, it load the configuration and continue with the specified command execution. ( current functionality)
If the file does not exists, create directory ~/.edgex-cli with 744 permissions, and copy ./res/configuration.toml file (already part of the distribution archive done by @mkbhanda ) into the newly created  ~/.edgex-cli directory and then continue with the execution of the specified command. (instead of having additional installation script)

Note: at the moment all archives contains edgex-cli executable file under different name:  edgex-cli-linux-amd64, edgex-cli-linux-arm64,  edgex-cli-mac, edgex-cli-win.exe. Let's make them consistent

My suggestion for the installation process/documentation is to be like that:

Sound like a good plan to me. I like that it initializes the toml file the first time so I don't have to worry about copying it to the correct place. From a maintenance perspective,  should remove the default toml file from edgex-cli since there will be duplicate in code and don't want to have to keep them in sync.

My suggestion for the installation process/documentation is to be like that:

Sound like a good plan to me. I like that it initializes the toml file the first time so I don't have to worry about copying it to the correct place. From a maintenance perspective,  should remove the default toml file from edgex-cli since there will be duplicate in code and don't want to have to keep them in sync.

@lenny-intel
There is not need to keep them in sync. If the configuration.toml file in ~/.edgex-cli directory exists this is the only source of information. But yes, we could accept it could be confusing having two configuration file one in the {installation-dir} and one in ~/.edgex-cli directory.
But ... I want even if the user delete ~/.edgex-cli directory, to be able to recreate it using the configuration file in the {installation directory}.

@lenny-intel
There is not need to keep them in sync. If the configuration.toml file in ~/.edgex-cli directory exists this is the only source of information. But yes, we could accept it could be confusing having two configuration file one in the {installation-dir} and one in ~/.edgex-cli directory.
But ... I want even if the user delete ~/.edgex-cli directory, to be able to recreate it using the configuration file in the {installation directory}.

Summarize the decision make in Core WG on 01/07/2021:

Rename configuration.toml file used as a template to .template_configuration.toml
binary edgex-cli  should be responsible to check if configuration.toml file in user HOME directory exists
If it does not exist - edgex-cli should copy the .template_configuration.toml file part of the distribution archive to user HOME dir and notify the user. (no need of installation script)

Summarize the decision make in Core WG on 01/07/2021:

Rename configuration.toml file used as a template to .template_configuration.toml
binary edgex-cli  should be responsible to check if configuration.toml file in user HOME directory exists
If it does not exist - edgex-cli should copy the .template_configuration.toml file part of the distribution archive to user HOME dir and notify the user. (no need of installation script)

@difince -- love your suggestion to copy configuration.toml if it does not exist on first run, echoing @lenny-intel and the renaming the file to "template-configuration.toml" or sample-configuration.toml, which would remove any confusion.
Much thanks!

@difince -- love your suggestion to copy configuration.toml if it does not exist on first run, echoing @lenny-intel and the renaming the file to "template-configuration.toml" or sample-configuration.toml, which would remove any confusion.
Much thanks!

Thinking of folding in some symbolic links to the arch specific binaries (keeps the binaries clearly arch specific) and the symbolic link for ease of use.
Only tested the MAC version, the other linux variants look good, zip looks good, hope the windows exe symbolic works as expected.

Thinking of folding in some symbolic links to the arch specific binaries (keeps the binaries clearly arch specific) and the symbolic link for ease of use.
Only tested the MAC version, the other linux variants look good, zip looks good, hope the windows exe symbolic works as expected.

Prior merging the PR I have tested the fix on Linux machine only.
After the PR was merged I have tested the fix on windows 10 machine and it gave me an error
C:\Users\home\Downloads\edgex-cli-win-0.0.0>edgex-cli.exe device list
This version of C:\Users\home\Downloads\edgex-cli-win-0.0.0\edgex-cli.exe is not compatible with the version of Windows you're running. Check your computer's system information and then contact the software publisher.

Prior merging the PR I have tested the fix on Linux machine only.
After the PR was merged I have tested the fix on windows 10 machine and it gave me an error
C:\Users\home\Downloads\edgex-cli-win-0.0.0>edgex-cli.exe device list
This version of C:\Users\home\Downloads\edgex-cli-win-0.0.0\edgex-cli.exe is not compatible with the version of Windows you're running. Check your computer's system information and then contact the software publisher.

In addition once we run make build-all  and immediately re rerun the same command - it fails because symbolic links already exists:
difince@difince:~/git/malini/edgex-cli$ make build-all
echo "GOPATH=/home/difince/git/malini/edgex-cli/go"
GOPATH=/home/difince/git/malini/edgex-cli/go
mkdir -p bin
mkdir -p bin/AMD64
mkdir -p bin/ARM64
mkdir -p bin/MAC
mkdir -p bin/WIN
GOOS=linux GOARCH=amd64 CGO_ENABLED=0 GO111MODULE=on go build -o bin/AMD64/edgex-cli-linux-amd64 -ldflags "-X github.com/edgexfoundry/edgex-cli/cmd/version.Version=0.0.0"; cd bin/AMD64; ln -s edgex-cli-linux-amd64  edgex-cli
GOOS=linux GOARCH=arm64 CGO_ENABLED=0 GO111MODULE=on go build -o bin/ARM64/edgex-cli-linux-arm64 -ldflags "-X github.com/edgexfoundry/edgex-cli/cmd/version.Version=0.0.0"; cd bin/ARM64; ln -s edgex-cli-linux-arm64 edgex-cli
GOOS=darwin GOARCH=amd64 CGO_ENABLED=0 GO111MODULE=on go build -o bin/MAC/edgex-cli-mac -ldflags "-X github.com/edgexfoundry/edgex-cli/cmd/version.Version=0.0.0"; cd bin/MAC; ln -s edgex-cli-mac edgex-cli
GOOS=windows GOARCH=amd64 CGO_ENABLED=0 GO111MODULE=on go build -o bin/WIN/edgex-cli-win.exe -ldflags "-X github.com/edgexfoundry/edgex-cli/cmd/version.Version=0.0.0"; cd bin/WIN; ln -s  edgex-cli-win.exe edgex-cli.exe
tar -czvf bin/edgex-cli-linux-amd64-0.0.0.tar.gz Attribution.txt LICENSE -C bin/AMD64 edgex-cli-linux-amd64 edgex-cli
Attribution.txt
LICENSE
edgex-cli-linux-amd64
edgex-cli
tar -czvf bin/edgex-cli-linux-arm64-0.0.0.tar.gz Attribution.txt LICENSE -C bin/ARM64 edgex-cli-linux-arm64 edgex-cli
Attribution.txt
LICENSE
edgex-cli-linux-arm64
edgex-cli
tar -czvf bin/edgex-cli-mac-0.0.0.tar.gz Attribution.txt LICENSE -C bin/MAC edgex-cli-mac edgex-cli
Attribution.txt
LICENSE
edgex-cli-mac
edgex-cli
zip -j --symlinks bin/edgex-cli-win-0.0.0.zip bin/WIN/edgex-cli-win.exe bin/WIN/edgex-cli.exe Attribution.txt LICENSE
updating: edgex-cli-win.exe (deflated 50%)
updating: edgex-cli.exe (stored 0%)
updating: Attribution.txt (deflated 78%)
updating: LICENSE (deflated 65%)

difince@difince:~/git/malini/edgex-cli$ make build-all
echo "GOPATH=/home/difince/git/malini/edgex-cli/go"
GOPATH=/home/difince/git/malini/edgex-cli/go
mkdir -p bin
mkdir -p bin/AMD64
mkdir -p bin/ARM64
mkdir -p bin/MAC
mkdir -p bin/WIN
GOOS=linux GOARCH=amd64 CGO_ENABLED=0 GO111MODULE=on go build -o bin/AMD64/edgex-cli-linux-amd64 -ldflags "-X github.com/edgexfoundry/edgex-cli/cmd/version.Version=0.0.0"; cd bin/AMD64; ln -s edgex-cli-linux-amd64  edgex-cli
ln: failed to create symbolic link 'edgex-cli': File exists
Makefile:34: recipe for target 'build-all' failed
make: *** [build-all] Error 1

In addition once we run make build-all  and immediately re rerun the same command - it fails because symbolic links already exists:
difince@difince:~/git/malini/edgex-cli$ make build-all
echo "GOPATH=/home/difince/git/malini/edgex-cli/go"
GOPATH=/home/difince/git/malini/edgex-cli/go
mkdir -p bin
mkdir -p bin/AMD64
mkdir -p bin/ARM64
mkdir -p bin/MAC
mkdir -p bin/WIN
GOOS=linux GOARCH=amd64 CGO_ENABLED=0 GO111MODULE=on go build -o bin/AMD64/edgex-cli-linux-amd64 -ldflags "-X github.com/edgexfoundry/edgex-cli/cmd/version.Version=0.0.0"; cd bin/AMD64; ln -s edgex-cli-linux-amd64  edgex-cli
GOOS=linux GOARCH=arm64 CGO_ENABLED=0 GO111MODULE=on go build -o bin/ARM64/edgex-cli-linux-arm64 -ldflags "-X github.com/edgexfoundry/edgex-cli/cmd/version.Version=0.0.0"; cd bin/ARM64; ln -s edgex-cli-linux-arm64 edgex-cli
GOOS=darwin GOARCH=amd64 CGO_ENABLED=0 GO111MODULE=on go build -o bin/MAC/edgex-cli-mac -ldflags "-X github.com/edgexfoundry/edgex-cli/cmd/version.Version=0.0.0"; cd bin/MAC; ln -s edgex-cli-mac edgex-cli
GOOS=windows GOARCH=amd64 CGO_ENABLED=0 GO111MODULE=on go build -o bin/WIN/edgex-cli-win.exe -ldflags "-X github.com/edgexfoundry/edgex-cli/cmd/version.Version=0.0.0"; cd bin/WIN; ln -s  edgex-cli-win.exe edgex-cli.exe
tar -czvf bin/edgex-cli-linux-amd64-0.0.0.tar.gz Attribution.txt LICENSE -C bin/AMD64 edgex-cli-linux-amd64 edgex-cli
Attribution.txt
LICENSE
edgex-cli-linux-amd64
edgex-cli
tar -czvf bin/edgex-cli-linux-arm64-0.0.0.tar.gz Attribution.txt LICENSE -C bin/ARM64 edgex-cli-linux-arm64 edgex-cli
Attribution.txt
LICENSE
edgex-cli-linux-arm64
edgex-cli
tar -czvf bin/edgex-cli-mac-0.0.0.tar.gz Attribution.txt LICENSE -C bin/MAC edgex-cli-mac edgex-cli
Attribution.txt
LICENSE
edgex-cli-mac
edgex-cli
zip -j --symlinks bin/edgex-cli-win-0.0.0.zip bin/WIN/edgex-cli-win.exe bin/WIN/edgex-cli.exe Attribution.txt LICENSE
updating: edgex-cli-win.exe (deflated 50%)
updating: edgex-cli.exe (stored 0%)
updating: Attribution.txt (deflated 78%)
updating: LICENSE (deflated 65%)

difince@difince:~/git/malini/edgex-cli$ make build-all
echo "GOPATH=/home/difince/git/malini/edgex-cli/go"
GOPATH=/home/difince/git/malini/edgex-cli/go
mkdir -p bin
mkdir -p bin/AMD64
mkdir -p bin/ARM64
mkdir -p bin/MAC
mkdir -p bin/WIN
GOOS=linux GOARCH=amd64 CGO_ENABLED=0 GO111MODULE=on go build -o bin/AMD64/edgex-cli-linux-amd64 -ldflags "-X github.com/edgexfoundry/edgex-cli/cmd/version.Version=0.0.0"; cd bin/AMD64; ln -s edgex-cli-linux-amd64  edgex-cli
ln: failed to create symbolic link 'edgex-cli': File exists
Makefile:34: recipe for target 'build-all' failed
make: *** [build-all] Error 1

authors: codecov-io difince lenny-intel mkbhanda

repo: edgexfoundry/edgex-cli


text:
busystate 0

hello, I got the following issue while running the --downgrade, And it's stuck on "Mounting filesystems".
device: iPhone SE iOS 12.2
000167.803994 wlan0.A[31] handleAdjustBusy@1551:AdjustBusy timeout in 120000 ms!

hello, I got the following issue while running the --downgrade, And it's stuck on "Mounting filesystems".
device: iPhone SE iOS 12.2
000167.803994 wlan0.A[31] handleAdjustBusy@1551:AdjustBusy timeout in 120000 ms!

12.2 ? this is only for 13.4 upper

xD...
so, i just want know there is anyway i can boot images lower than 13.4?

xD...
so, i just want know there is anyway i can boot images lower than 13.4?

as it needs to communicate with the sep when it is creating the data partition iirc, I guess you won't be able to go lower than 13.4  sadly

xD...
so, i just want know there is anyway i can boot images lower than 13.4?

as it needs to communicate with the sep when it is creating the data partition iirc, I guess you won't be able to go lower than 13.4 sadly

okay... thanks for the answer :D


text:
Audio Output Gets Cut Off at the End

Hello,
I’ve encountered an issue where the audio output seems to get cut off at the end of text sequences.
Instead of a smooth, natural conclusion to the generated audio, it feels like the audio either isn’t being fully generated or is getting truncated. This can make the outputs sound abrupt or incomplete, especially for longer/very short sequences or ones that would normally have a more gradual ending.
Steps to Reproduce:

Use OuteTTS to generate audio for a relatively long/small text sequence.
Observe the ending of the generated audio file.
Note that the last part of the audio feels cut off or truncated.
Input text used: uhm, who are you by the way?

See the output audio below
https://github.com/user-attachments/assets/b2c24d61-93c6-4273-ac9f-978b472e8f73
Notice that the last word way? is being cut off is this an expected behaviour or it wasn't planed?
Expected Behavior:
The generated audio should have a smooth and natural conclusion, matching the style and pace of the preceding content.
Environment Details:

Library version: v0.2.1
Python version: Python 3.11.4
OS: Windows 11
Model being used: OuteAI/OuteTTS-0.2-500M

Additional Notes:
If there’s any debug or additional logs you’d like me to provide, I’d be happy to help. Let me know if you need further details to investigate the issue.
Thank you for looking into this!

Are you using any speaker reference or not, and what backend are you using? This seems to work fine on my end. Could you share the code you're running?

Could try to increase the temperature a bit. Since the model was trained on only Latin characters, it doesn't have a clear understanding of punctuation, which might cause quick endings depending on the generation. This should improve in future versions as I'm planning to add support for special characters.

Here is my code snippet:
import outetts

# Configure the model
model_config = outetts.HFModelConfig_v1(
    model_path="OuteAI/OuteTTS-0.2-500M",
    language="en",  # Supported languages in v0.2: en, zh, ja, ko
)

# Initialize the interface
interface = outetts.InterfaceHF(model_version="0.2", cfg=model_config)

# Load speaker profile
speaker = interface.load_default_speaker(name="female_2")

while True:
    input_text = input("Enter Text: ")
    if input_text == "!exit":
        break
    output = interface.generate(
        text=input_text,
        temperature=0.6,
        repetition_penalty=1.1,
        max_length=4096,
        speaker=speaker,
    )

    output.save("output.wav")
    output.play()

Could try to increase the temperature a bit. Since the model was trained on only Latin characters, it doesn't have a clear understanding of punctuation, which might cause quick endings depending on the generation. This should improve in future versions as I'm planning to add support for special characters.

okay, i tried removing punctuations and still the model's output gets cut off at the end, the last second of the generated audio seems to be getting cut off

okay identified the problem. the play method is cutting the audio, i tried to play the saved audio and it played the full audio with the last 0.5 secs but the play method of output didn't.

okay, i tried removing punctuations

You don't need to remove punctuation yourself, the library handles text processing you can see the function here: process_text

okay identified the problem. the play method is cutting the audio, i tried to play the saved audio and it perfectly played the full audio with the last 0.5 secs but the play method of output didn't.

Great that you found the issue! It could be a compatibility problem between sounddevice and your hardware since that's the library used for audio playback. I should probably add other playback backends to the library.

Added Add support for multiple audio playback backends (sounddevice, pygame...) to the roadmap. Will have the ability to switch between playback libraries.

repo: edwko/OuteTTS


text:
Fixing bug related to Firebase event bundle value

Description
Fixing bug related to Firebase event bundle value. Firebase imposed no other restriction on values except string length of 100 chars; see.

Thanks for the pull request, @zahid-arbisoft! I've created OSPR-1992 to keep track of it in JIRA. JIRA is a place for product owners to prioritize feature reviews by the engineering development teams.
Feel free to add as much of the following information to the ticket:

supporting documentation
edx-code email threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will still be done via the GitHub pull request interface. As a reminder, our process documentation is here.
We can't start reviewing your pull request until you've submitted a     signed contributor agreement     or indicated your institutional affiliation.     If you like, you can add yourself to the AUTHORS      file for this repo, though that isn't required.     Please see the CONTRIBUTING     file for more information.

@miankhalid Can you confirm that @zahid-arbisoft is covered by the Arbisoft entity agreement?

I can confirm that he's an Arbisoft employee.
(Not sure about the Arbisoft entity agreement though or is that the same as
being an employee of the said company?)
On Nov 2, 2017 9:26 PM, "Ned Batchelder" notifications@github.com wrote:
@miankhalid https://github.com/miankhalid Can you confirm that
@zahid-arbisoft https://github.com/zahid-arbisoft is covered by the
Arbisoft entity agreement?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/edx/edx-app-android/pull/1021#issuecomment-341478292,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABoa1KKuthHieiqhwfHPJzIfvA1hphwJks5sye1IgaJpZM4QN_RE
.

@zahid-arbisoft for our records, what is your full name?

Sounds like this shouldn't have been considered an open-source pull request.  I'll clean up the JIRA ticket.

@nedbat I think there's a misunderstanding here, lemme explain. While @zahid-arbisoft is an Arbisoft employee, he isn't part of the edX Mobile team @ Arbisoft.
IMO this should still be considered an OSPR.

@nedbat My name is Syed Zahid. I am not part of edx team. I found this bug and thought I should create PR, that's all. :smile:

Not sure why Travis is stuck. Closing and opening again.

Closed in favor of https://github.com/edx/edx-app-android/pull/1076

Fixed https://github.com/edx/edx-app-android/pull/1021 so travis should be running tests now.

Apparently we want that PR setting off. Closing again and reopening the other PR.

Travis builds are working again for OSPRs, thanks to #1102.

authors: BenjiLee edx-webhook miankhalid nedbat zahid-arbisoft

repo: edx/edx-app-android


text:
Icon change for webOnly videos

Fixes: https://openedx.atlassian.net/browse/MA-1736
@1zaman @bguertin plz review

merge-able now @1zaman ?

merge-able now @1zaman ?

:+1:

:+1:


text:
feat: add five icons

Add icons ArrowForward ArrowBack Launch Settings and Program.

Coverage remained the same at 90.325% when pulling cce29dbef9b63960b79920a92d602ca778b2c43f on abutterworth/icons-addition into 570162cc181c4e9a56d7799c75674d1a331f8f24 on master.

Is that icon actually for 'launch' or 'opens in a new window'?

@wittjeff The name is Launch though likely used for the purpose you describe. We left the name unchanged from google material

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: abutterworth coveralls edx-semantic-release wittjeff

repo: edx/paragon


text:
rename LList.iso2 to LList.isoCurried

I got confused within only a few days of looking at the PR what iso2 was, so I am renaming it.

I don't think curried is the right word. From https://en.wikipedia.org/wiki/Currying:

currying is the technique of translating the evaluation of a function that takes multiple arguments (or a tuple of arguments) into evaluating a sequence of functions, each with a single argument.

We're just using a property (official or unofficial, I'm not sure) of Scala to use multiple parameter groups to resolve the type variables with the first function, so that we don't need to guide it with the second.
Given the purpose of the original method, namely deriving an LList representation of a type, I think the multiple parameter groups variant should always be used.
But I didn't want to break your API, and I can't overload because they erase to the same thing, so I just tacked on a "2".
Maybe we should deprecate the old method?

Technically speaking a function with multiple parameter groups might not the same as curried function A1 => A2 => R, but the distinction here I don't think is that important.
The idiomatic style of Scala function is to accept two parameters in one group unless it's meant to be an infix operator or while-replacement DSL. I am ok with breaking API for 0.8.0, but the thing that I am not comfortable with is leaning too much on type inference, which could widen etc unexpectedly.

the thing that I am not comfortable with is leaning too much on type inference, which could widen etc unexpectedly.

Without speaking about the design decision in general, but specifically to LList.iso, may I ask you to see if you can find any good examples where type inference of iso is preferable to iso?

Without speaking about the design decision in general..

I am not sure if I am violating this restriction, but I think it's best practice to ascribe types for implicit evidences. I think at some point Scala might introduce that as requirement. This is because capturing Some instead of Option could introduce subtle bugs.

Merging this so I can start the propagation of shaded JSON.

I am not sure if I am violating this restriction, but I think it's best practice to ascribe types for implicit evidences. I think at some point Scala might introduce that as requirement. This is because capturing Some instead of Option could introduce subtle bugs.

Yes, especially if you're using that type to drive other implicits (such as in or with shapeless). Btw, there's actually one exception though: values in methods; those don't need type annotations because they're evaluated sequentially only.


text:
Stack

add stack library

@AditMeh I have added some functions and updated the documentation. You can fetch the new commit and add anything else you want to add and request a pull, reopening this issue. Thank you again for contributing 😀