Add setuptools

Fix #2133

hi @giswqs is there any reason for updating to earthengine-api>=1.0.0 ??

@dfguerrerom Any particular reason you can't update to earthengine-api 1.0? Newer version sometimes has some security features that are not available in older versions. Eventually, you will be forced to update it because the server won't allow you connect if the api is lower than a cerntain verison.

Thanks for the heads up!, In the system where I work, we install a custom earthengine-api fork which allow us to better handle the authentication process. Your requirement makes our installation ee fork be overshadowed by the last ee version, which makes this app to crash. FTM I will pin a previous geemap version.

what custom authentcation process are you using? Have you tried the geemap.ee_initialize() function? Would that work for you? If not, let me know the requirements are. I will see if I can integrate it into geemap.

in https://sepal.io we allow users to authenticate in gee via UI, see: https://docs.sepal.io/en/latest/setup/gee.html#connect-gee-and-sepal. An integration won't be possible because we don't expose the refresh_token, and the access_token's are managed internally.
I need to check what is new in the latest ee release, and I hope they have fixed the issue that I pointed in a repo that I've started https://github.com/dfguerrerom/ee-client?tab=readme-ov-file#earth-engine-session-client to allow multi-user authentications.

Makes sense. Thanks for clarifying.


Cannot join etcd node with specific combinations of member IP addresses

Environmental Info:
k3s version v1.21.1+k3s1 (75dba57f)
go version go1.16.4
Also present in:
k3s version v1.21.3+k3s-a1e36153-dirty (a1e36153)
go version go1.16.6
the -dirty part just being the fix for this issue
Node(s) CPU architecture, OS, and Version:
Linux c-1 5.4.0-73-generic #82 SMP Thu Jun 3 02:29:43 UTC 2021 x86_64 GNU/Linux
k3OS v0.21.1-k3s1r0
Cluster Configuration:
Minimal test cluster: 1 server (including embedded etcd), 2nd server to join
Describe the bug:
Second server with etcd role cannot join if the string representation of its Node/Advertise IP address is a substring of the existing etcd server's IP
Steps To Reproduce:

Installed K3s: Installed k3OS on two nodes.
1st server with --cluster-init, node IP <IP_ADDRESS>
2nd server with server_url: https://<IP_ADDRESS>:6443, node IP <IP_ADDRESS>

Expected behavior:
Get a cluster with two server nodes, both being etcd members
Actual behavior:
2nd node won't join
Additional context / logs:
time="2021-08-12T19:07:15.180143758Z" level=info msg="Starting k3s v1.21.1+k3s1 (75dba57f)"
time="2021-08-12T19:07:15.219392660Z" level=warning msg="Cluster CA certificate is not trusted by the host CA bundle, but the token does not include a CA hash. Use the full token from the server's node-token file to enable Cluster CA validation."
time="2021-08-12T19:07:15.219765757Z" level=info msg="Managed etcd cluster not yet initialized"
time="2021-08-12T19:07:15.235265597Z" level=fatal msg="starting kubernetes: preparing server: start managed database: joining etcd cluster: etcdclient: no available endpoints"
Backporting

[ ] Needs backporting to older releases

Don't think this is needed, there's an easy workaround (use different IPs).

Validated the same as in https://github.com/k3s-io/k3s/issues/3833#issuecomment-901405862 using master commitid ad1a40a96c400c17780cf9455f5da330d690194c


[Documentation Update]:  Lc solution 863

Is there an existing issue for this?

[X] I have searched the existing issues

Issue Description
Addition of leetcode solution to problem 863
Suggested Change
Lc solution 863
Rationale
No response
Urgency
High
Acknowledgements

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository
[X] I have read and followed the Contribution Guidelines
[X] I have followed the code style guidelines of this project
[X] I have checked for any existing open issues that my pull request may address
[X] I have ensured that my changes do not break any existing functionality
[X] Each contributor is allowed to create a maximum of 4 issues per day. This helps us manage and address issues efficiently
[X] I have read the resources for guidance listed below
[X] I have not used AI-generated content (e.g., ChatGPT, other AI tools)
[X] I have not used content from existing sites (e.g., text, images)
[X] I have followed all security rules and only shared trusted resources

/assign


legacy: ANSI_QUOTES setting on second try

FIX Sets the ANSI_QUOTES setting also on the second attempt
to connect to the database in case of a lost connection.

Signed-off-by: Jan Aage Lavik<EMAIL_ADDRESS>

Just discovered this issue. Added it to the current milestone due to its small size.

:shipit:
--
fyi @hachreak

@jalavik since it has been introduced in 79741888d8e71b22e704a30038f9857d90a38590 I would remove FIX label from the commit message. Thanks a lot for yet another catch :+1:

@jalavik since it has been introduced in 7974188 I would remove FIX label from the commit message.

... or we can amend the original commit message here (via AMENDS 7974188) and also fix the (invalid) COMPATIBILITY label at the same time?

fix the (invalid) COMPATIBILITY label at the same time?

:+1:

So how would the commit message look with these considerations in mind?
legacy: ANSI_QUOTES setting on second try

* BETTER Supports database creation on PostgreSQL server.

* Enables 'sql_mode' as 'ansi_quotes' for quotes compatibility for MySQL.

* AMENDS 7974188

IMHO @tiborsimko meant s/COMPATIBILITY/INCOMPATIBLE/.

So, something like this?

:+1:


Check ownership before a slice is deleted

Only the owner can update the slice, so I think it makes sense to only allow the owner to delete the slices as well.

Coverage decreased (-0.2%) to 81.772% when pulling da30b28eba13b0d344b3360c0bc2ce5633732bf9 on x4base:check_own_on_delete into a11749899180c023a68b8f68a8061ed060c150d5 on airbnb:master.


Could you provide an 'Authorization Code' grant type example?

Might be I am not using the library correctly, but could you provide an example of 'Authorization Code' grant type? thanks a lot!
Here is my code, written with Kotlin
I got the response with 200 code, but the response.body is empty thus response.jsonParsed is false, so isSuccessful is false as well.
And I didn't see the redirect web page with YES or No button opened.
The Api doc is at https://help.infoodle.com/api/authentication
    val parameter = mapOf(
            "redirect_uri" to "https://app-t.infoodle.com/apiv2_auth",
            "response_type" to "code")
    val client = OAuth2Client.Builder(username, password,
            clientid, detail.clientSecret,
            "https://app-t.infoodle.com/apiv2/oauth2/authorise")
            .grantType("authorization_code")
            .parameters(parameter)
            .build()
    client.requestAccessToken{response ->
        if (response != null && response.isSuccessful) {
            val fragment = InfoodleDirectoryFragment.newInstance(response.accessToken)
            activity?.replaceFragment(fragment)
        } else {
            showDialog("hehe", "fail")
        }
    }

Thanks very much!

I get it, after reading these two pages, it is soooooo complicated.
I'll close this issue now.
https://medium.com/@android2ee/oauth-2-on-android-principles-using-google-apis-afb5cc12d935


Added key binding functionality for any task.

Closes #6550.
Update: The usage now is to define a command binding per @dbaeumer.  Once a command binding is added to the task, it will be available for making it a keyboard shortcut.
Example task in tasks.json:
		{
			"taskName": "Do Something",
                        "suppressTaskName": true,
			"showOutput": "always",
			"commandBinding": {
				"id": "myproject.specialtask",
				"title": "Do something",
                                "category": "Optional category"
			}
		}

Then Do something will show up in the menu and to add a keyboard shortcut, do this in keybindings.json:
  {
    "key": "ctrl+r r",
    "command": "myproject.specialtask"
  }

Hi @codyrigney92, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

@codyrigney92, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, MSBOT;

@codyrigney92 thanks for the PR. I have a couple of suggestions:

strings shown in the UI should never be concatenated using +. They always need to got through an nls.localize call. Think about a right to left language. Concatenating strings in the form you did doesn't work then. So code like nls.localize('RunTaskAction.label', "Run Task") + ' - ' + taskName must be written like this: nls.localize('RunTaskAction.label', "Run Task - {0}", taskName)

Not all tasks in a tasks.json should be given a RunSpecificTaskAction. The reason being that for gulp and grunt we do auto task detection. If a gulp file has 20 tasks we will add 20 actions. IMO we should tag tasks in the tasks.json which should get its own action.

@dbaeumer Thanks I'll work through those suggestions.  Can you elaborate what you mean by

IMO we should tag tasks in the tasks.json which should get its own action.

@codyrigney92 I am thinking out something comparable to how commands are registered in the package.json of an extension. I think the stories should be aligned since it will allow us to even bind a task then to a menu item or an action presented in the editor. The Json should look something like this:
		{
			"taskName": "MyTask",
			"commandBinding": {
				"id": "the command id",
				"title": "the title",
				"category": "the category used in F1",
				"icon": "an optional icon"
			}
		}

Unfortunately we can't name the property command like in package.json since command is already taken for the OS command to run. You want to take a look at the IUserFriendlyCommand in menusExtensionPoint.ts.
If we have these command we can even register them with the MenuRegistry to bind tasks to UI pieces like context menus.
Let me know if this makes sense to you.

@dbaeumer I think this makes sense.  So then would the key binding go next to commandBinding or would it go where it is now in the keybindings.json?  Also, we don't have icons yet do we?

@codyrigney92 the keybinding should go to the keybindings.json to ensure that we have one place where keybindings are defined. Icons could be resolved locally to the workspace if the path is relative.

@dbaeumer Ok.  Going back to a previous comment, why wouldn't we want grunt tasks to be able to have key bindings?  Your comment was this:

Not all tasks in a tasks.json should be given a RunSpecificTaskAction. The reason being that for gulp and grunt we do auto task detection.

@codyrigney92 gulp and grunt tasks should be able to have key bindings. However if a gulp file has 20 tasks I don't want to see the 20 tasks in the Command Palette when pressing F1. So we shouldn't simply take all TaskDescription from the task service. Instead we should only generate commands for those that have the binding information.
May be some more background: for gulp and grunt we merge the tasks defined in tasks.json with the once defined in the corresponding file (gulpfile.js). We basically auto detect these tasks. So if the gulp file has a task 'xyz' it will be in the task service even if not listed in the tasks.json.

@dbaeumer Sorry I've been busy lately, I'll try to get to this soon.

@cmrigney no problem. We wrap up September right now so this will have to wait for October

Are we there yet?

Is there any progress on this PR?

@20percent  I'm going to attempt to finish this today.

I have this finished but I ran into some issues pushing it upstream.  I'll have this updated tomorrow.

Ok I've pushed my new changes and updated my first comment on how to use it.  @dbaeumer Can you double check me to make sure I didn't miss anything?  I had trouble with the icon but I may have been misusing it.
Sorry this took so long and left some conflicts.  Let me know if there's anything else I need to do with this pull.  Thanks.

@cmrigney I will see what I can do :-). Any change that you resolve the merge conflicts and the failing tests.

@dbaeumer I can resolve the conflicts but I'm not sure about the tests.

@dbaeumer Ok no conflicts now, but unfortunately it added some white space changes...

Whitespace is all cleaned up.

@dbaeumer Any idea why the AppVeyor test failed? The log is blank.

Unfortunately I was not able to get this into November given the LSP work I had to do. For January we want to completely revisit the way tasks work. See the discussion here: https://github.com/Microsoft/vscode/issues/15179. I will make sure that this will make it into the new design.

I implemented a new runner that executes task in the terminal. The benefit is that we can now execute more than one task in parallel. It is not on be default, but will be in the next release. The release notes for the next release will contain instructions how to play with this.
However this raises the questions that key binding will not be per task only. Consider the use case where a watch task compiler ts -> js and one task compiles less -> css and users want to bind one keybinding to both tasks and even might define the order in which they are executed (parallel, sequence, ...). Since it is not clear how this will be declared I didn't merge this into the Jan release. I envision currently something like a composite task to which a key binding can then be assigned. This wouldn't  change the current design too mich. However not sure yet. If someone has ideas, please add them here.

@dbaeumer Is it possible to use this PR and modify it so that commandBinding optionally takes an array for multiple tasks?

@cmrigney not sure I understand that correctly. The commandBinding property is currently local to a task. If it would take array, what would be the array type.

@dbaeumer Ah yes your right, my mistake.  What about the command property of the keybindings? What if it took an array of strings?
 {
    "key": "ctrl+r r",
    "command": ["myproject.specialtask", "myproject.othertask"]
 }

Or maybe even allow each element in the array to be an object with other properties such as delay or whatever.

Interesting idea. Currently I lean more towards something like this
{
"taskName": "SuperTask",
"tasks": ["taskOne", "taskTwo"]
}
So a task has either a command or a task array. Then the command binding would stay the same. But I am not sure if this is a nice solution.

That's a good idea.  A task could execute other tasks. You would need to check for circular references though.

Good point. The task execution engine I would say :-)

@cmrigney started to work on this. A lot has change in the workbench which makes this now a lot easier. There are now command in the workbench first class and they can receive args from a keybinding. So this can even be done without any additional information in the tasks.json :-). See the cast attached. All I did are code changes and a keybinding definition. Hope this is what you expect:

@dbaeumer That's great!  Is this in the current version or will it be in the next release?

This will be in the next release and in the insider soon. Still on my private branch...

I am closing this PR since it got implemented using a new / better way leveraging new API. It is available since 1.10.


Is that possible to choose connector automatically?

Hi,
I tried to implement automatically choose connector based on given scheme.
I tried.
  let client = match uri.scheme().unwrap(){
    "https" =>::hyper::Client::configure()
        .connector(::hyper_tls::HttpsConnector::new(4, &core.handle()).unwrap())
        .build(&core.handle()),
    _ =>  Client::new(&core.handle())
  };

but get
error[E0308]: match arms have incompatible types
  --> src\client.rs:50:16
   |
50 |     let client = match  uri.scheme().unwrap(){
   |  ________________^
51 | |     "https" =>::hyper::Client::configure()
52 | |         .connector(::hyper_tls::HttpsConnector::new(4, &core.handle()).unwrap())
53 | |         .build(&core.handle()),
54 | |     _ =>  Client::new(&core.handle())
   | |           --------------------------- match arm with an incompatible type
55 | |   };
   | |___^ expected struct `hyper_tls::HttpsConnector`, found struct `hyper::client::HttpConnector`
   |
   = note: expected type `hyper::Client<hyper_tls::HttpsConnector<hyper::client::HttpConnector>, _>`
              found type `hyper::Client<hyper::client::HttpConnector, _>`

is that possible to get a compatible type?

Yea, that error is because the two clients are different types. The HttpsConnector in this crate already supports both schemes, only using TLS on HTTPS requests.


Provide clientset implementation for Datashim objects

Datashim does not have a client library so that external applications can query the K8S API Server for objects such as Datasets and DatasetInternals. The solution is to create a clientset following guides such as this

Initial set of client APIs pushed into branch generate_clientset


racer.racerBinPath is not set in your config.

[Enter steps to reproduce below:]

...
...

Atom Version: 1.3.2
System: Mac OS X 10.10.4
Thrown From: Atom Core
Stack Trace
racer.racerBinPath is not set in your config.
At undefined

undefined

Commands
     -3:11.9.0 editor:newline (atom-text-editor.editor.is-focused)
     -3:06.8.0 core:move-right (atom-text-editor.editor.is-focused)
  2x -3:05.2.0 core:move-left (atom-text-editor.editor.is-focused)
     -1:30.4.0 editor:newline (atom-text-editor.editor.is-focused)
  4x -1:27.9.0 core:backspace (atom-text-editor.editor.is-focused)
     -1:25.9.0 snippets:next-tab-stop (atom-text-editor.editor.is-focused)
     -1:25.9.0 snippets:expand (atom-text-editor.editor.is-focused)
     -1:25.9.0 editor:indent (atom-text-editor.editor.is-focused)
  5x -1:25 core:backspace (atom-text-editor.editor.is-focused)
     -1:06.0 grammar-selector:show (atom-text-editor.editor)
  4x -0:14.6.0 core:backspace (atom-text-editor.editor.is-focused)

Config
{
  "core": {},
  "editor": {
    "invisibles": {}
  }
}

Installed Packages
# User
language-rust, v0.4.5
racer, v0.17.2

# Dev
No dev packages

This looks like a duplicate of https://github.com/edubkendo/atom-racer/issues/64 – feel free to subscribe there for updates.


KAFKA-16584 Make log processing summary configurable or debug

KAFKA-16584 Make log processing summary configurable or debug
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Please don't forget to update the docs (upgrade guide and configs sections).

@dujian0068 -- you should send a final email to the VOTE thread calling the vote closed and accepted (also summarizing the vote result), and update the KIP wiki pages accordingly. Thanks.

Please don't forget to update the docs (upgrade guide and configs sections).

Thank you review:
Do you mean the documentation that needs to be updated is in the https://github.com/apache/kafka-site project?

No. The doc changes just go into kafka.git as part of this PR -> https://github.com/apache/kafka/tree/trunk/docs/streams
kafka-site.git will only be updated during the next release -- you don't have to worry about this part.

Failures unrelated
[Build / JDK 21 and Scala 2.13 / kafka.server.DelegationTokenRequestsTest."testDelegationTokenRequests(String).quorum=kraft"](https://ci-builds.apache.org/job/Kafka/job/kafka-pr/job/PR-16509/3/testReport/junit/kafka.server/DelegationTokenRequestsTest/Build___JDK_21_and_Scala_2_13____testDelegationTokenRequests_String__quorum_kraft_/)
[Build / JDK 21 and Scala 2.13 / kafka.zk.ZkMigrationFailoverTest.testControllerFailoverZkRace()](https://ci-builds.apache.org/job/Kafka/job/kafka-pr/job/PR-16509/3/testReport/junit/kafka.zk/ZkMigrationFailoverTest/Build___JDK_21_and_Scala_2_13___testControllerFailoverZkRace__/)
[Build / JDK 21 and Scala 2.13 / org.apache.kafka.controller.QuorumControllerTest.testFenceMultipleBrokers()](https://ci-builds.apache.org/job/Kafka/job/kafka-pr/job/PR-16509/3/testReport/junit/org.apache.kafka.controller/QuorumControllerTest/Build___JDK_21_and_Scala_2_13___testFenceMultipleBrokers__/)
[Build / JDK 21 and Scala 2.13 / org.apache.kafka.controller.QuorumControllerTest.testDelayedConfigurationOperations()](https://ci-builds.apache.org/job/Kafka/job/kafka-pr/job/PR-16509/3/testReport/junit/org.apache.kafka.controller/QuorumControllerTest/Build___JDK_21_and_Scala_2_13___testDelayedConfigurationOperations__/)
[Build / JDK 8 and Scala 2.12 / org.apache.kafka.connect.mirror.integration.MirrorConnectorsIntegrationTransactionsTest.testSyncTopicConfigs()](https://ci-builds.apache.org/job/Kafka/job/kafka-pr/job/PR-16509/3/testReport/junit/org.apache.kafka.connect.mirror.integration/MirrorConnectorsIntegrationTransactionsTest/Build___JDK_8_and_Scala_2_12___testSyncTopicConfigs__/)
[Build / JDK 8 and Scala 2.12 / kafka.api.ConsumerBounceTest.testConsumptionWithBrokerFailures()](https://ci-builds.apache.org/job/Kafka/job/kafka-pr/job/PR-16509/3/testReport/junit/kafka.api/ConsumerBounceTest/Build___JDK_8_and_Scala_2_12___testConsumptionWithBrokerFailures__/)
[Build / JDK 8 and Scala 2.12 / org.apache.kafka.tools.GetOffsetShellTest.testTopicPartitionsArg [2] Type=Raft-Isolated, MetadataVersion=4.0-IV0,Security=PLAINTEXT](https://ci-builds.apache.org/job/Kafka/job/kafka-pr/job/PR-16509/3/testReport/junit/org.apache.kafka.tools/GetOffsetShellTest/Build___JDK_8_and_Scala_2_12___testTopicPartitionsArg__2__Type_Raft_Isolated__MetadataVersion_4_0_IV0_Security_PLAINTEXT/)
[Build / JDK 8 and Scala 2.12 / org.apache.kafka.tools.MetadataQuorumCommandTest.testDescribeQuorumReplicationSuccessful [2] Type=Raft-Combined, MetadataVersion=4.0-IV0,Security=PLAINTEXT](https://ci-builds.apache.org/job/Kafka/job/kafka-pr/job/PR-16509/3/testReport/junit/org.apache.kafka.tools/MetadataQuorumCommandTest/Build___JDK_8_and_Scala_2_12___testDescribeQuorumReplicationSuccessful__2__Type_Raft_Combined__MetadataVersion_4_0_IV0_Security_PLAINTEXT/)

merged #16509 into trunk

Thanks @dujian0068 for the contribution!

@dujian0068 - can you also add an entry in the docs/streams/upgrade-guide.html with the changes your KIP introduced?

@dujian0068 - can you also add an entry in the docs/streams/upgrade-guide.html with the changes your KIP introduced?

@bbejeck Of course
I have submitted a new merge request：https://github.com/apache/kafka/pull/16709
Please help me review it
I considered updating this file before, but I saw that it was full of major updates, and my submission was a very small optimization, so I did not update this file. Can I ask which updates require updating this file?


fix swapped descriptions for output/processor plugins

Addresses https://github.com/influxdata/docs.influxdata.com/issues/2321
I noticed that the descriptions for output and processor plugins seemed swapped in a bunch of places.
This change makes sure that:

Output plugins are always described as "write metrics to various destinations."
Processor plugins are always described as "transform, decorate, and filter metrics."

Closing -- sorry, @kevin-cantwell, for missing the PR. I noticed the issue and fixed it while I was in the docs.


Provide a function with context for configuring MDX

I currently have an mdx-bundler wrapper function something like this:
    return await bundleMDXFile(filePath, {
      esbuildOptions: options => {
        options.platform = 'node'
        // Set the `outdir` to a public location for this bundle.
        options.outdir = `${process.cwd()}/public/img/${getSlug(filePath)}`
        options.loader = {
          ...options.loader,
          // Tell esbuild to use the `file` loader for pngs
          '.png': 'file',
          '.jpg': 'file'
        }
        // Set the public path to /img/about
        options.publicPath = `/img/${getSlug(filePath)}`

        // Set write to true so that esbuild will output the files.
        options.write = true

        return options
      },
      xdmOptions: options => {
        options.remarkPlugins = [
          ...(options.remarkPlugins ?? []),
          ...remarkPlugins
        ]
        options.rehypePlugins = [
          ...(options.rehypePlugins ?? []),
          ...rehypePlugins
        ]
        return options
      }
    })

You'll see that I'm able to use details from the context to configure esbuild for mdx-bundler. I use the filePath I've passed in to set an assets bundle path. I can also set the cwd to the folder of the file being bundled, allowing for easy linking of assets in the same folder as the MDX file (bundleMDXFile does it automatically). These options enable some nice functionality.
In contentlayers config I could imagine something like this:

 mdx: context => {
    return {
      cwd: path.dirname(context.filePath),
      remarkPlugins: [
        remarkGfm
      ],
      rehypePlugins: [
        [rehypePrism, { ignoreMissing: true }]
      ],
      esbuildOptions: options => {
        options.platform = 'node'
        // Set the `outdir` to a public location for this bundle.
        options.outdir = `${process.cwd()}/public/img/${getSlug(context.filepath)}`
        options.loader = {
          ...options.loader,
          // Tell esbuild to use the `file` loader for pngs
          '.png': 'file',
          '.jpg': 'file'
        }
        // Set the public path to /img/about
        options.publicPath = `/img/${getSlug(context.filepath)}`
        // Set write to true so that esbuild will output the files.
        options.write = true
        return options
      }
    }
}

@mshick thanks a lot for opening this issue. I'm curious to learn more about the use cases you have for this. Anything beyond #11?

Pretty much #11 — I'd like to be able keep my image assets next to my MDX files. Don't have any other great ideas right now!

Thanks for the update @mshick. I'll close this issue then in favour of #11. If you (or anyone else) has a use case for this original feature request, please comment here and we can re-open this issue. Thanks.

@schickling I've reviewed #11 and am actually using a similar approach already that works well enough, but doesn't address the capability I'd be able to get out of this feature, and which I think would be useful to many.
For instance, I could create a file structure like this:
-- content
---- blog-post
------ blog-post.mdx
------ cat-pic.png

Then, inside my post I could refer to my picture like so:
![A cat](./cat-pic.png)

Whereas currently, using an approach similar to what you've set up in #11 I'd have to do the following
![A cat](./blog-post/cat-pic.png)

It's a minor convenience, but would allow for some tidy file structures.
I think the proposed solution is (hopefully) low lift and opens up possibilities for other uses as well. I'm not sure how you'd surface this as a more proper contentlayer feature, but I could imagine a boolean along the lines of mdxSourceRelativeAssetPaths (quite a mouthful).
I'd be happy to take a stab at a PR for this if you're inclined.

This should be addressed with the 0.2.5 release. 🎉

@schickling I checked out the release notes and it's not clear to me whether this would handle the case I'm talking about. The issue is that the options (specifically the cwd) needs to be set to the current directory of the mdx file being processed. Unless contentlayer sets cwd itself then the only other way to handle this would be to take a function as an config option — similar to the new markdown option.
This allows you to use the mdx bundling behavior with markdown images and still have they show up in standard Markdown previews, e.g., GitHub's markdown preview. As-is, the only way to accomplish that is with a totally flat content directory which leads to some pretty gnarly results.

I'm not seeing how the 0.2.5 release addresses the problem @mshick mentioned. Currently there is no way to import components in .mdx files which are on the same level, only if the components are globally defined for the component returned by the useMDXComponent hook.

Resolved via #270. While the implementation is not as flexible as this issue requested, it does satisfy my primary objective of getting a relative cwd, and is generally easier to use.


9561-Backend

What is this implementation about? write a better commit message and description of the implementation. And then I  will do the review.


More allowed words

I added a few more words to the allowed list that triggered the bot in discord.

@eddiejaoude prefers that we don't use gendered pronouns. So everyone feels included and safe.

Can I get an example for exactly & basically? What issue number is this for?

Probably better to make another PR - 1 change at a time 👍 It makes it so we can find what change was made, how and why.

Ok i will make another PR with examples and it is for issue #365

That's my issue - I guess should re phase it, it's for words that should already be ignored but are not because they don't match the rules by the natural language processor.

Thank you for the Pull Request :+1:
closing PR.
RE:

@eddiejaoude prefers that we don't use gendered pronouns. So everyone feels included and safe.


Invalid discord invitation

It says that the link(in the issue template) has been expired or I have no permission to join the chat. Moreover, I've been randomly kicked out of the chat several times.

I updated the one here: https://discord.gg/sAgzNV27sA. See if you're using that invite code. It shouldn't be temporary.

Thanks @drunkirishcoder for finding those. They all should be hitting that link I posted.


Use fuzzy search to determine if a song has already been downloaded

Problem
This feature would help to manage an offline music library, even if using other scripts that name the files differently.
Solution
Implement fuzzy search using some python library

How will this work? Will the fuzzy search look in a single folder or will it be able to look recursively in subfolders too?

How will this work? Will the fuzzy search look in a single folder or will it be able to look recursively in subfolders too?

Looks like it will look only in a single folder

Would it be useful to look recursively?

Sure. If anyone wants to manage itslibrary with subfolders, it would be awesome to avoid duplicates


Clients Feature Branch

This pull request includes the search client plus some merge conflict resolutions from the recent changes. I'm going to be adding new clients over the coming days and will continue to push them to this branch, which I understand should update this PR. If I've done something incorrectly, please let me know, happy to revert or submit another way.

closing for now -- these will be brought over to @micro-stacks/query


Add on stopped working

Hi,
This was working very well, but stopped working on Friday morning (23/06/02). The log shows no errors, it just never reaches client ready status. I can see that node index is running and consuming resources on the host machine, but it just never finishes the start up.
I tried adding a second client, when scanning the QR code I got an error stating that the QR code in invalid, and I must ensure that it is from WA web, Desktop or other authorised app. Perhaps they changed something on their side which broke the add-on?
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[01:02:21] INFO: Installed custom component.
[2023-06-11T01:02:23.221] [INFO] default - Whatsapp Addon started.

I confirm. A similar problem with the inability to add a device via a qr code. HA 2023.6

Same here, whatsapp addon are not länger sending message, I reinsalled the addon as well, now not posible to connect via QR code, ( always get the message... please try later error occured )

a possible fix it to update the version on src/Defaults/baileys-version.json to "version": [2, 2323, 4] but i do not use HA supervised so cannot test this

I made a fork and did the change there - It seemed to have resolved the issue. The fork is https://github.com/ekkesa/ha-addons - I will delete the fork once this repo is updated.

Might have spoken to soon - It seems to resolve the QR code issue and the client not connecting, but it seems to fail on sending messages.

How can i install your fork in HA? i have it running now as addon but don't seem to be able to install it from your fork....

It's not the same for me. I get error when I scan qr...

Same method as the original - Just add my repo to HA and install. Remember to stop/remove the original one beforehand.

Hi I tried to run your fork but the QRcode still doesn't appear.
Can you help me?
Thanks


ISO C90 forbids mixed declarations and code -- worth fixing?

gcc 4.9.2 caught these warning under cygwin
marpa.w: In function ‘ahm_tag_safe’:
marpa.w:16116:1: warning: ISO C90 forbids mixed declarations and code [-Wpedantic]
marpa.w: In function ‘marpa_b_new’:
marpa.w:10478:1: warning: ISO C90 forbids mixed declarations and code [-Wpedantic]
marpa.w:10596:1: warning: ISO C90 forbids mixed declarations and code [-Wpedantic]

The can be fixed by dropping const and declaring as variables before the code. Is this worth doing or keeping const is more important?

I believe these warnings only occur when debugging is enabled, and I like them because they tell me that it's on -- the flags can be easy to miss.  It's possible that I might forget that debugging is on, but with all these warnings that's not likely.  [ At this point, because of the nature of the Libmarpa repo, at this point, I always run the tests with debugging on. ]

Ok, got it.


node link problem? How to find

In the operating system of WIN 10, starting two Nodes with the same cookie, I want to use the Nodes() api interface to get all nodes with the same cookie, but sometimes I can get it and sometimes I can't. Could you tell me how to query this problem?

Method Nodes() returns the list of connected nodes

Nodes() returns empty, so I wonder if I can drill down to the bottom to get a clue？

It returns an empty list even being connected with the other nodes, right? If so, could you please share the way how it can be reproduced?

``func main() {
StartGateNode(os.Args[1], "abc")
}
func StartGateNode(nodeName string, cookie string) {
gateNode, err := ergo.StartNode(nodeName, cookie, node.Options{})
if err != nil {
slog.Fatal("start gate node error:%v", err)
}
slog.Info("node name:%s, cookie:%s, start ok", gateNode.Name(), cookie)
slog.Info("nodes node :%v", gateNode.Nodes())
common.Node.Wait()
}

[2023-08-11T00:18:18.684] INFO gateapp/main.go:21 node<EMAIL_ADDRESS>cookie:abc, start ok
[2023-08-11T00:18:18.698] INFO gateapp/main.go:22 nodes node :[]

Oh, my mistake, I misunderstood, sometimes I just sent a message and then the link was on, and I did not manually execute connect, which is always understood as automatic connection by default


Catastrophic forgetting occur when I perform continued pre-training on Llama 3

My question
Why does catastrophic forgetting occur when I perform continued pre-training on Llama 3? I used open source data from BookCorpus, iterated 100,000 steps, and then after testing the trained model with litgpt chat, the output becomes chaotic, and the original knowledge of Llama 3 is forgotten. However, there was no problem when I iterated 200 steps. Is this a bug? Below are my commands and screenshots of the data.
This problem has troubled me for three weeks, and I have tried many methods but failed to solve it. I am eagerly looking forward to your feedback.  Thanks!
My commands
litgpt pretrain Meta-Llama-3-8B-Instruct
--tokenizer_dir checkpoints/meta-llama/Meta-Llama-3-8B-Instruct
--initial_checkpoint_dir checkpoints/meta-llama/Meta-Llama-3-8B-Instruct
--data TextFiles
--data.train_data_path "/workspace/pretrain/custom_texts"
--train.max_tokens<PHONE_NUMBER>
--train.max_seq_length 2048
--train.lr_warmup_steps 30000
--train.min_lr 4e-08
--train.global_batch_size 8
--train.micro_batch_size 1
--train.log_interval 10
--train.save_interval 100
--eval.interval 50
--eval.final_validation true
--out_dir out/custom-model
My data

My litgpt chat result
When testing with litgpt chat, for example, when the prompt inputs "hi," it starts to generate nonsense continuously and non-stop.

Does the format of continued pre-training have to be TextFiles? Can't it be in json format?

Thanks for the informative post and showing these hands-on examples, that's very helpful to see. Regarding catastrophic forgetting, what may help is adding ~5% of the original training data back into the continued pretraining dataset. There was a recent paper that looked into that. I've written a high-level overview here: https://magazine.sebastianraschka.com/i/142924793/simple-and-scalable-strategies-to-continually-pre-train-large-language-models

Does the format of continued pre-training have to be TextFiles? Can't it be in json format?

That's just the one I implemented because I thought it might be easier for people (I assume more people know what a text file is compared to JSON). But if you are up to it, please feel free to contribute a JSON dataset dataset approach analogous to the TextFiles approach -- that'd be welcome. (PS: We actually do support JSON for instruction finetuning)

@rasbt Thank you very much for your detailed explanation. I will study the article carefully now. As for the raw data of llama3, I actually don't know where to get it. I have been searching for it for a long time. Thanks for your answer.

Yes, getting the original data for Llama 3 is impossible for non Meta people, unfortunately. But I think it's safe to assume that the dataset more or less overlaps with public datasets like RefinedWeb.

@rasbt Thanks! I'll download RefinedWeb to test its effectiveness and observe whether training solely on RefinedWeb will result in catastrophic forgetting.

Good idea, this would be a good control experiment.

Thanks！

What if instead of continued pretrained do a fine-tuning with LoRA.
I believe that there is a paper that LoRA forgets less (I saw Sebastian's post on LinkedIn about it). Though in the paper they compared LoRA and a proper full fine-tuning, I think that there is no reason to at least try it also for pretraining (basically just a different naming).

@Andrei-Aksionov Indeed, I agree that the LoRA fine-tuning approach can definitely be applied to continued pre-training. I will carefully read this paper. Thanks！

In addition, you can take a look at the Studio template.
There @awaelchli discussed a topic of learning rate and forgetting (Warm up chapter).

@Andrei-Aksionov Okay, thank you for sharing. I will go to Studio template to learn more.


Event header in drawer can have overlapped information

The image background can overlap event information in the header. Instead, a panel should be shown below the header image containing basic info. Panel color should be generated using Android Palette

Are you working on it? @iamareebjamal

No

taking this up.


TypeScript definitions - help wanted

Greetings to all.
I am currently working on producing TypeScript definitions for this library to be added to DefinitelyTypes.
https://github.com/m-gallesio/DefinitelyTyped/blob/master/types/d3-flextree/index.d.ts
If anyone is interested, I would appreciate this to be tested by someone who has direct experience with this library (I am doing this mostly to update type definitions for https://github.com/bumbeishvili/org-chart which uses this library).
Regards.

This is now done and published.
Since noone commented, I will be open to further inputs if anyone has problems.


fix: fix broken links in the “See Also” section

The links in the “See Also” section on topic pages lead to a 404. This is very annoying since RDocumentation is often the first result for searches related to R packages. The missing page is:
/link/:topic?package=:package&version=:version
And it should point to:
/packages/:package/versions/:version/topics/:topic
However, It can’t be simply fixed by redirecting to the correct URL because the function names in the “See Also” section don’t always map directly to topic pages. There is an API endpoint with the same path that resolves the correct topic page and fallbacks with a search results:
[API_URL]/link/:topic?package=:package&version=:version
The problem is, it redirects to a page in the API domain, instead of returning JSON with a correct relative URL.
[API_URL]/packages/:package/versions/:version/topics/:topic
The solution: create the link page and fetch the corresponding API endpoint, get the URL it redirects to from response.url, strip the domain name and redirect.
This can be improved further by adding an API endpoint that returns the correct URL or by resolving the URL when the link is created thus saving on two redirects.
This solves #65 and #74.

thank you for this fix hope it'll be merged soon

Hi, @ncarchedi, @ddmkr can I expect this to be merged? It's a non breaking change that greatly improves the user experience.

@ztsorojev ? I saw you merged something recently, is there a reason not to do this? Usability is seriously impaired.

@sin Thank you for your contribution!! 🙏  Sorry that I replied so late! And thanks @ariliso for tagging me!
I tested your code, it's working so I will merge it now! It doesn't solve all the links from #74 unfortunately, but it's already a great improvement. I will look more into why other links are broken.

@ztsorojev Thank you! I think it also fixed the links in the body of text.
I've found out that we can sanitize the data to make it work more often.
For example, this link doesn't work: /link/all.equal()?package=dplyr
But this works: /link/all.equal?package=dplyr
Dropping the brackets from the function name would fix a lot of links. I'll create another PR shortly.


TEST - Metadata store: Plugin - Argo - Integration Tests

Int Tests for #125
2 branches to this.

WorkflowExecutor integration tests which test the metadata consumption on the TaskUpdateEvent
TaskExecutor integration tests to check that the metadata.json is included in a TaskUpdateEvent after consuming a TaskCallbackEvent

@elleyouseewhy can we close this as complete?


com.documents4j.throwables.ConversionInputException

Hi Raphw,
I'm encountering an error linked to the converter used when trying to convert file from XLS to MHTML.
For other type of conversion, I don't have any issue using your library.
Here the example document used for conversion :
CONVERTING :
C:\Users\eantlal\workspace\ExcelConverter\Temp\081N1_3.32081N1_1.42081N1_1-FP-22052017.xls
TO
C:\Users\eantlal\workspace\ExcelConverter\HTML\081N1_3.32081N1_1.42081N1_1-FP-22052017\081N1_3.32081N1_1.42081N1_1-FP-22052017.mhtml
Exception raised :

``Exception in thread "Thread-1" com.documents4j.throwables.ConversionInputException: No converter for conversion of application/vnd.ms-excel to application/x-mimearchive available

Stack trace :
at com.documents4j.conversion.ConverterRegistry.lookup(ConverterRegistry.java:65)	at com.documents4j.conversion.DefaultConversionManager.startConversion(DefaultConversionManager.java:30)
at com.documents4j.job.LocalFutureWrappingPriorityFuture.startConversion(LocalFutureWrappingPriorityFuture.java:50)
at com.documents4j.job.LocalFutureWrappingPriorityFuture.startConversion(LocalFutureWrappingPriorityFuture.java:11)

at com.documents4j.job.AbstractFutureWrappingPriorityFuture.run(AbstractFutureWrappingPriorityFuture.java:70)	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

Log from your library :
mai 30, 2017 10:58:04 AM org.zeroturnaround.exec.stream.slf4j.Slf4jInfoOutputStream processLine
INFO: Microsoft (R) Windows Script Host Version 5.8
mai 30, 2017 10:58:04 AM org.zeroturnaround.exec.stream.slf4j.Slf4jInfoOutputStream processLine
INFO: Copyright (C) Microsoft Corporation. All rights reserved.
mai 30, 2017 10:58:04 AM org.zeroturnaround.exec.stream.slf4j.Slf4jInfoOutputStream processLine
INFO:
mai 30, 2017 10:58:04 AM com.documents4j.conversion.msoffice.MicrosoftWordBridge startUp
INFO: From-Microsoft-Word-Converter was started successfully
mai 30, 2017 10:58:04 AM org.zeroturnaround.exec.stream.slf4j.Slf4jInfoOutputStream processLine
INFO: Microsoft (R) Windows Script Host Version 5.8
mai 30, 2017 10:58:04 AM org.zeroturnaround.exec.stream.slf4j.Slf4jInfoOutputStream processLine
INFO: Copyright (C) Microsoft Corporation. All rights reserved.
mai 30, 2017 10:58:04 AM org.zeroturnaround.exec.stream.slf4j.Slf4jInfoOutputStream processLine
INFO:
mai 30, 2017 10:58:04 AM com.documents4j.conversion.msoffice.MicrosoftExcelBridge startUp
INFO: From-Microsoft-Excel-Converter was started successfully
mai 30, 2017 10:58:04 AM com.documents4j.job.LocalConverter <init>
INFO: The documents4j local converter has started successfully

Code used :
File excelFile = new File(inputFile.getAbsolutePath()), htmlFile = new File(outputFile.getAbsolutePath());

htmlFile.getParentFile().mkdirs();

        	IConverter converterTest =  LocalConverter.builder()
                    .baseFolder(new File("C:\\Data Sync\\converter"))
                    .workerPool(20, 25, 2, TimeUnit.SECONDS)
                    .processTimeout(5, TimeUnit.SECONDS)
                    .build();

        	Boolean conversion = converterTest
        	                                .convert(excelFile).as(DocumentType.XLS)
        	                                .to(htmlFile).as(DocumentType.MHTML)
        	                                .prioritizeWith(1000) // optional
        	                                .execute();

I have OpenOffice/LibreOffice and Microsoft Office installed, and none of them could be use to convert xls to mhtml ? What software should I use to convert document ?
Best regards,
Anton L.

Can you convert an excel file to another format? I do not think that I have currently an html converter implemented. You can try to add that to the MS Excel bridge and send a PR.

Hi,
Indeed I can convert an excel file to xml, PDF, etc.
I though that your library made the link between any java application, and a third parties software.
This third parties software (MicrosoftExcelBridge in my case) would than make the conversion.
Meaning, that any export/save format from the third parties software would be available for conversion.
I suppose you had to add a layer between them, and it's why the MHTML format is not supported by the microsoft bridge ?
Anyhow, thank for your support.
Best regards,
Anton L.

There is probably an easy fix to this. Have a look at https://github.com/documents4j/documents4j/blob/master/documents4j-transformer-msoffice/documents4j-transformer-msoffice-excel/src/main/java/com/documents4j/conversion/msoffice/MicrosoftExcelBridge.java, you might just need to add the annotation value for mhtml. Additionally, you would need to add the format here: https://github.com/documents4j/documents4j/blob/master/documents4j-transformer-msoffice/documents4j-transformer-msoffice-excel/src/main/java/com/documents4j/conversion/msoffice/MicrosoftExcelFormat.java
If you can make it work, send me a PR and I will merge it.


Updates docs of AABB and Plane

AABB

Describes get_area() as returning the volume instead of area.
Adds description of relationship between end and the other two properties.
Makes the is_equal_approx() function reference clickable.

Plane

Adds parameter description of Plane(a, b, c, d).
Metions how the three points of Plane(v1, v2, v3) should be ordered.
Adds description for the five properties.

Thanks!


chore: bdd-sbhg-1582901802 to 0.0.1

chore: Promote bdd-sbhg-1582901802 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


ts-loader与arco-plugins/webpack-react冲突, 导致ts错误报错

[ ] I'm sure this does not appear in the issue list of the repository

Basic Info

Package Name And Version<EMAIL_ADDRESS>Browser: chrome96.0.4664.110
Reproduction Link: https://arco.design/react/docs/start

What is expected?
无法使用codepen配置这个插件复现问题, 希望解决

你好，希望可以建一个 github 仓库来复现这个问题，我们需要看一下具体配置来排查问题


Configured Server port not used in client config

change
Endpoint = $SERVER_PUB_IP:1194
to
Endpoint = $SERVER_PUB_IP:$SERVER_PORT

🤦♂ Thanks!


Support Observables and RxJS

It's just about convinience.
I want tabris objects to provide events as observables, like
widget.onFooChanged.subscribe(...)
and support RxJS operators like
widget.onFooChanged.pipe(...).
I also would like to allow setting ovservables and promises directly on properties, roughly like this:
FooWidget({prop: {async: promiseOrObservables}})
If you have other ideas I'd like to hear them.

for now i think that your ideas is enough, if i've any other idea i will let you know.

In 3.7 an Observable implementation is provided and used by the event system. The issue will not be closed yet since we also want to be able to consume observables.


[Webpack 5] Module Federation - Re-exports imported in remote crash application with no error message.

Bug report

What is the current behavior?
Bi-directional hosts. Exposed file is a re-export. Compilation does not throw an error. But application won't load.
Context

app1 exposes indexExternal.js as ./hostExports which re-exports some modules from exports.js which exports everything from deps.js and effects.js
app2 exposes demo-exports.js as ./remoteExports which is just a constant
Search for (1) and (2) in the code.

(1) - here we import from app2/remoteExports and it crashes the app with no error. The import is made in a file that is later re-exported. effects.js is re-exported in exports.js to indexExternal, where we only pick-up some of the exports. This is the file that is exposed from app1
(2) - here we import from app2/remoteExports in app1. This works, the file is not re-exported or anything similar.

If the current behavior is a bug, please provide the steps to reproduce.

Clone this repo
Start bi-directional hosts example. (For detailed explanations see Readme that explains the bug)
Search for (1) and un-comment the code underneath it. App no longer loads, no compilation error thrown.
Search for (2) and un-comment the code underneath it. App loads normally.

What is the expected behavior?
Regardless of where the import from the remote module to host is made, it should not crash the app or it should have some informative message.

Other relevant information:
webpack version<EMAIL_ADDRESS>Node.js version: v10.15.3
Operating System: Mac OS 10.14.6 Mojave
Additional tools:

Yes, this seem to be a bug. The container awaiting each other initialization during initialization. This creates a circular promise which never completes...

Since an image is worth a 1000 words, used the federation-dashboard to illustrate the dependencies in this issue.

I'd like to give this a go. But really no clue where to start with this? Any hypotheses for starting points on this ?
Not really familiar with the API or anything. Some hints would help.
I'll start diving into this myself in the meantime.

should be fixed

@mihaisavezi feel free to feedback


Removes duplication of devfile parsing and validation

What type of PR is this?
/kind cleanup
/kind code-refactoring
What does this PR do / why we need it:
Parsing and Validation of devfile already happens in "Complete"
function.
Which issue(s) this PR fixes:
Fixes NA
Part of #4298
PR acceptance criteria:

[ ] Unit test

[ ] Integration test

[ ] Documentation

[x] I have read the test guidelines

How to test changes / Special notes to the reviewer:
Tests should pass

/lgtm

/hold
Some genuine failure with odo create --now.

Any update on this PR?

Any update on this PR?

/close

/close


It is not clear how I can use the Windows ssh instead of openssh

In the readme it says: "If you are using the Windows-native version of OpenSSH that ships with Windows 10 1803 or newer, ", but it is not clear how I choose this.

It ships pre-installed with newer versions of windows, so it's simply a case of just running the executable and enabling/starting the OpenSSH Agent windows service.


jackett: 0.20.2175 -> 0.20.2218

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for jackett is: "API Support for your favorite torrent trackers"
meta.homepage for jackett is: "https://github.com/Jackett/Jackett/"
meta.changelog for jackett is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.20.2176 with grep in /nix/store/v2pxa05rgmfwib40y2n6nz4a2vs29d6x-jackett-0.20.2176
found 0.20.2176 in filename of file in /nix/store/v2pxa05rgmfwib40y2n6nz4a2vs29d6x-jackett-0.20.2176

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
jackett

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/v2pxa05rgmfwib40y2n6nz4a2vs29d6x-jackett-0.20.2176 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A jackett https://github.com/r-ryantm/nixpkgs/archive/71078ab3fcd4c01b6e213277f88936cfbf1db89e.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/v2pxa05rgmfwib40y2n6nz4a2vs29d6x-jackett-0.20.2176
ls -la /nix/store/v2pxa05rgmfwib40y2n6nz4a2vs29d6x-jackett-0.20.2176/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

jackett

Maintainer pings
cc @edwtjo @nyanloutre @purcell for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for jackett is: "API Support for your favorite torrent trackers"
meta.homepage for jackett is: "https://github.com/Jackett/Jackett/"
meta.changelog for jackett is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.20.2180 with grep in /nix/store/m02g8jazs7lncz4y5pcf4qpsa5mg136a-jackett-0.20.2180
found 0.20.2180 in filename of file in /nix/store/m02g8jazs7lncz4y5pcf4qpsa5mg136a-jackett-0.20.2180

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
jackett

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/m02g8jazs7lncz4y5pcf4qpsa5mg136a-jackett-0.20.2180 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A jackett https://github.com/r-ryantm/nixpkgs/archive/e5b3b54d2bca3b6c05a5ce5a2c74e330977bf2f7.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/m02g8jazs7lncz4y5pcf4qpsa5mg136a-jackett-0.20.2180
ls -la /nix/store/m02g8jazs7lncz4y5pcf4qpsa5mg136a-jackett-0.20.2180/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

jackett

Maintainer pings
cc @edwtjo @nyanloutre @purcell for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for jackett is: "API Support for your favorite torrent trackers"
meta.homepage for jackett is: "https://github.com/Jackett/Jackett/"
meta.changelog for jackett is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.20.2182 with grep in /nix/store/nim3ypch371liwqw297fhpmhm4zcfrqq-jackett-0.20.2182
found 0.20.2182 in filename of file in /nix/store/nim3ypch371liwqw297fhpmhm4zcfrqq-jackett-0.20.2182

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
jackett

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/nim3ypch371liwqw297fhpmhm4zcfrqq-jackett-0.20.2182 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A jackett https://github.com/r-ryantm/nixpkgs/archive/95810728f91ae64ab1c6e5493c4402e436c23394.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/nim3ypch371liwqw297fhpmhm4zcfrqq-jackett-0.20.2182
ls -la /nix/store/nim3ypch371liwqw297fhpmhm4zcfrqq-jackett-0.20.2182/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

jackett

Maintainer pings
cc @edwtjo @nyanloutre @purcell for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for jackett is: "API Support for your favorite torrent trackers"
meta.homepage for jackett is: "https://github.com/Jackett/Jackett/"
meta.changelog for jackett is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.20.2186 with grep in /nix/store/1l2271bz0504825z1dm8bsnvarsfpwr9-jackett-0.20.2186
found 0.20.2186 in filename of file in /nix/store/1l2271bz0504825z1dm8bsnvarsfpwr9-jackett-0.20.2186

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
jackett

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/1l2271bz0504825z1dm8bsnvarsfpwr9-jackett-0.20.2186 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A jackett https://github.com/r-ryantm/nixpkgs/archive/892669d0e1d7ffe441c01fa69c969aee0a99d8b0.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1l2271bz0504825z1dm8bsnvarsfpwr9-jackett-0.20.2186
ls -la /nix/store/1l2271bz0504825z1dm8bsnvarsfpwr9-jackett-0.20.2186/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

jackett

Maintainer pings
cc @edwtjo @nyanloutre @purcell for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for jackett is: "API Support for your favorite torrent trackers"
meta.homepage for jackett is: "https://github.com/Jackett/Jackett/"
meta.changelog for jackett is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.20.2189 with grep in /nix/store/xr0lkmjyszrcflrw2jym86y3fxwb8yfs-jackett-0.20.2189
found 0.20.2189 in filename of file in /nix/store/xr0lkmjyszrcflrw2jym86y3fxwb8yfs-jackett-0.20.2189

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
jackett

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/xr0lkmjyszrcflrw2jym86y3fxwb8yfs-jackett-0.20.2189 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A jackett https://github.com/r-ryantm/nixpkgs/archive/c2be6f730e534247451c0cf6d4615aeb9b84902b.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/xr0lkmjyszrcflrw2jym86y3fxwb8yfs-jackett-0.20.2189
ls -la /nix/store/xr0lkmjyszrcflrw2jym86y3fxwb8yfs-jackett-0.20.2189/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

jackett

Maintainer pings
cc @edwtjo @nyanloutre @purcell for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for jackett is: "API Support for your favorite torrent trackers"
meta.homepage for jackett is: "https://github.com/Jackett/Jackett/"
meta.changelog for jackett is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.20.2203 with grep in /nix/store/4n5r9g7jkg61mrc4ymjjmhvw6a7mr51f-jackett-0.20.2203
found 0.20.2203 in filename of file in /nix/store/4n5r9g7jkg61mrc4ymjjmhvw6a7mr51f-jackett-0.20.2203

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
jackett

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/4n5r9g7jkg61mrc4ymjjmhvw6a7mr51f-jackett-0.20.2203 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A jackett https://github.com/r-ryantm/nixpkgs/archive/317cfd7ad427eaced36445e4c5d785b8a8f50d61.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/4n5r9g7jkg61mrc4ymjjmhvw6a7mr51f-jackett-0.20.2203
ls -la /nix/store/4n5r9g7jkg61mrc4ymjjmhvw6a7mr51f-jackett-0.20.2203/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

jackett

Maintainer pings
cc @edwtjo @nyanloutre @purcell for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for jackett is: "API Support for your favorite torrent trackers"
meta.homepage for jackett is: "https://github.com/Jackett/Jackett/"
meta.changelog for jackett is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.20.2210 with grep in /nix/store/yn8ib27m5qiac8nmxa8sp138p6qs1jvc-jackett-0.20.2210
found 0.20.2210 in filename of file in /nix/store/yn8ib27m5qiac8nmxa8sp138p6qs1jvc-jackett-0.20.2210

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
jackett

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/yn8ib27m5qiac8nmxa8sp138p6qs1jvc-jackett-0.20.2210 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A jackett https://github.com/r-ryantm/nixpkgs/archive/4819ae354caf3c2033cbf2b6235d53c8e16a2873.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/yn8ib27m5qiac8nmxa8sp138p6qs1jvc-jackett-0.20.2210
ls -la /nix/store/yn8ib27m5qiac8nmxa8sp138p6qs1jvc-jackett-0.20.2210/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

jackett

Maintainer pings
cc @edwtjo @nyanloutre @purcell for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for jackett is: "API Support for your favorite torrent trackers"
meta.homepage for jackett is: "https://github.com/Jackett/Jackett/"
meta.changelog for jackett is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.20.2218 with grep in /nix/store/m0j86qvh7wadqc8cbn39ybrca56gf0d4-jackett-0.20.2218
found 0.20.2218 in filename of file in /nix/store/m0j86qvh7wadqc8cbn39ybrca56gf0d4-jackett-0.20.2218

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
jackett

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/m0j86qvh7wadqc8cbn39ybrca56gf0d4-jackett-0.20.2218 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A jackett https://github.com/r-ryantm/nixpkgs/archive/af0eb793b82027341f72e7c501e6972c1456c8b9.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/m0j86qvh7wadqc8cbn39ybrca56gf0d4-jackett-0.20.2218
ls -la /nix/store/m0j86qvh7wadqc8cbn39ybrca56gf0d4-jackett-0.20.2218/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

jackett

Maintainer pings
cc @edwtjo @nyanloutre @purcell for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for jackett is: "API Support for your favorite torrent trackers"
meta.homepage for jackett is: "https://github.com/Jackett/Jackett/"
meta.changelog for jackett is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.20.2220 with grep in /nix/store/9q86649g1vzkrcmq0cb21ddvxhddym8a-jackett-0.20.2220
found 0.20.2220 in filename of file in /nix/store/9q86649g1vzkrcmq0cb21ddvxhddym8a-jackett-0.20.2220

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
jackett

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/9q86649g1vzkrcmq0cb21ddvxhddym8a-jackett-0.20.2220 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A jackett https://github.com/r-ryantm/nixpkgs/archive/92919e3f35cd3449aab8aa97468347772afc31f4.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/9q86649g1vzkrcmq0cb21ddvxhddym8a-jackett-0.20.2220
ls -la /nix/store/9q86649g1vzkrcmq0cb21ddvxhddym8a-jackett-0.20.2220/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

jackett

Maintainer pings
cc @edwtjo @nyanloutre @purcell for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for jackett is: "API Support for your favorite torrent trackers"
meta.homepage for jackett is: "https://github.com/Jackett/Jackett/"
meta.changelog for jackett is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.20.2225 with grep in /nix/store/4ymr5wb58g42hz16p9211mknh6m6ig4b-jackett-0.20.2225
found 0.20.2225 in filename of file in /nix/store/4ymr5wb58g42hz16p9211mknh6m6ig4b-jackett-0.20.2225

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
jackett

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/4ymr5wb58g42hz16p9211mknh6m6ig4b-jackett-0.20.2225 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A jackett https://github.com/r-ryantm/nixpkgs/archive/544af65981cb2d7609f8ac585258e55c19918c16.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/4ymr5wb58g42hz16p9211mknh6m6ig4b-jackett-0.20.2225
ls -la /nix/store/4ymr5wb58g42hz16p9211mknh6m6ig4b-jackett-0.20.2225/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

jackett

Maintainer pings
cc @edwtjo @nyanloutre @purcell for testing.


[WFCORE-4355] Introduce a simple event logging API.

JIRA: https://issues.jboss.org/browse/WFCORE-4355
Proposal: https://github.com/wildfly/wildfly-proposals/pull/181
Introduces a simple event logging API into WildFly Core. This will be able to be used for things like access logging, security audit logging, EJB access logging and management audit logging. The purpose of this API for now is to simply have a unified way of formatting a JSON message and writing to stdout.

Core - Full Integration Build 8400 outcome was FAILURE using a merge of f657673746a918983aa61b8257b2cb32403ac0f6
Summary: Tests failed: 1 (1 new), passed: 4824, ignored: 133 Build time: 01:51:25
Failed tests
org.jboss.as.test.integration.messaging.mgmt.CoreQueueManagementTestCase.testChangeMessagePriority: java.lang.IllegalArgumentException
	at org.jboss.dmr.ModelValue.asLong(ModelValue.java:53)
	at org.jboss.dmr.ModelNode.asLong(ModelNode.java:250)
	at org.jboss.as.test.integration.messaging.mgmt.CoreQueueManagementTestCase.findMessageID(CoreQueueManagementTestCase.java:278)
	at org.jboss.as.test.integration.messaging.mgmt.CoreQueueManagementTestCase.testChangeMessagePriority(CoreQueueManagementTestCase.java:322)

I've added the Feature label, however this is an internal only feature and not subject to the full feature process. Though I did create a proposal for discussion purposes.

Core - Full Integration Build 8455 outcome was FAILURE using a merge of 5f29bd3b49a467e9dee8255522de7aca6ccce561
Summary: Tests failed: 1 (1 new), passed: 4842, ignored: 133 Build time: 02:08:16
Failed tests
org.jboss.as.test.layers.LayersTestCase.testServlet: java.lang.Exception: Some unreferenced modules are un-expected [org.wildfly.event.logger]
	at org.jboss.as.test.layers.LayersTest.test(LayersTest.java:100)
	at org.jboss.as.test.layers.LayersTestCase.testServlet(LayersTestCase.java:83)

Core - Full Integration Build 8457 outcome was FAILURE using a merge of 562050a8e0475fae8d1e936ab2322741fd154eff
Summary: Tests failed: 1, passed: 4842, ignored: 133 Build time: 03:25:26
Failed tests
org.jboss.as.test.layers.LayersTestCase.testServlet: java.lang.Exception: Some unreferenced modules are un-expected [org.wildfly.event.logger]
	at org.jboss.as.test.layers.LayersTest.test(LayersTest.java:100)
	at org.jboss.as.test.layers.LayersTestCase.testServlet(LayersTestCase.java:83)

https://github.com/wildfly/wildfly/pull/12205 should fix the test issues with the full integration tests.

Core - Full Integration Build 8476 outcome was FAILURE using a merge of 24f203f98fafc58eb5d86b00e6f1371f35ca576f
Summary: Tests failed: 1, passed: 4850, ignored: 134 Build time: 02:54:59
Failed tests
org.jboss.as.test.layers.LayersTestCase.testServlet: java.lang.Exception: Some unreferenced modules are un-expected [org.wildfly.event.logger]
	at org.jboss.as.test.layers.LayersTest.test(LayersTest.java:100)
	at org.jboss.as.test.layers.LayersTestCase.testServlet(LayersTestCase.java:83)

Core - Full Integration Build 8491 outcome was FAILURE using a merge of 0ef97ad1763b8d7d955ad999c551a916d1edfd2e
Summary: Tests failed: 1, passed: 4851, ignored: 134 Build time: 02:04:24
Failed tests
org.jboss.as.test.layers.LayersTestCase.testServlet: java.lang.Exception: Some unreferenced modules are un-expected [org.wildfly.event.logger]
	at org.jboss.as.test.layers.LayersTest.test(LayersTest.java:100)
	at org.jboss.as.test.layers.LayersTestCase.testServlet(LayersTestCase.java:83)

Core - Full Integration Build 8492 outcome was FAILURE using a merge of 0ef97ad1763b8d7d955ad999c551a916d1edfd2e
Summary: Tests failed: 1, passed: 4851, ignored: 134 Build time: 02:01:06
Failed tests
org.jboss.as.test.layers.LayersTestCase.testServlet: java.lang.Exception: Some unreferenced modules are un-expected [org.wildfly.event.logger]
	at org.jboss.as.test.layers.LayersTest.test(LayersTest.java:100)
	at org.jboss.as.test.layers.LayersTestCase.testServlet(LayersTestCase.java:83)

Core - Full Integration Build 8503 outcome was FAILURE using a merge of c9cd980309f3351eada286d536ff700c8801774e
Summary: Tests failed: 1, passed: 4851, ignored: 134 Build time: 01:56:41
Failed tests
org.jboss.as.test.layers.LayersTestCase.testServlet: java.lang.Exception: Some unreferenced modules are un-expected [org.wildfly.event.logger]
	at org.jboss.as.test.layers.LayersTest.test(LayersTest.java:100)
	at org.jboss.as.test.layers.LayersTestCase.testServlet(LayersTestCase.java:83)

The org.wildfly.core:wildfly-event-logger should be specified in core-feature-pack/src/license/core-feature-pack-licenses.xml

@jmesnil done. I only added the ASL license as it's all new code. If the LGPL license needs to be there too please just let me know.

Dependency Tree Analyzer Output:
New Dependencies:

org.wildfly.core:wildfly-event-logger:jar:9.0.0.Beta3-SNAPSHOT:compile

@jmesnil Possibly source is a bad name. It is currently more like a logging category so more like the kind or type. For example with the access logging I'm working the source is currently "web-access". So essentially the source is what is used to distinguish different log types.
I'm definitely open to different names as well. I originally had eventId, but that seemed like something that implied it should be unique. Maybe type is better though. I attempted to find a common type of name among the various log aggregators with little luck other than source seemed to be used quite frequently :)

Core - Full Integration Build 8563 outcome was UNKNOWN using a merge of f2af9777cde8590baa53ec15f2faa951e81b3191
Summary: Canceled (Error while applying patch; cannot find commit e1a4df1f82585317cf19d2d064bab3c9b7e5ec6f in the https://github.com/wildfly/wildfly-core.git repository, possible reason: refs/pull/3700/merge branch was updated and the commit selected for the ... Build time: 00:00:19

retest this please

@jamezp Naming is hard and I can see arguments both for and against source, kind and type.
The important thing is the actual use of this field.
AIUI, if I want to aggregate all access logs, I need to have a common json field I can specify and source is likely this field.
I think the doc should provide an example of good practices.
The doc should be updated to provide this use case by using a sensible source value (e.g. access-log) that can be aggregated instead of a generic non-descriptive one like my-event.

@jmesnil I've updated the README doc. Hopefully it makes it more clear now and if not please let me know. I'll be happy to add more content or edit content if needed.

re the deps-changed flag, the only change is a new internal dependency to the org.wildfly.core:wildfly-event-logger maven module.

Core - Full Integration Build 8574 outcome was UNKNOWN using a merge of b86359d861e7d36d8ba419fb3d7da11bde640934
Summary: Canceled (Tests passed: 4808, ignored: 133; exit code 143 (Step: Build & test full (Maven)) (new)) Build time: 02:20:25


NSMgr: manage loop crashes and node decomissioning

Currently in NSM, nothing is specified about how to manage a loop crash of nsmd :

do we unregister endpoints?
do we recreate crossconnects of the client?
do we attach datapath/endpoint containers to a alternative nsmgr?

The same kind of question may raise for a k8s node decommissioning, except clients located on that node will be restarted on a node with a nsmgr alive.
In case of a single crash of the nsmgr pod, the current implementation should handle the case gracefully, and k8s cache informer should report a UPDATE resource message with the new URL of the nsmgr pod.

I would suggest the first question is: how do we detect a crash loop?

@matrohon Is this still an ongoing concern?

I've not see this since July. Let's close and re-open if needed.


Nav menu shows "Home" on all pages on mobile

Another small issue that I noticed was that the Nav menu always shows "Home", rather than the name of the current page (when on mobile). Also there is no chevron to indicate that the link is actually a dropdown menu.

Proposed Solution
Adjust the Nav menu to replicate the behavior of the original Svelte site.

I'm happy to fix this also.

Thanks! A fix would be great.


Path can be a typo

Link: https://github.com/secure-device-onboard/pri-fidoiot/blame/master/README.md
•	Line No 147 , 148 : has path which could be a typo “Copy /demo//java.security to /etc/java-11-openjdk/security/” and “Copy /demo//pkcs11.cfg to /etc/softhsm/”

Resolved in PR#72


Create a main.rb file

in this branch tasks were done:

create main.rb
create app.rb

Implement startup actions:

Present the user with a list of options to perform.
Let users choose an option.
If needed, ask for parameters for the option.
Have a way to quit the app.

Your code is organized


Video sharing via instagram will be upside down on Android.

Steps to reproduce

Share a video via instagram

Expected behaviour
A perfect video.
Actual behaviour
The video will be upside down
Environment

**React Native version0.59:
React Native platform + platform version: Android 10

react-native-share
**Version1.2.1: npm version or "master"
When I share a video via Instagram. It will look like that.

But when I click "Next" the video will be upside down. Like that :

How can I fix it now?

This usually happens on Emulators.
Try running on a real device.


Android successFunc doesn't work properly if cancel

Android shareWithOptions successFunc return previous chosen app even through I choose cancel and without choose any app.
It work properly for first open the app choose cancel without choosing any app then the return is work properly.
Step to repeat the issue.

Use sharewithoptions and choose any app to share, example, I choose Whatsapp now and share.
Then I try to use sharewithoptions function again, without choose any app, then cancel the share option sheet, but it return whatsapp.

@dodomui, I've looked into similar things like this in the past, but stepping through the code execution for this one specifically, I can see the response object you're looking at with the completed and app properties comes from the callbackFromNative deep inside cordova.js, it's not something that this (or any other) plugin has any control over.
as such, I suggest you log an issue in the cordova-android repo for this one.

with that said, @EddyVerbruggen do you perhaps know of any other way that we can tell if the "share" action we initiated was completed or cancelled?


Add projects to schema

Pull these from the master smartsheet.
Confirm with Saskia and Shelby before merging.

@dyf Can you add some additional info?

Closing this issue since we no longer will be maintaining a list of project names in data-schema


Remove reply content in removeArticleReply.js script

Per 20210428 discussion, since we backup original reply text in the spreadsheet, we can consider removing spammer's reply text entirely.
We can modify removeArticleReply.js so that it optionally take a CLI argument that replaces the reply text with specified text. We can provide link to the spreadsheet or takedown note in the replaced text.

working on it

working on it

https://github.com/cofacts/rumors-api/pull/328


give ArbitraryJoda.arbJoda a time zone

It was easy so I just did it. If you would rather it be handled differently, that's fine, just let me know.
I didn't add an implicit val defaultTimeZone because I ran into a problem with ambiguous implicits.
https://github.com/47deg/scalacheck-toolbox/issues/16

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@58517ab). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             master     #58   +/-   ##
========================================
  Coverage          ?   97.6%
========================================
  Files             ?      10
  Lines             ?     125
  Branches          ?       4
========================================
  Hits              ?     122
  Misses            ?       3
  Partials          ?       0

Impacted Files
Coverage Δ

...rtysevendeg/scalacheck/datetime/joda/GenJoda.scala
94.44% <ø> (ø)

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 58517ab...9955938. Read the comment docs.


[PCFG-92] C/D/U BrokerPsp

POST /brokerspsp
PUT /brokerspsp/{brokerpspcode}
DELETE /brokerspsp/{brokerpspcode}

List of Changes

Updated BrokerPspController.java

added Post Put and Delete services

Updated BrokerPspService.java

implemented Post Put and Delete services

Updated Postman Collection
Updated OpenApi.json
Added flyway SQL scripts
Added explicit hibernate dependency to set the last version because it needs the @Type annotation

Motivation and Context
To add new services for the resource broker PSP
How Has This Been Tested?

Junit tests
manually

Screenshots (if appropriate):
Types of changes

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

Checklist:

[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

great 👍 but one stuff Added flyway SQL scripts , where ?

Sorry a mistake in the description.


[bug]: Prompt ignored / random image on 3rd party safetensor model

Is there an existing issue for this?

[X] I have searched the existing issues

OS
macOS
GPU
mps
VRAM
8gb
What happened?
Created Images on InvokeAI are completely random and seem to ignore the prompt completely when I use a 3rd party Safetensor Model. It just produces random images.

If I use the integrated stable-diffusion model, the image is created with the prompt.
If I use the same Model on Automatic1111, it is working
I use a MacBook Pro 2021 16"
I added screenshots and the termin

Screenshots
https://imgur.com/a/HAww6OI
Additional context
Please enter 1, 2, 3, 4, 5, 6 or 7: [2] 2
Starting the InvokeAI browser-based UI...

Initializing, be patient...

Initialization file /Users/joscha/invokeai/invokeai.init found. Loading...
Internet connectivity is True
InvokeAI, version 2.3.0
InvokeAI runtime directory is "/Users/joscha/invokeai"
GFPGAN Initialized
CodeFormer Initialized
ESRGAN Initialized
Using device_type mps
xformers not installed
Current VRAM usage:  0.00G
Loading diffusers model from runwayml/stable-diffusion-v1-5
| Using more accurate float32 precision
| Loading diffusers VAE from stabilityai/sd-vae-ft-mse
| Using more accurate float32 precision
Fetching 15 files: 100%|█████████████████████| 15/15 [00:00<00:00, 77768.31it/s]
| Default image dimensions = 512 x 512
Model loaded in 16.25s
Textual inversions available:
Setting Sampler to k_lms (LMSDiscreteScheduler)

--web was specified, starting web server...
Initializing, be patient...

Initialization file /Users/joscha/invokeai/invokeai.init found. Loading...
Started Invoke AI Web Server!
Default host address now <IP_ADDRESS> (localhost). Use --host <IP_ADDRESS> to bind any address.
Point your browser at http://<IP_ADDRESS>:9090
System config requested
patchmatch.patch_match: INFO - Compiling and loading c extensions from "/Users/joscha/invokeai/.venv/lib/python3.10/site-packages/patchmatch".
patchmatch.patch_match: ERROR - patchmatch failed to load or compile (Command 'make clean && make' returned non-zero exit status 2.).
patchmatch.patch_match: INFO - Refer to https://invoke-ai.github.io/InvokeAI/installation/060_INSTALL_PATCHMATCH/ for installation instructions.
Patchmatch not loaded (nonfatal)
System config requested
System config requested
Model change requested: realisticVisionV13_v13VAEIncluded
Current VRAM usage:  0.00G
Offloading stable-diffusion-1.5 to CPU
Loading realisticVisionV13_v13VAEIncluded from /Users/joscha/stable-diffusion-webui/models/Stable-diffusion/realisticVisionV13_v13VAEIncluded.safetensors
Scanning Model: realisticVisionV13_v13VAEIncluded
Model scanned ok!
Loading realisticVisionV13_v13VAEIncluded from /Users/joscha/stable-diffusion-webui/models/Stable-diffusion/realisticVisionV13_v13VAEIncluded.safetensors
| Forcing garbage collection prior to loading new model
| LatentDiffusion: Running in eps-prediction mode
| DiffusionWrapper has 859.52 M params.
| Making attention of type 'vanilla' with 512 in_channels
| Working with z of shape (1, 4, 32, 32) = 4096 dimensions.
| Making attention of type 'vanilla' with 512 in_channels
| Using more accurate float32 precision
Model loaded in 31.26s
Model loaded in 31.48s
Textual inversions available:
Setting Sampler to k_lms

Image Generation Parameters:

{'prompt': 'a green car', 'iterations': 1, 'steps': 50, 'cfg_scale': 7.5, 'threshold': 0, 'perlin': 0, 'height': 512, 'width': 512, 'sampler_name': 'k_euler', 'seed': 493816845, 'progress_images': False, 'progress_latents': True, 'save_intermediates': 5, 'generation_mode': 'txt2img', 'init_mask': '...', 'seamless': False, 'hires_fix': False, 'variation_amount': 0}

ESRGAN Parameters: False
Facetool Parameters: False
Setting Sampler to k_euler
/Users/joscha/invokeai/.venv/lib/python3.10/site-packages/ldm/modules/embedding_manager.py:146: UserWarning: The operator 'aten::nonzero' is not currently supported on the MPS backend and will fall back to run on the CPU. This may have performance implications. (Triggered internally at /Users/runner/work/pytorch/pytorch/pytorch/aten/src/ATen/mps/MPSFallback.mm:11.)
placeholder_rows, placeholder_cols = torch.where(
Generating:   0%|                                         | 0/1 [00:00<?, ?it/s]>> Ksampler using model noise schedule (steps >= 30)
Sampling with k_euler starting at step 0 of 50 (50 new sampling steps)
100%|███████████████████████████████████████████| 50/50 [01:18<00:00,  1.56s/it]
100%|███████████████████████████████████████████| 50/50 [01:18<00:00,  1.27s/it]

Image generated: "/Users/joscha/invokeai/outputs#/000003.1e3d309d.493816845.png"

Generating: 100%|█████████████████████████████████| 1/1 [01:22<00:00, 82.63s/it]

Usage stats:
1 image(s) generated in 83.03s

Contact Details
No response

Hi there! I have been able to reproduce your issue with this particular safetensors model. As far as I'm aware this is not a general issue with other safetensors models but please post followups if you find models with similar problems.
==Here is what to do to work around the problem==

Open up the command line client by choosing item 1 from the invoke launcher
After the invoke> prompt appears, type !optimize_model realisticVisionV13_v13VAEIncluded
This will convert the model to diffusers format. When I tried the diffusers version, it worked fine.

There's no followup on this so I'm hoping this means the workaround was acceptable.