difference between clatrin-mediated and receptor mediated

receptor-mediated endocytosis
An endocytosis process in which cell surface receptors ensure specificity of transport. A specific receptor on the cell surface binds tightly to the extracellular macromolecule (the ligand) that it recognizes; the plasma-membrane region containing the receptor-ligand complex then undergoes endocytosis, forming a transport vesicle containing the receptor-ligand complex and excluding most other plasma-membrane proteins. Receptor-mediated endocytosis generally occurs via clathrin-coated pits and vesicles.
has descendant
—clathrin-mediated endocytosis
An endocytosis process that begins when material is taken up into clathrin-coated pits, which then pinch off to form clathrin-coated endocytic vesicles.
This arrangement looks a little odd.
The paper I am approving says:
Many proteins participate in the different aspects of CME including endocytosis site selection, cargo recruitment, coat assembly, membrane curvature, actin polymerization and vesicle scission (Doherty and McMahon, 2009).
So it seems that there should be child terms
clathrin mediated endocytosis
—clathrin mediated endocytosis site selection
—clathrin mediated endocytosis cargo recruitment
—clathrin mediated endocytosis clathrin coat assemby
—clathrin mediated endocytosis membrane curvature
—clathrin mediated endocytosis actin polymerization
—clathrin mediated endocytosis vesicle scission
However, receptor-mediated endocytosis  is defined as the “cargo recruitment” step which is a part of the process.
I’m going to TG the specific clathrin mediated terms if I need them here, but I wanted to point out the logical inconsistency in the parentage.
Probably  the clathrin mediated endocytosis def could be improved too.....

They seem to be the same thing?
https://en.wikipedia.org/wiki/Receptor-mediated_endocytosis
the other type is
receptor-independent endocytosis
calveolin-mediated endocytosis
https://en.wikipedia.org/wiki/Caveolin
(calveolin is not present in fungi and so should have taxon restrictions)

and....
calveolin mediated endocytosis is under
receptor mediated endocytosis
http://www.ebi.ac.uk/QuickGO/GTerm?id=GO:0072583

ooh this is a big mess.....

So the questions seem to be:
(a) Is clathrin-mediated endocytosis always receptor mediated?  Wikipedia says yes, but I wouldn't expect it to capture odd exceptions.
(b) Is Caveolin-mediated endocytosis also receptor mediated?
(c) What constitutes the start/end/parts of (receptor/clathrin mediated endocytosis).  While defs could be clearer, I don't think it is justified to say that the current def of receptor-mediated endocytosis refers fo the 'cargo recruitment step'  It's just that this is one of its major differentia.  The genus endocytosis is clearly stated at the start of the def, it is defined as: "A vesicle-mediated transport process in which cells take up external materials or membrane constituents by the invagination of a small region of the plasma membrane to form a new membrane-bounded vesicle."  I agree that the partonomy needs some tidying up though.  There's a distinct absence of general terms for the steps in endocytosis.

I’m going to TG the specific clathrin mediated terms if I need them here

Via Involved in?

yep part_of.
clathrin-mediated is always receptor mediated.
All of the reviews above agree (the mechanism isn't fully elucidated, there are a number of proposed models)
(Hirst et al., 2011; http://www.ncbi.nlm.nih.gov/pubmed/22022230
Godlee and Kaksonen, 2013 http://www.ncbi.nlm.nih.gov/pubmed/24322426 the figures in this recent review are the most useful)
They have to be receptor mediated as the clathrin is linked to a receptor via the adaptor complex. Thats the same in all the models.

see also
https://github.com/geneontology/go-ontology/issues/12510

The membrane invagination part should also pull in this ticket. There are lots of processes which use similar mechanisms for membrane invagination... with slightly different names...tubulation,  spore membrane bending pathway, curvature etc .but they are not connected in the graph.
https://github.com/geneontology/go-ontology/issues/12387
A parent membrane invagination could be a useful grouping term for all of these.

PMID:26749213 has a nice summary of the steps in the intro
we should also consider this term.
http://www.ebi.ac.uk/QuickGO/GTerm?id=GO:0000147
This probably needs to be revisited. The 'actin cortical patch' is a  'low resolution' structure'
and represents 'an actin structure at the endocytic sites' It is now clear that ALL of the annotations to this  term represent  sub parts of the endocytic process.
For example SYP1 an early arriving protein, is annotated to "actin cortical patch assembly"
http://www.yeastgenome.org/locus/YCR030C/overview
at SGD (and ISS'd  to by PomBAse).  But the description is
Negative regulator of WASP-Arp23 complex; involved in endocytic site formation;
It might be a time to lose all of the 'actin cortical patch' related   terms from GO (only used by fungi), and remap to the endocytic sub processes and more appropriate component terms.

I have feedback from the author/curator of this paper
https://curation.pombase.org/pombe/curs/d5e1616053c30a60/ro/
that
Henar:
Yes, clathrin-mediated endocytosis and receptor-mediated endocytosis are the same thing, so the terms can be merged.

I am a bit concerned about this. I really don't have time to look at this today, or for a couple of weeks. I realise this book is a bit old but https://www.google.co.uk/url?sa=t&rct=j&q=&esrc=s&source=web&cd=4&ved=0ahUKEwizqc_-3_PNAhXjAsAKHWsaB6EQFgg9MAM&url=http%3A%2F%2Fwww.ncbi.nlm.nih.gov%2Fbooks%2FNBK21639%2F&usg=AFQjCNEXuTyxdZh0meuAZzBUq-V-IuJXKQ&sig2=xaXABQpL_mbR8dCLVuXDVQ suggests: Small invaginations of the plasma membrane termed caveolae, lined with the membrane protein caveolin, contain some receptor proteins and are used for certain types of receptor-mediated endocytosis. However, receptor-mediated endocytosis generally occurs via clathrin-coated pits and vesicles (Figure 17-44).
And http://www.jbc.org/content/286/10/8231.long (again a bit old 2011) states: two main pathways have been identified for receptor-mediated endocytosis: the clathrin-dependent and the caveolae/lipid raft-dependent endocytic pathways (1, 2). Clathrin-dependent endocytosis is the most well characterized mechanism for mediating the internalization of membrane receptors into cells. It is also important for intracellular trafficking at the trans-Golgi network and endosomes (3). Caveolae/raft-dependent endocytosis is involved in multiple biological processes, including mediating virus entry into host cells, internalizing glycophosphatidylinositol-anchored proteins and regulating certain signaling cascades. Caveola are cholesterol and sphingolipid-rich plasma membrane invaginations of a diameter of 60–80 nm, of which caveolin-1 is the main protein component required for caveola biogenesis (4).
Also supported by wikipedia (fab) endocytosis page: Uptake of extracellular molecules is also believed to be specifically mediated via receptors in caveolae.
Please DON'T merge clathrin-mediated endocytosis and receptor-mediated endocytosis
happy holidays for me.....
Ruth

OK, no hurry.
I think the first thing is to figure out what is meant by receptor-mediated in this context...
My understanding is that the receptor is an integral part of the mechanism, and is used to assembly the  clathrin apparatus in clathrin-mediated endocytosis:
https://en.wikipedia.org/wiki/Receptor-mediated_endocytosis
For calveolin mediated, the mechanism seems less clear,  there are probably more recent reviews
http://www.ncbi.nlm.nih.gov/pmc/articles/PMC2723140/
But the receptor-mediated seems less useful as a classifier than what the actual mechanism is
(clathrin-mediated, calveolin mediated etc)....
Note, caveolin-mediated endocytisis is currently a child of receptor mediated endocytosis, and this seems to be  definitely not always true?
VAl

I also found this http://www.nature.com/nrm/journal/v16/n5/full/nrm3968.html
They seem to indicate (figure 3) that receptor-mediated endocytosis can also occur without clathrin: "Model for Shiga toxin-driven membrane bending is shown. Shiga toxin binds to its cellular receptor, the glycosphingolipid (GSL) globotriaosylceramide (Gb3), and reorganizes membrane lipids to favour membrane bending without the need for cytosolic clathrin"
I like the idea of dividing using the mechanism.
Maybe @paolaroncaglia knows more? (tagging even though she's on vacation atm)

But the receptor-mediated seems less useful as a classifier than what the actual mechanism is (clathrin-mediated, calveolin mediated etc)....

I'm pretty sure we need both. Still reading around this, but seems pretty clear that caveolin-mediated endocytosis is not always triggered by receptors, so we should probably split this class into receptor-mediated and a more general class.  We should also make the receptor-mediated (triggered?) nature of clathrin-mediated endocytosis clearer in the definition.

OK sounds good.

I have moved 'caveloin-mediated endocytosis' up to be a direct subclass of endocytosis.  @RLovering  - happy to add a more specific subclass 'receptor/caveolin mediated endocytosis' if you think that is warranted.
Cheers,
David


nixos-install: only mount if root

Emergency fix for https://github.com/NixOS/nixpkgs/pull/210812#issuecomment-1385152889

@ofborg test installer.simple
@ofborg test ec2-config

I confirm the image builds locally.

Can also confirm it builds.

Uhm, if nixos-install is expected to work as non-root this needs to be done in an unshared namespace.
I just tried and it seems to work inside a unshare -mr.

I found a nicer solution: nixos-enter is already unsharing the mount namespace, so I'll just add these commands to its invocation with -c.


Heltec V3 (esp32 s3) install failed - invalid header: 0xffffffff [Web flasher]

Hi, I got new Heltec v3 board and i wasn't able to make it work with iGate firmware. Web flasher prompts successful flashing, but OLED stays black. I checked serial monitor and theres looped message "invalid header: 0xffffffff".
I also tried to use shell scripts provided in last release with same result. In order to make it work i needed to change esptool line by adding different chip type esp32-s3.
To check if this is hardware related issue i flashed meshtastic (also web-flasher) and it worked.
Am i missing something?

hi,
there is a know bug with the installers we provided for this board ....  so the only way for this board (until a few days when we will upload fixes) is installing it from VSCODE

HELTEC V3 is now added as a valid installer in new Web Installer v1.0.3


Topic/tombstone feature

WIP.
@jystic Not sure where Jetski is supposed to be.
Also there's some java which I have put a todo on.

@HuwCampbell it's fine if you upgrade it, the only difference is the merge commit, my bad for not doing this already.

@amosr would you mind having a look at this. I think someone else will have to do the Java generation part, but apart from that I think it is ok.

Yep, this looks good. I suspect this will all change in a little bit once I get the possibly shit going, but for now I'm happy to merge this.
Don't worry about the java generation either, that should fall out of the possibly stuff.

:children_crossing:


merge with base branch

`['merge']:('gh pr checkout 68)',

<EMAIL_ADDRESS>`.


NextJS 12 breaks useMutation usage

I have this component that use to work just fine with nextjs 11
const DeleteAccount = () => {
  const [deleteAccount] = useMutation((mutation) => {
    const data = mutation.deleteUser();

    return { ...data };
  });
})

Once I updated the project to yarn add next@12 it started throwing
Unhandled Runtime Error
TypeError: (0 , _gqtyWEBPACK_IMPORTED_MODULE_3.useMutation) is not a function

Rolling back to nextjs 11 the issue disappear.

Next 12 has no significant update for builds EXCEPT the removal of the deprecated webpack 4.
Are you using webpack 4 configs in your next.config.js?

Next 12 has no significant update for builds EXCEPT the removal of the deprecated webpack 4.
Are you using webpack 4 configs in your next.config.js?

Yeah, we need an answer to that question AND a reproduction repo, all the examples/manual tests of gqty are using Next.js v12 with webpack 5

Answering https://github.com/gqty-dev/gqty/issues/292#issuecomment-962457071
When using nextjs 11 the output is:
$ next dev
ready - started server on <IP_ADDRESS>:3000, url: http://localhost:3000
info  - Using webpack 5. Reason: Enabled by default https://nextjs.org/docs/messages/webpack5

My next.config.js is:
module.exports = {
  reactStrictMode: true,
  env: {
    GRAPHQL_ENDPOINT: process.env.GRAPHQL_ENDPOINT
  }
}

If I yarn add next@latest it breaks with the run time errors. Anyways. I'll look further. Thanks.

It doesn't need to be closed if your issue is still there, it's just that we need a reproduction

Here is a reproduction which was based on your nextjs example, i've bumped the deps for next and gqty to the latest.
i think it may just be a server-side error, i'm having it using resolved in getStaticProps
https://codesandbox.io/s/gqty-sandbox-forked-dwk3l?file=/src/pages/index.tsx:1468-1476

Here is a reproduction which was based on your nextjs example, i've bumped the deps for next and gqty to the latest.
i think it may just be a server-side error, i'm having it using resolved in getStaticProps
https://codesandbox.io/s/gqty-sandbox-forked-dwk3l?file=/src/pages/index.tsx:1468-1476

thank you, I will take a look into it

Good and bad news, it seems like Next.js 12 broke the "export const { ..." syntax, this fixes everything:

but already generated clients won't be able to get this fix retroactively, something that can be done is analyze the already generated clients and print a warning to change the export syntax

Cool, i can live with making that change myself, it seems to be working now thanks!


Disable diagnostics for blacklisted document schemes

Otherwise can lead to confusing duplicated diagnostics in VSCode
due to its usage of virtual documents for source control diffbases

sourcekitd does not properly handle virtual files when the
-working-directory flag is passed

PTAL, added tests

@swift-ci please test

@swift-ci please test


[feat] - Ability to use additional icons

Does your feature request relate to a specific USWDS component?
Yes. This is for the Icon component.
What USWDS Version is this feature present in?
This is a feature that was available in USWDS Icons since 2021.
Is your feature request related to a problem? Please describe.
USWDS by default is packaged with 242 Icons from Material Design. This list was a best guess of what most teams would need, but in the event that guess was off, they have provided ways to use either fewer or more icons than the initial set (full disclosure: I was on the team that built this component for USWDS). This was first done with uswds-gulp (now archived) and is now handled with uswds-compile.

Active icons are found in dist/img/usa-icons. The icons in this directory will be packaged into an SVG sprite. The complete set of available icons are located in two directories: dist/img/material-icons and dist/img/uswds-icons. Copy icons into a usa-icons directory within your project images directory, and rebuild the SVG sprite using uswds-compile.

Describe the solution you'd like
Would like to have a way to use these icons without requiring bespoke Icon solutions.
Describe alternatives you've considered
Building the Icon component custom, and not using the Icon component from this library
Additional context
Screenshot depicting full set of material icons in the uswds node_modules folder.

I'm imagining some way to specify a src for a more generic use of our Icon, or something like that. Sounds like a fun one!


Add more Silvercrest (from Lidl) devices. (HG06337 + HG06338)

Device description
HG06337 is a OnOffSwitchAdapter
HG06338 is an extension cord with 3 OnOffSwitchAdapters and 4 usb plugs (not sure if they can be switched on/off too)
Zigbee2mqtt page
https://www.zigbee2mqtt.io/devices/HG06337.html
https://www.zigbee2mqtt.io/devices/HG06338.html
MQTT message with device information
{"dateCode":"","description":"Smart Plug","friendly_name":"0x842e14fffef8cfbe","hardwareVersion":1,"ieeeAddr":"0x842e14fffef8cfbe","lastSeen":1606852330818,"manufacturerID":4098,"manufacturerName":"_TZ3000_kdi2o9m6","model":"HG06337","modelID":"TS011F","networkAddress":5908,"powerSource":"Mains (single phase)","type":"Router","vendor":"Silvercrest"}
{"dateCode":"","description":"3 gang switch, possibly with USB","friendly_name":"0xec1bbdfffeaedbb4","hardwareVersion":1,"ieeeAddr":"0xec1bbdfffeaedbb4","lastSeen":1606856441320,"manufacturerID":4098,"manufacturerName":"_TZ3000_1obwwnmq","model":"HG06338","modelID":"TS011F","networkAddress":5558,"powerSource":"Mains (single phase)","type":"Router","vendor":"Silvercrest"}
MQTT messages from device
MQTT state change commands
MQTT publish: topic 'zigbee2mqtt/0x842e14fffef8cfbe', payload '{"linkquality":42,"state":"OFF"}'
MQTT publish: topic 'zigbee2mqtt/0x842e14fffef8cfbe', payload '{"linkquality":42,"state":"ON"}'
MQTT publish: topic 'zigbee2mqtt/0xec1bbdfffeaedbb4', payload '{"linkquality":39,"state_l1":"ON","state_l2":"OFF","state_l3":"OFF"}'
MQTT publish: topic 'zigbee2mqtt/0xec1bbdfffeaedbb4', payload '{"linkquality":39,"state_l1":"ON","state_l2":"ON","state_l3":"OFF"}'
MQTT publish: topic 'zigbee2mqtt/0xec1bbdfffeaedbb4', payload '{"linkquality":39,"state_l1":"ON","state_l2":"ON","state_l3":"ON"}'
MQTT publish: topic 'zigbee2mqtt/0xec1bbdfffeaedbb4', payload '{"linkquality":39,"state_l1":"OFF","state_l2":"ON","state_l3":"ON"}'
MQTT publish: topic 'zigbee2mqtt/0xec1bbdfffeaedbb4', payload '{"linkquality":36,"state_l1":"OFF","state_l2":"OFF","state_l3":"ON"}'
MQTT publish: topic 'zigbee2mqtt/0xec1bbdfffeaedbb4', payload '{"linkquality":39,"state_l1":"OFF","state_l2":"OFF","state_l3":"OFF"}'

I see that the vendor is changes now, in Z2M but still the "sub"-devices are not yet created in Domoticz.
(Z2M dev branch is used, and the V3.0 branch of this plugin)

Nothing works for me since yesterday.
Do you have last dev from z2m?

It seems i thought i had the v3.0 branch, but actually i didn't.
The installation instructions were wrong (missed the "-b v3.0" option in the pull request).
I'm not working with git daily, so i didn't know that.
Completly removing the plugin and install with the mentioned option fixed it for me.

Re3garding
The installation instructions were wrong (missed the "-b v3.0" option in the pull request).
I'm not working with git daily, so i didn't know that.
Using switch "git pull-b v3.0" is showing me "error: unknown switch `b'"
am i wrong ?

Hi,
No, it's probably me not being clear enough.
the installations for normal branch are
cd domoticz/plugins
git clone https://github.com/stas-demydiuk/domoticz-zigbee2mqtt-plugin.git zigbee2mqtt

But for the v3.0 branch should be:
cd domoticz/plugins
git clone -b v3.0 https://github.com/stas-demydiuk/domoticz-zigbee2mqtt-plugin.git zigbee2mqtt

And if you are migrating from old to new, you should remove the existing zigbee2mqtt to a backup-location, and initiate a new git clone. Not upgrade with pull or such.
Hope that make's it more clear.

Thanks.  Try to get the Lidl power adapter to use with domoticz
CyberClwn<EMAIL_ADDRESS>schrieb am Fr., 11. Dez. 2020, 21:22:

Hi,
No, it's probably me not being clear enough.
the installations for normal branch are
cd domoticz/plugins
git clone https://github.com/stas-demydiuk/domoticz-zigbee2mqtt-plugin.git zigbee2mqtt
But for the v3.0 branch should be:
cd domoticz/plugins
git clone -b v3.0 https://github.com/stas-demydiuk/domoticz-zigbee2mqtt-plugin.git zigbee2mqtt
And if you are migrating from old to new, you should remove the existing
zigbee2mqtt to a backup-location, and initiate a new git clone. Not upgrade
with pull or such.
Hope that make's it more clear.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/stas-demydiuk/domoticz-zigbee2mqtt-plugin/issues/488#issuecomment-743407941,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIPLQ4O4DUOAAILHBT7OZATSUJ5RLANCNFSM4UKSHSFA
.

I've upgraded to the v3.0 branch (moved the older plugin directory outside domoticz directory first), but still the devices don't show in the devices list. They do show in the plugin page:

Friendly Name
Model
Description
Type
IEEE Address
Last Seen

Motion Sensor 1
HG06335
Smart motion sensor
EndDevice
0xbc33acfffe362fcc
2020-12-14 13:57:30

Motion Sensor 2
HG06335
Smart motion sensor
EndDevice
0xbc33acfffe362f9c
2020-12-14 13:58:47

Plug 4
HG06337
Smart Plug
Router
0x842e14fffee0e5ab
2020-12-14 14:17:33

What is going on?
Thanks!

Nevermind, v3.0 requires the experimental "new_api" switch to be set to "true" (forgot about that). Aplogies.
See https://github.com/Koenkk/zigbee2mqtt/issues/3281

Moved original folder and tried to load the "new 3.0"
git clone -b v3.0
https://github.com/stas-demydiuk/domoticz-zigbee2mqtt-plugin.git zigbee2mqtt
Klone nach 'zigbee2mqtt' ...
fatal: Remote-Branch v3.0 nicht im Upstream-Repository origin gefunden.
Where is the fault?
On Mon, 14 Dec 2020 at 15:22, lxh7<EMAIL_ADDRESS>wrote:

Nevermind, v3.0 requires the experimental "new_api" switch to be set to
"true" (forgot about that). Aplogies.
See Koenkk/zigbee2mqtt#3281
https://github.com/Koenkk/zigbee2mqtt/issues/3281
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/stas-demydiuk/domoticz-zigbee2mqtt-plugin/issues/488#issuecomment-744473133,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIPLQ4P5KUAOHGIAHFBH5Q3SUYNUDANCNFSM4UKSHSFA
.

--
Lothar Rieck
International Procurement Consultant
car and it accessories
Germany

`Hello Stas, how can I switch from v3.0 to master now?
 git reset --hard
git checkout master
git pull`

The v3.0 information is obsolete now, it has been moved to the master branch by stas.
so switch back to the master branch.


Changed do_why.py to causal_model.py

As discussed in #75, this PR just changes the name of do_why.py to causal_model.py

Perfect, thanks @jrfiedler


SolrConection not populating in ISolrOperation and receiving 401 in .net core 2.1 and 2.0 as well

Hi All,
I am facing issue of 401 in .net core 2.1 and 2.0 with Solr net with Microsoft DI. I am injecting  ISolrConnection and ISolrOperation in same class and I am seeing different connection for both object. ISolrConnection have default authrization header but the ISOLROperation didn't have that. Please below image of Isolroperation

See below header for I SolrConnection

I am initializationing  like below-:

services.AddSolrNet(solrConnectionConfiguration.SolrCoreUrl,options=> {options.HttpClient.DefaultRequestHeaders.Authorization =
new System.Net.Http.Headers.AuthenticationHeaderValue("Basic", Convert.ToBase64String(System.Text.Encoding.ASCII.GetBytes("userid:password")));});

Please suggest what i am doing wrong?

I believe was had something fixed in the last version. Does this problem still occur?


[Bug] CPU is too high

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
If I don't log in to Dinky over the weekend, my CPU will soar to 80% when I log in on Monday, and I can't log in anymore. The only solution is to restart. I'm not sure if it's caused by Dinky's built-in monitoring.
What you expected to happen
If I don't log in to Dinky over the weekend, my CPU will soar to 80% when I log in on Monday, and I can't log in anymore. The only solution is to restart. I'm not sure if it's caused by Dinky's built-in monitoring.
How to reproduce
If I don't log in to Dinky over the weekend, my CPU will soar to 80% when I log in on Monday, and I can't log in anymore. The only solution is to restart. I'm not sure if it's caused by Dinky's built-in monitoring.
Anything else
No response
Version
1.0.0
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

可以 dump 下内存快照协助排查一下该问题 , 目前确实有人反馈该问题,初步排查是由于 paimon 作为了监控存储介质,运行一段时间内会有内存泄漏风险, 可以协助确认一下该问题

找到问题了么 解决了嘛

找到问题了么 解决了嘛

可以一起协助排查该问题

Search before asking 先搜索后询问

[x]  I had searched in the issues and found no similar issues.我在问题中搜索过，没有发现类似的问题。

What happened 发生了什么事
If I don't log in to Dinky over the weekend, my CPU will soar to 80% when I log in on Monday, and I can't log in anymore. The only solution is to restart. I'm not sure if it's caused by Dinky's built-in monitoring.如果我周末不登录 Dinky，周一登录时我的 CPU 会飙升到 80%，我再也无法登录了。唯一的解决方案是重新启动。我不确定这是否是由 Dinky 的内置监控引起的。
What you expected to happen
您期望发生的情况
If I don't log in to Dinky over the weekend, my CPU will soar to 80% when I log in on Monday, and I can't log in anymore. The only solution is to restart. I'm not sure if it's caused by Dinky's built-in monitoring.如果我周末不登录 Dinky，周一登录时我的 CPU 会飙升到 80%，我再也无法登录了。唯一的解决方案是重新启动。我不确定这是否是由 Dinky 的内置监控引起的。
How to reproduce 如何繁殖
If I don't log in to Dinky over the weekend, my CPU will soar to 80% when I log in on Monday, and I can't log in anymore. The only solution is to restart. I'm not sure if it's caused by Dinky's built-in monitoring.如果我周末不登录 Dinky，周一登录时我的 CPU 会飙升到 80%，我再也无法登录了。唯一的解决方案是重新启动。我不确定这是否是由 Dinky 的内置监控引起的。
Anything else 别的东西
No response 没有回应
Version 版本
1.0.0
Are you willing to submit PR?
你愿意提交公关吗？

[ ]  Yes I am willing to submit a PR!是的，我愿意提交PR！

Code of Conduct 行为准则

[x]  I agree to follow this project's Code of Conduct我同意遵守本项目的行为准则

有试过关闭dinky上的jvm监控按钮吗

@Pandas886 sure，但貌似没什么用，不知道新版本是否修复好


WIP - Add Vue Ariakit implementation

Description

This is a big big big WIP that probably won't get merged for a long time, but I wanted to share what I'd done so far. Maybe this is something we can do iteratively as a team now that there's a rough pattern established for how to convert Ariakit stuff from React hooks to Vue composition API.
Testing Instructions

Checklist

[ ] My pull request has a descriptive title (not a vague title like Update index.md).
[ ] My pull request targets the default branch of the repository (main) or a parent feature branch.
[ ] My commit messages follow best practices.
[ ] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[ ] I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

Does it need to be changed all at once? Is there a way we can do it incrementally?

We can definitely do it incrementally. The only reason this one got so big was because I chose a place to start that had lots of internal dependencies. I think this was a good way to start because it forced me to reckon with different patterns that exist in Ariakit that we would have to solve with Vue analogues. In that sense this PR is probably good to keep around but we can start at the smaller parts of this PR (which we probably wouldn't be using directly).
It may be helpful for me or someone else to check out this PR and explicitly document the patterns I'm talking about here. Some things like how I decided to convert Ariakit's "state" objects into Vue reactives, the prop type shapes, other concepts like the listeners, attributes and classes standard pattern for the hook return values that allows them to compose.
One problem that still needs to be solved, however, is multiple ordered dispatch of events through hooks that all define the same listener. For example, if you are composing multiple hooks and more than one of them define a click handler, we'll need to recreate the behavior stopPropagation in an order dependent way. This could be as easy as looping over the list of handlers and breaking the loop once stopPropagation has been called on the event. Having a standard compose type function that composes a list of hook return values (i.e., it knows how to combine attributes, listeners and classes in a reactive way) would be a good way to do that.
What do you think @krysal? I've also chatted briefly with @diegohaz, the maintainer of Ariakit sometime earlier this year about contributing a Vue implementation. Working in Ariakit to make the baseline changes necessary to make Ariakit able to also house a Vue implementation (this mostly comes down to removing React as a base dependency from the base Ariakit packages) could be another good path to follow for this. It would just benefit us less immediately because it would take longer to be able to use that (much more up-front work). Having a standalone Vue implementation might be fine for now though... however Ariakit has undergone some big refactors. Maybe it'd be better to wait until we know Ariakit's API is more stable, even though there will inherently be differences between the React and Vue (and any other framework) version.

Closing this PR. We can and should continue this work but in smaller discrete chunks as Krystle suggested.


SSL certificate expired for https://research.edm.uhasselt.be/jori/jrtplib

Josephs-MacBook-Pro:~ joe$ curl -ILvvv https://research.edm.uhasselt.be/jori/jrtplib
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to research.edm.uhasselt.be (<IP_ADDRESS>) port 443 (#0)
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /usr/local/etc/openssl/cert.pem
  CApath: /usr/local/etc/openssl/certs
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (OUT), TLS alert, Server hello (2):
* SSL certificate problem: certificate has expired
* Closing connection 0
curl: (60) SSL certificate problem: certificate has expired
More details here: https://curl.haxx.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
Josephs-MacBook-Pro:~ joe$

Should be resolved


Strange HFO results - need to rethink min model error

In the early years of the HFO inversions, InTEM and ELRIS have almost zero emissions, while RHIME estimates substantial emissions for the whole time period, even though the obs show very few enhancements. The model error also looks wrong for RHIME in early years. Will elaborate on this further once I've investigated...

OK I think I know (at least partially) what the problem is here. For the HFO runs we are using the same prior for all time, but in the early years there are basically no emissions, so obs are virtually flat and the prior mf timeseries has a lot of variability. This means the stdev(obs-prior_mfs) is large, and hence we apply a large min model error. This means that the posterior mf timeseries is allowed to vary significantly from the obs, in order to reduce the posterior-prior flux map difference. The upshot is that we get a strong influence of the prior in these early years, and the posterior fluxes aren't allowed to go to (near) zero.
I think for now I will have to turn off the min model error for my hfo runs. Going forward it would be good to come up with some other ideas for min model error calculations that would not be so sensitive to errors in the prior emission map.

Thinking about it, this will impact any gas for which we are using a prior map that we don't have much confidence in, so I think it is relevant to the other PARIS runs too.

In the same idea, for gases like HFC-227ea where sporadic pollution events happen, assuming the errors are mean zero is not really accurate (I think..). (y - y_mod) should have an asymmetric distribution and therefore (y - y_mod) - mean(y - y_mod) is not appropriate for this case.

Correction for HFC-227: the current residual error method should be appropriate but may need to be sharpened, for example by calculating a min error for each site instead of one single min error.

In the same idea, for gases like HFC-227ea where sporadic pollution events happen, assuming the errors are mean zero is not really accurate (I think..). (y - y_mod) should have an asymmetric distribution and therefore (y - y_mod) - mean(y - y_mod) is not appropriate for this case.

If this is the case, we might want to use a "robust" distribution for the likelihood instead of a normal distribution. I have a book that recommends using a Student-T distribution, which has longer tails. I think this works by making big pollution events "less unlikely" so they have less influence on the posterior.
Without more time resolution in the flux, I don't think we can capture sporadic events, so I guess the best we can do it not fit to them too much.


some way to select only elements that have a particular event handler

Split from https://github.com/eeue56/elm-html-test/issues/32 by request.
some way to select only elements that have a particular event handler.  In this example, find the div with the onClick handler, and ignore the other divs:
div []
    [ div []
        [ div [ onClick MyMsg ]
            [ div [] [ text "Click me" ] ]
        , div [] []
        ]
    , div [] []
    ]

Possible API:
Query.find [ tag "div", withHandler "click" ]

This seems easy enough to implement, but I'm curious about the use case - are there tests we currently can't write without this?

I'm not sure I understand the question.  The issue shows an example of a test that can't currently be written (find the div that can be clicked without having to know the exact path to that div).

Sorry! Maybe a better way to say it would be: is there a reason searching for the click handler would be better than searching based on the text "Click me", given that this text also uniquely identifies the element we want?
I could see pros and cons of each approach. Searching by text would give a false negative if we changed the text of the button, but searching by click handler would give a false negative if we introduced an unrelated sibling button with different text, which also had a click handler.
All else being equal, I'd rather minimize API surface area and not introduce a new alternative way to do the same thing, so I'm wondering if we've encountered any real-world cases where existing queries (e.g. text queries) fell short, and being able to query based on handlers would have been a significant improvement over e.g. improving how we can do text queries.
Sorry I was less clear previously - does that make sense?

In the example above:

Query.find [ text "Click me" ] finds the text node, which if you try to click it, gives "Found element is a text, which does not produce events, therefore could not simulate click on it."
Query.find [ tag "div" ]  finds all the divs, and there is no way to get the clickable one: "Query.find always expects to find 1 element, but it found 5 instead"
With contains that you proposed elsewhere, Query.find [ tag "div", contains [ text "Click me" ] ] would still not solve this because it would match 3 of the 5 divs, and there would still be no way to get the one of those three that has the click handler.

Cool, thanks for clarifying @avh4! This motivation makes sense to me.
I'm planning to implement this on our next Hackday, which is Friday.
Any objections @eeue56?

👍


Long sliding deacceleration

Some issues I found :

Long sliding after keyboard release. Increasing 'deacceleration value' up to 1000 has no effect
Rarely produce null animation on movement 00:21
Crouch animation becoming jump without linear velocity.

https://github.com/ywmaa/Advanced-Movement-System-Godot/assets/16588932/5cef8da5-899a-4879-bb9f-877dc5457e8a
Step I use

Clone from master branch the date I write (0.9). It tested under godot 4.0.3-stable and 4.1.2-custom
using WASD keyboard for movement, Shift to run, Shift again to sprint. See video above

Thank you for your input,
I will check the last two issues myself.
For the sliding problem, are you using RigidBody3D or CharacterBody3D ?

I fixed 2 & 3, please check out latest commit.
also I can't really reproduce the very long sliding that happens for you.

To be sure that you change the deacceleration, change the value in CharacterMovementComponent, not the KinematicPlayer3D.
Closing this issue for now.
Reopen if issues still exist.


How to deal with days when the markets are closed

I'm trying to create a function that, given a ticker and a date, returns the close price of that ticker on that day. I'm having troubles in dealing with days when the markets are closed (saturdays and sundays, holidays etc...).
My goal is to return the value of the previous trading day (e.g. if I pass either a saturday or a sunday, it returns the value of the previous friday). However there's an annoying error message that I can't seem to get rid of. Also, the following solution is not that elegant.
Is it possible to add some flag whose default value is False, but if set to True it makes yf.Ticker follow the behaviour I just described?
This is my current implementation:
#!/usr/bin/env python3

import yfinance as yf
from datetime import date, timedelta

def price_at_close(ticker: str, date: date) -> float:
  """
  Returns the price of a given stock at market close of a given date. If the
  markets were closed on that day (e.g. Saturdays and Sundays, Holidays, etc.)
  it returns the close price of the previous trading day.
  """
  try:
    return float(yf.Ticker(ticker).history(start=date,
                                           end=date,
                                           rounding=2).Close)
  except:
    return price_at_close(ticker, date - timedelta(days=1))

if __name__ == "__main__":
  print(price_at_close("AMD", date(2020, 12, 25)))
  print(price_at_close("AMD", date(2020, 12, 26)))

which outputs:
91.81
- AMD: No data found for this date range, symbol may be delisted
91.81

What happens if you make it recursively invoke itself on the prior day if that exception occurs?

Thanks for posting. Something similar would come in handy. The code below fixes some bugs above. The error message meant the dataframe was empty, so you need to subtract days from end date. Then date need to be datetime.
def price_at_close(ticker: str, date: datetime, prices=None) -> float:
    """
    Returns the price of a given stock at market close of a given date. If the
    markets were closed on that day (e.g. Saturdays and Sundays, Holidays, etc.)
    it returns the close price of the previous trading day.
    """
    assert isinstance(date, datetime)
    if prices is None or date < prices.index[0]:
        end = date + timedelta(days=1)
        start = end - timedelta(days=10)
        prices = yf.Ticker(ticker).history(start=start, end=end, rounding=2)
    closep = Try(lambda: prices["Close"][date]).get_result()
    if closep is None:
        return price_at_close(ticker, date - timedelta(days=1), prices=prices)
    else:
        return closep

Thanks for posting. Something similar would come in handy. The code below fixes some bugs above. The error message meant the dataframe was empty, so you need to subtract days from end date. Then date need to be datetime.
def price_at_close(ticker: str, date: datetime, prices=None) -> float:
    """
    Returns the price of a given stock at market close of a given date. If the
    markets were closed on that day (e.g. Saturdays and Sundays, Holidays, etc.)
    it returns the close price of the previous trading day.
    """
    assert isinstance(date, datetime)
    if prices is None or date < prices.index[0]:
        end = date + timedelta(days=1)
        start = end - timedelta(days=10)
        prices = yf.Ticker(ticker).history(start=start, end=end, rounding=2)
    closep = Try(lambda: prices["Close"][date]).get_result()
    if closep is None:
        return price_at_close(ticker, date - timedelta(days=1), prices=prices)
    else:
        return closep

@totekp What's Try?

@totekp What's Try?

It's a handy monad. You can implement it or replace it with code that checks prices contains the date.

It's a handy monad. You can implement it or replace it with code that checks prices contains the date.

Thanks for the code snippeds above. I've simplified it to just check back for the current day and the last 7 days to see when we had a closing price, then take that the price.
def price_at_close(ticker: str, date: datetime) -> float:
    end = date + timedelta(days=1)
    start = end - timedelta(days=10)
    prices = yf.Ticker(ticker).history(start=start, end=end, rounding=2)
    for i in range(7):
        if date - timedelta(days=i) in prices['Close'].keys():
            print(f"Close price displayed {date-timedelta(days=i)}")
            return prices['Close'][date - timedelta(days=i)]


Dynamic eum host

Add ability to set the EUM host dynamically via environment variable.
The EUM host is necessary for loading the boomerang-scripts in the browser as well as exporting beacons and spans.

Wrong repository


⚠ Bofrost.at has degraded performance

In 3d51dcd, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1473 ms

Resolved: Bofrost.at performance has improved in cdebecf after 28 minutes.


Install error with setup.py, memory leak?

`[ 71%] Linking CXX executable stl_logging_unittest
[ 71%] Built target stl_logging_unittest
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions.
esp/core/CMakeFiles/core.dir/build.make:62: recipe for target 'esp/core/CMakeFiles/core.dir/esp.cpp.o' failed
make[2]: *** [esp/core/CMakeFiles/core.dir/esp.cpp.o] Error 4
CMakeFiles/Makefile2:5462: recipe for target 'esp/core/CMakeFiles/core.dir/all' failed
make[1]: *** [esp/core/CMakeFiles/core.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions.
deps/assimp/code/CMakeFiles/assimp.dir/build.make:1700: recipe for target 'deps/assimp/code/CMakeFiles/assimp.dir/Importer/IFC/IFCReaderGen2_2x3.cpp.o' failed
make[2]: *** [deps/assimp/code/CMakeFiles/assimp.dir/Importer/IFC/IFCReaderGen2_2x3.cpp.o] Error 4
make[2]: *** Waiting for unfinished jobs....
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions.
deps/corrade/src/Corrade/PluginManager/CMakeFiles/CorradePluginManager.dir/build.make:62: recipe for target 'deps/corrade/src/Corrade/PluginManager/CMakeFiles/CorradePluginManager.dir/AbstractManager.cpp.o' failed
make[2]: *** [deps/corrade/src/Corrade/PluginManager/CMakeFiles/CorradePluginManager.dir/AbstractManager.cpp.o] Error 4
CMakeFiles/Makefile2:3004: recipe for target 'deps/corrade/src/Corrade/PluginManager/CMakeFiles/CorradePluginManager.dir/all' failed
make[1]: *** [deps/corrade/src/Corrade/PluginManager/CMakeFiles/CorradePluginManager.dir/all] Error 2
[ 71%] Linking CXX executable example
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions.
deps/assimp/code/CMakeFiles/assimp.dir/build.make:1466: recipe for target 'deps/assimp/code/CMakeFiles/assimp.dir/OgreXmlSerializer.cpp.o' failed
make[2]: *** [deps/assimp/code/CMakeFiles/assimp.dir/OgreXmlSerializer.cpp.o] Error 4
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions.
deps/assimp/code/CMakeFiles/assimp.dir/build.make:1453: recipe for target 'deps/assimp/code/CMakeFiles/assimp.dir/OgreBinarySerializer.cpp.o' failed
make[2]: *** [deps/assimp/code/CMakeFiles/assimp.dir/OgreBinarySerializer.cpp.o] Error 4
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions.
deps/assimp/code/CMakeFiles/assimp.dir/build.make:1752: recipe for target 'deps/assimp/code/CMakeFiles/assimp.dir/Importer/IFC/IFCProfile.cpp.o' failed
make[2]: *** [deps/assimp/code/CMakeFiles/assimp.dir/Importer/IFC/IFCProfile.cpp.o] Error 4
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions.
deps/assimp/code/CMakeFiles/assimp.dir/build.make:972: recipe for target 'deps/assimp/code/CMakeFiles/assimp.dir/ASELoader.cpp.o' failed
make[2]: *** [deps/assimp/code/CMakeFiles/assimp.dir/ASELoader.cpp.o] Error 4
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions.
deps/assimp/code/CMakeFiles/assimp.dir/build.make:1193: recipe for target 'deps/assimp/code/CMakeFiles/assimp.dir/LWOBLoader.cpp.o' failed
make[2]: *** [deps/assimp/code/CMakeFiles/assimp.dir/LWOBLoader.cpp.o] Error 4
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions.
deps/assimp/code/CMakeFiles/assimp.dir/build.make:738: recipe for target 'deps/assimp/code/CMakeFiles/assimp.dir/DeboneProcess.cpp.o' failed
make[2]: *** [deps/assimp/code/CMakeFiles/assimp.dir/DeboneProcess.cpp.o] Error 4
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions.
deps/assimp/code/CMakeFiles/assimp.dir/build.make:114: recipe for target 'deps/assimp/code/CMakeFiles/assimp.dir/ImporterRegistry.cpp.o' failed
make[2]: *** [deps/assimp/code/CMakeFiles/assimp.dir/ImporterRegistry.cpp.o] Error 4
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions.
deps/assimp/code/CMakeFiles/assimp.dir/build.make:2285: recipe for target 'deps/assimp/code/CMakeFiles/assimp.dir/X3DImporter_Geometry2D.cpp.o' failed
make[2]: *** [deps/assimp/code/CMakeFiles/assimp.dir/X3DImporter_Geometry2D.cpp.o] Error 4
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions.
deps/assimp/code/CMakeFiles/assimp.dir/build.make:1271: recipe for target 'deps/assimp/code/CMakeFiles/assimp.dir/MD5Loader.cpp.o' failed
make[2]: *** [deps/assimp/code/CMakeFiles/assimp.dir/MD5Loader.cpp.o] Error 4
[ 71%] Built target example
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions.
deps/assimp/code/CMakeFiles/assimp.dir/build.make:907: recipe for target 'deps/assimp/code/CMakeFiles/assimp.dir/AMFImporter_Postprocess.cpp.o' failed
make[2]: *** [deps/assimp/code/CMakeFiles/assimp.dir/AMFImporter_Postprocess.cpp.o] Error 4
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions.
deps/assimp/code/CMakeFiles/assimp.dir/build.make:829: recipe for target 'deps/assimp/code/CMakeFiles/assimp.dir/Importer/StepFile/StepFileGen2.cpp.o' failed
make[2]: *** [deps/assimp/code/CMakeFiles/assimp.dir/Importer/StepFile/StepFileGen2.cpp.o] Error 4
[ 71%] Linking CXX static library libMagnum.a
[ 71%] Built target Magnum
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions.
deps/assimp/code/CMakeFiles/assimp.dir/build.make:1791: recipe for target 'deps/assimp/code/CMakeFiles/assimp.dir/Importer/IFC/IFCOpenings.cpp.o' failed
make[2]: *** [deps/assimp/code/CMakeFiles/assimp.dir/Importer/IFC/IFCOpenings.cpp.o] Error 4
[ 71%] Linking CXX executable logging_unittest
[ 71%] Built target logging_unittest
/home/yzhao/ProjectFolder/Unsupervised_depth_prediction/habitat-sim/src/deps/assimp/code/LWOMaterial.cpp: In member function ‘bool Assimp::LWOImporter::HandleTextures(aiMaterial*, const TextureList&, aiTextureType)’:
/home/yzhao/ProjectFolder/Unsupervised_depth_prediction/habitat-sim/src/deps/assimp/code/LWOMaterial.cpp:141:9: warning: ‘mapping’ may be used uninitialized in this function [-Wmaybe-uninitialized]
if (mapping != aiTextureMapping_UV) {
^
[ 71%] Built target MagnumShadersObjects
/home/yzhao/ProjectFolder/Unsupervised_depth_prediction/habitat-sim/src/deps/assimp/code/MDLLoader.cpp: In member function ‘void Assimp::MDLImporter::InternReadFile_Quake1()’:
/home/yzhao/ProjectFolder/Unsupervised_depth_prediction/habitat-sim/src/deps/assimp/code/MDLLoader.cpp:423:116: warning: ‘pcFirstFrame’ may be used uninitialized in this function [-Wmaybe-uninitialized]
BE_NCONST MDL::Vertex* pcVertices = (BE_NCONST MDL::Vertex*) ((pcFirstFrame->name) + sizeof(pcFirstFrame->name));
^
[ 71%] Linking C executable inputlag
[ 71%] Linking C executable joysticks
[ 71%] Linking C executable opacity
[ 71%] Built target inputlag
[ 71%] Built target joysticks
[ 71%] Built target opacity
[ 71%] Linking C executable gamma
[ 71%] Built target gamma
CMakeFiles/Makefile2:1469: recipe for target 'deps/assimp/code/CMakeFiles/assimp.dir/all' failed
make[1]: *** [deps/assimp/code/CMakeFiles/assimp.dir/all] Error 2
Makefile:151: recipe for target 'all' failed
make: *** [all] Error 2
Traceback (most recent call last):
File "setup.py", line 325, in
zip_safe=False,
File "/home/yzhao/.local/lib/python3.6/site-packages/setuptools/init.py", line 145, in setup
return distutils.core.setup(**attrs)
File "/usr/lib/python3.6/distutils/core.py", line 148, in setup
dist.run_commands()
File "/usr/lib/python3.6/distutils/dist.py", line 955, in run_commands
self.run_command(cmd)
File "/usr/lib/python3.6/distutils/dist.py", line 974, in run_command
cmd_obj.run()
File "/home/yzhao/.local/lib/python3.6/site-packages/setuptools/command/install.py", line 67, in run
self.do_egg_install()
File "/home/yzhao/.local/lib/python3.6/site-packages/setuptools/command/install.py", line 109, in do_egg_install
self.run_command('bdist_egg')
File "/usr/lib/python3.6/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/usr/lib/python3.6/distutils/dist.py", line 974, in run_command
cmd_obj.run()
File "/home/yzhao/.local/lib/python3.6/site-packages/setuptools/command/bdist_egg.py", line 172, in run
cmd = self.call_command('install_lib', warn_dir=0)
File "/home/yzhao/.local/lib/python3.6/site-packages/setuptools/command/bdist_egg.py", line 158, in call_command
self.run_command(cmdname)
File "/usr/lib/python3.6/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/usr/lib/python3.6/distutils/dist.py", line 974, in run_command
cmd_obj.run()
File "/home/yzhao/.local/lib/python3.6/site-packages/setuptools/command/install_lib.py", line 11, in run
self.build()
File "/usr/lib/python3.6/distutils/command/install_lib.py", line 109, in build
self.run_command('build_ext')
File "/usr/lib/python3.6/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/usr/lib/python3.6/distutils/dist.py", line 974, in run_command
cmd_obj.run()
File "setup.py", line 166, in run
self.build_extension(ext)
File "setup.py", line 220, in build_extension
shlex.split("cmake --build {}".format(self.build_temp)) + build_args
File "/usr/lib/python3.6/subprocess.py", line 311, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['cmake', '--build', 'build', '--config', 'RelWithDebInfo', '--', '-j']' returned non-zero exit status 2`

Never mind. I saw this closed issue, and it worked for me.

Now I'm pretty sure this should be the bug in recent version. Since this error happens even in docker, and after I add

git checkout 62bc01be8cbc148eb099e96fa0b123e16b21f95f

It works well.

It even try to use my swap memory... Guess memory leaking in some place

@placeforyiming how many CPU cores do you have? The compiler getting killed due to running out of memory is actually a quite possible scenario -- pybind11 python bindings code sometimes causes the compiler to consume extreme amounts of RAM, I encountered up to 2 GB per instance with GCC 8 and IIRC some older versions of GCC were consuming even more.
In #38 we added an option to specify max number of parallel instances. Can you run setup.py with e.g. --parallel 2, if it helps anything?

I have 12 cores in my computer. The ubuntu system in my computer uses 1G RAM as swap memory which may cause this problem, guess hard disk is a more popular choice? I didn't install the system by myself, not sure how they did that part.
I tried  sudo python3 setup.py install  --parallel 2 and  sudo python3 setup.py --parallel 2 install
but neither worked. Guess this is not the right way to pass argument.
I also see  python setup.py build_ext --build-temp=build --parallel 3 from #38 , but didn't try this one, since I'm not sure if this is the same as python setup.py install .
Inspired by #24 , I changed 'j' to 'j6' in line 200, a little bit backward, but finally solved my problem.

Yeah, it's a bit hard to get right: --parallel is an option of the build_ext command, so to do it all in one step you'd do this, I think:
python setup.py build_ext --parallel 3 install

Alternatively, Ctrl C during the build, cd into the build/ directory and run either make -jN or ninja -jN there, then once that's done, resume python setup.py install -- it'll pick up the already built libraries. That's also generally the most flexible way to fiddle with CMake parameters and such.


Disable tracing on empty traces_sample_rate

Noticed we can probably disable the tracing completely if the traces_sample_rate is 0.0 since there would be no chance to send a trace to Sentry which would negate any performance impact the tracing code could have on an application.
Looking at this code do we want to collect the trace data anyway even if we already know the sample rate is 0 and thus the trace will not be sent or is the traces_sampler option supposed to be able to override that later? Because then this PR might not be good...
Bottom line, if the traces_sample_rate === 0.0 should we even collect tracing data?
Yes = Merge, No = Close 😉

Tricky, PHP is a bit unique in that regard since it basically has no persistence in any way between requests. So it should be ok to do it. But let's wait a bit until we gathered more feedback to release this.

After consideration and looking at real world performance data I have decided to postpone this until actually needed since currently the impact is close to 0 and the impact with all the ways tracing can be sampled it's not worth it right now.


[N64 Bug Fix Request] Sims having infinite length with the Laser's secondary function Short Range Stream

Correct sims having infinite range with the Short Range Stream function of the laser, where they can keep it as a solid beam while damaging you from across a whole map's length.
https://github.com/fgsfdsfgs/perfect_dark/assets/66316465/fbef6d3a-b165-4929-b7dc-0a4a7347c1e1

God damn it, wrong issue number.

this seems to happen alot

Was that a darksim? Because the game states the Dark sims will cheat.
https://github.com/fgsfdsfgs/perfect_dark/assets/142272040/f2d1fc51-6dbc-4e7e-b9c2-9b8fd93187aa

While it's true DarkSims blatantly cheat and that's their nature... the sim in my video was an a FistSim on easy lol. The developers seemingly didn't apply the same restrictions on sim's lasers as player's ones, so any simulant can utilize the solid 'short range beam' across an entire map's length. Has always been annoying!


setting highlighting seems broken... again.

Clicking on the links in the beta thread does not result in the setting being highlighted: http://i.imgur.com/L9uya38.png
https://www.reddit.com/#?tbsettings=modbutton&setting=showinusernamearea Non-markdown links seem to work fine.  But markdown ones are broken.  IE: the ones in this thread: https://www.reddit.com/r/tb_beta/comments/3rr1fp/preliminary_33_changelog/

Nothing to see here.


Unable to get city information for any photos

I've recently tried using elodie on the current month's photos and it seems that nothing I do can get the "city" attribute to appear in the path.   Using another exiftool front end I've set "City", they've all got valid GPS coordinates, but any attempt to use "%city" in the path results in either "Unknown Location" if I use it by itself, or just the state (and possibly country) if I use it in conjunction with them.
eg:
EXIF data:
PSLatitude                     : 37 deg 53' 58.21" S
GPSLatitudeRef                  : South
GPSLongitude                    : 145 deg 4' 52.17" E
GPSLongitudeRef                 : East
GPSPosition                     : 37 deg 53' 58.21" S, 145 deg 4' 52.17" E
City                            : Hughesdale
Sub-location                    : Hughesdale
Province-State                  : Victoria
Country-PrimaryLocationCode     : AUS
Country-PrimaryLocationName     : Australia
config.ini
[Directory]
year=%Y
date=%Y-%m-%d
location=%city, %state, %country
full_path=%year/%date/%location|"Unknown Location"
Results in filesystem:
"Photos/2018/2018-03-19/Victoria, Australia"

Further investigation, it looks as though MapQuest never send City information on any coords within Australia.  Any chance of supporting api.geonames.org as a lookup source?

I'm not familiar with api.geonames.org. It would not be too difficult to support another API.
geolocation.lookup and geolocation.place_name are the two function which would need to be overloaded.


Meteo Control - Missing targetare link

ENVIRONMENT: production
Browser: Chrome
Device: Laptop
OS: Windows 10
STEPS TO REPRODUCE:
Open the https://scrapers.peviitor.ro/src/meteocontrol/index.html in browser.
Hover over the company's logo.
There is a functioning 'Targetare' button (with link) just under the 'Careers' one.
Click on "Targetare.ro".
EXPECTED RESULTS:
The company logo is visible in the square in the middle of the page.
There is a functioning 'Targetare' button (with link) just under the 'Careers' one.
ACTUAL RESULTS:
There is no 'Targetare' button.

Ai verificat pe targetare.ro sa vezi daca compania exista?

AM verificat si meteo control nu e.


List Specific Columns

I'm familiar with the gdrive list command and how it can be used to show files inside a directory.
An example of which is as follows:
gdrive list --query " 'DIRECTORY ID' in parents"
By default, this returns columns for ID, Name, Type, Size and Created.
Is there a way to limit this so, for example, I only get a list of file names and dates that they were created?

Option is currently not built-in. You can pipe the output to awk to select specific columns and column to pretty-print them.
For example to get only names and creation dates you can use:
gdrive list --query " 'DIRECTORY ID' in parents" | awk -F" {2,}" '{print $2 "#" $NF}' | column -ts'#'

Explanation of command: pipe output of list to awk, separate columns only if there are 2 or more spaces (-F" {2,}") to support filenames with spaces. Select the 2. and last columns ($2 and $NF), print them separated by pound sign then pretty-print it using column command and "#" as separator


responses

Adds typed responses. I was going to do a writeup, but responses.test.ts is I think the best way to see how it works :)

@codetheweb as per slack discussion, I moved back to the old mutable middleware model with next function


⚠ Bofrost.de has degraded performance

In 40d2d81, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1221 ms

Resolved: Bofrost.de performance has improved in d80cd5e.


Improve traceability of accountable memory usage for expensive queries

Problem Statement
If a cluster is under high query load, users can run into CircuitBreakingException. In case the total circuit breaker trips (indices.breaker.total.limit), users will see certain queries failing, but those are not necessarily the most expensive queries. There can be other (long-running) heavy queries that occupy large portions of memory, but are still below the (total) circuit breaker limits. Users may then start seeing relatively cheap queries failing.
As a user, I want to have an easy way to diagnose what queries are currently occupying (or have recently occopied) what amount of memory that is accountable for the total circuit breaking.
Besides troubleshooting circuit breaker exceptions, such a metric can also help to proactively review expensive queries before running into total circuit breaker exceptions.
Possible Solutions
There could be different solutions.

Use existing sys.operations(_log) tables
There already is a used_bytes column in sys.operations(_log). Would SELECT job_id, SUM(used_bytes) FROM sys.operations be an accurate representation of peak total accountable memory usage per query?
If yes, it could be documented in Diagnostics with System Tables.

Add a new field to sys.jobs(_log)
If there is no metric exposing the peak accountable memory usage of a query, a new field could be added to sys.jobs(_log).

Considered Alternatives
No response

Would SELECT job_id, SUM(used_bytes) FROM sys.operations be an accurate representation of peak total accountable memory usage per query?

Yes, that is what it is designed for. If it is not working as expected, it would be a bug.

If yes, it could be documented in Diagnostics with System Tables.


lens: hovering over [download json] button could show REST url to fetch trace

Feature:
When hovering over the download json button, it seems intuitive to show the full link to the trace (ie http://myhost/api/v2/trace/4f711e17e7e2290a) , in the browser status bar just as if you would hover over a normal href.
Rational
I could not remember the location of the swagger api definition at https://zipkin.io/zipkin-api/ , i wanted to fetch a trace using curl | jq . So i looked at the download button hoping to find the REST url there.

I love how this idea will both improve UX a bit and remove a significant amount of complexity from the code, thanks!


use poetry for publication

Signed-off-by: Chris Trevino<EMAIL_ADDRESS>

Fixes #
Changes proposed in this pull request:

Use poetry 1.2 in main.yml
Use poetry to install dynamic versioning plugin. This is the recommended method for 1.2.0+
Use poetry publish in release task

Before submitting

[X] I've read and followed all steps in the Making a pull request
section of the CONTRIBUTING docs.

After submitting

[ ] All GitHub Actions jobs for my pull request have passed.

Codecov Report

Merging #47 (110bca1) into main (940828c) will decrease coverage by 8.03%.
The diff coverage is 10.25%.

:exclamation: Current head 110bca1 differs from pull request most recent head 818386b. Consider uploading reports for the commit 818386b to get more accurate results

@@            Coverage Diff             @@
##             main      #47      +/-   ##
==========================================
- Coverage   75.21%   67.17%   -8.04%
==========================================
  Files          11       12       +1
  Lines         585      655      +70
  Branches      116      125       +9
==========================================
  Hits          440      440
- Misses        104      174      +70
  Partials       41       41

Impacted Files
Coverage Δ

dodiscover/ci/g_test.py
63.63% <ø> (ø)

dodiscover/constraint/_classes.py
0.00% <0.00%> (ø)

dodiscover/constraint/skeleton.py
70.51% <ø> (ø)

dodiscover/_protocol.py
61.53% <100.00%> (ø)

dodiscover/ci/oracle.py
86.95% <100.00%> (ø)

dodiscover/constraint/utils.py
46.15% <100.00%> (ø)

dodiscover/context.py
67.39% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


PSX games - On Retroarch it works but not on ES

I choose the core and the bios directory for a psx game and it works on retroarch. But if i want to play the game in ES it goes back to the menu.

Check your config files... copy the exact command and see if it works in a RUN command box...
These problems come from the es_systems file...

yeah my config was messed up. the bios path was wrong. but could you please show me an example how i run a command in the command box?


FIRST commit

It's great that you're learning how to use GitHub!
For the future, please experiment with commits and pull requests in your own repository. Hundreds of people get notified about every update to this project and your testing causes noise for these people, including maintainers. 🙇


Freeze on attempting to start Overwatch 2 from Steam

Hyprland Version
 System/Version info
Hyprland, built from branch main at commit 90a53aed59be6bac45c13eac954471d56ac23375  (CrashReporter: fix deadlocks by making it mostly async-signal-safe (5771)).
Date: Sat Apr 27 12:38:48 2024
Tag: v0.39.1-90-g90a53aed, commits: 4550

flags: (if any)

System Information:
System name: Linux
Node name: linux-pc
Release: 6.8.7-arch1-2
Version: #1 SMP PREEMPT_DYNAMIC Fri, 19 Apr 2024 09:51:31 +0000

GPU information:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA104 [GeForce RTX 3070] [10de:2484] (rev a1) (prog-if 00 [VGA controller])

os-release: NAME="EndeavourOS"
PRETTY_NAME="EndeavourOS"
ID="endeavouros"
ID_LIKE="arch"
BUILD_ID="2023.11.17"
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://endeavouros.com"
DOCUMENTATION_URL="https://discovery.endeavouros.com"
SUPPORT_URL="https://forum.endeavouros.com"
BUG_REPORT_URL="https://forum.endeavouros.com/c/arch-based-related-questions/bug-reports"
PRIVACY_POLICY_URL="https://endeavouros.com/privacy-policy-2"
LOGO="endeavouros"

plugins:
  hyprexpo by Vaxry ver 1.0
  XWayland Primary Display by Zakk ver 1.0

Bug or Regression?
Bug
Description
When I try to start Overwatch 2, Hyprland freezes and the entire system locks up, requiring a hard reboot to get back in.
I've done a git bisect and it seems to be caused by the latest commit, 90a53a.
How to reproduce

Start Hyprland
Start Steam
Start Overwatch 2

Crash reports, logs, images, videos
hyprland.log

@virchau13 as the regressor, any thoughts?

also please test without plugins

Still happens when plugins are disabled.
However, without hyprXPrimary managing my xrandr primary monitor, I did notice that Hyprland only crashes if I set the primary monitor for xwayland with  xrandr --output DP-1 --primary. If I leave xrandr as-is, Overwatch launches fine (albeit still unusable because the resolution is set to my other monitor's resolution).

sooo... hyprland crashes and deadlocks most likely...? odd because the commit shouldnt change anything outside of the actual cases when you've already crashed

from my understanding hyprland has a bug with wine applications being full screened

@virchau13 as the regressor, any thoughts?

My commit only affects the handleUnrecoverableSignal() code path, so I highly doubt it's the reason for the crash.
I suspect that there was some type of memory corruption bug already present in the codebase, and the reshuffling of addresses caused by my change just made it way easier to trigger.
@derethil can you try (ideally with a debug-compiled version of Hyprland):

Start Overwatch 2
Wait for deadlock
Wait 15 seconds. If Hyprland doesn't automatically close after 15 seconds, then this is not a crash handler deadlock.
If your Hyprland is still frozen, press SysRq+R and then Ctrl+Alt+F3 to switch to a new TTY. (SysRq+R takes the keyboard back from Hyprland.)
Run sudo gdb -p $(pgrep Hyprland) to attach gdb to the Hyprland process.
Run backtrace.
Send it here.

I can't seem to reproduce it in a debug-compiled version of Hyprland, which is.... odd lol.
I'm not sure if a non debug-compiled Hyprland version will be of any use, but backtrace showed this:
backtrace.txt
Additionally, when I was trying to do all of that at one point Hyprland actually did crash (not freeze) upon starting Overwatch. So here's that crashlog, if that's helpful.
hyprlandCrashReport7197.txt

Overwatch 2 no longer randomly crashes.

proton 9.0 regression

This is no longer happening after updating to v0.40 so I'll close this and re-open if it appears again.


Document Firebase Storage integration

Add proper documentation for how to use FirebaseUI Storage.

I believe this was fixed by #324


[github-actions] job queue stalled

Initial response from GitHub Support:

We've escalated this to our Actions engineers for investigation and will follow up as soon as we have an update.

Update from GitHub Support:

To provide an update, our engineers have identified the cause of this issue and implemented a fix.
You should now see the queued jobs start to get processed. There are quite a few jobs in the queue across your enterprise so it may take a little while to catch up.


Different StringEnumConverter-Behavior between STJ / Newtonsoft

Switching my project from Newtonsoft to STJ, I noticed the following different behavior between the two scheme generators:
Adding the JsonStringEnumConverter makes Swashbuckle aware of enums being serialized as string - so far, so good. But the STJ schema builder doesn't seam to be aware of IDictionary<[Enum], int>.
For Newtonsoft the following scheme was generated:
...
"properties": {
  "EnumValue1": {
	"type": "integer",
	"format": "int32"
  },
  "EnumValue2": {
	"type": "integer",
	"format": "int32"
  },
  "EnumValue3": {
	"type": "integer",
	"format": "int32"
  }
},
"additionalProperties": false,
...

Now I only get
"additionalProperties": {
  "type": "integer",
  "format": "int32"
},

So it's still being recognized as an object containing integer properties. Better than nothing. But the old scheme was way more explicit.

This might be related to https://github.com/dotnet/runtime/issues/47765 and this comment:
https://github.com/domaindrivendev/Swashbuckle.AspNetCore/blob/a17b464184d4043c559e74e2c0d8596d7685cf63/src/Swashbuckle.AspNetCore.SwaggerGen/SchemaGenerator/JsonSerializerDataContractResolver.cs#L60-L67
It's possible this is fixed by #2799, otherwise we might have to see if there's any changes needed to if the assertion in that comment is no longer true.

You may have to opt-in to this behaviour with JsonSerializerOptions.DictionaryKeyPolicy.

I could sure support here with a PR :) Can you give me a hint where to start?

I'm not sure where specifically without starting to debug it myself.


TypeError: argument of type 'Word2Vec' is not iterable

running command: python main.py --dataset yelp --sup_source docs --model cnn
i'm getting this error: ### Input preparation ###
Loading existing Word2Vec model ./yelp/embedding...
Traceback (most recent call last):
File "main.py", line 185, in
embedding_weights = train_word2vec(x, vocabulary_inv, args.dataset)
File "main.py", line 46, in train_word2vec
for key, word in vocabulary_inv.items()}
File "main.py", line 46, in
for key, word in vocabulary_inv.items()}
TypeError: argument of type 'Word2Vec' is not iterable

Hello,  I have met the same problem. Have you solve this problem?

@zengjl20 No. I went with conWea instead of this.

I met the same problem. In my case, changing "embedding_model" to "embedding_model.wv" in line 46 of 'main.py' solved my problem.


CTC-1027 import content model samples

Motivation
https://kentico.atlassian.net/browse/CTC-1027
Checklist

[ ] Code follows coding conventions held in this repo
[ ] Tests are passing
[ ] Documentation has been updated (if applicable)
[ ] Temporary settings (e.g. project ID used during development and testing) have been reverted to defaults

How to test
If manual testing is required, what are the steps?

Looks fine. Much better with unified whitespace. 👌


[BUG] BlobBaseClient.DownloadTo(string path) download >256MB or 0 size blob fail

Describe the bug
Download a >256MB (say 300MB) or 0 size block blob Fail with Track2 SDK API BlobBaseClient.DownloadTo().
public virtual Response DownloadTo(string path, CancellationToken cancellationToken);
Expected behavior
download should success
Actual behavior (include Exception or Stack Trace)
Download 0 size: fail with: 416 “The range specified is invalid for the current size of the resource.”
Downalod 300MB fail after retry 6 times, each time only download 256MB with return code 206.
To Reproduce
Steps to reproduce the behavior (include a code snippet, screenshot, or any additional information that might help us reproduce the issue)

Create a blob with 0 size, create another blob with 300MB
Try to download the blobs to local files with BlobBaseClient.DownloadTo(string path)

Compare network trace of Track2 SDK and Track1 SDK, we can see Track2 SDK has an additional Header “x-ms-range: bytes=0-268435455”.
Network Trace
Size 300MB (downloaded content is hide since too long.)

Track 2 SDK (retry 6 time, all fail same, following is one retry):

GET https://***.blob.core.windows.net/weitest/300 HTTP/1.1
x-ms-version: 2019-12-12
x-ms-range: bytes=0-268435455
x-ms-client-request-id: c5ddf65b-2e88-409c-b687-2089408595c4
x-ms-return-client-request-id: true
User-Agent: azsdk-net-Storage.Blobs/12.5.0-dev.20200603.3 (.NET Framework 4.8.4180.0; Microsoft Windows 10.0.18363 )
x-ms-date: Mon, 15 Jun 2020 07:54:18 GMT
Authorization: SharedKey ***:****
Host: ***.blob.core.windows.net
Connection: Keep-Alive

HTTP/1.1 206 Partial Content
Content-Length: 268435456
Content-Type: application/octet-stream
Content-Range: bytes 0-268435455/307200000
Last-Modified: Mon, 15 Jun 2020 07:53:19 GMT
Accept-Ranges: bytes
ETag: "0x8D811012B933EA4"
Server: Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0
x-ms-request-id: f3e3952e-701e-009a-6aea-42d379000000
x-ms-client-request-id: c5ddf65b-2e88-409c-b687-2089408595c4
x-ms-version: 2019-12-12
x-ms-version-id: 2020-06-15T07:53:19.6634788Z
x-ms-is-current-version: true
x-ms-creation-time: Mon, 15 Jun 2020 07:53:19 GMT
x-ms-blob-content-md5: 42e/YSV45GhxbHu/d5X8zA==
x-ms-lease-status: unlocked
x-ms-lease-state: available
x-ms-blob-type: BlockBlob
x-ms-server-encrypted: true
Date: Mon, 15 Jun 2020 07:54:20 GMT

Track1 SDK:

GET https://***.blob.core.windows.net/weitest/300 HTTP/1.1
x-ms-client-request-id: 3c4a727a-6661-46cc-b424-f8812a7363e4
User-Agent: Azure-Storage/11.1.1 (.NET Core; Win32NT 10.0.18363.0)
x-ms-version: 2019-02-02
x-ms-date: Mon, 15 Jun 2020 09:28:49 GMT
Authorization: SharedKey ***:****
Host: ***.blob.core.windows.net

HTTP/1.1 200 OK
Content-Length: 307200000
Content-Type: application/octet-stream
Content-MD5: 42e/YSV45GhxbHu/d5X8zA==
Last-Modified: Mon, 15 Jun 2020 07:53:19 GMT
Accept-Ranges: bytes
ETag: "0x8D811012B933EA4"
Server: Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0
x-ms-request-id: ab23f599-001e-0039-7ef7-42b6bc000000
x-ms-client-request-id: 3c4a727a-6661-46cc-b424-f8812a7363e4
x-ms-version: 2019-02-02
x-ms-creation-time: Mon, 15 Jun 2020 07:53:19 GMT
x-ms-lease-status: unlocked
x-ms-lease-state: available
x-ms-blob-type: BlockBlob
x-ms-server-encrypted: true
Date: Mon, 15 Jun 2020 09:28:49 GMT

Size 0:

Track 2 SDK:

GET https://***.blob.core.windows.net/weitest/testblob HTTP/1.1
x-ms-version: 2019-07-07
x-ms-range: bytes=0-268435455
x-ms-client-request-id: 97f35d91-c05c-401e-b073-480a8dcf580e
x-ms-return-client-request-id: true
User-Agent: azsdk-net-Storage.Blobs/12.4.0 (.NET Framework 4.8.4180.0; Microsoft Windows 10.0.18363 )
x-ms-date: Thu, 11 Jun 2020 06:31:12 GMT
Authorization: SharedKey ***:***
Host: ***.blob.core.windows.net

HTTP/1.1 416 The range specified is invalid for the current size of the resource.
Content-Length: 249
Content-Type: application/xml
Content-Range: bytes */0
Server: Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0
x-ms-request-id: 4137e650-a01e-0099-2fb9-3f321d000000
x-ms-client-request-id: 97f35d91-c05c-401e-b073-480a8dcf580e
x-ms-version: 2019-07-07
x-ms-error-code: InvalidRange
Date: Thu, 11 Jun 2020 06:31:11 GMT

<?xml version="1.0" encoding="utf-8"?><Error>InvalidRange<Message>The range specified is invalid for the current size of the resource.
RequestId:4137e650-a01e-0099-2fb9-3f321d000000
Time:2020-06-11T06:31:12.5196129Z</Message></Error>

Track 1 SDK:

GET https://***.blob.core.windows.net/weitest/testblob HTTP/1.1
x-ms-client-request-id: f4370237-bbca-445c-bba2-d5be0cac02cb
User-Agent: Azure-Storage/11.1.1 (.NET Core; Win32NT 10.0.18363.0)
x-ms-version: 2019-02-02
x-ms-date: Thu, 11 Jun 2020 06:31:43 GMT
Authorization: SharedKey ***:***
Host: ***.blob.core.windows.net

HTTP/1.1 200 OK
Content-Length: 0
Content-Type: application/octet-stream
Content-MD5: 1B2M2Y8AsgTpgAmY7PhCfg==
Last-Modified: Wed, 10 Jun 2020 03:42:15 GMT
Accept-Ranges: bytes
ETag: "0x8D80CF044A95EC8"
Server: Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0
x-ms-request-id: 6a58786f-e01e-0088-80b9-3fa8a9000000
x-ms-client-request-id: f4370237-bbca-445c-bba2-d5be0cac02cb
x-ms-version: 2019-02-02
x-ms-creation-time: Wed, 10 Jun 2020 03:42:15 GMT
x-ms-lease-status: unlocked
x-ms-lease-state: available
x-ms-blob-type: BlockBlob
x-ms-copy-id: 4592bed5-ce14-409d-adb6-bc05f40a1b9c
x-ms-copy-source: https://***.blob.core.windows.net/weitest/test3?versionid=2020-06-05T14:07:47.2661030Z&sv=2019-12-12&se=2020-06-17T03%3A42%3A15Z&sr=bv&sp=r
x-ms-copy-status: success
x-ms-copy-progress: 0/0
x-ms-copy-completion-time: Wed, 10 Jun 2020 03:42:15 GMT
x-ms-server-encrypted: true
Date: Thu, 11 Jun 2020 06:31:44 GMT

Environment:

Name and version of the Library package used: [e.g. Azure.Storage.Blobs 12.2.0]
Azure.Storage.Blobs 12.5.0-dev.20200603.3
Hosting platform or OS and .NET runtime version (dotnet --info output for .NET Core projects): [e.g. Azure AppService or Windows 10 .NET Framework 4.8]

.NET Core SDK (reflecting any global.json):
 Version:   2.2.108
 Commit:    33ed5b90ce

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.18363
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\2.2.108\

Host (useful for support):
  Version: 2.2.6
  Commit:  7dac9b1b51

.NET Core SDKs installed:
  2.2.108 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.2.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.2.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.2.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

IDE and version : [e.g. Visual Studio 16.3]
Visual studio 15.7.4

Hi @blueww, I can repo the size 0 issue, but not the 256 MB+ issue.
I believe your experience with 256MB+ is the requests are timing out.  To sidestep this, I'd recommend something along the lines of:
            using (var resultStream = new MemoryStream(data))
            {
                await blob.DownloadToAsync(
                    resultStream,
                    transferOptions: new StorageTransferOptions
                    {
                        MaximumConcurrency = 4,
                        MaximumTransferSize = 4 * Constants.MB,
                        InitialTransferSize = 4 * Constants.MB
                    });
            }

@blueww, what is your use case for downloading a blob of size 0?

The 300MB issue might be related to https://github.com/Azure/azure-sdk-for-net/issues/11503

@blueww For the 300MB . Did you use OpenRead before? If so then there is slight change of behavior. The stream in track 2 must be disposed after you're done reading it - otherwise it will block connection.
See https://github.com/Azure/azure-sdk-for-net/issues/11503#issuecomment-645014633

I got consistent repro of large file:

Use account that's far away (so that transfer rate is ~5Mbps)
Upload 800MB file
Use DownloadTo(path) or DownloadToAsync(path) (make sure connection is slow).
Make sure to use .NET Framework (not Core)

Here's what's happening:
Download spins up 5 concurrent workers.
ServicePointManager allows 2 connections per host by default.
Requests from 5 concurrent workers get queue up and some of them are timing out (due to slow transfer).
I got it working by either tweaking ServicePointManager or MaxWorkers and disposing stream eagerly in Downloader.
@blueww  things to try:

previous @seanmcc-msft  suggestion to decrease single download size (so it doesn't time out)
Increase connection pool , for example ServicePointManager.DefaultConnectionLimit = 10;
Decrease number of workers

await blockBlobClient.DownloadToAsync(fileName, transferOptions: new StorageTransferOptions
            {
                MaximumConcurrency = 2
            })

@seanmcc-msft , @kasobol-msft
Thanks for investigate this issue!
For 0 size, you can repro it.
For 300MB blob download, I think it's might not related with slow network, but related with the content to download with single request is too big (> 256MB).
The 206 return code should not cause by slow network, but cause by the blob > 256MB, since the Getblob request has header “x-ms-range: bytes=0-268435455”
You can try to repro by BlobBaseClient.DownloadTo(localFileName)

download to a local file path
don't user any transferOptions

Only 1-2 requests runs on same time in the repro, so ServicePointManager.DefaultConnectionLimit should not matter.

For the 300MB download fail, I have discussed with @kasobol-msft online.
It seems my issue is caused by the first request to download timeout (it will download 256MB), and all 6 retries all timeout so failed.
The default timeout for Track2 is 100s. For Track1 SDK it should be longer.
So when we have a slow network, and big chunk size, the first chunk might always fail so the whole blob download fail.
After make the chunk size to 4MB (each request download 4MB content), the issue not repro.
But there are still something need fix:

The documentation should be update for the difference of Track1 and Track2 SDK
The current Track2 Error message is is not clear. We don't see words like "timeout" in it.
0 size blob download fail

@seanmcc-msft  I probably hit this same size=0 issue too, and I view it as a bug, or at the least a doc bug!
My use-case for downloading the blobs is... I have two apps that read and write a common blob. One of them is responsible for creating and populating the blob.
The way it does this is it takes a lease on the blob, to avoid concurrent writes. But it has to have a blob to lease it, so it will create a size 0 blob just to lease it. Then it will eventually write the blob and release the lease.
The other app just tries to read the whole blob, if it exists, without taking a lease, using DownloadToAsync(), at which point it sometimes sees the empty blob, and blows up.
Azure.RequestFailedException: The range specified is invalid for the current size of the resource.
RequestId:db10bf77-001e-0076-4d24-35089f000000
Time:2021-04-19T14:04:36.9772757Z
Status: 416 (The range specified is invalid for the current size of the resource.)
ErrorCode: InvalidRange
Headers:
x-ms-request-id: db10bf77-001e-0076-4d24-35089f000000
x-ms-client-request-id: bec1dea6-8464-4262-9425-be6abda2d39c
x-ms-version: 2019-07-07
x-ms-error-code: InvalidRange
Date: Mon, 19 Apr 2021 14:04:36 GMT
Server: Windows-Azure-Blob/1.0,Microsoft-HTTPAPI/2.0
Content-Length: 249
Content-Range: bytes */0
Content-Type: application/xml
at Azure.Storage.Blobs.BlobRestClient.Blob.DownloadAsync_CreateResponse(ClientDiagnostics clientDiagnostics, Response response)
at Azure.Storage.Blobs.BlobRestClient.Blob.d__0.MoveNext()
at Azure.Storage.Blobs.Specialized.BlobBaseClient.d__45.MoveNext()
at Azure.Storage.Blobs.Specialized.BlobBaseClient.d__44.MoveNext()
at Azure.Storage.Blobs.Specialized.BlobBaseClient.d__43.MoveNext()
at Azure.Storage.Blobs.PartitionedDownloader.d__5.MoveNext()
at Azure.Storage.Blobs.Specialized.BlobBaseClient.d__58.MoveNext()
at Azure.Storage.Blobs.Specialized.BlobBaseClient.d__56.MoveNext()
at Azure.Storage.Blobs.Specialized.BlobBaseClient.d__52.MoveNext()
at Azure.Storage.Blobs.Specialized.BlobBaseClient.d__48.MoveNext()
...and that is the end of what was observed.
My expectation was different. My expectation was that an API like BlobClient.DownloadToAsync() shouldn't blow up with a RequestFailedException just because the blob is empty. It should download an empty blob.
My expectation was formed because I never saw this same issue happen with old storage library, and I wotted not that Azure Storage could respond with 416 for requests to download empty blobs, nor that this might be implied by the verbiage 'A RequestFailedException will be thrown if a failure occurs.'


Error: Unsupported architecture on Linux: arm64

Problem
Environment:

host: macos
via nhost functions locally in docker

On installing the @deno/kv package I get this runtime error
functions-1  | /opt/project/functions/node_modules/@deno/kv/script/_napi_index.cjs:100
functions-1  |         throw new Error(`Unsupported architecture on Linux: ${arch}`)
functions-1  |               ^
functions-1  |
functions-1  | Error: Unsupported architecture on Linux: arm64
functions-1  |     at Object.<anonymous> (/opt/project/functions/node_modules/@deno/kv/script/_napi_index.cjs:100:15)
functions-1  |     at Module._compile (node:internal/modules/cjs/loader:1256:14)

Looking into /opt/project/functions/node_modules/@deno/kv/script/_napi_index.cjs:100 then yes there is no matching package (linux/arm64)
This is the environment you can get in docker in macos.
Solution
Maybe add an automated build for linux/arm64
This architecture is also on e.g. raspberry pi devices.

I was able to build the image on a Raspberry Pi 5:
git clone https://github.com/denoland/denokv.git
cd denokv
docker buildx build -f Dockerfile --platform linux/arm64 -t rpi5/denokv ./

Change rpi5/denokv to whatever image name you prefer.
Build took around 8 minutes.
On an M2 MacBook I've been using the linx/amd64 image with no problem. I get the warning:
denokv The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested

but it still runs fine. Using Docker Desktop 4.28.0 on macOS 14.4. I did try building a native image (same command above) took a few minutes, haven't bothered to test it though.
Raspberry Pi 5:
Linux rpi5 6.6.20+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.20-1+rpt1 (2024-03-07) aarch64 GNU/Linux

Docker version on Pi 5 (install guide):
Client: Docker Engine - Community
 Version:           24.0.7
 API version:       1.43
 Go version:        go1.20.10
 Git commit:        afdd53b
 Built:             Thu Oct 26 09:08:02 2023
 OS/Arch:           linux/amd64
 Context:           default

Running fine on the Pi so far. I'll report back if any problems arise.
Official arm images would be nice now that Deno has offical arm binaries.

Yeah, it's the npm module @deno/kv that doesn't have the architecture. I am using the @deno/kv module from a node.js runtime. I don't have the ability to run my own docker image in this particular development setup, unfortunately.

But thanks for that example to create my own docker image.

That is unfortunately, what is needed to have it?

It's been a while since I looked at this, but it would look something like restoring only the aarch64-unknown-linux-gnu parts out of this: https://github.com/skymethod/kv-connect-kit/commit/6ff39d26deca3ab4a1023d4d2523cd293b7e8bb5
and then add the new arch to scripts/generate_napi_index.ts

Looks like this was resolve in v8.3 https://github.com/denoland/denokv/commit/ee723057db4ee4c8b24f1adf08340d05b98958e3
The GitHub releases page is still on 7.0 but the packages are on 8.3 with a linux/arm64 image.


Go 1.6 support

We know, we know.
Just filing this ticket so people can track our progress on fixing this.

Is there a known issue? I have it running on 1.6 right now.

There is currently unsafe cgo usage. I believe this can be detected setting GODEBUG=cgocheck=2 (the default is 1). We have a fix implemented, we are just musing at this point if it has the right tradeoffs.

Fixed by fb0c387e74932c5ac3da434bfee75e32e7961601


NTR: Bulk Culture Assay Evidence

Term Name: Bulk culture assay evidence
Definition 1: Bulk culture assay evidence is a cell-based assay evidence that can be used to measure populations of cells
Definition 2: Measurement of a population of cells
Parent Term:  Cell-based assay evidence ECO:0001565
References: PMID:30135120, 15862883

We also have an accompanying NTR that is a child of the above term.

Term Name: Optical density measurement of bulk culture assay
Synonym(s): lysis curve
Definition1: optical density measurement of bulk culture assay uses optical density measurements at various wavelengths to monitor cell culture growth
Parent term: Bulk culture assay evidence
Reference: PMID:30135120

Hi @jason-snow58,
Thanks for the NTRs.  I will get on this a.s.a.p.  May I ask what organization or ontology you work for so that I might add it to our "ontology requester" field?
More later...
James

This is for the CACAO course at Texas A&M University.

Thanks @jason-snow58.
James

Hi @jason-snow58 ,
How would this be different from ECO:0001563 (cell growth assay evidence)? And/or how would it relate to it?
Ivan

Pulling in @jimhu-tamu @cross12tamu
@ivanerill in this case we are measuring only the cells that are present, not whether they have grown. Importantly for spec measurements, we aren't always measuring growth, sometimes it is shape change. And for our lysis assays that use the spec, it is the loss of population.
Right now @jason-snow58 is suggesting it be under Cell-based assay evidence ECO:0001565, which put it on the same level as cell growth assay.

Hi everyone,
I am working on some ideas to discuss with the ECO team at our next meeting but in the meantime, I would like some clarification with the NTRs.
First, I would like to point out that where possible, we are trying to get away from 1) catch-all parent terms and 2) generating new terms that differ from established terms on the basis of the protocol used but not the type of evidence and 3) generating single child parents.  So, with that said...
Right now, I am not understanding how the NTR 'bulk cell culture assay evidence' differs from the established term 'cell-based assay evidence' and why it is needed as a parent to the NTR 'optical density measurement of bulk culture assay'.  Couldn't the NTR 'optical density measurement of bulk culture assay' be appropriately placed as a child of 'cell-based assay evidence'?
I am also trying to understand the need for the NTR 'optical density measurement of bulk culture assay'.  The provided definition states that cell growth is what is measured and used as evidence.  Ivan pointed out that 'cell growth assay evidence' would be appropriate, and I agree.  Yet it is then pointed out that "... we aren't always measuring growth, sometimes it is shape change. And for our lysis assays that use the spec, it is the loss of population."  If that is the case, then wouldn't an NTR that addresses cell/colony shape or morphology be more appropriate and if the evidence is the loss of cells in a population, then wouldn't one of the established terms 'cell proliferation assay evidence' or 'cell counting evidence' be appropriate?
Thanks for your patience,
James

I'm not entirely sure I understand all aspects of the NTR, but...
Cell growth assay evidence runs into the problem with growth terms in GO. Cell growth is technically the increase in size and mass of individual cells, not a change in number. As an aside, changes in size and mass can be shrinkage as well as growth, which I think is not reflected in this term (ECO:0001563) and its relatives.
The problem with proposing to use shape or cell number is that optical density measurements of cell cultures (which are actually better described as light scattering measurements) are not directly measuring those properties. If the OD decreases after induction of a lysis protein the experimenter infers that this is due to lysis and a decrease in cell number rather than a shape change. But the OD change per se doesn't tell us that. We bring additional knowledge to the process of making the inference.

Hi @jimhu-tamu ,
So I take it that the right thing to do here (which would catch the existing ECO:0001563 as well as these new terms), would be to rename  ECO:0001563 as "optical density assay", and then derive as needed?
Ivan

@ivanerill, and modify the definition? But then it's a new term.

Also that term would need to specify what is being measured with OD. Things like DNA and protein purity can also be measured using OD.
I have revised the NTR for 'Optical density measurement of bulk culture assay':
Change to term name: Optical density of cell culture assay evidence
Definition: Optical density of cell culture assay evidence uses optical density measurements at various wavelengths to monitor changes in a population of cells.
This can fall under ECO:0001563 ‘cell-based assay evidence’, however we still need a term to capture the use of OD measurements of cell cultures because this is a standard laboratory procedure that is not represented by any current ECO term. This term cannot fall under:

Cell growth/cell proliferation - because OD, along with cell growth, can also be used to monitor cell death, changes in cell shape, cellular production of light scattering components, etc.

Cell counting assay - because you cannot directly count cells using OD measurements, you can only approximate.

We agree that the term you want does not fit well into any existing terms under 'cell-based assay'. We feel that that the OD measurements you describe are measuring something about the populations of cells but cannot discriminate exactly what is being measured. So we suggest the following new term which will be a child of 'cell-based assay evidence':
'cell population optical density evidence'
definition: A type of cell-based assay evidence in which optical density is used to measure some aspect of a population of cells. Examples of aspects that can effect optical density measurements include, but are not limited to, cell number and cell shape.
Please let us know your thoughts.