Balloon Service 0x80041032

Balloon Service is generating the following WMI errorID:5858
"
Id = {00000000-0000-0000-0000-000000000000}; ClientMachine = HOSTNAME; User = NT AUTHORITY\SYSTEM; ClientProcessId = 964; Component = Unknown; Operation = Start IWbemServices::ExecQuery - root\cimv2 : SELECT * FROM Win32_PerfRawData_PerfOS_Memory; ResultCode = 0x80041032; PossibleCause = Unknown
"
Version: virtio-win-0.1.204-1
Host OS: Proxmox and ArchLinux
Guest OS: Windows Server 2016 (proxmox) & Windows 10 (archlinux)
On Windows 10, the WMI service was also spiking CPU Usage due to the WMI error. Stopping the Balloon service or restarting "Windows Management Instrumentation" service stops the CPU spikes until reboot.
Manually running "Get-WMIObject Win32_PerfRawData_PerfOS_Memory" from elevated powershell returns the expected output & doesnt cause any errorID 5858
Following KB indicates issue could be related to lack of timeout: https://docs.microsoft.com/en-us/troubleshoot/windows-client/system-management-components/wmi-activity-event-5858-logged-with-resultcode-0x80041032

@Svra44
Hi, I want to ask the detailed steps to reproduce this issue, in my env I didn't reproduce it.
Host: RHEL8
Guest:Win10-64(10.0.19043)
virtio-win-0.1-204
Steps:

Boot up vm with balloon device, machine type is q35.
Install balloon driver and start balloon service
blnsvr.exe -i
enable polling in qmp:
{"execute":"qmp_capabilities"}
{"execute": "qom-set","arguments": { "path":
"/machine/peripheral/balloon0","property": "guest-stats-polling-interval",
"value": 2 } }
{ "execute": "qom-get","arguments": { "path":
"/machine/peripheral/balloon0","property": "guest-stats" } }
Balloon memory via qmp
Check EVENT VIEWER in guest, didn't find any error log

@xiagao ,
There arent any specific steps to reproduce. I am seeing it on each of the VMs Ive checked so far. They would have been standard 10/Server2016 installs and then having virtio-win-gt-x64 0.1.173 installed.
Initially I identified the error because of a system having performance issues (running 0.1.173 blnsvr installed via virtio-win-gt-x64.msi I believe), and tracked the issue down to wmiprvse.exe CPU spikes which stopped once blnsvr service was stopped (& the 5858 errors stopped occurring).
Ive also tried uninstalling blnsvr and re-installing using 0.1.204 and have seen no change.
I am also seeing the same on a q35 VM, though most of my VMs are i440fx.
I setup a test VM using q35 with 21H1 19043.928 Windows 10 Pro N iso, copied "Balloon\w10\amd64*" from virtio-win-0.1.204.iso to the C Drive and installed via "blnsvr.exe -i". I didnt see the errors occur, though as per below continuation, that may just be because I didnt wait long enough.
I then uninstalled blnsvr.exe and installed Balloon Service via virtio-win-gt-x64 and began seeing the errors on this new VM, though they took about 5 minutes after initial upstart of blnsvr.exe to start appearing in Microsoft-Windows-WMI-Activity, and seem to occur less frequently(~1 minute in intervals) than some other VMs I have checked.
Checking the file SHA1 hashes virtio-win-gt-x64 installs the correct w10 files, however it doesnt include the .pdb files (though manually copying them over doesnt change the behaviour).
Uninstalling Virtio-win-driver and re-running "blnsvr.exe -i" using the manually copied over files again doesnt seem to produce the 5858 errors. Seems tied to installs via virtio-win-gt-x64?
You would need to specifically check for the error under Microsoft-Windows-WMI-Activity if you havnt already.
The reference "ClientProcessId = 7364" of the below example event also corresponds to blnsvr PID.

5858
0
2
0
0
0x4000000000000000

670

Microsoft-Windows-WMI-Activity/Operational
DESKTOP

{00000000-0000-0000-0000-000000000000}
DESKTOP
NT AUTHORITY\SYSTEM
7364
Unknown
Start IWbemServices::ExecQuery - root\cimv2 : SELECT * FROM Win32_PerfRawData_PerfOS_Memory
0x80041032
Unknown

@Svra44 ,
Yes, you are right.
Only hit this error when installing Balloon Service via virtio-win-gt-x64.Could not reproduce via 'blnsvr.exe -i'.
But I didn't have CPU spikes when get this error.
We will track this issue internally.
Thanks.

I came here trying to track down the 0x80041032 I saw flooding my event log. As a datapoint, Microsoft has this to say on the cause of this error:
WMI-Activity Error 5858 with ResultCode = 0x80041032 (WBEM_E_CALL_CANCELLED) indicates that the WMI caller has successfully issued IWbemServices:ExecQuery, but has released the IWbemContext object before retrieving the full result set using the IEnumWbemClassObject::Next method. If the WMI service is still holding data for the client when the client terminates the link (by releasing the IWbemContext object), this event will be logged.
(source: https://learn.microsoft.com/en-us/troubleshoot/windows-client/system-management-components/wmi-activity-event-5858-logged-with-resultcode-0x80041032)
I noticed that enumerator does not get enumerator->Release() called before going out of scope (at least, as far as I can see: I'm no C++ guru). Maybe that omission causes the events?
I do not have an environment in which I can build the exe, but I'd be happy to test it if it becomes available.

@kostyanf14 please check the last comment

@driehuis
The enumerator variable https://github.com/virtio-win/kvm-guest-drivers-windows/blob/ab703c5b9896f1d3061636ab02b25f78e1af7066/Balloon/app/memstat.cpp#L97  is a CComPtr object.   CComPtr is a smart pointer. According to Microsoft docs, we should not call enumerator->Release()

Ah, so it was my limited C++ knowledge after all :-)  I'll see if I can build the binary and toy with it to see if I can isolate the problem, seeing that I seem to be able to reproduce the issue easily.

@driehuis
You need Windows 10+/Windows Server 2016+ and EWDK Windows 11 21H2 (ISO) to build a binary. Detailed instructions are in the wiki: https://github.com/virtio-win/kvm-guest-drivers-windows/wiki/Building-the-drivers-using-Windows-11-21H2-EWDK

Got it built. Unfortunately, the reboot involved in getting the environment set up seems to have cleared the condition, so I'll first have to wait for the issue to be visible again. Dang.

The problems I had reproducing the issue were caused by delays in my logging pipeline, so ignore the presumed "clearing of the condition". The Event Viewer shows the issue immediately in the WMI-Activity channel, if you know where to find it. I added some code to consume the entire enumerator, and the problem goes away. If I run my home-built blnsvr.exe without the patch, I reproducibly get a ton of events.
I can only assume that the WMI API only cleans up its internal context after the entire enumerator is consumed, and randomly throws a hissy fit about it in the event log or not depending on timing.
I'm an old fashioned K&R C coder, so please review pull request #939 without assuming I will do anything right without prodding :-)  I have not been able to do any formal testing either.

Errrm, scratch that. The problem is back in a different incarnation:
Id = {BD897EE8-24C6-4355-891D-EE51E446AD7D}; ClientMachine = PLB-WS001; User = NT AUTHORITY\SYSTEM; ClientProcessId = 7760; Component = Unknown; Operation = Start IWbemServices::DeleteInstance - Root\Rsop\Computer : RSOP_ExtensionStatus.extensionGuid="{BC75B1ED-5833-4858-9BB8-CBF0B166DF9D}"; ResultCode = 0x80041002; PossibleCause = Unknown

https://issues.redhat.com/browse/RHEL-12116 tracker


Simplifying identifiers

This is a semi-desperate issue, but is there some way we could specify identifiers in a simpler manner? Currently, the long_identifier_or_op node has a few (3? 4?) valid combinations, and then they should be highlighted differently in different contexts, and it kinda just ends up exploding from there.
This isn't really a bug, but more of a would be nice-to-have. Please let me know if it's not possible and I'll close the issue.

I'm all for simplifying the structure, if it can make working with the AST easier.
Could you perhaps give some examples of the highlighting queries you're trying to do, and why it blows up for you?
Then we can work for there and see if we can simplify the structure, without introducing ambiguities

One example is this query I'm writing (which I haven't been able to get to work so far)
	(application_expression
      (dot_expression
       base:
       (long_identifier_or_op
        :anchor
        [((long_identifier
           :anchor
           [((identifier) @font-lock-variable-use-face
             ("." (identifier) @font-lock-property-use-face):*
             "." (identifier) @font-lock-function-call-face :anchor)
            (identifier) @font-lock-function-call-face] :anchor))
         ((long_identifier
           (identifier) @font-lock-variable-use-face
           (identifier) :* @font-lock-property-use-face)
          :anchor (identifier) @font-lock-property-use-face :anchor)
         (identifier) @font-lock-variable-use-face])
       field:
       (long_identifier_or_op
        :anchor
        [((long_identifier
           :anchor
           [((identifier) @font-lock-property-use-face
             (identifier):* @font-lock-property-use-face
             "." (identifier) @font-lock-function-call-face :anchor)
            (identifier) @font-lock-function-call-face]) :anchor)
         ((_) @font-lock-property-use-face
          :anchor (identifier) @font-lock-function-call-face :anchor)
         (identifier) @font-lock-function-call-face])))

It tries to highlight the first identifier in a dot expression chain as a variable, all but the last field access (property/method) as property access and the last as function call (if inside application_expresssion).
The most complex part of this query comes from the long_identifier_or_op children, and it's possible combinations.

I think we are going to hit this issue with more than just long_identifier_or_op, there are so many nested options of how to colour application expressions etc.
For example, to colour the function call a subset of the colourings we could consider:
(application_expression
  .
  [
    (long_indentifier_or_op ...) @function.call
    (dot_expression ...) @function.call
    (paren_expression ...) @function.call
    (paren_expression (dot_expression ...) @function.call)
  ]
)

Particularly, the paren_expression with nested dot_expression could be nested arbitrarily many times  😅
I think a better solution might be to only highlight a construct at its most specific location, i.e.
(dot_expression . base: (_) @module)
(long_identifier_or_op . (identifier)+ @module (identifier))
(application_expression . (_) @function.call)

Yeah, I definitely agree with you that it's not entirely easy to make sure what's what when F# has such flexibility.

One such query I came up with that works decently is this, as you can see it's quite long.
((application_expression
       (dot_expression
        base:
        [
         (long_identifier_or_op
          :anchor
          (long_identifier
           :anchor
           (identifier) @font-lock-type-face
           :anchor
           (identifier):* @font-lock-property-use-face
           :anchor
           (identifier) @font-lock-property-use-face
           :anchor)
          :anchor)
         (long_identifier_or_op
          :anchor
          (long_identifier
           :anchor
           (identifier) @font-lock-type-face
           :anchor)
          :anchor)
         (long_identifier_or_op
          :anchor
          (long_identifier
           :anchor
           (identifier) @font-lock-type-face
           (identifier):* @font-lock-property-use-face)
          :anchor (identifier) @font-lock-property-use-face
          :anchor)
         (long_identifier_or_op
          :anchor
          (identifier) @font-lock-type-face
          :anchor)
         ]

        field:
        [
         (long_identifier_or_op
          :anchor
          (long_identifier
           :anchor
           (identifier) @font-lock-property-use-face
           :anchor
           (identifier):* @font-lock-property-use-face
           :anchor
           (identifier) @font-lock-function-call-face :anchor)
          :anchor)
         (long_identifier_or_op
          :anchor
          (long_identifier
           :anchor
           (identifier) @font-lock-function-call-face :anchor)
          :anchor)
         (long_identifier_or_op
          :anchor
          (_) @font-lock-property-use-face
          :anchor (identifier) @font-lock-function-call-face :anchor)
         (long_identifier_or_op
          :anchor
          (identifier) @font-lock-function-call-face
          :anchor)
         ]))
      (:match "^[A-Z0-9]" @font-lock-type-face))


vault version

Hi, I noticed that hashicorp has released version 1.12.x?
What version of vault is bank-vaults using?

I found https://github.com/banzaicloud/bank-vaults/issues/1673 and https://github.com/banzaicloud/bank-vaults/issues/1649 which are actually helpful

I've managed to get it working with - vault:1.10.8 / v1.24.7+k3s1

also this combo seems to work: vault:1.11.5 / v1.24.7+k3s1

@rkoosaar can I ask which storage backend you are using? I have a suspicion https://github.com/banzaicloud/bank-vaults/issues/1649 might be related to storage backend as I get this issue on Vault 1.11 on a cluster with Postgres storage but not on a cluster using Raft storage.

@rkoosaar I'm using file storage backend in this test environment. I do plan to switch to raft.
I've not tried with postgres.

I'm running 1.11.3 using a raft with bank-vaults 1.16.0 on k8s 1.23.* upgraded from 1.6.0 without problems.
for the iss we configured the issuer in the authentication config uing: kubectl get --raw=/.well-known/openid-configuration | jq -r .issuer

Vault >= 1.12.x is not supported actually by banks-vault: new vault clusters can't be initialized.
The problem is: https://support.hashicorp.com/hc/en-us/articles/10294862912659-Vault-operator-init-cross-version-limitation

Vault >= 1.12.x is not supported actually by banks-vault: new vault clusters can't be initialized. The problem is: https://support.hashicorp.com/hc/en-us/articles/10294862912659-Vault-operator-init-cross-version-limitation

I believe https://github.com/banzaicloud/bank-vaults/pull/1755 will fix this issue

It would be nice to more visibly document the latest version of Vault that is supported, especially if it's not reflected in the deploy examples.

Thank you very much for the comments, we are working on a documentation and also on testing together current Vault versions with the operator. The plan is to document all limitations, and also the policy that is that we are willing to support all Vault versions on a Best effort basis, focusing on the last and the last Vault 3 versions.

@bonifaido What versions of vault does the 1.19.0 support? If I was to upgrade to vault 1.12.3 would that work now?


How to deal with batch effects?

Thank you for the great contribution! I'm currently trying scHPF on a few datasets and found that it was easy to apply.
I'd like to know how to properly deal with batch effects (mostly technical covariates), e.g. when input was processed using different plates. Do you have recommendations?
A rather simple solution would be to identify those factors that correlate highly with the covariate of interest - and simply leave the factor out in e.g. further dimensionality reduction?
Best,
Jens

Hi Jens,
Glad you have found scHPF useful!  I think how you handle batch effects under the current scHPF model will be highly dataset dependent.
In general, I think what you propose sounds totally reasonable.  Keep in mind though that many scRNA-seq experiments in human are completely batch confounded (ie on different genetic backgrounds, on people with different environmental exposures, etc.), so it can be hard to tell a technical "batch" effect from real biology.  If you take the throw away approach, I think it's prudent just to check that the factor in question isn't also correlated with a covariate you care about (if possible).
Another approach we have taken is to apply scHPF separately across different conditions, and cluster the resulting factors using the top and bottom genes to find conserved expression modules.  See Figure 4, Extended Data Figure 4 and Methods in Szabo, Levitin et al, 2019.
Let me know if you have any other questions.
Best,
Hanna

Thanks a lot, Hanna, for your helpful elaboration on my proposed approach. Your correlation-based approach sounds very straight-forward and might be more suitable for what I'm after. I will give it a try!


Update messages.fr.xlf

Add "search" terms which were missing in French :fr:

Thanks @flibustier.


[RM-12999] remove bootstrap-rgw key via forgetkeys

Fixes: #12999
Signed-off-by: Travis Rhoden<EMAIL_ADDRESS>

Refer to this link for build results (access rights to CI server needed):
http://jenkins.ceph.com//job/ceph-deploy-pull-requests/1755/
Test PASSed.


Running spdy with negroni results in no spdy support.

Running spdy with negroni results in no spdy support.
Example code:
import (
  "github.com/codegangsta/negroni"
  "github.com/SlyMarbo/spdy"
  "net/http"
  "fmt"
)

mux := http.NewServeMux()
mux.HandleFunc("/", func(w http.ResponseWriter, r *http.Request) {
    fmt.Fprintf(w, "%f", spdy.SPDYversion(w))
})
n := negroni.New()
n.UseHandler(mux)

err := spdy.ListenAndServeTLS(":443", "cert.pem", "key.pem", n)

See also https://github.com/SlyMarbo/spdy/issues/80

Thanks for linking this. If fixing this means exporting the ResponseWriter then we can look into supporting this

+1

I'm closing this out since (afaict) ResponseWriter is now public.  Please yell if this needs to be reopened! 😻


The WebGL renderer does not produce the same output as the GLES renderer after updating to samplers.

Hi, I am a member of a team that is porting a D3D renderer of Perimeter to Sokol. We are doing this in our free time, so it has taken a while. We started before Sokol had samplers. A couple of days ago, we updated our Sokol to the latest version, and everything was smooth, except for WebGL.
The WebGL renderer does not produce the same output as the GLES renderer on Linux. This is a bit strange; we didn't change anything, just split the shaders to use samplers. We have two objects that are rendered incorrectly in WebGL: an energy shield (the blue one) and chaos (fog outside of the terrain).
GLES3/WebGL without samplers:

WebGL with samplers:

Same picture in FF, Chrome, none WebGL warnings.
The chaos is just black, and the shield should be blue and is actually visible but too transparent. The shader used to render these objects is also used for many other objects and seems to work fine. Unfortunately, we have no idea what could be going wrong, maybe some internal state of Sokol. It could certainly be an issue with our renderer code, but why then does it work fine on Linux with GLES and the only problem is with WebGL?
Anyway, maybe you have some ideas for tests.
I did a bisect, and the first bad commit that I was able to build is:

sokol: facd53fdf15b5d893bcefd98f613d3ed27375215
tools-bin: 6040b18d39649d56dbae2ae1aed59fb755b26369

Here is the shader code (very simple):
Without samplers:
shader.txt
With samplers:
shader2.txt
Note: In shader2.txt, we use one sampler for two textures. I'm not sure if this is valid, but we also tried using two samplers for two textures with no differences.

Strange indeed. I'll set aside some time over the next few days to look at the problem.
Is there some way I can test the WebGL build myself? (e.g. is is hosted somewhere?)

Btw in the latest demo link you provided (with the Imgui-Integration) I'm seeing the fog (in Chrome on macOS):

Did you update sokol_gfx.h since the time those textures showed up as black? As I wrote on Twitter, until end of Oct-2023 there was a bug in the GL backend which caused textures without mipmaps to render as black/transparent if they used a sampler with a .mipmap_filter != SG_FILTER_NONE. WebGL may be especially strict about this, while native GL implementations may be more forgiving there.
But this had been fixed in the meantime.
How can I best check the energy shield?

PS: once we figured out that texturing problem we should do something about the many create/destroy buffer calls per frame, and that each sg_draw() is accompanied by a viewport, scissor-rect, pipeline and bindings-update (is possible) :)

Hmm, I also see the fog though on the non-imgui build with samplers (where it should be black).

Oh, that's true; it works! I didn't test it on different OSes, and so I thought it was just broken. But now, after more testing, we can say that it works everywhere except on Windows. I also tried setting .mipmap_filter to SG_FILTER_NONE - it didn't help.

Does not work (both chaos and shield):

Windows 11 Chrome <IP_ADDRESS> ANGLE (NVIDIA, NVIDIA GeForce RTX 3050 Laptop GPU (0x000025A2) Direct3D11 vs_5_0 ps_5_0, D3D11)
Windows 11 Firefox 123.0 ANGLE (AMD, Radeon HD 3200 Graphics Direct3D11 vs_5_0 ps_5_0), or similar
Windows 10 + RTX 2070 on FF
Windows + Intel GPU

Works fine:

Ubuntu 23.10 + Intel
linux + firefox + AMD Ryzen 7700 igpu
Mac M1 Firefox / Chrome
MacBook Pro 13 Iris GPU Chrome

Regarding shield:
Just start a Battle game instead of a campaign, then place the energy core and activate the shield.

Also natively it works fine:

windows native GL on Wine and real windows
gles3 on unbuntu under wsl

Ok, I have a Windows PC with RTX2070 and a Windows laptop with Intel GPU, should be close enough to reproduce.
It almost looks like a D3D11 limitation I'm not aware of yet.

This is commit that introduced this bug in game https://github.com/KD-lab-Open-Source/Perimeter/commit/e06f09ca458322718dcf3f0554f5610aec5afa48

Currently im trying to compile it with sokol enabled for D3D11, will report back once it works

One obvious difference I see is here when creating a sampler object:
    sampler_desc.min_filter = SG_FILTER_LINEAR;
    sampler_desc.mag_filter = SG_FILTER_LINEAR;
    sampler_desc.mipmap_filter = SG_FILTER_LINEAR;

...this is different from this old code:
imgdesc->min_filter = imgdesc->mag_filter = SG_FILTER_NEAREST;

...the equivalent would be:
    sampler_desc.min_filter = SG_FILTER_NEAREST;
    sampler_desc.mag_filter = SG_FILTER_NEAREST;
    sampler_desc.mipmap_filter = SG_FILTER_NONE;

Nearest vs Linear shouldn't result in the such a rendering artefact though, and @caiiiycuk already confirmend that changing the mipmap filter doesn't make a difference, and D3D11 doesn't have an actual 'none' mipmap filter mode anyway, only 'point' (aka nearest) or 'linear'.

...not much new from my side today except that I see the error on my Windows laptop too.
So we definitely have a case where WebGL behaves differently between platforms, which is very unusual.
Do you guys know what those two textures are which are affected, and what could be special about them? Things like "non-power-of-2" - although that shouldn't matter anymore on WebGL2. But there must be a reason why some textures have that problem while others work fine.

Btw, the Sprector.js webgl debugger might come in handy, for instance here I have the drawcall selected which renders the black background. On the right side you can inspect the entire WebGL2 state at the time of the drawcall. I haven't dived in detail into the state yet though.
The extension is here: https://chromewebstore.google.com/detail/spectorjs/denbgaamihkadbghdceggmchnflmhpmk
Here's what it looks like with the problematic draw call selected:

Btw, when I look very closely on my Intel GPU laptop I actually see some moving "cloud structures" in the black area, so it's not completely black, just extremely dark... hmm.

Yeah, and shield also sometimes visible it just  too much transparent. The chaos (fog) render is very simple, it just two cloud textures that moving by translation matrix. Maybe there is some browser bug with loading webp image (faced this once on iphone safari). Probably I can try to extract this into simple test case.

I mean tex coordinates changing each frame, vertexes are stable

Luckily, when @IonAgorria added support for D3D11, he removed the glsl100 dialect from the list of supported dialects. After that, rendering started to work fine. There is probably a bug in sokol-tools-bin that generates code to load glsl100 shaders in a GLES3 environment.

Here is a zip with shaders glsl330:glsl300es:metal_macos and "glsl330:glsl100:glsl300es:metal_macos.
shaders.zip

Of course. Supporting GLSL100 seems unnecessary, but could there be an error in the Sokol tool? It appears there are two blocks defined with #if defined(SOKOL_GLES3), where one block uses GLSL100 code and the other uses GLSL300es. Is that correct?

Theoretically it makes sense from the standpoint that GLSL100 shaders should also work in GLES3/WebGL2 (which for the most part they do, but as you discovered apparently not always). I'm not sure if sokol-shdc does the right thing when both glsl100 and glsl300es output is created, but in any case it makes more sense to remove glsl100 output from sokol-shdc entirely.


Every slurm job is downloading the model again!!

I am trying to run Harmbench for humanJailbreak on Llama2. I am using p3.8xlarge, which has four Tesla V100-SXM2-16GB. Every slurm job is trying to download the model again and again. resulting in Cuda out of memory error. Is it possible that I do not have sufficient memory? Should I upgrade to bigger GPUs or is a slurm configuration mistake?
torch.cuda.OutOfMemoryError: CUDA out of memory. Tried to allocate 32.00 MiB. GPU 1 has a total capacity of 15.77 GiB of which 26.88 MiB is free. Process 50977 has 984.00 MiB memory in use. Process 51004 has 984.00 MiB memory in use. Process 50968 has 984.00 MiB memory in use. Process 51008 has 984.00 MiB memory in use. Including non-PyTorch memory, this process has 984.00 MiB memory in use. Process 50975 has 952.00 MiB memory in use. Process 51021 has 984.00 MiB memory in use. Process 51035 has 984.00 MiB memory in use. Process 51009 has 984.00 MiB memory in use. Process 51039 has 984.00 MiB memory in use. Process 51038 has 984.00 MiB memory in use. Process 52508 has 1.30 GiB memory in use. Process 52577 has 1.30 GiB memory in use. Process 52628 has 1.30 GiB memory in use. Process 52550 has 1.30 GiB memory in use. Of the allocated memory 676.03 MiB is allocated by PyTorch, and 1.97 MiB is reserved by PyTorch but unallocated. If reserved but unallocated memory is large try setting PYTORCH_CUDA_ALLOC_CONF=expandable_segments:True to avoid fragmentation.  See documentation for Memory Management  (https://pytorch.org/docs/stable/notes/cuda.html#environment-variables)

Hi @GammaKing2000 , can you share the command you run to reproduce the error? Also, have you tried request more gpus for each job?

Slurm.conf
`ClusterName=localcluster
SlurmctldHost=localhost
MpiDefault=none
ProctrackType=proctrack/linuxproc
ReturnToService=2
SlurmctldPidFile=/run/slurm/slurmctld.pid
SlurmctldPort=6817
SlurmdPidFile=/run/slurm/slurmd.pid
SlurmdPort=6818
SlurmdSpoolDir=/var/lib/slurm-llnl/slurmd
SlurmUser=slurm
StateSaveLocation=/var/lib/slurm-llnl/slurmctld
SwitchType=switch/none
TaskPlugin=task/none

TIMERS
InactiveLimit=0
KillWait=30
MinJobAge=300
SlurmctldTimeout=120
SlurmdTimeout=300
Waittime=0
SCHEDULING
SchedulerType=sched/backfill
SelectType=select/cons_tres
SelectTypeParameters=CR_Core

#AccountingStoragePort=
AccountingStorageType=accounting_storage/none
JobCompType=jobcomp/none
JobAcctGatherFrequency=30
JobAcctGatherType=jobacct_gather/none
SlurmctldDebug=info
SlurmctldLogFile=/var/log/slurm-llnl/slurmctld.log
SlurmdDebug=info
SlurmdLogFile=/var/log/slurm-llnl/slurmd.log

COMPUTE NODES
NodeName=localhost CPUs=32 CoresPerSocket= 16 ThreadsPerCore=2 Gres=gpu:4 RealMemory=245610 State=UNKNOWN
PartitionName=LocalQ Nodes=ALL Default=YES MaxTime=INFINITE State=UP
DebugFlags=gres
GresTypes=gpu`
Gres.conf
NodeName=localhost Name=gpu File=/dev/nvidia[0-3]
Command
python ./scripts/run_pipeline.py --methods HumanJailbreak --models llama2_7b --step 2 --mode slurm

Hi @GammaKing2000,
Could you try downloading the model into a fixed location using snapshot_download? You can then adjust the model_name_or_path parameter in configs/model_configs/models.yaml for the models you want to load. If model_name_or_path points to a local folder, all the Slurm jobs should load the model from there rather than downloading it from scratch.


Tweaks to fetching CycloneDX SBOM

This commit changes the mechanism of fetching CycloneDX SBOMs. It now only takes into account the SBOM from within the image if necessary. It also has additional logic to either use the prefetched SBOM from the image, or fetch it directly from rego.
This change allows us to stop fetching the SBOM from the image from the EC CLI. Paired with those changes, this commit will have a significant performance boost, most notably to large images.
Resolves #1115

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

Project coverage is 100.00%. Comparing base (c9ed21c) to head (d7a138b).

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #1127   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files          117       117
  Lines         5857      5874   +17
=========================================
+ Hits          5857      5874   +17

Files with missing lines
Coverage Δ

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

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


can't edit or start azure function logging from visual studio code or portal

i can't edit function code or start azure function logging from visual studio code or the portal. same thing with storage (tables). yes, the storage account exists, i can access it and the tables within from the azure storage explorer desktop application. but not from the portal or visual studio code. the error below is from visual studio code:
Repro steps:1.2.Action: azureFunctions.startStreamingLogsError type: BadRequestError Message: Cannot resolve https://ls01storage.file.core.windows.net/. Please check if storage account exists.Version: 0.16.0OS: win32VS Code Version: 1.33.1Call Stackmodule.exports.l.pipeline (dist/extension.bundle.js:277:1572169)s (dist/extension.bundle.js:277:110820)s (dist/extension.bundle.js:165:25754)dist/extension.bundle.js:165:26994o (dist/extension.bundle.js:223:7055)dist/extension.bundle.js:165:24675$.module.exports.t.requestLibrarySink.t.headersOnly.t.streamedResponse.t.body.function.t.body.pipe.a [as _callback] (dist/extension.bundle.js:1:579051)$.module.exports.$.init.t._callback.t.callback.t.callback (dist/extension.bundle.js:253:5461)$.emit (events.js:182:13)$.<anonymous> (dist/extension.bundle.js:253:18274)$.emit (events.js:187:15)IncomingMessage.<anonymous> (dist/extension.bundle.js:253:17116)Object.onceWrapper (events.js:273:13)IncomingMessage.emit (events.js:187:15)endReadableNT (_stream_readable.js:1090:12)process._tickCallback (internal/process/next_tick.js:63:19)

@mahesh2000 can you add repro steps describing how you got into this position? For example, how did you create the function app? How did you deploy? And what language is your project?

hi,

everything started working again after 30 minutes. must've been a system problem on your end.

sometimes i have to log out and log in to azure portal several times (in the incognito window, because in the regular window it defaults to some other non-personal account with the same email address and even after i get it going with the right one, it will eventually go back to that; i don't want to keep clearing my cookies all the time) to get things to go right.

the azure function editor (online) won't work properly after about 30-60 minutes, so i copy the entire code to a local notepad, click on something else in the browser (say Storage) at which point i'm asked to save my changes (they don't get changed, so there's no point) and then clicking on functions again to get everything in the function blade to work again.

the log window will often disconnect.

there doesn't seem to be a way to edit existing functions in visual studio code, so if the portal isn't working, i'm stuck.

thanks!
mahesh

@mahesh2000 you're correct - we don't support editing existing functions. If you want to edit functions, we suggest creating/editing the functions on your local machine and deploying from VS Code. You can follow the steps as outlined in this tutorial:
https://code.visualstudio.com/tutorials/functions-extension/getting-started


METRON-1081:  Fix Alerts and Ops UI Notices file

Contributor Comments
[Please place any comments here.  A description of the problem/enhancement, how to reproduce the issue, your testing methodology, etc.]
Pull Request Checklist
Thank you for submitting a contribution to Apache Metron.
Please refer to our Development Guidelines for the complete guide to follow for contributions.
Please refer also to our Build Verification Guidelines for complete smoke testing guides.
In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? If not one needs to be created at Metron Jira.
[ ] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
[ ] Has your PR been rebased against the latest commit within the target branch (typically master)?

For code changes:

[ ] Have you included steps to reproduce the behavior or problem that is being changed or addressed?

[ ] Have you included steps or a guide to how the change may be verified and tested manually?

[ ] Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:
mvn -q clean integration-test install && build_utils/verify_licenses.sh

[ ] Have you written or updated unit tests and or integration tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

[ ] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via site-book/target/site/index.html:
cd site-book
mvn site

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
It is also recommended that travis-ci is set up for your personal repository such that your branches are built there before submitting a pull request.

I am not sure how to verify or review this

go to /Users/jsirota/Documents/hcp_release/metron-interface/metron-config and delete the node_modules folder.  then run npm install -prod to only pull in production libraries.  then run npm i npm-license-crawler -g to install the crawler program. then run npm-license-crawler --csv licenses.csv

Are the modules/versions pulled in dependent on the version of node or something?  My list is different.  I have more things, and different versions for some.
licenses.txt

Is this still relevant?

Yes, and needs to be done as an ongoing thing really. We have to keep on top of our Node licenses. I note that recent version of angular cli actually seem to generate licence and notice files for you, but not had chance to verify their depth and correctness yet. This may make life easier in future, but for now we're on older angular-cli, so have to use this method to keep on top of things.

+1 by inspection

So, no comment on the discrepancy I found then?

@ottobackwards I just re-ran this. We're not fixing versions in the UIs at the moment, so I would expect this kind of minor variance. This is mainly to ensure licenses are at least covered. The solution to the version fixing is the yarn stuff we're discussing elsewhere.

I assume we are doing this for apache compliance.  Our acceptance of this variance is compliant then.  That was not my understanding.  But I'm sure the chair knows.
Thanks

Sorry otto, I didn't see that comment, I'll admit.  I apologize.  Let me take a look at them and if there's further notices work to do, I'll make a follow-on PR.  Again, sorry, ignoring your discrepancy wasn't my intent.


[ML] add question_answering nlp configuration types

related: https://github.com/elastic/elasticsearch/pull/85958

superseded by: https://github.com/elastic/elasticsearch-specification/pull/1687


IngressMonitor

What is missing? Why do we need it?
The custom resources ServiceMonitor,PodMonitor can be used to specify a set of services and pods that should be monitored and for which the Prometheus operator generates the respective scrape config section.
That would also be very useful for k8s ingresses resources.
I'd propose to add IngressMonitor generating the scrape config for ingress resources based on that definition.
I'd be willing to come up with a PR similar to #2566 if there's a general agreement.

Something like this would really be most useful for blackbox exporting right? In that case I'd prefer if we could integrate something like this into the ideas discussed in #2680.

Exactly what I had in mind @brancz. Closing in favour of #2680.


Julia and R are missing on macos arm64

Description
New issue in case the discussion at https://github.com/actions/runner-images/issues/9394 is missed
Platforms affected

[ ] Azure DevOps
[ ] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] Ubuntu 24.04
[ ] macOS 12
[ ] macOS 13
[X] macOS 13 Arm64
[ ] macOS 14
[X] macOS 14 Arm64
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
Current runner version: '2.319.1'
Is it regression?
No
Expected behavior
These runtimes are included.
Actual behavior
These runtimes are not included.
Repro steps
NA

If the concern was about upstream support on the new platform, Julia has tier 1 support on Apple Silicon (aarch64-apple-darwin), and it has been so for over one year now

Hey @IanButterworth!
It was decided to remove the specified packages from the image due to the fact that they can be installed in less than a minute and also due to the need to take into account maintenance needs. I checked - the situation has not changed. Both packages can be quickly and easily installed at runtime using both official sources and the pre-installed Homebrew package manager. For example:
jobs:
  test:
    strategy:
      matrix:
        os: [ macos-14, macos-13 ]
    runs-on: ${{ matrix.os }}
    steps:
      - name: Julia
        run: |
          curl -fsSL https://install.julialang.org | sh -s -- -y
          # Depending on which shell you are using, run one of the following
          # commands to reload the PATH environment variable:
          . /Users/runner/.bashrc
          . /Users/runner/.bash_profile
          . /Users/runner/.zshrc
          julia --version
          juliaup --version
      - name: R
        run: |
          brew install r
          r --version

Unfortunately, the reasons for which the decision was made have not changed. We have to work to remove as many pre-installed packages as possible that are less frequently used and at the same time can be installed quickly and easily by users from new images, both to simplify the image build and maintenance process and to free up more available disk space.

Ok. Is there a plan to deprecate to homogenize the platforms?
Also, it's tricky to manage this partially because the docs are spread over multiple pages. Perhaps a single table could be made to show what's on each platform?

Ok. Is there a plan to deprecate to homogenize the platforms?
Also, it's tricky to manage this partially because the docs are spread over multiple pages. Perhaps a single table could be made to show what's on each platform?

This is a rather complex question. We have a support policy that we follow. All other optional packages vary from version to version depending on many factors. At the moment, the most consistent images are macOS-13 and macOS-14. macOS-12 contains many obsolete or unused packages in future OS versions. There is also some difference between the Intel and arm64 versions of the images, which we are unable to eliminate due to the architectural difference and which will be present for some time.

Support policy


add sample for amp-3d-gltf

Addresses https://github.com/ampproject/amp-by-example/issues/1297

The AMP validator does not yet seem to support all features of amp-3d-gltf. When is it going to be updated?

I am waiting for some response in this issue https://github.com/ampproject/amphtml/issues/15793

Validator is fixed, and relative paths should work in amphtml's master. I don't know when those changes will be visible from this project though.

Thanks to recent release, it seems to work on my machine. Though I had to add cors: true in your serve task (didn't committed that)

Though I had to add cors: true in serve task in gulpfile (didn't committed that)
the live example is currently broken due to the CORS issue.

@sebastianbenz would you help to enable CORS ? I created an issue to track #1446


Documentation clarification

[Enter feedback here]
Need clarification on the documentation as it reads below.
AADConnect can synchronize the same users, groups, and contacts from a single Active Directory to multiple Azure AD tenants. These tenants can be in different Azure environments, such as the Azure China environment or the Azure Government environment, but they could also be in the same Azure environment, such as two tenants that are both in Azure Commercial.
My understanding is "AADConnect (even with this release) does not support sync from one server to multiple tenants and there is no plan to support it" the above documentation needs to be modified to clarify this.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0562f646-ef99-e341-e2fc-fcc3eed44d15
Version Independent ID: 1fc5ebad-f1b3-babe-f492-c6c888c7781a
Content: Azure AD Connect: Supported topologies
Content Source: articles/active-directory/hybrid/plan-connect-topologies.md
Service: active-directory
Sub-service: hybrid
GitHub Login: @billmath
Microsoft Alias: billmath

Hi @Ravi-Kashyap , where did you get the info that this isn't supported even with this release?

from product team.

Closing this out in light of our offline discussion. Bullet #3 addresses this point by stating "You will need to deploy an AADConnect server for every Azure AD tenant you want to synchronize to - one AADConnect server cannot synchronize to more than one Azure AD tenant."


Link to code of conduct solved.

This PR fixes the following issue:
fixes #31
Changes made:

Added the working link of code_of_conduct.md in the readme file.
Now in the readme.md file code of conduct link is working properly.

Hey @Rishav1707 thoughts on just making this an explicit reference to the CODE_OF_CONDUCT.md file in the repo instead of the full link. It would port better if the repo gets moved/changed

ok

Hey @Rishav1707 thoughts on just making this an explicit reference to the CODE_OF_CONDUCT.md file in the repo instead of the full link. It would port better if the repo gets moved/changed

Done @jonathanloos


Additional async tests

Added some additional tests to make sure there won't be any behavior mismatches between the async and the sync versions.

Coverage: 93.75% (+2.3%) from 91.44% when pulling 2ebbc3a5a77d1d5800454570d747c7a8edd7dd79 on Czocher:additional-async-tests into be0834c6ecf1af38a9ed6c505ed3eecdf37aa3a8 on cljoly:master.


fix: missing parse errors with --noserver

Refactor request processing so that the flow is the same with and without --noserver command line option which was preventing parse errors being reported when --noserver was specified.
Add duration in milliseconds to request logging so we easily monitor how long the server side requests are taking.
Explicitly handle 404 errors so we don't needlessly retry them with a slow direct request.
Use chaining to improve readability.
Fixes #323

Mega-linter being shit and failing for spell using too many requests.

@nvuillam in case you missed the notification for the review of this, cool if you just didn't have time yet.

@stevenh do you want a new release right now or do you prefer to do it later yourself with new release management ?

I'd say it can wait, not sure when I'll get chance to look at new release process but this would be a nice test case.


Unique title background color

This commit series splits the title of the widget from the card list area with a small transparent separator, and (optionally) allows setting the title background and foreground from the list background and foreground.
By default, I've made the title slightly less opaque than the list.  I think it looks good like that.  But users can now customize the look more if they like.
The color selectors for the title background and title foreground now have a new button that will copy in the color of the list background and list foreground, so it's easier to set the list background/foreground, copy them to the title, then tweak the title's opacity or saturation a bit.

@lack can you push this to another remote branch?
I want to try it myself before merging.

Gladly!

Should be there for you as origin/lack/unique_title_background_color
Btw, I was a bit unhappy at first about the move to kotlin as I have a few more branches in the works that I had to basically redo. But the more I code in it the more I like it; A big improvement over java. Thanks for forcing me to learn a very nice language :)

I see it, thanks.
 It's pretty cool :)


Feature request: HDF5Matrix support for inferred slice indexing

@fchollet @jfsantos @mezzode @SnowMasaya @Danielhiversen @lebavarois @nithishdivakar
Hello,
The implementation of the HDF5Matrix class does not support inferred slices (e.g. data[:10]) as the code expects both key.start and key.stop to be integers.
https://github.com/fchollet/keras/blob/master/keras/utils/io_utils.py
Here is tiny modification to the if statement to support the said operation.
https://github.com/siryog90/keras/blob/inferred_HDF5_slices/keras/utils/io_utils.py
This is a small issue, but it can get annoying when inferring the end index (e.g. data[10:]), as I have to check the shape of the data set each time.
May I request a pull?

Sure, go ahead and open a PR.
On 17 April 2017 at 11:42, Sergey Kojoian<EMAIL_ADDRESS>wrote:

@fchollet https://github.com/fchollet
Hello,
The implementation of the HDF5Matrix class does not support inferred
slices (e.g. data[:10]) as the code expects both key.start and key.stop
to be integers.
https://github.com/fchollet/keras/blob/master/keras/utils/io_utils.py
Here is tiny modification to the if statement to support the said
operation.
https://github.com/siryog90/keras/blob/inferred_HDF5_
slices/keras/utils/io_utils.py
This is a small issue, but it can get annoying when inferring the end
index (e.g. data[10:]), as I have to check the shape of the data set each
time.
May I request a pull?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fchollet/keras/issues/6297, or mute the thread
https://github.com/notifications/unsubscribe-auth/AArWb78c4lRPlI090U6UcQ0I674FT0Dzks5rw7KHgaJpZM4M_bSZ
.

Single item access with
idx = 0
X = HDF5Matrix(args.database, 'train_patches', 0, None)
tmp = X[idx]

gives now errors like
File "/usr/local/lib/python3.4/dist-packages/keras/utils/io_utils.py", line 65, in __getitem__
    start, stop = key.start, key.stop
AttributeError: 'int' object has no attribute 'start'

@kielnino You are not using the newest version of Keras. Try to upgrade and see if that solves your problem.


Running wrangler publish on changed content seems to be buggy

Environment

operating system:
output of rustc -V: rustc 1.43.0
output of node -v: v10.20.1
output of wrangler -V: 👷 ✨  wrangler 1.11.0

Wrangler.toml
name = "my-site-default"
type = "webpack"
account_id = "some_id"
workers_dev = false
route = "somedomain.com/*"
zone_id = "some_zone"
kv-namespaces = [
	{ binding = "REDIRECTS", id = "some_id", preview_id = "some_id" }
]
[site]
bucket = "build"
entry-point = "workers-site"

[env.beta]
name = "my-site-beta"
entry-point = "workers-site-beta"
bucket = "build"
route = "beta.somedomain.com/*"
kv-namespaces = [
	{ binding = "REDIRECTS", id = "some_id", preview_id = "some_id" }
]

[env.production]
name = "my-site"
entry-point = "workers-site"
bucket = "build"
route = "somedomain.com/*"
kv-namespaces = [
	{ binding = "REDIRECTS", id = "some_id", preview_id = "some_id" }
]

Steps to reproduce

I run wrangler publish inside my build folder.
Then I use rsync -auv someIncrementalBuildFolder/ build/ to merge changes inside build/ folder (someIncrementalBuildFolder contains some new pages that needs to be added / replaced on worker site)
Then I run wrangler publish again. It finishes 43 seconds - but when I request the route that was added, I get a 404.
I verified that the route I am requesting does exist inside build/ folder.

What did you expect to see?
I would expect a 200 status code along with the contents.
What did you see instead?
I got a 404.

Not sure how this bug actually happend.
I notice that inside my /build/ folder there is no worker.js file as there is in /dist/ (dist was usually my go to, but I have just changed to /build/ and changed bucket to build).
Maybe it is related to changing the bucket configuration in wrangler?

Upon debugging further, I wanted to test to clear the whole KV namespace and then rerun wrangler publish. So I deleted the namespace, and ran wrangler publish again. It then said: 🌀  Created namespace for Workers Site "__jwr-nuxt-beta-workers_sites_assets" and I see the namespace in the dashboard. However, nothing happens after that. Rerunning it again it says 🌀  Using namespace for Workers Site "__jwr-nuxt-beta-workers_sites_assets" no keys are in. But site is still being served.
What am I missing here?

Maybe related? https://community.cloudflare.com/t/wrangler-claims-to-successfully-publish-but-doesnt-actually-update-workers/128316/4

Hoping it could help to rename the KV name (name = "something-unique"), but it didn't

I tried running with --verbose, but it seems as though that argument has been removed. It's funny, because the publish command use to output, e.g. "Routes stayed the same", but it sems to never get that far, and instead halt at 🌀  Using namespace for Workers Site "__jwr-nuxt-beta-workers_sites_assets"

Sorry, I don't want to stress this / you @ispivey, but I am eager to find a solution so I can continue deploying with my otherwise beloved Wrangler <3
Any temporary solutions / workarounds I can try would be greatly appreciated.

This is how it looks:

Ok, so I have just tested locally, and there it works fine. It's only on our deployment server it silently fails.

I have tried uninstalling wrangler completely, then re-install, but that did not help either

Not sure what went wrong, but I decided to start from scratch:

Created new user
Installed nvm as is the recommended way to use wrangler
Installed everything
Ran wrangler publish
Everything works fine.

Still curious what went wrong though.

i'm really glad you got this working @simplenotezy ! i'm going to close this for now, but if you end up reproducing the bug, we'll be happy to look into it 😄 !

Sorry to dig this back up but I'm having issues with files + KV as well.
I set up a new site wrangler generate --site my-site and tried publishing it:
C:\Code\my-site>wrangler publish --verbose
 Built successfully, built project size is 13 KiB.
 Using namespace for Workers Site "__my-site-workers_sites_assets"
 Success
 Uploading site files
 Successfully published your script to
 https://my-site.aelamarre.workers.dev

Nothing seems to get deployed though: https://my-site.aelamarre.workers.dev


improved implementation of ridge filters (bug fixes and reduced memory footprint)

related to #419
A large overhaul of the ridge filters, addressing inaccuracies and errors has been implemented for scikit-image 0.20. This PR ports the same changes to these functions to cuCIM.
upstream PRs:

scikit-image/scikit-image#6149
scikit-image/scikit-image#6440
scikit-image/scikit-image#6446
scikit-image/scikit-image#6509

These fix various bugs, simplify the implementation and reduce the memory footprint

@gpucibot merge

Merged this one so I can rebase #434 on top of it to look at one failing test case in the ridge filters.


Preview Mode alters the edit path of certain entity types, showing the preview iframe instead of the edit form

I configured the Preview Mode using the "Site Selector" plugin for two entity types and their bundles:

Custom Block - Footer (a custom bundle I created)
Custom menu link - Custom menu link

When a visit the edit URL of one of those entities, I see the preview iframe instead of the edit form, making impossible for editors to update them:
https://my-drupal-site/admin/structure/menu/item/5/edit

In other entity types and bundles (such as node--page) the problem is not occurring.

Yes. Preview mode takes over the canonical path for the entity. For content types, this is their View page. For blocks and menus, the canonical path is the Edit page.
Preview mode is intended to be enabled for entity types that have an equivalent path on the Next.js site. Example an article on Drupal having a /articles/path-of-article on the Next.js site.
Is there a reason you're enabling preview mode for blocks and menus?

I'm trying to enabling NextJS preview mode for Custom Blocks and menus because I want to send revalidation requests when the block or main menu are updated.
If I add a block entity (and a Revalidator) and don't assign a Plugin in the Preview Mode form, when trying to edit the block I get:
Error: Call to a member function getSitesForEntity() on null in Drupal\next\Render\MainContent\HtmlRenderer->prepare()
But if I do assign a site, like @camilo-escobar says, the non-working preview now obscures the block edit form.
Similar for custom menu links.

#481  would solve this issue for me because I could keep the Revalidation for my entity type but remove all sites from Preview.. I'm not sure if @camilo-escobar actually wants preview on blocks & menu items or was just trying to mitigate the error like me.

Fixed by #481


SVG with custom namespace fails check

Checking a SVG using a custom namespace fails with an error--epubcheck doesn't seem to recognize the custom namespace.  Here's a minimal, valid test SVG:
<?xml version="1.0" encoding="UTF-8"?>
<svg xmlns="http://www.w3.org/2000/svg" xmlns:test="https://example.org" version="1.1" viewBox="0 0 10 10" test:foo="bar">
</svg>

Expected result:
The valid SVG should not generate check errors.

This and #489 are causing issues with automated validation. It would be best not to write exceptions to EpubCheck, or sanitize SVG created by third party design tools that add their own namespaces.

@chrisauclair Hi, I'm not sure this is the right place but should I understand that we can use a custom namespace in epub3, but it won't be recognized by epubcheck?

@jacqueslelezard, my understanding is that namespaces should be supported because the specs for EPUB 3.1 and 3.0.1 require versions of SVG that use the same namespace rules as XML.

Do we agree that such foreign attributes should be allowed anywhere in SVG?  I can easily provide schema changes for this.

Do we agree that such foreign attributes should be allowed anywhere in SVG? I can easily provide schema changes for this.

Agreed. But probably our spec-guru @mattgarrish can have a second look at this ;-)

Technically it's both foreign elements and attributes that are allowed.[1]
Unlike HTML, which requires extending to be valid, SVG just expects foreign elements/attributes to be ignored by the UA. Further, we don't have a content restriction against either in the Content Docs spec.
[1] https://www.w3.org/TR/SVG/extend.html

If we do not use NVDL, alowing foreign elements requires a lot of changes to RNG  schemas.    But if we use NVDL, it is very easy to allow foreign elements and attributes without changing RNG schemas.  Does epubcheck now use NVDL?

There seems to be a SVG NVDL file in src/main/resources/com/adobe/epubcheck/schema/30/, but I think it's only used for the tests. Maybe I'm wrong and @rdeltour can help.
However, the SVG validation seems to be based on the RNC file in the same folder, which is referenced in the Java sources.
Don't know if this helps...

With nvdl you can remove the foreign attributes and elements from validation prior to comparing against the rnc schema. Without it, validation get more complicated as @murata0204 says.
But this is a little more complicated problem. I was digging through the specs, and even though SVG is permissive, HTML is not. So when an SVG is embedded in HTML, foreign namespaces are not allowed, as HTML only recognizes HTML, SVG and MathML for content. Only a top-level SVG document would allow foreign namespaces.
So the current behaviour is correct when validating within HTML, and would need to be retained in that context.

If NVDL validation is now invoked by epubcheck internally, I think that an NVDL script (only for SVG cont. doc) is a good solution.  It can allow both foreign elements and attributes.  If not,  I am inclined to allow foreign attributes  by revising the RNG schema for SVG.

It appears that NVDL is used for EPUB2 validation but not for EPUB3 validation.  See \src\main\java\com\adobe\epubcheck\ops\OPSChecker.java and \src\main\java\com\adobe\epubcheck\xml\XMLValidators.java.
I think that the best approach is to use NVDL for EPUB 3 valdiation.  But regression test, is probably required for such a big change.  I am afraid that I cannot do the test.  Can somebody help me?

Matt wrote:

But this is a little more complicated problem.   I was digging through the specs, and even though SVG is permissive, HTML is not.

So, we need a different NVDL script for SVG cont docs and XHTML cont docs.

I briefly looked into this. As the extensibility rules vary for embedded SVG islands and top-level SVG documents, I would suggest:

leave the XHTML validation as-is, i.e. relying on the validator.nu schemas (and ultimately, on the full validator.nu code)
use NVDL for SVG Content Documents

I can already tweak the XML parser to support data-* attributes in SVG (both contexts), and remove attributes in foreign namespaces in an XHTML context (in an SVG context, this would be handled by NVDL).

I can probably create an NVDL script for this purpose.

@murata2makoto I've made a start in PR #970. Feel free to improve on it.

Closed in #970


Generate base data layers - SRTM

Generate the following layers globally for SRTM

Slope (rad)
Aspect (rad)
Hillshade
Tobler
Water bodies

Can we run these across a 7 node, 20 node, 100 node, 500 node?
Also when you run tobler will that be the full script or in piece parts?
Last would it also be possible to run this on a 7 node bare metal cluster without S3?
Hum maybe this is getting too close to the benchmarking task, but I can't help but ask the questions..  Nice work guys.

Sure thing. I can run tobler either way, was planning on full script.


Update to version 1.0.1

Removing RC designation and updating to 1.0.1. Will use regular semver going forward.

Thanks @caraclarke!


Add markthink to Chinese review/approver teams

Fixes #10682
This PR adds @markthink to SIG Docs review/approver teams for content/zh/.
This PR is on hold pending @markthink joining the K8s org.
/hold

/lgtm

@zacharysarah thank you.

@markthink 👋 Ping for org membership--looks like you still need to open a new issue.

@zacharysarah ok, I have submitted the issue at https://github.com/kubernetes/org/issues/186.
The current Chinese translation article is managed by [Google Sheets] (https://docs.google.com/spreadsheets/d/1k49XTmtEkhjeh9M118fwwcXVfHvCe-DCy6sVVRQAxBk/edit?usp=drive_web&ouid=113717227214807779502), it translation process is [here] (https: //github.com/k8smeetup/k8s-official-translation/), I hope the email can be replied, what is the current participation rule, about this [confused] (https://github.com/kubernetes/website/pull/10657). thank you.

Unblocked by https://github.com/kubernetes/org/pull/192
@cody-clark 👋 Ready for approval when you are.
/hold cancel
/assign @cody-clark

@markthink

I hope the email can be replied, what is the current participation rule, about this confused

Did this reply help? Please let me know.

/approve

/approve

@zacharysarah OK，I will email the current translation process.


A couple of old links to DSHARP

README.md and testdata/satlib/README.md have the old bitbucket links to DSHARP.

Good catch! I've pushed a fix.


JupyerQ won't response to kernel

I have the problem getting response from JupyerQ.  It is running on Redhat Linux:
# conda list "embedpy|jupyterq|kdb|python"
# packages in environment at /bns/gfikdb/anaconda:
#
# Name                    Version                   Build  Channel
embedpy                   1.3.1            py35h14c3975_0    kx
ipython                   6.4.0                    py35_0
ipython_genutils          0.2.0            py35hc9e07d0_0
jupyterq                  1.1.3            py35h14c3975_0    kx
kdb                       3.6                  2018.10.23    kx
msgpack-python            0.5.6            py35h6bb024c_0
python                    3.5.5                hc3d631a_4
python-dateutil           2.7.3                    py35_0
python-graphviz           0.8.3                    py35_0

# q p.q
KDB+ 3.6 2018.11.09 Copyright (C) 1993-2018 Kx Systems
l64/ 2(2)core 193268MB root ###### ###### NONEXPIRE  ###### DEV HDB/RDB #52039

q)p)print('embedPy runs')
embedPy runs
q)

# jupyter console --kernel=qpk
Unrecognized message type history_request on channel sh
/bns/gfikdb/anaconda/lib/python3.5/site-packages/jupyter_console/ptshell.py:95: UserWarning: No lexer found for language 'q'. Treating as plain text.
  warn("No lexer found for language %r. Treating as plain text." % name)
Jupyter console 5.2.0

KDB+ v3.6 2018.11.09 kdb+ kernel for jupyter v 0.0.1

In [1]: til 1

and it stucks waiting forever when I ran til 1

Closing this issue. Feel free to reopen if the problem persists


feat: add automatic translation

The feature is currently hidden but this implements everything else necessary for automatic translation.

I found a more clever way to do this.


Feature/components

This moves the rendering components into their own files (for testing purposes for later) and greatly simplifies the single component.

Awesome!! How beautiful code style!!
In the portion of the multi-platform has learned a lesson
Thank you bear with my ugly code.  m(_ _)m


Add cloud specific tag suffix

Adding cloud specific tag suffixes for publishing images for non-public clouds

PR information

[X] The title of the PR is clear and informative.
[X] There are a small number of commits, each of which has an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[X] If applicable, the PR references the bug/issue that it fixes in the description.
[X] New Unit tests were added for the changes made and CI is passing.

Doesnt have to be part of this PR, but we will need similar change for V4 images as well.

Yes, will create another PR for v4.

update the test to include verification for this yml file as well - new test was added here - 66df854

@CooperLink said he is going to update the test next week

@cooperlink added a test to fill a test gap! @divyagandhisethi - please send a PR to updated the test to include verifying New yml file that is added in the PR

@balag0 - open a separate issue to include V4 images here

@balag0 - open a separate issue to include V4 images here

https://github.com/Azure/azure-functions-docker/issues/510


[Bug & Enhancement] Own user status

Describe the bug
If i have Radial status enabled, and i speak Radial Status block speak indicator.
My fix: (use at the end of file or paste in CustomCSS)
div.wrapper-1VLyxH:not([data-user-id]) > svg > rect{
    visibility: hidden; /* hide the status ring around your own avatar */
}

Screenshots

(No modification)

(like normal)
In VC, speak: (with mod)

in VC, speak, (no mod)

Infomation (please complete the following information):
Discord channel: Stable
OS: Linux
Mod: BetterDiscord
Discord language: PL

No definitive fix for this?

It's not ideal but try refresh (Ctr+R)

It's not ideal but try refresh (Ctr+R)

Doesn't do anything since the theme is broken


Proposal for adding support for passing arrays to variadic functions

@jrose-apple requested that I make a proposal for this request.
My original bug report can be found here: https://bugs.swift.org/browse/SR-128

Only reservation is that splat should reuse the same syntax as declaration of a variadic parameter: [1,2,3]... -- one precedent for this syntax that I know of is CoffeeScript.

Sure, I'm fine with this change, or with the use of a new attribute, @variadic, inside of the declaration of the function and the call to the function when passing an array.

This needs more discussion on the swift-evolution list first.


Missing 'Diode power'

Sorry for so many questions, but it seems to be a bug:
In Development branch, there is a attribute indicating 'Diode power' but the function related is missing.

Should be fairly easy, but I'll revisit this after refactoring.

Power has been added to the diode model.


Mingo EIP Changes (Again)

Hand merged the Mingo changes to support Micro800.
Also minor/patch version updates and some lint fixes.

Sorry, wrong repo - this PR can be deleted / ignored.


Add links to readme

Adds links to docs, discord, Xverse

now is ok?

Hey @JanKortes212, not quite sure what you mean, but the docs should look better now with the links


ContactUs Form Not Fully Visible, Footer is overlapping it

Steps to reproduce
1.Open http://www.mozpacers.org
2.Go to contact us form and this issue will be visible
This issue is due to a small problem in CSS of footer

Seems to be a chrome specific problem. Can you try in firefox and post the result?

@Slayslot I have found a fix to this bug, after the fix this problem seems to be resolved and site is looking perfectly okey in both Chrome And Mozilla Firefox.
Shall i send the pr for this fix

Test it thoroughly first and if you feel everything is good, push it with the PR you already have open.

#43 Fixed
Check #42 PR

Since this was terribly cluttering the site in mobile mode ( the submit button was hidden ), I've issued a fix for this. You shall do the AJAX loader part. Thanks :)

This bug is still confirmed on Chrome both in Desktop and Mobile.
@Slayslot Assigning this to you.

@vipinkhushu @CuriousLearner @yash14123 @ManrajGrover @h4xr Thoroughly check and close please.

I've checked this. Closing this. Thanks @Slayslot
Others, if you find issue, re-open this.


Add documentation for fair sharing

What type of PR is this?
/kind documentation
What this PR does / why we need it:
Make a concept page just for preemption and explain both classic preemption and fair sharing.
Which issue(s) this PR fixes:

Part of #1714
Special notes for your reviewer:
Preview of new page https://deploy-preview-2322--kubernetes-sigs-kueue.netlify.app/docs/concepts/preemption/#fair-sharing
Does this PR introduce a user-facing change?

NONE

/assign @cortespao

/assign @tenzen-y


Create jssandbox application worker docker image

The idea with this is to not have to rebuild the image whenever the javascript changes, but to instead link the files into the container as volumes. Example of the docker run command:
docker run -d --name jssandbox --link rabbitmq:rabbitmq --link redis:redis -e TRANSPORT_NAME=mytransport -v my-javascript-app.js:/app/app.js -v my-app-config.json:/app/config.json jssandbox

:+1:


When will Kafka 1.0.0 support will be released?

is kafka 1.0.1 supported in Spark?

Hi @BenFradet , Spark is still only supporting up until kafka-0.10.
From what I understand, this library (kafka-writer) is dependent on the 'spark-streaming-kafka-0-10' only for testing, to read the results from writing.
I have tried bumping the kafka version to 2.3.0 and the unit tests, after some small adjustments, seem to run fine.
Do you think that it is appropriate to increase the kafka version along with the scala version ?

I think so, definitely :+1:
I think the original concern was around aligning the kafka versions on the classpath when using this library together with spark-streaming-kafka-0-10.

done, closing


Feature/publishing exceptions documentation

Moving the documentation in the publishing section

@phatboyg any updates on this?


wishlist: lighting on sprig device needs another pass

it's VERY high contrast still.

@maxwofford Did you take a pass at this?

@leomcelroy @maxwofford Pinging this- is this something we're looking into?

I don't think this is active anymore. Can probably close as won't fix. I'm not 100% sure if this is referring to the contract on the device's screen or the editor's screen.

Closing it for now thanks!


Auto corrected by following Lint Ruby Style/PercentLiteralDelimiters

Auto corrected by following Lint Ruby Style/PercentLiteralDelimiters
Click here to configure it on awesomecode.io

Coverage remained the same at 80.156% when pulling 15c35e88e6b4038129d313f44010581935e40cd2 on awesomecode-lint-ruby-style-percentliteraldelimiters-48108 into 56112c1553662e475be05580a121e51cc264c283 on master.


FormBuilderDropdown reset button wrong color

The color of the reset button in FormBuilderDropdown is black.
In other widgets, the reset button looks like black54.
The color cannot be changed by InputDecoration.suffixIconColor.

Hi @tonypottera24
With reset button do you refer to resetIcon?

Hi @deandreamatias
yes... but I just noticed that it is called cleanIcon here...
and I cannot set it to null and provide my own icon by suffixIcon.

Yeah yeah, I misstype my sentence

@deandreamatias sorry that I'm not blaming you.
I'm just expect that FormBuilder ecosystem should use the same terms.


Price modifier

Updated ObjectsInformation.xnb to Object.xnb for Stardew Valley 1.6
Add a way for users to modify the price of their seeds for instances where seeds are gifted or are quest rewards

Too many changes to be considered


Permission system?

Just installed GitBucket, really like it so far and considering its use for primary Git hosting
One thing that makes me quite concerned is what looks like insufficient (as far as I can see) controls for managing permissions of user accounts. This is very important in a team environment where we may have short-term/temporary contract developers we are not yet ready to trust fully and have to manage carefully.
Specific concerns we see with non-Admin users -

They can always create repos (cluttering the system)
They can make their repos public (risking public exposure of code)
Disabling a user erases all their repos (which do not get restored when user is re-enabled)
User could self-erase their account (completely removing all record of their work)
User could erase their repos (to the same effect)
Removing and disabling users seems to do exactly same thing (losing repos)

Are there plans to address such issues in the near future, especially related to protection from data loss and unauthorized exposure of private repos?
EDIT: Here is GitLab permission system for comparison/reference (behind demo login)
http://demo.gitlabhq.com/help/permissions

+1

Merged with #1286


Beta release

Describe your changes
How best to test these changes
Issue ticket number and link

Codecov Report
Patch coverage has no change and project coverage change: -28.31 :warning:

Comparison is base (2012fe7) 58.89% compared to head (12fd6a1) 30.58%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff             @@
##             beta     #916       +/-   ##
===========================================
- Coverage   58.89%   30.58%   -28.31%
===========================================
  Files         180      180
  Lines       20565    20590       +25
===========================================
- Hits        12111     6297     -5814
- Misses       7452    13566     +6114
+ Partials     1002      727      -275

Impacted Files
Coverage Δ

api/server/v1/marshaler.go
21.18% <0.00%> (-16.21%)
:arrow_down:

server/services/v1/auth/gotrue.go
0.00% <0.00%> (ø)

lib/container/priority_queue.go
0.00% <0.00%> (-100.00%)
:arrow_down:

server/quota/namespace.go
0.00% <0.00%> (-98.37%)
:arrow_down:

server/search/sorted_hits.go
0.00% <0.00%> (-96.37%)
:arrow_down:

schema/lang/go.go
0.00% <0.00%> (-90.63%)
:arrow_down:

schema/lang/java.go
0.00% <0.00%> (-90.63%)
:arrow_down:

schema/lang/typescript.go
0.00% <0.00%> (-90.63%)
:arrow_down:

schema/inference.go
0.00% <0.00%> (-85.06%)
:arrow_down:

server/search/group.go
0.00% <0.00%> (-85.00%)
:arrow_down:

... and 117 more

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Add support for exposing agent ports

Proposed changes
This PR adds support for exposing agent ports in the deployments
Fixes
If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce? (A breaking change is a fix or feature that would cause existing functionality and APIs to not work as expected.)
Put an x in the box that applies

[ ] Non-breaking fix (non-breaking change which fixes an issue)
[ ] Breaking fix (breaking change which fixes an issue)
[ ] Non-breaking feature (non-breaking change which adds functionality)
[ ] Breaking feature (breaking change which adds functionality)
[ ] Refactor (non-breaking change which changes implementation)
[ ] Messy (mixture of the above - requires explanation!)

Checklist
Put an x in the boxes that apply.

[ ] I have read the CONTRIBUTING doc
[ ] I am making a pull request against the main branch (left side). Also you should start your branch off our main.
[ ] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have locally run services that could be impacted and they do not present failures derived from my changes

Im really not a fan of the extra flag for this.
Not sure if it would make sense to include it within the service level.


image meta data missing in inspect

When pulling an image from the fedora repository, there is a bunch of missing metadata according to inspect.  One question is if the metadata is present or missing or if podman just doesnt display it.  A good example image to test with is registry.fedoraproject.org/f26/httpd:latest.
Labels for example are missing.  Also, many ENV variables are also missing
            "Labels": {
                "Architecture": "x86_64",
                "BZComponent": "httpd",
                "Name": "f26/httpd",
                "Release": "2.f26container",
                "Version": "0",
                "architecture": "x86_64",
                "authoritative-source-url": "registry.example.com",
                "build-date": "2017-09-21T20:07:46.595262",
                "com.redhat.build-host": "osbs-node02.phx2.fedoraproject.org",
                "com.redhat.component": "httpd",
                "description": "Apache httpd 2.4 available as docker container, is a powerful, efficient, and extensible web server. Apache supports a variety of features, many implemented as compiled modules which extend the core functionality. These can range from server-side programming language support to authentication schemes. Virtual hosting allows one Apache installation to serve many different Web sites.",
                "distribution-scope": "private",
                "help": "help.1",
                "io.k8s.description": "Platform for running Apache httpd 2.4 or building httpd-based application",
                "io.k8s.display-name": "Apache httpd 2.4",
                "io.openshift.expose-services": "8080:http,8443:https",
                "io.openshift.s2i.scripts-url": "image:///usr/libexec/s2i",
                "io.openshift.tags": "builder,httpd,httpd24",
                "io.s2i.scripts-url": "image:///usr/libexec/s2i",
                "license": "MIT",
                "name": "f26/httpd",
                "release": "2.f26container",
                "summary": "Platform for running Apache httpd 2.4 or building httpd-based application",
                "usage": "docker run -d --name httpd -p 8080:8080 -v /wwwdata:/var/www:Z 26/httpd",
                "vcs-ref": "0f643ef80c30071b17c6c3c86fb4a5e98d5f07db",
                "vcs-type": "git",
                "vendor": "Fedora Project",
                "version": "0"
            }

Data seems to be there now.  I have opened a new issue on missing data and fields being different then docker inspect.  https://github.com/projectatomic/libpod/issues/305


console.warns in tests cases

`PASS src/Slices/ServiceInventory/UI/Tabs/ConfigTab.test.tsx (5.374 s)
● Console
console.warn

  Selectable only cards should not contain any other actions. If you wish to include additional actions, use a clickable and selectable card.

  at node_modules/@patternfly/react-core/src/components/Card/CardHeader.tsx:102:17

  at updateContextConsumer (node_modules/react-dom/cjs/react-dom.development.js:21207:19)

  at beginWork (node_modules/react-dom/cjs/react-dom.development.js:21652:14)

  at beginWork$1 (node_modules/react-dom/cjs/react-dom.development.js:27426:14)

  at performUnitOfWork (node_modules/react-dom/cjs/react-dom.development.js:26560:12)

  at workLoopSync (node_modules/react-dom/cjs/react-dom.development.js:26466:5)

  at renderRootSync (node_modules/react-dom/cjs/react-dom.development.js:26434:7)

  at performSyncWorkOnRoot (node_modules/react-dom/cjs/react-dom.development.js:26085:20)

  at flushSyncCallbacks (node_modules/react-dom/cjs/react-dom.development.js:12042:22)

  at node_modules/react-dom/cjs/react-dom.development.js:25651:13

  at invokeTheCallbackFunction (node_modules/jsdom/lib/jsdom/living/generated/Function.js:19:26)

  at node_modules/jsdom/lib/jsdom/browser/Window.js:554:9

console.warn

  Selectable only cards should not contain any other actions. If you wish to include additional actions, use a clickable and selectable card.

  at node_modules/@patternfly/react-core/src/components/Card/CardHeader.tsx:102:17

  at updateContextConsumer (node_modules/react-dom/cjs/react-dom.development.js:21207:19)

  at beginWork (node_modules/react-dom/cjs/react-dom.development.js:21652:14)

  at beginWork$1 (node_modules/react-dom/cjs/react-dom.development.js:27426:14)

  at performUnitOfWork (node_modules/react-dom/cjs/react-dom.development.js:26560:12)

  at workLoopSync (node_modules/react-dom/cjs/react-dom.development.js:26466:5)

  at renderRootSync (node_modules/react-dom/cjs/react-dom.development.js:26434:7)

  at performSyncWorkOnRoot (node_modules/react-dom/cjs/react-dom.development.js:26085:20)

  at flushSyncCallbacks (node_modules/react-dom/cjs/react-dom.development.js:12042:22)

  at flushActQueue (node_modules/react/cjs/react.development.js:2667:24)

  at recursivelyFlushAsyncActWork (node_modules/react/cjs/react.development.js:2633:9)

  at node_modules/react/cjs/react.development.js:2545:15

console.warn

  Selectable only cards should not contain any other actions. If you wish to include additional actions, use a clickable and selectable card.

  at node_modules/@patternfly/react-core/src/components/Card/CardHeader.tsx:102:17

  at updateContextConsumer (node_modules/react-dom/cjs/react-dom.development.js:21207:19)

  at beginWork (node_modules/react-dom/cjs/react-dom.development.js:21652:14)

  at beginWork$1 (node_modules/react-dom/cjs/react-dom.development.js:27426:14)

  at performUnitOfWork (node_modules/react-dom/cjs/react-dom.development.js:26560:12)

  at workLoopSync (node_modules/react-dom/cjs/react-dom.development.js:26466:5)

  at renderRootSync (node_modules/react-dom/cjs/react-dom.development.js:26434:7)

  at performSyncWorkOnRoot (node_modules/react-dom/cjs/react-dom.development.js:26085:20)

  at flushSyncCallbacks (node_modules/react-dom/cjs/react-dom.development.js:12042:22)

  at node_modules/react-dom/cjs/react-dom.development.js:25651:13

  at invokeTheCallbackFunction (node_modules/jsdom/lib/jsdom/living/generated/Function.js:19:26)

  at node_modules/jsdom/lib/jsdom/browser/Window.js:554:9

console.warn

  Selectable only cards should not contain any other actions. If you wish to include additional actions, use a clickable and selectable card.

  at node_modules/@patternfly/react-core/src/components/Card/CardHeader.tsx:102:17

  at updateContextConsumer (node_modules/react-dom/cjs/react-dom.development.js:21207:19)

  at beginWork (node_modules/react-dom/cjs/react-dom.development.js:21652:14)

  at beginWork$1 (node_modules/react-dom/cjs/react-dom.development.js:27426:14)

  at performUnitOfWork (node_modules/react-dom/cjs/react-dom.development.js:26560:12)

  at workLoopSync (node_modules/react-dom/cjs/react-dom.development.js:26466:5)

  at renderRootSync (node_modules/react-dom/cjs/react-dom.development.js:26434:7)

  at performSyncWorkOnRoot (node_modules/react-dom/cjs/react-dom.development.js:26085:20)

  at flushSyncCallbacks (node_modules/react-dom/cjs/react-dom.development.js:12042:22)

  at flushActQueue (node_modules/react/cjs/react.development.js:2667:24)

  at recursivelyFlushAsyncActWork (node_modules/react/cjs/react.development.js:2633:9)

  at node_modules/react/cjs/react.development.js:2545:15

console.warn

  Selectable only cards should not contain any other actions. If you wish to include additional actions, use a clickable and selectable card.

  at node_modules/@patternfly/react-core/src/components/Card/CardHeader.tsx:102:17

  at updateContextConsumer (node_modules/react-dom/cjs/react-dom.development.js:21207:19)

  at beginWork (node_modules/react-dom/cjs/react-dom.development.js:21652:14)

  at beginWork$1 (node_modules/react-dom/cjs/react-dom.development.js:27426:14)

  at performUnitOfWork (node_modules/react-dom/cjs/react-dom.development.js:26560:12)

  at workLoopSync (node_modules/react-dom/cjs/react-dom.development.js:26466:5)

  at renderRootSync (node_modules/react-dom/cjs/react-dom.development.js:26434:7)

  at performSyncWorkOnRoot (node_modules/react-dom/cjs/react-dom.development.js:26085:20)

  at flushSyncCallbacks (node_modules/react-dom/cjs/react-dom.development.js:12042:22)

  at node_modules/react-dom/cjs/react-dom.development.js:25651:13

  at invokeTheCallbackFunction (node_modules/jsdom/lib/jsdom/living/generated/Function.js:19:26)

  at node_modules/jsdom/lib/jsdom/browser/Window.js:554:9

`
`
PASS src/Slices/Diagnose/UI/Diagnose.test.tsx (5.339 s)
● Console
console.warn

  Selectable only cards should not contain any other actions. If you wish to include additional actions, use a clickable and selectable card.

  at node_modules/@patternfly/react-core/src/components/Card/CardHeader.tsx:102:17

  at updateContextConsumer (node_modules/react-dom/cjs/react-dom.development.js:21207:19)

  at beginWork (node_modules/react-dom/cjs/react-dom.development.js:21652:14)

  at beginWork$1 (node_modules/react-dom/cjs/react-dom.development.js:27426:14)

  at performUnitOfWork (node_modules/react-dom/cjs/react-dom.development.js:26560:12)

  at workLoopSync (node_modules/react-dom/cjs/react-dom.development.js:26466:5)

  at renderRootSync (node_modules/react-dom/cjs/react-dom.development.js:26434:7)

  at performSyncWorkOnRoot (node_modules/react-dom/cjs/react-dom.development.js:26085:20)

  at flushSyncCallbacks (node_modules/react-dom/cjs/react-dom.development.js:12042:22)

  at node_modules/react-dom/cjs/react-dom.development.js:25651:13

  at invokeTheCallbackFunction (node_modules/jsdom/lib/jsdom/living/generated/Function.js:19:26)

  at node_modules/jsdom/lib/jsdom/browser/Window.js:554:9

console.warn

  Selectable only cards should not contain any other actions. If you wish to include additional actions, use a clickable and selectable card.

  at node_modules/@patternfly/react-core/src/components/Card/CardHeader.tsx:102:17

  at updateContextConsumer (node_modules/react-dom/cjs/react-dom.development.js:21207:19)

  at beginWork (node_modules/react-dom/cjs/react-dom.development.js:21652:14)

  at beginWork$1 (node_modules/react-dom/cjs/react-dom.development.js:27426:14)

  at performUnitOfWork (node_modules/react-dom/cjs/react-dom.development.js:26560:12)

  at workLoopSync (node_modules/react-dom/cjs/react-dom.development.js:26466:5)

  at renderRootSync (node_modules/react-dom/cjs/react-dom.development.js:26434:7)

  at performSyncWorkOnRoot (node_modules/react-dom/cjs/react-dom.development.js:26085:20)

  at flushSyncCallbacks (node_modules/react-dom/cjs/react-dom.development.js:12042:22)

  at node_modules/react-dom/cjs/react-dom.development.js:25651:13

  at invokeTheCallbackFunction (node_modules/jsdom/lib/jsdom/living/generated/Function.js:19:26)

  at node_modules/jsdom/lib/jsdom/browser/Window.js:554:9

`
`
PASS src/Slices/ServiceInventory/UI/Tabs/ConfigDetails.test.tsx (5.09 s)
● Console
console.warn

  Selectable only cards should not contain any other actions. If you wish to include additional actions, use a clickable and selectable card.

  69 |     });

  70 |   });

> 71 |   rerender(component({ enabled: true }));

     |   ^

  72 |   expect(

  73 |     await screen.findByRole("checkbox", { name: "enabled-True" }),

  74 |   ).toBeDisabled();

  at node_modules/@patternfly/react-core/src/components/Card/CardHeader.tsx:102:17

  at updateContextConsumer (node_modules/react-dom/cjs/react-dom.development.js:21207:19)

  at beginWork (node_modules/react-dom/cjs/react-dom.development.js:21652:14)

  at beginWork$1 (node_modules/react-dom/cjs/react-dom.development.js:27426:14)

  at performUnitOfWork (node_modules/react-dom/cjs/react-dom.development.js:26560:12)

  at workLoopSync (node_modules/react-dom/cjs/react-dom.development.js:26466:5)

  at renderRootSync (node_modules/react-dom/cjs/react-dom.development.js:26434:7)

  at performConcurrentWorkOnRoot (node_modules/react-dom/cjs/react-dom.development.js:25738:74)

  at flushActQueue (node_modules/react/cjs/react.development.js:2667:24)

  at act (node_modules/react/cjs/react.development.js:2582:11)

  at node_modules/@testing-library/react/dist/act-compat.js:63:25

  at renderRoot (node_modules/@testing-library/react/dist/pure.js:159:26)

  at rerender (node_modules/@testing-library/react/dist/pure.js:178:7)

  at Object.<anonymous> (src/Slices/ServiceInventory/UI/Tabs/ConfigDetails.test.tsx:71:3)

`

No console warns are remaining now that the upgrade to PF5 has been stabilized.


chore: pull latest commit from release-0.4 branch

What type of PR is this?

Uncomment only one  /kind line, and delete the rest.
For example, > /kind bug would simply become: /kind bug

/kind bug
/kind cleanup
/kind failing-test
/kind enhancement
/kind documentation
/kind code-refactoring

What does this PR do / why we need it:
pull latest commit from release-0.4 branch of argocd-operator
Have you updated the necessary documentation?

[ ] Documentation update is required by this PR.
[ ] Documentation has been updated.

Which issue(s) this PR fixes:
Fixes #?
Test acceptance criteria:

[ ] Unit Test
[ ] E2E Test

How to test changes / Special notes to the reviewer:

/approved

/lgtm

/approve


Docker support

Added simple dockerfile and manual line

I think this should be moved to dist/

moved

@hufrea Any progress?

Guys, did you have any issues running the app inside docker? I tried to do it on mac os using Docker Desktop for Mac with the following dockerfile:
FROM alpine:latest

ARG version=v0.14.1
ARG filename=byedpi-14.1-x86_64.tar.gz

WORKDIR /app

RUN \
    wget https://github.com/hufrea/byedpi/releases/download/${version}/${filename} \
    && tar xzf ${filename}

EXPOSE 1080

CMD ["./ciadpi-x86_64", "--oob", "3"]

and when I built it and ran it (docker run --rm  -P -p <IP_ADDRESS>:1080:1080 byedpi:latest) I got the following error in Firefox:
Secure Connection Failed

An error occurred during a connection to www.google.com. Peer received an SSL record that was longer than is permitted.

Error code: SSL_ERROR_RECORD_OVERFLOW_ALERT

This option works perfect for byedpi directly running on mac os (I built it natively) but it does not work inside docker for mac. I think it can be related to docker network layer (I guess it somehow fragments tcp packets or so) but I have no proofs. Other options like --fake did not cause this error but youtube did not work with them on my ISP.
If I'm right and docker network layer (at least for bridge network) is reason for this error then there are some limitations for dockerizing the app.

any issues

use issues instead, dont mix -P and -p options.

dont mix -P and -p options.

It happens in any case so looks like it does not matter for docker.

use issues instead

I'll recheck it after the PR is merged and then will create an issue.


Subqueries run much slower for simple SELECT statement

Please reopen #9122 as this is still a hurting issue in v1.7.9. The described workaround can't be applied for all use-cases.
The issue is very easy to reproduce and I wonder how this got 'stale'.

@trollvottel Sorry about that and thanks for the comment. I've reopened the referenced issue.


test(space): Update this space component unit test.

Checklist

[ ] Fix linting errors
[x] Tests have been added / updated (or snapshots)

Change information
close #502

Codecov Report

Merging #503 (feb5bc7) into dev (a7a9d18) will decrease coverage by 0.21%.
The diff coverage is n/a.

:exclamation: Current head feb5bc7 differs from pull request most recent head 358748a. Consider uploading reports for the commit 358748a to get more accurate results

@@            Coverage Diff             @@
##              dev     #503      +/-   ##
==========================================
- Coverage   96.40%   96.19%   -0.22%
==========================================
  Files         217      217
  Lines        5151     5151
  Branches      945      945
==========================================
- Hits         4966     4955      -11
- Misses        185      196      +11

Impacted Files
Coverage Δ

packages/varlet-ui/src/space/Space.tsx
79.59% <0.00%> (-16.33%)
:arrow_down:

packages/varlet-ui/src/utils/elements.ts
94.33% <0.00%> (-2.84%)
:arrow_down:

Continue to review full report at Codecov.

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


Unable to start a node with gs_startnode MacOS

Just installed GridDb, already configured and everything worked fine except for an error:
checking whether FALLOC_FL_PUNCH_HOLE is declared... no
configure: error: fallocate and FALLOC_FL_PUNCH_HOLE must be supported

Which I skipped through, I was able to add user and actually even change the admin password with gs_adduser and gs_passwd but upon running gs_startnode, I get the error below and thus unable to proceed.
Traceback (most recent call last):
  File "/Users/jjoek/griddb/bin/gs_startnode", line 122, in <module>
    proc = subprocess.Popen(command, stdout=f, stderr=f)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/subprocess.py", line 394, in __init__
    errread, errwrite)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/subprocess.py", line 1047, in _execute_child
    raise child_exception
OSError: [Errno 2] No such file or directory

I am on a macos,
running python 2.7 but also have python3 installed.
Asked the question on stackoverflow here https://stackoverflow.com/questions/70299642/unable-to-start-a-node-with-gs-startnode-macos

Thank you for question.
Unfortunately GridDB Server doesn’t support MacOS as of now.
Currently the following linux distributions are supported (CentOS, Ubuntu, openSUSE).
Could you please use GridDB C Client library with GridDB Server on Linux ?


NotImplementedError: change_ordering for Slice is not implemented

Hello. I was using pytorch2keras, and I asked for this error on https://github.com/nerox8664/pytorch2keras/issues/122#issuecomment-755438313
They told me this may be from onnx2keras.
Can someone help me to fix it?

I also meet this issue. Could somebody help?

Hi @AzazelHD, @rbli-john: were you guys able to solve this issue? If yes, please let me know the solution.
best, Vivek


Problem on @required Annotation on non-nullable input (Null Safety)

Hi I just migrated my project to null safety last week I faced following condition which seems weird for me, if I use @required annotation in a non-nullable input, it will causes error when I not giving the default value input. I think this is quiet inconvenient.

In my humble opinion, I think following solution might works.
void function1({@required int input}) {}
main(){
function1(); // show error instead of alert, if not nullable required field not filled
}

This type of question is best suited for support forums like Discord, or StackOverflow. Anyway, you should use 'required' instead of '@required' as indicated by the linter


Plugins colliding with each other?

I just downloaded OpenIAB into a new project and attempted to make a build of the 'OpenIAB-demo' scene, but got the following errors:
Plugin 'OpenIAB_W8Plugin.dll' is used from several locations:
Assets/Plugins/WP8/OpenIAB_W8Plugin.dll would be copied to <PluginPath>/OpenIAB_W8Plugin.dll
Assets/Plugins/OpenIAB_W8Plugin.dll would be copied to <PluginPath>/OpenIAB_W8Plugin.dll
Please fix plugin settings and try again.

Plugins colliding with each other.

This is using the latest <IP_ADDRESS> release, with Unity 5.0.0f4, and set to the Windows Phone 8 target.

Oops, wrong issue page!


NPM package is imported twice from different sources

Hi, @JorgenVatle!
I found a subtle but quite critical issue. If some NPM package is imported in both the main app code and a Meteor package, it's imported from different sources. In the first case it's a file processed by Vite, while in the second case it's modules.js file generated by Meteor build system. This causes 2 problems:

2 versions of the same code are loaded on the client.
If an NPM package has some kind of internal state, the app and the package operate on different states.

I created a repo to illustrate the issue. Here we have a NPM package which has a random value as its internal state. Meteor package and the app code receive different values.

This appears to be the cause for incompatibility between Meteor's React packages and React processed by Vite.

This is also true for rdb:svelte-meteor-data. It has imports from svelte/internal - and that's how I discovered the issue.

Though I imagine we could set up a Vite plugin to point imports for these packages to the Meteor bundle instead of letting Vite compile them.

So the Vite plugin should:

Detect all imports from NPM packages inside Meteor packages.
If there is the same import in main code, point it to the Meteor bundle.
Is that correct?

Yeah, that's what I'm thinking would be the best approach to it.
Sorry for getting back to you so late on this.

In that case, it should be also taken into account that Meteor package can use Npm.depends() functionality. So the algorytm should be something like:
if (app and package use use the same NPM_package) {
    if (package has NPM_package in Npm.depends) {
        if (versions in NPM.depends and package.json are the same) {
             import from Meteor bundle
        }
        else { compile with Vite }
    }
    else { import from Meteor bundle }
}
else { compile with Vite }

Hello @JorgenVatle.
Do we understand correctly that this issue is not closed, since a solution has not yet been found?
We recently decided to test this - in the repo to illustrate we updated all dependencies to the latest versions, but this did not help.
Or maybe we need to make some settings that we may have missed?

Oh, hey, didn't spot your comment until now.
Resolving the issue was a little more complex than I had anticipated and would require a notable amount of refactoring if I recall correctly. Just haven't found the time to get started on that. Externalizing these packages with a custom Vite plugin has been the easiest way to deal with the issue so far. But that assumes that you know which packages are provided by Meteor of course. 😅
I'll have another crack at it later in the evening and get back to you if something comes up. 👍

I have a fix in the works now. 😄
Though, since we still need to rely on data made available to us from the Meteor bundle. These npm packages could potentially be outdated or only partially included in the client bundle if Meteor is to do any of tree-shaking. I haven't had the chance to verify whether this is the case, but I suspect it's unlikely.
Either way, just to be safe, we'll make it something you need to opt in to.
You'll be able to do this on a per-import basis. The syntax will be something like the following:
// No changes here.
// This will import from your node_modules like you would expect
import MyPackage from 'some-npm-package'

// If you have a Meteor package that already comes bundled with an npm package, the following
// syntax can be used to tell Vite to externalize this import request.
import MyPackage from 'meteor:some-npm-package';

This works on a per-import basis. So you can import from both places if you find a use case for it. Bearing in mind your client bundle will include both versions 👍

Bit on an update on this. It does indeed appear like Meteor is lazy-loading npm packages. In the final production bundle, it still might not be an issue as those imports should be picked up on. But in development, it's looking like we need to add explicit exports for each module you need into your Meteor client's mainModule.
With React, I'm not sure how sensitive it is to having multiple versions running. Like, if we pull in a library for React, and this library gets bundled by Vite and not Meteor, would React complain about that? Or a better way to put it, do React libraries ship with a version of React, or is that usually just a peer dependency?
If React libraries use their own versions of the React library, it's probably going to end up being a much better developer experience to simply publish a fork of the react-meteor-data package over npm instead of relying on the Atmosphere-published version. With this approach, we're probably also looking at a considerable improvement in production bundle times as well since Meteor will no longer be responsible for compiling your React dependencies.