crypto: Add Sui + Aggregation support

Added the support for any type of Aggregated Signature.

https://github.com/punwai/narwhal-1/pull/3

https://github.com/punwai/narwhal-1/pull/4

@huitseeker Also, would it be possible to remove the cargo test from the Code Coverage check? AFAIK it's already being done on another workflow and just makes code coverage checking directly on Github annoyingly long.

Also, would it be possible to remove the cargo test run from the Code Coverage check? AFAIK it's already being done on another workflow and just makes code coverage checking directly on Github annoyingly long.

Code coverage computations are done through code instrumentation and can't be computed without running tests.


F2 should not go to the Outline if the active window is the Explorer

F2 should not go to the Outline if the active window is the Explorer.
It should still rename the selected item.

Changed the hot key to swap to the outline to ctrl+f2


Resolves #974

Fixed required parameters and command syntax.
https://github.com/MicrosoftDocs/windows-powershell-docs/issues/974

@dariomws306 @get-itips @tseward
Peer review needed for this PR. Thanks.

Hello @velkovb
It seems that -Name parameter is also required, so we need to remove the [ ] for it.
Thank you!

Agree with @get-itips!

Hello @velkovb
It seems that -Name parameter is also required, so we need to remove the [ ] for it.
Thank you!

@get-itips @dariomws306
Thanks for the feedback but I have to disagree with you.
[-Name]  - means that the parameter value is required but the name can be ommitted because it is a positional parameter.
Optional paramerters have the following syntax:
[-Parameter ]
Optional positional parameter:
[[-Parameter] ]

Hi @velkovb, it's true, you are right. I had not noticed that, my answer is based on my belief that everything was in brackets.

Right!

I'm fine with this.

@AndreaBarr This PR can be merged. Thanks.


Bug 78/v4

Looks overall good to me, event if it can be improved by removing some parts of the checks (like undefined gid of the signature where default value gets used)

I was just redoing this and found out that suricata-verify would fail in case any of the inner levels of yaml tree do not have all the fields available. I don't know if it was always like this or was introduced recently. I'll check it out. Created ticket: https://redmine.openinfosecfoundation.org/issues/4276

I was just redoing this and found out that suricata-verify would fail in case any of the inner levels of yaml tree do not have all the fields available. I don't know if it was always like this or was introduced recently. I'll check it out. Created ticket: https://redmine.openinfosecfoundation.org/issues/4276

Replaced with #429


Configure travis to install/init git lfs

Now that we're using git lfs to manage our large test resources, we need to configure travis to install/init git lfs before running the test suite.

@lbergelson As the resident travis expert, feel like taking this one?

Yeah, I can do this.

Done!


Material gallery "confirmation dialog" demo is no confirmation dialog

How's that? The demo is lifted right from the spec: https://www.google.com/design/spec/components/dialogs.html#dialogs-confirmation-dialogs

wow. I stand corrected. I would not have called that a confirmation dialog.


Display featured jobs on Jobs page, above search results

Description of changes

Displays 'Featured Jobs' section above Ziprecruiter job search section on /jobs page.
Screenshot w/ mock data:

Issue Resolved

MVP requirements for #982
Note - do not merge this yet, as we still need content - the actual 'featured' jobs which will be highlighted at the top of the page. The front-end code is ready for review, I'm currently pulling in data from the static featuredJobs.json file, which only contains mock data for now.  This new feature should not go live until we actually have featured jobs to display on the page.  They can be loaded from featuredJobs.json or the API & DB (see Back-end PR # 366)

@ksmacleod99 @hollomancer Please post an update in here or Reach out via Slack message when the initial content is ready for this.

@kylemh I added a contact link in response to your comment - it will display below featured jobs, or if there are no jobs, it can serve as the placeholder text:

@hollomancer @ksmacleod99 Do you two want to go live with this now (without any featured jobs listed yet)? If so, let me know, and I can unblock/merge this.  The page will appear like so, with only the contact link:

The first set of featured job data has been posted in #985, and has been added to the static JSON file.


Storage: CreateVolumeFromCopy only set volume size from expanded config when source is image

For LVM and ZFS.

Testsuite passed


Request - Possible compatibility for Miyoo Mini (RetroArch)

Hi there,  thank you for your amazing work on  Amiga Vision/ MegaAGS for MiSTer it's pretty much the only content I use on the device.
I was hoping you might know or be able to assist with getting the 'MegaAGS-Pocket'  version of AmigaVision working on a Miyoo Mini, or any other linux handheld that uses RetroArch.  From my attempts, it seems to me that the requirement for the 'MegaAGS-Kickstart.rom' means that some of the available emulators on RetroArch will not boot the 'MegaAGS-Pocket.hdf' as they require specific hardcoded Kickstarts.
I was wondering if you had any experience / joy in getting AmigaVision working on these RetroArch powered devices.
All the best.

There is no Pocket-specific version anymore, as the majority of the platforms can handle 4GB+ image files either via exFAT or ext4. I have used my personal setup on an Anbernic RG35XX H (these names 🙄) using the puae2021 for the best results so far, but we are also working with the author of Amiberry to see if we can make it even better.
Closing this issue as we are tracking this in #184.


[SPARK-21696][SS]Fix a potential issue that may generate partial snapshot files

What changes were proposed in this pull request?
Directly writing a snapshot file may generate a partial file. This PR changes it to write to a temp file then rename to the target file.
How was this patch tested?
Jenkins.

@tdas

Test build #80557 has started for PR 18928 at commit c0b4655.

Test build #80557 has finished for PR 18928 at commit c0b4655.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80557/
Test PASSed.

LGTM.

@zsxwing Can you elaborate on why writing to a file directly may generate a partial file? Is this about an exception terminating the write to the underlying file system while the maintenance task is writing?

@YuvalItzchakov there are many cases: power outage, the process is killed by oom killer, or the user calls System.exit...

Right. We've had some problems with reading snapshots after executors dying on OOM, I hope this does the trick :)
Thanks.


Microsoft.Network/trafficManagerProfiles priority marked for removal

Describe the noise
Resource type (i.e. Microsoft.Storage/storageAccounts)
Microsoft.Network/trafficManagerProfiles
apiVersion (i.e. 2019-04-01)
2018-04-01
Client (PowerShell, Azure CLI, or API)
Azure CLI 2.10.1
Relevant ARM Template code (we only need the resource object for the above resourceType and apiVersion, but if it's easier you can include the entire template
{
  "type":"Microsoft.Network/trafficManagerProfiles",
  "apiVersion":"2018-04-01",
  "name":"myTrafficManager",
  "location":"global",
  "properties":{
    "profileStatus":"Enabled",
    "trafficRoutingMethod":"Performance",
    "dnsConfig":{
      "relativeName":"myTrafficManager",
      "ttl":60
    },
    "monitorConfig":{
      "profileMonitorStatus":"Enabled",
      "protocol":"HTTPS",
      "port":443,
      "path":"/health",
      "intervalInSeconds":30,
      "toleratedNumberOfFailures":3,
      "timeoutInSeconds":10
    },
    "endpoints":[
      {
        "id":"[concat(resourceId('Microsoft.Network/trafficManagerProfiles', 'myTrafficManager'), '/azureEndpoints/northeurope')]",
        "name":"northeurope",
        "type":"Microsoft.Network/trafficManagerProfiles/azureEndpoints",
        "properties":{
          "endpointStatus":"Enabled",
          "targetResourceId":"/subscriptions/<SUB_ID>/resourceGroups/<RESOURCE_GROUP>/providers/Microsoft.Network/publicIPAddresses/<PUBLIC_IP_NAME>]",
          "target":"my.domain.examle.com",
          "endpointLocation":"North Europe"
        }
      }
    ],
    "trafficViewEnrollmentStatus":"Disabled",
    "maxReturn":0
  }
}

Expected response (i.e. "I expected no noise since the template has not been modified since the resources were deployed)
No noise if the resource has already been created
Current (noisy) response (either include a screenshot of the what-if output, or copy/paste the text)
~ Microsoft.Network/trafficManagerProfiles/myTrafficManager [2018-04-01]
    ~ properties.endpoints: [
      ~ 0:
        - properties.priority:         1

Additional context
As priority is an optional argument the what-if command should maybe ignore this if the trafficRoutingMethod is not Pirority

[w40].

This fix should be full deployed. Let us know if you are still seeing the issue.

I have tried to run what-if for this template today and it looks like this noise is still present.

Investigating...

Found the cause and fixed it again. Waiting on deployment.

Week?

[w44]?

@shenglol - can we confirm this went out in w44

This fix has been deployed. Please let us know if you still see the issue.

This fix has been deployed. Please let us know if you still see the issue.

Looks good to me! :) Seems like this noise is no longer present. Thank you for this fix :+1:

Looks good to me! :) Seems like this noise is no longer present. Thank you for this fix :+1:


Arc 2745 fix exp time

What's in this PR?
Add ff to reduce the app token exp time
Why
TEN MINUTES is the max allowed, prone to error
Added feature flags
app-token-exp-in-milli-sec
Affected issues
ARC-2745
How has this been tested?
Unit test
Whats Next?

I don't like my PR.


[Snyk] Fix for 5 vulnerabilities

Snyk has created this PR to fix 5 vulnerabilities in the yarn dependencies of this project.
Snyk changed the following file(s):

plugins/microsoft-calendar/package.json

Note for zero-installs users
If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠ Warning
Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Regular Expression Denial of Service (ReDoS) SNYK-JS-ZOD-5925617
  264

Cross-site Scripting (XSS) SNYK-JS-DOMPURIFY-8184974
  248

Prototype Pollution SNYK-JS-DOMPURIFY-7984421
  192

Template Injection SNYK-JS-DOMPURIFY-6474511
  89

Improper Input Validation SNYK-JS-NANOID-8492085
  44

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Prototype Pollution
🦉 Cross-site Scripting (XSS)
🦉 Improper Input Validation
🦉 More lessons are available in Snyk Learn

:no_entry: Snyk checks have failed. 1 issues have been found so far.

Icon
Severity
Issues

Critical
0

High
0

Medium
1

Low
0

:no_entry: security/snyk check is complete. 1 issues have been found. (View Details)
:white_check_mark: license/snyk check is complete. No issues have been found. (View Details)


Fix: UI bugs had been rectified in Registration Page

Issue Number : #139
Registration Page Initially

Main Issues:

The image has been given proper margin and border radius, without cropping it.
In dark mode, the input text is in white color, with the same color applied to the input text box. Now, it is visible, and the issue has been rectified.

Side Issues

The Github link in navbar is in the wrong position.
There is extra margin for the Name input boxes at their top, bottom, and left.
There is improper space alignment for the password description and the policy agreement checkbox.
Forms have been made scrollable.
These issues also have been rectified.

Modified Registration Page

THough it looks good but can you fix the image and other changes on the signin page too ?

If you tell the requirements you expect clearly, I can able to do it

The UI modifications that you did on the registration page is same as in login page, will just suggest to avoid inline css and add the styling modifications in auth.css and that will hopefully reflect on the login page too


Zoom Source not available

Windows version 10.0.19045.3324]
Pyton 3.10.11
PyWinCtl 0.0.38
The zoom-and-follow  script charged in the right way, but the Zoom Source is not available in the windows properties.
Do Anyone has the solution?
Where is the problem?

What version of the script are you using?
Can you reproduce the issue on the current version?


delete Release?

is there any available Api that will allow me to delete release?

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

ID: 4fdce00f-8d63-9ac8-67da-cd49b59d6fa2
Version Independent ID: 44a6c5d6-3f8a-563e-434d-e19ec337224e
Content: Releases (Azure DevOps Release)
Content Source: docs-ref-autogen/5.0/release/Releases.yml
Product: devops
Technology: devops-ref
GitHub Login: @wnjenkin
Microsoft Alias: whjenkin

I also would like this feature as someone left an incorrect CI trigger switched on overnight to run every 3 minutes that created 300+ releases which now need to be cleaned up


Add int16 support to MINIMUM and MAXIMUM

This is needed for running this ops when using int16x8 quantization for audio models

Hi Andresovela:
Does TFLM support mfcc ops? This is also needed for audio models

Sorry, I don't know the answer to that


what is the difference between softmax and marginal mode in crf

the two modes in crf are join mode and marginal mode,but i am not clear about the marginal mode,and i use this mode to train the data, the result is almost same to the softmax, anyone can explain it?

@KARABAER  join mode is the real CRF by defnition, and the Viterbi algorithm gives you the usual prediction result, which is not softmax but best path. Since CRF is non-direct graph that models join distribution of all time slices, you can not get independent probability distribution for each time slice like RNN.   But of course you can talk about marginal distribution of each time slice either in training time or prediction time (see argument test_mode).  The marginal mode gives marginal distribution for each time slice at training time and uses the usual categorical crossentropy as loss, which is NOT the real CRF by definition, but is an approximation that some implementation does as it fits the neural network (direct graph) architect. It is similar to something called sum-product algorithm.

@linxihui I don't understand how marginal mode works. How do we calculate marginal probabilities after CRF layer at each time step?

@linxihui But there is mathematical formulation in a linear chain CRF to find the marginal probabilities at each time step. Please refer to this. What we need to calculate this are the forward path scores and the backward path scores (alpha and beta respectively).
Say, we want to find the marginal distribution at time step i, then we need alpha i-1 and beta i+1 along with the unary score at time step i.
What I wanted to ask @lzfelix was, if it's possible to do this in the current keras implementation. To be more specific, I need to calculate marginal probabilities in the join mode. Is it possible to do so with the current implementation?

To the best of my knowledge, if you want the probability distribution of observing each of the C possible labels at the i-th timestep, then you are going to need to compute the forward pass, ie. alpha, until timestep i, you don't need beta at all. Just remember that alpha computes the probability of arriving at some label at the i-th timestep from the beginning of the sequence, while beta[i] yields the probability of starting the sequence at the i-th timestep and observing some label in there and arriving at the end of the sequence, assuming that your sample is prepended and appended with special tokens that mark begin and end of sequence. You can find more details regarding these details on Jacob Eisenstein's NLP book, which is public and it can be found here.
Regarding the second part of your question, where you want to compute the probabilities of observing some desired label at the i-th timestep using the join mode, which in turn uses the the forward-backward, or, more specifically, the alpha computations, I do not this that this is possible right now. Maybe you could use the marginal mode as an approximation, as originally suggested by @linxihui ?

Since the performance of join mode is much better than marginal mode, we prefer to use join mode but the marginal probability is also important in application. I also wonder how CRF++ toolkit calculates the probability and can we learn from it.


Flow Propagation in GMFlow (CVPR22) vs Flow Field Deformation in LiteFlowNet3 (ECCV20)

Congratulations on your new work!
I think the idea of flow propagation in GMFlow is similar to the flow field deformation in LiteFlowNet3. Both of us propagate flow predictions and measure feature self-similarity. However,  LiteFlowNet3 was not cited in GMFlow.

Hi @twhui , thank you for bringing the flow field deformation in LiteFlowNet3 to our attention, sorry that we are not aware of this approach while working on our GMFlow project.
Actually, our flow propagation was inspired by the GMA (ICCV 2021) paper, as we have mentioned in our paper. However, I do agree that our high-level idea is similar after checking the LiteFlowNet3 paper despite some difference in implementations. Unfortunately the CVPR camera ready deadline has passed, but I will add LiteFlowNet3 in our extended paper in future. Thanks and wish all the best!

Hi @twhui ,
FYI, I have referenced LiteFlowNet3 in our updated arxiv paper.

Thank you.


Validation layer errors in samples

Hello!
I'm very interested in your work, so I took a look at the examples, and it seems they all generate errors on my pc.
The line 186 of simpleQuad.cpp generates these two errors:
VUID-VkMappedMemoryRange-size-01390(ERROR / SPEC): msgNum: 203426524 - vkFlushMappedMemoryRanges: Size in pMemRanges[0] is 0x18, which is not a multiple of VkPhysicalDeviceLimits::nonCoherentAtomSize (0x40). The spec valid usage text states 'If size is not equal to VK_WHOLE_SIZE, size must either be a multiple of VkPhysicalDeviceLimits::nonCoherentAtomSize, or offset plus size must equal the size of memory.' (https://www.khronos.org/registry/vulkan/specs/1.0/html/vkspec.html#VUID-VkMappedMemoryRange-size-01390)
and
 Objects: 1        [0] 0x4, type: 8, name: (null) Validation(ERROR): msg_code: 203426524:  [ VUID-VkMappedMemoryRange-size-01390 ]  [ VUID-VkMappedMemoryRange-size-01390 ] Object: 0x4 (Type = 8) | vkFlushMappedMemoryRanges: Size in pMemRanges[0] is 0x18, which is not a multiple of VkPhysicalDeviceLimits::nonCoherentAtomSize (0x40). The spec valid usage text states 'If size is not equal to VK_WHOLE_SIZE, size must either be a multiple of VkPhysicalDeviceLimits::nonCoherentAtomSize, or offset plus size must equal the size of memory.' (https://www.khronos.org/registry/vulkan/specs/1.0/html/vkspec.html#VUID-VkMappedMemoryRange-size-01390)
After that, the line 339 generate these errors:
VUID-VkSubpassDependency-dstAccessMask-00869(ERROR / SPEC): msgNum: 333448906 - CreateRenderPass: pDependencies[0].dstAccessMask (0x100) is not supported by dstStageMask (0x2000). The spec valid usage text states 'Any access flag included in dstAccessMask must be supported by one of the pipeline stages in dstStageMask, as specified in the table of supported access types.' (https://www.khronos.org/registry/vulkan/specs/1.0/html/vkspec.html#VUID-VkSubpassDependency-dstAccessMask-00869)
,
Objects: 1        [0] 0x0, type: 0, name: (null) Validation(ERROR): msg_code: 333448906:  [ VUID-VkSubpassDependency-dstAccessMask-00869 ]  [ VUID-VkSubpassDependency-dstAccessMask-00869 ] Object: VK_NULL_HANDLE (Type = 0) | CreateRenderPass: pDependencies[0].dstAccessMask (0x100) is not supported by dstStageMask (0x2000). The spec valid usage text states 'Any access flag included in dstAccessMask must be supported by one of the pipeline stages in dstStageMask, as specified in the table of supported access types.' (https://www.khronos.org/registry/vulkan/specs/1.0/html/vkspec.html#VUID-VkSubpassDependency-dstAccessMask-00869)
,
VUID-VkSubpassDependency-srcAccessMask-00868(ERROR / SPEC): msgNum: 333448904 - CreateRenderPass: pDependencies[1].srcAccessMask (0x100) is not supported by srcStageMask (0x2000). The spec valid usage text states 'Any access flag included in srcAccessMask must be supported by one of the pipeline stages in srcStageMask, as specified in the table of supported access types.' (https://www.khronos.org/registry/vulkan/specs/1.0/html/vkspec.html#VUID-VkSubpassDependency-srcAccessMask-00868)
and
Objects: 1        [0] 0x0, type: 0, name: (null) Validation(ERROR): msg_code: 333448904:  [ VUID-VkSubpassDependency-srcAccessMask-00868 ]  [ VUID-VkSubpassDependency-srcAccessMask-00868 ] Object: VK_NULL_HANDLE (Type = 0) | CreateRenderPass: pDependencies[1].srcAccessMask (0x100) is not supported by srcStageMask (0x2000). The spec valid usage text states 'Any access flag included in srcAccessMask must be supported by one of the pipeline stages in srcStageMask, as specified in the table of supported access types.' (https://www.khronos.org/registry/vulkan/specs/1.0/html/vkspec.html#VUID-VkSubpassDependency-srcAccessMask-00868)
Note that at the end, the SimpleQuad window finally launches.
I hope it can help improve your library. Thx 😄

This has been fixed and will be included in the upcoming open source release of V-EZ.  The source should be live in the next week or two.


can't use A(T) as generic type argument yet, use a more specific type

Sorry for my "silly-from-side" questions, but
https://play.crystal-lang.org/#/r/2neg
abstract class A(T)
  def foo
    puts T.to_s
  end
end

class B < A(Int32)
end

a = [] of A
a << B.new
a.each { |e| p e.foo }

# => Error in line 10: can't use A(T) as generic type argument yet, use a more specific type

It's weird, because A is abstract. Any workarounds?

You are not defining generic type on line 10:
abstract class A(T)
  def foo
    puts T.to_s
  end
end

class B < A(Int32)
end

a = [] of A(Int32) # <<<
a << B.new
a.each { |e| p e.foo }

https://carc.in/#/r/2nf6

@hugoabonizio the whole point of Generics is that there might be class C < A(String). There might be any amount of other classes.

@vladfaust But in [] of A, T is not specified. It could be anything. And that's not supported by the compiler... basically T would be Object here, but that's not supported...

@asterite will supporting Object be implemented some day?

https://www.youtube.com/watch?v=EkPy18xW1j8


issue/34 reworked for better typing

Reworked somethings for better typing. Still need to go through parts of the code that uses forms, and the files in services directory and will go through in future PRs when either fixing or reworking how forms are built.

This is a step in the right direction and not intended to be the complete set of necessary changes, so I'm going to merge this branch and we'll continue building on it.


Allows to find properties file by absolute path

So that the tool could be invoked from any directory.

Thank you, merging!


dont take user to register page if qty is 0

working on it

This is being worked on PR #363

@dreadpool2  thanks closing this


update to<EMAIL_ADDRESS>

includes https://github.com/r3dm/warning/pull/2 for browserify builds

:+1:

Thanks @zertosh !

np @mjackson. would it be possible to publish beta4 with this? it's keeping me from taking react-router 1.0 out for a spin in production (on a small internal site :P)


in the newest v0.11.0, function call breaks when using Claude LLM

After upgrade agent to v0.11, plugins-anthropic to v0.2.2, when using function call feature and using claude llm, there will be a 400 Bad Request error.
How to reproduce:

Using the example function_calling_weather.py
Change LLM to claude-3-5-sonnet-20241022
chat with agent.

(and openai llm works fine).
The problem is after function call, the 2nd call to LLM will be break. The log detail is here:
2024-10-31 10:46:45,680 - DEBUG anthropic._base_client - HTTP Request: POST https://api.anthropic.com/v1/messages "400 Bad Request" {"pid": 97601, "job_id": "AJ_9yyzzj3Bvwuj"}
2024-10-31 10:46:45,680 - DEBUG anthropic._base_client - Encountered httpx.HTTPStatusError
Traceback (most recent call last):
  File "/Users/medal/src/3rd/livekit-agents/examples/voice-pipeline-agent/.venv/lib/python3.12/site-packages/anthropic/_base_client.py", line 1612, in _request
    response.raise_for_status()
  File "/Users/medal/src/3rd/livekit-agents/examples/voice-pipeline-agent/.venv/lib/python3.12/site-packages/httpx/_models.py", line 763, in raise_for_status
    raise HTTPStatusError(message, request=request, response=self)
httpx.HTTPStatusError: Client error '400 Bad Request' for url 'https://api.anthropic.com/v1/messages'
For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400 {"pid": 97601, "job_id": "AJ_9yyzzj3Bvwuj"}
2024-10-31 10:46:45,685 - DEBUG anthropic._base_client - Not retrying as header `x-should-retry` is set to `false` {"pid": 97601, "job_id": "AJ_9yyzzj3Bvwuj"}
2024-10-31 10:46:45,686 - DEBUG anthropic._base_client - Re-raising status error {"pid": 97601, "job_id": "AJ_9yyzzj3Bvwuj"}
2024-10-31 10:46:45,689 - DEBUG livekit.agents.pipeline - speech playout finished {"speech_id": "23dbd39fdf93", "interrupted": false, "pid": 97601, "job_id": "AJ_9yyzzj3Bvwuj"}

Same issue encountered

It should be fixed in #1018. Will release a new version soon


after running un/install OpenCV, still get errors in console

the following errors
# 😺dzNodes: LayerStyle -> Warning: E:\comfy_ui\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI_LayerStyle\resource_dir.ini not found, default directory to be used.
# 😺dzNodes: LayerStyle -> Find 1 LUTs in E:\comfy_ui\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI_LayerStyle\lut
# 😺dzNodes: LayerStyle -> Find 1 Fonts in E:\comfy_ui\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI_LayerStyle\font

# 😺dzNodes: LayerStyle -> Warning: E:\comfy_ui\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI_LayerStyle\custom_size.ini not found, use default size.
# 😺dzNodes: LayerStyle -> Warning: E:\comfy_ui\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI_LayerStyle\custom_size.ini not found, use default size.

start_local_llm error
# 😺dzNodes: LayerStyle -> Warning: E:\comfy_ui\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI_LayerStyle\custom_size.ini not found, use default size.
# 😺dzNodes: LayerStyle -> Warning: E:\comfy_ui\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI_LayerStyle\custom_size.ini not found, use default size.

This information is not related to OpenCV

But how do I get rid of it?

Renaming all .ini.example files in the plugin directory to .ini

Got it thx 😊
thanks
best regards, raf
On Thu, 27 Jun 2024 at 13:40, chflame163 @.***> wrote:

Renaming all .ini.example files in the plugin directory to .ini
—
Reply to this email directly, view it on GitHub
https://github.com/chflame163/ComfyUI_LayerStyle/issues/133#issuecomment-2194456498,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APNXTFUFQ5YUQTADEHK2IKDZJP24RAVCNFSM6AAAAABJROVQD6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJUGQ2TMNBZHA
.
You are receiving this because you authored the thread.Message ID:
@.***>


5 move all database work in a separate module

I used the service.js file to take responsibility for all database usage, and the controller.js file serves as the API file.
I also formatted the code (next time I'll make smaller PRs)

You can assign me here when your PR is ready to review

Once you're done addressing the comments and making the required changes, please click the "reload" button to re-request a review from me

(next time I'll make smaller PRs)

oh any change under 200 lines of code is totally fine. What would be more important (but again not crucial at the scale we're working on) is only including the changes that are within the scope of this change.
E.g. if this PR is about separation of concerns for the back end, then we don't need formatting changes to the HTML


REALMC-9460: Prevent template app creation prompt from occurring automatically

Description
In this PR, I've reworked how the template app creation works within the realm-cli.
First off, I've updated the --template flag to have a default value when it is declared but is not supplied any arguments.
This allows us to distinguish between the following commands:

realm-cli app create --template=<template-id>

realm-cli app create --template

realm-cli app create

1 does not prompt the user for a template because it's already supplied
2 prompts the user for a template
3 does not prompt the user for template because we assume that users do not always want to create a template app.
Updated Help menu

<prompt-templates> is a special value used to distinguish whether we should prompt the user. This is probably going to be the point of contention in this PR since we don't really have this behavior anywhere else in the CLI. I'm happy to try and work this out and iron out the details if this is not acceptable.

blocked on REALMC-9512 for now. we're trying to figure out what our best course of action for providing a way to create a flag with optional arguments


Send correct schema revisions with activity results

also update to latest commits of appcore and bridgesdk

Are the schemaRevisions the same in prod? If not, will likely need an environment check and pass different schemaRevision for each environment.
r=me with caveat above

I can't think why they wouldn't be. Anyway I got them from this document Dwayne pointed me at, which is the definitive source and by all appearances would be the same in all environments: https://github.com/Sage-Bionetworks/BridgePF/blob/develop/conf/application-context.xml#L21


Allow providing custom project npm/yarn settings

NPM and Yarn settings are provided by local .npmrc config file.
We should be able to have such a configuration for an IDE by default enable a project to adapt the configuration to enter custom npm repositories for example. Here an example which environment variable to set for a custom configuration file:
NPM_CONFIG_USERCONFIG=%CD%/%CONF_PATH%/ide-settings-npm-yarn/.npmrc

Thanks for this feedback and input.
If I got you right the project may put this into their $DEVON_IDE_HOME/conf folder. I would rather put .npmrc directly there ommiting this strange ide-settings-npm-yarn subfolder (or is there any rationale for that?).
What will happen if that .npmrc file does not exist or is empty?
If that is tolerated, I would suggest to always export this environment variable NPM_CONFIG_USERCONFIG via devon.properties as ${DEVON_IDE_HOME}/conf/.npmrc and we are done. We could like we do with maven introduce a template that projects can define in their settings git repo.

The reason for the ide-settings-npm-yarn folder was the idea to sharing the config (maybe even more in future) by git.
You could also follow the more easier approach you posted, but this would remove the ability to share the config by git.
In general, I am using the same mechanism for sharing settings for all available settings and wanted to implement an update script in future, which does a pull on all these respositories automatically. Therefore, I was using a common mechanism like git to have a common way of sharing all different settings.

Okay. The idea with devon-ide is that the settings come from a git repo and can therefore be shared. However, the user should also have its freedom to tweak and customize configs rather than being dictated too much from what comes from the git repo. Therefore we put templates in the settings git and use them to initialize the ide by copying the templates to the users conf folder.
We already do the same for the settings.xml from maven. So is your suggestion to have a sub-folder like .m2 for maven also for npm and yarn settings inside conf?
I would like to use something more natural then. So if the variable is named NPM_CONFIG_USERCONFIG why should we just name the folder conf/npm or conf/.npm? The name ide-settings-npm-yarn seems a bit artificial and over-engineered to me.

What would be the content of such .npmrc file?
Can you give us some examples how a template may look like?

Private registry information for example : https://stackoverflow.com/questions/49404870/how-to-set-auth-for-a-scoped-registry-in-npmrc

Totally fine to rename it.

Hope the solution suites your needs.
Closing this issue after PR #130 has been merged.

The NPM_CONFIG_USERCONFIG in devon.properties does not yet point to the path, where the default template file is installed:
${DEVON_IDE_HOME}\npm.npmrc  vs.
${DEVON_IDE_HOME}\conf\npm.npmrc
I should probably open a pull request for this,  but for such one-line-changes the effort seems still a bit high to me.

I should probably open a pull request for this, but for such one-line-changes the effort seems still a bit high to me.

There are almost none:

got to the file on github in web-browser.
click on "pencil" icon.
edit file content in browser and fix the bug
click create feature branch
click new pull request
done.

Seems as @markusschuh is talking about this:
https://github.com/devonfw/devon-ide/blob/1bfa19732af7f435c7945eee2178d915422ddbac/scripts/src/main/resources/scripts/devon.properties#L15
should indeed be conf instead of npm. Thanks for notifying this bug 👍
Will fix it asap.

Fixed with PR #184.


Update workflow --help texts

What was changed

Updated the --help texts of tctl workflow commands
Why?

attempt to make it nicer to read
Checklist

Closes

How was this tested:

Any docs updates needed?

LGTM, but I would request another round from @flossypurse.


General Cache

I didn't spot one, but does the platform have an internal cache for things? page loads on my end are getting a little slow under problems due to the amount of challenges I have added (up to 151)
Memcache or Redis would be suggested.

We have implemented a simple cache for what I expected to be a bottle neck (calculating scores), but not for the challenges.  The problem is that the current implementation makes several queries for each problem, which should be changed without a doubt.  I just honestly never expect > 100 challenges.

Leave it to me to break things :) My CTF is still two months out so I'm doing all kinds of testing of the platform

I really appreciate the feedback.  It's good to have actual use cases that occur more frequently than once per year.    That last commit implements the built-in rails caching for each problem page.  That might start to solve your problem.  I won't be able to generate a test case that large until this weekend (I'll automate it, but writing the automation won't be trivial).  If you get a chance, see if that scratches your itch.  The commits are in the 'dev' branch.

Also, worth mentioning, the cache will only actually work in a "production" environment... so you'll have to run it inside the container or on Heroku to test.

RAILS_ENV=production
RACK_ENV=production
RAILS_SERVE_STATIC_FILES=enabled
LANG=en_US.UTF-8
PORT=3000
SSL_KEY=certs/server.key
SSL_CERT=certs/server.crt
DATABASE_URL=postgresql://xx:xx@localhost/postgres
REDISTOGO_URL=redis://<IP_ADDRESS>:6379/
HOST=ctf.bsidesroc.com
On Fri, Feb 16, 2018 at 7:21 AM, Forrest Fuqua<EMAIL_ADDRESS>wrote:

Nice, I am running the app in "Production" just using a .env to set all
the env vars I need beforehand
Also, I'm running my CTF from an ARM64 2GB Scaleway and its been doing
pretty well, Just docker tends to not work to well in that method.
On Fri, Feb 16, 2018 at 6:55 AM, Paul Jordan<EMAIL_ADDRESS>wrote:

Also, worth mentioning, the cache will only actually work in a
"production" environment... so you'll have to run it inside the container
or on Heroku to test.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mcpa-stlouis/hack-the-arch/issues/43#issuecomment-366216920,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAxE1PpWL0gdSeFNW1h-QxrQibNFyWlyks5tVWzIgaJpZM4SG-iN
.

Arm64 is fine outside of docker, ill look into it more for you,
scaleways are amazing for setting up small VPS quickly
On Sat, Feb 17, 2018 at 1:20 PM, Paul Jordan<EMAIL_ADDRESS>wrote:

Awesome! Did the caching improve the performance? Yeah, it looks like
ARM64 isn't "officially" supported. Does it not build, or does it just not
work?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mcpa-stlouis/hack-the-arch/issues/43#issuecomment-366460856,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAxE1ICktWgy-8suqHGr_M-m6Xjm3Gpoks5tVxhlgaJpZM4SG-iN
.

should note, I think getting a docker version running on a rpi might be the
best target to approach
On Sat, Feb 17, 2018 at 1:27 PM, Forrest Fuqua<EMAIL_ADDRESS>wrote:

Arm64 is fine outside of docker, ill look into it more for you,
scaleways are amazing for setting up small VPS quickly
On Sat, Feb 17, 2018 at 1:20 PM, Paul Jordan<EMAIL_ADDRESS>wrote:

Awesome! Did the caching improve the performance? Yeah, it looks like
ARM64 isn't "officially" supported. Does it not build, or does it just not
work?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mcpa-stlouis/hack-the-arch/issues/43#issuecomment-366460856,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAxE1ICktWgy-8suqHGr_M-m6Xjm3Gpoks5tVxhlgaJpZM4SG-iN
.

Interesting.  So getting Docker running these days on arm is pretty straight forward (I've got an old Pi running it right now).  I'm just not sure if the image needs to be specified.  I'm pretty sure it does, but that's easy.  You'd just change the "FROM" directive to: "FROM: arm64v8/ruby:2.5"  (I'm currently in the process of overhauling the Dockerfile though, so I'd hold off for a few minutes).


Add Musikcube

Musikcube is a open source CLI music player
They have a deb available from their website.
https://github.com/clangen/musikcube/releases/download/0.97.0/musikcube_standalone_0.97.0_x86_64.deb

^ (noted on Github) another untested commit that addresses the issue but dont want to do a PR request unless the code seems ok to the team.

To test it, go in the terminal to the folder where you cloned the repository and run:
./deb-get install musikcube

To test it, go in the terminal to the folder where you cloned the repository and run:
./deb-get install musikcube

thank you for the info


docs: add Raycast Extension to interact with Stretchly

Hi, hovancik
I made a Raycast Extension to interact with Stretchly.
This PR add a mention of Raycast Extension to README.md.

Requirements

Filling out the template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.

[x]  issue was opened to discuss proposed changes before starting implementation. It is important do discuss changes before implementing them (Why should we add it? How should it work? How should it look? Where will it be? ...).
[x]  during development, node version specified in package.json was used (ie using nvm).
[x]  package versions and package-lock.json were not changed (npm install --no-save).
[x]  app version number was not changed.
[x]  all new code has tests to ensure against regressions.
[x] npm run lint reports no offenses.
[x] npm run test is error-free.
[x]  README and CHANGELOG were updated accordingly.
[x]  after PR is approved, all commits in it are squashed

Description of the Change

Verification Process

Other information

Are you on Twitter? Can I tag you there?

this is my Twitter https://twitter.com/skyran1278. Thanks a lot!


Color change Notification

Is it possible that your module send a notification to the mirror with the color code from the overrode css.
So I could use the color-code to control a led light color according the css colors in the mirror.

Hi, you can do this in your module declaration:
Module.register("MMM-YourModuleName", {
  defaults: {
    //...
    events: {
          NOW_PLAYING: "NOW_PLAYING",
    }
  },

  notificationReceived: function (notification, payload) {
    this.config.events[notification]?.split(" ").forEach((e) => {
      switch (e) {
        case "NOW_PLAYING":
          // Read the color from CSS when a new song is played
          // This is the easiest way to get the current color, but lets say that for some reason
          // the color processing is slow (ex: image download), now you have the color of the last song played!
          //
          // Here is solved with a hard coded delay (And that is not the best solution). Adding an event
          // to the OnSpotify module that sends the color when it is updated is probably better, but now
          // you need to know when its processing song colors and not other colors like the pfp color.
          //
          // This is something to keep in mind, if you modify my module to add the event create a PR and I will merge it,
          // the change should be done inside the dom builder in the functions that are invoked on a new session and
          // on song update if I remember correctly

          if (this.nowPlaying) { // If is playing (here you can add more conditions)
            setTimeout(() => {
              /** rgb(255, 100, 50) */
              const cssVariable = getComputedStyle(document.documentElement).getPropertyValue('--ONSP-VIBRANT-VIBRANT').trim();
              /** [R, G, B] */
              const cssColor = cssVariable.includes("rgb") ? cssVariable.match(/\d+/g).map(Number) : [255, 255, 255];

              // Do stuff with you color. Ex: Send it to the node_helper to set your light
              console.log("Current CSS color:", cssColor);
              this.sendSocketNotification("SET_LIGHT_COLOR", { colorArray: cssColor });

            }, 400);
          } else {
            console.log("Current CSS color:", " NOT PLAYING");
            this.sendSocketNotification("SET_LIGHT_COLOR", { colorArray: [0, 0, 0] });
          }

          break;
      }
    })
  }

// [...]
}

Thank you Fabrizz. It works very well. I used the MMM-notification-to-command module to catch the notification.


Main into openqasm

Issue #, if available:
Description of changes:
Sync latest changes from main into openqasm generation feature branch
Testing done:
tox 100%
Merge Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.
General

[ ] I have read the CONTRIBUTING doc
[ ] I used the commit message format described in CONTRIBUTING
[ ] I have updated any necessary documentation, including READMEs and API docs (if appropriate)

Tests

[ ] I have added tests that prove my fix is effective or that my feature works (if appropriate)
[ ] I have checked that my tests are not configured for a specific region or account (if appropriate)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pennylane failures unrelated


Migrate tests to Reedkiln

This effort will include adding CTest items (add_test) to the project. Migrating to Reedkiln will ensure a proper build on newer versions of C and C++.

(paired with codylico/text-complex-plus#10)


Process is terminated due to StackOverflowException.

So it looks like the newest version of ccdocgen is throwing a stackoverflowexception. No stacktrace, just the message in the title. Happens on any project that I've built with any sort of complexity that has the "Emit contracts into XML doc files" checked. Killed many a build today.
Also, I figured that I could spend the night putting in a fix. Did a fork, pulled down, opened up Visual Studio... And I got stuck. I have no idea where that app lives in the code base. I found ccdoc10 but I can't figure out which solution that is housed in. Nor when opening up the project file can I find DataStructures10 or ContractMSInternal. Also it's late and I'm getting tired... If you can point me in the right direction, I'll take a crack at it but otherwise I guess I'll just say glhf (good luck, have fun).

Hi @JaCraig,
Thanks for taking the time to report this, and even to investigate it! We are all living with confusing code for now I think. Like many of the executables in Code Contracts, ccdocgen.exe is created by an ILMerge pass that runs separately from the normal build you see in Visual Studio - hence why you weren't able to find it. The primary ILMerge operations are defined here, and ccdocgen is created from ccdoc.exe plus these libraries.
Unfortunately the source code for all of this is not in this repository. All I see is a big group of binaries.

Just to confirm, I am also seeing this issue.

@sharwell I say this with all love and affection as someone who genuinely likes many of the things that you've worked on over the years (ANTLR, Code Contracts, DartVS, etc): But damn, you crazy.
That is one heck of a build process and debugging must be interesting... Are they binaries for a reason? For instance, if I were to say disassemble those DLLs, set up a project tree, etc. for those things would that be bad? Or are they just binaries because the code has been lost to time and the merge is really the only option without some work?

All of those assemblies are from CCI2: https://cciast.codeplex.com/. They should be replaced by a NuGet dependence, but I don't believe there is a NuGet package for them yet. We created the tools with ILMerge just because it made deployment easier (or at least, we thought it did --- it also reduces startup time because .NET seems to perform better with fewer assemblies). It would certainly be possible to change this decision and stop merging the assemblies to create the different tools.

@JaCraig :laughing: I had basically nothing to do with the build process in Code Contracts. In all fairness, my educated guess as to why it's so crazy is the project was started in the very early days of .NET and had access to internal projects (e.g. Spec#/Singularity/Midori) that never panned out. For anything where you think "that would be a bad idea", the item was probably in place in this code a few years before anyone actually decided the idea was bad.

@mike-barnett No, you guys can keep doing you. If the code for the assemblies is available then that means debugging isn't that bad. I just saw his comment of "All I see is a big group of binaries" and I audibly gasped. I've worked with research projects in the past where certain items were binaries because the person who started the project kicked it to a couple of grad students who didn't understand source control... So instantly my mind went to the scene from planet of the apes. One of you comes to a beach where you find the shattered remains of a CD with the original code. You drop to your knees and shout angrily at the sky "You Maniacs!    Good to know that isn't the case.
So I guess I'm also downloading CCI2 tonight. Well actually I'll try debugging without it first but good to know what those items are before I make the attempt.

Just for completeness: My builds in 2015 fail, too, but with
C:\Program Files (x86)\Microsoft\Contracts\MsBuild\v14.0\Microsoft.CodeContracts.targets(642,5): error MSB3073: The command ""C:\Program Files (x86)\Microsoft\Contracts\Bin\ccdocgen.exe"<EMAIL_ADDRESS>exited with code -1073741571.

@JaCraig A simple way to debug this without the need to have CCI2 or fiddle around with the build is to use JetBrains DotPeek and just generate PDB and source code directly from ccdocgen.exe.
The bug seems to be in CCI2:
namespace Microsoft.Cci.ILToCodeModel
{
  internal class ClosureFinder : CodeTraverser
  {
    ...

    private void AddOuterClosures(ITypeDefinition typeDefinition)
    {
      foreach (IFieldReference fieldReference in typeDefinition.Fields)
      {
        ITypeDefinition resolvedType = fieldReference.Type.ResolvedType;
        if (TypeHelper.IsCompilerGenerated(resolvedType) && !TypeHelper.IsEmbeddedInteropType(resolvedType))
        {
          this.closures.Add(resolvedType.InternedKey, (object) resolvedType);
          // => here the recursion happens:
          this.AddOuterClosures(resolvedType);
        }
      }
    }
  }
}

@mike-barnett this bug seems to be old - just that with assemblies generated by VS2013 this method get's never invoked.

Hmm, it probably has to do with the way that Roslyn has changed their code generation pattern for static closures (those that don't capture anything). Anyone have a repro that I can use to track it down?

@mike-barnett https://tomstoolbox.codeplex.com/SourceControl/latest
Just download and rebuild the Core module with VS2015

@mike-barnett if you think about making CCI2 an official package, there might be other requirements to consider. E.g. there is already a shadow copy for CCI around (https://www.nuget.org/packages/SymbolSource.Microsoft.Cci.Metadata/) because too few interfaces are public, making basic tasks like getting the list of source file names impossible (see e.g. https://github.com/NuGet/Home/issues/304 or https://github.com/NuGet/Home/issues/529). Relaxing the access of some classes would highly increase the usability of this library.

I got a StackOverflowException from VS2015 itself in the same class, ClosureFinder.

Can someone please provide a repo example?

https://tomstoolbox.codeplex.com/SourceControl/latest
Just download and rebuild the Core module with VS2015

@tom-englert Thanks, will try.
I just thought, that maybe someone already analyzed the issue and got small repo that could be easily used in unit tests for checking this issue.

@SergeyTeplyakov you would need to store a binary and run ccdocgen.exe against this.
Are there already unit tests covering ccdocgen?

Hi, @tom-englert, I don't know how to contact you directly, but we're working with Mike on migration this repo to dotnet foundation and I need to ask something. Could you please send me an email to<EMAIL_ADDRESS>and I'll reply to it with my question?

The same problem. Emitting contracts into XML doc works under VS 2013, and fails with StackoverflowException under VS 2015. Turning off "Emit contracts..." is a workaround.

@mike-barnett this bug is a real show stopper, but I don't see any progress.
Are there any plans to fix CCI2? Or are we supposed to clone the CCI2 sources an do our own fix?

@SergeyTeplyakov do you know anything new about this?

Sorry! I will try to get to this on the weekend.

@SergeyTeplyakov So is it possible to fix this bug in any way outside of decompiling the binary?
I am working around the bug by checking in generated doc files in hope that not a lot of discrepancy would accumulate before the bug is fixed, but that becomes tedious to maintain...

@mike-barnett any news?

@mike-barnett I have created a patch for https://cciast.codeplex.com (17904) that should fix this issue.
There is another patch for https://ccimetadata.codeplex.com (17902) that adds a simple function to pdb reader to enhace usage. It would be great it that could be published, too.

Any chance of getting this fixed?  It's a major head-ache and seems a pretty serious bug to me.Given the CCIAST has been reported, with a fix since Jun 11, 2013, I guess that's never going to be fixed.

Okay, sorry about the long delay. I have checked in the fixed sources to CCI (including the two patches 17904 and 17902). But I have not built new CCI2 binaries and checked them in to the Code Contracts repo, so if you can take care of that, then that would be great.
I haven't done anything yet about distributing CCI through NuGet, but that would be great. I'm still waiting to hear about getting both CCI and Code Contracts moved to the .NET Foundation organization. Hope to have news about that soon.

@mike-barnett Thanks! @tom-englert Are you able to sort this out?

I'll take a look at this

@mike-barnett I have downloaded the latest source of CCI, and I could prove that the new version fixes the bug. However, there are some open questions that are blocking me:

The CCDoc project exists, but was not part of the solution; instead there is a CCDoc.exe in the ImportedCCI2 folder.
The sources at codeplex seem to differ from the ones that have been used to create the original CCI2 import:
The source contains contracts, but contracts are turned off in the project settings. The ImportedCCI2 folder did contain contract information.
The imported dlls were all signed, while the source at codeplex does not contain any signing information.
The Microsoft.Cci.VBSourceEmitter.dll is not part of the codeplex sources, so I had to disable the usage of this dll to run my test.

I'd ** really ** need to get this bug fix, so I downloaded the latest source.
I then open a VS2015 cmd window and start
buildCC 1.9.12345.1
and unfortunatly get this error:
TlbExp : error TX0000: Can't load the assembly 'file:///C:/Tests/ON_MSCodeContract/16Oct2015/Microsoft.VisualStudio.CodeTools/CodeToolsSetup/Tools/TlbExp.exe' (Exception de HRESULT : 0x80131515)
Why not updating asap?
https://visualstudiogallery.msdn.microsoft.com/1ec7db13-3363-46c9-851f-1ce455f66970

I finally succeeded the compilation, for an unknown reason doing
>Tools\tlbexp ..\ITaskManager\bin\Release\ITaskManager.dll /out:..\TLB\ITaskManager.tlb

worked, and then recompiling again
>buildCC 1.9.12345.1

worked as well and produced Contracts.devlab9ts.msi
Nevertheless installing this fixed version still ends up in VS2015 with the error:
The command ""C:\Program Files (x86)\Microsoft\Contracts\Bin\ccdocgen.exe"<EMAIL_ADDRESS>exited with code 255.	MyDllThatUsesMSCC

and works if I disable Emit contracts into XML doc file, which is not an option.
I have no more time to lose on this, we should have waited more than 3 months before moving our dev to VS2015 after it gets RTM, we decided to revert back to VS2013 with old working MS Code Contract.

@psmacchia there is no fix committed yet for this issue,,,

@tom-Englert: Sorry to take so long to get back to you! I'm pretty sure that CCDoc was moved from the CCI tree to the CC tree. Where are you finding the CCDoc sources in the CCI CodePlex tree? I believe all of the assemblies are just signed with the .snk that is part of the solution. And where are you seeing the VB Source Emitter?

@mike-barnett:
CCDoc: Yes, the project and the sources are in the CC tree at Microsoft.Research/CCDoc/CCDoc10.csproj, however the project is not part of the solution. Instead there is a precompiled CCDoc.exe at /Microsoft.Research/ImportedCCI2/CCDoc.exe so I assume that was never built but just the imported version was used.
I am able to build a new CCDoc.exe by adding the CCDoc project to the solution, however I wonder if that build output would make it into the final installer or if the precompiled .exe would still be used. Once I can build CCDoc I think I can figure that out.
The CCDoc project is referencing the VBSourceEmitter, and I can find the imported dll at Microsoft.Research/ImportedCCI2/Microsoft.Cci.VBSourceEmitter.dll. However the sources at https://cciast.codeplex.com/SourceControl/latest don't contain such a project.
None of the sources at codeplex has CodeContracts turned on.However there are contract reference assemblies that came with the original import: Microsoft.Research/ImportedCCI2/CodeContracts
For the signing you are right, that's enabled in the codeplex sources, I will sort that out.

@tom-englert  so I spent another hour yet without success. I downloaded the last 276MB MSCC source and then try to recompile with buildCC and this time I stumbled on a new compile error
CTC : fatal error CTC2013: Can't start preprocessor (2) [C:\Tests\ON_MSCodeContract\27Oct2015\Microsoft.VisualStudio.CodeTools\TaskManagerUI\TaskManagerUi.vcxproj]

On the web on this error it is said to install VC++ so I installed it for both VS2013 and VS2015, restart my machine because this requires a restart, and retry buildCC with no luck same error.
All in all I lost more than 8 hours trying to make work MSCC with VS2015, still no success. Including Contracts.devlab9ts.msi within the MSCC github zip would have saved me a lot of time, or is buildCC a mandatory pain to deserve MSCC?

@psmacchia The error you are seeing may be caused by lack of VC++ compiler in your Visual Studio installation. It is required to compile Visual Studio integration parts of CodeContratcs. Do you have it installed?
Anyway, I have resolved merge conflicts in Tom's fix and build an installer for your convenience. You can download Contracts.devlab9ts.msi from AppVeyor:
https://ci.appveyor.com/project/hubuk/codecontracts/build/1.9.11027.13/artifacts
Let us know if your problem is gone after update.

@hubuk I downloaded this Contracts.devlab9ts.msi and still no luck.
It installs fine in VS2015 (I can see the right version from Extension and Update) but still no tab Code Contracts in Project Properties.
Same behavior under VS2013 (still no tab Code Contracts in Project Properties.) with the exception that version got from Extension and Update is still the old one.
If you want me to test more please provide me with a downloadable  Contracts.devlab9ts.msi you've compiled.

@psmacchia I once had the same problem, I solved it by first uninstall the existing version and the start the .msi from an administrative command prompt. Just double clicking sometimes seems to run some parts with the wrong elevation level.

@hubuk I also tested your msi above and had the same problem as @psmacchia: There is no Code Contracts tab in the Project Properties in VS2015 (started the msi from within an administrative command prompt).

I am looking into it.

@taschna @psmacchia CodeToolsUpdate project required some changes. I have submit a PR #281.
I will create an installer for you tomorrow.

@psmacchia @taschna I was able to build a new installer. However there is a one more problem which need to be addressed in addition to the previous one. I will be working on a fix and in a meantime you can check a new installer. It is available here:
https://ci.appveyor.com/project/hubuk/codecontracts/build/1.9.11028.16/artifacts
One additional thing you need to do is to create a CodeContractsAfter.targets file in C:\Program Files (x86)\MSBuild\14.0\Microsoft.Common.Targets\ImportAfter for VS2015 with the following content:
<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <!-- Begin CodeTools: CodeContracts: After -->
  <PropertyGroup>
    <CodeContractsInstallDir Condition="'$(CodeContractsInstallDir)'==''">C:\Program Files (x86)\Microsoft\Contracts\</CodeContractsInstallDir>
  </PropertyGroup>
  <Import Condition="'$(CodeContractsImported)' != 'true' AND '$(DontImportCodeContracts)' != 'true'" Project="$(CodeContractsInstallDir)MsBuild\v14.0\Microsoft.CodeContracts.targets" />

  <!-- End CodeTools: CodeContracts: After -->
</Project>

For some reason installer is not creating this file out of box.

@hubuk Have you created an issue for that?

@sharwell Unfortunately no. I do not know if it is still required. I have already submit a PR #282 for the issue.

@hubuk: The new installer worked exactly as promised: the project tab is visible and the XML file is emmitted. Thank you for the work!

@taschna I was only fixing my own defects:) @tom-englert provided the fix in title.

Ok, I finally found some time to test and all bugs I reported seems fixed, thanks. I am using this version https://ci.appveyor.com/project/hubuk/codecontracts/build/1.9.11111.33/artifacts
However I found a new bug, not a blocker one as previous one, yet it prevent a pro usage.
We have a lot of require not null contracts and I noticed that the contract formatting that used to be displayed as csharp="XYZ != null" is now csharp="!(XYZ <= null)". If I look in the xml generated I get:
// XML Generated Now     csharp="!(initialSeq <= null)"
<requires description="initialSeq must not be null" csharp="!(initialSeq <= null)" vb="!(initialSeq <= Nothing)">!(initialSeq <= null)</requires>

// XML Generated Before  csharp="initialSeq != null"
<requires description="initialSeq must not be null" csharp="initialSeq != null" vb="initialSeq <> Nothing">initialSeq != null</requires>

Here is the contract declaration in the C# code:
// Contract declaration in the C# code
Contract.Requires(initialSeq != null, "initialSeq must not be null");

At a guess, that's due to the way Roslyn now emits != null checks.
What's the IL for your contract declaration?

Please investigate.
Sorry I cannot take the time to  install CC 1.9 / deinstall CC 1.9 / reinstall CC 1.7 to work, it takes some time to apply this very tedious procedure http://stackoverflow.com/a/27914825/27194
Also why Roslyn would be the cause? It is the job of CC to weave the contract IL, isn't it? Does it uses Roslyn for that?
Here is the IL when compiled with VS2013 + Code Contract 1.7 if it can help:
L_0000: ldarg.0
L_0001: ldnull
L_0002: ceq
L_0004: ldc.i4.0
L_0005: ceq
L_0007: ldstr "initialSeq must not be null"
L_000c: ldstr "initialSeq != null"
L_0011: call void System.Diagnostics.Contracts.__ContractsRuntime::Requires(bool, string, string)
L_0016: nop
L_0017: ldarg.1
L_0018: ldnull
L_0019: ceq
L_001b: ldc.i4.0
L_001c: ceq

Yep. Here's the IL from VS2015 (Update 1 RC) after being rewritten with 1.9.1:
	IL_0000: ldarg.0
	IL_0001: ldnull
	IL_0002: cgt.un
	IL_0004: ldstr "initialSeq must not be null"
	IL_0009: ldstr "initialSeq != null"
	IL_000e: call void System.Diagnostics.Contracts.__ContractsRuntime::Requires(bool, string, string)
	IL_0013: nop
	IL_0014: nop
	IL_0015: br IL_001a

Thanks Yaakov, did you fix anything? is there a build I can try from https://ci.appveyor.com/project/hubuk/codecontracts ?
Your IL looks fine isn't it? "initialSeq != null"
Or is the bug still unfixed and you get:  !(initialSeq  <= null)"  in the XML doc rewritten by CC?

No, I don't have much expertise in actually modifying Code Contracts. I can edit the system contracts and that's about it.
But this is likely cause by Roslyn - Roslyn compiler emits x != null as x > null, whereas the old <= VS2013 compiler emitted it as (x == null) == 0 as you can see from your IL above.
ccdocgen likely needs to be updated to understand that x > null also means x != null, but I'd have no idea how to go about doing that.

Thanks yaakov-h, I opened a new issue, hopefully someone able to modify CC will handle it, thank
https://github.com/Microsoft/CodeContracts/issues/307

The best thing (I think, not having looked at the code…) would be to fix the CCI2 decompiler to understand this idiom and produce the x != null expression from the IL. Then all downstream tools, such as CCDoc, will automatically do the right thing.
Mike
From: psmacchia<EMAIL_ADDRESS>Sent: Wednesday, November 18, 2015 9:14 PM
To: Microsoft/CodeContracts<EMAIL_ADDRESS>Cc: Mike Barnett<EMAIL_ADDRESS>Subject: Re: [CodeContracts] Process is terminated due to StackOverflowException. (#169)
Thanks yaakov-h, I opened a new issue, hopefully someone able to modify CC will handle it, thank
#307https://github.com/Microsoft/CodeContracts/issues/307
—
Reply to this email directly or view it on GitHubhttps://github.com/Microsoft/CodeContracts/issues/169#issuecomment-157952976.

I had a brief look at the code and don't understand it fully, but I also think CCI is where the fix ought to go.

Is there any status on this stack overflow issue and when it is expected to be addressed?
It just started happening out of the blue in a project and I undid all the changes I made before it occurred but it seems once it occurs it doesn't go away.
I tried to read through this open issue and maybe I missed it but I don't see any workarounds either, are we screwed once this occurs and we have to disable code contracts to move forward? I mean if we cannot compile a project it kind of screws everything else that is dependent on that project.

@CreepyGnome StackOverflowException should be already fixed, but fixed version has not been relrease yet. You can clone repository and build an installer from master branch.
You can also use an installer produced by one of my latest builds. Unfortunately due to some problems with versioning scheme used by the project it has lower version number than the released one. As a result Visual Studio will keep telling you that it is outdated.

Code Contracts seem fragile enough right now as it is (crashes at least once every hour or so but seems to recover) that I don't think I should be experimenting with unofficial releases.  I like them, but right now I have a whole solution that have them disabled because of this stack overflow issue. Everything was fine and then it just started out of the blue and there appears to be no workaround once it starts. This seems like a fatal/critical bug and should prompted a release just for it as it is completely blocking.
I am aware of the version issue and have put in place the work around I posted on that issue.  So it does not tell me I am out of date, and I hope in the next official release that fix will be included and should just overwrite my workaround.

We rolled out build 1.9.11111.33 from appveyor, and the SO in CCDoc is certainly fixed, thank you @hubuk!

It's six months since the last release of Code Contracts - and we are STILL unable to work with Visual Studio 2015, build the Codeplex base, or otherwise make any progress.
I am writing off CodeContracts as there is obviously no official support for this track.

@caractacus Is there anything wrong with current release candidate? https://github.com/Microsoft/CodeContracts/releases/tag/v1.10.10126.2

Hi @hubuk, the release candidate works in VS2015, and the builds are completing successfully. Thank you, now I'll eat my hat.
However, Visual Studio continues to report v1.8.xxx installed, with an updated to v1.9.xxx available.

@caractacus I am seeing the same issue. I will investigate and submit a separate issue for that.

@hubuk I think the issue about the wrong version number being shown has already been reported as issue #377  https://github.com/Microsoft/CodeContracts/issues/377

The original issue (stack overflow) was fixed with PR #276.
@SergeyTeplyakov I think this issue can be closed.


Abstract out main.rs functions

I think main.rs should only contain the starting scripts, and nothing else. Most of the functions just add clutter to the file.

this is a step towards good idiomatic rust too

This would definitely make the code a lot easier to work on and pull request to.


Add Apple Metal support.

Apple recently announced a new graphics API called "metal" for iOS 8.

Metal essentially removes most of the state validation overhead in mobile drivers making the cost of draw calls dramatically lower.
This is pretty much a must have for iOS devices as it usually results in very dramatic improvements in rendering performance for many real world scenes which are not easily optimized with static or dynamic batching.
Essentially upvoting this as it is such a big deal.

There is initial Metal API support here: https://github.com/warrenm/bgfx/blob/bessemer/src/renderer_mtl.mm

:point_up_2: :+1:

Yet another work-in-progress metal port: https://github.com/attilaz/bgfx/blob/metal/src/renderer_mtl.mm
Here is a screenshot made on iPad mini 2 with metal:

It is far from finished. Performance is bad, I am syncing gpu and cpu every frame.
Performance of 13-stencil is especially bad as there are lot of bgfx view, each adds lot of backbuffer store/load.
Features like: framebuffer, compute shaders and dynamic texture update are still missing. So there are still a lot of TODOs and probably some bugs...

:+1:

Happy to see someone else picking this up. Awesome work so far!

Nice!

Good work! Excited to see this integrated.

Thanks for the positive feedback. Framebuffers and instanced rendering are also supported now.


Package [qtwebengine] Build Failure

Host Environment

OS: Windows 11 22H2
Compiler: MSVC 14.34.31933

To Reproduce
Steps to reproduce the behavior:
./vcpkg install  qt:x64-windows --x-buildtrees-root=D:\
Failure logs
-- Building x64-windows-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:131 (message):
    Command failed: D:/Code/vcpkg/downloads/tools/cmake-3.24.0-windows/cmake-3.24.0-windows-i386/bin/cmake.exe --build . --config Debug --target install -- -v -j21
    Working Directory: D:/temp/qtwebengine/x64-windows-dbg
    See logs for more information:
      D:\temp\qtwebengine\install-x64-windows-dbg-out.log

Call Stack (most recent call first):
  installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_build.cmake:74 (vcpkg_execute_build_process)
  installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_install.cmake:16 (vcpkg_cmake_build)
  ports/qtwebengine/portfile.cmake:111 (vcpkg_cmake_install)
  scripts/ports.cmake:147 (include)

error: building qtwebengine:x64-windows failed with: BUILD_FAILED
error: Please ensure you're using the latest port files with `git pull` and `vcpkg update`.
Then check for known issues at:
    https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+qtwebengine
You can submit a new issue at:
    https://github.com/microsoft/vcpkg/issues/new?template=report-package-build-failure.md&title=[qtwebengine]+Build+error
Include '[qtwebengine] Build error' in your bug report title, the following version information in your bug description, and attach any relevant failure logs from above.
    vcpkg-tool version: 2022-11-10-5fdee72bc1fceca198fb1ab7589837206a8b81ba
    vcpkg-scripts version: 4cb4a5c5d 2022-11-18 (2 days

install-x64-windows-dbg-out.log
Additional context
Same error occurred when trying vcpkg install  qtwebengine[core,default-features,geolocation,spellchecker,webchannel]:x64-windows --x-buildtrees-root=./.

D:\temp\qtwebengine\src\here-src-6-16142a6d06.clean\src\3rdparty\chromium\third_party\skia\src/core/SkShaderCodeDictionary.h(34): error C2039: 'string': is not a member of 'std'

looks like a include is probably missing.

D:\temp\qtwebengine\src\here-src-6-16142a6d06.clean\src\3rdparty\chromium\third_party\skia\src/core/SkShaderCodeDictionary.h(34): error C2039: 'string': is not a member of 'std'

looks like a include is probably missing.

Is that a problem with the source code?

Is that a problem with the source code?

Yes. A simple #include <string> is probably missing in SkShaderCodeDictionary.h
You can add it after you run
vcpkg install qtwebengine[core,default-features,geolocation,spellchecker,webchannel]:x64-windows --x-buildtrees-root=D:\ --editable once and it extracted the archives. (After that CTRL+C to abort building)
Than edit the file (make sure you are not editting in src/*.clean) and than rerun.
vcpkg install qtwebengine[core,default-features,geolocation,spellchecker,webchannel]:x64-windows --x-buildtrees-root=D:\

Fixed by https://github.com/microsoft/vcpkg/pull/27972

Great! Installed successfully after pulling the latest changes. Thank you very much for your hard work.


Allow selecting a single graph node to view along with its neighbors in

We expect to switch to using the data explorer.


预训练模型

大佬，非常感谢您的项目，我学习到了很多，麻烦能不能再提供一些您的预训练模型，上面的百度网盘链接过期了。十分感谢

你好，链接已更新

作者你好，网盘链接过期了

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
N8Brooks, @albertaleksieiev, @momo-AUX1, @sureindia-in, @LivXue, @chuang0310, @ytbryan, @oluizfabio, @erichocean, @andywer, @ahmetbarisdurak, @ZZfive, @colorpeach, @SergeyRyskin, @enestaylan, @yvonwin, @iCGY96, @artony4444, @nuts3745, @1-ashraful-islam


Hypothetical support for VulkanMod?

I would like to know if there are any plans to support VulkanMod? If anything, I have its fork (for now), not the main version. Is there even such a possibility and probability of such support? And in general, is there any way to disable some of the mixins of this mod, or even replace them altogether?

Does VulkanMod support hardware ray tracing?
Portal rendering is much simpler in ray tracing. If VulkanMod supports hardware ray tracing, it may be easy to integrate.
However, if VulkanMod only does rasterization, I think there is no much need to support VulkanMod.


Feature: add parameter exclude_from_purge

Summary of PR changes

Add parameter to allow pass comma separate list for folders/files to keep during the deployment cleaning

PR Requirements

[x] For major, minor, or breaking changes, at least one of the commit messages contains the appropriate +semver: keywords.

See the Incrementing the Version section of the repository's README.md for more details.

[x] The action code does not contain sensitive information.

NOTE: If the repo's workflow could not automatically update the README.md, it should be updated manually with the next version.  For javascript actions, if the repo's workflow could not automatically recompile the action it should also be updated manually as part of the PR.

👍🏽 Please make sure to update the workflow templates that use this action: https://github.com/im-practices/.github/tree/main/workflow-templates

here is the PR for the workflow template updates
https://github.com/im-practices/.github/pull/217

Hello. Can we merge this PR? It will be really helpful for me because it's just the feature that I need to migrate one of my applications from Octopus to Github Actions.


Group navigation prototype

Adds setting and code to put Group shortcuts into the context menu.
https://github.com/rgthree/rgthree-comfy/assets/448862/8b093186-e1f7-4a42-95af-dcd5f36ed0b0

Updated based on the comments from the Bookmarks one. It feels like most users would use one or the other, most of the time.
How do you feel about adding the shortcut functionality to groups, similar to the quick toggles?


Updated Validation

Updated Validation.md for Azure Monitor Insights

thanks for this contribution @shubhammicrosoft1, please let us close this now it is merged.


chore: bdd-spring-1573551775 to 0.0.1

chore: Promote bdd-spring-1573551775 to version 0.0.1

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

Needs approval from an approver in each of these files:

OWNERS

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


How to integrate Simple Sidebar

I think this is Blackrock Digital's bug: How to use side nav bar in angular 6? It is a documentation bug.
The project's README says:

After downloading, simply edit the HTML and CSS files included with the template in your favorite text editor to make changes.

The README never says what changes to make in a prescriptive manner. That is, the README should provide the exact steps a user needs to perform instead of saying "[just] make changes".
For users unfamiliar with the library or project, they need exact steps to perform.

This is just a static HTML template, so how users decided to implement it into various frameworks is up to them.


os-freeradius location folder

hello.
i have installed plugin os-freeradius in a clean opnsense test.
in a gui i have enable a services, create one user and create a client to test.
if i connect in ssh to /usr/local/etc/raddb/ not find in users and in a client my setting edited in gui
where are the location of ufficial data of freeradius?

https://github.com/opnsense/plugins/blob/master/net/freeradius/src/opnsense/service/templates/OPNsense/Freeradius/%2BTARGETS


refactor: merge servers::context into session

I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
This pr mainly merge servers::context into session crate since it's now an independent crate.
Quota and Predicates from servers::context are now temporary removed since we haven't use them for now.
Checklist

[x]  I have written the necessary rustdoc comments.
[x]  I have added the necessary unit tests and integration tests.

Refer to a related PR or issue link (optional)

@MichaelScofield
should we place UserInfo and ConnInfo in QueryContext so that these info can be passed down to lower layer, or change passing struct from QueryContext to Session later if these info is required?
cc @Fengys123

@shuiyisong I think UserInfo and ConnInfo should be placed in our own SessionContext. Should QueryContext too.


BSON.podspec missing for >= v8.0

Would it be possible to re-add the podspec for the latest version?

I've not used cocoapods in years. I'm happy to add it if we can get CI to automatically update cocoapods with new releases

Have any progress been done with this?


feat(view-cli): can use directory path & update project menu

cli

ディレクトリを受け取ることを許容

view

Project利用時、サイドメニューのルートの名前を調整

Codecov Report

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

@@            Coverage Diff            @@
##             master      #15   +/-   ##
=========================================
  Coverage          ?   91.66%
=========================================
  Files             ?       10
  Lines             ?       84
  Branches          ?        5
=========================================
  Hits              ?       77
  Misses            ?        6
  Partials          ?        1

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9f5285f...c50e19d. Read the comment docs.


terminate called after throwing an instance of 'std::out_of_range'

I'm having an issue with bedtools coverage throwing this error:
terminate called after throwing an instance of 'std::out_of_range'
what():  basic_string::substr
Aborted
The command is as follows: bedtools coverage -counts -a in.gtf -b in.bam > out.counts
Its happening with multiple data sources, not limited to a specific bam file. The input files were mapped with bowtie, and can be viewed without a problem in IGV. I can find a little bit of documentation for this error for a different bedtools command, but nothing that addresses this problem.

What version of bedtools? Could you see if the problem exists with the current version (2.28.0)?
Could you share a minimal bam file and gtf that create this problem? Without test data, it will be difficult to track down.

Hi @signor-molevol,
Wondering whether you were able to sort this issue out. I'm facing the same issue pr5ocessing a cellranger output bam file with bedtools/2.26.0.

Also ran into this issue on version v2.26.0:
  what():  vector::_M_range_check: __n (which is 21840194) >= this->size() (which is 2779)
Aborted

Using version v2.29.0 fixed the issue.

I use this script     bamToBed -i test.sort.bam -cigar -bed12 > test.bed     get same error ! on  version 2.23.0


improve printing algorithm performance for many nested callbacks

Suggested implementation, with a caveat of me know being familiar with the code at all :-)
I have completely removed propagateForcedBreaks from the code as it looked to me to be doing nothing while forcing evaluation of everything. Did I miss something?
See #261.
time ./_build/install/default/bin/rescript -print res <test file>
./_build/install/default/bin/rescript -print res   0.65s user 0.03s system 33% cpu 2.009 total

Removing the propagate... function did break a bunch of things :-)

The problem is that the way propagateForceBreaks is implemented forces evaluation of all elements of the document, the handling of the Concat case is a fold_left so no early exit condition. It is called from toString before the findGroupThatFits are evaluated, so it processes elements that will be later discarded.
Can the two cases that propagate... handles be handled in the recursive process function within toString?

Prettier:
let foo = function (x, y, z) {
  foo(x, y, z);
};

let foo = function (x, y, z) {
  foo(x, y, function (x, y, z) {
    foo(x, y, z);
  });
};

let foo = function (x, y, z) {
  foo(x, y, function (x, y, z) {
    foo(x, y, function (x, y, z) {
      foo(x, y, z);
    });
  });
};

let foo = function (x, y, z) {
  foo(x, y, function (x, y, z) {
    foo(x, y, function (x, y, z) {
      foo(x, y, function (x, y, z) {
        foo(x, y, z);
      });
    });
  });
};

let foo1 = (x, y, z) => foo(x, y, z);

let foo2 = (x, y, z) => foo1(x, y, (x, y, z) => foo(x, y, z));

let foo3 = (x, y, z) =>
  foo2(x, y, (x, y, z) => foo1(x, y, (x, y, z) => foo(x, y, z)));

let foo4 = (x, y, z) =>
  foo3(x, y, (x, y, z) =>
    foo2(x, y, (x, y, z) => foo1(x, y, (x, y, z) => foo(x, y, z)))
  );

let foo5 = (x, y, z) =>
  foo4(x, y, (x, y, z) =>
    foo3(x, y, (x, y, z) =>
      foo2(x, y, (x, y, z) => foo1(x, y, (x, y, z) => foo(x, y, z)))
    )
  );

let foo1 = (x, y, z) => {
  foo(x, y, z);
};

let foo2 = (x, y, z) => {
  foo1(x, y, (x, y, z) => {
    foo(x, y, z);
  });
};

let foo3 = (x, y, z) => {
  foo2(x, y, (x, y, z) => {
    foo1(x, y, (x, y, z) => {
      foo(x, y, z);
    });
  });
};

let foo4 = (x, y, z) => {
  foo3(x, y, (x, y, z) => {
    foo2(x, y, (x, y, z) => {
      foo1(x, y, (x, y, z) => {
        foo(x, y, z);
      });
    });
  });
};

Rescript:
let foo1 = (x, y, z) => foo(x, y, z)

let foo2 = (x, y, z) => foo1(x, y, (x, y, z) => foo(x, y, z))

let foo3 = (x, y, z) => foo2(x, y, (x, y, z) => foo1(x, y, (x, y, z) => foo(x, y, z)))

let foo4 = (x, y, z) =>
  foo3(x, y, (x, y, z) => foo2(x, y, (x, y, z) => foo1(x, y, (x, y, z) => foo(x, y, z))))

let foo5 = (x, y, z) =>
  foo4(x, y, (x, y, z) =>
    foo3(x, y, (x, y, z) => foo2(x, y, (x, y, z) => foo1(x, y, (x, y, z) => foo(x, y, z))))
  )

let foo1 = (x, y, z) => {
  foo(x, y, z)
}

let foo2 = (x, y, z) => {
  foo1(x, y, (x, y, z) => {
    foo(x, y, z)
  })
}

let foo3 = (x, y, z) => {
  foo2(x, y, (x, y, z) => {
    foo1(x, y, (x, y, z) => {
      foo(x, y, z)
    })
  })
}

let foo4 = (x, y, z) => {
  foo3(x, y, (x, y, z) => {
    foo2(x, y, (x, y, z) => {
      foo1(x, y, (x, y, z) => {
        foo(x, y, z)
      })
    })
  })
}

On the example
Prettier:
let foo = () =>
  bar((x) =>
    bar((x) =>
      bar((x) =>
        bar((x) =>
          bar((x) =>
            bar((x) =>
              bar((x) =>
                bar((x) => bar((x) => bar((x) => bar((x) => bar((x) => x)))))
              )
            )
          )
        )
      )
    )
  );

ReScript:
let foo = () =>
  bar(x =>
    bar(x =>
      bar(x =>
        bar(x => bar(x => bar(x => bar(x => bar(x => bar(x => bar(x => bar(x => bar(x => x)))))))))
      )
    )
  )

So first observation is: prettier might be using 2 things not 3? Possible.
Second observation: the state exploration does not seem to need to be complete (i.e. 2 or 3, to the power of n). In the following sense:

If the nested one further down breaks, the current one breaks too.

So you don't get e.g. a stack of (breaks, doesn't, breaks, doesn't).
So really it should not be exponential explosion.
In that sense, the semantics of Doc.customLayout would change in that it would not try all the possibilities.
How does that sound?

Sounds good to me. Is that a complex change?

Sounds good to me. Is that a complex change?

Don't know, one needs to try.
I think the printing functions will likely need to pass an extra parameter to know whether it's an immediately-nested case.
But to test the idea, one can just set a global reference in the file. And add a coupe of lines that mutate it.

I think likely only the willBreak and fits functions in res_doc. ml.

This is what I would try.
Permitted sequences have the form 1 1 1 1 1 2 2 2 ~1~.
Suppose there are at most 2 cases. Keep the current level, a number between 1 and 2.
If the current level is 1 then do the following:

Take case1 and try to format the rest at level 1. If it fits, choose case1.
If it does not fit, choose case2 and format the rest at level 2.

If the current level is 2 then:

Choose case2 and format the rest at level 2.

This generalises to level n by always trying case n and switch to case n+1 and level n+1 when it does not fit.
There can be different instances of customLayout with different cases, and different numbers of cases. One can tree them all the same. Start from level 1, and if the current level is, say 4, and the customLayout being considered only has 2 cases,
assume by convention that we're talking about case2.

How does your suggestion solve the performance hit incurred by scanning the whole tree in propagateForceBreaks immediately when toString starts?
Maybe toString can be refactored to incorporate that logic but only for the actual nodes that are chosen?

How does your suggestion solve the performance hit incurred by scanning the whole tree in propagateForceBreaks immediately when toString starts?
Maybe toString can be refactored to incorporate that logic but only for the actual nodes that are chosen?

I had a vague memory that was not an issue. Just checked the code:
    | CustomLayout children ->
      (* When using CustomLayout, we don't want to propagate forced breaks
       * from the children up. By definition it picks the first layout that fits
       * otherwise it takes the last of the list.
       * However we do want to propagate forced breaks in the sublayouts. They
       * might need to be broken. We just don't propagate them any higher here *)
      let _ = walk (Concat children) in
      false

can't see any slowdown there.

But I'm not sure I understood your question.
The main point of the suggestion is: replace exponential traversal with linear traversal.

Take it with a grain of salt, done a quick back-of-the-envelope calculation. But the difference, given exactly the same grammar we have today, is from 3 ^ n to 3 * n.

Walking the children using Content means a fold_left that traverses all variations. Unless I am missing something here, again, not very familiar with this code base. From my previous tests with the lazy evaluated variations, skipping the call in toString make it almost instantaneous.
I now brought back the propagateForceBreaks function and the call to it from toString but without processing CustomLayout variations. Instead, I call it from the process helper in toString after a CustomeLayout variation is chosen. This greatly impacts the overall performance, with only a minimal impact on formatting.
Performance:
./_build/install/default/bin/rescript -print res   0.65s user 0.02s system 46% cpu 1.452 total

Compared to ~22 seconds before lazy evaluation and the propagateForceBreaks changes.
The formatting difference (hence failed tests):
diff --git a/tests/printer/other/expected/nesting.res.txt b/tests/printer/other/expected/nesting.res.txt
index 0cafca836cfc..b25b2d1724cd 100644
--- a/tests/printer/other/expected/nesting.res.txt
+++ b/tests/printer/other/expected/nesting.res.txt
@@ -1,7 +1,5 @@
-let unitsCommands = state.units->Js.Array2.mapi((
-  {unit: targetUnit, coordinates: targetCoordinates},
-  i,
-) => {
+let unitsCommands =
+  state.units->Js.Array2.mapi(({unit: targetUnit, coordinates: targetCoordinates}, i) => {
     // n^2
     let res = []
     state.units->Js.Array2.forEachi((
@@ -50,4 +48,4 @@ let unitsCommands = state.units->Js.Array2.mapi((
       }
     })
     res
-})
+  })

Tried the latest version here.
I've made the example slightly bigger:
% dune exec -- time rescript tst.txt
let foo = () =>
  bar(x =>
    bar(x =>
      bar(x =>
        bar(x =>
          bar(x =>
            bar(x =>
              bar(x =>
                bar(x =>
                  bar(x =>
                    bar(x =>
                      bar(x =>
                        bar(x =>
                          bar(x => bar(x => bar(x => bar(x => bar(x => bar(x => bar(x => x)))))))
                        )
                      )
                    )
                  )
                )
              )
            )
          )
        )
      )
    )
  )
        4.78 real         3.88 user         0.58 sys

With just another 3 more nested callbacks, it uses up nearly all the memory on my machine and takes 57 seconds.
Can't optimise against exponentials, one needs to remove them.

The first issue is that it generates an exponential number of docs, even before trying to format them.

Turns out parsing also takes time on a bigger nested example. So that time should be factored out of the measurement.

The 2 cases produced in printArgumentsWithCallbackInLastPosition alone creates an exponential number of docs.

To summarise my understanding.
There's doc construction and doc printing.
This separation makes it difficult to express interesting logic when several layout cases need to be considered out of which one is chosen.
The only construct supporting logic is Customlayout, which only supports the logic "try this, else try that, else that".
The current PR puts the real logic behind lazy, so that printing can do more work. It has gotten rid of a 3^n explosion but there's still a 2^n explosion left at doc construction time.
Perhaps it's possible to patch this PR to remove the 2^n.
The alternative is to put more logic into the doc so that linearly size, non-lazy, docs can be contructed.

One step forward, in the lazy approach, here: https://github.com/rescript-lang/syntax/pull/590
The output is still not the desired one but it's fast.
Another approach consists of not generating  at all an exponential number of docs (whether hidden behind lazy or not), but only generate those corresponding to the sequences: https://github.com/rescript-lang/syntax/pull/576#issuecomment-1164439620

My thoughts:

We're already seeing a formatting change, is that acceptable?
I don't mind laziness, it is an easy solution to reduce upfront costs of any values we won't really need later on, so can provide value whatever the final process looks like.
The current state of this PR, given we're ok with (1) above, is a significant improvement in runtime. Maybe that's good enough to merge and release so that some benefit will already be made available? (also see the next point)
I admit I have not fully understood the change you're looking to do in fits and willBreak. Adding a level argument to willBreak and process all the way down to calculate in fits and selecting the second CustomLayout case whenever it's higher than 1, did not make any change to the runtime.

WDYT?

By output is still not the desired one, do you mean the final formatting being printed, or timing/code structure?

It's fast but it does not print what we want (e.g. the example motivating this, but also changes to the tests, need to check if they are good or not).
So if it can be made to print what we need , then we can keep it.
More experimentation needed.

Btw this is the output:
let foo = () => bar(x => bar(x => bar(x => bar(x => bar(x => bar(x => bar(x => bar(x => bar(x =>
                    bar(x => bar(x => bar(x => bar(x => bar(x => x)))))
                  )))))))))

It corresponds to what TS does.

I admit I have not fully understood the change you're looking to do in fits and willBreak. Adding a level argument to willBreak and process all the way down to calculate in fits and selecting the second CustomLayout case whenever it's higher than 1, did not make any change to the runtime.

The idea is to pass an extra parameter to all the functions that produce a doc. So all the printing functions.
And: don't print a call-back that breaks, inside another callback printed as non-breaking.
So you literally generate a smaller doc, with fewer cases.


Under Ubuntu 22 system：Error trying to scan for ingame report file

LOG：
@2024-08-20T00:21:54.907Z | IMPORTANT | Manager      | User 'admin' executed: login - []
@2024-08-20T00:21:54.908Z | IMPORTANT | Manager      | User admin logged in - []
@2024-08-20T00:22:24.507Z | IMPORTANT | Manager      | User 'admin' executed: login - []
@2024-08-20T00:22:24.508Z | IMPORTANT | Manager      | User admin logged in - []
@2024-08-20T00:22:26.776Z | INFO      | Monitor      | Server running... - []
@2024-08-20T00:22:27.782Z | IMPORTANT | RCON         | Listening on <IP_ADDRESS>:42814 - []
@2024-08-20T00:22:27.811Z | IMPORTANT | RCON         | Log-In Successful. RCON Connected - []
@2024-08-20T00:22:27.815Z | WARN      | RCON         | Command 'say -1 Big Brother Connected.' (0) failed - []
@2024-08-20T00:22:27.816Z | WARN      | Discord      | Queueing message because client did not start or is not yet ready - [false]
@2024-08-20T00:22:27.821Z | WARN      | Discord      | Queueing message because client did not start or is not yet ready - [false]
@2024-08-20T00:22:51.805Z | WARN      | Discord      | Queueing message because client did not start or is not yet ready - [false]
@2024-08-20T00:22:52.432Z | WARN      | Discord      | Queueing message because client did not start or is not yet ready - [false]
@2024-08-20T00:22:52.903Z | WARN      | Discord      | Queueing message because client did not start or is not yet ready - [false]
@2024-08-20T00:22:54.265Z | WARN      | Discord      | Queueing message because client did not start or is not yet ready - [false]
@2024-08-20T00:22:57.258Z | INFO      | Monitor      | Server running... - []
@2024-08-20T00:23:19.476Z | WARN      | Discord      | Queueing message because client did not start or is not yet ready - [false]
@2024-08-20T00:23:27.300Z | INFO      | Monitor      | Server running... - []
@2024-08-20T00:23:35.946Z | WARN      | Discord      | Queueing message because client did not start or is not yet ready - [false]
@2024-08-20T00:23:37.136Z | WARN      | Discord      | Queueing message because client did not start or is not yet ready - [false]
@2024-08-20T00:23:38.449Z | WARN      | Discord      | Queueing message because client did not start or is not yet ready - [false]
@2024-08-20T00:23:57.320Z | INFO      | Monitor      | Server running... - []
@2024-08-20T00:24:02.136Z | WARN      | Discord      | Queueing message because client did not start or is not yet ready - [false]
@2024-08-20T00:24:02.902Z | WARN      | Discord      | Queueing message because client did not start or is not yet ready - [false]
@2024-08-20T00:24:12.746Z | WARN      | Discord      | Queueing message because client did not start or is not yet ready - [false]
@2024-08-20T00:24:19.540Z | WARN      | Discord      | Queueing message because client did not start or is not yet ready - [false]
@2024-08-20T00:24:27.349Z | INFO      | Monitor      | Server running... - []
@2024-08-20T00:24:57.853Z | INFO      | Monitor      | Server running... - []
@2024-08-20T00:24:58.840Z | ERROR     | IngameReport | Error trying to scan for ingame report file - [{}]
@2024-08-20T00:25:27.904Z | INFO      | Monitor      | Server running... - []
@2024-08-20T00:25:28.859Z | ERROR     | IngameReport | Error trying to scan for ingame report file - [{}]
@2024-08-20T00:25:57.924Z | INFO      | Monitor      | Server running... - []
@2024-08-20T00:25:58.904Z | ERROR     | IngameReport | Error trying to scan for ingame report file - [{}]

I found that the DZSM-TICK.json file is damaged,Every time he is deleted, it can be restored, but after a while, the file becomes damaged again。
code end:
"id": 2996397,
"id2": "",
"position": "3799.474609 190.410690 12985.645508",
"speed": "0.000000 0.000000 0.000000",
"damage": 0.0
}
]
}}

I am having this exact issue sadly. but it is with every additional spawnable type, not just the closing entry.