[BUG] org.opensearch.indices.replication.RemoteStoreReplicationSourceTests.testGetCheckpointMetadataEmpty is failing

Describe the bug
The org.opensearch.indices.replication.RemoteStoreReplicationSourceTests.testGetCheckpointMetadataEmpty is failing on main, apparently after https://github.com/opensearch-project/OpenSearch/pull/8433
com.carrotsearch.randomizedtesting.UncaughtExceptionError: Captured an uncaught exception in thread: Thread[id=100, name=opensearch[org.opensearch.indices.replication.RemoteStoreReplicationSourceTests][remote_refresh][T#1], state=RUNNABLE, group=TGRP-RemoteStoreReplicationSourceTests]
Caused by: java.lang.AssertionError
	at __randomizedtesting.SeedInfo.seed([92C4ACD8A776127B]:0)
	at org.opensearch.index.seqno.ReplicationTracker.setLatestReplicationCheckpoint(ReplicationTracker.java:1216)
	at org.opensearch.index.shard.IndexShard.onCheckpointPublished(IndexShard.java:1857)
	at org.opensearch.index.shard.RemoteStoreRefreshListener.syncSegments(RemoteStoreRefreshListener.java:195)
	at org.opensearch.index.shard.RemoteStoreRefreshListener.lambda$afterRefresh$0(RemoteStoreRefreshListener.java:183)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:577)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
	at org.opensearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:849)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
	at java.base/java.lang.Thread.run(Thread.java:1623)

To Reproduce
./gradlew ':server:test' --tests "org.opensearch.indices.replication.RemoteStoreReplicationSourceTests.testGetCheckpointMetadataEmpty" -Dtests.seed=92C4ACD8A776127B -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=sk-SK -Dtests.timezone=Canada/Yukon -Druntime.java=20

Expected behavior
The test should always pass
Plugins
Standard
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):

CI

Additional context
https://build.ci.opensearch.org/job/gradle-check/20172/
https://build.ci.opensearch.org/job/gradle-check/20196/

@ankitkala it seems like it is caused by https://github.com/opensearch-project/OpenSearch/pull/8433, cloud you please take a look?


Remove the auto_now and keep the auto_now_add per the documentation. …

…As the ticket should not be updated after creation, we only need to create the timestamp on creation.
Credit: Brandon Grant

Thank you!


Create an SAP Fiori App Using SAP Business Application Studio

Tutorial URL: https://developers.sap.com/tutorials/appstudio-fioriapps-create.html
Step 8, even though I have connectivity to the SAP system, there is no data available in the dropdown, and I am now stuck

Hi @CatherineofNorway ,
Can you share a screenshot of where you're stuck?
Regards - Raz

Hi Raz,
Thanks for getting back to me. I see now it was step 1, point 8. Every time
I tried to set up a consumer pointed to the SAP system ES5 there were no
destinations (My SAP Systems). It turns out that I needed to log into the
CF and set an organisation and dev space and all was well.
The tutorial explains quite a lot further down that we have to log in;
perhaps bring this into step 1?
On Thu, 20 Aug 2020 at 17:06, Raz Korn<EMAIL_ADDRESS>wrote:

Hi @CatherineofNorway https://github.com/CatherineofNorway ,
Can you share a screenshot of where you're stuck?
Regards - Raz
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SAPDocuments/Tutorials/issues/5718#issuecomment-677722456,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGFMLWKUETQFHDUOBXZYAQTSBU3YZANCNFSM4QE2SSBA
.

--
Regards,
Catherine Adams
+27 789659675 / +47 406 33 980

Hi yes, I was exactly following these tutorials, in this order. I did have
to stop in between and start the next day though, which is probably why I
was logged out.
On Sun, 23 Aug 2020 at 09:44, Raz Korn<EMAIL_ADDRESS>wrote:

Hi @CatherineofNorway https://github.com/CatherineofNorway ,
Thanks for sharing your feedback with me.
My 2c:

I assume that you use BAS on trial. In order to access BAS, you should
have created a trial account, which by default creates the default
subaccount and space.
The tutorial is part of a tutorials group. In the first tutorial
https://developers.sap.com/tutorials/appstudio-onboarding.html the
pre-req is to have a trial account. The second tutorial
https://developers.sap.com/tutorials/cp-portal-cloud-foundry-gateway-connection.html
guides through the creation of the ES5 destination.
Regards - Raz
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SAPDocuments/Tutorials/issues/5718#issuecomment-678741587,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGFMLWOT7RUC67MT7KHDH7DSCDCFRANCNFSM4QE2SSBA
.

--
Regards,
Catherine Adams
+27 789659675 / +47 406 33 980

Hi @CatherineofNorway ,
BAS stops dev spaces after an idle time. That's probably what you experienced.
In the next tutorials update, I'll add a comment on this.
Regards - Raz

Thank you for your feedback. The issue seems to be resolved, so I am closing the issue.
If you still have questions, feel free to reopen the issue.


Add MoveNet

Main tasks

[ ] Move dependencies into /docs/.vuepress/public/handsfreejs
[ ] Make sure dependencies transfer when building
[ ] Extend the class from BaseModel

Other tasks

Moved into #150


Arguments with default values are nullable in resolvers

When assigning a default value to a field's arg, I would expect the arg in the resolver to have a Typescript type that doesn't include null and undefined.
However, the opposite was the case. The value was nullable even though with the default value that should not happen.
See the following code sample:
builder.objectRef<ProfilePhoto>('ProfilePhoto').implement({
  fields: t => ({
    url: t.field({
      type: 'String',
      args: {
        width: t.arg({ type: 'Int', defaultValue: 60 }),
      },
      resolve: ({ key }, { width }) => {
        // The type of `width` is `string | null | undefined`. I expected it to be just `string`
       // ...
      },
    }),
  }),
})

Of course, I can make the argument required and only then is the TS type correct. (GraphQL allows for required args with default values, but I think this should work without having to resort to that.)
Please let me know if I'm missing something and this is expected behaviour. If this is indeed a bug and you don't expect the fix to be too complex, I can look into submitting a PR.

default arguments in GraphQL are a little un-intuitive in how they work:
When you provide a default value for an argument, that value will be used when no value is explicitly provided.  If you have a nullable argument with a default value, you can still explicitly provide null as a value in the query, which will not be overwritten by the default value.
Making an argument non-nullable (required in pothos), specifying a default value means that you will not need to provide that value as part of the query.
So if your goal is to have an argument with a default value, that doesn't need to be provided in a query, but always has a value in the resolver, the correct way to do this is to make it non-null with a default.
Hope that helps, let me know if you have any other questions!

Got it, thanks for the clarification!


add option to add files in container

Hi,
I've added the possibility to add files that will be mounted into the scala-steward container. I needed this for two things:

for use with the --repo-config option which requires a file. I could of course put this into each individual repo, but I want to be able to configure it the same way across repos
for the /root/.sbt/1.0/credentials.sbt file where I read the Nexus credentials from the env variables. again, I don't want to modify lots of different repos to do this.

Let me know what you think.

Thanks for the review, I've rebased the changes.

I've also adjusted version and appVersion in Chart.yaml

Thanks! The changes look right. I want to test this a bit before I merge. I'm busy today and am hoping to get a coworker to look soon (maybe tomorrow if I'm lucky). If I don't respond by Monday, please tag me on Tuesday.

OK cool

Ping @jsoref!
I've pushed another change to correctly handle the case where additionalFiles is empty.

Fwiw, I've asked someone to run a test of this, so hopefully they'll check tomorrow and have feedback for me by Monday.

I'm running this right now and it's working fine for me (I've added a credentials configuration for sbt and a repo configuration for scala-steward), so I'm not sure what more testing it is you need to do. But go ahead, do your thing.

Sorry... sometimes I'm overly cautious. I'm used to things going wrong. Many things I've tried this week have gone wrong.
What I can say is that we tested the basic chart from this PR and it worked. We haven't had time to test the volume mounts although I absolutely expect them to work.
I'm going to check with a coworker and I think I'll merge by Monday.

Thanks @jsoref

Thanks for contributing and sorry about the long time to merge.


Expose ImageChrome option in SpectrogramFalseColourConfig

Is your feature request related to a problem? Please describe.
Sometimes I'd like to produce a FCS without any of the axes, legends, or gridlines.
Describe the solution you'd like
Expose the internal ImageChrome option of the FCS rendering methods by adding a config file property in SpectrogramFalseColourConfig.
Describe alternatives you've considered
N/A
Additional context
This issue was filed on behalf of an external collaborator.

Hey I would really like this functionality too. I'm hoping to include some FCS in a web application so plain images would be ideal


Consistency of enumerations and css properties

Consider ImageFit:

class ImageFit(Enum):
    NONE = "none"
    CONTAIN = "contain"
    COVER = "cover"
    FILL = "fill"
    FIT_HEIGHT = "fitHeight"
    FIT_WIDTH = "fitWidth"
    SCALE_DOWN = "scaleDown"

The documentation says that the default value is .NONE, which is equal to "none"
But in the code, the default value is None, which I run as .CONTAIN
Is this a documentation error or does it work differently for me?

Consider MainAxisAlignment:

class MainAxisAlignment(Enum):
    NONE = None
    START = "start"
    END = "end"
    CENTER = "center"
    SPACE_BETWEEN = "spaceBetween"
    SPACE_AROUND = "spaceAround"
    SPACE_EVENLY = "spaceEvenly"

The documentation says that the default value is .START, and it is.
But in the code, the default value is not .START, but .NONE
Frankly, it's very confusing. I need to understand what approach you see as the right one in this situation? Why would you put None in a separate field and why would you choose a name that matches an existing CSS property? And why are the default properties somehow different from the ones declared in the documentation, either by name or by value?

Having None in some enumerations is just a way to have a typing without Optional.
So, instead of:
actions_alignment: Optional[MainAxisAlignment] = None

we have:
actions_alignment: MainAxisAlignment = MainAxisAlignment.NONE

Semantically, setting prop value to None means "default to whatever value is default on Flutter side, like .STARTforMainAxisAlignment`.
I think we should get rid of None in all enums and use Optional instead.
Does it make sense?

Makes sense to me.
Can PR that, if needed.

@ndonkoHenri sure, PR would be great, thank you!

@ndonkoHenri @FeodorFitsner
I would suggest using
MainAxisAlignmentDefault = MainAxisAlignment.START
ImageFitDefault = ImageFit.CONTAIN
# and so on

That way we could get rid of None and .NONE is None on the api side with the user, and return default values in case of unusual data.
It's not clear yet what value to return correctly by default, I can't close the previous question correctly.
If you are satisfied with this, I will also make a PR, and you decide for yourself what suits you best

@FeodorFitsner I think @Vlod-github is somehow right.
Setting the right defaults will make it possible for users extract the correct values.
So, if someone creates a x=Row() and below it calls x.alignment, he should get "start" and not None.

The PR has been created. You can read the changes here. Worth looking at utils.py, types.py, and others. Adding default values changed the internal contents of empty objects, which affected the tests. As well as the absence of None.


minceraft

it may or may not be based on a popular game, w to jump, s/d to move side to side, your object is to collect all the emeralds to open the nether portal, and the lava kills you
loosely based on a similar game i made for my CS class
I feel like I should add more to the game, but I'm not really sure what to add

Thanks for PR!

Was your objective for the spriteto float?

I think you could change the main sprite, be creative :)

Could you add your references in the code header?

If you use setBackground, you can get rid of the blank white spaces in your map :) Check the docs for details!
I couldn't figure out the second level -- the emeralds didn't seem to work?
Could you make the gravity more ... gravity-y? Might be worth looking at this game, I think it had really great gravity!

I feel like I should add more to the game, but I'm not really sure what to add
ooh, what if you took a note from falling block and added things to dodge on some of the levels? :eyes:

So far, great work, can't wait to see what you come up with :)

thank you guys so much for the suggestions, im working on implementing them rn, but i do have some questions

I couldn't figure out the second level -- the emeralds didn't seem to work?

the emeralds are kind of weird because i have them in afterInput, so i think you have to actually move onto one instead of fall to get it (and also it was deleting the first instance instead of the one you were on until now)

If you use setBackground, you can get rid of the blank white spaces in your map :) Check the docs for details!

I tried to do this, but it sets the background for all maps, is there a way to not do that?

ooh, what if you took a page from falling block and added things to dodge on some of the levels? 👀

i actually had blazes that moved in the old game, but i havent implemented them yet

@tildezero How's the game going?

the emeralds are kind of weird because i have them in afterInput, so i think you have to actually move onto one instead of fall to get it (and also it was deleting the first instance instead of the one you were on until now)

Try putting all the emerald stuff in a function and calling that in the gravity, it might work.

I tried to do this, but it sets the background for all maps, is there a way to not do that?

You can change the background with setBackground(spriteKey). You can use if statements to detect which level it is to change the background.
Let us know if you need anything!

It seems you need to make more changes before you're ready to get your Sprig. I'm going to close this PR for now. Feel free to reopen if you want to continue working on your game.


Add -std=c99 to CFLAGS

I needed to add -std=c99 to CFLAGS to get this to compile (gcc relatively recent version). I'm pretty sure this flag should be safe on LLVM as well, so maybe it could be added to config.mk? I'm happy to create the commit and pull request if agreed.

I can't reproduce this (gcc version 11.3.0)


De-duplicate Package.onUse to fix issue with Meteor <IP_ADDRESS>

Fixes #20.

Thanks for doing this!
Since this is only a problem with 1.7, maybe we should add<EMAIL_ADDRESS>just in case removing those files introduces a backwards compatibility problem.

Released as 3.0.4, thanks @banjerluke and @moberegger
I wasn't sure about the difference between mainModule and addFiles when I upgraded this repo. I assumed mainModule would only work for people using modules, can anyone clarify?

I'm no expert on modules, but api.mainModule has been around since Meteor 1.3 and there's nothing in the changelog to suggest its behavior has changed. Basically, mainModule implies adding the file to the bundle. It does more, of course, and some refactoring might be in order eventually (not doing an api.addFiles on files that are being imported through api.mainModule, maybe), but this should work with no issues in the meantime.


[Bug] Incorrect Ratelimit implementation

The current rate limit implementation assumes that X-RateLimit-Bucket header is sent per route + params tracks buckets in relation to endpoints, which is wasteful of resources. Also global rate limit is bugged due to a typo and rate limit does not avoid 429.
This is inconsistent with what the docs say

fixed in commit 7f3665fc6f1ca62a619a84dbef20e02cd2b0070f


Fix r-universe badge

Upstream issue. https://github.com/etiennebacher/altdoc/issues/178

Fixed upstream.


Crash when both Show Me Your Skin! and Blue Skies are installed

Mod Name
Show Me Your Skin!
Mod Homepage
https://modrinth.com/mod/show-me-your-skin
Minecraft version
1.20.1
Describe the bug
Crash when Show Me Your Skin! and Blue Skies are installed
Steps to reproduce
Install Blue Skies (A forge only mod) and Show Me Your Skin!
Try to launch Minecraft
Game crashes
Logs
https://mclo.gs/1xGzGUg
Additional context
Connector is currently the only way I'm aware of to have both mods running together, so it's not possible for me to easily determine whether Connector is causing the issue, or if this is just an incompatibility between the two mods.

I have both mods installed in my modpack having the same issue did you find a solution?

It was fixed beta 38 iirc
It's been a while since I've used those mods (or played mc actually)
Has it regressed? if so you may need to open a new issue


Fix typo in docs "Migrate to JUnit 5 from JUnit 4"

What's changed?
Fixes a typo in the docs that caused the error:
Execution failed for task ':rewriteResolveDependencies'.
> Could not resolve all files for configuration ':detachedConfiguration1'.
   > Could not find org.openrewrite.recipe:rewrite-testing-frameworks:.
     Required by:
         project :

What's your motivation?
Prevent people from suffering the same error.
Checklist

[ ] I've added unit tests to cover both positive and negative cases
[ ] I've read and applied the recipe conventions and best practices
[ ] I've used the IntelliJ IDEA auto-formatter on affected files

Thanks a lot for the fix @seraco ; I imagine this might affect a few of our other guides as well; would you mind double checking @mike-solomon ? Since you're about to change the version numbers here too

I'll merge this in and take a look over the other docs and see. Thanks!


Fix hyperlink

The existing link to ScopeOwner at the bottom of the page throws a 404. It may be replaced with https://docs.microsoft.com/en-us/uwp/api/windows.ui.xaml.input.keyboardaccelerator.scopeowner?view=winrt-18362 (if that was the intended target)

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

ID: 5276572e-ea22-46ff-62a9-72833f552805
Version Independent ID: d457bacd-7d32-fcee-ff17-d14271df40cf
Content: UIElement.KeyboardAccelerators Property (Windows.UI.Xaml) - Windows UWP applications
Content Source: winrt-api-build/xml/Windows.UI.Xaml/UIElement.xml
Product: uwp
Technology: winui
GitHub Login: @jwmsft
Microsoft Alias: jimwalk

Topic has been revised. Thanks!

Is it? Still seeing the same link and the same 404


{emqx_auth_http,{different_server,{emqx_auth_http_app,start,[normal,[]]}}}  why?

Hi @condingyz In the 4.2.5, the auth_req, super_req, acl_req option should have the same host and port in it's URL

Hi @condingyz In the 4.2.5, the auth_req, super_req, acl_req option should have the same host and port in it's URL


Replace click on tags with actual edit buttons

@peduarte would you mind testing this for me and tell me if you think it's better? Cheers!!!

Ok...

Yeah, it's nicer and more consistent with the GH interface

:+1:


Checkpoint 2 Review

Changes Unknown when pulling 98f70ea40dc7e2740ba76ab288f78b4af1ace57b on develop into ** on master**.

Changes Unknown when pulling b3d51e72b490e73bcda7b14062a351d3c8b71a71 on develop into ** on master**.

Changes Unknown when pulling 3b72d429f6a78ea43f7ab2263f6bcad6dd3c9c5a on develop into ** on master**.

Changes Unknown when pulling a711bd612b32f2ead9637194dc27def3c736405c on develop into ** on master**.

Changes Unknown when pulling 33d144450e99ff26e0c4cca9d46884d139451d9c on develop into ** on master**.

Changes Unknown when pulling 33d144450e99ff26e0c4cca9d46884d139451d9c on develop into ** on master**.

Changes Unknown when pulling bc2266e7bb3d501bd10b9d030cb873d6afdf9424 on develop into ** on master**.

Changes Unknown when pulling<PHONE_NUMBER>aa8d4b68c0e2999fb67a6518626d9c on develop into ** on master**.

Changes Unknown when pulling c7f9d3e0de23b6287bc2eeba5b7693dad37d934e on develop into ** on master**.

Changes Unknown when pulling 4ec10257e5a18e253e2e5ddfa8d4038a3250136f on develop into ** on master**.

Changes Unknown when pulling 8ecf8c53916856458e28155e7b794954108145ed on develop into ** on master**.


numbered lists do not increment

1. blah 1
2. blah 2
3. blah 3

gets converted to:
1. blah 1
1. blah 2
1. blah 3

The latest version (published today) increments ordered list item numbers properly. Please reopen this bug (or open another) if you see any issues related to this change.


[QUESTION]: Steps to upgrade app

With the latest version released, how does one go about upgrading to this version properly without losing everything?

Hi @GradyD ,
I can update the readme later with steps.
So that you're unblocked, here's some steps:
https://github.com/MicrosoftDocs/powerapps-docs/issues/1148#issuecomment-600213848

Readme.md has been updated with instructions for importing an updated app or flow 👍
aka.ms/CrisisCommunicationSolution


Update https://registry.npm.taobao.org to https://registry.npmmirror.com

Update https://registry.npm.taobao.org to https://registry.npmmirror.com, For more info please refer to https://zhuanlan.zhihu.com/p/430580607.
This is an automated PR by @npmmirror (Which is a bot maintained by 8d6e8cefe5a7e3202364ec2c48db03fcc544218cf70100bf65d2ed2df5cc83da).

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.NPM Mirror Bot seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


support repair attempts in Maven directly

Problem statement: today, using repairnator requires to have an external server (either Jenkins, self-hosted scanner, etc).
Solution: using Repairnator by simply adding maven-repair to the pom.xml of projects. Then, it will be easy to put repairnator in our own repositories, and to propose it for friend repositories.
Related work: "Automatically repairing dependency-related build breakage"

simply adding maven-repair in the pom would trigger repair attempts when a test case fails.
(maven-repair would register to the surefire events)

Link https://github.com/eclipse/repairnator/tree/master/src/maven-repair

I'm working on it. FH

@cokefh what's the progress here?

There are two files to modify for doing this for NPEFix

https://github.com/eclipse/repairnator/blob/master/src/maven-repair/src/main/java/com/github/tdurieux/repair/maven/plugin/AbstractRepairMojo.java
https://github.com/eclipse/repairnator/blob/master/src/maven-repair/src/main/java/com/github/tdurieux/repair/maven/plugin/NPEFixMojo.java

Today we must run the tests first and the run the repair attempt:
mvn test -DtrimStackTrace=false
mvn fr.inria.gforge.spirals:repair-maven-plugin:npefix

With the change, when the maven plugin is setup in pom.xml, only mvn test would be necessary, upon failures, the repair attempt would be started automatically.
mvn test

If a patch exists, it would be outputted on the console.

Reference documentation: https://maven.apache.org/guides/mini/guide-configuring-plugins.html#Using_the_executions_Tag

FYI: deflaker does something similar: https://github.com/gmu-swe/deflaker

See https://github.com/gmu-swe/deflaker/blob/master/maven-extension/src/main/java/org/deflaker/maven/DeflakerLifecycleParticipant.java

Two kinds of extensions:

Maven lifecycle extensions, see https://maven.apache.org/examples/maven-3-lifecycle-extensions.html (we would like to extend the phase test)
Surefire extensions (see below)

Maven lifecycle extensions

Example of configuration: See bottom of https://maven.apache.org/examples/maven-3-lifecycle-extensions.html and deflaker readme
Example of code: https://github.com/gmu-swe/deflaker/blob/master/maven-extension/src/main/java/org/deflaker/maven/DeflakerLifecycleParticipant.java

Surefire extensions
Potential extension points of surefire:
startupReportConfiguration; consoleLogger; statelessTestsetReporter; consoleOutputReporter; statelessTestsetInfoReporter; surefireClassLoader
(not documented in code)
(not documented in https://maven.apache.org/surefire/surefire-extensions-api/)
Example of surefire extension configuration:
https://github.com/fabriciorby/maven-surefire-junit5-tree-reporter/blob/master/pom.xml#L92
Example of class extending JUnit5StatelessTestsetInfoReporter
https://github.com/fabriciorby/maven-surefire-junit5-tree-reporter/blob/bed1975a6b1a4cff3ae87df5d9a6c727f2396bce/src/main/java/org/apache/maven/plugin/surefire/extensions/junit5/JUnit5StatelessTestsetInfoTreeReporter.java

To get the current live documentation of the plugin:
mvn help:describe -DgroupId=fr.inria.gforge.spirals -DartifactId=repair-maven-plugin -Ddetail=true

It clearly shows that the repair goals are already bound to phase test
repair:npefix
  Description: (no description available)
  Implementation: com.github.tdurieux.repair.maven.plugin.NPEFixMojo
  Language: java
  Bound to phase: test

  Available parameters:

    javaVersion (Default: -1)
      User property: java.version
      (no description available)

    localRepository (Default: ${localRepository})
      (no description available)

    nbIteration (Default: 100)
      Required: true
      User property: laps
      (no description available)

    oldSource (Default: -1)
      User property: maven.compile.source
      (no description available)

    outputDirectory (Default: ${project.build.directory}/npefix)
      Required: true
      User property: outputDir
      Location of the file.

    repairStrategy (Default: default)
      Required: true
      User property: strategy
      (no description available)

    resultDirectory (Default: ${project.build.directory}/npefix)
      Required: true
      User property: resultDir
      (no description available)

    scope (Default: class)
      Required: true
      User property: scope
      (no description available)

    selector (Default: exploration)
      Required: true
      User property: selector
      (no description available)

    source (Default: -1)
      User property: maven.compiler.source
      (no description available)

Who calls NPEFixMojo.execute?
	at com.github.tdurieux.repair.maven.plugin.NPEFixMojo.execute(NPEFixMojo.java:86)
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
	at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)
	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:192)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

The solution is probably to configure either or both the pom.xml of maven-repair or the pom.xml of the program under repair.

Here I think we may need to modify both the maven-repair pom.xml file and the project pom.xml file, for the sake of tidyness of project pom.xml.

To check that a plugin is well bound:
mvn fr.jcgay.maven.plugins:buildplan-maven-plugin:list

-----------------------------------------------------------------------------------------
PLUGIN                 | PHASE                  | ID                      | GOAL
-----------------------------------------------------------------------------------------
maven-resources-plugin | process-resources      | default-resources       | resources
maven-compiler-plugin  | compile                | default-compile         | compile
maven-resources-plugin | process-test-resources | default-testResources   | testResources
maven-compiler-plugin  | test-compile           | default-testCompile     | testCompile
maven-surefire-plugin  | test                   | default-test            | test
repair-maven-plugin    | test                   | execution2sfsdfsdfgsdfg | npefix
maven-jar-plugin       | package                | default-jar             | jar
maven-install-plugin   | install                | default-install         | install
maven-deploy-plugin    | deploy                 | default-deploy          | deploy

repair-maven-plugin is there!

Yet, repair-maven-plugin is skipped if the previous goal (maven-surefire-plugin:default-test) fails.
This contradicts what we want to do!

Next steps:
With -Dmaven.test.failure.ignore=true the build does not fail if there is a test failure, which is the opposite of what the users want. Solutions:
First, we never want to fail the build if there is an error during the repair process, so we'll add a try-catch block around the repair code
try {
  .... repair
} catch (Exception e) {
  Log.info();
}

We have do this for all repair goals but we'll do it for npefix first.
Second, we have to fail the build if there one one test failure:
// at the end of execute

if (thereWasAtLeastOneTestFailure()) {
  throw new RuntimeException("there was one test failure"); // may be one specific MojoException or SurefireException
} else {
  // do nothing
}

FTR, #1106 does this for NpeFix

For supporting this feature in the other repair tools, we need to do a refactoring.
AbstractRepairMojo.java would be the only class to override execute from the Maven framework, in order to do the test checks / try-catch / rethrow failures. It would also declare an absract method executeRepair.
Each Mojo would implement executeRepair.


feat: [WIP] Support Document Index as a layout class

Issue resolved by this Pull Request:
Resolves #126
Checklist:

[ ] Commit Message Formatting: Commit titles and messages follow guidelines in the
conventional commits.
[ ] Documentation has been updated, if necessary.
[ ] Examples have been added, if necessary.
[ ] Tests have been added, if necessary.

Superseded by https://github.com/DS4SD/docling/pull/530


Size of slices exceeds correct value by 8 Bytes

While we managed to fix the early &mut T bug, it wasn't the one I encountered in the other crates. This pull request adds a test with the case encountered in the other crate, which is currently failing. @vigna when you have time, please do check whether my expected deep size of the CustomArray is correct.

Mmmhhhh... this seems more like of a problem of the ballet with adding and subtracting size_of's.

Well, apparently size_of a slice includes a usize. In the example,
[mem_dbg/src/impl_mem_size.rs:116:13] core::mem::size_of::<Self>() = 16
[mem_dbg/src/impl_mem_size.rs:116:13] <T as MemSize>::mem_size(*self, flags) = 28

That seems a legit fuckup from my part in the original implementation.

The actual problem is coverage. No tests for [T] were ever written. As soon as you do, you need five lines:
#[test]
fn test_slice_u8() {
    let data = [0_u8; 10].as_slice();
    assert_eq!(
        (*data).mem_size(SizeFlags::default()),
        std::mem::size_of::<usize>() * 2 + 10
    );
}

Would you like for me to replace the current tests with the simpler one you provided?

I already added it, I'll remove yours after the merge.


server: clean up sandbox network when running the sandbox fails

Runtimes need to clean up anything that needs it if RunPodSandbox() fails.  Like the network.
@rajatchopra @mrunalp

Looks good!

:+1: waiting for tests

[retest]

LGTM


Error message with period='max'

When running :
data = yf.download('ABTC-USD.SW', period='max', interval='1d', auto_adjust=True)
I am getting the following error :
1 Failed download:

ABTC-USD.SW: 1d data not available for startTime=-2208988800 and endTime=1611763275. Only 100 years worth of day granularity data are allowed to be fetched per request.

The line of code does work with ticker 'ABTC.SW' though.

This may be linked to issue #545

This may be linked to issue #545

until it's fixed you can just use period='99y' instead period='max'

Hi, issue is that start parameter is set to 1.1.1900 and yahoo finance forbids data requests over a time period longer than 100 years. I suggest to set start parameter to 1.1.1950 (other earlier dates would also work, but does yahoo finance provide data before 1950?):
I  created a pull request: https://github.com/ranaroussi/yfinance/pull/648 to fix this issue

Solved by #648


Slas helper missing register helper

There is no helper for registering a user.

Hi @kevinxh, is the ask only to provide a wrapper around the API? Or would this helper be accomplishing other things?


Add build of native binaries for Linux, Mac, and Windows to remove node requirement for clients

I was looking at the awesome Spectral JSON validator project https://github.com/stoplightio/spectral, and noticed that their build creates native binaries for Linux, Mac, and Windows.  These native binaries can then be used for validation on the respective client machines without requiring users to install node.js.  This seems like it could enable more widespread usability of lint-openapi.
It appears that they use yarn to do their building and that there is a simple npm script that creates these binaries. (pasted below)  Seems like adding this would not be difficult...
"scripts": {
...
"build.binary": "yarn build && yarn build.manifest && cp yarn.lock dist && cd dist && yarn && pkg . --out-path ./bin",

The comment I put in before about yarn is incorrect.  I didn't understand that actually the tool that was doing the work of packaging was in fact "pkg" ,. https://github.com/zeit/pkg.

:tada: This issue has been resolved in version 0.10.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


android.os.FileUriExposedException  filepath.jpg exposed beyond app on android Nouget

I am getting above exception in android Nougat while taking a picture.Earlier versions it is working properly.
https://developer.android.com/training/camera/photobasics.html
As per this url it seems that it has to be handled in a  different way from android 7.0 onwards

@bensmiley @kykrueger  @simonsmiley64 Is this issue resolved?

@bensmiley @simonsmiley64 @kykrueger  Is this issue resolved?I am eagerly waiting for the major update(It was supposed to release in the first week of Sept).When it will be released?
Waiting for your Reply.

Anyone Please Help me regarding this issue?


Access for peer credentials from initial DTLS connection to later phases

In order to support deployments with automated device registration during device bootstrapping one needs to have access to TLS Client Certificate detail in order to approve auto registration.
Due to nature of bootstrapping process with the need to support different kind of authentication methods this decision cannot be made at time when DTLS is first validated but needs to be carried later so that rule based analysis can be performed by bootstrap service.
This is also required in for the EST support: https://github.com/eclipse/leshan/issues/859

This seems to be most challening problem to solve as it touched quite a many places. An advice is asked where to store this properly.
To get forward I have added it to Identity class but that kind feels incorrect but then again feels only place it could be placed:
As:
    /**
     * Note: peerCertificate is only needed during runtime (transient) and does not need to be serialized.
     */
    private final transient X509Certificate peerCertificate;
    /**
     * Note: peerCertPath is only needed during runtime (transient) and does not need to be serialized.
     */
    private final transient CertPath peerCertPath;

I'm not sure to get the point. Could you explain this a bit more maybe with an exemple or point me some code where this is used ?

I am currently having a workout with test suite after some changes so not everything is nice and tidy yet... but just pushed by local version here:
https://github.com/dachaac/leshan/commits/est-support
Perhaps most related points are:
Those declarations are in here:
https://github.com/dachaac/leshan/commit/d11067a3c2b29d230d5ab25ca8c6a8ab2da99a23#diff-8040b506e90c042422eaf1be4805f9e2R39
Capturing of the peer credentials:
https://github.com/dachaac/leshan/commit/d11067a3c2b29d230d5ab25ca8c6a8ab2da99a23#diff-286c42661669116cbe1fdeec53ea4080R72
Then in here I think the actual checking if device is allowed in or not (still needs work):
https://github.com/dachaac/leshan/commit/d11067a3c2b29d230d5ab25ca8c6a8ab2da99a23#diff-e6d76e95d80a1d82c3aed465e374e89fR47
More or less the changes all around are somehow related to this :|
One part of the changes is related to getting trust store a bit more configurable so that this information can be used later.
Code flow kinda happens something like this:

Client connects to server
Server gets new DTLS connection but cannot do PKIX validation in normal point as there is a need to support other authentication types AND we need Endpoint client name also in the play and that we receive in LWM2M protocol level later on.
If x509 client certificate is provided by the client it and its chain is recorded in Identity class
Then code goes forward where it we start to actually check that is client allowed in or not
In future in this point there would be analysis on certificate chain and some rules to in example allow auto-registration of client.

Then in here I think the actual checking if device is allowed in or not (still needs work):
dachaac@d11067a#diff-e6d76e95d80a1d82c3aed465e374e89fR47

The API will depends a lot of what we want to do here. (This is the part which is not clear to me)
My vision is that DTLS layer ensure authentication. It ensure that the device is really who it pretends to be, then at LWM2M layer we only have the DTLS Identity.
Adding the whole certificate + certificates chain in Identity could be OK to me. (This maybe brings more flexibility)
But If we need less we can maybe find a better abstraction. E.G. maybe we don't need the whole certificate but just the whole Subject DN ?
I don't know if you aware about this class  CertificateVerifier  but this could also be a good place for PKIX validation. (We need to define which part of PKIX validation must be done in CertificateVerifier and which part should be done in SecurityChecker)

Then in here I think the actual checking if device is allowed in or not (still needs work):
dachaac/leshan@d11067a#diff-e6d76e95d80a1d82c3aed465e374e89fR47

The API will depends a lot of what we want to do here. (This is the part which is not clear to me)
My vision is that DTLS layer ensure authentication. It ensure that the device is really who it pretends to be, then at LWM2M layer we only have the DTLS Identity.
Adding the whole certificate + certificates chain in Identity could be OK to me. (This maybe brings more flexibility)
But If we need less we can maybe find a better abstraction. E.G. maybe we don't need the whole certificate but just the whole Subject DN ?

For normal TLS Server Certificates where there is server location in Subject DN's CN field or in Subject Alternative Name then just having a list of trusted Root CA's is enough. There is set of rules that just need to be matched and we are fine.
But the TLS Client Certificate is rather problematic in sense of validating when certificate can be considered valid. It does not have source location (as that varies). When there is only one Root CA and one knows how that is managed then you could just trust in Certrificate Serial Number, or in additional OID in extended key usage, or Subject DN., and/or some other certificate details. How to build identity from here is a rather good question. In theory it is the whole certificate (and its chain).
As an example I have seen machine certificates where subject DN was empty and then in Subject Alternative Name had information. So this is completely up to PKI admin of particular Root CA to decide how things are done there. While this gives flexibility for systems operations it gives headache for anyone using the system. Some standard (or at least limited number of differences) would be really nice for this.
Now if we have multiple root CA's in picture this gets a bit messy. All those different Root CA's might behave differently.
So far the best idea I have had is that once we know the Root CA for the connecting client we can assign a policy for that Root CA. Policy might be rule set how to interpret the TLS Client Certificate and Endpoint Client Name.
If we consider bootstrapping service that can have multiple Manufacturer Root CA's registered and then force client to transition to TLS Client Certificate that is service managed (issued under Service Specific Root CA) then we kinda have complexity only in bootstrapping phase and rest of the services could just trust in Subject DN field (or so). This forced transition works for both Certificate mode and EST mode.
Now this leads us back to question to what information do we need in what phase.
I believe that in DTLS phase we have list of Root CA's so that we can verify that when client does TLS Client Certificate Authentication then it must be issued by one of those Root CA's. BUT we need to carry out this Root CA issuer information (or policy information) forward somehow so that we can then look in LWM2M protocol level whether the client is actually allowed in or not.
LWM2M Specification states following about Endpoint Client Name:

This specification recommends, but does not mandate, transmission of the endpoint client name in the BootstrapRequest and in the Register message. Since the endpoint client name is not authenticated at the application layer the
LwM2M Server MUST compare the received endpoint client name identifier with the identifier used at the TLS/DTLS
handshake. This comparison may either be an equality match or may involve a dedicated lookup table to ensure that
LwM2M Clients cannot intentionally or due to misconfiguration impersonate other LwM2M Clients. The LwM2M Server
MUST respond with a "4.00 Bad Request" to the LwM2M Client if these fields do not match.

Most important part here I believe is This comparison may either be an equality match or may involve a dedicated lookup table to ensure that LwM2M Clients cannot intentionally or due to misconfiguration impersonate other LwM2M Clients.. Meaning that if the Endpoint Client Name is somehow trusted in LWM2M service it must be verified. What I have seen so far is that Endpoint Client Name's value is used as identifier in services -- so I suppose the goal should be that the Endpoint Client Name is unique in the service.
Now in context of Leshan as it is a library for making a LWM2M software it is a bit more complex as there might be different needs in different implementors. For this reason I was thinking that if we pass whole certificate chain forward it allows one to do system of their liking.
Now for the wish of having a standard way for TLS Client Certificate there seems to be several references in RFC's (like CoAP-EST) for IEEE Std 802.1AR-2018: Secure Device Identity standard. It also seems that IEEE Secure Device Identity just got a bit bigger as it seems to be now ISO/IEC/IEEE 8802-1AR:2020 (under paywall so I have not checked it out yet) giving it even more trustworthiness.
What I see good in IEEE Secure Device Identity standard is that it tells what kind of certificate one should be making. If device manufacturer would be following IDevID specification then job gets a bit easier. It says (in 8.6 subject) that:

A certificate’s subject and subjectAltName fields comprise a unique subject name that identifies the
entity (a device in DevID certificates, and a CA in DevID intermediate certificates) associated with the
public key in the subjectPublicKeyInfo field.
The DevID certificate subject field is always present, but can be empty. If non-null it contains an X.500
Distinguished Name (DN). An IDevID certificate subject field shall be non-null and should include a
unique device serial number encoded as the serialNumber attribute (RFC 5280 X520SerialNumber). In
the case of a third-party CA or a standards certification agency, the subject field can contain information
identifying the supplier or manufacturer of the device.
NOTE 1—As stated above, the recommended serialNumber is unique within the issuer’s (8.4) domain of significance,
not just within the context of precursor DN fields.

How I interpret this is that then:
Subject DN: /CN=MyProduct/serialNumber=P1234567 (and rest details is optional).
There are couple of things to think in here:

If we have multiple Manufacturer Root CA's registered -- there could still be collision as Subject DN field itself does not guarantee global uniqueness. When combined in context of certificate chain it becomes unique.
Now this is nice that there is clear definition what to do but encoding this to Endpoint Client Name is a bit problematic.

So once again we are having a problem what information from TLS Client Certificate we use and how it relates to Endpoint Client Name.
One solution for this is to recommend manufacturer if you manufacture your device with IEEE Secure Device Identity based IDevID then when doing LWM2M then send you Endpoint Client Name in certain format. What is good in this kind of operation is that there could be standard option -- mark this Manufacturer CA operating in IEEE Secure Device Identity mode. Eg. pre-existing policy/rule that can be selected.
Best idea so far that I have is utilizing dev-urn-ops form for Endpoint Client Name as that could be easily matched to certificate.
O == organization == enterprise OID (globally unique as there is registry -- and manufacturer knows their OID)
P == product == MyProduct
S == serial number == P1234567
So this would cause following sequence to happen:

Device connects to LWM2M Bootstrap service using:

IDevID for DTLS connection
In LWM2M using Endpoint Client Name in dev-urn-ops form.

LWM2M Bootstrap server then determines what policy is associated to Root CA which issued TLS Client Certificate.

If it is IEEE Secure Device Identity it looks up for associated Enterprise OID and verifies that Endpoint Client Name matches.
If it is "Globally Unique Subject DN's CN value" (eg. in case on dev-urn-imei or so) then it does simple compare.
<your rule/policy here>

LWM2M Bootstrap server stores device identity to its device registry
Next trick here is to go for Service Unique credentials -- LWM2M really should have feature to configure Endpoint Client Name from bootstrap server to client (probably should be proposed) but as a backup in system where Endpoint Client Name can be guarantee to be unique one could create TLS Client Certificate for device with endpoint client name in it that is signed under Service Specific Root CA. This works for both Certificate mode and for EST mode. I assume EST mode in this sequence.
Device would create a CSR with Subject DN: /CN=<endpoint client name>.
Device would connect to CoAP-EST service and authenticate itself with IDevID
CoAP-EST service need to verify client's credentials now. It need to lookup based on certificate details on device registry so that it can determine what is expected Endpoint Client Name for the device.
CoAP-EST service need to verify that CSR does include matching Endpoint Client Name
CoAP-EST service could do some other CSR validation checks too in here
CoAP-EST has now approved the CSR -> sends it to EST server for actual certificate creation.
CoAP-EST received certificate from EST server and provides it to device.
Device stores received certificate and associates it for this particular LWM2M service. (becomes Service Specific Device Certificate)
Device connects with new Service Specific Device Certificate to LWM2M Server (which was configured in bootstrap phase).
LWM2M Server only trusts X.509 Certificates under Service Specific Root CA and once passed it can do simple Subject DN's comparison against Endpoint Client Name.

I don't know if you aware about this class CertificateVerifier but this could also be a good place for PKIX validation. (We need to define which part of PKIX validation must be done in CertificateVerifier and which part should be done in SecurityChecker)

Both are needed. We need to do PKIX validation and then also look on the chain later.

so I suppose the goal should be that the Endpoint Client Name is unique in the service.

This is mandatory : "The Endpoint Client Name identifier MUST be unique at the server or servers it is being used with."  ( see 7.3.1. Endpoint Client Name)

For this reason I was thinking that if we pass whole certificate chain forward it allows one to do system of their liking.

We can do that even if for now I have still some doubts that some part of the certificate could really be useful at LWM2M level (e.g. Public Key)

LWM2M really should have feature to configure Endpoint Client Name from bootstrap server to client

As endpoint client name MUST be unique are you agree this is finally not needed ?

Both are needed. We need to do PKIX validation and then also look on the chain later.

Of course both are needed but maybe cert chain could only be used at DTLS/Scandium level using CertificateVerifier and ApplicationLevelInfoSupplier(https://github.com/eclipse/californium/pull/1014).
Because theoretically you have all the information necessary to retrieve the corresponding endpoint name in certificate :

either because the value is already present
or you have data needed to retrieve endpoint name though lookup table and you can store it principal via ApplicationLevelInfoSupplier.
(It's a possibility don't know if this is the best choice)

(I will bring more feedback tomorrow)

About Endpoint Client Name.
In Core v1.1.1 - 7.3 there is:

Endpoint Client Name

String

Identifies the LwM2M Client on one LwM2M Server (including LwM2M Bootstrap-Server).
This parameter is optional and provided to the LwM2M Server during Registration, also provided to LwM2M
Bootstrap-Server when executing the Bootstrap procedure. It MUST be provided when the security protocol does
not provide an authenticated identifier or this information is not available for the server.
The Endpoint Client Name is a string. Recommended URI and URN formats are documented in Section Endpoint
Client Name.

It says here that it is optional if security protocol provides authenticated identity. And for (D)TLS with X.509 TLS Client Certificate we do get authenticated identity from certificate itself (and from its chain) so in theory Endpoint Client Name cloud be omitted altogether.
Then in Core v1.1.1 - 7.3.1 is a bit more verbose on that but still contains the same information but adds:

This parameter MAY be omitted when the security protocol provides to the server an authenticated identifier that is identical to this parameter. For more discussion consult the security consideration section in the [LwM2M-TRANSPORT] specification.

And then in Transport v1.1.1 - 5.2.6 - Endpoint Client Name:

This specification recommends, but does not mandate, transmission of the endpoint client name in the Bootstrap-
Request and in the Register message. Since the endpoint client name is not authenticated at the application layer the
LwM2M Server MUST compare the received endpoint client name identifier with the identifier used at the TLS/DTLS
handshake. This comparison may either be an equality match or may involve a dedicated lookup table to ensure that
LwM2M Clients cannot intentionally or due to misconfiguration impersonate other LwM2M Clients.

Where as "comparison may either be an equality match or may involve a dedicated lookup table" gives freedom how X.509 certificate details shall be interpreted.
Based on those text I would interpret it as:

If Endpoint Client Name is presented it must be matched for the outer layer security credentials with equality match or with lookup/rule based matcher.
If Endpoint Client Name is missing it shall be copied/generated from outer layer security credentials with same rules.

And resulting in-memory object related to particular connection there should be Endpoint Client Name that can be used as unique device identity in context of particular LWM2M service.
Additional problem is that if same identity is given by different (Manufacturer) Root CA's which may require us to store also issuer information in the device registry on auto-registration cases so that another device does not have possibility to steal the identity.
If we do have PSK or Raw Public Key then it must be matched with pre-registered information stored in device registry. And then either take Endpoint Client Name from registry if missing or when provided then match that it matches what is in registry.

About X.509 Certificate Details.
I do not know what is the right amount of details to store in-memory and in device registry.
When one does auto-registration thru the bootstrapping then it might be good enough to store issuer information in addition to subject information.
Issuer information should be in format that can be matched to information in bootstrapping trust store.
In normal operations LWM2M Server should only have smaller service specific trust store only listing services own Service Specific Device Root CA where it is issuing device certificates. When device is later connecting back to bootstrapping service it must be possible to match DTLS TLS Client Certificate either to previously stored Manufacturer Root CA (in case of factory reset or so in the device) or to Service Specific Device Root CA used by service.
Issuer information and subject information are a bit problematic as subjectAlternativeName is also in picture. This is only problem for Manufacturer Root CA issued TLS Client Certificates and Service Specific Device Root CA issued certificates can have clean and easier contents.
If we can always do whole chain verification then in device registry we could store reference to Manufacturer's Root CA and then Endpoint Client Name as generated by rules or extracted from field in certificate itself.
About Public Key in X.509 Certificate -- we don't actually care about the value -- we trust in chain and it is used only in authenticating that client posesses associated private key and then in chain validation that it was really issued under by trusted root ca.
Haven't yet though if there is a need to store "next credentials" also in device registry. Like in case when device connects back to bootstrapping service to get new credentials while the old credentials are still valid. For X.509 certificates probably not needed as Endpoint Client Name should not be changing but might be needed for PSK/Raw Public Key cases.
There may be need to have different Bootstrapping credentials (pre-registration case) vs. Given credentials (given by bootstrapping service with security object).

Now about this ApplicationLevelInfoSupplier:
This might do the trick need to play with it.

You thought a lot about all of this and I must to confess that It's pretty hard to me to follow you. Probably because the problem is very vast and complex and there is also some terminology which is not so clear to me.
Maybe I'm wrong but is it possible that you try to achieve too many issues/use-cases at the same time.
Maybe we should start with the simpler use case (e.g: endpoint available in Subject DN), support/implement it.
Then identify the next one and trying to support it.
1 step at a time.
(knowing that we are in development phase for the 2.0.x, so it's OK to me to break API between 2 milestone releases )


Training problem?

Hi,wang
Thanks for your excellent work! When I train my custom dataset, loss suddenly changes to NaN on the way descent.
I'm tring to find reasons.
I have a question that your dtu dataset has a same depth range [dmin,dmax], but my dataset' depth range is different in every image. I don't know whether defferent  depth range  is ok for training. Could you  give me some advices ?

Hi,
I do not think the different depth range may cause a training problem. I did some experiments on BlendedMVS before, where the depth range are different for different images.

@FangjinhuaWang
Ok, thanks for your reply.


community[mini]: Add stop_reason and stop_sequence to Bedrock Anthropic model output

Description:
Currently, the output of Amazon Bedrock llms will ignore the stop_reason and stop_sequence fields in the output of Anthropic models, making it hard for users to rely on these fields to build agents.
Description of these two fields are described here:
https://docs.aws.amazon.com/bedrock/latest/userguide/model-parameters-anthropic-claude-messages.html
This PR adds these two fields in the "metadata" output field  if Bedrock returns them in the response so the downstream users could read and use the accordingly.
Dependencies:
n/a

Seems this approach is not feasible as the llm model eventually will only return "text" back in _call


AttributeError: module 'attr' has no attribute 'setters'

I tried to use this library to work with Airtable using the API, copied the code from the main page of the project to Github, after a second an error was raised:
AttributeError: module 'attr' has no attribute 'setters'

I also tried to install every existing version of attr but after checking none of the versions fixed this error.
Namely versions: 0.1.0, 0.2.0, 0.3.0, 0.3.1, 0.3.2

The dependency on the attrs library has been removed.


Robots.txt module get lost

I have slot A and slot B, both have Robots.txt module installed. But when I periodically import slot B's database into A, the Robots.txt module got lost. I can't see the module from orchard dashboard.
I checked orchard log and DB log, nothing helpful.

Modules (NHibernate) creates their own database tables. Maybe the problem is with how you export that data. You should use the import/export module for that matter. If you want to just switch from one database to another you need to be sure you have that module locally and remotely. That way, you are sure at least to have the same database structure on both ends.

@JingyuShao "Got lost" can mean many things. You should look into the log to see why it didn't get loaded. Also what do you do to get it back up?

Talked offline with @JingyuShao The module was not part of the git repository, and was hence lost after each deployment.


chore(main): release 1.3.0

:robot: I have created a release beep boop
1.3.0 (2024-05-03)
Features

add support for indent-blankline (a9eb003)
add support for treesitter-context (ef2cbcc)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/scottmckendry/cyberdream.nvim/releases/tag/v1.3.0 :sunflower:


[BEAM-12168] Revert "[BEAM-12011] Eliminate WindowFn.getOutputTime method"

This reverts commit fcf0f508adc002056a2534b9017f5807eec733d0 which caused breakage in https://ci-beam.apache.org/job/beam_PostRelease_NightlySnapshot/1341
Need to separate elimination of the method from elimination of its uses, to build a Dataflow Java worker that doesn't depend on it.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @kileys who alerted me to this

Run Gradle Publish

If that finishes running, Run Dataflow PostRelease should run beam_Release_NightlySnapshot

It looks like it can't find a worker to run the publish
https://ci-beam.apache.org/job/beam_Release_NightlySnapshot/

Code history will be cleaner with this revert and the roll-forward of removing uses, though, so that's probably worth it.

I see. So that makes a snapshot release from a PR? Makes me slightly uncomfortable but I'll take it. Anyhow merged this. And yes that Jenkins problem is a big one.


Sign in to confirm you're not a bot - YouTube

Hi
I've been following this bug in yt-dlp where YouTube is now blocking downloads:
https://github.com/yt-dlp/yt-dlp/issues/10128
I've implemented the OAuth2 workaround: https://github.com/yt-dlp/yt-dlp/issues/10128#issuecomment-2157140324
It is working from a residential IP address server. (got banned from Azure server)
If anyone has other success (from Cloud servers?) that would be good to know about.
Also if you need archiving from one of my servers please get in touch<EMAIL_ADDRESS>Regards
Dave

Also following the issue mentioned.
Current suggestion is to try the oauth2 plugin or rotate your IP (advice is to use residential proxies rather than VPNs).

As of release 2024.10.22 of yt-dlp, it has the OAuth flow built in.  https://github.com/yt-dlp/yt-dlp/wiki/Extractors#logging-in-with-oauth
pipenv update

# check which version you are using
pipenv shell

yt-dlp --version

# note that the new version just needs oauth and not oauth2 at the end of the config line

# youtubedl_archiver.py
ydl_options = {'outtmpl': os.path.join(ArchivingContext.get_tmp_dir(), f'%(id)s.%(ext)s'), 'quiet': False, 'noplaylist': not self.allow_playlist , 'writesubtitles': self.subtitles, 'writeautomaticsub': self.subtitles, "live_from_start": self.live_from_start, "proxy": self.proxy, "max_downloads": self.max_downloads, "playlistend": self.max_downloads, "username": "oauth", "password": ""}

And now the OAuth flow is not implemented anymore in yt-dlp.  https://github.com/yt-dlp/yt-dlp/wiki/Extractors#logging-in-with-oauth


external storage not cooperating with storage drawers drawer controller

Issue description:
useing storage drawers controller via the external storage but the storage shows as over full
What happens:
no items will go into the drawers due to the storage showing over 100% full even though there is only one or a few of each item per drawer
What you expected to happen:
expected to use storage drawers to accept the items assigned
Steps to reproduce:

build a basic rs system with priority 0
2.build a drawer system and set a few items (controller with some drawers)
put a external storage system with a negative priority
...

Version (make sure you are on the latest version before reporting):
playing the FTB omnia 1.4.0 pack

Minecraft: 1.15.2
Forge: 31.1.87
Refined Storage: 1.8.3
storage drawers 1.15.2-7.0.2

Does this issue occur on a server? yes
If a (crash)log is relevant for this issue, link it here:
[pastebin/gist/etc link here]

Higher Priority get inserted first.
Also, the numbers there are purely visual. They have no impact on whether items may be inserted.

Did I mix up mods. Does the priority number in rs have to be higher in value or lower? Cuz I set my external storage to -10 and the main storage to 0

Higher priority storage get considered first.  So you want +10 not -10.


add /status API endpoint for devtool data

This endpoint serves data useful to the SDK and other dev tools, e.g. to automatically set themselves up / automatically adjust to the config of the devmode:
curl --location --request GET 'http://localhost:3313/status'  --header 'Accept: application/json'  --data-raw ''
returns:
{
   "accounts":[
      {
private_key":"e6a91d633c77cf5771329d3354b3bcef1bc5e032c43d70b6d35af923ce1eb74dcea7ade470c9f99d9d4e400880a86f1d49bb444b62f11a9ebb64bbcfeb73fef3",
         "public_key":"ak_2a1j2Mk9YSmC1gioUq4PWRm3bsv887MbuRVwyv4KaUGoR1eiKi"
      },
...
   ],
   "chain":{
      "all_balances":[
         {
            "balance":1,
            "public_key":"ak_GLab8McCgXqng1pZbQDmjbCLw6f48qGyP4zWqzqBVnYwdNWVc"
         },
     ...
      ],
      "mempool_height":0,
      "top_height":1970
   },
   "devmode_settings":{
      "auto_emit_microblocks":false,
      "keyblock_interval":0,
      "microblock_interval":0
   }
}

as we discussed about an extended status endpoint this morning we could continue this here as I think it's currently the right place to do it.
@Denis Davidyuk can you comment this in regards to https://github.com/aeternity/aeternity/issues/3644? how would we like to observe that stuff in the SDK?
would it theoretically be possible to put that in the status input of the node where we could maybe have an extra property that includes plugin-specific status information? or do we need to keep it separate? @uwiger

Currently the devmode spawns a separate webserver. Serving this info would require having ways to access the plugin from within the node I guess, @uwiger ? Related to this: If not done so already, could we please ship devmode with the node client? From a communications- and developer marketing perspective, this would be a big big help for us, as it would kill extra steps necessary to get going with starting developing with aeternity. See this as a request from my role in the marketing team @uwiger . 🙏

The idea behind keeping it separate was that it could be one a more rapid track than the actual core software. This doesn't preclude bundling them, of course.
The step of supporting JSON was something I had started on too, since I felt that adding more functionality in the plugin 'API' would be too clumsy using only the initial makeshift web interface. From the beginning, I fully expected someone to rip out the sampe UX and use a more structured solution. This may still happen. OTOH, adding JSON endpoints won't be too hard as it is.
The plugin does run inside the node, so adding functionality to it and accessing it via the same web server won't be an issue (the web server also runs inside the node).

Ah, I see the point for being more agile. Maybe for now we could provide some one-line installer for the devmode, and include it a bit further down the road once it's a bit more mature ?

And technically, aeplugin_devmode_handler is accessible from the node's code then ?
And one could have the node's web api functions access the functionalities in there?

the point about having the regular status endpoint of the node exposing some data about the plugins is that the SDK e.g. could easily check about the supported plugins of the node it talks to.
personally I think at least for information purposes this would be great. not sure if devmode specific information like accounts etc. should be served in the same endpoint or if we should keep it separate.
I just want to provide some background about the discussion we had for everybody to be able to make suggestions and hopefully proceed with the right decision 😅

Well, the aeplugin_devmode_handler runs inside the actual node, but if we were to introduce code dependencies from the node to the plugin code, we should instead include it as a permanent part of the node.
The plugin starts as a regular OTP application inside the node, and fires up its own web server (this is trivial in Erlang). So theoretically, the devmode handler can efficiently call any function in the node. The main concern is that we don't want all internal functions of the node to be exposed as a de-facto API, since this would make maintenance extremely hard.
Having the plugin web server report on the functionality in the plugin is perfectly sensible. Having it call stable APIs (by some reasonable interpretation of the term) in the node is also ok.
If you want to have multiple plugins, serving different needs, this is fine too.

Having the plugin web server report on the functionality in the plugin is perfectly sensible. Having it call stable APIs (by some reasonable interpretation of the term) in the node is also ok.

This sounds perfekt to me. What do you think @davidyuk @mradkov ?

What plugins are included could of course be made available as a debug endpoint in the node. This is a slightly bigger operation than adding it to the devmode plugin, given the assumption that the plugin is ours to play with, at least for now.

I like the ideas here. I propose adding information on active plugins to the node's status api, containing (please amend):
-name (only mandatory field)
-version
-repo
-api url (if it has some API, like the devmode)
@uwiger correct me if I'm wrong, but currently, I see plugin info is only read from the config. I see two ways to get to the information above: it also has to be provided in the config, or we could amend something to the node's code that would try retrieving the information above directly from the plugins - a feature, that plugins could optionally support, basically providing some "meta data"?

Nikita's proposal looks too complicated, can the status response contain a plugins field as an object mapping the plugin name to data that that plugin assumes reasonable to have there? Can devmode plugin register itself in the node to don't make node depend on it?


RaiseError

I just noticed there is now a Raise Error Activity which is great but not mentioned on this page.

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

ID: d6923630-4042-e434-576a-a3dd7d5e5097
Version Independent ID: 530ddfec-68e0-eae3-5fb7-5e5633db6327
Content: What's new in Azure Data Factory - Azure Data Factory
Content Source: articles/data-factory/whats-new.md
Service: data-factory
Sub-service: concepts
GitHub Login: @PennyZhou-MSFT
Microsoft Alias: xupzhou

Here is a link to the doc.  I guess the feature was released a week ago, so your page is accurate as it should just be listed under October new features.
https://docs.microsoft.com/en-us/azure/data-factory/control-flow-fail-activity
From: Kranthi Pakala @.>
Sent: Tuesday, October 12, 2021 7:15 PM
To: MicrosoftDocs/azure-docs @.>
Cc: Noel Levine @.>; Author @.>
Subject: Re: [MicrosoftDocs/azure-docs] RaiseError (#82290)
Hi @Noel-ChillETLhttps://github.com/Noel-ChillETL, Thanks for sharing your feedback here. Could you please share a screenshot of the activity that your are referring to?
Thank you
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/82290#issuecomment-941732735, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AWBAAEOYQHGSKL3DV524JPDUGS6OZANCNFSM5F3WB5NA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@Noel-ChillETL I have assigned this issue relevant team who will further review your request and provide an update accordingly.
Hi @ssabat - Could you please review above feedback from @Noel-ChillETL . Thank you


Bug when limiting the number of sentences in the summary

When I limit the number of sentences in the summary to 1, for example, the forward function in PtrExtractorRL in /model/rl.py is called.
The for loop for _ in range(n_step): is run once (n_step=1) and the output is returned.
Yet in decode_full_model.py the last element of the extracted output is removed as EOE:
 ext = extractor(raw_art_sents)[:-1] # exclude EOE.
So in this case the only sentence being extracted is discarded as EOE.
One solution I can think of is to append an EOE in the forward function of PtrExtractorRL. Specifically, insert the following lines just before the return call:
if out.item() != score.size()[1]:
    append(torch.tensor([[score.size()[1]]], device=out.get_device()))

You should use PtrExtractorRLStop. PtrExtractorRL is developed before I came out with the EOE action idea. Since models with EOE work much better I did not maintain a version without it.


Bootstrap Ubuntu taking longer than expected time

Normally, it only takes like no more than 2 minutes.
But these day, it takes more than 10 minutes, with the same rackhd server and rackhd nodes.
Is there any debug methods we could try?

Hey @kaleo211,
When you say it normally takes no more than 2 minutes, was that using an earlier version of RackHD, or a separate system?
We found the Ubuntu installs to be fairly time consuming I'm afraid, they're also the most intense with file transfer, which is where (at a complete guess with no data) most of the time is being consumed.
If you watch the logs from the on-http process, you'll see all the requests back and forth during the install process, and that should give some sense of if that's the bottleneck or not. Right now, we're serving all files through on-http (serves static files as well as the REST API), so as a single process it could be the bottleneck. I'd need more information from you to help verify that though.
If that does turn out to be the issue, you can host the static files yourself using an alternate (faster, leaner) method. I would personally tend to suggest nginx for something like that. If you go this route, you'll need to tweak the template used for the installation (lines like https://github.com/RackHD/on-http/blob/master/data/templates/ubuntu-trusty-preseed#L4 and https://github.com/RackHD/on-http/blob/master/data/templates/ubuntu-trusty-preseed#L183) to reference the correct location for however you set up nginx.
You may also find that tweaking the debseed for an Ubuntu installation itself can render some speed benefits - the templates we have in there are examples, and you may want to tweak them for your own uses regardless.


how to limit rdp sessions number in rdpwrap ini file

how to limit rdp sessions number in rdpwrap.ini file (to set possible maximum, lets say 5 sessions at one time)
sorry, if this question is already answered, but i checked issues and did not find answer (maybe missed;))

It should be normally configured with GP.
Closed as not actual


Catalog should validate input parameters before using graveler

Remove the NewXXX calls for graveler data types
Validate Catalog input parameters based on the same validation we currently use in cataloger

Closed by https://github.com/treeverse/lakeFS/commit/095ac0e01a3dcad7cd5b246656d19e17372b8005

Closed by https://github.com/treeverse/lakeFS/commit/095ac0e01a3dcad7cd5b246656d19e17372b8005


Align UX and API on Product Create/Edit

The Create/Update methods have been moved out of the ProductsController into the ManageIqProductsController.
UX is currently expecting Create/Update methods defined on Products Controller which is causing an
AbstractController::ActionNotFound (The action 'create' could not be found for ProductsController):

error to be thrown.
Figure out a way to resolve this.

IS this the same issue here:
https://github.com/projectjellyfish/ux/issues/268

Duplicate of UX#268 closing.


Programmable Switch Event in Homebridge Log

Is this a bug with the plugin keeps on pinging the button?

Dear @ebaauw, I have read through a couple of threads with the same problem - you always send a link to the Wiki and updating the log level. For you or anyone completely into this stuff, this might seem like a perfect response. But there are many people out there - myself included - that have absolutely no idea what all that means and where to actually change it.
Could you please - for us idiots - give us a step by step foolproof mini guide, as to what we should change in Homebridge, so we do not get the message anymore? In the config? In the console?
Thanks so much!!!!!

@Domser21  did you figure it out somehow? we're lost, too. and the wiki link isn't helping.


Add serde support for Hash behind optional feature

Added a new cargo feature serde that when enabled will derive serde::Serialize and serde::Deserialize for the blake3::Hash struct.
Fixes https://github.com/BLAKE3-team/BLAKE3/issues/290

Lots of folks have asked for this over the last couple years, so it probably does make sense to go ahead and include it. Thanks for opening the PR!

Lots of folks have asked for this over the last couple years, so it probably does make sense to go ahead and include it. Thanks for opening the PR!

Thanks, I'm glad you are willing to merge it into main!

Could you rebase on the most recent master? There has been some churn in Cargo.toml.

Sure no problem, rebased with latest master branch

Landed, thanks!


An unexpected status code 520 response was received from the server.

Describe the bug
As a test of the capabilities, I requested it to make a browser based game and it did but the "preview" was just a white screen so I tried to deploy it, it spend 30k tokens and produced an error...

Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-qaq8b3
Steps to reproduce

Prompt: "Create a browser based RTS game in the spirit of command and conquer"
Prompt: "Deploy this application."

Expected behavior
Launch the game
Screen Recording / Screenshot

Platform
Browser name = Firefox
Full version = 132.0
Major version = 132
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:132.0) Gecko/20100101 Firefox/132.0
performance.memory = undefined
Username = Domoramo
Chat ID = 84dc9c0b2e7c

Additional context
No response

Appreciate the feedback! We are aware of this issue and are tracking it here.


[BUG] Unable to delete snapshot due to code = Unimplemented desc = unknown method SnapshotHashCancel for service ptypes.SyncAgentService

Describe the bug (🐛 if you encounter this issue)
Unable to delete snapshots since upgrading to 1.4.2.   When attempting to delete the snapshot within the UI, we receive the message:-
failed to delete snapshot: proxyServer=<IP_ADDRESS>:8501 destination=<IP_ADDRESS>:10005: failed to remove snapshot [backup-all-c-9b20dda1]: rpc error: code = Unknown desc = failed to cancel snapshot backup-all-c-9b20dda1 hash task: rpc error: code = Unimplemented desc = unknown method SnapshotHashCancel for service ptypes.SyncAgentService
I didn't incorrectly upgrade from 1.2.x to 1.4.2, accidently skip 1.3.x.   But snapshots created on 1.4.2 also receive the same message.
Even deleting the snapshot using kubectl does not work.
To Reproduce
Steps to reproduce the behavior:

Locate a Volume
Click Take Snaphot
Wait for snapshot to be created
click on snapshot and select delete
receive the error message

Expected behavior
I expect snapshots to be deleted.
Log or Support bundle
Support bundle will be sent
Environment

Longhorn version: 1.4.2
Installation method (e.g. Rancher Catalog App/Helm/Kubectl): kubectl apply
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: k8s

Number of management node in the cluster: 6
Number of worker node in the cluster: 6

Node config

OS type and version: Ubuntu 20.04 and 22.04
CPU per node: Normally 4
Memory per node: Normally 16gb
Disk type(e.g. SSD/NVMe): SAN
Network bandwidth between the nodes: 1GB

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): VMWare and Openstack
Number of Longhorn volumes in the cluster:106

Additional context

Is the engine of the problematic volume upgraded to v1.4.2?

Yes,  everything is at 1.4.2

Need to send support bundle,  but don't want to attach to public issue

Sure. You can send it to<EMAIL_ADDRESS>

support bundle too big to email,   so I have sent an email with a link to download it.

@Michael-Baylis
Thanks for the support bundle. I've checked the support bundle.
Most of volumes are still using longhornio/longhorn-engine:v1.2.3 image, e.g. pvc-001e0476-d91a-4f78-b080-fd21a6dbdd36. You can scale down the workloads using these volumes, upgrade the engine image of the volumes to v1.4.2, and then scale up.

Well,  don't I feel like I am an idiot!
I think I am missing a concept.   Will review ta.

Well, don't I feel like I am an idiot!
I think I am missing a concept. Will review ta.

No worries.  Feel free to contact us if need any help. Thank you.

I can confirm that when I upgrade the volume engine image,   I can now delete the snapshots.
Thank you for your assistance.


Fixed README

Changed 'respect' to 'expect' to make sense in sentence.

"Respect" is the correct English word to use here - all of the commands will obey/respect the text in nvmrc. "expect" implies a requirement, which is not the case - nvmrc is optional.


Testing with Bun(experimental)

Codecov Report

Merging #345 (b932a6b) into main (8741056) will increase coverage by 0.00%.
The diff coverage is 87.50%.

:exclamation: Current head b932a6b differs from pull request most recent head 457952a. Consider uploading reports for the commit 457952a to get more accurate results

@@           Coverage Diff           @@
##             main     #345   +/-   ##
=======================================
  Coverage   87.57%   87.57%
=======================================
  Files          72       72
  Lines        4451     4452    +1
  Branches      564      564
=======================================
+ Hits         3898     3899    +1
  Misses        552      552
  Partials        1        1

Impacted Files
Coverage Δ

packages/core/src/utils/uniqueIdFactory.ts
75.00% <75.00%> (ø)

packages/core/src/utils/index.ts
100.00% <100.00%> (ø)

...ackages/swagger-ts/src/generators/TypeGenerator.ts
66.76% <100.00%> (+0.18%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Revert "Bump github.com/dgraph-io/ristretto from 0.0.3 to 0.1.0 (#8500)"

This reverts commit dad900ab5fd01999642e5cd79a547b1d318897db.
What does this PR do?
A brief description of the change being made with this pull request.
Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
Describe how to test your changes
Write here in detail how you have tested your changes
and instructions on how this should be tested in QA.
Describe or link instructions to set up environment
for testing, if the process requires more than just
running the agent on one of the supported platforms.
Checklist

[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] The need-change/operator and need-change/helm labels has been applied if applicable.
[ ] The appropriate team/.. label has been applied, if known.
[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] The config template has been updated if applicable.

Note: Adding GitHub labels is only possible for contributors with write access.

I found those errors in AppVeyor:
=== FAIL: pkg/network/config TestIgnoreConntrackInitFailure (unknown)
panic: Failed to find GetQueuedCompletionStatus procedure in kernel32.dll: The specified procedure could not be found.

goroutine 48 [running]:
golang.org/x/sys/windows.(*LazyProc).mustFind(...)
	C:/gopath/pkg/mod/golang.org/x/sys@v0.0.0-20210601080250-7ecdf8ef093b/windows/dll_windows.go:325
golang.org/x/sys/windows.(*LazyProc).Addr(...)
	C:/gopath/pkg/mod/golang.org/x/sys@v0.0.0-20210601080250-7ecdf8ef093b/windows/dll_windows.go:333
github.com/Microsoft/go-winio.getQueuedCompletionStatus(0x12c, 0xc0004bff9c, 0xc0004bffa0, 0xc0004bffa8, 0xc0ffffffff, 0x206ce75, 0x3431880)
	C:/gopath/pkg/mod/github.com/!microsoft/go-winio@v0.4.17-0.20210211115548-6eac466e5fa3/zsyscall_windows.go:357 +0x15b
github.com/Microsoft/go-winio.ioCompletionProcessor(0x12c)
	C:/gopath/pkg/mod/github.com/!microsoft/go-winio@v0.4.17-0.20210211115548-6eac466e5fa3/file.go:167 +0xb6
created by github.com/Microsoft/go-winio.initIo
	C:/gopath/pkg/mod/github.com/!microsoft/go-winio@v0.4.17-0.20210211115548-6eac466e5fa3/file.go:73 +0x85

=== FAIL: pkg/network/config TestIgnoreConntrackInitFailure/via_YAML (unknown)
panic: Failed to find GetQueuedCompletionStatus procedure in kernel32.dll: The specified procedure could not be found.

goroutine 48 [running]:
golang.org/x/sys/windows.(*LazyProc).mustFind(...)
	C:/gopath/pkg/mod/golang.org/x/sys@v0.0.0-20210601080250-7ecdf8ef093b/windows/dll_windows.go:325
golang.org/x/sys/windows.(*LazyProc).Addr(...)
	C:/gopath/pkg/mod/golang.org/x/sys@v0.0.0-20210601080250-7ecdf8ef093b/windows/dll_windows.go:333
github.com/Microsoft/go-winio.getQueuedCompletionStatus(0x12c, 0xc0004bff9c, 0xc0004bffa0, 0xc0004bffa8, 0xc0ffffffff, 0x206ce75, 0x3431880)
	C:/gopath/pkg/mod/github.com/!microsoft/go-winio@v0.4.17-0.20210211115548-6eac466e5fa3/zsyscall_windows.go:357 +0x15b
github.com/Microsoft/go-winio.ioCompletionProcessor(0x12c)
	C:/gopath/pkg/mod/github.com/!microsoft/go-winio@v0.4.17-0.20210211115548-6eac466e5fa3/file.go:167 +0xb6
created by github.com/Microsoft/go-winio.initIo
	C:/gopath/pkg/mod/github.com/!microsoft/go-winio@v0.4.17-0.20210211115548-6eac466e5fa3/file.go:73 +0x85


Adding external JARs

I was trying to access the spark-csv package, but I was unsuccessful by either
a) Adding it to the java.classpath like
java.classpath.push("/tmp/jarCache/spark-csv_2.10-1.3.0.jar");

b) Specifying the --jar parameter in the args for 'NodeSparkSubmit'
Is there a suggested way to do this that I am missing?

Nevermind, found the answer by supplying the --packages argument like this
args = ['--class', 'org.apache.spark.repl.Main', '--packages', 'com.databricks:spark-csv_2.10:1.3.0']
           .concat(['spark-shell']);

and supplying the SparkContext with the JAR via addJar() like this: sparkContext.addJar()
Maybe it would make sense to add this to the Readme...

Maybe it would make sense to add this to the Readme...

Indeed... PR welcome :)
(bonus points for providing a short example of using the package...)

tobilg

i need yr help
i need to create facebook api group post comment fetch
i will pay u for this job
pls
contact<EMAIL_ADDRESS>thanks

@steptaker10 What in the world has the Facebook API to do with this issue? Look at the docs at https://developers.facebook.com/docs/graph-api/reference/v2.5/group#read and build it yourself.

@tobilg actually re the first part, you should be able to pass --packages 'com.databricks:spark csv_2.10:1.3.0'  on the command line rather than having to modify args in the file. Let me know if that doesn't work.

That's correct if you use if from the command line. As I integrated it into another application, I will need to use the args array I guess. The passign of the packages can be dynamic, I just wrote it statically to show the behavior.


Update request: pot 2.7.9 → 3.0.5

Package name: pot
Latest released version: 3.0.5

Current version on the unstable channel: 2.7.9
Current version on the stable/release channel: 2.7.9

[x] Checked the nixpkgs pull requests

Notify maintainers
@linsui

Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

https://github.com/pot-app/pot-desktop#环境要求
https://github.com/NixOS/nixpkgs/pull/320250