Mobile branch v4.12.1 linenumbers above 9 not displayed correctly on iOS/Safari

I just got the latest mobile branch v.4.12.1 and tested on iOS 8.1.3 in Safari and the linenumbers above 9 are not displayed correctly. The digits are drawn on top of each other.
The latest master branch doesn't have this problem, but it still got the nasty cursor bug which isn't anymore on the mobile branch :) Both bugs are important to me and neither branch fixes both :(
Here a screenshot of the linenumber problem:

I can't reproduce this issue (using iOS 8.1.3 as well) -- the line numbers show up fine for me. If you strip down your test case to just an editor, and remove extra CSS, does the problem still occur?

This problem is present on iPad iOS 8 and Android 4.2.2 tablet on codemirror 5.0 when there is more than 99 rows as seen in this picture.

Also note that at the two red arrows in the image the numbers go
10
10
So it appears that this is not just a styling issue as the number 10 (or could be 100 as the 0s could be on top of each other) is repeated twice.
This issue is also present on the codemirror website by just hitting backspace until you go past line 100 so it doesn't seem to be cause by our styling implementation.
http://codemirror.net/demo/marker.html

I ran into the same problem in Android TextView using the master branch code (haven't tested with mobile branch yet), and fixed it with a css style.
.CodeMirror-gutter-elt {
white-space: nowrap;
}
I think it is just a styling issue. "0" in "100" is wrapped to the next line and overlaps with "0" in "101", and the wrapped "1" in "101" overlaps with "0" in the "102" line, etc..
The problem doesn't occur in a desktop browser. I have no idea why ...

I've managed to reproduce this. The line number gutter's width is automatically adjusted to fit the actual numbers' width, but it seems that in some cases on iOS a rounding error made the resulting elements too narrow. Attached patch adds an extra pixel to compensate for this, and for good measure also adds the nowrap rule. The problem is no longer showing up for me now.

I can also confirm that it's working fine now. Thanks.


Edit

👷 Deploy Preview for adoring-leavitt-e31a11 processing.

Name
Link

🔨 Latest commit
864e1abc11288c2723a2b37e2996309a4e5309f5

🔍 Latest deploy log
https://app.netlify.com/sites/adoring-leavitt-e31a11/deploys/62a1d480178c7000089e5bb7


Fix directory installation on rebuild

This fixes a minor bug that prevented the project to be built twice in a row without crashing.

This has been used in the builds before moving to BoringSSL and working merging.


Latest jquery broke YUI compressor

Looks like yui doesn't support ecmascript5+. Issue reported almost a year ago with no traction: https://github.com/yui/yuicompressor/issues/234
Switch to using CLOSURE compiler for js which seems to work better.
        <jsEngine>CLOSURE</jsEngine>
        <closureLanguage>ECMASCRIPT5</closureLanguage>

Closure compiler leaves line breaks every 500 or so chars (https://developers.google.com/closure/compiler/faq?csw=1#linefeeds) so also need to update the minification test.

Closure compiler leaves line breaks every 500 or so chars (https://developers.google.com/closure/compiler/faq?csw=1#linefeeds) so also need to update the minification test.


Make Darwin compilation works

Due to some cgo dependencies, we cannot cross-compile Darwin binaries. Compile them using a Darwin Travis node. Bblfsh cannot run on Darwin, so we will need to skip integration tests doing like here: https://github.com/bblfsh/client-go/blob/64416eecb5321d57179f787750f191fb6da045ce/client_test.go#L25

what if we run bblfsh in docker

Bblfsh cannot run on Darwin
What does it mean? We cannot compile it on OSX?

Bblfsh is run on docker right now, isn't it? It should not be a problem. I run it on docker on darwin and I have no problem with it.
Also, we might want to revisit the idea of compiling this on a darwin travis node. The build queue for OSX machines in travis is huge and the waiting time for them is a lot. It was so much that for enry we went with cross-compile from linux. An example of how to do that is on the enry makefile.

I've been trying to cross-compile this from linux but it's been basically hell. xgo didn't do it either. So I'm gonna give up and just use a travis macOS instance to upload the binary.


Theming is not applied for number input background

The background color of the number input cell overlay is not adapted to the provided theme. In this example with the dark theme, the number input has a white background (and white font) while all other cell editors have the black background:

Fixed in 3.4.0


Add option to change the default date range

By default, pingwatch shows you the last 14 days of data. For some people that might be too much, and it should be configurable.

Hi,
thanks for merging my PR :+1:
I currently run pingwatch with interval of 10 seconds to 8 or 9 destinations.
2 days worth of data were already >100k entries in pingwatch.sqlite and had some loading time in the browser, so i decided 1day is fine for me. But the trigger is easily changeable.
Maybe the long term goal was some timeseries database like influxdb, where you have a co6*nfigurable retention policies? I'm certainly no expert on this, but I could somehow plug together some systems with influxdb and grafana in the past.
(I am lucky I found the "insert into" statement in your go code so that I could know which date format you were actually using - tbh. I had never seen julian date format being used anywhere, but I knew it were no unix timestamps)
br

On Sep 22, 2020, at 14:35, aslmx<EMAIL_ADDRESS>wrote:
thanks for merging my PR 👍
I currently run pingwatch with interval of 10 seconds to 8 or 9 destinations.

I was wondering how many, as I feared the legend would not scale to large numbers of destinations.
Just out of curiosity, are you using this to measure your Internet connection, or to monitor server uptime?

2 days worth of data were already >100k entries in pingwatch.sqlite and had some loading time in the browser, so i decided 1day is fine for me. But the trigger is easily changeable.

SQLite is not the issue, but parsing CSV in the browser probably is. I pushed an update yesterday to use Dygraph’s native format, which should speed things up, in preparation for adding the auto-refresh feature you asked for. It should be significantly snappier already. I also just added the option to change the default display window.

Maybe the long term goal was some timeseries database like influxdb, where you have a co6*nfigurable retention policies? I'm certainly no expert on this, but I could somehow plug together some systems with influxdb and grafana in the past.

There is a new embedded DB called DuckDB that shows promise for analytic applications. It doesn’t have Go bindings yet, however. Something relatively heavyweight like InfluxDB would defeat the purpose of having a single self-contained executable small enough to run without taxing a RPi like the one I have installed in my in-laws’ closet.

(I am lucky I found the "insert into" statement in your go code so that I could know which date format you were actually using - tbh. I had never seen julian date format being used anywhere, but I knew it were no unix timestamps)

It’s the native SQLite date/time format, such as it is. I agree it’s a rather strange choice.
--
Fazal Majid
<EMAIL_ADDRESS>			+44 7367 212202
27 Westfield, 15 Kidderpore Ave                 www.majid.info
London, NW3 7SF

On Sep 22, 2020, at 14:35, aslmx<EMAIL_ADDRESS>wrote:
Maybe the long term goal was some timeseries database like influxdb, where you have a co6*nfigurable retention policies? I'm certainly no expert on this, but I could somehow plug together some systems with influxdb and grafana in the past.

InfluxData’s Telegraf has a ping plugin, BTW:
https://github.com/influxdata/telegraf/tree/master/plugins/inputs/ping

Obviously it’s a full-featured solution that can do a lot more than simply monitor ping times, but that brings along unavoidable complexity.
--
Fazal Majid
<EMAIL_ADDRESS>			+44 7367 212202
27 Westfield, 15 Kidderpore Ave                 www.majid.info
London, NW3 7SF

On Sep 22, 2020, at 14:35, aslmx @.***> wrote: thanks for merging my PR +1 I currently run pingwatch with interval of 10 seconds to 8 or 9 destinations.
I was wondering how many, as I feared the legend would not scale to large numbers of destinations. Just out of curiosity, are you using this to measure your Internet connection, or to monitor server uptime?

Both. Uptime/Reachability of two of my servers, Reachability of my DNS provider (had some issues in the past) and general connectivity.

2 days worth of data were already >100k entries in pingwatch.sqlite and had some loading time in the browser, so i decided 1day is fine for me. But the trigger is easily changeable.
SQLite is not the issue, but parsing CSV in the browser probably is. I pushed an update yesterday to use Dygraph’s native format, which should speed things up, in preparation for adding the auto-refresh feature you asked for. It should be significantly snappier already. I also just added the option to change the default display window

I'm building it right now :+1:

Maybe the long term goal was some timeseries database like influxdb, where you have a configurable retention policies? I'm certainly no expert on this, but I could somehow plug together some systems with influxdb and grafana in the past.
There is a new embedded DB called DuckDB that shows promise for analytic applications. It doesn’t have Go bindings yet, however. Something relatively heavyweight like InfluxDB would defeat the purpose of having a single self-contained executable small enough to run without taxing a RPi like the one I have installed in my in-laws’ closet.
Never heard of... If the libraries are either statically linked (i understand that this would then not require any dependencies for the binary, right?) or very commonly available in Distributions repository, i'm open for it - Your choice!

I heard about Telegraf, but i did not yet have the time to look further into it, but thanks for reminding me.
Thanks for your efforts!


Add ability to import connections from other solutions

This includes for example putty, mremote, and more

This is probably not going to happen since there are so many incompatibilities.


RFC for minimum balance or fee

@o1pranay might have insights here.
The idea here is to prevent people from

filling the ledger
making a bunch of garbage transactions

Per @cmr 's suggestion, we could also maybe "charge rent" in some way.

Will dig into it, and find out what other networks do.
From talking to Luke, Tezos has a 0.257ꜩ origination burn fee, or roughly ~$0.30


Add PPP for Jia Rong

Codecov Report

Merging #199 (7da4398) into master (aad177c) will increase coverage by 1.16%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #199      +/-   ##
============================================
+ Coverage     73.26%   74.43%   +1.16%
- Complexity      584      626      +42
============================================
  Files            94       94
  Lines          1803     1932     +129
  Branches        232      272      +40
============================================
+ Hits           1321     1438     +117
- Misses          403      410       +7
- Partials         79       84       +5

Impacted Files
Coverage Δ

...du/address/logic/commands/CreateFolderCommand.java
92.00% <0.00%> (-8.00%)
:arrow_down:

.../java/seedu/address/model/util/SampleDataUtil.java
16.00% <0.00%> (-4.00%)
:arrow_down:

.../logic/commands/DeletePersonFromFolderCommand.java
74.35% <0.00%> (-1.65%)
:arrow_down:

.../seedu/address/logic/parser/EditCommandParser.java
92.10% <0.00%> (-0.21%)
:arrow_down:

.../seedu/address/logic/parser/FindCommandParser.java
100.00% <0.00%> (ø)

...eedu/address/logic/parser/DeleteCommandParser.java
100.00% <0.00%> (ø)

...du/address/logic/commands/DeleteFolderCommand.java
100.00% <0.00%> (ø)

...address/logic/parser/FindFoldersCommandParser.java
100.00% <0.00%> (ø)

...in/java/seedu/address/commons/util/StringUtil.java
96.87% <0.00%> (+0.87%)
:arrow_up:

...in/java/seedu/address/model/folder/FolderName.java
81.25% <0.00%> (+1.25%)
:arrow_up:

... and 4 more

Continue to review full report at Codecov.

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


Error: 304

Error trace for<EMAIL_ADDRESS>🔥  / Error: 304 on http://localhost:45678/
 at Promise (/node_modules/minimalcss/src/run.js:249:29)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)
(node:78612) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Protocol error (Network.getResponseBody): Target closed.
(node:78612) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:78612) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): Error: Protocol error (Network.getResponseBody): Target closed.
error An unexpected error occurred: "Command failed.

Update minimalcss to 0.7.3 error happens at  node_modules/minimalcss/src/run.js:245:29
304 stands for Not Modified so maybe we do not need to throw error here?

Update minimalcss to 0.7.3 error happens at  node_modules/minimalcss/src/run.js:245:29

Shouldn't it be if (withoutjavascript)?
      if (!withoutjavascript) {
        // First, go to the page with JavaScript disabled.
        await page.setJavaScriptEnabled(false);
        response = await page.goto(pageUrl);
        if (!response.ok()) {
          return safeReject(new Error(`${response.status()} on ${pageUrl}`));
        }
        const htmlVanilla = await page.content();
        doms.push(cheerio.load(htmlVanilla));
        await page.setJavaScriptEnabled(true);
      }

Another finding: Google web fonts uses User Agent Sniffing, so Google fonts css should be left untouched.

The whole point of us looking at statuses where the code was [300, 400] is so that we can write down what the URL redirects to. That way we can "track" what Chrome does already but have a record of all redirects.
So ultimately we're only really interested in "Was there a redirect?". We currently have this:
        } else if (response.status() >= 300) {
          // If the 'Location' header points to a relative URL,
          // convert it to an absolute URL.
          // If it already was an absolute URL, it stays like that.
          const redirectsTo = new url.URL(
            response.headers().location,
            responseUrl
          ).toString();
          redirectResponses[responseUrl] = redirectsTo;

Can we change that to:
        } else if (response.status() >= 300) {
+         // Not all 3xx statuses means a redirect happened.
+         if (response.headers().location) {
+           // There was a redirect!
            // If the 'Location' header points to a relative URL,
            // convert it to an absolute URL.
            // If it already was an absolute URL, it stays like that.
            const redirectsTo = new url.URL(
              response.headers().location,
              responseUrl
            ).toString();
            redirectResponses[responseUrl] = redirectsTo;
+         }

That way, if it was a 304 it stays within this block (and doesn't attempt to do response.text().then(text => {).

https://github.com/peterbe/minimalcss/pull/165 is merged now.


added mul to backend fieldops

This change is

#441  👈
dev

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

Join @ohad-starkware and the rest of your teammates on  Graphite


fix: lets avoid terraform removing k8s resources

as sometimes TF is connected to the wrong cluster ;)

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign jstrachan
You can assign the PR to them by writing /assign @jstrachan in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jstrachan: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm-kapp
02982fdd02c2d479bffee2a172bff4b1c5c5a199
link
/test gsm-kapp

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

/retest

/approve

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jstrachan
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jstrachan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Add lemmas for the obvious bounds of AND and OR.

Note: you almost certainly don't want to merge this as-is. I'm just following up on this list message since I happened to have the time and the message indicated that it might be useful. I'm sure that someone who knows what they're doing could do this far more elegantly.

Thanks Adam. The FStar.BitVector module is still very crude and in my opinion those changes are very welcome.
Because it is generally bad to let modules grow to large (it clobbers the SMT context), I suggest that in a new future we split the module into several chunks (e.g. a Core module with only the bitvector definition, a Lemma module with all useful lemmas, a Trigger module, adding SMT triggers to those lemmas to experiment with better automation, etc.
I will open a separate issue for that, in the mean time let us merge this PR.


should helm_resource always use k8s_context()?

It feels like helm_resource should respect k8s_context() by passing --kube-context={k8s_context()} (pseudocode) to helm. I've got a naive, untested implementation here, but I'm guessing there might be a better, more maintainable solution?

i believe the way it currently works is that tilt generates a custom kubeconfig for subprocesses to use with only one context, sets the KUBECONFIG environment variable, and helm respects that. No need to pass --kube-context directly

There doesn't appear to be any bug report here, so I'm going to close this issue. Let me know if I missed something!

Update: this definitely doesn't work as intended, at least for the delete_cmd part of helm_resource.
Can we reopen this and #598 ?

Sure, can you add more details on what you tried, what you expected to happen,  and what happened instead?

for what it's worth, here are the repro steps i tried:

Created two kubectl contexts -- kind, and a dummy kubectl context connected to a dead cluster.
kubectl config set-context kind-kind
Ran tilt up in https://github.com/tilt-dev/tilt-extensions/tree/master/helm_resource/test
kubectl config set-context dummy
tilt trigger helloworld
Confirmed that the helm chart was deleted and re-installed to the cluster successfully

Instead, for 2, kubectl config use-context dummy, then tilt up --context kind-kind

(thx for trying to repro btw :) )

we received a bug report about kube contexts not resolving correctly sometimes if you were using docker compose and kubernetes in the same tiltfile - https://github.com/tilt-dev/tilt/issues/6453
was that possibly the issue here?

I was building images with docker, but no docker compose

If you see this comment, the issue is tilt's --context not being respected by helm_resource

(obvs when you get a chance), can you try

Create two kubectl contexts -- kind, and a dummy kubectl context connected to a dead cluster.
kubectl config use-context dummy
Ran tilt up --context kind-kind in https://github.com/tilt-dev/tilt-extensions/tree/master/helm_resource/test
Check if tilt installs into the kind cluster or errors trying to install into the dead cluster

sure, here's what i tried:
https://github.com/tilt-dev/tilt-extensions/pull/624
seems to work correctly:
https://app.circleci.com/pipelines/github/tilt-dev/tilt-extensions/1726/workflows/0f14996e-bca2-4753-8fb4-dbd6b96b1b4a/jobs/4203


Add kubeadm support for Istio local test installation

Describe the feature request
Many PRs are blocked due to test failures, I feel a bit bad about the contributing experience. I think reproducing a test environment is the first step to reduce the failures but I was blocked in creating a local test environment.
I tried minikube and has no luck so far because my VM does not support nested virtualization even if I have installed kvm.
I am a Kubernetes maintainer and many k8s contributors are using kubeadm which supports single-node mode as well.
Describe alternatives you've considered
To workaround the unsupported nested virtualization issues, I am working on deploy Istio cluster via kubeadm tool. I would like to contribute the startup scripts and hope can help people who have the same troubles.
Additional context

cc @costinm @gargnupur @hklai @JimmyCYJ

If no one has objection to this, I will send a PR...

The group is also working on a new test framework that runs all required istio components in memory without having to depend on k8s or gke. That should greatly improve testing/contributing experience.
However, that does not necessarily remove the need for testing with a cluster. So something like this can still be useful in the cases you described.

@m1093782566 - note I use kubeadm (on bare metal) for all my workflows.  You may (or may not) find these scripts helpful:
#!/bin/bash

set -xe

echo Deploying Kubernetes
sudo kubeadm init --config=$HOME/kubeadm.conf

echo Setting Credentials for kubectl access
mkdir -p $HOME/.kube
sudo -H cp /etc/kubernetes/admin.conf $HOME/.kube/config
sudo -H chown $(id -u):$(id -g) $HOME/.kube/config

kubectl taint nodes --all=true  node-role.kubernetes.io/master:NoSchedule-

echo Deploying Calico CNI
kubectl apply -f $HOME/calico.yaml

echo Deploying metallb
kubectl apply -f https://raw.githubusercontent.com/google/metallb/v0.3.1/manifests/metallb.yaml
kubectl apply -f $HOME/configmap.yaml

where configmap.yaml is:
apiVersion: v1
kind: ConfigMap
metadata:
  namespace: metallb-system
  name: config
data:
  config: |
    address-pools:
    - name: my-ip-space
      protocol: arp
      arp-network: <IP_ADDRESS>/26
      cidr:
      - <IP_ADDRESS>/30

and kubeadm.conf is:
apiVersion: kubeadm.k8s.io/v1alpha1
kind: MasterConfiguration
clusterName: falkor07
networking:
  serviceSubnet: <IP_ADDRESS>/16
  podSubnet: <IP_ADDRESS>/16
apiServerExtraArgs:
  runtime-config: admissionregistration.k8s.io/v1alpha1

Note I test with multicluster, which is the rationale behind changing the service and pod subnets.  If you don't want to do that, you can leave those out.   Also I think the runtime-config is no longer needed in kubernetes 1.9+.
My calico.yaml is calico upstream modified to network my pod and service subnets correctly.
metallb is a bare metal load balancer.
Cheers
-steve

thanks @sdake - it is truely helpful to my work. I will add these scripts into my PR :)

@m1093782566 can you change our circleci scripts to deploy kubeadm instead of localkube? This will make sure that the kubeadm setup is well tested, and help you accurately reproduce CI failure locally as well.
All the circleci configs are in .circleci/.. We are currently launching localkube for our e2e tests. Would love to have kubeadm there instead.

Sure @rshriram
I am happy to join the work and it would be great if you can provide more context.

I just created a new issue for tracking this task, xref: #8365


update pls

hello, could you update cheat, pls?

I'll update it today

https://github.com/Blaumaus/le_chiffre/releases/tag/v1.4.2 sorry for a delay


Request: galaxy effective radius in sherlock_classifications table

It would be really useful for some queries to be able to use host galaxy radius in the tables (the half light radius, Kron radius, or whatever measure is provided by many catalogs). E.g. if I only want transients in compact dwarf galaxies.
The older version of Lasair included major_axis_arcsec from NED, but in Lasair-iris no measurements are reported. Using the Kron radius from PanSTARRS, or petrosian radius from Sloan, would probably be most useful and cover the largest number of galaxies.
Ideally this could be included information both as angular radius and physical radius if distance is known.

Matt -- Can you pick out what you want from the full Sherlock output? -- Roy
{
"classifications": {
"ZTF21abbzhvg": [
"NT",
"The transient is synonymous with <a href="https://ned.ipac.caltech.edu/cgi-bin/objsearch?objname=2MASXJ16222678+0737007&extend=no&hconst=73&omegam=0.27&omegav=0.73&corr_z=1&out_csys=Equatorial&out_equinox=J2000.0&obj_sort=RA+or+Longitude&of=pre_text&zv_breaker=30000.0&list_limit=5&img_stamp=YES\">2MASXJ16222678+0737007; an r=16.51 mag galaxy found in the NED/SDSS catalogues. It's located 0.4" (0.5 Kpc) from the galaxy core. A host z=0.072 implies a m - M = 37.56."
]
},
"crossmatches": [
{
"catalogue_object_subtype": "multiple",
"catalogue_object_id": "2MASXJ16222678+0737007",
"z": 0.072089,
"unkMag": 17.1,
"separationArcsec": 0.3710646029979128,
"northSeparationArcsec": "-0.4",
"eastSeparationArcsec": "0.0",
"association_type": "NT",
"catalogue_view_name": "multiple",
"transient_object_id": "ZTF21abbzhvg",
"catalogue_table_name": "NED/SDSS",
"catalogue_table_id": 68,
"catalogue_view_id": 29,
"classificationReliability": 1,
"scale": 1.373188,
"distance": 325.549219,
"distance_modulus": 37.563083,
"major_axis_arcsec": 24.599999999999998,
"direct_distance": null,
"direct_distance_scale": null,
"direct_distance_modulus": null,
"catalogue_object_type": "galaxy",
"search_name": "multiple",
"raDeg":<PHONE_NUMBER>31531,
"decDeg": 7.616751004102683,
"original_search_radius_arcsec": "multiple",
"physical_separation_kpc": 0.5095414600614979,
"merged_rank": null,
"photoZ": null,
"photoZErr": null,
"_r": 16.5142,
"_rErr": 0.015218,
"_g": 17.2973,
"_gErr": 0.0170546,
"_i": 16.0778,
"_iErr": 0.0133541,
"_z": 15.9029,
"_zErr": 0.0260184,
"_u": 19.2743,
"_uErr": 0.15441,
"rankScore":<PHONE_NUMBER>730031,
"rank": 1
},
{
"catalogue_object_subtype": "G",
"catalogue_object_id": "2MASX J16222678+0737007",
"z": 0.072089,
"unkMag": 17.1,
"separationArcsec": 0.3739051362534249,
"northSeparationArcsec": "-0.4",
"eastSeparationArcsec": "0.0",
"association_type": "NT",
"catalogue_view_name": "tcs_view_galaxy_ned_stream",
"transient_object_id": "ZTF21abbzhvg",
"catalogue_table_name": "NED",
"catalogue_table_id": 68,
"catalogue_view_id": 29,
"classificationReliability": 1,
"scale": 1.373188,
"distance": 325.549219,
"distance_modulus": 37.563083,
"major_axis_arcsec": 24.599999999999998,
"direct_distance": null,
"direct_distance_scale": null,
"direct_distance_modulus": null,
"catalogue_object_type": "galaxy",
"search_name": "ned spec galaxy physical (within 1.2 * major axis) (redshift distance)",
"raDeg":<PHONE_NUMBER>,
"decDeg": 7.61675,
"original_search_radius_arcsec": 36.41162025884292,
"physical_separation_kpc": 0.5134420462415681,
"merged_rank": 1,
"rankScore":<PHONE_NUMBER>730031
},
{
"catalogue_object_subtype": 3,
"catalogue_object_id":<PHONE_NUMBER>149498184,
"z": 0.0720786,
"_u": 19.2743,
"_uErr": 0.15441,
"_g": 17.2973,
"_gErr": 0.0170546,
"_r": 16.5142,
"_rErr": 0.015218,
"_i": 16.0778,
"_iErr": 0.0133541,
"_z": 15.9029,
"_zErr": 0.0260184,
"separationArcsec": 0.3710646029979128,
"northSeparationArcsec": "-0.370137",
"eastSeparationArcsec": "-0.026435",
"association_type": "NT",
"catalogue_view_name": "tcs_view_galaxy_sdss_spect_galaxies_qsos_dr12",
"transient_object_id": "ZTF21abbzhvg",
"catalogue_table_name": "SDSS DR12 SpecObjAll Table",
"catalogue_table_id": 48,
"catalogue_view_id": 14,
"classificationReliability": 1,
"scale": 1.3730061,
"distance":<PHONE_NUMBER>,
"distance_modulus": 37.5627542,
"major_axis_arcsec": null,
"direct_distance": null,
"direct_distance_scale": null,
"direct_distance_modulus": null,
"catalogue_object_type": "galaxy",
"search_name": "sdss spec sn physical (redshift distance)",
"raDeg":<PHONE_NUMBER>31531,
"decDeg": 7.616751004102683,
"original_search_radius_arcsec": 36.416444180400944,
"physical_separation_kpc": 0.5094739634102126,
"merged_rank": 1,
"rankScore":<PHONE_NUMBER>730031
}
]
}

Hi @mnicholl - I will need to do a little work on Sherlock to integrate the Kron & petrosian radiui. Unfortunately I currently don't have SDSS petrosian radii in Sherlock's SDSS tables, this could be rectified while upgrading the SDSS tables from DR12 to DR16. But I'm assuming the PanSTARRS Kron radii are much greater value in this context? These I do have.
It would be ideal if I could integrate these values into the current Sherlock schema. My proposal would be to use the major_axis_arcsec column that currently only hosts NED values for the galaxy diameter.
The PanSTARRS Kron and SDSS petrosian radii are both measured in arcsec, so I would simply multiply these values by 2 and have them populate the major_axis_arcsec column.
I have griyz Kron radii for PanSTARRS. Which filter do you prefer to port into the Sherlock results? r-band?

Hi @RoyWilliams @thespacedoctor , thanks for replies. In answer to Roy first, major_axis_arcsec sounds like the right one to include in the lasair tables. The magnitudes _g, _r etc would also be very useful for other things.
Dave: Kron radii as good as anything else I think, so starting with those is perfect. And yes including them within the current schema as major_axis_arcsec should still be easy to work with for the user. As for the filter my instinct is r but probably any of gri would be fine, perhaps if there is an object with no radius in r for some reason it could then grab the value from another band, if that isn't too annoying to have to build in...

I will add the major_axis_arcsec value into the sherlock lite output as this is (almost) homogenizable and so can be placed in the top-level crossmatch attributes. With _g and _r we are getting back into the catalogue specific territory, so if these are really needed then we would need to revisit reintroducing the old sherlock_crossmatch table.

Hi Dave, don't worry about the _g and _r then, using the mag and filter as currently implemented are fine for now. I guess looking ahead for LSST, the ugrizy LSST mags of the nearest object should be in there!

This is complete.


8.2: Page List block pagination displays as "Previous" and "Next" when logged out

https://www.concrete5.org/community/forums/customizing_c5/concrete5-8.2-pagination-broken
Steps to reproduce:

add a Page List block on a page
set the "Number of Pages to Display" count so it creates pagination
check "Display pagination interface if more items are available than are displayed."

Logged In:

Logged Out:

If you sign in with non super admin user, you'll see next/previous pager pagination.

I think this is a backward compatibility issue, but core team didn't write about this change in Backward Compatibility Notes section on release note.

Yes, this is the intended behavior; when logged in as super user we don't pass the pages through permissions, so we know exactly how many there are and can display the full set of pages. When you're logged in as anyone else or logged out we use permissions and we can't know for certain how many pages we can display.

But people have to change every block now/edit their templates to make it work, right? I mean, the update means it's not the way it was as before.. At least, it wasn't for me.

But people have to change every block now/edit their templates to make it work, right?

I guess so: for instance the "Next" link at http://andrewembler.com/topics/concrete5 doesn't seems to work xD

OK.. so that means that every site will be affected upon update. Wouldn't it make more sense to not have this behavior on existing sites? I mean, one would not expect this to happen. It's not really friendly to those updating their site, expecting to have a simple thing like this still working and in place on their pages. Right?

Personally I'm not a big fan of pagination, I actually prefer pages to be longer with more items.
But my concern here is that some people seem to love pagination, and would continue to expect seeing it for things like blogs.
Would something like this be able to be handled with a config option (not through the interface, but able to be adjusted via config files)?
'Efficient PageList Pagination'
Upgrades would default to no, new installs yes.

Correct @Mesuva
Having things working as it worked before on existing sites would be awesome. I've read the "There are some backward compatibility issues with version 8.2.0" in the blog post, but there was no mention of this particular behavior. It's only after browsing some pages after I saw this happening (and thought it could be a bug in my templates, rather than new behavior).

@aembler
Losing page number pagination seems like a significant loss.

When you are doing a search or looking for a page in a page list, there could be 2 pages or 2000, you would never know.
It is hard to keep track of where you are in the pagination/results.
If you are searching through a page list that is sorted by date for example, if the page is in the far future or past, you would have to keep clicking and clicking to get to find it.
It is a breaking change that requires updating all themes and add-ons that have custom and/or styled pagination.

A suggestion, and polite request, would be to make the page number pagination the default and make "Previous/Next" pagination optional.
Also, I wonder if the "Previous/Next" pagination could be improved by showing a page number without knowing the full result count.
Example: https://newrepublic.com/tags/politics?page=4

If the justification for changing pagination to a simple prev/next is to support better performance with page permissions, then I can only conclude there is something fundamentally wrong with the way permissions are implemented.
On a more general point, all these 'little' backward compatibility issues with every update add up to an ongoing trickle of unnecessary work on any one site and a massive number of lost hours across all the developers affected. They are making concrete5 bad for business.

Hmm. Is this not the intended behaviour of the Previous and Next block?!
This does seem like a weird fix.

@aembler what's the actual problem here? I agree with all the comments, this is a very ugly breaking change, but I don't see why it was actually done. You're only saying that you don't know how many pages there are, based on that I can only assume that the permission system is too complex to be used in an SQL query?
 Something where permissions by groups are filtered by SQL and the time based features in PHP? That way we would cover the vast majority of sites without having any kind of degradation.
Can you please confirm this? Maybe the community can help out here to come up with a better solution that doesn't break existing sites. As Michele pointed out, even your own site is broken now. I'm sure others will run into the same problem too..

To break it down:
"Because I don't know how many pages we have i just remove the entire functionality before displaying 7 instead of 6"
?

I agree with @Remo. And on top of that, not all sites use these "Advanced Permissions", so it would not affect all, right? So the simple configured ones can still work as it did before, only the advanced ones need some code changes for this (either a combo of PHP + MySQL or whatever we can come up with).

Me too I agree 100% with @Remo

Agree with both @Remo and @MrKarlDilkington

The reason all cars have the brake pedal on the left is because expected behaviour is kinda important sometimes.

I'm with the others here in thinking there must be something more fundamentally flawed in permissions if that's where the bottleneck is. The Auto-Nav block has the option to check permissions and that block gets called a LOT more than the Page List so I'm not sure why it's good for the goose and not for the gander.

Yeah so that page #s element not being displayed is going to be a scaling issue.
I just double-checked and I use Page List as part of a gallery I built for a client. While I can also filter based on Attributes of the entries, having Page #s for something like that means that the Gallery can scale by a lot, but still be accessible.
When you build a website that is intended to have a Page List presenting a very LARGE amount of pages, having only "Next" and "Previous" causes scaling issues.
Let's say you have 10 entries shown per "Page". And you have staff adding... 3 entries per week. In a single quarter that becomes 36 entries. In a year that's 144 entries. Do you really think people are going to go through the trouble of only hitting "Next" or "Previous" to get to the very end?
I'm not sure if this behaviour has been like this for a long time, or this is a recent change, but I genuinely see scaling issues with how it is presented now.
And if we want Concrete5 to be used by more people, these are the kinds of things we need to take into consideration.

I'm sure if need be computational work could be possibly turned into an automated job, or part of the caching mechanism. I just really don't see "computational cost" as a good enough reason for this to not be there. Like, are we suddenly running low on CPU cycles or something? No, we're not. In fact computers are ludicrously powerful, and in many cases there's a glut of available cycles. So which is more improtant, saving a few cycles, or a better UX?
Me, I'm voting UX. My CPU can bend to my will, as it should.

I'd like to request that get back old "Pagination" style as default in 8.2.1, also add a config option to choose new "Pager Pagination" style for large and complex website. I think this is the fastest way to avoid breaking existing sites and keep the discussion about the performance issue.

When we make a website our target is end users.
As they may not be an Engineer, they aren't concern about system performance. They wants greater UI & UX. And it'll be weird if they see there is no pagination on the websites where it was before.
From user perspective, me also like pagination. Because it's convenient.
For example-
I've liked a blog site which is made by concrete5 and it has lots of post which I want to read all. In this circumstance-

First of all, I would like to know how many pages or post there. So that I can guess how much time I need to spend to read all of those.
Definitely it's impossible to read all of those pages on a single sit. So, when I get back to read again I want to jump the pages.

As @hissy said, we can use config option to choose new style or old style.

We also use pagination is almost every website we build. This should definitely be made optional for larger sites and previous default behavior restored. I don't see how this would suddenly be a larger issue if the current pagination system has been working fine for ages. I think @hissy suggested a good solution for this in the future where pagination behavior could be controlled in the settings.

I agree the page numbers should be there simply for UX purposes. I think the end users should always come first, they are who you build the sites for. You don't build the site for the CPU.
As a side note, I kind of feel this has been lately the direction with the latest versions of c5. The direction of development seems to think more on how to make it more technically "superior" (or complex) and giving less attention to the end users.

I guess that for CPU doesn't mean to only save some CPU cycles: it means speed. If you have 100,000 pages and you need yo check the accessibility of every page, it's very easy that it would take a few seconds. I think that's why the core team adopted this solution. BTW I think that this solution should be configurable: if I know that the affected pages are not that many (of if speed is not an issue for me), I'd prefer to have the old fully-featured pagination

@mlocati Yeah, very good point about accessibility, the pages of course need to load fast for anyone to use them in the first place. However, there is already a caching layer that should be easy enough to use, even with pagination (?).
I would back @Remo on putting together an SQL based solution as far as possible. I am aware of the complexity of the permissions system but maybe it would be most likely possible (although not easy) to create something that works well enough for 80-90% of cases.
Or alternatively as you mention above @mlocati, make it configurable to bring back the old functionality.

I think whilst we all except in the name of progress, there may sometimes be a few breaking changes in new c5 versions, it is also becoming difficult for developers to make sure all of their websites are both up to date serving the latest stable version and also all current functionality is working before any upgrade.
IMHO as has been mentioned above - having a config value that can be set on new installs to use the new pagination, whilst leaving this set to false on upgrades will at least allow developer to upgrade sites with more flexibility on time frames to get all sites brought back up to standard.
Without getting in to the granular details of the code, it does seem there must surely be a better solution than to simply drop core functionality.

We will introduce a fix for this in the next day or two that will be
included in 8.2.1. It will restore the old functionality to the public page
list block, while retaining the current next/previous functionality in the
Dashboard.
Some notes:

The existing pagination in 8.1 and earlier caps out at 500 pages
maximum. And since we have to retrieve the pages in order to build the
pagination, we're always grabbing 500 pages or files. On small sites that's
not a problem. On large sites it is. So it's impossible to display an
entire result set that's larger than 500 pages or files unless you don't
care about it being permissioned.

It's not feasible to check permissions through MySQL. If you spent any
time with the advanced access entity functionality you'd know this. There
are so many things that can determine whether a given user can see a piece
of content, and it only gets more complicated with additional access
entities added to the core.

"Get close to 90% of it" – unfortunately, the core can't work for 90% of
sites. It has to work for 100%.

That said, this was a breaking change, and we can fix the vast majority of
the problems here (and in other issues) by simply making the administrative
interfaces use the new functionality while defaulting the public page lists
and other blocks to use the functionality they previously had.

It's not feasible to check permissions through MySQL

Oh, really? I remember legacy version did it (with so complicated SQL). However, this is another discussion. Let's add another issue to discuss about how to improve permission check in page/file/user list.

@aembler I didn't mean to create a solution that only works in 90% of the cases, I've meant a solution that works using pure sql in 90% of the cases and only uses PHP for something advanced like the time limitations. I've hardly ever seen these in the wild and those who use that should be able to come up with a custom solution.
My idea was that we'd return a result set like:

cID
requiresPhpProcessing

1
0

2
1

The page with the cID 1 either doesn't have any permissions assigned to it or only basic permissions that have been processed by sql, the page with cID 2 requires PHP logic. That way we could gradually shift more logic to SQL and make things faster. We could start with only the basic group permission assignments, but that would already improve a lot. At least in my experience.

After a few tests and feedback from users the pagination will have to be brought back. The consensus from my end was a resounding 100% for it.


KAFKA-9261; Client should handle unavailable leader metadata

The client caches metadata fetched from Metadata requests. Previously, each metadata response overwrote all of the metadata from the previous one, so we could rely on the expectation that the broker only returned the leaderId for a partition if it had connection information available. This behavior changed with KIP-320 since having the leader epoch allows the client to filter out partition metadata which is known to be stale. However, because of this, we can no longer rely on the request-level guarantee of leader availability. There is no mechanism similar to the leader epoch to track the staleness of broker metadata, so we still overwrite all of the broker metadata from each response, which means that the partition metadata can get out of sync with the broker metadata in the client's cache. Hence it is no longer safe to validate inside the Cluster constructor that each leader has an associated Node
Fixing this issue was unfortunately not straightforward because the cache was built to maintain references to broker metadata through the Node object at the partition level. In order to keep the state consistent, each Node reference would need to be updated based on the new broker metadata. Instead of doing that, this patch changes the cache so that it is structured more closely with the Metadata response schema. Broker node information is maintained at the top level in a single collection and cached partition metadata only references the id of the broker. To accommodate this, we have removed PartitionInfoAndEpoch and we have altered MetadataResponse.PartitionMetadata to eliminate its Node references.
Note that one of the side benefits of the refactor here is that we virtually eliminate one of the hotspots in Metadata request handling in MetadataCache.getEndpoints (which was renamed to maybeFilterAliveReplicas). The only reason this was expensive was because we had to build a new collection for the Node representations of each of the replica lists. This information was doomed to just get discarded on serialization, so the whole effort was wasteful. Now, we work with the lower level id lists and no copy of the replicas is needed (at least for all versions other than 0).
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Note given the size/risk of this patch, I am planning to submit a smaller fix for 2.4.

retest this please

hi, @hachikuji
I'm still confused about that we can no longer rely on the request-level guarantee of leader availability, I checked the code, If stale partition metadata is detected, the client ignores it and uses the last known metadata, but the last known metadata is also from last MetadataResponse so it should also contain leader info. Why it is normal before KIP-320 but unnormal when using mix of multiple metadata responses?

@dengziming The point I was making is that the cache on the client is no longer guaranteed to contain only metadata from a single response. Because of this, the request-level guarantee on the availability of leader connection information cannot be assumed to hold for the cache in general.


[Key Request] Table 121 "Purch. Rcpt. Line" - Two new keys

For page sorting we need two new keys with Standard fields only. Currently it is not passible to use a table Extension to create new keys on existing tables.
The new keys are:
1. First key
Buy-from Vendor No.,Type,No.
2. Second key
Pay-to Vendor No.,Type,No.

We are going to deliver possibility for partners to add table keys soon. Closing this old request for now.


I broke the build...

Not sure how... I only bumped the version number of the standalone package...
https://travis-ci.org/pact-foundation/pact-provider-verifier-npm/builds/261229517#L4099
Got any idea @mefellows ?

Not sure, but i'll take a look! It looks like it ran on new servers (Trusty), shouldn't be the cause though. I did notice this locally a while back but thought maybe it was my machine.
I'm currently investigating if there is an option to not have to have all of these modules in separate places. There might be away to do the install directly when we install pact-node (or even just pact itself).
Having all of these modules seems a bit... messy.

It does. I'm afraid I'm not enough of a node person to think of a better way to do it.

In any case, i've fixed this (see the .travis.yml file).
I'm not sure why, but it was performing an npm link on all os/architectures which I can't see how it would work. Linking only the correct architecture seems to have done the trick.


BUG Report

Help

Doesn't work with any values

Use Bypass instead but keep on mind that proxies are not working currently

fixed in new update


Purge "multinomial"

Looks great!  Should we also get rid of the categories column in the weights view here, I remember you flagged as unnecessary in a previous commit?

I assume you meant dd_graph_weights.categories? Removing now.


Combat feel

WIP
Combat experience improved, with better fluidity.
Lock times reduced, weapons' hit boxes fit more into their animations.
Working on slight improvements on ranged attacks

Hey @VBoschMatas I think the fluidity can be felt, good job! I'd like to test it more with the last changes on dev, what do you say if we merge dev it into this branch?

The changes you are doing feels great while playing.
I have updated the gamepad controls as you requested:

Melee Attack with X.
Range Attack with RB or LB.
Moved Pickup Parasite to B.

Hope with this we can start all testing with gamepad better.

Now attack sound only play at every attack

Click buffer changed to be a timed buffer, it will remember the last click done in the previous 0.5 sec (can be changed if you feel we need a wider window), but a new click will override the previous buffer so if you chage clicking positions the player will change attacking direction accordingly.

Ranged attacks now are held with the button and you can aim wherever you want, once you release the button it will shoot (animations need updating)


RBTree: Implement custom comparison algorithm

In MS-CFB documentation, it is mentioned that comparing two different directory name follows as below:

A node that has a shorter name is less than a node that has a longer name. (Compare the length of the names from the Directory Entry Name Length field.)
For nodes that have the same name length from Directory Entry Name Length, iterate through each UTF-16 code point, one at a time, from the beginning of the Unicode string.
For each UTF-16 code point, convert to uppercase by using the Unicode Default Case Conversion Algorithm, simple case conversion variant (simple case foldings), with the following notes.<3>Compare each uppercased UTF-16 code point binary value.
Unicode surrogate characters are never uppercased, because they are represented by two UTF-16 code points, while the sorting relationship uppercases a single UTF-16 code point at a time.
Lowercase characters that are defined in a newer, later version of the Unicode standard can be uppercased by an implementation that conforms to that later Unicode standard.

Fix current rbtree module to follow this rule for each node.

Implemented comparison algorithm for directory entry. It uses python's built-in string comparison algorithm. Though it is not perfectly identical with CFB's algorithm, but differences are negligible.


added proof builder

added proof builder
refactored tests

Codecov Report

Merging #12 (07ae97b) into develop (dce71b0) will decrease coverage by 1.97%.
The diff coverage is 78.33%.

@@             Coverage Diff             @@
##           develop      #12      +/-   ##
===========================================
- Coverage    85.81%   83.84%   -1.98%
===========================================
  Files           15       16       +1
  Lines          409      427      +18
  Branches       117      119       +2
===========================================
+ Hits           351      358       +7
- Misses          55       66      +11
  Partials         3        3

Flag
Coverage Δ

unittest
83.84% <78.33%> (-1.98%)
:arrow_down:

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

Impacted Files
Coverage Δ

lib/functions/HttpUtils.ts
76.92% <0.00%> (-0.44%)
:arrow_down:

lib/functions/index.ts
100.00% <ø> (ø)

lib/types/CredentialIssuance.types.ts
100.00% <ø> (ø)

lib/ProofOfPossessionBuilder.ts
75.00% <75.00%> (ø)

lib/CredentialRequestClient.ts
78.94% <77.77%> (-9.95%)
:arrow_down:

lib/functions/ProofUtils.ts
82.75% <82.75%> (ø)

lib/types/Oidc4vciErrors.ts
100.00% <100.00%> (ø)

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


Fail to initialize plugins

Microsoft PowerToys version
0.81.1
Installation method
Microsoft Store
Running as admin
None
Area(s) with issue?
General
Steps to reproduce
When PT launches (system startup), I can see the following error message:

Fail to initialize plugins
Plugins: Visual Studio - fail to load and would be disabled, please contact plugins creator for help

PowerToysReport_2024-05-31-14-05-06.zip
✔ Expected Behavior
No error messages
❌ Actual Behavior
Error message displayed.
Other Software
No response
Related: #17501.

None of the error messages are exactly similar to the one I'm seeing (Visual Studio). I've added a bug report ZIP file to my original post.

Hi @weitzhandler
The error is related to the Visual Studio plugin and since this isn't shipped inside PowerToys the issue should be reported in the plugin repository.
You should update the plugin to the latest release: https://github.com/davidegiacometti/PowerToys-Run-VisualStudio/releases/tag/0.3.1
/helped

That fixed the issue. Thank you ❤


Using Litecoin original codebase

Hello,
It is more a comment/question than a bug/regular issue.
The current master branch of this project contains only 2 commits. The first commit - as far as I understand - is the entire codebase of the project, which was taken from the main Litecoin project :
https://github.com/litecoin-project/litecoin.
So I am wondering why the Litecoincash project didn't fork the original Litecoin project - and all its previous commits - and then add new commits with the changes.
I won't expose all the benefits that such a method would have, but as a simple user, I can't audit the code easily, going through the list of changes, I can't check that the claimed differences between Litecoincash and Litecoin (original) are correct or not, nor from which commit the project was forked from Litecoin (original).
More generally, I can't really trust Litecoincash repository as a Litecoin (original) fork : If I wanted to ensure that the code doesn't contain any malicious lines, I would need to either read the entire code or make a diff between this repository code and the Litecoin (original) repository code by myself.
If the code was forked properly from the Litecoin (original) repository, I would just read the commits that are specific to litecoincash (given that I trust the original Litecoin codebase).
I am sure there is plenty of other arguments (and developer-wise arguments) for a proper codebase fork VS. copy-paste-changes-big-commit.
What to you think ?

Have you seen dev here? They don't care.

Hi Neozaru, in fact you can see full history of every single commit; just look to the staging/integration tree: https://bitbucket.org/l8team/litecoincash/
Essentially we wanted to be on Github because it's the norm for coins and you gain the ability to have the visual link to the upstream, but our team always used Bitbucket internally.
The practice of seperate integration and release trees isn't ideal and we're working to unify.
Note that release gitian builds are built from the Bitbucket tree, and (for now at least) that's the place to submit pull requests.
@inliquid I'm sorry you feel that way; it's true that we haven't been monitoring GitHub as much as we should, but you can usually find a member of the dev team on our Discord if you need us. Alternatively we always respond to mail to<EMAIL_ADDRESS>

There's a [diff]https://pastebin.com/AZy7n7Tq) of the two repositories posted if you're looking for shenanigans. I agree this move was, unusual, to be charitable.


State of lights not updating

What issue do you have? Please be as thorough and explicit as possible.
The state of the devices are not bring refreshed by the plugin. The control of the devices does work, but if the state changes as a result of an action outside of homebridge it does not detect it. For example turn the devices off through Homebridge, and then in the Govee app turn them on and the accessories page does not show the lights on.
I have two lights and both experience the issue, one LAN enabled and one using Govee Credentials. Restarting does not force the state to update. For example, the below device is "off" but shows as on. As mentioned I can turn it off through Homebridge and back on to get it back in sync but it will eventually be out of sync once a change is triggered outside homebridge.

Details of your setup.

Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?
Homebridge UI

Which version of Homebridge/HOOBS do you have?
v1.6.0

Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.
Linux

Which version of this plugin (homebridge-govee) do you have? Has the issue started since upgrading from a previous version?
homebridge-govee v7.2.0

Which Govee devices do you have that are causing issues? Please include product models if applicable.
H6199, H7061

Please paste any relevant logs below.
[11/30/2022, 6:51:24 PM] [Govee] [Flood lights] initialising with options {"adaptiveLightingShift":0,"aws":"enabled","ble":"disabled","brightnessStep":1,"colourSafeMode":false,"lan":"enabled"}.
[11/30/2022, 6:51:24 PM] [Govee] [Flood lights] initialised with id [XXXXXXXXXXX] [H7061].
[11/30/2022, 6:51:24 PM] [Govee] [TV Light Strip] initialising with options {"adaptiveLightingShift":0,"aws":"enabled","ble":"disabled","brightnessStep":1,"colourSafeMode":false,"lan":"unsupported"}.
[11/30/2022, 6:51:24 PM] [Govee] [TV Light Strip] initialised with id [XXXXXXXXXXX] [H6199].
[11/30/2022, 6:51:24 PM] [Govee] [AWS] offline event.
[11/30/2022, 6:51:24 PM] [Govee] [AWS] close event.
[11/30/2022, 6:51:25 PM] [Govee] [AWS] reconnect event.
[11/30/2022, 6:51:25 PM] [Govee] [AWS] close event.
[11/30/2022, 6:51:27 PM] [Govee] [AWS] reconnect event.
[11/30/2022, 6:51:28 PM] [Govee] [AWS] close event.
[11/30/2022, 6:51:32 PM] [Govee] [AWS] reconnect event.
[11/30/2022, 6:51:32 PM] [Govee] [AWS] close event.
[11/30/2022, 6:51:40 PM] [Govee] [AWS] reconnect event.
[11/30/2022, 6:51:40 PM] [Govee] [AWS] close event.
[11/30/2022, 6:51:56 PM] [Govee] [AWS] reconnect event.
[11/30/2022, 6:51:56 PM] [Govee] [AWS] close event.
[11/30/2022, 6:52:28 PM] [Govee] [AWS] reconnect event.
[11/30/2022, 6:52:28 PM] [Govee] [AWS] close event.
[11/30/2022, 6:53:32 PM] [Govee] [AWS] reconnect event.
[11/30/2022, 6:53:32 PM] [Govee] [AWS] close event.

Config
        {
            "name": "Govee",
            "username": "XXXXXXXXXX,
            "password": "XXXXXXXXXX",
            "debug": true,
            "apiRefreshTime": 15,
            "lanRefreshTime": 10,
            "lanScanInterval": 60,
            "lightDevices": [
                {
                    "label": "TV Light Strip",
                    "deviceId": "XXXXXXXXXX",
                    "scene": "XXXXXXXXXX",
                    "sceneTwo": "XXXXXXXXXX",
                    "videoMode": "XXXXXXXXXX",
                    "videoModeTwo": "XXXXXXXXXX",
                    "segmented": "XXXXXXXXXX",
                    "segmentedTwo": "XXXXXXXXXX"
                },
                {
                    "label": "Flood lights",
                    "deviceId": "XXXXXXXXXX"
                }
            ],
            "platform": "Govee"
        },

This seems pretty widespread. Main thread about this issue (started by Ben) here: #367

Is it the same issue? One of my devices supports LAN control, I assumed AWS connection was not used for that.

Closing, please see https://github.com/bwp91/homebridge-govee/issues/367


use new script

@allclark,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Ic 162/extend base peripheral

@blu3beri the name needs to be in the registerOnScannedListener and it must be expecting an onject so I put that back (from the last commend in the other PR I removed it - but that broke the app)
Otherwise feel free to leave comments

@blu3beri you can merge if you're happy with it?! I cannot...


Update zh-HANS.coffee

Translate new Homepage

@wjllance could you look at this PR and resolve conflicts?

@wjllance could you look at this PR and resolve conflicts?

I found there are not too much different translation from our last commit version, maybe we can commit these lines next time:)

@icodegame can you look at your PR again please?


Housekeeping

[x] Updating Go modules

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


ase and split not working

Hi,
Using a multi-sample phased vcf file with eagle2 and even the 1KG phased VCF or a toy VCF. The bam file passed the QC.
Both VCF and BAM are from RNA-seq. split did not give any error but no read was split
Thanks
A

I am sorry for my late reply. I have created an example script that shows how you can use the 1kGP VCF file to split a BAM file and annotate allele-specific counts.
https://github.com/tobiasrausch/alfred/blob/master/example/split_ase_example.sh
Maybe the chromosome naming is different in the VCF and the BAM (chr1 vs. 1)?

Hi Tobias,
Thanks for your feedback. I ran the script you shared and it still does not work. The output file looks like:
chr	pos	id	ref	alt	depth	refsupport	altsupport	gt	af	pvalue
chr22	20010565	.	G	A	0	0	0	0|1	NA	NA
chr22	20023327	.	G	A	0	0	0	0|1	NA	NA
chr22	20034442	.	C	T	0	0	0	1|0	NA	NA
chr22	20037873	.	G	A	0	0	0	0|1	NA	NA
chr22	20038684	.	G	A	0	0	0	1|0	NA	NA
chr22	20038929	.	T	G	0	0	0	1|0	NA	NA
chr22	20039002	.	A	G	0	0	0	1|0	NA	NA
chr22	20039394	.	T	C	0	0	0	1|0	NA	NA
chr22	20041737	.	T	C	0	0	0	1|0	NA	NA
chr22	20042355	.	T	C	0	0	0	1|0	NA	NA
chr22	20044141	.	G	A	0	0	0	1|0	NA	NA
All the refsupport and altsupport are set to 0
Thanks
Best
A

My bad! the download had a problem. I will let you know once I try it on my data.
Thanks
best
A


[Feature]: Only download assets from a specific topic

Description
There are numerous topics in a group, and if I specify the chat_id as well as the range, for example, download_filter: id >= 8244 && id <= 8262, videos from other topics in this group will also be downloaded because they may have been multi-uploading to different topics.
Since the chat_id for all the topics in the group is the same, is there anyway the applet can identify and download the assets (images/videos/etc.) only from specific topics, like https://t.me/c/1745040687/9840 and https://t.me/c/1745040687/49 respectively?
Suggested Solution
A way to download assets only from a specific topic in a group without id range.
Alternatives
No response
Additional Context
No response

@doio hi,what means topic?

@doio hi,what means topic?

I think it's essentially a group, but the contents for each topic is divided by topic tags and they are different and can be easily navigated to?
Ref.
https://telegram.org/blog/topics-in-groups-collectible-usernames
Perhaps, another way to download at the moment is by specifying the hashtag that's in each topic?

Would love that feature too

@doio hi, This is a good feature!

try reply_to_message_id

d94ee7a

Hi @tangyoha This feature is marked as closed. Can you explain how to use it and download from a specific topic?

@jpleite hi, we add filter reply_to_message_id for this, try use bot cmd /get_info to get reply_to_message_id value.

@jpleite hi, if you like this project, please give a star.

Tested just now but getting None  @_@

we will test late

测试没有问题，下载前检查data.yaml是否有之前没有下载完成的任务

@tangyoha Oh, didn't know about the data.yml and the fact that it keeps unfinished failed download IDs. Cleared the file and it seems... It works now!
You could actually append the filter to bot commands, didn't know about that either. However when I typed like your command in the picture, I got this instead and no downloads were initiating:
from CHANNEL_NAME download message id = 1 - 0 !
I wonder why's that.

@doio hi, I will close this issue. please ask question in telegram group.

Hi, this feature has stopped working again, can you check it?  Always reply_to_message_id: None


Improve interface for steady-state insertion operators

We've got nice pluggable operators for generational evolution, but our support for steady-state mechanisms is a little rough around the edges.
Specifically, steady-state algorithms make use of "insertion" operators.  These typically

Receive a new individual
Choose an individual in the population for replacement
Optionally compete the new individual against the replacement and keep the winner.

For step (2), it would be really nice if we could use the same selection operators we use for everything else (ex. ops.tournament_selection, ops.random_selection, etc.).  But these operators return individuals, and for step (3) we need to know the index of the selected individual so we can replace it with the new one.
We've handled this two different ways so far:

In distributed.asynchronous module, we wrote custom insertion functions to that implicitly re-implement hard-coded selection methods as needed, but based on indices.
In the ops.migrate() function, we accepted a standard selection operator as a contestant_selector argument, and then used the population.remove() list operator to delete losing contests.  This searches the population by value, which is problematic (not to mention slow):

It would be nice to have the best of both worlds.
One solution I can think of it having selection operators take an optional argument of a mutable list that they could populate with the indices of the selected individuals.  That's a little ugly, but would give us a way to get index information out of them when we need it, but ignore it when we don't.

Thought: Steady-state evolution is an operator.
What makes steady-state different from generational is that it separates the notion of "updating a population" from "running individuals through a reproductive pipeline."  You have this reproductive process kind of out to the side, and it reaches in to pull and insert individuals into this persistent population over on the other side.
That's why we currently have separate metaheuristics for generation_ea and steady-state EAs.
But, since steady-state reproduction is so different, why don't we think of it as separate from the population pipeline?  Or as its own sub-pipeline?  We could just plug a "steady-state operator" into a generational pipeline something like this:
    ea = generational_ea(generations=100,pop_size=pop_size,
                             problem=problem,
                             representation=...,

                             # Operator pipeline
                             pipeline=[
                                 ops.steady_state_step(
                                     reproduction_pipeline=[
                                         ops.tournament_selection,
                                         ops.clone,
                                         mutate_binomial(std=1.5, bounds=[problem.bounds]*l,
                                                expected_num_mutations=1)
                                     ]),
                                     contestant_selector=ops.random_selection,
                                     evaluator=...
                                 ),
                                 # Some visualization probes so we can watch what happens
                                 probe.PlotTrajectoryProbe(xlim=problem.bounds, ylim=problem.bounds,
                                        contours=problem),
                                 probe.PopulationPlotProbe(),
                                 probe.FitnessStatsCSVProbe(stream=sys.stdout)
                             ]
                        )

This gives us a loosely-coupled view of steady-state EAs as a kind of generational EA that has a nested operator.  The operator takes a population, does something to it, and returns the modified population.
One advantage is that it's easy to toss population-level probes onto the end of the pipeline.
The downside is it's a bit tricky to introduce people to: having a reproduction_pipelien inside another pipeline operator may be confusing and steepen the learning curve.

How does asynchrony fit into this model?
On Sat, May 1, 2021 at 7:55 PM SigmaX @.***> wrote:

Thought: Steady-state evolution is an operator.
What makes steady-state different from generational is that it separates
the notion of "updating a population" from "running individuals through a
reproductive pipeline." You have this reproductive process kind of out to
the side, and it reaches in to pull and insert individuals into this
persistent population over on the other side.
That's why we currently have separate metaheuristics for generation_ea
and steady-state EAs.
But, since steady-state reproduction is so different, why don't we think
of it as separate from the population pipeline? Or as its own sub-pipeline?
We could just plug a "steady-state operator" into a generational pipeline
something like this:
ea = generational_ea(generations=100,pop_size=pop_size,
                         problem=problem,
                         representation=...,

                         # Operator pipeline
                         pipeline=[
                             ops.steady_state_step(
                                 reproduction_pipeline=[
                                     ops.tournament_selection,
                                     ops.clone,
                                     mutate_binomial(std=1.5, bounds=[problem.bounds]*l,
                                            expected_num_mutations=1)
                                 ]),
                                 contestant_selector=ops.random_selection,
                                 evaluator=...
                             ),
                             # Some visualization probes so we can watch what happens
                             probe.PlotTrajectoryProbe(xlim=problem.bounds, ylim=problem.bounds,
                                    contours=problem),
                             probe.PopulationPlotProbe(),
                             probe.FitnessStatsCSVProbe(stream=sys.stdout)
                         ]
                    )

This gives us a loosely-coupled view of steady-state EAs as a kind of
generational EA that has a nested operator. The operator takes a
population, does something to it, and returns the modified population.
One advantage is that it's easy to toss population-level probes onto the
end of the pipeline.
The downside is it's a bit tricky to introduce people to: having a
reproduction_pipelien inside another pipeline operator may be confusing
and steepen the learning curve.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/AureumChaos/LEAP/issues/118#issuecomment-830711163,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZHWSCQBSKEOLG5KPSABYDTLSIIPANCNFSM4Z5CQYOA
.

--
@.***

It ought to be straightforward: a parallel mixed version of the steady-state operator will generate a new individual at each step and send it off to Dask, but insert whatever individual completes next.
Setting the number of processors to zero (or using a non-parallel version of the operator) would restore traditional (non-asynchronous) steady-state behavior.
We could have other variations too: generation gaps of something other than 1 could be handled by a similar operator, or variations like the quasi-generational EA we studied a few years ago.

I think we've stabilized on a solution here:

[ ] finish adding indices arguments to the remaining selection operators,
[ ] add the steady_state_step operator to leap_ec.ops for people who want to use it, with an example app
[ ] rename generational_ea to iterative_ea since it can be used for non-generational algorithms,
[ ] write an example of how to achieve the same thing in an equally simple by writing your own evolutionary loop,
[ ] and add a steady_state_ea metaheuristic so there's an easy off-the-shelf component

This will still leave the asynchronous metaheuristic out, so we'll have a bit of code duplication that isn't unified into a single approach, but that's not a problem for this issue.


Preloading bug

(you don't have to strictly follow this form)
Bug Report
Briefly describe the bug
Syntax error: failed at position 107 ('='):

ALTER TABLE olap.olap_comm_deal_margin_agreement_indicator_di_cube_v37 MODIFY SETTINGS parts_preload_level=3;

Expected one of: CODEC, PRIMARY KEY, end of query, BitEngineEncode, NULL, INTO OUTFILE, ALIAS, COMPRESSION, BLOOM, TTL, Comma, SETTINGS, SECURITY, ENCRYPT, FORMAT, KV, DEFAULT, NOT, BYTE, MATERIALIZED, COMMENT, BitmapIndex, token, AUTO_INCREMENT

The result you expected
The operation was successful
How to Reproduce
https://byconity.github.io/docs/query-optimization/query-optimization-with-cache-preload
ALTER TABLE olap.olap_comm_deal_margin_agreement_indicator_di_cube_v37 MODIFY SETTINGS parts_preload_level=3;
Version
0.4.0

hi @bright-zy, sorry for the mislead. It should be SETTING instead of SETTINGS:
ALTER TABLE olap.olap_comm_deal_margin_agreement_indicator_di_cube_v37 MODIFY SETTING parts_preload_level=3;
We will update the webpages accordingly. Thanks for the feedback!


Unable to change database context in the Query Editor after dropping a database

Create a new database (e.g. ADSTest)
Open a query editor, make sure the context is the ADSTest database.
Create a table in the database (create table dbo.test (col1 int))
Right-click on the database to drop it, select Close Existing Connections
The database will be dropped successfully (yay!)
Back in the query editor window, the database context still shows ADSTest.
From the drop down, try to change the context.  Message is: Failed to change database.
It doesn't appear I'm able to change context with the USE statement either.

Version: 1.46.0-insider (user setup)
Commit: d5a9c172d10dc49ef18b02455835cdba0b938a02
Date: 2023-08-22T18:08:21.002Z
VS Code: 1.79.2
Electron: 22.3.14
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621

Dropping Connections is a SMO-level action, so I wonder if the same problem happens if you delete the database through SSMS and try to change the connection in ADS.

Yes, the same thing happens when deleting the database outside of ADS. So looks like this is more of a connection resiliency thing with the query editor.


Link "Rename and delete feed" is broken

Under section "Feed permissions overview" the link to "Rename and delete feed" is broken.
It is configured to
https://docs.microsoft.com/en-us/azure/devops/artifacts/feeds/edit-feed?view=azure-devops
and it get the page
https://docs.microsoft.com/de-de/azure/devops/artifacts/?view=azure-devops

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

ID: 0e77774e-012a-45cc-d566-7170d86003cd
Version Independent ID: 778dafea-bf98-3292-f451-d82ce8db5bbc
Content: Secure and share packages using feed permissions
Content Source: docs/artifacts/feeds/feed-permissions.md
Product: devops
Technology: devops-artifacts
GitHub Login: @elbatk
Microsoft Alias: elbatk

Thanks @lg2de , @chasewilson we can probably just remove that link altogether, I believe we got rid of that article because it wasn't getting hits and wasn't very helpful.

Responding from the right GitHub account :)
Thanks @lg2de , @chasewilson we can probably just remove that link altogether, I believe we got rid of that article because it wasn't getting hits and wasn't very helpful.


Pin working ldpc dependency

Addresses #133 by pinning prior version.

Looks like checks/all_.py broke since checks-superstaq removed the sphinx_paths argument in favor of using sphinx-autoapi, in this PR.  So let's update the checks-superstaq dependency as well, and fix checks/all_.py here.
Incidentally, I am curious how to use sphinx-autoapi in qLDPC as well.  Let me know if one of the folks on your end can help me out with that sometime 🙂.

Incidentally, I am curious how to use sphinx-autoapi in qLDPC as well. Let me know if one of the folks on your end can help me out with that sometime 🙂.

cc @cdbf1


EditorExportPlugin._export_file is not called for many file types

Godot version
3.5.1.stable
System information
Arch Linux (rolling release). GLES3 backend
Issue description
What I wanted to do: use an EditorExportPlugin to filter files intended for inclusion in a separate pck. I wanted to see if I could use a 'dlc' feature tag to build DLC pcks, and exclude DLC content from the base game, because the built-in export filters are difficult to use correctly (I don't want to manually update a file list every time I add a file to a DLC package).
What I expected: EditorExportPlugin._export_file would be called for each file to being included in the pck (as in the documentation), and I could use skip to exclude it.
What actually happened: _export_file is not called for certain resource types, e.g. PNGs and OGGs. These resources are always silently included in every exported build.
Steps to reproduce

Open the attached minimal reproduction project.
Export a zip using either the linux or windows preset.
Note the text logged to the output panel. This is generated by the addon/export_plugin/export_plugin.gd script:

Including res://Main.tscn
Including res://default_env.tres
Excluding res://dlc/Test.tscn

Open the zip and note that the compiled script in res://dlc/ is included, and the OGG and PNG content are present in .import/.

Given that nothing was logged for the script, OGG, and PNG, it appears that _export_file was never called, and so these resources were included in the zip by default.
Minimal reproduction project
export_plugin_test.zip

Similar issue—I wrote an addon to exclude specific mod content directories when building a game, and noticed files created during gdscript compilation are not passed into _export_file.

Details
Given these files in the folder:
res://MOD_CONTENT/FakeCache/fake_cache.gd
res://MOD_CONTENT/FakeCache/fakecache.tscn
res://MOD_CONTENT/FakeCache/init.gd
res://MOD_CONTENT/FakeCache/mod.json

And this directory in the exclusion list:
res://MOD_CONTENT/FakeCache

The tscn and json files are detected and excluded, however compiled gdc files (as well as remaps) in the excluded dir appear in savepack steps in build log:
...

	savepack: step 27: Storing File: res://MOD_CONTENT/FakeCache/fake_cache.gdc

...

[plugin:_export_file] res://MOD_CONTENT/FakeCache/fakecache.tscn
[plugin:_export_file] Excluding res://MOD_CONTENT/FakeCache/fakecache.tscn

...

	savepack: step 27: Storing File: res://MOD_CONTENT/FakeCache/init.gdc

...

[plugin:_export_file] res://MOD_CONTENT/FakeCache/mod.json
[plugin:_export_file] Excluding res://MOD_CONTENT/FakeCache/mod.json

...

	savepack: step 102: Storing File: res://MOD_CONTENT/FakeCache/fake_cache.gd.remap

...

	savepack: step 102: Storing File: res://MOD_CONTENT/FakeCache/init.gd.remap

...

[plugin:_export_end] Directory exclusion list:
[plugin:_export_end]  - "res://MOD_CONTENT/FakeCache"
[plugin:_export_end] Excluded files:
[plugin:_export_end]  - "res://MOD_CONTENT/FakeCache/fakecache.tscn"
[plugin:_export_end]  - "res://MOD_CONTENT/FakeCache/mod.json"

As well as the output pck:

Still reproducible in 3.6.beta2 and 4.1.beta2.
In 3.5.stable ~ 3.6.beta2,
_export_file is called for .tscn, .tres, .ogv, .otf, .ttf, .shader,
not called for .gd, .png, .ogg, .res.
mrp:
EditorExportPluginBug.zip
In 4.1.beta2,
mrp:
EditorExportPluginBugG4.zip
_export_file is called for .gd, .tscn, .tres, .res, .gdshader, .ogv,
not called for .otf, .ttf, .png, .ogg.

Still valid in 4.3 dev3.

To those subscribed to this issue who are interested in testing an alternate fix to the one that was merged one month ago, I’ve put together a PR that calls _export_file on all resource types: #93878


Tangent space calculation error

Such faces lead to wrong tangent space.
Notice several vertices in row.

Probably, bug in FBX SDK.
Triangulate mesh before export.


[Rendering] Fix frustum culling

At present our frustum culling is both slow and incorrect.
An optimisation was made by @kanerogers to create a virtual frustum incorporating both cameras, but this has not proven to be correct. In addition, the underlying isVisible function in the compute shader is extremely expensive, and should, if possible, be reduced to a plane intersection check.

I'm assuming that #280 addressed the correctness issues. The current code looks reasonable to me in that respect, though I haven't independently audited the math used to extract clipping planes. However, one serious design issue remains:
https://github.com/leetvr/hotham/blob/c3fc0142a9e6d1f9a68d9cbe2ffd8e9def27c19c/hotham/src/resources/render_context.rs#L284-L287
This forces a full pipeline stall and host round-trip between culling and whatever operations follow (presumably, drawing). It should be replaced with appropriate pipeline barriers.

Thanks for looking into this!
re: the hard wait on the Fence, how would we ensure the dispatch is complete when the CPU then reads the cull buffer?
Noting that we are not doing multiDrawIndirect; we are simply iterating through the results of the cull buffer and guiding up our draw commands CPU side. Previously we simply used barriers and drawIndirect, which though technically correct, has serious implementation issues on the Adreno 650 hardware we're targeting.

Ah, I didn't realize you had resorted to reading back the results on the CPU! In that case it might be better to do the culling on the CPU exclusively rather than synchronously shuffling data back and forth, though it's hard to say for sure without profiling and/or benchmarking on the target hardware with representative scenes. Another option is conditional rendering, but that doesn't seem to be supported on the Quest 2.
Is the vendor working on fixing their bugs? Might make sense to hold off on further iteration regardless if a fix is in flight.

I have thought about doing everything on the CPU, but the overhead for CPU
<> GPU seems fairly minimal from my profiling (remembering that we’ve got
unified coherent memory). At the very least, the cost of parallelism should
be in our favour for any real world number of objects.
re: vendor bugs it doesn’t seem to be so much of a bug as a design flaw.
The entire Adreno series seems to not have good support for drawIndirect,
and speaking with Meta and other engine folks (eg. Godot), the solution is
just to not even bother. We can get pretty good results with CPU batching
and GPU instancing, so I’m reasonably happy with this architecture for now,
even though a purely GPU driven renderer would be much more satisfying.
Meta has been (understandably) tight lipped about the hardware for their
upcoming high end headset, but  think we can assume it’ll probably still be
Qualcomm hardware. In any event, it took 5 minutes to implement  the
fence/drawInstanced change, I’d imagine it would take a trivial amount of
time to add an optional path for drawIndirect if we get Vulkan hardware
that properly supports it.
On Sun, 31 Jul 2022 at 2:07 am, Benjamin Saunders @.***>
wrote:

Ah, I didn't realize you had resorted to reading back the results on the
CPU! In that case it might be better to do the culling on the CPU
exclusively rather than synchronously shuffling data back and forth, though
it's hard to say for sure without profiling and/or benchmarking on the
target hardware with representative scenes. Another option is conditional
rendering, but that doesn't seem to be supported on the Quest 2.
Is the vendor working on fixing their bugs? Might make sense to hold off
on further iteration regardless if a fix is in flight.
—
Reply to this email directly, view it on GitHub
https://github.com/leetvr/hotham/issues/275#issuecomment-1200243987, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPNXZ64LHREX3PVRBAZH7LVWVHK7ANCNFSM54JNDRFA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Sounds like this issue is settled for now, then!


[BEAM-12164] Feat: Added SpannerChangeStreamIT to Cloud Spanner Change Streams connector to test transaction tags filtering in the Change Stream records

This change adds SpannerChangeStreamIT integration test verifying filtering of Change Streams records by transaction tag fields. This test will be referenced in Cloud Spanner public documentation for Change Streams Beam.
Design doc: https://docs.google.com/document/d/1qA-PE8CcwNHonhnHG46kOgi7-b9tTnzaZ89daVbeYUU/edit
R: @thiagotnunes
R: @nancyxu123
R: @pabloem

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Run Java PreCommit

lgtm as the test is psasing

Run Java_GCP_IO_Direct PreCommit

Run Java_GCP_IO_Dataflow PreCommit

LGTM

lgtm thanks all!


Check out cocalc support

Having pluto code run in mybinder is great, but how is support for pluto in cocalc?
this thread seems relevant:
https://github.com/sagemathinc/cocalc/issues/5270
We can get a licence for cocalc if that is helpful to explore.

I think that mybinder is a dead end, it's too slow. Will look into cocalc

CoCalc doesn't look like it will work without first installing Julia and Pluto in order to get a Project ID, so no easier than just running Pluto

https://juliacomputing.com/products/juliahub/ might work, although that looks more like something for runnign jobs at "scale" rather than teaching

I think you're right, it looks like it's most useful for a scale that we're not probably concerned about for CATAM


what am I doing wrong?

everything according to instructions, but

what am I doing wrong?

source bin/activate

@Kafkamorph
repeated from scratch was the sad result of the new

That output really tells a lot:

you need to upgrade pip - follow what is shown
python libraries seem to not be in the right place or not installed - did you do a pip install -r requirements.txt?

@Kafkamorph

@Kafkamorph An error appeared on this

@Kafkamorph I tried to python3 instead python2. as a result of all the assembled correctly but does not start

just install python-dev


Dev: Pass .env vars as an object to child process

- Summary
This is to fix an inconsistency in NodeJS which results in process.env not realizing changes if they're accessed shortly after.
Fixes: https://github.com/netlify/cli/issues/747

- Test plan

Have your create-react-app project connected to Netlify production with netlify link.
Have some env variable in Netlify production
Have a .env file in project root locally that overrides that env variable
Run netlify dev and observe the value of that env variable

- Description for the changelog
Pass the variables from .env file as setting.env object to startDevServer, so that, they're set explicitly on the new process.

- A picture of a cute animal (not mandatory but encouraged)
🐳

Ah I see. Thanks a bunch @erezrokah. This was a head scratcher. I never looked at the detectors logic, I thought they only returned application specific env variables.

Can you please take another look @erezrokah

Sure, reviewing now

Yeah. All of the detectors inherit process.env. And it is part of the template, so, the future detectors will do the same.
I suggest that we don't change this since it's explained in the docs and example. But if we do need to, we can do that later.


mx.sym.argsort() cannot sort array with large tensor

For bugs or installation issues, please provide the following information.
The more information you provide, the more likely people will be able to help you.
Environment info
Operating System: ubuntu 14.04
Compiler: GCC4.4.7
Package used (Python/R/Scala/Julia): python
MXNet version: 0.11.0
MXNet commit hash :  568b5a2d3e701768ff6f270238e5edccc2f35ff1
Minimum reproducible example
if you are using your own code, please provide a short script that reproduces the error.
import mxnet as mx
import numpy as np

value = mx.sym.Variable('data')
sorted_adj = mx.sym.argsort(value, axis = 2)

coord_data = np.random.rand(32, 2048, 2048)
coord_blob = mx.nd.array(coord_data, mx.gpu())
e = sorted_adj.bind(mx.gpu(), {'data':coord_blob})
y = e.forward()

result =  y[0].asnumpy()

vis = np.zeros(2048)
for i in range (2048):
    vis[int(result[4, 0, i])] = 1
cnt = 0
for i in range (2048):
    if vis[i] == 0:
        cnt += 1
print cnt

Steps to reproduce

The provided code will give the cnt!=0, which should be 0 because the argsort should return all the integer from 0 to 2047.
If the result[4, 0, i] has been changed to result[3, 0, i] , the result will be correct again.

What have you tried to solve it?
1.If the size of coord_data is (10000, 2048), and the axis in argsort changed to 1, then result[8000, :] will cover from 0 to 2047 as desired; but vis[int(result[9000, i])] will be incorrect again. (I guess it may because 8000<4*2048<9000)
2. By several tests, it seems that the argsort function can only deal with the first 2^24 element.

@sxjscience

I've confirmed. This is a bug. I'll look into what caused it. It may be related to the way I do batched sort.

I've switch to the cub to have a try.

OK, I've found the problem. It's this line https://github.com/apache/incubator-mxnet/blob/master/src/operator/tensor/ordering_op-inl.h#L207. When there are too many elements, the real_t type is not precise enough to store all the index values.

I'll pr the fix after the MShadow side is merged.

Thank you so much for your timely update! @sxjscience


fix: #tno-2090 - radio content content type broken

apparently the library we used to determine contentype type is wrong
an m4a file should map to audio/mp4 NOT audio/m4a
switched to new library
updated all references
removed unused references
small fix for content migrator to fix issue with null settings

Thanks for solving this mystery


Added Scrollviews for buttons and bubbles + animations + clickable markers

Fix issue with right ad being shown for marker


Guarantee order to be called

Codecov Report

Merging #11 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #11   +/-   ##
=======================================
  Coverage   60.72%   60.72%
=======================================
  Files           8        8
  Lines         415      415
=======================================
  Hits          252      252
  Misses        139      139
  Partials       24       24

Continue to review full report at Codecov.

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


Update the release process to match the branching model

Suggested fix for #79

Remove all mention of merging release/ branches into the main branch
Split the version update instructions in two parts:

In release/ branches, it's about removing the dev0, or increasing PATCH only
In the main/ branch, it's about increasing the minor or major version only (keeping .dev0)

Clarify that the hotfixes should be merged in main first, then cherry-picked in any applicable release branch. Remove mentions of "merging" hotfixes branch into "release" branches, this would actually bring a mess from the main branch.

Oopsie, I missed a point to update the version in the release branch too to remove any .dev0 suffix.

Agree with the changes. Thanks @plule-ansys. Let me know when this is ready for review.

@plule-ansys This sounds really good. Thanks for this modification. As @akaszynski  said let us know when it is ready.

Hello, @akaszynski and @MaxJPRey . This is ready for review. Unfortunately for some reason the doc gen was not cooperative, please check locally :)

LGTM. Thanks for the contribution @plule-ansys .


Enable fast saving mode for PNGs

Makes saving PNGs 2.5x faster for me at only 2% (!) increase in filesize, although please note that I only did basic testing.
Helps with Movie Maker, see godotengine/godot-proposals#4751

I'm interested. Not able to review this week due to a brief break from godot engine 4.0 release.

Benchmark
CPU: Intel Core i9-13900K
GPU: GeForce RTX 4090
OS: Fedora 37
Time taken to render https://github.com/Calinou/godot-movie-maker-demo:

Type
AVI
PNG - master
PNG - this PR

Editor 1280×720
1m07s
6m25s
1m41s

Editor 3840×2160
6m49s
48m00s
10m44s

Release template 1280×720
39s
6m36s
1m48s

Release template 3840×2160
3m31s
47m06s
9m37s

File size of first frame in 3840×2160:

PNG - master
PNG - this PR

7,173 KB
9,432 KB

Considering saving time is the most important criterion in Movie Maker, I'd say this increase in file size is fine. It's common for games in general to take large, unoptimized screenshots to ensure they save quickly (so they don't interrupt the action for too long).

! Amazing.

Won't this increase the filesize of every PNG saved by the engine? Not just the ones created by the MovieMaker feature?

t's common for games in general to take large, unoptimized screenshots to ensure they save quickly (so they don't interrupt the action for too long).

I think @myaaaaaaaaa is saying that's a good tradeoff.

It's common for games in general to take large, unoptimized screenshots to ensure they save quickly (so they don't interrupt the action for too long).

I think @myaaaaaaaaa is saying that's a good tradeoff.

@Calinou , not me :slightly_smiling_face:

Won't this increase the filesize of every PNG saved by the engine? Not just the ones created by the MovieMaker feature?

The proper solution would definitely be to add a filesize option to Image::save_png(). This was more of a quick post to bring the existence of PNG_IMAGE_FLAG_FAST to people's attention, but in the form of a PR in case the Godot team wanted to merge it in as an interim solution.

Won't this increase the filesize of every PNG saved by the engine? Not just the ones created by the MovieMaker feature?

It will, but the engine defaults to saving lossless WebP when importing images since 3.5.

In the "Marshalls.raw_to_base64(vp.get_texture().get_data().save_png_to_buffer())" that is very slow, and have several bottleneck point, one being the get_texture itself that can be better implemented to have bigger delay but low cpu usage, the Save_png_to_buffer, is the one that consume the most CPU time.

That said, we could make save_png() accept a compression mode parameter (uncompressed, fast compression, best compression).

I agree we should make this a flag in save_png(). Also discussed it with @reduz who agreed.
Could default to fast compression, but users should still have a way to opt in to best compression if they value size over compression speed.


Reference Index Links Broken

Documentation Related To Component:

Documentation itself
Please check those that apply

[ ] typo
[ ] documentation doesn't exist
[ ] documentation needs clarification
[ ] error(s) in example
[ ] needs example
[x] documentation links broken

Description Of The Issue

All of the links in the index section found at https://rxjs-dev.firebaseapp.com/api are currently broken and returning "Page not found".
For example: https://rxjs-dev.firebaseapp.com/api/index/async

The Images are also broken.
For example: https://rxjs-dev.firebaseapp.com/api/operators/switchMap.png

The images are hopefully fixed with #4191 .
Regarding the broken links. So we changed the urls, maybe that's causing the problem. But I couldn't reproduce it. I could imagine that you used a cached version due to service worker magic. @JaimeStill could you maybe recheck?