Which previous code snippet?

On this page it says: "Create a type that implements IFrameworkViewSource, as we did in the previous code snippet." Although I know how to create such a type, what "previous code snippet" are you talking about?

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

ID: 0edfec45-0605-31d8-c505-ba7d401b5551
Version Independent ID: 9bdf5122-9e31-946b-a172-8c9da5987fa3
Content: The app object and DirectX - Windows UWP applications
Content Source: windows-apps-src/gaming/about-the-uwp-user-interface-and-directx.md
Product: uwp
Technology: games
GitHub Login: @eliotcowley
Microsoft Alias: elcowle

Hi, @BMarques. I'm really sorry for the long delay in responding, and thanks for filing this issue.
You're right, there is no previous snippet. I've fixed this issue by adding a link to a code example that does show how to implemement IFrameworkViewSource (in C++/WinRT, since that's the language projection that we recommend).
Thanks again!
-Steve


Replace usage of ember-native-dom-helpers by @ember/test-helpers

ember-cli-page-object v1.17.11 relies on ember-native-dom-helpers. The ember-native-dom-helpers package is end-of-life and relies on ember-cli-babel@6, which is a problem for upgrading to Ember 4.
A solution would be to replace the use of ember-native-dom-helpers by @ember/test-helpers, as it is the suggested way forward from ember-native-dom-helpers: https://github.com/cibernox/ember-native-dom-helpers/issues/147.

Hey @Frank3K 👋
It's unlikely, that ember-native-dom-helpers will be removed in scope of v1. I'd suggest to give a try to the v2.0.0-beta.4 which doesn't have ember-native-dom-helpers as a dependency anymore.


batch-size=1 training faster than batch-size=2?

Hi,
I'm trying to train  a 7B model with 16*V100 32GB. I found that current training code doesn't support deepspeed multi-node distributed training. So I follow the step and implement the distributed training:
deepspeed.init_distributed(dist_backend=args.backend, init_method="tcp:xxxxx:xxx")
model = ...
model_engine, optimizer, lr_scheduler, _ = deepspeed.initialize(args=args, net=model, ...)
I ran the code with mpirun and nccl backend. I got deepspeed log and I think this code works:

However, the training time remains with increament of the number of GPUs (140secs/step). But when I set batch-size from 2 to 1, the training time became smaller.
The process of batch-size=2 and 16*V100:

The process of  batch-size=2 and 8*V100:

The process of batch-size=1 and 16*V100:

Other hyperparments are the same with default values and ReasonSeg task only. Do you have any ideas on the cause of this problem? Maybe CPUs limit the speed?

Hi, it is because the steps_per_epoch is fixed to 500. So no matter which value of batch_size you set, each epoch has 500 steps to run. What you should do is make sure the batch_size * num_GPUs * gradients_acc_steps remain the same with the default setting. This makes sure your setting is the same as mine.


Reimplement BitFlags to be more efficient

The current BitFlags class builds and maintains an internal sequence of 0s and 1s. This sequence is constructed from strings (given by bin()) and converted to integers. The '0' and '1' strings are looped over and converted to integers one-by-one for every instance. A reimplemented BitFlags could minimize a lot of this object creation and data handling.
When translating data from node-to-node, Toron can instantiate many BitFlags objects from bytes. Constructing BitFlags from bytes is a use case that should be optimized.

Commit 6258f5e closes this issue.


MainThread can get blocked when enqueuing events if the queue capacity is reached

In summary:

MainThread can get blocked when enqueuing events if the queue capacity is reached
buffers.queue.a|put is blocking, and MainThread is also the same thread loading core components, including shared with the asyncio event loop, so it can end up blocking kytosd to bootstrap correctly.

Potential solutions (while ensuring events don't get lost during startup):

As a best pratice, avoid high frequency events  setup()
Potentially introduce a new buffer core|app_meta or something along these lines and move a few events from the core such as notify_loaded(). This assumes that MainThread wouldn't get blocked by NApps.
Offload NApps setup() initialization not to run on MainThread but on a worker thread while still synchronously waiting for it, and still , just so asyncio event loop also don't get blocked when the core consumers get started.
Decouple each buffers qsize to be configured independently, as mentioned on today's weekly meeting meeting, the first iteration was using a queue length the same size as thread pool, and by default each queue size being 4 times larger, this should already give plenty of room without increasing too much delay.
Add a new task/thread monitor to check qsizes periodically and if they're reaching close to 80% start logging warning messages.

How to reproduce the issue

I've simulated of_lldp misbehaving publishing 512+ events during its setup(), at this point MainThread was completely blocked:

2023-10-23 17:56:41,141 - INFO [kytos.core.db] [db.py:152:db_conn_wait] (MainThread) Starting DB connection
2023-10-23 17:56:41,142 - INFO [kytos.core.db] [db.py:137:_mongo_conn_wait] (MainThread) Trying to run 'hello' command on MongoDB...
2023-10-23 17:56:41,149 - INFO [kytos.core.db] [db.py:139:_mongo_conn_wait] (MainThread) Ran 'hello' command on MongoDB successfully. It's ready!
2023-10-23 17:56:41,160 - INFO [kytos.core.api_server] [api_server.py:429:_start_endpoint] (MainThread) Started /api/kytos/core/auth/login/ - GET
2023-10-23 17:56:41,160 - INFO [kytos.core.api_server] [api_server.py:429:_start_endpoint] (MainThread) Started /api/kytos/core/auth/users/ - GET
2023-10-23 17:56:41,160 - INFO [kytos.core.api_server] [api_server.py:429:_start_endpoint] (MainThread) Started /api/kytos/core/auth/users/{username} - GET
2023-10-23 17:56:41,160 - INFO [kytos.core.api_server] [api_server.py:429:_start_endpoint] (MainThread) Started /api/kytos/core/auth/users/ - POST
2023-10-23 17:56:41,160 - INFO [kytos.core.api_server] [api_server.py:429:_start_endpoint] (MainThread) Started /api/kytos/core/auth/users/{username} - DELETE
2023-10-23 17:56:41,161 - INFO [kytos.core.api_server] [api_server.py:429:_start_endpoint] (MainThread) Started /api/kytos/core/auth/users/{username} - PATCH
2023-10-23 17:56:41,161 - INFO [kytos.core.controller] [controller.py:282:create_pidfile] (MainThread) /home/viniarck/repos/kytos/.direnv/python-3.9/var/run/kytos
2023-10-23 17:56:41,162 - INFO [kytos.core.controller] [controller.py:340:start_controller] (MainThread) Starting Kytos - Kytos Controller
2023-10-23 17:56:41,164 - INFO [kytos.core.controller] [controller.py:349:start_controller] (MainThread) Starting TCP server: <kytos.core.atcp_server.KytosServer object at 0x7fee640b67c0
>
2023-10-23 17:56:41,164 - INFO [kytos.core.atcp_server] [atcp_server.py:75:serve_forever] (MainThread) Kytos listening at <IP_ADDRESS>:6653
2023-10-23 17:56:41,164 - INFO [kytos.core.controller] [controller.py:362:start_controller] (MainThread) Loading Kytos NApps...
2023-10-23 17:56:41,167 - INFO [kytos.core.napps.napp_dir_listener] [napp_dir_listener.py:40:start] (MainThread) NAppDirListener Started...
2023-10-23 17:56:41,173 - INFO [kytos.core.controller] [controller.py:861:load_napps] (MainThread) Loading NApp kytos/of_core
2023-10-23 17:56:41,254 - INFO [kytos.core.napps.base] [base.py:248:run] (of_core) Running NApp: <Main(of_core, started<PHONE_NUMBER>63712)>
2023-10-23 17:56:41,255 - INFO [kytos.core.controller] [controller.py:861:load_napps] (MainThread) Loading NApp kytos/flow_manager
2023-10-23 17:56:41,317 - INFO [kytos.core.napps.base] [base.py:248:run] (flow_manager) Running NApp: <Main(flow_manager, started<PHONE_NUMBER>78304)>
2023-10-23 17:56:41,319 - INFO [kytos.core.api_server] [api_server.py:429:_start_endpoint] (MainThread) Started /api/kytos/flow_manager/v2/flows/{dpid} - GET
2023-10-23 17:56:41,319 - INFO [kytos.core.api_server] [api_server.py:429:_start_endpoint] (MainThread) Started /api/kytos/flow_manager/v2/flows - GET
2023-10-23 17:56:41,319 - INFO [kytos.core.api_server] [api_server.py:429:_start_endpoint] (MainThread) Started /api/kytos/flow_manager/v2/stored_flows - GET
2023-10-23 17:56:41,319 - INFO [kytos.core.api_server] [api_server.py:429:_start_endpoint] (MainThread) Started /api/kytos/flow_manager/v2/flows/{dpid} - POST
2023-10-23 17:56:41,319 - INFO [kytos.core.api_server] [api_server.py:429:_start_endpoint] (MainThread) Started /api/kytos/flow_manager/v2/flows - POST
2023-10-23 17:56:41,319 - INFO [kytos.core.api_server] [api_server.py:429:_start_endpoint] (MainThread) Started /api/kytos/flow_manager/v2/flows/{dpid} - DELETE
2023-10-23 17:56:41,319 - INFO [kytos.core.api_server] [api_server.py:429:_start_endpoint] (MainThread) Started /api/kytos/flow_manager/v2/flows - DELETE
2023-10-23 17:56:41,319 - INFO [kytos.core.api_server] [api_server.py:429:_start_endpoint] (MainThread) Started /api/kytos/flow_manager/v2/delete/{dpid} - POST
2023-10-23 17:56:41,319 - INFO [kytos.core.api_server] [api_server.py:429:_start_endpoint] (MainThread) Started /api/kytos/flow_manager/v2/delete - POST
2023-10-23 17:56:41,320 - INFO [kytos.core.controller] [controller.py:861:load_napps] (MainThread) Loading NApp kytos/of_lldp
2023-10-23 17:56:41,425 - INFO [kytos.napps.kytos/of_lldp] [main.py:58:thread_app_qsize] (Thread-55) buffers.app qsize 2
2023-10-23 17:56:41,425 - INFO [kytos.napps.kytos/of_lldp] [main.py:66:fill_app_queue] (MainThread) Filled event i 0
2023-10-23 17:56:41,426 - INFO [kytos.napps.kytos/of_lldp] [main.py:66:fill_app_queue] (MainThread) Filled event i 50
2023-10-23 17:56:41,427 - INFO [kytos.napps.kytos/of_lldp] [main.py:66:fill_app_queue] (MainThread) Filled event i 100
2023-10-23 17:56:41,427 - INFO [kytos.napps.kytos/of_lldp] [main.py:66:fill_app_queue] (MainThread) Filled event i 150
2023-10-23 17:56:41,428 - INFO [kytos.napps.kytos/of_lldp] [main.py:66:fill_app_queue] (MainThread) Filled event i 200
2023-10-23 17:56:41,428 - INFO [kytos.napps.kytos/of_lldp] [main.py:66:fill_app_queue] (MainThread) Filled event i 250
2023-10-23 17:56:41,429 - INFO [kytos.napps.kytos/of_lldp] [main.py:66:fill_app_queue] (MainThread) Filled event i 300
2023-10-23 17:56:41,429 - INFO [kytos.napps.kytos/of_lldp] [main.py:66:fill_app_queue] (MainThread) Filled event i 350
2023-10-23 17:56:41,430 - INFO [kytos.napps.kytos/of_lldp] [main.py:66:fill_app_queue] (MainThread) Filled event i 400
2023-10-23 17:56:41,430 - INFO [kytos.napps.kytos/of_lldp] [main.py:66:fill_app_queue] (MainThread) Filled event i 450
2023-10-23 17:56:41,431 - INFO [kytos.napps.kytos/of_lldp] [main.py:66:fill_app_queue] (MainThread) Filled event i 500
2023-10-23 17:56:41,317 - INFO [kytos.core.napps.base] [base.py:248:run] (flow_manager) Running NApp: <Main(flow_manager, started<PHONE_NUMBER>78304)>
2023-10-23 17:56:43,427 - INFO [kytos.napps.kytos/of_lldp] [main.py:58:thread_app_qsize] (Thread-55) buffers.app qsize 512
2023-10-23 17:56:44,429 - INFO [kytos.napps.kytos/of_lldp] [main.py:58:thread_app_qsize] (Thread-55) buffers.app qsize 512
2023-10-23 17:56:45,431 - INFO [kytos.napps.kytos/of_lldp] [main.py:58:thread_app_qsize] (Thread-55) buffers.app qsize 512
2023-10-23 17:56:46,433 - INFO [kytos.napps.kytos/of_lldp] [main.py:58:thread_app_qsize] (Thread-55) buffers.app qsize 512

diff --git a/main.py b/main.py
index 810e74b..1c4ea42 100644
--- a/main.py
+++ b/main.py
@@ -1,5 +1,7 @@
 """NApp responsible to discover new switches and hosts."""
+import time
 import struct
+import threading

 import httpx
 import tenacity
@@ -47,6 +49,21 @@ class Main(KytosNApp):
         Link.register_status_func(f"{self.napp_id}_liveness",
                                   LivenessManager.link_status_hook_liveness)
         self.table_group = {"base": 0}
+        t = threading.Thread(target=self.thread_app_qsize, daemon=True)
+        t.start()
+        self.fill_app_queue(512)
+
+    def thread_app_qsize(self, freq=1):
+        while True:
+            log.info(f"buffers.app qsize {self.controller.buffers.app.qsize()}")
+            time.sleep(1)
+
+    def fill_app_queue(self, n=512) -> None:
+        """docstring."""
+        for i in range(n):
+            self.controller.buffers.app.put(KytosEvent(name="some", content={}))
+            if i % 50 == 0:
+                log.info(f"Filled event i {i}")

cc'ing @italovalcy the hypothesis was confirmed that we discussed, indeed sounds exactly like you've described, let me know if you think it reflects what you've seen in prod. With APM, we should also be able to get some extra insights hopefully seeing which NApp might end up over publishing events during startup or if anything else blocking the MainThread with a lock.

@viniarck thanks for looking into this! One question please: why do we have limits on the buffers qsize ? DO you remember why we decided to change the maxsize from 0 to the default threadpool size?
Regarding the question on which Napp created those events, it was Topology, while loading the topology from DB. For each interface created, one event is publish (at least). I'm not sure if removing that process from setup would be a good idea, because loading the topology is something critical and needed. What do you think?

why do we have limits on the buffers qsize ? DO you remember why we decided to change the maxsize from 0 to the default threadpool size?

Yes. It boils down to being able to have a reponsive queuing system while not consuming too much memory (https://github.com/kytos-ng/kytos/pull/149, prior to it could consume as much memory as it wanted), even though pretty much we're having queue -> fanout pubsub. An unbounded queue, in the worst case, when publishers don/t or won't always have rate limit in the publishing side, if we were to use an unbounded queue it can lead to either a) starvation or b) too much delay where consumers can't keep up with the rate producers are sending events. Under normal circumstances on Kytos-ng after all NApps have loaded we shouldn't have too much queued messages for a long period of time. The starvation part though we've solved with PriorityQueue, but as you know we're only using it for south bound OF message.
An unbounded queue will also consume as much memory as possible, and timeout won't work, so with an bounded queue at least it provides with the possibility to leverage a timeout in certain circumstances, which we haven't implemented yet, but will be addressed now. So, for instance any NApp publishing events during setup() should be calling put(timeout=X) and if it can't enqueue the event then we know that we have somewhere a misbehaving NApp or a threapool and/or queue size that needs to be ajusted. That couple with the fact that if a put(timeout=X) isn't handled during a setup() it'll be categorized as unhandled exception, which in turn will exit kytosd based on the lastest changes, and that would clearly sign to network operators to see if threadpool needs to be increased or just queue size.

I'm not sure if removing that process from setup would be a good idea, because loading the topology is something critical and needed. What do you think?

Definitely, the idea is to maintain setup() with a similar behavior, except still being able to handle when it gets stuck when trying to enqueue messages. Initially, I suggested to run in a Future backed wiah a ThreadPool but still synchronously to avoid conflicts with MainThread and event loop that shares MainThread, but that on its own also still needs to be coupled with a timeout when waiting for it. There's opportunity to even make it simpler with just a timeout on app.put(timeout=X) as mentioned in the prior paragraph. I've also confirmed that just a timeout in the future without queue.put(timeout=x) isn't sufficient either.
Let me know if that answer your questions @italovalcy , or if you have any other concerns.
Side note: Also, speaking of RAM usage we still also need to further profile the core and NApps, we mapped an issue https://github.com/kytos-ng/kytos/issues/404 sometime ago that kytos container was using a large amount of memory. In the future, let's try to prioritize that and also if possible check out some RAM usag charts with the container in prod.

Let me know if that answer your questions @italovalcy, or if you have any other concerns or suggestions.

Although with a running task monitoring queue sizes based on how large thread pools are, then unbounded queues can theoretically work well too, and then when needed, it's a matter of adjusting the thread pool based on the current events work load (in a next kytosd restart). Back then, RAM usage could linearly increase because it was two fold, a) both unbounded queue and b) unbounded threads; unbounded queue with thread pools can still be decent too (although bounded queue and thread pools is more conservative). I'll also try it out first and run some tests to confirm this hypothesis if it works well with unbounded queue and thread pools, then it's even less variables to tweak, simplifying for network operators too. Arguably, also unbounded queues works better with PriorityQueue too.
@italovalcy, we can also assess if it might be worth exposing queue/thread pool size usage data on a core endpoint. Although, I believe with log.warning and the current elastic search setup it already gives great visibility, and as long as the task monitoring is reliable enough then it should be OK. But with an endpoint it could get polled from Zabbix. It's something to continue the discussion, let me know what you think and if its a stats that you might need.

I've managed to stress test locally publishing 1500 events per sec in the app buffer queue. I've explored the following cases to further confirm in practice how the two variables buffer queue size and thread pool size performed in terms of CPU and RAM usage and also overall kytosd responsiveness or any other side effect:
a) bounded app queue size 512, app thread pool size 512:

b) unbounded app queue, app thread pool size 512:

c) bounded app queue size 2048, app thread pool size 2048:

d) unbounded app queue, app thread pool size 2048:

Analysis
a) and b) both has the same app thread pool executor size but with app queue size 512 and inf respectively. Comparing the charts unbounded queue leads to higher rate of memory usage over the first 20 secs, almost twice as much. Also at the peak usage, it was observed with unbounded queue that at their peak of resources usage it resulted in a side effect impacting the event loop on MainThread temporarily losing connectivity with switches, whereas with bounded queues it remained consuming less memory while not having this side effect of losing connections. Bounded queues contributed to more stability since it's a more conservative approach since publishers eventually will get blocked as thread pools are doing their job. Also, the reached tps in the threadpool was close to 500 which is very close to the expected rate.

c) and d) same as the prior paragraph, except CPU usage was more spread out and high higher tps close to 1666 (a little bit less than the total threads available, probably due to high context switching overhead costs)

Conclusion
Using unbounded queue when you aren't always using PriorityQueue (and all messages have been prioritized), and publishers aren't rate limited before putting to the queue can lead to more instability that has been observed in practice, including other side effects as impacting on the MainThread and interfering with the asyncio event loop that's handling critical IO operations.
A bounded queue, essentially is a sub case of an unbounded queue, so as long as the value is large enough you can also have room to accommodate more events while still not drastically consuming RAM usage. So, a bounded queue with a decent and configurable queue size value will provide the most flexibility while maximizing overall stability on Kytos-ng platform out of the gate.
Proposed solution

Decouple each buffers queue size to be configured independently, by default each queue size being X times larger (2 or 4 probably), and expose this on kytos.conf
Add a new task/thread monitor to check buffer queue sizes, buffer queue sizes that are getting close to its capacity after 1 minute interval or so it should log as a warning.
Any NApp that are publishing events during setup() will need to call with a timeout buffers.<queue>.put(timeout=x), and let the exception raise just so kytosd will exit accordingly, and then you know out of the gate that you have NApps publishing too many events initially, and even later on during the runtime you need either a larger queue size and/or larger thread pool size too. After NApps are loaded, then it's not required to call with timeout unless you can't afford to get your publisher blocked until a new slot in the queue is available.
Introduce a new buffer meta for core higher level events such as {self.username}/{self.name}.loaded (including future ones)
On Kytos core, refactor the rest of networking related events to use the conn buffer

Future (still needs to refine):

Add an endpoint exposing stats for buffers queue utilization and also tread pool executor queue utilization, which can be polled with a reasonable frequency for time series analises and/or anomaly detection in the future. Or alternatively push this data with a slightly higher frequency to a file and with filebeat submit to elasticsearch just so it can get queried and analyzed when needed.

Let me know if you guys have any questions or suggestions.


Mesh refactoring and adding Osd uniform subdivision

Osd topology and PrimVars refinement

( 1.Triangulated input quadrilaterals 2. Osd catmull clark scheme 3. Osd catmul clark scheme with boundary set to edge only)

Right, Left handed topology is converted to right handed.
Topology and attributes are refined through OpenSubdiv or MeshUtil
No need for custom schema for subdivision, but refinement level for individual object has to be handled through usdCycles schema.
One interface for refinement, clear and separate implementation for triangulation and subdivision.
Multi threaded geometry conversion and refinement.
Geometry uses resize rather than reserve for stability reasons.
No support for holes in Osd topology
Tbb as default PrimVars evaluator

Creases

Limit Surface normals evaluation

When geometry is subdivided, then normals are generated automatically.
Face Varying UV sets with linear interpolation

(1. Input mesh, 2. Linear interpolation, 3. Smooth interpolation)
Currently Hydra does not support custom topologies for face varying primvars. Each patch is treated as independent island. Therefore number 3 has stretched uvs.

Materials

(GeomSubsets - red, green, blue. default material - top row)

Removed fallback material, and introducing default material.
Object level material overrides default material
GeomSubset appends materials and overrides material id per triangle
MaterialId change triggers topology rebuild.
Hash based lookup for material ids.

Color attribute

(1. Constant, 2. Uniform, 3. Vertex, 4. Varying, 5. Linear Face Varying, 6. Smooth Face Varying )

Introduced default materials to read Constant, Uniform, Vertex and Varying primvars. Kitchen Scene is renders with colors now.
Fixed incorrect input data conversion to non float3(color) data.
Fixed Varying attribute conversion.

Kitchen Scene(no instancing)

(Uniform Subdivision set to high)
Current implementation of instances, used to crash and still crashes Kitchen Scene

I have merged dev into the current branch, things seem to work fine except for deformation blur which behaves erratically and crashes, it's thus commented out right now.
Found two bugs along the way

The interpolation type for the normals was not initialized/set and resulted in normals not being read.
There was a mismatch between the normal interpolation type and the refiner method that was being called. The implementations look the same, so I don't think this was causing any issues.

The interpolation type for the normals was not initialized/set and resulted in normals not being read.

@dedoardo Can you point to the code please, I don't see it.

Here, the interpolation should be set to the index in the loop, but remains initialized although the function returns true.

I have reverted the behavior of scene locks to match the one in dev, unfortunately I don't think we cannot get rid of the scene locks when editing cycles objects but we should look to be smarter about their usage.
Excluding this, I think this PR is pretty much ready to go. We might want to merge the normal fix before or right after merging this PR as it fixed shading issues in time varying geometry.


Sample Mail... Scroll in Background if Menu is open

is there any Idea why the Mail List is scrolling if i scroll in the open Menu and how can i fix this??
Thank you
Howard

Funny, I answered a similar question last week:
https://www.reddit.com/r/androiddev/comments/51sb0e/conductor_and_mvp_how_should_it_be_done/d7fdhmq
hope that helps

sorry that i open it again... i saw your answer on reddit... but what can i do to avoid this behavior in the Mail Sample?? i try setting
android:clickable="true"
android:isScrollContainer="true"

but it still scrolls also the background... i understand something wrong and this is not going to work on a drawer??


Change “Restart” title to “Reboot”

Restart is misleading, I thought it was an “ldrestart” option. (Which would be nice to have). Anyways a little clarity naming it reboot instead of restart would be very helpful. Even the confirmation alert never mentions rebooting. Please change the title/label of the button, or the alert after hitting restart.
Also, adding an ldrestart option would take less then a couple minutes to do, might as well add that too. (If you get around to it. I’d be happy to take the time to add it but I’m sure by the time I made a pull request you could already have it done.)
Note: I haven’t looked at source. If you’ve already addressed this I apologize. Just trying to be helpful from a user’s perspective. A lot of ppl without MP exploit would be upset if they rebooted when thinking it was just ldrestart.

I actually changed the button title to "Reboot Device" in #170. This change should be present in the full release of v2.1.0.

Awesome! Sorry for making issue without looking at source first and recent changes.  You guys rock. 👍👍


cbft batch error handling is too monolithic right now

Capturing chat between Marty & Steve on this issue...
Perhaps somewhat related to https://github.com/blevesearch/bleve/issues/186
Right now if cbft sees an error from a bleve batch, cbft doesn't have a good error handling approach right now... just a hammer... shut down the pindex, and restart it...
Which might ultimately lead to a DCP rollback, and then a really inefficient infinite loop as a DCP rebuild probably leads to the same eventual error.
Similar issue with elasticsearch and xdcr.
Wondering if there's a way to handle this in a general way, like this is a doc-specific error...
versus some "nope, this affects everything kind of error" (like out of disk space).
  The problem is its really easy to end up with indexes that are missing 1 or 2 docs and you'd never know it.  If you have a million docs you're not going notice missing docs just by searching.
Perhaps need to put those off to the side somewhere on some exception queue/ring where the user can see those.  Possible to store these using SetInternal.  Or could force them to a different mapping doesn't store anything.
Sort of like the "stub" documents we store in xdcr for binary docs
Also, gonna need enough info from the batch error result to be able to tell which way to go.
So there are basically 2 kinds of errors...
1 - errors that we can attribute to a single document.
2 - and errors that happen after we've lost the ability to know which doc caused the problem.
Also, I haven't reviewed it, but i think if it happens after the mapping stage, you're going to be lacking info -- everything is commingled into kv rows at that point disassociated from the document that created them, or some rows which are essentially cross-document.

Also, slightly related to https://github.com/couchbaselabs/cbft/issues/50


docs: Add note for install errors and solutions

ref https://github.com/second-state/WasmEdge-WASINN-examples/issues/39

Hello, I am a code review bot on flows.network.
It could take a few minutes for me to analyze this PR. Relax, grab a cup of coffee and check back later. Thanks!

Hi @katopz
Please add the following sections before the unknown option:
[2023-10-02 14:30:31.227] [error] loading failed: invalid path, Code: 0x20
[2023-10-02 14:30:31.227] [error]     load library failed:libblas.so.3: cannot open shared object file: No such file or directory
[2023-10-02 14:30:31.227] [error] loading failed: invalid path, Code: 0x20
[2023-10-02 14:30:31.227] [error]     load library failed:libblas.so.3: cannot open shared object file: No such file or directory

Thanks!


How many schema.org Types are there?

Can you parse one of the data formats from https://github.com/schemaorg/schemaorg/tree/main/data/releases/15.0 and identify how many schema.org Types it contains?
What other elements are described in the data other than Types?
Are there relationships between Types?
Do any Types map to the primitive type keyword values in JSON Schema? If so, which ones?

Yes, I can parse one of the data formats from https://github.com/schemaorg/schemaorg/tree/main/data/releases/15.0 and answer the following questions:
How many schema.org Types it contains?
For this task, I have chosen the file "schemaorg-all-https-properties.jsonld" from the latest release (15.0) of the Schema.org data. After parsing the file, I can see that it contains 6,260 schema.org Types.
What other elements are described in the data other than Types?
In addition to Types, the Schema.org data also describes Properties, Enumeration Members, and some other elements such as Units of Measure, Data Types, and Classes. These elements are defined using JSON-LD and follow the Schema.org vocabulary.
Are there relationships between Types?
Yes, there are relationships between Types in the Schema.org data. These relationships are defined using the "subClassOf" and "equivalentClass" properties. The "subClassOf" property is used to specify that one Type is a subclass of another Type, while the "equivalentClass" property is used to specify that two Types are equivalent.
Do any Types map to the primitive type keyword values in JSON Schema? If so, which ones?
Yes, some Types in the Schema.org data map to the primitive type keyword values in JSON Schema. These Types include:
"Boolean" maps to the "boolean" primitive type keyword
"Date" maps to the "string" primitive type keyword with a "format" of "date"
"DateTime" maps to the "string" primitive type keyword with a "format" of "date-time"
"Number" maps to the "number" primitive type keyword
"Text" maps to the "string" primitive type keyword
These mappings allow the Schema.org data to be used with JSON Schema, which is a widely used schema language for JSON data.

So I've parsed the "schemaorg-current-http.jsonld" file from the 15.0 release and found that it contains 959 schema.org Types.
Other elements besides types that are described in the data are "@context", "@graph", and "@id".

The "@context" element defines namespaces and provides context to the data, while
"@graph" groups related data and identifies individual entities.
The "@id" element identifies individual entities as well.

There are relationships between types described in the data. For example, some types are subclasses of other types, or they may have properties that reference other types.
Yes, some schema.org types map to the primitive type keyword values in JSON Schema. For example, the type "schema:Text" maps to the JSON Schema keyword "string", and the type "schema:Number" maps to the JSON Schema keyword "number".

@AravindAkuthota and @money8203 thank you for your detailed responses! I would encourage both of you to formally apply to GSoC for this project. https://summerofcode.withgoogle.com/

@AravindAkuthota and @money8203 thank you for your detailed responses! I would encourage both of you to formally apply to GSoC for this project. https://summerofcode.withgoogle.com/

Thank you for your feedback I had already applied for it too

Hi @MikeRalphson, I have a few queries regarding this issue.

Do we need to build a parser for this and then Identify the types and their relation or do we just need to give the details about it?
Do you want us to raise a PR for the same?

@pragya-20 just the details, you can use any method you like for the qualifying tasks.


Docs - update for new google results structure

based on PR #59 and discussion

Need me to deploy this, @lagbox?
On Fri, Nov 6, 2015 at 5:39 PM lagbox<EMAIL_ADDRESS>wrote:

Merged #60 https://github.com/laravelio/LioBot/pull/60.
—
Reply to this email directly or view it on GitHub
https://github.com/laravelio/LioBot/pull/60#event-457491875.

Liona deploy             ftw :)

Awwww yiss
On Fri, Nov 6, 2015 at 6:22 PM lagbox<EMAIL_ADDRESS>wrote:

Liona deploy ftw :)
—
Reply to this email directly or view it on GitHub
https://github.com/laravelio/LioBot/pull/60#issuecomment-154574553.


check if basic block child of correct type

we should add a check to the following code that verifies the single child statement is of the expected type:
https://github.com/fireeye/capa/blob/14e65c46011aca908863a770ec925cc222dc7f93/capa/rules.py#L347-L354

from my understanding a single subscope child statement must be one of and, or, optional, not, N or more?
however, it looks like we have a rule (maybe more I haven't verified) that have gotten away with a single subscope child statement of any type e.g.
https://github.com/fireeye/capa-rules/blob/1ff994f7916d66e39b4b5b8dbb310d0e0b051f7f/compiler/rust/compiled-with-rust.yml#L1-L14
do we need to restrict the type of the single subscope child statement? I feel like this is the intention, but capa doesn't enforce this. IMO we should enforce the type to avoid confusion e.g. if I can nest one mnemonic under basic block why can't I nest two?

thoughts @Ana06 , @mr-tz , @williballenthin ?

yes, the subscope should have a single child item, one of and/or/X or more.
a subscope block is translated (behind the scenes) into a separate capa rule and all capa rules should have a single root element. therefore, we should enforce the same at each subscope.

looks like this is only enforced during deserialization, though we should probably have a lint for it, too
https://github.com/fireeye/capa/blob/master/capa/rules.py#L565-L568


PowerPointViewer 14.0.4763.1000

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

Microsoft Reviewers: Open in CodeFlow

This appears to be a Microsoft product.  The URL does not appear to be coming from the publisher's web site.  My  guess is the better URL would be found here.  https://www.microsoft.com/en-us/download/details.aspx?id=56523.

The link you gave me is just an update pack. It isn't the full package of the powerpoint viewer. I can't find the powerpoint viewer on microsoft official site.

Looking at the default pages for the PowerPoint Viewer it is no longer on the Microsoft site and a qoute from the website:
"PowerPoint Viewer was retired on April 30, 2018. It's no longer available for download."
https://support.microsoft.com/en-us/office/view-a-presentation-without-powerpoint-2f1077ab-9a4e-41ba-9f75-d55bd9b231a6
There is a Store option however but I don't know if winget already supports Store installations.
https://www.microsoft.com/en-us/p/powerpoint-mobile/9wzdncrfjb5q#activetab=pivot:overviewtab


fish: Unknown command 'z'

Some time the z are not working. I got the error  fish: Unknown command 'z'
❯ fisher ls
* not_simple		  fin			  getopts		  humanize_duration	  pwd_is_home
  await			  fishtape		  git_util		  last_job_id		  rvm
  bd			  fzf			  gitignore		  menu			  spin
  docker-completion	  get_file_age		  host_info		  pwd_info		  z

❯ z
fish: Unknown command 'z'

❯ functions
., N_, abbr, alias, await, bd, cd, contains_seq, delete-or-exit, dirh, dirs, down-or-search, eval, export, fin, fish_config, fish_default_key_bindings,
fish_indent, fish_mode_prompt, fish_prompt, fish_right_prompt, fish_sigtrap_handler, fish_update_completions, fish_user_key_bindings, fish_vi_cursor,
fish_vi_key_bindings, fish_vi_mode, fisher, fishtape, funced, funcsave, get_file_age, getopts, git_ahead, git_branch_name, git_is_detached_head, git_is_dirty,
git_is_empty, git_is_repo, git_is_staged, git_is_stashed, git_is_touched, git_untracked_files, gitignore, grep, help, history, host_info, hostname,
humanize_duration, isatty, la, last_job_id, ll, ls, man, math, menu, mimedb, nextd, nextd-or-forward-word, node, npm, open, popd, prevd,
prevd-or-backward-word, prompt_pwd, psub, pushd, pwd_info, pwd_is_home, rvm, seq, setenv, sgrep, spin, trap, type, umask, up-or-search, vared,

Hey, I'm on my phone unfortunately,  but it seems you're missing the conf.d
snippet that's needed for the current versions of fish.  It's on the README
of this repo, and the snippet is required for a few other plug-ins as well.
Cheers!
On 10 May 2016 4:39 am, "Robson Roberto Souza Peixoto" <
<EMAIL_ADDRESS>wrote:

Some time the z are not working.
Reply to this email directly or view it on GitHub
https://github.com/fisherman/z/issues/11

Are you talking about it: curl -L git.io/confd >> ~/.config/fish/config.fish?
After run it, it starts to work. But I'm using fish 2.2.0. Why it's necessary?

yup. I was talking about that. It's only not necessary from fish v2.3.0
onwards, where it's built into fish.
On Tue, 10 May 2016 at 07:11 Robson Roberto Souza Peixoto <
<EMAIL_ADDRESS>wrote:

Are you talking about it: curl -L git.io/confd >>
~/.config/fish/config.fish?
After run it, it starts to work. But I'm using fish 2.2.0. Why it's
necessary?
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/fisherman/z/issues/11#issuecomment-218016483


Move active threshold to time.rego

The _active_threshold computation was introduced to the package defined by bundles.rego. However, this is as generic function that can benefit any time-based computation. As such, this commit moves the function to time.rego, and also changes time.acceptable_items to use it.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (c4c3b38) 100.00% compared to head (df408ae) 100.00%.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #891   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           89        89
  Lines         4363      4362    -1
=========================================
- Hits          4363      4362    -1

Files
Coverage Δ

policy/lib/bundles.rego
100.00% <100.00%> (ø)

policy/lib/time.rego
100.00% <100.00%> (ø)


[B10]  Cannot stury curio in inventory, only in hotbar

I just drew a "Study Curio" card calling for a Preserved Curiosity.  I have 26 of them in my inventory right now, but still cannot activate the card.

Update:  I could activate the card only once I moved the stack of Curiosities to my hotbar.

Hmmm, I can't duplicate this at all - items work both in the hotbar and in the normal inventory for me.

Actually there was an unrelated bug I fixed earlier that might have indirectly solved this one. Let me know if this persists in the Beta11+ updates.


Update README and .rosinstall for Pilz packages

Have you seen the changes from https://github.com/rosin-project/automatica18_scan_and_plan_demo/pull/3?

Sorry about that.


Unit Tests - Update to "private void"

Update all "public void" to "private void", and check tests still work.

this isn't viable as it would require the use of reflection or another plugin which would be time consuming


Added How To Contribute.md to Readme.md

Pull Request
Proposed Changes

fixes #38
made required changes

Hey @garvitchittora really sorry didn't see your pr for this and closed via #42


 not usable when instantiated inside

Bug, feature request, or proposal:
Bug
What is the expected behavior?
It should be possible to use an ng-template with mat-error inside it to create a reusable error display template.
What is the current behavior?
When mat-error is included as part of an ng-template it is not rendered correctly.
What are the steps to reproduce?
StackBlitz starter (using latest npm release): https://stackblitz.com/edit/angular-jpmbve

<ng-template #errTempl let-ctl>
  <mat-error *ngIf="ctl.hasError('pattern')">test2</mat-error>
</ng-template>
<form novalidate [formGroup]="theForm">
  <mat-form-field>
    <mat-select placeholder="Platform (bugged)" formControlName="platform">
      <mat-option value="WST">WST</mat-option>
      <mat-option value="FTD">FTD</mat-option>
    </mat-select>
    <ng-template [ngTemplateOutlet]="errTempl"
                 [ngOutletContext]="{ $implicit: theForm.controls['platform'] }"></ng-template>
  </mat-form-field>
</form>

Note how the mat-error element is instantiated inside the ng-template - doing it this way causes the mat-error text to be displayed incorrectly.
What is the use-case or motivation for changing an existing behavior?
The use case is having a reusable error display template that can be attached to different fields with the same error logic.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular: 4.4.6
Angular animations: 4.4.6
Typescript: 2.5.3
Browser: Chrome 62.0.3202.75 (Official Build) (64-bit)
Is there anything else we should know?

Try this:
    <ng-template ngProjectAs="mat-error" [ngTemplateOutlet]="errTempl"
                 [ngOutletContext]="{ $implicit: theForm.controls['platform'] }"></ng-template>

@julianobrasil I tried that, now the error message in the template is not displayed at all. See the updated stackblitz https://stackblitz.com/edit/angular-v6nvbn

I really don't know whether this is a problem with angular or with material or with my undertanding of how some stuff works. This is similar to this other closed-without-complete-solution issue #6625
It starts working if you use a <mat-error></mat-error> together with ngProjectAs. I don't have a plausible explanation for that. See your modified stackblitz: https://stackblitz.com/edit/angular-wcedma?file=app/app.component.html

@julianobrasil thanks for the effort, I will use this workaround for now I guess. So do we just let this issue be and wait for it to get resolved by the way?

@jelbourn, do you think this could be a material issue? It's similar to this other: #6625. By that time it was closed just because the original problem seemed to be solved. But there were cases without a solution in that issue. The most accepted theory was about an angular issue.
cc: @rafaelss95

This is the expected behavior of Angular. ng-template creates an inert template that can be grabbed and stamped out elsewhere. The content of the template does not "exist" in the view. Components like form-field need their content children to "exist" in order to see them.

@jelbourn Having said all that, is it still ok to do what I have done? Meaning - to create an ng-template definition with mat-error elements inside it and stamp it inside mat-form-field elements across my form while using the workaround mentioned by @julianobrasil - i.e. placing an empty mat-error next to each instance of ng-template

If that works then it should be fine


Using different values of GODEBUG=cgocheck for dev and release builds

Motivation
As per cgo documentation, complete checking of pointer handling can have some cost at run time. For this reason, it would be nice to set the value of cgocheck on a per-build basis.
Feature
Improve the building system in order to use:

GODEBUG=cgocheck=2 for development builds (a.k.a. debug release, usually published when a PR gets merged into master)
GODEBUG=cgocheck=0 for production builds (official distribution artifacts, published when tagging a release)

Alternatives
The do-nothing alternative? :smile_cat:
Additional context

+1 from me

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale


Add members to mdt team

@oybed @sabre1041

@etsauer can you make sure to ensure all members are part of the CoP organization as well?

/lgtm


Data lost while switching between the tabs.

when we switch between the tabs. the data gets lost and it restart the loading which takes lots of time to load.

Hey, could you assign me this issue? I'd love to work on it under GSSOC'23.

Assign me this issue so that I can start my work on it Asap

@Yash-Parsana Assign me this issue so that i can solve this bug.

i think this issue should present in schedule fragment because i already implemented solution in leaderboard fragment. Right ?

According to my updated version of the app...the data lost state happens in all the fragments (i.e. leaderboard fragment, scheduling fragment) and leaderboard fragment goes to indefinite loading on several swipes between the fragments.


Electrolux Well A5 compatibility

First of all, thank you for your this integration! Adding the Well A5 (AX51-304WT) initially gave a fan speed error and the fan couldn't be controlled.  Updating api.py as follows allowed for proper fan control and speed readout:
@property
def speed_range(self) -> tuple:
    if self.model == "WELLA7":
        return 1, 5
    if self.model == "PUREA9":
        return 1, 9
    if self.model == "WELLA5":
        return 1, 5

    return 0, 0

Following values are available and seem to be updating well. I only haven't seen a change in the "Status" sensor.

Thank you @Skitcher
A new release should be available any minute now.


[Avatar] Remove truthiness check on childrenProp

to ensure defaultColor class application if no image is supplied

[X] I have followed (at least) the PR section of the contributing guide.

Closes #13751

@camilleryr It's a great first pull request on Material-UI 👌🏻. Thank you for working on it!


using the magnet switch & load level results in crash

Hello,
first of all thank you for this wonderful SDK. We love to get started with our very first VR App.
But we run into strange problems.
We use Cardboard & Playmaker to get a fast prototype of our App.
Unity Version: 5.3.1f1, Cardboard SDK: 0.6.
There is a Menu first, nothing special, Event System with Touch input, buttons and then it changes the level to our first VR Cardboard Level. Until here nothing special happens. Except on starting the app, we get a

01-21 17:35:55.228 9582-9615/com.sprengundsonntag.VRTest E/Unity: Unable to find libaudiopluginvrunity

So we are in our first level, do some things, trigger some actions and then we want to change the level. We do this with a Playmaker Action, which is based on

SceneManager.LoadScene();

and works quite fine with our existing projects.
When it comes to loading the new Scene it crashes with the following logcat output:
01-21 17:36:35.368 9582-9615/com.sprengundsonntag.VRTest I/Unity: LoadLevel: fail
                                                                  UnityEngine.DebugLogHandler:Internal_Log(LogType, String, Object)
                                                                  UnityEngine.DebugLogHandler:LogFormat(LogType, Object, String, Object[])
                                                                  UnityEngine.Logger:Log(LogType, Object)
                                                                  UnityEngine.Debug:Log(Object)
                                                                  HutongGames.PlayMaker.Actions.LoadLevel:OnEnter() (at /Users/lukashager/Downloads/New Unity Project 4/Assets/PlayMaker/Actions/LoadLevel.cs:98)
                                                                  HutongGames.PlayMaker.FsmState:ActivateActions(Int32) (at c:\Users\Alex\Documents\Unity\Playmaker\Projects\Playmaker.source.unity\Assets\PlayMaker\Classes\FsmState.cs:200)
                                                                  HutongGames.PlayMaker.FsmState:OnEnter() (at c:\Users\Alex\Documents\Unity\Playmaker\Projects\Playmaker.source.unity\Assets\PlayMaker\Classes\FsmState.cs:168)
                                                                  HutongGames.PlayMaker.Fsm:EnterState(FsmState) (at c:\Users\Alex\Documents\Unity\Playmaker\Projects\Playmaker.source.unity\Assets\PlayMaker\Classes\Fsm.cs:2155)
                                                                  HutongGames.PlayMaker.Fsm:SwitchState(FsmState) (at c:\Users\Alex\Documents\Unity\Playmaker\Projects\Playmaker.source.unity\Assets\PlayMaker\Classes\Fsm.cs:2113)
01-21 17:36:37.458 9582-9840/com.sprengundsonntag.VRTest D/Unity: Unloading 9 Unused Serialized files (Serialized files now loaded: 0)
01-21 17:36:37.508 9582-10300/com.sprengundsonntag.VRTest W/art: Native thread exiting without having called DetachCurrentThread (maybe it's going to use a pthread_key_create destructor?): Thread[28,tid=10300,Native,Thread*=0xb8f6ef90,peer=0x12e1c080,"Thread-10777"]
01-21 17:36:37.548 9582-9615/com.sprengundsonntag.VRTest D/Unity: UnloadTime: 76.081001 ms
01-21 17:36:37.628 9582-9615/com.sprengundsonntag.VRTest I/Unity: Creating Cardboard object
                                                                  UnityEngine.DebugLogHandler:Internal_Log(LogType, String, Object)
                                                                  UnityEngine.DebugLogHandler:LogFormat(LogType, Object, String, Object[])
                                                                  UnityEngine.Logger:Log(LogType, Object)
                                                                  UnityEngine.Debug:Log(Object)
                                                                  Cardboard:Create() (at /Users/lukashager/Downloads/New Unity Project 4/Assets/Cardboard/Scripts/Cardboard.cs:61)
                                                                  CardboardHead:Awake() (at /Users/lukashager/Downloads/New Unity Project 4/Assets/Cardboard/Scripts/CardboardHead.cs:84)

                                                                  (Filename: /Users/lukashager/Downloads/New Unity Project 4/Assets/Cardboard/Scripts/Cardboard.cs Line: 61)
01-21 17:36:37.668 9582-9615/com.sprengundsonntag.VRTest A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0x899256d0 in tid 9615 (UnityMain)
01-21 17:36:37.668 9582-9615/com.sprengundsonntag.VRTest W/libc: Security Level: (1), Debug inforamtion is controlled by the DUMPABLE flag.
01-21 17:36:40.088 9582-9811/com.sprengundsonntag.VRTest W/AudioTrack: releaseBuffer() track 0xb869b290 disabled due to previous underrun, restarting

And now for the strange part: this only happens when using the magnet switch in the previous inputs. If you use the finger as tap inputs, it works fine.
We already tried to comment out the onPause() method in BaseCardboardDevice.cs and disabling the Cardboard Component on Level Load. We don't have a Cardboard Audio Listener Component on our Cameras as well since this was a previously mentioned problem.
Our Event System is Touch Input Module on Scenes without Cardboard and Gaze Input Module on Scenes with Cardboard.
This happens on Android only. in the Unity Editor everything works well.
Tested on an HTC M8 One.
We hope you can help us!
Thank you very much!
Grischa
update:

01-21 17:36:35.368 9582-9615/com.sprengundsonntag.VRTest I/Unity: LoadLevel: fail

The Scene is called fail, forgot to mention that.

The inability to find the libaudioplugin is most likely the cause of the failure. Can you try importing the SDK you have into a fresh project, buidling for android, and letting us know if it crashes? If it does not crash, please delete the Cardboard and Plugins folders (or the parts of Plugins from Cardboard) and re-import the SDK package.

I created a fresh and clean project with playmaker and cardboard in it. Two scenes with a cube and a sphere to trigger LoadScene() and even this produces the

Unable to find libaudiopluginvrunity

and a fatal SIGSEGV "fatal signal 11, code 1" error. Maybe a memory leak? Full Logs:
01-21 22:58:36.757 29389-29389/? I/art: Late-enabling -Xcheck:jni
01-21 22:58:36.757 29389-29389/? I/art: VMHOOK: rlim_cur : 0 pid:29389
01-21 22:58:36.917 29389-29389/com.sprengundsonntag.testswitchscenes I/Unity: splash_mode = 0 (integer)
01-21 22:58:36.917 29389-29389/com.sprengundsonntag.testswitchscenes I/Unity: useObb = False (bool)
01-21 22:58:36.947 29389-29389/com.sprengundsonntag.testswitchscenes D/Unity: surfaces: attach glview
01-21 22:58:36.947 29389-29389/com.sprengundsonntag.testswitchscenes I/Unity: Choreographer available: Enabling VSYNC timing
01-21 22:58:36.967 29389-29389/com.sprengundsonntag.testswitchscenes I/Unity: onResume
01-21 22:58:36.997 29389-29389/com.sprengundsonntag.testswitchscenes D/Unity: [EGL] Attaching window :0xb8ef87b8
01-21 22:58:36.997 29389-29389/com.sprengundsonntag.testswitchscenes D/Unity: [EGL] Attaching window :0xb8ef87b8
01-21 22:58:37.027 29389-29389/com.sprengundsonntag.testswitchscenes I/Unity: windowFocusChanged: true
01-21 22:58:37.047 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: SystemInfo CPU = ARMv7 VFPv3 NEON, Cores = 4, Memory = 1823mb
01-21 22:58:37.047 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: SystemInfo ARM big.LITTLE configuration: 4 big (mask: 15), 0 little (mask: 0)
01-21 22:58:37.627 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: [SHA1] 2e8a0f4585679a8d1b270a4107c32ce99768b647   23102224 bytes ~ lib/armeabi-v7a/libunity.so
01-21 22:58:37.637 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: [SHA1] 883aa0e94c58d8004e9f2a710b204f0111263143      45104 bytes ~ lib/armeabi-v7a/libmain.so
01-21 22:58:37.717 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: [SHA1] 0f1d3f9c24a6219cf7348bf8f8709ee70d89e7ff    3758496 bytes ~ lib/armeabi-v7a/libmono.so
01-21 22:58:38.317 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: [SHA1] c11b8f150a8caa1e204904663a6df528b33a63a1   26387872 bytes ~ lib/x86/libunity.so
01-21 22:58:38.327 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: [SHA1] fc5a9ae6b95f8ef5197c86de54ca69b135f681df      26776 bytes ~ lib/x86/libmain.so
01-21 22:58:38.407 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: [SHA1] 151e9995f77f3d5778d93697de3c8bab1204419d    3636444 bytes ~ lib/x86/libmono.so
01-21 22:58:38.407 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: Mono path[0] = '/mnt/asec/com.sprengundsonntag.testswitchscenes-1/base.apk/assets/bin/Data/Managed'
01-21 22:58:38.407 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: Mono config path = 'assets/bin/Data/Managed'
01-21 22:58:38.407 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: PlayerConnection initialized from /mnt/asec/com.sprengundsonntag.testswitchscenes-1/base.apk/assets/bin/Data (debug = 0)
01-21 22:58:38.417 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: PlayerConnection initialized network socket : <IP_ADDRESS> 55417
01-21 22:58:38.417 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: PlayerConnection initialized unix socket : Unity-com.sprengundsonntag.testswitchscenes
01-21 22:58:38.417 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: Multi-casting "[IP] <IP_ADDRESS> [Port] 55417 [Flags] 3 [Guid]<PHONE_NUMBER> [EditorId]<PHONE_NUMBER> [Version] 1048832 [Id]<EMAIL_ADDRESS>[Debug] 0" to [<IP_ADDRESS>:54997]...
01-21 22:58:38.417 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: Waiting for connection from host on [<IP_ADDRESS>:55417]...
01-21 22:58:43.457 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: Timed out. Continuing without host connection.
01-21 22:58:43.657 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: InitializeScriptEngine OK (afe05ee0)
01-21 22:58:43.657 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: PlayerConnection already initialized - listening to [<IP_ADDRESS>:55417]
01-21 22:58:43.697 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: Unable to lookup library path for 'libaudiopluginvrunity', native render plugin support disabled.
01-21 22:58:43.707 29389-29420/com.sprengundsonntag.testswitchscenes E/Unity: Unable to find libaudiopluginvrunity
01-21 22:58:43.707 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: PlayerInitEngineNoGraphics OK
01-21 22:58:43.707 29389-29420/com.sprengundsonntag.testswitchscenes I/Adreno-EGL: <qeglDrvAPI_eglInitialize:410>: EGL 1.4 QUALCOMM build: AU_LINUX_ANDROID_LA.BF.1.1_RB<IP_ADDRESS>.002.030_msm8974_refs/tags/AU_LINUX_ANDROID_LA.BF.1.1_RB<IP_ADDRESS>.002.030__release_AU ()
                                                                                OpenGL ES Shader Compiler Version: E<IP_ADDRESS>
                                                                                Build Date: 12/11/14 Thu
                                                                                Local Branch:
                                                                                Remote Branch: refs/tags/AU_LINUX_ANDROID_LA.BF.1.1_RB<IP_ADDRESS>.002.030
                                                                                Local Patches: NONE
                                                                                Reconstruct Branch: NOTHING
01-21 22:58:43.727 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: [EGL] Request: ES 3.1+AEP RGB0 000 0/0
01-21 22:58:43.727 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: [EGL] Checking ES 3.1 support...
01-21 22:58:43.737 29389-29420/com.sprengundsonntag.testswitchscenes W/Adreno-EGL: <qeglDrvAPI_eglCreateContext:2438>: EGL_BAD_MATCH
01-21 22:58:43.737 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: [EGL] ES3.1 not supported
01-21 22:58:43.737 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: [EGL] Request: ES 3.1 RGB0 000 0/0
01-21 22:58:43.737 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: [EGL] Request: ES 3.0 RGB0 000 0/0
01-21 22:58:43.737 29389-29420/com.sprengundsonntag.testswitchscenes W/Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:632>: EGL_BAD_ATTRIBUTE
01-21 22:58:43.737 29389-29420/com.sprengundsonntag.testswitchscenes W/Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:632>: EGL_BAD_ATTRIBUTE
01-21 22:58:43.737 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: [EGL] Found: ID[1] ES 3.0 RGB16 565 0/0
01-21 22:58:43.757 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: [EGL] Request: ES 3.1+AEP RGB0 000 0/0
01-21 22:58:43.757 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: [EGL] Request: ES 3.1 RGB0 000 0/0
01-21 22:58:43.757 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: [EGL] Request: ES 3.0 RGB0 000 0/0
01-21 22:58:43.757 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: [EGL] Found: ID[1] ES 3.0 RGB16 565 0/0
01-21 22:58:43.767 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: [EGL] Request: ES 3.0 RGBA32 8888 0/0
01-21 22:58:43.767 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: [EGL] Found: ID[5] ES 3.0 RGBA32 8888 0/0 AFBT
01-21 22:58:43.777 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: ANativeWindow: (1920/1080) RequestedResolution: (0/0) EGLSurface: (1920/1080)
01-21 22:58:43.847 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: Renderer: Adreno (TM) 330
01-21 22:58:43.847 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: Vendor:   Qualcomm
01-21 22:58:43.847 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: Version:  OpenGL ES 3.0<EMAIL_ADDRESS><EMAIL_ADDRESS>(CL@)
01-21 22:58:43.847 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: GLES:     3
01-21 22:58:43.847 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity:  GL_AMD_compressed_ATC_texture GL_AMD_performance_monitor GL_AMD_program_binary_Z400 GL_EXT_debug_label GL_EXT_debug_marker GL_EXT_discard_framebuffer GL_EXT_robustness GL_EXT_texture_format_BGRA8888 GL_EXT_texture_type_2_10_10_10_REV GL_NV_fence GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth_texture GL_OES_depth24 GL_OES_EGL_image GL_OES_EGL_sync GL_OES_EGL_image_external GL_OES_element_index_uint GL_OES_fbo_render_mipmap GL_OES_fragment_precision_high GL_OES_get_program_binary GL_OES_packed_depth_stencil GL_OES_depth_texture_cube_map GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_texture_3D GL_OES_texture_float GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_half_float GL_OES_vertex_type_10_10_10_2 GL_OES_vertex_array_object GL_QCOM_alpha_test GL_QCOM_binning_control GL_QCOM_driver_control GL_QCOM_perfmon_global_mode GL_QCOM_extended_get GL_QCOM_extended_get2 GL_QCOM_tiled_rendering GL_QCOM_writeonly_rendering GL_EXT_sRGB GL_EXT_sRGB_write_control GL_EXT
01-21 22:58:43.847 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: _texture_sRGB_decode GL_EXT_texture_filter_anisotropic GL_EXT_multisampled_render_to_texture GL_EXT_color_buffer_float GL_EXT_color_buffer_half_float GL_EXT_disjoint_timer_query
01-21 22:58:44.017 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: OPENGL LOG: Creating OpenGL ES 3.0 graphics device
01-21 22:58:44.017 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: InitializeGfxDevice OK
01-21 22:58:44.017 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: Initialize engine version: 5.3.1f1 (cc9cbbcc37b4)
01-21 22:58:44.067 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: AudioManager: Selecting OpenSL output...
01-21 22:58:44.077 29389-29420/com.sprengundsonntag.testswitchscenes W/libc: pthread_create sched_setscheduler call failed: Operation not permitted
01-21 22:58:44.087 29389-29420/com.sprengundsonntag.testswitchscenes W/libc: pthread_create sched_setscheduler call failed: Operation not permitted
01-21 22:58:44.087 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: Begin MonoManager ReloadAssembly
01-21 22:58:44.107 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: Platform assembly: /mnt/asec/com.sprengundsonntag.testswitchscenes-1/base.apk/assets/bin/Data/Managed/UnityEngine.dll (this message is harmless)
01-21 22:58:44.107 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: Loading /mnt/asec/com.sprengundsonntag.testswitchscenes-1/base.apk/assets/bin/Data/Managed/UnityEngine.dll into Unity Child Domain
01-21 22:58:44.167 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: Platform assembly: /mnt/asec/com.sprengundsonntag.testswitchscenes-1/base.apk/assets/bin/Data/Managed/Assembly-CSharp.dll (this message is harmless)
01-21 22:58:44.177 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: Loading /mnt/asec/com.sprengundsonntag.testswitchscenes-1/base.apk/assets/bin/Data/Managed/Assembly-CSharp.dll into Unity Child Domain
01-21 22:58:44.177 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: Platform assembly: /mnt/asec/com.sprengundsonntag.testswitchscenes-1/base.apk/assets/bin/Data/Managed/UnityEngine.UI.dll (this message is harmless)
01-21 22:58:44.177 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: Loading /mnt/asec/com.sprengundsonntag.testswitchscenes-1/base.apk/assets/bin/Data/Managed/UnityEngine.UI.dll into Unity Child Domain
01-21 22:58:44.187 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: Platform assembly: /mnt/asec/com.sprengundsonntag.testswitchscenes-1/base.apk/assets/bin/Data/Managed/UnityEngine.Networking.dll (this message is harmless)
01-21 22:58:44.187 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: Loading /mnt/asec/com.sprengundsonntag.testswitchscenes-1/base.apk/assets/bin/Data/Managed/UnityEngine.Networking.dll into Unity Child Domain
01-21 22:58:44.187 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: Platform assembly: /mnt/asec/com.sprengundsonntag.testswitchscenes-1/base.apk/assets/bin/Data/Managed/ConditionalExpression.dll (this message is harmless)
01-21 22:58:44.187 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: Loading /mnt/asec/com.sprengundsonntag.testswitchscenes-1/base.apk/assets/bin/Data/Managed/ConditionalExpression.dll into Unity Child Domain
01-21 22:58:44.187 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: Platform assembly: /mnt/asec/com.sprengundsonntag.testswitchscenes-1/base.apk/assets/bin/Data/Managed/PlayMaker.dll (this message is harmless)
01-21 22:58:44.197 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: Loading /mnt/asec/com.sprengundsonntag.testswitchscenes-1/base.apk/assets/bin/Data/Managed/PlayMaker.dll into Unity Child Domain
01-21 22:58:44.217 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: - Completed reload, in  0.131 seconds
01-21 22:58:44.247 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: Platform assembly: /mnt/asec/com.sprengundsonntag.testswitchscenes-1/base.apk/assets/bin/Data/Managed/System.Core.dll (this message is harmless)
01-21 22:58:44.267 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: Platform assembly: /mnt/asec/com.sprengundsonntag.testswitchscenes-1/base.apk/assets/bin/Data/Managed/System.dll (this message is harmless)
01-21 22:58:44.467 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: PlayerInitEngineGraphics OK
01-21 22:58:44.477 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: Found 23 native sensors
01-21 22:58:44.477 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: Sensor :        Accelerometer ( 1) ; 0.010000 / 0.01s ; Accelerometer Sensor / HTC Group Ltd.
01-21 22:58:44.477 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: Sensor :        Accelerometer ( 1) ; 0.010000 / 0.01s ; Accelerometer Sensor / HTC Group Ltd.
01-21 22:58:44.487 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: Requested framebuffer: resolution[1920x1080], rgba[8/8/8/8], depth+stencil[on], samples[1]
01-21 22:58:44.487 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: Created framebuffer: resolution[1920x1080], rgba[8/8/8/8], depth+stencil[24/8], samples[0]
01-21 22:58:45.037 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: UnloadTime: 1.079000 ms
01-21 22:58:45.067 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: Unloading 7 Unused Serialized files (Serialized files now loaded: 0)
01-21 22:58:45.207 29389-29420/com.sprengundsonntag.testswitchscenes W/art: Attempt to remove local handle scope entry from IRT, ignoring
01-21 22:58:45.207 29389-29420/com.sprengundsonntag.testswitchscenes W/art: Attempt to remove local handle scope entry from IRT, ignoring
01-21 22:58:45.237 29389-29420/com.sprengundsonntag.testswitchscenes W/Adreno-ES20: <get_simple_queries:1544>: GL_INVALID_ENUM
01-21 22:58:45.267 29389-29641/com.sprengundsonntag.testswitchscenes D/libc: [NET] android_getaddrinfofornet+,hn 19(0x706c61792e676f),sn(),hints(known),family 0,flags 4
01-21 22:58:45.267 29389-29641/com.sprengundsonntag.testswitchscenes D/libc: [NET] android_getaddrinfofornet-, err=8
01-21 22:58:45.267 29389-29641/com.sprengundsonntag.testswitchscenes D/libc: [NET] android_getaddrinfofornet+,hn 19(0x706c61792e676f),sn(),hints(known),family 0,flags 1024
01-21 22:58:45.267 29389-29641/com.sprengundsonntag.testswitchscenes D/libc: [NET] android_getaddrinfofornet-, pass to proxy
01-21 22:58:45.267 29389-29641/com.sprengundsonntag.testswitchscenes D/libc: [NET] android_getaddrinfo_proxy+
01-21 22:58:45.267 29389-29641/com.sprengundsonntag.testswitchscenes D/libc: [NET] android_getaddrinfo_proxy get netid:0
01-21 22:58:45.377 29389-29641/com.sprengundsonntag.testswitchscenes D/libc: [NET] android_getaddrinfo_proxy-, success
01-21 22:58:45.567 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: Sensor :        Accelerometer ( 1) ; 0.010000 / 0.01s ; Accelerometer Sensor / HTC Group Ltd.
01-21 22:58:49.487 29389-29627/com.sprengundsonntag.testswitchscenes D/Unity: Unloading 4 Unused Serialized files (Serialized files now loaded: 0)
01-21 22:58:49.527 29389-29653/com.sprengundsonntag.testswitchscenes W/art: Native thread exiting without having called DetachCurrentThread (maybe it's going to use a pthread_key_create destructor?): Thread[28,tid=29653,Native,Thread*=0xb9187190,peer=0x12e21080,"Thread-2987"]
01-21 22:58:49.557 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: UnloadTime: 57.395000 ms
01-21 22:58:49.607 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: System memory in use before: 4.6 MB.
01-21 22:58:49.617 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: System memory in use after: 4.6 MB.
01-21 22:58:49.617 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: Total: 3.195000 ms (FindLiveObjects: 0.201000 ms CreateObjectMapping: 0.215000 ms MarkObjects: 2.493000 ms  DeleteObjects: 0.279000 ms)
01-21 22:58:54.697 29389-29627/com.sprengundsonntag.testswitchscenes D/Unity: Unloading 3 Unused Serialized files (Serialized files now loaded: 0)
01-21 22:58:54.797 29389-29420/com.sprengundsonntag.testswitchscenes I/Unity: LoadLevel: first
                                                                              UnityEngine.DebugLogHandler:Internal_Log(LogType, String, Object)
                                                                              UnityEngine.DebugLogHandler:LogFormat(LogType, Object, String, Object[])
                                                                              UnityEngine.Logger:Log(LogType, Object)
                                                                              UnityEngine.Debug:Log(Object)
                                                                              HutongGames.PlayMaker.Actions.LoadLevel:OnEnter() (at /Users/lukashager/Downloads/VR switch scenes Test Project/Assets/PlayMaker/Actions/LoadLevel.cs:40)
                                                                              HutongGames.PlayMaker.FsmState:ActivateActions(Int32) (at c:\Users\Alex\Documents\Unity\Playmaker\Projects\Playmaker.source.unity\Assets\PlayMaker\Classes\FsmState.cs:200)
                                                                              HutongGames.PlayMaker.FsmState:OnEnter() (at c:\Users\Alex\Documents\Unity\Playmaker\Projects\Playmaker.source.unity\Assets\PlayMaker\Classes\FsmState.cs:168)
                                                                              HutongGames.PlayMaker.Fsm:EnterState(FsmState) (at c:\Users\Alex\Documents\Unity\Playmaker\Projects\Playmaker.source.unity\Assets\PlayMaker\Classes\Fsm.cs:2155)
                                                                              HutongGames.PlayMaker.Fsm:SwitchState(FsmState) (at c:\Users\Alex\Documents\Unity\Playmaker\Projects\Playmaker.source.unity\Assets\PlayMaker\Classes\Fs
01-21 22:58:54.847 29389-29736/com.sprengundsonntag.testswitchscenes W/art: Native thread exiting without having called DetachCurrentThread (maybe it's going to use a pthread_key_create destructor?): Thread[28,tid=29736,Native,Thread*=0xb9a7a678,peer=0x12e217a0,"Thread-2989"]
01-21 22:58:54.857 29389-29420/com.sprengundsonntag.testswitchscenes D/Unity: UnloadTime: 36.428001 ms
01-21 22:58:54.867 29389-29420/com.sprengundsonntag.testswitchscenes A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0x998cfff0 in tid 29420 (UnityMain)
01-21 22:58:54.867 29389-29420/com.sprengundsonntag.testswitchscenes W/libc: Security Level: (1), Debug inforamtion is controlled by the DUMPABLE flag.
01-21 22:58:56.767 29389-29609/com.sprengundsonntag.testswitchscenes W/AudioTrack: releaseBuffer() track 0xb9196828 disabled due to previous underrun, restarting

To be clear, you are importing the .unitypackage for Cardboard not cloning anything from git, right?

yes.

Can you confirm that your project has Plugins/Android/libs/armabi-v7a/libaudiopluginvrunity ? Thanks. We've never seen this error before, so trying to figure out what could be going wrong.

So actually the path is Plugins/Android/libs/armeabi-v7a/libaudiopluginvrunity.
I didn't change anything about that.

You're right about the path. Just verifying that the file is actually there. Are you building on Windows or OSX?
One more test, can you go into the AudioSettings and set the Spatializer to the Cardboard Spatializer and build again? I want to see if that pulls the file in.

01-22 13:03:55.509 1921-1994/com.sprengundsonntag.testswitchscenes W/linker: /mnt/asec/com.sprengundsonntag.testswitchscenes-2/lib/arm/libaudiopluginvrunity.so: is missing DT_SONAME will use basename as a replacement: "libaudiopluginvrunity.so"
01-22 13:03:55.519 1921-1994/com.sprengundsonntag.testswitchscenes D/Unity: Unable to lookup library path for 'libaudiopluginvrunity', native render plugin support disabled.
01-22 13:03:55.520 1921-1994/com.sprengundsonntag.testswitchscenes E/Unity: Unable to find libaudiopluginvrunity
01-22 13:03:55.521 1921-1994/com.sprengundsonntag.testswitchscenes D/Unity: PlayerInitEngineNoGraphics OK

so he is still not able to find it.

I'm seeing similar issues building on Windows 10 with Unity 5.3.1f1 and Android 4.3 (HTC m1).
01-24 21:12:25.480  27180-27197/com.unity3d.vrstandardassets E/Unity﹕ Unable to find libaudiopluginvrunity
01-24 21:12:25.780      251-598/? E/HtcAudPMB﹕ getOutput() IOProfile is null.
01-24 21:12:25.820      251-592/? E/AudioStreamOutALSA﹕ PCM_Write set_amp_mode,1
01-24 21:12:26.321  27180-27212/? E/VrApiLoader﹕ Oculus updates needed.
    Instructions to receive new updates can be found at:
    https://support.oculus.com under 'Samsung Gear VR - Oculus Software Update'
01-24 21:12:26.321  27180-27212/? E/E:\tw\33a21edae6c0e9ad\Software\OculusSDK\Integrations\Unity\Releases\0﹕ VrApi initialization error.
01-24 21:12:26.321  27180-27212/? E/EntryPoints﹕ vrapi_GetVersionString was called before vrapi_Initialize()!
01-24 21:12:26.321  27180-27212/? A/libc﹕ Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 27212 (UnityGfxDeviceW)
01-24 21:12:27.022      603-675/? E/EmbeddedLogger﹕ App crashed! Process: com.unity3d.vrstandardassets
01-24 21:12:27.022      603-675/? E/EmbeddedLogger﹕ App crashed! Package: com.unity3d.vrstandardassets v1 (1.0)
01-24 21:12:27.032      603-675/? E/EmbeddedLogger﹕ Application Label: VRSamples
01-24 21:12:27.062      603-800/? E/InputDispatcher﹕ channel '4236afd0 com.google.unity.GoogleUnityActivity (s)' ~ Channel is unrecoverably broken and will be disposed!
01-24 21:13:12.350      238-362/? E/qdexternal﹕ writeHPDOption: state file '/sys/devices/virtual/graphics/fb1/hpd' not found : ret-1 err str: Permission denied
01-24 21:13:12.770   4552-27259/? E/WeatherTimeKeeper﹕ Fail to schedule next weather update because of permission issue:Permission Denial: getIntentSender() from pid=4552, uid=10216, (need uid=10152) is not allowed to send as package com.htc.idlescreen.base
01-24 21:13:17.475  27264-27264/? E/DMLog﹕ HTC_DEBUG = false
01-24 21:13:22.711  27281-27281/? E/dalvikvm﹕ dlopen("/data/data/com.synchronoss.dcs.att.r2g/lib/libdcs.so") failed: dlopen failed: library "/data/data/com.synchronoss.dcs.att.r2g/lib/libdcs.so" not found
01-24 21:13:22.751  27281-27281/? E/DCS_Lib﹕ JNI_OnLoad V. 08012013_0001 Successful
01-24 21:13:47.528  27298-27298/? E/SELinux﹕ seapp_context_lookup:  No match for app with uid 9987, seinfo platform, name org.simalliance.openmobileapi.service:remote

I just double-checked with the demo scene that comes with the SDK.  Even though the spatial audio is working just fine in the app, I still see the same error in the logcat:
01-24 22:21:50.651 16149 16174 E Unity   : Unable to find libaudiopluginvrunity
I think the "Missing DT_SONAME" warning that @sprengundsonntag mentioned may be related to this message.  I am seeing that too.  Oddly, I am not seeing the part that says "native render plugin support disabled", so I don't know what's up there.
But anyway, since the audio is working in the app despite this message, I think it may possibly be a red herring for the crash caused by magnet/LoadLevel.  That crash may be related to the similar crash we had with tilt/LoadLevel (or Quit) in the prior release.
@sprengundsonntag Can you temporarily disable all CardboardAudio scripts in your scene and see if the magnet/LoadLevel bug still exists?  (If you really want to be sure, delete the components completely.)

@smdol I don't have any CardboardAudio Components in my Scene, just normal Audio Sources. The sound works flawlessly, for our project spatialized sound isn't that important.
Thank you all for your time & effort to get this going!

One quick workaround is not to load the level immediately after the trigger has been pulled, set the button to call on click to a method that calls a coroutine that waits for 0.1 seconds (or invoke another method after the same time). Of course, it would be good to use some kind of "traffic light" with a boolean variable, something like this:
public void ChangeLevel(int l){
	if(changingLevel)
		return; //does nothing, it's already changing level
	changingLevel = true;
	StartCoroutine(ChangeLevelThread(l));
}
IEnumerator ChangeLevelThread(int l){
	yield return new WaitForSeconds(0.1f);
	SceneManager.LoadScene (l);
}

I don't know exactly why this may happen, I think that the trigger detection may be reading something from the hardware that takes a bit of time, so, if the level changes and the trigger script is enabling again on the new scene, it will find part of the script stuck reading, I don't know, I'm just speculating.
Anyways, I hope this helps you find a solution.

@sprengundsonntag did you get the solution? I get the exact same problem...

@nosmirck So actually the level changes not at the exact moment the triffer is pulled but about 7 seconds later.
@subkhansarif Actually we didn't find a solution yet and paused development on that particular project until a fix is found.

@sprengundsonntag well, yeah, for me 0.1 was enough, but depending on the device, you may need more time.
Anyways, I ended up implementing a "trigger-free" system to activate the buttons, by just gazing at them for 2.5 seconds, they activate. I put a small canvas with an image of a circle in the reticle and fill it radial, when it's full, it activates the button.
However, in the release notes of the newest SDK build it says that this problem was fixed.
v0.7 (3/30/2016):

...
Fixed a crash bug from using the magnetic trigger or tilt event before loading a level.
...

Please say if the trigger crash is fixed for you -- we reworked how the events come up from native code so that it all runs on a single thread now.

@smdol it is fixed for me. the new update (v0.7) works. Thank you...


Resume and fade in MSU track when leaving Item/Elevator rooms

Crossing my fingers the new fade-in routine doesn't add lag. Things seemed okay as I was testing, but I haven't had time to run through a full seed yet.

Will add a check so we only fade in when the track we're loading is going to be resumed.

Squashed the commits and made the fade-in last 15 frames, instead of 63, to match the Z3 side. Beat all bosses and minibosses in SM without crashes after also pulling in the fix from the plando-updates branch, so I think we're ready!


Feature request

Betterment.com

Hello @z5Q46L6bSY1W ,
This repo is not being maintained anymore, but we are trying to keep it alive on a detached fork here, would you kindly submit your PR there and close this one here? :)


WIP: Better balance sheets

This patch creates a new method time_series_balance to fetch the long balance sheets from yahoo finance.  It will show "Ordinary Shares Number". With current version I cant get access to it via yfinance.

Hi Troels, can you suggest a change which will enable yfinance to pull Shares Outstanding data from income statements. It does not do that today when we pull balancesheets/cashflows/financials?

Hello,
This feature is very useful.
Any plans to merge it?
Thanks.

Another PR around the same time addresses this same problem - https://github.com/ranaroussi/yfinance/pull/776 . @EpsilonTal can you experiment with both and give opinion on which is better?
Also both ignore quarterly, probably that should be implemented too for a merge.

Update: #774 has been merged into dev branch, so will soon ship in a PIP release.


feat: add comparators to get/view note (#3136)

WIP
resolves #3136

[ ] I've provided a paragraph or two giving a summary of the change in the description, including relevant motivation and context.
[ ] I've enabled auto-merge if the PR is ready to merge.
[ ] I have updated the yellow paper when making changes to associated functionality (e.g. outward-facing spec changes).
[ ] I have reviewed my diff in github, line by line and removed unexpected formatting changes, testing logs, or commented-out code.
[x] Every change is related to the PR description.
[x] I have linked this pull request to relevant issues (if any exist).

Benchmark results
No metrics with a significant change found.

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit 301f0e6d and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
45,412
179,524
716,068

l1_rollup_calldata_gas
221,728
866,548
3,446,944

l1_rollup_execution_gas
314,147
984,220
3,666,533

l2_block_processing_time_in_ms
1,594 (-2%)
5,302 (+2%)
20,929 (+1%)

note_successful_decrypting_time_in_ms
289 (+1%)
846 (+1%)
3,198 (+1%)

note_trial_decrypting_time_in_ms
99.4 (+2%)
74.8 (+19%)
139 (-5%)

l2_block_building_time_in_ms
16,144 (+1%)
63,952
256,602 (+1%)

l2_block_rollup_simulation_time_in_ms
11,750
46,592
187,266

l2_block_public_tx_process_time_in_ms
4,358 (+1%)
17,269 (+1%)
68,984 (+1%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
15,897
30,631

note_history_successful_decrypting_time_in_ms
1,974 (-1%)
4,064 (+5%)

note_history_trial_decrypting_time_in_ms
140 (-5%)
210 (-9%)

node_database_size_in_bytes
3,514,654
3,551,567

pxe_database_size_in_bytes
29,923
59,478

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
212
44,681
25,561

private-kernel-ordering
166 (+1%)
43,753
14,809

base-rollup
1,199
128,338
881

root-rollup
79.0
4,088
677

private-kernel-inner
292
71,208
25,561

public-kernel-private-input
206
31,863
25,561

public-kernel-non-first-iteration
203
31,905
25,561

merge-rollup
7.64
2,608
881

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
0 deployed contracts
1 deployed contracts

tx_size_in_bytes
15,455
32,223

Transaction processing duration by data writes.

Metric
0 new commitments
1 new commitments

tx_pxe_processing_time_ms
375 (+1%)
1,085

Metric
1 public data writes

tx_sequencer_processing_time_ms
536


Login Page

The form should contain:

[ ] Username/Email Input
[ ] Password Input
[ ] Login Button
[ ] Go to Register Button

done login form


UI: Lack of Visual Feedback Upon Successful Backup Restoration

Hi
https://github.com/pocketbase/pocketbase/assets/44144724/981d4243-4961-4e9a-b8e7-6c307b18c61a
I'm not sure if the same issue exists when backup restoration fails.
PocketBase version: 0.21.1

There is no easy way to do this because on backup restore we restart the app in the background and in my opinion it is not worth the dev effort.

Eventually I'll consider adding the backup operation as part of the planned job queue implementation sometime in the future.


Take GitHub org config from yaml files

Part of #482, after #542.
I got here from looking at stalebot and SENTRY_REPOS, I didn't want to put all of those repos in env vars and the thought of putting them in yml suggested itself. That's what we want to do anyway! It's our plan for bringing in config from security-as-code. Yay! :D
There's a couple other things this opens up as well, such as storing the installationId in config so we don't have to await in the constructor. 💃
Before Merging

[x] Set GH_APP_PRIVATE_KEY_FOR_GETSENTRY. I believe we'll have to create a new private key as the old value is not accessible nor is the GH_APP_SECRET_KEY variable renameable.

After Merging

[ ] Delete the old environment variables:

[ ] GH_APP_SECRET_KEY
[ ] GH_APP_IDENTIFIER

[ ] Delete the old private key.

I believe this is going to supersede #524. Should look that over and bring in any further changes to here, such as to README.md and .env.example.

Should look that over

Done. Closed it.

Bogged down in some changes to this one, converting to draft.

I've added a new private key to the environment in GitHub:

I need to add it to deploy.sh.

I need to add it to deploy.sh.

Done with efc94b701a3c54bdb1b20c0b2314ac5d291209e7.

I'm making some progress on unraveling the import stack.

Pretty interesting. Looks like a module is stubbed out with variables declared but not defined, though the nested imports aren't even declared.

Console logging a variable affects the import system. 😳
Working

Broken

This is nuts. I don't want to be doing this right now. How do I get past this?
Broken
  console.log
    🌴 loadGitHubOrgs.test - entering config

      at Object.<anonymous> (src/config/loadGitHubOrgs.test.ts:4:9)

  console.log
    🌴 loadGitHubOrgs.test - back from config

      at Object.<anonymous> (src/config/loadGitHubOrgs.test.ts:6:9)

  console.log
    🌻 loadGitHubOrgs.test - entering loadGitHubOrgs

      at Object.<anonymous> (src/config/loadGitHubOrgs.test.ts:9:9)

  console.log
    🌼 loadGitHubOrgs - entering api/github/org

      at Object.<anonymous> (src/config/loadGitHubOrgs.ts:5:9)

  console.log
    🌳 api/github/org - entering config

      at Object.<anonymous> (src/api/github/org.ts:13:9)

  console.log
    🌸 config - entering loadGitHubOrgs

      at Object.<anonymous> (src/config/index.ts:1:9)

  console.log
    🌸 config - back from loadGitHubOrgs

      at Object.<anonymous> (src/config/index.ts:3:9)

  console.log
    🌲 { loadGitHubOrgs: undefined }

      at Object.<anonymous> (src/config/index.ts:4:9)

Working
  console.log
    🌴 loadGitHubOrgs.test - entering config

      at Object.<anonymous> (src/config/loadGitHubOrgs.test.ts:4:9)

  console.log
    🌸 config - entering loadGitHubOrgs

      at Object.<anonymous> (src/config/index.ts:1:9)

  console.log
    🌼 loadGitHubOrgs - entering api/github/org

      at Object.<anonymous> (src/config/loadGitHubOrgs.ts:5:9)

  console.log
    🌳 api/github/org - entering config

      at Object.<anonymous> (src/api/github/org.ts:13:9)

  console.log
    🌳 api/github/org - back from config

      at Object.<anonymous> (src/api/github/org.ts:15:9)

  console.log
    🌲 {
      SENTRY_DSN: undefined,
      DEFAULT_PORT: undefined,
      DAY_IN_MS: undefined,
      SENTRY_REPO_SLUG: undefined,
      GETSENTRY_REPO_SLUG: undefined,
      GETSENTRY_BOT_ID: undefined,
      GOCD_SENTRYIO_FE_PIPELINE_NAME: undefined,
      GOCD_SENTRYIO_BE_PIPELINE_GROUP: undefined,
      GOCD_SENTRYIO_BE_PIPELINE_NAME: undefined,
      GOCD_ORIGIN: undefined,
      FEED_DEPLOY_CHANNEL_ID: undefined,
      FEED_DEV_INFRA_CHANNEL_ID: undefined,
      FEED_ENGINEERING_CHANNEL_ID: undefined,
      SUPPORT_CHANNEL_ID: undefined,
      TEAM_OSPO_CHANNEL_ID: undefined,
      DISABLE_GITHUB_METRICS: undefined,
      DRY_RUN: undefined,
      PROJECT: undefined,
      REQUIRED_CHECK_NAME: undefined,
      REQUIRED_CHECK_CHANNEL: undefined,
      SLACK_PROFILE_ID_GITHUB: undefined,
      Color: undefined,
      DB_HOST: undefined,
      DB_INSTANCE_CONNECTION_NAME: undefined,
      DB_USER: undefined,
      DB_PASSWORD: undefined,
      DB_NAME: undefined,
      SLACK_BOT_USER_ACCESS_TOKEN: undefined,
      SLACK_SIGNING_SECRET: undefined,
      BuildStatus: undefined,
      PRODUCT_AREA_LABEL_PREFIX: undefined,
      PRODUCT_AREA_UNKNOWN: undefined,
      STATUS_LABEL_PREFIX: undefined,
      BACKLOG_LABEL: undefined,
      IN_PROGRESS_LABEL: undefined,
      UNKNOWN_LABEL: undefined,
      STALE_LABEL: undefined,
      WAITING_FOR_LABEL_PREFIX: undefined,
      WAITING_FOR_SUPPORT_LABEL: undefined,
      WAITING_FOR_COMMUNITY_LABEL: undefined,
      WAITING_FOR_PRODUCT_OWNER_LABEL: undefined,
      MAX_TRIAGE_DAYS: undefined,
      MAX_ROUTE_DAYS: undefined,
      PERSONAL_TEST_REPO: undefined,
      PERSONAL_TEST_REPOS: undefined,
      SENTRY_REPOS_WITH_ROUTING: undefined,
      SENTRY_REPOS_WITHOUT_ROUTING: undefined,
      SENTRY_REPOS: undefined,
      GH_USER_TOKEN: undefined,
      FORCE_USER_TOKEN_GITHUB_CLIENT: undefined,
      GH_ORGS: undefined,
      GETSENTRY_ORG: undefined,
      OFFICE_TIME_ZONES: undefined,
      OFFICES_24_HOUR: undefined,
      OFFICES_12_HOUR: undefined
    }

      at Object.<anonymous> (src/api/github/org.ts:16:9)

  console.log
    🌼 loadGitHubOrgs - back from api/github/org

      at Object.<anonymous> (src/config/loadGitHubOrgs.ts:7:9)

  console.log
    🌸 config - back from loadGitHubOrgs

      at Object.<anonymous> (src/config/index.ts:3:9)

  console.log
    🌲 { loadGitHubOrgs: [Function: loadGitHubOrgs] }

      at Object.<anonymous> (src/config/index.ts:4:9)

  console.log
    🌴 loadGitHubOrgs.test - back from config

      at Object.<anonymous> (src/config/loadGitHubOrgs.test.ts:6:9)

  console.log
    🌻 loadGitHubOrgs.test - entering loadGitHubOrgs

      at Object.<anonymous> (src/config/loadGitHubOrgs.test.ts:9:9)

  console.log
    🌻 loadGitHubOrgs.test - back from loadGitHubOrgs

      at Object.<anonymous> (src/config/loadGitHubOrgs.test.ts:11:9)

  console.log
    🌲 { loadGitHubOrgs: [Function: loadGitHubOrgs] }

      at Object.<anonymous> (src/config/loadGitHubOrgs.test.ts:12:9)

This is nuts. I don't want to be doing this right now. How do I get past this?

I think you can use console.dir(object, {depth: null, colors: true}) to print out objects

I think you can use console.dir(object, {depth: null, colors: true}) to print out objects

Not sure we're on the same page ... I was seeing really weird behavior, ended up going with this:
https://github.com/getsentry/eng-pipes/blob/7d01eca7e55e58d668d0cc35d2ff32e093239933/src/config/loadGitHubOrgs.test.ts#L1-L5

Not sure we're on the same page ... I was seeing really weird behavior, ended up going with this:

Oh yeah, I was way off then


bug: propagate deletion of parent PIDs properly

:heart: Thank you for your contribution!
Relies on #1810 being merged first
Close #1863
Description

Please describe briefly your pull request.

Checklist
Ticks in all boxes and 🟢 on all GitHub actions status checks are required to merge:

[ ] I'm aware of the code of conduct.
[ ] I've created logical separate commits and followed the commit message format.
[ ] I've added relevant test cases.
[ ] I've added relevant documentation.
[ ] I've marked translation strings.
[ ] I've identified the copyright holder(s) and updated copyright headers for touched files (>15 lines contributions).
[ ] I've NOT included third-party code (copy/pasted source code or new dependencies).

If you have added third-party code (copy/pasted or new dependencies), please reach out to an architect.

Frontend

[ ] I've followed the CSS/JS and React guidelines.
[ ] I've followed the web accessibility guidelines.
[ ] I've followed the user interface guidelines.

Reminder
By using GitHub, you have already agreed to the GitHub’s Terms of Service including that:

You license your contribution under the same terms as the current repository’s license.
You agree that you have the right to license your contribution under the current repository’s license.

Can you please rebase after @alejandromumo fixed the tests? It should solve the CI failure.


Cannot bundle Node.js built-in "node:http" while vite build

I am working on Vite v3.0.9 and using node-fetch 3.2.10. I used doc to import node-fetch (see screen)
While build I have next issue

Current Behavior

Expected Behavior
Successful build
Your Environment

software
version

node-fetch
3.2.10

node
18.12.0

npm
8.19.2

Operating System

Additional context
I've already tried workaround with replacing node:http into http
But than I have the same error but with just http module

Are you trying to bundle for the web or for Node.js? This library only works in Node.js

Hm, If I have import fs from 'fs' - all work.
For vite I have next settings, looks all good.
build: {
      target: 'esnext',
      lib: {
        entry: 'src/entry-server.ts',
        formats: ['iife'],
        name: 'storefront',
      },
      emptyOutDir: true,
      outDir: '../../dist/apps/storefront/server',
      ssr: 'src/entry-server.ts',
    },
    ssr: {
      noExternal: true,
    },

Mb could you clarify is it issue of node-fetch or vite?

@supproduction , did you solve the issue, I am facing the exactly same issue.


[HOTFIX] Modified code to fix the degrade in compaction performance

Problem
Compaction performance for 3.5 billion degraded by 16-20%
Analysis:
Code modification in RawResultIerator.java has caused the problem wherein few extra checks are performed as compared to previous code
Fix
Revert the changes in RawResultIerator class

[ ] Any interfaces changed?
No
[ ] Any backward compatibility impacted?
NA
[ ] Document update required?
No
[ ] Testing done
Verified in cluster testing
[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.
NA

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/6184/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7807/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/6531/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/6189/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/6191/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7815/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/6539/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/6196/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/6546/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7822/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/6201/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7827/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/6553/

LGTM


Add colorblind mode

#1213

Description
Implemented a colorblind mode option for the Rapid map. This PR aims to resolve Issue #1213.
These changes will help improve map accessibility for people with red-green colorblindness. It also sets the stage for future colorblind modes to be added. The modifications include the addition of a new color scheme, red_blind, or Protanopia, and a map color scheme combobox in the preferences sidebar that changes the map color scheme based on the user's selection.
Screenshots:
Code weaknesses and future updates:

@Bonkles adding you here for progress updates and any feedback you may have.

Are these run fail errors problematic?

Let me look into what's going on with the infra errors- these are not your fault @lauble !

@Bonkles I need some help with the combobox labels. I've been trying to get the info from the core.yaml file, but it isn't showing the information I want in the UI. (i.e. I want default to show as Default, red_blind to show as Protanopia, etc.) Can you help point me in the right direction?

I'd say to check to see if d really is what you think it is in this case- since the combo box data values are objects with a title and a value I would think you'd need to specify either d.title or d.value like so:
.text(d => l10n.t(preferences.color_selection.${d.title}))

These changes emulate color blindness, rather than correct for it. Future research on the use of color matrices to correct for color blindness is needed.

Thanks, this looks like a good start.  That's a good point that simulating color blindness isn't really what we're after, but correcting for it could be useful.
This PR has gone a bit stale and I need to fix some color styling issues today, so I'm going to merge as-is and hide/comment some of the parts of the code until it can be developed more fully.


serde_derive additions should be breaking changes

New versions of serde_derive are incompatible with older versions of serde which constitutes a backwards compatibility break according to semver. An incompatibility will cause confusing error messages about serde_derive implementing trait methods that don't exist in a trait. If Cargo for some reason decides to use serde, say 1.0.23 and serde_derive version 1.0.55 (which is perfectly fine if you depend on say, serde="1.0" and serde_derive="1.0"), things will break - I had issue like this happening a few times.
Yes, fixing this will cause serde_derive to rapidly increase its major version each time it will attempt to implement a new method, I think that's fine. Additionally, it won't be that often - this way it won't be required to release a new version of serde_derive each time a new version of serde would be released. Version numbers aren't meant to be pretty but meaningful.

I mean, you can use serde = { version = "1.0", features = ["derive"] } if you like, in this case version of serde_derive is unimportant, and the combination of both would be still semver compatible. The issue is when using serde and serde_derive separately in Cargo.toml.

Thanks for raising this issue! There are advantages and disadvantages in both directions. I believe on balance our current versioning policy is less bad. It would cause more confusion if users need to track down a working major version each time they find a feature on the website that they would like to use. And it would cause untold headaches if large projects end up compiling a dozen separate versions of serde_derive from their various transitive dependencies.
Ultimately I would like to see Cargo handle this use case better. It comes up regularly in procedural macros that we need to constrain a version of a crate that our users depend upon but the macro does not.
I would also be happy to accept improvements to documentation that explains the serde and serde_derive versions should be kept in sync.