Boot process hangs sometimes (Possible deadlock?)

I use AppleALC since Sierra PB3 through PB4 so I can not speak for earlier versions. I use this commit since the latest release had kernel panics on sierra: d21d436c9a78ce291c960c61f8901c613213812a
What I experience is that some times the boot just hangs (apple logo / stalling progress bar). Then I have to hard reset and try again. Then it works (most of the time). It happens mostly when I start the Hackintosh for the first time at that day (cold start / no reboot). Some times it does not work multiple times after another then I try booting without caches or just verbose mode, which resolves the issue. When I remove AppleALC the problem does not appear.
You added some locks  in the latest patches. My guess without looking too hard at the code is that you probably introduced a race condition resulting in a deadlock under the wrong circumstances.
This makes sense because locks are notorious for introducing deadlocks and changing the timing (verbose mode, no caches) resolves the issue.

Hi,
Unfortunately the issue is much deeper than you might think. That's not me but Apple introduced a dead lock in Sierra, right here. It assumes that the callback runs very quickly and acquires a memory allocation lock right afterwards. However, an interrupt is generated and the lock is acquired in the other place locking the boot process forever.
My initial idea was to disable interrupts, however, due to XNU specifics they could have gotten reenabled at certain places, and disabling them led to malfunctioning of certain parts of code.
My second idea was to acquire the memory allocation lock itself and avoid allocating any memory myself. However, the IOReg APIs I use do that, and to let them function I need to release the lock.
There clearly is a race-condition here, in fact three, and I am aware of all. First the initial one between lock acquisition in the beginning of my callback, and an interrupt. Second one between interrupts and lock releases allowing memory allocations to succeed. Third one between the release of the lock in my handler, and an acquisition of it later right outside in XNU.
The first one should not happen in a way it does not normally happen without AppleALC, the timing is basically the same, and even though that code is deadly Apple relies on it. The third one can be fixed by nopping upstream lock instructions and not releasing the lock itself.
The second one is worst, and it might be the one you have trouble with, I initially forgot about those APIs allocating memory, and calling them before is not possible because they use the results of probing performed by AppleHDAController (and because IORegistry is not even filled earlier).
You could try disabling interrupts and then enabling them in the lock releases I added for Sierra around IOReg APIs, but that will almost certainly panic since it seems to call the allocator via an interrupt. All in all it is important to know where exactly it hands, so if you have kernel debugger, it would be of some help, otherwise try to boot in -v -alcdbg mode and record the lines appearing before a hang.

Thank you for the extensive explanation. Although I have some driver development experience with Linux I can't comprehend all the things you wrote. Basically because I do not have a broad overview about how AppleALC does the kext patching.  I guess most of the callbacks and functions you are using for that you have extracted from the XNU sources because they are not included in the SDK, right? But how did you know what changes Apple did in Sierra? They did not release the sources, yet.
Does there exist some broad overview into the AppleALC code which could get other developers started? Of course I could just read the source (I have to do this anyways) but some short guide with the broad concepts used and where the caveats are would be really helpful.
I added  -v and -alcdbg to clover. Will report back when it happens again.

Well, in brief AppleALC installs itself to a callback invoked after loading every kext, and when the kext matches AppleHDAController/AppleHDA (or some others) it runs a [handler)(https://github.com/vit9696/AppleALC/blob/master/AppleALC/kern_alc.cpp#L107), which solves codec controller info, codec info, patches kext memory, installs intercepting callbacks to resource loading functions. Most of the code was commented (I tried to make it easy to read) but I guess some questions may still arise.
As for Sierra specifics… as usual this was understood via some basic reverse-engineering. Several APIs used are indeed not available as public APIs, and I have to solve their addresses in memory.
I will be waiting for your report, thanks!

I tried starting with -alcdb. It did not stall while I had it enabled. I had to remove it because when it is enabled the sound is completely broken (delay and quality) and the OS is somewhat laggy. I played a game and it was as if I had very low FPS while the FPS counter said 100 fps. Is this intended?

-alcdbg* This is not really possible. The only cause could be -v, but that is also unlikely. AppleALC prints almost nothing to system log after booting (unless you have constant kextload/kextunload).

Okay then it was a coincidence I guess. I will add it back and report when it happens again.

Did not happen so far (right now I am booting only once a day and do not have time for extensive testing). I looked into the code and noticed that I have to compile it with "#define DEDBUG" to have the "DBGLOG" print something (in addition to adding the parameter). I guess I have to deploy a debug build to have this enabled. I will add the define in the release build to not alter the timing too much.

Okay I tried to just enable DBGLOG unconditionally instead of doing a proper Debug build. That did not work: The kext loaded but did no parching at all -> no devices
Don't know why but it was this way (tried 3 boots always the same)
Then I did a proper debug build and got multiple hangs. All of them ended with this message being printed forever in quick succession:
"alc @ codec entry misses properties, skipping"
I could not see what was in the Log before because it fills the whole screen very quickly.

Mhm. That's weird. The message you get is printed when AppleALC fails to obtain codec information, i.e. IOHDACodecVendorID and IOHDACodecRevisionID. According to AppleHDA (well, its assembly), one is supposed to continue asking IOReg for these values. Perhaps it gets not enough time to load it in a separate thread, so I could suggest you moving the locks a bit?

Shouldn't IORegistryEntry::getProperty block because it returns the value? So there is no race condition between the retrieval and the re-obtaining of the lock.
Allow me some more questions regarding the broader situation. Do you know why the memory lock acquired by the interrupt blocks the boot process? Is this some deadlock between the thread that executes the callback and later tries to acquire the lock? I mean to deadlock there must be another lock or resource that is held by the callback thread (so they wait for each other). Maybe that is the place to start.

Shouldn't IORegistryEntry::getProperty block because it returns the value? So there is no race condition between the retrieval and the re-obtaining of the lock.
Ah, sorry, I might have sounded confusing. getProperty does nothing but returns the current value after obtaining it from IOReg. What I fear is that the value itself does not make its way to IOReg due to the memory allocation lock. I do not think this should be the case but given your prints in the log it is the first assumption that arises in my head.

Do you know why the memory lock acquired by the interrupt blocks the boot process?
It is not like I know what exactly is acquired by the interrupt. I know that kext loading stops if does not acquire memory lock quickly enough. Quite possible the interrupt has nothing to do to the memory lock I acquire but something else. My only experience with Sierra so far is a VM installation and a few hours of static disassembly. I would prefer not to speculate but so far it is likely that the whole thread is suspended and never resumed. The right way here is to set a kernel debugger up and see what actually happens. But that's the matter of time I cannot imagine myself spending on it at the moment.

I had this error now 5 times since my last posting. It was always the same message as before:

alc @ codec entry misses properties, skipping

At least it is always the same error. Since it is not reproducible it is hard to check if moving the locks helps fixing the error.

@athei ,
you tred this: https://clover-wiki.zetam.org/Configuration/Devices#devices_audio_audio-resethda

I did not know about it. I just added the key and will report back. Is there a way to verify that the ResetHDA is working? Did not find any key to enable logging in the clover wiki.

Clover debug output can be read with bdmesg but I do not think RestHDA actions are logged anywhere.

Okay I tested for a while and unfortunately the bug is still there. Sometimes the boot just hangs. Am I really the only one that experiences this?

Yes. So far you are the only one. I do really wonder whether this is an AppleALC issue. As I explained above the "freeze" is not really a freeze but just AppleALC trying to obtain the necessary codec information from IOReg. It loops for quite a while here. The max count value is really large and for this reason it looks like a feeze.
Since the information is not there it is likely that the codec is not initialising most of the time for a weird reason. You could disable AppleALC or reduce the max count but that would not change the fact AppleHDA(Controller) is not loading (!).
Why… I do not know, perhaps your codec needs some commands from codec commander or something. Maybe it is a good idea to ask other people having the same codec? Also, if the issue is still there, why not to try VoodooHDA? Sound quality is the same, just voodoo often needs some configuration.

Hi,
Today I received the same error on which you discuss. I'm not sure whether panic report will be necessary, but  I will post it:
*** Panic Report ***
panic(cpu 3 caller 0xffffff8000310785): "thread_invoke: preemption_level 1, possible cause: blocking while holding a spinlock, or within interrupt context"@/Library/Caches/com.apple.xbs/Sources/xnu/xnu-3789.1.32/osfmk/kern/sched_prim.c:2077
Backtrace (CPU 3), Frame : Return Address
0xffffff911116b990 : 0xffffff80002f748c
0xffffff911116ba10 : 0xffffff8000310785
0xffffff911116ba90 : 0xffffff800030f4ee
0xffffff911116bad0 : 0xffffff80004020a9
0xffffff911116bb30 : 0xffffff800089040a
0xffffff911116bbe0 : 0xffffff7f82d536e5
0xffffff911116bc00 : 0xffffff7f82d490df
0xffffff911116bca0 : 0xffffff7f82d48e92
0xffffff911116bce0 : 0xffffff7f82d542d6
0xffffff911116bd20 : 0xffffff800084e778
0xffffff911116bda0 : 0xffffff8000845ee4
0xffffff911116be10 : 0xffffff8000852c92
0xffffff911116be60 : 0xffffff80008b6f90
0xffffff911116be80 : 0xffffff800089b44e
0xffffff911116bf10 : 0xffffff800089b0d6
0xffffff911116bf60 : 0xffffff800089caee
0xffffff911116bfb0 : 0xffffff80002a6af7
      Kernel Extensions in backtrace:
         as.vit9696.AppleALC(1.0.16)[A2176A8D-0B84-3DEC-884D-4F94324ABD91]@0xffffff7f82d48000->0xffffff7f82e02fff

@pkk0 it is unlikely the issue is the same, your panic log without keepsyms=1 in boot-args is useless.

@vit9696 What keepsyms=1 flag does?

You will see the symbol names (function names) instead of their addresses in the panic log.

Does the issue still happen with the recent version?

In my case, the problem seems to be solved.

With which version? As far as I remember it also happened for 1.17 for me. Right now I removed the kext because of this problem. I can test with the next version :)

Latest commit probably.

I installed the latest commit 9ed485d7b5544212c5299bddee315a4e4b2c463a
It is still happening for me. I never had a panic. It's always the hang like already discussed. When it happens it's always after a coldboot and then most of the time I have to reset multiple times before it works again.
I mean we all know that there are race conditions. It's just that my hardware config has the "right" timings while others are more lucky.

Sigh. Pretty much expected. Anyway, we got a source release from apple, and I am somewhat hoping to understand things better now.  Please check it out.

Installed it! Will report back in a few days when I have enough data.

@athei so, may I assume it isbetter now?

Didn't had that much boots since then because I was away from home. I think approximately 10 boots without the error surfacing. So it did not happen since then bot some times the error does not surface for a while. But it is looking very promising.

Well then, I should probably release an update now and close this issue.
If it appears again, the cause will likely be different from the previous one, so create a new report.
Thanks.


VD-26 remove project icon & advanced search option, and change VB ico…

…n behavior and rename to index.html

Several changes are made:

Remove Project icon at Detailed Table
Remove Advanced Search Option at top search bar (IR related)
Adjust VB icon on top left (may need to change the link later)
Change vb_geohashes_mean.html to index.html per Bob

added VB icon at /images and change its location at index.html


[FR] - LiveView and cli query tip should include current epoch / slot information

Currently the sample output of querying the tip information outputs:
Tip (SlotNo {unSlotNo = 32032}) (ShelleyHash {unShelleyHash = HashHeader {unHashHeader = f14ed0605fa5cc0ada0c0445a1948e9682cf85b0d9e63860e2a803aa433e5af6}}) (BlockNo {unBlockNo = 8248})
it would be useful for pool operators to have a new field that would show current epoch / slot within the epoch, to save us needing to do the querying of genesis settings and doing modulo arithmetic.
Similarly, LiveView could be enhanced to add a field to show current network clock (epoch / slot no), so to speak - this would make it easier to detect whether the last time node fetched some new block information from the network was a long time ago (e.g. indicating stuck network / stuck node).

Hi bergr01, this is Viktor at IOHK Tech Support. Thank you for submitting this feature request. We have added it to our backlog and we`ll allocate it to one of our future development sprints. We appreciate your participation and support for the Cardano project!

Since LiveView is officially deprecated and will be removed from the node very soon, I'm closing this issue. Please check RTView, our new tool for real-time watching for Cardano nodes. You can open an issue here.


Add version control support inside spyder

From<EMAIL_ADDRESS>on 2014-08-01T03:14:39Z
Now that I have been working with version control for my own research and for spyder development I am finding 'annoying' having to go to the console to commit changes, doing pulling and pulling of files and repo...
I think that there should be some sort of version control functionality (git and hg with github and bitbucket  etc...) so that within the code editor (or within spyder with a new plugin) you could easily do version control managing.
I think a way to do this would be to create a new plugin that is linked to the code editor file so that the selected file would display info on its version control. Initially it could support basic things and we could build from there.
Features:
=========
-init a repo and add files
-keep track of files if added
-allow one click commit+push plus some keyboard shortcuts!
-display online repos for a github/bitbucket account (initially....)
-allow pull from online repos listed
-restore file to a previous commit
-display colored versions diff?
This plugin can be kept simple and minimalist but could aid enormously in the creation and development of reproducible science and also in the development of spyder itself.
If we can agree on some basic roadmap I can start laying out the basics.
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=1919

From contrebasse on 2014-08-02T10:53:05Z
This is a duplicate of issue #816 .
I personally prefer having a separate window for version control, but more options is good!
BTW, you can launch a system console inside spyder to do version control (I don't use it either).

From ccordoba12 on 2014-08-23T14:01:30Z
Status: Duplicate
Mergedinto: 816

From<EMAIL_ADDRESS>on 2014-08-02T11:17:09Z
Yes... I realized that afterwards... I forgot to look first. My bad.
Can someone delete this issue? or merged it to the other one?
I personally prefer a minimum extra help... like I start a new file in a folder and I want to init a repo and then add this file.. it should be simple... like a shortcut..
Then after some work I would like to commit... maybe another shortcut... and have a popping up windows asking for the message of the commit...
Just make life easy, not adding to many features, but just the minimum :)


Running on an asymmetric equilibrium does not save the asymmetric quantities

I am running this version of booz_xform to benchmark the DESC implementation of the boozmn.nc style output files, and for asymmetric cases I noticed that the saved .nc file from this booz_xform does not seem to save the asymmetric quantities, even though they are calculated and accessible through the structure after b.run() is called. printing b.asym results in True so the flag seems to be set correctly, and the quantities do end up being calculated so it is probably just a logic thing in the write call.
Maybe I am doing something wrong with the write call, but I don't thing the write call takes any arguments. My script is shown here, I end up saving the asymmetric quantiites as .npy files to get around this
import booz_xform as bx
import time

t = time.time()
b = bx.Booz_xform()
nsurfs=100
b.read_wout(f"wout_QA_asym_{nsurfs}_surfs.nc")
b.mboz =40
b.nboz = 40
print(b.asym)
#print(b.compute_surfs)
b.run()
print(b.rmns_b)

import numpy as np
np.save(f"rmns_b_{nsurfs}_{b.mboz}.npy",b.rmns_b)

np.save(f"zmnc_b_{nsurfs}_{b.mboz}.npy",b.zmnc_b)
np.save(f"bmns_b_{nsurfs}_{b.mboz}.npy",b.bmns_b)
np.save(f"gmns_b_{nsurfs}_{b.mboz}.npy",b.gmns_b)
np.save(f"pmnc_b_{nsurfs}_{b.mboz}.npy",-b.pmnc_b) # negated to abide by the legacy sign convention

b.write_boozmn(f"boozmn_{nsurfs}_surfs_QA_asym_sims_booz_{b.mboz}.nc")
print(f"time taken: {time.time()-t} s")```

Hi @dpanici , I tried your example just now with the non-stellarator-symmetric equilibria tests/test_files/wout_up_down_asymmetric_tokamak.nc and tests/test_files/wout_LandremanSenguptaPlunk_section5p3.nc. In both cases, I do see the fields rmns_b, zmnc_b, bmns_b, gmns_b, and pmnc_b in the .nc output file. The logic for writing these fields is here, and looks ok. Do you experience the problem with those two specific wout files in the repo?

Ah sorry, I realize I was using an older pip version 0.0.6, this is working now with 0.0.8. Thanks!


Add UI Notification for Invalid Mod Installs

https://user-images.githubusercontent.com/64006268/221428440-8e58d698-c8d2-4804-bf2a-781adaa19f0a.mp4
Display a notification if incorrectly installed mods are found.
Depends on

[ ] https://github.com/Alystrasz/NorthstarLauncher/pull/3
[ ] https://github.com/R2Northstar/NorthstarLauncher/pull/415

haven't tested, but ui looks great!

The compile check fails because some exposed function signatures have been corrected in https://github.com/R2Northstar/NorthstarLauncher/pull/415.

The compile check fails because some exposed function signatures have been corrected in R2Northstar/NorthstarLauncher#415.

In that case you can already update the signatures in .github/nativefuncs.json. The mods CI technically does not depend on launcher code (but should obviously be kept in sync :P)

Btw panel_mainmenu.nut is a new vanilla file @GeckoEidechse

@uniboi this is currently broken due to outside changes using native functions that are removed in this PR. (also merge conflicts)

I'm not sure if this is even needed anymore. I haven't seen someone manually installing mods incorrectly in a while. Maybe most people are using mod managers now?

I'm not sure if this is even needed anymore. I haven't seen someone manually installing mods incorrectly in a while. Maybe most people are using mod managers now?

A vast amount of people dont use mod managers and screw it up
Plus, this extra info doesnt hurt

@uniboi I think your branch is outdated, the feature does not work anymore

@uniboi there's currently some merge conflicts.

@uniboi bump

bump

@uniboi 'sup?


[BUG] Error getting an EventType using the topicIntegratorConnector

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Attempting to create an EventType gives this error :
PropertyServerException{reportedHTTPCode=500, reportingClassName='org.odpi.openmetadata.commonservices.ffdc.RESTExceptionHandler', reportingActionDescription='getEventTypeByGUID', reportedErrorMessage='OMAG-GENERIC-HANDLERS-500-002 The Data Manager OMAS service has not implemented the getNewBean(entity) method in a subclass of the org.odpi.openmetadata.accessservices.datamanager.converters.EventTypeConverter converter class for bean class org.odpi.openmetadata.accessservices.datamanager.metadataelements.EventTypeElement and so is unable to create the bean for method getEventTypeByGUID', reportedErrorMessageId='OMAG-GENERIC-HANDLERS-500-002', reportedErrorMessageParameters=[Data Manager OMAS, getNewBean(entity), org.odpi.openmetadata.accessservices.datamanager.converters.EventTypeConverter, org.odpi.openmetadata.accessservices.datamanager.metadataelements.EventTypeElement, getEventTypeByGUID], reportedSystemAction='The system is unable to process the request because it is not able to populate the bean.', reportedUserAction='Correct the converter implementation as part of this module.', reportedCaughtException=null, reportedCaughtExceptionClassName='null', relatedProperties=null}
at org.odpi.openmetadata.commonservices.ffdc.RESTExceptionHandler.throwPropertyServerException(RESTExceptionHandler.java:283)
at org.odpi.openmetadata.commonservices.ffdc.RESTExceptionHandler.detectAndThrowStandardExceptions(RESTExceptionHandler.java:126)
at org.odpi.openmetadata.accessservices.datamanager.client.rest.DataManagerRESTClient.callEventTypeGetRESTCall(DataManagerRESTClient.java:1427)
at org.odpi.openmetadata.accessservices.datamanager.client.EventBrokerClient.getEventTypeByGUID(EventBrokerClient.java:1004)
at org.odpi.openmetadata.integrationservices.topic.connector.TopicIntegratorContext.getEventTypeByGUID(TopicIntegratorContext.java:524)
at .....
Expected Behavior
The error message indicates " has not implemented the getNewBean(entity) method in a subclass of the org.odpi.openmetadata.accessservices.datamanager.converters.EventTypeConverter"
I assume that we need a getNewBean(entity) method  in EventTypeConverter, similar to the method in TopicConverter.
I also need to ensure that the create processing associated this EventType with the Topic asset as its anchor
Steps To Reproduce
Create a topicIntegration connector that issues myContext.createEventType(topicGUID, properties)
Environment
- Egeria:
- OS:
- Java:
- Browser (for UI issues):
- Additional connectors and integration:

Any Further Information?
No response

This is not the correct fix.  EventType is a schema attribute and so getNewBean(entity) should not be called for a get.
The question is why is the converter called for create ...?   What are the messages/stack trace in the metadata server.

As discussed, the error is actually in get not create.  sorry to mislead you @mandy-chessell .

@mandy-chessell I have the above fix on and can see in the Rex Ui that a topic has an EventTypeList that has an EventType. My integration connector issues a call to the context to get the event-types associated with a topic. This issues an OMAS GET call  https://localhost:9443/servers/cocoMDS1/open-metadata/access-services/data-manager/users/fred/topics/9ebef6c1-4ff8-4161-8331-299fabb141a7/event-types?startFrom=0&pageSize=1000  ,which ends up in the generic handler line 8514.  where is still getting the 'OMAG-GENERIC-HANDLERS-500-002 error as below. This exception is swallowed because the code thinks it is an inaccessibility exception - but it is a real error.
 I have not done testing to prove it but this appears to be a regression.


about pubsub

In what area(s)?

/area pubsub

What version of Dapr?

1.8.4
edge: output of git describe --dirty

Expected Behavior

My pubsub file:
apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
  name: pubsub
spec:
  type: pubsub.redis
  version: v1
  metadata:
  - name: redisHost
    value: <IP_ADDRESS>:6379
  - name: redisPassword
    value: ""

but

time="2022-10-18T03:13:34.759517528Z" level=info msg="log level set to: info" app_id=sub instance=2070cd0f7e09 scope=dapr.runtime type=log ver=1.8.4
time="2022-10-18T03:13:34.759580176Z" level=info msg="metrics server started on :9090/" app_id=sub instance=2070cd0f7e09 scope=dapr.metrics type=log ver=1.8.4
time="2022-10-18T03:13:34.760186991Z" level=info msg="standalone mode configured" app_id=sub instance=2070cd0f7e09 scope=dapr.runtime type=log ver=1.8.4
time="2022-10-18T03:13:34.760212026Z" level=info msg="app id: sub" app_id=sub instance=2070cd0f7e09 scope=dapr.runtime type=log ver=1.8.4
time="2022-10-18T03:13:34.760490452Z" level=info msg="mTLS is disabled. Skipping certificate request and tls validation" app_id=sub instance=2070cd0f7e09 scope=dapr.runtime type=log ver=1.8.4
time="2022-10-18T03:13:34.760946078Z" level=info msg="local service entry announced: sub -> <IP_ADDRESS>:38721" app_id=sub instance=2070cd0f7e09 scope=dapr.contrib type=log ver=1.8.4
time="2022-10-18T03:13:34.760965767Z" level=info msg="Initialized name resolution to mdns" app_id=sub instance=2070cd0f7e09 scope=dapr.runtime type=log ver=1.8.4
time="2022-10-18T03:13:34.761092103Z" level=info msg="loading components" app_id=sub instance=2070cd0f7e09 scope=dapr.runtime type=log ver=1.8.4
time="2022-10-18T03:13:34.763154305Z" level=info msg="component loaded. name: pubsub, type: pubsub.redis/v1" app_id=sub instance=2070cd0f7e09 scope=dapr.runtime type=log ver=1.8.4
time="2022-10-18T03:13:34.763202536Z" level=info msg="waiting for all outstanding components to be processed" app_id=sub instance=2070cd0f7e09 scope=dapr.runtime type=log ver=1.8.4
time="2022-10-18T03:13:34.829538296Z" level=warning msg="error initializing state store statestore (state.redis/v1): redis store: error connecting to redis at localhost:6379: dial tcp <IP_ADDRESS>:6379: connect: connection refused" app_id=sub instance=2070cd0f7e09 scope=dapr.runtime type=log ver=1.8.4
time="2022-10-18T03:13:34.829571504Z" level=warning msg="error processing component, daprd process will exit gracefully" app_id=sub instance=2070cd0f7e09 scope=dapr.runtime type=log ver=1.8.4
time="2022-10-18T03:13:34.829578428Z" level=info msg="dapr shutting down." app_id=sub instance=2070cd0f7e09 scope=dapr.runtime type=log ver=1.8.4
time="2022-10-18T03:13:34.82958401Z" level=info msg="Stopping PubSub subscribers" app_id=sub instance=2070cd0f7e09 scope=dapr.runtime type=log ver=1.8.4
time="2022-10-18T03:13:34.829589901Z" level=info msg="Stopping Dapr APIs" app_id=sub instance=2070cd0f7e09 scope=dapr.runtime type=log ver=1.8.4
time="2022-10-18T03:13:34.829599336Z" level=info msg="Waiting 5s to finish outstanding operations" app_id=sub instance=2070cd0f7e09 scope=dapr.runtime type=log ver=1.8.4
time="2022-10-18T03:13:39.830010348Z" level=info msg="Shutting down all remaining components" app_id=sub instance=2070cd0f7e09 scope=dapr.runtime type=log ver=1.8.4
time="2022-10-18T03:13:39.830221881Z" level=fatal msg="process component statestore error: redis store: error connecting to redis at localhost:6379: dial tcp <IP_ADDRESS>:6379: connect: connection refused" app_id=sub instance=2070cd0f7e09 scope=dapr.runtime type=log ver=1.8.4

what?
error connecting to redis at localhost:6379: dial tcp <IP_ADDRESS>:6379: connect: connection refused
Actual Behavior

Steps to Reproduce the Problem

Release Note

RELEASE NOTE:

error initializing state store statestore (state.redis/v1): redis store:

In addition to the pubsub.redis component instance configuration, do you have a state.redis component instance configuration?

error initializing state store statestore (state.redis/v1): redis store:

In addition to the pubsub.redis component instance configuration, do you have a state.redis component instance configuration?

thank you
This is the problem of  state.redis


Doesn't work in Laravel 5.3

I cannot get this package to install in laravel 5.3 with composer. I get the following error:
composer require thiagof/laravelrpc
Using version ^0.1.4 for thiagof/laravelrpc
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for thiagof/laravelrpc ^0.1.4 -> satisfiable by thiagof/laravelrpc[0.1.4].
- Conclusion: remove laravel/framework v5.3.18
- Conclusion: don't install laravel/framework v5.3.18
- thiagof/laravelrpc 0.1.4 requires illuminate/support >=5.0,<5.2 -> satisfiable by illuminate/support[v5.0.0, v5.0.22, v5.0.25, v5.0.26, v5.0.28, v5.0.33, v5.0.4, v5.1.1, v5.1.13, v5.1.16, v5.1.2, v5.1.20, v5.1.22, v5.1.25, v5.1.28, v5.1.30, v5.1.31, v5.1.41, v5.1.6, v5.1.8].
- don't install illuminate/support v5.1.1|don't install laravel/framework v5.3.18
- don't install illuminate/support v5.1.13|don't install laravel/framework v5.3.18
- don't install illuminate/support v5.1.16|don't install laravel/framework v5.3.18
- don't install illuminate/support v5.1.2|don't install laravel/framework v5.3.18
- don't install illuminate/support v5.1.20|don't install laravel/framework v5.3.18
- don't install illuminate/support v5.1.22|don't install laravel/framework v5.3.18
- don't install illuminate/support v5.1.25|don't install laravel/framework v5.3.18
- don't install illuminate/support v5.1.28|don't install laravel/framework v5.3.18
- don't install illuminate/support v5.1.30|don't install laravel/framework v5.3.18
- don't install illuminate/support v5.1.31|don't install laravel/framework v5.3.18
- don't install illuminate/support v5.1.41|don't install laravel/framework v5.3.18
- don't install illuminate/support v5.1.6|don't install laravel/framework v5.3.18
- don't install illuminate/support v5.1.8|don't install laravel/framework v5.3.18
- don't install illuminate/support v5.0.0|don't install laravel/framework v5.3.18
- don't install illuminate/support v5.0.22|don't install laravel/framework v5.3.18
- don't install illuminate/support v5.0.25|don't install laravel/framework v5.3.18
- don't install illuminate/support v5.0.26|don't install laravel/framework v5.3.18
- don't install illuminate/support v5.0.28|don't install laravel/framework v5.3.18
- don't install illuminate/support v5.0.33|don't install laravel/framework v5.3.18
- don't install illuminate/support v5.0.4|don't install laravel/framework v5.3.18
- Installation request for laravel/framework (locked at v5.3.18, required as 5.3.*) -> satisfiable by laravel/framework[v5.3.18].
Installation failed, reverting ./composer.json to its original content.

Yes upgraded the package to laravel latest version
Please check out again


-p flag is not working

Expected behavior:
dapr dashboard -p 33291
Dapr Dashboard running on http://localhost:33291

Actual behavior:
dapr dashboard -p 33291
Dapr Dashboard running on http://localhost:8080

It's always using 8080 even when port is provided.

cli need to pass the flag to dashboard.


:sparkles: Introducing ActionsColumn Component in Assessment Table

This PR introduces the ActionsColumn component in the assessment table

Awesome! Nitpicks with self-closing tags, take them or leave them.
TIL about the ActionsColumn component, I suppose we should update the other composable tables to use it too

+1 Opened this issue to track https://github.com/konveyor/tackle2-ui/issues/1318


Need to add SSH server support to the default local.conf

closed by adding the openSSH components configurations inside the local.conf


Fix bug in PR #1237

Description

PR #1237 had a bug uncovered by internal integration tests. Need to check that an mpiAction is deifned before querying runActionExclusive.
Checklist

[x] This PR has only one purpose or idea.
[x] Tests have been added/updated to verify that the new/changed code works.

[x] The code style follows good practices.
[x] The commit message(s) follow good practices.

[x] The release notes (location doc/release/0.X.rst) are up-to-date with any bug fixes or new features.
[x] The documentation is still up-to-date in the doc folder.
[x] The dependencies are still up-to-date in setup.py.

I'm assuming that the internal test was resolved with this PR?
Also, can you add some context to PR #1237? It's difficult to know if this PR solves the problem without any context (outside of the PR title) for why these changes were made in the first place. E.g., why the PR was necessary and how the proposed changes accomplish the task.
I'm also not super familiar with our mpi usage in general so I'm going to tag in @john-science to give a hand here.


Reduce the pod count to pass the windows load test

The windows load test times out from testgrid. And after SSH  to windows vm, the pause image is loaded, and around 30 pods are up running. Maybe 80 is too big, so change to 10 to see if it's the cause.

/cc @pjh @yliag

cc @yliaog

/assign @krzysied

/ok-to-test
/lgtm

/approve


Allow to use OpenBSD specific service_flags and package_flavors.

Give example for passenger in README.md and add OpenBSD to the
supported OSs in metadata.json.

Neat! Thanks for the code!


Pass Chocolatey Arguments as one parameter (install options?)

We would like to be able to pass through arguments directly to Chocolatey, without needing to add a parameter for each new option. Would you be keen to this?

@ferventcoder Already made a PR for this. See #50.
This takes only switch params right now. I could adjust it to take anykind of param. Accepting ANY param would break paramvalidation.
Another option would be to just wrap all chocolatey params in a single string.

@javydekoning I didn't see it allowed choco switch parameters - I see that now.
I totally meant something like chocoSwitchParams, but no mapping on what could be passed to it.
At the end of the day, instead of trying to keep track of all of the arguments that can be passed (you missed all of the pro/business edition switches/options by the way ;) ) and permutations of how those could be passed, the param could be a simple string array that passes those switches straight through and allows choco to validate them.

Very nice! I provided some comments on the PR.

Duplicate of #45 ?

@ferventcoder This would superseed #45 and #12 indeed.
Secondly, I have to agree with you here. I think I should change #50 and implement it your way. This way there is no validation in DSC but you are able to pass anything down to choco. @ebekker @lawrencegripper what do you guys think?

Sounds good to me as it would allow more flexibility for users and reduce maintenance overhead of the DSC resources. Loss of validation is a shame bit feels like a fair trade-off

Ok good, I'll re-write this somewhere later this week.

@ferventcoder so we have 2 options here:

Array:
cChocoPackageInstaller skype
{
Name = "skype"
chocoParams = 'allowdowngrade',
'allowemptychecksum',
'execution-timeout=200'
Ensure = 'Present'
Version = '<IP_ADDRESS>'
PsDscRunAsCredential = $Credential
DependsOn = "[cChocoInstaller]installChoco"
}

String:
cChocoPackageInstaller skype
{
Name = "skype"
chocoParams = '--allowdowngrade --allowemptychecksum --execution-timeout=200'
Ensure = 'Present'
Version = '<IP_ADDRESS>'
PsDscRunAsCredential = $Credential
DependsOn = "[cChocoInstaller]installChoco"
}

Either way it's going to be different from 'version' and 'Params'. I think that might be confusing to the user. I'm leaning towards the string option but it the array option looks a bit harder in code.
@lawrencegripper @ebekker opinions?

I agree, the string option seems like the best route. Always a fan of keeping things simple, when appropriate, and it also keeps things consistent with the way in which the other package "params" option works too.

I'd say string.

Or both?

At least string.

Implemented as string. See PR #53
Example:
https://github.com/javydekoning/cChoco/blob/dfbae887be1e5fd14e0306ee920ee3207b8f4e74/ExampleConfig.ps1#L20-L27


[Filter] - behaviour

@oterral
The filters apply to the layers under "massnahme".
In http://web-emapis.prod.bgdi.ch/?massnahme=ch.blw.emapis-wegebau&typ=5214 the filter applies only to ch.blw.emapis-wegebau. Meaning the user should be able to add other layers from "Strukturverbesserungen", which will not be filtered.

Good point

It also means that if a layer is in the permalink and filtered (and hence checked at page start), after unselecting and selecting it, we should take care that it is not filtered this time.


Exercise cases changes

Exercise case changes extracted from: https://github.com/exercism/xruby/pull/585
Tests added.
Tests are not currently comprehensive but cover all lines according to simplecov.

https://github.com/exercism/xruby/pull/591


[Feature][Queue]`Queue manage ' is renamed' yarn queue manage '

At present, the name of queue management function is easy to be confused.
It is suggested to change it to yarn queue management

+1


Handle file paths that are not valid UTF-8

Rust makes a careful distinction between str and OsStr in order to allow handling strings that are permitted by the operating system but are not valid UTF-8. Paths are based on OsStr. Xi naively takes a String for the new_view command. Anyone making a frontend will have to handle paths that are potentially not valid UTF-8, and then figure out how to fit the square peg in a round hole when invoking the new_view command. What's the correct way for frontends to deal with this?

I've thought about this. The problem is that non-UTF-8 strings are a bear to encode in JSON. It can be done, say using base64, but then it's a very platform specific encoding.
How much of a problem is this in practice? It seems to me reasonable to say xi can't be used to edit files with such malformed names. I imagine a whole lot of other programming tools will also fail.

I could go either way. I'm not familiar enough with windows to know how much of a problem this will be in real use; but I don't think it would be too hard to allow the new_view rpc to optionally take a path_base64 argument, and there's definitely no reason for paths to ever be passed as Strings.

Relevant: https://github.com/serde-rs/json/issues/465


[Q] bitrate_monitor usage with alarm_command and periodic-bitrate params

I don't believe this is possible at the moment but thought I would ask in case there is a trick to make it work!
I'm trying to use the bitrate_monitor to monitor input and output bitrates, both for alarms and for status monitoring. I have a script that works to fire the alarm_command variables at an external service gathering data from tsswitch and other processes.
Is it possible for the alarm_command to be triggered at the specified period?
I can only make it trigger when the signal is outside min and/or max thresholds so this may be an enhancement on top of #31

I do not really understand your need. Could you precisely specify what you would like to achieve?

My apologies. I'm trying to monitor the bitrate of the transport streams entering and leaving tsswitch in a script which updates a database and monitoring dashboard.
If the bitrate_monitor plugin is started with --alarm-command and --periodic-bitrate arguments, it would be great if the script being called by --alarm-command received values at the --periodic-bitrate interval.
Does that make more sense?

OK, I see. Instead of the alarm command being run when there is a change of state, you would like it to be triggered at periodic intervals, reporting the current state, regardless of the state change. Do I get it correctly?
In that case, instead of changing the semantics of the current options, I would rather add some new --periodic-command option.  It would get a duration in seconds, just like --periodic-bitrate, and forces the --alarm-command to be run at periodic intervals, in addition to state changes.
I prefer to keep --periodic-bitrate outside of this because reporting a bitrate is a cheap action while running a command (process creation, etc) is more expensive. We may like to have a cheap periodic bitrate reporting and an expensive command launch on alarms only.

Yes thats correct. It's purely confidence monitoring to assist with fault finding when there are problems. Noted your comment about cheap and expensive actions, will try not to have too low an interval for reporting but your suggestion sounds excellent, thank you!

OK, option --periodic-command has just been added. Please try it and let us know if it works as expected

Apologies for the delay. Just compiled and tested (on Mac M1 Max), works as expected. I really didn't expect that to be done so soon, thank you so much!


Reorg repo for python only

https://github.com/leopiccionia/numista-sdk was created and is managing a JS SDK, so this can focus on Python only.

#3


Fix similar float values encoding overflow

If similar float values were encoded, the number of leading bits would
overflow the 5 available bits to store them (e.g. store 33 in 5 bits).  When
decoding, the values after the overflowed value would spike to very large and
small values.
To prevent the overflow, we clamp the value to 31 which is the maximum
number of leading zero bits we can encode.
Fixes #4357
Thanks @dgryski for help fixing this.

What does it actually mean to clamp? Do we lose some information?

Or is it purely cosmetic the way 00000000.0001 and 0.0001 are the same numbers?

@otoolep It means to restrict a value to a given range.  If a value is greater than the max value for the range, the value is set to the max value.  Similarly if it's below the minimum value for a range, it's set to the min.

Got it. This is not introducing any new range restrictions in our system, just enforcing existing restrictions I presume.

I understand there are some float differences so small that the tsm1 engine cannot encode them. But the test data uses a set of values I presume is to bring out the issue, yet the tests expect the same values back. So the system encoded them with perfect fidelity.
What am I missing here?

Yes.  Just fixing an overflow case where the number of leading zero bits overflow the allotted number of bits we have to store them.

OK, if it's leading bits, then makes sense, since the numbers are the same.
+1 in that case.


Improves stability of syncmanager samples

fixes crash from syncmanager swift sample #56
improves finding index of sendbird objects that received from collection
removes localization

Thank you for the update, unfortunately, we already moved on to another project.


Startsample.sh bad performances and crash with autoboot

IMPORTANT: Before you create an issue, please take a look at our Issue Reporting Guide.
Briefly summarize your issue:
The sample app launch with the pi as expected after following the solution from #https://github.com/alexa/avs-device-sdk/issues/539#issuecomment-369685404 but I have some problems:
-Alexa is very slow to answer, slower than a manual start. Radio and daily flashes are regularely interrupted. I even have trouble to trigger it.
-And inevitably, after some minutes it totaly crash, and have to reboot or launch alexa.service
Theses problems are not there with a manual start, where everything work like a charm.
I don't know how to access to logs from there, , here is the exit code:
`pi@Nestor:~ $ sudo systemctl status alexa.service
● alexa.service - Amazon Alexa
Loaded: loaded (/lib/systemd/system/alexa.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2019-01-13 05:09:20 CET; 6min ago
Process: 365 ExecStart=/home/pi/alexa.sh (code=exited, status=137)
Main PID: 365 (code=exited, status=137)
janv. 13 05:09:20 Nestor alexa.sh[365]: ##############################
janv. 13 05:09:20 Nestor alexa.sh[365]: #       Invalid Option       #
janv. 13 05:09:20 Nestor alexa.sh[365]: ##############################
janv. 13 05:09:20 Nestor alexa.sh[365]: #       Invalid Option       #
janv. 13 05:09:20 Nestor alexa.sh[365]: ##############################
janv. 13 05:09:20 Nestor alexa.sh[365]: #       Invalid Option       #
janv. 13 05:09:20 Nestor alexa.sh[365]: ##############################
janv. 13 05:09:20 Nestor systemd[1]: alexa.service: Main process exited, code=exited, status=137/n/a
janv. 13 05:09:20 Nestor systemd[1]: alexa.service: Unit entered failed state.
janv. 13 05:09:20 Nestor systemd[1]: alexa.service: Failed with result 'exit-code'.`
I wasn't able to install the "screen" solution following on the same issue i've refered earlyer, I don't know if it can help.
Does anyone have this problem ?
Tell us what hardware you're using:

[ ] Desktop / Laptop
[ x] Raspberry Pi
[ ] Other - tell us more:

Tell us about your OS (Type & version):

[ ] Linux
[ ] MacOS
[ x] Raspbian Stretch
[ ] Raspbian Jessy
[ ] Other - tell us more:

Hi @yoshitslc , I'm closing this issue due to inactivity. Feel free to reopen if you have further inquiries regarding this. Thanks


Unregistering processes

I'm not certain this is a bug, but looking for some clarification (I'm a bit new to Elixir, so sorry if this is obvious).
I integrated Swarm into an existing library using :via tuples. That seems to work fine, but tests that were killing a process and restarting it were failing. It seems there's a longer delay between a process being killed and Swarm.Tracker unregistering the process than with the Registry module.
Now that makes sense since in a distributed system it would take longer, but I'm testing on a single node so I didn't expect this to be an issue. I'm able to make the issue go away in tests by either using Process.sleep() or explicitly calling Swarm.unregister_name. I have an example project that reproduces the issue. Here's the relevant code:
  def test() do
    uuid = "b78932b0-1265-4317-bd92-3a1a3c64789e"
    TestSwarm.Supervisor.start_worker(uuid)
    TestSwarm.Worker.worker_state(uuid)
    shutdown(uuid)
    TestSwarm.Supervisor.start_worker(uuid)
    TestSwarm.Worker.worker_state(uuid)
  end

And the output:
iex(2)> TestSwarm.Helper.test()

15:03:40.975 [debug] Starting worker for uuid: "b78932b0-1265-4317-bd92-3a1a3c64789e"

15:03:40.982 [debug] [swarm on nonode@nohost] [tracker:handle_call] registering #PID<0.178.0> as "b78932b0-1265-4317-bd92-3a1a3c64789e", with metadata %{}

15:03:40.984 [debug] [swarm on nonode@nohost] [tracker:handle_call] add_meta {:workergroup, true} to #PID<0.178.0>

15:03:40.984 [debug] Starting worker for uuid: "b78932b0-1265-4317-bd92-3a1a3c64789e"

15:03:40.984 [debug] [swarm on nonode@nohost] [tracker:handle_monitor] "b78932b0-1265-4317-bd92-3a1a3c64789e" is down: :shutdown
** (exit) exited in: GenServer.call({:via, :swarm, "b78932b0-1265-4317-bd92-3a1a3c64789e"}, {:get_state}, 5000)
    ** (EXIT) no process: the process is not alive or there's no process currently associated with the given name, possibly because its application isn't started
    (elixir) lib/gen_server.ex:737: GenServer.call/3

If it's not a bug (which is probably likely), is there something my Supervisor or Worker needs to be doing?
Call Swarm.unregister_name from the Supervisor or in the terminate/2 of the worker?  I also thought that maybe I need to block until the tracker is updated, but I don't see a good spot to do that.

Where are you logging the Starting worker bit? From start_worker, the worker's start_link or init? Are you starting the child asynchronously in the start_worker implementation (i.e. in a Task or spawned process?)
It looks to me like the worker is started asynchronously, because the worker could not be fully started until it's registration is complete (in fact, init/1 is not even called until the registration has completed, as that's one of the first things GenServer does under the covers), and if it was complete, then :noproc is not possible (well, unless a bug is in play). However, reading registrations (what happens when you call whereis_name or do a lookup with {:via, :swarm, name}) is done by reading the registrations table (an ETS table) concurrently with modifications being made through the Tracker - so if you are doing the registration in parallel with the lookup, it may look like they happen in the correct order, but the read against the registry could still occur before the write does, and thus fail. Since register_name is blocking, calling it and then performing a subsequent lookup should always be consistent. Likewise with de-registrations. Another approach is to do something like this:
def send_work(name, work) do
  case Swarm.whereis_name(name) do
    nil ->
      case start_worker(name) do
        {:ok, pid} -> GenServer.call(pid, work)
        {:error, {:already_registered, pid}} -> GenServer.call(pid, work)
        {:error, _} = err -> throw err
      end
    pid when is_pid(pid) -> GenServer.call(pid, work)
  end
end

The above provides you with some extra protection from using :via tuples with call, and also gracefully handles the inherent race when two things try to start a worker with the same name at the same time.

Well, I don't think the worker is started asynchronously. This is how the worker is started in my example project:
  def start_worker(uuid) do
    Logger.debug(fn -> "Starting worker for uuid: #{inspect uuid}" end)
    case Supervisor.start_child(__MODULE__, [uuid]) do
      {:ok, _pid} -> {:ok, uuid}
      {:error, {:already_started, _pid}} -> {:ok, uuid}
      other -> {:error, other}
    end
  end

Which seems close to what you're suggesting. I'm basically just leaning on the builtin GenServer functionality to let me know if the process is registered or not. But even with your code, it still seems vulnerable to the process dying and Swarm not unregistering it yet. You might try looking at the example project to see how I'm killing the process: https://github.com/uberbrodt/test_swarm/blob/master/lib/test_swarm/helper.ex

I tried your solution and it matches on :already_registered, but the process is  dead so it errors out

I think this was just a timing issue in some test cases. Closing


Add SysDig monitoring to Traction namespaces

Add SysDig monitoring to bc0192 namespace set. Follow what already done for this ticket as draft: https://github.com/bcgov/DITP-DevOps/issues/63
Acceptance Criteria:

Add SysDig dashboards to bc0192-dev, bc0192-test, bc0192-prod
Add alerts for appropriate event in those environments
Provide DTS DevOps members with access to the dashboards

Hi @esune - Can you please let me know the who will require access to bc0192 namespace ?

Assuming Acceptance Criteria is to add dashboard monitoring in dev , test and prod environment and also adding alerts for them

@rajpalc7, I don't see a sysdigteam file for bc0192 here; https://github.com/bcgov/DITP-DevOps/tree/main/sysdig.  No PRs for one either.

@rajpalc7, Where would I find the links to the dashboards?  I don't see them listed here with the rest of them; https://trello.com/c/Mj9EqIzq/88-sysdig-dashboards

@rajpalc7, Were you going to do backups for the dashboards you created for bc0192?  I don't see a PR for them or any here; https://github.com/bcgov/DITP-DevOps/tree/main/sysdig/dashboard backups

@rajpalc7, Can you provide a summary and links to the dashboards and alerts so I'm not having to search for and guess at what you did?  Thanks.

@WadeBarnes - I just followed the ticket's acceptance criteria and did what was asked to do there. I can create the links for dashboards and alerts shortly.

Links for dashboards and alerts are available on https://trello.com/c/Mj9EqIzq/88-sysdig-dashboards now

https://github.com/bcgov/DITP-DevOps/pull/105/commits - Dashboards backup and sysdig team PR

@rajpalc7, All of the alerts for the bc0192-team are looking at the wrong namespace, they all contain a99fd4 in their queries.  Please review and fix.

Dashboards:

Traction - backup-int-traction-Test - bc0192

No data being displayed

Traction - backup-int-wallets-Test - bc0192

No data being displayed

Traction - tenant-ui-Dev - bc0192

Missing lots of data

Traction - tenant-ui-Test- bc0192

LInk to PVC Dashboard goes to https://app.sysdigcloud.com/#/shared/dashboard/a09b8b779e584909881eca7127eae0a3?last=3600 which is not a PVC dashboard.

Traction - traction-acapy- Dev - bc0192

Similar issue with the link to the PVC dashboard

Traction - traction-acapy- Prod- bc0192

Similar issue with the link to the PVC dashboard

Traction - traction-acapy- Test - bc0192

Similar issue with the link to the PVC dashboard

Traction - traction-tenant-proxy-Dev - bc0192

Similar issue with the link to the PVC dashboard

Traction - traction-tenant-proxy-Prod - bc0192

Similar issue with the link to the PVC dashboard

Traction - traction-tenant-proxy-Test - bc0192

Similar issue with the link to the PVC dashboard

Traction -postgresql-Dev - bc0192

Similar issue with the link to the PVC dashboard

Traction -postgresql-Prod - bc0192

Similar issue with the link to the PVC dashboard

Traction -postgresql-Test - bc0192

Similar issue with the link to the PVC dashboard

Hi @WadeBarnes - We are seeing this issues because looks like they have made changes in the pod names. I think it will be better for me to work on these dashboards once we have something permanent.
What do you suggest ?

Hi @WadeBarnes - We are seeing this issues because looks like they have made changes in the pod names. I think it will be better for me to work on these dashboards once we have something permanent. What do you suggest ?

What do you mean by changes in the pod names, exactly? Is this about the Tenant UI pods clightly changing the naming pattern, or something else? Can you use k8s labels as selectors, which will likely be more consistent, instead of pod names?

I mean deployment label names but i did talk to Lucas about it and he says it will remain the same from now on. Hopefully!

@WadeBarnes - I have made all the necessary changes according to the new deployment label and PVC dashboards now. Ready for review

Alerts seem to be working now- thanks.
The dashboards are all showing data now and the links to the PVC Dashboard are working - thanks.
The PVC Dashboard needs a few updates though:

It has a link to itself - please remove the Links section.
PVC metric display panels are labeled as Backup PVC.  There are no Backup PVCs defined it the Traction namespaces, yet.  I assume these are actually for the Traction database.  Please update the labels appropriately.

Thanks @WadeBarnes PVC dashboard is fixed now. Ready for review

Looks good.  Thanks


Travis test returns an error, should it be fixed?

I'm not sure if you are using travis tests for local testing or just for the badge (both, I guess!) but the second one returns an error by trying to create an android emulator, should it be removed in purpose to fix the badge/travis tests?
I have a lot to learn about TDD, so sorry for the possibly absurd questions.

Travis have cancer and sometimes when everything is good he gives us error 😃

OK, it's good to know xD I close the issue then.


Lazy-loading autocomplete, loading options remotely based on query in filter

I want the user to choose an option in a list of millions of records and I don't want to load the millions of records in memory for obvious reasons. It would be great if there was a way to show matches based on an (async) external function. Possible solutions:

I'll keep options empty. A onFilterTextChange must be added, allowing me to populate options with matched fetched from a query I got from onFilterTextChange. Error and loading is added to show "Loading" or an error in the modal.

<ModalFilterPicker loading={loading} error={error} onFilterTextChange={(query) => loadOptions(query)} options={options} />

...

loadOptions(query) {
  this.setState({options: [], loading: true, error: null})
  this.optionsService.find(query)
    .then(options => this.setState({options, loading: false}))
    .catch(error => this.setState({options: [], error, loading: false})
}

The component accepts a function for options, that has 2 arguments: the query/filter, and a callback. Every time the filter is changed, the function is invoked. The callback must be called with the filtered options.

<ModalFilterPicker options={queryOptions} />

...

queryOptions(query, cb) {
  // the component will invoke this function, showing a Loading message
  // as long as the callback isn't called. The callback is called with either
  // an error (which is shown in red or something) or a list of options.
  this.optionsService.find(query).then(options => cb(null, options)).catch(err => cb(err));
}

Thoughts? PRs welcome? Any pointers/hints/guides?

facing same issue


docs: Fix always_select_remote_on_create type

Describe what this PR does / why we need it
This commit fixes a type error on the configuration outlined in the readme. I noticed it when doing type validation in another PR

Thanks!


CPU Scaling

Could we get auto scaling on the single CPU graph for both system and process performance graphs?
Also would like multi-CPU view on process performance graph if that info is available.
In multi-CPU could autoscale on the biggest graph.
Doing some analysis on software packages I've written and some more visibility on thread behavior and CPU usage (albeit small CPU usage) would be more than nice to have.
Mike

get auto scaling on the single CPU graph

How would you determine the difference between 10% and 100% when one graph was scaled to the same height? I'd have thought the point of having fixed scale was to easily determine the utilization.

some more visibility on thread behavior and CPU usage

The Threads tab columns would be a lot better for this than using the graphs? For example the nightly builds:

The Threads tab shows cumulative -- I'm interested in real-time.
I would take the multi-CPU view and either put the scale in the graph or maybe just next the "CPU" to tell you the scale for all.Or perhaps let the user choose the scale.  Just need a few scales.
CPU Scale=100%CPU Scale=50%CPU Scale=20%CPU Scale=10%CPU Scale =5%CPU Scale = 2%CPU Scale = 1%
On Tuesday, April 20, 2021, 11:37:17 AM CDT, dmex<EMAIL_ADDRESS>wrote:

get auto scaling on the single CPU graph
How would you determine the difference between 10% and 100% when one graph was scaled to the same height? I'd have thought the point of having fixed scale was to easily determine the utilization.
some more visibility on thread behavior and CPU usage
The Threads tab columns would be a lot better for this than using the graphs? For example the nightly builds:
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

The latest nightly includes a new EnableScaleCpuGraph setting for enabling scaling of the CPU graphs

Thanks for that....I see the peak is getting labeled to tell the scale....but it gets overwritten by the statistics...Maybe rather than scaling to the peak it could scale say to 50%/25%/10%/5% instead?Then the scale could just be in the upper right corner all the time.
Mike
On Sunday, July 25, 2021, 04:52:53 AM CDT, dmex<EMAIL_ADDRESS>wrote:

The latest nightly includes a new EnableScaleCpuGraph setting for enabling scaling of the CPU graphs
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

it gets overwritten by the statistics

Options > Graphs > Show Text > untick


How to get assistant's response text?

ConverseResponse.result.spoken_response_text is always blank in the grpc sample.

see here https://developers.google.com/assistant/sdk/reference/rpc/google.assistant.embedded.v1alpha1#google.assistant.embedded.v1alpha1.ConverseResult
spoken_response_text	- This is only returned for an IFTTT action.

Is there a reason it is not supported for non-IFTTT actions?

@krsnaa feel free to discuss this topic w/ the team in the Google+ community.
A few pointer to similar discussion in the past:
https://plus.google.com/112935559604288840722/posts/aufnsN9uCvN
https://plus.google.com/+MartíPlanellas/posts/eoQbWzemQvd
https://plus.google.com/101852559274654726533/posts/BskrFscRYdh

Hi,
is it still the case we have to use IFTTT for getting text response !? or we can do it with api.ai webhook (google cloud Functions)
I tried doing multiple options, however there is something or other issues coming up. wondering how to fix those :)

tried picking up query when use says something and parse it and execute local function (Turn on LEDs) - with this I am able to get things done, but not in interpretative way as my local functions are executing no query not the response from home assistant

I tried with https://github.com/api-ai/apiai-python-client - I was able to send query to api.ai and get response back with from my action and able to run my local functions based on api.ai response, However, google home responds with different results for query. Since execution logic not depended response from google home it's not user friendly.

Trying to figure out how this webhook works and do we have to use webhooks !?? wondering.

As I was started researching more got to see this IO demo/info where they talked about user talks to Microwave and it turns on since it has Assistant SDK installed native. However, they didn't showed the demo of it.
Problem statement : I am trying to solve is.., I have RPi, installed Assistant SDK (works great) and now I would like to control connected hardware to it based on google home response.
Any suggestions much appreciated.

Here is a code snippet from a modified hotword.py sample.
You can get the spoken text from event.args["text"]
def process_event(event, assistant):
"""Pretty prints events.
Prints all events that occur with two spaces between each new
conversation and a single space between turns of a conversation.

Args:
    event(event.Event): The current event to process.
"""
print(event)

if event.type == EventType.ON_RECOGNIZING_SPEECH_FINISHED:
    speech_text = event.args["text"]
    print("speech text: " + speech_text)
    # here is where we add our code
    if "some command" in speech:
        # do this if you don't want to play the conversation response
        assistant.stop_conversation()
        # then do some custom action

def main():
parser = argparse.ArgumentParser(
formatter_class=argparse.RawTextHelpFormatter)
parser.add_argument('--credentials', type=existing_file,
metavar='OAUTH2_CREDENTIALS_FILE',
default=os.path.join(
os.path.expanduser('~/.config'),
'google-oauthlib-tool',
'credentials.json'
),
help='Path to store and read OAuth2 credentials')
args = parser.parse_args()
with open(args.credentials, 'r') as f:
credentials = google.oauth2.credentials.Credentials(token=None,
**json.load(f))
with Assistant(credentials) as assistant:
    for event in assistant.start():
        process_event(event, assistant)

if name == 'main':
main()

supplemental_display_text can now be retrieved for all responses from the Assistant.

Sorry to be the threadromancer here but is there any documentation on supplemental_display_text?

The documentation for supplemental display text is available, as well as for SpeechRecognitionResult.
At the same time, it does seem like you'd be better off going with a custom device action.

Custom device action work nicely on RPi.
Several standard device types are supported, but it is not possible to add your own custom device.
And, as I see it, it is not possible to configure more than 1 device of as specific type, So only 1 light, 1 switch.
But for a simple application it works nicely.

I'm not actually controlling any external devices, I just need to be able to receive assistant responses for parsing as part of another function. I can't see any code examples to try out and I'm not proficient enough in Python yet to know what's likely to work.

Sorry to jump in, but just to clarify: Google does not allow you to get spoken_response_text unless you use IFTTT. But now  spoken_response_text will be included in the supplemental_display_text ? am I understanding that correctly? Thanks.

Yes we are now sending back the response text to the developer. The IFTTT limitation was true a year ago but the feature was added in December.

All of our samples have been updated to include getting the text output and printing it.

@Fleker Sorry to add more to this thread, but is there a sure way to retrieve a text response that's always identical to the speech spoken in AssistResponse.audio_out? The doc for supplemental_display_text says that the text may be "additional information which aids the user's understanding" instead of the spoken output.

Text output is available in both the service and library.
It is not necessarily going to be identical to the audio output. Certain queries made on a phone, for example, will return different audio than text. The text may have more or less detail than the audio.

@Fleker Thanks for the response. I'm still trying to get the text response with the library. How would we go about retrieving dialogstateout in--for example--the hotword.py sample?

It wouldn't be in the same API structure. It should be returned as an event with the text as a parameter.

I am developing with AIY voice kit v2, and trying to get Assistant's response in text format. I am using aiy.assistant.library but could not find a way to get the text properly with supplemental_display_text. Is there any sample code or documentation that I can refer to? I am not proficient in Python...
As per what you said 'it should be returned as an event with the text as a parameter', are you referring to ON_RENDER_RESPONSE? The text parameter I got from this is always empty...


certificate: fix grammar

Fixes from @MarkusTeufelberger

Seems fine now, thanks! :-)

Seems fine now, thanks! :-)


Add GeeksforGeeks under general resources on the website

Add link to geeksforgeeks portal under general resources on the website

You can submit PR and I will merge it right away.

Just a heads up... this has been completed.

@MattCSmith @Dhaval1403 can you close this issue


cmd/dist: regex of test does not allow test names in -run parameter

What version of Go are you using (go version)?

go version go1.11.4 windows/amd64

Does this issue reproduce with the latest release? Yes, on tip

>go tool dist version
devel +c482e0cd38 Sun Dec 23 14:07:55 2018 +0100

What operating system and processor architecture are you using (go env)?
go env Output
$ go env
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\***\AppData\Local\go-build
set GOEXE=.exe
set GOFLAGS=-v -vet=off
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\Users\***\Documents\Google\
set GOPROXY=
set GORACE=
set GOROOT=C:\Users\***\Documents\Google\golang\go
set GOTMPDIR=
set GOTOOLDIR=C:\Users\***\Documents\Google\golang\go\pkg\tool\windows_amd64
set GCCGO=gccgo
set CC=gcc
set CXX=g++
set CGO_ENABLED=0
set GOMOD=
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=C:\Users\***\AppData\Local\Temp\go-build911439174=/tmp/go-build -gno-record-gcc-switches

What did you do?
C:\Program Files (x86)\Google\Cloud SDK>go tool dist test -run=^TestScript:cmd/go$
What did you expect to see?
C:\Program Files (x86)\Google\Cloud SDK>go tool dist test -run=^cmd/go$

##### Testing packages.
...(some tests executed)
ALL TESTS PASSED (some were excluded)

What did you see instead?
No test is executed.
C:\Program Files (x86)\Google\Cloud SDK>go tool dist test -run=^TestScript:cmd/go$

ALL TESTS PASSED (some were excluded)

This is especially a problem to test cmd/go package.
Running the tests of cmd/go times out even in short mode (#25300).
Further, In short mode, no external network is usable and no test of f.i. of git is doable (#26837).
The fix handles the regex in the format testname:package-name as an added case.

As far as I know, go tool dist test is meant to test the entirety of Go. If you just want to test the scripts within cmd/go, you can just do go test -run=Script cmd/go.

The purpose of  go tool dist test seems to re-build the tests of the updated packages and to only run the relevant tests.
A new build created in golang/go/bin/ using make.bat requires to set GOROOT  to bin\.. folder. Then go tool dist is usable.
go test gets an error for several packages which is related to a version file as far as I know.
golang\go\src>set GO
GOFLAGS=-vet=off
GOPATH=C:\Users\***\Documents\Google\
GOROOT=C:\Users\***\Documents\Google\golang\go
GOROOT_BOOTSTRAP=c:\Go
GO_TEST_SHORT=0
golang\go\src>go tool dist version
devel +7ef8502d16 Tue Dec 25 11:33:12 2018 +0100
golang\go\src>go test -run=Script cmd/go
...
# internal/cpu
compile: version "devel +7ef8502d16 Tue Dec 25 11:33:12 2018 +0100" does not match go tool version "go1.11.4"
...

This fix seems inline with the description of the tool and allows to fix tests independently of the build process as the -compile-only flag hints:
golang\go\src>go tool dist test -h
usage: go tool dist test [options]
...
  -compile-only
        compile tests, but don't run them. This is for some builders. Not all dist tests respect this flag, but most do.
...

The purpose of go tool dist test seems to re-build the tests of the updated packages and to only run the relevant tests.

Yes, but only during the process of a complete build of Go.  If you just want to test a package yourself, just use go test.  No reason to use go tool dist test.  The purpose of the -run option to go tool dist test is to permit sharding the tests across several different automatic builders.  I don't see any reason for anybody other than the builders to run go tool dist test -run themselves.  Just use go test.

When working on several projects, a stable Go version resides in the default directory. When re-building go to investigate some issue. This unstable version resides under golang\go\ as all tools foresee.
Using go test on this unstable requires to override the stable version or to update the go env. This is cumbersome and a flag is easy to forget when you work on a single machine. This set up allows to easily switch between projects.
If go tool dist is targeted at builders. This issue might be eventually marked as a proposal.

If you want to work on Go's master/tip version, but still be able to use the stable version, you can simply use aliases. For example, go on my system is always master, and then I do alias go1=/usr/bin/go, which currently is 1.11.x. Some people do the opposite, with gotip being an alias to the master version. Just using the right binary should be enough; there's no need to fiddle with GOPATH.
Like @ianlancetaylor said, if you're working on Go itself, you're expected to just use go test. I'm going to close this issue for now, as there doesn't seem to be a particular suggestion or bug here. Feel free to reopen or create a new issue if you have a particular suggestion for the go tool, but I'd recommend discussing it with other Go contributors before sending proposals or CLs.

Running the instructions using go 1.12 beta2 is indeed successful. On Windows, two things to know which might be written elsewhere:

You have to run these instruction in CMD
Directory %GOPATH%/bin must in in the PATH using f.i. set PATH=%PATH%;%GOPATH%/bin

Similarly, using make.bat builds go tip into the golang repo bin directory.
The easiest is to move the executable like move %GOPATH%\golang\go\bin\go.exe %GOPATH%/bin/gotip.exe (on Windows). Then gotip test encoding/xml works as expected.
Maybe, make.bat should build directly into %GOPATH%/bin for consistency purposes.

No, the make scripts should not write the output binaries to GOPATH/bin. If that were the case, it would be impossible to build two versions of Go from source, as the go binaries would be installed in the same place.
Please don't use this issue to make other comments about buiding or testing Go; the issue is closed. If you have any questions or would like to share tips with other Go developers, see https://github.com/golang/go/wiki/Questions.


Model - Collection object - completeness of the record

As a part of workflow we try to resolve as much information from the label. Soft validation highlights potential issues (missing determination, missing georeference, etc.). But some older specimen do not have enough information to cover all missing data. At some point, I would like to mark a specimen as "DONE" in terms of possible parsing. may be a checkbox, to switch off soft validation on this particular record.

I feel that Confidence and the batch application/chaging, etc. meets this need of "done".
I guess the question is whether soft validtions are always directives to change data, maybe so.


The videos generated by the CogVideoX-fun models become mosaics

Hello, I have encountered a major issue. After updating the version, all videos generated based on the cogvideo X-fun model have turned into mosaics without any errors. However, they have become pure noise. May I ask what's going on?

I used these workflows for testing：
cogvideox_Fun_I2V_02
cogvideox_Fun_I2V_Tora

On what hardware? And only those? Can't replicate the issue at all with those workflows at least.

hi, same issue here at 49 frames, windows 11, RTX 4060 ti 16gb,  32gb ram, i didnt have that issue at 16 frames. i test at 32 to see.
the workflows with 1.5 is ok !

My outputs are completely "burned".
I started 2 days ago, so can't say about previous v
CogVideoX_burned.json
ersions.
@kijai please see attached workflow and sample output. I would do additional tests if asked.
# Configuration:
Platform: Windows Python version: 3.10.11
Total VRAM 24563 MB, total RAM 65346 MB
pytorch version: 2.5.1+cu124
Set vram state to: NORMAL_VRAM
Device: cuda:0 NVIDIA GeForce RTX 3090 Ti : cudaMallocAsync

https://github.com/user-attachments/assets/80a1a0ec-e9d8-49e1-8f3f-ca1485f9a73c
Attaching source image for reference

My outputs are completely "burned". I started 2 days ago, so can't say about previous v CogVideoX_burned.json ersions. @kijai please see attached workflow and sample output. I would do additional tests if asked.
# Configuration:
Platform: Windows Python version: 3.10.11
Total VRAM 24563 MB, total RAM 65346 MB
pytorch version: 2.5.1+cu124
Set vram state to: NORMAL_VRAM
Device: cuda:0 NVIDIA GeForce RTX 3090 Ti : cudaMallocAsync

24_11_21_130830_00001.mp4
Attaching source image for reference

This is an old workflow, most of the CogVideo nodes there would need to be recreated. Please check the readme for the big update notice.

This is an old workflow, most of the CogVideo nodes there would need to be recreated. Please check the readme for the big update notice.

I understand that on Update 8 was BREAKING ✌ I've re-created nodes on the old workflow, cause they were giving errors, attached VAE links, etc. And now think the workflow I have attached has every node in latest state. Question to you as a master here: How do I find/spot "outdated" nodes without re-creating whole workflow? I've also checked JSON file, but could not identify version or anything.

First I want to know if the example workflows work, if they do then updating old ones would entail basically re-creating all the CogVideo specific nodes (fastest way is the right click "Fix node" option). Depending how things were wired there may be bad links that don't error out but affect wrong values etc.
It's impossible for me to know how any other workflow is wired besides mine, I'm well aware updates like this are annoying but like I explained it became necessary to fight the bloat caused by all the new models/features that have been released.


Support more and variable media types, add rawBody per claudiajs documentation

The goal of this PR is to get a little closer to being in-spec with the ClaudiaJS documentations surrounding the body and rawBody functionality.
Specifically, I noticed that if I try to either upload a file using a curl POST request or if I try to upload a string while specifying any mimetype other than application/json or application/x-www-form-urlencoded that the body is not correct. It will always have the empty object value ({}) and never have the contents which I attempted to submit via POST.
Relevant ClaudiaJS docs:
https://github.com/claudiajs/claudia-api-builder/blob/master/docs/request-object.md

@suddi, I don't think I have permission to add you as a reviewer to this PR. Any chance you have some time to take a look at it and provide feedback?


89 create desktop display

Meant to send this earlier, but this should be the main rework of the main menu that we went through this morning.

By the way, I HIGHLY recommend adding screenshots to your PRs when making UI changes. That way someone doesn't have to pull down your branch to see the visual changes you are making. But when someone does it's also very helpful because you can verify that the changes are the same across devices.


Fix issue with Discriminator type resolution that impacted the decoding of oneOf types in some conditions

Background
The oneOf OpenAPI schema types are represented as enum types in generated Swift code where each nested type becomes an enum case. Each enum case is named after the type that it represents and with this, there is one enum case per type.
When decoding, a discriminator, which defines a property used to disambiguate, is used to help decode the right payload into the right type. The init(from:) decoder will switch on the discriminator value and try to decode the container into the type that matches the appropriate case.
We identified a problem however where in some scenarios, the case doesn't get added to the switch in the decoder implementation which results in the decoding failing.
I reproduced this in the following commit: 35d48dee854965ec9971abd6dc4dfaee40fbfd60. In the diff, you will notice that the discriminator lists a mapping with values one, two and three however the decodable implementation only switches on a value of three. one and two are missed from the generated code.

Note:
This happens in this particular example because the One and Two types are identical to their reference A so CreateAPI has optimised things by skipping them. You will notice that the enum itself has spotted that since there is an a case and a three case, but the decodable init didn't figure this out.

Changes
After some digging, I traced this back to the way that the Discriminator type is build when evaluating the schema:
https://github.com/CreateAPI/CreateAPI/blob/5a6a20076a91acddfcb3528daef420066ed9cc97/Sources/CreateAPI/Generator/Generator%2BSchemas.swift#L402-L428
In the prior implementation, it would try and resolve the ref string that was provided as a mapping to a type. In this case, it resolved it as One and Two, but later on, since those types didn't get generated, it just skipped them in the initialiser body. The problem here is that this implementation differs to how we resolve names of references elsewhere so the logic for optimising out the redundant One and Two is missed and the bug is reproduced.
To fix the issue, it's a relatively straightforward case of using the existing getReferenceType(_:context:) method that is used elsewhere instead. After making the change and regenerating snapshots, we get the correct result (35d48dee854965ec9971abd6dc4dfaee40fbfd60).

Now we may remove these 2 workarounds which are likely related to what you fixed...?

Ahh great spot @imjn, I see how these are likely related now (to begin with, I struggled to understand what they might be doing 😅)
@kean By any chance do you remember any more details about the two workarounds above? Are you able to provide a reproducible example of them in use so that I can understand if my change solve them? Were they related to the Discriminator alone?
Removing these workarounds doesn't break anything in the CreateAPI test suite so I might just do it and see if anything gets raised.

I don't remember the details, but I suggest running before and after for the two attached specs and checking the diff. specs.zip

Thanks for confirming, I ran those schemas against this change before and after and it makes no difference. I also tested removing those workarounds and while the Zoom one seems to be redundant now, the OpenBanking one appears to still be relevant.
I'll leave it for now but will look into that later on at some point 👍


sendgrid Login is not working

My Login is not working. Can you please check and resolve this urgently.
My user id is : ujjawal2005
email<EMAIL_ADDRESS>Thanks,
Uj

Hello @ujjawal2005,
Thanks for submitting a GitHub issue! We are very sorry that you are running into this problem. In order to better serve you, as this does not present itself as a library specific issue, we would like to ask that you reach out to our support team at https://support.sendgrid.com.
Thank you!
SendGrid DX Team

Hello !!
Please check i'm recently create account in sendgrid and its not working while i'm sending confirmation email and its not sending email to confirm my account.
USERNAME: jojo101
Email<EMAIL_ADDRESS>Please fix this ASAP tons of work is pending.
Thankyou !!


 WIP

just need to address merits now


Newrelic Add-on

Hello
Is there any plan or active development to add Newrelic add-on to EKS Bluepirnts kubernetes-addons list?
Here is more info:
https://github.com/newrelic-experimental/newrelic-eks-blueprints-addon

We will defer to Marketplace support once #1260 is implemented.

Thank you for the issue @viktoraws - as you have pointed out, there already exists a module to provision the New Relic addon or you can use the aws_eks_addon resource for deploying EKS addons or 3rd party addons from the AWS Marketplace


Changed cache directory to runtime/htmlcache

Changed the cache directory to runtime/htmlcache see #3
Use CRAFT_STORAGE_PATH instead of the getTempPath() function to determine the storage path.
htmlcache_checkCache returns NULL when cache is expired better to return false
cleanup + code styling
@webremote Why did the htmlcache_directory return a path ending with a dot?

@KoenRijpstra not on purpose actually! thanks for the PR!


nmdc-schema doesn't know about the compatibility of GOLD path elements

@pkalita-lbl has modifications to DataHarmonizer that make the more specific GOLD path elements dependent on the more general ones. It also resets the more specific ones if a more general one is changed.
implementation with enums vs strings?
source of the GOLD path knowledge?

should we start with some environment-specific filter?

merge into DH?

Some of the data and code are NMDC-specific... integrate with sheets and friends?


nimble/host: Add support for ext adv param v2 HCI command

BLE spec version 5.4 introduced support for host to pass primary and secondary phy options in set extended advertising parameters. For this a new HCI command "HCI_LE_Set_Extended_Advertising_Parameters v[2] " with OCF 0x007F got introduced.
This patch adds support in host for this HCI command.

@sjanc  please take a look and review

Hi @sjanc  , please review.

Hi @sjanc , @andrzej-kaczmarek  , please let me know in case of any further comments

until now we didn't have need for V2 (or more) HCI commands in host but I think we should start tracking controller supported commands.
I believe we should be able to simply extend host API and if no preference is selected we can fallback to V1 if V2 is not supported,  in case of preference set by app, we fail if V2 is not supported

until now we didn't have need for V2 (or more) HCI commands in host but I think we should start tracking controller supported commands.
I believe we should be able to simply extend host API and if no preference is selected we can fallback to V1 if V2 is not supported, in case of preference set by app, we fail if V2 is not supported

So current implementation to read supported commands is only for event mask2 . I have extended it to use all commands bits ( so that future implementation can use it as needed).

looks good to me!  but please fix those few style issues reported by CI

looks good to me! but please fix those few style issues reported by CI

Thank you. Have pushed again.


Crossplane - Deploy ProviderConfig and ClusterRole/Binding for each namespace/team using crossplane

[x] Investigate possible approaches to take for deployment
[x] Create necessary issues

Created issues #520 #521 #522 #523 as a breakdown of this task


Lizzaria doesn't appear with mod

I played a singleplayer campaign as well as a multiplayer game with the mod enabled and both times, Lizzaria didn't appear when she should have; the fight with the dark apprentices in the Bone Keep took place, but the dialogue with Lizzaria didn't trigger. (I only know where it should have triggered by watching YouTube videos.) One affected playthrough was with the Steam version, the other with GOG.
I have no idea whether this is a bug in the vanilla game or the mod, though; there were also other issues with this quest (the subtask "look for another way in" can be triggered by returning to the courtyard after confronting Mardracht and standing in front of the main gate, but there is no way to progress beyond this point save via the debug console; also, reentering the keep through one of the other wells again leads to faction attitude increases).
I don't plan a third playthrough, especially not without the otherwise wonderful mod, so I can't really promise more information; I'm submitting this report in the hope that it's helpful.

We don't touch any campaign at all with the mod. Most likely a vanilla bug introduced in their last patch.


add bind_ip to better listen IP control

In my opinion, this small change will help Pro users gain more control over server ports, and users who like to restrict the application via IPTABLES or firewall or make the Reverse Proxy for this application have  more options and are easier to reassure.

We already enable the firewall "UFW" and deny access to wg-dashboard via other interfaces than <IP_ADDRESS> so this should already be given, right?

yes, but many users disable UFW and use iptables

UFW uses iptables too, I see no reason why you should not be able to block a port via iptables.
I understand your concern, how would you design usability and reachability of wg-dashboard?
I'd like to listen on <IP_ADDRESS> and wg0 ip so the dashboard can be reached over vpn without having to configure ssh.

I use reverse proxy with IP white-list and Iptables in production environment and to use wg-dashboard in our design so I had to make some changes to it to make it compatible with our production environment. So I thought maybe someone else would have an environment like us, and so I requested this change. But this is a friendly suggestion you can ignore it or poll it from others
Be happy and OpenSource :)


Send GHCR image to AWS Lightsail

Next step after runner --> GHCR.

Following this blog post: https://aws.amazon.com/blogs/aws/lightsail-containers-an-easy-way-to-run-your-containers-in-the-cloud/

When I try to deploy manually I get problems. The logs aren't particularly helpful either:
[3/Mar/2024:22:19:17] [deployment:2] Creating your deployment
[3/Mar/2024:22:20:13] [deployment:2] Started 1 new node
[3/Mar/2024:22:21:13] [deployment:2] Started 1 new node
[3/Mar/2024:22:22:16] [deployment:2] Started 1 new node
[3/Mar/2024:22:22:41] [deployment:2] Canceled

I inserted a print statement at the start of the Python file, so I don't think it's even getting that far.

Okay, I tried replacing the image link with some random garbage and it produced the same log files. I think that's good, because it means the problem is likely in accessing the image at all rather than some problem with the image itself (hard to test without local access to Docker).

I'm not having any luck, so I'm going to try deploying to AWS Lightsail from a workflow. I think I might get more information that way.

Abandoning that track for a moment because setting up IAM credentials is being annoying. I tried manually deploying the image from the tutorial (not my version of it but rather the original Docker Hub image that the tutorial writer created) and the deployment worked! That's exciting!
The next step would seemingly be to copy that image (which we know runs) from Docker Hub and put it in my GitHub Container Registry account. Will it still work, or is the issue something with AWS accessing GHCR?

Okay, when I copy the tutorial image from Docker Hub to my personal GitHub Container Registry, the AWS deployment fails. That definitely tells me that it's not even accessing the Docker image before crashing. That should help pinpoint the bug!

And it turns out my GHCR image was private. That would explain things, wouldn't it?

Okay, I can deploy the images manually now. I'm re-evaluating my priorities at the moment.
The most important part of the Docker / CICD pipeline / etc. was control. I didn't want code changing under my feet, and I wanted the main branch to always be solid. I think I've achieved that for now. For the time being, I think it's okay to manually deploy to staging and production.

A lot of stuff has changed since I last touched this issue. I'm now probably going to have to have multiple Docker containers to deal with all of the moving parts of my Django deployment. It's unclear that I still want to use AWS Lightsail. I think it's time to close this issue and move on.


Update func to v0.25.1

Per title update func plugin.
/cc @rhuss @lance

/lgtm - thanks for this

@lance np, glad to help. And you might want to re-add just a single line /lgtm. Prow seems to be confused.

/lgtm


Implement E2E tests for the Zeebe binding

Description
This PR implements E2E tests for the Zeebe binding.
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[ ] Code compiles correctly
[ ] Created/updated tests
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

@pkedy Would be great if you could give some early feedback if this goes in the right direction.

@akkie You've got some linter errors breaking the build but this look like its structured well. You've got a README and docker compose for running it which is great.

@pkedy Do you have a suggestion how I can resolve the issue regarding the global variables.
`ZeebeVersion` is a global variable (gochecknoglobals)

I would like to share them between the tests.

I have created a getter for the environment variables to fix the global lint issue. I have also created a new entry in the makefile to run the tests from CI. I have not created a new workflow for E2E tests, because I'm not sure if each test should run separate or if it makes sense to create a shell script that runs all the E2E tests.
From my perspective the PR is finished and can be reviewed.

@akkie please resolve conflicts and we can merge.

@yaron2 Done


Include rangefinder in the estimation

A possible approach:
Start by simply substituting the rangefinder for the baro, then see whether all three (rangefinder, baro, accel) could be incorporated. One thing worth looking into is the AGL (Above Ground Level) versus ASL (Above Sea Level) issue. An optimal solution would probably compute ASL, and would have some conditional like "If rangefinder reading changes suddenly (faster than some threshold) while baro remains constant (or gradual), vehicle is above a ground obstacle, and ASL is unchanged"

A possible approach would be to place the rangefinder looking upwards. This way obstacles do not affect the measurements. Think about it.

Clever idea -- but how about going through doorways? ;^)

I am switching to another approach in order to perform altitude estimation. So far it looks more promising: https://github.com/juangallostra/Range-Baro-AltitudeEstimation.
Closing the issue since I don't think I will work anymore on this.


Add copy to clipboard on tutorials

Fixed in marble 2.6.3 https://github.com/wedeploy/marble/commit/e0ffeaf9501522d21d4fd8205a5613c3000f08f8


Create FD_ZERO macro

Unfortunately, I'll have to close this PR without taking it, for the reasons below.
The system doesn't recognize this macro, so we can't document it like this (that is, with a formal topic for it, in this repo). Even if we took this PR, these topics wouldn't be recognized by the system (since the system doesn't recognize the macro), so these topics wouldn't be published by the system.
And I don't think it's vital to have full, detailed, formal topics for this macro. This macro is already mentioned in Select, fd_set, and FD_XXX Macros. So if we need a little more info about them, then that might be a good place.


After the recent comfyui update，somthing about api run the wrong way.

After the recent comfyui update, the realtime api in my photoshop  becomes extremely slow. I found that the process of transferring the image changes in Photoshop to comfyui is extremely slow. So I rolled back the comfyui version, the speed was normal again, and I saw  ”Using rgthree's optimized recursive execution“ now. I don't know if this is of reference value , but it definitely affects the daily work of users like me.

The optimization has been there for about a year, and I don't see ComfyUI updating the execution at all that would cause this to break. Regardless, if you think it's negatively affecting your speed, you can turn off the optimization in the configuration (easiest is from the rgthree-comfy settings in the ComfyUI interface); turning it off from the UI will also turn it off in the backend (say, if using just an API).
Assuming that doesn't actually fix you speed, it seems your issue may either be ComfyUI itself, or another extension.


"nether portal cooldown" in Entity is used for all portals

This field seems to be used for end gateways but not end portals.

Seems like that is not the case, yeah


Add MVS' find toolchain

Part of #2478 (to reduce diff).
These are quite stable changes, we can merge it without CI on Windows. @gshimansky if you don't mind.

What if instead of VS i have only VS BuildTools?

What if instead of VS i have only VS BuildTools?

This most likely won't work, see https://github.com/intel/intel-xpu-backend-for-triton/pull/2478#discussion_r1831383897 for details.

@pbchekin ready for review

Blocked by https://github.com/intel/intel-xpu-backend-for-triton/pull/2743


Surprising redaction for RubyGem token

The pattern for the RubyGem token is:
https://github.com/github/redacting-logger/blob/c078d9075b99cd8886e1632cf7cba21ce7bd7f6b/lib/patterns/default.rb#L50
However, the test is:
https://github.com/github/redacting-logger/blob/c078d9075b99cd8886e1632cf7cba21ce7bd7f6b/spec/lib/redacting_logger_spec.rb#L154-L158
This should be "using rubygems token: [REDACTED]", but it hits the GitHub token pattern instead:
https://github.com/github/redacting-logger/blob/c078d9075b99cd8886e1632cf7cba21ce7bd7f6b/lib/patterns/default.rb#L9
Possible fixes:

Remove the RubyGem pattern because it's duplicative
Change the GitHub token pattern to use {40} instead of {40,} so it doesn't match.

Aside: I think you could improve the performance of this library by combining all the regular expressions into a single regex to run once rather than looping over them until finding a match.

@look I went ahead and just moved the rubygems pattern match in the array to fix the issue for now via https://github.com/github/redacting-logger/pull/66
I think what we will want to do long term is just have one jumbo regex that runs to help prevent this and also for performance gains so I will leave this issue open until that happens (one way or another).

I think what we will want to do long term is just have one jumbo regex that runs to help prevent this and also for performance gains so I will leave this issue open until that happens (one way or another).

That is the approach I took in https://github.com/github/blackbird-mw/pull/2927.


no props to disable Cancel-Button and Select-Button conditionally

is : Cancel and Select Button cannot be disabled conditionally
must : Cancel and Select Button can be disabled conditionally

I coudn't find a way to disable those button conditionally @Jasenkoo

I couldn't find a way to disable those buttons conditionally, why did you close it @Jasenkoo ?


make page note more consistent

make page note more consistent

can some1 check and apply, it mostly has fixes in page formatting etc where on some pages the section about Notes etc dont match with other pages, actually there are many such pages but these are the first few i found and fixed, will do so to the rest once i get some time.


WIP: Project accelerator details API

Add new API endpoints to fetch and update a project's accelerator details.
TODO: Define new read and update permissions for this.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1795  👈
#1794
#1793
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @sgrimm and the rest of your teammates on  Graphite

An alternative approach here would have been to put these new fields in the existing projects API and selectively include or omit them depending on the user's permissions. That has the upside that the client doesn't have to do two fetches to get the full information about a project, but the downside that the accelerator-specific details aren't neatly segregated such that end-user-facing code will never encounter them at all.

Merge activity

Mar 26, 4:40 PM EDT: @sgrimm started a stack merge that includes this pull request via Graphite.


Python Vulnerabilities

Discussed in https://github.com/toluaina/pgsync/discussions/555

Originally posted by MikeNikolayev July 21, 2024
I installed latest tag (built 6 month ago) and found vulnerabilities list.
All of them are already fixed in requirements file. Do you mind building a new tag with fixes?
The list

Library: idna (METADATA)

Vulnerability: CVE-2024-3651
Severity: MEDIUM
Status: fixed
Installed Version: 3.6
Fixed Version: 3.7
Title: python-idna: potential DoS via resource consumption via specially crafted inputs to idna.encode()
More info: CVE-2024-3651

Library: requests (METADATA)

Vulnerability: CVE-2024-35195
Severity: MEDIUM
Installed Version: 2.31.0
Fixed Version: 2.32.0
Title: requests: subsequent requests to the same host ignore cert verification
More info: CVE-2024-35195

Library: sqlparse (METADATA)

Vulnerability: CVE-2024-4340
Severity: HIGH
Installed Version: 0.4.4
Fixed Version: 0.5.0
Title: sqlparse: parsing heavily nested list leads to denial of service
More info: CVE-2024-4340

Library: urllib3 (METADATA)

Vulnerability: CVE-2024-37891
Severity: MEDIUM
Installed Version: 1.26.18
Fixed Version: 1.26.19, 2.2.2
Title: urllib3: proxy-authorization request header is not stripped during cross-origin redirects
More info: CVE-2024-37891

all done and thanks for pointing this out. A new version has been published.