[Bug]: Moshi not cutting rasters

Summary Description
First, I just got this old K40 with a moshi board10105 v4.87 .  I am new to git hub too so I am learning. Let me know if I am not following procedures correctly.
I appreciate the work this community is doing with this software.
I seem to be cutting ok. But The problem I am having is raster cutting paths.  I created the design in inkscape, converted text and paths to outlines.  saved as svg and inported to meerk40t,
When laser runs just the raster action, it cuts a few lines of the raster then either runs to the left or right and rams into the rail.  I was running at 150mm/sec but I read some where to run at 70 mm/sec but that did not help.   Then I started to home the machine before each time I executed the file.  still same problem.
First what is the correct steps to load a cut to the laser after it is imported to meerk40t?  Execute - validate - blob - spool?  or can I just arm - start the file to the laser.
Based on other post I am including some screen shots.  I do not know if it is important for your analysis.
here is the meerk40t screen and file

this is the the results of the job at 150 mm/sec.  ran a few lines then rammed straight into the right rail (blue marker)

this is the results at 69 mm/sec. more lines where cut but then rammed straight into left rail.

Thanks for all you help.
Additional Details
No response
Crash logs
No response
MeerK40t Version
0.7.5001
MeerK40t Type
Executable
Your Operating System
Windows

First what is the correct steps to load a cut to the laser after it is imported to meerk40t? Execute - validate - blob - spool? or can I just arm - start the file to the laser.

Arm -> Start is just a shortcut for running through all the steps in the Execute Job window.

First what is the correct steps to load a cut to the laser after it is imported to meerk40t? Execute - validate - blob - spool? or can I just arm - start the file to the laser.

Arm -> Start is just a shortcut for running through all the steps in the Execute Job window.

So it is an ok procedure to arm - start for the moshi board instead of running through all the steps in the execute window?

So it is an ok procedure to arm - start for the moshi board instead of running through all the steps in the execute window?

Yes it's the same. You can also disable remove the arm button in Settings.
Regars your issue that bumps into the rail on left side is because moshiboard need some margins in x-y so just move your object 10mm right and 10mm bottom

@TheGarageEngineer can you test the svg file below and check if the raster is in the right place, please?
Just do right click on the picture below and save as, to get the file.

So it is an ok procedure to arm - start for the moshi board instead of running through all the steps in the execute window?

Yes it's the same. You can also disable remove the arm button in Settings.
Regars your issue that bumps into the rail on left side is because moshiboard need some margins in x-y so just move your object 10mm right and 10mm bottom

Thank you for info. Great ideas. I will try.  But it's not just bumping the rail it is hitting the rail and staying on the rail and looks like it is trying to continue the cut on the rail.  And not moving left or right. But let me try your suggestion

Thank you for info. Great ideas. I will try. But it's not just bumping the rail it is hitting the rail and staying on the rail and looks like it is trying to continue the cut on the rail. And not moving left or right. But let me try your suggestion

When it touch the end stop moshiboard not working as expected so just give some margins and don't forget that raster have overscan so i think you need add margins on x axis even considering this value.
if you can test the file i sent you before i would be grateful because i opened an issue of wrong raster position with moshiboard that we couldn't solve so it would be helpful if you also have the same problem or just me.

So raster cut first and was off and low.  cut boarder was in correct location

So I tried to run my logo as I did yesterday.  Yesterday I was at (0,0) but today I moved to start position to (20,20) and this is what I got.

#1 arrow - raster started low (offset), just like the 'test' raster. after a few lines it moved to location #2
#2 arrow - and continued the raster where it left off from #1. after a few more lines rastered
#3 arrow -  it moved to the right about 10mm and began the outline cut sequence, but instead of moving in a circular pattern as per the design it cut a straight line because the lens was headed to the right rail and would have crashed the rail if I had not turned off the machine.
I hope this helps with the diagnosis.

@TheGarageEngineer have you tried with 0.7.5000 version instead of .5001?
In the last version the paths are engraved separatly that maybe can introduce more issues with moshiboard.
At the moment on the first start the raster is not inbox but after finish if you click start again without touching anything the text is inbox so in the right position.

@tatarize as you can see here regards to moshi raster position the issue is in the object position maybe when calculate the offset.
In my tests the margins was 10,10 and the raster is just a little bit below the vector box, in this case with margins 20,20 the raster position is like double times below the box

@dorsi90 I have not tried 0.7.5000   I will look into that.
I only ran file once.  I did not click start again without touching anything. I will try that procedure and respond with my results.

Ok, you have my same issue.
If you can send your svg file i can test it for you as well.

Ok, you have my same issue. If you can send your svg file i can test it for you as well.

@dorsi90
Here is my file.
Also, have you tried ver 0.7.500 yet?  does the same problem occur with the 'test' file?

@TheGarageEngineer yes is the same but you use the executable so i think only has ruida control filx and not include the raster path separation maybe it was included later and usable only if you run the app from source code. Basically it engrave the letters separatly and in my case the T was in wrong place so outside the box while EST are in the right place inside the box.
Tomorrow i check try to engrave your file and tell you what happen.

In console, type: set -p moshi/driver/0 enable_raster False
This will turn your rasters into hard-rasters which will basically make these things correct. I ordered the new moshiboard because even with the added debug stuff I narrowed down some of the issues but it didn't see to correct things fully. I could also try extra move-to-origins after every raster since that seems to be the core protocol there. And may be a solid enough check for that branch.

@TheGarageEngineer your file looks like my file so on first start the raster is in wrong position

While on second start it's perfect

@TheGarageEngineer your file looks like my file so on first start the raster is in wrong position
While on second start it's perfect

I wasn't even getting the consistency that you got.  But I will try what @tatarize recommended and see if that helps.
Thanks

I put the object in position 10,10.
I have already tested setting enable_raster to false and the raster is in the right position but the engraving is done very slow like vector engraving so you burn too much.

good to know about the 10,10.  That is probable why I was having problem.
What is the difference between raster engrave and vector engrave?

You can read the differences and others good information from meerk40t wiki here

So I have not changed the settings yet but I ran a test of my logo
I positioned the logo at 10,10. It started the raster lower than it should be as we have been seeing. But it only ran a few lines.  Then it stopped.  Moved to the correct location on the computer screen and then continued the raster.  Then it did the proper cut out.
Then with out doing anything.  I ran it again.  The lens took off directly to the right rail.  I turned the machine off so it would not crash.
@dorsi90
I beginning to think I need to change the board out.

With version 0.7.5001 this also happens to me, try the version 0.7.5000
I see also that you engrave from bottom to top while i set top to bottom in raster operation i don't know if it introduce more issues. However i think that with this board at the moment is better to use moshidraw that also has many many bugs but when start to engrave it complete the job without issues.

I beginning to think I need to change the board out.

I already bought the M2 Nano board from AliExpress for 22 euros (only the mainboard) and i still waiting that arrive to me and i can start to use this beautiful software

With version 0.7.5001 this also happens to me, try the version 0.7.5000
I see also that you engrave from bottom to top while i set top to bottom in raster operation i don't know if it introduce more issues. However i think that with this board at the moment is better to use moshidraw that also has many many bugs but when start to engrave it complete the job without issues.

I beginning to think I need to change the board out.

I already bought the M2 Nano board from AliExpress for 22 euros (only the mainboard) and i still waiting that arrive to me and i can start to use this beautiful software

Where could I get moshi draw?  I went to their website but the only button I was on the page was buy.  And it did no action. Do you have a link to moshidraw?
I have a diode laser ortur laser master, I think it has a gbrl board. I think I am going to look at it to see if it can be rewired for the m40.

Which software do you use for your k40?
Do you have the usb dongle? Is it red or orange?

I have nothing.  I was given the machine and that was it.  No dongle either.  That is why I was hoping meerk40t would work better
Dennis Machida
Trail47.com
On Mar 18, 2022, 4:58 AM -0400, Giuseppe @.***>, wrote:

Which software do you use for your k40?
Do you have the usb dongle? Is it red or orange?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

The software requires windows 7 or so, and the dongle which also requires some drivers. So it's a bit of a pain to get it working even if you had the dongle which would run like $110 dollars to get a replacement for. The best bet is to order a new M2 Nano. I need the hardware to figure out the issue it'll still be a while before it arrives. And a bit longer to test the stuff. I wish it worked better too. It seemed to mostly work before and the current PR trying to fix it just doesn't do enough though I think it should be better if I homed it between each raster event. Which I think I should be able able to make sure it actually does. And hopefully I'll find a little bit of time to home before each raster, and try that.
Even if you can find the Moshi software, it does absolutely require that dongle and it's a bit of a pain to get the dongle drivers to work. The M2 Nano board runs 25 bucks and has a lot of open source support today. And you can get pretty reasonable GRBL cards for 80 bucks or so.

I agree with @tatarize that is better to buy the M2 Nano. I have the moshi software and i also can send you it but without usb dongle it's not working. In my case with windows 8.1 OS the red usb dongle not required drivers i don't know for orange dongle but the price is of course expensive then M2 Nano board If you bought k40 you can ask to the seller for the dongle that usually is included when buy this machines.

But, 25 bucks and deal with the weird power connection issue is likely preferred.  My replacement moshiboard is 10 days before it even gets on the Chinese boat. Though I could try homing before each raster attempt in the moshi branch where I tried to fix most of the errors. https://github.com/meerk40t/meerk40t/pull/878
And there's a couple other things I could try. It wouldn't be that hard to add in a bunch of potential raster fixes as settings that are disabled and ask for some attempts to be made.

Raster offset always set to 0.
Home before all rasters.
Raster start at first position for the given offset (never use move).
Avoid all negative numbers within rasters by setting correct minimum offset.

I seem to recall when I was trying to get rasters working they were a bit annoying and sort of broke a lot. And had a somewhat nasty habit of suddenly running into the left wall. I got a version of raster that seemed like it worked. Though I now realize it must have been off in positioning and without outlining the raster I messed that up. There's only so many ways to build a moshiblob, but even in the best conditions I still consider moshiboards to be a bit inferior to M2 Nano, except that they store their current position which is sometimes rather nice. And I don't know how big the buffer is but I've never needed to know since it seems like it hasn't tapped out for me.

I think I will look into a new board
@dorsi90 @tatarize  Check out this video. The presenter sounds like he was having the same issue with moshi. Then upgraded to a cohesion 3d board.
https://youtu.be/iB6wjvk6vRc

@TheGarageEngineer it is not the same he used moshidraw without know how it works. Moshidraw crash when manipulating the object, can't import svg files, ecc but it works perfect when engrave and cut. It can use the position relative to the plane or to the object so if you use relative to the object without know how it woks then you have wrong positions.
Cohesion 3D is a good board to use with lightburn but you need to buy a license.
@tatarize the buffer is more then 4kb. When engraving large image in moshidraw it show the total data to send and after it has sends some data it show busy message then when not busy sends 4kb and then busy again.

Sweet. I had always wondered that. It isn't too hard to detect the device as busy but it wasn't clear where the cutoff was between one chunk of data and the next. But, there should be some data limit since infinite buffer isn't plausible.

Well, I got my new replacement moshi card. I can at least test this on hardware and I'll hopefully find a time to do that.

I am still waiting for the m2 nano card.  Starting from the second time the raster is in the right place but sometimes after the head moves to the object location and when start the raster mode the head moves to the right direction and bumps into the rail so i need to turn off the machine and start it again.
Which moshiboard version do you have?


Listing records Builder in sitemap.xml

Added output of records via Builder List on the page. Can I add them all to sitemap.xml?

@WebProviderNGO not directly through the Builder plugin. You would have to create a plugin that listens for the page.menuItem events that are provided in the Pages and Sitemap plugins and register a new type of navigation item from the records you created in your Builder-built plugin.


A result looks wrong

@MatthewLQM Please explain your pull request in details.

    x = tf.constant([[1, 2, 3],
                     [4, 5, 6],
                     [7, 8, 9]])

    print(x[:].numpy())

This code have result:
[[1 2 3]
 [4 5 6]
 [7 8 9]]

but in master branch, it shows
[[1 2 3]
 [4 5 6]]

@MatthewLQM I do not see that issue. One previous was merged now. Please report this as an issue if it persisted. Also please take a look at this section.


Can you support cocoapds

I’m afraid not: our experience with Swift-NIO is that cocoa pods were a substantial maintenance burden for us.


Add support for AppEngine-specific dialer.

The default gRPC dialer does not seem to work on AppEngine. This will be e2e tested by deploying a Go app to AppEngine.

Unfortunately we can't easily trigger the new codepath in a unit test, since it is gated by an API that checks whether the application is running on AppEngine. For safety, I've flag-guarded this feature and we will prioritize setting up a Kokoro test that launches an AppEngine app and tests out this code.


Can I store files with arbitrary checksum generation?

First of all: I was planning on using this server for storing build artifacts which are not generated by bazel so this might just be out of scope.
I am generating the sha256 from the files that are used to generate the resulting binary. Then when I do a PUT with /cas/my-generated-id i get:
checksums don't match. Expected ab4c0ae56fa464863c133ec2d4607fbc36dfbe869909713c392e4dd874693c91, found 11e0900e166a593f26fa999a73b1ea9174bea4b29f4cf15cd8e1ac4e0c323045

I looked into the code and sure enough the sha256 for the uploaded file is generated and compared to the provided sha.
My question comes from (probably) misunderstanding how bazel works:
Doesn't bazel also generate the sha256 before building the artifact from files/env variables/parameters? Isn't that the whole trick? Where does the assumption come from that the sha256 should be that of the file? Maybe you can clear up my confusion.

Nvm read the docs.

Bazel breaks a build into discrete steps, which are called actions. Each action has inputs, output names, a command line, and environment variables. Required inputs and expected outputs are declared explicitly for each action. You can set up a server to be a remote cache for build outputs, which are these action outputs. These outputs consist of a list of output file names and the hashes of their contents. With a remote cache, you can reuse build outputs from another user's build rather than building each new output locally.

I understand this as: I need to create those actions and the corresponding meta data and then upload the files with their sha256

If you want to use bazel-remote as a memcached-style LRU (but with a filesystem backing store), ie without sha256 verification, you can use the --disable_http_ac_validation flag, and use URLs of the format /ac/


Add missing lifecycle APIs

program.unload
link.pin() for FdLink only

and any others that appear missing.
Related to aya-rs/book#26

Also done


Fix matching proper PipelineRun with /test

We were always getting the first one of the pipelinerun, i thought the
filtering was already done and it would always be only one PipelineRun
but we re-fetch everything on resolve.Resolve, so redoing the filtering
properly.
Improve e2e to make sure it handles this properly to explicit test the
proper PipelineRun.
Refactor a bit the gitea tests for GitOPS commands to be in its own file.
g# Changes

Submitter Checklist

[ ] 📝 Please ensure your commit message is clear and informative. For guidance on crafting effective commit messages, refer to the How to write a git commit message guide. We prefer the commit message to be included in the PR body itself rather than a link to an external website (ie: Jira ticket).

[ ] ♽ Before submitting a PR, run make test lint to avoid unnecessary CI processing. For an even more efficient workflow, consider installing pre-commit and running pre-commit install in the root of this repository.

[ ] ✨ We use linters to maintain clean and consistent code. Please ensure you've run make lint before submitting a PR. Some linters offer a --fix mode, which can be executed with the command make fix-linters (ensure markdownlint and golangci-lint tools are installed first).

[ ] 📖 If you're introducing a user-facing feature or changing existing behavior, please ensure it's properly documented.

[ ] 🧪 While 100% coverage isn't a requirement, we encourage unit tests for any code changes where possible.

[ ] 🎁 If feasible, please check if an end-to-end test can be added. See README for more details.

[ ] 🔎 If there's any flakiness in the CI tests, don't necessarily ignore it. It's better to address the issue before merging, or provide a valid reason to bypass it if fixing isn't possible (e.g., token rate limitations).

/lgtm

/lgtm


[updater] Updating Windows app from Tauri 1 to 2 repeats update dialog

I had an app built with Tauri 1. When I transitioned and published the app with Tauri 2, I got the update dialog as usual. I install the new update, but the app restarts in the version it tried to replace. I selected download again, and it goes on as a loop.
I checked my installed programs, and I had two versions of my program installed, one 1.3.2, and another 1.3.4.

Just to be sure, did you test msi -> msi or setup.exe -> setup.exe ?
Assuming we're talking about https://github.com/calejvaldez/YouAreTyping/releases/tag/v1.3.4 then latest.json points to the .msi which means that if you install the first app instance via setup.exe the update will fail.
(setup.exe -> msi updates are somewhat supported but not the other way around)

Thanks for the quick response!
When I first noticed it, I wasn't sure how I originally installed it. However, the second time around (redownloaded to make sure) it was msi -> msi.

Came back with more information.

The Updater installed the v2 version (1.3.4), but also keeps the v1 version installed (1.3.2).
When I open the file location of the program, I'm sent to this folder:

Where You Are Typing.exe is 1.3.2, but you-are-typing.exe is 1.3.4, again keeping both installed. When the Updater restarts the program, it restarts using You Are Typing.exe.
My workaround is just instructing users to delete 1.3.2.

Ah okay, this one is tracked here https://github.com/tauri-apps/tauri/issues/10355 - i'll keep your issue open though so it's tracked on both repos.

Closed by https://github.com/tauri-apps/tauri/pull/10962 and https://github.com/tauri-apps/tauri/pull/10969


How to Remove Old 2FA Device and Register New One?

Hi,
Was using the mithril plugin integrated with my AD, and was able to set up the environment fine.
Unfortunately, one of the users had to have their phone undergo factory reset, resulting in the old device being no longer valid.
How can I delete the old 2FA device and let the AD user register a new one?
Thanks

Hello,
When using AD for authentication, 2FA secrets are stored on disk using the file storage.
The path to the file is configured in config.json, the default value is "file": "users.json"
To reset 2FA you need to stop the Kibana server, edit users.json and set verified: false and the user should then be able to register the key again.
If anyone wants to submit a PR for this,

Add a file listener on user.json to reload it on change.
Create a utility script for clearing the verified flag on secrets.

This would make it possible to reset 2Fa codes without restarting the server.
BR // Robin


Trying to compile HelloWorld with Xcode 7 "ld: library not found for -lmmwormhole"

I am trying to compile the Hello World example like in the readme, and am getting this error.
Does anyone else have this problem?

Brian

ld: library not found for -lmmwormhole
clang: error: linker command failed with exit code 1 (use -v to see invocation)

** BUILD FAILED **

The following build commands failed:
    Ld build/emulator/HelloCordova\ WatchKit\ 1\ Extension.appex/HelloCordova\ WatchKit\ 1\ Extension normal i386
(1 failure)
Error code 65 for command: xcodebuild with args: -xcconfig,/Users/bp/myTest/applewatchtest/platforms/ios/cordova/build-debug.xcconfig,-project,HelloCordova.xcodeproj,ARCHS=i386,-target,HelloCordova,-configuration,Debug,-sdk,iphonesimulator,build,VALID_ARCHS=i386,CONFIGURATION_BUILD_DIR=/Users/bp/myTest/applewatchtest/platforms/ios/build/emulator,SHARED_PRECOMPS_DIR=/Users/bp/myTest/applewatchtest/platforms/ios/build/sharedpch
ERROR building one of the platforms: Error: /Users/bp/myTest/applewatchtest/platforms/ios/cordova/build: Command failed with exit code 2
You may not have the required environment or OS to build this project
Error: /Users/bp/myTest/applewatchtest/platforms/ios/cordova/build: Command failed with exit code 2
    at ChildProcess.whenDone (/usr/local/lib/node_modules/cordova/node_modules/cordova-lib/src/cordova/superspawn.js:139:23)
    at ChildProcess.emit (events.js:98:17)
    at maybeClose (child_process.js:756:16)
    at Process.ChildProcess._handle.onexit (child_process.js:823:5)

This must have been some problem related to a previous Xcode version (6.4) or a previous HelloWorld test. I just deleted and added the linked library in Xcode and it worked.

I have the same problem
ld: library not found for -lmmwormhole
Cleaning the whole project doesn't work.
What else can I try?

@sandman4sure can you perhaps send me your xcode project? It could be many things and I'll gladly take a look. (eddyverbruggen at gmail)

For others: the problem for @sandman4sure was solved by deselecting and selecting those targets on the right for the libmmwormhole.a file:

I have the same problem with older verison xcode(6.3) project.
I run code in xCode 8.0 and it's give me error like show in the following screen.

Any one help me to sort out?
Please reply ASAP.
Thanks in Advance.

This solved my problem.Please try this
http://stackoverflow.com/questions/31139534/pod-error-in-xcode-id-framework-not-found-pods


Add a unit test to check if fake stars have been planted in a grid

exists now in test_fakeplanter() function in test_diffimageml
(probably needs debugging)


Version 2.6 is not fully SPFx 1.12.1 compatible

Category

[ ] Enhancement
[ X] Bug
[ ] Question

Version
Please specify what version of the library you are using: [ 2.6.0 and 2.7.0 beta ]
Expected / Desired Behavior / Question
The following code should compile:
PropertyFieldListPicker('propertyName', {
    label: 'Picker Label',
    onPropertyChange: this.onPropertyPaneFieldChanged.bind(this),
    properties: this.properties,
    context: this.context,
}),

Observed Behavior
Unfortunately, it fails to compile, reporting the following error on the context: this.context, line:
Type 'WebPartContext' is not assignable to type 'IWebPartContext'.
  The types of 'manifest.componentType' are incompatible between these types.
    Type 'import("/path to project/node_modules/.pnpm/@microsoft+sp-module-interfaces@1.12.1/node_modules/@microsoft/sp-module-interfaces/dist/index-internal").ComponentType' is not assignable to type 'import("/path to project/node_modules/.pnpm/@microsoft+sp-module-interfaces@1.11.0/node_modules/@microsoft/sp-module-interfaces/dist/index-internal").ComponentType'.
      Type '"AdaptiveCardExtension"' is not assignable to type 'ComponentType'.ts(2322)
IPropertyFieldListPicker.d.ts(39, 5): The expected type comes from property 'context' which is declared here on type 'IPropertyFieldListPickerProps'

I'm not sure how the whole dependency mechanism works but there appears to still be a dependency on 1.11.0 in there and the 2.6 controls are still using the 1.11.0 version of IWebPartContext which is not compatible with the 1.12.1 version of WebPartContext.
The lock file shows the following dependencies for @pnp/spfx-property-controls:
<EMAIL_ADDRESS>    resolution: {integrity: sha512-s3mtN1jY0ZEgQIruH4EGb4FjqiHKMEGM84bCbcukpX8YuQ1b1VJFy6auXPb7qS2VclsTNEMq0PctRypkjlQOYw==}
    engines: {node: '>=0.10.0'}
    requiresBuild: true
    dependencies:
      '@microsoft/sp-core-library': 1.11.0
      '@microsoft/sp-lodash-subset': 1.11.0
      '@microsoft/sp-office-ui-fabric-core': 1.11.0
      '@microsoft/sp-webpart-base': 1.11.0_d8ecccf2889e06c2a80080b62409afec
      '@pnp/common': 1.3.11
      '@pnp/logging': 1.3.11
      '@pnp/odata': 1.3.11_0735193bd073e5cc36fcb4261de894d9
      '@pnp/sp': 1.3.11_97ef0e213a5999822e11d2e99b1ed457
      '@pnp/sp-clientsvc': 1.3.11_5ebb02c573206a4d27a8d882b140be71
      '@pnp/sp-taxonomy': 1.3.11_aeab9ef356b7306c5f0f03811326079a
      '@pnp/telemetry-js': 2.0.0
      '@uifabric/icons': 7.5.17_d8ecccf2889e06c2a80080b62409afec
      lodash.omit: 4.5.0
      markdown-to-jsx<EMAIL_ADDRESS>      office-ui-fabric-react: 6.214.0_d8ecccf2889e06c2a80080b62409afec
      react: 16.8.5
      react-ace: 5.8.0_react-dom<EMAIL_ADDRESS>      react-dom<EMAIL_ADDRESS>    transitivePeerDependencies:
      - '@types/react'
      - '@types/react-dom'
    dev: false

Steps to Reproduce
Option 1. Upgrade an existing project that uses PropertyFieldListPicker. Odds are that it already contains context: this.context
Option 2:

Build a new default 'HelloWorld' web part using the 1.12.1 yo generator.
Add spfx-property-controls

npm install @pnp/spfx-property-controls@latest

Add the following to the groupFields array in getPropertyPaneConfiguration in HelloWorldWebPart.ts:

PropertyFieldListPicker('toolboxItemsList', {
    label: 'Toolbox items list',
    onPropertyChange: this.onPropertyPaneFieldChanged.bind(this),
    properties: this.properties,
    context: this.context,
})

Add the import to HelloWorldWebPart.ts:

import { PropertyFieldListPicker } from '@pnp/spfx-property-controls/lib/PropertyFieldListPicker';

Compile.

Note: As a workaround, changing the line to context: this.context as any, keeps the compiler happy and appears to work well enough to let me get on with other things. I don't know enough about the inner workings of SPFx to trust it in production though.

Hi @IvanTheBearable, version 2.X is for SPFx 1.11.0. For SPFx 1.12.1 you should be using version 3.1.0 of the property controls.
Please try updating to 3.1.0 as that should resolve the issue

Hmm. 2.6 and 2.7 beta is all pnpm offered me. I will look into that. Thank you.

@IvanTheBearable you can see a list of all versions here: https://www.npmjs.com/package/@pnp/spfx-property-controls (click on the Versions tab).

Yes, I looked there. What appears to have happened is that I didn't look past the @latest and @next tags, which are 2.6 and 2.7 beta respectively. I didn't scroll down enough to see 3.1. :-)


feat: forward-port leanprover-community/mathlib#18446

<EMAIL_ADDRESS><EMAIL_ADDRESS>

leanprover-community/mathlib#18446

bors merge
(since @joneugster did all the work, this doesn't feel like reviewing my own PR)


Theme fails to apply to Discord

So I got wal-discord working perfectly on my laptop after I used the -t flag.

I replicated my process exactly on my desktop running an identical setup with i3, betterdiscord, and wal-discord, using the same wallpaper. Here's what the theme looks like on my desktop

is the discord version the same?

When I run discord -v on both devices, the first line is
Discord 0.0.10

So I think so? Both were downloaded today from the Arch repositories

I think Discord -v is kind of broken, it tends to do it's own updating thing that isn't that easy to check.
Do make sure you're actually running discord and not something like discord-canary.
the CSS on your desktop looks an awful lot like the unfixed css of last week.
could you make sure the repo is up to date and the master.scss file is properly linked and up to date?
Other than that I've ran into some CSS buggyness with betterdiscord, beautifuldiscord might be worth a shot if that doesn't help.

I have

Updated the wal-discord repository
Completely reinstalled Discord
Completely reinstalled Betterdiscord
Completely reinstalled betterdiscordctl
Removed and regenerated the wal_discord theme file.

I don't have too much knowledge of betterdiscord, besides the fact that the base betterdiscord fork is depreciated. Seems that at least for Arch, betterdiscordctl or betterdiscord-rauenzi from the AUR seem to be updated and running.
That said, I've done a fast check on betterdiscordctl and manually injected the style.css contents into the custom css location and it worked identically. I would recommend using beautiful discord for future troubleshooting as it omits factors (not necessarily incompatible with betterdiscord either and is very lightweight.)
The command you want to get beautifuldiscord to work and make sure wal-discord refreshes would be wal-discord; beautifuldiscord --css ~/.cache/wal-discord/style.css.
my comments on software I'm not familiar with aside;
Could you do a manual check on the following two files files located at ~/.config/wal-discord/master.scss and ~/.dache/wal-discord/style.css to see if they are identical across both machines? Them being different in structure would mean there is a problem with the file generation and them being identical would indicate the problem is instead in applying the theme.
I personally suspect it's a configuration error somewhere, either with betterdiscord or somewhere with the file linking/handling, because the screenshot is almost identical to the old css we had, before #11 was fixed. Aka somewhere the css isn't going where it needs to.

I don't have too much knowledge of betterdiscord, besides the fact that the base betterdiscord fork is depreciated. Seems that at least for Arch, betterdiscordctl or betterdiscord-rauenzi from the AUR seem to be updated and running.

I should have specified, this is the fork I'm running. I will edit momentarily and attach diffs

Seems that the master file is not updated properly, meaning that the theme that generates is still based off of the old broken code.
Could you pease try the following?
cd to your git repo of wal-discord,
remove the master.scss ln by executing the following command rm ~/.config/wal-discord/master.scss
double check the repo is up to date through git pull (should go off without a hitch and prompt it is already up to date.)
then recreate the file link by executing ln -s [git repo location of wal-discord]/config/master.scss] ~/.config/wal-discord/master.scss.

That did it!
It looks like beautifuldiscord auto injected the CSS when I created the new symlink.
Thanks for the help!


Question about optimal mask ratio

Hi, Thank you for your awesome work. I am trying to reproduce the results of your Hyper-parameter Study experiment, but when I changed the mask ratio, I got different results from the paper on all three datasets.
In order to reproduce the problem, I clone STEP locally, use the dataset you provided, and then I only change the mask ratio to 0.25 and GPU num to 4 and then re-train the TSFormer and STEP models. Here are the results.
Result for PEMS04 dataset,

"2023-04-06 11:44:21,101 - easytorch-training - INFO - Epoch 89 / 100
2023-04-06 11:48:05,343 - easytorch-training - INFO - Result : [train_time: 224.24 (s), lr: 6.25e-05, train_MAE: 17.7495, train_RMSE: 28.6461, train_MAPE: 0.1334]
2023-04-06 11:48:05,345 - easytorch-training - INFO - Start validation.
2023-04-06 11:50:55,722 - easytorch-training - INFO - Result : [val_time: 170.38 (s), val_MAE: 18.1383, val_RMSE: 28.1314, val_MAPE: 0.1222]
2023-04-06 11:50:57,130 - easytorch-training - INFO - Checkpoint checkpoints/STEP_100/e87a2127b73d6ba8cda30085f7beb2b3/STEP_best_val_MAE.pt saved
2023-04-06 11:53:47,204 - easytorch-training - INFO - Evaluate best model on test data for horizon 1, Test MAE: 16.3986, Test RMSE: 26.5760, Test MAPE: 0.1097
2023-04-06 11:53:47,209 - easytorch-training - INFO - Evaluate best model on test data for horizon 2, Test MAE: 16.8978, Test RMSE: 27.5110, Test MAPE: 0.1138
2023-04-06 11:53:47,213 - easytorch-training - INFO - Evaluate best model on test data for horizon 3, Test MAE: 17.3182, Test RMSE: 28.1838, Test MAPE: 0.1168
2023-04-06 11:53:47,216 - easytorch-training - INFO - Evaluate best model on test data for horizon 4, Test MAE: 17.6034, Test RMSE: 28.6846, Test MAPE: 0.1193
2023-04-06 11:53:47,219 - easytorch-training - INFO - Evaluate best model on test data for horizon 5, Test MAE: 17.8579, Test RMSE: 29.0966, Test MAPE: 0.1208
2023-04-06 11:53:47,222 - easytorch-training - INFO - Evaluate best model on test data for horizon 6, Test MAE: 18.0855, Test RMSE: 29.4533, Test MAPE: 0.1219
2023-04-06 11:53:47,226 - easytorch-training - INFO - Evaluate best model on test data for horizon 7, Test MAE: 18.2933, Test RMSE: 29.7824, Test MAPE: 0.1234
2023-04-06 11:53:47,229 - easytorch-training - INFO - Evaluate best model on test data for horizon 8, Test MAE: 18.4903, Test RMSE: 30.0777, Test MAPE: 0.1249
2023-04-06 11:53:47,232 - easytorch-training - INFO - Evaluate best model on test data for horizon 9, Test MAE: 18.6646, Test RMSE: 30.3532, Test MAPE: 0.1263
2023-04-06 11:53:47,235 - easytorch-training - INFO - Evaluate best model on test data for horizon 10, Test MAE: 18.8327, Test RMSE: 30.6055, Test MAPE: 0.1280
2023-04-06 11:53:47,238 - easytorch-training - INFO - Evaluate best model on test data for horizon 11, Test MAE: 19.0170, Test RMSE: 30.8598, Test MAPE: 0.1294
2023-04-06 11:53:47,241 - easytorch-training - INFO - Evaluate best model on test data for horizon 12, Test MAE: 19.2633, Test RMSE: 31.1607, Test MAPE: 0.1311
2023-04-06 11:53:47,286 - easytorch-training - INFO - Result : [test_time: 170.16 (s), test_MAE: 18.0602, test_RMSE: 29.3930, test_MAPE: 0.1221]"

Result for METR-LA dataset,

2023-04-10 06:42:39,345 - easytorch-training - INFO - Epoch 96 / 100
2023-04-10 06:45:14,351 - easytorch-training - INFO - Result : [train_time: 155.01 (s), lr: 1.56e-04, train_MAE: 2.7075, train_RMSE: 5.3461, train_MAPE: 0.0707]
2023-04-10 06:45:14,354 - easytorch-training - INFO - Start validation.
2023-04-10 06:45:56,978 - easytorch-training - INFO - Result : [val_time: 42.62 (s), val_MAE: 2.6742, val_RMSE: 5.1144, val_MAPE: 0.0727]
2023-04-10 06:45:59,152 - easytorch-training - INFO - Checkpoint checkpoints/STEP_100/aa28a6aab40136a6af5885691c378f94/STEP_best_val_MAE.pt saved
2023-04-10 06:47:22,991 - easytorch-training - INFO - Evaluate best model on test data for horizon 1, Test MAE: 2.1564, Test RMSE: 3.7474, Test MAPE: 0.0513
2023-04-10 06:47:22,994 - easytorch-training - INFO - Evaluate best model on test data for horizon 2, Test MAE: 2.4244, Test RMSE: 4.4858, Test MAPE: 0.0598
2023-04-10 06:47:22,998 - easytorch-training - INFO - Evaluate best model on test data for horizon 3, Test MAE: 2.6010, Test RMSE: 4.9821, Test MAPE: 0.0661
2023-04-10 06:47:23,002 - easytorch-training - INFO - Evaluate best model on test data for horizon 4, Test MAE: 2.7384, Test RMSE: 5.3681, Test MAPE: 0.0713
2023-04-10 06:47:23,005 - easytorch-training - INFO - Evaluate best model on test data for horizon 5, Test MAE: 2.8518, Test RMSE: 5.6969, Test MAPE: 0.0758
2023-04-10 06:47:23,009 - easytorch-training - INFO - Evaluate best model on test data for horizon 6, Test MAE: 2.9472, Test RMSE: 5.9612, Test MAPE: 0.0793
2023-04-10 06:47:23,012 - easytorch-training - INFO - Evaluate best model on test data for horizon 7, Test MAE: 3.0293, Test RMSE: 6.1882, Test MAPE: 0.0824
2023-04-10 06:47:23,015 - easytorch-training - INFO - Evaluate best model on test data for horizon 8, Test MAE: 3.1039, Test RMSE: 6.3804, Test MAPE: 0.0852
2023-04-10 06:47:23,019 - easytorch-training - INFO - Evaluate best model on test data for horizon 9, Test MAE: 3.1690, Test RMSE: 6.5411, Test MAPE: 0.0877
2023-04-10 06:47:23,023 - easytorch-training - INFO - Evaluate best model on test data for horizon 10, Test MAE: 3.2300, Test RMSE: 6.6843, Test MAPE: 0.0900
2023-04-10 06:47:23,026 - easytorch-training - INFO - Evaluate best model on test data for horizon 11, Test MAE: 3.2900, Test RMSE: 6.8177, Test MAPE: 0.0923
2023-04-10 06:47:23,030 - easytorch-training - INFO - Evaluate best model on test data for horizon 12, Test MAE: 3.3564, Test RMSE: 6.9536, Test MAPE: 0.0946
2023-04-10 06:47:23,075 - easytorch-training - INFO - Result : [test_time: 83.92 (s), test_MAE: 2.9081, test_RMSE: 5.8956, test_MAPE: 0.0780]

Result for PEMS-BAY dataset,

2023-04-12 21:09:24,701 - easytorch-training - INFO - Epoch 99 / 100
2023-04-12 21:17:14,073 - easytorch-training - INFO - Result : [train_time: 469.37 (s), lr: 3.13e-05, train_MAE: 1.4102, train_RMSE: 3.1304, train_MAPE: 0.0307]
2023-04-12 21:17:14,076 - easytorch-training - INFO - Start validation.
2023-04-12 21:19:04,273 - easytorch-training - INFO - Result : [val_time: 110.20 (s), val_MAE: 1.4673, val_RMSE: 3.0659, val_MAPE: 0.0333]
2023-04-12 21:19:07,612 - easytorch-training - INFO - Checkpoint checkpoints/STEP_100/88e31eeaa70eda996a9b04849238f61f/STEP_best_val_MAE.pt saved
2023-04-12 21:22:46,004 - easytorch-training - INFO - Evaluate best model on test data for horizon 1, Test MAE: 0.8249, Test RMSE: 1.5080, Test MAPE: 0.0159
2023-04-12 21:22:46,013 - easytorch-training - INFO - Evaluate best model on test data for horizon 2, Test MAE: 1.0714, Test RMSE: 2.1557, Test MAPE: 0.0215
2023-04-12 21:22:46,023 - easytorch-training - INFO - Evaluate best model on test data for horizon 3, Test MAE: 1.2304, Test RMSE: 2.6389, Test MAPE: 0.0256
2023-04-12 21:22:46,031 - easytorch-training - INFO - Evaluate best model on test data for horizon 4, Test MAE: 1.3444, Test RMSE: 2.9996, Test MAPE: 0.0288
2023-04-12 21:22:46,038 - easytorch-training - INFO - Evaluate best model on test data for horizon 5, Test MAE: 1.4280, Test RMSE: 3.2660, Test MAPE: 0.0313
2023-04-12 21:22:46,046 - easytorch-training - INFO - Evaluate best model on test data for horizon 6, Test MAE: 1.4926, Test RMSE: 3.4677, Test MAPE: 0.0333
2023-04-12 21:22:46,054 - easytorch-training - INFO - Evaluate best model on test data for horizon 7, Test MAE: 1.5432, Test RMSE: 3.6218, Test MAPE: 0.0349
2023-04-12 21:22:46,062 - easytorch-training - INFO - Evaluate best model on test data for horizon 8, Test MAE: 1.5850, Test RMSE: 3.7426, Test MAPE: 0.0363
2023-04-12 21:22:46,070 - easytorch-training - INFO - Evaluate best model on test data for horizon 9, Test MAE: 1.6201, Test RMSE: 3.8362, Test MAPE: 0.0374
2023-04-12 21:22:46,079 - easytorch-training - INFO - Evaluate best model on test data for horizon 10, Test MAE: 1.6513, Test RMSE: 3.9144, Test MAPE: 0.0385
2023-04-12 21:22:46,088 - easytorch-training - INFO - Evaluate best model on test data for horizon 11, Test MAE: 1.6804, Test RMSE: 3.9816, Test MAPE: 0.0393
2023-04-12 21:22:46,096 - easytorch-training - INFO - Evaluate best model on test data for horizon 12, Test MAE: 1.7121, Test RMSE: 4.0462, Test MAPE: 0.0402
2023-04-12 21:22:46,249 - easytorch-training - INFO - Result : [test_time: 218.64 (s), test_MAE: 1.4320, test_RMSE: 3.3536, test_MAPE: 0.0319]
2023-04-12 21:22:47,739 - easytorch-training - INFO - Checkpoint checkpoints/STEP_100/88e31eeaa70eda996a9b04849238f61f/STEP_099.pt saved

Here is a comparison of the two results, STEP's results are from https://arxiv.org/pdf/2206.09113.pdf, and https://github.com/zezhishao/BasicTS.

I would like to ask you to help me figure it out.
Looking forward to your reply.
Best regards

That's strange, have you tested other masking ratios? E.g., the ratios in the paper.
Since the code has be significantly refactored, I now need to redo these experiments, which may take some time.

@zezhishao Have you tested this problem yet? Looking forward to your reply.

Hello, I am very sorry for the late reply. I have been very busy looking for a job recently.
At present, I haven't finished the test and come to an insightful conclusion.
I tested a few masking ratios, and the results under different masking ratios seem to have no specific rules.
In addition, I have not tested the masking ratios in the paper ,and STEP has been refactored, so I'm not sure if something went wrong.

I tested a few more masking ratios again.
From preliminary tests, masking ratio seems to only affect efficiency, and the impact on performance is not significant.
This is not consistent with the results of the ablation study in the paper. I will continue to test the previous version of STEP to see if I can reproduce the results at that time. If it is not consistent, I will immediately revise the results of the paper.
In addition, if you have any further findings or insights, please let me know. Maybe we can figure out why and write a paper together.


--as-dockerfile doesn't read builder image labels labels

It seems that s2i build --as-dockerfile doesn't read the builder image labels when generating the Dockerfile, especially the io.openshift.s2i.* ones.
As an example, see this gist. The image use in there registry.access.redhat.com/redhat-openjdk-18/openjdk18-openshift.
skopeo inspect docker://registry.access.redhat.com/redhat-openjdk-18/openjdk18-openshift | grep io.openshift.s2i
        "io.openshift.s2i.destination": "/tmp",
        "io.openshift.s2i.scripts-url": "image:///usr/local/s2i",

When trying to build the generated Dockerfile from this builder, it fails as it is looking at it tries to execute a RUN on /usr/libexec/s2i/assemble, which doesn't exists in that image.
STEP 6: USER 1001
--> 496bfb3d9130701e154304c2b444788fc6110780b26adc71620315b3d440a8b2
STEP 7: RUN /usr/libexec/s2i/assemble
/bin/sh: /usr/libexec/s2i/assemble: No such file or directory
subprocess exited with status 127
subprocess exited with status 127
error building at STEP "RUN /usr/libexec/s2i/assemble": exit status 127

Related to https://github.com/openshift/source-to-image/issues/966#issuecomment-495169765.
cc @siamaksade @rhuss

Looking into the source at https://github.com/openshift/source-to-image/blob/3bdb78d004cc1f012b0eb4cb8aca41273bb6e6cf/pkg/build/strategies/dockerfile/dockerfile.go#L415-L423
it's really only about the options --scripts-url and --image-scripts-url (with a fallback to /usr/libexec/s2i/)
In fact, it would be super awesome if this detection could be done automatically as all information is already there. No need to bug the user to know where within the builder image the s2i directory is located.

The challenge is how to discover the information.  The intent of the --as-dockerfile invocation is that we have no reliance on any specific tool/library that would be used to inspect the image in question, thus we can't look at the labels to determine this information.  (If we assume the presence of a docker daemon and use that to inspect the image, we might as well just run s2i in the traditional mode where it builds the whole image for you).

The intent of the --as-dockerfile invocation is that we have no reliance on any specific tool/library that would be used to inspect the image in question, thus we can't look at the labels to determine this information.

I do get the "no reliance on any specific tool" but not on the library part. We could easily re-use containers/image as a library (same as skopeo does I think), to query the image registry for the image labels. I don't think a dependency to containers/image would be that bad — this would allow s2i to do more image introspection without depending on the presence of any docker daemon.

If we assume the presence of a docker daemon and use that to inspect the image, we might as well just run s2i in the traditional mode where it builds the whole image for you.

We definitely can't (or do not want) to assume the presence of a docker daemon, especially on OpenShift 4.x — but it's also true for some GKE cluster version where docker is not even there anymore (using cri-containerd instead).
@bparees related to https://github.com/openshift/source-to-image/issues/966 (especially the latest comments), I am guessing OpenShift 4 is either affected by that issue or (most likely) does the remote inspect on its own, right ? If it's true, I feel it would be beneficial to have this part in the repository so s2i build --as-dockerfile would act and work more closely to what OpenShift 4.x source to image strategy does.

I am guessing OpenShift 4 is either affected by that issue or (most likely) does the remote inspect on its own, right

openshift4 does its own image inspect prior to invoking the s2i bits.

If it's true, I feel it would be beneficial to have this part in the repository so s2i build --as-dockerfile would act and work more closely to what OpenShift 4.x source to image strategy does.

it could be done, yes.

/lifecycle frozen

May I point out that all S2I related ClusterTasks that come with OpenShift Pipelines use s2i build ... --as-dockerfile and thus are affected by this bug. I.e. silently all these ClusterTasks are dependent on the S2I machinery being located below /usr/libexec/s2i (with the exeption of s2i-java that expects the S2I machinery below /usr/local/s2i). I was always wondering why there doesn't exist a generic S2I ClusterTask and tried to implement one myself. I got pretty far until I had to deal with the Java base images.
As long as this bug persists you (I mean the Red Hat engineers) will not be able to change the location of the S2I machinery within any S2I base image (as has been done with the Java S2I base image some time in the past).

We've hit this (again) in three customer cases over the last couple of weeks; another relevant label this time is io.openshift.s2i.assemble-user, ,we've had subtle behavioural differences because ignoring that label and using 1001 partly works for our images.
For io.openshift.s2i.scripts-url we can mitigate this in the Java images by moving the scripts to align with s2i's default (https://issues.redhat.com/browse/OPENJDK-2805). But I don't think we can change our default UID without risking disruption elsewhere.
Asides from fixing this in s2i at a code level (appreciate that this is not straightforward), it would be a good idea to note that the labels don't do anything in --as-dockerfile mode in the docs e.g. in https://github.com/openshift/source-to-image/blob/master/docs/builder_image.md


refactor: remove usages of deprecated rxjs apis

Removes the following APIs that are deprecated as of RxJS 6.0:

Replaces usages of empty() with EMPTY.
Replaces uses of the resultSelector parameter of combineLatest with calls to map.

@crisbeto needs rebase


Add support for multiple designated types for an operator declaration.

Add parsing, type checking, serialization, and deserialization support
for specifying multiple types as "designated" for operator lookup for
a given operator declaration.
The constraint solver still considers only the first type when
deciding the order to attempt the elements of a disjunction, so this
doesn't really change behavior yet.

@swift-ci Please smoke test

It looks like I missed a few printing changes so I'll finish those up and push another commit tomorrow.

@swift-ci Please smoke test

@swift-ci Please smoke test Linux platform

@swift-ci Please smoke test Linux platform

@swift-ci Please smoke test

@dmbryson Is this issue that popped up in my linux build one you're already aware of?
10:39:49 Failing Tests (1):
10:39:49     llbuild :: BuildSystem/Build/lane-release.llbuild

Will retry in case this is a non-deterministic failure.

@swift-ci Please smoke test Linux platform

:/ Not sure what happened there.  There should have been more detailed log messages for any of the failure conditions.

Hmm, failed again. Very strange.

Looking into it: rdar://problem/45196629 lane-release.llbuild test is failing in some Swift-CI linux runs

@swift-ci Please smoke test

@rintaro @harlanhaskins It's not clear to me if there is a better way to deal with the libSyntax update here. This captures the syntax, but nothing about the semantic meaning of the identifiers in the list after the colon.

Latest error:
/home/buildnode/jenkins/workspace/swift-PR-Linux-smoke-test/branch-master/swift-corelibs-libdispatch/src/swift/Block.swift:43:73: error: cannot convert value of type 'UInt32' to expected argument type 'UInt'
16:15:46                 _block =  dispatch_block_create_with_qos_class(dispatch_block_flags_t(UInt32(flags.rawValue)),

@swift-ci Please smoke test Linux platform

I'll merge the other Swift syntax fixes in a separate PR.


sift --edge-thresh 10 Error: unknown flag `edge-thresh'

Hello,
I downloaded shift and while executing (this is in reference  to book "programming computer Vision with python" by author Jan Erik Solem)
what I need to do to resolve this...?
-Thanks
-Alok
python examples/ch3_panorama.py
Error: unknown flag `edge-thresh'
processed tmp.pgm to ../data/Univ1.sift
Traceback (most recent call last):
File "examples/ch3_panorama.py", line 24, in
l[i],d[i] = sift.read_features_from_file(featname[i])
File "/Users/akmishra/Development/python2.7/lib/python2.7/site-packages/PCV/localdescriptors/sift.py", line 25, in read_features_from_file
f = loadtxt(filename)
File "/Users/akmishra/Development/python2.7/lib/python2.7/site-packages/numpy/lib/npyio.py", line 962, in loadtxt
fh = np.lib._datasource.open(fname, 'rt', encoding=encoding)
File "/Users/akmishra/Development/python2.7/lib/python2.7/site-packages/numpy/lib/_datasource.py", line 266, in open
return ds.open(path, mode, encoding=encoding, newline=newline)
File "/Users/akmishra/Development/python2.7/lib/python2.7/site-packages/numpy/lib/_datasource.py", line 624, in open
raise IOError("%s not found." % path)
IOError: ../data/Univ1.sift not found.

I mean sift instead of shift


Error when fetching balance with Enjin Relay Chain

Fix error when fetching balance with Enjin Relay Chain

Version test: http://<IP_ADDRESS>:8900/s/sMYgKkfo5Dr9pwL
Validation passed.


[Feature Request]: Align parameter files naming and scenarios

Description
Align on the different use cases we want to cover in our module tests and reflect that in the parameter naming convention. For instance:

modules covering multiple services should cover all test scenarios

e.g. cognitive services cover both speech and face services. parameter files should cover both use cases, hence include speech.parameters.json and face.parameters.json

always include a min.parameters.json to cover only required parameters. For modules covering multiple services this could be duplicated if different services lead to different implementations.

e.g. cognitive services cover both speech and face services. parameter files should cover both use cases, hence include speech.min.parameters.json and face.min.parameters.json

all modules providing cmk functionality should include a encr.parameters.json (or cmk.parameters.json). For modules covering multiple services this could be duplicated if different services lead to different implementations.

Discussion needed: we could go for either a "always use encr.parameters.json" for consistency and to clearly show shorter specific examples in the readme or "use it only if required due to incompatibility with other settings" to instead try to include all possible features in the main parameters.json. The latter approach would probably be preferable considering the new dependencies approach. In either case update the Wiki as needed.

all modules providing networking functionalities ahould include a net.parameters.json (or similar). For modules covering multiple services this could be duplicated if different services lead to different implementations.

Discussion needed: same as above.

Update: this is now related to main.test.bicep wrapper modules

Related to #401 which would be the implementation out of this discussion. I'd also propose to rename current max.parameters.json (analysys services and API management) to parameters.json to have consistency throughout the repo for the main test file. This main test file is a good candidate to be used for the public Bicep registry contribution, so it makes sense to have a consistent naming for that one.

Wiki also needs to be updated

I wonder if this is still relevant given the AVM specs. Thoughts @eriqua?

@AlexanderSehr I think this is more related to the implementation than it is on the specs definition. I wish that was already the case in AVM. Starting from "the defaults test should only include required parametes" 😄
We're still not covering the above, but specs are covering almost all already. However the gap is more on making sure that related AVM specs are fullfilled than about improving the specs coverage.


Any recommendations for libraries similar to react-ts-form?

Hi,
I've been exploring form libraries and found react-ts-form, which I find very useful for type-safe and declarative form handling. However, it seems like the library is no longer being actively maintained.
I’m looking for other libraries with similar features or functionality that are actively supported. If you have any recommendations or experiences with such libraries, I’d greatly appreciate your input.
Thank you!

Which did you find and evaluate @kanapan?


Would it be possible to add a screenshot-example to the main README here?

Would it be possible to add a single screenshot to the main readme, as a link?
Reason I ask is primarily that I want to compare it to the default jruby-swing
style that I am using (and I actually use ruby-gtk most of the time). So I am
curious how jrubyfx would look differently, if it does look differently at all.
Feel free to close this issue here at any moment in time though.

Well, it's not a swing style, it is its own toolkit. It looks like any old JavaFX app, and most certainly doesn't look native on any platform because of that. While it would be trivial to link to one of these images over on http://fxexperience.com/2013/03/modena-theme-update/ I'm not sure if that is useful.


e2e, pkg/expect: distinguish between Stop and Close

Fixes #4928

lgtm.

fixed merge conflict, merging on greenlight


Fixes #44 : Update CodeEditor to display the complete content

The code at the bottom of the CodeEditor in the examples was hidden, due to overflow : 'hidden' to the parent element. Made changes to show complete code. Also, hid the scroll-bar for better UI.

@bvaughn @gaearon Please review :)

@bvaughn Made the requested changes :)

@bvaughn Thanks for merging :) This was my first PR to the org :smile: Many more to come! :fireworks:

We're excited to hear that!


Removing the subdir and tag options with git/hg command

A while ago I noticed that the subdir and tag/revision features weren't documented so I created a PR to do that #531. I didn't notice however that the reason for this was because some years ago they were intended to be removed:

8ee54470ba5544f5f263f03aece7cd7a918868e9
https://github.com/HaxeFoundation/haxelib/tree/vcs_version_remove

The reason behind removing subdir is explained in this issue: #238 (starting at https://github.com/HaxeFoundation/haxelib/issues/238#issuecomment-193492391)
I also found this to be somewhat relevant: #263. The feature is a bit of a relic.
The only time I have ever used this feature is for installing the hashlink haxelib, which tends to be out of date. However, there are other solutions to that problem, such as separating it into a separate repository.
Is it ok to continue with their deprecation and removal? Having to accommodate for these features has always been a bit of an inconvenience, and they are not even supported in haxelib.json dependencies so removing them shouldn't break too much. The only potential hurdle is that both of them are positional, which could be an issue if either should be kept. However, I would argue that if that were the case they should be replaced with command specific option flags: #319.
If it is ok to remove it then I'm happy to take it on myself after #510.

The subdir option is useful for a lot of hashlink libraries (hlsdl, hlopenal, hldx, hashlink) and it's been around for a long time so I think it would be better not to remove it.

https://github.com/HaxeFoundation/haxelib/issues/263#issuecomment-1256955617
However, I still think it would be good to stop using positional arguments and instead use --subdir etc. for these options.

Closing in favour of #319


[Feature request] Add possibility to export/import settings

There are settings in AppData but not if building chatterino via Qt, would like to transfer them to installer chatterino

Closing in favour of #1989


Dev-tools tests cannot be started parallel in two PRs same time

https://jenkins.nordix.org/job/metal3_dev_tools_integration_test_centos/285/console
+ openstack keypair create -f json --public-key /data/ci/images/../scripts/openstack/id_ed25519_****.pub ****-key-centos
ConflictException: 409: Client Error for url: https://kna1.citycloud.com:8774/v2.1/os-keypairs, Key pair '****-key-centos' already exists.

Openstack integration conflicts between two PRs.

/cc @lentzi90 @Rozzii

I suspect a race condition where both jobs try to first delete and then create the keypair. Maybe we could randomize the keypair name (especially if it is any way re-created every time) and delete it when finished.

Ref: https://github.com/Nordix/metal3-dev-tools/blob/87600f79fd94f5e96f239d5ba68ae5b67ae32a13/ci/images/gen_metal3_ubuntu_image.sh#L65-L68
(same for all other images)


[SMALLFIX-DOC-INSTALLJAVA]Add a period between 'file' and 'Double' in Java-Setup.md

"A Finder window appears containing an icon of an open box and the name of the .pkg file Double click the package icon to launch the Install app." in Java-Setup.md lose a period between "file" and "Double".

Can one of the admins verify this patch?

Jenkins, ok to test

Thanks for the docfix @summerDG! LGTM

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/8368/
Test PASSed.

LGTM


Stick The Sticker Game

PR Description 📜
In this game there are several stickers given in various pieces. The pieces can be shuffled to form a meaningful sticker.
Fixes # <your_issue_number>
#2119

Mark the task you have completed ✅

[x] I follow [CONTRIBUTING GUIDELINE]
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for website preview in assets/images
[x] I have added entries for my game in main README.md
[x] I have added README.md in my folder
[] I have added working video of the game in README.md (optional)
[x] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

@kunjgit I have made the changes you asked-


any way to restrict draggable element inside the slides?

What I mean is to make possible that only a child element inside the slide can make the slide drag. Thanks.

Please read the contribution guidelines :)

Not possible with current API, and probably never.
Slick is a carousel, not an abstract UI widget :) -- feel free to try and hack it to your whim, but we don't support that. Try Stackoverflow.
Best, Si.

All right, ty  :)


⚠ Bofrost.be has degraded performance

In 8190635, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 908 ms

Resolved: Bofrost.be performance has improved in 8c59b11 after 11 minutes.


GitHub Apps but for tools

Describe the solution you'd like
GitHub Apps should be expanded to tools, using a .dockstore.yml to register remotely multiple tools in the same repo.
See also https://github.com/dockstore/dockstore/issues/3475 for a good example that could take advantage of this
┆Issue is synchronized with this Jira Story
┆Issue Type: Story
┆Fix Versions: Dockstore 2.X
┆Sprint: Backlog
┆Issue Number: DOCK-1366

Do some research on how we currently add tools and the different modes we have.
Think through how expanding things to github apps would affect that. (Storytime)


Adds Lasso, Ridge and ElasticNet

closes #624

Codecov Report

Merging #625 (21027f6) into main (8df9db3) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #625   +/-   ##
=======================================
  Coverage   90.17%   90.18%
=======================================
  Files          78       78
  Lines        4549     4552    +3
  Branches      943      943
=======================================
+ Hits         4102     4105    +3
  Misses        252      252
  Partials      195      195

Flag
Coverage Δ

unittests
90.18% <100.00%> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...mmingbird/ml/operator_converters/sklearn/linear.py
100.00% <100.00%> (ø)

hummingbird/ml/supported.py
92.98% <100.00%> (ø)

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

Thanks so much for this contribution! Thanks for adding tests!
@interesaaat can take a look when he is back shortly :)

Can you please merge with master? I will merge afterwards (I would do it but I am currently OOF)


Changed PR to Pull  Request

Changed PR to Pull  Request in first sentence.

Please make sure to read the CONTRIBUTING document before opening the PR for relevant information on contributing to the documentation. Thanks!

Thanks for opening the PR, you have missed the commit prefix to signify the change-type for your PR. Please read https://github.com/balena-io/docs/blob/master/CONTRIBUTING.md#creating-commits-in-line-with-semantic-versioning

Hey @laurentava did you get a chance to look at this?

Hey @laurentava did you get a chance to look at this?

@vipulgupta2048 yes, I thought I fixed it. May need some tips on what to do to close out. Thanks!

Happy to help @laurentava when you create a commit from the GitHub UI or from the terminal, you would need to add a prefix to your commit to signify what the change is. You can refer to this document about the same https://github.com/balena-io/docs/blob/master/CONTRIBUTING.md#creating-commits-in-line-with-semantic-versioning and you actually did do it correctly in your first PR here https://github.com/balena-io/docs/pull/1866
Since, GitHub UI doesn't allow for editing the commits at this time. You can try again by opening a new pull request and make sure you add the commit prefix? It's all good.

I think there's a bit of confusion between "commit contents", and "commit comment"? And I'm not sure if the CONTRIBUTING.md makes that very clear either? I think for the automatic-versioning that Balena uses, the patch:  needs to be at the start of the commit comment? ("commit comment" might sometimes also be called "commit message")
"Commit contents" is the actual change, and "commit comment" is a description of the change.

 Whereas I think what you actually wanted was a commit content of "pull request (PR)" and a commit comment of "patch: Updated PR to pull request (PR)" ? :shrug:

I think there's a bit of confusion between "commit contents", and "commit comment"? And I'm not sure if the CONTRIBUTING.md makes that very clear either? I think for the automatic-versioning that Balena uses, the patch:  needs to be at the start of the commit comment? ("commit comment" might sometimes also be called "commit message")
"Commit contents" is the actual change, and "commit comment" is a description of the change.

 Whereas I think what you actually wanted was a commit content of "pull request (PR)" and a commit comment of "patch: Updated PR to pull request (PR)" ? 🤷

Can you remind me where I go to create a new edit and request? And to confirm I will make the edit just like this: pull request (PR) in the actual doc. And then where do I put patch: Updated PR to pull request (PR)?
Thanks for all your help!


Type Parameter Syntax is not analyzed properly

Type: Bug
Hi maintainers. I love vscode and vscode-python extension so much. Thank you for your dedicated efforts.
This issue is moved from https://github.com/microsoft/pylance-release/issues/4645 since it seems better to treat here.
Environment data

Language Server version: v2023.7.31
OS and version: Public python docker image python:3.12.0b4-bulluseye
Python version (& distribution if applicable, e.g. Anaconda): 3.12.0b4

Code Snippet

from dataclasses import dataclass
from typing import Self

@dataclass
class MyInt:
    value: int
    def __add__(self, other: Self) -> Self:
        return MyInt(self.value + other.value)

def add[T: MyInt](a: T, b: T) -> T:
    return a + b

if __name__ == "__main__":
    print(add(MyInt(value=3), MyInt(value=4)))

Repro Steps

Start the container pulled from the official python repository with the above mentioned tag.
Attach to it using vscode remote-development extension.
Install the python extension.
Paste the code above and let the pylance analyze it.

Expected behavior
I expected the color of the return arrow of add function to be white,
Actual behavior
it becomes red, which is very confusing.

By the way, when I stop using custom MyInt class and typehint without type parameter syntax, this behaviour goes away.

As there is a growing focus on type-safe Python, generic programming, and hence, this type parameter syntax feature is crucial for many users. I respectfully request prioritizing this issue.
Extension version: 2023.22.1
VS Code version: Code 1.85.0 (af28b32d7e553898b2a91af498b1fb666fdebe0c, 2023-12-06T22:27:05.695Z)
OS version: Linux x64 5.19.0-50-generic
Modes:
Remote OS version: Linux x64 5.19.0-50-generic

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 x 4599)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
1, 0, 0

Memory (System)
15.53GB (10.19GB free)

Process Argv
--unity-launch --crash-reporter-id 9322d294-702f-42bf-8bdc-0c1b2ccc7155

Screen Reader
no

VM
0%

DESKTOP_SESSION
ubuntu

XDG_CURRENT_DESKTOP
Unity

XDG_SESSION_DESKTOP
ubuntu

XDG_SESSION_TYPE
x11

Item
Value

Remote
コンテナー python:3.12 (py312)

OS
Linux x64 5.19.0-50-generic

CPUs
Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 x 4600)

Memory (System)
15.53GB (10.19GB free)

VM
0%

Duplicate of https://github.com/microsoft/pylance-release/issues/4645. This is a bug in TextMate grammar that VS Code uses for Python. We have a work item tracking the idea of us (Pylance or Python extension) shipping and maintaining a TextMate grammar ourselves, but no decision has been made there yet.
cc: @luabud


[ENG-330] [OATHPIT] Throw figshare into the Oath Pit

Ticket
https://openscience.atlassian.net/browse/ENG-330
Purpose
Enable and update the figshare provider for aiohttp3.
Changes

figshare directly calls aiohttp.request() with aiohttp-0.18 for some downloads, which no longer works with aiohttp-3.5. Instead, use the updated super().make_request(). However, this only partially fix the download issue.

To fully fix the issue, the figshare auth header must be dropped.

As for the figshare provider: When a file has been published, he figshare download request returns a redirection URL which downloads the file directly from its backend storage S3. The new request does not need any auth at all. More importantly, the default figshare auth header breaks the download since S3 API does not understand figshare API. Thus, the provider must use no_auth_header=True to inform super().make_request() to drop the header.
As for the core provider: Instead of modifying how headers are built with build_headers(), simply update make_request() to drop the Authorization header  built into the headers.

Side effects
No
QA Notes
TBD
Deployment Notes
No

Coverage increased (+6.8%) to 76.114% when pulling 7f8422d99881d202107025f405f52d6ed95568c6 on cslzchen:feature/oathpit-figshare into be3b81f989cdb44de0b213635bd9073351297cf5 on CenterForOpenScience:feature/oathpit.


Allow changes to the first created instance, or let us delete it if we have others set up.

Feature request
Allow changes to the first created instance, or let us completely delete it if we have others set up.
What problem does this feature solve?
I had to reinstall WLED on a blank D1 mini and point my first instance at that, then never turn that d1 on.
I wasn't happy with the led's behind my monitor, added better colour strips and more led's and the first instance kept re-initialising itself (while tied to the same IP of the new working instance). It wouldn't let me change the led's of the first instance which was all I really needed to do to accommodate the changes. I would have been fine either pointing it to an IP that it could never resolve or if I could remove the instance entirely, or if changes I made to disable the instance remained disabled between sessions.
Are you willing to work on this yourself?
Willing but entirely incapable with my current abilities.
If I just missed something and this was already possible I apologise, but I really did poke everywhere (in gui) I thought would be relevant and nothing stuck or helped.


RuntimeError: Sizes of tensors must match except in dimension 1. Expected size 1 but got size 0 for tensor number 2 in the list.

Hi. I am running the code with default setting and both no defense and robosac_mAP. However, I am getting the following error:
....
at epoch 49
/mnt/data/fare01/ROBOSAC/coperception/tools/det/robosac.py:168: RuntimeWarning: divide by zero encountered in log
N = np.ceil(np.log(1 - 0.99) / np.log(1 - np.power(1 - eta, num_consensus))).astype(int)
10%|████                                    | 800/8000 [01:36<12:41,  9.45it/s]
Scene 8, Frame 0:
10%|████                                    | 800/8000 [01:43<15:33,  7.71it/s]
Traceback (most recent call last):
File "/mnt/data/anaconda3/envs/amongus/lib/python3.7/site-packages/torch/nn/parallel/data_parallel.py", line 171, in forward
python-BaseException
outputs = self.parallel_apply(replicas, inputs, kwargs)
File "/mnt/data/anaconda3/envs/amongus/lib/python3.7/site-packages/torch/nn/parallel/data_parallel.py", line 181, in parallel_apply
return parallel_apply(replicas, inputs, kwargs, self.device_ids[:len(replicas)])
File "/mnt/data/anaconda3/envs/amongus/lib/python3.7/site-packages/torch/nn/parallel/parallel_apply.py", line 89, in parallel_apply
output.reraise()
File "/mnt/data/anaconda3/envs/amongus/lib/python3.7/site-packages/torch/_utils.py", line 543, in reraise
raise exception
RuntimeError: Caught RuntimeError in replica 0 on device 0.
Original Traceback (most recent call last):
File "/mnt/data/anaconda3/envs/amongus/lib/python3.7/site-packages/torch/nn/parallel/parallel_apply.py", line 64, in _worker
output = module(*input, **kwargs)
File "/mnt/data/anaconda3/envs/amongus/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1194, in _call_impl
return forward_call(*input, **kwargs)
File "/mnt/data/fare01/ROBOSAC/coperception/coperception/models/det/base/FusionBase.py", line 116, in forward
feat_list
File "/mnt/data/fare01/ROBOSAC/coperception/coperception/models/det/base/DetModelBase.py", line 127, in build_local_communication_matrix
return torch.cat(tuple(feature_list), 1)
RuntimeError: Sizes of tensors must match except in dimension 1. Expected size 1 but got size 0 for tensor number 2 in the list.
Could you please help me to figure out what is the problem?

@qifang-robotics @RoboticsYimingLi can you take a look at this? Thank you!

Hi Farzaneh,
From the error msg it seems that you may run the code with more than one GPU allocated. You can try running by specifying "CUDA_VISIBLE_DEVICES=0" at the beginning of your command.
If that fix still won't work, please put your complete command line to run the code here, so that we can debug on our end.

Sorry for the late response. I noticed that the dataset has 8000 samples, which should not be the case for the test set.
Could you please double-check if the downloaded dataset (https://drive.google.com/drive/folders/1zFK9VWvXvYUHatKod5PTl8kZxSFskGGE, V2X-Sim-det.zip) were correct, and ensure specifying the test set in --data argument of robosac.py (should be ".../V2X-Sim-det/test")?

Hi Farzaneh,
From the error msg it seems that you may run the code with more than one GPU allocated. You can try running by specifying "CUDA_VISIBLE_DEVICES=0" at the beginning of your command.
If that fix still won't work, please put your complete command line to run the code here, so that we can debug on our end.

Hi, Thank you for your answer, I set CUDA_VISIBLE_DEVICES=0. My command is: CUDA_VISIBLE_DEVICES=0 python robosac.py --log --robosac no_defense --adv_iter 15 --number_of_attackers 2 --ego_agent 1

NP. I did it. It works fine now. Thanks

Sorry for the late response. I noticed that the dataset has 8000 samples, which should not be the case for the test set.
Could you please double-check if the downloaded dataset (https://drive.google.com/drive/folders/1zFK9VWvXvYUHatKod5PTl8kZxSFskGGE, V2X-Sim-det.zip) were correct, and ensure specifying the test set in --data argument of robosac.py (should be ".../V2X-Sim-det/test")?

Hi Farzaneh,
From the error msg it seems that you may run the code with more than one GPU allocated. You can try running by specifying "CUDA_VISIBLE_DEVICES=0" at the beginning of your command.
If that fix still won't work, please put your complete command line to run the code here, so that we can debug on our end.

Hi, Thank you for your answer, I set CUDA_VISIBLE_DEVICES=0. My command is: CUDA_VISIBLE_DEVICES=0 python robosac.py --log --robosac no_defense --adv_iter 15 --number_of_attackers 2 --ego_agent 1


Image Coherency - Herpaderping

Enhancement Proposal
In response to research on process tampering (Hollowing, Doppelganing, Herpaderping). I would like to propose an enhancement to Process Hacker which inspects the coherency between an executing process and the image on disk.
For context on Herpaderping please see: https://jxy-s.github.io/herpaderping/
Summary
This enhancement would add a coherency API to phlib which will inspect the image on disk and the image mapped into the process. This calculation will represent the similarity between the image on disk and the mapped image. This would be displayed in the process tree by "noting" the process' which have "Low Image Coherency". In addition, this would enhance the process table with a column displaying the "Image Coherency".
Here is a screenshot from the changes on my local branch:

Value
This enhancement would display which processes have been tampered with using techniques associated with Hollowing, Doppelganing, and Herpaderping. This will assist in identifying exploited processes and troubleshooting issues with processes.
The API is also a valuable enhancement to the library as an example of coherency checks that may be used and improved upon for detections of this class of exploitation.
Scope
This enhancement is not meant to be a catch-all solution for this class of exploitation and should not aim to solve all edge cases. The coherency API does not aim to be complete as someone may work around or bypass the calculation. Rather, it aims to be simple enough to highlight the base of the exploitation techniques (which are already well documented). While still providing value to the Process Hacker users.
Additionally, the API should be performant and minimize time-complexity. This is achieved by simplifying the inspection, limiting the amount of data inspected, and conceding some edge cases.
The Process Hacker source has plenty of facility in place to achieve this. PhLoadMappedImageEx and PhLoadRemoteMappedImage are enough to satisfy requirements with one limitation. PhLoadRemoteMappedImage does not support remote mapping an ELF binary. While it is plausible to carry out this type of exploit in WSL removing ELF<->ELF coherency checks is reasonable. That said, using an ELF binary to obscure the image backing a process is still be supported (e.g. ELF<->non-ELF) by checking for the mismatch in the calls to PhLoadMappedImageEx and PhLoadRemoteMappedImage.
My implementation does this inspection in PhpProcessQueryStage2 after the PhIsExecutablePacked check. But, expertise/feedback from the maintainers is always welcome.
Risk
"Low Image Coherency" binaries that are inherently incoherent is a risk. This might include self extracting archives, packed, or "legitimate" polymorphic code. However, the number of these types of binaries should be declining as most of "legitimate" cases are used to minimize the size of downloaded binaries. While they still exist, modern computing and network bandwidth has minimized the necessary. Furthermore, some of the "legitimate" binary packers leave writable and executable sections in the PE file, which are ripe for exploitation. The users of process hacker would still benefit from highlighting these.
Mitigating Risk
The UI will give the option to disable highlighting for "Low Image Coherency" if the user wishes:

APIs and Structures
Single public API from phlib:
/**
* Inspects the process image coherency compared to the file on disk.
*
* \param[in] FileName Win32 path to the image file on disk.
* \param[in] ProcessId Process ID of the active process to compare to.
* \param[out] ImageCoherency Image coherency value between 0 and 1. This
* indicates how similar the image on-disk is compared to what is mapped into
* the process. A value of 1 means coherent while a value lower than 1
* indicates how incoherent the image is.
*
* \return Status indicating the coherency calculation, note errors may indicate
* partial success.
* STATUS_SUCCESS The coherency calculation was successful.
* STATUS_INVALID_IMAGE_HASH The coherency calculation was successful or
* partially successful and unusually incoherent.
* STATUS_INVALID_IMAGE_FORMAT The coherency calculation was successful or
* partially successful and unusually incoherent.
* STATUS_SUBSYSTEM_NOT_PRESENT The coherency calculation was successful or
* partially successful and unusually incoherent.
* All other errors are failures to calculate.
*/
NTSTATUS
PhGetProcessImageCoherency(
    _In_ PWSTR FileName,
    _In_ HANDLE ProcessId,
    _Out_ PFLOAT ImageCoherency
    );

This context is used only internally but expresses the amount of tracking necessary for the coherency calculation and the usage of existing facility in Process Hacker:
/**
* Process image coherency context, used during the calculation of the process
* image coherency.
*/
typedef struct _PH_PROCESS_IMAGE_COHERENCY_CONTEXT
{
    NTSTATUS MappedImageStatus;               /**< Status of initializing MappedImage */
    PH_MAPPED_IMAGE MappedImage;              /**< On-disk image mapping */

    NTSTATUS RemoteMappedImageStatus;         /**< Status of initializing RemoteMappedImage */
    PH_REMOTE_MAPPED_IMAGE RemoteMappedImage; /**< Process remote image mapping */

    PVOID RemoteImageBase;                    /**< Remote image base address */

} PH_PROCESS_IMAGE_COHERENCY_CONTEXT, *PPH_PROCESS_IMAGE_COHERENCY_CONTEXT;

The addition of two fields in PH_PROCESS_ITEM:
/*CUT*/
    NTSTATUS ImageCoherencyStatus;
    FLOAT ImageCoherency;
} PH_PROCESS_ITEM, *PPH_PROCESS_ITEM;

process tampering (Hollowing, Doppelganing, Herpaderping)

I hate how these issues haven't been fixed 🙁

PhLoadRemoteMappedImage does not support remote mapping an ELF binary.

The ELF parser is located in mapexlf.c here:
https://github.com/processhacker/processhacker/blob/master/phlib/mapexlf.c

PhGetProcessImageCoherency

You can email the function for me to check otherwise it was left out of the above issue 🤔

The ELF parser is located in mapexlf.c here:
I didn't find an equivalent remote mapper to PhLoadRemoteMappedImage for ELF, maybe there is one? But, PhLoadMappedImageEx will satisfy both by calling the appropriate initialization PhInitializeMappedImage or PhInitializeMappedWslImage.

You can email the function for me to check otherwise it was left out of the above issue 🤔
I wasn't sure if I should include the implementation here or put up a PR for it. The guidelines indicate I should open an issue first. Just trying to follow protocol 😄. I can email you the file.

I wasn't sure if I should include the implementation here or put up a PR for it.  The guidelines indicate I should open an issue first.

You can do or say whatever on these tickets. I don't enforce any policy unless it's for something malicious 🥰

I didn't find an equivalent remote mapper to PhLoadRemoteMappedImage for ELF

WSL processes include PPL protection so I'd have to write the remote mapping.

Thanks for the info, I emailed you imgcoherency.c. FWIW, I don't think there needs to be support for ELF<->ELF unless you think otherwise - certainly enchantable later. Since the facility exists already for mapping the file on disk as ELF, some checks may be done at least for non-subsystem processes. In the case where someone overwrites a PE with an ELF to obscure the process.

https://github.com/processhacker/processhacker/pull/751 Implements this functionality, closed issue.

I am a bit lost here.
A lot of apps are colored in purple and display no native icons in my process list.
Everything (by David Carpenter), Foobar2000 (by Peter Pawlowski), Keepass (by Dominik Reichl) to name a few.
Why is that?

Is Processor hacer running with administrative permission?

no native icons in my process list

This indicates something blocked file system access which shouldn't happen for applications in the \Program Files\ directory and likely why the entries are also purple.

A lot of “good” apps are colored in purple

If you add the "image coherency" column to the process list what is the result for those entries? For example:

Is ProcessHacker running with administrative permission?

I guess so as the administrative account is the only one out there.

If you add the "image coherency" column to the process list what is the result for those entries?

0%
I tried to reset Process Hacker 3 settings, then un-installed it completely and tried 2.39, nothing changed for the better.

I guess so as the administrative account is the only one out there.

Is Process Hacker running elevated? If you elevate (run as admin) Process Hacker, does the problem persist?
As @dmex mentioned, the observable behavior seems like something is preventing Process Hacker from accessing the file on disk. Thus, the coherency check is reporting 0% coherency as it can't run the coherency calculation to verify what is mapped matches what in on disk. Running as administrator may resolve this. Also, where are those files executing from?
There is an option to disable the scanning (or increase the level of the scanning).

ImageCoherencyScanLevel
PH_IMAGE_COHERENCY_SCAN_TYPE
Note

0
N/A
Disable image coherency scan completely

1
PhImageCoherencyQuick
Closes behavior to what was previously implemented

2
PhImageCoherencyNormal
More comprehensive scan within reasonable limits

3 or higher
PhImageCoherencyFull
Compete scan, may be slow in some situations

Is Process Hacker running elevated? If you elevate (run as admin) Process Hacker, does the problem continue?

Yes.
I added a column filename and it seems there is something wrong with reporting correct paths of 'purple' apps.
The displayed paths are old ones, which existed a while ago, before I moved the apps to another folder.

Windows 7

Can you run this command and paste the version here?
reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v BuildLabEx

$ reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v BuildLabEx
BuildLabEx    REG_SZ    7601.24565.amd64fre.win7sp1_ldr_escrow.210122-0047


Shape

Adjust receptacle shape, add center point formula

We should pause merging this until it can be associated with an issue during the next sprint.


Docs: Add Features docs section

Before you start...

[X] Have you refreshed the page? You might be using an old version of the website.
[X] Have you checked if someone already requested this feature? If they have, post a comment with your use case instead.

Description
Users can see easility what Files have and support and at the same time we can provide richer explanation when someone ask about a feature of Files app on Discord or somewhere else.
Alternative solutions
None I believe.
Relevant Assets
No response

I'd like to add if approved.

Can you give some examples on how you would reorganize the existing docs?


Feature: Add alert when server starts

Send an alert to Discord channel when the Minecraft server starts.

Done!

Done!


10 pkgbuild tests against public pub failing after r34853

I assume this is because you are preparing to ship a new version publicly?
I will suppress the errors in the status files

This issue has been moved to dart-lang/barback#44.


devc should pull latest version of the parent image

Currently dev mode runs docker build without the --pull option.  If the user runs dev mode on a fresh environment, Docker will get the latest version of the parent image specified in the Dockerfile, but only once.  Then on all subsequent runs, it would just continue using the same version of the parent image.  Even if Liberty releases a new version later on, the user would not get that latest version unless they run docker pull manually.
To resolve this, we should change dev mode to run docker build --pull so that Docker always attempts to pull a newer version of the image if one is available.  If a specific version of Liberty is desired, the user should specify that version of the image in their Dockerfile.

Note that if dev mode rebuilds the image while it is already running (e.g. to include certain changes into the image), the above proposal would also attempt to update Liberty (if there is a newer image) at that time too.  An alternative could be to just run docker pull on dev mode startup.

We will do the following:
docker build --pull on dev mode startup
docker build (no pull) if the image is being rebuilt during dev mode


integration no longer works with HA 2022.4.0

Version, from the manifest file says 0.2.2  I pulled the latest version from git, and the bug report says to check const.py for the version number, but all that this file contains is this :
"""Constants for the Govee LED strips integration."""

DOMAIN = "govee"

CONF_DISABLE_ATTRIBUTE_UPDATES = "disable_attribute_updates"
CONF_OFFLINE_IS_OFF = "offline_is_off"
CONF_USE_ASSUMED_STATE = "use_assumed_state"

COLOR_TEMP_KELVIN_MIN = 2000
COLOR_TEMP_KELVIN_MAX = 9000

Nothing in the logs
The integration says it failed to start, deleted it and tried to re-add which produced this error dialogue:

Same here

Same here as well

Mine is also not working after upgrade to latest version of HA

Same here ...

same here

Same here

The problem persists with the latest version on my installation

The problem persists with the latest version on my installation

Updated both and restarted HA? Did you try to remove Govee from custom_components?
For me it looked like a complete new installation starting with HACS even custom_components was still existing in my case.

I don't use HACS, it caused performance problems the last time I had it installed with constant updates and restarts. I only use three custom components which are trivial to update with a simple bash script. If you now have to install HACS to use the Govee integration, then that will be the end of the road for me.

Govee integration still listed in HA or not?
For me it hasn't been visible in HACS and HA. I totally added the integration again and created a new API key in the official app.
HACS shouldn't be the issue because any folders in custom_components should be loaded by HA.

as for me it did not work... the govee integration still shows that it is not configurable throught the ui

Just started working again for me after update to Home Assistant 2022.4.4

Updated to 2022.4.4 and still have the same issue...

It hasn't worked for me for maybe the last 6/7 HA updates.

upgrading to HA v2022.4.6 solved this issue for me

No, still does not work after the 2022.4.6 upgrade, same "This integration does not support configuration via the UI" error message when trying to add the integration.

Installation via HACS (begrudgingly) wortks OK, but don't see why this would be any different from installing directly from the repo...

I don't know that this should have been closed. My setup is already through HACS and it is still not working...

@IIAIronWolf No problem, hair to reopen, as with either be useful to get an explanation of the issue.

@IIAIronWolf No problem, hair to reopen, as with either be useful to get an explanation of the issue.

I agree. It hasn't been working through HACS for me, but deleting and re-adding seemed to fix it. I will update if it stops working again. Maybe a HA/HACS update broke it temporarily, and re-adding is the fix?

Unfortunately it seems to be back in 2022.4.7 🙈
Readding under integrations only doesn't solve it now.

Has anyone had any luck with HA 2022.5.0? I've installed HACS and downloaded the Govee repository, but the Govee integration doesn't appear when I search for it.

Has anyone had any luck with HA 2022.5.0? I've installed HACS and downloaded the Govee repository, but the Govee integration doesn't appear when I search for it.

Did you try clearing your browser cache and and then looking for it again.


having problem using $ docker-compose up -d mail

Hello, i am using Ubuntu 14.04 for setup mail server. i face this error pls help.
root@docker-4gb-nyc1-01:~/docker-mailserver# docker-compose up -d mail
Creating mail
ERROR: for mail  Cannot create container for service mail: Conflict. The name "/mail" is already in use by container c157858ebb8de31f85c97b69d6e26c4063ab51da57de144c6905a0747e016815. You have to remove (or rename) that container to be able to reuse that name.
ERROR: Encountered errors while bringing up the project.

Hi, you already have a container named mail. that's what is written :-)
Remove it (if possible) and restart. Otherwise change the name in your Dockerfile to something else than mail.

how can i test?
On 23 August 2016 at 03:34, Hamin Ishrak<EMAIL_ADDRESS>wrote:

On 23 August 2016 at 03:08, Thomas VIAL<EMAIL_ADDRESS>wrote:

Closed #275 https://github.com/tomav/docker-mailserver/issues/275.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tomav/docker-mailserver/issues/275#event-763637934,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATN8flxjA1gbJfe96QuTrSxlKmM86GgDks5qig_rgaJpZM4JqTT_
.

--
[image: --]
Fatin Ishrak
[image: https://]about.me/Ishrak
https://about.me/Ishrak?promo=email_sig&utm_source=email_sig&utm_medium=email_sig&utm_campaign=external_links

--
[image: --]
Fatin Ishrak
[image: https://]about.me/Ishrak
https://about.me/Ishrak?promo=email_sig&utm_source=email_sig&utm_medium=email_sig&utm_campaign=external_links


How to distinguish Robot variable and KSH Variable?

I tried to use Robot to do the following operation in KSH to remove the ".auto" postfix in a directory:
Write    for file in .auto; do mv $file ${file%.}; done
The ${file%.} is for KSH variable however Robot always considered it as Robot variable and gave the error message: "Resolving variable '${file%.}' failed: Variable '${file}' not found."
Is there any way to tell Robot that the ${file%.*} is not for a Robot variable?

Escape ${file%.} like \${file%.}.

Thanks for your info!


National VSK enhancement | DiSanc Survey

There is a request for a few urgent changes within the NCF program in National VSK. Attached are the CSV files with the data incorporated.
A Separate tab by the name DiSanc survey should be incorporated within the NCF program. Two charts showing the countrywide heat map and the bar chart should be shown side by side.
Country-wide heat map showing state-wise Disanc survey done
Bar chart showing language-wise survey done - This shows how many people have been surveyed in language

At present, the configurations are provided by the cQube team. Request the team to share the modified configurations at the earliest.
NCERT is using cQube Edu v1.5 (July, 2022) at the moment. The plan is to update the same with modified configuration.

New reports has added in the national curriculum framework

@devu1454 Please test this

These are the few issues in NCF - Disanc Survey
Issue 1 : All Languages in the y-axis are in BLOCK letters

Issue 2 :Values not separated by comma in tooltip

issue3: Download button is not present

@FaizanMohammed326 issue 1 not resolved

Completed and It is up


feat: Track UI event #8402

Signed-off-by: momom<EMAIL_ADDRESS>Fixes #8402
I've confirmed the logs  using this TrackEvent component, but as I wrote in the issue I'm not sure where to insert it and I've not implemented that part.

This looks great! Can I ask for some changes?
I think all API operation IDs must be REST conventional verb+noun So what is our verb+noun? I think it is Collect+Event. Can you change it to CollectEvent? That means the request payload should be CollectEventRequest rather than TrackUserInterfaceUsageRequest, and it should be POST rather than GET. The HTTP URL should match the payload type, so it can we make it /api/v1/tracking/event?
Regarding the Event, I think we should have type. Google Analytics allows up to 25 arbitrary parameters. I think GRPC can do this with a map<>. Could you change that?
I think this should also include a test in argo_server_test.go, just to make sure the endpoint returns 200 OK.
Finally, for the UI, we could track lots of different things, but lets not do that! Instead, how about embedding the tracker in each page in the left hand nagging, workflow list, workflow template list etc. The type could be openedWorkflowList etc.
We should test that it works correctly, sometimes React just renders everything at once, so would send tracking events all at once. You can see what happens in your Brower’s the Web Inspector Network view.
If you don’t know this already, you can start the UI by running make start UI=true.
I don’t think we need any feature flag to disable this. It is very low risk, and the data never leaves your company network.

Great stuff by the way!

Thank you for your kind instructions!
I'm still working on it, and I think it'll be done tomorrow.
By the way, while trying to run argo-workflows locally, I met the error same as this issue at this.
I bumped up goreman version and it seemed to be fixed.
If this situation seems to occur in someone's environment, I'd like to create its issue. What do you think? 🤔

Looks like we need a new version of goreman, do you want to update the Makefile?
https://github.com/argoproj/argo-workflows/blob/e368f504307ecbbfa2f228bccfab1f943efaca9d/Makefile#L465

Run yarn --cwd ui lint to fix UI problems. Run make pre-commit -B to fix codegen issues.

Looks good. You should revert the change to gh-pages file.
Can I check - when you run the UI, do the events get recorded, only when the page is displayed?

Can I check - when you run the UI, do the events get recorded, only when the page is displayed?

Yes it is in my local. I saw sometimes requests were sending 2 or 3 times per page, but they send it only when the page is displayed.

I think it is important we only send one request per page. I think the page is probably getting re-rendered due to a React key change. I'll investigate.

I think it is important we only send one request per page. I think the page is probably getting re-rendered due to a React key change. I'll investigate.

Thank you, I'm also trying to find a way to do so.

Another, perhaps easier, solution would be to rate limit the track on the client side. I.e. the React component keeps track of the last time it sent an event, and does not send another one, even if asked, for (say) 5s.

Those should both work too.

I removed TrackEvent component because it just passes to service function and resends requests.
Now tracking log looks like as follows and is sent only when each page is displayed at the beginning:
argo-server | time="2022-05-01T03:09:51.503Z" level=info msg="tracking UI usage" name=openedWorkflowList

LGTM! 🚀