Browser navigation buttons no longer work properly

Open a Notion homepage created with Fruition
Navigate to another sub-page
Click the browser back button
Result

Click the browser forward button
Result

yeah... same, nothing has worked so far.


[FEATURE]  Plan-and-execute Langchain Agent Implementation

Plan-and-execute Langchain Agent
Plan-and-execute agents accomplish an objective by first planning what to do, then executing the sub tasks, parallely. This idea is largely inspired by BabyAGI and then the "Plan-and-Solve" paper.
Additional context
https://github.com/langchain-ai/langchain/blob/master/cookbook/plan_and_execute_agent.ipynb

you can now create the plan and execute agent in the new sequential agentic workflow, there is an example - https://github.com/FlowiseAI/Flowise/releases/tag/flowise%402.0.0


Specify only the first few characters

It would be a nice feature if you could just specify the first few characters of the connection ID, similar to how Docker containers work with the first few characters, rather than needing to copy and paste the entire ID to use that :)

Depending on how you're connecting to your clients, this is already a feature.
If you are using the server console (e.g ssh -p 3232 your.rssh.server) you can use connect and then tab after the first few matching characters.
You can also use other aliases for a client rather than having to input the whole ID, I typically use the hostname, unless I've got multiple clients running on one machine.
E.g
ssh -J your.rssh.server:3232 username.hostname

As I believe this would be a simple change, I'll look into it. A good break from implementing tuntap :P

Sweet, I've added this to the unstable branch. Have a play around!


Add FAQ and TOS

The FAQ(Frequently Asked Questions) and TOS(Terms of Services) have been added.
Entry to pages
For now, the links to these pages are put on the footer. A text hyperlink and button-like link for FAQ; text hyperlink for TOS.
TBD

[ ] The content of TOS
[ ] The content of FAQ (which I already put some examples)

The pages are created, I will add the content later.
Some screenshots below.

The pages are created, I will add the content later.
Some screenshots below.


[Bug] Conflict with Token Health mod

When used with Token Health, the checkboxes in the Dice Stat window are always empty, do not get filled when clicked off/on

Can you link to the module? I think I have the Token Health Module (Unless I have a different one) and I believe it works for me. try pressing f12 and view console. See if there is an error/ linking a photo of the error would be a great help.
Will investigate.
Photo example Issue #7

Here you are: https://github.com/schlosrat/token-health
foundry.js:727 Foundry VTT | Error thrown in hooked function '' for hook 'renderApplication'
#call @ foundry.js:727
callAll @ foundry.js:681
_render @ foundry.js:5153
await in _render (async)
_render @ foundry.js:5822
render @ foundry.js:5067
_handleButtonClick @ dice-stats-main.js:471
dispatch @ jquery.min.js:2
y.handle @ jquery.min.js:2
foundry.js:747 TypeError: Error thrown in hooked function '' for hook 'renderApplication'. Cannot read properties of undefined (reading 'contains')
[Detected 1 package: pf2e-dorako-ui]
at Object.fn (misc-hooks.js:107:25)
at #call (foundry.js:724:20)
at Hooks.callAll (foundry.js:681:17)
at PlayerStatusPage._render (foundry.js:5153:13)
at async PlayerStatusPage._render (foundry.js:5822:5)
onError @ foundry.js:747
🎁call_wrapped @ libWrapper-wrapper.js:507
🎁Hooks.onError#lib-wrapper @ listeners.js:138
🎁Hooks.onError#0 @ libWrapper-wrapper.js:187
#call @ foundry.js:728
callAll @ foundry.js:681
_render @ foundry.js:5153
await in _render (async)
_render @ foundry.js:5822
render @ foundry.js:5067
_handleButtonClick @ dice-stats-main.js:471
dispatch @ jquery.min.js:2
y.handle @ jquery.min.js:2
foundry.js:727 Foundry VTT | Error thrown in hooked function '' for hook 'renderApplication'
#call @ foundry.js:727
callAll @ foundry.js:681
_render @ foundry.js:5153
await in _render (async)
_render @ foundry.js:5822
render @ foundry.js:5067
_handleButtonClick @ dice-stats-main.js:471
dispatch @ jquery.min.js:2
y.handle @ jquery.min.js:2
foundry.js:747 TypeError: Error thrown in hooked function '' for hook 'renderApplication'. Cannot read properties of undefined (reading 'contains')
[Detected 1 package: pf2e-dorako-ui]
at Object.fn (dark-theme-hooks.js:35:24)
at #call (foundry.js:724:20)
at Hooks.callAll (foundry.js:681:17)
at PlayerStatusPage._render (foundry.js:5153:13)
at async PlayerStatusPage._render (foundry.js:5822:5)
onError @ foundry.js:747
🎁call_wrapped @ libWrapper-wrapper.js:507
🎁Hooks.onError#lib-wrapper @ listeners.js:138
🎁Hooks.onError#0 @ libWrapper-wrapper.js:187
#call @ foundry.js:728
callAll @ foundry.js:681
_render @ foundry.js:5153
await in _render (async)
_render @ foundry.js:5822
render @ foundry.js:5067
_handleButtonClick @ dice-stats-main.js:471
dispatch @ jquery.min.js:2
y.handle @ jquery.min.js:2
foundry.js:727 Foundry VTT | Error thrown in hooked function '' for hook 'renderApplication'
#call @ foundry.js:727
callAll @ foundry.js:681
_render @ foundry.js:5153
await in _render (async)
_render @ foundry.js:5822
render @ foundry.js:5067
_handleButtonClick @ dice-stats-main.js:471
dispatch @ jquery.min.js:2
y.handle @ jquery.min.js:2
foundry.js:747 TypeError: Error thrown in hooked function '' for hook 'renderApplication'. Cannot read properties of undefined (reading 'contains')
[Detected 1 package: pf2e-dorako-ui]
at Object.fn (base-theme-hooks.js:87:24)
at #call (foundry.js:724:20)
at Hooks.callAll (foundry.js:681:17)
at PlayerStatusPage._render (foundry.js:5153:13)
at async PlayerStatusPage._render (foundry.js:5822:5)
onError @ foundry.js:747
🎁call_wrapped @ libWrapper-wrapper.js:507
🎁Hooks.onError#lib-wrapper @ listeners.js:138
🎁Hooks.onError#0 @ libWrapper-wrapper.js:187
#call @ foundry.js:728
callAll @ foundry.js:681
_render @ foundry.js:5153
await in _render (async)
_render @ foundry.js:5822
render @ foundry.js:5067
_handleButtonClick @ dice-stats-main.js:471
dispatch @ jquery.min.js:2
y.handle @ jquery.min.js:2
foundry.js:727 Foundry VTT | Error thrown in hooked function '' for hook 'renderApplication'
#call @ foundry.js:727
callAll @ foundry.js:681
_render @ foundry.js:5153
await in _render (async)
_render @ foundry.js:5822
render @ foundry.js:5067
_handleButtonClick @ dice-stats-main.js:471
dispatch @ jquery.min.js:2
y.handle @ jquery.min.js:2
foundry.js:747 TypeError: Error thrown in hooked function '' for hook 'renderApplication'. Cannot read properties of undefined (reading 'contains')
[Detected 1 package: pf2e-dorako-ui]
at Object.fn (base-theme-hooks.js:129:23)
at #call (foundry.js:724:20)
at Hooks.callAll (foundry.js:681:17)
at PlayerStatusPage._render (foundry.js:5153:13)
at async PlayerStatusPage._render (foundry.js:5822:5)

Thanks for the extra info.
Very strange issue but seems like its a problem with token health itself.
I Made a blank form with just checkboxes and no other info and it was messed up for them to.
Somereason their mod is messing with checkbox input types or something

Found the issue. Will be fixed in next release


[Operator] Optimize CrossEntropyLoss

reimplement cross_entropy_loss forward and backward
support indices/probabilities/weight/reduction/ignore_index/label_smoothing
perform better than torch eager on large scale tensors

LG. Are you going to add label smoothing later?

Fisinehd


Provisioning of AWS host as exclusive, shared, or any, ++

When provisioning a host, specify whether to provision the host exclusive to
the application, or require a shared host, or if any will do.
Set the exclusiveTo on the host in the node repo.

Merged in #15086


my telegram link

hi I have this message from phisfort
that my Telegram link is blacklisted... the channel or group has 2 users on it
can you please remove the blacklist please? thanks

https://t.me/bancambios


Unbreak failing tests

The razor engine had a feature that had built in default usings for
System and System.Threading.Tasks. We're removing that API. You can
either define your own global usings and other directives like I did
in this workaround, or just add the necessary namespaces where they are
used.
I also fixed the console output for tests. I'm not sure if was
intentionally not working, but this makes the tests much easier to
diagnose.

FYI @prafullbhosale


chore: dev-tools 1.16 update kustomize, terragrunt, tflint, remove terraform-validator

Please hold off on release this. I have a change in the CLI that I'd like to push in here. Thanks.


When creating cluster Node Template is no longer auto-selected for you when have more than 1 template

Version: v2.1.8
Version: Master 2.2 (2/19/19)
What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):

Create a cluster and node template.
Create another node template.

Result:
The Node Template is no longer picked for us when have 2 or more. This was working earlier today.

Other details that may be helpful:
For my testing I was using EC2. I also tried clearing my browser cache and still observe the issue.

@tfiduccia can you let me know if this works in 2.1.8 and it regressed in v2.2.1?

@deniseschannon Tani checked and exists in v2.1.8; updated issue to mention this version as well

@deniseschannon @davidnuzik I don't think this change makes sense. I'm not sure why it was auto picked for David the first time but I speculate that as mentioned it could have been a caching issue or perhaps the new node template was created in a different tab or window.
Regardless, when the user has two node templates to choose from it would be incorrect to select one for them. Logically, when only a single node template exists for a given cloud provider it would be safe to assume the user wants this node template selected because they have no other templates available and they know the cost of that template on the cloud provider and the options.  Conversely, when more than one is available the same assumption can not be made. For example, the cost for standard droplets doubles every step up. If the user has one 2gb template named smallish-do and a 32gb template named largish-do the cost difference is massive and the name gives no indication of the actual size. Making the user choose is an explicit action and implies the user knows the options of that template. If anything we should change it so the node template selection never auto selects. The first assumption could still cost an organization extra money if the user wasn't paying attention and they thought they'd already added a small node template but only had a single large template available.
I think those arguments are extreme but in cases where we select options for hosted k8s providers we choose the smallest resource that will work for Rancher in an effort to avoid issues like this so, IMO, it follows we'd apply the same logic here.

Agree with Wes's analysis. I dont think we need to auto-select here. We are very likely to make the wrong choice on behalf of the user. Feel free to reopen and comment if you still feel strongly @davidnuzik

Thanks, yes it's a valid point and I agree with Wes as well.


Validity of link latency parameters

Hello, I have question about the link latency value used in one of your tutorials (Exercise 3: Comparing Systems)
There, 500ns was used for link latency of nvlink in DGX-2.
Is this a valid number? If so can you share some reference?
Thanks.

Hi @sylee0124 ,
NVLink latency parameters are confidential and not public. Our estimation of NVLink latency is based form some measurements that are also reported in this paper:
https://ieeexplore.ieee.org/abstract/document/9188288
However, I can refer you to this paper that did some studies on Nvlink latencies (page 3):
https://arxiv.org/abs/2111.04867
This paper assumes 700 ns for NVLink (on NDv2 platform) step latency.

Thank you for your kind response @rashidi1saeed !!


Editor not scrollable when expanding many sections

I have the issue that I need to test lots of options in the editor and found it hard to reach all sections, due to it's fixed position and the inner iframe not forcing a scroll on overflow.
However, it is possible using flexbox (see my PR #26). Is this the right way to go?

h5p-cli core functionality has been rewritten. Closing this since it is no longer relevant.


How to get alert as a mail when opensearch cluster is not green status

Hi Team,
How can we get OpenSearch cluster monitor with cluster status as  alert with email.
What are the required changes from our end, we want to implement this in production cluster.
Please take a high priority this and do ASAP help us to get it success.
Thanks
Anil

@prudhvigodithi , can you please look into the issue, Thanks

Hey @ganilmca you can leverage OpenSearch alerting plugin to set up the alerts once the cluster is up and running with helm charts.
https://opster.com/guides/opensearch/opensearch-basics/how-to-set-up-alerting-in-opensearch/
Thank you
@getsaurabh02


Update typescript to 3.7

For #8395
Because I cannot wait to use optional chaining.

Codecov Report

Merging #8396 into master will decrease coverage by 0.73%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##           master    #8396      +/-   ##
==========================================
- Coverage   59.37%   58.63%   -0.74%
==========================================
  Files         509      509
  Lines       23299    22929     -370
  Branches     3763     3758       -5
==========================================
- Hits        13833    13445     -388
- Misses       8567     8576       +9
- Partials      899      908       +9

Impacted Files
Coverage Δ

...preter/locators/services/windowsRegistryService.ts
91.02% <0%> (ø)
:arrow_up:

src/client/datascience/jupyter/notebookStarter.ts
65.65% <100%> (ø)
:arrow_up:

...rpreter/locators/services/baseVirtualEnvService.ts
34.09% <100%> (ø)
:arrow_up:

...nt/datascience/jupyter/invalidNotebookFileError.ts
0% <0%> (-75%)
:arrow_down:

.../client/datascience/jupyter/jupyterConnectError.ts
0% <0%> (-66.67%)
:arrow_down:

...science/jupyter/jupyterKernelPromiseFailedError.ts
0% <0%> (-50%)
:arrow_down:

...ent/datascience/jupyter/jupyterWaitForIdleError.ts
0% <0%> (-50%)
:arrow_down:

...cience/jupyter/jupyterDebuggerNotInstalledError.ts
50% <0%> (-30%)
:arrow_down:

src/client/common/utils/platform.ts
64.7% <0%> (-23.53%)
:arrow_down:

src/client/language/characters.ts
12% <0%> (-21.34%)
:arrow_down:

... and 39 more

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 9db47aa...7c35136. Read the comment docs.


Please update IDC web apps

@wlongabaugh please use this tag to build the viewer for IDC: idc-ohif-2020-08-28

Done


refactor(starknet_sequencer_node): rename component execution config

Stack:

#2548
#2547
#2546 ⬅
#2545
#2544

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

This change is

✓ Commit merged in pull request #2547


MP+: utilize ReadWriteMany volumes for repository cache

Description
So far, we've been using only block storage (AWS EBS), which can't be accessed in ReadWriteMany mode.
Because of that, we need to have one repository cache for each worker - see #210
On MP+ we can also use AWS EFS file storage (basically NFS - network file system) which can be accessed in ReadWriteMany mode.
Hence, after we have both, stg & prod on MP+, we can consolidate all the RWO worker volumes (1+1 per long-running worker) we use for the repository cache into one(?) RWX.
And we can change workers from StatefulSet to Deployment at the same time, I guess.
Benefit
The long-running workers will use significantly less disk space (1 volume instead of 4 for 2 l-r workers)
Importance
gain/low, impact/low
Workaround

[x] There is an existing workaround that can be used until this feature is implemented.

Participation

[X] I am willing to submit a pull request for this issue. (Packit team is happy to help!)

Still relevant.


suggestion:biome discover

Have the ability to use a discovery of a particular biome as a goal.

ok. sorry bout delay. testing now.

task not showing up.
this is the json
{
    "id": 5,
    "title": "Fourth Test Quest",
    "level": 0,
    "type": "explore",
    "profession": "cartographer",
    "task": [
        "travel",
        "skylore:ak_nights"
    ],
    "description": "This is a test description for the first quest",
    "experience": 10,
    "reward": [
        "minecraft:stick",
        10,
        "minecraft:bucket",
        1
    ]
}

Like this:
    "task": [
        "explore",
        "minecraft:plains",
        1
    ]

Released the new version


Not latest version of @react-native/metro-config is published

npm outdated

I would expect that 0.74.0 is the latest and not last published 0.73.2

(Transferred to facebook/react-native because this is an RN-monorepo package versioned and released with RN, not Metro)

Duplicates https://github.com/facebook/react-native/issues/41587


Vendor Neutral Modelica Annotation Prototypes in MSL

Reported by peter.fritzson on 1 Oct 2012 15:17 UTC
Regarding new annotations,
There should a neutral mechanism where vendor names do not appear in MSL. This can e.g. be used for new annotations in the prototype
stage, for prototype version of the annotations.
Proposal:
Introduce  something called AnnotationPrototype__AnnotationName
An annotation prototype can be introduced in MSL, provided that:

Name and Documentation about the annotation is registered at modelica.org somewhere (or the SVN). The purpose, motivation, implementation hints.

There should be a contact person for the Annotation Prototype proposal, and also a library officer who has done some preliminary checking of it.

As usual, annotations should not influence the simulation behavior, only tool appearance (graphical), and maybe performance.
There is a discussion if such annotation prototypes should be allowed in MSL, since the language and library standard need to become more stable in the future.
The annotation prototypes could be coupled to the innovation process. The question is whether they should be allowed in released versions of MSL or only in prototype versions of MSL?
Anyway, anotation prototypes is a step forward compared to the current situation when we have vendor specific annotations with vendor names in MSL.

Migrated-From: https://trac.modelica.org/Modelica/ticket/849

Comment by hansolsson on 1 Oct 2012 15:38 UTC
Adding my comments from mail so that the concrete proposals ideas are not lost:
Was also going to suggest something similar; but with __Prototype_…, __Proposed_… or __Experimental_… instead; so basically just viewing it as a vendor-specific annotation for the Prototype-vendor, e.g.:
  annotation(__Experimental_choicesAllMatching=true);

Alternatively starting with a lower-case letter.
As for registering I don’t see that we need a need new infrastructure. It should be a proposal (in some stage) for Modelica Language, so it should be on the trac – but it might help if we can tag them in some way.

Comment by choeger on 1 Oct 2012 17:42 UTC
Just for the sake of style: Is there a reason we cannot use the existing namespace technique (the conceptual representation as records) for those annotations?
e.g.
annotation(Experimental(choicesAllMatching = true ));

For later versions, I would really like to see all annotations defined as records (as for instance in Java). A compiler could thus check for valid use of annotations. The semantics would, of course, be defined as now, but could be reflected e.g. in comments of the defining record.
If interest in this exists, I could write a more formal proposal about this.

Comment by uckun on 2 Oct 2012 14:50 UTC
(discussion moved over from the Modelica-Design group)
Mike Tiller asked me to clarify my position on annotations. Here is my response.
In MSL, I am opposed to the use of any vendor-specific annotations (and I applaud the MA for taking a bold step to eliminate them from the MSL).  MSL should not contain references to specific products or language features that are not covered in the official language specification.
In the production version of MSL, I am also opposed to the use of vendor-neutral annotations. MSL is one of the core capabilities included in Modelica, and it needs to be as robust as possible in order for it to be used in engineering practice. The presumed purpose of prototype annotations is to introduce new features before such features are ratified by the MA. Even if we do not allow annotations that change language semantics, there are several risks in using unofficial annotations in the MSL. If users integrate MSL models with prototype annotations in their production code, what would happen if the prototype function is revised, removed, or renamed in the future?  What if the MA cannot agree on the implementation of a prototype and it lingers on as an unofficial language feature for several years?  What is the tool vendors' responsibility for supporting these annotations?  What is the process for preventing a large number of new half-baked annotations from flooding in?
In my opinion, the only safe use of annotations in the MSL is in "experimental" versions of the MSL.
Based on my brief experience in the Modelica community, the main issue appears to be a rather slow and arduous innovation process. To the best of my understanding, the use of annotations in the MSL is envisioned as a way for tool vendors and library providers to forge ahead with new ideas without having to wait for the MA to ratify them.  This is a dangerous pattern that limits the authority of the MA as the official forum for defining the Modelica language.
I believe that a safer, more robust approach is to improve the innovation process within the MA so that people won't have to go around the ratification bottleneck.

Comment by choeger on 2 Oct 2012 16:38 UTC
Replying to [comment:3 uckun]:

In my opinion, the only safe use of annotations in the MSL is in "experimental" versions of the MSL.

Did you consider all current use cases of annotations? In current Modelica, they serve a lot of different purposes: Documentation, graphical description, optimizations and execution information. They are all well founded IMO. The common principle I can see is, that you do not need an annotation to reason about the meaning of a model. This is IMO a little bit different from Java where e.g. the @Test annotation is crucial in a given context. Yet Modelica does a little bit more with annotations than e.g. Java: Java has a static void main() entry point where Modelica allows to use an annotation.

Comment by uckun on 23 Oct 2012 23:14 UTC
Christoph is correct.  Annotations (especially vendor-specific annotations) should not be used to modify language semantics.  This is a necessary (but not sufficient) requirement for interoperability between various tools. He is also correct that not all annotations have the potential to cause interoperability problems between tools and models, which is my primary concern.
Of the 12 annotation types listed in the language spec, here are the ones I have specific concerns about:

Annotations for the use of external functions: Perfectly reasonable in end-user models, but might cause compatibility issues if used in MSL.
Vendor-specific annotations.  The language spec is overly permissive about the use of such annotations.  To quote the 3.3 spec (page 213): "A Modelica tool is free to define and use other annotations [...]. A vendor may – anywhere inside an annotation – add specific, possibly undocumented, annotations which are not intended to be interpreted by other tools."  Essentially, this language allows a vendor to define annotations that perform specific functions that tools from other vendors may not be able to parse or replicate. Again, this might be OK in end-user models as long as the end user is committed to a particular tool for life, at their own risk (but not desirable from the perspective of an open language standard that promotes interoperability).  When such annotations leak out to the MSL (as is the case with the current MSL), they render affected MSL models unusable in other tools.

All other annotation types are benign with respect to their use in MSL models.
I will repeat the most important point from my earlier comment.  The use of vendor-specific annotations for "innovation", that is, to stay ahead of the official language specification, is a dangerous pattern that causes interoperability issues between tools and limits end-user choice.  It is also contrary to the spirit of an open language specification that is managed by the Modelica community.
At the next Design Meeting, I will propose some approaches to increasing the efficiency of the innovation process so that new features may be ratified quickly and incorporated into the language spec without having to circumvent the spec through vendor-specific annotations.

Comment by otter on 11 Dec 2015 11:35 UTC
Set the milestone do "undecided", because I do not understand what should be improved in MSL 3.2.2.
I like the idea of using an experimental Modelica annotation and maybe if it is necessary for some good reason we should introduce it. However, I do not see that this is the case for MSL 3.2.2


Question: Fetch network + chain

As a developer, how can I make sure that NeoLine's user account is currently at TestNet (network) and Neo3 (chain)?
How can I get the information that it's Neo3 instead of Neo2?

By testing the dev branch I could still not see the information coming whether it's Neo3 or Neo2.

@gsmachado Hi, the latest N3 dAPI is pushed into dev, and the N3 Beta docs link is: https://neoline.io/dapi/N3.html

Yes, the last version of dev branch brings this info -- which is essential to dApps. I'm closing this issue. 💪


Quic协议无法连接

你正在使用哪个版本的 V2Ray？（如果服务器和客户端使用了不同版本，请注明）
都是4.14.0 客户端用的V2rayN
你的使用场景是什么？比如使用 Chrome 通过 Socks/VMess 代理观看 YouTube 视频。
打开Google.com
你看到的不正常的现象是什么？（请描述具体现象，比如访问超时，TLS 证书错误等）

无法访问此网站 www.google.com 意外终止了连接。
请试试以下办法：

检查网络连接
检查代理服务器和防火墙
运行 Windows 网络诊断
ERR_CONNECTION_CLOSED

你期待看到的正确表现是怎样的？
打开google
请附上你的配置（提交 Issue 前请隐藏服务器端IP地址）。
服务器端配置:

{
  "inbounds": [
    {
      "port": 12306,
      "protocol": "vmess",
      "settings": {
        "clients": [
          {
            "id": "UUID",
            "level": 1,
            "alterId": 64
          }
        ]
      },
      "streamSettings": {
        "network": "kcp",
        "security": "tls",
        "tlsSettings": {
          "serverName": "the.right.domain",
          "allowInsecure": false,
          "alpn": [
            "http/1.1"
          ],
          "certificates": [
            {
              "certificateFile": "/etc/v2ray/v2ray.crt",
              "keyFile": "/etc/v2ray/v2ray.key"
            }
          ]
        },
        "kcpSettings": {
          "mtu": 1350,
          "tti": 20,
          "uplinkCapacity": 10,
          "downlinkCapacity": 100,
          "congestion": false,
          "readBufferSize": 1,
          "writeBufferSize": 1,
          "header": {
            "type": "utp"
          }
        }
      }
    },
    {
      "port": 443,
      "protocol": "vmess",
      "settings": {
        "clients": [
          {
            "id": "UUID",
            "level": 1,
            "alterId": 64
          }
        ]
      },
      "streamSettings": {
        "network": "quic",
        "security": "tls",
        "tlsSettings": {
          "serverName": "the.right.domain",
          "allowInsecure": false,
          "alpn": [
            "http/1.1"
          ],
          "certificates": [
            {
              "certificateFile": "/etc/v2ray/v2ray.crt",
              "keyFile": "/etc/v2ray/v2ray.key"
            }
          ]
        },
        "quicSettings": {
          "security": "none",
          "key": "",
          "header": {
            "type": "none"
          }
        }
      }
    }
  ],
  "outbounds": [
    {
      "protocol": "freedom",
      "settings": {}
    },
    {
      "protocol": "blackhole",
      "settings": {},
      "tag": "blocked"
    }
  ],
  "routing": {
    "rules": [
      {
        "type": "field",
        "ip": [
          "geoip:private"
        ],
        "outboundTag": "blocked"
      }
    ]
  }
}

客户端配置:
出错的配置：
{
  "log": {
    "access": "C:\\Temp\\v2ray\\_access.log",
    "error": "C:\\Temp\\v2ray\\_error.log",
    "loglevel": "warning"
  },
  "inbounds": [
    {
      "port": 1080,
      "protocol": "socks",
      "sniffing": {
        "enabled": true,
        "destOverride": ["http", "tls"]
      },
      "settings": {
        "auth": null
      }
    }
  ],
  "outbounds": [
    {
      "protocol": "vmess",
      "settings": {
        "vnext": [
          {
            "address": "the.right.domain",
            "port": 443,
            "users": [
              {
                "id": "UUID",
                "alterId": 64
              }
            ]
          }
        ]
      },
      "streamSettings": {
        "network": "quic",
        "security": "tls",
        "quicSettings": {
          "security": "none",
          "key": "",
          "header": {
            "type": "none"
          }
        }
      }
    }
  ]
}

作为对照的可以使用的mkcp,tls设置
{
  "log": {
    "access": "",
    "error": "",
    "loglevel": "warning"
  },
  "inbounds": [
    {
      "port": 1080,
      "listen": "<IP_ADDRESS>",
      "protocol": "socks",
      "sniffing": {
        "enabled": true,
        "destOverride": [
          "http",
          "tls"
        ]
      },
      "settings": {
        "auth": "noauth",
        "udp": true,
        "ip": null,
        "clients": null
      },
      "streamSettings": null
    }
  ],
  "outbounds": [
    {
      "tag": "proxy",
      "protocol": "vmess",
      "settings": {
        "vnext": [
          {
            "address": "the.right.domain",
            "port": 12306,
            "users": [
              {
                "id": "UUID",
                "alterId": 64,
                "email"<EMAIL_ADDRESS>                "security": "aes-128-gcm"
              }
            ]
          }
        ],
        "servers": null,
        "response": null
      },
      "streamSettings": {
        "network": "kcp",
        "security": "tls",
        "tlsSettings": null,
        "tcpSettings": null,
        "kcpSettings": {
          "mtu": 1350,
          "tti": 50,
          "uplinkCapacity": 12,
          "downlinkCapacity": 12,
          "congestion": false,
          "readBufferSize": 2,
          "writeBufferSize": 2,
          "header": {
            "type": "utp",
            "request": null,
            "response": null
          }
        },
        "wsSettings": null,
        "httpSettings": null
      },
      "mux": {
        "enabled": true
      }
    },
    {
      "tag": "direct",
      "protocol": "freedom",
      "settings": {
        "vnext": null,
        "servers": null,
        "response": null
      },
      "streamSettings": null,
      "mux": null
    },
    {
      "tag": "block",
      "protocol": "blackhole",
      "settings": {
        "vnext": null,
        "servers": null,
        "response": {
          "type": "http"
        }
      },
      "streamSettings": null,
      "mux": null
    }
  ],
  "dns": null,
  "routing": {
    "strategy": "rules",
    "settings": {
      "domainStrategy": "IPIfNonMatch",
      "rules": []
    }
  }
}

请附上出错时软件输出的错误日志。在 Linux 中，日志通常在 /var/log/v2ray/error.log 文件中。

服务器端错误日志:
2019/02/06 04:49:09 [Warning] v2ray.com/core: V2Ray 4.14.0 started

客户端错误日志:
2019/02/06 17:46:11 [Warning] v2ray.com/core: V2Ray 4.14.0 started
2019/02/06 17:46:13 [Warning] [901938644] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: failed to find an available destination > v2ray.com/core/common/retry: [missing port in address] > v2ray.com/core/common/retry: all retry attempts failed
2019/02/06 17:46:13 [Warning] [2858915964] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: failed to find an available destination > v2ray.com/core/common/retry: [missing port in address] > v2ray.com/core/common/retry: all retry attempts failed
2019/02/06 17:46:13 [Warning] [1554404465] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: failed to find an available destination > v2ray.com/core/common/retry: [missing port in address] > v2ray.com/core/common/retry: all retry attempts failed
2019/02/06 17:46:13 [Warning] [589984885] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: failed to find an available destination > v2ray.com/core/common/retry: [missing port in address] > v2ray.com/core/common/retry: all retry attempts failed
2019/02/06 17:46:15 [Warning] [1094986759] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: failed to find an available destination > v2ray.com/core/common/retry: [missing port in address] > v2ray.com/core/common/retry: all retry attempts failed
2019/02/06 17:46:15 [Warning] [1664075750] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: failed to find an available destination > v2ray.com/core/common/retry: [missing port in address] > v2ray.com/core/common/retry: all retry attempts failed
2019/02/06 17:46:17 [Warning] [349918465] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: failed to find an available destination > v2ray.com/core/common/retry: [missing port in address] > v2ray.com/core/common/retry: all retry attempts failed
2019/02/06 17:46:17 [Warning] [3781407420] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: failed to find an available destination > v2ray.com/core/common/retry: [missing port in address] > v2ray.com/core/common/retry: all retry attempts failed
2019/02/06 17:46:18 [Warning] [3834276080] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: failed to find an available destination > v2ray.com/core/common/retry: [missing port in address] > v2ray.com/core/common/retry: all retry attempts failed
2019/02/06 17:46:19 [Warning] [3739477303] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: failed to find an available destination > v2ray.com/core/common/retry: [missing port in address] > v2ray.com/core/common/retry: all retry attempts failed
2019/02/06 17:46:19 [Warning] [633264040] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: failed to find an available destination > v2ray.com/core/common/retry: [missing port in address] > v2ray.com/core/common/retry: all retry attempts failed
2019/02/06 17:46:19 [Warning] [2383844478] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: failed to find an available destination > v2ray.com/core/common/retry: [missing port in address] > v2ray.com/core/common/retry: all retry attempts failed
2019/02/06 17:46:19 [Warning] [3513065507] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: failed to find an available destination > v2ray.com/core/common/retry: [missing port in address] > v2ray.com/core/common/retry: all retry attempts failed
2019/02/06 17:46:22 [Warning] [4226517202] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: failed to find an available destination > v2ray.com/core/common/retry: [missing port in address] > v2ray.com/core/common/retry: all retry attempts failed

请附上访问日志。在 Linux 中，日志通常在 /var/log/v2ray/access.log 文件中。

没有生成该文件。

其它相关的配置文件（如 Nginx）和相关日志。

如果 V2Ray 无法启动，请附上 --test 输出。

通常的命令为 /usr/bin/v2ray/v2ray --test --config /etc/v2ray/config.json。请按实际情况修改。

如果 V2Ray 服务运行不正常，请附上 journal 日志。

通常的命令为 journalctl -u v2ray。
请预览一下你填的内容再提交。

客户端加入tlsSettings:{"serverName":"域名"}问题解决


Improve automatic configuration

Ideally in most cases, users of this library would not pass host/port or socket to the constructor, allowing configuration by environment variables and in their absence, selecting an appropriate default.
https://github.com/DataDog/dd-trace-rb/pull/1700 did something similar for dd-trace-rb, selecting a socket if the expected file exists.

This would need some tracking across libraries/languages.


[UI] Fix Visibility Filters in Configuration pages

Current Behavior

Desired Behavior

Screenshots/Logs

Environment

Browser: Chrome Safari Firefox
Host OS: Mac Linux Windows
Meshery Server Version: stable-v
Meshery Client Version: stable-v
Platform: Docker Kubernetes

Contributor Guides and Handbook

🎨 Wireframes and designs for Meshery UI in Figma (open invite)
🖥 Contributing to Meshery UI
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

hi, can you provide some insights over the issue. I want to contribute to it.


requirebin.com failing with gists with require('events')

I noticed that browserifying events crashes
eg wzrd.in/bundle/events
crashes with
---FLAGRANT SYSTEM ERROR---

(logs uuid: ddda41f0-d478-11e4-a264-e1b37a8145d7 )

Error: "spawn ENOENT"

code: ENOENT
errno: ENOENT
syscall: spawn
dirPath: /tmp/events115227-8665-1ywg3ra

This is probably an issue with the package, and not browserify-cdn itself.
If you feel differently, feel free to file a bug report at:

    https://github.com/jesusabdullah/browserify-cdn/issues

Include the ENTIRETY of the contents of this message, and he can
try to help you out.

Have a nice day!

I browserified events@latest with<EMAIL_ADDRESS>works locally?

I can recreate the issue locally using the latest cloned browserify-cdn.
However I haven't found the problem yet :(

I'm also experiencing this e.g. with assert
---FLAGRANT SYSTEM ERROR---

(logs uuid: 8e648ac0-dd30-11e4-b2d2-5176a443e15b )

Error: "spawn ENOENT"

code: ENOENT
errno: ENOENT
syscall: spawn
dirPath: /tmp/assert11537-32164-40gw1p

This is probably an issue with the package, and not browserify-cdn itself.
If you feel differently, feel free to file a bug report at:

    https://github.com/jfhbrook/browserify-cdn/issues

Include the ENTIRETY of the contents of this message, and the maintainer(s)
can try to help you out.

Have a nice day!


[zh] sync automated-tasks-with-cron-jobs.md

Sync with en. Some content is moved to the concept page that will be included in another PR.
content/zh-cn/docs/tasks/job/automated-tasks-with-cron-jobs.md

/approve


Initial commit for adding address line 2 to address verification

Integrated Address Line 2 and 3 into Address Verification

Thanks for submitting the PR!

If you resolve conflicts we can get this merged in.

Fixed conflicts


Enabling additional vulkan extension and adding further checks

Slowly working my way through fixing #69951

Testing this out locally now. Running with the profile provided by Sakrel we get the following output:
ERROR: Your GPU doesn't support image cube arrays.
   at: (drivers\vulkan\vulkan_context.cpp:1287)
ERROR: Condition "err != OK" is true. Returning: ERR_CANT_CREATE
   at: VulkanContext::_window_create (drivers\vulkan\vulkan_context.cpp:1631)
ERROR: Failed to create Vulkan Window.
   at: (platform\windows\display_server_windows.cpp:3638)
ERROR: Failed to create main window.
   at: (platform\windows\display_server_windows.cpp:3953)
Using "winink" pen tablet driver...

================================================================
CrashHandlerException: Program crashed
Engine version: Godot Engine v4.0.beta.custom_build (c513c0d39da954f448c740a5fdbad0da7d6f8adf)
Dumping the backtrace. Please include this when reporting the bug to the project developer.
[0] ???
[1] ???
[2] RendererCompositor::create (F:\dev\godot\servers\rendering\renderer_compositor.cpp:43)
[3] RenderingServerDefault::RenderingServerDefault (F:\dev\godot\servers\rendering\rendering_server_default.cpp:413)
[4] Main::setup2 (F:\dev\godot\main\main.cpp:2075)
[5] Main::setup (F:\dev\godot\main\main.cpp:1882)
[6] widechar_main (F:\dev\godot\platform\windows\godot_windows.cpp:164)
[7] _main (F:\dev\godot\platform\windows\godot_windows.cpp:203)
[8] main (F:\dev\godot\platform\windows\godot_windows.cpp:217)
[9] WinMain (F:\dev\godot\platform\windows\godot_windows.cpp:231)
[10] __scrt_common_main_seh (d:\a01\_work\6\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:288)
[11] <couldn't map PC to fn name>
-- END OF BACKTRACE --
================================================================

The initial error is good, but we should close the process safely instead of crashing. I'll enable for cubemap arrays and see what happens

The initial error is good, but we should close the process safely instead of crashing. I'll enable for cubemap arrays and see what happens

That worries me a little, that means any error result from _create_physical_device would lead to a crash. I'll see how easy it is to fix that.

Looks like the profile provided in the issue is missing a bunch of device features. The updated profile is here.
With the updated profile I get the following validation error when compiling the fsr shader:

VUID-VkShaderModuleCreateInfo-pCode-01091(ERROR / SPEC): msgNum: -1480880714 - Validation Error: [ VUID-VkShaderModuleCreateInfo-pCode-01091 ] Object 0: handle = 0x1ea7b058460, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0xa7bb8db6 | vkCreateShaderModule(): The SPIR-V Capability (Int16) was declared, but none of the requirements were met to use it. The Vulkan spec states: If pCode declares any of the capabilities listed in the SPIR-V Environment appendix, one of the corresponding requirements must be satisfied (https://vulkan.lunarg.com/doc/view/<IP_ADDRESS>/windows/1.3-extensions/vkspec.html#VUID-VkShaderModuleCreateInfo-pCode-01091)

I think to fix this validation error, this line must also check whether VkPhysicalDeviceFeatures::shaderInt16 is supported:
https://github.com/godotengine/godot/blob/1d14c054a12dacdc193b589e4afb0ef319ee2aae/servers/rendering/renderer_rd/effects/fsr.cpp#L45-L46
The MODE_FSR_UPSCALE_NORMAL define enables the A_HALF define which tells the fsr shader that both 16-bit integers and floats are supported.
https://github.com/godotengine/godot/blob/1d14c054a12dacdc193b589e4afb0ef319ee2aae/servers/rendering/renderer_rd/shaders/effects/fsr_upscale.glsl#L40-L44
https://github.com/godotengine/godot/blob/1d14c054a12dacdc193b589e4afb0ef319ee2aae/thirdparty/amd-fsr/ffx_a.h#L57

@sakrel, I've added it to the check for SUPPORTS_FSR_HALF_FLOAT itself, it actually already checked various related things.

Thanks!


Private information for devices

Ability to store information against a user's device that is only visible to the themselves, including:

Some kind of private name for the device
IP Address (probably last one it was seen from?) plus geoip-ed location if server supports it
Name of client
Type of device ('iPhone' / 'OnePlus 6' / 'Google Chrome' etc.)

anything else?

Dup of #1826


Crash when running with larger dataset

Hello,
I am having some trouble running umap with a large data-set (0.75m with 75 columns) on 0.4.1
After running around 10-15mins, the python session just crash.
I was able to run the exact same things on a slightly bigger data-set (2.5m with 75 columns) on 0.3.10.
Cheers,

That sounds troubling, but I can't say too much without a little more information. Presumably the whole thing is segfaulting somewhere inside numba's workload. Are you using any different metrics, or is this with the euclidean metric? There have been some reports of possible issues in mahalanobis and/or correlation.

I was using all the default parameter which is euclidean.
Here is the verbose output before it crash:
UMAP(a=None, angular_rp_forest=False, b=None,      force_approximation_algorithm=False, init='spectral', learning_rate=1.0,      local_connectivity=1.0, low_memory=False, metric='euclidean',      metric_kwds=None, min_dist=0.1, n_components=2, n_epochs=None,      n_neighbors=15, negative_sample_rate=5, output_metric='euclidean',      output_metric_kwds=None, random_state=None, repulsion_strength=1.0,      set_op_mix_ratio=1.0, spread=1.0, target_metric='categorical',      target_metric_kwds=None, target_n_neighbors=-1, target_weight=0.5,      transform_queue_size=4.0, transform_seed=42, unique=False, verbose=True) Construct fuzzy simplicial set Wed Apr 29 02:30:21 2020 Finding Nearest Neighbors Wed Apr 29 02:30:21 2020 Building RP forest with 48 trees Wed Apr 29 02:32:40 2020 NN descent for 20 iterations

Any chance you could try installing pynndescent and see if that makes any difference?

It works after pynndescent was installed (tested on 2.5m x 75).
Also much better performance as well.
0.3.10
CPU times: user 2h 24min 10s, sys: 49.7 s, total: 2h 25min
Wall time: 2h 22min 37s

0.4.1
CPU times: user 3h 29min 4s, sys: 1min 17s, total: 3h 30min 21s
Wall time: 21min 30s

UMAP(a=None, angular_rp_forest=False, b=None,
     force_approximation_algorithm=False, init='spectral', learning_rate=1.0,
     local_connectivity=1.0, low_memory=False, metric='euclidean',
     metric_kwds=None, min_dist=0.1, n_components=2, n_epochs=None,
     n_neighbors=15, negative_sample_rate=5, output_metric='euclidean',
     output_metric_kwds=None, random_state=None, repulsion_strength=1.0,
     set_op_mix_ratio=1.0, spread=1.0, target_metric='categorical',
     target_metric_kwds=None, target_n_neighbors=-1, target_weight=0.5,
     transform_queue_size=4.0, transform_seed=42, unique=False, verbose=True)
Construct fuzzy simplicial set
Wed Apr 29 14:01:29 2020 Finding Nearest Neighbors
Wed Apr 29 14:01:29 2020 Building RP forest with 82 trees
Wed Apr 29 14:02:53 2020 NN descent for 21 iterations
	 0  /  21
	 1  /  21
	 2  /  21
	 3  /  21
	 4  /  21
	 5  /  21
	 6  /  21
/home/ec2-user/anaconda3/envs/python3/lib/python3.6/site-packages/pynndescent/pynndescent_.py:1155: RuntimeWarning: invalid value encountered in sqrt
  self._distance_correction(self._neighbor_graph[1]),
Wed Apr 29 14:09:49 2020 Finished Nearest Neighbor Search
Wed Apr 29 14:10:15 2020 Construct embedding
	completed  0  /  200 epochs
	completed  20  /  200 epochs
	completed  40  /  200 epochs
	completed  60  /  200 epochs
	completed  80  /  200 epochs
	completed  100  /  200 epochs
	completed  120  /  200 epochs
	completed  140  /  200 epochs
	completed  160  /  200 epochs
	completed  180  /  200 epochs
Wed Apr 29 14:22:55 2020 Finished embedding

I'm afraid this may have to suffice as a workaround for now -- I'll try to figure out what the issue might be, but it will likely be hard to track down, so it will take some time.

I wonder if this is the same issue I'm having in #430. I'll try the pynndescent resolution too.

Installed pynndescent=0.3.3 and my pipeline still failed at exactly the same place as before, ughhhhh :-( I'll return to posting my updates on #430.

So pynndescent=0.4.7 worked for me when installed in an env with just
- ipykernel
- seaborn
- pandas
- numba
- hdbscan
- umap-learn
- pynndescent

So not sure exactly what's going on. The env I have now has numba 0.46.0. Either way, it's going now and it's going fast 😄🎉

I'm glad it is working. The crash is very puzzling. I am seeing some crash issues with a new metric I am implementing in pynndescent (it won't be the cause of your issues) that are very hard to track down, but are, possibly, stemming from a similar root cause. I'll let you know if I manage to find something reproducible on my end that might solve the problem more permanently for you.

Glad to hear that I was able to confirm your suggestion worked at least as a temp fix for others! Thank you for this amazing library and all your hard work!

Installing pynndescent solved it for us as well. Worth adding it to the requirements or shouldn't it be a hard dependency?

I had this problem and found it was solved by scaling the data using sklearn StandardScaler.

I seem to have the same problem while using the fashion mnist data for UMAP().fit_transform.
When I divide it with fit and then run transform, the crash seems to happen in transform.
This is the verbose message I get before crashing
UMAP(a=None, angular_rp_forest=False, b=None,
force_approximation_algorithm=False, init='spectral', learning_rate=1.0,
local_connectivity=1.0, low_memory=False, metric='euclidean',
metric_kwds=None, min_dist=0.1, n_components=2, n_epochs=None,
n_neighbors=5, negative_sample_rate=5, output_metric='euclidean',
output_metric_kwds=None, random_state=None, repulsion_strength=1.0,
set_op_mix_ratio=1.0, spread=1.0, target_metric='categorical',
target_metric_kwds=None, target_n_neighbors=-1, target_weight=0.5,
transform_queue_size=4.0, transform_seed=42, unique=False, verbose=True)
Construct fuzzy simplicial set
Fri Aug  7 00:13:22 2020 Finding Nearest Neighbors
Fri Aug  7 00:13:22 2020 Building RP forest with 17 trees
Fri Aug  7 00:13:25 2020 NN descent for 16 iterations
0  /  16
1  /  16
2  /  16
3  /  16
Fri Aug  7 00:13:38 2020 Finished Nearest Neighbor Search
Fri Aug  7 00:13:40 2020 Construct embedding
completed  0  /  200 epochs
completed  20  /  200 epochs
completed  40  /  200 epochs
completed  60  /  200 epochs
completed  80  /  200 epochs
completed  100  /  200 epochs
completed  120  /  200 epochs
completed  140  /  200 epochs
completed  160  /  200 epochs
completed  180  /  200 epochs
Fri Aug  7 00:13:57 2020 Finished embedding
This even occurs after installing pynndescent.
This might be connected to the local environments since if I learn a similar code in google colab, it doesn't crash.

I have the same issue. Silent exit.
In my case UMAP with cosine fails if I use robust scaler, but works if I use minmax or standard scaler.
python 3.8.12
umap_model = umap.UMAP(n_components=6, verbose=True, metric='cosine', low_memory=True)


1.21: bring back compatibility tests

Once the 1.21-dev branch is capable of fully synching and AuxPoW-mining, but before any Alpha release, we MUST bring back the compatibility test suite that was disabled with https://github.com/dogecoin/dogecoin/pull/1754 to make sure that 1.14 and 1.21 play nice together, with emphasis on softforks that were disabled in 1.14 (CSV and SegWit) because that functionality can in theory still be triggered within 1.14 clients.
We'll need to not only re-enable these tests, but also make sure that we cover all plausible scenarios specific to Dogecoin.

@patricklodder Should we close this one?

Should we close this one?

Absolutely not. This is imho a must-have for 1.21


"from plasma import Plasma" crashes qtile on Ubuntu

I'm running Ubuntu 16.04 and even just importing the Plasma class seems to crash qtile and cause it to resort to the default config. Any ideas why this is happening?
Plasma is installed correctly and I've had a look through the source and I can't see anything in the __init__ that could be running on import. Is import order important?

@sminez Did you have a chance to check if the installation works fo you now?

Hi I'm afraid that this ended up rather badly: it caused a hard crash of
qtile that I had to reboot from. In an unrelated issue, my system ended up
completely bricked (hard drive partition table got nuked it seems...!)
Once I'm back up and running I'll try again but at the moment it seems to
still be a problem. I'm afraid I don't have any log output for you (for
obvious reasons!)
On 1 Feb 2018 8:43 pm, "Arminius"<EMAIL_ADDRESS>wrote:

@sminez https://github.com/sminez Did you have a chance to check if the
installation works fo you now?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/numirias/qtile-plasma/issues/7#issuecomment-362395626,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHvXfH6ZIz36pxKnlisDaJDD0cZo9HH7ks5tQiHUgaJpZM4Rzrik
.

--
Cocoon is home security without the hassle.

This communication is only for the use of the addressee. It may contain
information which is confidential and commercially sensitive. If you are
not the intended recipient you must not read, copy, distribute or spread
this communication or any attachments to anyone other than the addressee or
use the information it contains. If you receive this communication in
error, please inform us by telephone at once. No responsibility is accepted
by Cocoon Labs Ltd for personal e-mails, or e-mails unconnected with the
company's business.
Cocoon Labs Ltd is a company registered in England and Wales. Registered
number: 09045251. Registered office: 46 The Calls, Leeds, LS2 7EY, UK.

Good lord! Best of luck getting your system back up, and thanks for all the feedback.
Travis runs the build against Ubuntu 14 + Python 3.5 without errors, so I had really hoped there is no more problem with the package.
Your initial crash could be related to the problem I first suspected (that Qtile doesn't recognize new modules without a complete restart). Another idea would be that Qtile and Plasma aren't installed for the same Python version.
There are also some methods to test your changed config without risking to crash the current session. For example, you can switch to a different tty (usually using CTRL+ALT+F1-12) from where you can then start a new X session without killing the current one (as also explained in the Qtile hacking chapter.

Back up and running with some data loss - but not too bad. Serves me right for not having a proper backup policy!
Anyway, I'm happy to say that your patch works: Plasma now runs under 3.5 👍

Great, thanks for your help.


Add updated Api specification v1.15

Specifications API RFPLAYER V1.15.pdf (2,0 Mo)
https://forum.gce-electronics.com/uploads/short-url/1wLsNPTOUzvBj03WcRUD7eXXr10.pdf
thanks to Jarek Polok https://github.com/Doubledom45/HA_Rfplayer_Beta/pull/9

can you delete the old pdf file and name the new one rfplayer_api_v1.9.pdf

@Aohzan sure, done. Thanks!

thank you @prahal


Fix coverage checking

run_coverage.py seemed to be broken in a couple of ways - these updates allow me to run it locally again - for example, invoking
./run_coverage.py numba.cuda.tests

results in running the CUDA tests, with a coverage report produced in the htmlcov directory.

@sklam thanks for the feedback. WIth testing across Linux and Windows, and different ways of invoking it, e.g.
python run_coverage.py
python ./run_coverage.pu
./run_coverage.py
# etc.

I found there's a bunch of fiddly issues still to resolve that seem a bit pointless to plough much time into. Instead, I think it's better to document the workflow using the coverage CLI tool, so I've updated this PR accordingly.

Do you follow these exact steps?
Do you have any other coverage-related tips?


Writing Netlify deployment documentation

Step by step deployment
Netlify build button

https://github.com/wheelroom/wheelroom/commit/8b6684f5f897044b8a9ae7358295fd18a2472ac4


"screenfull": "^5.0.2" is not work in vuecli4!

"screenfull": "^5.0.2" is not work in vuecli4!  but 4.2.1 is ok!

Use the Vue support channels for Vue support.

Use the Vue support channels for Vue support.


DOC: Update boilerplate generation with TemplateFlow reference

Codecov Report
Patch coverage: 100.00% and project coverage change: -2.64 :warning:

Comparison is base (00a23f9) 68.73% compared to head (c14d949) 66.10%.

: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             @@
##           master     #329      +/-   ##
==========================================
- Coverage   68.73%   66.10%   -2.64%
==========================================
  Files          20       20
  Lines        1353     1354       +1
  Branches      227      227
==========================================
- Hits          930      895      -35
- Misses        355      398      +43
+ Partials       68       61       -7

Flag
Coverage Δ

ds005
54.13% <100.00%> (-3.08%)
:arrow_down:

ds054
45.05% <100.00%> (+0.04%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

smriprep/workflows/norm.py
100.00% <100.00%> (ø)

... and 4 files with indirect coverage changes
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 in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Phase 7: Group Documentation Creation

Description
Group documentation creation. (Duration: 2 Weeks)

Define the goals of the final deliverable after the 6 month period.
Create a timeline with significant milestones.
Assign roles for participants if needed.

Submit documentation to the steering committee.

These documents will be made public.

Output

Steering Committee delivers timeline guidance / templates to group managers.
Each group delivers the following to the steering committee:

Six month goal list.
Tracking timeline.
Role list for participants (if needed).

Steering Committee publishes delivered documents.
Steering Committee notifies community of document publishing via communication channels.

Supporting Documents

Phased Plan

Closing issues associated with deprecated project plan. Please see https://github.com/orgs/DevRel-Foundation/projects/7 for new project plan


get-the-schedule fails

schedule.rkt> (get-the-schedule)
; Failed to connect to Forecast #"HTTP/1.1 422 Unprocessable Entity"

Verified Forecast id and token, and that Forecast is up.
Failing step is get-assignments (team, project and clients all work correctly):
...
schedule.rkt> (fc:get-assignments <forecast>)
; Failed to connect to Forecast #"HTTP/1.1 422 Unprocessable Entity"

Wimbledon is also unable to update at the moment, although that might be unrelated
The Forecast webapp successfully connects to https://api.forecastapp.com/assignments?end_date=2021-05-02&start_date=2021-04-05&state=active (the same endpoint as get-assignments, with some parameters)


Merge Original branch commits.

This pull request adds the original project's new commits. It includes scrollToDate function fix

Adds original project's new commits that may fix the scrollToDate function.


Long Dash Converted to "â��"

When using Yoast Long Dash ( em-dash — ) titles are converted to
Page Title â�� Site Title

This problem is resolved in the latest release 6.6.15 fixes the issue

Latest release fixes this problem.


[Feature Request] Exclude idle time from merged test duration

Describe the bug
After merging reports with the merge function from monocart-reporter, the duration for the test run shown at the top of the monocart reporter after the title and on the side bar under the Timeline section is incorrect.
To Reproduce

Version: 2.7.1
Node Version: v20.15.0
Have you tried the latest version (including node), and does the issue still exist? yes
Steps to reproduce the actual behavior:

Execute a sharded run with Playwright test using monocart-reporter.
Merge the monocart reports as explained in Merge Shard Reports documentation.
Check the test duration which is displayed at the top of the merged report after title and on the side bar under the Timeline section. It won't match the sum of the duration of the sharded reports.

Expected behavior
I believe that the duration displayed should match the sum of the duration of the sharded reports right?
Errors or Screenshots
First shard: 1m 17s

Second shard: 52.3s

Third shard: 37.4s

Fourth shard: 41.5s

Merged report: 6m 23s

The sum of the duration from the sharded reports does not add to 6m 23s.

I just noticed that the 6m 23s from the merged report seem to be calculated by doing the difference from when the first shard started which was at 17:42:47 and when the last shard ended which was at 17:49:10 (fourth shard start time plus its 41.5s of duration rounded up to 42). So 17:49:10 - 17:42:47 = 6m 23s.
Perhaps one can argue that there's no bug here, I can understand why the calculation is done like this but it wasn't immediately obvious to me where the merged duration was coming from.
Out of curiosity, why did you choose to implement it like this instead of doing the sum of the duration of all the sharded reports duration? If I think about it perhaps it's because you have the same logic for detecting duration whether the report is from merging sharded runs or from a single run. In a single run it makes sense that the duration of the report is the diff between its end time and start time but in a sharded run for me it would make more sense for the duration to be the sum of the sharded runs...

Because shards are generally parallel.
I've considered several options

Sum the time of all shards like you expected, But obviously, it's incorrect if the shards are running in parallel.
Use the longest duration among the shards. Still incorrect if the shards do not start at the same time.
Use absolute time (current approach)

const startDate = Math.min.apply(null, startDates);
const endDate = Math.max.apply(null, endDates);
const duration = endDate - date;

It should be correct whether it's parallel or serial. The only issue is whether the system time on each shard machine is accurate (synchronized with the world time).
Is this acceptable?
The shards are running in parallel which should be similar to worker in parallel

Thank you for the detailed description of the options you considered 🙌.
I agree with your current implementation. However, there's a catch and I believe the key here is considering that not all shard runs will start at similar times (as in your example).
Let me give you an example of what happens in my CI system. We have a limited number of agents which serve many pipelines and in my Playwright tests pipeline I use 3 shards. What happens often is that the 3 shards don't start running at the same time because of lack of available agents and at times it happens that one of the shard run stays in waiting for an available agent for some minutes. For sake of this example let's say 5 min.
What this means is that when I look at the time of the merged report it shows a very large time for the test execution than I expected. This time, thought technically correct for the total time the sharded run took, since the first shard started until the last shard ended, also contains waiting time for an agent that is irrelevant for the test time duration.
You can test this locally by running one shard, then waiting a few minutes and running another shard and lastly merging the monocart reports. Here's an example:

Shard 1: started at 10:35:30 and duration was 1m 59s
Wait some minutes, in this example I waited 14min (random time, I went to get something to eat =p)
Shard 2: started at 10:49:31 and duration was 1m 13s
Merged report: started at 10:35:30 and duration was 15m 14s.

Wouldn't it be more correct for the merged report to NOT count with the idle time? If there's an improvement to be made is to account for idle time, if there is any. Does that make sense? Not sure how easy it is to calculate idle time though, specially when you have many shards.
Here's an example of detecting idle time:

Shard 1: started at 22:00:00 and duration was 1m 30s
Shard 2: started at 22:03:30 and duration was 1m 00s
Shard 3: started at 22:01:00 and duration was 2m 00s

gantt
    dateFormat HH:mm:ss
    axisFormat %H:%M:%S
    first shard          :s1, 22:00:00, 22:01:30
    second shard         :s2, 22:03:30, 22:04:30
    third shard          :s3, 22:01:00, 22:03:00
    idle time            :i1, 22:03:00, 22:03:30

Any thoughts?

I believe that the current duration implementation is correct, no matter how these shards are executed, it always represents the total time needed to complete all tests.
But I also wonder if there is a way to resolve the issue in your situation.
This is a idea which is adding one more onMerge hook to handle the report data inlcudes calculating the duration as you wish.
import { merge, Util } from 'monocart-reporter';

// json file path
const reportDataList = [
    'path-to/shard1/index.json',
    'path-to/shard2/index.json',
    'path-to/shard3/index.json'
];

await merge(reportDataList, {
    name: 'My Merged Report',
    outputFile: 'merged-report/index.html',
    onMerge: (reportData, dataList) => {
        // sum or do whatever you want
        reportData.duration = dataList.map(d => d.duration).reduce((p, a) => p + a, 0);
    },
    onEnd: async (reportData, helper) => {
        // send email or third party integration
    }
});

Shortly after I created this issue I realized that my naïve approach wasn't really what I wanted. I didn't want to see the sum of all sharded runs as the duration of the report.

It makes sense that the duration of the merged report is calculated as:

const startDate = Math.min.apply(null, startDates);
const endDate = Math.max.apply(null, endDates);
const duration = endDate - startDate;

Thank you for showing a way to customize the duration of the report when merging. Using this approach also seems possible to calculate the idle time and remove it from the report duration.

The only caveat for me with point number two, with the way the duration of the merged report is calculated, is that it doesn't account for what I described as idle time. However you said that:

I believe that the current duration implementation is correct, no matter how these shards are executed, it always represents the total time needed to complete all tests.

Which perhaps means that you believe that idle time is should also be part of the test duration?
I don't dispute that taking into account idle time helps you understand when the test execution finished, meaning when the last shard finished executing. For instance we can look at the start time of the report and add the duration of the merged report and we will know when the last shard finished executing. That's true.
But I do think that knowing that is not the same as the duration of the test execution in sharded runs unless idle time is taken removed:
const startDate = Math.min.apply(null, startDates);
const endDate = Math.max.apply(null, endDates);
cost idleTime = <calculate idle time>
const duration = endDate - startDate - idleTime;

I believe this would be a more rigorous approach and if there is idle time the report could show it. Right now it only shows Start time and duration but it could show:

Start time: the time the test execution started (first shard to start).
End time: the time the test execution finished (last shard to finish)
duration: the duration of the test execution (which as shown above would exclude idle time).
idle time: the idle time (perhaps this could only be shown if exists, if not it wouldn't show).

Feel free to close this issue without any further action if you believe this is not worth doing. I understand now that there is no bug here. Changing this to a feature request.

Yes, I think the idle time is should also be part of the test duration. (These idle times are out of control, it depends on how your shard system works)
I consider providing a hook that allows users to generate the data they expect.

Please try<EMAIL_ADDRESS>with onData hook
import { merge, Util } from 'monocart-reporter';

const reportDataList = [
    'path-to/shard1/index.json',
    'path-to/shard2/index.json',
    'path-to/shard3/index.json'
];

await merge(reportDataList, {
    name: 'My Merged Report',
    outputFile: 'merged-report/index.html',

    onData: (reportData, dataList) => {
        // sum or do whatever you want
        reportData.duration = dataList.map(d => d.duration).reduce((p, a) => p + a, 0);
        // human-readable duration
        reportData.durationH = `${Util.TF(reportData.duration)} (Sum)`;
    },

    onEnd: async (reportData, helper) => {

    }
});

Hi @cenfun , sorry for my delayed response.
I'm unable to confirm I can use the onData function to perform a custom calculation for reports. What is happening to me is that the dataList parameter in your example above only has 1 entry, even though its merging two reports.
What I did was run Playwright test with 1/2 shards and then with 2/2 shards, then I used a config very similar to the one you have above and I used a console.log to see the length of the dataList and it came out as 1 instead of 2. It seems only the last shard is in that array. I say this because I also used console.log on the dataList object and one of the properties was jsonDir: 'shards/2' which indicated it was the report data for the second shard.
Perhaps there's some bug on the onData function and the rawData doesn not properly reflect all the reports data? Also, the data types for the onData function are of type any which makes it harder to understand the structure of the data and what we can do with it. If it was possible to have some types for this it would be awesome (but that perhaps is another issue if you think it's worth doing).

Thanks for the feedback. It should be fixed in<EMAIL_ADDRESS>

I can confirm that version 2.8.1 is working as expected now. I will also share how I used the onData hook to exclude idle time from the merged report duration in case anyone wants to do the same:

[!NOTE]
The part that matters is the calculateTestRunDuration function which sums the duration of each sharded test run excluding idle times and the usage of this function in the MonocartReporterOptions.onData function.

// This is the content of the merge CLI config file

const path = require("node:path");

/**
 * Start and end times of a sharded test run.
 * @typedef {{start:Date, end: Date}} ShardedTestRunTime
 */

/**
 * @returns {number} The total duration of all test runs in milliseconds excluding idle time.
 * @param {ShardedTestRunTime[]} shardedTestRunTimes
 */
function calculateTestRunDuration(shardedTestRunTimes) {
  if (shardedTestRunTimes.length === 0) return 0;

  // Step 1: Sort the test runs by start date
  shardedTestRunTimes.sort((a, b) => a.start.getTime() - b.start.getTime());

  // Step 2: Merge overlapping intervals
  const mergedDurations = [];
  let current = shardedTestRunTimes[0];

  for (let i = 1; i < shardedTestRunTimes.length; i++) {
      if (current.end >= shardedTestRunTimes[i].start) {
          // Overlapping intervals, merge them
          current.end = new Date(Math.max(current.end.getTime(), shardedTestRunTimes[i].end.getTime()));
      } else {
          // No overlap, push the current interval and move to the next
          mergedDurations.push(current);
          current = shardedTestRunTimes[i];
      }
  }
  // Push the last interval
  mergedDurations.push(current);

  // Step 3: Calculate the total duration
  let totalDurationInMilliseconds = 0;
  for (const duration of mergedDurations) {
      totalDurationInMilliseconds += duration.end.getTime() - duration.start.getTime();
  }

  return totalDurationInMilliseconds;
}

/**
 * @returns {string} The duration formatted as a string in the format "h m s" or "m s".
 * @param {number} milliseconds
 */
function formatDuration(milliseconds) {
  let seconds = Math.floor(milliseconds / 1000);
  let minutes = Math.floor(seconds / 60);
  let hours = Math.floor(minutes / 60);

  seconds = seconds % 60;
  minutes = minutes % 60;

  if (hours > 0) {
      return `${hours}h ${minutes}m ${seconds}s`;
  } else {
      return `${minutes}m ${seconds}s`;
  }
}

/**
 * @typedef {import('monocart-reporter').MonocartReporterOptions} MonocartReporterOptions
 * @returns {import('monocart-reporter').MonocartReporterOptions}
 * @param {string} reportersOutputDir
 */
function getMonocartReporterOptions(reportersOutputDir) {
  const monocartReporterOutputDir = path.resolve(reportersOutputDir, "monocart-reporter");
  /**
   * @type {MonocartReporterOptions}
   */
  const monocartOptions = {
    name: "Playground app for @ln/ngx-module-federation-tools",
    outputFile: path.resolve(monocartReporterOutputDir, "monocart-report.html"),
    onData: (reportData, dataList) => {
      if (isShardedTestRun || dataList.length === undefined  || dataList.length <= 1) {
        return;
      }

      const shardedTestRunTime = dataList.map(x => {
        return {
          start: new Date(x.system.timestampStart),
          end: new Date(x.system.timestampEnd),
        }
      });
      const totalDurationInMilliseconds = calculateTestRunDuration(shardedTestRunTime);
      reportData.durationH = formatDuration(totalDurationInMilliseconds);
    },
  };

  return monocartOptions;
}

const reportersOutputDir= path.resolve("./test-reporters/playwright");
const options = getMonocartReporterOptions(reportersOutputDir);
module.exports = options;

With the above I got what I expected. Let's consider this simple example:

first shard run from 14:25:04 to 14:26:57 with duration of 1min 53s.
second shard run from 14:32:38 to 14:33:48 with duration of 1min 10s.
idle time of 6min 41s.

Which can be visualized as:
gantt
    dateFormat HH:mm:ss
    axisFormat %H:%M:%S
    first shard          :s1, 14:25:04, 14:26:57
    second shard         :s2, 14:32:38, 14:33:48
    idle time            :i1, 14:26:58, 14:32:37

Using the logic to exclude idle time I got a report duration of: 3min 04s.

Which to me makes more sense specially when looking at the time from each shard in the report.
1st shard run:

2nd shard run:

Without this custom logic to exclude idle time the merged report duration by default shows as 8m 44s.

@cenfun Even with the onData function logic updating the reportData.durationH to show the time I want on the report, the time that shows on the MR summary is still the time without my logic.
Given the example from the previous post, even though I updated the report text for the duration to be the string 3min 04s but the MR summary shows:
[MR] Playground app for @ln/ngx-module-federation-tools
┌─────────────┬──────────────────────┐
│ Tests       │ 354                  │
│ ├ Passed    │ 205 (57.9%)          │
│ ├ Flaky     │ 0   (0.0%)           │
│ ├ Skipped   │ 148 (41.8%)          │
│ └ Failed    │ 1   (0.3%)           │
│ Steps       │ 18937                │
│ Suites      │ 67                   │
│ ├ Projects  │ 3                    │
│ ├ Files     │ 22                   │
│ ├ Describes │ 0                    │
│ └ Shards    │ 2                    │
│ Retries     │ 0                    │
│ Errors      │ 150                  │
│ Logs        │ 0                    │
│ Attachments │ 3                    │
│ Artifacts   │ 1                    │
│ Playwright  │ v1.47.1              │
│ Date        │ 18/09/2024, 15:25:04 │
│ Duration    │ 8m 44s               │
└─────────────┴──────────────────────┘

Notice that the last field of the summary, Duration, says 8min 44s instead of 3min 04s.
Is there a way to update that value for the MR summary? Or is this potentially a bug where the MR summary should read from the updated reportData.durationH field?

try updating duration too
reportData.durationH = formatDuration(totalDurationInMilliseconds);
+ reportData.duration = totalDurationInMilliseconds;

That was it. And you had that already set in your initial demo, I just didn't notice that I had removed it when I was implementing it on my side.
Awesome as always @cenfun . Thank you 💯


"fisher_plugins" file not found: "update"

After coming across your work with Antibody and seeing your Fish dotfiles, I really wanted to give it a test run, because I've been sorely needing an automated dotfiles system for a while, and I really liked yours.
So when I attempted to run the bootstrap.fish script within a devcontainer, so I could start tweaking it to better fit my needs before attempting to install it directly on my system first, I ran into a fatal error right away:

After a little investigating, I found that fisher update is not wanting to work with symlinks... again. After searching through the issues in Fisher repo, this appears to be a reoccurring problem.
I was gonna post an issue there, but I first wanted to see if you've encountered this problem before and if you have any quick-fix recommendations.
If not, I figured I'd at least let you know about it.

I was gonna post an issue there, but I first wanted to see if you've encountered this problem before and if you have any quick-fix recommendations.

I haven't no, no idea as well...


General Best

Changelog:

Assets's folder:
Move assets to it's folder inside assets's folder:
images to /assets/images/
stylesheets to /assets/stylesheets/
and changes the references to it in the php files
Include a db.inc.sample and git ignore db.inc.php
Update README to Markdown syntax

Thanks Gutem


Bump tracing-journald from 0.1.0 to 0.2.2

Motivation
We should keep dependencies up to date.
We must fix breaking changes, see logs in https://github.com/ZcashFoundation/zebra/pull/3358
Specifications

Designs

Related Work

Hey team! Please add your planning poker estimate with ZenHub @conradoplg @dconnolly @jvff @oxarbitrage @teor2345 @upbqdn

Duplicate of #2953


DatesInUtc parameter of RenderListDataAsStream not working

Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
SharePoint CSOM
Developer environment
Windows
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[ ] 💥 Microsoft Edge
[ ] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[X] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details
No response
Describe the bug / error
The RenderListDataAsStream API has a parameter DatesInUtc. When it is true, it indicates that any DateTime values in the Caml query is in universal time. However, since today or earlier, it no longer seem to work. For the same query, I need to set the site's time zone to UTC to get any results.
Steps to reproduce

Set time zone in regional settings to Stockholm
Create a file with the value 2024-07-07 for the field TestDate
Call RenderListDataAsStream with the following parameters and CAML query:

RenderListDataParameters
{
    ViewXml = viewXml,
    DatesInUtc = true,
    RenderOptions = RenderListDataOptions.ListData,
    RenderURLFieldInJSON = true
}

<View Scope='Recursive'>
    <Query>
        <Where>
            <Eq>
                <FieldRef Name='TestDate' />
                <Value IncludeTimeValue='TRUE' Type='DateTime'>2024-07-06T22:00:00Z</Value>
            </Eq>
        </Where>
        <OrderBy UseIndexForOrderBy='FALSE' Override='FALSE'>
            <FieldRef Name='Modified' Ascending='False' />
        </OrderBy>
    </Query>
    <ViewFields>
        <FieldRef Name='ContentTypeId' />
        <FieldRef Name='Modified' />
        <FieldRef Name='FileLeafRef' />
        <FieldRef Name='File_x0020_Type' />
        <FieldRef Name='Title' />
        <FieldRef Name='TestChoice' />
        <FieldRef Name='TestNumber' />
        <FieldRef Name='TestDate' />
        <FieldRef Name='TestMmd' />
        <FieldRef Name='TestMmdMulti' />
        <FieldRef Name='TestPeopleMultiple' />
        <FieldRef Name='TestNote' />
        <FieldRef Name='TestBoolean' />
        <FieldRef Name='Editor' />
        <FieldRef Name='FileDirRef' />
        <FieldRef Name='File_x0020_Size' />
        <FieldRef Name='CheckoutUser' />
        <FieldRef Name='CheckedOutUserId' />
        <FieldRef Name='ContentType' />
        <FieldRef Name='ContentTypeId' />
        <FieldRef Name='Editor' />
        <FieldRef Name='File_x0020_Size' />
        <FieldRef Name='File_x0020_Type' />
        <FieldRef Name='FileRef' />
        <FieldRef Name='FileLeafRef' />
        <FieldRef Name='HTML_x0020_File_x0020_Type' />
        <FieldRef Name='Modified' />
        <FieldRef Name='_UIVersionString' />
        <FieldRef Name='_CheckinComment' />
    </ViewFields>
    <RowLimit Paged='TRUE'>50</RowLimit>
</View>

Notice there are no results
Change time zone to UTC
Try again
Notice that there are results

Expected behavior
When using the DatesInUtc parameter, passing DateTime values in UTC, and there are matching items I expect them in the result, regardless of regional settings.

we are having similar issues in power automate when doing renderlistasdatastream it only returning 1 value when there should be 40ish, similar thing happens when we create a custom view and filter on the same thing we only get one value returned

I am relieved to hear that I am not alone.

Adding the attribute StorageTZ='TRUE' to date values seem to help. I could swear this was not necessary before.
Working example:
<Value StorageTZ='TRUE' IncludeTimeValue='TRUE' Type='DateTime'>2024-07-06T22:00:00Z</Value>