Does this happen consistently? Can you describe reproduction steps in more detail?

I can reproduce this consistently: it happens every single time. Steps are (sorry if this is stupidly verbose, but I just in case):

Open game.
"Play offline".
"Singleplayer".
"New world".
Enter some random name.
Click that world, create.
Select that world, play.
The launcher says "Generating world..." for a bit, then "Simulating world..."
The launcher hides, screen flashes (like something draws for a single frame or something)
The launcher reappears.

Selecting a pre-existing world has the same result.
I believe these dependencies are relevant:

mono: <IP_ADDRESS>
gtk2: 2.24.31
gtk-sharp-2: 2.12.42
sdl_mixer: 1.2.12
webkitgtk2: 2.4.11-6

I also tried deleting ~/.config/truecraft.

I can reproduce. Will look into it.

I've been getting the same error as well. When I try to just run the client I got this as an output.
Unhandled Exception:
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at TrueCraft.Client.Program.Main (System.String[] args) [0x0001c] in :0
[ERROR] FATAL UNHANDLED EXCEPTION: System.IndexOutOfRangeException: Index was outside the bounds of the array.
at TrueCraft.Client.Program.Main (System.String[] args) [0x0001c] in :0

I'm having the same issue with @hobarrera

same issue with @BearzRobotics

Send me a patch and I'll merge it.

Ended up figuring this out by accident. The fast path for HandleChunkData seems to assume the chunk size when it may, for example, only have block IDs without metadata, light, or sky light. This fixes the crash for me, but I'm guessing the packet is supposed to have all of these things...?
diff --git a/TrueCraft.Client/Handlers/ChunkHandlers.cs b/TrueCraft.Client/Handlers/ChunkHandlers.cs
index 254299f..ede145a 100644
--- a/TrueCraft.Client/Handlers/ChunkHandlers.cs
+++ b/TrueCraft.Client/Handlers/ChunkHandlers.cs
@@ -52,16 +52,31 @@ namespace TrueCraft.Client.Handlers
                 && packet.Height == Chunk.Height
                 && packet.Depth == Chunk.Depth) // Fast path
             {
+                // Chunk data offsets
+                int metadataOffset = chunk.Data.Length;
+                int lightOffset = metadataOffset + chunk.Metadata.Length;
+                int skylightOffset = lightOffset + chunk.BlockLight.Length;
+
                 // Block IDs
                 Buffer.BlockCopy(data, 0, chunk.Data, 0, chunk.Data.Length);
                 // Block metadata
-                Buffer.BlockCopy(data, chunk.Data.Length, chunk.Metadata.Data, 0, chunk.Metadata.Data.Length);
+                if (metadataOffset < data.Length)
+                {
+                    Buffer.BlockCopy(data, metadataOffset,
+                        chunk.Metadata.Data, 0, chunk.Metadata.Data.Length);
+                }
                 // Block light
-                Buffer.BlockCopy(data, chunk.Data.Length + chunk.Metadata.Data.Length,
-                    chunk.BlockLight.Data, 0, chunk.BlockLight.Data.Length);
+                if (lightOffset < data.Length)
+                {
+                    Buffer.BlockCopy(data, lightOffset,
+                        chunk.BlockLight.Data, 0, chunk.BlockLight.Data.Length);
+                }
                 // Sky light
-                Buffer.BlockCopy(data, chunk.Data.Length + chunk.Metadata.Data.Length + chunk.BlockLight.Data.Length,
-                    chunk.SkyLight.Data, 0, chunk.SkyLight.Data.Length);
+                if (skylightOffset < data.Length)
+                {
+                    Buffer.BlockCopy(data, skylightOffset,
+                        chunk.SkyLight.Data, 0, chunk.SkyLight.Data.Length);
+                }
             }
             else // Slow path
             {

Can you send this as a pull request instead of a patch thrown into a commit? You can email me a patch if you want, too.

Done: https://github.com/SirCmpwn/TrueCraft/pull/282

Using latest commit still warrants the same effect. However, I want to note that this happens regardless of offline, or online mode and whether or not I load an already generated world.

Weird, on my side it runs fine.

Gentoo Linux
Mono <IP_ADDRESS>

Do you actually have the same error?


Error: Command failed: open --background one-thing:?text=Prepare%20for%20important%20meeting

one-thing 'Prepare for important meeting'
Error: Command failed: open --background one-thing:?text=Prepare%20for%20important%20meeting
No application knows how to open URL one-thing:?text=Prepare%20for%20important%20meeting (Error Domain=NSOSStatusErrorDomain Code=-10814 "kLSApplicationNotFoundErr: E.g. no application claims the file" UserInfo={_LSLine=1489, _LSFunction=runEvaluator}).
at ChildProcess.exithandler (node:child_process:397:12)

=========
nodejs v16.13.2
macbook

Do you have the "One Thing" app installed?

Do you have the "One Thing" app installed?

NO.
I just use
yarn global add  one-thing one-thing 'Prepare for important meeting'
I'll install the app, and try again

Do you have the "One Thing" app installed?

after install app， i do it success .
thanks


Config exmaple or generate config?

There is no config generated for the CLI, and I cannot find an example config in this repo.
I need to specify a URL for the default privatebin instance to use.
What is the recommended course of action here?

By default using a premade binary result sin:

Error: cannot load configuration: cannot open file: open /home/douglas/.config/privatebin/config.json: no such file or directory

However, adding an emoty cofnig file with an empty JSON objects results in:
Error: cannot find "" bin configuration: cannot find "" bin configuration

I tried to reverse engineer it, but still get the same error 😒
Using the example in the docs:

cat example.txt | privatebin create

{
  "bin": [
    {
      "name": "example",
      "host": "[my private instance]",
      "expire": "1week",
      "open-discussion": false,
      "burn-after-reading": false,
      "gzip": false,
      "formatter": "plaintext"
    }
  ],
  "expire": "1week",
  "open-discussion": false,
  "burn-after-reading": false,
  "gzip": false,
  "formatter": "plaintext"
}

Looks like I needed an empty bin profile name for the default.

The default instance is unnamed, and you can specify other named instances using the --bin flag.
I agree that adding functionality to auto-generate a config if none exists would improve the user experience — I'll consider implementing this enhancement.
For more details on configuration, please refer to the documentation: https://github.com/gearnode/privatebin/blob/master/doc/privatebin.conf.5.md

@gearnode was this solved by a pr that can be linked to it?

@douglasg14b  I'll add the generator feature one day, or feel free to open a pull request to add it if you have the time. Updating the documentation to clarify that the empty string is the default for the private bin instance would also be a good improvement. However, since there’s no bug in the program, I’m closing this issue.

@gearnode
I'm not following. Is this not a bug?
The CLI will not work out of the box unless the user fixes it. It may not be a logical defect, but it is still a defect that degrades the user experience.


Store the task history in one cache

Currently, Gradle is using two cache files for storing the task history: One for the file collection snapshots involved and another one storing the remainder of the task history.
Using a separate cache for file collection snapshots may cause inconsistent state as seen in #2827. Instead of having a different cache file for the snapshots we should just have one cache for the task history including the snapshots.

@lptr Please have another look.

@lptr Please have another look.


Automator: Update dependencies in istio-ecosystem/sail-operator@main

Generated by Automator - 2024-05-31T23:01:00+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_sail-operator_main
afce0c182af8924fd014b0d1c397876dbcf0c297
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_sail-operator_main
afce0c182af8924fd014b0d1c397876dbcf0c297
link
true
/test unit-tests-arm64

unit-tests_sail-operator_main
afce0c182af8924fd014b0d1c397876dbcf0c297
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_sail-operator_main
afce0c182af8924fd014b0d1c397876dbcf0c297
link
true
/test unit-tests-arm64

unit-tests_sail-operator_main
afce0c182af8924fd014b0d1c397876dbcf0c297
link
true
/test unit-tests

e2e-kind_sail-operator_main
afce0c182af8924fd014b0d1c397876dbcf0c297
link
true
/test e2e-kind

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_sail-operator_main
afce0c182af8924fd014b0d1c397876dbcf0c297
link
true
/test unit-tests

e2e-kind_sail-operator_main
afce0c182af8924fd014b0d1c397876dbcf0c297
link
true
/test e2e-kind

unit-tests-arm64_sail-operator_main
6413d14c084b827e7a8e64b7de01e0da1eeee510
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

e2e-kind_sail-operator_main
afce0c182af8924fd014b0d1c397876dbcf0c297
link
true
/test e2e-kind

unit-tests-arm64_sail-operator_main
6413d14c084b827e7a8e64b7de01e0da1eeee510
link
true
/test unit-tests-arm64

unit-tests_sail-operator_main
6413d14c084b827e7a8e64b7de01e0da1eeee510
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_sail-operator_main
6413d14c084b827e7a8e64b7de01e0da1eeee510
link
true
/test unit-tests-arm64

unit-tests_sail-operator_main
6413d14c084b827e7a8e64b7de01e0da1eeee510
link
true
/test unit-tests

e2e-kind_sail-operator_main
6413d14c084b827e7a8e64b7de01e0da1eeee510
link
true
/test e2e-kind

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.


Pinch to zoom on Safari mac doesn't consider modals

Demo

What do you think should be the appropriate behavior? IMO it shouldn't zoom the canvas, but we also don't want to zoom in on the dialog as it would then break the canvas.

On Chrome & Firefox, it zooms in on the dialog now. If I close the modal while it is zoomed in, pinching out to zoom out doesn't work till I open the dialog again.
I think we should fix it by allowing zooming in while a dialog is open but reset zoom on exiting it.

I think we should fix it by allowing zooming in while a dialog is open but reset zoom on exiting it.

Not really possible to manipulate the browser zoom level programmatically. There are some non-cross-browser hacks, but they still don't change the zoom level.


ref(core): Adjust requiredness of user and internal options

This PR adjusts some user-facing and internal options from being strictly required to being optional. The reason for this change is that with the introduction of Sentry CLI, we can (and for feature parity should) let users either use env variables or specify some values via a .sentryclirc config file.
Note that for release injection to work properly, users have to specify project, org and release either via the options or via env variables. The reason is that the config file which could also hold these options is only later used by Sentry CLI. This behaviour is identical to what we do in the webpack plugin.
A validation improvement PR will follow soon
ref #91

FYI: Hope you don't mind, but I edited the title and PR description to pluralize "options," since I found the singular confusing. (I kept thinking, 'wait, which option?')
Also, L: You might consider being more specific in the PR title about which direction the adjustment is going (something like ref(core): Make various user and internal options optional, for example).

can you explain why reading from the file comes too late? Could you just do that earlier?

The reason is that we (and with that I mean the new bundler plugin but also the old webpack plugin) don't do anything with the config file. We just pass through the configFile option to Sentry CLI which only then reads it and uses the values specified in there. Release injection doesn't use Sentry CLI for anything other than automatically detecting a release name if none is specified via options or an env variable  (which does not seem to check env variables or the config file). So the way I see this, there is no way how values from the config file could be accessed for release injection. Unless of course, we say we go beyond feature parity and parse the file ourselves (which would be scope creep).


Getting "Cache size 0" warnings

I've started to get these warnings in in my terminal and I'm quite sure I've started to get them after I started using MotionModel. I can't find any place in the MotionModel code that would output such a warning, but I simply don't know what else it could be:
May 11 18:16:43 Holger-Sindbaeks-iPhone Slang[1563] <Warning>: Cache size 0

Are you familiar with this warning? Am I right, that it's related to MotionModel?

This doesn't ring any bells. There is no string in MotionModel that warns about cache size. Have you pinged motion support?

No... you think it might be generally RubyMotion related?

It's hard to say, but the string does not exist in MotionModel as far as I can see and if it doesn't exist in your app, that leaves only 2 other places: Frameworks and RubyMotion. Right?

Can't argue with that. Thanks for the clarification!


Run analyzer for multiple observables

Hello,
First of all great work frikky :)
Im trying this tools for integraton with theHive, at this moment I created worflows with these nodes:
https://pasteboard.co/JrFvpTLe.png

getObservables: getting observables from case
getIpAnalyzers: getting avaible analyzers for IP
getDomainAnalyzers:  getting avaible analyzers for domain
runAnalyzers: run analyzers for $getObervables.#.id

"run analyzers" function of TheHive app works with single artifact_id but it dosen't work with multiple artifacts like array of artifact_id ( $getObservables.#.id)
Best regards
A.A.

Hey @AndreAzzalin and thanks!
Can you share the (redacted) data returned from getObservables?
Also: there was a bug with loops and JSON that was fixed two days ago. Have you recreated the app after that (Force update from Github)?

Hello,
Thanks for reply, here the JSON returned from getObservables:
"Results for getObservables":[4 items
0:{18 items
"_routing":"AXN8RSAvZP8HpukK-R"
"reports":{}0 items
"data":"<IP_ADDRESS>"
"dataType":"ip"
"_type":"case_artifact"
"sighted":false
"message":"Found in the email body"
"tags":[...]1 item
"createdAt":1595517778023
"_parent":"AXN8RSAvZP8HpukK-R"
"createdBy":"synapse"
"tlp":2
"_id":"bd0da20b7fa79e1cd1f26b69a024bebe"
"id":"bd0da20b7fa79e1cd1f26b69a024bebe"
"ioc":false
"_version":1
"startDate":1595517778024
"status":"Ok"
}
1:{...}20 items
2:{...}20 items
]
I've already force update from your repo but it still doesn't work, runAnalyzer return :

Status FAILURE
Result General exception: list index out of range

Parameters pass to runAnalyzer function :

analyzer_id:
$getIpAnalyzers.#
artifact_id:
$getObservables.#._id

Hopefully you have all the information you need while I'm working on the script to make it work
Regards :)

Well, good thing is you've understood how the system works, bad thing is that there seems to be an issue with the system itself. In my PoC with that data it worked, so I have one more check before I'll properly test it with TheHive myself:

Did you update the App SDK before force updating? It can be done like this:

docker pull frikky/shuffle:app_sdk

I totally forgot about that bit in my last message. This also reminds me that I should have a frontend check for that sort of stuff.

I've force updating with:
 docker pull frikky/shuffle:app_sdk
only after the docker restart the changes were effective, but now function runAnayzer return different error :
PARAMETERS:
analyzer_id: $getIpAnalyzers.#

Status SUCCESS
Result ['GoogleSafebrowsing_2_0', 'VirusTotal_GetReport_3_0', 'URLhaus_2_0', 'MISP_2_1', 'OTXQuery_2_0', 'GoogleDNS_resolve_1_0_0', 'Abuse_Finder_3_0', 'Threatcrowd_1_0', 'CyberCrime-Tracker_1_0', 'Mnemonic_pDNS_Public_3_0', 'Urlscan_io_Scan_0_1_0']

artifact_id: $getObservables.#.id

"Results for getObservables":[4 items
0:{18 items
"_routing":"AXS2jJ0UaSCDULf45fwq"
"reports":{}0 items
"data":"<IP_ADDRESS>"
"dataType":"ip"
"_type":"case_artifact"
"sighted":false
"message":"Found in the email body"
"tags":[...]1 item
"createdAt":1600790509008
"_parent":"AXS2jJ0UaSCDULf45fwq"
"createdBy":"synapse"
"tlp":2
"_id":"da39832a62b5186912ac5db67ffff126"
"id":"da39832a62b5186912ac5db67ffff126"
"ioc":false
"_version":1
"startDate":1600790509009
"status":"Ok"
}
1:{...}18 items
2:{...}18 items
3:{...}18 items
]

RETURN VALUE:

"Results for runAnalyzer":{2 items
"type":"NotFoundError"
"message":"analyzer ["DShield_lookup_1_0", "GreyNoise_2_3", "VirusTotal_GetReport_3_0", "URLhaus_2_0", "MISP_2_1", "AbuseIPDB_1_0", "OTXQuery_2_0", "GoogleDNS_resolve_1_0_0", "Abuse_Finder_3_0", "TalosReputation_1_0", "Threatcrowd_1_0", "CyberCrime-Tracker_1_0", "Mnemonic_pDNS_Public_3_0"] not found"
}

I don't understand if I'm missing something :(

Looks like it's sending all the values rather than looping them, which is incorrect behavior from the App SDK. You're doing it exactly right :D
I'll get it fixed within the week :)
PS: You're one of the first to try using loops properly after I did the last fix, which is why it's kind of wonky. Sorry about the issues.

lol no problem
Thanks for your kind support, it's a pleasure for me helping you improve this project 👍

Heyo!
Try to update your App_sdk, then run force update again! This issues should now be fixed :fire:
# Updating:
docker pull frikky/shuffle:app_sdk

Hey Frikky,
Unfortunately still doesn't work, also after force pull from docker :(
for function runAnalyzer return:
Status FAILURE
Result General exception: list index out of range

Are you sure to push new fixed code for TheHive app? :)

Alright, I'll set it up properly myself and test! I'll get back to you - this shouldn't be an issue :disappointed:

I pushed yet another fix to loops in the app SDK, and tested a lot with your data meaning: it should work now.
Can you run the updating process again and try?
1:
docker pull frikky/shuffle:app_sdk

2: Click "force update" on the apps

Update again: I did a major update to the app SDK today to fix this issue. Please update it and tell me how it works :+1:

I also update here the status of the issue
Im follow the pull procedure:

docker pull frikky/shuffle:app_sdk
wait some minute
"force update" on the apps

Unfortunally app with function "runAnalyzer" still return:
Status FAILURE
Result General exception: list index out of range

Working on it. This is a tricky issue and is also hard to test :/

Fixed and verified by @AndreAzzalin in an email.
Reference ID: https://github.com/frikky/Shuffle/commit/722d832d881de4bfeafc2424d8145c37f779002c
PS: This issue will kind of show up again when we reach >2 loops.
Reference issue: https://github.com/frikky/Shuffle/issues/170


feat: add options goToAndPlay and goToAndStop

I created two wrapper functions for goToAndPlay and goToAndStop.
I had a problem to run test even before changes. Is that known issue?

I really wanted this feature

Can this be merged please

I also need this feature please merge to master

I really need this feature, please merge

please merge this feature


Successful deid requests must return status code 200

Update the OpenAPI spec if needed

Related to https://github.com/nlpsandbox/nlpsandbox-schemas/issues/86#issue-747886275


Warning Triggered During PyTorch Dispatch

When using the flag_gems library, specifically after calling flag_gems.enable() or with flag_gems.use_gems(), a warning is triggered:
UserWarning: Warning only once for all operators, other operators may also be overridden.
This warning indicates that a previously registered kernel for a specific operator is being overridden. It appears in the following context:
In [1]: import flag_gems

In [2]: flag_gems.enable()
/usr/local/lib/python3.10/dist-packages/torch/library.py:169: UserWarning: Warning only once for all operators,  other operators may also be overrided.
  Overriding a previously registered kernel for the same operator and the same dispatch key
  operator: aten::add.Tensor(Tensor self, Tensor other, *, Scalar alpha=1) -> Tensor
    registered at aten/src/ATen/RegisterSchema.cpp:6
  dispatch key: CUDA
  previous kernel: registered at ../aten/src/ATen/LegacyBatchingRegistrations.cpp:1079
       new kernel: registered at /dev/null:241 (Triggered internally at ../aten/src/ATen/core/dispatch/OperatorEntry.cpp:153.)
  self.m.impl(name, dispatch_key if dispatch_key != "" else "CompositeImplicitAutograd", fn)

Additionally, this warning is also displayed when running unit tests with pytest.
Related PR
To address this issue, a recent pull request was made to suppress this specific warning during PyTorch dispatch calls.
#190

warning is expected. it indicates that the replacement of flag_gems succeeded.

https://github.com/FlagOpen/FlagGems/pull/190


getProductHistoricRates not responding to start=, end=

When looking at the official documentation of GDAX, the getProductHistoricRates takes arguments start, end and granularity. However only the latter one seems to work. Whenever using start or end it just returns the latest result from the server.
Any thoughts to why?

note that the start and end parameters are in ISO 8601. hence YYYY-MM-DD for example may 4 2017 is 2017-05-04.
here is a link to explain https://en.wikipedia.org/wiki/ISO_8601
here is some sample code PC.getProductHistoricRates(granularity=1000 , start='2017-05-04', end='2017-05-05' )

My bad it very clearly states ISO 8601 in the documentation.


YamlSequence.java:8-11: Implement and unit test decorator Strict...

The puzzle 6-754324bd in src/main/java/com/amihaiemil/camel/YamlSequence.java (lines 8-11) has to be resolved: Implement and unit test decorator StrictYamlSequence which should throw YamlNodeNotFoundException if any of the methods of the decorated YamlSequence returns null (if the given index points to a YamlNode that is not a YamlMapping, for instance).
The puzzle was created by amihaiemil on 19-Jan-17.
Estimate: 30 minutes, role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code.

@salikjan could you do this?
By the way, this is what I meant when I said issues are opened automatically. When a puzzle is left in the code, the 0pdd bot opens an issue for it and will also close the issue when the puzzle is removed from the code.

@amihaiemil yes, i'll do. firstly i have to take a look at global changes in project ;)

@salikjan Sure, you should do that. Any questions you have, or if you don't like something, open an issue and we can discuss there :)

The puzzle 6-754324bd has disappeared from the source code, that's why I closed this issue. //cc @amihaiemil


[Bug]: Sorting on Compare table does not sort colors

What did you expect to happen?
.
What happened?
When sorting, the colors do not follow the rows as they move (the colors stay stationary while everything else re-orders)
Version
Beta 0.1.0
What browsers are you seeing the problem on?
No response
Relevant log output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

related to: https://github.com/UTDNebula/utd-trends/issues/175


Deletion of scratch orgs or auth:logout does not remove org alias from ~/.sfdx/aliases.json

Summary
When a scratch org is deleted or you logout of an org with an alias, that alias is not removed from the ~/.sfdx/aliases.json file.
Steps To Reproduce:

Create a scratch org with an alias
Delete that scratch org
Check the ~/.sfdx/aliases.json file.  Alias is still present even though org auth is gone.

Expected result
aliases.json file should have alias removed
Actual result
aliases.json file does not have alias removed
System Information
{
	"cliVersion": "sfdx-cli/7.138.0",
	"architecture": "darwin-x64",
	"nodeVersion": "node-v16.14.0",
	"pluginVersions": [
		"@dx-cli-toolbox/sfdx-toolbox-package-utils 0.8.1 (link) /Users/john/workspace/_cli-related/sfdx-toolbox-package-utils",
		"@dx-cli-toolbox/sfdx-toolbox-utils 0.0.2 (link) /Users/john/workspace/_cli-related/sfdx-toolbox-utils",
		"@oclif/plugin-autocomplete 1.2.0",
		"@oclif/plugin-commands 1.3.0 (core)",
		"@oclif/plugin-help 3.3.1 (core)",
		"@oclif/plugin-not-found 1.2.6 (core)",
		"@oclif/plugin-plugins 1.10.11 (core)",
		"@oclif/plugin-update 1.5.0 (core)",
		"@oclif/plugin-warn-if-update-available 1.7.3 (core)",
		"@oclif/plugin-which 1.0.4 (core)",
		"@salesforce/sfdx-plugin-lwc-test 0.1.7 (core)",
		"@salesforce/sfdx-scanner 2.12.0",
		"alias 1.2.1 (core)",
		"apex 0.8.0 (core)",
		"auth 1.8.1 (core)",
		"community 1.1.4 (core)",
		"config 1.3.19 (core)",
		"custom-metadata 1.0.12 (core)",
		"data 0.6.9 (core)",
		"generator 1.2.2 (core)",
		"info 1.2.1 (core)",
		"limits 1.3.0 (core)",
		"org 1.11.1 (core)",
		"salesforce-alm 53.10.0 (core)",
		"schema 1.1.0 (core)",
		"sfdmu 4.12.7",
		"sfdx-cli 7.138.0 (core)",
		"shane-sfdx-plugins 4.43.0",
		"├─ @mshanemc/plugin-streaming 1.1.7",
		"└─ @mshanemc/sfdx-sosl 1.1.0",
		"soqlx-opener 0.1.12",
		"source 1.8.11 (core)",
		"telemetry 1.4.0 (core)",
		"templates 53.5.0 (core)",
		"trust 1.1.0 (core)",
		"user 1.7.1 (core)"
	],
	"osVersion": "Darwin 21.2.0"
}

Thanks @ImJohnMDaniel, was able to replicate this also. Created a work item to get this cleaned up.

hmm, we didn't get this listed in the release notes but it was fixed last week: https://github.com/forcedotcom/sfdx-core/pull/525/files.
Make sure to install sfdx v7.140.0 😃


🐛 Front camera recording is inverted when going from Back to Front camera during recording on Android

What's happening?
On an Android device, while taking a video recording with the Back camera started, if user switches to Front camera during the same recording the Front video recording becomes inverted -- it looks okay during the recording session but the saved video recording of the Front camera is inverted (upside-down).
Interestingly, if I start the recording using the Front camera then switch to Back camera the recording of the Front video is fine.
Reproduceable Code
const [cameraPosition, setCameraPosition] = useState<'front' | 'back'>('back');
  const cameraDevice = useCameraDevice(cameraPosition);

<Camera
            ref={cameraRef}
            device={cameraDevice}
            torchEnabled={torchEnabled}
            onRotate={useCallback(() => {
              setCameraPosition((p) => (p === 'back' ? 'front' : 'back'));
            }, [])}
            onTorchToggle={() => setTorchEnabled((prev) => !prev)}
          />

Relevant log output
Back Camera:
{"formats": [{"autoFocusSystem": "none", "fieldOfView":<PHONE_NUMBER>0825525, "maxFps": 30, "maxISO": 1600, "minFps": 2, "minISO": 25, "photoHeight": 144, "photoWidth": 176, "supportsDepthCapture": false, "supportsPhotoHdr": false, "supportsVideoHdr": false, "videoHeight": 720, "videoStabilizationModes": [Array], "videoWidth": 1280}, {"autoFocusSystem": "none", "fieldOfView":<PHONE_NUMBER>0825525, "maxFps": 30, "maxISO": 1600, "minFps": 2, "minISO": 25, "photoHeight": 240, "photoWidth": 320, "supportsDepthCapture": false, "supportsPhotoHdr": false, "supportsVideoHdr": false, "videoHeight": 720, "videoStabilizationModes": [Array], "videoWidth": 1280}, {"autoFocusSystem": "none", "fieldOfView":<PHONE_NUMBER>0825525, "maxFps": 30, "maxISO": 1600, "minFps": 2, "minISO": 25, "photoHeight": 288, "photoWidth": 352, "supportsDepthCapture": false, "supportsPhotoHdr": false, "supportsVideoHdr": false, "videoHeight": 720, "videoStabilizationModes": [Array], "videoWidth": 1280}, {"autoFocusSystem": "none", "fieldOfView":<PHONE_NUMBER>0825525, "maxFps": 30, "maxISO": 1600, "minFps": 2, "minISO": 25, "photoHeight": 480, "photoWidth": 640, "supportsDepthCapture": false, "supportsPhotoHdr": false, "supportsVideoHdr": false, "videoHeight": 720, "videoStabilizationModes": [Array], "videoWidth": 1280}, {"autoFocusSystem": "none", "fieldOfView":<PHONE_NUMBER>0825525, "maxFps": 30, "maxISO": 1600, "minFps": 2, "minISO": 25, "photoHeight": 720, "photoWidth": 1280, "supportsDepthCapture": false, "supportsPhotoHdr": false, "supportsVideoHdr": false, "videoHeight": 720, "videoStabilizationModes": [Array], "videoWidth": 1280}, {"autoFocusSystem": "none", "fieldOfView":<PHONE_NUMBER>0825525, "maxFps": 30, "maxISO": 1600, "minFps": 2, "minISO": 25, "photoHeight": 960, "photoWidth": 1280, "supportsDepthCapture": false, "supportsPhotoHdr": false, "supportsVideoHdr": false, "videoHeight": 720, "videoStabilizationModes": [Array], "videoWidth": 1280}], "hardwareLevel": "limited", "hasFlash": false, "hasTorch": false, "id": "10", "isMultiCam": false, "maxExposure": 6, "maxZoom": 1, "minExposure": -6, "minFocusDistance":<PHONE_NUMBER>98839, "minZoom": 1, "name": "10 (BACK) androidx.camera.camera2", "neutralZoom": 1, "physicalDevices": ["ultra-wide-angle-camera"], "position": "back", "sensorOrientation": "landscape-left", "supportsFocus": false, "supportsLowLightBoost": false, "supportsRawCapture": false}

Front Camera:
{"formats": [{"autoFocusSystem": "contrast-detection", "fieldOfView": 77.70146040253039, "maxFps": 30, "maxISO": 1000, "minFps": 7, "minISO": 100, "photoHeight": 1440, "photoWidth": 1920, "supportsDepthCapture": false, "supportsPhotoHdr": false, "supportsVideoHdr": false, "videoHeight": 720, "videoStabilizationModes": [Array], "videoWidth": 1280}, {"autoFocusSystem": "contrast-detection", "fieldOfView": 77.70146040253039, "maxFps": 30, "maxISO": 1000, "minFps": 7, "minISO": 100, "photoHeight": 1080, "photoWidth": 1920, "supportsDepthCapture": false, "supportsPhotoHdr": false, "supportsVideoHdr": false, "videoHeight": 720, "videoStabilizationModes": [Array], "videoWidth": 1280}, {"autoFocusSystem": "contrast-detection", "fieldOfView": 77.70146040253039, "maxFps": 30, "maxISO": 1000, "minFps": 7, "minISO": 100, "photoHeight": 960, "photoWidth": 1920, "supportsDepthCapture": false, "supportsPhotoHdr": false, "supportsVideoHdr": false, "videoHeight": 720, "videoStabilizationModes": [Array], "videoWidth": 1280}, {"autoFocusSystem": "contrast-detection", "fieldOfView": 77.70146040253039, "maxFps": 30, "maxISO": 1000, "minFps": 7, "minISO": 100, "photoHeight": 1200, "photoWidth": 1600, "supportsDepthCapture": false, "supportsPhotoHdr": false, "supportsVideoHdr": false, "videoHeight": 720, "videoStabilizationModes": [Array], "videoWidth": 1280}, {"autoFocusSystem": "contrast-detection", "fieldOfView": 77.70146040253039, "maxFps": 30, "maxISO": 1000, "minFps": 7, "minISO": 100, "photoHeight": 1080, "photoWidth": 1440, "supportsDepthCapture": false, "supportsPhotoHdr": false, "supportsVideoHdr": false, "videoHeight": 720, "videoStabilizationModes": [Array], "videoWidth": 1280}, {"autoFocusSystem": "contrast-detection", "fieldOfView": 77.70146040253039, "maxFps": 30, "maxISO": 1000, "minFps": 7, "minISO": 100, "photoHeight": 960, "photoWidth": 1280, "supportsDepthCapture": false, "supportsPhotoHdr": false, "supportsVideoHdr": false, "videoHeight": 720, "videoStabilizationModes": [Array], "videoWidth": 1280}, {"autoFocusSystem": "contrast-detection", "fieldOfView": 77.70146040253039, "maxFps": 30, "maxISO": 1000, "minFps": 7, "minISO": 100, "photoHeight": 720, "photoWidth": 1280, "supportsDepthCapture": false, "supportsPhotoHdr": false, "supportsVideoHdr": false, "videoHeight": 720, "videoStabilizationModes": [Array], "videoWidth": 1280}, {"autoFocusSystem": "contrast-detection", "fieldOfView": 77.70146040253039, "maxFps": 30, "maxISO": 1000, "minFps": 7, "minISO": 100, "photoHeight": 768, "photoWidth": 1024, "supportsDepthCapture": false, "supportsPhotoHdr": false, "supportsVideoHdr": false, "videoHeight": 720, "videoStabilizationModes": [Array], "videoWidth": 1280}, {"autoFocusSystem": "contrast-detection", "fieldOfView": 77.70146040253039, "maxFps": 30, "maxISO": 1000, "minFps": 7, "minISO": 100, "photoHeight": 600, "photoWidth": 800, "supportsDepthCapture": false, "supportsPhotoHdr": false, "supportsVideoHdr": false, "videoHeight": 720, "videoStabilizationModes": [Array], "videoWidth": 1280}, {"autoFocusSystem": "contrast-detection", "fieldOfView": 77.70146040253039, "maxFps": 30, "maxISO": 1000, "minFps": 7, "minISO": 100, "photoHeight": 480, "photoWidth": 720, "supportsDepthCapture": false, "supportsPhotoHdr": false, "supportsVideoHdr": false, "videoHeight": 720, "videoStabilizationModes": [Array], "videoWidth": 1280}, {"autoFocusSystem": "contrast-detection", "fieldOfView": 77.70146040253039, "maxFps": 30, "maxISO": 1000, "minFps": 7, "minISO": 100, "photoHeight": 480, "photoWidth": 640, "supportsDepthCapture": false, "supportsPhotoHdr": false, "supportsVideoHdr": false, "videoHeight": 720, "videoStabilizationModes": [Array], "videoWidth": 1280}, {"autoFocusSystem": "contrast-detection", "fieldOfView": 77.70146040253039, "maxFps": 30, "maxISO": 1000, "minFps": 7, "minISO": 100, "photoHeight": 360, "photoWidth": 640, "supportsDepthCapture": false, "supportsPhotoHdr": false, "supportsVideoHdr": false, "videoHeight": 720, "videoStabilizationModes": [Array], "videoWidth": 1280}, {"autoFocusSystem": "contrast-detection", "fieldOfView": 77.70146040253039, "maxFps": 30, "maxISO": 1000, "minFps": 7, "minISO": 100, "photoHeight": 288, "photoWidth": 352, "supportsDepthCapture": false, "supportsPhotoHdr": false, "supportsVideoHdr": false, "videoHeight": 720, "videoStabilizationModes": [Array], "videoWidth": 1280}, {"autoFocusSystem": "contrast-detection", "fieldOfView": 77.70146040253039, "maxFps": 30, "maxISO": 1000, "minFps": 7, "minISO": 100, "photoHeight": 240, "photoWidth": 320, "supportsDepthCapture": false, "supportsPhotoHdr": false, "supportsVideoHdr": false, "videoHeight": 720, "videoStabilizationModes": [Array], "videoWidth": 1280}], "hardwareLevel": "full", "hasFlash": true, "hasTorch": true, "id": "1", "isMultiCam": true, "maxExposure": 24, "maxZoom": 12.931958198547363, "minExposure": -24, "minFocusDistance": 9.800000093460085, "minZoom": 1, "name": "1 (FRONT) androidx.camera.camera2", "neutralZoom": 1, "physicalDevices": ["wide-angle-camera", "wide-angle-camera", "telephoto-camera"], "position": "front", "sensorOrientation": "landscape-right", "supportsFocus": true, "supportsLowLightBoost": false, "supportsRawCapture": false}

Camera Device
Back Camera
{
  "formats": [],
  "sensorOrientation": "landscape-left",
  "hardwareLevel": "limited",
  "maxZoom": 1,
  "minZoom": 1,
  "maxExposure": 6,
  "supportsLowLightBoost": false,
  "neutralZoom": 1,
  "physicalDevices": [
    "ultra-wide-angle-camera"
  ],
  "supportsFocus": false,
  "supportsRawCapture": false,
  "isMultiCam": false,
  "minFocusDistance":<PHONE_NUMBER>98839,
  "minExposure": -6,
  "name": "10 (BACK) androidx.camera.camera2",
  "hasFlash": false,
  "hasTorch": false,
  "position": "back",
  "id": "10"
}

Front Camera
{
  "formats": [],
  "sensorOrientation": "landscape-right",
  "hardwareLevel": "full",
  "maxZoom": 12.931958198547363,
  "minZoom": 1,
  "maxExposure": 24,
  "supportsLowLightBoost": false,
  "neutralZoom": 1,
  "physicalDevices": [
    "wide-angle-camera",
    "wide-angle-camera",
    "telephoto-camera"
  ],
  "supportsFocus": true,
  "supportsRawCapture": false,
  "isMultiCam": true,
  "minFocusDistance": 9.800000093460085,
  "minExposure": -24,
  "name": "1 (FRONT) androidx.camera.camera2",
  "hasFlash": true,
  "hasTorch": true,
  "position": "front",
  "id": "1"
}

Device
Android Pixel 6 Pro API 34 (emulator), Pixel 5 API 34 (physical device)
VisionCamera Version
4.0.3
Can you reproduce this issue in the VisionCamera Example app?
I didn't try (⚠ your issue might get ignored & closed if you don't try this)
Additional information

[ ] I am using Expo
[ ] I have enabled Frame Processors (react-native-worklets-core)
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

What does inverted mean? Please attach a sample video.

Here is a screen recording using the Android Pixel 6 Pro API 34 emulator. The same happens on physical device:
https://github.com/mrousavy/react-native-vision-camera/assets/147250490/c930e17b-1c46-4fa0-89a3-0e96bd6a1a08

Okay, this is a CameraX bug then, nothing I am doing explicitly - could you create a bug report in the Google CameraX issue tracker about this?
Thanks!

@mrousavy I think I figured out the issue -- at least doing this change fixes it for me:
In this file:
node_modules/react-native-vision-camera/android/src/main/java/com/mrousavy/camera/core/CameraSession.kt
I commented out line 308:
val video = VideoCapture.Builder(recorder).also { video ->
// Configure Video Output
// video.setMirrorMode(MirrorMode.MIRROR_MODE_ON_FRONT_ONLY)
And the issue was resolved. I think this is because in my use case, the recording starts using the back camera and the CameraX must set a certain orientation, and when I switch to Front camera during the same recording the orientation is not updated to relative to Front camera, so mirrorMode causes the inversion.
I'm not sure if there is a way to adjust the code to check if the orientation is correct before applying the setMirrorMode or maybe this is the desired behavior just an issue with CameraX as you say.
Thanks.

Hey - I think I fixed this issue in the latest releases. I update orientation immediately after switching devices. Can you confirm if that works for you?

Hi Marc,
Yes the latest version seems to be working now! No more inverted selfie
videos on Android.
I appreciate your follow up and all the work you are doing for this great
package.
Thanks,
Carson
On Wed, Jul 10, 2024 at 8:17 AM Marc Rousavy @.***>
wrote:

Hey - I think I fixed this issue in the latest releases. I update
orientation immediately after switching devices. Can you confirm if that
works for you?
—
Reply to this email directly, view it on GitHub
https://github.com/mrousavy/react-native-vision-camera/issues/2854#issuecomment-2220360780,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BDDN2OQZNIOHYOC43ADQHIDZLUQ6LAVCNFSM6AAAAABHLQAYRCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRQGM3DANZYGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Awesome thank you. If you appreciate my work and dedication please consider sponsoring me on GitHub :)


Chore: rewrite get_models_ids to use the SDK

This is what the function looking like right now in (file link)
Lets adjust this to use our SDK instead of a custom data structure for the Model.
def get_models_ids() -> Dict[str, Dict[str, Union[str, int]]]:
    # api_instance = pos_client.ModelsApi(api_client)

    # api_response = api_instance.models_snapshot()
    # models = {model.name: {"uuid":model.id,"word_limit":model.max_tokens.input} for model in api_response.iterable if model.cloud or model.downloading} # getting the models that are available in the cloud or is downloaded

    # call the api until the sdks updated
    response = urllib.request.urlopen('http://localhost:1000/models').read()
    response = json.loads(response)["iterable"]
    models = {model["name"]:{"uuid":model["id"] ,"word_limit" :model["maxTokens"]["input"]} for model in response if model["cloud"] or model["downloading"]}
    return models

These are the foundations that added in 2.0.0 which are not in 1.2.7
PHI_1_DOT_5 = 'PHI_1.5'
PHI_2 = 'PHI_2'
MIXTRAL_8_X_7_B = 'MIXTRAL_8_x_7B'

@mark-at-pieces @Bishoy-at-pieces I'm talking with dom on getting our python SDK updated which may solve this. Will send updates as they come.


question: OAuth with Keycloak

I am using Keycloak as IDP.
https://github.com/authp/authp.github.io/blob/main/assets/conf/oauth/keycloak/Caddyfile
This configuration works well but I have a question here,
Can I use Keycloak's JWT after authentication?
As I understood, after authentication, caddy-security issues its own JWT which would be used in authorization.
Can I configure it to use Keycloak's JWT in authentication and decrypt it with Keycloak's pub key in authorization?
Kindly give me your comments.
Thanks

Can I use Keycloak's JWT after authentication?

@alirf81 , no.


Add OKD compatibility to snc for building CRC for OKD bundles

This pull request is to satisfy:
https://github.com/code-ready/crc/issues/977
https://github.com/code-ready/snc/issues/212
I see that there is an existing Pull Request that might pre-empt this one: https://github.com/code-ready/snc/pull/216
These changes to createdisk.sh are similar.  I made the modifications so that the build of snc for OCP should not require any changes.
To build snc for OKD you will set the following ENV vars: (For example)
export OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE="quay.io/openshift/okd:4.5.0-0.okd-2020-08-12-020541"
export OPENSHIFT_VERSION=4.5.0-0.okd-2020-08-12-020541
export BUNDLE_VERSION=${OPENSHIFT_VERSION}                                  # This is for building crc
export MIRROR=https://github.com/openshift/okd/releases/download     # Also used by crc
export OPENSHIFT_PULL_SECRET_PATH="/tmp/pull_secret.json"
export BASE_OS=fedora-coreos

The pull secret is fake:
cat << EOF > /tmp/pull_secret.json
{"auths":{"fake":{"auth": "Zm9vOmJhcgo="}}}
EOF

In createdisk.sh, BASE_OS defaults to rhcos.   Otherwise, it is used to distinguish between rhcos and fedora-coreos for disk image logic.
The logic for guestfish is:
    if [[ ${BASE_OS} == "rhcos" ]]
    then
        guestfish --remote <<EOF
add-drive $baseDir/$srcFile
run
luks-open $partition coreos-root
mount /dev/mapper/coreos-root /
zero-free-space /boot/
EOF
    else
        guestfish --remote <<EOF
add-drive $baseDir/$srcFile
run
mount $partition /
zero-free-space /boot/
EOF
    fi

/ok-to-test

@cgruver Can you please update the README file about how to create the OKD bundles.

export OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE="quay.io/openshift/okd:4.5.0-0.okd-2020-08-12-020541"
export OPENSHIFT_VERSION=4.5.0-0.okd-2020-08-12-020541

Do we need both of these, i think the release image is taken based on the release info of the particular release of OPENSHIFT_VERSION with the mirror set to github okd releases only OPENSHIFT_VERSION should be enough?

Error from the CI.
++ export GUESTFISH_PID
+ '[' 0 -ne 0 ']'
+ [[ '' == \r\h\c\o\s ]]
+ guestfish --remote
libguestfs: error: mount: mount exited with status 32: mount: /sysroot: unknown filesystem type 'crypto_LUKS'.
Failed to sparsify crc_libvirt_2020-09-04/crc-rmjhw-base, aborting
+ '[' 1 -ne 0 ']'
+ echo 'Failed to sparsify crc_libvirt_2020-09-04/crc-rmjhw-base, aborting'
+ exit 1

/retest

Replacing this draft with: https://github.com/code-ready/snc/pull/232


Work Files tool save modified changes on scene open prompt confusing

What happened?
There's been a note on the Work Files tool by one of our artists regarding it asking to save or don't save on opening another scene. Somehow this one artist tries to go too quick and ends up clicking the wrong button.
This is the current prompt:

What did the user expect?
He asked instead to change the buttons "Yes" and "No" to "Save" and "Don't Save" which makes it more similar to e.g. what Maya does by default.
Maya's default prompt:

Houdini's default prompt:

And the best UX reference, Paint:

It does make the specific buttons more explicit and seems more in line with the hosts. I am wondering whether others have heard this too or feel the same (or indifferent about it).
Any thoughts on this?

Sure, sounds good to me.

Never heard the complaint, but don't see a reason not to change it as you're suggesting.


#2869 upgrading h2 to 1.4.200

Fixes Issue #2869
Description of Change
Updated the checked in h2 database and updated the pom.
Have test cases been added to cover the new functionality?
no

This would resolve the failing test from https://github.com/jeremylong/DependencyCheck/pull/2718

@sellersj thank you for the PR - seriously. However, I'm debating the best way to incorporate this as every-time we have a breaking database change it causes a TON of issues because people don't read the release notes.  I suppose I could just start versioning inside the cli/data directory like we do within the maven and gradle data directories...

No worries at all and a totally understandable issue. In our CI/CD system I have it if the update fails to purge the directory and try to update it again. Hopefully the steps in the ticket will help any future work too.
Thanks again for all the great work.

I was trying to figure out how to put this into 6.2.0 - but this is going to end up being a breaking change for some users. As such, I'm holding off until 7.0.

this should no longer be merged, anything below 2.0.202 is vulnerable for CVE-2021-23463
see also #3894

@sellersj thank you for the detailed instructions on upgrading the H2 database. In order to move to the latest I had to make a few other changes and as such this PR has been superseded by #3928.


Don't require rbenv to build ruru

Instead, it queries the ruby directory from Ruby's RbConfig.

Hey @malept! Thank you, that's awesome!

This is great! I was working on my own patch using which, but this is better :+1:


Add destructuring to catch clause

Fixes #6636
I also moved location of error to be more accurate when there is type annotation

Not sure if this is considered type annotation?
try {
} catch ({message = 'foo'}) {
  message // type is string
}

/cc @panagosg7 anything here?


Don't strip commas when creating a new note

Hi,
IMHO, your plugin significantly improves working with people in Obsidian. Thank you!
However, there is a minor issue that continues to bother me. I prefer my people-notes to be in the format "lastName, firstName", and I write them in this way when using your plugin. For instance, I type "@Skywalker, Anakin" and then press Enter to create a new note.
The newly created note is named "Skywalker Anakin", with the comma missing. As a result, I always have to rename the file and adjust the title within the file, which is somewhat inconvenient. I would greatly appreciate it if the new note could be named exactly as I typed it after the '@' symbol.

Good catch! Should be fixed in 1.4.9


Initial window size is below minimum size on i3 window manager (DisplayServer regression)

Godot version
4.0beta10
System information
Arch Linux, X.org, i3 window manager
Issue description
The size of windows showing the Godot logo is initially very small, too small to show even the logo. They don't get bigger after their content is loaded, either.
This happens in the i3 window manager, which otherwise is pretty good at following standards like freedesktop. And the issue didn't occur in Godot 3, so I think something in the new version is to blame.
Steps to reproduce
Have this in ~/.config/i3/config to make Godot windows floating by default:
for_window [instance="^Godot_Engine$"] floating enable

Launch Godot 4:

Wait until the project manager becomes "visible":

Resize the window; it immediately snaps to its minimum size and can't be made smaller anymore:

(Black rectangle added afterwards, it does actually show my projects :))
Minimal reproduction project
n/a

Incorrect min. size should be fixed by https://github.com/godotengine/godot/pull/70863, not sure why initial size is not set, probably i3 specific issue.

Can confirm with i3, Ubuntu. Splash screens are tiny. Project Manager and Editor are resized when loaded to fill the content, but under the minimum. Editor is also not centered, but resizes on the spot towards bottom right.

The behaviour with 4.0beta11 is better than in 4.0beta10, probably thanks to #70863: when the tiny splash screen turns into the project manager, the window is now automatically resized (towards the bottom right) to its new minimum size.
The splash screen still starts out tiny though.

I continue to have this problem on RC 1.  Using xprop to see the window details of the running project, program specified size is set to 0x0 unless display/window/size/resiable is disabled, whereupon program specified size is correct, but also program specified minimum/maximum size are set (hence unresizable).  I have a hunch the whole thing would just work as expected if the program minimum size property would just get set when resizable is enabled, but for some reason it isn't.
#window resiable = false
$ xprop
_NET_WM_ICON(CARDINAL) = 	Icon (128 x 128):
	(not shown)

_NET_WM_NAME(UTF8_STRING) = "PokingAround (DEBUG)"
_NET_WM_DESKTOP(CARDINAL) = 2
_NET_WM_STATE(ATOM) =
WM_STATE(WM_STATE):
		window state: Normal
		icon window: 0x0
I3_FLOATING_WINDOW(CARDINAL) = 1
WM_NORMAL_HINTS(WM_SIZE_HINTS):
		program specified location: 384, 216
		program specified size: 1152 by 648
		program specified minimum size: 1152 by 648
		program specified maximum size: 1152 by 648
_NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_NORMAL
WM_CLASS(STRING) = "Godot_Engine", "PokingAround"
XdndAware(ATOM) = BITMAP
WM_PROTOCOLS(ATOM): protocols  WM_DELETE_WINDOW
WM_NAME(STRING) = "PokingAround (DEBUG)"
_NET_WM_PID(CARDINAL) = 17368

#window resiable = true
 $ xprop
_NET_WM_ICON(CARDINAL) = 	Icon (128 x 128):
	(not shown)

_NET_WM_NAME(UTF8_STRING) = "PokingAround (DEBUG)"
_NET_WM_DESKTOP(CARDINAL) = 2
_NET_WM_STATE(ATOM) =
WM_STATE(WM_STATE):
		window state: Normal
		icon window: 0x0
I3_FLOATING_WINDOW(CARDINAL) = 1
WM_NORMAL_HINTS(WM_SIZE_HINTS):
		program specified location: 0, 0
		program specified size: 0 by 0
_NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_NORMAL
WM_CLASS(STRING) = "Godot_Engine", "PokingAround"
XdndAware(ATOM) = BITMAP
WM_PROTOCOLS(ATOM): protocols  WM_DELETE_WINDOW
WM_NAME(STRING) = "PokingAround (DEBUG)"
_NET_WM_PID(CARDINAL) = 17867

@cptchuckles Thank you, that's great info! Based on that, I did some more debugging. Here's the code responsible:
https://github.com/godotengine/godot/blob/4848877b802b17f4ab1aecfde42c81a7cc9b6f08/platform/linuxbsd/x11/display_server_x11.cpp#L1640-L1645
It was added in a31b164071dd7af790d4b62057d9f9222285e59d, almost three years ago. Before this commit, setting the position and size hints was conditional on id != MAIN_WINDOW_ID. That check disappeared. If I put it back, the problem is solved for me. However, I don't think that's the correct fix.
This is called once, in _create_window:
https://github.com/godotengine/godot/blob/4848877b802b17f4ab1aecfde42c81a7cc9b6f08/platform/linuxbsd/x11/display_server_x11.cpp#L5109
It's worth noting that none of window_set_size, window_set_min_size and window_max_size get called at project manager startup. So i3 does the right thing here: it tries to honour Godot's silly request of a 0x0 window. The issue description "window size is below minimum size" is misleading since there is no minimum size.
Related: the settings display/window/size/viewport_width and display/window/size/viewport_height have no effect on the initial window size. It seems like window_set_size is never called when running the game from the editor either.
These sizes should normally be set from Window::_update_window_size:
https://github.com/godotengine/godot/blob/master/scene/main/window.cpp#L914-L916
The root window is automatically created by DisplayServer, so it's a special case. It turns out that window_id == -1 on the root Window object throughout startup, so the check window_id != DisplayServer::INVALID_WINDOW_ID fails, even if the window is long visible already.
Window::window_id is set to DisplayServer::MAIN_WINDOW_ID when receiving NOTIFICATION_ENTER_TREE, which is very late in the startup process:
https://github.com/godotengine/godot/blob/master/scene/main/window.cpp#L1116
Even then, _update_window_size is not called.
I'll send a PR to fix both these issues.


Suitable evaluation metrics and datasets for inverse rendering

Hi, thank you for your outstanding contributions. Indeed, inverse rendering requires some dedicated real datasets to evaluate its effectiveness, and you have pioneered this direction.
I have some thoughts on inverse rendering.
About the evaluation metrics: I believe that rendering tasks, such as novel-view synthesis and PBR rendering, are important metrics for assessing inverse rendering, reflecting the fidelity of the reconstruction. However, I think a more crucial metric for inverse rendering is the accuracy in decomposing materials (albedo/roughness/metallic), environment lighting, normals, and visibility. I've noticed that, although TensoIR has good rendering metrics, the decomposition of its individual components isn't perfect. It tends to bake shadows and indirect light into the albedo. It would be great if the dataset could include ground truths for albedo, roughness, and environment light (though I'm unsure how to obtain the real dataset's ground truth for albedo).
About the choice of objects in the dataset: I believe that the objects in the current method are mostly simpler single-surface objects. They don't have the complexity of self-occlusion and outdoor shadows like NeRF's hotdog/lego. I think if some more complex objects could be incorporated into the next work, it would provide a more scientific evaluation of the robustness of inverse rendering methods.
Here are the experimental results of TensoIR on some complex objects. The inherent challenge is that the method struggles with shadows caused by self-occlusion and reflections from indirect light. TensoIR, due to the lack of extensive priors on the decomposed components, tends to make the albedo and rendered color as close as possible.

Hi Ziyi, thanks for your great suggestions! For evaluation metrics, I agree that decomposed materials (albedo/roughness/metallic) are important ground truth for inverse rendering evaluation. In fact, we provide OLAT images which can be used to generate pseudo GT albedos and normal maps through photometric stereo, and we also provide ground truth illumination in SGs format.
For the choice of objects, our primary focus has been on encompassing a wide variety of surface materials, while we haven't prioritized geometry complexity. To make sure all lights are well calibrated and consistent, we capture all the objects in a controlled dark room lab setting,  thus eliminating any in-the-wild illumination in our dataset. The prospect of capturing in-the-wild data is an excellent consideration for our future endeavors. Thanks again for your insightful thoughts and valuable comments! :)


Domainaliases which are (Sub-)domains without www. prefix won't work with version 2.0.0

There is a problem with adding Domain-Aliases which are not using the www subdomain e.g. extranet.acme.com.
Let's encrypt then tries to resolve www.extranet.acme.com which leads to an error if that subdomain does not resolve to the same server and vhost.
ATM I can't see a way via GUI to prevent the www. subdomain being used for domain-aliases, at least if the main domain has it enabled.

I think they need to update the plugin, having issues here too.
e.g.
Error: Let's Encrypt SSL certificate installation failed: Invalid response from https://acme-v01.api.letsencrypt.org/acme/new-authz: Must agree to subscriber agreement before any further actions.
Type: urn:acme:error:unauthorized.

Could you please check the issue on 2.0.2 version of LE Extension?  It should be fixed now.

Nope, does not work:
Warnung: Failed to resolve challenge for www.subdomain.xxx.com. Details:
Challenge marked as invalid. Details: Invalid response from http://www.subdomain.xxx.com/.well-known/acme-challenge/
where www.subdomain.xxx.com is not a subdomain which resolves anyway. only "subdomain.xxx.com" resolves.
subdomain.xxx.com is an alias for domainyyy.com (which has activated to add www.domainyyy.com too)

can you reopen that issue?

Could you set log.filter.priority=7 in panel.ini, reproduce the issue and provide us with the panel.log records?

ahm, ok, the subdomain with the www. prefix resolves.
but to a completely different server, serving some custom error-page. and i do not have access to their dns as it is a 'foreign' domain.
edge-case i would like to say ...
So, if I check 'add www.maindomain.com', and i have several subdomains, where the www. prefix is NOT resolving at all, i get some fat warning boxes in yellow, but the subdomain-certificates without the www. prefix are at least issued and added. Thanks for that!

sorry for that 'edge-case' i help myself on this with adding a domain to the same directory of the webserver. not nice, but until the customer does not get the dns-records clean, i can live with that ... ;)
so from my side: you can keep this issue as closed.
Well done, many thanks!


V2 Api changes

What are you plans to support the new (March 2016) v2 API with higher rate limits?

I didn't know there was a new api.  I'd be happy to merge pull requests that work with the new api if you fee like putting in the work.

I've already started looking into the upgrade and forked the repo as I prefer the process model you've implemented over the other Freshdesk (SN) package.
With respect the the changes... a lot has changed in both methods and models. Considering the following (emphasis mine), an upgrade to V2 is the best path.

API deprecation and breaking change policies
The existing version of the APIs (v1.0) has been deprecated. There will be no further updates or releases. However, the v1 APIs will continue to be functional until the end of September.
We will also notify you 60 days in advance before a breaking change comes into effect.

It's quite possible that the v1 API is still working, but its very probable that it will be turned off at some point in the very near future.
Looking at the code in its current state, I'd say that the implementation is very young and has a lot of limitations in terms of making this a useful package (for my use case that is)

GET T methods
GET List methods
Create new models for the updated v2 API objects

Freshdesk just notified that the v1 API is end-of-life in July.  Has anyone started patching to v2?

I've stopped working on this due to lack of time.  If anyone feels like taking up the mantle, by all means, feel free.

I don't think this works anymore without upgrading to API v2:


Such a good idea.

Just have to say that this is such a smart idea. We’ll done! :)

That’s all. Just wanted to express my gratitude.

Thank you for the kind words 😊


nginx + v3: high CPU usage on rule 200001

I'm not sure if this issue was already reported. Anyway:
What reported here https://github.com/SpiderLabs/owasp-modsecurity-crs/issues/1133 seems to be related to the rule 200001 and the requestBodyProcessor=JSON on each request with Content-Type: application/json.
With a long JSON string in the request body, the rule 200001 takes a very long time to process it, and the nginx worker CPU usage stuck at 100% until it finishes.
Logs and dumps
Using an 800 Kb JSON file as request body, and sent with content-type application/json the request took 83 seconds:
curl -s -H 'Content-Type: application/json' -d @test.json 'http://localhost' -w @curl-format.txt
host localhost upstream:
    time_namelookup:  0.005550
       time_connect:  0.006125
    time_appconnect:  0.000000
   time_pretransfer:  0.011318
      time_redirect:  0.000000
 time_starttransfer:  0.014967
                    ----------
         time_total:  83.675212

Just replacing the content-type value with application/x-www-form-urlencoded, the request took just 2 seconds:
curl -s -H 'Content-Type: application/x-www-form-urlencoded' -d @test.json 'http://localhost' -w @curl-format.txt
host localhost upstream:
    time_namelookup:  0.005729
       time_connect:  0.006164
    time_appconnect:  0.000000
   time_pretransfer:  0.006292
      time_redirect:  0.000000
 time_starttransfer:  0.012784
                    ----------
         time_total:  2.071719

To Reproduce

download test.json
create curl-format.txt as following

    time_namelookup:  %{time_namelookup}\n
       time_connect:  %{time_connect}\n
    time_appconnect:  %{time_appconnect}\n
   time_pretransfer:  %{time_pretransfer}\n
      time_redirect:  %{time_redirect}\n
 time_starttransfer:  %{time_starttransfer}\n
                    ----------\n
         time_total:  %{time_total}\n

send request to nginx with content-type application/json and the test.json content as the request body:

$ curl -v -H 'Content-Type: application/json' -d @test.json 'http://localhost' -w @curl-format.txt

Server:

ModSecurity - v3.0.3-45-g145f2f35 for Linux
Modsecurity-nginx 1.0.0
nginx 1.13.6

Hey @theMiddleBlue,
We had a similar issue in the past that was brought on the Nginx-connector issue tracker: https://github.com/SpiderLabs/ModSecurity-nginx/issues/89. This was found to be resolved a number of performance improvements added last year.
Can you re-run your tests without the CRS loaded? With CRS it was taking a significant amount to process, but with the basic configuration (which includes rule 200001 to activate JSON parsing), it was taking only 2.3 seconds here using that measurement model:
    time_namelookup:  0.000516
       time_connect:  0.002522
    time_appconnect:  0.000000
   time_pretransfer:  0.002735
      time_redirect:  0.000000
 time_starttransfer:  0.003224
                    ----------
         time_total:  2.324432

It's worth mentioning that this payload as is could trigger a 412 error due to the default value of SecRequestBodyNoFilesLimit.
But I still stumbled upon a weird behaviour (Empty reply from server!?) when running this against ModSec 2.9.x with the CRS. Without the CRS it runs fine.
Can you please let us know what you get if you run this against 2.9?
Maybe a good approach to identify any rule which might be using causing the slowdown is using the benchmark  and SystemTap scripts and plot in a flame graph like this:

I tested this with modsecurity 3.0.3, nginx 1.15.8, modsecurity-nginx 1.0.0 and crs 3.1.0.
Actually the problem is not the JSON parser itself. The real issue is that a relatively small JSON payload can generate thousands of arguments, which fill the ARGS and ARGS_NAMES collections, and then the OWASP CRS rules spend a lot of matching all of these values. This is why disabling the JSON processing makes modsecurity much faster. There is no single root cause, just the total complexity. (I can share the systemtap output to back this).
Unfortunately it makes the JSON processor completely unusable with the CRS. I see no other solution than completely disabling JSON processing, because my application relies on large arbitrary JSON requests, and the alternative is a huge DoS vulnerability in the http server.

Hi, @theMiddleBlue
Thank you for raise this up. Considering the comments from @victorhora and @jleproust I think it is safe to close that issue. If you think otherwise, please open it again within your concerns.

Well, it's still an issue and the only usable fix for now is my PR #2060, right? Maybe we should keep it open as a reference until we merge it or find a better solution?

Thanks for the work on this issue @jleproust!
We had to stop using ModSecurity due to request timeouts caused by this. Is there an estimate when #2060 will be merged and released?

@goweiwen You're welcome! I have debian 9 and ubuntu 16.04 packages if you want to test.


Can't access the page for 2021 survey

Can't access the page for 2021 survey.

Sorry, looks like scaling issues. I'm scaling up, hopefully you can try again in a couple minutes and it should be better.

Not working for me just now, getting the same error


 The referenced thread doesn't say it's a bad idea to sort, just that you have to be aware of how sorts & queries will interact with the indexes you have, which is going to be true for pretty much any query optimizer for any DB.

On Wed, Feb 29, 2012 at 3:15 PM, Forrest L Norvell
<EMAIL_ADDRESS>wrote:

Can you expand on why you think it's stupid? The referenced thread doesn't say it's a bad idea to sort, just that you have to be aware of how sorts & queries will interact with the indexes you have, which is going to be true for pretty much any query optimizer for any DB.

Reply to this email directly or view it on GitHub:
https://github.com/LockerProject/Locker/issues/890#issuecomment-4246982

Fixed in https://github.com/LockerProject/Locker/commit/87d6852032aca2d70565c5d07004c1fdb2982c78


PublishBuildArtifacts fails silently on +, %, {, or } in ArtifactName

Required Information
Question, Bug, or Feature?  Bug
Enter Task Name: PublishBuildArtifactsV1
Environment

Server - TFS on-premises

Version Azure DevOps Server 2020 Update 1.1

Agent - Private

Red Hat Enterprise Linux Workstation release 7.9 (Maipo)
Agent.Version 2.202.0

Issue Description
Setup
I'm using the PublishBuildArtifactsV1 task to publish downloadable test logs as build artifacts to work around https://github.com/microsoft/azure-pipelines-tasks/issues/16696. I have several jobs within a multi-configuration pipeline that are similar but use different cmake commands. Rather than maintain and remember a mapping between cmake ../command -Dwith=special+characters and a mangled version of that name, I'm using the job name directly as the artifact name. In the excerpts below, each .yaml includes the template below it.
jobs:
- template: ./CMakeBuildWorkflowOneJob.yaml
  parameters:
    jobName: SimpleDescriptiveString1
    cmakeArguments: ../command -Dwith=special+characters
- template: ./CMakeBuildWorkflowOneJob.yaml
  parameters:
    jobName: SimpleDescriptiveString2
    cmakeArguments: ../different/command -Dwith=different_special+characters

jobs:
- job: ${{ parameters.jobName }}
  displayName: ${{ parameters.cmakeArguments }}
  steps:
  - template: ./CmakeBuildWorkflowSteps.yaml

steps:
  ...
  - template: ./PublishTestResults.yaml
    parameters:
      publishName: '$(Agent.JobName)'

steps:
  ...
  - task: PublishBuildArtifacts@1
    displayName: "Publish Artifact: ${{ parameters.publishName }}"
    inputs:
      artifactName: '${{ parameters.publishName }} logs'

The Good
ArtifactNames that contain alphanumeric characters, spaces, and some special characters (-, =, (, and )) successfully upload the artifacts.
The Bad
ArtifactNames that contain the special character + silently fail, passing the Publish Build Artifacts task step, generating a expandable file tree in the Artifacts tab of the pipeline summary, but then providing a "Server Error 404 - File or directory not found. The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable." error message when I try to download the artifacts.

Requested Fix

Support + special character in the artifactName argument of PublishBuildArtifacts
or
Fail the pipeline task if special characters are detected in artifactName that would make the artifacts undownloadable
or
Provide a way to remove special characters like + from predefined variables like ${Agent.JobName}?

Task logs
I can't provide logs from my company machine, but should be able to recreate this with a public project if that would help.

Understood! I took a stab at solution 2 in #16730

Ok, I confirmed in a public test project that this only happens for PublishBuildArtifacts, not for PublishPipelineArtifacts
https://dev.azure.com/codytylermartin/Codym48/_git/cmake_saver/pullrequest/3
https://dev.azure.com/codytylermartin/Codym48/_build/results?buildId=42&view=artifacts&pathAsName=false&type=publishedArtifacts

Clicking the ❌ leads to

Which means solutions 1 and 3 probably aren't worth it since PublishBuildArtifacts is deprecated.

Testing shows PublishBuildArtifacts, but not PublishPipelineArtifacts, will false pass on % in the ArtifactName, too:
{"$id":"1","innerException":null,"message":"A potentially dangerous Request.Path value was detected from the

client (%).","typeName":"System.Web.HttpException, System.Web","typeKey":"HttpException","errorCode":0,"eventId":0}
And { and } (generate an empty artifact).

@LiliaSabitova is there any chance we can complete my PR to close this?


etcd-mesos scheduler doesnt clean up healthcheck tcp socket

etcd version 2.2.3, mesosphere/etcd-mesos:0.1.3
etcd-mesos container leaves open sockets (we saw over 42,000k) and this eats up ports and bleeds into other port ranges eventually killing Spartan and therefore the worker nodes health.
1026 / 1027 is a ports running etcd
{
"name": "_etcd-server._client.etcd-ptx.mesos.",
"host": "etcd-server-8hw4j-s4.etcd-ptx.mesos.:1026",
"rtype": "SRV"
}

{
"name": "_etcd-server._client.etcd-ptx.mesos.",
"host": "etcd-server-yemwe-s0.etcd-ptx.mesos.:1027",
"rtype": "SRV"
}

{
"name": "_etcd-server._client.etcd-ptx.mesos.",
"host": "etcd-server-6rfx8-s6.etcd-ptx.mesos.:1026",
"rtype": "SRV"
}

$ sudo lsof -i -P -n  | grep -oc :1026
10527

$ sudo lsof -i -P -n  | grep -oc :1027
3905

You can see 10k open, we saw spartan killed at 40K
$  sudo lsof -i -P -n  | grep 1026
px        131653         root    5u  IPv4 73405621      0t0  TCP <IP_ADDRESS>:36338-><IP_ADDRESS>:1026 (ESTABLISHED)
px        131653         root    7u  IPv4 73394523      0t0  TCP <IP_ADDRESS>:36340-><IP_ADDRESS>:1026 (ESTABLISHED)
px        131653         root   24u  IPv4 74751557      0t0  TCP <IP_ADDRESS>:37012-><IP_ADDRESS>:1026 (ESTABLISHED)
px        131653         root   26u  IPv4 73414087      0t0  TCP <IP_ADDRESS>:36470-><IP_ADDRESS>:1026 (ESTABLISHED)
px        131653         root   30u  IPv4 74757811      0t0  TCP <IP_ADDRESS>:37640-><IP_ADDRESS>:1026 (ESTABLISHED)
px        131653         root   31u  IPv4 74740409      0t0  TCP <IP_ADDRESS>:36816-><IP_ADDRESS>:1026 (ESTABLISHED)
etcd-meso 168715         root   13u  IPv4 74566478      0t0  TCP <IP_ADDRESS>:37786-><IP_ADDRESS>:1026 (ESTABLISHED)
etcd-meso 168715         root   15u  IPv4 74693374      0t0  TCP <IP_ADDRESS>:37873-><IP_ADDRESS>:1026 (ESTABLISHED)
etcd-meso 168715         root   17u  IPv4 74693376      0t0  TCP <IP_ADDRESS>:38010-><IP_ADDRESS>:1026 (ESTABLISHED)
etcd-meso 168715         root   18u  IPv4 74566510      0t0  TCP <IP_ADDRESS>:58952-><IP_ADDRESS>:1026 (ESTABLISHED)
etcd-meso 168715         root   20u  IPv4 74783939      0t0  TCP <IP_ADDRESS>:59134-><IP_ADDRESS>:1026 (ESTABLISHED)
etcd-meso 168715         root   21u  IPv4 74786210      0t0  TCP <IP_ADDRESS>:59136-><IP_ADDRESS>:1026 (ESTABLISHED)
etcd-meso 168715         root   22u  IPv4 74768044      0t0  TCP <IP_ADDRESS>:38198-><IP_ADDRESS>:1026 (ESTABLISHED)
etcd-meso 168715         root   24u  IPv4 74759147      0t0  TCP <IP_ADDRESS>:38514-><IP_ADDRESS>:1026 (ESTABLISHED)
etcd-meso 168715         root   27u  IPv4 74755262      0t0  TCP <IP_ADDRESS>:59608-><IP_ADDRESS>:1026 (ESTABLISHED)
etcd-meso 168715         root   30u  IPv4 74793585      0t0  TCP <IP_ADDRESS>:38952-><IP_ADDRESS>:1026 (ESTABLISHED)
etcd-meso 168715         root   31u  IPv4 74800159      0t0  TCP <IP_ADDRESS>:39084-><IP_ADDRESS>:1026 (ESTABLISHED)
etcd-meso 168715         root   32u  IPv4 74800160      0t0  TCP <IP_ADDRESS>:60026-><IP_ADDRESS>:1026 (ESTABLISHED)
etcd-meso 168715         root   33u  IPv4 74800195      0t0  TCP <IP_ADDRESS>:39206-><IP_ADDRESS>:1026 (ESTABLISHED)
etcd-meso 168715         root   34u  IPv4 74800196      0t0  TCP <IP_ADDRESS>:60150-><IP_ADDRESS>:1026 (ESTABLISHED)
etcd-meso 168715         root   35u  IPv4 74800228      0t0  TCP <IP_ADDRESS>:39346-><IP_ADDRESS>:1026 (ESTABLISHED)
etcd-meso 168715         root   36u  IPv4 74800229      0t0  TCP <IP_ADDRESS>:60288-><IP_ADDRESS>:1026 (ESTABLISHED)
etcd-meso 168715         root   37u  IPv4 74801560      0t0  TCP <IP_ADDRESS>:39488-><IP_ADDRESS>:1026 (ESTABLISHED)```

I wrote a quick fix: https://github.com/minyk/etcd-mesos/commit/2b54e65119aed4c8ea5112c8f3927fab80194672 Just client.Close(), then connection numbers are very stable(~20) for now.


DESTDIR not respected during zig build

Using the DESTDIR as advertised in PACKAGING.md does not work, it still tries to write things directly to the prefix directory. Only using --prefix "$DESTDIR/usr" seems to work for me.

This is because b.install_prefix is used in https://github.com/ghostty-org/ghostty/blob/a8e5eef11cc67f87f445626f9ca2993373774bf8/build.zig#L483-L499, which does not account for DESTDIR unlike b.install_path. One solution can be to use b.addInstallDirectory here instead of calling cp, like it's done in Gentoo patch:
-                const copy_step = RunStep.create(b, "copy terminfo db");
-                copy_step.addArgs(&.{ "cp", "-R" });
-                copy_step.addFileArg(path);
-                copy_step.addArg(b.fmt("{s}/share", .{b.install_prefix}));
-                b.getInstallStep().dependOn(&copy_step.step);
+                const install_dir_step = b.addInstallDirectory(.{
+                    .source_dir = path,
+                    .install_dir = .prefix,
+                    .install_subdir = "share/terminfo",
+                });
+                b.getInstallStep().dependOn(&install_dir_step.step);

Otherwise, as a fast fix just replace install_prefix with install_path.


cannot upload files such as .jpg, .jpeg, .png, .pdf, .doc

I am using ModSecurity v3.0, and I have applied it to Ubuntu v22.4 to secure a web server.
The installation was successful, but there is an issue when the admin tries to update the website content. They cannot upload files such as .jpg, .jpeg, .png, .pdf, .doc, and so on. Is there a solution?
For example, when uploading a file, it shows: "The uploaded file was only partially uploaded."

What does the error load shows? If ModSecurity is blocking anything, it will be logged in the site error logs.

ModSecurity: Access denied with code 200 (phase 2). Matched "Operator Eq' with parameter 0' against variable REQBODY_ERROR' (Value: 1' ) [file "/etc/apache2/modsecurity.d/modsecurity.conf"] [line "64"] [id "200002"] [rev ""] [msg "Failed to parse request body."] [data "Multipart parsing error: Multipart: Final boundary missing."] [severity "2"] [ver ""] [maturity "0"] [accuracy "0"] [hostname "domain.com"] [uri "/wp-admin/async-upload.php"] [unique_id "1695711906"] [ref "v2070,1v2070,1v2070,1v2070,1v2070,1v2070,1v2070,1v2070,1v2070,1v2070,1v2070,1v2070,1v2070,1v2070,1v2070,1v2070,1v2070,1"]

What web server are you using? Nginx or Apache?

Server version: Apache/2.4.41 (Ubuntu)

ModSecurity: Access denied with code 200 (phase 2). Matched "Operator `Eq' with parameter `0' against variable `REQBODY_ERROR' (Value: `1' ) [file "/etc/apache2/modsecurity.d/modsecurity.conf"] [line "64"] [id "200002"] [rev ""] [msg "Failed to parse request body."] [data "Multipart parsing error: Multipart: Final boundary missing."] [severity "2"] [ver ""] [maturity "0"] [accuracy "0"] [hostname "domain.com"] [uri "/wp-admin/async-upload.php"] [unique_id "1695711906"] [ref "v2070,1v2070,1v2070,1v2070,1v2070,1v2070,1v2070,1v2070,1v2070,1v2070,1v2070,1v2070,1v2070,1v2070,1v2070,1v2070,1v2070,1"]

You can disable the rule 200002. Unfortunately it generates many false positive results.

Does disabling rule 200002 affect its security?

I don't think so.
The other chance is that you inspect the whole request to find the root cause. (I bet you will find a wrong behavior of multipart parser.)

Apart from @airween suggestion, using ModSecurity 3 with Apache used to be discouraged (not sure about the latest guidelines). It is better to use ModSecurity 2.9 with Apache and ModSecurity 3.x with nginx along with the nginx connector.

Per the comment from @void-in , ModSecurity v3 is not recommended for use with Apache -- the Apache connector required to do so is simply not considered production ready. So, yes, it continues to be the recommendation that, with Apache, to use ModSecurity v2.9.x.
(For ModSecurity implementations as a whole, the only case I can think of that causes such an issue (when the request is compliant) is if one is using size limits but with SecRequestBodyLimitAction ProcessPartial. That configuration option is not recommended.


Add Mongolian National University

It is a Mongolian university named 'Mongolian National University'.
Home page: https://mnun.edu.mn/
For IT courses look here: https://mnun.edu.mn/school-of-information-technology-design/
For domain proof look at the contacts page: https://mnun.edu.mn/contacts/

@erbold-bu First stage of verification passed, official domain is facebook.com as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision. Proof of domain ownership: https://fr-ca.facebook.com/MNUniversity/

@erbold-bu Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Fix verdaccio build

Closes
✅ Pull Request Checklist:

[ ] Included link to corresponding React Spectrum GitHub Issue.
[ ] Added/updated unit tests and storybook for this change (for new code or code which already has tests).
[ ] Filled out test instructions.
[ ] Updated documentation (if it already exists for this component).
[ ] Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

🧢 Your Project:

closing for https://github.com/adobe/react-spectrum/pull/3851


build: Revert to using @_implementationOnly for all BoringSSL modules

Motivation
The 3.5.0 release has been causing some compilation failures for downstream projects that depend on other packages that also vendor in a copy of BoringSSL.
This is likely because we stopped using @_implementationOnly when importing our internal CCryptoBoringSSL target, which we did because we moved the ArbitraryPrecisionInteger and FiniteFieldArithmeticContext types, that were previously internal to Crypto, into CryptoBoringWrapper so they could be used in _CryptoExtras to implement RSABSSA.
While Swift Crypto goes to some lengths to avoid clashing with other vendor'd copies of BoringSSL by prefixing its symbols, it clearly isn't enough and we've heard reports of downstream projects failing to build.
We have shipped one patch release, 3.5.1, with a fix to the vendor script that has resolved a subset of adopters, it hasn't resolved everything.
At this stage, I'd like to propose that we mitigate the impact of the issue and give us time to revisit how we vendor and import the C module, rather than us chasing a long tail of reported issues downstream.
Modifications

Moved ArbitraryPrecisionInteger and FiniteFieldArithmeticContext back into Crypto as internal types, but bringing along the additional operations that were added as part of 3.5.0.
Revert to using @_implementationOnly imports of CCryptoBoringSSL and CCryptoBoringSSLShims everywhere.
Share these two files with _CryptoExtras by symlink.
Update CMakeLists.txt to account for new location of files in Crypto.
Update CMakeLists.txt to account for new symlinks in _CryptoExtras.
Update CMake script to accommodate use of symlinks.

Result
Greater confidence that we won't have broken downstream projects due to BoringSSL symbol clashes.

One example of a project that currently does not build with 3.5.1 https://github.com/vapor/penny-bot. Here is the dependabot CI run that failed for 3.5.1: https://github.com/vapor/penny-bot/actions/runs/9767425786/job/26962669715?pr=211
I have confirmed I can reproduce that failure locally and that this patch resolves the issue.

//cc @MahdiBM

This is very troubling. We did a fair bit of analysis that tried to identify a difference between the @_implementationOnly and non-@_implementationOnly use-cases, and couldn't identify any meaningful difference.
Can we identify one now?


Updated Walkthrough Spelling

@da5is : Thanks for your contribution! The author, @KumudD, has been notified to review your proposed change.

#sign-off


Numbers 0 are not accepted in money type

I realized that when typing the number zero using the money type it just doesn't insert the value correctly.
Does this problem occur only to me?

+1

Me too!

+1

options={{
precision: -1,
}}


Text added to RichTextLabel using append_bbcode is removed if the screen is resized

Godot version:

3.1 master
OS/device including version:

Windows 10 Pro
Issue description:

adding text to a rich text label using append_bbcode and resizing the window causes the text to be deleted
Steps to reproduce:
this line works good:
	Messages.bbcode_text += new_bbcode
this line works bad
	Messages.append_bbcode(new_bbcode)

probably related to #24173

yeah, calling update makes new text added to be discarded, the same that when window is resized

Closing as duplicate of #24173 then.

This issue is not a duplicate of #24173 as that issue was fixed yet this one still persists.  24173 uses the bbcode_text property on RichTextLabel which seems to be fixed, while this one uses the append_bbcode method which is still buggy!  I think this issue should be reopened.

Although this issue is fixed in Godot 4.0 as the whole BBCode system had major changes.

Hmm. I can not replicate this issue outside of my project for some reason. The only thing I can think of is that I'm using async functions and the append_bbcode method is called at the same time twice on the same node.

After some more testing, I managed to recreate the issue outside of my project. The issue seems to only occur when using a custom (Dynamic) font.

https://user-images.githubusercontent.com/104794884/209484429-52c7aa16-9e26-4d33-a1ad-9490c2864edc.mp4
Showcase of issue


Add a show-paper-key path to provisioning flow

@keybase/react-hackers
There's a (fairly common) provisioning path that was missing the show-paper-key stage -- when you have a keybase account with no device keys and login through the GUI app.  Before this PR, the displayPrimaryPaperKey RPC is unhandled and we just move to being logged in without ever showing the user their new paper key.
After this PR, we go to the same show-paper-key screen that signup uses as its Success page, but now parameterized to say appropriate things for our case.
I'm not going to merge this until I see whether this breaks the signup flow; I can test that once DESKTOP-818 is fixed.

 I think that has everything you need and you won't need to mess with the connectstuff.

Thanks, followed all of the review comments!  There's way less changed code now.  Another look for thumbs?

looking

:+1:


win7 cmd create error;

system:win7;
error:The filename, directory name, or volume slogan method is not correct.

Please reopen this if it still happens.

the problem still happens

Are you using latest version? only create-vue-app is available now, it works fine for me on windows 10


Consider adding a TechEmpower comparison for Sapper

Hi!
I noticed that Sapper is missing from https://github.com/TechEmpower/FrameworkBenchmarks/ - are you interested in adding a benchmark there? Alternatively, I can add one if you're not against it :)

Yes, welcome to do it, thank you.


sources icons missing

I have an issue with sources icons:

Installed via packer:
	use({
		"nvim-neo-tree/neo-tree.nvim",
		branch = "v2.x",
		requires = {
			"nvim-lua/plenary.nvim",
			"nvim-tree/nvim-web-devicons",
			"MunifTanjim/nui.nvim",
		},
	})

Config:
require("neo-tree").setup({
	source_selector = {
		winbar = true,
		content_layout = "center",
	},
	filesystem = {
		filtered_items = {
			visible = false, -- when true, they will just be displayed differently than normal items
			hide_dotfiles = false,
			hide_gitignored = true,
			hide_hidden = true, -- only works on Windows for hidden files/directories
			hide_by_name = {
				".DS_Store",
				"thumbs.db",
				--"node_modules",
			},
			hide_by_pattern = {
				--"*.meta",
				--"*/src/*/tsconfig.json",
			},
			always_show = { -- remains visible even if other settings would normally hide it
				--".gitignored",
			},
			never_show = { -- remains hidden even if visible is toggled to true, this overrides always_show
				--".DS_Store",
				--"thumbs.db",
			},
			never_show_by_pattern = { -- uses glob style patterns
				--".null-ls_*",
			},
		},
	},
	window = {
		position = "left",
		width = 40,
		mapping_options = {
			noremap = true,
			nowait = true,
		},
		mappings = {
			["<space>"] = {
				"toggle_node",
				nowait = false, -- disable `nowait` if you have existing combos starting with this char that you want to use
			},
			["<2-LeftMouse>"] = "open",
			["<cr>"] = "open",
			["<esc>"] = "revert_preview",
			["P"] = { "toggle_preview", config = { use_float = true } },
			["S"] = "open_split",
			["s"] = "open_vsplit",
			-- ["S"] = "split_with_window_picker",
			-- ["s"] = "vsplit_with_window_picker",
			["t"] = "open_tabnew",
			-- ["<cr>"] = "open_drop",
			-- ["t"] = "open_tab_drop",
			["w"] = "open_with_window_picker",
			--["P"] = "toggle_preview", -- enter preview mode, which shows the current node without focusing
			["C"] = "close_node",
			["z"] = "close_all_nodes",
			--["Z"] = "expand_all_nodes",
			["a"] = {
				"add",
				-- some commands may take optional config options, see `:h neo-tree-mappings` for details
				config = {
					show_path = "none", -- "none", "relative", "absolute"
				},
			},
			["A"] = "add_directory", -- also accepts the optional config.show_path option like "add".
			["d"] = "delete",
			["r"] = "rename",
			["y"] = "copy_to_clipboard",
			["x"] = "cut_to_clipboard",
			["p"] = "paste_from_clipboard",
			["c"] = "copy", -- takes text input for destination, also accepts the optional config.show_path option like "add":
			-- ["c"] = {
			--  "copy",
			--  config = {
			--    show_path = "none" -- "none", "relative", "absolute"
			--  }
			--}
			["m"] = "move", -- takes text input for destination, also accepts the optional config.show_path option like "add".
			["q"] = "close_window",
			["R"] = "refresh",
			["?"] = "show_help",
			["<"] = "prev_source",
			[">"] = "next_source",

			["Y"] = function(state)
				local node = state.tree:get_node()
				local content = node.path
				-- relative
				-- local content = node.path:gsub(state.path, ""):sub(2)
				vim.fn.setreg('"', content)
				vim.fn.setreg("1", content)
				vim.fn.setreg("+", content)
			end,
		},
	},
})

Funny. I came to report exactly the same issue. I even get the same icons you do displayed on neovim tabs.
I know you can custom some stuff on
default_componen_config { icon }

But I cannot find anything to customize the tabs.

These kinds of issues are almost always due to your terminal not having a proper nerd font available. Do you know what font your terminal is using?
@Zeioth see :h neo-tree-source-selector, that details how to set the name of each tab in your source selector. The icons being displayed are just characters and thus are part of the "source selector" name.

Thank you so much @miversen33 that did the trick

Solution:
(Instead of geticon you can just use a string)
{
 opts = {
      sources = { "filesystem", "buffers", "git_status" },
      source_selector = {
        sources = {
          {
            source = "filesystem",
            display_name = get_icon "DefaultFile",
          },
          {
            source = "buffers",
            display_name = get_icon "Ellipsis",

          },
          {
            source = "git_status",
            display_name = get_icon "Git",

          },
      }
}
}

@nhat-vo why did we close this issue? OP has not responded with any of the information I requested a few days ago.

Ah my bad. I thought @Zeioth was the OP and the issue was solved for him

@Zeioth solution references some get_icon, where i can require it?

@coffebar That is specifically for AstroVim. If you are not using that you can use custom icons. You can have a look at https://www.nerdfonts.com/cheat-sheet for a list of icons.

Solution is telling you to use an string if you are not on astrovim, like this.
{
   opts = {
        sources = { "filesystem", "buffers", "git_status" },
        source_selector = {
          sources = {
          { source = "filesystem", display_name = "A" },
          { source = "buffers", display_name = "B" },
          { source = "git_status", display_name = "C" },
          { source = "diagnostics", display_name = "D" },
        },
  }
}

Just paste a unicode icon you like instead of the letter.

good, thanks!


fix: clean magic value, and update if-else to switch

Description
This PR...

clean magic value, and update if-else to switch

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
Cleanup (Code refactoring and cleanup, that may add test cases)
[ ] build/CI

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
Trivial

Screenshots (if appropriate):
How Has This Been Tested?

How did you try to break this feature and the system with this change?

@blueorangutan package

@DaanHoogland a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el7 ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 9099

@blueorangutan test alma9 kvm-alma9

@DaanHoogland a [SL] Trillian-Jenkins test job (alma9 mgmt + kvm-alma9) has been kicked to run smoke tests

[SF] Trillian test result (tid-9656)
Environment: kvm-alma9 (x2), Advanced Networking with Mgmt server a9
Total time taken: 53600 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr8848-t9656-kvm-alma9.zip
Smoke tests completed. 127 look OK, 2 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

test_02_enableHumanReadableLogs
Error
0.16
test_human_readable_logs.py

test_03_secured_to_nonsecured_vm_migration
Error
155.35
test_vm_life_cycle.py

test_04_nonsecured_to_secured_vm_migration
Error
274.39
test_vm_life_cycle.py

suggestion:
use EnumUtils.getEnumIgnoreCase with a default value

@cheng102e , will you replace the switch statement?


Promise never rejected on missing files

The following call to load a file that does not exist always results in the System.import Promise to be fulfilled. But since something bad happened it should be rejected!
System.import('./styles/does-not-exist.css!').then(
  function(){console.log('ok');},    // onFulfilled
  function(){console.log('oh no');}  // onRejected
);
// => 'ok'

If the promise would be rejected, I could try something else or notify the user or whatever. But as it is now I do not even know that it failed at all.

Thanks, I've fixed this in 0.1.18.


fix bad stretching

https://github.com/plugget/plugget-unreal-plugin/issues/15 duplicate

fixed


Format 14 cmaps needed for Noto Color Emoji font

In order to do easier font selection, supporting cmap format 14 tables in the Noto Color Emoji font for the variation sequences defined in Unicode would be very useful.
The exhaustive list is at http://www.unicode.org/Public/UCD/latest/ucd/StandardizedVariants.txt (the sequences whose second field is "emoji style", which is the same as all sequences ending in FE0F).
/cc @raphlinus @behdad @dougfelt @xiangyexiao

/cc @nona-google

/cc @agustinfz


Silverstripe 5 support

Checked against an Auth0 installation and it seems to work OK.  The league/oauth-client is still on major ^2 upstream, so the dependency doesn't need to be changed.

Thanks @elliot-sawyer


Fix frontstore order details crashing when variant was deleted

This fixes #2501 and also fix the invalid variable in fulfilled lines (fulfilled_line.variant -> fulfilled_line.order_line.variant).
As mentioned in #2501, there should not be any link to the product (variant); I dropped the <a> tag to order lines that no longer have a variant associated to them.
Thus, some changes on the structure were made. I decided to move the class order-details__product__description that was used for the product name of the order line (under <span>); this was moved to wrap the order lines first column (thumbnail and product name). Instead of selecting the product name by this class, it is now selecting the span tag.
Those changes allowing to more easily select the whole first column instead of selecting it by the tag a or the bootstrap column, thus preventing from being too dependent over the template structure or introducing new classes.
Pull Request Checklist

[x] Privileged views and APIs are guarded by proper permission checks.
[x] All visible strings are translated with proper context.
[x] All data-formatting is locale-aware (dates, numbers, and so on).
[x] Database queries are optimized and the number of queries is constant.
[x] The changes are tested.
[x] The code is documented (docstrings, project documentation).

Not sure if the rebase messed up with the history.

That way we could make the history even cleaner and get rid of "merge" commits and keep only your actual work.

Thank you, that must be that. I will do that next time instead of the standard rebase.


Use Java 8 (Lambdas) in Selenide

This ticket is registered for brainstorming. What could be lambdas useful for?
Some ideas:

Use predicate as a condition:

$("div").shouldBe(se -> se.getText().startsWith("Dear client "));

Run tests inside window/tab/frame:

inWindow("my window title", w -> {....});
inFrame("my frame name", f -> {....});

Your ideas?...

I have not come across a need for Lambdas in Selenide.
ElementsCollection already has Stream, so that is all I need.


[Bug] LoRA Finetuned model is not generating any text.

Checklist

[X] 1. I have searched related issues but cannot get the expected help.
[ ] 2. The bug has not been fixed in the latest version.
[ ] 3. Please note that if the bug-related issue you submitted lacks corresponding environment info and a minimal reproducible demo, it will be challenging for us to reproduce and resolve the issue, reducing the likelihood of receiving feedback.

Describe the bug
I finetuned the model InternVL-2B with LoRA and uploaded the model to hugging face by copying the missing scripts from original model.. i uploaded it on https://huggingface.co/shivavardhineedi/my_mini_internVL_lora
when i try to inference it... i get:

i see the model is merged model anyways... there is no adapter_config.json... so no need to handle with peft_model module... but why is this not generating any repsonse?
Reproduction
finetuned with 2nd_finetune documentation... and uploaded the output from work_dir to hugging face... but it doesnt work
Environment
just as mentioned in documentation

Error traceback
No response

Have you tried your merged model with transformers code（official demo)? You should try that first and it will check whether the merged model is correct or not.

Yeah... it didnt work with transformers as well

@irexyc i did also do python tools/merge.py   and still no output... why is my model not getting weights?

I think lmdeploy doesn't have the tools/merge.py file. You should first make sure the model could generate normal results with transformers api.


Collision not working with Animation Player and AnimatableBody3D.

Godot version
v4.0.beta1.official.20d667284
System information
Windows 11, Vulkan, NVidia Gtx 1060 6GB
Issue description
When moving an object AnimatableBody3D against another physical object like CharacterBody3D the collision does not occur, the object overtakes the other, which is not expected according to documentation
Steps to reproduce
Move a AnimatableBody3D,  with the property sync_to_pyshics enabled, using a AnimationPlayer, with the property playback_process_mode to physics, against another object pyshics 3d.

Minimal reproduction project
animatable_body_3d_problem.zip

You're setting the position every frame using an AnimationPlayer node. This is expected to ignore collision checks. Set the linear velocity instead.

I tried too and it didn't work.
In documentation:
"When the body is moved manually, either from code or from an AnimationPlayer (with AnimationPlayer.playback_process_mode set to physics), the physics will automatically compute an estimate of their linear and angular velocity. This makes them very useful for moving platforms or other AnimationPlayer-controlled objects (like a door, a bridge that opens, etc)."
I was just trying to use it for a door. if a  AnimatableBody3D doesn't work with AnimationPlayer what is it for?