Exception in server tick loop crash when updating my origins datapack to 1.19

I've been making origins on 1.18 for a while now and when it was time to update them to 1.19 this strange crash started happening
crash-2022-07-30_13.09.45-server.txt
Any info on this crash would be incredibly helpful

I'm getting this crash as well, this only happened once I updated to 1.19.1.

Same issue
crash-2022-07-31_21.13.31-server.txt
was loading custom datapacks for origins mod

Origins is not compatible with 1.19.1 - the file on CF is not marked as compatible with 1.19.1.
The problem is a changed method in the command system, making execute_command actions cause this crash.

You may want to update the listing on Modrinth then, as it is listed as 1.19.1-compatible on Modrinth (which is why I assumed it would work).

You may want to update the listing on Modrinth then, as it is listed as 1.19.1-compatible on Modrinth (which is why I assumed it would work).

It does not. Having the same issue here.

A comment on Curse leads me to wonder whether this is caused specifically by selected origins that alter player size. It would certainly match up with my own experience getting this crash, as all of the origins I'd personally tried from Bucolic Origins do indeed have size alterations, but I have yet to test more extensively with origins that don't do anything with the player's size
Could anyone else who has had this issue perhaps clarify what origin datapack/addon they are using/getting the crash with, as well as whether the origin selected that causes the crash alters player size in any way?
Quoting the comment itself for ease of access:

playing on 1.19.2 works fine but any origin that changes size causes this error, causing any server (singleplayer or dedicated) to crash, yes i have pehkui

Description: Exception in server tick loopDescription: Exception in server tick loop
java.lang.NoSuchMethodError: 'int net.minecraft.class_2170.method_9249(net.minecraft.class_2168, java.lang.String)' at Not Enough Crashes deobfuscated stack trace.(1.19.2+build.8) at io.github.apace100.apoli.power.factory.action.EntityActions.lambda$register$15(EntityActions.java:235) at io.github.apace100.apoli.power.factory.action.ActionFactory$Instance.accept(ActionFactory.java:41) at io.github.apace100.origins.power.OriginsCallbackPower.onChosen(OriginsCallbackPower.java:24) at io.github.apace100.origins.component.OriginComponent.lambda$onChosen$0(OriginComponent.java:49) at java.lang.Iterable.forEach(Iterable.java:75) at io.github.apace100.origins.component.OriginComponent.onChosen(OriginComponent.java:49) at io.github.apace100.origins.networking.ModPacketsC2S.lambda$chooseOrigin$0(ModPacketsC2S.java:50) at net.minecraft.server.ServerTask.run(ServerTask:18) at net.minecraft.util.thread.ThreadExecutor.executeTask(ThreadExecutor:157) at net.minecraft.util.thread.ReentrantThreadExecutor.executeTask(ReentrantThreadExecutor:23) at net.minecraft.server.MinecraftServer.executeTask(MinecraftServer:776) at net.minecraft.server.MinecraftServer.executeTask(MinecraftServer:159) at net.minecraft.util.thread.ThreadExecutor.runTask(ThreadExecutor:131) at net.minecraft.server.MinecraftServer.runOneTask(MinecraftServer:758) at net.minecraft.server.MinecraftServer.runTask(MinecraftServer:752) at net.minecraft.util.thread.ThreadExecutor.runTasks(ThreadExecutor:140) at net.minecraft.server.MinecraftServer.runTasksTillTickEnd(MinecraftServer:737) at net.minecraft.server.MinecraftServer.runServer(MinecraftServer:669) at net.minecraft.server.MinecraftServer.method_29739(MinecraftServer:257) at java.lang.Thread.run(Thread.java:833)

A bit late, but this should now be fixed in Origins 1.7.0


Laravel integration

Hi there,
Is this package working with Laravel?

What package?

I am speaking about this omnipay-paratika. I have test details from HalkBank for Intesa 3D secure payment and im
trying to find the way to implement in laravel


provide pseudo algorithm in README.md

add pseudo algorithm

Thanks for contributing Saba!
Generally, I think pseudo code can be useful, but in this case, the actual implementation is so small, that it ~matches the pseudo code.
Maybe we could do is this. Instead of writing the pseudo code, we could write something along the lines of:
"To study the algorithm, start with matchVariable querySingle, and actualize."


Update readerKWPSlow.ino

Updated to add altSerial.  No idea how it works with Serial1, did not compile.

Updated to add altSerial. No idea how it works with Serial1, did not compile.

Heh, all reader, readerKWP and this one are made for a Teensy 3.0, it'ss an arduino compatible board that has 3 serial ports >_<
I'm not sure if we should update this, or keep it as is to be in line with the other reader examples. Alternatively, we could rename it readerKWPSlow_softserial, to follow the convention of this.
I'd rather do that, could you commit these changes as a new example called reader_KWPSlow_softserial?

Nah, I wont worry about it.  Makes sense what you said.  I might go to a Teensy too because softwareSerial and altSoftwareSerial have been giving me problems.


unknown field "artifactRepository" in io.k8s.api.core.v1.ConfigMap

Is this a BUG REPORT or FEATURE REQUEST?:
BUG REPORT
What happened:
when add cepth to argo,display error message unknown field "artifactRepository" in io.k8s.api.core.v1.ConfigMap. and the method to add cepth to argo as below:
kubectl edit configmap workflow-controller-configmap -n ci
artifactRepository:
s3:
bucket: argo
keyPrefix: prefix/in/bucket #optional
endpoint: ceph-s3-front.cicd:7480
insecure: true
accessKeySecret:
name: FUF5IS1XM27U81GT1J6B
key: iJMRLzEqurCBthP7Tqeddd94eibvefaRqhfBTOdw
What you expected to happen:
i expected edit configmap success.
How to reproduce it (as minimally and precisely as possible):
Environment:

Argo version:

[root@node128 nexus]# argo version
argo: v2.2.0
  BuildDate: 2018-08-30T08:52:05Z
  GitCommit: af636ddd8455660f307d835814d3112b90815dfd
  GitTreeState: clean
  GitTag: v2.2.0
  GoVersion: go1.10.3
  Compiler: gc
  Platform: linux/amd64

Kubernetes version :

[root@node128 nexus]# kubectl version -o yaml
clientVersion:
  buildDate: 2018-08-07T23:17:28Z
  compiler: gc
  gitCommit: bb9ffb1654d4a729bb4cec18ff088eacc153c239
  gitTreeState: clean
  gitVersion: v1.11.2
  goVersion: go1.10.3
  major: "1"
  minor: "11"
  platform: linux/amd64
serverVersion:
  buildDate: 2018-09-09T17:53:03Z
  compiler: gc
  gitCommit: a4529464e4629c21224b3d52edfe0ea91b072862
  gitTreeState: clean
  gitVersion: v1.11.3
  goVersion: go1.10.3
  major: "1"
  minor: "11"
  platform: linux/amd64

Other debugging information (if applicable):
- workflow-controller logs:

[root@node128 nexus]# kubectl logs -n ci $(kubectl get pods -l app=workflow-controller -n ci -o name)
time="2018-10-09T10:57:43Z" level=info msg="workflow controller configuration from workflow-controller-configmap:\nnamespace: ci\n"
time="2018-10-09T10:57:43Z" level=info msg="Workflow Controller (version: v2.2.0) starting"
time="2018-10-09T10:57:43Z" level=info msg="Workers: workflow: 8, pod: 8"
time="2018-10-09T10:57:43Z" level=info msg="Watch Workflow controller config map updates"
time="2018-10-09T10:57:43Z" level=info msg="Starting workflow TTL controller (resync 20m0s)"
time="2018-10-09T10:57:43Z" level=info msg="Detected ConfigMap update. Updating the controller config."
time="2018-10-09T10:57:43Z" level=info msg="workflow controller configuration from workflow-controller-configmap:\nnamespace: ci\n"
time="2018-10-09T10:57:43Z" level=info msg="Started workflow TTL worker"
time="2018-10-09T11:02:43Z" level=info msg="Alloc=3030 TotalAlloc=10794 Sys=10342 NumGC=7 Goroutines=62"
W1009 11:03:15.867684       1 reflector.go:341] github.com/argoproj/argo/workflow/controller/config.go:157: watch of *v1.ConfigMap ended with: too old resource version: 14221 (14494)
time="2018-10-09T11:07:43Z" level=info msg="Alloc=3039 TotalAlloc=10945 Sys=10342 NumGC=9 Goroutines=62"
W1009 11:10:50.884878       1 reflector.go:341] github.com/argoproj/argo/workflow/controller/config.go:157: watch of *v1.ConfigMap ended with: too old resource version: 14895 (15401)
time="2018-10-09T11:12:43Z" level=info msg="Alloc=3040 TotalAlloc=11031 Sys=10342 NumGC=12 Goroutines=62"
time="2018-10-09T11:17:43Z" level=info msg="Alloc=3060 TotalAlloc=11087 Sys=10342 NumGC=14 Goroutines=62"
W1009 11:19:43.902158       1 reflector.go:341] github.com/argoproj/argo/workflow/controller/config.go:157: watch of *v1.ConfigMap ended with: too old resource version: 15799 (16462)
time="2018-10-09T11:22:43Z" level=info msg="Alloc=3079 TotalAlloc=11208 Sys=10342 NumGC=17 Goroutines=62"

The artifactRepository field supposed to be specified inside config field. E.g.
apiVersion: v1
data:
  config: |
    artifactRepository:
      ...

Error message is correct, ConfigMap does not have artifactRepository field


Ollie: Watch geanimeds3(?:@gmail.com)?

Ollie requests the watch of the watch_keyword geanimeds3(?:@gmail\.com)?. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

geanimeds3(?:@gmail\.com)? has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Spevacus in Charcoal HQ


[HUDI-6645] Relax the restriction for Spark MDT rollback

Change Logs
Describe context and summary for this change. Highlight if any code was copied.
none
Impact
Describe any public API or user-facing feature change or any performance impact.
Relax the restriction for Spark MDT rollback
Risk level (write none, low medium or high below)
If medium or high, explain what verification was done to mitigate the risks.
none
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

cc @danny0405  have a review plz


Require numpy 1 due to incompatibility with Streamlit

Update bokeh version to work with latest numpy
Closes #334

I actually meant to use >= not ==, let me fix

Ah, there was a reason for that specific version. This could be a problem
StreamlitAPIException: Streamlit only supports Bokeh version 2.4.3, but you have version 3.5.0 installed. Please run pip install --force-reinstall --no-deps bokeh==2.4.3 to install the correct version.

It's failing on
    assert all(c in EXPECTED_FIELDS for c in df.columns.tolist())

On a quick look through the perflog the fields look ok. Maybe something has changed in the spac spec dict?

If it helps, I think the change causing this may have taken place 28 - 29 May. Using the line plot PR as reference again, all tests were passing on the 28th, but when I pushed some inconsequential changes on the 29th this specific test started failing.

The field version has changed to reframe version (I assume in a new version of ReFrame). I'm running 4.6.2. I updated it in the test and now it passes. I noticed we don't have whitespace in other field names. Is that going to cause any issues @pineapple-cat?

Of course, I forgot about ReFrame field name updates; thank you for finding the issue.

This change seems to have happened in ReFrame 4.6.1. Are we happy to update the requirement to that?

I think so.  Better to be explicit about the actually supported versions.


Find IDocumentProvider using a more-laborious process

Type.GetType(string) requires an assembly-qualified name and we don't know the assembly

nit:

reflect recent change to dotnet-getdocument's Resources.resx file in its designer file

Would like to get this into the feature branch soon 😃

Changed base now that I've merged feature/client.code.generation into release/2.2

Added fix for #8593
@rynowak or @pranavkm this is what we've been discussing offline. Please have a look.

:up::date:
With one of the fixes discussed offline w.r.t. Startup.Configure(...), everything is again working end-to-end. Not including anything more here until that discussion completes.

:up::date: @rynowak do you want to take one more look?


Release for ES 7.9.3

Release notes: https://www.elastic.co/guide/en/elasticsearch/reference/7.9/release-notes-7.9.3.html

Version <IP_ADDRESS> has been released today.


Fix typos: self -> this

Thank you! But wouldn't this point to Color there and not the global object?
Perhaps typeof CSS !== "undefined" might be better?

In that case, maybe so. After I found the first self, I just did a find and replace for the other, I honestly didn't look at the second case too close 😅.

Yes, this fixes the issue with Node, but it also completely changes the meaning of those loc. It's just that Node doesn't need those loc. 😄

Looking closer, no one ever uses this.Proxy either. I'm not entirely sure what is being checked there either.

On the client-side, self is just another way to say window. The former exists in Web workers too, but not the latter, so I've gotten into the habit to prefer the former.
Checking for self.Proxy just checks for Proxy support :)

Haha, well I dabble in some web stuff, but clearly, I'm not a web dev, so this was a little new to me. I made a very big assumption which is very much incorrect 😆.

I've adjusted the fix based on your statements. If I am still off, feel free to let me know. I also won't feel bad if you find it easier to just fix it directly sidestepping this pull 😄.

Thank you for the fast turnaround! You need === instead of !== for actual equivalence with the previous code, now you're checking for the opposite :)

🤦 Third times a charm!

Merged, thanks!


type="module" on script tag results in "Cannot read property 'webpackHotUpdate' of undefined" when hot reloading is enabled.

Do you want to request a feature or report a bug?
Bug
What is the current behavior?
The compiled bundle fails to execute with the error Uncaught TypeError: Cannot read property 'webpackHotUpdate' of undefined when using type="module" on script tags.
If the current behavior is a bug, please provide the steps to reproduce.
https://github.com/RDGthree/webpackHotUpdate-bug-example
Clone this repo, npm install, and npm run start. Open index.html in a browser and check the console. I used webpack-dev-server, but the issue relates to Webpack's core.
I'm pretty sure the issue relates to this no longer referring to window with type="module".
What is the expected behavior?
When using type="module" on script tags, Hot Module Reloading works the same as with type="text/javascript", or has a helpful error.
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.

Operating System: MacOS 10.12
Node Version: 8.4.0
NPM Version: 5.3.0
webpack Version: 3.6.0
webpack-dev-server Version: 2.9.1

have the problom of hotupdate too.  It's wired that webpack didn't inject webpackHotUpdate in some case. Especially debug & run different environment.

I don't think so. As far as I can see, this is exclusively related to the new module script standard for browsers. Everything is working as expected, other than this being undefined.

Same problem here, I have almost the same configuration except for webpack version (3.7) and I'm using yarn, but of course I don't think this is related to system configuration.


In-memory engine: panic in cross check task

Bug Report
Panic occured in cross check task (now, audit task).
Error messages before panic:
[2024/06/27 09:48:58.734 +00:00] [INFO] [apply.rs:1857] ["handle put"] [index=13171] [key=7480000000000000FF1A5F728000000000FF0307E80000000000FA] [start_ts=450751820106825740] [cf="\"lock\""] [region_id=109363] [thread_id=116]
[2024/06/27 09:48:59.594 +00:00] [INFO] [apply.rs:1857] ["handle put"] [index=13194] [key=7480000000000000FF1A5F728000000000FF0307E80000000000FAF9BE9B9B66ABFFC8] [start_ts=450751820106825740] [cf="\"write\""] [region_id=109363] [thread_id=116]
[2024/06/27 09:48:59.594 +00:00] [INFO] [apply.rs:1923] ["handle delete"] [index=13194] [key=7480000000000000FF1A5F728000000000FF0307E80000000000FA] [start_ts=450751820106825740] [cf="\"lock\""] [region_id=109363] [thread_id=116]
[2024/06/27 09:48:59.661 +00:00] [INFO] [engine.rs:506] ["Range to load"] [Pending=11] [Cached=66] [range="CacheRange { tag: \"[region_id=109363]\", range_start: 7A7480000000000000FF1A5F728000000000FF013DBA0000000000FA, range_end: 7A7480000000000000FF9400000000000000F8 }"] [Tag="[region_id=109363]"] [thread_id=116]
[2024/06/27 09:49:42.248 +00:00] [INFO] [background.rs:1152] ["Loading range"] [range="CacheRange { tag: \"[region_id=109363]\", range_start: 7A7480000000000000FF1A5F728000000000FF013DBA0000000000FA, range_end: 7A7480000000000000FF9400000000000000F8 }"] [thread_id=28]
[2024/06/27 09:49:42.321 +00:00] [INFO] [background.rs:1238] ["write to memory in load"] [cf="\"lock\""] [key=7A<PHONE_NUMBER>000000FF1A5F728000000000FF0307E80000000000FA016E0E8B0A000000] [thread_id=28]
[2024/06/27 09:50:59.551 +00:00] [ERROR] [background.rs:1053] ["seek_to_first result not equal"] [cf="\"lock\""] [seqno=180785903] [cache_key=7A7480000000000000FF1A5F728000000000FF0307E80000000000FA] [upper=7A7480000000000000FF9400000000000000F8] [lower=7A7480000000000000FF1A5F728000000000FF013DBA0000000000FA] [thread_id=32]

The message shows the rocksdb snapshot lost the last handle delete, which may mean that there's unbuffered writes at the time of calling prepare_for_apply.

Since the first report, we've done several refactors, and the issue hasn't been reproduced for months.

Cc #17241


Fix bug where publish fails with no tests

There is a bug in jest where using passWithNoTests in the jest config JSON does not take effect. See https://github.com/facebook/jest/issues/8896

/assign @vojtechszocs

/lgtm


ModSecurity module doesn't follow AddType when AddHandler is missing

According to http://httpd.apache.org/docs/current/mod/mod_mime.html#addtype Apache2.x Official documentation it is claimed that :

If no handler is explicitly set for a request, the specified content type will also be used as the handler name.
When explicit directives such as SetHandler or AddHandler do not apply to the current request, the internal handler name normally set by those directives is instead set to the content type specified by this directive.
This is a historical behavior that may be used by some third-party modules (such as mod_php) for taking responsibility for the matching request.

In a configuration where apache is serving .php files using  AddType application/x-httpd-php .php normally, this "Note" above is being practically used.
But it seems that ModSecurity internally does not check for AddType, if AddHandler is missing, resulting on .php source code exposure.

Is this still an issue?
If so, I'm afraid you're going to have to indulge me and provide a more detailed explanation of the issue.
For example, I'm not at all clear on what tangible problem is being alleged here.
Under what conditions will ModSecurity act in a way that is not in keeping with reasonable expectations?
How is that non-reasonable manner manifest to a ModSecurity user?


dEQP-VK.api.object_management.alloc_callback_fail.instance failed

Install the loader <IP_ADDRESS> or later.
Run the VulknaCTS with "./deqp-vk -n dEQP-VK.api.object_management.alloc_callback_fail.instance"
Failed.
It's not seen with loader 1.0.37.
There are 12 memory blocks leaked in the loader. Following is one of the callstack
#1  0x000000000153a0b4 in vk::AllocationCallbackRecorder::allocate (this=0x7fffffffd5c0, size=6, alignment=8, allocationScope=vk::VK_SYSTEM_ALLOCATION_SCOPE_COMMAND)
at /jacob/auto_test/tests/vulkancts_internal/external/vulkancts/framework/vulkan/vkAllocationCallbackUtil.cpp:318
#2  0x000000000153965b in vk::allocationCallback (pUserData=0x7fffffffd5c0, size=6, alignment=8, allocationScope=vk::VK_SYSTEM_ALLOCATION_SCOPE_COMMAND)
at /jacob/auto_test/tests/vulkancts_internal/external/vulkancts/framework/vulkan/vkAllocationCallbackUtil.cpp:90
#3  0x00007ffff5b58114 in loader_instance_heap_alloc (instance=0x4407340, size=6, alloc_scope=VK_SYSTEM_ALLOCATION_SCOPE_COMMAND)
at /root/VulkanSamples/loader/loader.c:221
#4  0x00007ffff5b58293 in loader_instance_tls_heap_alloc (size=6) at /root/VulkanSamples/loader/loader.c:266
#5  0x00007ffff5b73483 in parse_string (item=0x4161570,
str=0x7fffffffcece ""1.0.0",\n    "layer" : {\n        "name": "VK_LAYER_GOOGLE_threading",\n        "type": "GLOBAL",\n        "library_path": "./libVkLayer_threading.so",\n        "api_version": "1.0.41",\n        "implement"...) at /root/VulkanSamples/loader/cJSON.c:261
#6  0x00007ffff5b73e3c in parse_value (item=0x4161570,
value=0x7fffffffcece ""1.0.0",\n    "layer" : {\n        "name": "VK_LAYER_GOOGLE_threading",\n        "type": "GLOBAL",\n        "library_path": "./libVkLayer_threading.so",\n        "api_version": "1.0.41",\n        "implement"...) at /root/VulkanSamples/loader/cJSON.c:503
#7  0x00007ffff5b748e0 in parse_object (item=0x4181e30,
value=0x7fffffffcecc ": "1.0.0",\n    "layer" : {\n        "name": "VK_LAYER_GOOGLE_threading",\n        "type": "GLOBAL",\n        "library_path": "./libVkLayer_threading.so",\n        "api_version": "1.0.41",\n        "impleme"...) at /root/VulkanSamples/loader/cJSON.c:735
#8  0x00007ffff5b73eb5 in parse_value (item=0x4181e30,
value=0x7fffffffceb0 "{\n    "file_format_version" : "1.0.0",\n    "layer" : {\n        "name": "VK_LAYER_GOOGLE_threading",\n        "type": "GLOBAL",\n        "library_path": "./libVkLayer_threading.so",\n        "api_version""...) at /root/VulkanSamples/loader/cJSON.c:512
#9  0x00007ffff5b73bf5 in cJSON_ParseWithOpts (
value=0x7fffffffceb0 "{\n    "file_format_version" : "1.0.0",\n    "layer" : {\n        "name": "VK_LAYER_GOOGLE_threading",\n        "type": "GLOBAL",\n        "library_path": "./libVkLayer_threading.so",\n        "api_version""..., return_parse_end=0x0, require_null_terminated=0)
at /root/VulkanSamples/loader/cJSON.c:452
#10 0x00007ffff5b73c8c in cJSON_Parse (
value=0x7fffffffceb0 "{\n    "file_format_version" : "1.0.0",\n    "layer" : {\n        "name": "VK_LAYER_GOOGLE_threading",\n        "type": "GLOBAL",\n        "library_path": "./libVkLayer_threading.so",\n        "api_version""...) at /root/VulkanSamples/loader/cJSON.c:472
#11 0x00007ffff5b5c455 in loader_get_json (inst=0x4407340, filename=0x441b9f0 "/root/VulkanSamples/dbuild_42/layers/VkLayer_threading.json", json=0x7fffffffd130)
at /root/VulkanSamples/loader/loader.c:1910
#12 0x00007ffff5b60b26 in loader_layer_scan (inst=0x4407340, instance_layers=0x440b220) at /root/VulkanSamples/loader/loader.c:3263
#13 0x00007ffff5b6984f in vkCreateInstance (pCreateInfo=0x7fffffffd380, pAllocator=0x7fffffffd5c8, pInstance=0x7fffffffd278)
at /root/VulkanSamples/loader/trampoline.c:307
#14 0x0000000001507f57 in vk::PlatformDriver::createInstance (this=0x27b98c8, pCreateInfo=0x7fffffffd380, pAllocator=0x7fffffffd5c8, pInstance=0x7fffffffd278)
at /jacob/auto_test/tests/vulkancts_internal/external/vulkancts/framework/vulkan/vkPlatformDriverImpl.inl:7
#15 0x00000000014ff920 in vk::createInstance (vk=..., pCreateInfo=0x7fffffffd380, pAllocator=0x7fffffffd5c8)
at /jacob/auto_test/tests/vulkancts_internal/external/vulkancts/framework/vulkan/vkRefUtilImpl.inl:132
---Type  to continue, or q  to quit---
#16 0x0000000000ca7904 in vkt::api::(anonymous namespace)::Instance::create (env=...)
at /jacob/auto_test/tests/vulkancts_internal/external/vulkancts/modules/vulkan/api/vktApiObjectManagementTests.cpp:466
#17 0x0000000000ce3256 in vkt::api::(anonymous namespace)::allocCallbackFailTest<vkt::api::(anonymous namespace)::Instance> (context=..., params=...)
at /jacob/auto_test/tests/vulkancts_internal/external/vulkancts/modules/vulkan/api/vktApiObjectManagementTests.cpp:2355
#18 0x0000000000d1337b in vkt::FunctionInstance1<vkt::api::(anonymous namespace)::Instance::Parameters>::iterate (this=0x40bd7b0)
at /jacob/auto_test/tests/vulkancts_internal/external/vulkancts/modules/vulkan/api/../vktTestCaseUtil.hpp:97
#19 0x0000000000c16abf in vkt::TestCaseExecutor::iterate (this=0x27b93c0)
at /jacob/auto_test/tests/vulkancts_internal/external/vulkancts/modules/vulkan/vktTestPackage.cpp:294
#20 0x0000000001752e94 in tcu::TestSessionExecutor::iterateTestCase (this=0x27bb250, testCase=0x2c8aad0)
at /jacob/auto_test/tests/vulkancts_internal/framework/common/tcuTestSessionExecutor.cpp:270
#21 0x000000000175234b in tcu::TestSessionExecutor::iterate (this=0x27bb250) at /jacob/auto_test/tests/vulkancts_internal/framework/common/tcuTestSessionExecutor.cpp:133
#22 0x000000000172aaf3 in tcu::App::iterate (this=0x27b8a40) at /jacob/auto_test/tests/vulkancts_internal/framework/common/tcuApp.cpp:172
#23 0x0000000000c10850 in main (argc=3, argv=0x7fffffffe328) at /jacob/auto_test/tests/vulkancts_internal/framework/platform/tcuMain.cpp:55

I just ran with 1.0.2 CTS, and the latest version of master and I see no problem.  Although you're using a really old version of the loader, potentially.
I ran it with and without validation enabled.  I ran on Fedora Core 25 with Intel Skylake using the Mesa Vulkan driver.  I believe we have another test machine which runs automatically which shows no error as well, and that's likely Nvidia.
Two things I would try:

Update to the <IP_ADDRESS> SDK/Loader
If that fails, can you give me more details on your setup?  Perhaps even running VIA and attaching the HTML output?

I just looked, and the 1.0.41 layer versions seen in your callstack indicate you haven't updated your tree since at least Feb 28th (when we updated to 1.0.42).

I fixed an issue which only appeared on Windows with commit 61ff81af2702610eb1121f3a392f4f73d79a3b28.

Hi Mark,
Sorry for late reply. what does "haven't updated your tree" mean? I just downloaded the loader from lunarg. Do you mean there is no this issue with the latest master?

The layers reported themselves as 1.0.41.  Since we didn't build a 1.0.41 SDK (just a 1.0.42 SDK), I thought you had built the layers yourself out of the tree.
However, the fixes are in the Git branch here in Github, so if you clone the tree and build, you should get the fix.

Thanks Mark. It's fixed with <IP_ADDRESS>.

Sorry, it's fixed with <IP_ADDRESS>.


✨ Ability to drag and drop files and folders in the project navigator

Describe the solution you'd like
We need the ability to drag and drop files and folders in the project navigator to relocate them to a new desired location.
Additional context
https://user-images.githubusercontent.com/806104/214147155-af13d341-588d-43d8-bca7-fc73d3e448e3.mov

I can try looking into this

@neilZon Thanks, I assigned this to you for now 👍

Before you get two far I wonder if we follow Xcode in how the drop target is visually represented.
In Xcode, custom order matters. You can rearrange files and folders in a very custom order so the drop target is represented by a small circle attached to a line in between the items where the target is.
In CodeEdit and most other editors, files and folders are arranged alphabetically, and so custom order doesn’t matter. Therefore, I think the drop target should be represented more like it is in Finder in list view.
Do you have any thoughts around this?

I like the way that finder implements drag and drop which is what I'm gonna try to aim for since it feels cleaner even when compared to VSCode since finder only highlights the drop of the parent vs VSCode that highlights the whole directory.
Personally, I don't really care for the fact that XCode allows for custom orders of files but I can see how that could be something that some people want but I'm not sure if this should be offered as an extension or an optional setting if this were to be implemented

One thing to note is: In Xcode it only works for projects but not for Swift Packages since the order is saved in project.pbxproj inside the .xcodeproj package.

Should I support multiple file drag and drop in this issue? What about dragging files from outside of CodeEdit to within like from the desktop or browser?

If you feel comfortable doing all of that, then sure. If not capture it in an issue and we can tackle it later.

In Xcode, custom order matters. You can rearrange files and folders in a very custom order so the drop target is represented by a small circle attached to a line in between the items where the target is.
In CodeEdit and most other editors, files and folders are arranged alphabetically, and so custom order doesn’t matter. Therefore, I think the drop target should be represented more like it is in Finder in list view.

Yeah let's not implement the Xcode files rearrange thing. It will be very confusing if you have never used Xcode. Perhaps in the future it can be a setting.

Should I support multiple file drag and drop in this issue? What about dragging files from outside of CodeEdit to within like from the desktop or browser?

Let's not make the scope to big, we can create new issues and PR's for these kinds of things.

I think for now I'll just do the single file or folder drag and drop just to keep the scope small

@matthijseikelenboom smaller scope = smaller PRs so I agree, good idea. Thanks again @neilZon!


Implement searching documentation files

There is a search bar in documentation pages. This branch will try to implement it.

Note that this PR will merge to documentation and not to main since in main we don't have much documentation to search yet.
If you feel like doing so, you can transfer this to server (since this is executed on the server, after all), and/or reimplement/modify it to make it more efficient/...


Maximum 16 users, after that black screen.

Hello, since 2 or 3 updates i have this strange issue.
I use my PC for 25 users with RDPWrap, but it seems to be a limit.
Once 16 users logged in, no one else can log on. It shows a black screen and a message that the remote sesion has ended.
If i disconect one user from task manager, then it can log on, but again only till 16.
Also, if i manualy log on the user on the PC, for example 3 users that are not connected, after that those 3 users can connect, and now i have 19 connected, and so on..

Why don't u use Windows Server? It's strange to try home system for your purpose.

Any progress on this? Since 10.0.18362.267, this happens to me too. Only 16 RDP users.

Дуплицате оф https://github.com/stascorp/rdpwrap/issues/512


Images not shown first time after getting permission iOS 14

I'm using this library on iOS 14 and when I install my app the first time and allow permission to access all photos then there is no image in the picker.
after cancel when again press the upload button and I got all pictures.
this is my code to present the image picker.
let imagePicker = ImagePickerController()         imagePicker.settings.fetch.assets.supportedMediaTypes = [.image]         imagePicker.settings.selection.max = 5         imagePicker.settings.theme.selectionStyle = .numbered         imagePicker.settings.selection.unselectOnReachingMax = false         let options = imagePicker.settings.fetch.album.options         imagePicker.settings.fetch.album.fetchResults = [             PHAssetCollection.fetchAssetCollections(with: .smartAlbum, subtype: .smartAlbumUserLibrary, options: options),             PHAssetCollection.fetchAssetCollections(with: .album, subtype: .albumRegular, options: options),         ]

I am facing the same problem, did you find a solution?

Does it work if you don't set a custom fetch result?

I wrote a UIViewControllerRepresentable to use the picker in SwiftUI, am I missing something here?
struct ImagePicker: UIViewControllerRepresentable {
    @Binding var assets: [PHAsset]?

    func makeCoordinator() -> ImagePicker.Coordinator {
        return Coordinator(self)
    }

    func makeUIViewController(context: Context) -> ImagePickerController {
        let picker = ImagePickerController()
        picker.imagePickerDelegate = context.coordinator
        return picker
    }

    func updateUIViewController(_ uiViewController: ImagePickerController, context: Context) {

    }
}

extension ImagePicker {
    class Coordinator: NSObject, ImagePickerControllerDelegate {
        var parent: ImagePicker
        init(_ parent: ImagePicker) {
            self.parent = parent
            self.parent.assets = []
        }

        func imagePicker(_ imagePicker: ImagePickerController, didSelectAsset asset: PHAsset) {
            print("didSelectAsset")
        }

        func imagePicker(_ imagePicker: ImagePickerController, didDeselectAsset asset: PHAsset) {
            print("didDeselectAsset")

        }

        func imagePicker(_ imagePicker: ImagePickerController, didFinishWithAssets assets: [PHAsset]) {
            print("didFinishWithAssets assets \(assets.count)")
            parent.assets = assets

        }

        func imagePicker(_ imagePicker: ImagePickerController, didCancelWithAssets assets: [PHAsset]) {
            print("didCancelWithAssets")

        }

        func imagePicker(_ imagePicker: ImagePickerController, didReachSelectionLimit count: Int) {
            print("didReachSelectionLimit")

        }
    }
}

Same problem faced here and I have not used any custom fetch results

Also getting this same problem

func photoAuthorization(authorized: @escaping () -> Void, unauthorized: @escaping () -> Void) {         PHPhotoLibrary.requestAuthorization { (status) in             switch status {             case .authorized:                 DispatchQueue.main.async(execute: authorized)             default:                 DispatchQueue.main.async(execute: unauthorized)             }         }     }
and user thsi as
UIHelper.sharedInstance.photoAuthorization {                 self.setupImagePicker()             } unauthorized: {                 SVProgressHUD.dismiss()                 self.showAlertViewSettings()             }

I solved this issue on my application by wrapping the function that presents the ImagePickerController in a wrapper function that asks the user for authorization prior to presenting the picker:
`
PHPhotoLibrary.requestAuthorization { (auth_status) in
if auth_status== .denied || auth_status== .notDetermined {
    /* User denied permission or left the authorization in an undetermined state
    Enter code here to handle this event or leave it blank if you don't want to do anything
    */
} else {
    /*
    auth_status is either authorized, limited, or restricted. Call wrapper function
    */
    self.FunctionThatPresentsImagePickerController()
}

}
`

The issue was because of the authorisation status

I solved this issue on my application by wrapping the function that presents the ImagePickerController in a wrapper function that asks the user for authorization prior to presenting the picker:
PHPhotoLibrary.requestAuthorization { (auth_status) in

    if auth_status == .denied || auth_status == .notDetermined {
        /* User denied permission or left the authorization in an undetermined state
        Enter code here to handle this event or leave it blank if you don't want to do anything
        */
    } else {
        /*
        auth_status is either authorized, limited, or restricted. Call wrapper function
        */
        self.FunctionThatPresentsImagePickerController()
    }

}

However in iOS 14 when the PHAuthorizationStatus is limited the prompt will never re-appear, leaving users to only select the initial images they selected and nothing else. Upon further investigation I found that this is intended behavior on Apple's end- they only prompt to ask you to select more images once per app session. Odd design but that's how it works right now.
This solution is an anti-pattern and only really serves as a temporary solution until a fix is made.

The was the solution for my case as well. However instead of checking the status I manually asked for premission using the PHPhotoLibrary.requestAuthorization and in the callback I presented the ImagePicker using the UIViewController's present method instead of presentImagePicker() provided by the library.
EG:
PHPhotoLibrary.requestAuthorization { (status) in             switch status {             case .authorized:                   self.present(imagePicker, animated: true)             case .denied:                 // Handle the denied logic             default:                 break             }         }


Fix typecheck of input args

If the value of an input is undefined, do not remove it from the schema

Undefined means the parameter is set (to be slot-filled) so it should be removed from the schema, otherwise you can parameter pass into it, which is wrong. What is this solving? Do you have a test case?

In the make rule GUI, I need to get the input arguments.

Why do you need to go through typecheck in make rule? Presumably you have an Invocation directly, not an Ast.Table or Ast.Action? Or maybe you should use the primitive templates instead, like we do in Android? In any case, I'm not convinced this patch is correct.

Why do you need to go through typecheck in make rule? Presumably you have an Invocation directly, not an Ast.Table or Ast.Action? Or maybe you should use the primitive templates instead, like we do in Android? In any case, I'm not convinced this patch is correct.

I am using the primitive templates, that's why I don't have invocation directly. I guess I can do iteratePrimitives, and track what parameter has been used locally...

Wait no, if you're using the primitive templates, then you have the primitive template arguments, and you're good to go. Beta reduce those, do nothing else.


remove YeOldePlumberSchool.java, unused

This is no longer used and can be removed.

Look like it's also mentioned in docs/content/design/plumber.md, so that can be removed too

Oops, had a *.java filter when I searched for occurrences, thanks :+1:

Look like it's also mentioned in docs/content/design/plumber.md, so that can be removed too

Ah, actually this documentation is removed in latest master after the doc change, so I just did a pointless merge :shrug:

General issue: #6860


Code-golf rectangle_fs.wgsl to work around a suspected angle/mesa bug and avoid crash on chrome (#3931)

What
When we added support for YUY2 format in (https://github.com/rerun-io/rerun/pull/4877) we we re-triggered the issue originally originally reported in https://github.com/rerun-io/rerun/issues/3931 and now https://github.com/rerun-io/rerun/issues/5073

This is a more extreme version of: https://github.com/rerun-io/rerun/pull/3948 which was the workaround the first time we hit this.

Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[x] I have tested the web demo (if applicable):

Using newly built examples: app.rerun.io
Using examples from latest main build: app.rerun.io
Using full set of examples from nightly build: app.rerun.io

[x] The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
[x] If applicable, add a new check to the release checklist!

PR Build Summary
Docs preview
Examples preview
Recent benchmark results
Wasm size tracking

Let's make sure we test this new shader properly before merging!

Let's make sure we test this new shader properly before merging!
Confirmed both nv12/yuy2 working on both native and web.


Add Snackbar Control with Auto-hide, Message Queuing, and Animations

Is your feature request related to a problem? Please describe.
Sometimes it's important to show a temporary message to the user that will automatically disappear after a set duration. For instance, I have a small application that updates the database in the background, and I need to show a brief notification (around 5 seconds) informing the user about the completed action. Currently, the user can click on an action button labeled "Details" to open a new view with the full update details. While the Infobar control exists, it doesn't fully meet my needs. Specifically, it lacks the ability to auto-hide after a specified time, and it isn't as visually dynamic or flexible for this use case.
Describe the solution you'd like

Auto-close functionality: The snackbar should disappear automatically after a specified time (e.g., 5 seconds). If not time is set then it will just stay open until the user close it manually.
Message queuing: It should support queuing multiple messages, displaying them one after the other.
Slide-in/Slide-out animations: The snackbar should have smooth animations when it appears and disappears (e.g., sliding from the bottom).
Customizable message content: The control should allow for custom content, including text and optional action buttons (e.g., "Undo" or "Details").
Message prioritization: The ability to prioritize certain messages in the queue or display an important message immediately if needed.
Styling options: The snackbar should allow for custom styling and theming, enabling the user to adjust colors, padding, and other visual aspects (Optional).

Describe alternatives you've considered
I have considered using the Infobar, but it lacks several key features, such as auto-hide timing, smooth animations, and message queuing. As such, it doesn't fulfill the requirements for this particular use case.
Additional context
A snackbar would be a highly useful addition to the FluentAvalonia toolkit, as it would provide a more visually engaging and dynamic way to display brief, non-intrusive notifications in applications. If possible, a demo or example implementation would be great to help with integration.

Isn't WindowNotificationManager what you need? It's a plain Avalonia control. Check Avalonia sample for reference. https://github.com/AvaloniaUI/Avalonia/blob/master/src/Avalonia.Controls/Notifications/WindowNotificationManager.cs

As Tim said above, Avalonia's built-in WindowNotificationManager already exists. If that isn't feature complete enough for you, either make feature requests upstream or make a new proposal that explains how a new control could significantly fill the gap that doesn't exist.


v2 temperature graph has been way off for a couple of weeks

Since some point last month, the v2 temperature has consistently been about 4° too low for my location. Check out this screenshot and compare the graph to the display temperature in the "Weather" line:

(data obtained with terminal command curl v2.wttr.in/hannover in lxterminal)

I switched it from FeelsLike to the real temperature, but it still fully off.
Unfortunately, the data from our data source seems to be really bad (though quite expensive). I think it is slowly the time to think about the support of other data sources.

I switched it from FeelsLike to the real temperature, but it still fully off.
Unfortunately, the data from our data source seems to be really bad (though quite expensive). I think it is slowly the time to think about the support of other data sources.

Thanks! At least the graphic is internally consistent now, which is certainly an improvement. I'll close the issue.

Thanks! At least the graphic is internally consistent now, which is certainly an improvement. I'll close the issue.


Replace  with Markdown backticks instead of curly brackets

<c></c> tags are currently replaced by {}, but this is rather old code, and I couldn't find anything about this being standard practice in OpenAPI/Swagger (the only mention I could find of {} was in relation to URL path parameters). Redoc displays curly brackets as-is.
This PR changes the behaviour to use GitHub-flavoured markdown, instead - <c></c> tags are replaced with single backticks and  tags (previously ignored) are replaced with triple backticks. Redoc supports this style of code formatting out of the box.

thanks


Minecraft Editor on Bedrock Mobile

Please make this available for mobile when it's finished

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

ID: 7f970d29-d692-24c3-0ebb-53c97f19c9c8
Version Independent ID: 7f970d29-d692-24c3-0ebb-53c97f19c9c8
Content: Minecraft Bedrock Editor Installation
Content Source: creator/Documents/EditorInstallation.md
Product: gaming
GitHub Login: @JDHeaden
Microsoft Alias: v-jillheaden

Thank you for your feedback! While we are unable to provide general support via this feedback channel that isn’t related to specific documentation issues, we will do our best to pass on your message to the appropriate channels.


remove selectable from component settings card

Fixes

https://issues.redhat.com/browse/HAC-2998
Description

Type of change

[ ] Feature
[x] Bugfix
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

Screen shots / Gifs for design review

How to test or reproduce?

Browser conformance:

[x] Chrome
[ ] Firefox
[ ] Safari
[ ] Edge

No blue line (at the top) is fine. This isn't a selectable card. It's just expandable. This aligns with the samples in patternfly.
before:

/lgtm
/approve

/retest

/retest


fix setup version

Coverage remained the same at 100.0% when pulling 9c14a866a177c2c51d3b3a5fe5d13341ddc61022 on yuce:fix-setup-v into dd6833cb06a7c9f8985aa532ed49be1ca05279d5 on pilosa:master.


Use Other Component Frameworks.

The currently used Material-UI frameworks actually is good as the standard components framework for this app. But let's try to reconsider this, i just found another frameworks, Chakra UI, which has a lot more components than Material-UI. It seems other frameworks (like i mentioned earlier) could be much simplier to be used as it already provide a lot of things. Actually we do not need an customizable components, just a standard ones that had a lot of features that we could just use. imagine creating a loading button without the need to manually add loading components and state into it.

Alternative, https://github.com/TuSimple/naive-ui.


[TYPO] Future Topics Section

https://craigtaub.dev/introducing-my-under-the-hood-of-series
Under Future Topics
Go a suggestion? Email me at<EMAIL_ADDRESS>
Correction: Go -> Got

Thanks so much for flagging, this is now corrected.


Electron 1.2.x SQLite3 not working on windows (DLL related issue)

Hi, I already spent 3 days trying to fix this problem, the SQLIte3 module works fine in Linux and Darwin, but in windows x64 it is launching the following error:
A dynamic link library (DLL) initialization routine failed.
node_modules\sqlite3\lib\binding\electron-v1.2-win32-x64\node_sqlite3.node
I tried rebuilding the module targeting electron 1.2.7 with this commands:
npm run prepublish
node-gyp configure --module_name=node_sqlite3 --module_path=../lib/binding/electron-v1.2-win32-x64
node-gyp rebuild --target=1.2.7 --arch=x64 --target_platform=win32 --dist-url=https://atom.io/download/atom-shell --module_name=node_sqlite3 --module_path=../lib/binding/electron-v1.2-win32-x64

But it fails throwing a lot of erros and warnings about deprecated stuff, if I change the target to electron v. 0.37.0 then it compiles correctly but I get the same DLL error and I have no idea why is it happening.
Had anyone any luck when trying to use the SQLIte module in windows with the latests electron versions? All I have found is just rebuild instructions using always the 0.x.x versions.
I'm trying to run this on:

Windows 10 x64
Node 6.3.0
NPM 3.10.3
Electron 1.2.7

Thanks in advance.

Hi, I faced the rebuilding issue and fixed in my environment.

Windows 7 x64
node 4.4.1
npm <IP_ADDRESS>
Electron 1.3.1

A dynamic link library (DLL) initialization routine failed.
node_modules\sqlite3\lib\binding\electron-v1.2-win32-x64\node_sqlite3.node

I assume the path above is a part of the DLL error message.
Is the path actually exists on your file system? If not, it obviously fails.
It will be helpful that you provide the error messages.
I hope this helps.

Can't use Node 6.x @CheckMater - I found this out the extremely hard way. This whole build process really needs fixing on Windows. Some prebuilt binaries here would go a LONG way for this project.
The only successful combination that's worked for me:

node 4.4.x
npm 2.x.y
python 2.7
visual studio 2013 express (didn't work for me in vs2015)
set environment variable GYP_MSYS_VERSION=2013
launch the Developer Command Prompt for VS2013 shortcut as Administrator

npm run prepublish
node-gyp configure --module_name=node_sqlite3 --module_path=../lib/binding/electron-v1.3-win32-x64
node-gyp rebuild --target=1.3.0 --target_arch=x64 --target_platform=win32 --dist-url=https://atom.io/download/atom-shell --module_name=node_sqlite3 --module_path=../lib/binding/electron-v1.3-win32-x64 --runtime=electron`

Is doing this:

npm run prepublish
node-gyp configure --module_name=node_sqlite3 --module_path=../lib/binding/electron-v1.3-win32-x64
node-gyp rebuild --target=1.3.0 --target_arch=x64 --target_platform=win32 --dist-url=https://atom.io/download/atom-shell --module_name=node_sqlite3 --module_path=../lib/binding/electron-v1.3-win32-x64 --runtime=electron`

Is the same as using electron-rebuild
.\node_modules.bin\electron-rebuild.cmd
?
@erikyuzwa Did you manage to get SQLite to work after rebuilding ?

Is the same as using electron-rebuild
.\node_modules.bin\electron-rebuild.cmd

I don't know. I had no idea that existed. I'd say go for it and see what happens.
Mine rebuilds SQLite3 and works for me every time now, so I'm leaving it. :+1:


Calibration

Hi,
I want to calibrate two L515 sensors, to make 3D reconstructions from different cameras. How I can do that?

Required Info

Camera Model
{ L515 }

Firmware Version
(Open RealSense Viewer --> Click info)

Operating System & Version
Ubuntu 18

@MartyG-RealSense Thank you for the reply.
can you give details on how cameras had their positions calibrated relative to each other using Apriltags? I am using Open3d for 3D reconstruction. But I want to figure out how can I use multiple cameras?

The YouTube video shows that the solid 3D model resulting from the stitching was being viewed in Open3D but does not provide details of the software being used during the scanning process or how the apriltag boards were used for calibration.

There was a similar Open3D project in the link below that uses multiple Azure Kinect cameras to calibrate against apriltags and generate a combined point cloud.
https://github.com/stytim/k4a-calibration

Hi @likui01  Do you require further assistance with this case, please?  Thanks!

@MartyG-RealSense, thank you for your response.
I am still unable to calibrate the two L515, it's a work in progress. At this time i don't have an exact question.
I am looking into ways in which i can calibrate using April tags.

Another commercial 3D software tool that supports the L515 camera model is DotProduct Dot3D.  It is available in a Lite version and a Pro version for larger scenes that captures up to 160 million points.
https://www.dotproduct3d.com/dot3dlite.html
https://www.dotproduct3d.com/dot3dpro.html
DotProduct has a tutorial for how two separate scans can be registered together using apriltags.
https://desk.zoho.com/portal/dotproduct/en/kb/articles/dot3d-tutorial-registering-multiple-dp-scans-with-apriltags-in-dot3d-pro

Hi @likui01  Do you require further assistance with this case, please?  Thanks!

Case closed due to no further comments received.


fix(selection-list): do not coerece option value to boolean

Currently the value of a MdListOption is coerced to a boolean. This is not the correct behavior because it would mean that there could be only two values (true/false).
Needed for #6896

#6901 covers it already.


Implement Rayon traits (optional)

IntoParallelIterator by value, ref, and ref mut

Implements both ParallelIterator and IndexedParallelIterator

FromParallelIterator
ParallelExtend by value and ref copy

As awesome as this is, it does interfere with easy 1.0'ing of ordermap.

Would you want to wait for rayon-1.0?  Or would you hesitate even then?
Another idea is to add as_slice(), as_mut_slice(), and into_vec(), and put a public API on the Bucket, so people could themselves write something like:
omap.as_slice().into_par_iter()
    .map(|b| (b.key(), b.value())))
    .for_each(|(k, v)| ...);

That's not as ergonomic, but at least it would be possible to use Rayon with ordermap efficiently, and maybe enable other cool uses too!
(tombstones would make this uglier though.)

With rayon-1.0 I would not hesitate, but you're right, one could be worried about the version entanglement even then.
For the record, we've decided that OrderMap will stay as it is with its current properties, indexing, exact size = no tombstones (and probably the same name too, if we don't find a better one). This data structure is useful as it is, so to implement a similar one with tombstones, it will be a new thing. We could end up with both.

W.r.t order I'm very fond of a deterministic order (hash function independent).
I had a different thought -- would it be possible to implement OrderMap shared and mutable views. So that it would natively support splitting (by index) into two parts. Both the shared and mutable view would mean shared/mutable access to the elements only, not inserting or removing elements. I think that means that the mutable views can all have the same shared immutable reference to the index/hash vector.
In a mutable view, the implementation peeking into another view's part of the entries vector would be verboten.

I think views are a neat idea!  It wouldn't directly enable rayon, but it could let there be something like ordermap-parallel, like you did with ndarray and ndarray-parallel.

I've now rebased, updated to rayon 1.0, and added the basic set implementations.

That's cool! I'm fine with merging this, but I haven't looked through it in fine detail. rayon 1.0 is quite the thing, and maybe we can dare to go 1.0 with it as dependency. (Congratulations!)

I was also thinking of par_eq, par_is_disjoint, par_is_subset, and par_is_superset, as these are all operations that have to (potentially) iterate the whole set.  This might be too much par_ though. 😜
The only thing left would be drain, which we haven't really addressed at all in rayon.  I'm thinking about adding a general ParDrain trait, but I'm not sure.
Anyway, I should at least write some documentation and tests here before we merge. 😅
One specific API question for you is whether it's good to have these Par* types re-exported in the main map and set modules, next to their serial counterparts.  It might be better in separate modules, perhaps even public from the indexmap::rayon::map/set where they're currently implemented, and remove Par from their names. (like Rayon does for std iterator types)

This PR is clearly amazing. I think this is a great feature set for a hashmap library and in safe Rust no less (thanks to the giants of std::vec::Vec and rayon).
I think that's a lot of functions. I'd probably drop the comparisons and par_sorted_by (sorted_by would probably not have existed if sort_by was realized first? It is a tad more efficient, than sort_by though..). I'm just wondering if we can get most of the value with less API.
I don't know about the module and name prefix question. Mirroring std fits well with rayon. Here I don't mind either way.

What's the status of this pull request? I'm a fan of IndexMap, but right now I'm in a situation where I'd really like to be able to use rayon to get a performance boost, and unfortunately can't.

@cuviper Wow the quick response is much appreciated :)
I don't have a much input -- I'm just hoping to take advantage of rayon's accessible parallelism (where not having to worry about the details is a selling point) with the determinism I get from using an IndexMap everywhere internally.
I imagine there might be others in the same boat, who like IndexMap for it's determinism, but would also like to operate on the values in parallel.

I think this is good. Rayon is rock solid :wink: and doesn't feel like a risk. The code is simple.
Only review comment that is important to fix, is that the new methods (par_keys etc) need to be listed last in the docs, not first in the docs. I'd enable the rayon feature in docs.rs generation and make sure items are labelled in docs to require that feature (I can do that).

What's the state of this? I would like to use this feature

I think this is ready for reconsideration.

OK, that conflict was just in the compat downgrades, which #97 removed.
Rebased without that, and CI passed -- r=bluss

Great. I can do the release of 1.1.0


tab Page reloading every time there is a navigation to another page

Ionic version:  (check one with "x")
[ ] 1.x
[ ] 2.x
[x ] 3.x
I'm submitting a ...  (check one with "x")
[x ] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:

I have an application updated from ionic 2 to ionic 3 following the given instructoins in changelogs,
after the update everything is working fine expect the navigation, every time the app navigate from
a  page (source) to another page (destination), the source page reloads. Maybe it has something to do with the lazy loading.

Hello, thanks for opening an issue with us. Would you mind sharing a repo that we can use to reproduce this issue?

I think this is related to #11015.
@jgw96 there I provided a repo where you can reproduce the issue. I added a console.log in ionViewDidLoad() of every page and it logs out every time a tab is clicked the first time and also if it is clicked two times consecutively.

This might be resolved by https://github.com/driftyco/ionic/pull/11084

Your PR fix it

Hello all, after further review I am going to close this issue as a duplicate of https://github.com/driftyco/ionic/issues/11015.


Update the two-bucket proof and tests.

The moves() function now returns an object with keys: moves, goalBucket, otherBucket.
This removes the need for goalBucket and otherBucket properties.
I also fixed the "bug" where moves() can return after the 2nd move if the second bucket is the same size as the goal (fixes #1551).

You mentioned before that the tests in problem spec for this exercise were updated so I was expecting this PR would include a change to the tests.toml file due to the new sync via configlet. 🤔

There was no changes necessary to tests.toml. This PR is actually reflecting the actual problem-spec: https://github.com/exercism/problem-specifications/blob/87cd20ff0b2f078d5eb2da716dc7d74fb71ea258/exercises/two-bucket/canonical-data.json#L85

I saw you changed the output format for the exercise. I think it is definitely better then before.

Based on @joshgoebel's suggestion. It certainly simplifies things.

I was wondering whether the stub really needs to contain a class definition with the new changes you made. Would it make sense that the stub is just a function (e.g. solve) that returns the result object you defined? Then the student would be free too choose what classes they think they need in the implementation. (You don't have to change anything if you don't want to  but I would like to hear your thoughts.)

I don't have strong opinions about it. I think this problem naturally points to an OO solution, so I'm fine with what's there. I didn't want to make overly large changes to what was there already.

Whatever we decide for, the format of the input and expected output should be described in the instructions.append.md file so the student does not have to guess the format from the tests. You can also create an issue for this and it can be addressed later.

I see something similar for the satellite exercise. I'll add it to this PR.

I think this problem naturally points to an OO solution, so I'm fine with what's there.

@glennj Thanks for your feedback. Then let's keep it as is. One small thing though, what do you think about renaming the moves method to solve? Currently moves returns a result object which then has moves again as property. That seems a bit strange.


Compilation of envoy 1.24.6 on rocky linux with gcc version 8.5

When I am compiling envoy 1.24.6 on rocky linux with gcc version 8.5. I am getting compilation error like gcc version 9.2 or greater required.
Please confirm is this any kind of limitation that gcc version 9.2 or higher is required on rocky linux to compile envoy 1.24.6

cc @phlax as area owner

@Gaurav0411GitHub could you post the fail logs please ?
The gcc version used in the build image is 9.4.0
$ ./ci/run_envoy_docker.sh gcc --version
gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0

so that is what is tested, but i wasnt aware of a limitation on a particular version

Actually we were using envoy 1.17.4 version that was compiled on gcc version 8.5 but when I have upgraded to envoy 1.23.1 it was simply giving error like gcc version 9.2 or higher version is required so I took gcc 10.2 stable version and i was able to compile successfully.
At this moment I can not share compilation error log on gcc 8.5 so please update this limitation in your documentation also

please update this limitation in your documentation also

happy to review/raise a PR if i can confirm what the constraints actually are

...if i can confirm what the constraints actually are

and also why
im aware that there are people building with various compilers/toolchains and in some cases workarounds are neccessary
i suspect in this case its an issue with a dependent lib, but may well be wrong

https://github.com/envoyproxy/envoy/issues/26965#issuecomment-1527374656

You have updated the latest building guide but actual user should know which minimum gcc version should be used so I think rather than wasting time on compilation minimum gcc version should be mentioned that will be helpful for the user
so please specify minimum gcc version which can be used in compiling envoy

https://github.com/envoyproxy/envoy/issues/26965#issuecomment-1527374656

which minimum gcc version can be used to compile envoy code?

What is the end of life of envoy 1.17.4 and envoy 1.21.5 ?

I am getting the below error logs while i am compiling on gcc 8.5. Could you please help me in this?
bazel --bazelrc=/dev/null build --sandbox_debug --verbose_failures --copt="-DENVOY_IGNORE_GLIBCXX_USE_CXX11_ABI_ERROR=1 -DLLVM_USE_SPLIT_DWARF" --define wasm=disabled --config=sizeopt -c opt //source/exe:envoy-static.stripped
INFO: Analyzed target //source/exe:envoy-static.stripped (0 packages loaded, 0 targets configured).
INFO: Found 1 target...
ERROR: /root/.cache/bazel/bazel_root/54592e55cbb3b41c11501e7d56ec7ed8/external/com_github_google_tcmalloc/tcmalloc/internal/BUILD:516:11: Compiling tcmalloc/internal/page_size.cc failed: (Exit 1): process-wrapper failed: error executing command
(cd /root/.cache/bazel/bazel_root/54592e55cbb3b41c11501e7d56ec7ed8/sandbox/processwrapper-sandbox/2127/execroot/envoy &&
exec env -
BAZEL_LINKLIBS=-l%:libstdc++.a
BAZEL_LINKOPTS=-lm
PATH=/root/.cache/bazelisk/downloads/bazelbuild/bazel-6.1.0-linux-x86_64/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PWD=/proc/self/cwd
TMPDIR=/tmp
/root/.cache/bazel/bazel_root/install/f0478d8547df16461adab7eb1d945d57/process-wrapper '--timeout=0' '--kill_delay=15' '--stats=/root/.cache/bazel/bazel_root/54592e55cbb3b41c11501e7d56ec7ed8/sandbox/processwrapper-sandbox/2127/stats.out' /usr/bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 '-D_FORTIFY_SOURCE=1' -DNDEBUG -ffunction-sections -fdata-sections '-std=c++0x' -MD -MF bazel-out/k8-opt/bin/external/com_github_google_tcmalloc/tcmalloc/internal/objs/page_size/page_size.d '-frandom-seed=bazel-out/k8-opt/bin/external/com_github_google_tcmalloc/tcmalloc/internal/objs/page_size/page_size.o' -gsplit-dwarf -g '-DBAZEL_CURRENT_REPOSITORY="com_github_google_tcmalloc"' -iquote external/com_github_google_tcmalloc -iquote bazel-out/k8-opt/bin/external/com_github_google_tcmalloc -iquote external/com_google_absl -iquote bazel-out/k8-opt/bin/external/com_google_absl '-DABSL_MIN_LOG_LEVEL=4' -fPIC -Wno-deprecated-declarations '-DENVOY_IGNORE_GLIBCXX_USE_CXX11_ABI_ERROR=1 -DLLVM_USE_SPLIT_DWARF' -Os '-std=c++17' -Werror -Wno-attribute-alias -Wno-sign-compare -Wno-stringop-overflow -Wno-uninitialized -Wno-unused-function -Wno-unused-result -Wno-unused-variable -fno-canonical-system-headers -Wno-builtin-macro-redefined '-D__DATE="redacted"' '-D__TIMESTAMP="redacted"' '-D__TIME="redacted"' -c external/com_github_google_tcmalloc/tcmalloc/internal/page_size.cc -o bazel-out/k8-opt/bin/external/com_github_google_tcmalloc/tcmalloc/internal/_objs/page_size/page_size.o)
In file included from external/com_github_google_tcmalloc/tcmalloc/internal/page_size.h:21,
from external/com_github_google_tcmalloc/tcmalloc/internal/page_size.cc:15:
external/com_github_google_tcmalloc/tcmalloc/internal/config.h:89:2: error: #error "GCC 9.2 or higher is required."
#error "GCC 9.2 or higher is required."
^~~~~
Target //source/exe:envoy-static.stripped failed to build
INFO: Elapsed time: 1.292s, Critical Path: 0.38s

Please let me know what is the workaround for this

If you know the work around for gcc 8.5 error, Please let me know
I have compiled on gcc 11.2. In which I am getting below logs.
[2023-05-12 14:42:05.155][56649][warning][config] [source/common/config/grpc_subscription_impl.cc:128] gRPC config for type.googleapis.com/envoy.config.listener.v3.Listener rejected: Error adding/updating listener(s) AA_LISTENER_0: Only IPv6 address '::' or valid IPv4-mapped IPv6 address can set ipv4_compat: X.X.X.X:4568
AA_LISTENER_01: Only IPv6 address '::' or valid IPv4-mapped IPv6 address can set ipv4_compat: [IPvIP]:4568
AA_SEC_LISTENER_0: Only IPv6 address '::' or valid IPv4-mapped IPv6 address can set ipv4_compat: X.X.X.X:4569
are these errors or info logs?

Hi,
I have compiled successfully envoy 1.26.1 version on gcc 11.2 version
envoy 1.26.1 is compatible with gRPC 1.30.3 version and ibprotoc.so.<IP_ADDRESS> ?
While we are upgrading from envoy 1.17.4 to envoy 1.26.1, we are not able to use envoy.filters.network.tcp_proxy.
could you please suggest us should i need to update envoy api or give me reference how can we use envoy.filters.network?

Some of the examples provide the updated config you are looking for - eg https://github.com/envoyproxy/envoy/blob/2a63fe20f7dd77062e8ca04ee19bc605bf9e02d5/examples/postgres/envoy.yaml#L14-L18
https://www.envoyproxy.io/docs/envoy/v1.26.1/start/sandboxes/postgres

Hi,
We have upgraded envoy1.26.1 but we are getting below error
[2023-05-23 12:33:43.456][2411][warning][config] [source/common/config/grpc_subscription_impl.cc:128] gRPC config for type.googleapis.com/envoy.config.listener.v3.Listener rejected: Error adding/updating listener(s) H2I_NONSEC_LISTENER_0: Only IPv6 address '::' or valid IPv4-mapped IPv6 address can set ipv4_compat: <IP_ADDRESS>:4568.
Please let mw know how can we solve the problem?


Document Terraform changes

document Terraform changes in the getting started guide
add a new GCE section for Terraform
update the existing OpenStack section for Terraform
change the roadmap
fix formatting everywhere in the docs
add some awesome images
probably the start of the singularity or something, I don't know.

anyway, if someone like @keithchambers or @stevendborrelli could give these changes a quick look, I'd appreciate it.

Although I haven't been able to test on Openstack or GCE entirely yet, here's some preliminary feedback:

I couldn't use Service Account in GCE, as I am not project owner. This might be mentioned.
I didn't understand the distinction between the two region fields.
"Customizing your deployment" should be moved up.
This command should include security.yml: ansible-playbook -i plugins/inventory/terraform.py terraform.yml

After getting everything provisioned on Openstack, I'd say the documentation looks good!

@siddharthist I'll merge this, can you submit a pull for the documentation changes you suggested?

@stevendborrelli

service account: 8ad7fc8
moving link up: a2dd530
region fields: 86c77e1
security.yml in command: 3b061d0


PyData Sphinx -  accessibility audit

### Tasks
- [ ] Keyboard navigation event (scheduled)

This happened - Tania needs to follow up on the actions and opening issues on the pydata sphinx repo


Shares backend

\OCA\ScienceMesh\Controller::RevaController
Methods:  78.05% (32/41)   Lines:  76.67% (355/463)

I will probably need it for Unshare().

@br0kk0l1 Ok I updated it.


database: fixed bug

time was in milliseconds and promo expected seconds

@marcelhollerbach noted that milliseconds worked when he tested it. @kelunik is it possible that the specification is wrong and you use milliseconds too?

It's a bug in both implementations, not the spec. ;-)

so what gets altered? the implementation or the spec? If its a bug you can merge the pull request ;)

Implementations. ;-)


Error building with latest dawn

Hi Henry,
I am currently working on setting up a homebrew formula for dawn to allow people to more easily try out swift-webgpu (because building from source can take over 45 minutes on my laptop).
It seems like swift-webgpu might not quite be compiling with the latest dawn though. Here's the error I get:
➜  swift-webgpu git:(main) swift build -c release
Building for production...
In file included from /Users/stackotter/Desktop/Projects/Swift/Experiments/DawnBuild/swift-webgpu/Sources/CDawnNative/dawn_native.cpp:4:
/usr/local/include/dawn/native/DawnNative.h:25:15: warning: nested namespace definition is a C++17 extension; define each namespace separately [-Wc++17-extensions]
namespace dawn::platform {
              ^~~~~~~~~~
               { namespace platform
warning: nested namespace definition is a C++17 extension; define each namespace separately [-Wc++17-extensions]
namespace dawn::native {
              ^~~~~~~~
               { namespace native
2 warnings generated.
/Users/stackotter/Desktop/Projects/Swift/Experiments/DawnBuild/swift-webgpu/Sources/WebGPU/Structs.swift:841:48: error: missing arguments for parameters 'timestampWriteCount', 'timestampWrites' in call
        var cStruct = WGPUComputePassDescriptor(
                                               ^
CWebGPU.WGPUComputePassDescriptor:3:12: note: 'init(nextInChain:label:timestampWriteCount:timestampWrites:)' declared here
    public init(nextInChain: UnsafePointer<WGPUChainedStruct>!, label: UnsafePointer<CChar>!, timestampWriteCount: UInt32, timestampWrites: UnsafePointer<WGPUComputePassTimestampWrite>!)
           ^
/Users/stackotter/Desktop/Projects/Swift/Experiments/DawnBuild/swift-webgpu/Sources/WebGPU/Structs.swift:1586:51: error: missing argument for parameter 'clearValue' in call
            clearColor: cStruct_clearColor.pointee
                                                  ^
                                                  , clearValue: <#WGPUColor#>
CWebGPU.WGPURenderPassColorAttachment:3:12: note: 'init(view:resolveTarget:loadOp:storeOp:clearColor:clearValue:)' declared here
    public init(view: WGPUTextureView!, resolveTarget: WGPUTextureView!, loadOp: WGPULoadOp, storeOp: WGPUStoreOp, clearColor: WGPUColor, clearValue: WGPUColor)
           ^
/Users/stackotter/Desktop/Projects/Swift/Experiments/DawnBuild/swift-webgpu/Sources/WebGPU/Structs.swift:1635:59: error: missing arguments for parameters 'depthClearValue', 'stencilClearValue' in call
        var cStruct = WGPURenderPassDepthStencilAttachment(
                                                          ^
CWebGPU.WGPURenderPassDepthStencilAttachment:3:12: note: 'init(view:depthLoadOp:depthStoreOp:clearDepth:depthClearValue:depthReadOnly:stencilLoadOp:stencilStoreOp:clearStencil:stencilClearValue:stencilReadOnly:)' declared here
    public init(view: WGPUTextureView!, depthLoadOp: WGPULoadOp, depthStoreOp: WGPUStoreOp, clearDepth: Float, depthClearValue: Float, depthReadOnly: Bool, stencilLoadOp: WGPULoadOp, stencilStoreOp: WGPUStoreOp, clearStencil: UInt32, stencilClearValue: UInt32, stencilReadOnly: Bool)
           ^
/Users/stackotter/Desktop/Projects/Swift/Experiments/DawnBuild/swift-webgpu/Sources/WebGPU/Structs.swift:1634:16: warning: no calls to throwing functions occur within 'try' expression
        return try self.view.withUnsafeHandle { handle_view in
               ^
/Users/stackotter/Desktop/Projects/Swift/Experiments/DawnBuild/swift-webgpu/Sources/WebGPU/Structs.swift:1689:47: error: missing arguments for parameters 'timestampWriteCount', 'timestampWrites' in call
        var cStruct = WGPURenderPassDescriptor(
                                              ^
CWebGPU.WGPURenderPassDescriptor:3:12: note: 'init(nextInChain:label:colorAttachmentCount:colorAttachments:depthStencilAttachment:occlusionQuerySet:timestampWriteCount:timestampWrites:)' declared here
    public init(nextInChain: UnsafePointer<WGPUChainedStruct>!, label: UnsafePointer<CChar>!, colorAttachmentCount: UInt32, colorAttachments: UnsafePointer<WGPURenderPassColorAttachment>!, depthStencilAttachment: UnsafePointer<WGPURenderPassDepthStencilAttachment>!, occlusionQuerySet: WGPUQuerySet!, timestampWriteCount: UInt32, timestampWrites: UnsafePointer<WGPURenderPassTimestampWrite>!)

And then if I regenerate the code from the current dawn.json file I get different errors:
Building for production...
/Users/stackotter/Desktop/Projects/Swift/Experiments/DawnBuild/swift-webgpu/Sources/WebGPU/Structs.swift:1601:137: error: consecutive statements on a line must be separated by ';'
    public init(view: TextureView? = nil, resolveTarget: TextureView? = nil, loadOp: LoadOp, storeOp: StoreOp, clearColor: Color = { NAN, NAN, NAN, NAN }, clearValue: Color) {
                                                                                ^
                                                                                ;
/Users/stackotter/Desktop/Projects/Swift/Experiments/DawnBuild/swift-webgpu/Sources/WebGPU/Structs.swift:1601:137: error: expected expression
    public init(view: TextureView? = nil, resolveTarget: TextureView? = nil, loadOp: LoadOp, storeOp: StoreOp, clearColor: Color = { NAN, NAN, NAN, NAN }, clearValue: Color) {
                                                                                ^
/Users/stackotter/Desktop/Projects/Swift/Experiments/DawnBuild/swift-webgpu/Sources/WebGPU/Structs.swift:1601:134: error: cannot find 'NAN' in scope
    public init(view: TextureView? = nil, resolveTarget: TextureView? = nil, loadOp: LoadOp, storeOp: StoreOp, clearColor: Color = { NAN, NAN, NAN, NAN }, clearValue: Color) {
                                                                                ^~~
/Users/stackotter/Desktop/Projects/Swift/Experiments/DawnBuild/swift-webgpu/Sources/WebGPU/Structs.swift:1656:126: error: cannot find 'NAN' in scope
    public init(view: TextureView, depthLoadOp: LoadOp = .undefined, depthStoreOp: StoreOp = .undefined, clearDepth: Float = NAN, depthClearValue: Float = 0, depthReadOnly: Bool = false, stencilLoadOp: LoadOp = .undefined, stencilStoreOp: StoreOp = .undefined, clearStencil: UInt32 = 0, stencilClearValue: UInt32 = 0, stencilReadOnly: Bool = false) {
                                                                                ^~~
[1/7] Compiling WebGPU Aliases.swift

The dawn commit I am using is ed84058.
Do you get the same errors when you try to build swift-webgpu with the latest dawn commit? (there have been two newer commits but they're just dep rolls and the errors I'm getting seem to be more about breaking changes in dawn)

Here's the repo with the script I used to build dawn. And here's the dawn homebrew tap I made which seems to be working. But swift-webgpu doesn't build with the tap installed or with the current way from the readme (same error both ways).

Hey,
Sounds good! A homebrew formula will definitely help make it more accessible. You can probably disable a few things like swiftshader, vulkan, angle/opengl to speed up the dawn build, if you know that you will be targeting metal.
Looks like they added a couple of new concepts to dawn.json, which I've implemented now in the swift-webgpu generator. If you pull the latest, you should find that it works with that dawn commit.
It's probably worth me documenting which dawn commit the swift files are generated from. Eventually, I would like to remove the generated swift files from this repo and have them generated as a custom build step. I believe this will be possible in an upcoming release of the swift package manager.

Would you be able to point me in the right direction for how to disable the unnecessary components?
Thanks for fixing that!
I've just tried building with the latest commit and I'm getting a lot of strange errors. I've tried troubleshooting for quite a while and I'm only managing to create even weirder errors. The one time I managed to get it to compile, it gave me this error when running DemoTriangle:
dyld[5006]: Symbol not found: _wgpuAdapterEnumerateFeatures
  Referenced from: /Users/stackotter/Desktop/Projects/Swift/Experiments/DawnBuild/swift-webgpu/.build/x86_64-apple-macosx/release/DemoTriangle
  Expected in: /usr/lib/libSystem.B.dylib
[1]    5006 abort      .build/x86_64-apple-macosx/release/DemoTriangle

Here's what happens if I do it clean without trying to fix anything (I have attached the 896 lines of errors in a text file)
output.txt.
The command I ran was:
swift build -c release \
-Xcc -I/path/to/dawn/src/include \
-Xcc -I/path/to/dawn/out/Release_x64/gen/include \
-Xlinker -L/path/to/dawn/out/Release_x64 \
-Xlinker -rpath -Xlinker /path/to/dawn/out/Release_x64

At the moment I'm just trying without using the version installed with homebrew, because I don't really have a chance of getting it to compile with those if it won't compile the normal way.

You can run gn args out/Release --list in the dawn directory and this should list all of the available options that you can add to your args.gn file. The most relevant ones should start with "dawn_". I currently use the following for development:
is_debug=false
dawn_use_angle=false
dawn_use_swiftshader=false

I suppose if you did want to target a Mac that doesn't support metal then you may want to leave them enabled, but I can't imagine that is very common these days?
Ah, they did reorganise the dawn folder structure recently and I need to update the readme. The first include path should now be /path/to/dawn/include instead of /path/to/dawn/src/include. That might explain those errors.
You may also run into an issue with the dawn libraries having incorrect install names. I'll add a note to the readme about that as well. Homebrew will likely fix these for you automatically though.

Ok, thanks for the tips. I'll try changing that include path when I get back to my laptop. And I'll also see how's he quicker builds are with those settings disabled. The one time I did get it to compile (dunno how), the rpath for dawn_native was libnative.dylib and so naturally it couldn't find the dylib. Is that what you mean by install issues?

And with the install names issue I tried using install_name_tool to correct it, but it couldn't find libdawn_native.dylib either even though it was in /usr/local/lib which is on the default search path according to the ld man page

Just tried building again, and with the new include path it built. However now I think I'm running into the install name error you were talking about.
Here's the error I get when I run it:
dyld[11967]: Symbol not found: _wgpuAdapterEnumerateFeatures
  Referenced from: /Users/stackotter/Desktop/Projects/Swift/Experiments/DawnBuild/swift-webgpu/.build/x86_64-apple-macosx/release/DemoTriangle
  Expected in: /usr/lib/libSystem.B.dylib
[1]    11967 abort      ./DemoTriangle

I tried fixing the path for dawn_native with install_name_tool (otool -L showed me that it's trying to link against libnative.dylib and somehow doesn't throw an error about not finding the dylib).
install_name_tool -change @rpath/libnative.dylib /path/to/dawn/out/Release/libdawn_native.dylib DemoTriangle

However, I still get the same error when running. For some reason Swift seems to be telling the linker that all the dawn_native symbols are in libSystem.B.dylib? I'm on Swift 5.6 by the way, here's the exact version: swift-driver version: 1.44.2 Apple Swift version 5.6 (swiftlang-<IP_ADDRESS>0.8 clang-13<IP_ADDRESS>). I'm on Xcode 13.3 beta 1.

I just tried the new build instructions (including how to fix the linking issue) and it's finally running again, woohoo! Now I just need to figure out how to get it to link against the dawn installed by homebrew. It keeps giving me errors about not being able to find the library for -ldawn_native even though when I run ld manually it finds it correctly. Maybe Swift doesn't link to things from the system unless explicitly mentioned in package.swift or a module map?
Anyway, that's not part of this issue anymore, and I don't think it's an issue with swift-webgpu/dawn anymore (just the way swift does linking), so I'll close this issue.
Thanks for all the help :)

Yep, guessed it:
Library search paths:
	/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/macosx
	/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk/usr/lib/swift
	/usr/local/Cellar/glfw/3.3.6/lib
	/Users/stackotter/Desktop/Projects/Swift/Experiments/DawnBuild/swift-webgpu/.build/x86_64-apple-macosx/release
	/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/usr/lib
	/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib
	/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk/usr/lib

It only includes search paths for tools that it was explicitly told to link to, probably smart for portability of swift to do that. Hopefully I get some time this week to get the brew dawn working properly with swift-webgpu

Ah ok, brew can be added as a provider for dawn in the Package.swift, as is the case with glfw, which should work?
You should also be able to add the path manually with a linker flag - something like -Xlinker -L/usr/local/Cellar/dawn/lib.
Out of interest, how did you get that list of search paths?

I think I've figured out what needs to be changed, my homebrew dawn formula needs to create a pkg config file so that swift knows where to find it (i think that's how it finds glfw, the provider thing is just to tell users what to do when it's missing from memory?). I can't try that right now though cause I don't have my laptop.
I got the linker search paths by add -Xlinker -v to the build command.
Yeah, it works when I add it to the search paths manually with the flag, but I don't want users to have to do that because then building from Xcode is cumbersome and everyone using derivative packages also has to add the flags.

Hi again Henry, I've been juggling quite a few different open-source projects recently, so swift-webgpu has fallen down my priorities list again.
Feel free to try getting the homebrew package working though, I'd be happy to explain what I've done so far and what the current issues are. Just thought I should let you know that it'll probably be a while before I get around to working on this project again.


Link needed

It would be helpful if there was a link provided to NAVApp.

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

ID: c6dd7c9e-51a5-eeea-a2f6-dd4d40b93295
Version Independent ID: d6fb1d1b-fa2e-606e-6c79-115651b60a29
Content: Writing extensions installation code - Business Central
Content Source: dev-itpro/developer/devenv-extension-install-code.md
Service: dynamics365-business-central
GitHub Login: @jswymer
Microsoft Alias: solsen

Thanks for the feedback. The issue will be fixed with the next doc refresh.

Thanks for the feedback. The issue will be fixed with the next doc refresh.


Using a round delta printer with origin set to 'center' in the printer profile cause off set issues

If I slice with a printer profile that has the origin set to 'center', and a printer area of 200x200x300 the gcode generated puts the part completely off the bed to the top-right when viewed in the gcode viewer.
Using the built in slicer without any other plugins works perfectly.

Sorry for the delay. Just came back from a long vacation.
Will work on this issue whenever I get a chance.

No worries, thank you for looking into it!
Thanks,
Jorg
Erik 'Jorg' Jorgensen
Support Systems Administrator - Principal
Vended Applications Support Services
Division of IT
University of Missouri - Columbia
jorgie<EMAIL_ADDRESS>573.882.5974
"If you're not gonna tell the truth, then why start talking?" - Gene Wilder, 1933 - 2016 R.I.P.
From: Kenneth Jiang<EMAIL_ADDRESS>Sent: Thursday, December 1, 2016 8:37 AM
To: kennethjiang/OctoPrint-Slicer<EMAIL_ADDRESS>Cc: Jorgensen, Erik<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [kennethjiang/OctoPrint-Slicer] Using a round delta printer with origin set to 'center' in the printer profile cause off set issues (#18)
Sorry for the delay. Just came back from a long vacation.
Will work on this issue whenever I get a chance.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/kennethjiang/OctoPrint-Slicer/issues/18#issuecomment-264188752, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ANENV6Hk1FKQkARvb8F2GyVq7e9_375mks5rDtungaJpZM4K3K3-.


Upate documentation

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Add a feature to the invoice that would show currency in words as a readable string

Description
This feature request aims to enhance the invoice generation system by adding the capability to display the currency amount in words as a readable string. This addition will improve the clarity and professionalism of the generated invoices, making them more user-friendly for clients and partners.
Proposed Implementation
There could be a switch in the invoice that toggles this functionality. It can be turned on by default. Next, a format function is needed to turn a float (Ex: 100.50) into words
Why it's Important

Professionalism: Providing the currency in words demonstrates attention to detail and professionalism in our financial documents.

Clarity: It makes it easier for clients to understand and verify the invoice amounts, reducing potential disputes and inquiries.

Legal Compliance: In some regions, displaying the currency in words is a legal requirement for invoices.

Feature implemented by commits 75289bc and 997249d


browser common js version has debug enabled by default

What version of bluebird is the issue happening on?

3.5.0

What platform and version? (For example Node.js 0.12 or Google Chrome 32)

bundling with browserify, dist picked via browser field js/browser/bluebird.js
https://github.com/petkaantonov/bluebird/blob/v3.5.0/js/browser/bluebird.js#L687
Issue is that __DEBUG__ global is set to true by default in this version, so unless it's explicitly disabled via other env vars, performance is insanely poor in IE11 due to long stack traces (at least thats one of the problems)
I didn't see anywhere that this is the documented behaviour, so I expect that to be a bug. If not - would be nice to have a clarification in the README about it
Thanks!

I think the installation instructions are pretty clear at http://bluebirdjs.com/docs/install.html - feel free to edit them and submit a PR if you think we can clarify them.

Thing is, using these instructions with browserify:
var Promise = require('bluebird')

// ... do stuff

Leads to inclusion of https://github.com/petkaantonov/bluebird/blob/master/package.json#L71 (debug browser build) - therefore I'd suggest this is at least changed to minified version


Log noise when using multiple secret validators

I use a combination of secret validators (ones provided out of the box by you guys)
As I understand it when trying to validate secrets, IdentityServer4 will enumerate through your validators to see if one matches a secret that is being validated.
However quite often even though the secret is valid for a given validator, a validator unsuitable for the secret would try and validate the secret causing these messages to come through the logs
Secret: [[Secret Description]] uses invalid hashing algorithm.
Also I get the following when trying to validate my implicit clients which have no secrets
No client secret found
Now these two messages are clogging up my logs and im wondering if this is intended behavior or how do I omit this besides adding some sort of filter to my log provider which I would prefer to not do.
Info:
Using identityserver beta4-update1
Adding my validators using the following on the IDS4 builder
builder.AddSecretValidator<HashedSharedSecretValidator>();
builder.AddSecretValidator<PlainTextSharedSecretValidator>();

Maybe this is not a Error level log but a warning level log? since it does not particularly mean that your validation request has failed. We typically log Error level and above to e-mail.

Sure, we can take a look.

Why are you using both hashed and plain text at the same time?

For legacy reasons to be honest.Some of our clients have thier secrets stored in plaintext while the others are hashed. The vast majority of them are stored as hashed secrets. We also have a sort of portal to manage clients and we would like to have some of these client_ids and client secrets in 'human' readable form for ease of remembering them. These are mostly for our internal prototype projects.

OK - will have a look.
but I don't understand this part:

Also I get the following when trying to validate my implicit clients which have no secrets

No client secret found

under which circumstances does this happen?

Ahh my apologies they are two separate issues.


Handle the case where we send proceed and the other side never replies

Easiest way to reproduce this is with Snikket iOS but it can happen in other cases. Call in with Snikket iOS, then hang up on iOS before answering with SDK. iOS sends nothing to indicate this hangup has occurred so we keep ringing. Then if we try to accept call we send proceed, and we never get a reply, so we are stuck forever thinking this is an ongoing call.

This may be less bad than I thought if we properly allow the user to push "hang up" in any UI then they can at least terminate the call based on their sense that it is not connecting. But a timeout might be sensible as well.


Ability to run inside kubernetes

Note: this issue was imported from https://github.com/wercker/stern/issues/87, but it was originally created by pastukhov...
Hi!
Is anyone rut stern as a driver to collect all the logs to elasticsearch/graylog?

This is not the scope of stern. We recommend using a log forwarder such as fluentd or fluent-bit.


Commit history

The commit history from this long running project has not been kept in the move to git/github. This information is important and a source of pride to the contributors. Please make every effort to retrieve it.

Commit history is available. I can do git log and get all the history from java.net. Did you try it yourself?

I was expecting to see the history here https://github.com/javacc/javacc/commits/master

There I see commits going back to 2003.

Yeah. Also looks like for most of the source code that was refactored
around 2013, there s no prior history.

There I see commits going back to 2003.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/javacc/javacc/issues/23#issuecomment-294513435,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATQdrYXC9FUpoLl_TS6x_eJWj0VTa5w5ks5rw4n_gaJpZM4M4B7S.

--
JavaCC Support Team

OK, looks like this can be closed!!


Banner script refactored

I improved the script using find instead of a loop and file renames.

Hello @cesarcosta99 I think removing this loop and add some simple command using shell script with no other dependencies, it would be perfect. My desire was to reduce and make this a little more readable code.
Anyway, Thanks for your attention!


chore: add new "enhance" API to runtime with optimization

As a replacement to "withPresets"

Fixes #536


Mosaic plot (2x2) more information box for stats tab - finalize styling & implement

In ClinEpi, we will use the explanatory info box for the 2x2 mosaic viz tool statistics tab. The box will be closed by default but the user can choose to expand / open the box to read more about which statistics are appropriate to use for their analysis. this info box should be similar in styling to the 2x2 mosaic parameter selection screen
the explanatory information box allows users to read help / additional information so the sure can refer to it while they are making parameter selections for visualizations or apps.
mockups here: https://www.figma.com/file/Su1eNm3Bby85CfrnX42L7q/2x2-table-UI?node-id=317%3A623&t=ZCxlWaPOOG1AbgKr-0

Hey @moontrip we finalized the more info box for the stats tab in the 1/23/2023 EDA UX meeting
See final mockups, which contain approved verbiage: https://www.figma.com/file/Su1eNm3Bby85CfrnX42L7q/2x2-table-UI?node-id=403%3A725&t=sDSejTfcwyglUYu9-0
For styling:

background color - blue, like banners
border - gray, like other containers
toggle collapse/expansion icon - single arrow/caret
info icon - include dark blue info icon

More info here: https://www.figma.com/file/Su1eNm3Bby85CfrnX42L7q/2x2-table-UI?node-id=139%3A233&t=C7dsTpu6Y9mLsmoz-0

Looks good!


Complete switch to Read the Docs

Add Read the Docs badges in the relevant places
Change URLs to point to Read the Docs

Closes #78

Coverage remained the same at 92.348% when pulling de834217da4c6e9c18932ccc047bd42dd91051af on rtd into e40080de46021393eb4e8db7f859a56601f7d317 on develop.


Breadth First Search [CPP]

http://www.geeksforgeeks.org/breadth-first-traversal-for-a-graph/

Can I work on this?

@TarunISCO: Go ahead.

@iiitv/project-maintainers can i work on this issue.

@The-Keshav-Agarwal GFI :+1:


[DOCS] change TF_TRACE -> TF_LOG

The environment variable used/set for getting logs is TF_LOG which you can set to TRACE.
I believe this is just a simple mistake combining TF_LOG and TRACE to accidentally have TF_TRACE in the docs.

@leezen - Just checking to see if this change is a valid change or if I'm off base here. Thanks!

@williamsbdev apologies for the delay, will get someone to review it for ya as soon as possible.


nginx proxy-body-size update in fiab

This is to address https://github.com/cisco-open/flame/issues/226.

Codecov Report

Merging #228 (dd7aa42) into main (c6cc492) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #228   +/-   ##
=======================================
  Coverage   22.41%   22.41%
=======================================
  Files          35       35
  Lines        1593     1593
=======================================
  Hits          357      357
  Misses       1226     1226
  Partials       10       10

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


Better Profile Command

Add a profile Card (Username, Badges, Bio and maybe..banners?) in image format instaed of a ugly embed.

Answser of the round within a card. (Cover, Title, Round Number, Type)

Done in Canary Branch.

Merged in #51

Profile Card (Username, Badges, Bio and maybe..banners?)
Postponed to Ritsu V3.

 Don't worry about this issue.


[MINOR][R] fix R project description

What changes were proposed in this pull request?
update as per this NOTE when running CRAN check
The Title field should be in title case, current version then in title case:
‘R Front end for 'Apache Spark'’
‘R Front End for 'Apache Spark'’

this should go to master & branch-2.4.

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/testing-k8s-prb-make-spark-distribution-unified/9465/
Test PASSed.

Test build #104119 has started for PR 24255 at commit be65d62.

Test build #104119 has finished for PR 24255 at commit be65d62.

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/104119/
Test PASSed.


MCC-764738: switched from http-kit to clj-http

switched from http-kit to clj-http for tracing auto-instrumentation support from motel-java

One question that's out of context otherwise LGTM.
Would it be possible to bump the http-kit dependency to something non-alpha?

Absolutely. In fact, I tried that first to see if we could get tracing support from a later version of http-kit, but it turns out we don't. Feel free to submit a PR if you'd like it updated.


Fixed footer message for web pages

Fix for #346
Changed the copyright info from Apple Inc. to Open Printing on the pages.

Verified in the VM - the footer now shows OpenPrinting copyright.
@Rishabh-792 thank you for the PR! :)


valgrind memcheck detects reads of unitialized memory memory

While debugging an (unrelated) memory leak in my own code using valgrind's memcheck tool, the following error was reported in this library.
Unfortunately I'm not quite in a state to be able to share some code to reproduce this error, but hopefully the output from memcheck will help
==1102663== Use of uninitialised value of size 8
==1102663==    at 0x3D3A64: fast_image_resize::convolution::u8x1::::horiz_convolution (optimisations.rs:113)
==1102663==    by 0x3E72A3: fast_image_resize::resizer::resample_convolution (resizer.rs:285)
==1102663==    by 0x3E3B95: fast_image_resize::resizer::Resizer::resize (resizer.rs:0)
==1102663==    by 0x3B2C9F: vid_dup_finder_common::video_frames_gray::crop_resize_frame (video_frames_gray.rs:382)

I have created a snippet of my calling code: https://gist.github.com/Farmadupe/c88f5d526331163f2741354d83fa1f9d
The resize filter is Lanczos3.
If image dimensions are important, the unitialized read occurs when called with the following arguments:
src_dimensions: 1280x720, src_crop: (left: 0, top: 0, width: 1280, height: 720), new_dimensions: 64x64
src_dimensions: 1280x720, src_crop: (left: 0, top: 80, width: 1280, height: 612),  new_dimensions: 64x64

Could you please attach an example of the source image? I can't reproduce this error with my test images.

Apologies for the very long delay. This issue was raised in error, and was caused due to memory alignment issues in my own code.


Cancel Mesa Terrain only if constructed from SpongeForge

Fixes SpongePowered/SpongeForge#1834
This restores vanilla behavior if BiomeMesa is constructed without MixinBiome::buildPopulators being called, which to my knowledge, only gets called under Sponge world generators.
If this is bypassed e.g. mods not knowing about us extracting the Mesa biome into a decorator/populator then it defaults to vanilla's.

@Fla5hFyre Test Build:
TestBuild.jar.zip

https://github.com/SpongePowered/SpongeCommon/commit/ad4859eeff55a9f883a93cb43c3b6657a4f40e4a