Config Incompatibility with Modded Scrap

The config does not work properly when editing the scrap pool of any moon. It works well with vanilla loot, but not if it's from any mods.
I'll be using the modded moon Asteroid-13 as an example. Let's say I want have this as my customized setup...
Blue Folder:40,Red Folder:40,Stapler:40,Fire Extinguisher:34,Documents:26,Stun Baton:29,Banana:8,Coil:27,Bronze Trophy:13,Typewriter:19,Experiment Log Hyper Acid:8,Experiment Log Comedy Mask:8,Experiment Log Cursed Coin:8,Experiment Log BIO HXNV7:8,Old Computer:7,BIO-HXNV7:5,Mug:7,Remote:6,Old phone:4,Magnifying glass:4,Fancy lamp:3,Cash register:2,Fire hydrant:2,Retro PC:0,Computer Chip:0,Computer Fan:0,Gas Can:0,Metal Beam:0,CRT Monitor:0,Box Of Parts:0,Copper Wire Spool:0,Ball Bearing:0,Metal Disk:0,Small Motor:0,Stator:0,Air Compressor:0,Gear:0,Cog:0,Small Gear:0,Flathead Screw:0,Hex Screw:0,Panhead Screw:0,Floppy Disk:0,Big Wrench:0,Lost Employee Helmet:0,Lost Employee Tank:0,Aerial Dish:0,Old Missile:0,Diesel Generator:0,Oil Drum:0,Studio Camera:0,6 Pin Cable:0,Capacitor:0,Diode:0,Transistor:0,Magnet:0,Blue Tape:0,Tape Measure:0,Flip Phone:0,Control Panel:0,Car Battery:0,Piston:0,AC Unit:0,Alarm Clock:0,AA Battery:0,9V Battery:0,Polaroid Camera:0,Jet Engine:0,Lightbulb:0,Lighter:0,Neon Sign:0,Propane Tank:0,Traffic light:0,Vice:0,Arson Plush:1,Cookie Fumo:1,Toimari Plush:2,Hamis Plush:2,Dirty Arson Plush:1,Maxwell:1,Glizzy:1,Revolver:2,Gremlin Can:2,Toy Hammer:5,Gnarpy Plush:2,Army Helmet:1,Army Canteen:1,Gramophone:1,Old Radio:1,RockingHorse:1,TypeWriter:1,WheelRim:1,WireSpool:1,Bracken Plushie:1,Bunker Spider plushie:1,CoilHead Plush:8,Comedy mask Plushie:1,Lootbug Plushie:1,Scavenger Plushie:1,Tragedy Plushie:1
If Enable Content Configuration is set to true, then all it does is spawn in vanilla loot. It includes all the vanilla loot that's in the list above but somehow it was also including ones that aren't supposed to be in there like comedy/tragedy masks (probably because of the Plushie part).
Then I tried to set it to this...
Blue Folder:40,Red Folder:40,Stapler:40,Fire Extinguisher:34,Documents:26,Stun Baton:29,Banana:8,Coil:27,Bronze Trophy:13,Typewriter:19
But it just gets stuck in a forever-loading loop.
I wasn't able to test this part well enough but I think this also extends to spawn weights of modded entities such as Shy guy, Herobrine, or Boombas.
I can try to supply more information as requested but I'm not a modder.

Closed as Lethal Expansion is now deprecated.


Make ViewComponentTagHelper's bound attribute display names nicer.

Went from typeName __Generated__SomeViewComponentTagHelper.PropertyName to typeName SomeViewComponentTagHelper.PropertyName.
Updated TagHelperBoundDescriptorBuilder to allow setting of DisplayName.
Added TagHelperBoundAttributeDescriptorBuilderTest class to verify new DisplayName additions.
Updated ViewComponentTagHelperDescriptorFactoryTest expectations.

#1251
Just realized this piece was missed. Right now I have this posed against rel/15.3, let me know if you want to delay the addition of this.

We don't have approval to put this in 15.3 so just fix it in dev for now. We can consider this for 15.4

Please open another issue to track fixing this for 15.4


启动 helloworld 里的消费者报错

2022/09/22 13:28:51 SendMessage err:  kafka server: Request was for a topic or partition that does not exist on this broker.

需要创建对应的 topic 才行 @yunlongw


Was v2023.11.17 mistagged?

I'm assuming that pipenv is using date-based versioning, in which case I would have expected the latest release to be v2024.01.21 not v2023.11.17. Is there some reason for this discrepancy?

I initially thought the most recent release version was broken too, until I found this issue.
Would it be possible to say bump the version to a visibly-not-a-real-date version (eg 3000.Y.Z), to reduce the chance for confusion?

Also I think a clearer explicit call-out at the top of the release notes would be helpful:
https://github.com/pypa/pipenv/releases/tag/v2023.11.17
Currently the only mention is this:

Update release script to enforce semver going forward in 2024

...which (a) requires quite a bit of reading between the lines to understand the impact, (b) was in the middle of a number of other changelog entries, rather than being called out at the top in an intro paragraph etc.

We can do the major 3000 thing when we do our next major version release (have some install API changes planned and same for uninstall), but until then it's going to be based off the incrementing off the current version.


Not supporting mobile touch in angular project

Hi,
I tried to use this plugin in an angular project.
It is great that works in desktop , but it is not working on mobile.
I'm using this " jquery-3.2.1.min.js" version of jquery.
I'm using this version of slider<EMAIL_ADDRESS>I know that it works on mobile originally, but just not working on my angular project.
Just wonder how to make it work on mobile?
(I have already included angular-touch and have ngTouch module in my app)
Thanks,
Nick.

You probably have some library conflicting with this one. Indeed, our demo website works fine on mobile: http://angular-slider.github.io/angularjs-slider/


Implement Redux Store for Edit Interface

Need a way to be able to save the current state between reloads and allow the editors to select personal defaults.

We should discuss before you go down this path what you're hoping to achieve with Redux specifically. I'd rather get through the basic editing workflow before we worry too much about state persistence, customizability, and the like.

State management is important, but redux is not the way to do it.


Typo fix

@thebillkidy : Thanks for your contribution to the SQL documentation! The author, @barbkess, has been notified to review your proposed change.

@thebillkidy - thanks for the edit! This PR is ready to merge.
#sign-off


webpack

Why there is a webpack configuration for the library?

Webpack is used only for running tests and in case you want to create the umd file. Have a look on the post that I linked in the readme file, it explain all the details


TFT-Screen

would this also work with a PiTFT 3.5" screen? https://www.adafruit.com/product/2097
If so, what would need to be done? Because nothing is displayed at the moment

pycasso implements omni-epd , which does not appear to support this screen and probably won't in the future as it's not an EPD. You can feel free to post an issue there if you'd like to request that functionality there, but I don't think it's in scope of that project either.
It might not be too hard to retrofit a solution into pycasso to display this from possibly the mockepd generated image, but I will close this issue as that's out of scope of this project.


Trying to use crunch with Polkadex substrate chain fails with Invalid Metadata error

Hi,
We are trying to use crunch (latest crunch version, built from source, tried the binary too) with Polkadex chain and it fails with following error:
$ crunch --config-path /home/user/.env.pdex --substrate-ws-url ws://<IP_ADDRESS>:9945/ view
[2022-02-11T12:31:56Z INFO crunch] crunch v0.4.1 * Crunch is a command-line interface (CLI) to claim staking rewards (flakes) every X hours for Substrate-based chains
[2022-02-11T12:31:56Z ERROR crunch::crunch] Invalid Metadata: Invalid version
[2022-02-11T12:31:56Z INFO crunch::crunch] Awaiting for connection using ws://<IP_ADDRESS>:9945/

We also tried to save polkadex metadata using subxt to metadata/polkadex_metadata.scale and compiled crunch again, but no go. Attaching polkadex_metadata.scale
polkadex_metadata.txt
We are currently using crunch successfully for kusama chain. Any help is appreciated.

Hi @radiumb glad you posted your issue here.
Apart from the polkadex_metadata.scale, a polkadex specific module to load the metadata file is also needed. Have a look at the kusama module here.
If polkadex staking pallet uses the same events and storage methods as the ones in the relay chain, you can just copy the kusama module here, update the  polkadex_metadata.scale in the module and import the module in the other project dependency files so you can test it.
I'm happy to review any PR.
Otherwise let me if there is any test faucet for polkadex so i can test it against their test network.


Feature/pybullet backend - PybulletClient, IK + FK

What type of change is this?

[ ] New feature in a backwards-compatible manner.

This PR is the starting point for the compas_fab.backends.pybullet. Mimicking the RosClient, I added PybulletClient that can create the robot in the pybullet environment, computing IK and FK using functionalities provided by pybullet_planning.
ikfast_pybind is not used in the IK computation in this PR, since it is a standalone thing (but can be integrated to pybullet_planning quite smoothly).
Please see the backends/pybullet/test_pb.py test file for example usage. By adding the --viewer flag in pytest --viewer, you will be able to invoke the pybullet GUI to check the results visually.
After @gonzalocasas approve these changes, I can go on and add the plan_motion and other features.
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[ ] I added a line to the CHANGELOG.rst file in the Unreleased section under the most fitting heading (e.g. Added, Changed, Removed).
[x] I ran all tests on my computer and it's all green (i.e. invoke test).
[ ] I ran lint on my computer and there are no errors (i.e. invoke lint) .
[x] I added new functions/classes and made them available on a second-level import, e.g. compas_fab.robots.Configuration.
[x] I have added tests that prove my fix is effective or that my feature works.
[ ] I have added necessary documentation (if appropriate)

Any update on this? I think having the basic cartesian-, joint- motion planning, collision checking for a given planning scene, and ikfast functionality done can have immediate benefits for many of us (as a light-weight, docker-free alternative to ROS-backend for quick prototyping).
We've talked about this before: I think I need @gonzalocasas 's help on reformulating ikfast_pybind. But we can just keep it that way and add corresponding module for the robots in robot_setups.

Just catching up on this... Is pybullet a supported backend in compas_fab? 🤖

Not yet, but we're getting closer to it. Recently a very large refactoring of how backends are integrated has been merged to master (#149) which cleared the way for a clean integration of pybullet (and a bunch more!).

@gonzalocasas Should I close this in the light of #181 ?


CustomBuild Command environment does not contain the result of a SetEnv even though Exec does

I have used CoApp to create a nuget package to package some code generators (binaries). I want to be able to use these code generators in a msbuild custombuild step to generate the code
I have a targets file that defines the following (using CoApp)
<SetEnv Condition="'$(Platform.ToLower())' == 'x64' And '$(PlatformToolset.ToLower())' == 'v100' And ( $(Configuration.ToLower().IndexOf('debug')) == -1 )" Name="PATH" Prefix="true" Value="$(MSBuildThisFileDirectory)../..//build/native/bin/x64\v100\Release;">   <Output TaskParameter="OutputEnvironmentVariable" PropertyName="PATH" /> </SetEnv>
The targets file containing this snippet is imported like so into a project (vcxproj file)
<Import Project="..\packages\habitat.id.redist.<IP_ADDRESS>\build\native\habitat.id.redist.targets
within the project
<Exec Command="echo %PATH%"/>
returns the desired outcome i.e. that which takes the form
../..//build/native/bin/x64\v100\Release;
so I can call the executable that I want to run from the project. (except for unlike a custombuild command step there is no concept of outputs. So incremental builds will thence not work)
however
<CustomBuild Include="..\directory\filename">   <FileType>Document</FileType>   <Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">   echo $(PATH) </Command>
does not contain the path that I want that was set through the SetEnv.
There are unit tests that show the desired behavior for the Exec command though it uses/loads a custom assembly for setenvv.
For Exec it goes through the temporarybatchfile routine. What is the equivalent for the CustomBuild >  Command
The question has also been asked here http://stackoverflow.com/questions/36489469/msbuild-14-0-visual-studio-2015-custombuild-command-environment-does-not-contain
I would like to fix this issue but need help to know where the code is

You're not finding the code here because the CustomBuild task is part of the C++ task assembly, not the core MSBuild package. The C++ team's code is still Microsoft-internal, and supported through the usual Microsoft mechanisms. But you might not need to go through them.
Do you really need to use CustomBuild? Can you just create a target that uses Exec?
You may also be able to avoid using environment variables at all by making your target take a full path and just setting it as an MSBuild property. You're already computing the path in MSBuild.

I wanted to continue to use the custom build because it is exposed through the standard visual studio property sheet, a custom target is not (until you customize the property sheet hence introducing something that not everyone is familiar with and will forget to install and then complain) So I was hoping to get a product level solution that would come through the next product update. That looks unlikely
I was looking to continue to use the environment variable approach because that's the way CoApp does it for nuget package it creates for C++ binaries. It's easy enough to change the spec file. (Not using Coapp's Write-NugetPackage but use nuget pack instead)
Yes I will use the Target-Exec-Property combination because that looks like the next best option
Should I close this issue or will this be forwarded to the C++ team?


Deploy WAR with Powershell does not work in Ubuntu

My pipeline:
pool:
  vmImage: ubuntu-latest`

# maven build

- powershell: Publish-AzWebapp -ResourceGroupName ...

The error I get is
Line |
2 |  Publish-AzWebapp -ResourceGroupName rg-prod-pim-01 -Name pim-01-prod  …
|  ~~~~~~~~~~~~~~~~
| The term 'Publish-AzWebapp' is not recognized as a name of a
| cmdlet, function, script file, or executable program. Check
| the spelling of the name, or if a path was included, verify
| that the path is correct and try again.
##[error]PowerShell exited with code '1'.
Isn't this cmdlet supported on Linux? Do the docs need to be updated?

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

ID: 4ce674e6-fcb7-a867-2a74-f28f6a1b0204
Version Independent ID: 461fc0b5-ac32-54b8-cdb6-76a2c8e6052f
Content: Deploy files to App Service - Azure App Service
Content Source: articles/app-service/deploy-zip.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

Don't use powershell as it doesn't have Az.Module. Change your task to AzPowerShell instead; see https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/deploy/azure-powershell?view=azure-devops for more details on the task. Or use a script file that will also install the power shell module in addition to publishing your WAR file. If you have any issues, please feel free to tag me in your reply below.

HI, I've tried your suggestion

task: @.***
inputs:
azureSubscription: 'essity-sub-is-prod-cmn-01'
displayName: 'Deploy OPC WAR'
ScriptType: 'InlineScript'
inline: 'Publish-AzWebapp -ResourceGroupName <...> -Name <...>
-ArchivePath target/opc-0.1.0.war'

and and the error is:
"The pipeline is not valid. Job Job: Step AzurePowerShell input
ConnectedServiceNameARM references service connection
essity-sub-is-prod-cmn-01 which could not be found. The service connection
does not exist or has not been authorized for use. For authorization
details, refer to https://aka.ms/yamlauthz."
Please guide me further. Is this about an authorization to the artifact
that the pipeline produces? This is what I inferred from
https://aka.ms/yamlauthz..
Thanks
Lucian
On Sat, Jan 15, 2022 at 1:59 AM Ryan Hill @.***> wrote:

Don't use powershell as it doesn't have Az.Module. Change your task to
AzPowerShell instead; see
https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/deploy/azure-powershell?view=azure-devops
for more details on the task. Or use a script file that will also install
the power shell module
https://docs.microsoft.com/en-us/powershell/azure/install-az-ps?view=azps-7.1.0
in addition to publishing your WAR file. If you have any issues, please
feel free to tag me in your reply below.
—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/86360#issuecomment-1013550237,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AESRV6SF2RQYSQZLWKGJFXLUWC2HBANCNFSM5L3UZKGA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

Forget that, I passed that error by using a service connection name.
Now I have to fix this one
Az version null not avaiable locally on the agent. Downloading dynamically.
Validate-VersionParameters: Cannot convert value 'null' to type
'System.Version'.
On Mon, Jan 17, 2022 at 3:33 PM Lucian Ciufudean @.***>
wrote:

HI, I've tried your suggestion

task: @.***
inputs:
azureSubscription: 'essity-sub-is-prod-cmn-01'
displayName: 'Deploy OPC WAR'
ScriptType: 'InlineScript'
inline: 'Publish-AzWebapp -ResourceGroupName <...> -Name <...>
-ArchivePath target/opc-0.1.0.war'

and and the error is:
"The pipeline is not valid. Job Job: Step AzurePowerShell input
ConnectedServiceNameARM references service connection
essity-sub-is-prod-cmn-01 which could not be found. The service connection
does not exist or has not been authorized for use. For authorization
details, refer to https://aka.ms/yamlauthz."
Please guide me further. Is this about an authorization to the artifact
that the pipeline produces? This is what I inferred from
https://aka.ms/yamlauthz..
Thanks
Lucian
On Sat, Jan 15, 2022 at 1:59 AM Ryan Hill @.***>
wrote:

Don't use powershell as it doesn't have Az.Module. Change your task to
AzPowerShell instead; see
https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/deploy/azure-powershell?view=azure-devops
for more details on the task. Or use a script file that will also install
the power shell module
https://docs.microsoft.com/en-us/powershell/azure/install-az-ps?view=azps-7.1.0
in addition to publishing your WAR file. If you have any issues, please
feel free to tag me in your reply below.
—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/86360#issuecomment-1013550237,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AESRV6SF2RQYSQZLWKGJFXLUWC2HBANCNFSM5L3UZKGA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

OK, nailed that one too.
Eventually I used this task:

task: @.***
inputs:
azureSubscription: 'PIM Prod connection'
displayName: 'Deploy OPC WAR'
ScriptType: 'InlineScript'
inline: 'Publish-AzWebapp -ResourceGroupName rg-prod-pim-01 -Name
pim-01-prod -ArchivePath target/opc-0.1.0.war -Force'
azurePowerShellVersion: 'latestVersion'

It ran successfully, but note that I had to use the undocumented Force
parameter
to get it to run.
Otherwise I was getting this error:
*Publish-AzWebApp:
/home/vsts/work/_temp/b2d54580-8cb4-489e-8662-3fc3998d7dca.ps1:4Line |4 |
Publish-AzWebapp -ResourceGroupName rg-prod-pim-01 -Name pim-01-prod …|
PowerShell is in NonInteractive mode. Read and Prompt| functionality is not
available.*

Sounds like a regression, see
https://github.com/Azure/azure-powershell/issues/10224.

Now to the real issue: Even if AzurePowerShell ran successfully, the app
page still shows the generic "Hey, Java developers!" page.

Streaming the logs:

*Running STARTUP_COMMAND: java -jar
/home/site/wwwroot/opc-0.1.0.war2022-01-18T00:48:17.140038369Z Error:
Unable to access jarfile /home/site/wwwroot/opc-0.1.0.wa*

So the WAR file I am deploying cannot be found.
I have a Linux app service, Java SE.
Can I even deploy WAR files?
https://docs.microsoft.com/en-us/azure/app-service/configure-language-java?pivots=platform-linux#java-se
says that only .jars are supported named app.jar.
On the other hand,
https://docs.microsoft.com/en-us/azure/app-service/deploy-zip?tabs=api#deploy-warjarear-packages
does not mention any filename restrictions nor that I cannot deploy a WAR
using Kudu or powershell.
this
https://docs.microsoft.com/en-us/azure/app-service/faq-app-service-linux#what-are-the-expected-values-for-the-startup-file-section-when-i-configure-the-runtime-stack-
suggests that any name should be possible if I configure a startup command..

I am really confused.

Lucian

On Mon, Jan 17, 2022 at 3:42 PM Lucian Ciufudean<EMAIL_ADDRESS>wrote:

> Forget that, I passed that error by using a service connection name.
> Now I have to fix this one
>
> Az version null not avaiable locally on the agent. Downloading
> dynamically.
> Validate-VersionParameters: Cannot convert value 'null' to type
> 'System.Version'.
>
>
> On Mon, Jan 17, 2022 at 3:33 PM Lucian Ciufudean <
><EMAIL_ADDRESS>wrote:
>
>> HI, I've tried your suggestion
>>
>> - task<EMAIL_ADDRESS>>>   inputs:
>>     azureSubscription: 'essity-sub-is-prod-cmn-01'
>>     displayName: 'Deploy OPC WAR'
>>     ScriptType: 'InlineScript'
>>     inline: 'Publish-AzWebapp -ResourceGroupName <...> -Name <...>
>> -ArchivePath target/opc-0.1.0.war'
>>
>> and and the error is:
>>
>> "The pipeline is not valid. Job Job: Step AzurePowerShell input
>> ConnectedServiceNameARM references service connection
>> essity-sub-is-prod-cmn-01 which could not be found. The service connection
>> does not exist or has not been authorized for use. For authorization
>> details, refer to https://aka.ms/yamlauthz."
>>
>> Please guide me further. Is this about an authorization to the artifact
>> that the pipeline produces? This is what I inferred from
>> https://aka.ms/yamlauthz..
>>
>> Thanks
>> Lucian
>>
>>
>>
>> On Sat, Jan 15, 2022 at 1:59 AM Ryan Hill<EMAIL_ADDRESS>>> wrote:
>>
>>> Don't use powershell as it doesn't have Az.Module. Change your task to
>>> AzPowerShell instead; see
>>> https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/deploy/azure-powershell?view=azure-devops
>>> for more details on the task. Or use a script file that will also install
>>> the power shell module
>>> <https://docs.microsoft.com/en-us/powershell/azure/install-az-ps?view=azps-7.1.0>
>>> in addition to publishing your WAR file. If you have any issues, please
>>> feel free to tag me in your reply below.
>>>
>>> —
>>> Reply to this email directly, view it on GitHub
>>> <https://github.com/MicrosoftDocs/azure-docs/issues/86360#issuecomment-1013550237>,
>>> or unsubscribe
>>> <https://github.com/notifications/unsubscribe-auth/AESRV6SF2RQYSQZLWKGJFXLUWC2HBANCNFSM5L3UZKGA>
>>> .
>>> Triage notifications on the go with GitHub Mobile for iOS
>>> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
>>> or Android
>>> <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
>>>
>>> You are receiving this because you authored the thread.Message ID:
>>><EMAIL_ADDRESS>>>>
>>


clstmocr - error opening clstm file (trained model)

I have a trained uw3 model which had trained about 4000 iterations. Then, when I execute clstmocr, I face some error:
./clstmocr image.jpg
#: load = uw3-500-4000.clstm
#: conf = 0
#: output = text
#: save_text = 1
FATAL: error on open

Any ideas ?

No idea yet but a confirmation of your report:
kmw@lal:~/projects/dta/ocropus/baz$ load=baz.clstm conf=1 ~/built/clstm/clstmocr test_bin/facs_1_tl_21.bin.png
#: load = baz.clstm
#: conf = 1
#: output = text
#: save_text = 1
FATAL: error on open

Using the absolute path does not help either. @kba Could you please have a look at this? I am pretty sure that this caused by incorrect invocation of clstmocr.

I don't have a machine to test ATM, hopefully in over the weekend I'll get it back @zuphilip Can you try?

As I suspected, incorrect invocation. Should have a look at test-ocr.sh first: The argument to clstmocr has to be a text file containing image paths rather than an image file:
kmw@lal:~/projects/dta/ocropus/baz$ echo "test_bin/facs_1_tl_21.bin.png" > test_single.lst
kmw@lal:~/projects/dta/ocropus/baz$ load=baz-4000.clstm ~/built/clstm/clstmocr test_single.lst
#: load = baz-4000.clstm
#: conf = 0
#: output = text
#: save_text = 1
test_bin/facs_1_tl_21.bin.png	behalten wird, müißte alsn spätestenm Aniamg Dirz mit den krcben von Solisten

@lomograb Can you try and confirm in order to resolve this issue?

@wrznr you are right. now clstmocr produces values, what do they mean?
0	7	32	0.999997
1	19	32	0.999999
2	32	32	0.999993
3	36	32	0.986836
4	41	32	0.997986
5	56	1585	0.998276
6	60	32	0.404907
7	72	1585	0.957227
8	78	1585	0.958865
9	85	1585	0.847094
10	89	1585	0.966943
11	97	32	0.783419

@christophered I am sorry, but for me it does not produce numbers but rather output text (cf. console output from my post above). If you provide your invocation command, I will try to interpret those numbers.

@christophered Okay, figured it out. You invoked clstmocr with the env variable conf=1, i.e.:
load=baz-4000.clstm conf=1 ~/built/clstm/clstmocr test_single.lst

The numbers give you 1. Position in output text, 2. starting pixel (that's a wild guess, @kba Could you pls confirm?), 3. Recognized char (i.e. decimal unicode point), 4. char confidence (i.e. how sure was the system at this point).
If you set conf=0 (or leave it out), the numbers disappear and only the recognized text is printed.
I guess the issue could be closed now, right?


compute: support using node instead/above of instance label

What
Either change compute modules' instance to node, or support e.g. --compute.vm-instance-label=LABEL_NAME.
Why
Couple main reasons:

When using cloudcost-exporter metrics in Kubernetes, to be able to join against kube_.* metrics (like kube_node_labels, kube_node_annotations, kube_node_status_capacity, kube_node_status_allocatable, ... see full list below), you then are forced to relabel instance to node with a construct like

  label_join( <CSP>_instance_cpu_usd_per_core_hour{}, "node", "", "exported_instance")

The above needs to be done for every <CSP> you may run (especially the case if you have a centralized TSDB), note also that you need to visit every timeseries to perform this relabelling (under the context of TSDB pressure).

Wisely, cloudcost-exporter already chose cluster_name instead of cluster (this being a popular label_name choice, then avoiding the scrape-time rename to exported_cluster), then why keeping instance that by design scraping agents will always rename to exported_instance (thus the example relabelling query above).

Appendix
Pasting the full list of Kubernetes metrics using node, from this query count by (__name__)({__name__=~"kube_.+", node!=""})
kube_node_annotations
kube_node_created
kube_node_info
kube_node_labels
kube_node_spec_taint
kube_node_spec_unschedulable
kube_node_status_allocatable
kube_node_status_allocatable_cpu_cores
kube_node_status_allocatable_memory_bytes
kube_node_status_capacity
kube_node_status_capacity_cpu_cores
kube_node_status_capacity_memory_bytes
kube_node_status_condition
kube_pod_container_resource_limits
kube_pod_container_resource_requests
kube_pod_info
kube_node_status_addresses
kube_pod_init_container_resource_limits
kube_pod_init_container_resource_requests

I'm hesitant about replacing the instance label with node, as this couples our definition of "machine" with "machine provisioned by kubernetes".  Since we want to make this more agnostic of how the machine was provisioned, I think that node wouldn't be the right choice here.
That being said, this does make sense as an optional config argument, as it can then be used for convenience for a big (and possibly majority) use-case: managed Kubernetes.
I think this brings up an interesting point, since the instance label will often be replaced by Prometheus Scrapers and rewritten as exported_instance (as the instance of the job running cloudcost-exporter is already using the instance label).  Thoughts on:

config value for the label meaning "name of machine"?
renaming the instance label to something agnostic of how it was provisioned, like machine_name?

I'm hesitant about replacing the instance label with node, as this couples our definition of "machine" with "machine provisioned by kubernetes". Since we want to make this more agnostic of how the machine was provisioned, I think that node wouldn't be the right choice here.
That being said, this does make sense as an optional config argument, as it can then be used for convenience for a big (and possibly majority) use-case: managed Kubernetes.
I think this brings up an interesting point, since the instance label will often be replaced by Prometheus Scrapers and rewritten as exported_instance (as the instance of the job running cloudcost-exporter is already using the instance label). Thoughts on:

config value for the label meaning "name of machine"?
renaming the instance label to something agnostic of how it was provisioned, like machine_name?

+1 moving away from instance, I like machine_name as the default value for such e.g. --compute.vm-instance-label=LABEL_NAME (or alike, naming-is-hard always hunting us).

I am opposed to having labels defined via command line arguments for the following reasons:

It implies we got the names of labels incorrect and we're masking that to ease PromQL creation
Potential of running many collectors with different labels at the same time which means we can't guarantee the use of a metric with a specific query
Exposing us to having a configuration for every label and having a massive config struct to run the application

I'd really like for us to get alignment on what the root problem is that we're trying to address(In this case, instance doesn't appear to be the appropriate label, it should be node), and then agree on a solution. Whichever path we take is going to require us to rewrite our internal PromQL queries and do a migration of the metrics.

I am opposed to having labels defined via command line arguments for the following reasons:

It implies we got the names of labels incorrect and we're masking that to ease PromQL creation

It's not only easying promQL, it's actually decreasing the load into TSDB, for an arbitrary renaming that will likely be always needed (should we keep instance as its name).

Potential of running many collectors with different labels at the same time which means we can't guarantee the use of a metric with a specific query

(?) sure, as operator you could always shoot yourself in the foot, nevertheless top->down label setting currently only allows one entry point for it.

Exposing us to having a configuration for every label and having a massive config struct to run the application

Didn't ever propose that -- it's this particular one I'm concerned, as we do know [*] we have disjoint sets of metrics (ec2, kube) that inevitably use either instance (sorry for that one, as it'll always be exported_instance unless changed at scrape time), xor node.

I'd really like for us to get alignment on what the root problem is that we're trying to address(In this case, instance doesn't appear to be the appropriate label, it should be node), and then agree on a solution. Whichever path we take is going to require us to rewrite our internal PromQL queries and do a migration of the metrics.

Already replied in the very previous paragraph[*]

I am opposed to having labels defined via command line arguments for the following reasons:

It implies we got the names of labels incorrect and we're masking that to ease PromQL creation

It's not only easying promQL, it's actually decreasing the load into TSDB, for an arbitrary renaming that will likely be always needed (should we keep instance as its name).

Potential of running many collectors with different labels at the same time which means we can't guarantee the use of a metric with a specific query

(?) sure, as operator you could always shoot yourself in the foot, nevertheless top->down label setting currently only allows one entry point for it.

Exposing us to having a configuration for every label and having a massive config struct to run the application

Didn't ever propose that -- it's this particular one I'm concerned, as we do know [*] we have disjoint sets of metrics (ec2, kube) that inevitably use either instance (sorry for that one, as it'll always be exported_instance unless changed at scrape time), xor node.

I'd really like for us to get alignment on what the root problem is that we're trying to address(In this case, instance doesn't appear to be the appropriate label, it should be node), and then agree on a solution. Whichever path we take is going to require us to rewrite our internal PromQL queries and do a migration of the metrics.

Already replied in the very previous paragraph[*]

Indeed, one aspect that I'll really like cloudcost-exporter to shine when compared with other existing solutions, is being as "friendly" as possible to the TSDB, for obvious reasons.


i cant login to the dashboard, when i try to login and i enter again to the page, still appears login

change this:
bot.channels.cache.get('845762798709375042').send(User authorize with ${userResponse.username}#${userResponse.discriminator}) in the "webapi_handler.js" to your guild channel


MS Graph Api v1.0 is not returning all data

Describe the bug
MS Graph Api v1.0 is not returning all data stored in outlook contacts. Fields you can add with "add more" option are  not provided via the api, even with expand.
Related api page:
https://docs.microsoft.com/de-de/graph/api/user-list-contacts?view=graph-rest-1.0&tabs=http
To Reproduce
1.) Add contact in outlook online and click "add more"->"Phone"->"Other"
and add an "Business Fax" entry and then save it.
2.) Call "/me/contacts" via MS Graph-Api v1.0
3.) You get a list of the contacts but their is no data for "Business Fax". This also happens for other fields. Adding $expand to the query is giving the same result. "/me/contacts/{id}" is also not helping.
Expected behavior
The api-Call should provide the contacts with data
Api-Response-Example
....
{
<EMAIL_ADDRESS>"W/"EQAA....B7ZT+"",
"id": "AQMkA....EgAAAA==",
"createdDateTime": "2020-01-08T11:21:24Z",
"lastModifiedDateTime": "2020-01-09T09:32:32Z",
"changeKey": "EQA....AB7ZT+",
"categories": [],
"parentFolderId": "AQMkAD...mogAAAgEOAAAA",
"birthday": null,
"fileAs": "",
"displayName": "x y",
"givenName": "x",
"initials": null,
"middleName": null,
"nickName": null,
"surname": "y",
"title": null,
"yomiGivenName": null,
"yomiSurname": null,
"yomiCompanyName": null,
"generation": null,
"imAddresses": [],
"jobTitle": null,
"companyName": null,
"department": null,
"officeLocation": null,
"profession": null,
"businessHomePage": null,
"assistantName": null,
"manager": null,
"homePhones": ["1234567"],
"mobilePhone": null,
"businessPhones": [],
"spouseName": null,
"personalNotes": "",
"children": [],
"emailAddresses": [{
"name"<EMAIL_ADDRESS>"address"<EMAIL_ADDRESS>}],
"homeAddress": {},
"businessAddress": {},
"otherAddress": {
"street": "Some road 1",
"city": "Somecity",
"countryOrRegion": "Someregion",
"postalCode": "12345"
}
}
...

@jkopen Thanks for taking the time to give us your feedback.
I've flagged the issue for a member of the docs team for awareness and investigation.
Appreciate your contribution to our docs community.
@Lauragra Can you take a look or reassign if/as needed?


hspec/setup-haskell broken on macos-latest (macos-14)

The macos-14 image does not have ghc in the path any longer:
https://github.com/sol/doctest/actions/runs/9172384682/job/25218779659?pr=423#step:3:7

Run hspec/setup-haskell@v1
with:
ghc-version: system
Workaround for https://github.com/actions/runner-images/issues/7061
Error: Unable to locate executable file: ghc. Please verify either the file path exists or the file can be found within a directory >specified by the PATH environment variable. Also check the file mode to verify the file is executable.

Thanks @andreasabel.  For the time being, I'm not going to do anything here.  macos-12 still works.


Add svelte export condition

Adds an export condition to replace the deprecated "svelte" field. The "svelte" field will stop working at some point in the future with vite-plugin-svelte.
https://github.com/sveltejs/vite-plugin-svelte/blob/main/docs/faq.md#missing-exports-condition

Bump

Thanks! I will merge this but probably rework this library for SvelteKit anyway soon.
Nonetheless this should be a good temporary solution.

I just released v2.1.0 which contains the changes made by this PR. Thanks again!


Error while using add-safari-permissions in xcode 14.3 environment

Orb version: 2.3.5
What happened:
When using the add-safari-permissions job from this orb in xcode 14.3 environment (and macos.x86.medium.gen2 resource class) the following error appears

207:287: execution error: System Events got an error: Can’t get menu item "Preferences…" of menu 1 of menu bar item "Safari" of menu bar 1 of process "Safari". (-1728)

Expected behavior:
Safari permissions are enabled
Additional Information:
This works with xcode 14.2 and medium resource class.
Example workflow.
Thank you

The menu item isn't named Preferences anymore, but Settings. Changing this in the script makes it work as expected.

@herschel666 can you create a PR to solve the issue? 🙂

@BytesGuy When will v2.3.6 be available in the registry? Latest public version there is v2.3.4.

It works, thank you 🙏


Add public variable containing module and script paths

This PR closes #120 by creating a public variable called $PSGetPath containing the following properties:

AllUsersModules
AllUsersScripts
CurrentUserModules
CurrentUserScripts

Let me know if the variable or type name should be changed.

Thanks for all the PRs @tnieto88! 😄

Thank you  @tnieto88


Runtime config reference not synced with the 3.6.0 engine

Somehow this is still missing few newer options.
"[graphics] window", "[graphics] fullscreen", and maybe anything else
https://github.com/adventuregamestudio/ags/blob/release-3.6.0/OPTIONS.md
EDIT: also "[misc] titletext".

added graphics window and fullscreen here: https://github.com/adventuregamestudio/ags-manual/wiki/EngineConfigFile/_compare/2ffa4e9^...2ffa4e9

I'd like to double check.

Okay, seems to match now; I also had to remove few old options remaining since pre-3.6.0 times.
https://github.com/adventuregamestudio/ags-manual/wiki/EngineConfigFile/_compare/821f1c041245a377b411026f4b00705a5c57289d...3829feefea8a75e612d56990252771ec44447626

Where it says that options are locked in a default state, does that mean the AGS default (similar to if the option was not in the cfg file) or does it mean whatever is stated in the cfg file?

Where it says that options are locked in a default state, does that mean the AGS default (similar to if the option was not in the cfg file) or does it mean whatever is stated in the cfg file?

The option set in cfg file.

Where it says that options are locked in a default state, does that mean the AGS default (similar to if the option was not in the cfg file) or does it mean whatever is stated in the cfg file?
The option set in cfg file.

Maybe the manual could indicate that?

Does it look better now?
https://github.com/adventuregamestudio/ags-manual/wiki/EngineConfigFile/_compare/3829feefea8a75e612d56990252771ec44447626...45961828944035911b7e467478b5ab9409c5e9a7

Looks good to me!


Incorrect display of icons in the list of Windows 10 applications

VSCode Version: 1.31.1
OS Version: Windows 10 v. 1809

Steps to Reproduce:

Open Settings of Windows 10
Select Apps
Select Apps & features
Find Microsoft Visual Studio Code

Does this issue occur when all extensions are disabled?: Yes
Screenshot

@Rakleed how does it look like?

@bpasero I attached a screenshot in the first message. Or something else you want?

@Rakleed thanks, yeah that is weird. Does a uninstall and reinstall help?

@bpasero no, it doesn't.

@bpasero maybe you have the same problem. Here you can read about it in more detail.

Closing optimistically given https://github.com/Microsoft/vscode-docs/blob/vnext/release-notes/v1_35.md#updated-visual-studio-code-icon. Please report back otherwise.


Smoke alarm only shows battery state

Hi!
Thanks for bringing this official integration without needing to renew cloud access.
I have a LSC smoke detector. In Home Assistant I can only see the battery percentage but not the state of the smoke detector.

Can you provide diagnostics file？

@gsqqq123 does this help you?
"data": {
"endpoint": "https://apigw.tuyaeu.com",
"terminal_id": "17006420450440D3CLT",
"mqtt_connected": true,
"disabled_by": null,
"disabled_polling": false,
"id": "61840056c45bbee98e87",
"name": "Rauchwarnmelder",
"category": "ywbj",
"product_id": "cjlutkuuvxnie17o",
"product_name": "Smoke Alarm",
"online": true,
"sub": false,
"time_zone": "+01:00",
"active_time": "2022-11-10T09:53:34+00:00",
"create_time": "2022-11-10T09:53:34+00:00",
"update_time": "2022-11-10T09:53:34+00:00",
"function": {},
"status_range": {
"battery_state": {
"type": "Enum",
"value": {
"range": [
"low",
"middle",
"high"
]
}
}
},
"status": {
"battery_state": "high"
},
"home_assistant": {
"name": "Rauchwarnmelder",
"name_by_user": null,
"disabled": false,
"disabled_by": null,
"entities": [
{
"disabled": false,
"disabled_by": null,
"entity_category": "diagnostic",
"device_class": null,
"original_device_class": null,
"icon": null,
"original_icon": "mdi:battery",
"unit_of_measurement": null,
"state": {
"entity_id": "sensor.rauchwarnmelder_battery_state_2",
"state": "high",
"attributes": {
"icon": "mdi:battery",
"friendly_name": "Rauchwarnmelder Battery state"
},
"last_changed": "2023-11-29T09:58:10.384294+00:00",
"last_updated": "2023-11-29T09:58:10.384294+00:00"
}
}
]
},
"set_up": true,
"support_local": true
}

HA does not support all functions here, only the standard instruction set of the device is supported.
This device only support battery_state.

That's not true. I am using the Tuya IoT connection in parallel at the moment and that one is showing the status of the smoke detector.
See the diagnostic info of the IoT integration of that device
      "name": "Rauchwarnmelder",
      "name_by_user": null,
      "disabled": false,
      "disabled_by": null,
      "entities": [
        {
          "disabled": false,
          "disabled_by": null,
          "entity_category": "diagnostic",
          "device_class": null,
          "original_device_class": null,
          "icon": null,
          "original_icon": "mdi:battery",
          "unit_of_measurement": null,
          "state": {
            "entity_id": "sensor.rauchwarnmelder_battery_state",
            "state": "high",
            "attributes": {
              "icon": "mdi:battery",
              "friendly_name": "Rauchwarnmelder Batteriestatus"
            },
            "last_changed": "2023-11-29T09:58:10.229352+00:00",
            "last_updated": "2023-11-29T09:58:10.229352+00:00"
          }
        },
        {
          "disabled": false,
          "disabled_by": null,
          "entity_category": null,
          "device_class": null,
          "original_device_class": "smoke",
          "icon": null,
          "original_icon": null,
          "unit_of_measurement": null,
          "state": {
            "entity_id": "binary_sensor.rauchwarnmelder_rauch",
            "state": "off",
            "attributes": {
              "device_class": "smoke",
              "friendly_name": "Rauchwarnmelder Rauch"
            },
            "last_changed": "2023-11-29T09:58:10.128675+00:00",
            "last_updated": "2023-11-29T09:58:10.128675+00:00"
          }
        }

sorry Non standard instruction sets are not supported.


Code cleanup

This change:

adds jshinting to the test suite
makes jshint pass, including some dead code removal
fixes the test script definition so it properly expands and finds all tests

If you compare the test output of this branch vs the previous successful master build, you can see we were missing many tests before: before, after

Ahh, the test matching bug just manifested itself in the most recent commit.
Thanks for that and the general cleanup @ef4!

That makes sense -- I was surprised that the tests were all passing if they really hadn't been running for a while!

@ef4 amazing! Thanks for this!


Is there any possibility to add ARM64 support?

XDA ported Process Hacker to ARM some years ago:
https://forum.xda-developers.com/showthread.php?t=2179754
The only reason why the official builds don't support ARM is the lack of hardware (or at least someone who can submit patches).

@dmex any update on this? I have deployed ARM64 Win10 1909 to my Lumia 950XL and would like to use ProcessHacker

It is possible to cross-compile in Visual Studio with MSVC. But the project files and solution files need to be modified to add ARM64 (AArch64) and ARM (AArch32) configurations and solution platforms. Also someone has to test it.

It is possible to cross-compile in Visual Studio with MSVC. But the project files and solution files need to be modified to add ARM64 (AArch64) and ARM (AArch32) configurations and solution platforms. This video may help https://www.youtube.com/watch?v=OZtVBDeVqCE.
The source code need heavy change. For example, there are some SSE X86_64 C wrappers used in phlib (basesup.c file). Some NT structures are hugely differs between AMD64 and ARM64 (maybe I've seen those in Mr. Alex Ionescu's blog).

@Biswa96 do you want to start working on it and create a PR?

The only problem that I am not fluent in ARM assembly language and the ntoskrnl world.

The only problem that I am not fluent in ARM assembly language and the ntoskrnl world 😭

KProcessHacker driver compiles without any significant changes. Here are the list of failure of compilation in Visual Studio with ARM64 configuration:

phlib -- basesup.c -- PhCountStringZ -- due to usage of SSE.
phlib -- symprv.c -- PhpLookupFunctionEntry -- EndAddress absent in _IMAGE_ARM64_RUNTIME_FUNCTION_ENTRY.
phlib -- symprv.c -- PhWalkThreadStack -- Rip absent in _CONTEXT.
peview -- pdb.c -- _malloca and _freea absent.

Questions:

Is there any usermode test (only C) I can do to check if the kernel mode driver loaded successfully?
Does the kernel mode driver depend on any driver other than ksecdd driver? i.e. does it load other driver dynamically (kmode alternative of LoadLibrary)?

Is there any usermode test (only C) I can do to check if the kernel mode driver loaded successfully?

The EnumDeviceDrivers function can check if the module was loaded. See this example:
https://docs.microsoft.com/en-us/windows/win32/psapi/enumerating-all-device-drivers-in-the-system

Does the kernel mode driver depend on any driver other than ksecdd driver?

No

Here is my test case. I have Raspberry Pi 4B. I have booted Windows 10 ARM64 PE using EDK2 firmware and install kprocesshacker driver with sc create (test signing mode enabled). It is shown in EnumDeviceDrivers() as you have provided. If this peculiar environment sems to be somewhat similar with normal 500$ Windows 10 ARM laptops then I can do a PR.

Here is my test case. I have Raspberry Pi 4B. I have booted Windows 10 ARM64 PE using EDK2 firmware and install kprocesshacker driver with sc create (test signing mode enabled). It is shown in EnumDeviceDrivers() as you have provided. If this peculiar environment seems to be somewhat similar with normal 500$ Windows 10 ARM laptops then I can do a PR.

@Biswa96 do you have test builds? I can test it on WIn10 1909 ARM64 on my Lumia 950XL

I have only loaded the kernel driver. I am afraid to provide any kernel mode binary. If you have latest Windows 10 and Visual Studio 2019 you can see my forked repo and the 2nd branch.

Here is a release mode build kprocesshacker.sys.txt. Remove the .txt extension. You've to enable testsigning and nointegritychecks in bcdedit. Then add the driver as a service. For example:
bcdedit.exe /set {default} nointegritychecks on
bcdedit.exe /set {default} testsigning on
:: Restart PC here
sc create kph binPath= "path\to\kprocesshacker.sys" type= kernel
sc query kph

This test driver works on my 950XL:
sc query kph shows running:
C:\Windows\system32>sc query kph

SERVICE_NAME: kph
        TYPE               : 1  KERNEL_DRIVER
        STATE              : 4  RUNNING
                                (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

C:\Windows\system32>

Will the X86 version of ProcessHacker work with ARM64 version of the driver? I am think about it like this -- Download the X86 version of processhacker ZIP file, extract it, remove the driver (sys file) in that folder, register the ARM64 driver as kprocesshacker3 service, run the X86 ProcessHacker GUI as admin.
The ARM64 WinPE that I'm using in Raspberry Pi4 doesn't have the X86 emulation layer.

x86 processhacker doesn't start at all.

@dmex Is it possible to include malloc.h in pdb.c and notifico.c file for _malloca and _freea? The ARM64 config does not get the function declaration without that header file.

The phlib-test project can not be compiled. Errors -- The referenced project '....\phlib\phlib.vcxproj' does not exist. Cannot open include file: 'ph.h'.

@Biswa96
phlib-test should be fixed 👍

The X64 platform is missing.

The X64 platform is missing. Could you add the X64 platform in phlib-test project? When I tried to copy the config from Win32 platform msbuild searches the phlib.lib file in Debug32 folder instead of Debug64.

@Biswa96
I've added the x64 solutions. You'll have to ignore some asserts from UTF16 string length checks - they were incorrectly using UTF8 null terminators instead of UTF16 terminators and have the wrong lengths by 1 character.

Now this error is shown:
LINK : fatal error LNK1181: cannot open input file 'F:\processhacker\phlib\bin\Debug32\phlib.lib'

Now this error is shown with X64 debug, using VS 2019:
LINK : fatal error LNK1181: cannot open input file 'F:\processhacker\phlib\bin\Debug32\phlib.lib'

@Biswa96
The linker tries to open both libraries and you'll need to build the 32bit processhacker.sln to fix the issue. I have no idea why but it does need both libraries present.

Is it possible to add a C alternative of PhFindCharInStringRef and PhFindLastCharInStringRef functions without Intel intrinsic? i.e. PhpVectorLevel < PH_VECTOR_LEVEL_SSE2

With the recent PR, peview works. But processhacker window opens with WerFault.

ProcessHacker and peview now works in ARM64 Windows 10. See my fork where the binaries can be downloaded from CI build.

Temporary link to download arm64 builds https://ci.appveyor.com/project/Biswa96/processhacker/build/artifacts

@MagicAndre1981 Could you check if the symbols tab in peview works?

yes, both exe work fine. Great to have PH running as 64 Bit app  😍

@dmex
Is there any plan to add ARM64 support to build scripts?
So that it is possible to easily create whole package for ARM64.
I can have a look at it.
If you are willing to do that direction.
I can also do some testing on ARM64 devices (I have Surface Pro X at hand).

I have been using these commands to build everything in ProcessHacker:
call "%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Community\VC\Auxiliary\Build\vcvarsall.bat" amd64_arm64
msbuild KProcessHacker\KProcessHacker.sln -property:Configuration=Debug -property:Platform=ARM64 -verbosity:minimal
msbuild ProcessHacker.sln -property:Configuration=Debug -property:Platform=ARM64 -verbosity:minimal
mkdir sdk\lib\arm64
copy bin\DebugARM64\ProcessHacker.lib sdk\lib\arm64
msbuild plugins\Plugins.sln -property:Configuration=Debug -property:Platform=ARM64 -verbosity:minimal

Some catches:

The 3rd and 4th commands are handled by tools/CustomBuildTool but it doesn't support ARM64 platform.
The "ExtendedTools" plugin crashed with 0xC06D007F error in my WinPE ARM64 in qemu.
The KprocessHacker driver need to be signed to work properly.

@Biswa96
Thank you. I know how to build ProcessHacker.
I just wanted to offer working on kind of official build support (in CustomBuildTools and scripts).

The "ExtendedTools" plugin crashed with 0xC06D007F error in my WinPE ARM64 in qemu.

It seems to be working fine on Surface X device. I can see GPU/disk/network graphs.

The KprocessHacker driver need to be signed to work properly.

Yup. For now I have testsigning enabled on device.
Driver seems to be working just fine.

Yup. For now I have testsigning enabled on device.
Driver seems to be working just fine.

yes, driver also works for Lumia 950XL. I could also try the plugins. Is the ARM64 configuration already added for plugins?

@MagicAndre1981
Yes.
Just open Plugins.sln in VS, pick ARM64 platform and rebuild whole solution.
Plugins seems to work without any issue for me.

doesn't work for me. I always get this message :
LINK : fatal error LNK1104: cannot open file 'ProcessHacker.lib'
Win32 and x64 compile fine.  I first opened ph sln and build it for all configurations.

See my previous comment. Run the mkdir and copy command before compiling the plugins. This step is done by CustomBuildTool but ARM64 is not added there. I am not well versed in C#.

ok, this is easy, in Build.cs add 2 lines:
https://github.com/processhacker/processhacker/blob/master/tools/CustomBuildTool/Build.cs#L82 add here arm64
and here copy the lib
https://github.com/processhacker/processhacker/blob/master/tools/CustomBuildTool/Build.cs#L492

@Biswa96 @MagicAndre1981
See PR #635.

The patch works and looks good to me. Though the patch focuses on the sdk option, I thought it would be better if arm64 platform is added as a whole in CustomBuildTool which also creates zip files and artifacts in appveyor. Maybe it is in dmex's area.

I thought it would be better if arm64 platform is added as a whole in CustomBuildTool which also creates zip files and artifacts in appveyor

This is what I was trying to ask @dmex here. Whether he wants to go that direction or what are his plans regarding ARM64.
I'd like to work on that if it is desired.

@Biswa96
here is now a way to get Windows 10 ARM64 running on Pi4 via USB 3.0 boot:
https://rpi4-uefi.dev/alternate-guide-running-windows-10-on-the-pi-4/

I know, have done it 4 days ago. Also tested many projects, will test many.

Looking forward to this.

ARM64 platform is added to plugins-extra repository also.

I have been using these commands to build everything in ProcessHacker

I've added the build script: https://github.com/processhacker/processhacker/commit/280fd94feb0486b4ccd11bce8ab0267468a02292  👍

@dmex can you add ARM64 to nightly build?

I thought something will be added to CustomBuildTools so that the result will be seamless with other builds. Also the script doesn't handle release mode.

Adding comment to be notified of the progress. I've got an Allview Allbook Q notebook with Snapdragon 835 so having an ARM64 port of Process Hacker (which actually works correctly -- the x86 port reports higher CPU usage than Task Manager does) would definitely be nice.

I've added the build script: 280fd94 👍

I get this error during build:
E:\processhacker\plugins\ToolStatus\taskbar.c(401,31): error C2220: the following warning is treated as an error [E:\processhacker\plugins\ToolStatus\ToolStatus.vcxproj]
E:\processhacker\plugins\ToolStatus\taskbar.c(401,31): warning C4013: '_malloca' undefined; assuming extern returning int [E:\processhacker\plugins\ToolStatus\ToolStatus.vcxproj]
E:\processhacker\plugins\ToolStatus\taskbar.c(401,61): warning C4047: '=': 'PFLOAT' differs in levels of indirection from 'int' [E:\processhacker\plugins\ToolStatus\ToolStatus.vcxproj]
E:\processhacker\plugins\ToolStatus\taskbar.c(422,11): warning C4013: '_freea' undefined; assuming extern returning int [E:\processhacker\plugins\ToolStatus\ToolStatus.vcxproj]
E:\processhacker\plugins\ToolStatus\taskbar.c(460,61): warning C4047: '=': 'PFLOAT' differs in levels of indirection from 'int' [E:\processhacker\plugins\ToolStatus\ToolStatus.vcxproj]

VS2019 16.8.3 /19041 SDK/WDK

@MagicAndre1981
Add #include <malloc.h> into the \ToolStatus\taskbar.c header.
I fixed this last week but haven't pushed it live yet.

I fixed this last week but haven't pushed it live yet.

works, I also found the docs right now
In Sysinfo->GPU I get a assert when I click on details:

Btw, the Windows on ARM project now supports the Lumia Dock , so you can add a monitor and extend the desktop. So if anyone has the old things, you can use to play with ARM64 version of Windows 10

@MagicAndre1981

In Sysinfo->GPU I get a assert when I click on details:

I'll need the stacktrace to know what caused that issue. There are more than 100,000 calls to that function which could have triggered that assert.

I'll need the stacktrace to know what caused that issue. There are more than 100,000 calls to that function which could have triggered that assert.

I struggle with the remote debugging. ph exe gets copied to the lumia, but not the plugin.

I'm closing this issue since the project is supported and compiles with ARM64... If there are issues/assertions running ARM64 builds then please create a new issue 👍

@MagicAndre1981
That issue will be fixed in the latest nightly.

@MagicAndre1981
That issue will be fixed in the latest nightly.

ok, but please release the ARM64 as nightly. I want to remove the C++ workload to save space in my VM

release the ARM64 as nightly

I don't have any ARM hardware and if something breaks it won't get fixed for days/weeks.

I don't have any ARM hardware and if something breaks it won't get fixed for days/weeks.

I'm using my old Lumia 950XL and run Win10 ARM64, you can try a Raspberry Pi 4 if you have one.

If you want, I can (not very regularly, to be fair) test ARM64 releases myself (not enough time after my normal job to actually contribute though). Allview Allbook Q (SD835).

ok, now it gets complicated @dmex  .
You can now run x64 software on Windows 11 ARM64, so your ARM64 hacks fail.
I see now Virtual<EMAIL_ADDRESS>on my Raspi4 when running the x64 version because it is not the ARM64 build so it executes the cpuid command

So maybe it is better to check the cpu architecture at runtime

when running the x64 version because it is not the ARM64 build
maybe it is better to check the cpu architecture at runtime

You could also use the ARM build when running on ARM where the emulation won't be a problem?

You could also use the ARM build when running on ARM where the emulation won't be a problem?

as I said, I no longer install the C++ workload to save space in my VMs so I can't recompile it. And I only do what endusers do, download and run your last nightly

The build procedure changed a lot. I think the CustomBuildTool need to add something for ARM64. The phapppub.h and other sdk headers are not copied automatically to build tools.

I just got a PI4 and need a good task manager for it :D so I may need to look into porting as much as I can.
For example i don't see yet a good way to distinguish x64 from ARM64EC processes when querying SystemSupportedProcessorArchitectures2 they look exactly the same,
mut M$'s task manager can tel them apart, I wonder how... may be reading PEB fields like ChpeV2ProcessInfo in wonder...

It is possible https://github.com/msys2/MINGW-packages/discussions/8991

mut M$'s task manager can tel them apart, I wonder how

It's just using IsWow64Process2 @DavidXanatos
https://docs.microsoft.com/en-us/windows/win32/api/wow64apiset/nf-wow64apiset-iswow64process2

don't see yet a good way to distinguish x64 from ARM64EC processes

It should be returning IMAGE_FILE_MACHINE_CHPE_X86 (not included in the SDK but rather the WDK ntimage.h)?

On my raspi 4
for a x64 process it returns
ProcessMachine: 0x0000
NativeMachine: 0xaa64
same for ARM64EC and ARM64
IsWow64Process2 seams to work only for 32 bit processes

To me this decisively looks like x64 on arm64 is not longer WOW but a different interoperability mechanism.
Also there is no \Syswow6464 or something folder for x64 and no registry redirection eider.
See:
´´´
NtQuerySystemInformationEx(SystemSupportedProcessorArchitectures2, &handle, sizeof(handle), info, sizeof(info), &length);
x86 on Arm64:
Machine: ARM64;       KernelMode: 1; UserMode: 1; Native: 1; Process: 0; WoW64Container: 0
Machine: x86;         KernelMode: 0; UserMode: 1; Native: 0; Process: 1; WoW64Container: 1
Machine: ARM-Thumb-2; KernelMode: 0; UserMode: 1; Native: 0; Process: 0; WoW64Container: 1
Machine: x64;         KernelMode: 0; UserMode: 1; Native: 0; Process: 0; WoW64Container: 0
x64 on Arm64:
Machine: ARM64;       KernelMode: 1; UserMode: 1; Native: 1; Process: 0; WoW64Container: 0
Machine: x86;         KernelMode: 0; UserMode: 1; Native: 0; Process: 0; WoW64Container: 1
Machine: ARM-Thumb-2; KernelMode: 0; UserMode: 1; Native: 0; Process: 0; WoW64Container: 1
Machine: x64;         KernelMode: 0; UserMode: 1; Native: 0; Process: 1; WoW64Container: 0
Arm64EC on Arm64:
Machine: ARM64;       KernelMode: 1; UserMode: 1; Native: 1; Process: 0; WoW64Container: 0
Machine: x86;         KernelMode: 0; UserMode: 1; Native: 0; Process: 0; WoW64Container: 1
Machine: ARM-Thumb-2; KernelMode: 0; UserMode: 1; Native: 0; Process: 0; WoW64Container: 1
Machine: x64;         KernelMode: 0; UserMode: 1; Native: 0; Process: 1; WoW64Container: 0
Arm64:
Machine: ARM64;       KernelMode: 1; UserMode: 1; Native: 1; Process: 1; WoW64Container: 0
Machine: x86;         KernelMode: 0; UserMode: 1; Native: 0; Process: 0; WoW64Container: 1
Machine: ARM-Thumb-2; KernelMode: 0; UserMode: 1; Native: 0; Process: 0; WoW64Container: 1
Machine: x64;         KernelMode: 0; UserMode: 1; Native: 0; Process: 0; WoW64Container: 0
Arm on Arm64:
Machine: ARM64;       KernelMode: 1; UserMode: 1; Native: 1; Process: 0; WoW64Container: 0
Machine: x86;         KernelMode: 0; UserMode: 1; Native: 0; Process: 0; WoW64Container: 1
Machine: ARM-Thumb-2; KernelMode: 0; UserMode: 1; Native: 0; Process: 1; WoW64Container: 1
Machine: x64;         KernelMode: 0; UserMode: 1; Native: 0; Process: 0; WoW64Container: 0
x64 on x64:
Machine: x64;         KernelMode: 1; UserMode: 1; Native: 1; Process: 1; WoW64Container: 0
Machine: x86;         KernelMode: 0; UserMode: 1; Native: 0; Process: 0; WoW64Container: 0
x86 on x64:
Machine: x64;         KernelMode: 1; UserMode: 1; Native: 1; Process: 0; WoW64Container: 0
Machine: x86;         KernelMode: 0; UserMode: 1; Native: 0; Process: 1; WoW64Container: 0
´´´

compiler error in arm64 build
processhacker\ProcessHacker\syssccpu.c(1685,12): error C2220: the following warning is treated as an error
processhacker\ProcessHacker\syssccpu.c(1685,12): warning C4013: 'CpuIdEx' undefined; assuming extern returning int


fix(cli): less noise from diagnostics

Summary
This PR reduces the amount of diagnostics that bothered some users.
The diagnostics are still present but are now tagged with the verbose signature. Also, I changed the logic of how the --verbose option works.
If users want to see them, they need to pass --verbose

Test Plan
I tested on local project of mine, and I also created new tests.

I was wondering: in the summary of handled files we say that x skipped files. We could also say x skipped protected files?


Response heartbeat key 12 | Error : The coordinator is not aware of this member

{"level":"ERROR","timestamp":"2018-09-17T12:35:16.757Z","logger":"kafkajs","message":"[Connection] Response Heartbeat(key: 12, version: 0)","broker":"<IP_ADDRESS>:28094","clientId":"kafkajs","error":"The coordinator is not aware of this member","correlationId":106,"size":6}
{"level":"ERROR","timestamp":"2018-09-17T12:35:16.757Z","logger":"kafkajs","message":"[Runner] The coordinator is not aware of this member, re-joining the group","groupId":"x-group","memberId":"kafkajs-b39167d2-1a03-437c-a0e9-04ea1130fa16","error":"The coordinator is not aware of this member","retryCount":0,"retryTime":313}
Sometimes I get this error and can be there for long time, then it is working fine.. or sometimes it is not consuming directly because it is showing this... the configuration always is the same, so not understand why sometimes is going fine, and other times not

Hey Elio,
The error you're encountering is because your consumer has not communicated with the brokers in more than sessionTimeout milliseconds (see sessionTimeout in https://github.com/tulios/kafkajs#-options-1).
Basically, in order for the coordinator to know which consumers in the consumer group are healthy, each consumer needs to send a heartbeat to indicate that it is alive. The sessionTimeout option sets after how long the coordinator should consider the consumer unhealthy if it has not sent a heartbeat. How often your consumer heartbeats is configured with the heartbeatInterval option. Note, however, that heartbeatInterval only sets the minimum amount of time that has to pass between each heartbeat. If you take a look at the implementation of eachMessage, you can see that by default we will heartbeat after processing each message, provided that at least heartbeatInterval milliseconds has passed:
https://github.com/tulios/kafkajs/blob/master/src/consumer/runner.js#L129-L158
In other words, what may be happening is that processing each message is taking longer than your sessionTimeout. If so, when the consumer finally finishes processing the message and gets the opportunity to heartbeat, the coordinator will consider it to be unhealthy and you will get the error message you're seeing.
The way to solve this is to think about how long processing each message will take (taking into account any retries or backoff strategies you may be employing), and then setting the sessionTimeout to a bit more than that.
I haven't found any great documentation on this, but this should give you a decent high-level overview: https://www.opsclarity.com/understanding-kafka-consumer-lag/

Just complementing the reply, your heartbeat interval should be at least 1/3 of your session timeout.

@Nevon , you said that the will heartbeat after processing each message, provided that at least heartbeatInterval milliseconds has passed. If a message gets processed very fast, and the next message will only arrive sometime later, can that cause a heartbeat to be missed as well?

If a message gets processed very fast, and the next message will only arrive sometime later, can that cause a heartbeat to be missed as well?

No. It doesn't matter if there are messages to process. On each Fetch request, which happens continuously in a loop, we'll heartbeat if enough time has passed since the last heartbeat.

Question to this, looking at the code you've posted @Nevon. If there's an error of processing the event and together with retries it's taking longer than sessionTimeout the heartbeat is never sent? I mean, imagine a scenario where the DB is down for longer than sessionTimeout and we keep retrying processing the same event. In that case the consumer would get this error after the DB is back up and try to finally commit?

Yes, that is correct. However, since I wrote that comment back in 2018, we have added a heartbeat function to the eachMessage/eachBatch payloads so that you yourself can heartbeat if you want the consumer to still be considered to be alive even though it's stuck.
Keep in mind that this is often not a good idea. For example, consider a network partition where one of your consumers is unable to reach its database, and it keeps retrying the same operation endlessly. If you keep heartbeating during that time, the consumer will continue to be considered healthy and will keep being assigned to its partitions, but no progress is happening. What would be better in that scenario is that the consumer doesn't heartbeat, gets kicked out of the consumer group, the partitions reassigned to an actually healthy consumer, and progress can be made. Once the faulty consumer recovers and tries to heartbeat or commit, it gets told that it's no longer a part of the consumer group and has to rejoin. It's assigned new partitions and continues working. That is the point of the heartbeat mechanism.


Feature: help command

I see that nvy is getting more and more options. It is great. Unfortunately, there is no way to learn what options are available(e.g, I doubt anyone can guess new one --disable-ligatures :) ). I propose adding --help/-h flag to display what options exist.
This --help output should also include the binary version - I do not know how to check current version because nvy --version does nothing.

Thats a good idea, I'll implement this for the next version.


Question about GRU-D implementation

Hi there, I have a question about calculating dp_mask for x_t and m_dp_mask for m_t in your GRU-D implementation (file gru_d.py).
First, the dp_mask is generated from GRUCell built-in function get_dropout_mask_for_cell: code
Then, the dropout mask m_dp_mask for masking vector m_t is generated by calling _generate_dropout_mask: code
By doing so, the dp_mask and m_dp_mask zero out different elements in two inputs x_t and m_t. I can reproduce your result, however, I think that the dropout masks should be the same for x_t and m_t. Can you please clarify this for me? Did I misunderstand something in the core TensorFlow implementation/your implementation?
Thanks for the great work!

Hey ducnx,
good catch! It seems like this behavior is not totally in line with the original publication of GRU-D:

We apply recurrent dropout with rate of 0.3 with same dropout samples at each time step on weights W, U, V.

Where $V$ is the weight matrix for the input mask.
It looks like we retained the behavior from the implementation this code is based on (see https://github.com/PeterChe1990/GRU-D) and did not notice the discrepancy to the original GRU-D implementation.
Unfortunately, the publication is already in print, such that we will not be able to update the description of GRU-D there.
To my understanding, the separate dropout of the input mask does not lead to values being imputed which are actually present. Instead it would reduce the models reliance on observation patterns compared to the original implementation because the independent dropout mask makes it harder for the model to differentiate observed and imputed values. Generally, I think it should not have a detrimental effect on GRU-D performance and might even be beneficial to a certain degree.
Anyway, thanks for pointing this out. I will think of a way to make this apparent for the readers of the paper and users of the code. Until than I will leave this issue open.
Cheers,
Max

Thanks for the comment!
I agree that the behavior from the original implementation is similar to yours. As you explained, using different dropout masks for m_t leads to stronger regularization than using the same mask as x_t. Maybe the performance won't be that much different from using the same dropout mask. I'll check that out.


Added the link for Servicing Stack Updates (SSU)

SSUs are security updates are now security updated and they get synced automatically. I have updated that info and added the link to the document which was missing and now it is pointing to the main document.
Problem https://github.com/MicrosoftDocs/windows-itpro-docs/issues/2999

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: joinimran sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@nenonix @JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks.

Copy edited. No further changes.

@joinimran - Kindly make the recommended changes to the PR. Please see above comments from nenonix and jdeckerms. Thank you.

@nenonix @jdeckerms I have applied the suggested changes. Please confirm at your end.


Absorbing states?

Shouldn't one use an artificial target "policy" made of all zeros here? Then the gradients would be zero, right? 🤔
https://github.com/werner-duvaud/muzero-general/blob/ed3fc8a4532bd4afe564c29c2374e27c0e17544e/replay_buffer.py#L272

Hi,
I think that this part is not detailed in the paper, I am interested if there are similar things in other papers.
We have made the target policy uniform for the absorbing states to avoid biasing the model towards a particular distribution. But we also experimented with only 0's and it didn't make any noticeable difference in performance so I don't know which is best.


Missing SSL certificate option(s) for https request.

Hello,
i need some options for using ssl certificates for an HTTPS request

I think I need this too.
I keep getting:
SSL certificate problem: unable to get local issuer certificate

I can turn it off in test but that are not acceptable in a production environment.
I know I have the certificates in "/etc/ssl/certs/" but nothing I can do to use them.

Should be fixed. Feel free to open a new issue in case this is still a problem.


agent get blocked with zombie vehicles

I test my own code on longest6  while I meet a lot of zomblie vehicles get blocked.  Could you give me some suggestions?

You would need to provide more details on your problem. What do you mean by zombie vehicle?

The zombie vehicle is the other vehicles which set the autonomous driving. I notice the vehicle may get blocked somtimes,  such as no move or block at the  crossroad.  Is that normal ?

If you mean the other traffic can get stuck in intersections this is normal yes.
The algorithm that drives them is not perfect.
Other vehicles will de-spawn randomly if they are stuck for more then 90s which usually resolves this problem.

Thanks a lot


Diagnostic function for Prisma Client (What engine file would be used for Query Engine?)

Problem
Right now the only way to understand what query engine the Client is using, is to look at the .prisma/client folder - which of course does not account for overrides via environment variables, or other code behavior one might not even know about.
Suggested solution
Prisma Client should have a debug function that can be called to get some diagnostic information. The first use case would be to ask it for the path of the engine that would be used to start the query engine to execute queries.
Alternatives
None really.
Additional context
This would be really useful in context of tests for the Node-API functionality, as it would give us a definitive way to understand if Prisma Client is doing what we expect it to do.

Suggestion from @matthewmueller:

Prisma.prismaVersion could also work maybe:
import { PrismaClient, Prisma } from "@prisma/client"
console.log(Prisma.prismaVersion)

$ ts-node index.ts
{
  client: '2.31.0-dev.48',
  engine: '772c82a66c7f237d9b0e89a8bb99d0a10521b759'
}


When will the version 1 stable released?

Any road map for it?
I'm moving from MongoClient to this extension. Looking forward to the stable version to get it work on production.

The primary issue tracker is the "PHPLIB" project in the MongoDB JIRA..
The MongoDB 3.2 release has taken priority lately over shipping 1.0.0-final but its coming "soon" :)
See the 1.0.0 milestone in jira


Ensure that Install apps flow can detect newly-installed FeaturedApplication extension

Dev Home version
0.503.260.0
Windows build number
10.0.23551.1000
Other software
OS Build Version: 10.0.23551.1000.amd64fre.ni_moment_directadept.230915-1358
.NET Version: .NET 6.0.21
Steps to reproduce the bug

Launch Dev Home
Run the Sample Extension from the solution in repository via F5

Expected result
The FeaturedApplication group is shown on the 'Install application' flow
Actual result
I don't see that tile group until I restart Dev Home (the Extensions page detects the extension as expected).
Included System Information
Physical Memory: 63.86GB (44.11GB free)
Processor Architecture: x64
Included Extensions Information
Extensions:
Microsoft.Windows.DevHome.Canary_0.503.260.0_x64__8wekyb3d8bbwe
Microsoft.Windows.DevHomeGitHubExtension.Canary_0.501.260.0_x64__8wekyb3d8bbwe

Looks like this is a dupe of #1553, will close this one out (thanks, @AmelBawa-msft!).


Getting time from an RTC

Hello dears,
Can the code be changed to get the time from an external I2C RTC like DS3231 module instead of internet?
The time does not persist during reboot, without the internet connection.
Thank in advance

It would be very useful!
The best would be to set from GUI the GPIO for the optional I2C RTC connection...

@matjack1 Can I add functions and GUI to select the RTC clock of I2C? Power failure is very useful

Sure! It would be brilliant!


Use UDFs as sources

Background
With the amount of sources and how different is consumed by the clients, using UDFs could help to support more sources:

Http long pooling  (Internal APIs)
WebSockets/SSE (GraphQL/Rest)
Grpc Endpoints

Design
The UDFs are already supporting tables, and use yield to generate the values through streaming futures https://github.com/risingwavelabs/risingwave/blob/ed75502880af4fad364b9821ab85e7026188063d/src/expr/core/src/table_function/user_defined.rs#L93-L132.
This functionality could be translated to tables/sources to emit records when a new value is received from the UDF, using a sintax like CREATE [TABLE|SOURCE ] .. AS  <function_name> (param1, param2)
Future Optimizations

Add support for async wasm UDFs
Define a way to provide splits
Add support for local state (to keep things as the auth tokens)

Discussions
No response
Q&A
No response

https://github.com/risingwavelabs/rfcs/pull/87#issuecomment-2333169493

https://github.com/risingwavelabs/rfcs/pull/87#issuecomment-2333169493


Algorithm to check if a graph is connected or not

Assign this task to me

yes i want to contribute to this repo please assign me this task


Some clean ups to the node client

This will close #47 and probably more.

is this ready?

is this ready?

Yup! Once 579 is merged and this is updated to use the fluvio composite action. :crossed_fingers: :rocket:


Improve CLI (@vscode/l10n-dev ) feedback

Hi,
After updating half dozen of my extensions to support l10n I can say that both API and tooling, are really easy to use. Congrats!
And, as a feedback to the CLI (@vscode/l10n-dev), specially for newcomers, I would suggest a few improvements related to error messages and default values.

[ ] Validate if the pre-requisites are correctly set in package.json, like:

[ ] The engine and @types/vscode entries are defined to 1.73.0 minimum
[ ] The l10n entry is also defined

[ ] Use the value defined in l10n entry, if --outDir param is missing

Thank you

Dear me. :-) I know it's not the proper place to ask but how do you use it? Documentation seems very contradicting, some suggest to use the vscode/l10n dependency, others say it's built-in already if you only want to use in the main extension. package.nls.json gets picked up all right but I simply can't make the bundle.l10n.json file to work.
Trying to use vscode.l10n.t() gives an error of Property 'l10n' does not exist on type 'typeof import("vscode").
If I do depend on the package, then I can import:
import { t } from "@vscode/l10n";

And it looks like it might work but then comes a very nasty surprise: is it real that, in the bundle files, I have to use the English original as a key? Can't I use a key like in the package level? Eg:
"extension.key1.text": "first text",
"extension.key2.text": "second text",
"extension.key3.text": "three text",

Really? This is insane, no other localization does that. What makes you think the same original will always be translated to the same? There are homonyms in English. There might be situations when the same expression has to be spelled, cased or translated differently, depending on context. Tell me I misunderstood something...

Can you split these up into separate issues? We do 1 issue per issue. This makes it easier for issue verification at the end of the month

For sure. Created #66 for the second request.
Thank you

The engine and @types/vscode entries are defined to 1.73.0 minimum

I think @vscode/vsce should already handle this so I don't think we need to do anything in this package.

The l10n entry is also defined

This is a must


Changed IP then CSS files 404

I had to rebuild a server and changed IPs but same domain. When I fire up new server everything works except 404 for all pagespeed CSS files.
Other file types appear to be working as expected, and when I try ?ModPagespeed=off it fetches the correct file directly and everything looks fine.
Running the same CSS related stuff as old configuration
 #CSS handling
 pagespeed EnableFilters combine_css,fallback_rewrite_css_urls,flatten_css_imports,inline_css,rewrite_css;

I did not set this up initially, and this is my intro to pagespeed. Any ideas of what I am missing here?

Maybe the dns resolution is being cached for the domain on the server. The module would then attempt to fetch from the old server.

| I did not set this up initially, and this is my intro to pagespeed. Any ideas of what I am missing here?
Before this, you do nothing with css files?
Can you try https;//mydomain.com/?PageSpeedFilters=+debug anf then look at the html code to see debug messages?

It seemed to be working for a while tonight. CSS files were all being delivered. All I did was purge the cache a few times. Then I was switching between Google users (chrome instances) and then all CSS 404ed again.
Could it have something to do with this session cookie?
#this next part requires the more_clear_headers module - if nginx fails, remove this
if ($skip_cache = 0 ) {
    more_clear_headers "Set-Cookie*";
    set $rt_session "";
}

This is the only thing I didn't install from the previous setup. Based on the comment I found I just skipped it.

When you cleared the cache, css files are served rewrited by pagespeed or are the original css files?
My bet is that some thing has changed and pagespeed is unable to fech the resources.
I you try https;//mydomain.com/?PageSpeedFilters=+debug maybe the debug messages (as html comments in the code) have some clue.
How pagespeed fecht https resources (What config have)?
What domains have you authorized?
Have you tried the LoadFromFile?

I am back trying to get our server up again.
This is a gist with the output from ?PageSpeedFilters=+debug
The configuration

PageSpeed appears to be partially working, with a couple CSS files not being found

When I purge the cache:
That initial reload looks fine as it is fetching the actual server resources.
 Once in a while it is the main CSS file, which is catastrophic.
The configuration is exactly the same on this new server as the current one. This new one has new versions of Ubuntu, PHP, Nginx, etc.

This is a gist with the output from ?PageSpeedFilters=+debug

No, this gist contains only javascript, in not the output from the filter.
Some server config is wrong, when I try to PageSpeedFilters=+debug,-inline_css this come in an infinyte loop, the plus sign is decoded to %20....
The outpu from the debug filter is some like:

You can see in green the debug messages.
An other question is that some css don´t be manipulated by pagespeed.
Ths one is:

But this other not:

See the diff betwen the Etag headers, and the second image don´t have the pagespeed header. Both are from your domain, so are authorized.

I still haven't figured this out...granted I just now put the new IP live for the first time since my last post. I seems to randomly produce 404 errors for CSS files - but only some of them.

I still haven't figured this out...granted I just now put the new IP live for the first time since my last post. I seems to randomly produce 404 errors for CSS files - but only some of them.

I would recommend putting the module in OptimizeForBandwidth mode to avoid the need for http(s) fetching while figuring this out. You may also want to check https://www.modpagespeed.com/doc/https_support#configuring_ssl_certificates as a potential culprit.

The issue persists. When I purge the cache everything runs fine for a couple days, then I start to get 404s again on some CSS files. If it happens to hit the main CSS it becomes a critical situation. I purge the cache a couple times and everything works again.
Here is our output from ?PageSpeedFilters=+debug:
https://gist.github.com/benjaminadk/75cbcaf8c0ab21541ade94de3120be79
Here is our current config:
# ...

# PageSpeed Admin
pagespeed StatisticsPath /ngx_pagespeed_statistics;
pagespeed GlobalStatisticsPath /ngx_pagespeed_global_statistics;
pagespeed MessagesPath /ngx_pagespeed_message;
pagespeed ConsolePath /pagespeed_console;
pagespeed AdminPath /pagespeed_admin;
pagespeed GlobalAdminPath /pagespeed_global_admin;
pagespeed Statistics on;
pagespeed StatisticsLogging on;

# PageSpeed Cache Purge
pagespeed EnableCachePurge on;
pagespeed PurgeMethod PURGE;

pagespeed MessageBufferSize 300000;
pagespeed FileCachePath /sites/ladesignconcepts.com/pagespeed-cache;
pagespeed ForceCaching on;
pagespeed FileCacheSizeKb<PHONE_NUMBER>;
pagespeed FileCacheCleanIntervalMs   3600000;
pagespeed FileCacheInodeLimit        500000;
pagespeed SslCertDirectory /etc/ssl/certs;

server {
  # ...

    # Pagespeed Config
    pagespeed on;

    location ~ "\.pagespeed\.([a-z]\.)?[a-z]{2}\.[^.]{10}\.[^.]+" {
        add_header "" "";
    }

    location ~ "^/pagespeed_static/" { }

    location ~ "^/ngx_pagespeed_beacon$" { }

    # Disable pagespeed WP Admin, Woo cart, etc
    pagespeed Disallow */wp-admin/*;
    pagespeed Disallow */cart/*;
    pagespeed Disallow */ideas/*;
    pagespeed Disallow */my-account/*;

    # PageSpeed Filters
    pagespeed RewriteLevel PassThrough;

    pagespeed EnableFilters add_head;
    pagespeed EnableFilters convert_meta_tags;
    pagespeed EnableFilters extend_cache;
    pagespeed EnableFilters rewrite_style_attributes_with_url;
    pagespeed EnableFilters inline_import_to_link;

    # HTML
    pagespeed EnableFilters insert_dns_prefetch;
    pagespeed EnableFilters collapse_whitespace,remove_comments;
    pagespeed EnableFilters canonicalize_javascript_libraries;
    pagespeed PreserveUrlRelativity on;
    pagespeed ImagePreserveURLs on;

    # CSS
    pagespeed EnableFilters combine_css;
    pagespeed EnableFilters fallback_rewrite_css_urls;
    pagespeed EnableFilters flatten_css_imports;
    pagespeed EnableFilters inline_css;
    pagespeed EnableFilters rewrite_css;

    # JS (Disabled)
    #pagespeed EnableFilters combine_javascript;
    #pagespeed EnableFilters inline_javascript;
    #pagespeed EnableFilters rewrite_javascript;

    # Images
    pagespeed EnableFilters sprite_images;
    pagespeed EnableFilters lazyload_images;

    # Images (Disabled)
    #inline_images,recompress_images,convert_to_webp_lossless,resize_images.
    #pagespeed EnableFilters rewrite_images;
    #pagespeed DisableFilters convert_jpeg_to_webp,convert_to_webp_lossless,convert_to_webp_animated,recompress_webp;
    #pagespeed EnableFilters responsive_images,resize_rendered_image_dimensions,resize_images,responsive_images_zoom;
    #pagespeed EnableFilters strip_image_meta_data,strip_image_color_profile;
    #pagespeed EnableFilters jpeg_subsampling,recompress_jpeg,recompress_png,;
    #pagespeed EnableFilters convert_png_to_jpeg,convert_gif_to_png;
    #pagespeed EnableFilters convert_jpeg_to_progressive;

    # Lazy Loading (Disabled)
    #pagespeed LazyloadImagesBlankUrl "https://www.gstatic.com/psa/static/1.gif";

    # Prioritize (Disabled)
    #pagespeed EnableFilters defer_javascript;
    #pagespeed EnableFilters prioritize_critical_css;

    # Google Analytics Async
    pagespeed EnableFilters make_google_analytics_async;

    # Google Fonts
    pagespeed FetchHttps enable;
    pagespeed EnableFilters inline_google_font_css;

    # Domains
    pagespeed Domain https://ladesignconcepts.com;
    pagespeed Domain http*://*.ladesignconcepts.com;
    pagespeed MapRewriteDomain ladesignconcepts.com images.ladesignconcepts.com;
    pagespeed MapOriginDomain localhost ladesignconcepts.com;
    pagespeed ShardDomain https://images.ladesignconcepts.com https://ladesignconcepts.com;

    pagespeed MaxSegmentLength 250;

    # Memcached
    pagespeed MemcachedThreads 1;
    pagespeed MemcachedServers "<IP_ADDRESS>:11211";
}

# ...

1.- pagespeed FetchHttps enable  need
pagespeed SslCertDirectory directory;
pagespeed SslCertFile file;

See  https://www.modpagespeed.com/doc/https_support#configuring_ssl_certificates as stated by @oschaaf
2.- pagespeed Domain https://ladesignconcepts.com; and pagespeed Domain http*://*.ladesignconcepts.com; are redundant, the 1st is included in the 2nd.
3- Why you need MapRewriteDomain, MapOriginDomain and ShardDomain?
Whit pagespeed MapRewriteDomain ladesignconcepts.com images.ladesignconcepts.com; any images.ladesignconcepts.com in the html code is converted to ladesignconcepts.com but I can´t see any images.ladesignconcepts.com in the html code when pagespeed is turned off.
Whit pagespeed ShardDomain https://images.ladesignconcepts.com https://ladesignconcepts.com; you try to download request to https://images.ladesignconcepts.com from https://ladesignconcepts.com but you use http2 so no shard works here. Http2 creates 1 connection and download all assets from this connection.
Whit pagespeed MapOriginDomain localhost ladesignconcepts.com; you make a request to localhost when the client request http://ladesignconcepts.com. This need 2 servers blocks in nginx config, 1 for localhost (http) and 1 for ladesignconcepts.com (http).
If ladesignconcepts.com is https and you have this config, then the directive must be set as:
pagespeed MapOriginDomain localhost https://ladesignconcepts.com;

@Lofesa, thanks for bringing these issues to my attention. I inherited this whole project and have no idea who wrote the code or set it all up. These issues aren't surprising, there have been many.
I attempted to address the config issues:
1 - I added  SslCertDirectory /etc/ssl/certs and I read the follow to mean I would not set SslCertFile file; on my VM.
The default directory for Debian-based systems is /etc/ssl/certs, and there is no certificate file setting.

2 & 3 - I commented out MapRewriteDomain, MapOriginDomain and ShardDomain.
I will continue to monitor this issue.

I have tested it now, and don´t have any more 404 error.
But some css files are "out of radar" for pagespeed module. You may compare the http headers of css files from your own domain (from others domains not to be rewrited by pagespeed is normal) and you can see diffs betwwen these rewrited by pagespeed and those not rewrited.
Maybe there is a Disallow directive for those css files not rewrited?

yes. i put a Disallow on a couple css files for plugins.

So I finally got a 404 on the main CSS file today. One week since the last time it happened. I purged the cache and all is well.

@benjaminadk did you end up resolving the issue or is this something that come back link boomerang ?


Bootstrap Migration for Layout.tsx

This issue is meant to track some of the remaining work needed to close out the migration from css modules to react-bootstrap/styled components/typescript. This card covers the migration for the main site layout page - Layout.tsx
Success criteria:

[ ] Refactor components to integrate Bootstrap and styled components while removing CSS modules.
[ ] When called for, find or create reusable (sub)components to reduce repetition and ensure uniformity.
[ ] Create or revise the Storybook story for these components, and any new sub-components.
[ ] Convert from js to tsx

The components covered by this issue are:

[ ] Layout.tsx (The base site layout)

Just as a callout, this page includes the main site Nav component's styles.


fix: bad links and refs

closes #53
this just cleans up all of the bad ref links throughout. the issue was
i created targets like this
On the share code page, I made a (share-code)= reference. But this becomes confusing when you have a page name that can be used in an index file tree within the dir that also has a reference with the same name! So that was the main issue that I hadn't considered.
once we merge this CI should be happy again (i think!).

@willingc this pr fixes all of the red CI issues. and it will close the open issue about the red x too. CI breaking bugs me too 😆


Scheduling a container to different host does not work when upgrading

Rancher Version:
1.2.0
Docker Version:
1.12.5
OS and where are the hosts located? (cloud, bare metal, etc):
rancherOS, baremetal
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
2 node cluster, single Rancher Server (internal DB)
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle Environment
Steps to Reproduce:
Start a service with one container. It gets placed on host x in an active state.
Now update/upgrade that service selecting Schedule -> Only one Host -> Select a different host.
Results:
The update process completes, but merely starts up another instance of the container on the same host.
Expected:
The update process to spawn the new container on the host I explicitly defined on the update page.

Note that If I launch a stack unticking "start services on creation" I can then "upgrade" the service, select the host I want, and then spawn it.

Version - 1.2.1 - Checked and this is still an issue in the current release.

@vincent99 - not sure what we can do here.  Do we want to remove the option to go directly to a specific host?

Hmm. I don't really mind how its handled, so long as there is something there letting me know that functionality won't actually work the way I'd expect it to (maybe just a little note or something). Maybe it is best you remove that option entirely or maybe gray/shadow it out so people understand its not a supported action when doing an upgrade.

1.2.1: I just tried editing a service, adding a host label rule to change which host a run-once service runs on -- no effect.

With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.


Quota Management API

Quota Management API
http://www.w3.org/TR/quota-api/

This issue was imported from Google Moderator
Moderator votes: +5
Issue added by Ginaria on 2014-04-09
To vote this issue up or down, simply include +1 or -1 in your comment.

+1

+1

+1

+1

+1

Status Edge:
https://developer.microsoft.com/en-us/microsoft-edge/platform/status/quotamanagementapi/

It was implemented for a moment in Chrome but removed again in favour of the new API: https://storage.spec.whatwg.org/
Firefox is said to have it implemented, too.
Chrome status: https://www.chromestatus.com/features/5630353511284736

Original Quota Management API is available at https://caniuse.com/#feat=mdn-api_storagequota though support info is limited to will leave this open.

My comment from #3246 (probably a dupe):

Previously tracked in MDN browser compat data but removed in mdn/browser-compat-data#9459 due to a lack of implementations.
The Quota Management API spec has been unmaintained since 2018, and the MDN link now redirects to: https://developer.mozilla.org/en-US/docs/Web/API/StorageManager
StorageManager is defined in the WHATWG Storage Standard: https://storage.spec.whatwg.org/#storagemanager
And the StorageManager API is covered by MDN browser compat data: https://caniuse.com/mdn-api_storagemanager
(via mdn/browser-compat-data#1441, mdn/browser-compat-data#2272)


[SPARK-44727][CORE][DOCS] Improve docs and error message for dynamic allocation conditions

What changes were proposed in this pull request?

Clarify the DRA enabling conditions in docs and error message. (no \n actually)
Dynamic allocation of executors requires one of the following conditions:
1) enabling external shuffle service through spark.shuffle.service.enabled.
2) enabling shuffle tracking through spark.dynamicAllocation.shuffleTracking.enabled.
3) enabling shuffle blocks decommission through spark.decommission.enabled and spark.storage.decommission.shuffleBlocks.enabled.
4) (Experimental) configuring spark.shuffle.sort.io.plugin.class to use a custom ShuffleDataIO who's ShuffleDriverComponents supports reliable storage.

Why are the changes needed?

Currently, ESS is not the only way to support DRA, but users always see the misleading error message when it does not meet the DRA conditions
Dynamic allocation of executors requires the external shuffle service. You may enable this
through spark.shuffle.service.enabled.

This is misleading, especially for users who want to enable DRA in Spark on K8s cases.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

Review.

cc @holdenk @dongjoon-hyun @mridulm

thanks, merged to master and 3.5


state setitem

implement a setitem for state, that essentially allows input of any type and casts it to a StateElement

See PR#76